Rockbox

Playing 320K MP3s pauses often in Version 3.15 and daily build 7d00533 also UI becomes unresponsive
Version 3.14 or older does not reproduce the issue in either 44 or 48khz sampling rate and same sound options
Is not reproducible under OF or Version 3.15 running on IPOD 6G
seems to be a cpu usage issue as compiling a version of rockbox with much higher than stock CPU clocks seems to alleviate the issue to an extent but there is still occasional pauses that is not present after reverting to 3.14 and stock 80 mhz clock speed.

On my X3, it triggers the MIPS equivalent of a segfault. (directory has 792 entries, tried to access it with only 500 allowed)

Rather than crashing outright, I think it would be better to detect this and somehow error out gracefully?

Whenever the HOLD switch is turned off, the hold icon in rockbox disappears, but hold actually doesn’t let go. I can’t use any keys until scroling is used. Scrolling left or right is the only thing that actually switches off hold. It can be pretty annoying as I use HOLD a lot.

When using the H300 non-lcd remote to turn on the player (iriver H340) I get the following error message “hold switch on, power off…” (the hold switch is not on).

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.

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.

This was reported in the past as part of another bug (FS #6707), and although the other one hasn’t happened anymore, this one still does.

Happens only from time to time. Scenario:

- player is playing song (in WPS), backlight off
- press stop
- only backlight goes on, playback continues

I attach this to H300 series but this may not be player specific

I'm using the newest build of Rockbox (2007-07-21) with an iAudio X5 20 GB and I have my tuner set to the European region. I encounter two little flaws in the FM-radio. I think they partially have to do with the player's hardware, but maybe Rockbox can improve the quality a bit.

1. The player is really sensitive to movement. The signal strength differs with every meter that you take the player with you. On top of that, most stations sound like they're not correctly tuned, but I can't get them any better. Maybe Rockbox could be more accurate in frequency selection? (Like 101.100, 101.125, 101.150.) I can get these stations quite well on my home radio. I don't expect the same quality from such a small device, but some finetuning would be great. The only problem is that it would take a while to scroll through the frequencies, but once set it'd be fine.
2. (I assume this is very hardware related.) The radio signal may change between stereo and mono. I have it set to stereo, but sometimes it just picks mono. I guess this is because of the hardware, since it is place related. I also didn't find any potential bugs in the source code.

What are your thoughts on this?

Oh, and keep up this good work! I really enjoy Rockbox!

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

Holding the Pause button (to move/paint down) will shut down rockbox.

This shutdown combination should be disabled for Rockpaint!

While I’m at it (and you can put this in a different Flyspray if you want), I suggest that we make use of the iPod scrollwheel somehow in Rockpaint, maybe to change the size or shape of the brush or something and/or in the menus.

I would also like to be able to set the colour of the background to start with.

When the dc jack is plugged in to charge while the player is not running (switched off), the display says ‘ATA Error -11’. It can’t be reset except by removing the batteries and dc jack. I ran an older build from last year and it works fine.

Recipe:
1) Play an album. Wait until buffering completes.
2) Skip from track 1 to track 2. No buffering occurs.
3) Skip from track 2 to track 1. No buffering occurs.
4) In the playlist viewer, select track 2. Rebuffering occurs, even though the track is buffered.

The same problem occurs in the opposite direction (e.g. after step 2, it should be possible to switch to track 1 using the playlist viewer without rebuffering).

The Idle Poweroff only reboots my 1G iPod. I assume it should power it off or put it into a power saving mode. This forces it to use up the battery faster then normal unless I set the Hold button to boot into the iPod firmware to do a proper suspend when Rockbox reboots.

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.

Rockbox hangs if the disk gets full during database creation.

When recording, as file size reaches 25.2MB and again at 52.4MB respectively, disk thrashing noise drowns out the recording for about 2 minutes.
This occurs at about 27.5 minutes if recording as mp3.
And about 5.25 minutes if recording as wav.

I am assuming that Rockbox is filling a cache and then dumping the file to disk all at once.

I would expect it to write quietly. Even if it where to write on the fly, the noise would be reduced to short bursts. 2 minutes of interruption is just not acceptable. I missed out on important information during those 2 minute periods.

How can we eliminate write noise altogether? Or at least in the recording itself.

Select ‘FM Radio’ Choose your station.
Then from the menu select ‘Recording’ Press ‘play’ or ‘Rec’ to begin recording.
Wait for file size to reach about 28MB. Then stop.

I can also provide recordings if necessary.

*note: I also had the USB cord attached to give better FM reception.
tested on e260 & e280
Rockbox Version: r15988-080102

Thanks

On the Sansa C240 V1, to switch on the line level audio output on the dock connector pin 8 needs to go high. So jumping 3V+ from pin 22 will activate the line level audio. This works fine with the Sansa firmware but Rockbox produces no sound through the line level outputs on the C240, with pin 8 jumped or not jumped.

How to reproduce this:-

Use the remote to turn on the player while the hold switch is set to lock on the player. Backlight on both the player and the remote stay on constantly (timeout is set to 5s presently).

If you set the hold switch to unlock the backlight goes off after the timeout has expired and thereafter will turn off however the hold switch is set.

Rockbox Version:r16780-080324

Description:
If the “Bookmark on Stop” option is set to “Yes” and there is no free space left on the storage, rockbox freezes/takes a REALLY long time if pressing the Poweoff(=Stop) button, because it cannot save the bookmark(or has to push out the less recent?).

I wondered why rockbox crashed if doing this til I discovered this bug.

Expected behavoiur: Instantls notify user there’s no space left and don’t save the bookmark

How to reproduce:
1. Power on the player, launch rockbox. Make sure there’s enough disk space.
2. Go Settings→General Settings→Bookmarking→Bookmark on Stop→Set to “Yes” 3. Reboot, connect to PC
4. Create a text file which is big enough to consume the rest of your free disk space
5. Restart Sansa into rockbox
6. Play a track
7. Press poweroff (short)

When utilizing the database on the iPod Photo (as well as other 4G iPods I have used), on occasion when entering a directory or going to the parent directory, any button on the iPod will need to be pressed before the others will have effect. I.E. before I can scroll to select a song, I must press Select or one of the other wheel buttons. It is severely annoying, in part because it is too sporadic to even be assumed to be a “feature”.

The (software-)equalizer is adding high noises to the playback.

I made a recording, the first part with eq enabled the second one with disabled equalizer.

I could also make a test on my older H110, on which I never used the sw-eq though.

Hi,

There is a compilation problem when the environment variable BLOCK_SIZE is set. It gave me errors about a comma.

This can be set or cleared systematically or on a command by command basis.

Suggestion one; unset BLOCK_SIZE and its relatives high in the build chain, but be prepared for POSIX to bite with 512 byte blocks.

Suggestion two; set LS_BLOCK_SIZE=1 high in the build chain. (And DF_BLOCK_SIZE=1024 and DU_BLOCK_SIZE=1024 ?)

Suggestion three; edit apps/lang/Makefile so that

$(SILENT)echo “#define MAX_LANGUAGE_SIZE `ls -ln $(OBJDIR)/* | awk ‘{print $$5}’ | sort -n | tail -1`” > $(HEADER)

becomes

$(SILENT)echo “#define MAX_LANGUAGE_SIZE `ls -ln –block-size=1 $(OBJDIR)/* | awk ‘{print $$5}’ | sort -n | tail -1`” > $(HEADER)

or

$(SILENT)echo “#define MAX_LANGUAGE_SIZE `LS_BLOCK_SIZE=1 ls -ln $(OBJDIR)/* | awk ‘{print $$5}’ | sort -n | tail -1`” > $(HEADER)

Suggestion four; just tell people that they are not allowed to have commas in their core utilities output (and be prepared to be bitten badly if the default block size ever changes).

BTW I *like* having thousands separators on my command line, so I have

export BLOCK_SIZE=\'1
export DF_BLOCK_SIZE=\'M

in my /etc/bashrc file.

RB does not play AC3 tracks which were extracted from DVD with splitting one-track/one-song (splitting by chapters).

In other words - if you extract single AC3 song RB will not be able to play it back, despite the fact foobar2000 and Winamp with AC3Filter plugin will play it fine.

It is not a problem related to extracting software as the problem occurs for AC3 files saved by DVD Audio Extractor and SmartRipper. (Files saved by them are bit-bit the same as file comparison showed).

Simulator does not display any debugging info when you try to play AC3 file which RB is unable to play.

AC3 playback is not completely broken because RB plays AC3 files if you extracted full AC3 track without splitting it.

- 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.

The database hangs when doing initialization if there is no music file on the player.

How to reproduce:
1. Install Rockbox.
2. Put some music files onto the device.
3. Initialize database.
4. Reboot.
5. Remove all music files from the player.
6. Initialize database.

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 ?

When you play back a broken flac file (in this case a file that was truncated) it can happen that he decoder outputs constant loud noise instead of just skipping to the next track.

I’m not sure if this is really a bug since you are not supposed to play back broken files.

Attached is a file where this happens.

H300 r18009 (happens in the uisim too).

I have only tested this on my H120 with an 18007 build. I have been using the APE codec for some time now and never had a problem in the past.

After reformatting my hard drive and installing the current build I found that rockbox has 2 problems with my APE files

1. The parser for APE files no longer recognizes my APE files encoded with version 8,9 of Jriver Media Center. Result is that files don't play when selected in the file browser and these files do net get added to the database.

2. When switching APE tracks one of two possible behavior occur. a) the Iriver freezes completely. b) On switching tracks there is a loud hiss and then playback of the next track resumes.

Cheers

  Thomas

Hello World :)
Attached is a VBR WMA music file, which fails to play correctly on my “RockPod” iPod Nano.
The same file decodes perfectly using the latest ffmpeg build.
Therefore I can only assume there is something about this file which triggers a bug in the Rockbox-specific WMA decoder.
Also attached is a microphone recording of the sound which comes out of my iPod when Rockbox attempts to play the faulty WMA.

I have over 3000 WMA tracks, all encoded using an identical method, all of which will not play correctly in rock box, so if you would like any more examples, or information, please ask.

Thanks for all your help :)
(If there is any way I can help debug/update the code for the wma decoder, please let me know where to start, I understand the C source code pretty well)

~Andrew

The Sazanami-Mincho-Regular-*.fnt includes 7128 characters.
However, there are about 7500 character not included in the Sazanami-Mincho-Regular-*.fnt though it is included in the sazanami-mincho.ttf font (This font is a font that became an origin when the Sazanami-Mincho-Regular-*.bdf font is made).

Please look at “List.txt” file about the character not included in the Sazanami-Mincho-Regular-*.fnt.

The cause of this problem is in “fontForge”(http://fontforge.sourceforge.net)
used when the bdf file is made from the ttf file.

When the bdf file was made by using　”Otf2bdf”(http://www.math.nmsu.edu/~mleisher/Software/otf2bdf/) instead of “fontForge”, all characters included in the ttf file were able to be taken out.

However, when you make the Sazanami-Mincho-Regular-*.fnt by using Sazanami-mincho-Regular-*.bdf that applies the patch,
The interval between the line and the line opens from present Sazanami-Mincho-Regular-*.fnt a little.

Please report by using new Sazanami-Mincho-Regular-*.fnt(in new-Sazanami-Mincho-Regular-fonts.zip).

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.

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.

I have experienced a fade in reception with my sansa e260. If I tune to a station, the longer I listen, the more static becomes present until the station is all static. I have found however that if I navigate to another station and go back. The station is clear again. This does not happen on the original firmware and does not seem to be location specific.

So the firmware seems to be seeing a degrading signal, but the signal is not actually degrading. Or perhaps the frequency to which the FM tuner is tuned, begins to deviate until it reaches a point of all static, even though the tuner still displays the original frequency.

Thanks.

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

I have just now installed the latest stable version of rockbox (that would be 3.0) on an iriver h340. Unfortunately, it’s unusable at the moment due to some serious screen corruption. It sort of looks like this picture: http://img54.imageshack.us/img54/2263/iriver3qs.jpg, but is so much worse that it’s impossible to navigate the menus. If I wait for the backlight to go off, and then press a button, the screen looks fine until I start navigating, at which point the corruption resurfaces.

I’m really excited about rockbox, but this bug is a showstopper for me at the moment.

Thanks for looking into it!

Regards.

also category:
Some containers, like Matroska MKA or like Ogg can contain numerous audio tracks, for example the whole AudioCD contained within single Ogg file.

For example VideoLAN.org plays such files ok, while fails to show separate tracks/tags in playlist.

However, RockBox justs freezes and until reboot can no longer play music (each file is detected as having zero duration)

example can be found: [link deleted - it was a full copyrighted album]

Setting the Idle Poweroff setting seems to work just fine initially because the player ceases to respond to any input. However, when you push the power button back up to turn it on, the screen lights up and says “Shutting down…” for a few seconds before actually powering off. You then have to push the power button back on to turn it on proper.

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.

Tested with r19410

If I boot with the headphones plugged in, sound always works (at least I didn’t have it fail yet). If I boot without headhones plugged in, and plug them in later, sound often doesn’t work. This may also depend on whether the player was turned off for a long time, whether the previous boot was USB mode, and whether the headphones were unplugged before or after shutting down.

This is a recurring problem with this target it seems. With 3.1 installed and resume playback on start up enabled, playback hangs and skips badly while the hard drive is being scanned during start up.

The same behavior occurs when resume on start up is disabled, but playback is resumed by the user during the hard drive scan.

After upgrading from 3.0 to 3.1, the “Beep” sound (enabled in Settings / Playback Settings / Beep Volume) now sounds very distorted and fuzzy.

It sounds this way on any setting. Strong, Moderate or Weak and with the player’s volume on any setting. It definitely sounded like a normal clean beep with 3.0

This is on an 80gb Ipod 5.5 with Rockbox r19569-081223

I’m not sure if this should be under “Music Playback”, as I don’t seem to hear the distortion and fuzziness when playing mp3’s.

Mike

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.

I used the official toshiba updater to get an “original” fresh install on my beast and then attempted to run through the install procedure for a single boot rockbox install. After a (seemingly) sucessful install I’d end up in recover mode after any reboot.

Fatal error when attempting to install nk.bin (rockbox only bootloader) using sendfirm in Windows to an updated (v1.2) Gigabeat S player.

After install of both bootloader and rockbox the Gigabeat S, once rebooted, goes into recovery mode (toshiba) and requires an update/restore. This is the Number 3 Triangle.

Notes:
Gigabeat was first updated using the official toshiba MESV12US updater. “gbs_update_1_2_us.exe”

Using SVN revision 19741 to compile nk.bin under WinXP and Cygwin.
Using MTP.zip of 7/4/2008 found on the wiki to send over the bootloader.

I suspect most devs updated their bootloaders using the sendfirm utility *before/without* updating the entire player with the updater utility from toshiba. Thus they started from a v1.1 OF and never updated any part of that.

Maybe the updater changes something in the bootcode. I don’t know.

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.

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.

“First Keypress Enables Backlight Only” doesn’t work on the 5G iPod. For example, if that’s enabled, the backlight is off and I press next track while at the WPS, Rockbox will go to the next track.

It seems like clickwheel event(s) generated when I touch the wheel turn on the backlight. When the button is pressed, the backlight is already considered to be on and the button press performs its usual action. If I carefully hold my finger still on the clickwheel, let the backlight fade, and then carefully press a button without moving my finger on the clickwheel, I am able to turn on the backlight without causing anything else to happen.

I don’t know what to do about this. Requiring a physical button press might be annoying. Removing this option on affected targets might be okay, because it’s easy to turn on the backlight by touching the clickwheel (and that doesn’t seem to cause anything else to happen). Another possibility is to require more or specific wheel events.

I set player type to iPod 5G because that’s all I have, but I expect this problem also exists on other clickwheel iPods. This problem exists on r20079 and r20033.

If your Ipod accessory doesn’t work with rockbox, you can report it here.

Please put your device name, Ipod model, and tested rockbox version in your post. If some but not all features work, be sure to mention that in your post.

Edit by rasher:
You should also add your results to this page page: http://www.rockbox.org/twiki/bin/view/Main/IpodAccessories

For any developers who might work on IAP support, please add patches to this task, so potential testers are notified.

I have been using Rockbox for almost 2 years now on my X5L together with the remote and I have frequently updated to the current version, so I am familiar with how it works.

I have noticed that after updating to version 20090221, my X5’s remote’s LCD behaves erratically (strange lines being displayed all over, vertically shaky image) right after booting Rockbox, then the display turns off completely after a few seconds. Strangely though, the controls still work and the blue display light comes on when working the controls, but the display is turned off (there is nothing being displayed, as if the player were turned off). If I unplug and reconnect the remote, the remote’s LCD comes on, but soon turns off again. The X5’s main LCD is working just fine.

I thought that my remote was dying on me, but decided to check if it was somehow related to the development of Rockbox. I reverted back one build after another and found that the last build that works OK for my remote is 20090210. So, in all the builds starting with 20090211 (I have thoroughly checked all from 20090211 to 20090225), the remote is practically unusable. I looked at the changes done on that day (http://www.rockbox.org/daily/changelogs/changes-20090211.html), but could not single out the probable cause.

Great software, anyway!

Using a bootloader from  FS#9955 , a USB connection is not made if Start Screen is set to WPS, and the user boots Rockbox by inserting a USB cable.

This is possibly also true for other values of Start Screen.

Tested on e280, but I expect it’ll likely be the case on other PP targets with USB

The H10 5G MTP needs a different bootloader than the UMS version (see http://www.rockbox.org/twiki/bin/view/Main/IriverH10PortDevInfo#Build_a_Rockbox_Bootloader).
I’m not sure about the correct way to do this in configure, so I’ll leave it to someone who is.