Recent Posts
91
Rockbox General Discussion / An Ode to rockbox...
« Last post by Multiplex on June 03, 2025, 08:36:48 AM »Not been here for a while (Years) but I just tripped over "an Ode to Rockbox" on youtube
https://www.youtube.com/watch?v=Qw-VvGsYpSU
I searched here for the video ID and the youtuber (mitxela) but didn't get any hits so even though it's 4 years old it may be news to folk here.
I'm not a user any more, I have the luxury of not working in an office any more so can use Lyrion https://lyrion.org/on my squeezebox players - it's a pretty similar vibe to the heyday here, but my nephew is Rocking my old Sansa player as he's not allowed a phone at his work :-)
https://www.youtube.com/watch?v=Qw-VvGsYpSU
I searched here for the video ID and the youtuber (mitxela) but didn't get any hits so even though it's 4 years old it may be news to folk here.
I'm not a user any more, I have the luxury of not working in an office any more so can use Lyrion https://lyrion.org/on my squeezebox players - it's a pretty similar vibe to the heyday here, but my nephew is Rocking my old Sansa player as he's not allowed a phone at his work :-)
92
Theming and Appearance Customization / Re: Need to Remove Messed up Themes
« Last post by delta on June 03, 2025, 12:57:25 AM »I did it again... im reeeeallly sorry. This time its onebitmono2.https://themes.rockbox.org/index.php?themeid=3781&target=ipod6g
93
Plugins/Viewers / Re: fopen file in .rockbox dir
« Last post by rockbox_dev123 on June 02, 2025, 09:35:05 PM »I managed to finish my plugin. It's a port of display-dhammapada with an updated translation courtesy of the BPS. It's not in a state to be upstreamed so I'm uploading it here instead for anyone interested.
The plugin selects a random set of verses and displays them verse by verse using simple_viewer.c. On an iPod Classic I can press skip backwards, menu or select to advance the verses until the end of the range.
I have the plugin set to run on startup now and it works well.
Place dhammapada-english-bps.txt into .rockbox/dhammapada/dhammapada-english-bps.txt then you can compile dhammapada.c like you would any other C plugin. Docs here.
The plugin selects a random set of verses and displays them verse by verse using simple_viewer.c. On an iPod Classic I can press skip backwards, menu or select to advance the verses until the end of the range.
I have the plugin set to run on startup now and it works well.
Quote
display-dhammapada was originally written by Richard Cepas <rch@online.lt> and later updated by bodhi.zazen <bodhizazen at fedoraproject dot org> and paultag <paultag at ubuntu.com>
Place dhammapada-english-bps.txt into .rockbox/dhammapada/dhammapada-english-bps.txt then you can compile dhammapada.c like you would any other C plugin. Docs here.
94
Theming and Appearance Customization / Re: themes with font support for both arabic and english other than stock?
« Last post by speachy on June 02, 2025, 08:30:55 PM »i tried so many different themes and changed a lot of settings trying to make the once i like work with arabic letters but i had no luck i would appreciate any help if someone else found a theme or figured a way to make them work by changing some settings
-AIGO EROS Q / K (HIFI WALKER H2)
Most themes with custom fonts don't include coverage beyond the Latin-derived scripts.
This page shows the language coverage of the fonts that Rockbox distributes as part of its full font bundle:
https://translate.rockbox.org/whichfont.php
According to that, only four of our fonts have full Arabic coverage; perhaps you could alter a theme you like to use one of these fonts instead?
(BTW, our Arabic translation is _very_ incomplete; if you are so inclined any update/contribution would be very welcome)
95
Theming and Appearance Customization / themes with font support for both arabic and english other than stock?
« Last post by seafantm on June 02, 2025, 07:50:19 PM »i tried so many different themes and changed a lot of settings trying to make the once i like work with arabic letters but i had no luck i would appreciate any help if someone else found a theme or figured a way to make them work by changing some settings
-AIGO EROS Q / K (HIFI WALKER H2)
-AIGO EROS Q / K (HIFI WALKER H2)
96
New Ports / Re: Need help compiling rockbox using devkitARM toolchain.
« Last post by gama on June 02, 2025, 06:09:30 PM »[UPDATE]
I have been able to compile and run rockbox on the N3DS.
But currently I cannot test any codec since libctru does not have a dirfd implementation.
I have been able to compile and run rockbox on the N3DS.
But currently I cannot test any codec since libctru does not have a dirfd implementation.
97
Iriver - Installation/Removal/Flashing / Re: iHP 120 on Rockbox 4.0 / how to permanently get flash and ROLO right
« Last post by DTSyX on June 02, 2025, 05:12:26 PM »Having done the update myself with a H140 today, I can share some experiences from that task.
- I used Rockbox Utility for patching the original h120.hex file (again). If you want to patch it yourself, make sure you use the fwpatcher from 2020 (https://download.rockbox.org/bootloader/iriver/8.0/fwpatcher.exe)! The one in the base directory (which the link you posted points to) is from 2006 and (according to this site https://www.rockbox.org/wiki/IriverBoot.html#TODO_list_for_the_upcoming_bootloader_revision) makes the hex file "suitable" for bootloader v6 and probably not working with bootloader v8, if my interpretation is correct.
- https://www.rockbox.org/wiki/IriverFlashing provides a good manual on how to flash the firmware but also especially the bootloader.
- Esp. before flashing RAM/ROM for the first time, make sure you make a ROM dump first to have a backup to be able to go back to the original ROM if necessary.
- For the update (of the the firmware), boot from disk, not from RAM or ROM!
- Set the file view to "all" to be able to see the .rockbox directory in the rockbox "file manager".
- Before flashing RAM or ROM, update the bootloader. In fact, you could update the bootloader before even updating the firmware, I guess, to be sure. But I don't actually know if older firmware versions can handle the latest bootloader, but I would assume that there should be no problem given that the bootloader boots the firmware not the other way around.
- For updating the bootloader, put the bootloader.iriver file (v8) into the .rockbox directory of your H120/H140, unplug the device and navigate to "files -> ,rockbox", in that directory, navigate to bootloader.iriver to "mark" that file -> long press the navigation button -> select "open with..." -> select "iriver_flash" (probably selected by default) -> press navigation button straight down or to the right -> if everything is ok there should be a popup asking to proceed by pressing the play button. If you're sure, press the play button (but that might also brick your device according to the link above!) -> let the flash process do its thing (4 steps iirc). Done.
You can see which bootloader is installed at the boot menu (which you can force if you active the "Hold" slider to interrupt the boot process. The bootloader version is displayed at the top of the screen.
- Maybe it's a good idea to reboot (from disk), iirc, to have the new bootloader being used for starting the system for the flashing of RAM and ROM.
- Flashing RAM requires to do RoLo of the the rockbox.iriver file first = selecting the file and short-pressing (or clicking to the right) on that file. That step is not necessary (or even possible?) for the ROM file (rombox.iriver). After having done the RoLo thing and the system "restarted" in v4.0, do the flashing thing: long-pressing the Navigation button - just as described for the bootloader update above.
- Flashing ROM: Do the second step just described for RAM.
This should conclude your update of the firmware, RAM, ROM and bootloader of your H120/H140 device.
I hope my memory didn't make too many / any big mistakes!
I, too, had some problems when updating, like getting "incompatible bootloader" when trying to flash RAM / ROM. But I think that was because I hadn't yet updated the bootloader from v7pre4 to v8.
Unless RAM/ROM are flashed they are still on the previous version and try to boot that. It booted "fine" for 3.15, but as v4.0 was installed, e.g. some entries in settings and other menu entries were missing - and others were not making much sense. Only after flashing RAM and ROM would both boot v4.0 without any issue or manual tricks.
Also, this is done on a H140 with ssd, so no original hdd needed (unless one would need a ROM dump and had no backup elsewhere - but I didn't need that at any point of the update procedures to Rockbox v4.0 / bootloader v8).
Also: I, too, read that manual entry where there should be some magic menu before booting when pressing the navigation button at start. I guess that's outdated or not applicable for iriver. Therefore it's confusing. Just ignore it. Same for the Firmware upgrade, which might only be applicable if you boot the original firmware when doing the "Rockbox install" for the first time.
- I used Rockbox Utility for patching the original h120.hex file (again). If you want to patch it yourself, make sure you use the fwpatcher from 2020 (https://download.rockbox.org/bootloader/iriver/8.0/fwpatcher.exe)! The one in the base directory (which the link you posted points to) is from 2006 and (according to this site https://www.rockbox.org/wiki/IriverBoot.html#TODO_list_for_the_upcoming_bootloader_revision) makes the hex file "suitable" for bootloader v6 and probably not working with bootloader v8, if my interpretation is correct.
- https://www.rockbox.org/wiki/IriverFlashing provides a good manual on how to flash the firmware but also especially the bootloader.
- Esp. before flashing RAM/ROM for the first time, make sure you make a ROM dump first to have a backup to be able to go back to the original ROM if necessary.
- For the update (of the the firmware), boot from disk, not from RAM or ROM!
- Set the file view to "all" to be able to see the .rockbox directory in the rockbox "file manager".
- Before flashing RAM or ROM, update the bootloader. In fact, you could update the bootloader before even updating the firmware, I guess, to be sure. But I don't actually know if older firmware versions can handle the latest bootloader, but I would assume that there should be no problem given that the bootloader boots the firmware not the other way around.
- For updating the bootloader, put the bootloader.iriver file (v8) into the .rockbox directory of your H120/H140, unplug the device and navigate to "files -> ,rockbox", in that directory, navigate to bootloader.iriver to "mark" that file -> long press the navigation button -> select "open with..." -> select "iriver_flash" (probably selected by default) -> press navigation button straight down or to the right -> if everything is ok there should be a popup asking to proceed by pressing the play button. If you're sure, press the play button (but that might also brick your device according to the link above!) -> let the flash process do its thing (4 steps iirc). Done.
You can see which bootloader is installed at the boot menu (which you can force if you active the "Hold" slider to interrupt the boot process. The bootloader version is displayed at the top of the screen.
- Maybe it's a good idea to reboot (from disk), iirc, to have the new bootloader being used for starting the system for the flashing of RAM and ROM.
- Flashing RAM requires to do RoLo of the the rockbox.iriver file first = selecting the file and short-pressing (or clicking to the right) on that file. That step is not necessary (or even possible?) for the ROM file (rombox.iriver). After having done the RoLo thing and the system "restarted" in v4.0, do the flashing thing: long-pressing the Navigation button - just as described for the bootloader update above.
- Flashing ROM: Do the second step just described for RAM.
This should conclude your update of the firmware, RAM, ROM and bootloader of your H120/H140 device.
I hope my memory didn't make too many / any big mistakes!
I, too, had some problems when updating, like getting "incompatible bootloader" when trying to flash RAM / ROM. But I think that was because I hadn't yet updated the bootloader from v7pre4 to v8.
Unless RAM/ROM are flashed they are still on the previous version and try to boot that. It booted "fine" for 3.15, but as v4.0 was installed, e.g. some entries in settings and other menu entries were missing - and others were not making much sense. Only after flashing RAM and ROM would both boot v4.0 without any issue or manual tricks.
Also, this is done on a H140 with ssd, so no original hdd needed (unless one would need a ROM dump and had no backup elsewhere - but I didn't need that at any point of the update procedures to Rockbox v4.0 / bootloader v8).
Also: I, too, read that manual entry where there should be some magic menu before booting when pressing the navigation button at start. I guess that's outdated or not applicable for iriver. Therefore it's confusing. Just ignore it. Same for the Firmware upgrade, which might only be applicable if you boot the original firmware when doing the "Rockbox install" for the first time.
98
Announcements / Re: Rockbox 4.0 released!
« Last post by DTSyX on June 02, 2025, 04:05:24 PM »Great news!
Thank you very much!
I was a bit skeptical at first due to the release date / date of announcement tbh, though, if there really was a new Rockbox version available at last... :-)
Thank you very much!
I was a bit skeptical at first due to the release date / date of announcement tbh, though, if there really was a new Rockbox version available at last... :-)
99
Rockbox Utility / What does "Update Iriver H100 / H300 series bootloader." in the changelog mean?
« Last post by DTSyX on June 02, 2025, 03:56:24 PM »I just found out about the new Rockbox release and the new Rockbox Utility today by chance.
Checking the changelog, I noticed "Update Iriver H100 / H300 series bootloader." as one of the changes in v1.5.0 of the Rockbox Utility.
Checking the box in the Rockbox Utility when installing the new Rockbox release thinking that would update the bootloader, I realized that this wasn't the case. A (new) h120.hex file was created, in order to actually update the bootloader from v7pre4 I had to manually download the latest one (v8), place the bootloader.iriver file into the .rockbox directory and flash it to the device - a task I assumed the Rockbox Utility (v1.5.1) would do judging from the changelog.
So, I'm wondering what that line in the changelog actually means in regards to the Rockbox Utility - and also, what version of the bootloader is meant by this.
Checking the changelog, I noticed "Update Iriver H100 / H300 series bootloader." as one of the changes in v1.5.0 of the Rockbox Utility.
Checking the box in the Rockbox Utility when installing the new Rockbox release thinking that would update the bootloader, I realized that this wasn't the case. A (new) h120.hex file was created, in order to actually update the bootloader from v7pre4 I had to manually download the latest one (v8), place the bootloader.iriver file into the .rockbox directory and flash it to the device - a task I assumed the Rockbox Utility (v1.5.1) would do judging from the changelog.
So, I'm wondering what that line in the changelog actually means in regards to the Rockbox Utility - and also, what version of the bootloader is meant by this.
100
Hardware / Re: HiBy R1
« Last post by 7o9 on June 02, 2025, 01:56:16 PM »Yes, sorry, you need to supply the name of the file to the extract script.
The rebuild script runs without errors on current (native) Ubuntu and the firmware updater seems to accept it but refuses to succesfully flash the player. The exact same script oddly generates a working firmware update when I try to run it on Ubuntu on WSL2. It must be related to the versions or the (default) parameters of genisoimage or mksquashfs. I cannot explain it.
In an attempt to create a patch file against the current Rockbox source the inspiration struck to fix an old issue: Finally the bootloader icons have the correct colors (I was calling the bmp2rb with the wrong parameter for the lcd bit depth setting I configured). Unfortunately the icons are still rotated 90 degrees. The Rockbox logo when booting is still garbled.
Attached is my attempt at a patch file. Most of it was borrowed from other hosted targets, specifically the recent Surfans F28 addition. There are some files in there that are not actually used (mostly audio related, which is disabled anyway).
I can provide the patched firmware update file if someone can host it somewhere.
The rebuild script runs without errors on current (native) Ubuntu and the firmware updater seems to accept it but refuses to succesfully flash the player. The exact same script oddly generates a working firmware update when I try to run it on Ubuntu on WSL2. It must be related to the versions or the (default) parameters of genisoimage or mksquashfs. I cannot explain it.
In an attempt to create a patch file against the current Rockbox source the inspiration struck to fix an old issue: Finally the bootloader icons have the correct colors (I was calling the bmp2rb with the wrong parameter for the lcd bit depth setting I configured). Unfortunately the icons are still rotated 90 degrees. The Rockbox logo when booting is still garbled.
Attached is my attempt at a patch file. Most of it was borrowed from other hosted targets, specifically the recent Surfans F28 addition. There are some files in there that are not actually used (mostly audio related, which is disabled anyway).
I can provide the patched firmware update file if someone can host it somewhere.