recently android auto seems to be running extremely slow. I am running it on a S7 flat and connecting it to ford edge sync. Its takes forever to get on the head unit, and opening maps and everything else takes for ever. If i try to use the phone minimizing the back anriod auto screen all the apps are running just as slow. This want the case before. i am not sure if it happened after one the andriod auto app updates.
i don't remember this being an issue in the past. The phone has no speed issues when its not connected. Has anyone else noticed this or have any suggestions?
Related
-Edit-
Looks like i solved the problem.
I removed and added my exchange account and now everything seems fine.
-Edit-
Yesterday i updated my SGS yo Android 2.2 and after doing that the phone is so slow i can hardly use it.
My phone hasn't been problematically slow on 2.1, small lags here and there but over all performing good. Examples of the issues are the alarm app hanging and eventually crashing upon setting an alarm, LauncherPro crashing after unlocking.
When typing something in to Google or any other web page it takes forever for the keyboard to appear. Opening the email app also takes very long and sometimes crashes.
The crashing applies to all software that is slow, now and then it crashes. Before the update i hardly ever experienced crashing, now it happens 10 times + a day.
The phone is not rooted and i haven't done anything but use the official update through kies.
I'm running Juice Defender and Advanced Task Manager.
Any feedback is appreciated.
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.
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
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'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.