ROLO is broken on Nano 2G 3.10RC. It just says: Executng… and freezes. Seems to be happening not only for me:

http://www.rockbox.org/mail/archive//rockbox-archive-2011-11/0070.shtml http://www.rockbox.org/irc/log-20111105#23:01:01 (is this also related?) http://forums.rockbox.org/index.php?topic=28467.0

When trying to start RockDoom on the iPod Classic, Doom appears to load normally until the iPod crashes and says "Prefetch abort at 71D0BF24 FSR (domain 0, fault 5)". Build ver. 8abdd9b-120902

The volume settings are bypassed and is at max volume when the plugin is started. Even when putting it at -60DB it still has sound. After exiting and relaunching the app,the volume is maxed again,regardless of volume settings.

(sansa fuze)
for some games (such as pokemon)
when you walk around alot;
it is difficult because even the slightest movement of the wheel activates the pause screen;
I have tried multiple controls setups;
and whatever is setup to use the scrollwhell is always extremely sensitive;
a sensitivity setting should be added, to allow a change in the threshold required to count as a button press

Sound in all games sounds like chirps or clicks that sounds kinda like the real music on the Nano2G.

I noticed, that every time I’m in the car listening to music, and I disconnect the iPod 30G (5th gen), while its playing, and I then try to shut it down, it’ll jump to the main window and will not move away from it.

From this point on, I cannot turn off the device nor more away from the main window. Only a HR will resolve this and let the iPod come back to normal working order.

Further more, while it is in that situation (which it is right now, while I write this), the device won’t even go on sleep or turn off the monitor. So basically, it’ll stay with the screen wide awake and lit up.

The two only buttons that will work are the Hold button, which will in turn, turn off the screen and the scroll will allow me to scroll up and down and around on the main window.

Q: What sort of car connection do you use? Line-out+power, or MSC? Or the accessory
I’m not familiar with these connection and their types. All I know is that it is connected to the car stereo from back (ie. the stereo was pull out and the adapter was connected in the back). Also, that it is a connection that connects to the bottom of the iPod (ie. flat and wide connection). It gives me control from the car’s stereo and the steering wheel. When I bought it and then they hooked it up, they told me this is an iPod adapter.

This DOES NOT happen if first stop the music and go to another menu BEFORE I disconnect it from the adapter.

The manual offered by Rockbox Utility is not necessarily the version that accords with the installed (or to-be-installed) program.

E.g. select Release 3.13, and the Manual offered is http://download.rockbox.org/manual/rockbox-sansafuze.pdf not http://download.rockbox.org/release/3.13/rockbox-sansafuze-3.13.pdf .

http://www.rockbox.org/irc/log-20140124#15:41:22 says this is a bug. Since the user does reasonably expect a manual to accord with the program, I too think this is a bug. Whether it is a design bug or code bug, I cannot guess.

Note: this task says Operating System: All players but only because the actual player, Sansa Fuze, is not offered. Though this issue may indeed apply to all players.

This is basically a documentation update. For several years I generated accessibility voice files on my devices. Then one day I was reinstalling and it would generate a lot of the voice files but die from a weird error. For more than six months I combed the manual and the forums, trying to figure out what had changed, trying to debug it myself. Eventually I stumbled across the problem. I had noticed the “install on player” option in Rockbox Utility and started generating voice files while running from the player. Once I switched back to running Rockbox Utility by launching the utility from my regular PC disk, everything worked again. I again looked for any warning about this in the manual, and didn’t find anything.

The simplest fix is to include something about this in the section on accessibility and generating voice files.

Another fix, probably not worth it, would be for the voice files to use system tmp space for intermediate files. I suspect that the recursive generation of talk files on player ends up in some infinite regression as it generates talk files for temporary files.

This probably happens on all players, but I only experienced it on the iPod Nano 1st Gen.

r28936, sim build for iriver H120, fresh installation folder, i.e. no file “config.cfg”

I modified the function “sim_open” to ouput what files it’s opening, and got the following output (see attached text file). Note that there are files “-.kbd”, “-.sbs” and “-.rsbs”. I think these files should not be opened, even tried.

So, I have a Clip Zip at the moment. Been using rockbox on it since day 1, and since day one i've always had an issue: during playback, when accessing files from the SD card, the player randomly freezes. It's not always, it's not when accessing the same files or some specific characteristic shared by them, it just appears to be random. When it freezes, the LCD usually still responds to my commands (i can access menus, see the file info, even change song and it will display in the playback screen), but the actual playback doesn't, and I eventually have to hard reset it. I guess it's some kind of SD compatibility issues: I have an 8GB class 4 PNY. I know it's not the own card's problem since it worked perfectly on my Clip+ and does on my Android Cellphone.
I've been updating daily builds for this device at least once a week since I got it, and it happens with every build.

I primarily use my unit for audio books while driving, but the latest build (as I write this) won't play one of the files properly. It tries to start, stuck at 0:00. Trying to seek hangs the player altogether, requiring a hard restart.

I've recreated this problem on a flaky Clip+ and an AGPTek Rocker.

The 'file' tool identifies it as: ISO Media, MP4 v2 [ISO 14496-14]

Here's what mplayer has to say (while playing it back properly):

[lavf] stream 0: audio (aac), -aid 0, -alang eng

Rockbox hangs if the disk gets full during database creation.

charging isn’t monitored on ipod 3G. it just goes up to 100% very quickly and stays there.

this is ordinary mp3 file.
I think it was name problem, renamed to simple.
Still not play.
Player Sansa Clip+ (not found in bug report menu)
Rockbox 3.12 (not found in bug report menu)
Standard firmware has no problem with this.
Good luck!

It is 16Mb size so I put it to my dropbox
https://dl.dropbox.com/u/17669498/rockboxbug/08.mp3

Hello

I run rockbox daily (last update 27 Feb 2014) and found an issue that I like to report. I have my sandisk clip zip connected to an external USB hub, which is connected to my notebook. Today I left the sandisk clip zip connected and turned the notebook off. I expected that the player will disconnect from the USB hub → blanks the screen after 20-30 seconds (depending on the setup) and then turns off after a while (depending on the setup). Unfortunately the last step won't happen.

The sandisk clip zip really disconnected from the USB connection (the usb picture disappears from the display) with the notebook going back into the rockbox menu (Play, Radio, Settings, Recording etc.) and after a while also blanks the screen as expected.

Unfortunately it does NOT turn itself off as it would if you leave it entirely unconnected (unwired) with the USB. The sandisk clip zip starts to turn the screen on again after a while, turns off again, turns on again after a while, turns off etc.

I had to plug off the mini USB connection (the wiring between the player and the usb hub) so it turns off and shuts down after a while.

What I believe is, that the USB subroutines might not know the difference between powered on notebook and powered off notebook. It only knows that it's wired and thus tries to turn the player on again after it blanks. It should really be possible to keep the player connected (and wired) when the notebook shuts down and have the player shut down as well (after blanking and then turning itself off).

Could this be reviewed and maybe worked on ?

Thanks so far.

I am trying to build Rockbox for Sony NWZ-380 from Git repo, commit ce0b31d87db3c4c1c1bfb535c50770d33e9c4aaf.
arm-elf-eabi-gcc version 5.4.0, ARM binutils 2.30.
Everything goes smooth until just the latest step where this happens:

… LD duke3d.ovl
LD bmp.ovl
LD jpeg.ovl
LD png.ovl
LD ppm.ovl
LD gif.ovl
LD rockbox.elf
/usr/libexec/gcc/arm-elf-eabi/ld: section .ARM.exidx VMA [00000000600a9548,00000000600a954f] overlaps section .bss VMA [00000000600a7f20,00000000600ff773]

I'm using Rockbox on my NWZ-384 for a couple of years now and there were no problems building it in the past. I also was very glad that NWZ-380 port reached stable status in 3.14,
but now something seems to be broken (not terrible it seems, just requires some adjustments to the linker scripts but still).

For the last couple of weeks, I can’t get Rockbox to run anymore on my phone. I use Rasher’s build, which used to work fine. I even built one on my own, but it still doesn’t work. I tried running it on the emulator and it worked fine. I am not sure what is wrong, reading the logcat gets me nowhere because I don’t really understand most of it. I have attached the logcat here. I do not know if I’m the only one having this problem.

I tried various method to get it working again on my phone, I even tried resetting my phone in case if I messed up somewhere. I also noticed this when I was trying out another ROM for my phone, which runs on Gingerbread 2.3.7. I thought it was the ROM’s problem, so I changed back to the ROM that I frequently use, which used to had no problems at all running Rockbox. The last working build was on 01 March 2014, after that, nothing works anymore on my phone.

The only possibility that I can think of is that my phone is outdated and the kernel or the ROM is missing something crucial to run the latest Rockbox builds. Other than that, I have no idea. I hope the logcat attached could help you identify this problem. Thank you in advance.

Build version: 915bc09-140318
Last working build (on phone): unknown revision, dated 01 March 2014
Phone: Sony Ericsson Xperia X10
Android: 4.1.2 Jelly Bean (CyanogenMod 10)
Emulator: 4.1.2 (API 16) with same screen dimension.

This may represent other players as well.

I installed a new battery on my iriver, a 2100 mAh that is working perfectly. The problem however, is that when fully charged, the voltage holds up to 4.12 volts, and until it drains to somewhere under 3.9 volts, Rockbox thinks that it is powered via USB, so naturally Rockbox gets stuck in USB mode until the battery is drained enough for Rockbox to realize that it IS a battery. With this problem at hand, I have to charge my iriver to only less than seventy percent of its battery life, or else wait for an hour or so to drain it to that point. I HAVE tested it in its original firmware, like I said, works perfectly. The problem lies with Rockbox thinking that the battery is a USB charger. I am asking for a fix around this. Is there a way that I can modify Rockbox so that it may understand that it is running off of a battery that will get up to 4.12 volts and not mistake that for USB power? I just now thought to turn off the “Charge During USB Connection,” maybe that will solve the problem; I will get back when I find out whether or not that works. However, I would still like to request a work around for this problem. Any help is much appreciated. Thanks.

When Playing with rockboy on sansa e200 V1 , Rom that have a size of more than 1m Bug and Rockbox often shutdown. And even if these roms run, the speed isn't playable.

After updating Rockbox from 3.10 to 3.11.2 on my Ipod Nano 1g i noticed the robotfindskitten game did not work as it should anymore. When robot has touched the first object, the text on the top does not change anymore when touching more objects until he finds kitten. The kitten animation also is hidden behind the text of the first object and the scrolling of the text starts at the end, not at the beginning.
I think it worked fine in 3.10, or at least in 3.9.

Please investigate this problem.
Thanks,
Hugo

After upgrading from "Version: 33856d9-161111" to "Version: 6436c6e-170211" Resume Playback from the main menu does not work. Here are the steps taken to verify the problem:

Running Version: 6436c6e-170211… Reset config
Using default settings, enabled Shuffle via Shortcuts
Started playlist; track identified as 1 of 5330
Skipped ahead to the 5th track
Paused @ 1:01
Forced shutdown
Enabled Hold switch
Waited ~1 min., then booted via disengaging Hold switch
Clicked Resume Playback… resumed on the same first track (1 of 5330)
This behavior occurred every time I attempted to Resume Playback.

Restored previous version (Version: 33856d9-161111)
Rebooted
Reset Settings
Using default settings, enabled Shuffle via Shortcuts
Started playlist; track identified as 1 of 5330
Skipped ahead to the 5th track
Paused @ 1:01
Forced shutdown
Enabled Hold switch
Waited ~1 min., then booted via disengaging Hold switch
Clicked Resume Playback… resumed on the fifth track @ 1:01

FWIW: No Bookmarking used (never have). Database not initialized (never use it).

I tested this on a clip+ (3.13) and creative zen (rev cc64d9e), so assuming it’s the same for all devices.

Following setup:
- ReplayGain is configured to “Track if Shuffle” - “Prevent clipping” is set to on/off, does not matter

How to reproduce:
- make a copy of any RG scanned file which has track/album gain and peak tags
- remove the peak tags _only_, leaving gain tags intact

Expected result:
- player should be able to adjust the volume, but not prevent clipping

Actual result:
- player does not apply neither track not album gain.

Files containing only gain tags but not peak tags come from converting lossless → lossy and transferring gain info (since peaks will be different for the lossy file, peak tags are omitted.) With 11db of volume difference on some tracks, it’s impossible to not notice that. I am not sure why applying RG requires peak tags in rockbox, foobar2000 handles peak tag-less files without issue. Any chance to change this behavior to not rely on peak tags?

I use the attached custom WPS that displays the active Replaygain value and type next to the track number.

When playing mpc files created by foobar2000 with the tracknumber/totaltracks tag format, if the track# is 10 or higher and the applied gain negative (as in the attached mpc), mangled characters are displayed between the gain value and type, eg:

10/12 -2.00 dB *gibberish* (Album)

This is reproducible with the latest simulator build d0fffd6-150104 but I only recently noticed the issue and don't know when it began. I have an old sim build 935d8be-121229 and it works correctly there.

Pressing the remote volume UP key on my iriver 140 in wps sometimes results in directory skip.
This is not easy to reproduce, but I was able to repeat once that problem in conditions where I'm sure that the directory skip key wasn't pressed.

I don't know if it's a hardware related problem, but I've read somewhere about another user having the same problem.

I know that the folks that added recording functions to the PP targets only did it as a proof-of-concept, which rteally works well already. I am curious if anyone has looked into the bizarre noise that is generated on the right channel, I have tested this on two different 4g grayscale ipods and on 5.5g ipod. The noise level is lower in the 5.5g than the 4g's. I have attatched a png of jamin running a "silent" recording (no mic connected) and the wavpack file. I amplified the sound to get it to register higher on my spectrum analyzer.

On my Sansa Clip+ 4GB, with Rockbox v3.11.2

Recording a wav file through internal microphone. If the audio signal clips at the positive limit, bad things happen:
1) Most of the time the recorded signal wraps around to a full scale negative value, which makes it sound terrible.
2) Sometimes the recorded signal wraps around to a near zero value, which still makes it sound terrible but the distortion is not so loud

3) Clipping at the negative end of the range is as you would expect - a flat line which sounds like normal digital distortion, as you would expect

See attached picture of the recorded waveform showing each of the 3 situations described above.

I think commit 1654efc31339972d0e6bd41a499fcffc0a45822e introduces the following error:
storage_init in firmware/storage.c does not return an rc error code in case !CONFIG_STORAGE_MULTI
because its discarded here:

#else /* ndef CONFIG_STORAGE_MULTI */
+ STORAGE_FUNCTION(init)();
+#endif /* CONFIG_STORAGE_MULTI */

+ storage_thread_init();

   return 0;

Unsure if this is an RBUtil isssue or a sansapatcher issue, or even a Sansa issue that can’t be solved, but according to this (http://www.rockbox.org/irc/log-20080709#02:36:38), it reports a successful install on the e200R when it hasn’t. Related to  FS#7526 ?

Affected versions:
RBUtil V1.4.0
git version 2a2800b528010320ca504a39106806ec21f0220 (2016-10-12)

rbutil fails to build bootloader. Tested for Iriver H1x0 and H3x0 platforms.

Progress window shows:

Adding bootloader firmware file
Error in patching: reading firmware failed

Terminal output shows:

[httpget.cpp:230 INFO] Get URI “http://download.rockbox.org/bootloader/iriver/bootloader-h300.bin”
[httpget.cpp:200 INFO] Request started
[httpget.cpp:148 INFO] Request finished, status code: 200
[httpget.cpp:151 INFO] Data from cache: true
[bootloaderinstallbase.cpp:71 INFO] Downloading bootloader finished, error: false
/tmp/qt_temp.U16458: Resource temporarily unavailable
[selectiveinstallwidget.cpp:195 INFO] continuing install with stage 1
[selectiveinstallwidget.cpp:197 ERROR] Last part returned error.
[selectiveinstallwidget.cpp:214 INFO] All install stages done.
[rockboxinfo.cpp:27 INFO] Getting version info from rockbox-info.txt

Fired up gdb and debugged the git 2a2800b5280103… build:

The failure is in function mkboot_iriver in mkboot.c line 98:
Line 98:

  i = fread(image+16, 1, len, f);

len is calculated as 2636272.
But file size of /tmp/qt_temp.U16458 is only 2621440, resulting in a short read of 2621424 bytes. So error condition “i < len” fires and function returns without building bootloader.

I tested this on two different gentoo systems. It worked on one, but failed on the other. Both are more or less up to date, but have one significant difference: 32bit vs 64bit system.

The system that did compile and run perfectly uses:
gcc i686-pc-linux-gnu-4.9.4 (len=2636272, file size=2637824)
The system that failed uses:
gcc x86_64-pc-linux-gnu-4.9.3 (len=2636272, file size=2621440)

So, the failing rbutil creates a temporary file that is too short. I didn’t debug deeper to find out why.

cu
John

Sometimes when I shut my unit off and then turn it on again and resume playback, RB resumes from a different place than where it left off, and even though when I resume shuffle is on (as indicated by its icon), it isn’t. It’ll play the current track, then the next track in the playlist (which in my case is in order by track number, so it’ll play the next track on the album), and so on.

If I turn shuffle off and then on again, shuffle works correctly again.

I’m using a build from January 19 (19800-090119) on an Archos Recorder. I
noticed this bug occurring in the 3.1 build as well.

It seems to happen randomly – I can’t figure out anything specifically that I can do to always make it happen.

When I skip backwards 3 songs, Rockbox aborts with the following dump:

Data abort at 60077EB8
FSR 0x1
(domain 0, fault 1)
address 0x00000005

It happens always, playing or in pause. At the 3rd song dumps.

RB version: 04cd1fd-120320

Regards!

Rockbox Info: Version: 3.12

Device: iRiver H140, 80GB Toshiba MK8009GAH 8mm 1.8" IDE HDD 8mm

BUG: Repeatable, Consistent.

Additional Information:
1. To verify that I had a good installation of the 3.12 version of the Rockbox firmware working, I have reformatted, and re-flashed rockbox 3.12 two seperate times after initially encountering this, duplicating this behavior. So it doesn't seem to be a bad firmware flash.

Expected Behavior:

1. Player should Power On and boot properly every single time the bootup sequence is initiated correctly (Play Button pressed when Player is in a Powered Off state).

Buggy Behavior:

1. Player Powers Up, then locks up (i.e. "crashes") during bootloader sequence, requiring a hard reset, and upon second boot, finally Powers On and boots properly, bringing up a functional session of the Main User Interface. This is repeatable, and consistent.

Bug Symptoms & How To Repeat:

1. Consistently the Player will lock up during first "boot" sequence. The bootloader will usually reach the text stage, and sometimes crash here. Sometimes the bootloader will get through the text stage and reach the Rockbox Logo and then crash here. The Main User Interface is never reached upon first "boot" sequence.

2. The result of the first "boot" lockup (i.e. "crash") requires that I reset the Player by inserting a paperclip into the Reset hole (on the bottom plate of the Player) and triggering the button hidden in there. This Powers Down the Player, and Resets the Firmware, leaving the Player ready to be Powered On again.

3. Upon the second "boot", the Player will "boot" and the bootloader will make it past the text stage, the Rockbox Logo stage, and then spin up the HDD properly; the bootloader will not lock up the firmware, and behaves 'normally', finally resulting in a completed boot up sequence with the Main User Interface coming up (as a user would expect). The Player is now ready to use.

Hi,

the random_folder_advance_config plugin fails to build the
folders on N900 / RaaA. I guess it suffers from the same
as the database update did in the past: It probably follows
starts over and over again in the /proc or /sys filesystem.

For a couple of months my Sansa Fuze v2 has been crashing randomly when playing music. Most of the time I just get a white screen with an error message. The last message I got was :

'undefined instruction at 0006DC8C'

(I think that last number varies at each crash)

This didn't happen with v3.13, but it's been happening with every daily build I've tested IIRC.

It doesn't happen very often so it's hard to reproduce. I listen to music in public transports about twice a day and this happens not more than once a week. It seems to happen more often when the battery is low (less than 10%). It generally happens early in a playback session, when the first or second track is played.

Sometimes I don't get a white screen, but the program freezes and some parts of the interface are surrounded with white frames. I don't know if it's the same bug or if it's unrelated.

Note that I'm always listening to music on a microSD card, and I haven't tried on the main memory.

PS: I chose "Sansa Fuze+" in the OS list because I couldn't find Sansa Fuse v2.

Over the past month? the radio menu has been disappearing. When I reinstall the menu comes back and the radio works and the debug screen shows the radio.

When it re-initializes the DB, the radio disappears and the debug screen said that there's is no hardware.

If I manually deleted the DB files, the radio comes back…

A few other people on anythingbutipod forum have mentioned the same issue.

Still an issue August 1, 2007: r14133-070801

  Nowadays there're more and more Android devices hit the market with higher and higher definetion. Therefore, we need to compile Rockbox with higher definetion.
  Though we can compile and run Rockbox fluently, it doesn't always work as we expected. Sometimes it can't load background image/WPS/SBS or it'll even stop singing. I did a lot of test and comparison between builds with different version and  definition and find out that it's the lacking of buffer which disturbs Rockbox working normally.
  Big tracks, images and WPSs/SBSs and maybe other can cause the buffer lacking. We have bigger and bigger RAM for apps now but Rockbox always can't get enough buffer to hold the data. Hope fix!

r31037 and later causes the device and sim to crash when resuming playback after leaving FM Radio. This crash has been reproduced on both e200v1 device and w32 sim and the e200v2 w32 sim. The failure is less likely to happen when there is a small number of files on the device/sim. (I have approximately 2200 files on the device and 5400 on the sim).

Tested with r30145

Steps to reproduce:
1. load the attached fms file (needs 35-Nimbus.fnt)
2. load an fm preset file - be sure to have station art
3. enter fm radio and select a preset station be sure art is displayed
4. power off device or sim
5. power on device or sim
6. start a playlist
7. stop playback
8. power off device or sim
9. power on device or sim
10. enter radio
11. exit radio
12. select resume playback
13. device or sim crashes

The e200v1 crash is:
Data abort
at 000095F0 (0)

Only filetree.c should be allowed to call opendir(), anything that needs to recursively scan directories should be calling ft_load() which can smartly open, scan and close a directory.

The problem with this is that the filename buffer could get corrupted easily if its misused.

as of r18234 the following is using opendir() in the core
filetree.c:133: dir = opendir(c→currdir); ← not recursive
filetree.c:257: dir = opendir(tempdir); ← in ft_load() so ok
filetree.c:259: dir = opendir(c→currdir); ← “” “” “” misc.c:164: dir = opendir(pathlen ? buffer : “/”);
misc.c:1059: dir = opendir(BOOTDIR);
misc.c:1142: DIR* d = opendir(path);
onplay.c:466: dir = opendir(dirname);
onplay.c:817: srcdir = opendir(src);
tagcache.c:4075: dir = opendir(dirname);

the tagcache and the onplay.c ones are dangerous… the 3 in misc.c are not recursive so safe.

the following are uses in plugins, havnt checked them so I only know for sure that stats, disktidy and properties are unsafe
plugins/disktidy.c:203: dir = rb→opendir(name);
plugins/disktidy.c:270: dir = rb→opendir(name);
plugins/md5sum.c:78: dir = rb→opendir( path );
plugins/md5sum.c:113: DIR *dir = rb→opendir( newpath );
plugins/md5sum.c:209: dir = rb→opendir( arg );
plugins/properties.c:79: dir = rb→opendir(tstr);
plugins/properties.c:151: dir = rb→opendir(dps→dirname);
plugins/properties.c:276: dir = rb→opendir(str_dirname);
plugins/random_folder_advance_config.c:70: dir = rb→opendir(fullpath);
plugins/random_folder_advance_config.c:165: dir_check = rb→opendir(formatted_line);
plugins/rockpaint.c:740: d = rb→opendir( bbuf );
plugins/rockpaint.c:754: d = rb→opendir( “/” );
plugins/rockpaint.c:915: d = rb→opendir( FONT_DIR “/” );
plugins/sokoban.c:925: if(!(dir = rb→opendir(dirname)))
plugins/stats.c:139: dir = rb→opendir(fullpath);
plugins/test_codec.c:763: dir = rb→opendir(dirpath);
plugins/test_disk.c:356: dir = rb→opendir(testbasedir);
plugins/test_disk.c:359: rb→splash(HZ, “opendir() failed.”);
plugins/test_disk.c:421: if 1) == NULL)
plugins/wavrecord.c:3774: if 2) == NULL)

so,
The bad calls in the core should be changed to use ft_load, and the plugins should either get a new function in the lib to grab some ram and manage the whole thing, or maybe its safe to just call ft_load there also?

or alternatively, we can go on ignoring the issue.

There are some problems with the quickscreen on the Sansa Fuze. I traced it back to r31246, a text alignment bugfix:

- Quickscreen items flicker a lot and sometimes vanish for half a second on each change of an option.

- Setting the right option (Repeat) to "Shuffle" and then back to something else causes "Shuffle" to stick on screen. Leaving the quickscreen and returning to it reveals the correct setting.

This only happens for longer scrolling strings of text, e.g. "Shuffle" is "Zufallswiedergabe" in German.

Reported Version: 3.15 not 3.14

Hello,

I am using a "SanDisk Sansa Clip+" and it seems that currently it is not possible to remove quickscreen entries when they are set, you can only overwrite them.

In the manual chapter "3.15 Quick Screen" has to be adapted, once this function has been implemented.

It would be very nice to have this possibility!

-Ramon

Pure i20 does not charge the iPod classic with OS rockbox.
I feel like Rockbox can not recognize interface pure i20 (drivers?)
Through Pure i20 will not play music even if it is in the installed Rockbox in the iPod.(only apple Flash = possible charging/playing via Pure i20)

I own Ipod classic 6G 160GB (flashed rockbox)

I was recently renaming some of the music files on my Sansa Clip+ MP3 player using my computer. Some of the renames were as simple as changing the case of some of the letters in the filename, from uppercase to lowercase. After I disconnected my device, I noticed that there were duplicates of certain entries in the database. Upon further investigation, I realized that all of the entries that were duplicated were the files that the names of which I had renamed by changing the case of the letters. After I discovered this, I tried to rename a file in this manner using the device. When I tried to save the file with the new name, the screen showed a box that read “Rename Failed.”
Apparently, at least for Sansa Clip+, RockBox has a problem with renaming files by changing the case of the letters. Let me know if any other RockBox devices have this problem as well.

Since the daily builds in between 3.9.1 and now and also on the release 3.10 i experienced a problem with MPEG player not displaying the the fonts right and the chip8 emulator just freezes after loading a file i tested it with a few game files found on the plugin wiki.

While examining disk performance with  FS#9708 , I found one album where the disk stayed spinning with no activity for 5 s longer when using PIO. This is repeatable with that particular album. With the downloaded r19739-090109 build, this did not happen with the default settings but it started happening as soon as I enabled dircache. Prolonging the disk timeout prolongs the extra sleeping time.

Experimentation with shows that the storage_sleep() part of fill_buffer() (in apps/buffering.c) is executed early in the buffering and it is not executed at the end. With another album where spindown happens properly, ata_sleep() is called twice. Note that ata_sleep() just sets last_disk_activity, and sleep happens over half a second later if there is no disk activity during that period and last_user_activity has timed out.

I think this is a race condition based on how dircache and transfer rates change things. I wonder if it is related to  FS#9541 .

The data mentioned is located at http://spreadsheets.google.com/ccc?key=pkeRcfM0sg949P3a5EYXtew and the delayed spindown is seen in the EP7 PIO test. In that data, also note how sectors written are 5, 10 or 15, with differences between different tests with the same album.

I have a 30GB 5th generation iPod, but I expect this issue affects all SW-codec players.

According to http://download.rockbox.org/manual/rockbox-sansac200/rockbox-buildch5.html#x8-930005.8 the power button is supposed to exit the recording menu, but when I press it nothing happens. I have to power off the device and power it on again to get back to the main menu.

The manual says in page 31 chapter 4.3.3. that you can get to the Playlist Viewer Settings from the Playlist Viewer Menu (which should probably be named Playlist Viewer Context Menu), but there is no such entry on the actual player. Just via the settings menu from the main menu.

Ordinarily, when Rockbox is shut off and turned back on, it will remember the position in the last-played song, and begin playing from where you left off. However, in the latest build, Rockbox doesn't remember the last track that was playing if the file used a relative path. This happens on every version of 3.14 including the current daily build (2017-11-13).

Here is how the error can be reproduced:

Have a folder with two songs. Then, in the parent folder, create two m3u playlists named "absolute.m3u" and "relative.m3u".
.\
—absolute.m3u
—relative.m3u
—MUSIC\
——song1.ogg
——song2.ogg

In the absolute.m3u playlist, add the following lines:
MUSIC\song1.ogg
MUSIC\song2.ogg

In the relative.m3u playlist, add the following lines:
.\MUSIC\song1.ogg
.\MUSIC\song2.ogg

To see expected behavior:

1.) Open the files list, and run absolute.m3u and song1.ogg begins playing.
2.) Push right to start song2.ogg. Let it play a few seconds in.
3.) Turn off your device by pressing power.
4.) Turn on your device with the power button.
5.) song2.ogg continues to play the same song at the same location as when it was shut off.

To reproduce the bug:

1.) Open the files list, and run relative.m3u and song 1 begins playing.
2.) Push right to start song2.ogg. Let it play a few seconds in.
3.) Turn off your device by pressing power.
4.) Turn on your device with the power button.
5.) song1.ogg plays from the very beginning.

The file format of the songs doesn't seem to matter (I've tested ogg and mp3).

I'm running Rockbox 3.11.2 on a Sansa Clip+.
I followed these steps:
- go to the Main Menu
- Files
- long press on <microSD1>
- Playlist Catalogue
- Add to New Playlist
I tried to save the playlist with a long press of the select button (not sure of the button's actual name; it is the button in the middle of the 4-way controller and the one that is usually used to select the highlighted option). I was returned to the Files menu. The playlist did not get saved, and there was no error explaining why.

As a result, I spent a long time assuming that long press of select was a "cancel" action, and tried short and long presses of every other button trying to save the playlist.

Workaround: instead of accepting the suggested filename, remove the "<" and ">" characters from the auto-entered filename ("/Playlists/<microSD1>.m3u8") to be able to save the playlist.

Suggested fixes: The filename suggested by Rockbox should not include "<", ">", or other un-saveable characters. In addition, if the user tries to save a file with invalid characters, a warning or error message should be posted (like the "Cancelled" message that briefly pops up when the power button is pressed to exit from the set-filename screen).

Build 575bd89 2016-12-19

Playing the attached zero-duration WMA '_ length 0.0s WMA.wma' causes crash:

Divide by zero at 6008D274
pc:6008D2&4 sp:600CC7DC
bt end

This WMA file was created by Goldwave and plays without crash in Windows Media Player, GoldWave and MediaMonkey.

Zero-length WAV and MP3 files (examples attached) don't cause a crash.

On the latest development iPod Video and ZEN simulators, MP3 and WAV are reported 'failed' and WMA crashes http://i.imgur.com/k3dKaSN.png http://i.imgur.com/CiYnVuH.png

Daily build: c413591-120705 and earlies.
When I connect powered down my Fuze V1 and disconnect from USB, it hangs displaying USB screen. I must hold power switch for several seconds to power off player. Tested on two different machines with windows7 x64. When I connect powered on player everything works perfectly.