Good morning. I have been having a particular, repeated issue since the last google maps update (7.0.2). Whenever I get into my truck I put my One in the OEM dock and it goes into "car" mode. Overall I love this app and find it incredibly efficient at doing its job.
However, since the last update from Google maps (which is also pretty indredible) I have been having a very specific error, that I believe is related to HTC's car mode. If I start navigation though the car dashboard and some event happens that pulls it from navi to the dashboard (i.e. a call comes in or a message) then when I return to navigation it again asks me to select the destination and I have to hit start. This will cause a "maps stopped working" error about 75% of the time.
What I believe is happening is that maps is already navigating but when in car mode you have to click on the "navigation" icon to get back to it, and it tries to launch another instance or over itself. This will also happen if I start navigation while not docked (i.e. walking to my truck) and docking, then launching the app. Also, maps is the one app that actually leaves car mode (you can see the system tray and then navigate to other non car mode apps) and I believe this is the root of the issue.
Since the car mode is (I believe) part of Sense, this would seem to be something specific to this. I thought there would be lots of inquiries into this but could find none. Thoughts?
I'm getting this too. It's deeply annoying and quite dangerous when going down the motorway. Considering going back to previous version.
Sent from my HTC One using xda app-developers app
It's an issue with the new Maps app. It sucks balls. I have those issues and I don't have the car dock.
Take a call or something else then when you try to go back to nav by selecting it from the notification panel, it does nothing or crashes or takes you to regular map and have to restart your route.
I hate it. It's pretty but so buggy. I reloaded the old version.
Sent from my HTC One
HTC car mode and Google maps
I am also having same problem. UN installed update and gone back to the much better old version
This is more of a Android Smart Lock question than a Nexus device question since i had this very issue on my OnePlus. I am running 6.0 Cataclysm stable version. No complaints but this one but I have had this issues on every ROM in I have run since Smart Lock was a thing.
We have all read the Smart Lock not working or works only sometimes questions. Well I noticed the times mine isn't working that when I open up my Trusted Agents in settings I see it quickly toggle on right before my eyes. I tried getting a scream recording of it but now its working fine and sure enough when I open Smart Lock settings its on and not quickly turning on.
Any ideas.
Sent from my Nexus 6 using XDA Forums
I've been having problems the past few days too. Mine never works at home or when connected to Bluetooth in my car even though both my home (and my neighbor's) home address and my Bluetooth device are setup as trusted places/devices.
I see what you are saying about the setting toggling on when you go into settings. I captured a screen recording. I went in and out of the Trust Agents setting 3 times. 2 of the 3 times you can see quickly switch from off to on (the first may be hard to catch but the third is very clear). Only on the second attempt does it appear to be active immediately.
I have the same intermittent Smart Lock problem and see my Trust Agents toggle as well.
Workaround that works 100% of the time for those having trouble connecting.
Unlock phone and turn on car or head unit. Note you should have android auto installed already before this will work. Plug in the cable to your phone and you will hear the link sound and the screen on your phone will flash off for just a second. As quickly as possible once the screen goes black on your phone uncable the phone and reconnect it. I know this sounds janky, but it really works. You can tell it is working by the screen on your head unit going black in the background and you will see the android auto icon sI have tried all suggested fixes and this is the only one that works 100% of the time. It also does not take over the telephone's display so you can navigate to other apps and still have android auto running. It is quick and gives you the best of both worlds. I almost returned my 2016 gti due to the frustration from this issue, but now it is no big deal.
Hope this helps guys and gals.
No. For what I read , the only API available for 3rd parties are to send messages and music, and that, using google interface. No other developer can do anything with AA.
In waze I cant press the buttons on the screen where they are toward the bottom. For example after I have selected a route and it is navigating, if I want to check routes manually I have to tap the screen about 1/2" above where the ">" is for it to work.
I cant even push the button for posting a report. Nothing happens.
This all started after my note 9 updated on verizon.
Using beta 4.44.0.900
I realize this probably related to the phone update, but my Pocket Cast app buttons seem to be fine.
This also appears to happen in google maps.
Matt
mattdb said:
In waze I cant press the buttons on the screen where they are toward the bottom. For example after I have selected a route and it is navigating, if I want to check routes manually I have to tap the screen about 1/2" above where the ">" is for it to work.
I cant even push the button for posting a report. Nothing happens.
This all started after my note 9 updated on verizon.
Using beta 4.44.0.900
I realize this probably related to the phone update, but my Pocket Cast app buttons seem to be fine.
This also appears to happen in google maps.
Matt
Click to expand...
Click to collapse
I got the Verizon update on the 26th, and have had zero issues since. Now, I can't speak for the beta Waze app, but non-beta works fine, and I use it every day. And there's nothing wrong with Google Maps, either.
RGardner said:
I got the Verizon update on the 26th, and have had zero issues since. Now, I can't speak for the beta Waze app, but non-beta works fine, and I use it every day. And there's nothing wrong with Google Maps, either.
Click to expand...
Click to collapse
Well crap. I had the regular version of waze on there and installed the beta trying to fix it. It does it in google maps too. I even went so far as to uninstall it and reinstall.
I am in a 2018 Chevy Volt for reference. I use it everyday as well and it is annoying. I cant find any settings anywhere to adjust any of it.
Update. Found some other users with the same problem
https://productforums.google.com/forum/#!topic/android-auto/vGpwzvweki0;context-place=topicsearchin/android-auto/waze$20touch
Short answer: Try turning off Performance mode, or changing your phones resolution from WQHD+ to FHD+
That is til they fix it.
I never had issues with Android Auto in my 2017 Civic until the ARJ5 update yesterday.
Now I can't press any buttons on the navigation screen. Using beta maps.
I tried to use Waze, non beta I downloaded it, and it had hard time registering presses. Even misaligned presses, I try to click home, and it selects work underneath it.
Wife's phone works just fine, S9+
Sent from my SM-N960U using Tapatalk
mattdb said:
Update. Found some other users with the same problem
Short answer: Try turning off Performance mode, or changing your phones resolution from WQHD+ to FHD+
That is til they fix it.
Click to expand...
Click to collapse
That might explain why I have seen no issues... mine is set to FHD+.
This is also an issue with the TMO update to the Note 9 they pushed on 11/18. I had to set mine to FHD+ for it to properly do Waze/Google Maps & Android Auto. I'll bet this isn't fixed until Samsung pushes Android 9.0 since AA users seem to get little love these days.
Same Issue, but found out why.
aergern said:
This is also an issue with the TMO update to the Note 9 they pushed on 11/18. I had to set mine to FHD+ for it to properly do Waze/Google Maps & Android Auto. I'll bet this isn't fixed until Samsung pushes Android 9.0 since AA users seem to get little love these days.
Click to expand...
Click to collapse
I started having the same issue, and changing the screen resolution solved it. It started happening again and again, but then I realized that my Samsung VR headset makes me change the screen resolution back to WQHD+. This makes it a little annoying to have to go in and change it back each time. I now added a switch on my main screen to change the resolution quickly.
toolittletime said:
I started having the same issue, and changing the screen resolution solved it. It started happening again and again, but then I realized that my Samsung VR headset makes me change the screen resolution back to WQHD+. This makes it a little annoying to have to go in and change it back each time. I now added a switch on my main screen to change the resolution quickly.
Click to expand...
Click to collapse
Switch? How?
toolittletime said:
I now added a switch on my main screen to change the resolution quickly.
Click to expand...
Click to collapse
I looked into the app QuickShortcutMaker to make a home screen icon to Screen Resolution but couldn't find it, is this what you're referring to?
BigMosely said:
I looked into the app QuickShortcutMaker to make a home screen icon to Screen Resolution but couldn't find it, is this what you're referring to?
Click to expand...
Click to collapse
I started with that as well and finally settled on Macrodroid to make my own toggle switch. Unfortunately, I also had to root my phone to get access to the screen resolution.
glad i found this page. i've been dealing with this issue since first patches in November on my att note9. will test resolution change later today.
It's been reported on the Google AA community that Pie fixes this. Well, I can say that the Oreo December security patch (on Verizon Wireless, at least) fixed this issue as well. I've been on WQHD+ since.
I 7se Google Maps daily on the S10. But if the screen goes off it stops giving directions and I have to hit Start again and resume. Only way it stays on is if I start the trip and physically hold the phone and not let the screen lock. Anyone else? Never had this issue with any other phone, Galaxy or otherwise.
I have the same issue. I use Automate to automatically turn AOD on and off based on received notification. I originally thought it causes this problem. Unfortunately, I can´t proove it because I needed to drive and hadn´t time to play with the phone. Just an idea to consider.
Edit: maybe it is Google maps bug. Have you tried uninstalling app updates?
Might have to do just that. But it does seems like a Maps bug, yet it was fine on my Note 8, and the iPhone X before that. So idk if it's Maps or a software bug with the S10. Normally I just tap "start" and then immediately click the lock/wake button and set the phone down and it sends the directions through the car or headset.
Verizon variant here by the way 100% stock.
Try to prevent the phone to set the Maps app to sleep. I had a similar thing with the old version of Maps (V6 which I still use).
Just search for 'Sleeping Apps' in your settings