Galaxy S4 navigation through phone speaker issue

I have a Honda with built-in bluetooth. Like others, I wanted to be able to have the navigation audio directions come through my S4 speakers, so that I can listen to the radio and still get the audio directions. I followed the forum instructions and set text to speech to SoundAbout TTS with Google as the TTS engine. The audio output is speaker, the max utterance is 2, and the delay utterance is none.

Like many others, it worked after that, but with the double voice. I did option B at https://soundabout.forumotion.com/t201-get-rid-of-double-voice-when-using-google-navigation-and-soundabout-tts.

After that, everything worked perfectly a couple of times, but all of a sudden, the voice just stopped working at all. It doesn't come out of the phone speaker or out of the bluetooth (when I change my car to the bluetooth audio source). The interesting thing is that if I put my car in bluetooth audio mode and play music, the music pauses when the directions are supposedly being played. I just don't hear them.

The media volume on my phone is turned all the way up when I try this. Everything else seems to work correctly.

Please help!

Thanks.

If you go into the phone setting, and then Manage Apps, scroll down to SoundAbout and click on it. What version of SoundAbout are you using?

Can you give the latest Beta version a try?
https://soundabout.forumotion.com/f8-download-beta-versions

Thanks for your help.

I was using version 2.5.6.1.

I installed the latest beta version and it seems to be working now, but with the double voice.

I did the fix again for that issue and I'll report back if I'm still having problems.

I have the double voice again as well. I think it was due to an update for Google Maps.

The double voice went away after doing the fix, but calls aren't coming through bluetooth. My phone shows that it's in headset mode, but I don't hear anything, even if my car source is on Bluetooth. If I hit speaker on my phone, I still don't hear anything.

OK, I put a newer Beta version out there. One thing to remember, is that on a lot of newer phones, the manufacturer phone application may behave differently. A lot of them will try to use the headset, if it is plugged in, regardless of SoundAbout trying to force otherwise. The only way around this is to answer the phone call with the Bluetooth headset "answer" button, or the car's "answer" button.

https://soundabout.forumotion.com/f8-download-beta-versions

I was using the car's answer button. I tried the new beta version with no luck. I'm going to completely uninstall and reinstall and see if it helps.

I would go into manage apps, find SoundAbout, clear cache, clear data, force stop , un-install.

Then install the new version.

Ok. Thanks. I'll let you know how it goes.

Also, Your phone may need the new setting. In Bluetooth Behavior section, there is a new setting called "Disabled Wired Media". This will disable wired headset/aux while Bluetooth phone call is in progress.

Just uploaded another new Beta version. Make sure to go into Manage apps, find SoundAbout and click it. Clear cache, clear data, force stop and un-install. Then install the new Beta and restart the phone to start fresh.

It seems to be working at the moment. Thanks for your help. I'll let you know if I have anymore issues.

That's Great. It works out well. Those that have an issue can use the setting and those that want the headset to be available for switching from Bluetooth can leave that setting un-checked.

I've been using it for a couple of weeks and it works great, except for 1 weird issue.

After saying the next direction, it sometimes then says a direction from much later in the trip. My max utterances is set to 2. It doesn't do it after every command and I can't seem to figure out a pattern. If it can't be fixed, I can live with it, but I figured I'd check. Thanks.

What is the direction that it is saying? Is it a generic term, like "Turn left" or "Head west"?

Sometimes people get a "double voice" effect during the first couple of words that is solved by doing what is in this thread:
https://soundabout.forumotion.com/t201-get-rid-of-double-voice-when-using-google-navigation-and-soundabout-tts

I already did that to get rid of the double voice.

It's not generic. It actually tells me steps from later on in the directions, like "turn left onto Park". That could be a direction from somewhere at the end of my trip, even while I'm at the beginning of the trip. It always first says the correct next direction before it says a later incorrect direction.

Did you try going into phone settings, manage apps, finding Google Maps and clearing the cache and clearing data?

I tried that, but I'm still get later steps thrown in every once in a while as described in my earlier post. It's not the end of the world if there is no solution. It's much better than not being able to listen to the radio while navigating. It's also usually pretty obvious when it's a direction for later in the trip, since it lumps it in after other directions, but doesn't say "then" before it like most 2nd steps.

See if the latest Beta helps. I added code to help with letting the client (Google maps), know that the Text-To-Speech is finished processing:
https://soundabout.forumotion.com/f8-download-beta-versions

jaqc19 wrote:I've been using it for a couple of weeks and it works great, except for 1 weird issue.

After saying the next direction, it sometimes then says a direction from much later in the trip. My max utterances is set to 2. It doesn't do it after every command and I can't seem to figure out a pattern. If it can't be fixed, I can live with it, but I figured I'd check. Thanks.

I am also experiencing this same issue. With max utterances set to 2, I sometimes will hear a direction from much later in the trip. I also cannot figure out the pattern to why this happens. This goes away with max utterances set to 1 but then that creates a worse problem where the current instructions get cutoff as they sometimes require 2 utterances.

SoundAbout Pro
Version 2.5.7.8.3

I just read your instructions for installing a beta version. I will re-install the beta version 2.5.7.8.3 as you described and will report back once I get to work this morning.

When you install a beta version of SoundAbout, make sure you do the following.

1) Un-install SoundAbout main app (not the pro version key). Go into Settings, Manage Apps, find SoundAbout (no Pro), click on SoundAbout and then click the Clear cache (if available), Clear data (if available), Force Stop, and then un-install.
2) Install the attached version.
3) Reboot the phone.

Early in my trip, I was told to make a right onto the current road. The next instruction was to continue on the major highway but that was still far off in my trip so it does appear that the problem still exists.

I uploaded another new Beta Version give the new one a try:

https://soundabout.forumotion.com/f8-download-beta-versions

I installed 2.5.7.8.5. I'll be driving from NY to D.C.on Wednesday. I'll see how it works.

I'm still having the issue, and now when I have bluetooth turned on on my phone (even if I'm not connected to a bluetooth device), all my sounds keep automatically muting and I can't adjust any of the volumes. If I turn bluetooth off and then on, everything is fine for a while before it happens again.

Can you try the latest Beta to see if the muting issue is resolved?
https://soundabout.forumotion.com/f8-download-beta-versions