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
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.
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
So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?
Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.
smart lock on?
Removed all trusted devices from smart lock and it still happened.
Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.
Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.
I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.
Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).
Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.
Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.
You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...
I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone
Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.
Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.
I'm not sure if this has to do with recent updates to Android Auto or if it's specific to the make and model of my device (I got the new phone around the same time as the latest AA updates were released), but I'm now experiencing endless frustrations with constant connection failures between my phone and my Jeep's Uconnect 8.4 head unit again. I went through a similar thing, as did many others, around this time last year and the year before. It's infuriating.
Most of the time, when I plug my phone into the vehicle's USB port, the Android auto icon appears on the display of the head unit for a moment or two and then disappears. There's a notification in the shade on my phone that says something like "Connecting to Android Auto" or "Starting Android Auto." But then it never really starts.
Occasionally I try clearing the data, storage and cache from the Android Auto app and sometimes Google Play Services. Sometimes I'll also have to go into the Uconnect settings menu and tell my head unit to "Forget device." Every so often, as long as I then turn off the ignition and then restart the vehicle and then reboot my phone, this will bring me back to the Android auto setup screen and I'll be able to use Android auto for a single drive cycle. as soon as I cut the engine and unplug my phone, it's over. When I get back into the vehicle I'm back where I started: with the head unit seemingly able to recognize that an Android Auto device is connected for a moment and then Android Auto just quits out.
It's insane. Seems like Google can't just get this right. As soon as they release a build that works, they follow up with an update that completely breaks functionality.
Anyone else have a similar experience and, hopefully, have suggestions and how to resolve this nonsense?
Used my iPhone with my 2018 Challenger for a year and it worked perfectly. Switched to a Note 20 Ultra last month and it worked for about 2 weeks. Same issue you're experiencing. I'm going back to iPhone.