Rockbox

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.

I am trying to use the last method mentioned on the ipodpatcher wiki page to write Rockbox directly into the OSOS image on my iPod Nano2G. Sometimes it works properly, but other times it fails saying that it couldn't read the header from the .ipodx file. I am following the instructions exactly, so that can't be an issue. I have tried hexediting the .ipodx file, and in some cases I can get ipodpatcher to read the header by editing the first four values, but this always causes a Checksum Error. Here is the exact output:

C:\Users\Michael Marley\Downloads>ipodpatcher.exe -wf rockbox.ipodx
ipodpatcher 5.0 with v4.0 bootloaders (v1.0 for 2nd Gen Nano)
(C) Dave Chapman 2006-2009
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[INFO] Scanning disk devices… [INFO] Read XML info (4 bytes)
[INFO] Ipod found - 2nd Generation Nano ("winpod") - disk device 1
[INFO] Reading partition table from \\.\PhysicalDrive1
[INFO] Sector size is 2048 bytes
[INFO] Part Start Sector End Sector Size (MB) Type
[INFO] 0 63 48194 94.0 Empty (0x00)
[INFO] 1 48195 1982462 3777.9 W95 FAT32 (0x0b)
[INFO] Read XML info (4 bytes)
[INFO] Ipod model: 2nd Generation Nano ("winpod")
[ERR] Failed to read header from rockbox.ipodx
[ERR] –write-firmware failed.

This patch adds a couple more lines to Track Info for Play Count and Rating.
Currently these don’t seem to show up anywhere else.

Tested against r26427 with Fuze v2 and USim.

New build target, for iriver E10.

A lot of target-specific functions are missing, so it doesn't compile when it reaches the linker. But I think it's about time to insert the build target into SVN, and #rockbox seems to agree.

Also, building a simulator build works quite well. The simulator BMP and the keymaps needs some work, but it works pretty well, including music playback.

I've done some testing with building for other targets and nothing seems to be broken by this patch. I couldn't figure out how to include the BMP in the patch so i attach it separately.

Added seeking by holdplus/holdminus buttons, pause/play by holdmenu button, hiding the OSD panel by briefly pressing power switch.

When loading a saved Brickmania game, the game is loaded corrupted. Please see screenshot attached to see for yourself. There is one brick in the right side which is shown corrupted, and one corrupted rectangle in the left side of the screen which drops like a power object, and stays at the bottom of the screen.

This issue happens on Cowon D2 target. It doesn't happen on the D2's simulator.

Looking at the code and comparing the loading/saving function against the Bubble's game functions, I can see that the return value of file operations is not checked (I'll fix that).
In Bubbles, there's a single file operation of reading/writing the game context struct. In Brickmania there are several consequent file operation to read/write each variable. Maybe the drivers doesn't handle this well on this target. A workaround for that could possibly be to join all saved variables under one game context struct as in Bubbles, but that could mask a real bug somewhere else.

Building Rockbox fails if assert() (in firmware/include/assert.h) is used.

Then, I reworked assert.h.

changes:
When assert() failed, the correction that displayed the file name, the number of lines, and the condition of failing was done.
Moreover, when the log was enabled, the log was output to the file.

Please select the following to make assert() enabled when you make Rockbox.

1) Run tools/configure

2) Build (N)ormal, (A)dvanced, (S)imulator, (B)ootloader, …

    Select "A"

3) (D)EBUG, (L)ogf, (A)ssert, (S)imulator, (P)rofile, (V)oice

   Select "A"

4) make

This is a first attempt at creating an entry for the new fft plugin. The button table was automatically generated with the attached python script.

The script takes a file (or - for stdin), looks for an #ifdef CONFIG_KEYPAD….#endif block and if it finds one (and it is relatively simple), it parses it and creates the corresponding LaTeX table.

The script is extremely simple but it does provide a good basis for further work.

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 bug currently exists as of rev 21444.

If settings are modified on the recording screen they aren't persistent after a reboot unless another setting is changed somewhere in the menu system.

The problem is that global_settings is being modified without a subsequent call to settings_save().

Attached is a fix for this problem. I've so far only tested it on the h1x0 simulator but I think it's a pretty benign change, unlikely to cause problems on other targets.

This patch enables you to compile the Rockbox simulator with LLVM (you still need to alter the Makefile yourself though).

However, it fails at linking stage with 'file not recognized: File truncated' errors.

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

I tried to make the first shot on adding fm radio support for the Samsung YH-* devices.

–

As of r21894, the pitch changing mode (in the pitch screen) can only be toggled (cycled through) in one direction. However it would be handy to be able to cycle in the other direction to change procentual vs. semitone while still staying in the time stretch mode. This patch adds such a possibility.

The key mappings is only defined for H1xx and H3xx (as a long press of Mode). Please add keys for other platfroms.

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

Since FM stations list may require that the FM region is set to a certain value, it would be good if the FM region could be set along with the station list. The patch does just that.

The region is set by putting the line “region:N” into the FMR file (at any line there). N can be one of the values allowed for the fm_region setting.

The patch does not work on the simulators for e200 and h120 (the only two I tried) because, for some reason, the symbol HAVE_RADIO_REGION is not defined for them. Could anybody tell why?

Saving the region along with the station list is not implemented.

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

I was reading http://forums.rockbox.org/index.php?topic=17079.0 and thought I’d take a swing at it. So far, I have added (potentially shaky?) support for the ‘#’ comments in the file posted, allowing both Windows and Linux line ending formats, and longer filename support.
Still having problems with the white space after each entry, and detecting or assuming the presence of the file extension.

This patch is a continuation of FS#9879 and includes it (but adds something more). It adds the possibility to switch the lamp on and off without leaving the plugin.

Key mappings were taken from FS#8934.

This patch will correct how thai vowels and tonal makers display.

The scrollpad on the H10 (20gb, not sure about 5/10gb) has always bothered me with being jumpy, inaccurate, and unintuitive. At the moment (in rockbox) it seems as though it is working as a simple two button device (up/down), with no real dragging capabilities. I am wondering if this is a limitation of the hardware or current software implementation.

The original firmware seemed to work as follows:
split slider into upper and lower field. Tapping in either upper or lower half would create click-type event for up/down. Dragging in upper half would produce scroll up, draggin in lower half would produce scroll down events. The problem was that upper and lower halves are really kinda arbitrary and not easily distinguishable.

What I think would work nicely:
Tapping top and bottom, as before. Remove upper and lower restrictions for dragging, i.e. if dragging down (anywhere on the scrollpad) create scroll down event, if dragging up (again, anywhere) create scroll up event. Drag and hold will scroll in desired direction proportional to the drag speed (as in pushing a puck on ice). Hold (just hold, no tap or drag) on the touchpad creates a sliding value that can be used as a coordinate for different types of continuous input.

To implement this, we’d need some kind of knowledge about what signals the actual hardware provides, what resolution the pad has, i.e. what the physical and logical implementations of the device are. I am not sure how the Ipod scrollwheel works, but it seems that some of that code could be re-purposed, maybe?

This patch changes the iriver H300 series bootloader's power and usb handling. When a USB or Power plug are inserted into the H300, it will now boot as normal, not stop in the bootloader usb/charging modes. This was mainly for use in my car, but is also helpful for people with charging cradles for their computers.

Forum thread can be found here http://forums.rockbox.org/index.php?topic=17202.0

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

Dumb patch but introduces handling for non triangular faces (by triangulating them when rendering). Vertices courtesy of http://mackayj.doosh.net/eliteships.html (in particular I hand-converted http://mackayj.doosh.net/files/vrml/eliteships/cobra3.wrl)

This patch adds an option to disable the speed limiting that slows down seeking as you approach the end or beginning of a track.

It defaults to limiting enabled, to maintain compatibility. Personally, I prefer the fast seeking without the limiting.

The manual is not included, I can't compile them still…

Hi all.

I have found a funny thing, which should get fixed. In set_prescaled_volume there is this call:
audiohw_set_lineout_vol(tenthdb2master(0), tenthdb2master(0));

As far as I can see this call is not needed here. So this patch removes it, but as I own only a sansa e280 I can not test this change. I hope to commit this soon.

If this call is needed… do we need it every time audio changes or only once at init?

Thanks,
AustrianCOder

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

The patch reorganizes Rockboy to use the same method for storing GB frame buffer data on greyscale targets as color targets. As a result, support for greyscale iPods is much easier and has been implemented (inspired by FS #5282).

Some other changes include:
- Enable the menu for iRiver H100
- Ability to “Show Stats” on all targets
- Screen is redrawn all at once on greyscale instead of line by line
- Elimination of fb.mode (all targets use options.scaling for scaling options)
- Elimination of fb.cc on non-color targets
- Minor variable renaming
- Unification of LCD variables (vdest vs frameb)
- Move greyscale LCD code into lcd.c
- ifdef out vid_update() on greyscale and color targets

Since I don’t have an iPod, I’m curious to see how well this works. It should be fine since the patch my work is based on seems to work for people.

I really need iRiver H1X0 users to test this. There are significant changes to the LCD code and I’d like to know if the is any speed change, whether its an improvement or not. I’d guess that it’s slightly faster or the same as SVN but there’s always a chance that it is slower.

Patch changes controls for Doom:

Forward: rec/up
Left/Right: scrollwheel (it needs a lot of scrolls for large turns, but hopefully it can be modified to work better in the future)
Back: down
Shoot/Enter (menu): select
Change weapon: left
Open: right
Esc: power

Some improvements for voicebox on windows. Mainly an option to voice file extensions. Not perfect yet. Instead of an option to voice file extensions there are two voice files options in the hta file. Anyone know what is wrong with this?
Thanks

This is the first plugin I’ve ever written from scratch, and well, it was fun. I haven’t worked out how to use bitmaps yet, bear with me, for now it uses coloured rectangles. Still learning :p.

If this were to get committed, please wait until I’ve added better support for more targets, commented as many lines as are possible to help other people new to making plugins, potentially add AI (Although that would kinda ruin it as it would probably force a draw every time), and figured out how to use bitmaps properly.

If people are willing to test this out for me and tell me any bugs, please do so. I have tested this on the H10, the Gigabeat, and, using the simulator, the iPod mini G2 (Which displays it but out of alignment, will work on that soon.

I realize it’s not too exciting, but for my first real bit of work in C I’m happy :p.

Playing APE 24/44.1 with harsh noise in different parts of the track. If you decode APE file to WAV using the codec console, then there are no problems. So the matter is in the player’s APE decoder.

At 24/48 everything is fine.

I store the album art by putting a folder.jpg file in the album's directory.
Any WPS on other players shows the cover pictures properly if album art is enabled in the theme.

I am aware of caveats like progressive jpgs, that are not supported by RB.

In the attached zip file, there are four directories with a folder.jpg file and a free opus file for demonstration purposes.

All pictures show up fine on my Sansa E200 (v1) using CabbieV2 or lebellium_Samsung-like.
However, on my XduOO x3ii the pictures are not displayed for the examples 1 - 3, but show for example 4.

None of the jpgs are progressive and I cannot figure out a difference between 1-3 and 4.

I don't know how to debug this further myself, but would be happy doing any furter experiments.

This is true for the current dev builds, e.g. b450707955.

Trying to cross-compile GCC for the ipod with GCC 9.2 I keep running into errors:

In file included from ../../gcc-4.4.4/gcc/diagnostic.h:25,

               from ../../gcc-4.4.4/gcc/tree-mudflap.c:43:

../../gcc-4.4.4/gcc/pretty-print.h: At top level:
../../gcc-4.4.4/gcc/pretty-print.h:310:6: error: ‘cgraph_node’ is not defined as a type

310 |      ATTRIBUTE_GCC_PPDIAG(2,3);
    |      ^~~~~~~~~~~~~~~~~~~~

This would seem to be the same issue as the one described on https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90677

The attached patch against GCC seems to fix the problem for me.

This bug is sporatic “the worst kind”, has effected a 4gb fuze+ “foolsh in IRC” and an 8gb fuze+ “DmL in IRC“, but also has been confirmed to be absent from one other 4gb fuze+

Rockboy data aborts on menu key press, when the srceen is rotated left and image is stretched across the whole srceen. Also no matter what key is mapped to the menu entry it will still fail.

It never fails when aspect ratio is maintained with scale or when not scaled at all, and never aborts when rotated right or not at all.

Only four files even mention rotate in the apps/plugins/rockboy/ directory “lcd.c menu.c rockmacros.h and sys_rockbox.c”

Sometimes the failure does not happen and reaching the menu is possible, but the rockboy option file may get written and not allow the user back into the menu later to change the rotate option back. When this happens the option file must be edited or erased to make rockboy work again normally.

space80 is a digital-plate-like reverb effect, i dump it from my soundcard driver and translate it to c code, the original author is stylus02, thanks him for teaching me many things about the dsp theory:)

about the speed:
eats about 21.86MHz cpu on a cowon d2 target

Neither of the tools, ipodpatcher or Rockbox Utility 1.4.0, work on macOS Catalina.

Catalina removed 32bit support.

Using ipodpatcher generates the following error:

bash-3.2$ ./ipodpatcher
bash: ./ipodpatcher: Bad CPU type in executable

And Rockbox Utility has a white circle with a line through it indicating that it does not work with this version of the OS.

(see attached file)

Creative ZEN simulator build 9d0c0e3-170115
Creative ZEN device build 8fec364f6-170125

Steps:

(Using attached config.cfg)

1 Ensure Settings > Playback Settings > Shuffle is No
2 In Files, move to a list of tracks and press Select
3 In Files, move to a different list of tracks and do long Select > Current playlist > Insert
4 View the playlist e.g. http://i.imgur.com/xR0WMQm.png 5 Set Shuffle Yes and then Shuffle No
6 View the playlist

Expected e.g. https://archive.is/41khH#selection-1007.0-1007.44 , https://archive.is/nypDH#selection-1079.0-1092.0:
Playlist order restored.

Observed: Playlist changed, but not restored - http://i.imgur.com/DBW9wSI.png

Video at https://www.youtube.com/watch?v=2_s27g_FwXg

Creative ZEN simulator build 9d0c0e3-170115
Creative ZEN device build 8fec364f6-170125

Steps:

(Asing attached config.cfg)

1 Set Settings, Playback Settings > Shuffle to Yes
2 In Files, enter a folder of tracks and press Select to play
3 Go up to the folder itself, press long select > Current playlist > Insert Last
4 Press long select > Current playlist > Insert
5 Press long select > Current playlist > Insert
6 Go to Now Playing > Current playlist > View current playlist

Expected: Four copies of the list, all shuffled

Observed: One copy of the list, shuffled, followed by three not shuffled: http://i.imgur.com/Emldcdt.png

Video at https://www.youtube.com/watch?v=KANEkz0zRZ8

I am reopening  FS#11501  - Sansa Clip v2 FLAC playback skips regularly, which was closed because a sample file was not provided. I didn't think this was necessary because I stated it happened regularly with just about any file.

I am currently on build 30217. It skipped for me last night on this track:
http://www.archive.org/download/johnbutlertrio2011-07-24.lsdII.flac16/johnbutlertrio2011-07-24_lsdII_t07.flac

I cannot attach the track to this ticket because it is larger than 2mb.

Again, it is nothing inherent in that track: a second playthrough did not skip. That 16-bit/44.1khz track was generated with FLAC 1.2.1b using normal procedures.

This problem has occurred for any build I've ever tried on a clip v2 player.

Here is my original problem statement:

Build 27566 (and all previous builds), Sansa Clip v2.

playback of 16-bit/44khz FLAC format regularly will skip ahead to next track.

in a 60 minute playback session, it'll probably happen 2-3 times. this is not due to a defect in the FLAC files. it happens with any FLAC set I attempt.

this does not happen with the Clip v1 on the same build number.

this is my first bug submitted. I searched for duplicate reports but didn't find anything.

thank you!

Create silence in Audacity program (Generate → Silence). Convert the wav file to ogg vorbis file. Put into the sansa clip+ player wav and Ogg files. Turn on the equalizer and set 32 hz, 64 hz, 125 hz in the 0.5-2.0.
Turn on maximum volume. Listen to the silence of wav file. Absolute silence. Listen Ogg Vorbis file - hear the noise (like the wind). It’s bug with only ogg vorbis. mp3, flac, mp4 is absolute silence.
On a musical files it’s additional noise. Ogg vorbis is economical of disk space. Testing on a sansa clip+ with 2GB.

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

Here is how the error can be reproduced:

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

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

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

To see expected behavior:

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

To reproduce the bug:

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

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

Bug exists in the DEV builds for, at least, Sansa Clip+, Sansa Fuze+, and iPod Video for at least a year, although I cannot confirm this as I've only just now tracked down the problem. The issue was discovered because imagemagick occasionally selects 1x2,1x2,1x2 as the chroma sampling factor when converting an image.

To recreate this bug, convert any image using imagemagick to a JPEG with that chroma sampling factor and attempt to view it in Rockbox. What you will see is a nonsensical image to the size of the original JPEG. Any desktop image viewer, like eyeofgnome, renders the picture correctly.

I've also included a sample Rockbox logo generated in the faulty fashion along with this bug. To create it, run this command in a Unix-like with imagemagick and curl installed: 'curl -J -L "https://www.rockbox.org/rockbox400.png" | convert - -sampling-factor 1x2,1x2,1x2 -quality 100 folder.jpg'

This patch will add a setting, called "Scroll Bar Border", which will determine whether menus / lists will have scrollbars with borders or not.

The default value for this setting is "yes", so that it matches previous behavior.

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?

This patch changes the frequency range when selecting "Region: Other" for the FM radio:

With this patch, the "full range" from 76 MHz to 108 MHz, in 0.05 MHz steps, is available when selecting the "Other" region.

First noticed the issue in the previous dev build, and just confirmed in 15fa7f8.

When playing .opus files, no metadata is displayed. Some files (92kbit stereo music files so far) do play fine otherwise. Others induce crashes upon attempting to play. An example is attached.

First test, I played a couple of music files successfully, then tried to play the attached file. System crashed immediately showing the following:
“Undefined instruction
pc:30000002 sp:300632[display cuts off here]
bt end”

Powered off, restarted, and tried to play the attached file immediately. After a second or so of audio, player crashed again:
“Undefined instruction
pc:08180002 sp:302029[display cuts off here]
bt end”

On the previous dev build, I was getting similar errors if I tried to play the attached file (or several other similar ones) after successfully playing other files, but would get a black-screen crash if I tried to play it immediately on powerup (this is not what is happening on 15fa7f8).

I am NOT experiencing these problems on another AMSv1 player (Sansa c240 [”c200v1”]) with the same dev build, so this may be specific to the Clipv1. On the c240 with both the previous build and 15fa7f8, metadata displays fine and the attached file plays without any apparent error.

if i format the clip+'s microsd card to contain a DOS partition table, then the vfat formatted partition is not recognized.

if i format the sd card with a vfat fs starting at the first block, then the fs is recognized by rockbox.

** if i then reformat the sd card with a partition table like above, then the second fs i created is still recognized by rockbox, even though the first 512 bytes or so have been clobbered. the result is that rb and my laptop see different fs structures, and clobber each other's metadata, causing corrupt file systems.

the work-around is to dd if=/dev/zero the beginning of the sd card and format without partitions.

i kindly request that rb support dos, or some other, partition table, and maybe that rb doesn't mount fs'es which appear to be clobbered by a partition table. one problem with this change is that some people may be using a clobbered fs without knowing. with such a patch, they could end up seeing a corrupt fs instead.

i don't consider this very high priority. thanks for the awesome firmware!

Hi, thanks a lot for all of your coding efforts, support, etc. I noticed that the WPS layout changed slightly after installing the latest dev build.

===

Problem: An unexpected indent appears in the WPS after installing the latest dev build on a Sansa Clip+. Please see attachment for an example.

Steps to Reproduce:
1. Install 3.13 with Blind theme
2. Play some tracks to see WPS
3. Upgrade to latest dev build
4. Play some tracks to see WPS
5. Problem occurs here: there’s an extra indentation after the “{current track number} / {number of tracks in playlist}” text, at the bottom-left of the screen.

Player: Sansa Clip+
Rockbox version: 1879de7-140525
Binary: rockbox.sansa
Size: 582384

Additional: Possibly related to #12953

After setting the “Charge During USB Connection” Rockbox setting to “no”, the battery in my iPod Classic still gets charged whenever connecting the iPod to my PC via USB. From the iPod Video manual:

“This option lets you control whether the player should charge during the USB connection and hence draw the full 500 mA. Turning it Off is recommended if the player is connected through an unpowered USB hub or a laptop port.”

I would expect the battery NOT to get charged. Running Rockbox dev build 9576134.