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
Related
Has anyone else had an issue on the S6 Edge with the Pandora app not responding? Nothing I have tried has stopped the issue. Sometimes it will play for a while, but as soon as I turn my screen on it will freeze up, slow down my whole phone and then eventually just either stop running altogether or will display an ANR. It was doing this when I had the phone completely stock and still does it after I have rooted.
I have uninstalled, cleared application cache, cleared phone cache, changed settings with data and nothing will fix it.
Any insight would be great.
Thanks
I also wanted to report I have the same issue but I have the HTC M8. I don't think its specific to the S6.
Zabalba said:
I also wanted to report I have the same issue but I have the HTC M8. I don't think its specific to the S6.
Click to expand...
Click to collapse
chiming in from VZW G3, can confirm it is not limited to only the s6. I had freezing on both 5.1.1 AOSP and 5.0.2 stock rooted.
If you’re acquiring issues for the S6 Edge with the Pandora application certainly not replying, often times quitting your current application, re-opening that and also going back to http://www.pandora.com for your best suggestions.
I have had an issue when running my Pandora as well. It makes a crackling sound if I'm scrolling or touching the screen while it plays and then after a few of those crackles it just starts emitting this horrible high pitched squeal until I hit the back button enough times. Even then if any sound comes through the phone like a notification or incoming call, it starts again until I reboot it. I've had the phone for less than 24 hours...
S6 here and Pandora problems as well...just stops responding and I get the wait, report or OK prompt.
Thing is, it worked fine at first and my phone had not been updated, so I'm assuming at some point Pandora updated and fubard it.
Hope there's a fix soon!
I have this issue as well on a Nexus 6 pretty much every time I use Pandora. I've never had a problem in the past on any prior phone. I haven't seen many other people talking about this so I have kind of assumed it's related to Lollipop and having a lot of apps installed or something (worth noting even if I remove all apps from recents and reboot it still happens).
So frustrating. At least I'm not alone.
My Nexus 6 keeps forgetting my Bluetooth pairs. I'll wake up and notice that my pairs are gone. Which is an annoyance with my car and Android Wear watch. It happened once before but then when it happened last night I know there is an issue. It started after I upgraded to Marshmallow. I'm running the MRA58R build. Any ideas?
I have the same issue...ever since marshmallow...both 6.0.0 official and 6.0.1 official, both times before installs the phone was wiped...but never the less it always forgets my bluetooth pairs
it seems to correlate to when the phone fully dies. If the phone fully dies 1-2 out of 5 times it will boot back up without the bluetooth pairings.
Also if I don't pair my Wear watch(original 360) this does not seem to happen either
I'm having this issue as well. My phone will randomly ask to pair with my car, even though it's been paired already. And sometimes it will just ask me to allow it to share Messaging, which was also already set. It's frustrating. I've only noticed it with Marshmallow.
For me it doesn't seem to correlate with charge level.
Having the same problem here and now that you mention it, it does seem to happen when it fully dies. Until someone comes up with a solution I'm going to see about backing them up and restore if it happens again.
Allowing your phone to completely die is a bad idea. The sudden shut down is what is corrupting it.
Also restoring that type of system data is just asking for other random issues, also not a great idea.
While I run an AOSP based rom I have never had my device forget any of my 5 BT pairings.
I agree don't let phone die.
Also if low battery plays a role (before phone dies), it could be related to battery saver features that can activate at low batteries level. (Adjustable in settings)
For the android wear app, turn off battery optimization (to prevent it from being interrupted by doze. )
I have had zero disconnection between my n6 and my moto 360 g1 android wear watch in the last month.
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
My phone has done this now twice in three days on N Preview 3. Has anyone found a solution?
mine does it too. but it will forget ALL my paired devices. it's pretty annoying
This is happening to me as well. Nexus 6 is forgetting all paired bluetooth devices.
Most annoying is the Android Wear issue because I've been having to factory reset the watch to get it to pair again. Some of this might be the watch because I'm running a Samsung Gear 2 with Android Wear but I also have several other devices that I have to repair every time.
Also seems to correlate with the battery dying.
There has to be a common bug. As all my devices have no issue remembering the pairing. Mind you I also dont pair to my car.
Also keep in mind that it was found long ago that OEM put in lists of cars that it will not work with in their roms. We found it on samsung devices years ago where it would block all connections to BMW, Audi and a few others.
N6 running 6.0.1 (no root)
This just started happening to me yesterday but has happened twice so far in two days. My phone has not died as seems to be a symptom for others here. It did get below 10% today but I charged it up without issue. it wasn't until several hours later that it wiped all of its paired devices. below is a list of my paired devices:
Samsung ATIV book 8 (windows 10)
UE Mobile BoomBox
Moto360 2nd Gen
2014 Infiniti Q50
2015 Nissan Murano
After it wiped everything yesterday I re-paired the following:
Samsung ATIV book 8
Infiniti Q50
Moto 360
After the first wipe today I paired the watch and the car.
If anyone has any ideas I would be grateful. This is a GIANT PIA!
Does not look like there is a solution to this forthcoming... is there anyone with this problem that's recently updated to N? And has it gone away? I get this usually after a forced reboot... all bt settings gone. Totally a problem.
Any update on this. I think it started happening after I updated to 7 and then went back to 6 after having battery issues?
rkshack
Giant PIA
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5. I drive a lot for work, and need my phone paired to a JVC headunit (listed as JVC UNIT on my phone) in my van so I can take phone calls handsfree, and listen to podcasts. Every now and again, maybe once a day, with no rhyme or reason that I can discern, I get into the van and notice that my phone is not paired. It's a pain to have to pull over and re-pair the phone, and then set it up a a trusted bluetooth device again (so as to avoid entering my passcode whenever unlocking the screen).
- Definitely nothing to do with battery levels. My phone is normally fully charged and plugged in to a charger.
- I don't lose all paired devices, as my UE Boom 2 (not often used) is still listed as a paired device, whereas the JVC UNIT drops off fairly often.
Please could someone sort this issue out! It sounds like quite a few people are experiencing it.
thanks,
Phil
Phil in NZ said:
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5.
Click to expand...
Click to collapse
Not likely to get sorted for your phone in this N6 thread. [emoji6]
I am on Android 11 and it still happens to me, my car pairing is being forgotten from time to time. Happens to any of you?
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'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.
Good day everyone, I'm having a really frustrating problem since I got my phone a month ago. I hope I can get some help here.
From day 1 I've had issues with network on my WiFi. No issues connecting to it, no issues using the internet, let me explain. I first noticed it on MIUI Themes. That was the first thing I went into after setting up my phone. It kept saying "can't connect to network". I figured it was a bug and will be fixed in the 12.5 update (spoiler alert: it didn't). Then I started to notice during setting up of my accounts, discord, reddit, etc. that the login was incredible slow the first time. It would just keep loading when I hit next. Not long after, I downloaded a game and it refused to update saying "can't connect to server". I had to start the process with my data then switch back to WiFi. For clarity, once I'm in the game itself there's no issues, the stability never drops, I never lag, etc.
It became truly evident it wasn't isolated incidents when I would open one of my online shopping apps. It loads the main screen instantly but when I switch the tab to see notifications, the page would load but the notifications would take up to 30 seconds to load. If I clicked on it, the next page would take another 30 seconds to load. Since I've used this app on my previous phone/ipad on the same WiFi I could tell there was something wrong. It should be instant. I opened up MI Community app and I kid you not, it must have taken me 10 - 15 minutes to create an account with all the loading/lag. Every single time I open the app, it takes at least 40 seconds to a minute to load with other pages lagging as well.
I started this long process of trying everything I could find that talks about it which was not much and usually about older phones. I tried everything I could find except factory reset (some have said it doesn't fix it after trying it themselves). I tried all the WiFi adjustments, traffic mode, off private DNS, developer mode options, and obviously reset networks/router/reboot multiple times.
After spending a couple of hours trying to find every mention of this whether it's Youtube, websites or Reddit and trying them (I would switch them back to default after testing the suggestions as they didn't work), my PC started giving WiFi problems. It NEVER gives problems but I figured maybe it was due to the turning on/off router multiple times. I was so frustrated, I was like, screw this I'm done.
I restarted my PC and switched to my PS4 (which runs on the same WiFi with no issues ever in 3 years). As my PS4 booted up, I picked up my phone to check the delivery status on my shopping app and BAAM! For the first time since I downloaded the app, my notifications appeared instantly like it should, the next page loaded immediately. I was like, hold up... I went into MI Community app and BOOM! it loaded immediately, I was shook. One final test, MIUI Themes that has never worked properly since day 1 with its constant "can't connect to network". BLAAM! Every page, instant, clean sweet speed. It felt like a whole new phone, like the new phone that I was supposed to feel all along.
I enjoyed a good 6 hours of bliss, constantly checking my shopping status just as an excuse to enjoy witnessing the speed. He giveth and then he taketh away and as luck would have it, there was a power outage midday. When the power was back on and the WiFi was up, we were back to the suffering. I tried to restart my PC as that was the key trigger and it worked for about a minute and then was the end of it. No amount of shutting down / restarting PC/router fixed it again.
There's something blocking the connection between my router and phone I believe. I figured the initial restart PC fix stopped the connection to the PC and gave the priority to my phone, if you will. That's rubbish I know because my WiFi runs on 4 other devices and never lags.
I'm no tech expert, in fact, I'm the opposite of that, it's embarrassing. I hope y'all can see something I'm unaware of and guide me. I'm certain the phone isn't defective and my WiFi is fine on every other device not to mention it ran flawlessly for 6 hours while other devices were also using the same WiFi.
If you've read this far, thank you very much. I apologize the post is very long, I wanted to get everything in so it paints a clear picture of the issue. I'll add a TLDR just incase.
TLDR: WiFi issues from day 1 in 2/3 of apps mostly with initial connections. 1 month later a chance restart of my PC fixed it. Power outage later that day, problem returned.
T