Hi
Does anyone know where / how I can find what's making my Android Auto crash?
I've experienced this across 2 cars and tested with another phone - it's something I have installed on my phone but I can't figure out what.
I can go 20 minutes sometimes with no issue. Other times it can crash a couple of times in a short space of time.
What happens is it simply disconnects as if I've unplugged the phone. Then after 10-20 seconds it comes back.
Any logs or something I can check anywhere to see what's causing it?
Samsung S22 Ultra but I believe I had the issue on S21 Ultra also. As I say I've tried other people's Android phones in my car and they work fine.
Related
Anyone else with this phone using Android Auto? I've been having issues with my Kenwood DDX9207S head unit where it sometimes doesn't initialize AA properly, is more often than not very laggy, etc. Sometimes it runs smoothly, as I would expect for a phone of this class with these specs, but it's getting pretty frustrating. I've tried clearing Android Auto's data/cache and uninstalling and reinstalling it, but nothing seems to help. I'm not sure if it's an AA issue, phone issue, or possibly the head unit (very doubtful, but the screen sometimes stays stuck on AA after disconnecting the phone). I can sometimes resolve the issue simply by unplugging and replugging the phone in, sometimes I have to kill all app processes, and sometimes I have to flat out reboot the phone.
EDIT:
Did some testing last night and this morning during my commute (I sit in a lot of traffic, don't worry) and found a possible culprit: Settings. I looked at the memory usage for apps, and without fail, everything was using very little memory except Settings, which was eating 100-300mbs. Killing the process instantly made AA responsive again, but within 5-10 minutes, I was seeing lag again, and Settings was building up memory usage. I'm going to perform a factory reset on the phone today to see if that alleviates the issue.
EDIT II:
After factory resetting the phone, I'm not seeing issues, SO FAR, with AA. The settings thing wasn't the right target. I still get high RAM numbers with it regardless, and I see the same thing on my Tab S2, so that's obviously not what was causing the issue. The difference *might* be that I disabled a lot of AT&T bloatware before, and in doing so might have messed something up. I'm leaving everything enabled right now, so we'll see how this goes. I only have one car ride under my belt so far, so it's not a very scientific comparison.
EDIT III:
Ran into the exact same issues earlier this afternoon. Plugged the phone in, got the "Accept" screen on my head unit, and then blank. I looked at my phone and realized that AA didn't actually launch, so I unplugged it and plugged it back in. It launched that time, but the lag was there. I can take up to 10 seconds for AA to register a touch, and Maps freezes up constantly for 10 seconds or so before trying to catch up (it usually doesn't catch all the way up before it freezes again). This makes AA more or less unusable for me. I can't find anyone else out there that has had these issues with AA and this phone, so I'm unsure of what the issue actually is. The only difference between last night and today is that last night I was listening to podcasts through Pocket Casts, and today I used Audible. I'll do a bit more testing with/without Audible to see if that's the culprit; I know AA support is relatively new on Audible (though it was in the beta for a while). Again, I haven't seen anyone complain of poor AA performance while using Audible, so I don't know if that's the issue. I wish I had a Nexus to test this against to see if its the phone...
Having the same issue it does not connect all the time
Apparently this issue affects some Note 8 users on Oreo as well. I did a factory reset and it didn't fix it.
Has anyone solved this problem? It makes the phone unusable with Android Auto. I'm actually going to get a different phone if I can't fix it.
I have similiaar issues. Luckily not my car though.
Mine will drop connection just like yours does but with headphones.
There is a thread I joined on the Samsung site: https://us.community.samsung.com/t5...uetooth-turns-off-and-on-randomly/td-p/382246
No answers though. I did see that when my Wear OS watch is connected it makes the issue worse. Sometimes it gets so bad I need to disconnect the watch.
I wonder if anyone has opened a ticket with Google about it?
so have recieved the S10 today
i wont go into the things i like because it is an amazing phone
i just have couple if issues and wondering if anyone else had these and/or have fixes
some apps are crashing - basically open and they instantly force close
specifically: google photos, google home, Netflix
android wear is not finding my watch despite resetting the watch several times, and the watch seeing the phone but not other way around
do wall papers change as well or is it just the lock wall papers that change?
thanks xxx:silly:
tim2london said:
so have recieved the S10 today
i wont go into the things i like because it is an amazing phone
i just have couple if issues and wondering if anyone else had these and/or have fixes
some apps are crashing - basically open and they instantly force close
specifically: google photos, google home, Netflix
android wear is not finding my watch despite resetting the watch several times, and the watch seeing the phone but not other way around
do wall papers change as well or is it just the lock wall papers that change?
thanks xxx:silly:
Click to expand...
Click to collapse
Yes it's a wonderful phone but things can go wrong sometimes. The issues you described are most probably due to some weird setting or app. Try to reset your phone and see
I have the regular S10 and haven't experienced the issues you describe. The thing that caused me the biggest amount of grief was setting up WhatsApp!!
Try a factory reset - if issue persists get it exchanged although it sounds more likely it's a software issue. Good luck, hope you get it sorted.
Yeah I can't get android wear to recognize my android watch either
I also noticed that my LTE speeds are atrocious compared to my previous S8 (both on the same carrier...Sprint).
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.
Hello everyone.
I was using UleFone Power 3 (Android 7.1.1) with my RCD330+ without any problems (on VW Golf Mk6 2011 year).
However, phone became old and started developing issues, so I was forced to buy new one.
A few weeks ago I purchased Realme GT Master Edition which runs Android 11.
However, now I am having problems since day one with the phone and RCD330+.
When using Waze, the display on RCD completely freezes for 30-40 seconds every 3-5 minutes. You can pass a few intersections with Waze still showing you frozen far behind. Everything is frozen - map, speed display, etc.
After ~30-40 seconds, it unfreezes and is displayed all fine again for next 3-5 minutes where it freezes again and all repeats.
Could anyone please help me toubleshoot where the problem is?
Only the phone has changed, no configuration changes were done in RCD330+, USB cable also remained the same.
RCD330+ firmware version 5614
Android Auto version 7.6.621703-release
Waze release 4.82.5.1
Another question - what's the best tool to use to switch off Bluetooth after device is being disconnected from USB?
Thank you
I'm having the same problem and I managed to reduce a little bit the freezing. And don't know if it'd work for you.
Enable developers options and go almost to the bottom, under applications there's an option called "Limite de procesos en segundo plano" which might be something like "Limit backgroud processes" and set it to MAX 4 instead of Standard.
It helped quite a bit. Please let me know if you find something else.