Rockbox

On the Official Test Build for the Sansa Fuze, when playing Doom, in middle of playing, Rockbox gives a Data Abort Error. If it doesn't happen in middle of playing, it is always reproducible by entering the second Map. The most recent error i got is "Data Abort at 307B32D4". My Version is "r21704-090707".

It happened once just browsing through the Menu, but is only reproduced every time by playing Doom, which is why I filed it under Doom.

I will try to try a later revision and see if it fixes the bug.

Using the latest revision (r20001 - but its been broken since I started using Rockbox) the iAudio M3 does not recharge the battery using either the USB or the Power adapter.

The only way I can get the iAudio M3 to charge is to use Cowon’s firmware.

if bookmark=ask is set and the mpeg is stopped, the user is asked for pressing select (for make bookark) or any key (for discard)
on apple devices: if the clickwheel is used for discarding, the bookmark is not set (as intended) but the clickwheel is not working anymore.
to get the clickwheel working again, the keyboard lock has to be set and unset and select has to be pressed.

When the wake-up alarm starts up the iPod, you wouldn’t want it to boot the OF, but it will do so if hold is on. This patch makes the bootloader check if the alarm is active and start rockbox regardless of the hold state if it is. Also, if the hold switch is on during start up rockbox would normally reset all settings, but this is inactivated if rockbox was started by the alarm.

Applying the patch:
Besides building the firmware, you will need to build and upload the bootloader to your ipod using ipodpatcher.

Limitations:
The bootloader doesn’t check if the alarm started ipod, it only checks if the alarm is active. If you have set the alarm you will have to use the MENU button to start the OF.

I don’t know if this works on any other iPods than the iPod video, but it will probably work on all of them.

I've started to write a new game, which is similiar to the popular freeware game Icytower. (http://en.wikipedia.org/wiki/Icy_Tower)
The basic game engine is ready, but there is much work on the adaption to the targets, so that the difficulty is likely.
By now I used just wildcards for the player and the floors, because I'm not talented in drawing something. I hope you can help me with the images.

I'm looking forward for any feedback.

This very small patch simply plays a beep when a charger is removed or plugged in.
I know  FS#7910  voiced this but that was a bit annoying.

The charger stuff will be removed from p7910. I could have added this to it but it isn’t really that related.

This is a variant of an the classic Paratroopers.

It lacks the particles, planes and stacking men. Instead of solders, They're just falling bombs.

For more details about the source of inspiration:
http://en.wikipedia.org/wiki/Paratrooper_(video_game)

It would be nice if the “Generate” menu-option opened a submenu where you could pick which difficulty to generate.

I’ve had a quick glance at the code, and it looks like it’d have to generate until a suitable difficulty is found, but that’s no different from what users have to do now, if they’re after a specific difficulty, except it’d happen automatically.

If I get the time/motivation, I may have another look at it in the next couple of days.

After playing a few opus files (~128 kbps) the system becomes so unresponsive that it cannot decode the file in real time, and the device cannot respond to any input within a reasonable timeframe (have to hard power off).

This does not occur when you set the cpu frequency beyond the highest setting in the debug menu!

To reproduce:
play opus files in a playlist with normal cpu scaling
on beginning of 2nd or 3rd file, system will become unresponsive.

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.

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.

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.

The player (Sansa Clip Zip) appears to refuse or unable to play some of my WMA tracks; as far as I can tell, the problem is specific to my WMA Pro files only as it plays none of them (but works with WMA2 successfully). I have attached one of the examples.

I understand that a similar issue was reported recently (in  FS#12619 ) although, in my case, the player doesn’t start playing and skips to the next immediately, rather than playing part of the track.

EQ settings changed via Touchscreen WPS action setting_inc & setting_dec are not reflected in the sound output of the device even though they display having been changed in the menus. The changes are also not written to the main config file on disk so they do not "stick" after Rockbox has been rebooted.

example syntax to toggle EQ on/off (display DOES get toggled):
%T(148,520,54,46,setting_dec,eq enabled)
%T(148,520,54,46,&setting_inc,eq enabled)
%xl(E,eq.bmp,0,0)
%V(148,520,54,46,-)
%?St(eq enabled)<%xd(E)|>

I'm not sure if this problem is specific to Android or if the problem applies to all targets.
APK Build: Feb 4, 2011

r29445 introduced problems with screendump on sansa e200 and e200v2 (and possibly more). Screendump works properly with r29444.

Steps to reproduce:

1. delete or backup existing .rockbox directory
2. install r29445 (or later)
3. reboot
4. navigate to System → Debug (Keep Out!) → Screendump and press select to enable
5. attach USB cable to trigger screendump

On e200, this results in:
*PANIC*
Stkov usb (0)

on e200v2, this results in a deadlock - no keypad response - backlight & button light never timeout. Upon reboot, multiple dump files exist.

On e200v2 only, when dircache is disabled, screendump will function properly.

This patch makes some changes to codec_api to help remove dependencies for my project.

The unused strcasestr callback is removed.

The global_settings pointer was being used by several codecs to check whether REPEAT_ONE mode is on; this has been replaced with a callback "should_loop()".

The MOD codec has been modified not to restart the file when it reaches the end. This does not affect MOD files that use "position jump" to loop part of the song. Ideally the MOD codec would only follow such loops if should_loop() returns 1, but detecting loops is nontrivial.

The attached proof-of-concept patch highlights (places the cursor at) each album's last-played track in database views. The intention is to allow easy resuming of multi-track audiobooks or podcasts where they were last left off. This works best when autoresume has also been enabled.

The patch relies on runtime statistics gathering being enabled (and the DB needs to be enables as well, of course).

The current patch has some caveats that I plan to address in future revisions:

Right now, it's unconditionally enabled for all database-based track views. We might consider allowing to turn this off for regular music albums.

When the last-played track has been completed (played through to its end), we should actually highlight the next track (or the first track if the last-played track was the final track of the album). [EDIT: fixed – see latest patch in comments section]

It would be great if a similar feature was available for the file browser. I'd find it acceptable if that would require the DB as well (as that's the place where the last-played info is stored). It could benefit from an add-to-DB-as-files-are-played feature (aka FS#12073).

Comments?

[EDIT: Clarified summary. Fixed a rather severe bug in the patch to make it actually work. :) ]
[ EDIT 2: Linked to FS#12073. Addressed one caveat. ]

The attached patch slightly modifies the keymap of the H300 non-LCD remote to allow access to the browser from the WPS (by use of LONG PLAY).

I know that it works ok from an H300 with a non-LCD remote, but I don’t know if I’ve broken the LCD remotes completely.

Please could users of both the H100 and H300 LCD remotes try this patch and tell me that the WPS context keymap is unaffected. For reference, you can see the intended mapping here: http://www.rockbox.org/twiki/bin/view/Main/KeymapIriverHSeries

I am running 3.4 on a 5.5G iPod modified with a 240gb drive. Rockbox is stock 3.4 with LBA48 added in and the max sector size turned off. The database was working ok on 3.3. Only issue was it took forever to add new files. After upgrading to 3.4 I noticed every time I powered on rockbox would lock up in the menus for up to 10 minutes before functioning normally. So I completely removed the .rockbox dir (including the database files of course) and re-expanded a fresh copy. I then tried to init the db. It runs until it is around ~44k files and 99% and then just sits there. If left alone it will eventually just turn it self off. When I turn it back on it will ask me to init the db again. I have seen it try to commit once or twice but it never takes. I am not really sure how to debug this at this point. Also in the debug disk info area, it things my drive is 131071MB. Under Rockbox Info it says 223GB which is better, but these two things are the same as in 3.3. All my Oggs are converted via a script I wrote from my flacs. I do not believe my flacs have any art, I am not even sure you can store art in a flac tag and even them I don’t think the ogg encoder is transferring them. I ran a tag dump (ogginfo) against my oggs and do not see anything to do with album art. I had 4 files on the device with album art. They were all in a directory with a database.ignore file. So they should not have been noticed. Just in case I removed that directory and rebuilt. It went though 44k files, commited 1-9 and then went back to “scanning” but the disk activity had stopped. Upon reboot it asked me to init the db again.

This is not a patched build. I simply changed the config to include large drive support. This is an issue that needs to be looked at. Please check into it, I will be happy to test any ideas.

I didn't like that the "Backlight on first keypress" function ignores the first keypress no matter which key was pressed. For example, I want the volume keys to work normally even when the backlight is off (that is, they should turn on the backlight *and* change the volume).

This patch restricts "Backlight on first keypress" to certain buttons only. in other words, these buttons work normally only when the backlight is on; otherwise, they just turn on the backlight. As a proof of concept, it changes the Clip and Clip+ behavior to filter out only the Home key when the backlight is off, allowing the other keys to function normally.

It works by allowing button-target.h to define the buttons that are filtered by the "Backlight on first keypress" function. If left undefined, the function filters all buttons when the backlight is off, as in the status quo.

[EDIT: Clarified that there is no overlap with  FS#9305  - Context sensitive backlight on key press]

Hi there,

i am currently trying to learn the morse code. I thougt it would be fun to have rockbox as an aid, so i started to write a plugin for that.

This plugin currently has a limited functionality, but the current things are implemented:

1. Morsing of custom texts, typed from the rockbox keyboard
2. Morsing of random chars, till the battery drains (or less ;))
3. Input of own Call and 'morsing' the same
4. selection of speeds from 1-45 WPM in steps of 3
5. selection of chars from 5 mixable groups
   1. letters
   2. numbers
   3. punctuation marks
   4. special chars (KA,BT,AR,VE)
   5. pauses

It would be very nice if someone tested these on some soft-codec targets. I included the source tarball (please add plugin to SOURCES and CATEGORIES if using this), a diff on r17715 and the binary .rock for the sansa c250.

Idd be very happy if, with a little help, this could move upstream. I am new to the plugin api and need some help especially in using the definitions to make this work on different DAPs (avoid building this on targets that don't support some features and so on). Correct me if i am wrong, but his should from my point of view work with all SWCODEC devices with LCD. I tried to write at least readable code and added some comments for the curious.

This builds at least on the c250 and works for me.

Thanks, Joel

Remind me, if i forgot something.

Tracks played via a cuesheet are not recorded in .scrobbler Last.fm log.

This patch adds a sector-based read/write cache between the storage and fat drivers.
It has a static pool of 64 sector buffers which can be locked by the file handling code to replace the sector buffers in the file and dir structs, and serve as cache as long as they aren’t used. It can also be used to enforce exclusive access to a sector.

If requested using the STORAGE_NEEDS_ALIGN define, all storage accesses will be aligned to cacheline boundaries.

This patch adds a changable wheel scroll speed option on ipod video.

I think this is good since now the plugins in the list appear in the order of their occurrence in viewers.config which is rather random.

The Rockbox firmware and cross compilers build by using MinGW.

It is necessary to use MSYS’s make (MinGW’s make (mingw32-make) does not used.).

The cross_compilers.zip is a patch file necessary to make cross compilers using by rockboxdev.sh.

I confirmed the Rockbox firmware, codecs and plugins was built by using the compiler on MinGW.
But I can not confirm whether the Rockbox executes excluding iPod video.

Could you confirm operation to various players?

I’d like to suggest the following new WPS feature(s):

1. A viewport can be assigned an image as a “backdrop”.

 a. A viewport may be assigned an image dynamically via the WPS tag "%VX<identifier>"
   (i.e. %VXa for image a, %VXZ for image Z, etc.)
  b. As a viewport is being processed and drawn, its backdrop would be drawn "first", followed by any other normal images/characters.

2. Viewport may define FF00FF as a background color, which would then be “transparent”. This would allow overlapping viewports.

3. Fonts drawn in a viewport with a backdrop would automatically be drawn with DRMODE_FG.

Notes on the attached patch file:
+ It was created from the SVN revision 18997 on Nov 3, 2008.
+ Although I stubbed in the new functions for all the LCD drivers, I’ve only flushed out the 16 bit driver so far.

Cheers!

This plugin searches in the .rockbox/rocks/apps/drumkit directory for .raw sound files, loads them into memory, and assigns the keys to play them, creating a drumkit /sample trigger / instrument out of the player. Currently only designed for the Sansa e200.

Room for improvement:

- Add keymaps for all
Allow multiple samples to be played at the same time (by using
Allow for a variety of sound file types to be
Find a better name

This is a new plugin that mimics the open source PC program mnemosyne (http://www.mnemosyne-proj.org/), a program that assists with memorizing flash cards. The plugin is fully functional, but it still needs a menu and assumes that the user has setup the folders it needs for storing cards before running (if you don’t create them it will crash). I’ll fix these issues in the near future, but in the mean time any feedback is appreciated :)

This patch attempts to permanently fix the inconsistent mixture of “Title Case” and “Sentence case” in english.lang by applying “Sentence case” to the entire file.

I suggested we do this in a post to the rockbox-dev mailing list last year, but that just ended in a very split discussion with no conclusion.

I’m not sure if this patch wil result in anything different, but I made it for my own use, and thought I would post it, as there were a fair number of posters to that discussion that also prefered sentence case.

The old discussion:

http://www.rockbox.org/mail/archive/rockbox-dev-archive-2008-08/0034.shtml

EDIT: I forgot to say this patch also changes a couple of uses of “center” to “centre”…

Hello,

This plugin is a game to be played in two.
I like to play go and pente and so is my wife (at least she plays pente) so I wrote this plugin.

I think the code is clear enough. I also used all the #ifdef that I knew.. so, I believe it wouldn’t break any compilation.

The plugin was tested on IPOD 5G (VIDEO) and works just fine. I also compiled it to a few more players without any problem.
I did not try to compile it for players that don’t have the lcd_update() function. It won’t work (at least this first version).

The board size in the LCD is based on WIDTH, since Sansa has width smaller than height you will lose part of the board (horizontally).
I just tested the code in sansa using the Simulator…

It is easy to fix and I will, but I’ll be traveling for a week (that’s why I wrote it, so I could play it while I wait in the airport/plane…) When I came back I will fix it.

Meanwhile, you guys can patch it or use it.
Feedbacks are also welcome.

Current Features:
- Save / Load games
- Pente / Go (Board 9×9, 13×13 and 19×19)
- Remove groups / stones automatically when they are dead

I attached the code and the “executable” for IPOD 5G (Video)

Enjoy!
Alex

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.

It would be useful to change the configure and voice.pl files in order to allow the user to choose also the Loquendo and ViaVoice TTS

- What behaviour you are seeing

Rockbox 17612-080523 on an iRiver H340 skips entire tracks, and also skips within tracks, when the battery level falls below 30%

- What behaviour you expected

No skipping.

- How to reproduce the bug

Allow the battery level to fall below 30% and start playing a directory of files. Some files will be skipped, some files will have parts skipped in the middle.

- The SVN revision you are using and if possible the particular SVN revision in which you think the bug was introduced.

17612-080523, no idea when the bug started.

If you need any further info on this bug, please ask and I’ll give more details. I have no other hardware to test whether this behaviour occurs on other Rockbox platforms.

Hi there,

first of all: this is my first contribution to rockbox and I tried my best to make myself familiar with the way things work there. I am sure, not everything is where it belongs. Please help me to get things in order :).

second: thanks to the author of Patch  FS#1803  that made this possible.

The purpose of this patch is to watch the tuner reported field strength (estimate) and mute, when it drops below a customizable threshold. Wether muting or not as well as the threshold are customizable in the fm tuner menu. It should not interfere with manual muting and should not affect recording (i didn’t test that yet). THe threshold is specified in pseudo-dBuV.
It also adjusts frequency display to display as MMM.KKK instead of MMM.KK. This is for people who adjust region settings and channel widths.

My testing conditions were limited to the sansa c250.  FS#1803  reports to work on the tuner chips LV24020LP (e.g. sansa c250) and TEA5767. I only tested the first. Please report back possible field strength values you see on devices using these chips.

This code should not break anything. I did a testbuild for some iPods (without tuner) that compiled cleanly. Simulator also works.

Currently only english and german translation are done.

User guide:
This patch conditionally adds 1 or 2 lines to the tuner main window that look like this:

Sig: [-M] -235dBuV
Automute below -555dBuV

The second line is only displayed if automute is enabled. The first line shows the status of the tuner. The 2 characters in the braces exlain as [ab]:

a: either 'O' or '-' 
   'O': current field strength is above threshold
   '-': current field strength is equal to or below threshold
b: either 'M' or '-'
   'M': will mute on or below threshold
   '-': automute disabled.
(both are only updated on field strength change)

The second line should be selfexplaining, same for the menu entries.

Request for comments!

Where possible (i.e. the buttons aren’t needed for somethinig else), the PLAY button should go straight to the WPS (resuming as required) or radio.

These are almost the case, but on the H300 there are the following exceptions:

- Rockbox Info (PLAY performs the disk free space scan, same as SELECT)
- Playlist Viewer when selected from the Main > Playlists menu (PLAY returns to the menu above, same as LEFT)
- Sleep Timer (PLAY does nothing)
- Debug Manu (PLAY enters the selected item, same as SELECT)
- Browse x in Settings, where x = Themes, Fonts or .cfg/.wps/.rwps Files (PLAY returns to the menu above, same as LEFT). (Note that the plugin browser works fine!)

Similarly, the STOP button should stop playback, which is largely ok, except:

- In the Playlist Viewer (STOP does nothing)

I don’t have any other targets handy, but feel free to add any other suspect screens here.

I noticed various RDS-related issues on my Clip Zip and Samsung R0

1) Sansa Clip Zip
With the latest builds (for example version 341e2c4-120929) I noticed the RDS text just behaves crazy, like blinking for no reason and displaying strange characters. Besides, the RDS name won't display most of time or at least needs much time to display.
When reverting back to an older build (0c4bd3a-120406 for example), the RDS name displays quickly and for all stations now and the RDS text is just displaying and scrolling normally.
Tested and noticed with my theme lebellium Samsung -like: http://themes.rockbox.org/index.php?themeid=1681 and with the various DFKT Minimum Zip themes (this one for example: http://themes.rockbox.org/index.php?themeid=1539 )
screenshots of the issue: http://imageshack.us/a/img855/8724/dump120926124155.png http://imageshack.us/a/img837/2154/dump120926124439.png

2) Samsung YP-R0
In addition to the RDS issues reported for the Zip above that also exist on the R0, it seems that the RDS text makes the device crash after a few seconds or minutes with my theme lebellium Samsung-like (version 1.60 beta to download in attachment).
I found 2 unsatisfying ways to bypass this annoying crash:
-Remove the %s scrolling tag for the RDS text, that is to say replace "%s%ac%tz" by "%ac%tz". But that's not a good solution since then the RDS text is cut off. The %tz tag only makes sense when associated with a %s tag and all other themes supporting RDS use it and work well that way.
-Replace the RDS text font (currently 20-DroidSans-Bold.fnt) by another font from the Rockbox Font Pack. As I want a nice anti-aliased font, the only acceptable alternative I found is the Ubuntu Bold font. But this font makes the device crash too…

So I just hope there is a bug somewhere that can be fixed?

I’ve been using the latest dev builds everyday for iPod Nano 2G and still encountering “Swapped Channels” on Playback (e.g. Left Channel → Right Headphone / Right Channel → Left Headphone).

Used latest build 5785cfb-120625

Sans Clip V2

24bit 96000 Hz 6 Channel (5.1) FLAC files skip to next song after 30 seconds. 30 seconds is an estimate because my screen is broken, so I can’t see what’s happening. I downloaded a daily build 3 days ago, but I think it’s a buffering issue. Flac is 8181 kbps (says Foobar).

It’s the first time I tried these files, so I don’t know if they ever worked, or ever will.
If they never will work, I’m sorry for reporting this.

Thank you all for your time and efforts.

So far there's still two problem which have never been fixed on Android:
1.When opening Rockbox, its volume bump to max automatically whatever it was when last quit;
2.On most HTC(and probably other) devices one can't use physical volume keys to adjust. Volume bars in WPS and SBS work well however.

Hopes the fixes!

I have RockBox version 3.9 on my Sansa Fuze v2 and so far I love it, but I have one problem. On a few tracks in my library, when I play them, the first few minutes of the song will be strangely distorted. Most of them are songs where the music starts off in just one of the speakers before moving into the other one. There will be bursts of loud, crackly noise in the other speaker during these first few seconds (that seem to be in time with the music) and then it will fix itself and the rest of the song will play perfectly. When I boot the default Sandisk firmware the songs play perfect like they should, it is only in RockBox that this glitch happens. I’ve messed with the settings a bit and even reset them completely, but nothing has worked thus far.

Attached is one of the songs that this happens with, from about 2 seconds in to about 7 seconds in. Any help would be greatly appreciated. I really want to enjoy my music without that crap in it.

Every time I try to set my theme to ThinBasic in Rockbox 3.11.2 on my nano 1g, a panic occurs.
I only tried this in 3.11.2 so I'm not sure if older versions have this problem too.

Hi, firstly i put Sansa c200 because SansaClip+ is not available in the list.
My player is a Sandisk SansaClip+ bought 6 months ago with an 8Gb class 4 Sandisk microsd (that is currently empty, no songs stored).

Steps to reproduce the issue (after a fresh installation of the Firmware, no settings changed):

1) Switch on
2) → database
3) → track
4) select any track
5) press the central button
6) Erase Dynamic Playlist? is displayed.. Select Yes
7) countdown then starts to play
8) Seek to the next song (it happens at the first seek or might need three, four one after the other)

Data abort
at 30813E44
FSR 0x8
(domani 0, fault 8)
address 0x62E90028

- I installed version 3.10 on top of version 3.09, but later on I tried to uninstall completely 3.10 and reinstall it from scratch and the issue is the same.

- After the crash i have to keep the "switchoff" button pressed for a while.. then I press it again to restart the player and I try to resume the song I get "playlist control file is invalid" or "nothing to resume"

- behavior is the same with or without the SD card

- The issue was randomly happening (but very very rarely) also on the previous version of the firmware (3.09) I got the error a couple of times in 6 months.

If loading a config file that holds all configuration settings (Settings → Manage Settings - Save .cfg File) from Rockbox 3.9.1 in Rockbox 3.10 or the daily builds for Archos Recorder with Firmware V3, the player will not bootup correctly on the next restart and show:

I 4: IllInstr

directly at booting. I then press "On" again and get:

*PANIC*
Stkov main

and the HD shuts down. If I press "On" again, the same loop continues.

The problem can only be resolved by plugging the player to USB, removing the rockbox directory and copying it again from the newest daily build or 3.10, then restart. It boots up fine again then. Doing the previous settings manually on 3.10 or the daily builds and then saving / loading them works fine and the player won´t have the boot-bug anymore.

I have attached the config file that creates the problem.

The location for recordings can be set, but the only way to see the current value for the setting is to look into the config file. The patch adds a note stating that to the manual.

Also, there is a known bug ( FS#12517 ,  FS#12500 ) preventing saving the recorded files in the root directory (maybe this applies only to some targets, not all). The patch adds a warning about that.

If Rockbox is connected via USB with no sd card inserted and it is inserted, it offers the OS to mount the new drive.
If the sd card is removed and reinsterted again, it fails to offer and recognize it.

I could locate the problem in firmware/usbstack/usb_storage.c in the line

if(inserted && check_disk_present(IF_MD(volume))) {

after reinserting the card, check_disk_present fails to return true, so this check fails and the card isn't recognized anymore.

sometimes when i click on next(or previous) button a couple of times , rockbox gets stuck and then anfter 3 or 4 secs ,it restarts .then when loaded the battery is empty.
i am not sure if this is a rockbox related issue or hardware realated cause i use my ipod for file transfer mainly .and this issue existed from version 3.3 till now( i cont know or remember about before that).

is there a way that i can somehow debug (trace) this issue?

This patch adds a secondary backlight timeout (similar to what the the iPod OF does).

It adds two extra settings: secondary backlight timeout and secondary brightness (I'm not sure wrt the naming of those, any suggestions?)

The code isn't very clean, but it works (except for CONFIG_BACKLIGHT_FADING == BACKLIGHT_FADING_PWM targets, for which I haven't implemented this).

Please test this.

to reproduce:

1. set playback settings–>fade on stop/pause to on.
2. play some music.
3. press the pause button to stop the music, and again to restart it. repeat that a few times, because this bug does not always occur.

you will notice that both “time-displays” sometimes change very to the previous second and then back to the normal one, e.g 3:32, then very short 3:31, and back to 3:32. the progressbar sometimes get smaller for a fraction of a second, too.

maybe i’ll search for the revision which introduced this in the next few days

The patch allows to use the persistent dircache even in targets that do not define HAVE_EEPROM_SETTINGS.

Starting trying to implement such a feature for my iPod Video, I "discovered" the functions dircache_load/save (I have a slight knowledge of the RB software). Investigating why it was not used on my target, I saw that it's conditioned to the define HAVE_EEPROM_SETTINGS without an apparently reason to limit them just to some targets.
So, I simply "detach" the functions definition and use from the define.
I'm using it since an hour, starting up and shutting down the DAP various times, jumping back and forth inside the dynamic play list, and I got no problems at all.

If I guess correctly the code, the dircache should be updated also when changing the DAP content, if the USB connection is done by RB and not the OF.

It's applied to r29907.