Rockbox

This adds a very simple way for themers to add some customisability to their themes without requiring the user to actually edit the skin files.

2 new tags are added:
%Sl(name, default, …) to configure a setting named "name" with the default value "default", the … is any amount (up to 32) of strings which are accepted values. The order here is the order to be used with the next tag.

%Sv(name) to get the value. If the users value isnt in the above list, or the setting file is missing the default value will be used… can be used with normal ?<> conditionals or %if() (both number and name should work)

For the user to actually use this he needs to create /.rockbox/wps/skinsettings.txt which has the same syntax as .cfg files. i.e "name: value" and #comment.

This first version is very stupid and loads the .txt file into every skin which has a least one %Sl(), but the final version will do this much smarterer. (Also these settings are static so the values should be loaded at parser time instead of runtime.)

Also a plugin could be made to dump the allowed values for the used theme (or all skins) to disk to make it easier.

Because there is no limit to what the settings could be, I'm hoping that defacto setting names will just happen, the theme site could help with this also. It isnt a big deal if theme A accepts different values for a setting than theme B though.

Lastly, I need to also add a simple way for yes/no type settings %?Sv(show aa)<%Cd> should be able to work… Actually, brain fart time… because the settings are loaded at parse time we could probably use the feature handling code to always only parse the correct branch which would save a bunch of skin buffer and render time.

I think I have experienced a bug in 3.7+ builds with WPS themes related to %Vf.
If you put the %Vf on a new line, the following text is displayed, then cleared, but only if its a scrolling line, if the first line is static it is displayed properly, and subsequent lines are also displayed properly even if they are scrolling

example:

%Vl(b,0,108,176,60,1)
%Vf(999999)
%s%ac%?Ia<%Ia|>
%s%ac%?It<%It|%Fn>

artist is displayed briefly then cleared, if you take out %s artist is displayed properly, if you put the %Vf on the same line with %vl artist is displayed properly with scrolling, if you put a static text line before the first %s line then all lines are displayed properly.

so my quick fix is to just move the %vf on the line with %vl, but this bug probalby breaks many WPS, also this worked before 3.7, not sure when it stopped working. Tested this bug with latest build:r28534-101108 and 3.7 release sansa e200 v1. (also with latest e200 simulator)

this bug was not in builds up to or prior to: r27944-100830

r28936, sim build for iriver H120, fresh installation folder, i.e. no file “config.cfg”

I modified the function “sim_open” to ouput what files it’s opening, and got the following output (see attached text file). Note that there are files “-.kbd”, “-.sbs” and “-.rsbs”. I think these files should not be opened, even tried.

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

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

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

The patch adds two new WPS tags:

1. %Ln yields the number of the list item currently being drawn

2. The operator "/?" (which can be used in the %if tag) yields the string "div" if the first operant is divisible by the second and NULL otherwise.

With these two additions it should be possible to create themes where list items are coloured alternately (as an example).

The whole work has been done by gevaerts on 2011-09-12 (and all the credits also go to him), I only placed the patch to the patch tracker, changed the operator from "/" to "/?", and changed the function name from "skinlist_get_item" to "skinlist_get_item_number".

He posted the patch on the binpaste and it would be pity if it got lost.

r31037 and later causes the device and sim to crash when resuming playback after leaving FM Radio. This crash has been reproduced on both e200v1 device and w32 sim and the e200v2 w32 sim. The failure is less likely to happen when there is a small number of files on the device/sim. (I have approximately 2200 files on the device and 5400 on the sim).

Tested with r30145

Steps to reproduce:
1. load the attached fms file (needs 35-Nimbus.fnt)
2. load an fm preset file - be sure to have station art
3. enter fm radio and select a preset station be sure art is displayed
4. power off device or sim
5. power on device or sim
6. start a playlist
7. stop playback
8. power off device or sim
9. power on device or sim
10. enter radio
11. exit radio
12. select resume playback
13. device or sim crashes

The e200v1 crash is:
Data abort
at 000095F0 (0)

When using an image in a theme it shows ugly gradients/dithering, as if it was only 16 bit. When the same image however is used as backdrop (%X tag, instead of ‘regular’ %xl and %xd), it looks smooth and 24 bit.

Attached image shows the issue. Top half shows what Rockbox does when the image is loaded via %xl and %xd. Bottom half shows how the image should look like (and how it does indeed look when it’s used as a %X backdrop).

Tested on a Cowon D2 simulator and on an Android device running RaaA.

Both issues seem to appear with any version of my theme and with any build.
Let's try it with the latest version 1.30 of my theme (in attachment but also here: http://themes.rockbox.org/index.php?themeid=1585 ) and a recent build (I use version: 0c4bd3a-120406)

-Theme loading

When you load the theme for the 1st time, the WPS will never load properly (failsafe). The workaround is to turn off the device and turn it on again and then the WPS will always load properly until you reload the theme for some reasons (trying another theme and revert back to mine etc).
I tried both with the full theme version and this "light" version of WPS: http://pastie.org/3747546

-USB connection (tested on Windows 7, with or without a microSD, and there isn't such an issue with the other themes)

If I plug the USB cable while the player is on or off, it will almost never mount properly.
Usually the USB screen appears on my SBS, the computer recognizes a USB device is connected but either nothing appears in "my computer" or the device appears but is not accessible. When I unplug the USB cable, the Zip gets stuck on the USB screen and only reset can turn it off.
Sometimes it even displays some erros like that when plugging the USB cable: "data abort at 30FSR 0x8 (domain 0, fault address 0x964176 bt pc: 0x3006AC3 bt end" , sometimes it doesn't display the USB on SBS but gets stuck on the main menu.
And rarely in the same conditions it also mounts properly…

Like for WPS, I made a "light" version of SBS without the status bar and that way the Zip seems to mount and unmout properly every time!
http://pastie.org/private/cauhxelaip7hrpqpcwdbxw So maybe a tag in the status bar causes the issue with USB connection?

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

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?

Android:
The Notification bar which use "Remoteviews" may be not suitable for some ICS Roms (see Attachment).
So I change the Remoteviews to "Notification.setLatestEventInfo" to display the track information.

The patch may have some offsets.

%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

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.

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

Consider the following theme markup:

%Vl(progressbar,306,156,10,80,-)
%pb(0,0,10,80,progressbar.bmp,vertical)

That draws a vertical progress bar that will get filled from bottom to top. When a song starts to play, the progress bar is one pixel high, at the correct position (at the bottom of the viewport). That 1px-high image quickly jumps up one pixel (moves up by one pixel), then comes back down one pixel (at the correct position) whenever the progress percentage is high enough. The progress bar then displays normally and grows as the song is playing. See attached screenshots.

Expected behavior: the position of the progress bar (relative to the viewport) should not change. The bug has been observed in the iPod Classic and Clip Zip sims (builds 1bc89bd and 77bfff5) as well on the actual devices. Inverting the progress bar (with the "invert" parameter) shows the correct behavior (inverted bar with no such glitch).

Affected themes: Ash (iPod Classic), SugarBrown (Clip Zip).

When a WPS defines a touch area combining %T and setting_inc or setting_dec, although the themesite parser does not show any problems and allows the theme to be loaded normally, the themesite doesn't display the theme. Some examples to be found in this forums thread : http://forums.rockbox.org/index.php?topic=25098.msg173725#msg173725

Note: This is work in progress.
Status: Code implemented

      Manual not updated
      Wiki not updated (only after commit)

The idea of this patch is to have the same keyboard keys assign to the same actions in all platforms.

For example, have +/- keys (both on keyboard and on Numpad) are assigned to Volume Up and Volume Down keys of the original platform.
For platforms which do not have these keys, pressing the +/- keys in the simulator will do nothing.

This change will help developers to do manual regression testing on lots of platforms easily, as they do not have to memorize each platform’s key assignment.

Future development: Display key assignment on screen, and/or on console

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.

This patch enables you to control the simulator using a named pipe to provide simulated keypresses, rather than the keyboard.

Unfortunately there is a bug that means that not all events seem to have any effect. On the e200 sim, I can use the scroll buttons to move in the main menu, but neither RIGHT nor SELECT lets me enter any of the entries. I suspect it's related to repeat or hold/release handling, but I'm not sure how to fake that properly.

This patch adds to the simulator the ability to simulate usb on a Linux host.
To do this, you'll need to download, build and install a device driver. You can download it here:
http://sourceforge.net/projects/usb-vhci/files/ Just download the "linux kernel module". See install instruction in it but it's make && make install. Of course you'll need root rights. There also a wiki about it (http://sourceforge.net/apps/mediawiki/usb-vhci/index.php?title=Main_Page)

Now to have usb simulation works correctly you'll of course need to load the driver
modprobe vhci-hcd
And you'll probably need to edit the access rights of the device control device:
violent example: chmod 0666 /dev/vhci-ctrl
other example: chown root:<myself> /dev/vhci-ctrl
Or you can add a udev rule if you can make this work.

You can then run the simulator normally (note the the detection is at runtime so you don't need to have it work before launching the simulator).
Press 'u' to simulate usb insertion and 'u' once more the simulate usb removal.

Some miscellaneous remarks:
-the patch enables usb hid but for some reasons it doesn't work in main menu. However, the remote_control plugins works
-the patch enables usbserial which of no interest here but a way to test bulk transfers
-the patch DOESN'T enable usbstorage because storage simulation is a stub currently.

If it doesn't work, you can still uncomment this line in usb-drc.c:
/*#define USB_VHCI_DRIVER_DEBUG*/
And this line in usb-core.c:
/*#define LOGF_ENABLE*/
But beware ! Your console will end up full of obscure messages.

I'm particulary interested in compile feedback under Windows and OSX.
And of course I'm interested in working feedback ranging from device detection to working state (HID and usbserial) for example.

This patchs modifies the simulator so that it can emulate the storage layer. More preciserly, it enables all the storage code and simply redirect all storage_{read,write, …} to a file. This way, all fs functions used are the one of rockbox, which allows to debug the FAT code for example.

To run this, apply the patch and modify the makefile to add this: -DROCKBOX_SIMULATE_STORAGE_LAYER
to the line:
export GCCOPTS=….

When running the simulator, it expects to read from file simdisk.raw. You can change this by using the –root option:
./rockboxui –root <file>

The code doesn’t work for me, FAT code seems to choke on something for now, I’m not sure why.

Sorry, not sure in which build part of this ceased to function, but I think it was just prior to 3.10

In the Clip Sim's I can no longer access the Lock Screen. "H" used to do this for me, as I recall.

Also, the charge values in the Clip Sim's no longer incrementally increase and decrease. The charge values used to go from 0 to 100 and then back down again.

This applies to the Clip Zip Sim as well. I haven't tried the Fuze Sim.

Thanks.

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

rockbox 3.5: ipod doesn’t recognize the connection of usb. i understand that rockbox doesn’t support usb on a 3G ipod, but it would be nice to boot into disk-mode like it does for firewire.

Seen with r27199 on the e200 simulator.

If I place a .wps file in the root directory and “play” it from the file browser, the WPS is not loaded. I’d expect it to load but not to be saved as the setting.

The same file is loaded if it’s in the directory /.rockbox/wps, i.e. it’s not the wrong file contents that’s causing the error.

This patch allows the line out on the Sansa Fuze V2 to be enable/disabled by means of the existing Lineout poweroff setting (previously used on some iPods).

By assigning this setting to the quickscreen I can switch between headphones and lineout after plugging into the dock. Still no luck in finding out how to autodetect the dock.

I'm not 100% sure that re-using the "Lineout Poweroff" setting is the right thing to do here as it's not powering on/off the line-out - just switching between headphones and line out

Following my patch to control line-out on the Fuze via a setting on the quickscreen (FS#12074), I found I kept forgetting to leave the quickscreen. This meant that when I intended to change track, I was actually changing the shuffle / repeat settings etc and had to fiddle around to get back to where I wanted to - not a good idea when driving at >70mph!

The attached patch adds a configurable timeout to the quickscreen so that it returns to the WPS screen if no button is touched within N seconds. 0 (the default) will disable the timeout preserving the existing behaviour.

When I use the "Wake Up Alarm" with the "Wake Up Screen" set to "Recording." my Nano turns on OK, but the screen starts on the FM screen. This is especially strange as there is no FM radio on this player.

I am expecting the player to turn on and start recording.

This is a 1g Nano running 3.9

Thanks.

in svn settings_apply() is called whenever a config is loaded (after boot) regardless of what is in the file. even an empty one will cause a full settings_apply() (which is slow, causes disk access and will stop music thanks to the buflib users).

This patch will apply settings individually if they have a callback registered, and if no settings without a callback are applied it doesnt bother calling settings_apply().

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

I 4: IllInstr

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

*PANIC*
Stkov main

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

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

I have attached the config file that creates the problem.

Settings such as "eq enabled" and "replaygain type" do not apply to a playing track when selected from shortcut menu, although the setting does appear to have changed when checking in the settings menu. The audio remains unchanged when changing the settings. However, when changing the same settings via the settings menu they function correctly (e.g. audio noticeably changes from loud to quiet after a few seconds).

Also, while displaying "debug info" on the wps, I noticed that %rg (replaygain value in dB) DOES change when the replaygain is changed via the shortcut menu, even though the audio doesn't change. (Both %rg and the audio change when the same setting is changed via the settings menu).

NB Some settings DO work, such as bass and treble.

Problem noticed on Sansa Clip Zip (build 2f1da04-120627), UiSimulator of Sansa Clip Zip (build fa17cb9M-120627).

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

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.

Hello there,

When I reboot my Rockboxed iPod nano second generation, it changes the time +5 hours.

Does anyone know why this can be? Thanks

Pressing the remote volume UP key on my iriver 140 in wps sometimes results in directory skip.
This is not easy to reproduce, but I was able to repeat once that problem in conditions where I'm sure that the directory skip key wasn't pressed.

I don't know if it's a hardware related problem, but I've read somewhere about another user having the same problem.

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

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

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

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!

When adding text via the keyboard, neither the selection function nor the done function work using the remote play button. Pressing 'play' on the main unit however, does work and has the correct behaviour.

I checked the keymap-m3.c source and I noticed that unlike the other entires, the last entry for these options refers to the main unit buttons and not the remote:

{ ACTION_KBD_SELECT, BUTTON_RC_PLAY|BUTTON_REL, BUTTON_PLAY },
{ ACTION_KBD_DONE, BUTTON_RC_PLAY|BUTTON_REPEAT, BUTTON_PLAY },

I changed the entries to the following:

{ ACTION_KBD_SELECT, BUTTON_RC_PLAY|BUTTON_REL, BUTTON_RC_PLAY },
{ ACTION_KBD_DONE, BUTTON_RC_PLAY|BUTTON_REPEAT, BUTTON_RC_PLAY },

After rebuilding and installing this change onto my M3 the keybord now works when using the remote.

Attached is the patch file for this change.

Hi,

this patch, that takes some of the FS10494, improves dock detection and initialization.

It should correct the erratic behaviour on some hardware, and it also adds support for some remote buttons: menu, select, up_arrow and down_arrow.

The buttons arrow are not usable by now, even if they are defined. I tried severals things but i couldn't get it to work.

Any idea of which context I should use to use the button arrow to scroll through the main menu?

When connected to PC.
While transferring files from PC to Sansa e280v2.
Both source and destination folders are open.
Sansa shuts off after some time. while transfer is still happening.
this does not happen with original firmware.

Rockbox starts with remote, but doesn't respond to button presses except turning backlight on with build 6039eb05b-180313.
It works with deaeb73-161114 though.

Hi,
I’m trying to record myself playing the guitar using my old, trusty FuzeV2 (both a very old version - sorry didn’t wrote it down but had to be at least a couple of years ago - and today’s version 87229a4). Recording parameters as follows:

Trigger: Repeat
TrigType: New file
Prerecord Time: 1s
Start Above: -22dB
for at least: 1s
Stop Below: -26dB
for at least: 1s
Presplit Gap: 1s (don’t really understand what it does from the manual, but it says it usually has to be the same value of the Stop Below Time, so…)

Recording starts correctly when noise is detected according to conditions; then apparently it correctly detects the silence and stops the recording. But immediately the ‘Repeat Trigger’ parameter kicks in and _immediately starts a new recording_. At this point, the trigger status and the recording status aren’t matching anymore. The recording screen shows the recording file size growing, but the Trigger status is ‘Ready’. I have confirmed that on the actual file on disk the silence is meanwhile recorded.

Did I understand any of the parameters wrong or has anybody else the same problem?

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.

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.

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

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.

I navigate to any directory in the file tree, enter the context menu and set it as the recording directory. Then I go to the recording screen, cancel out immediately and return to the file tree.

There is now a new directory, in the same place as the directory I just set for recording. The new directory has exactly the same name except the final 3 letters have been removed, and it is this directory that has become the recording directory. The original directory is still there too, but now it does nothing.

The workaround is to create a bogus directory with 3 extra letters, then delete it once the bug creates the new directory with the truncated name.

Hi!

I’ve found very important bug in Rockbox 3.7, witch my be dangerous for both the player and the memory card (if present).
It turned out that Rockbox doesn’t react to very low battery level while voice or FM radio is recorded. It causes damage to the recorded file when finally hardware falls due to lack of energy. This corrupted file is absolutely unreadable.

What the title says.
At whatever sample rate I use (24k & 48k tested), each sample is duplicated.