Having a weird one here, sometimes my Android Auto will not load (as per video below). This does not matter if using Android Auto just on the phone or connected to the car. It seems to get stuck in a loop when in the car (of restarting), whereas on the phone as per the video, you select Android Auto and it crashes out to the screen.
I have tried uninstalling and re-installing, rebooting the phone, clearing the cache, downgrading google play services and re-install, but still the same
The weird bit, is sometimes it will work fine, but then the next time I run it, the crashing happens, and does not seem to be anyway to sort it, it just sometimes starts to work again for a limited time
I am running this on a P20 Pro with android 8.1. I have the latest google play version of Android Auto installed
https://photos.app.goo.gl/ku3u44BZCWBU4VVk6
Related
Hi, I'm having problems with now cards on homescreen. I'm running Android auto on Astra K's Intellilink 4.0 using my S4 Active (5.0.1 original FW).
Everything seems to be working ok, except homescreen notificatios. It seems like its stuck in some kind of demo mode - it always shows cards like "Drive to hoover dam", "Weather in Las Vegas" and recent call from (650) 253-0000 (but clicking on it will open up dialer and start dialing my real recent call). Receiving notifications from hangouts seems to be working ok though.
I've tried reseting headunit to factory settings, clearing AA data, cache, uninstalling it, clearing play store cache, reinstalling google app, enabling/disabling now cards, but nothing seems to be working. I'm always stuck with the same cards on home screen no matter what.
I've also noticed that the night mode in google maps is not working (it's always in day mode) but if I unplug phone and open maps, they switch to night mode without problem. Also I can use the phone normally even when plugged in and running AA on headunit (no black screen with AA logo).
I would appreciate any help, I've tried googling but haven't found anything related to this issue.
Hi,
I had been using Android Auto with a Huawei P8 lite. It never crashed, but only the response times where a bit sluggish.
I got a brand new Samsung 5 Neo, and after setting up the phone, there was immediately an update to Marshmallow.
When I started using Android Auto, I was pleased to see that the overall experience was faster and better than my Huawei.
But for some reason, during (longer) drives, my Spotify (and Google Music), would crash in the middle of a song. (first a stutter, it could happen after two songs, five songs, there is no logic in it). After it crashes, Google Maps becomes unresponsive. The only thing that helps is disconnecting the cable.
After reading the web, I learned that it could have been because of the marshmallow update.
So after trying all the usual fixes (rebooting phone before using Android Auto, keep data always alive, etc), I decided to downgrade to Android 5.0.
At first sight, I thought everything was solved, but after a few days, the exact same problem started to appear
I will now try to clear the app cache, and reboot the phone each time, but I'm a bit dissapointed that it doens't work as it's supposed to work.
Any tips, remarks are welcome.
Downgrading to Android 5 didn't help, so I flashed it to a version of Android 6.
Magically the issue got away. And interesting fact, after a few days without any problem, a song started to stutter (I thought "not again"), but there was a message on android auto that said: "no internet connection", and the song paused (without the whole head unit crashing). Interesting enough, the whole playlist is available offline on my phone. So I guess, it's some sort of background data the music app needs (maybe the syncing to last.fm), that caused the issue. But glad, for some reason in this build, they handle the exception better.
Downgrading to Android 5 didn't help, so I flashed it to a version of Android 6.
Magically the issue got away. And interesting fact, after a few days without any problem, a song started to stutter (I thought "not again"), but there was a message on android auto that said: "no internet connection", and the song paused (without the whole head unit crashing). Interesting enough, the whole playlist is available offline on my phone. So I guess, it's some sort of background data the music app needs (maybe the syncing to last.fm), that caused the issue. But glad, for some reason in this build, they handle the exception better.
I've been running Lineage 13 for 6 months, but the phone mysteriously got into a boot loop yesterday, so I had clear the local data and re-install the apps from the Playstore
However I found that every time I installed the nRFToolbox app (by Nordic Semiconductors) (Who are a reputable company), that when the App installed, it crashed a load of internal OS services e.g. PlayServices and all sorts of Google services.
If I rebooted the phone it appeared to work OK, but if I went into the "Apps" in Settings, the phone hung again, and I had to reboot it.
I tried updating to the latest unofficial Lineage 13, but that didnt help, so I've now installed the official Lineage 14, and this seems to have solved the problem.
But I don't quite see how a single app can kill so many core services, and I prefer to stay on Android 6 (Lineage 13), because of XPosed and specifically XPrivacy.
(BTW. I know XPosed is now supposed to work on Android 7, but I didnt think XPrivacy will every get ported to work with the updated version of Xposed - at least according to the developer)
Does anyone have any insight into why this app can hang the phone
I don't know, why this APP makes your phone crash, but i had similar problems when installing greenifys latest app and two days ago, i updated some apps ending in bootloops.... I am using unofficial Lineage 13 with xposed and xprivacy too
I run stock OS but have this same issue when updating any big and heavy apps such as Snapchat, Google app and FB Messenger for the past 6 months at least. The app starts to update but then will crash in the installing phase often giving an error such as "503 can't be updated", at which point multiple Google services will crash endlessly the only way to stop the crash is hold down power to force the phone to reboot.
I have reset the phone several times but after setting up the phone and updating all the apps the first update to one of those apps the issue happens again (the app always installs from scratch ok it's only it's updates that cause it)
A sort of fix I have been using (because it doesn't 100% always work) is when you see an update for the app you know will cause the crash first update all the other apps manually leaving only the problem app, then close all apps go to Settings > Storage & USB > Internal storage and clear the Cached data, then power cycle the phone, let the phone boot and complete all it's background tasks it does after booting, then open Play Store and click Update on the offending app then put the phone down and leave it until the app either updates or causes the crashes. If this doesn't work then waiting 24 hours and doing the same steps seems to work.
I am certain it comes from either an app update (probably from Play services or the Play Store app) or maybe from having the phone encrypted which does make the phone run slower especially over time. (May or may not be related but I've noticed on my phone if I factory reset it then after setting it up and updating all the apps I try to encrypt the phone the phone will 'break' and will boot loop forcing a reset from the boot loader, however if I set up the phone, don't update any apps then encrypt it completes successfully, all the apps will then update ok and the phone then functions as you would expect)
All in all this issue is incredibly frustrating!
I've had this happen in numerous GM Vehicles from 2016-2018 Chevrolet, Cadillac, GMC units with AA.
While using Waze or Maps I can run fin 90 percent of the time
While using the above and a music source like I heart or Stitcher I get frequent crashes. My phone will reboot. But when it reboots, I dont have bluetooth connectivity. I have to unplug the phone, Reboot a second time and pluf it back in.
This is annoying and hope there is a solution
Im running the latest versions of Apps on my Galaxy S8 with a Samsung Data cable that came with my phone.
I was recently using an oppo r7sf with lineageos installed and had similar problems. Spontaneous Communications error 12 but no reboot. AA would crash on the head unit and I'd have to reboot in order to get it working properly. Tried many many things but in the end got a new phone and havent had an issue since.
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.