TTS to BT Mono not working (Nexus 5)

So I'm trying to use my Nexus 5 with my OEM BT mono capable car for Google Maps navigation, and when properly setup (or so I think) I get no audio out of either the phone or the car. Phone calls work fine, where the stereo displays "Phone." During navigation prompts, the SoundAbout menu icon shows up, but nothing appears on the car's display. This to me indicates that there is a software issue initiating a connection to the car. I'm coming from an iPhone, which worked with nav out of the box and I'm afraid that I'm too spoiled to turn back..

My settings are as follows:

TTS Behavior
- Android TTS settings: SoundAbout TTS
- Audio output: Bluetooth (mono)
- Max utterance per request: Two
- Delay utterance (secs): 1.0 (also tried 1.5, 2.0)
- Allow background audio: checked

Bluetooth Behavior (I think I have tried nearly every combo here)
- Bluetooth Auto Enable: checked
- (A2DP) Media audio usage: checked
- (Mono) Media audio usage: NOT checked
- (Dynamic) Media audio usage: NOT checked
- (Mono) microphone override: NOT checked
- Phone call audio usage: checked
- Disable wired audio: NOT checked
- Bluetooth disconnect audio: checked


Any help to get the software up and running would be amazing! I did purchase the Pro license, but I don't believe that has any effect

thanks,
Bryson

Bluetooth mono has to fake a phone call for the audio to get to the Bluetooth mono device (car). Not all devices/cars will do this.

Can you try the latest Beta version? Restart the phone after installing Beta from here:
https://soundabout.forumotion.com/f8-download-beta-versions

Working with the latest beta! Just have to fix the double announcements now. Thanks!

OK, great. Did you see this post?:

https://soundabout.forumotion.com/t201-get-rid-of-double-voice-when-using-google-navigation-and-soundabout-tts

Thanks, I did see that earlier. Very strange problem and I seem to recall a 'beep' sound when an instruction began on the iPhone using Google maps, I wonder if it's the same bit of code in action that generates this noise on android? Odd behavior, either way

Thanks again

Yes, if you "disable" the double voice, it beeps. It's OK because it just means less time for the delay setting when using Bluetooth mono.

An update: it appears to have fixed the issue in one car but not the other. The OEM Bluetooth is still not functioning (symptoms as in the original post) but my aftermarket Parrot BT now works.

Not all devices will allow the "fake" phone call to allow Bluetooth mono audio. You can test by changing the "Media audio" setting to "Bluetooth mono" and trying to test to see if media will transmit. Some apps will reduce the audio quality to allow music to transmit over Bluetooth mono. I usually test with an app like "Voice Reading". It reads text from web pages out load. Since it is voice quality it is a good test for Bluetooth mono. Voice Reading can also be used to test Text-To-Speech in SoundAbout.

I just find it odd that it only works in one vehicle with the same phone, as it worked in both vehicles with the iPhone and neither bluetooth setup handles more than headset mono. I'll test as you suggest and report back

There is another Beta version out there. You most likely don't need the delay utterances any more when using Bluetooth mono.

The Beta versions are here:
https://soundabout.forumotion.com/f8-download-beta-versions

Brilliant!  I was trying to get the latest official version from the Play Store to work with my Nexus 5 and I couldn't get any sounds out of my car's BT (2010 Mazda3).  After installing the latest beta, it works!  Now I can listen to the radio or a CD in my car's system, and when Google wants to give me directions it cuts in using the BT.  I love it!!  Thanks for this handy little app :-)

Just FYI, I am using all the default settings, except TTS where:
Audio output - BT (mono)
Max utterances - 1
Delay - 2.0 secs (I find that I do need this delay)

Update: I used the app on a few trips and noticed a couple of quirks. Sometimes, I got the double voice issue, and sometimes the instruction would get cut off e.g. it would start to say "In 1000 feet" and then stop. I just followed the steps you listed to get rid of the double voice, we'll see if that helps.

It is connecting to the car BT pretty reliably, though, so that's great news! :-)

Yes, that does happen in Google Nav. I have found that CoPilot works great. I think it is programmed to receive all directions (one by one) using TTS. This works great for redirecting audio.