Flyspray:: Flyspray:: Rockbox: Recently opened tasks 2016-02-06T17:04:13Z FS#13067: ibasso dx90 Left button does not work 2016-02-06T17:04:13Z 2016-02-06T17:04:13Z
Previous song and Fast Backward are unable to work
yong xu
FS#13066: ibasso dx90 When playing music sometimes crackling sound 2016-02-04T05:54:42Z 2016-02-04T05:54:42Z
When playing music sometimes crackling sound especially when playing bass
yong xu
FS#13065: ibasso dx90 Back button and rewind button does not work 2016-02-04T05:45:50Z 2016-02-04T05:45:50Z
Back button does not work, and sometimes the same function as the forward button.
Rewind button does not work
Of course, I am talking about are the physical buttons,Touch buttons are working properly。
yong xu
FS#13064: Actions are not voiced while in FM radio 2016-01-27T13:48:00Z 2016-01-27T13:48:00Z
Version: e6cd53a-160125

I upgraded from version 1e7b93a-141009 to e6cd53a-160125.
Now, when using the FM radio, none of the voice messages are played.
On [Submenu] the mode is toggled from "Preset" to "Scan" but "Preset" or "Scan"
is not voiced.
On [Select] the presets list is activated but the entries are not voiced
On [Long Select] the FM radio menu is activated but the options are not voiced.
etc ...
The english.voice file is installed correctly:
when I [Long Select] on the "FM radio" option from the main menu the options
are voiced correctly.
If i leave the FM radio by pressing [Home], the radio continues to play
but the main menu is not voiced.
Even if I [Home] while FM radio is muted the main menu is not voiced.
Jim Dunleavy
FS#13063: Volume triggered recording fails to stop 2016-01-09T20:26:51Z 2016-01-09T20:26:51Z
I'm trying to record myself playing the guitar using my old, trusty FuzeV2 (both a very old version - sorry didn't wrote it down but had to be at least a couple of years ago - and today's version 87229a4). Recording parameters as follows:

Trigger: Repeat
TrigType: New file
Prerecord Time: 1s
Start Above: -22dB
for at least: 1s
Stop Below: -26dB
for at least: 1s
Presplit Gap: 1s (don't really understand what it does from the manual, but it says it usually has to be the same value of the Stop Below Time, so...)

Recording starts correctly when noise is detected according to conditions; then apparently it correctly detects the silence and stops the recording. But immediately the 'Repeat Trigger' parameter kicks in and _immediately starts a new recording_. At this point, the trigger status and the recording status aren't matching anymore. The recording screen shows the recording file size growing, but the Trigger status is 'Ready'. I have confirmed that on the actual file on disk the silence is meanwhile recorded.

Did I understand any of the parameters wrong or has anybody else the same problem?
Luca Leonardo Scorcia
FS#13062: gub vorbis codec and eq (bass noise) 2015-12-01T10:33:48Z 2015-12-01T10:33:48Z
Create silence in Audacity program (Generate -> Silence). Convert the wav file to ogg vorbis file. Put into the sansa clip+ player wav and Ogg files. Turn on the equalizer and set 32 hz, 64 hz, 125 hz in the 0.5-2.0.
Turn on maximum volume. Listen to the silence of wav file. Absolute silence. Listen Ogg Vorbis file - hear the noise (like the wind). It's bug with only ogg vorbis. mp3, flac, mp4 is absolute silence.
On a musical files it's additional noise. Ogg vorbis is economical of disk space. Testing on a sansa clip+ with 2GB.
FS#13061: Buttons doesn't work after Hold Switch 2015-11-13T09:53:07Z 2015-11-13T09:53:07Z
Revision a8758c9 and Stable (3.13)

If you use the Hold Switch to Lock Keys and remove it again to unlock, buttons doesn't work.
Move around with finger at touchpad work. After this bottons work without problems.

Start Rockbox
Move the curser over Settings (Example)
Move Hold switch to Lock
Move Hold switch to Unlock
Press Middle Button (Doesnt work)
Move around on Touchpad
Press Middle Button (work)
FS#13060: Seeking in long opus files leads to crash on Sansa Clip+ 2015-10-26T16:24:03Z 2015-10-26T16:24:03Z
possibly related to FS#12851.

When seeking in large opus files, rockbox crashes.
Using git bisect, I found commit 9b7ec42 to be the first one showing this behavior.

The crash screen for the latest git revision d57e651 looks as follows:

Stkov codec
pc:3006008C sp:30803B{cut of due to screenspace ending. Next character could possibly be a '3'}
A: 3008728C
bt end

If I interpret the map-file correctly (and I totally might not), that would put the Program Counter somewhere in cancel_cpu_boost (thread.o).

for 9b7ec42 it is pc:3005E264, A: 3005E2BC. Stackpointer is the same.
Here the pc appears to be in check_tmo_threads (thread.o)

I haven't quite figured out where exactly "large" starts, but it does happen with 4 hour long files (~60MB), but not with 1 hour long files (~20MB). It also does not happen in the Simulator, only on the actual hardware.

Example files:
error occurs:
error does not occur:
Stephan Lohse
FS#13059: MP3 Codec decoding has artifacts 2015-10-22T21:21:06Z 2015-10-22T21:21:06Z
When playing music, I can hear codec errors in the music. It occurs every time on a certain song, and other songs that are smaller in file size, it does not occur on, but occurs on the next one. I believe it is a buffering issue, and makes the music unlistenable. I used the daily on 10/21/2015

On 320kb/s MP3s it occurs much more often, and 128kb/s MP3s it occurs less often, but when it occurs its a series of glitches that distort the music.

I am sure its not the MP3s themselves, because it doesn't occur in the official firmware, and when I rewind it, it does not make the same sound until later. It has a very prominent 'glitchy' sound and later it changes the speed of the song.

I replaced it with the 3.1.3 MP3 codec, and the same glitch occurs.

I do not have a line out so its made through the speaker, but the problem is so bad that you can hear it very clearly.

The MP3 was 320kb/s

Memo is the glitchy one, and Memo-1 is it being played correctly.
FS#13058: sleep timer deactivates the idle power off 2015-10-19T15:40:03Z 2015-10-19T15:40:03Z
Use of the sleep timer deactivates the idle power off. Both should be independent pathways to shutdown. The Idle Poweroff should initiate shutdown if there is no playback and no keypress inside the indicated time. The sleep timer only is to use keypresses. However, the actual behavior is for the sleep timer to disable the idle poweroff. This is a bug. Instead of either or it (If ... else if) should be two "If then .. If then" constructs.

The benefit is that you can save battery life if you leave the device on while player, or if you get interrupted. Currently, you can only do one.

To replicate:
use sansa clip, latest version. Set idle power off at 1 minute and sleep timer at 30 minutes (default). Play then pause for two minutes. Press volume button and note unit is on instead of off.