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.
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
Hi all,
So I recently received a replacement S6 (because of a camera vibrating issue). Thankfully that issue is fixed, but what I've come to realize is that whenever I listen to podcasts, my phone would randomly rewind or fast-forward what I am currently listening to on its own. It took me a day to realize I wasn't crazy.
For example:
While listening to a podcast using Podcast Addict or PodBean, audio would randomly repeat the last 5 seconds, or skip forwards 5 seconds. I tried multiple stations, apps, and even kept the screen on to watch for it to happen. I thought it could possibly be my phone inputting commands on its own, so I watched and noticed Podbean only has a R/FF option for 30 seconds, yet it still does it in shorter increments.
Questions:
1. Has anyone experienced this before?
2. Is there any way to for the device to trigger a toast when a command is issued?
3. Would a keylogger work to find out what's happening? (I don't know..)
4. Should I get another device? Maybe this is why my current device was returned?
Currently on:
Galaxy S6 Replacement Device
Stock S6 MM 6.0.1
Having same issue.
I am having the same issue I started to notice it right after I updated to Marshmallow 6.0.1. Im using Pocket Casts as my podcast app. I have not found any fixes, I thought I was the only one with this kind of issue
Hello all,
I have the 960U1 US Unlocked version of the Note 9 I've had since Day 1 release of last August. It's quite the powerhouse of a phone, and has everything of what you want in a smartphone. I was aggravated by how late the Pie update came, but I never expected how many issues came along with that changed the user experience since Oreo. After updating to Pie, I did a factory reset for a clean run but then I ran into these following issues:
Download, installing, and uninstalling apps from the Play store: I've tried to download apps, which get stuck at 99% or 100%, but then just hangs there to not install. Same thing with uninstalling. It'll say uninstall for an abnormally long time.
GPS issues: I travel frequently on weekends. Sometimes I would like to pull up my Google Maps timeline to review where I went and at what times. One weekend, I went out of town 3 hours away from home and yet my timeline showed me saying I stayed all day and night where my Home location is. Map guidance still worked, but it still showed me that my "current location" was still being at home.
Bluetooth Power indicator pop up: This is a recent issue I found that other Samsung users in other forums encountered as well. I have a Sony WI-1000x Bluetooth neckband that does extremely well for all the bells and whistles it does. I've noticed that after I factory reset again after experiencing the previous 2 issues to get them fixed, there is a pop up that keeps appearing every 10 or so seconds that tell me my headset is battery at 100%. I have found no way of disabling that, and I had to unpair/pair my headset as well as clear Bluetooth data in System App settings to try and get rid of it. Good thing it hasn't been doing that after several tries, but now there is another issue with BT.
Bluetooth notification sound output: I've noticed when my BT is connected, I don't hear notifications from my text messaging app, e-mail, Arlo, and social media apps. I've checked to see that my Sound settings are all up and running as it should be. Then I went to try and play a notification sound, and nothing came out of my phone speakers. It only played through the headset itself, and that's an annoyance as I don't wear them all the time in my ear unless I'm using it for phone calls or listening to media. It seems to be an Android Pie issue and I have yet to find a permanent solution as this wasn't an issue before on Oreo. The only workaround I've found is using the SmartThings Audio Output toolbar in the Notifications drop down and select to play Media from my device. The notification sounds work then, and I can still answer calls through my headset. But it's a dumb issue that I have to manually set this whenever I want to go back to listening media.
The Note 9 is a great phone despite the small shortcomings it had before the Pie update. Now it's after the Pie update, all these issues come up and I don't understand what happened in what Samsung did. I'm almost tempted in calling Samsung to ask if my phone just somehow became defective, but I don't want to have something done and they send me some refurbished model when I kept my phone in near mint condition. What are your guys' thoughts about the issues I've had and what solutions would you suggest?
GigaSPX said:
Hello all,
I have the 960U1 US Unlocked version of the Note 9 I've had since Day 1 release of last August. It's quite the powerhouse of a phone, and has everything of what you want in a smartphone. I was aggravated by how late the Pie update came, but I never expected how many issues came along with that changed the user experience since Oreo. After updating to Pie, I did a factory reset for a clean run but then I ran into these following issues:
Download, installing, and uninstalling apps from the Play store: I've tried to download apps, which get stuck at 99% or 100%, but then just hangs there to not install. Same thing with uninstalling. It'll say uninstall for an abnormally long time.
GPS issues: I travel frequently on weekends. Sometimes I would like to pull up my Google Maps timeline to review where I went and at what times. One weekend, I went out of town 3 hours away from home and yet my timeline showed me saying I stayed all day and night where my Home location is. Map guidance still worked, but it still showed me that my "current location" was still being at home.
Bluetooth Power indicator pop up: This is a recent issue I found that other Samsung users in other forums encountered as well. I have a Sony WI-1000x Bluetooth neckband that does extremely well for all the bells and whistles it does. I've noticed that after I factory reset again after experiencing the previous 2 issues to get them fixed, there is a pop up that keeps appearing every 10 or so seconds that tell me my headset is battery at 100%. I have found no way of disabling that, and I had to unpair/pair my headset as well as clear Bluetooth data in System App settings to try and get rid of it. Good thing it hasn't been doing that after several tries, but now there is another issue with BT.
Bluetooth notification sound output: I've noticed when my BT is connected, I don't hear notifications from my text messaging app, e-mail, Arlo, and social media apps. I've checked to see that my Sound settings are all up and running as it should be. Then I went to try and play a notification sound, and nothing came out of my phone speakers. It only played through the headset itself, and that's an annoyance as I don't wear them all the time in my ear unless I'm using it for phone calls or listening to media. It seems to be an Android Pie issue and I have yet to find a permanent solution as this wasn't an issue before on Oreo. The only workaround I've found is using the SmartThings Audio Output toolbar in the Notifications drop down and select to play Media from my device. The notification sounds work then, and I can still answer calls through my headset. But it's a dumb issue that I have to manually set this whenever I want to go back to listening media.
The Note 9 is a great phone despite the small shortcomings it had before the Pie update. Now it's after the Pie update, all these issues come up and I don't understand what happened in what Samsung did. I'm almost tempted in calling Samsung to ask if my phone just somehow became defective, but I don't want to have something done and they send me some refurbished model when I kept my phone in near mint condition. What are your guys' thoughts about the issues I've had and what solutions would you suggest?
Click to expand...
Click to collapse
I had issues with android pie sprint model. Ended up flashing android oreo back and no more issues. Theirs guides out their all u need to do is download the correct files and flash file ,real easy process just follow instructions. Do your research and ull be good
GigaSPX said:
...
I have the 960U1 US Unlocked version of the Note 9...
The Note 9 is a great phone despite the small shortcomings it had before the Pie update...
What are your guys' thoughts about the issues I've had and what solutions would you suggest?
Click to expand...
Click to collapse
timex300 said:
I had issues with android pie sprint model. Ended up flashing android oreo back and no more issues. Theirs guides out their all u need to do is download the correct files and flash file ,real easy process just follow instructions. Do your research and ull be good
Click to expand...
Click to collapse
Hey GigaSPX, noting you have a 960U1 US Unlocked, I've been working on this step-by-step for a 960U1:
Confirm These Steps to Downgrade US Unlocked SM-N960U1 from Pie to Oreo
If you decide to go this route, take a look and share your experience.
Thanks for the links and guide tips to downgrade to Oreo, but I enjoy One UI too much to give up on that user experience. I still have my Note 8 and I know it benefited significantly from the pie update to have it last all day unlike before on Oreo.
GigaSPX said:
Thanks for the links and guide tips to downgrade to Oreo, but I enjoy One UI too much to give up on that user experience. I still have my Note 8 and I know it benefited significantly from the pie update to have it last all day unlike before on Oreo.
Click to expand...
Click to collapse
You're welcome.
Good to know about your Pie experience on your Note 8.
Basically since the introduction of emui 9, I have add the issue that the google news feed (swipe left at home screen) will close while scrolling down the article list, or whilst reading an article.
With version 9, it was often enough to be annoying, but not so terrible that I avoided to use it.
With EMUI 10, I normally avoid to look at the google feed at all since I know it will just close at any time.
It could be after 1 minute, or 30 seconds. However, it will always close at some point. I have set every google app to manual manage in the battery app.
Does anyone else have an issue with this crap box phone just randomly decided to close an app? Any idea how to prevent it?
At the moment It is hard to overstate how much I hate this phone.
I have the same problem. It started happening after the update to EMUI 10...
I noticed today, it also does it with the google store.
My god what a crap phone. I don't understand how Huawei was able to make something as good as the nexus 6P and then come up with ****-show EMUI at the same time. Had I not dropped my already cracked phone into water, thus killing it, I would just go back to the old nexus until December when it's time for a new contract.
I cannot imagine any situation where I would ever consider to another Huawei product.
pablo_max said:
Basically since the introduction of emui 9, I have add the issue that the google news feed (swipe left at home screen) will close while scrolling down the article list, or whilst reading an article.
With version 9, it was often enough to be annoying, but not so terrible that I avoided to use it.
With EMUI 10, I normally avoid to look at the google feed at all since I know it will just close at any time.
It could be after 1 minute, or 30 seconds. However, it will always close at some point. I have set every google app to manual manage in the battery app.
Does anyone else have an issue with this crap box phone just randomly decided to close an app? Any idea how to prevent it?
At the moment It is hard to overstate how much I hate this phone.
Click to expand...
Click to collapse
So I am aware that this reply comes almost a year later, but this problem had me searching the entire web for months, only for me to give up. I have a Huawei Y9 (2019) with EMUI 9.1 that did the same. So the obvious solution i tried was to go to settings->apps->google and clear data and clear cache. This temporarily fixed it for a few hours before going back to the same crashing issue. I even tried turning the gestures on and off but that did not help either. Now I had a lot of documents , high resolution images and videos in my phone which occupied almost 88% of my 64gb of internal storage. So I recently decided to back up my data to an external hard drive and removed a lot of the large files from my phone, dropping my occupied storage to about 78% and the very next moment, google feed stopped crashing at all. There were no recent updates and no other changes were made to the phone except freeing up some space. I guess its functionality requires a good amount of free space?
So Im not sure if this will work for anyone else. But it did for me. And so I just want to reply here in case someone else is still facing the exact same problem or still uses their old Huawei. Try freeing up some storage space in your phone if it is full well above 85%. Try dropping it down to 80% or below and hopefully it will fix the issue if nothing else did.
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.