AIGO EROS Q / AIGO EROS K / IRULU Surfans F20 / AGPTek H3 / HIFI WALKER H2

[dconrad]

Were there any folks in here with the native port installed on their players? If someone wants to test out a new bootloader which supports booting into the OF it would be helpful.

Basically I just need someone to use jztool to load up this bootloader build and see if the Aigo Player option works. There's no need to actually install it on your player unless you really want to.

It works really well on my player, but I don't know for sure that it will work on others so it's probably good to test.

It corresponds to change #4394 on gerrit.

[amachronic]

By the way, I've added installation instructions for the Eros Q native port to the Rockbox wiki: https://www.rockbox.org/wiki/JztoolInstall.

[dconrad]

If there is anybody in here with the Native port, it now supports dual-booting into the original firmware!

Here is a download of the bootloader build:
http://download.rockbox.org/bootloader/aigo/native/bootloader.erosq

Instructions are, as amachronic said above, listed in the wiki.

[Falco98]

If there is anybody in here with the Native port, it now supports dual-booting into the original firmware!

I just got one from Amazon with OF version 2.7 on it.  I was able to do the manual "update" down to the pre-patched dual-booting 2.5 firmware; the boot sequence seems to work fine, both for booting into Rockbox as well as into the OF.  However as soon as I attempt to start playback on a music file in Rockbox, it crashes with a segmentation fault error message (after which any button press will reboot the unit).  Is this some known issue / limitation?  Is it due to downgrading from a higher OF version?  (I did confirm that music playback in the OF, 2.5 version, works fine, with the same file(s)).

ETA: ugh -- I'm really sorry, in my haste I forgot to mention that the actual unit I got was the Surfans F20.  Maybe the firmware numbers I listed were enough info for some readers, but I'm not sure, and no idea why I didn't include that originally.  Also I'm not sure why I replied to a comment about the Native port, as I definitely installed the hosted port.

Also: if anyone's interested, the RockboxUtility installer *definitely* seemed to not want to work on this player out-of-box.  I provided RBUtil with the "original" 2.5 version firmware from the Surfans website (despite the player already being at version 2.7), and RBUtil basically just crashes and disappears after providing the firmware file.  As I mentioned above, manually updating with the pre-patched Rockbox "2.5" version worked.  Just in case someone wants to look into this, and/or have me try something different for debugging reasons.

[dconrad]

It sounds like you're on the hosted port rather than the native port, is that right? if you installed with the pre-patched firmware version, that is the hosted port. Does the Rockbox/OF select screen come up every time you boot the player?

As for the segmentation fault error message, that is a new one. Just to try to narrow down the situation, were you trying to play a file from the file browser or from the database? What file type and how long is it, and are there any special characters in the folder or file name?

[Falco98]

It sounds like you're on the hosted port rather than the native port, is that right? if you installed with the pre-patched firmware version, that is the hosted port. Does the Rockbox/OF select screen come up every time you boot the player?

Yes, and yes (as far as I understand the difference between hosted / native; all my other RB devices have been too old to offer such a distinction).  To confirm, the selection screen does come up every time it powers on.

As far as the song I tried: it's an Ogg Vorbis file, encoded in a standard way; I tried to start it from the file browser.  I only loaded a single album to the device for testing reasons, though I can load more and see if other formats act differently.  No particular special characters, etc.

Edit: tried with FLAC and MP3 albums and both work.  So, so far it's just the Ogg Vorbis (standard encoding, Q5) that produces the segfault.  I'll try with some other albums and encodings and see if the error seems to follow anything in particular.  Sorry for not troubleshooting more first, lol.

Edit 2: ok, now i feel silly.  I removed the baked-in album art from the album in question and it no longer SegFaults.  The only difference between the art on this album and most others is that it's like 1400px square - I only left it in because it came with that one by default.  Most other times I swap out for a 500 or 600 pixel square version.  And of course it's useless in Rockbox anyway since it doesn't even observe embedded album art in flac/vorbis files -_-

The funniest part?  If I extract the troublesome album art and put it in the album folder (in the standard convention of "folder.jpg" etc), it works fine in Rockbox and even displays.  So it's not even as if it's a corrupt image file or anything.  Goofy.  But I assume it's just a quirk and I just had the bad luck of trying this one first, lol.

[dconrad]

Ok, sounds good, thanks for narrowing it down. It doesn't sound like something device-specific if it's only ogg vorbis format files. One other sanity-check thing is, is this an old SD card? You could try overwriting your .rockbox folder - I had once or twice where a really cheap SD card actually corrupted the .rockbox folder right off the bat and I had weird crashing issues. Maybe try a good, name brand SD card you trust and see if the issue is still present.

[Falco98]

Ok, sounds good, thanks for narrowing it down. It doesn't sound like something device-specific if it's only ogg vorbis format files. One other sanity-check thing is, is this an old SD card? You could try overwriting your .rockbox folder - I had once or twice where a really cheap SD card actually corrupted the .rockbox folder right off the bat and I had weird crashing issues. Maybe try a good, name brand SD card you trust and see if the issue is still present.

Sorry - I added some further info in edits to my last reply above.  TL;DR is it ended up being that Rockbox is choking on embedded album art in one particular Ogg album with an unusually large-resolution cover image (though the image's filesize is only 290kb).

The "Cheap SD card" thing is an interesting thought too - I'm actually using the 32gb card that comes preinstalled in the F20 - I didn't even take it out yet to verify what brand it allegedly is.  But now that I have things working otherwise I'm assuming that isn't the particular issue I'm experiencing here.

[dconrad]

Good to hear you got it sorted out. To be honest, trying to load a too-big image file really shouldn't cause it to segfault like that. But, sometimes that's reality.

I don't think I have any ogg vorbis files at the moment, but I definitely use FLAC files with embedded art, so that should work. It is important to make sure that the art is a basic jpg rather than a progressive jpg or png, and like you say, a reasonable size - I think I use 700x700 usually.

[Falco98]

To be honest, trying to load a too-big image file really shouldn't cause it to segfault like that. But, sometimes that's reality.

I'd've thought so myself.  I'll check later if I can reproduce the same issue with a "blank" ogg file with the same album art, and if so I can attach it here for any interested parties to look into.

I don't think I have any ogg vorbis files at the moment, but I definitely use FLAC files with embedded art, so that should work.

Can you confirm?  AFAIK none of my "vorbisComment" type files (flac or ogg) currently work in Rockbox with embedded art.  As the vorbisComment spec doesn't "officially" support it (last i checked, i guess?), I assumed it was not yet supported in RB.  The only one I was sure would work was MP3.

It is important to make sure that the art is a basic jpg rather than a progressive jpg or png, and like you say, a reasonable size - I think I use 700x700 usually.

I'm used to this constraint, having been using RB on color targets since the Ipod 5.5gen became stable years-and-years ago
I checked the extracted art file for the one that seems to have caused the seg fault, and it's not progressive, at least.  Not only that, but when I placed it separately in the music folder (alongside files no longer containing the image), it works in rockbox.  Go figure.

[dconrad]

Yep, I can confirm I have .flac files with Tag 2, type Vorbis, where the embedded album art works. the picture type is "Cover (front)", Mimetype image/jpeg, and text encoding ISO-8859-1. I did rename the cover.jpg in the same folder to bak_c_over.jpg too, because I'm not sure what the filename matching requirements are for that.

I should add, these are all FLACs I've downloaded from bandcamp, but I have a script which ensures the album art is suitable for RB using kid3 and imagemagick - all it does is extracts it, converts to baseline jpeg, and rescales it to 700x700, then re-embeds it.

[Falco98]

Yep, I can confirm I have .flac files with Tag 2, type Vorbis, where the embedded album art works. the picture type is "Cover (front)", Mimetype image/jpeg, and text encoding ISO-8859-1. I did rename the cover.jpg in the same folder to bak_c_over.jpg too, because I'm not sure what the filename matching requirements are for that.

Thanks - it turns out the one FLAC album I'd tried had cover art files in the directory so I assumed it was using those.  I just deleted the files and re-tested and it does seem to pick up the embedded art.  Given that, I wonder why it doesn't work yet for Ogg Vorbis files... after all, FLAC files use *vorbis* comments, lol.

Edit: to add to the confusion a bit, current versions of the manual seem to indicate that vorbiscomment embedded album art still shouldn't work: http://download.rockbox.org/daily/manual/rockbox-fiiom3k/rockbox-buildap2.html#x18-428000B.2

[JoeH2]

I recently got a new "HiFi Walker H2".
Unfortunately the installed Firmware Version is 1.4 and installing Rockbox was not working.
I tried to install using Rockbox Utility.
Auto recognition failed, so i selected "HiFi Walker H2 1.3+"
SD content looks ok.

When running Firmware Update from the stock firmware, output is:

"Updater V1.1
v_v File error"

and then:
"v_v Failed"

 



BTW: There is a video on YT where someone opens a Aigo Eros, but the PCB looks very different to the one of dconrad.
The PCB there has to marking "QII_V2_20190523".
https://www.youtube.com/watch?v=rPH3Trj3P00

[azndante]

I also got the Surfans F20 with V2.7 firmware loaded on it. Even though I can downgrade with the pre-patched V2.5 hosted-port firmware, the line-out port stopped working for me. Going back to V2.7 firmware got the line-out port again. I bought the player for the line-out port, so I will have to stay with the official firmware until the pre-patched firmware is available. I haven't tested if any other functionality stopped working using an older firmware yet.

[7o9]

BTW: There is a video on YT where someone opens a Aigo Eros, but the PCB looks very different to the one of dconrad.
The PCB there has to marking "QII_V2_20190523".

By that marking, it sounds like a Qii, for which the wiki says 'NOTE: The EROS Qii uses a very different internal platform internally, and is *not supported.*': https://www.rockbox.org/wiki/AIGOErosQK