FS#8144 - FM Tuner doesn't work on iRiver H10
Although it was recently implimented into Rockbox, the FM Tuner does not work on my iRiver H10 20gb.
There is no reception, and when I go to scan for channels, it gets half-way through and then the iRiver freezes. I then have to do a hard reset of the device in order to make the device functional again.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
My friend have experienced the issue too.
You could try to mannually search for a channel. It should give you proper reception.
Try to edit ./rockbox/fmpresets/preset01.fmr You can find there a list of radio channels in a format:
<frequency in Hz>:<channel name> for example:
99900000:Trojka
This adds radio channel called "Trojka" which frequency is 99,9MHz.
Enter all channels that you can recieve, load preset (long hold "o" button in radio mode). After that select a station from the list. If all you can hear is noise press "left" button to change mode from preset to search and using FF/REW mannually change frequency a bit to "catch" proper reception. Once you catch it you would be able to enter preset mode again and choose one from among your channels which recieve properly.
In case of my friend it helped. Radio channel frequency was shifted 0,1-0,3MHz. Mannual change of a frequency helped to catch reception, and then he was able to use preset frequency values.
Hope this helps.
well i applied a field strength (shows signal strength) patch to my builds, n figured this out, when i tuned into a frequency with 9dBvf or so it hangs, do try it out, otherwise above that value all frequencies work well
Try to apply a patch from
FS#8238it may help you.Is this still an issue with a current build?
No. It was fixed by
FS#8238. I think this task should be closed now.