Android Auto works great with my MXPE and Pioneer 4200NEX most of the time. Occasionally and seemingly at random the screen in the HU will go black and display "to use android auto please park your car and check your android phone". I have to unplug and plug back in to fix it, but the error will come back. Anyone else have issues with AA? I'm rooted if that matters.
Related
I know that this question belong in the relevant development forums, but I'm too new to post there.
Bell Canada S4 and after running TW 4.2.2 decided that I wanted to try Kitkat.
Started with the "Gummy" rom and install was fine. Worked well as a daily driver except for Bluetooth with my car (a 2012 Golf TDI). Every 5 minutes or so I will see the car display telling me the phone has been disconnected and then a minute later it reconnects. It would also disconnect mid-call. After some random time of doing this, the Bluetooth will "lock" in the turning on stage. By that I mean that if you go to the Bluetooth settings, it will say Bluetooth is turning on, and never go anywhere or connect. The only way to reset it was to restart the phone. If I was sitting in the car and working with it when it disconnected, I would see a message "Bluetooth Share has stopped" on the phone
Similar experience with Dandriod. Except that instead of locking up trying to turn on Bluetooth, the phone will reboot.
Anybody have any suggestions on where to look? And yes I clean flashed the ROMs, with a wipe cache/davlik after install. I'm liking 4.4 overall, but I need Bluetooth working consistently. The fine for driving with a phone in your hand is something I don't want to pay for.
i all
I have a LG G watch R, i have had this around 10 months, its paired with my Nexus 5.
Over the past year there has been a few occasions where suddenly the "mute phone alerts and calls" option has suddenly stopped working! *Half way through the day all of a sudden id still get the message on my watch but my phone would make a noise too!
Usually i fixed this by uni stalling android wear, resetting the watch back to factory setting and re pairing them..this usually solved the issue until next time....however!
This time it happened again and no matter what i do it wont work! i have the option to mute phone call and alerts but the phone still makes a noise and is not muted! when i toggle the volume bar it used to say before "muted by android wear" but now it does not.
My phone was updated to android 6.0 last week but for the past week its been fine so i doubt it related to that as like i said its done this before on lollipop.
Few more things to note that may be related, if i swipe down in my notifications box it used to say "android wear connected" but thats no longer there, and if i go into the watch and go into settings and bluetooth devices it does not say anything it just says scanning for nearby devices, and i notced once it said nexus 5 disconcerted??
I must stress that i am connected to my phone as all my notifications come through on my watch fine.
Anyone had this or know a fix?
Thanks
Chris*
Did you find a solution?
Same problem here. I have moto x play (no developer edition) unlocked bootloader/rooted/lollipop 5.1 and LG G watch R.
In my case it seems related to Moto Display (Motorola'app similar to ambient display). If I disable it, mute comes back.
I tried to uninstall android wear app, and then installing 1.3 version. No fix.
On reddit I read that it should be the last update of Google play service instead: user restored his phone fixing the problem. I tried to uninstall play service (no factory reset)...no fix
EDIT: Ok I have just found a middle-solution. I downloaded a module for Xposed (True silent Mode), after activation you will not able to receive any vibrations or sounds on your phone, but you'll receive a vibration on your watch instead. It's similar to android wear function, the difference is if you disconnect your watch you have to disable the silent mode on your phone manually. Hoping Google (or Motorola in my case) fixes it soon in the meantime...
Looks like we are not alone: https://productforums.google.com/forum/#!topicsearchin/android-wear/mute
https://productforums.google.com/fo...context-place=topicsearchin/android-wear/mute
I see other reports and see the issue myself where android wear often says that the watch isn't connected anymore while the watch says it is. And voice commands etc. on the watch still works (I guess they go directly through GMS not involving the android wear app itself).
Maybe there is a bug between android wear and the detection of the connected watch that keeps thinking android wear that no watch is connected and then not muting the notifications on the phone.
Do you have the cloud sync enabled? It's in "privacy & personal data". I have.
Hi still have the same issue, and yes my watch thinks it's not connected also
I have tried both cloud synced and un synced
Try putting your watch on charge, then taking it off
It worked for me, you will notice when on charge the ph is connected but notifications are not muted
I think the ph must think the watch is charging...
The latest wear app version fixed it for me.
http://www.apkmirror.com/apk/google...-wear-1-4-0-2470307-gms-android-apk-download/
Hasn't for me
Hello I have a Skyworth Android tv and when I turn it on it gives the error of “Unfortunately HiRMServices has stopped” and I click ok and it’s just keeps popping up over and until I restart the tv a couple of times then it goes away. It’s running android 4.4.2 I was wondering has anyone encounters this or if there is a fix the tv is rooted also or if I can just remove Android period and just use a stick or android box. I think it has something to do with the internet once it’s connected after the boot it doesn’t give me the error just a guess
Workaround
Hey bud. I have been having the same issue with mine. One workaround so you don’t have to keep rebooting and cross your fingers it works is to go to sound settings and put the option for sound only and then the tv backlight turns off and only the speakers stay on. It literally turns off the rest of the tv and kinda puts it on standby until you wake it up. It’s a good workaround until we figure out a fix.
My Galaxy S8 only connects to Uconnect 7" (Abarth 595) after a fresh reboot.
If i disconnect the cable and plug it in again, the Uconnect no longer detects an Android Auto enabled phone, and the phone prompts me with a generic "USB device wants to access data: Allow/Deny".
If i reboot and plug it in again, it works just fine one more time (Android Auto lights up on the phone and Uconnect launches the AA UI), no data access prompt (which is expected).
Downgrading/upgrading Android Auto app on my phone doesn't seem to make a difference, same for Google Play Services.
I've tried an older S6 Edge, everything is fine, works every time, even if you unplug 10 times in a row.
Is there anything i can do or has Samsung improved this for good? Thanks!
Samsung Galaxy S8
Android 9, stock, no root
Android Auto 4.2.591444-release
Google Play Services (beta) 17.1.21
My active has a similiar issue (18 ram 1500 uconnect with AA) but the g892a is still on oreo which has a known issue with AA. My wifes s9+ and my company phone (s8) both on android 9, work no issues, but you said your phone already has android 9. Not sure where to go with this.
Looks like i've fixed it by simply disabling USB Debugging in the phone's Settings.
Plugged it in about 6 times already and it worked every time, no restarts necessary.
Someone's end to end testing is either broken or completely missing and by someone i mean either Samsung or Uconnect.
My android head unit closes all the open apps when I turn off the ignition ( even for one second). Whether I'm using the navigation or watching YouTube, if I shut off the car and back on, all the opened apps close and I have to redo everything all over again. I've heard about some apps captures the status of the unit right before closing, and once you start the car again, everything is back to the previous status, is that real ? Also some head units have an option in the developer options to enable quick boot or fast boot, but I don't have it in my head unit, is there a way to enable that option? Is there a "hibernate mode" for Android like the one in windows? Any ideas are very appreciated. Thanks in advance
Hello friend, I have the same problem as you. Did you get a solution? Thanks