Suggestions for updates to GoPiGo O/S 3.0.1

[jimrh]

@jimrh

The particular part of these lines is the -d hw:CARD=Headphones part. This was deliberately placed to force output through the audio jack regardless of what the normal system settings might be.

Solution / Workaround:

Remove the -d hw:CARD=Headphones part of those three lines.
Viz.:

su -c "espeak-ng 'f'" pi
su -c "espeak-ng 'WiFi IP'" pi
su -c "espeak-ng $IP_NUMBER" pi
su -c "espeak-ng repeating "  pi
su -c "espeak-ng $IP_NUMBER" pi

I have submitted this, along with my other proposed changes, to Nicole at MR for review and, (if they like them), inclusion in the next release.

There appear to be a few places where Nicole forces output to the headphone jack with that parameter, and I have suggested that they find/grep for every instance of that line and remove it.

There are a number of clean-up tasks they can do, (for example, removing obsolete features that never made it to prime-time and cleaning up the apt cache and logs), that will reduce the unzipped image by almost a gig.

I have asked them to send me a copy of the new release so I can beat on it and verify that all the fixes are in.

At this point, I’ve done just about everything I can do with this beastie until they send me a new one, so I am going to telescope all the way back in to my “New Remote Camera Robot” project.

[cleoqc]

@jimrh

There appear to be a few places where Nicole forces output to the headphone jack with that parameter, and I have suggested that they find/grep for every instance of that line and remove it.

Indeed we’re forcing it to the audiojack because if someone uses a Pi that was previously connected to a screen, the HDMI setting seems to get stuck. This doesn’t happen all the time but we did get more than a couple of cases.
And that’s why the audio jack is getting forced.

[jimrh]

That raises the issue again of why forcing headphone output causes the audio to go all pear-shaped.

I’m going to skip that for awhile.