Rockbox

This is a reopen of issue #1 of  bug 7354  (http://www.rockbox.org/tracker/task/7354)

SETUP:
HW: sansa clip+
SW: 8687b98-121001

CD's ripped as wav/cue with EAC 1.0b3 then converted to FLAC w/embedded cue with cuetools 2.1.4; used accuraterip to confirm good rip.

EXPECTED BEHAVIOUR:

loading a flac w/embedded cue would display markers within the track and allow forward/back skipping within the track.

ISSUE:
Some tracks I am unable skip to using next/back or rewind to the start of using back.
If I listen to the whole preceeding track then the display updates correctly as it goes.

I've tested this with a handful of CDs, and given the previous bug, this appears to be a general issue with flacs/embedded cuefiles.

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.

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.

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

Player: Sansa Clip+
FW: Rockbox 3.12, official stable build, but it happens on older versions too

While playing some FLAC file, RB skips to the next track automatically. I know there is a lot of similar bugs, but this is unique:)
Firstly, the problem is repeatable on my Clip. Skipping is always at one time, e.g. 00:19 for one file and 01:40 for other one. I think that these files are stored on corrupted part of SD card. OK, if it's corrupted then I have to buy a new one, but when I switch to original Sansa Clip+ firmware it play normally! At problematic places (00:19 or 01:40) there is a little 'click', but it continues to play. My conclusion is: if original FW handles such a files on bad memory, Rockbox should has workaround also.
Files are OK, when I copy them to internal memory, Rockbox plays continuously.
I didn't notice skipping of MP3 files on the same SD card, only with FLACs.
Computer players (e.g. AIMP) plays FLACs from this SD without any problems.

I've attached movies that presents the bug on 2 different tracks. Hope it helps.
http://youtu.be/0e4Xf8rKTh0 http://youtu.be/zl4LX4wEwlI

I recognize some problem with USB support.

When I’m connecting my player first time, it’s work correct - computer’s mounting device propertly. BUT When I disconnecting it, turn on playing and while music is still playing I’m connecting player once more - Rockbox is crashing and give information about “unidentified instruction at… “. Now player looks like dead - I must reset it and Rockbox start correctly.
When I’m not turning on songs - all works fine.

Sorry for my english…I’m still learining It

when rockbox startup, a loud popping sound will be produced to the output

if plug off the headphone before startup, and plug in on after startup, the popping sound also produced;

if plug it before startup and hear the popping, then re-plug the headphone will not hear any popping again(until i restart the rockbox)

I am working on adding album art support for FLAC and Ogg files. FLAC looks straightfoward, but there is a design problem with Ogg.

https://wiki.xiph.org/VorbisComment#Cover_art

The struct containing the image and associated data is base64 encoded. I can't just set id3→albumart.pos to a location in the file like all other supported album art formats (and FLAC). Obivously I could allocate memory for the decoded base64 data, but it would have to be deallocated later to prevent a leak.

On IRC, nick_p suggested: "how about adding a new id3 struct element id3→albumart.base64_encoded=true and decoding it when needed on the fly?" This sounds like a good idea, with one issue: it's not the album art alone that is base64 encoded, but the data struct described here:

http://flac.sourceforge.net/format.html#metadata_block_picture

I can test to see if I can parse the beginning of the base64 block, then set the pos pointer to the middle of of the block (with the id3 struct addition) and see if it will still decode.

The remaining time estimate shown under System>Rockbox Info reports just “0h -1m”.

The battery indicator on the status line works OK… maybe it’s just a display bug?

The Clip Zip's text viewer does not bookmark anymore. When holding down the Submenu and Select keys (which according to the manual sets a bookmark), no bookmark is created, and the screen flashes between the context menu and the text file instead. This bug has been confirmed by skip252 here: [ http://anythingbutipod.com/forum/showthread.php?p=629493&posted=1#post629493 ].

Rockbox build is the latest dev build at the time of filing [62de15f-130103].

As the title suggests, fun things like: https://plus.google.com/102855057878446061693/posts/FkQ4wQZb8VD can happen in this instance.

Initially reported here: http://www.rockbox.org/irc/log-20130113#07:14:49

[Saint]

When my Fuze+ is charged and it's still connected to the charger, it seems it keeps toggling between charging and discharging.

I think the problem is that it reacts to some voltage to stop charging. When it's charging it measures up to 4.35 V. But when it stops charging it changes to 4.25V, and says something like 96-99% charged, and which point it changes to charging again, and so on.

So it's basicly toggling between charging and discharging very often, and I don't think that's very good for the battery. Once it's charged it should stop charging as long as the charger is connected. (This might apply to other devices too.)

This was with version 2ef7a54-130111

Kurt

%px tag does not behave properly with large files. When playback reaches the time 11:55:50, then the %px resets (starting to show 0).
It’s more extensively described here: http://forums.rockbox.org/index.php/topic,42661.0.html

Sometimes my Clip Zip gets in a state where I can resume playback after booting it but then it doesn’t let me seek anymore (seek thingy still moves but then jumps back to where it was, playback is totally unaffected which in this case is bad of course). I also can’t pause or skip. I can go back to the main menu but I can’t move the cursor or go back to the WPS. When I go into the playlist by long-pressing down, the list usually appears but is not functional although here I can usually move the cursor up and down (sometimes I only get a kind of frame but rendering freezes at that point). Trying to shut down lets the “shutting down” popup appear but that’s it.

I seem to remember that going via “recent bookmarks” once was a workaround but in the current state this doesn’t work either.

This broken states persists between shutdowns (or well, switch-offs more like since shutting down doesn’t work). I also tried to recreate the playlist but that didn’t help either so I’m currently stuck with a player that will play but I can’t it make change what to play. I will also have to listen to the same podcast over and over again since no new resume position is saved.

The build I use is 42a725f.

Oh and sorry I didn’t choose the right player. Couldn’t find any Sansa Clip in the list in fact :/

I’m having weird problems with a 160Gb 6G Classic (yes I know it’s unsupported/unstable).

With emcore and rockbox it works fine. Connecting it to my computer the USB works as expected and everything is great (copied 100Gb+ of music to it with no trouble).

However… when I connect it to either of my cars (via USB), the iPod shows the USB screen for a few seconds then goes back to the Rockbox menu and locks solid. It then needs a MENU+Select to reboot it.

Using a USB flash drive in both cars (different head units) works fine and I can navigate around the filesystem and play music. I did notice that the flash drive was partitioned, not ‘superfloppy’, so I setup my iPod with 1 partition and stuck rockbox on that…. didn’t make any difference though.

Someone suggested that the head units (Kenwood and OEM Jaguar) might be detecting the device as an iPod from the USB ID and then ‘doing something special’. So I compiled my own rockbox from git source changing the USB ID and VENDOR to 0001. I then verified the change by doing a lsusb on my Linux box and the ID showed as 0001:0001.

Sadly this makes zero difference to the iPod’s behaviour when connected to my car(s).

Does anyone have any suggestions? I’m happy to recompile, grabs logs, insert code etc

Here’s the rockbox-info.txt from the one I built:

Target: ipod6g
Target id: 71
Target define: -DIPOD_6G
Memory: 64
CPU: arm
Manufacturer: s5l8702
Version: 189148eM-130128
Binary: rockbox.ipod
Binary size: 646268
Voice format: 400
Actual size: 646260
RAM usage: 1755172
Features: accessory_supply:backlight_brightness:crossfade:dircache:headphone_detection:hold_button:hotkey:lcd_bitmap:lcd_non-mono:lcd_color:lcd_sleep:morse_input:pitchscreen:quickscreen:rtc:swcodec:tagcache:tc_ramcache:charging:usb_charging_enable:wheel_acceleration:lineout_poweroff:large_plugin_buffer:albumart:disk_storage:scrollwheel:usb_power:usbstack:hardware_click
gcc: arm-elf-eabi-gcc (GCC) 4.4.4
ld: GNU ld (GNU Binutils) 2.20.1.20100303
Host gcc: gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
Host system: Linux

Rockbox Daily Build rev 085c10 (2013-01-30)
120gb 7G iPod Classic.

When I connect my rockboxed iPod Classic via Line Out (Apple Dock or Fiio Line Out Adapter) I’m getting heavy distorted with clipping an low volume sound. Headphones out its working while connected to the dock.

Same reported in the mailing list (http://www.rockbox.org/mail/archive/rockbox-archive-2012-10/0006.shtml). Stock firmware, and rockboxed iPod Video (5.5G) working with the same setting.

I have no programing knowledge, but I’m willing to help!!

I’m using 42a725f, and after frequency scaling implementation, sometimes the player slowdown extremely, being unusable (don’t stop playing, only small gaps in audio occur).
Less frequently, the player freezes.

I noticed it’s happens more frequently if the device is just powered on, and hits play. If I wait a few seconds before resuming play, the freezes are less frequent.

- How often does this happen?
* Frequently, about 2 o 3 times a day (4 hour average playback time, with several shutdown/boot in the middle)

- playing which file format (mp3, ogg, flac, mpc, etc…)?
* Confirmed with mp3 and flac

- which lcd is your device?
*st7783

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.

The MENU key is mapped to close the Chip8 emulator, so mapping it to a Chip8 key is pointless. This makes some games unplayable.
This may affect other iPod models, I don’t know.

Key lock (activated by pressing Power in the WPS) deactivates when music playback stops (end of playlist). The keypad then becomes active again. It shouldn’t get activated until Power is pressed again.

Changing “Enable EQ” setting does nothing until the player is restarted. However, selecting an EQ preset does enable the EQ and take affect within a few seconds. With the new 3.13 presets I am working around this issue by simply selecting the “Flat” EQ config file to “Turn Off” the EQ. I have tried stopping playback and skipping around to other tracks forcing the buffer to refill. That doesn’t work.

I don’t know when the bug was introduced except that testing 3.11 on my Gigabeat F proved it WAS NOT present in 3.11.

I have verified the bug in 3.13 on all of these targets, so at this time I’m saying this affects all players.

Confirmed on Fuze v2, Clip v1, Clip +, Clip Zip, Gigabeat F

Version: 3.13

Variable ‘tmp’ on line 565 is possibly not initialised (found by cppcheck).

I would like to leave my player charging overnight and have it resume playback in the morning to wake me.

My player remains on when charging and cannot be turned off.

The alarm does not resume playing if the player is already on when the alarm time passes.

I suspect this probably applies to all players, mine is a Sandisk Sansa Clip+.

Rockbox info says v. 3.13 - the stable build grabbed by RockboxUtility, which this bugtracker doesn’t seem to know about yet.

It seems that operators are discarded when used in a tagnavi.config (or tagnavi_custom.config) format line condition.

For example,

%format “fmt_abtitle” “*%s - %02d:%02d” title Lm Ls ? playcount > “0” & lastoffset == “0” %format “fmt_abtitle” “%s - %02d:%02d” title Lm Ls Now if we used “fmt_abtitle” instead of “fmt_title” in the default tagnavi file, we would expect all tracks with a playcount greater than 0 and lastoffset equal to zero to be prefixed by three asterixes (*). Instead ALL the tracks with a playcount greater than zero are prefixed, leading me to think that the & lastoffset == “0” part is discarded. If I make the following change:

%format “fmt_abtitle” “***%s - %02d:%02d” title Lm Ls ? lastoffset == “0” & playcount > “0” %format “fmt_abtitle” “%s - %02d:%02d” title Lm Ls

Now all tracks with a lastoffset equal to zero are prefixed, which again proves that the and operator was clearly ignored and unparsed.

Playback halts.
No error screen appears – screen seems to stay where it is when freeze occurs, i.e. WPS or back light off.

Tested multiple audio formats.

Does not occur if no head phones are plugged in.

If you play a song for a bit at low volume (tested -14dB) before raising the volume, it is okay.

To reproduce:
Find a loud, bass-heavy part of a song, and halt playback right there.
Set volume to 6dB.
Set bass to 14.
Resume playback.

Usually freezes in less than a second when I do that.

RB version:
33f3af2-130523

This may be all players; I have only had experience with the Sansa Clip+ and Clip Zip. On version 3.13 the Automatic Resume feature works inconsistently, especially on the 2nd+ file of a playlist.

In version 3.11.2, the feature worked correctly on my Clip+. If I paused the player and the player turned off due to the timeout, when I turned the player back on and pressed the “Home” button or “Resume Playback”, the entire playlist would be back in place and playback would resume at the spot I paused. If I was 30 seconds into the third file in a playlist, playback would resume at that point. When that file finished, the next file in the playlist would start. Pressing “Previous” or “Next” would play the previous or next file in the playlist.

In version 3.13, this feature does not always work correctly. In fact, it rarely works correctly when playing a file that is not the first file in a playlist. Some times it works fine. Most times when I try to resume playback, it instead plays the beginning of the first track in the playlist. Some times when that happens, if I manually navigate to the track I was in when I paused, it will resume that track from the correct position rather than starting it over from the beginning.

This behavior is seriously agitating. I use my player to listen to multi-hour podcasts broken into separate files for each hour. If I get a phone call and pause my player I expect my player to automatically shut itself off after a few minutes, and it does. When I start the player again, I want to be able to pick up just where I left off. On versions prior to this, I could. In 3.13 it does not work 9 out of 10 times.

In FAT, file name can have max 255 characters (not bytes).
A file name that have 255 characters(contains many multibyte characters) is listed in File menu, but playback can’t.

Using patched firmware\include\file.h as a test, MAX_PATH 260 up to 520, rockbox can playback the long name file.
But, changing theme causes PANIC.

Alarm wakeup doesn’t work reliably. It is unclear whether the setup is wrong or the wake up is. It might be that the player wakes up before time because of a small press on the power button and thus somehow forgets about alarm.

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.

When displaying %mp in a theme while playback is stopped, the value 0 (zero) is displayed.

However, to test for “playback stopped”, one has to test:
%?if(%mp, =, 1)
That is, one has to test for (index + 1) in order to return true for any given enumerator index number.

Same problem when testing for an arbitrary number. Example:
%?if(%ss(0, 2, %St(font), number), =, 15)
returns true when the font is set to “14-Nimbus”, and false when the font is set to “15-Adobe-Helvetica”.

When testing a %tag that holds a numerical value though, it works as expected:
%?if(%pv, =, 0)
returns true when volume is set to 0dB.

Fixing this would likely break all existing Rockbox themes. One solution to this, would be to require new / updated themes to include some specific code that “acknowledges” the new behavior.

The filename cover.jpg works ok. But {album}-{artist}.jpg doesnt wokr. Also the albumart appears on the WPS, but not in the Pictureflow

I’m using the latest Dev build for the Fuze+. SanDisk Sansa Fuze+ 5ef1e2d. Same issues experienced in v3.12 stable.

The screen, for lack of a better term, jumps when navigating in upside-down mode.

http://youtu.be/dRfiBtMx2to

According to the manual, to exit the EQ settings page you press the back button on the fuze+. This doesn’t work. I tried all key combos and none work.

(Confirmed this in 4c6c8cd-130926, discovered in build from several weeks earlier)

If ‘Voice Menus’ are enabled, entering the Recording menu will freeze the player…usually before the entire screen is redrawn. Although I can still hear the sound the mic is picking up, the player is locked up, and removing the battery or super-long-pressing of Power is required.

During my testing, I was able to randomly get it to -not- lock up, but it was like a 1 in 50 occurance…tried all formats/sample rates/etc. When ‘Voice Menus’ is -disabled-, all formats/rates/etc work fine.

Thinking it was a problem with my config that I’ve been using for years, I tried with a clean config.cfg (well, deleted and let it regenerate), and narrowed the cause down to the spoken ‘Voice Menus’ being enabled.

Latest version of rockbox installed on both Sansa e200 2GB and Sansa Clip Zip 4GB. (3.13) Sorry, release 3.12 was the only one available in the reported version pulldown.

Windows 7 Pro 16GB RAM, i5-2500K, 3.3GHz/ 3.6 GHz, 64-bit. 7.3 Windows Experience Index. OS is otherwise stable and up-to-date.

Blue Screen of Death only happens when I try to connect first one Sansa Device via USB to Windows, transfer mp3’s or update a theme, unplug it, then connect a second Sansa different device. It doesn’t matter whether I start with the e200 or the Clip Zip or vice versa. Upon immediately connecting via USB with the second device, I get a BSOD. I have two e200 devices. It can happen sometimes even when I connect first one e200, then the other.

I can disconnect and reconnect the starting device (for instance the Clip Zip) as often as necessary, but if I want to connect to the e200 (for instance to update a theme), I have to reboot the computer in order to avoid the BSOD.

Short Next + Long Next causes a hang about 50% of the time. This was reported before and still seems to happen on the Clip Zip.

The 2bit greyscale LCD drivers ignore the current viewport’s drawmode. This makes you unable to draw icons with a non-clear background.

When I connect my Sansa Clip Zip with most recent Rockbox version to my pc (Windows 8) while it’s paused or not playing a song at all, pc gives message ‘Device not recognized’.
When a song is playing, and I connect the player to the pc, the song will pause (expected behaviour of course), and I can access the internal and sd storage on the device.

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?

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.

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.

http://www.konscience.de/wp-content/uploads/kns017-maertyrer-gegen-copyright.m4a

The current build as well as 3.13 report and then fail:

parsing /kns017-maertyrer-gegen-copyright.m4a failed (format: ALAC)

However, foobar reports:

Codec profile : AAC SBR

Which is likely correct given that the bitrate is far too low to be ALAC.

http://web.mit.edu/mgg6/www/cover.jpg

This file is correctly decoded and displayed in the Fuze+ simulator, but testing on device results in playback stopping. Interestingly, nothing crashes, playback just stops. In theory we should be able to decode this, the resizer does not need to load more than a few lines of the image at once, which should easily fit in memory. Alternatively, if it is too large (or rather wide given that its decoded line by line) for the available space, it should probably just be rejected.

Metronome plugin is not functional on Ipod 6G.

Steps to reproduce:
1) Open metronome;
2) Hold the "Select" button.

Expected:
– The metronome starts to tick in the headphones.

Observed:
– The text on the screen changes from "start: hold select" to "stop : cancel", but no sound is made.
– A short click on the Select button emits a single tick sound, but the tapped frequency cannot be captured as the Ipod 6G does not have any "Record" button.

Comment:
As single taps can be made, the metronome.c / play_tock() seems to work
and at least some sort of sound can be produced on this hardware,
maybe something is wrong with the timer_callback() ?

When I try to build rockbox, I get the following error:

=⇒ make: execvp: /bin/sh: Argument list too long
⇐=

My build path is a fairly long path. Building it at a location with shorter path it works. Details:

Steps to reproduce:

* Create a location where you want to have the sources; use a fairly long path name, e.g.

  mkdir -p /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/

* Change to that directory:

  cd /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/

* Download git sources (Tried with version from 2014-09-22, 10:55:11 GMT+1, Commit by "Marcin Bukat marcin.bukat@gmail.com", Change-Id: "Ie3aa9b208e3f4f17d4d02f11f69839e9b381217d") to a long path:

  git clone git://git.rockbox.org/rockbox 

* Make a build directory and change into it:

  mkdir -p /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2
  cd /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2

* Configure the build:

  ../rockbox/tools/configure --target=63 --type=N

prodces the output

==>

Using temporary directory /tmp
Platform set to sansafuzev2
Normal build selected
Using source code root directory: /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/rockbox
Using arm-elf-eabi-gcc 4.4.4 (404)
Using arm-elf-eabi-ld 2.20.1.20100303
Found and uses ccache (/sbin/ccache)
Automatically selected arch: arm (ver 5)
Created Makefile

<==

* Running "make":

  make

produces the output

==>

Generating dependencies
make: execvp: /bin/sh: Argument list too long
make: *** No rule to make target '/home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2/make.dep', needed by 'all'. Stop.

<==

and returns with exit code 2.

Workaround:

Building it in a directory with shorter path, e.g. doing everything in "/tmp", works.

But that is only a workaround; it should not fail when building in arbitrary locations, and especially not with a message not making it clear _what_ the underlying problem ist. (I had to do a long internet search to get to the idea that the build place can be the problem).

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.

I have Rockbox (Development version Revision 9a5f7ce). Rockbox music playback was crystal clear, however after few days of use, a constant static background hiss/static noise can be heard.

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.

The following link to example.m4b file which I can’t open in latest rockbox build (4c4c645) on my sansa clip+ and sansa clip zip:
https://cloud.mail.ru/public/KeHt/tmu5sr9YR

I can open it on my computer without any issues.

First, thanks for existing …

I just bought a 8GB Sansa Clip+ and had issues when trying to listen 24 bit Flacs, which was instantly solved using RockBox. Well, the issue I’d like to report is that it freezes when I plug it into my Mac while having the SD card on it; to avoid this I have to remove the SD card, but this is kind of unconfortable.

Any advise?

Thanks in advance