Anyone there with do not disturb mode bug on android N ?
Me and many other users with a smartwatch + a Nexus phone (maybe it's a nougat bug) have this bug. The phone , which in my case is a nexus 6 ,enter the do not disturb mode ,and under the volume slider tells me that has been triggered by wear. I'm trying to isolate the problem,so if there's anyone with the same bug maybe we can find a solution.
I think it got fixed server side or via Google play services update. This bug it's gone away the same as it started by itself. I m on pure nexus 7.1.1 on nexus 6, and 3 my friends never got this bug . Two of them are on note 4 official 6.1.1 + g watch , one is on one+ one official 5.1.1 and a g watch too. No one with this bug??? Seriously? I saw this with the Bluetooth turning off bug ,in many forums related to pixels ,nexus 6 ,6p and 5x . Since 2 days im back to the experience of my nexus 5 pure nexus 6.1.1 ,no bug at all neither with Bluetooth, g watch, phone and Bluetooth car stereo (parrot asteroid classic)
Related
Wondering if anyone has issues with Bluetooth turning off/on by itself and sometimes it will fully crash requiring a reboot to fix.
Situation 1) I have a Sony smartband (BLE) connected and works perfectly unless I'm near my wife which happens to have a Fitbit (BLE) also. When we are near, bluetooth will turn itself off/on repeatedly and my smartband reports disconnected/connected in notifications drop down (the only reason I actually noticed it though) but will eventually stop turning on/off and stay connected. Now in this situation bluetooth doesn't actually stay crashed requiring a reboot to fix it, however situation 2 does.
Situation 2) Picked up 2 pairs of Soundbeats HV-800 BLE headphones from amazon (one for the wife). When I connect them, bluetooth will turn itself on/off about 8 times in a row and then stop, only way to turn bluetooth back on is to restart the phone. Now if I turn off my smartband, stay out of range of any other BLE devices (wifes fitbit for example) and restart my phone, bluetooth stays on with the headset connected. Within moments of turning my smartband back on though or moving in range of wifes fitbit, bluetooth will start crashing turning on/off again. This also happens at work when I'm around someone with another BLE device.
Here's what I've figured out so far
1) Happens on wifes G3 which is stock and not rooted (mine is rooted) so rooting does not appear to be a cause
2) Happens with Fitbit and Smartband so it does not appear to be the particular device that causes it
3) Happens with both headsets, although with situation 1, the headset is not even relevant.
4) Works fine as long as there is not multiple BLE devices in range after a reboot until more BLE devices come into range
5) These issues don't exist with my Moto G (4.4.4), Moto X (4.4.4), or my Galaxy Nexus (Shiny 4.4.4). Infact just as a test, I linked my smartband, the wife's fitbit, and headset to my Moto G all at the same time and no issues.
With all the above it appears to be specifically related to the quantity of BLE devices the G3 can see for a given amount of time. With that in mind it lead me to thinking it's related to the bug listed HERE but I"m not positive. I did try the Bluetooth Crash Resolver app mentioned and while it does pick up the crashes, it does not fix/resolve them.
Has anyone else ran into this yet and/or found a fix? Unless I'm totally off on thinking it's the 4.4.2 bug, this may just continue to be a problem until 4.4.4 for the G3 is released or a patched upgrade of the current 4.4.2 is put out by LG.
Thoughts?
i have an lg lucky that is running android 4.4.2 as per the thread title
my issue is the bluetooth keeps overloading and disconnecting all of my devices, i have tried a cheap Bluetooth headset, iv tried a moga, and a ps4 controller as to test weather it was the headset or not
the headset after about 10 mins will start crackling for no reason, and the microphone will not work at all
all other devices instantly disconnect after 10-20 secs, i sent my phone back and got a new one, of the same model only to have the same issues
does anyone know how to fix this?
I bought a new kia optima sports wagon which was working fine with a Samsung note 3 on lollipop. I have since got an elephone p9000 which runs marshmallow out of the box, since then I am getting problems with android auto connectivity, mostly android auto will connect but it will often just bomb out and display communication error 6 on the phones screen, mainly when I try and play media using google music, also WhatsApp is not sending messages on,cwhen I press the voice command on steering wheel I can say WhatsApp and it will ask who I want to chat with, it then let's me say who I want to chat with and asks for the message which it then plays back to me and asks if I want to send it, I reply send and it says it is done but it doesn't actually get sent.
Not sure where the prpblem might lay. The new usb C type cable (tried a different one), lateste android mm update has screwed something, maybe the android auto on car infotainment system isnt compatible with update.
Any one else experiencing issues ?
P9000 screwing up with Android Auto......????
Same problem......does P9000 (6.0) have the 'ability' to properly run Android Auto...?
Hey all, I recently traded in my V20 for a new G6.
I've got a 2016 Honda Civic and am having serious issues with Android Auto. Every time i plug in, it will play audio for about 10 minutes and then disconnect. Once I reconnect it will be about 10 seconds to 1 minute before it disconnects again if it connects at all. After clearing app data in AA i usually can get it to stay for about 10 minutes and then it does it again.
I know it's not the cable because i've tested both the cable that i was using with my v20 and also the one that came as a charging cable for the g6.
I have tried turning on USB debugging and also have tried all three USB connection modes.
This is super frustrating especially because for some reason (even though my v20 played audio just fine) the g6 and civic combo will only connect bluetooth for voice and not for media (without crashing.)
Anyone else experience this??
Sorry I can't help. It works fine on my Tesla.
I have what might be a similar issue. I don't get disconnects but on my 2017 Chevy Colorado, if I turn off the truck with the phone still connected to USB (for example, a quick stop at a gas station), after I restart the truck, G6 audio doesn't work at all. I have to reboot. I've tried force-stopping Waze, Pandora, and Android Auto; disconnecting and reconnecting USB; and even going into airplane mode (my phone hitchhikes on the truck's WiFi)... nothing works except a reboot. Literally the only thing I don't like about the G6.
Android Auto was flawless on my previous Nexus 6P ... but it went into bootloop and became a $700 paperweight.
I'm having similar issues with my G6 and AAuto in a 17Civic Hatchback My 1st drive of the day is usually ok But 2nd and thereafter drives no matter how much time in between The radio or music play pauses randomly whether it's a music player on Bluetooth sub Amazon music Pandora even Sirius radio I brought it in for service 4 times they tell me it's the phone or settings on the phone finally got a tech to see what's going on long story shorter they just replaced the entire radio/android system with latest android update well guess what same old same old still doing it very frustrating I had an LG G3 prior and for the most part no issues So is it a G6 thing Android Auto thing or Honda thing??? I also tried 4 or 5 different music player apps that are compatible with AA
When pressing the play button on any music player while connected to my 2017 Civic, it instantly crashes the bluetooth application. Oddly enough, for some reason the YouTube Music application can play multiple tracks without issue as long as you're using a playlist and keeping the screen off while doing so. I don't think that Android Auto is the problem, because it works perfectly fine via USB port and always allows me to interface with the application on my Civic's touchscreen panel. However, I am glad to see that I'm not the only one with this issue so maybe there will be a fix hopefully somewhere down the line.
Sent from my VS988 using Tapatalk
Hey guys, I would like to start a discussion about the Android Auto and it's issues on the latest ROMs for k20/9t pro. For instance I find it barely working on latest pixel experience but the January version of this rom is not affected.
I consider Android auto as must be as well as correct notification that's why I have chosen custom rom.. but now I'm at the crossroads.
What seems to be a problem? Is there any hope for positive future implementation of this app?
I believe there were no topics like this If so let me know.
I don't know why xiaomi phones have such problems with android auto, in custom roms it doesn't work also in all xiaomi roms (global, stable, beta, eu, china...) If you enable dual app it stop working and it does that in every xiaomi phone(to be exact mi mix 3, mi8, k20 pro is the same scenario)
It's not Xiaomi phone's fault , android auto is not working in many other custom , I had Google pixel 2 xl as well, and it was running on havoc os and still android auto were not working in that model.
It's google problem poor programators like in M$
Sometimes, when I plug the phone, media controls (on steering wheel) don't work, and Spotify doesn't show on screen, and I need to unplug and plug again the phone for getting them to work.
Except this, I don't have other problems.
Sorry for the off-topic, but how about MirrorLink? Is it still only compatible with Samsung, Sony, and Nokia phones? It would be great to be able to mirror screen to my 10" in-car screen. My last 3-4 phones had luck only with Android Auto, and some of them barely worked. 2020, and there's still no proper communication standard (wireless preferably) between Android phones and cars.