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

[speakn2pabst]

Hello! I'm a newish owner of a HIFI Walker H2 that came with a 1.5 version firmware.  This evening I upgraded a Hosted Rockbox setup that I've been using since November to the Native version.

  I'd like to volunteer to test in an effort to get the Line Out port functional.  What would be required to do this?

  I'm not sure of the difference between Line Out and the Headphone jack.  Assuming someone provides the software changes would a typical low-impedance headphone be suitable for testing the Line Out jack?

  This is by no means urgent on my part. I'm satisfied currently using the Headphone jack but wish to help in service of the community.  And perhaps down the line may find use for a functional Line Out.

Thanks for the port and your consideration.

[dconrad]

Hello! I'm a newish owner of a HIFI Walker H2 that came with a 1.5 version firmware.  This evening I upgraded a Hosted Rockbox setup that I've been using since November to the Native version.

  I'd like to volunteer to test in an effort to get the Line Out port functional.  What would be required to do this?

  I'm not sure of the difference between Line Out and the Headphone jack.  Assuming someone provides the software changes would a typical low-impedance headphone be suitable for testing the Line Out jack?

  This is by no means urgent on my part. I'm satisfied currently using the Headphone jack but wish to help in service of the community.  And perhaps down the line may find use for a functional Line Out.

Thanks for the port and your consideration.

Great that you are willing to help get line out working! I don't know your comfort level with programming in general, but are you able to set up a build environment? That would be the quickest way to be able to test builds yourself. This wiki page under "Set up your environment" has links to how to set that up.

Otherwise, I can do some builds here later today and post them for you to try.

I think some regular headphones would probably be fine to try the line out, it's a situation where it either works or it doesn't work.

We're really shooting in the dark here, but I have a guess that the stereo switch is now hooked up to switch between the headphone and line-out outputs, so maybe changing this line (https://github.com/Rockbox/rockbox/blob/master/firmware/target/mips/ingenic_x1000/erosqnative/audiohw-erosqnative.c#L79) from 0 to 1 may change the behavior.

We might have to just try changing the states of some of the relevant GPIO pins listed here (https://github.com/Rockbox/rockbox/blob/master/firmware/target/mips/ingenic_x1000/erosqnative/gpio-target.h#L28), probably in that same audiohw_postinit() function to see what behavior changes.

As a side note, I'm curious - does your player have microUSB or USBC?

[speakn2pabst]

Great that you are willing to help get line out working! I don't know your comfort level with programming in general, but are you able to set up a build environment? That would be the quickest way to be able to test builds yourself. This wiki page under "Set up your environment" has links to how to set that up.

Otherwise, I can do some builds here later today and post them for you to try.

I think some regular headphones would probably be fine to try the line out, it's a situation where it either works or it doesn't work.

We're really shooting in the dark here, but I have a guess that the stereo switch is now hooked up to switch between the headphone and line-out outputs, so maybe changing this line (https://github.com/Rockbox/rockbox/blob/master/firmware/target/mips/ingenic_x1000/erosqnative/audiohw-erosqnative.c#L79) from 0 to 1 may change the behavior.

We might have to just try changing the states of some of the relevant GPIO pins listed here (https://github.com/Rockbox/rockbox/blob/master/firmware/target/mips/ingenic_x1000/erosqnative/gpio-target.h#L28), probably in that same audiohw_postinit() function to see what behavior changes.

As a side note, I'm curious - does your player have microUSB or USBC?

As far as programming and build environments I've built some well documented projects before by following detailed guides (OpenWRT and WINE for example).  These pages you've linked to are of the level of detail that I'm comfortable with so I'll give it a try.

  I'm on ArchLinux and I've cloned the git repo.  Will it be helpful if I create a Git or Gerrit login? I've not usually sent in commits before. 

As far as the device, it has a USBC port.

I'll have some available time after 6:00 PST which is about an hour from now.

[speakn2pabst]

Well I've put together a working build environment (to avoid a struggle with dependencies I opened an Ubuntu image in Boxes and just used all the apt commands and rockboxdev.sh).

Looking at the highlighted code from the last post I saw it was under firmware so I assumed the selection of "Bootloader" as opposed to a normal Rockbox build when given the choice by the configure script.  That was a guess though.
 
Since I was able to compile I tried making the change of "0" to "1" in the highlighted line of file audiohw-erosqnative.c

I then compiled a bootloader and I tried it by updating from the (Vol Up + Power) bootmenu while it was present on the SD card root directory and it successfully flashed but that change alone wasn't sufficient.  Rockbox launched successfully and played through the Headphones port but not a peep through Line Out.

At this point I'm a bit out of my depth.  I don't know what are appropriate changes to try in the gpio-target.h file.

I'll check back tomorrow and attempt further progress.

[dconrad]

Great that you got the build environment put together!

Sorry I should have been more clear, there's no need to build or reinstall the bootloader, the normal build is enough. I actually think the audio hardware initialization stuff doesn't get run in the bootloader at all, so give it another try with the normal build.

[speakn2pabst]

Alright, I tried making the "Normal" build and then replaced the .rockbox folder with the new one.

Currently the headphone port stopped working and the Line Out acted strangely. While shoving the plug into the Line Out for a moment I heard the tracks playing across my headphones, but when the plug is seated fully in the port it was silent.  I could partially unplug the connection and hear intermittent flashes of sound.

Looking for guidance on next steps.

[dconrad]

That's good that you got life out of the line out - I'll think it over for a bit and try to come up with a next step.

EDIT: Ok, I think the next step we can try is to now comment out this line (https://github.com/Rockbox/rockbox/blob/master/firmware/drivers/audio/eros_qn_codec.c#L62).

What I'm guessing here is that the line-out is being run through the headphone amp now. I don't know why they would do that - you would think it would go like DAC-->Switch-->HP AMP-->HP, but I wouldn't be surprised if the switch and headphone amp are reversed.

[speakn2pabst]

That's good that you got life out of the line out - I'll think it over for a bit and try to come up with a next step.

EDIT: Ok, I think the next step we can try is to now comment out this line (https://github.com/Rockbox/rockbox/blob/master/firmware/drivers/audio/eros_qn_codec.c#L62).

What I'm guessing here is that the line-out is being run through the headphone amp now. I don't know why they would do that - you would think it would go like DAC-->Switch-->HP AMP-->HP, but I wouldn't be surprised if the switch and headphone amp are reversed.

Your latest assumption seems to be getting us closer to the mark.  This time the headphone port remained inactive but the Line Out active (with a fully seated headphone jack).  It was uncomfortably loud for headphones and further did not respond to volume adjustments, up or down.  Even when I bottomed out the GUI volume curve it still was unaffected.

[ge2655]

mrsubway,
Thanks for the replies.

I contacted HiFi Walker, requesting a link to firmware version 1.5.  They informed me that they do not provide access to their firmware versions.  In the meantime, I ordered a Surfans F20. 

Upon the F20’s arrival (firmware version 2.7) I was able to load RockBox without issue.  After the successful RockBox installation, I returned the HiFi Walker.  The stock sound of the HiFi Walker (EQ off) is very, very good but my inability to get RockBox loaded was a deal breaker. The limited play, sound and display options of the stock firmware are clearly evident to anyone who is accustomed to the plethora of RockBox options.  If you do not care about running RockBox, the HiFi Walker is a very good player.

I’ve been using (still have) RockBoxed Sansa players (Fuze, Fuze+, clip, clip+, clip zip) and believe any of them, coupled with a pair of Kramer-modded Koss KSC75 [to my ears], is the best sounding budget combination.

If you are a vintage Sansa fan looking for a newer alternative, a RockBoxed Surfans F20 is worth a look. The F20 is bulkier (built like a tank) than the Sansas but the RockBoxed F20 offers silky smooth operation with only one minor hiccup I’ve noticed.

If there are mixed file types (Mp3 and Opus, for example) in a common folder, when one type of file crossfades with a different type the transition is premature and abrupt.  Crossfades between the same type of files are perfect.

-Gary

[dconrad]

Your latest assumption seems to be getting us closer to the mark.  This time the headphone port remained inactive but the Line Out active (with a fully seated headphone jack).  It was uncomfortably loud for headphones and further did not respond to volume adjustments, up or down.  Even when I bottomed out the GUI volume curve it still was unaffected.

Good to hear! That all makes sense. Rockbox's behavior is that when the line out is being used, the volume is fixed to maximum (the max volume can be set in the settings).

So it sounds like the line-out is being run through the headphone amp now. What we can probably do is remove the headphone amp muting logic and add switching based on the plugged/unplugged states of the headphone and line-out jacks.

The only gotcha is the line-out may be too hot if it's being run through the hp amp... Maybe we could add a new setting specifically for setting the line-out mode volume. Unfortunately the level is kind of hard to test without having someone actually measure it.

If I'm thinking about this right, I don't think this would really affect the usability of the earlier units either. I'll have to test it out. I think the only thing that would be different is plugging in line-out will disable the headphones, whereas now you could actually use both outputs at once if you wanted to.

Actually, if you want to try replacing audiohw_set_volume() with this, I think this should work:

Code: [Select]

void audiohw_set_volume(int vol_l, int vol_r)
{
    int l, r;

    vol_l_hw = vol_l;
    vol_r_hw = vol_r;

    l = vol_l;
    r = vol_r;

#if (defined(HAVE_HEADPHONE_DETECTION) && defined(HAVE_LINEOUT_DETECTION))
    /* make sure headphones aren't present - don't want to
     * blow out our eardrums cranking it to full */
    if (lineout_inserted() && !headphones_inserted())
    {
        l = r = global_settings.volume_limit * 10;

        /* mute the headphone amp if not plugged in */
        /* on newer units, the headphone amp is in circuit for the
         * line output as well, so do not mute */
        //audiohw_mute_hp(1);
       
        /* on newer units, the stereo switch actually switches
         * between the headphone output and the line output */
        gpio_set_level(GPIO_ISL54405_SEL, 1);
    }
    else
    {
        /* unmute the headphone amp when plugged in */
        //audiohw_mute_hp(0);
       
        /* on newer units, the stereo switch actually switches
         * between the headphone output and the line output */
        gpio_set_level(GPIO_ISL54405_SEL, 0);

        l = vol_l;
        r = vol_r;
    }
#endif

    l = l <= PCM5102A_VOLUME_MIN ? PCM_MUTE_LEVEL : (l / 20);
    r = r <= PCM5102A_VOLUME_MIN ? PCM_MUTE_LEVEL : (r / 20);

    pcm_set_master_volume(l, r);
}
I also wonder if there are any new hardware capabilities with the new changes, but one step at a time 

[speakn2pabst]

Success!  With the current changes the Line Out works at full volume while the HP port also works and respects the volume setting.

I was curious about testing the simultaneous situation and so tried plugging in two headsets.  With both plugged in only the HP port connected set was playing.  It didn't matter if the HP port was populated first or second, in both cases as soon as there was two connected only the HP port set would play.

Personally I find this either/or reasonable.

"The only gotcha is the line-out may be too hot if it's being run through the hp amp... Maybe we could add a new setting specifically for setting the line-out mode volume. Unfortunately the level is kind of hard to test without having someone actually measure it."

Is this something that can be measured using an auxiliary cable from the Rockbox Line Out to a Microphone or Line In port on a computer Sound Card, in conjunction with some free software?  Or does "too hot" imply some risk to the receiving device?

Regarding new hardware capabilities, yeah let's keep going.

[dconrad]

Success!  With the current changes the Line Out works at full volume while the HP port also works and respects the volume setting.

I was curious about testing the simultaneous situation and so tried plugging in two headsets.  With both plugged in only the HP port connected set was playing.  It didn't matter if the HP port was populated first or second, in both cases as soon as there was two connected only the HP port set would play.

Personally I find this either/or reasonable.

Yeah, I agree. I think the typical behavior for most devices is to prefer the headphone output, and I think we can stick with that. I'll start working on a patchset later and see if it works OK on older devices.

"The only gotcha is the line-out may be too hot if it's being run through the hp amp... Maybe we could add a new setting specifically for setting the line-out mode volume. Unfortunately the level is kind of hard to test without having someone actually measure it."

Is this something that can be measured using an auxiliary cable from the Rockbox Line Out to a Microphone or Line In port on a computer Sound Card, in conjunction with some free software?  Or does "too hot" imply some risk to the receiving device?

That's a good idea regarding using a line-in port on a computer. I don't know if you can typically get an idea for what the actual level is, but I imagine Audacity would probably be the tool for the job. Basically you would probably want to create a full-scale 440Hz FLAC file or some other lossless file to play back.

I wouldn't worry about any risk to any devices. Worst case scenario is that it may distort, I think.

[mrsubway]

mrsubway,
Thanks for the replies.

I contacted HiFi Walker, requesting a link to firmware version 1.5.  They informed me that they do not provide access to their firmware versions.  In the meantime, I ordered a Surfans F20. 

Upon the F20’s arrival (firmware version 2.7) I was able to load RockBox without issue.  After the successful RockBox installation, I returned the HiFi Walker.  The stock sound of the HiFi Walker (EQ off) is very, very good but my inability to get RockBox loaded was a deal breaker. The limited play, sound and display options of the stock firmware are clearly evident to anyone who is accustomed to the plethora of RockBox options.  If you do not care about running RockBox, the HiFi Walker is a very good player.

I’ve been using (still have) RockBoxed Sansa players (Fuze, Fuze+, clip, clip+, clip zip) and believe any of them, coupled with a pair of Kramer-modded Koss KSC75 [to my ears], is the best sounding budget combination.

If you are a vintage Sansa fan looking for a newer alternative, a RockBoxed Surfans F20 is worth a look. The F20 is bulkier (built like a tank) than the Sansas but the RockBoxed F20 offers silky smooth operation with only one minor hiccup I’ve noticed.

If there are mixed file types (Mp3 and Opus, for example) in a common folder, when one type of file crossfades with a different type the transition is premature and abrupt.  Crossfades between the same type of files are perfect.

-Gary

Flash the link I sent you.  Mine came with the beta as well.  The flash will install Rockbox as a boot option, and downgrade the original firmware to 1.5.  You'll lose the beta firmware, and have an environment where you can boot into Rockbox or 1.5.

I have no idea what the advantages of the 1.5 beta are.

[speakn2pabst]

"The only gotcha is the line-out may be too hot if it's being run through the hp amp... Maybe we could add a new setting specifically for setting the line-out mode volume. Unfortunately the level is kind of hard to test without having someone actually measure it."

Is this something that can be measured using an auxiliary cable from the Rockbox Line Out to a Microphone or Line In port on a computer Sound Card, in conjunction with some free software?  Or does "too hot" imply some risk to the receiving device?

That's a good idea regarding using a line-in port on a computer. I don't know if you can typically get an idea for what the actual level is, but I imagine Audacity would probably be the tool for the job. Basically you would probably want to create a full-scale 440Hz FLAC file or some other lossless file to play back.

I wouldn't worry about any risk to any devices. Worst case scenario is that it may distort, I think.

I have some lossless 440Hz FLAC files I can play.  But I'm not sure of the measurement to report. Is a screenshot while monitoring the plug sufficient?  This shows a peak in the volume or very close to it.   Tenacity is a fork of Audacity.

[dconrad]

I have some lossless 440Hz FLAC files I can play.  But I'm not sure of the measurement to report. Is a screenshot while monitoring the plug sufficient?  This shows a peak in the volume or very close to it.   Tenacity is a fork of Audacity.

That's the part I'm not sure of either. You would be looking for like a dBV or dBu value - I don't know if there is some capability of using a calibration or setting for your specific model of sound card or something like that.