Topic Sponsor
2015 - 2020 Ford F150 General discussion on the 13th generation Ford F150 truck.
Sponsored by:
Sponsored by: Worksport

Android Auto and WAZE app issues

Thread Tools
 
Search this Thread
 
Old Sep 18, 2017 | 09:32 AM
  #1  
DogHauler's Avatar
Thread Starter
Senior Member
 
Joined: Mar 2017
Posts: 138
Likes: 25
From: NC
Default Android Auto and WAZE app issues

Didn't see this being discussed, so if it has already I apologize.

So I got in my truck and had to use nav, noticed WAZE was an option finally. Selected it and was wildly disappointed. I use WAZE a lot on my phone, and this AA version seems to have a lot of flaws?

1. Very delayed/sluggish response (it sent me on a wrong turn and took forever to recover and redirect)

2. The voice volume vs music volume is erratic: If you use volume while the voice is speaking it will independently adjust the voice volume. But randomly it will permanently drop the music volume to 4. Sometimes it would return music volume to previous level prior to the voice speaking.

3. Voice search, it repeated my destination address perfectly but said nothing found. Had to type it in and it found it right away.

4. Didn't have any traffic alerts, and there weren't any actual issues on the route so don't know if this function is different than the normal app.

5. The speed limit and current speed aren't displayed, this may be a setting you can change but I didn't see it with minimal looking.

So anyone else having these issues/observations? Any tips or tricks to get it to function more like the phone only app?
Reply
Old Sep 18, 2017 | 10:34 AM
  #2  
ReBeL50V8's Avatar
Senior Member
 
Joined: Jul 2014
Posts: 313
Likes: 23
From: Jersey
Default

Mine works just like my phone, I'm using the s8+ may be an update on ur phone is needed?
Reply
Old Sep 18, 2017 | 11:42 AM
  #3  
bound4doom's Avatar
Senior Member
10 Year Member
Liked
Loved
Community Favorite
 
Joined: Dec 2013
Posts: 234
Likes: 54
From: Michigan
Default

1. Very delayed/sluggish response (it sent me on a wrong turn and took forever to recover and redirect)

This honestly is usually your phone. Delayed and slow and so on you have a lot going on with your phone or your network like only a single bar.

The wrong turn is well waze, not in the ford stuff. What happens when it need to get new directions it send your locaiton off to Waze Servers they send back the corrected route. So either you phone is too slow in sending and receiving or your network. Now I have noticed this but no different that Waze did in my old truck when I just had my phone up on a stand so I could see it.

2. The voice volume vs music volume is erratic: If you use volume while the voice is speaking it will independently adjust the voice volume. But randomly it will permanently drop the music volume to 4. Sometimes it would return music volume to previous level prior to the voice speaking.

Yes this is a problem with Waze. I have reported it to them and contacted them. If you can't tell yet I am a computer programmer so what is happening is a problem with Waze. What it does is say your volume is at 14, Wazes stores that number, lowers your volume speaks and tells your radio to go back to 14. The problem is when Waze takes a brief pause and says something else. Your radio hasn't quite reached back to level 14 well say it is at 7 well waze sees 7 as your volume number now, says what it needs to say then tells your radio to restore back to 7. Hopefully they will fix it soon because yes this can be annoying.

3. Voice search, it repeated my destination address perfectly but said nothing found. Had to type it in and it found it right away.

There could be a lot of issue with this. However, if you are using an android phone, it uses google to recognise your voice if your using apple it uses Siri. What it does is try to decipher what you said then passes that to Waze. Both of those hear what you said then send it back to thier servers to get the text. Again since this is the tech on your phone, and your havin issues, in number 1 you might have too much crap running, phone too slow, or network too slow.

4. Didn't have any traffic alerts, and there weren't any actual issues on the route so don't know if this function is different than the normal app.

Nope this should all be the same. Maybe you just had no traffic alerts. However, this all works as prior. Again rememebr your getting this info from the Waze servers, if you have poor network connectivity or something going on then this could affect that.

5. The speed limit and current speed aren't displayed, this may be a setting you can change but I didn't see it with minimal looking.

No they have not gotten this to work yet with the current Waze version for in car. Supposedly coming in a newer version.


Best advice shut down all the crap on your phone, you don't need to be getting facebook alerts and stuff while driving. The more you have running on your phone the slower it is going to be. I had an issue with Waze this weekend. I closed all the apps on my phone then rebooted it. Fixed all my issues. This is rare but I have had to do this a couple times. The Current version of Waze app out there is the First version released that works and was only released a month ago, maybe month and a half. They are working on fixing a lot of the issues, Volume, Spedometer, etc. The only thing you can do is wait for them to fix them.
Reply
Old Sep 18, 2017 | 12:30 PM
  #4  
DogHauler's Avatar
Thread Starter
Senior Member
 
Joined: Mar 2017
Posts: 138
Likes: 25
From: NC
Default

Bound, thanks for the inputs. I usually only use WAZE on longer drives, but I've never had a problem with signal, directions, or wrong turns before so figured it could be an AA app issue.

I am using a droid fully updated.

FWIW I don't have any alerts on my phone, I don't have any games, nor FB crap :p But I'll cold boot the phone next time prior to use to eliminate any possibilities. I've waited a year for the WAZE AA, I can wait another for it to be fully functional like the standalone version :p
Reply
Old Sep 18, 2017 | 01:33 PM
  #5  
markp123's Avatar
Junior Member
 
Joined: Jul 2017
Posts: 5
Likes: 0
Default

For the delayed/sluggish/poor accuracy make sure your phone is not on power saver mode. Waze will perform much better once this is turned off. Does not seem to affect google maps performance, but will on waze.
Reply
Old Sep 18, 2017 | 03:04 PM
  #6  
bound4doom's Avatar
Senior Member
10 Year Member
Liked
Loved
Community Favorite
 
Joined: Dec 2013
Posts: 234
Likes: 54
From: Michigan
Default

Originally Posted by DogHauler
Bound, thanks for the inputs. I usually only use WAZE on longer drives, but I've never had a problem with signal, directions, or wrong turns before so figured it could be an AA app issue.

I am using a droid fully updated.

FWIW I don't have any alerts on my phone, I don't have any games, nor FB crap :p But I'll cold boot the phone next time prior to use to eliminate any possibilities. I've waited a year for the WAZE AA, I can wait another for it to be fully functional like the standalone version :p
Ok, shouldn't have to much issues then, when something squirrely like that happens usually I just restart my phones. A couple things happen when you restart your phone especially when traveling. When it connects to a tower it also pulls in tower information for surrounding towers and tells the phone which ones are better to connect to. Whenever I get to a new city a couple hundred miles away I just reboot my phone. They do update automatically, tower information but no telling exactly when. They Will always update when rebooted.

Also the voice recognition uses Googles voice stuff, you know where you talk to you phone and say Ok Google. I turned all that stuff off. However, before I did that I worked with the phone to train it to my voice. Might be something worth trying, turn on the google assistant features. Talk to it a while like a few days doing some google searches and stuff. It also has a voice training thing in it. This way it gets to know your voice. So anyway when you hit the waze button to tell it where to go, you speak, it goes out to google translates to text then passes that text to Waze. The Google part is what is problematic for you I think.
Reply




All times are GMT -4. The time now is 08:36 PM.