Rockbox mail archiveSubject: Re: Issues with Rockbox on Sansa e280
Re: Issues with Rockbox on Sansa e280
From: Charles philip Chan <cpchan_at_sympatico.ca>
Date: Sat, 28 Jul 2007 10:17:54 -0400
Gert Brinkmann <g111_at_netcologne.de> writes:
> * The worst thing is that there are background noises when using
> rockbox. The original firmware does not have this problem. Especially
> when starting the first track (mp3 or ogg - this does not matter) you
> hear modem-like sounds in the background.
Whether you can hear that also depends on your cans. I can't hear it
with my PX-100 (open cans). However, it is very noticable with IEM's.
> They disappear after some seconds and you can listen clearly to the
> music then. (I am not sure if some very quiet noises still can be
> heared, but if so they do not bother me at the moment.) But when
> scrolling through the menu you can hear a very quiet noisy tick on
> each menu item change.
The noise comes from the LCD being on and IIRC buffering.
> * The folder "MUSIC" on the Sansa did not show up in the file
> browser. After switching the settings to show all files, not only the
> supported formats, it is there. Is this a bug? I think the music
> folder should be shown in every case.
No, The original firmware have this annoying habit of hiding and
rehiding the "Music" directory. You can either unhide the directory
(which you can't do under Linux) and rename it or create a new directory
and move your music there. I personally use "Musica".
> * The plugin Bubbles should use the wheel instead of left/right to
> turn the arrow. ;)
There are patched versions that does that. You can try one of my builds
(new version in about half an hour):
> * The display shows a line with pixel errors at the top. The symbols
> that are displayed there are cut off at the half height. Can I fix
> this somehow?
This only happens with the 1.1 version of the hardware. There is a
temporary work around in my builds.
> * The plugins should be sorted in submenus to separate games, demos
> and tools. (maybe other categories?)
IIRC, there is talk of a plugin reorganization.
> It worked with the first try. (The only little thing was, that I was
> not sure if the sansa-device had to be mounted or not. But without
> mounting it, the sansapatcher could not find the device, so it was
> very clear.)
It doesn't have to be mounted when installing the bootloader (it uses
raw parition access). However, it takes a few seconds for the USB
subsystem to recognize it.
-- panic("Oh boy, that early out of memory?"); linux-2.2.16/arch/mips/mm/init.c