Rockbox on HiFi Walker H2

[psyscott]

I have tried to install Rockbox on the H2 and I am getting it to apparently boot into Rockbox but I can't boot back into the native firmware. When I do boot into Rockbox, the font size is barely large enough for me read WITH glasses, but I don't see any settings so I don't know how to change the font size of the display. Also, I'm not sure if I've installed it correctly because I'm not able to do a dual boot and boot into the original firmware. Any help would be appreciated.

[dconrad]

When you boot it up, does it go directly into Rockbox within about 3 seconds, or does it show the brand logo first, then bring up a menu which you need to select Rockbox from?

Font size can be changed by going to Settings --> Theme Settings --> Font. The numbers before each font are the size, so bigger numbers means bigger font.

[psyscott]

I can get into the settings as you described. When I selected Font, I got this error message:
Segmentation fault at 00479(something... can't read it)
address 0xc
rockbox.erosq(rb_back trace+0x44) [ox482c4]
Thank you for replying.

[psyscott]

Tried it again and got the same error when I selected Font. I can barely read it even with reading glasses so I really need that font size changed.
Thanks.

[psyscott]

As much as I know about error and versions when I try to select fonts

14

906

address
rockbox erosq (rb_back trace+0x44) [0x4862c41

rockbox-aigoerosq-20250610
EROSQ-v18-patched.upt
Device HIFI Walker H2
Also doing DLs and copies to card (formatted Fat32) on a Mac

[dconrad]

We'll get it so that the font is larger, but we have to figure out why it's crashing like that first. Iif it's crashing like that, something is clearly wrong. I would guess that something is wrong with your SD card, like corruption or such.

Is this the SD card that came with the device? Or what's the history of this card? If you have another card that you trust, I would try that by downloading rockbox-aigoerosq-*.zip again and extracting it to that card.

I would also use one of the flash checker tools to see if you can find that it is a bad card or not. The SD cards that come with these devices are notoriously low quality and you might be experiencing corruption. Please see Bilgus' post here: https://forums.rockbox.org/index.php/topic,55193.0.html

Based on the.upt file you used, you should be able to use the original firmware by scrolling through the first menu it comes to, with the large square icon that just says "Rockbox". That's the bootloader menu, I believe the original firmware option is called "Aigo Player". Click Play/select on that and it should boot into the original firmware.

[psyscott]

No, not a card that came with anything. Sandisisk picture attached. I vaguely recall that ROCKBOX IS pretty limited about cards, but don't recall how. Guess I'll just buy a different card & start over.

[dconrad]

Gotcha. Did you look at Bilgus' post that I linked to? With one of those tools you should be able to identify if your SD card is OK or not before buying a new one.

You're sort of correct in remembering that rockbox is picky about SD cards - it lives on the SD card, so is not tolerant of data corruption.

As an aside, the "Native" devices (this, fortunately does not apply to your player!) also do not support the exFAT filesystem, only regular FAT.

For what it's worth, that branding on the card looks off somehow to me, but I can't claim to be an expert on counterfeit sandisk cards either.

[psyscott]

OK. I did as suggested,bought a new card, started over. reinstalled, booted Rockbox, went to settings and to fonts, and exactly the same  thing occurred. Yes, there is something very wrong, but it is NOT the card! What else but a BUG? Suggestions now?

[psyscott]

Sansa 128 is probably not a counterfeit but the picture is probably a little wonky and that's what you're thinking makes it look like a counterfeit. The new card is also a Sansa, a 64mb, and I did format it fat32. Should I try a different build? Another card. Does Rockbox have a favorite brand of storage?

[dconrad]

Ok, hmm. I was sure that was it. Can you use any other features in rockbox? Can you browse the file tree without crashing? Play a file?

I'm looking at the rockbox zip file now and I notice that it does not have a .roxkbox/fonts folder... I wonder if this is a bug if no fonts have been installed. I was under the impression that it came with at least a few fonts but perhaps not.

You could try adding the fonts so that there are actually some fonts to browse. Unzip this folder onto the root of your drive: https://download.rockbox.org/daily/fonts/rockbox-fonts-20250612.zip

I'm terribly sorry I made you go out and get a new SD card when it seems that wasn't the issue! I was so sure of it.

[dconrad]

I just tried it and I can indeed reproduce the issue on my player. All I needed to do was to remove the .rockbox/fonts folder and attempt to browse fonts, and then a crash. Even an empty fonts directory prevents the crash.

Again, I'm sorry I doubted!

[dconrad]

bug report: https://www.rockbox.org/tracker/task/13636

(the workaround being to also install the fonts pack at installation time)

[speachy]

I'm looking at the rockbox zip file now and I notice that it does not have a .roxkbox/fonts folder... I wonder if this is a bug if no fonts have been installed. I was under the impression that it came with at least a few fonts but perhaps not.

* The 4.0 erosqnative release zip includes .rockbox/fonts/15-Adobe-Helvetica.fnt
 * The latest daily build zip (20250612) also includes the same font
 * A fresh build on my workstation produces a zip with the same font

There doesn't seem to be anything wrong with our build scripts and download infrastructure.

EDIT:  Missed that this was for the _hosted_ aigoerosq build.  That is indeed missing a font in the download zip.

[speachy]

The missing font and some related default theme issues has now been fixed, and will show up in the 20250613 nightly builds.

If you can't wait that long, you can grab the bleeding-edge dev build from:   https://build.rockbox.org/data/rockbox-aigoerosq.zip

The _crash_ is still unaddressed at this time, but at least it will require active malfeasance to trigger.