Rockbox

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.

Version 9e186e34ab-190820

i have an ipod 7th gen
rockbox installed
140.000 titles

database contains in unpredictable many cases of the folders 2 times the same title
not in all folders, but it happens very often that i open one and i see all titles 2x although they are only 1x on the sd card

the files exist only ONCE
but the database keeps listing them all 2 times

i rebuilt it several times, but the database keeps on doing that

any hint what i can do?

start as apple / itunes and delete rockbox folder / install new did not help

This is a sequel for  FS#5736 . It correctly displays the OEM-encoded short DOS file names.

Following code pages are supported: cp850 (western Europe), cp852 (central Europe), cp737 (greek), cp866 (cyriliic), cp862 (hebrew).

If you change the default code page (in the settings menu) and there are files that are displayed with the short DOS names, you’d better rebuild the dir cache (if it’s activated) since the UTF8-name of the file changes.

When I compile the modified sources, I get the following warning which I don’t understand:
CC common/unicode.c
common/unicode.c:136: warning: function declaration isn’t a prototype

Could anyone tell me what that means and what the reason is?

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 should apply to all ipods, but needs testing - on both a mixture of ipods and mixture of operating systems. I’ve tested it successfully on my Color with both Linux and Mac OS X.

Current SVN behaviour is to write some magic to the end of IRAM and reboot the ipod when a USB connection is detected. This causes the Apple bootloader to start the disk mode application which is stored in flash ROM.

This patch cuts out the reboot stage and uses rolo to start the disk mode application directly from flash - meaning the ipod enters disk mode almost immediately. This is done in a new rolo_load_rom() function which copies the image from ROM to RAM and then executes it.

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

First approach, to add dma read/write disk access to the sansa.

There are some restrictions on the dma functionality with this patch:
- only stabile at 80MHz ⇒ cpu boost control added to the driver
- only on 16byte aligned data ptr ⇒ all data are copied to/from aligned memory
- no interrupt support ⇒ using polling method

At 30MHz the driver is much more stable with the following PLL settings:
PLL_CONTROL = 0x8a221e0c; /* 30 MHz = (48MHz/12*30) / 4 */
CLOCK_SOURCE = 0×40007777; /* source #1, #2, #3, #4: PLL (#4 active) */

Reading seems to be in general more reliable than writing of the cards.
The data throughput is a little worse than in the current implementation.
This is partly due to the data copying.
The sporadical ‘2bytes inserted’ problem with the USB file transfer is still
there. Interestingly @30MHz with the above settings, there is another problem:
sporadically ‘2bytes missing’ and ‘2bytes inserted’. Perhaps the DMA transfer
needs some more initialization for proper synchronization.

Here is a preliminary patch for TV out on a 5th generation iPod. Play a BMP file and TV out will activate. NTSC is the default. If the file has 576 lines, the output will be in PAL. The image stays until another is loaded or TV output is disabled via the debug menu..

The following formats ought to work:
720×480, 24 bpp for NTSC
720×576, 24 bpp for PAL
Many programs including Windows Paint and ImageMagick convert can write such files. Other resolutions and bit depths may work. For example WPS background screens display properly but other WPS bitmaps don’t.

Known issues:
- More work needs to be done to integrate this with Rockbox. No, you cannot view the Rockbox interface, JPEGs or mpegplayer output yet.
- When the LCD is updated, there is a temporary disturbance on TV output
- http://en.wikipedia.org/wiki/Macrovision#Analog_copy_prevention is enabled. Yes, the hardware can disable it, but I haven’t figured out how to do that yet.
- The original firmware probably outputs images differently. It can load programs into the BCM which perform decoding there, and that is probably faster.

Here’s a patch to have a functional usb_serial driver allowing the use of “Logf over Usb” debug function.

This patch will make an e200 present its SD card as an ipod mini 2G when queried by iTunes. It does this by changing a number of things:

1) Responding to SCSI inqueries
2) Using Ipod USB vid/pid and other usb details

The patch also enables logf for the usb_storage.c because I’m in a bit of a hurry.

To use this, make sure you have a partition on the SD card of type 0 (any size should do) and also the appropriate Ipod file structure (can be generated with e.g. gtkpod).

firmware/export/usb_ch9.h comes from linux (include/linux/usb/ch9.h) with only trivial changes. The original doesn’t mention a specific license, so it probably is GPLv2
file basically contains only structure declarations and defines for things straight from the USB specification though, so I’m not sure if there is a real problem.

I am running 3.4 on a 5.5G iPod modified with a 240gb drive. Rockbox is stock 3.4 with LBA48 added in and the max sector size turned off. The database was working ok on 3.3. Only issue was it took forever to add new files. After upgrading to 3.4 I noticed every time I powered on rockbox would lock up in the menus for up to 10 minutes before functioning normally. So I completely removed the .rockbox dir (including the database files of course) and re-expanded a fresh copy. I then tried to init the db. It runs until it is around ~44k files and 99% and then just sits there. If left alone it will eventually just turn it self off. When I turn it back on it will ask me to init the db again. I have seen it try to commit once or twice but it never takes. I am not really sure how to debug this at this point. Also in the debug disk info area, it things my drive is 131071MB. Under Rockbox Info it says 223GB which is better, but these two things are the same as in 3.3. All my Oggs are converted via a script I wrote from my flacs. I do not believe my flacs have any art, I am not even sure you can store art in a flac tag and even them I don’t think the ogg encoder is transferring them. I ran a tag dump (ogginfo) against my oggs and do not see anything to do with album art. I had 4 files on the device with album art. They were all in a directory with a database.ignore file. So they should not have been noticed. Just in case I removed that directory and rebuilt. It went though 44k files, commited 1-9 and then went back to “scanning” but the disk activity had stopped. Upon reboot it asked me to init the db again.

This is not a patched build. I simply changed the config to include large drive support. This is an issue that needs to be looked at. Please check into it, I will be happy to test any ideas.

This task is about the implementation of the MTP protocol for rockbox.

The code can be found in a github repository:
http://github.com/godeater/rockbox/tree/mtp The two main files are:
firmware/usbstack/usb_mtp.{c|h}
But there also are some other modification to be able to run it using the debug menu.

This is a very early patch to enable USB on the mini2440.

This patch let rockbox react on USB, but unfortunatly i dont get further then the first reset interrupt from USB. Something in the init has to be wrong, so i dont get ep0 interrupt which should follow the reset.

Because of this problems, no attempt has been made to implement the acutal data transfer functions.

If someone wants to step in and debug.. feel free !

if bookmark=ask is set and the mpeg is stopped, the user is asked for pressing select (for make bookark) or any key (for discard)
on apple devices: if the clickwheel is used for discarding, the bookmark is not set (as intended) but the clickwheel is not working anymore.
to get the clickwheel working again, the keyboard lock has to be set and unset and select has to be pressed.

Can't load Rockbox from my SDHC 32 GB A-Data Turbo Class 6.
Get “ATA mount File not found”. Cowon FW loads well.

This flyspray task will hold the development of a potential usb audio driver for rockbox.
It will also serve for the development of the isochronous transfer support support in usb code.

This patch modifies hardware registers for pclk & fclk in one instruction.

I’m currently testing it on Clipv2 to see if it gets rid of crashes

I've tried a dozen of builds around, and it seems that the new touchscreen on D2+ is not working properly - there're wild distortions (sometimes it's possible to press a button on lower bottom of the panel, but usually it's to no effect at all) at the edges of panel - i have to press almost on the edge of panel in order to tap the buttons, for instance in this (http://themes.rockbox.org/index.php?themeid=1146&target=cowond2) theme.

I've hunted this down here is what I found out.

from
http://developer.android.com/reference/android/view/KeyEvent.Callback.html

public abstract boolean onKeyDown (int keyCode, KeyEvent event)
Since: API Level 1

Called when a key down event has occurred. If you return true, you can first call KeyEvent.startTracking() to have the framework track the event through its onKeyUp(int, KeyEvent) and also call your onKeyLongPress(int, KeyEvent) if it occurs.

We need to return true and call KeyEvent.startTracking() from /android/src/org/rockbox/RockboxFramebuffer.java then set the interrupt flag from /firmware/target/hosted/button-android.c and find out what is passed back after a key release and handle that. I may not be a great programmer but this looks like the ticket to removing the BUTTON_REL work around from /firmware/target/hosted/android/app/button-application.c

Problem found in versions r29044-110113 to r29143-110126. I could not test 3.7.1, because it did not recognize my 16 GB Transcend flash card (fixed in above versions).

At the beginning of tracks and during rebuffering of longer tracks there is a short humming sound (like a bumblebee) mixed with a fast sequence of random high frequency tones. The sound differs as a function of data format and content. It is very homogeneous with WAV tracks (only humming) and different with lossy and lossless codecs. The same file encoded with FLAC and AAC leads to different short distortions. It is only audible for tracks with initial silence or very dynamic content, for example classical music with quiet passages or audio books. With sensitive headphones, this can be quite annoying.

The original firmware does not show this behavior!

It only happens while reading from the SD card, not from the internal storage.

Initially I thought this might be a CPU throttling issue. But now I think it might also be related to the controller driver.

There is a thread on Hydrogenaudio with independent confirmations of the issue:

http://www.hydrogenaudio.org/forums/index.php?showtopic=86306

If I can provide any additional information to help, please let me know.

[EDIT: Attached patch for experimenting with AS3543 settings.]

When playing back audio on a Sansa ClipV2 player, there is a regular background noise that’s audible with sensitive headphones and that’s quite annoying during quite music passages. The background noise is a hissing sound that repeats about 4 times per second. The noise can be heard when there is no disk activity and even at very low volume or when playback is muted. It stops as soon as audio is paused.

The noise is not present in the original firmware (OF).

This is a long-known issue, but hasn’t been formally tracked before. It is related to FS#11907, but different in that the background noise is present when there’s no disk (SD) activity. However, I did have the impression that disk activity intensifies the noise.

This item serves to collect the various approaches people have tried to eliminate the noise, and ideas for future exploration.

I ran a series of experiments on the assumption that the audio hardware is misconfigured is some way. I worked through various settings of the AS3543 component based on its datasheet. Here is what I have tried; but nothing helped to eliminate the noise:

* Higher-quality audio settings as proposed in  FS#11304  (AUDIOSET2_HPH_QUALITY_HIGH,
Disabled DAC gain control
Bypassed mixer and disabled mixer gain control (HPH_OUT_R_HP_OUT_DAC, AUDIOSET2_AGC_off,
Mute SDI data
Enable and control DAC attenuation
Disable common mode buffer (phantom ground)
Disabled various unused mixer components (AUDIOSET3_MICMIX_off, AUDIOSET3_ADCMIX_off,
Used external clock source for DAC
Enable headphone detection
Resetting all reserved audio registers to 0

[EDIT: I have attached a patch that allows experimenting with these settings by uncommenting the relevant source lines at compile time or extending the provided debug function to toggle the setting at run time.]

Possible next steps (suggested by various people on IRC):

* As the noise is not present on the other AMSv2 targets (Clip+, FuzeV2), a dump of the AS3543 settings (as3514_regs[] array) on these targets would be helpful. I have attached a patch that adds a debug-menu function for doing this (needs a logf build).

* Someone with a JTAG could read the AS3543 configuration set by the OF.

* The issue could be unrelated to the AS3543; it could be a power-management or frequency-scaling issue.

Also attached: A dump of as3514_regs[] (logf.txt; all values in
I’ve removed the patch to dump these settings; see a later comment in this task for a more up-to-date patch to do this.]

Other ideas?

r29445 introduced problems with screendump on sansa e200 and e200v2 (and possibly more). Screendump works properly with r29444.

Steps to reproduce:

1. delete or backup existing .rockbox directory
2. install r29445 (or later)
3. reboot
4. navigate to System → Debug (Keep Out!) → Screendump and press select to enable
5. attach USB cable to trigger screendump

On e200, this results in:
*PANIC*
Stkov usb (0)

on e200v2, this results in a deadlock - no keypad response - backlight & button light never timeout. Upon reboot, multiple dump files exist.

On e200v2 only, when dircache is disabled, screendump will function properly.

If I set my Gigabeat F20 touchpad sensitivity to High, the touchpad and all buttons stop working - except for the long POWER action which shuts down in the normal manner.

I then need to reset settings on boot (or connect to a PC and edit them) to restore usability.

If other owners could try this out, I'd be interested - it may be that I have a stuck button under the touchpad, of course.

This patch changes some of the settings of the AS3515 to highest audio quality, similar to  FS#11304  but for AMSv1.

AUDIOSET2_IBR_DAC_50 → AUDIOSET2_IBR_DAC_0

0% reduction (instead of 50%) of DAC bias. This will probably increase power consumption.

Not set AUDIOSET3_IBR_HPH.

Increases HP amp bias. Recommended by the data sheet for 16Ohm loads (and will probably reduce THD).

Would be great if these settings could be changed during audio playback to listen for any actual changes in quality :)

Can't set the time of day clock

started at SVN R29234 and continues to current build.
all the builds work in the simulators but break on player.
when you enter in the settings to set clock it shows correct date but shows

00:00:00

and you can change it but it will not set returns you to settings menu and you get

1. -:–:–

unknown

built fresh svn versions each time to confirm when it started

There is something wrong on my iPod Video 5.5 with ROCKBOX 3.9.1. Because I change my ipod's HDD to Samsung's 32G ssd as my rigid disk, I can not enter my rockbox system.
Rockbox boot
leader version v 4.0
ipod version )x000B0011
ATA-82
partition 1 : 0x0B 15598843 sectors
loading Rockbox … Error!
can t load rockbox, ipod:
file not found

Is there something wrong with my new SSD? Or it is just a bug with rockbox which can not support my SSD

USB is broken on mr500. I’ve tried r31467, but this has been the case since at least a few weeks ago.

Enabling logf in the relevant places causes rockbox not to boot, so wasn’t helpful.

Daily build: c413591-120705 and earlies.
When I connect powered down my Fuze V1 and disconnect from USB, it hangs displaying USB screen. I must hold power switch for several seconds to power off player. Tested on two different machines with windows7 x64. When I connect powered on player everything works perfectly.

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)

With my 5th generation iPod, if I connect USB while the hard drive is spinning, I often get full speed mode instead of high speed mode. This testing is with 00b8563, but I’ve observed the same problem in the past. Here’s the relevant part of Linux 3.8.0-21-generic dmesg output:

[26644.712035] usb 2-2: new high-speed USB device number 18 using ehci-pci
[26644.904471] usb 2-2: device descriptor read/all, error -71
[26644.965905] ehci-pci 0000:00:1d.7: port 2 reset error -110
[26644.967780] ehci-pci 0000:00:1d.7: port 2 reset error -110
[26644.968004] ehci-pci 0000:00:1d.7: port 2 reset error -110
[26644.971577] ehci-pci 0000:00:1d.7: port 2 reset error -110
[26644.973440] ehci-pci 0000:00:1d.7: port 2 reset error -110
[26644.973459] hub 2-0:1.0: hub_port_status failed (err = -32)
[26645.176048] hub 2-0:1.0: unable to enumerate USB device on port 2
[26645.428038] usb 6-2: new full-speed USB device number 8 using uhci_hcd
[26645.979070] usb 6-2: not running at top speed; connect to a high speed hub
[26646.009069] usb 6-2: New USB device found, idVendor=05ac, idProduct=1209
[26646.009076] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[26646.009080] usb 6-2: Product: Rockbox media player
[26646.009083] usb 6-2: Manufacturer: Rockbox.org
[26646.009087] usb 6-2: SerialNumber: 100000000000A270014B32BEB
[26646.024242] scsi21 : usb-storage 6-2:1.0
[26647.038109] scsi 21:0:0:0: Direct-Access TOSHIBA MK3008GAL BU11 PQ: 0 ANSI: 4
(I’ve removed the remaining USB storage messages because they don’t seem relevant)

If the hard drive is not spinning, I get high speed mode. However, there is a disconnect and the device is detected twice:

[27356.784126] usb 6-2: USB disconnect, device number 9
[27371.208044] usb 2-2: new high-speed USB device number 24 using ehci-pci
[27371.347053] usb 2-2: New USB device found, idVendor=05ac, idProduct=1209
[27371.347058] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27371.347062] usb 2-2: Product: Rockbox media player
[27371.347065] usb 2-2: Manufacturer: Rockbox.org
[27371.347069] usb 2-2: SerialNumber: 100000000000A270014B32BEB
[27373.079038] scsi25 : usb-storage 2-2:1.0
[27373.337244] usb 2-2: USB disconnect, device number 24
[27373.640029] usb 2-2: new high-speed USB device number 25 using ehci-pci
[27373.779220] usb 2-2: New USB device found, idVendor=05ac, idProduct=1209
[27373.779226] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27373.779229] usb 2-2: Product: Rockbox media player
[27373.779233] usb 2-2: Manufacturer: Rockbox.org
[27373.779236] usb 2-2: SerialNumber: 100000000000A270014B32BEB
[27373.820382] scsi26 : usb-storage 2-2:1.0
[27374.823266] scsi 26:0:0:0: Direct-Access TOSHIBA MK3008GAL BU11 PQ: 0 ANSI: 4
(Again, I’ve removed the remaining USB storage messages because they don’t seem relevant)

I get the same behaviour regarding high speed vs. full speed mode in Windows 7, but I’m not aware of Windows reporting other USB errors anywhere.

I was sometimes having USB difficulties that seemed to be due to contact oxidization or dust from not using the dock connector in a long time, but I don’t think that’s the cause here.

I’m attaching USB traces from WireShark using Linux usbmon. In both cases I removed all the USB mass storage stuff after get max lun because it seems irrelevant and increases file size a lot. When the result is full speed, something goes wrong after the set address response. When the result is high speed, something goes wrong after the set configuration request. In both cases the first sign of trouble is an interrupt from the USB hub.

This is on a Gigabyte GA-P35-DS3R rev V1.0 motherboard with Intel P35 + ICH9R chipset.

I have an upgraded iPod 5.5 with CF 32Gb installed in CF-ZIF adapter.
Both iTunes & Rockbox are working fine with this setup.

Then I tried to increase the storage space by using mSata SSD 64 GB + mSata-ZIF adapter. iTunes recovered the iPod successfully and it is working just fine. I installed Rockbox latest stable (non-stable latest = same thing) version & after the Rockbox boot-up it reporting an ATA error -11.

I wonder if this can be solved.

Thanks!

I use a 64 GB MicroSD card in my Clip Zip and the stock firmware recognizes it. Rockbox recognizes it in the debug disk info screen and when connected to a computer via USB, I can read and write it through rockbox. However, when I try to access it or when I just check the regular rockbox info, rockbox does not show the SD card, nor can I play music from it.

The bug is also present in the current development version and is overall very similar to this one: https://www.rockbox.org/tracker/11798

I tried reinstalling rockbox and reformatting the SD card, but nothing worked.

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

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

What are your thoughts on this?

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

Hi there,

first of all: this is my first contribution to rockbox and I tried my best to make myself familiar with the way things work there. I am sure, not everything is where it belongs. Please help me to get things in order :).

second: thanks to the author of Patch  FS#1803  that made this possible.

The purpose of this patch is to watch the tuner reported field strength (estimate) and mute, when it drops below a customizable threshold. Wether muting or not as well as the threshold are customizable in the fm tuner menu. It should not interfere with manual muting and should not affect recording (i didn’t test that yet). THe threshold is specified in pseudo-dBuV.
It also adjusts frequency display to display as MMM.KKK instead of MMM.KK. This is for people who adjust region settings and channel widths.

My testing conditions were limited to the sansa c250.  FS#1803  reports to work on the tuner chips LV24020LP (e.g. sansa c250) and TEA5767. I only tested the first. Please report back possible field strength values you see on devices using these chips.

This code should not break anything. I did a testbuild for some iPods (without tuner) that compiled cleanly. Simulator also works.

Currently only english and german translation are done.

User guide:
This patch conditionally adds 1 or 2 lines to the tuner main window that look like this:

Sig: [-M] -235dBuV
Automute below -555dBuV

The second line is only displayed if automute is enabled. The first line shows the status of the tuner. The 2 characters in the braces exlain as [ab]:

a: either 'O' or '-' 
   'O': current field strength is above threshold
   '-': current field strength is equal to or below threshold
b: either 'M' or '-'
   'M': will mute on or below threshold
   '-': automute disabled.
(both are only updated on field strength change)

The second line should be selfexplaining, same for the menu entries.

Request for comments!

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

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

Thanks.

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.

I installed release 3.3 on my Sansa e260. 3.2 worked. On 3.3, volume controls work fine in normal playback mode, but when I switch to FM Radio, they are ignored. If I switch back to normal playback mode, I can set the volume level again, just not while listening to the radio.

The FM Tuner appears to be very sensitive to noise and static compared to the original firmware radio.

Apart from the static and noise the Rockbox FM Tuner sounds much clearer and sharper than the original firmware, so I wonder if this may be related to the OF using a lower sampling rate or cutting off the higher frequencies to reduce noise.

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

–

ONDA VX777
While in FM-Radio it isn’t possible to change the volume value, nor from the context menu, nor from the virtual 3×3 touch screen grid and nor from the .fms %T tag in absolute mode.

when the FM tuner is turned on and say that you want to go to Add a Preset you cannot hear thevoice over the radio. this should be controlled where the Fm volume is turned down and the volume of the voice is turned up just like in playing regular music.

While in the fm radio screen, a ticking noise can be heard in the background. When pressing the power button in the radio screen the noise disappears.

Player: iPod Video 5th Gen. (5.5)
Rockbox Release v. 3.9 downloaded/installed 06/28/2011

Accessory: Griffin iFM Radio Receiver for iPhone and iPod - has a doc connector, short cable to a "dongle" which is the FM tuner, with earphone jack on the dongle. No batteries or other power source.

Here's a link to the product's Amazon page:
http://www.amazon.com/gp/product/B003ERT46W

Booting into Apple firmware
1. Turned player on with nothing plugged in, the "Radio" menu item does not show up. Plugged in the Griffin iFM, the "Radio" menu item shows up, and when I select it, I get the FM frequency and dial, I can tune it, it works. I did not have to download anything at all from the Apple iTunes store.

2. Turned player on with iFM plugged in - the "Radio" menu item shows up, and from there it all works as above.

Booting into Rockbox OS 1. Turned player on with nothing plugged in, then plugged the iFM on the dock connector, the "FM Radio" item never shows up.

2. Turned player on with iFM plugged in, still no "FM Radio" on the menu.

3. Went into System then Debug then FM Radio - got message: "HW Detected: no"

So Rockbox does not detect it at all. And there's no sense expecting that any Apple/iTunes software would do anything under Rockbox.

What's interesting is, that with the player off (under both Apple and Rockbox OS), if I only plug in the Griffin iFM to the dock connector, and do nothing else, the player turns on. So there must be some kind of hardware detection there.

Actual behavior:

1. FM Tuner option never shows up on main menu (whether powering up with FM Tuner plugged in, or plugging in after power up).

2. When player is OFF, connecting the FM Tuner to the dock port turns on the player.

3. In System/Debug/FM Tuner, "HW Detected" is always "no"

Expected behavior:
1. Expected the FM Tuner option to be available on the main menu (at least when booting with the accessory plugged in to the dock port) as described in the manual.

2. Expecting to be able to tune in to FM stations and play at least through the tuner's headphones connector, if not through the player's headphones connector. Other features (displaying song information, presets, etc.) are secondary (to me).

Device: Sansa Fuze v2 (stable port)
Rockbox Release: 3.12

Recently I have been noticing a problem with themes that allow radio station logos to be displayed on the FMS screen. This is most noticeable with the analog and Fuzemod themes. While the logo displays properly, other images on the screen do not. In the case of the analog theme, the VU meter appears corrupted and with the Fuzemod theme the battery animation, tuning bar slider and playmode indicator icons fail to appear as expected. This problem was not present when either of these themes was used with the releases before version 3.12. In fact this bug appears to have been introduced by one of the experimental daily development builds either in May or June. I have tried different sets of radio station logos and preset lists with these themes but I always get the same result when using version 3.12; everything is fine with any previous release. Since this problem occurs with two different themes along with any combination of radio station logos and preset lists, I can only conclude that it originates with the firmware.

I have attached to this report three generic radio station logos in bitmap format along with a generic preset list. You can put these into /.rockbox/fmpresets and try your own tests. Since the frequencies were selected at random, don’t expect them to tune in anything. Besides, there is nothing wrong with the ability of the Rockbox firmware to tune in radio stations or play their music. The problem starts as soon as the user starts flipping through the station presets, so don’t be shy about changing the station frequently during your tests. I also find that in order to accurately reproduce this problem the Sansa Fuze v2 should be powered off then on again whenever a new theme or preset list is loaded.

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.

Heyup,

I’ve recently updated the build on my zip and the radio volume is greatly reduced. It`s very noticeable since I use a passive speaker connected straight to the player (top volume required). Volume of file playback is unaffected.

Here’s someone describing the same issue-
http://www.anythingbutipod.com/forum/showthread.php?t=74910

Same symptoms including (notably) normal volume in the recording screen (gain=0), and region settings make no difference.

I have no note of which build I had before the update but it was from around the end of 2014. Looking thru the changelog yielded no clues.

trunk 983c808-150717

I have an iPod 4G Grayscale (model A1059) running Rockbox 3.14 with an Apple FM remote (model A1187). The remote part works ok (Play/Select and Fwd/Rev buttons work - volume control is separate due to it being connected to the line out, but works).

However, the radio menu does not show up in the main menu when connected. Not when I boot with the remote connected, not when I connect it after booting, and not if I go to a different menu and then back.

In the debugging menu, it simply says that the FM tuner hardware is not found.

I am sure that this used to work at some point. Are there known regressions?

I created the following fonts from DejaVuSans.ttf using ttf2bdf.

I use them as an alternative for unifont, which is fixed-width.

Attached are a screenshot and a tarball with 8 to 12pt versions of the font.
Perhaps they could be included in the official distribution, if others like them.

This font is part of the WenQuanYi Project at [1]. It’s in Chinese, but there’s an english page at [2].

I’m adding this font because:
1. Currently there is no good Chinese font for Rockbox.
2. The best Chinese font (unifont) has unevenly sized Chinese characters, while this font has uniformly sized Chinese characters.

The attachments contain screenshots of the simulator, to show how this font would look like on the iPod Nano. I’ve also attached a screenshot using the Unifont font to show the uneven sizes of Chinese characters, for comparison. I don’t know about other languages, but I’d think other CJK languages work better in this font as well, due to the merging of WenQuanYi Bitmap Song.

According to the project[3], this font is made by combining the GNU Unifont (GPL), WenQuanYi Bitmap Song (GPL) and Fixed-16×8 (Public Domain) fonts. The maintainer of GNU Unifont also acknowledges this fact at [4].

This font is licensed under the GPLv2 with a font embedding exception[3]:

[quote]
** GPL v2 license with font embedding exception:

As a special exception, if you create a document which uses this
font, and embed this font or unaltered portions of this font into
the document, this font does not by itself cause the resulting
document to be covered by the GNU General Public License. This
exception does not however invalidate any other reasons why the
document might be covered by the GNU General Public License. If you
modify this font, you may extend this exception to your version of
the font, but you are not obligated to do so. If you do not wish to
do so, delete this exception statement from your version.
[/quote]

I don’t mind either way, but it would be up to Rockbox developers whether to strip off this exception. And either way, the font is compatible with Rockbox’s license (GPLv2).

The font I’m attaching is a modified version (and only the bdf); you can download the original version from [5]. My modification is:

— wqy-unibit.bdf.orig 2008-06-01 04:47:36.839752214 +0800
+++ wqy-unibit.bdf 2008-06-01 05:01:51.031748178 +0800
@@ -64,7 +64,7 @@
CHARSET_ENCODING “-1” CHARSET_COLLECTIONS “ASCII ISO8859-5 GB2312.1980 BIG5-0 KSC5601.1989-0 JISX0208.1997 ISO10646-1” ENDPROPERTIES
-CHARS 46443
+CHARS 46444
STARTCHAR uni0000
ENCODING 0
SWIDTH 500 0

This is because convbdf will emit a warning “Warning: DWIDTH spec > max FONTBOUNDINGBOX” when converting the font. This is because there are actually 46444 STARTCHAR entries, but only 46443 glyphs – the character “mu” is encoded as 181 and 956, with the exact same glyph. The generated .fnt file is exactly the same with or without my modification.

Additionally, this font is quite big so it’s a bit big on the screen of the iPod Nano. But it would be great on larger screens. Please take a look at the screenshots in the attachments.

Links:
[1] http://www.wenq.org/ [2] http://wqy.sourceforge.net/cgi-bin/enindex.cgi [3] http://www.wenq.org/index.cgi?Unibit_README [4] http://www.unifoundry.com/unifont.html [5] http://downloads.sourceforge.net/wqy/wqy-unibit-bdf-1.1.0-1.tar.gz?use_mirror=osdn