Create voice3aplushack.md

[andrewtvuong]

Sorry it's a pretty rough submit. Just jot down thoughts.

11-16-18 AIY image is the latest image, and the only image late enough to support the new 3A+ released also in November 2018. Unfortunately that particular image, I've encounter many audio playback issues, some microphone issues also. There would be no sound which I suspect has something to do with pulseaudio that was introduced with August 2018 AIY image. The most recent AIY image that worked as expected was 4-13-18, but unfortunately does not support futureware 3A+. 3A+ would not boot unless with November 2018 the latest AIY image.

Therefore I experimented by downloading the most recent Raspbian image from raspberrypi.org 11-13-18 to ensure that 3A+ would boot. From there I followed the hacking.md guide from google/aiy-raspbian to proceed to add setup AIY voice with src files from 4-13-18 the version that did not include pulseaudio and worked fine. Along with minor changes to configuration files as you will see.

My experiment worked. 3A+ was able to boot, play audio from the v1 voice hat.

I suspect pulseaudio to be the culprit. Additionally, the script folder with install-alsa and install-services with asound.conf seem to disappear from the most recent image. These were found in the 4-13-18 AIY image src/scripts.

Happy hacking!

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[andrewtvuong]

I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.