Welcome to the Rockbox Technical Forums!
I like your idea of the car aux input impedance being too high to be detected ... except that I've just disproved it!I looked with a 'scope at the line out (cable unconnected to anything else) and I can see 'music' waveforms. I haven't generated a sine wave .flac to check but I am pretty sure it is audio - stops when I press pause etc.I can also confirm that the level does not change with the H2's volume controls, so as you say this must be a recent FW change.
I am reasonably confident about installing RockBox - I am actually a SW developer amongst other things, and I have installed it on an Xduo XX and X3ii. However this involves updating the bootloader on the H2's flash doesn't it? If I end up returning the device then I would not want to have fiddled with it in that way. I couldn't find mention (in a fairly cursory read of the docs) of how to save the current bootloader and revert it afterwards; if you can point me at that I will probably try that.Thanks for the information about the scroll wheel
Right, a fair bit of progress...I have successfully installed Rockbox on the H2! This included saving the original bootloader .bin file somewhere safe. I must say it was a relief to see the familiar Rockbox menu!And I can report that with the output mode set to 'Line out', I do indeed get output from that jack, and can play on the Car's Aux input!Somewhat strangely, I am not not sure if the Headphone output works correctly. 'Auto' switching doesn't seem to work for the Line out socket, at least, I will experiment a bit further.I was mis-understanding one thing ... on the Xduoo X3ii port, the Rockbox bootloader allows booting into either the original (HiBy) firmware, or Rockbox firmware. That doesn't seem to be the case for this H2 bootloader, is that correct?And I have realised that nothing has happened to the original H2 v2.0 firmware, I presume it is still living in Flash on the H2. So if I were to want to revert, I just have to use the recovery menu and re-flash the original bootloader image I saved (renamed...), and the H2 will boot into stock v2.0 firmware. Correct?Thanks a lot for all of this - at the very least it has answered my original question - it is some sort of issue with the stock v2.0 firmware not switching correctly - and it has got me up to speed with Rockbox installation on the H2.Thanks a lot for your help with this.Regards, jon N
Hi! Regarding reverting to stock bootloader, check my post from two pages earlier, from a few months ago. I had made a “custom” stock v2.0 image that will restore the bootloader back to the original. So you won’t need to worry. I had a couple others test it successfully when I was helping them out on Reddit.
QuoteHi! Regarding reverting to stock bootloader, check my post from two pages earlier, from a few months ago. I had made a “custom” stock v2.0 image that will restore the bootloader back to the original. So you won’t need to worry. I had a couple others test it successfully when I was helping them out on Reddit.Thanks, I see those posts now. The link in post #456 is no longer there BTW; is it superseded by the one in post #458?For interest ... what is the relationship between a 'backup' bootloader erosqnative-boot.bin file that I created and the update.upt file that is mentioned there?Regards, J^n
Oh. So the discussion in the jzinstall docs about saving the bootloader .bin, eg. so that you might later restore it, does not (currently?) apply to the H2?
Page created in 0.058 seconds with 16 queries.