Hi all,
A couple months ago I treated myself with a pony car from Ford, that runs a Ford Sync 3 multimedia system. It supports Android Auto as well as Carplay, by cable only.
When I brought the car from Germany (2nd found there) I was still running my old 5T as a temporary phone because my 8 Pro was being serviced (long story, useless here). AA worked flawlessly with it.
Since I got my 8 Pro back (initially running OOS11), it has NEVER worked correctly with Android Auto: whatever the cable, whatever the OS, AA will eventually disconnect. The phone keeps showing a "android auto is enabled" notification, but the media system does not see it anymore. Basically, all ongoing app stop working on the screen, the media system reverts to a non-AA state.
I have tried with the OEM cable and third-party ones. On the front USB plug of the one in the armrest. Resetting the phone, resetting the car. Eventually, it fails again. All Pointe towards some stability of the USB connection: it works for longer with the OEM cable. As read in other threads and googling, I've tried by setting the default USB mode to various things (in dev options), enabling/disabling OTG... To no avail.
This is very frustrating because although I could buy a wireless AA dongle, I like things to "work as intended". Android Auto seems to be a very painful experience, overall (that's what a quick Google search tends to say). Is there any way to actually troubleshoot things? AA has a developer mode, is there any chance to grab a proper debug log for when it crashes? Sadly enough, Carplay works fine. I'm stuck with my wife's Spotify Playlist...!
Same happened with OOS11, OOS12 (C.20 atm but also occurred with the one just below). Oh yeah, I'm magisk rooted, just FYI.
Thanks and cheers!
/e : apologies for posting to the the wrong section and thanks to the mod who moved the thread
Little bump. Has anyone faced issues with Android Auto, and found a way to at least troubleshoot it?
Problems with android auto afaik are mostly car related. Using it for a long time with less problems, oos 11 and 12, hyundai i20 (wireless android auto). Maybe you should ask Ford for that, maybe they have updates for car audio firmware. Seems some car audio system didnt have a proper integration of android auto...
Bump here.
I have digged the question of firmware updates for the APIM. Turns out there are none (even checked myself with FORScan). Got the opportunity to try with another OP8 (not a Pro). Exact same behavior. These same two phones (my OP8Pro and the other OP8) do work perfectly fine in another car (Hyundai) though.
Android Auto has always been questionable in terms of reliability but this is completely unusable now. Is there any chance to troubleshoot the connection in developper mode ?
Related
I'm working with a Nexus 7 (2013) and a Nexus 4. I've had both devices for quite awhile, the 4 for well over a year and the 7 for a year. Both are rooted and using stock ROMs, 4.4.4.
I have the two devices Bluetooth paired and sometimes connect them. For the most part, over the last year, there have been no problems doing that. Once in awhile, they won't connect, but if I reboot, they will. Now, all of a sudden, I can't get them to connect under any circumstances. They're paired. But they won't connect. They both connect to an external Bluetooth speaker and the phone connects to my car bluetooth. That happens with 100% reliability. But these devices just won't connect with each other. And I need them to for certain work related purposes.
What could have happened?
I've unpaired and repaired them a few times. I've rebooted both devices. Potentially competing Bluetooth devices (like my car and the speaker I mentioned) are turned off. The devices aren't connected to any other Bluetooth devices.
Strangely, someone I work with who's doing the same sort of thing (and whose urgency to make them work together is greater than mine) with the same exact devices as I am is having the exact same problems.
What could be going on? Please let me know if you have any ideas.
Thanks.
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
pjc123 said:
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
Click to expand...
Click to collapse
Thanks for the commentary, pjc123. At least someone said something.
I restored one of my Nexus devices to stock 4.4.3, then 4.4.4. Didn't change anything. Maybe I need to take a couple of them back to 4.4.2 or earlier and see what happens. But AFAIK, my friend who has the same problem hasn't ever even updated to those versions of the OS. And it worked fine for him, doing these Bluetooth connections on no less than a weekly basis for a year.
Google's tech support, fwiw, told me that the first thing I needed to do was to update to 4.4.4. Not that I took that as anything other than their reading off a script.
Please let me know if you ever figure anything out with this. I'll report here if I do, too.
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
pjc123 said:
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
Click to expand...
Click to collapse
Interesting. I temporarily turned XPrivacy off just for that purpose. The app that's failing for me wasn't being protected, anyway, but it doesn't matter. I can't even get to that point, because the devices don't connect, even though they're paired. Furthermore, only one of my devices even has XPrivacy installed. I can't get any two of my, or my friend's, Nexus devices to connect, even though they're all paired. And they all used to.
I'm waking up this thread again to see if anyone has any ideas. I just can't connect two Bluetooth devices anymore by using the list of Bluetooth devices in settings on a Nexus device. This prevents an app that's dependent on that from working.
I CAN connect two devices via Bluetooth using ES File Explorer and see the contents of the other device and make file transfers. But the Bluetooth icon remains unlit and the connection isn't made in the settings. Maybe it's a different aspect of Bluetooth. When I close the connection with ES File Explorer, the toast says that the OBEX connection has been discontinued.
Why would I be able to connect two Nexus devices regularly for a year, then not be able to anymore?
I've tried to get Google support on this. Unlike some companies who provide inept support, even laughably so, Google just blows off the notion altogether.
Some months later...
This problem remains unresolved. I've now tested this on multiple devices (about ten of them) running various different versions of Android. I just tried it today with another, a stock, factory state N4 trying to connect to a stock, factory state N7 (2012). I wiped the devices, reinstalled the OS and then tried to pair and connect as the very first act on the clean systems once I got past the initiation routine.. I even loaded a few different versions of Android from distant past (4.2) to present. I CAN NOT connect two paired Android devices using Bluetooth, even if they're successfully paired and Bluetooth is turned on for both devices. All these devices connect fine with things like external speakers and cars. I've shown this to Google employees, some of whom have tried it on their own devices. Nobody succeeds.
As mentioned earlier in the thread, this used to work every time on every set of paired devices, regardless of the Android version.
What could possibly be going on here?
I struggled with this for awhile today. Same symptom: the devices can pair, but will quickly go from "Conecting..." to "not connected". I eventually stumbled on the solution: one device must have internet tethering enabled. This setting is in the "Tethering & portable hotspot" section, not in the bluetooth settings. This will enable the two devices to connect, and it will also enable the second device to use the "Internet access" feature in the bluetooth configuration for its connection with the first device. Hope that helps!
Google needs to start supporting MirrorLink on Nexus phones. I have a Nexus 6 and the Pioneer AVH-4100NEX.
Android Auto has been a horrible experience so far. It worked at first, for a couple of months, and then I don't know why (Android update maybe?) but suddenly it stopped working and hasn't worked since.
Even when it did work, there were some VERY annoying things:
1) if your phone is plugged into the USB cable, Android Auto launches, and as long as you're still plugged in I couldn't find any way to temporarily get out of Android Auto (such as if I want to check my email or some other app on the phone). Or if I want to listen to a YouTube video (or watch it from my phone, lets say I'm the passenger ok?), then I'd have to un-plug the USB which means my phone isn't charging.
2) The other really annoying thing is that Android Auto limits developers in how many screen clicks user would need to do to get to content (including, clicking the down arrow to browse through a long list). Where this is a problem for me for example, is my Spotify playlists. Android Auto will only display about 10 or so of my playlists.
So I find myself disconnecting the phone from the cable and just streaming over bluetooth.
In fact at first I was really upset that my phone was no longer launching Android Auto at all and stopped working with my Pioneer AVH-4100NEX, but now that I am just able to leave the phone charging all the time and have full access to my phone apps, all my spotify playlists, youtube, and am just streaming over bluetooth now I'm not really sure I even want to fix Android Auto.
What I really want at this point is to just MIRROR my phone screen to my head unit. This way no matter what I want to watch or listen to, it doesn't matter if "Android Auto" supports it or not. I can put on YouTube videos, or anything I want.
So this gets me back to Mirror Link, I don't know why Google or Motorola is not supporting it, MirrorLink from what I've seen should be another viable option for Android users (and for now I think a better option than Android Auto)
It seems it's being treated as something old/legacy but in fact I think it's a step in the right direction and something we should all have the capability to do with our phones.
natv said:
Google needs to start supporting MirrorLink on Nexus phones. I have a Nexus 6 and the Pioneer AVH-4100NEX.
Android Auto has been a horrible experience so far. It worked at first, for a couple of months, and then I don't know why (Android update maybe?) but suddenly it stopped working and hasn't worked since.
Even when it did work, there were some VERY annoying things:
1) if your phone is plugged into the USB cable, Android Auto launches, and as long as you're still plugged in I couldn't find any way to temporarily get out of Android Auto (such as if I want to check my email or some other app on the phone). Or if I want to listen to a YouTube video (or watch it from my phone, lets say I'm the passenger ok?), then I'd have to un-plug the USB which means my phone isn't charging.
2) The other really annoying thing is that Android Auto limits developers in how many screen clicks user would need to do to get to content (including, clicking the down arrow to browse through a long list). Where this is a problem for me for example, is my Spotify playlists. Android Auto will only display about 10 or so of my playlists.
So I find myself disconnecting the phone from the cable and just streaming over bluetooth.
In fact at first I was really upset that my phone was no longer launching Android Auto at all and stopped working with my Pioneer AVH-4100NEX, but now that I am just able to leave the phone charging all the time and have full access to my phone apps, all my spotify playlists, youtube, and am just streaming over bluetooth now I'm not really sure I even want to fix Android Auto.
What I really want at this point is to just MIRROR my phone screen to my head unit. This way no matter what I want to watch or listen to, it doesn't matter if "Android Auto" supports it or not. I can put on YouTube videos, or anything I want.
So this gets me back to Mirror Link, I don't know why Google or Motorola is not supporting it, MirrorLink from what I've seen should be another viable option for Android users (and for now I think a better option than Android Auto)
It seems it's being treated as something old/legacy but in fact I think it's a step in the right direction and something we should all have the capability to do with our phones.
Click to expand...
Click to collapse
You have to take into account the many laws in different places concerning cell phones and driving. In some places you can get a ticket just for having your phone in your hand while driving. And now they are cracking down even harder on it. Also some OEM have been known to block some cars from working with devices like that. It was found that one samsung device had a list built into the OS that blocked a number of different cars from working with Android Auto. This I can only assume came from the Car manufacturer.
Also on a side not there is no need to open another thread about the same topic you have already replied to. This is called spamming.
Hi all,
I've got a Withings Pulse Ox (Bluetooth activity tracker, like a fitbit) that I've had for the life of my OP5. It's always worked on OOS 4 and 5, however since upgrading to Android Pie (OOS 9.0.1) it refuses to pair with the phone. It is discoverable, and will attempt to pair but never succeeds. My other devices (headphones, and car audio) continue to work just as they did previously.
I've tried the usual array of rebooting phone, tracker, uninstalling and re-installing the Withings app - but never works (trying another phone, running an earlier version of Android pairs immediately). I'm talking to Withings Support, but they are being typically useless so far.
Phone is rooted, with Magisk, but the only modules I've got installed are related to the camera.
Has anyone had any experience of trackers not working since upgrading to Pie / have any suggestions for what else I could try?
After installing Pie i had connectivity issues with my Anker Soundsync Drive hands-free kit. I unpaired , cleared storage and cache of the Bluetooth and Bluetooth MIDI service app in "Settings --- Apps&Notifications --- See all xxx apps --- Show system --- Bluetooth / Bluetooth MIDI service --- Storage". After a reboot it connected flawlessly.
I hope this helps
V.
Hi,
Thanks for the suggestion. I've tried this but unfortunately still not pairing and syncing.
Hello,
1.Open the Fitbit app and start the sync process. It will say “looking…”
2.While it is looking for your device, quickly go to Android Bluetooth settings, choose Pair New Device, and select the tracker as if to pair it for the first time. (remember to remove it from your Bluetooth devices first)
3.Switch back to the app and the sync process should complete.
That's work for me.
OnePlus 5 - Android 9
Same problem for me. Still not fixed with 9.0.3.
SolykZ, have you got the same issue specifically with a Withings Pulse Ox device?
phoenix1589 said:
SolykZ, have you got the same issue specifically with a Withings Pulse Ox device?
Click to expand...
Click to collapse
I own a Withings Pulse 0x and I had absolutely no problems with my previous phones and my current OP5t before the Pie update. I even full-wiped the phone "just in case" with no luck. Any other phone will pair without any issue. I can't try with another Pie phone since this one is my only one Pie-powered device, sadly.
Hi,
Any update about this?
Regards,
Chris.
Withings swapped my pulse for a Steel, as they couldn't work out what was going wrong (or they knew they messed up but didn't want to fix an old device).
Thanks a lot for your feedback. I'll contact them asap. Hopefully the french support (I'm from Belgium) will be that convenient with my own problem.
Hi, everyone. I've been using my 8 Pro without issue on my 2016 Jeep Grand Cherokee since I got it, but ever since I updated to Android 11 last week my radio system has been rebooting every 3 minutes on the dot if my phone is connected via Bluetooth. No phone call or music needs to be active, it just has to be connected. When I turn off Bluetooth and the phone is disconnected, no issues whatsoever. Has anyone experienced anything similar?
Also, if I choose to downgrade, will it be an in-place downgrade and keep all of my settings and files, etc (just like the upgrade was) or will it wipe everything? I have no issue downgrading, I didn't dislike Android 10; I just want to make sure I won't have to setup everything from scratch.
Thanks for your time!
EindhovenOne said:
Hi, everyone. I've been using my 8 Pro without issue on my 2016 Jeep Grand Cherokee since I got it, but ever since I updated to Android 11 last week my radio system has been rebooting every 3 minutes on the dot if my phone is connected via Bluetooth. No phone call or music needs to be active, it just has to be connected. When I turn off Bluetooth and the phone is disconnected, no issues whatsoever. Has anyone experienced anything similar?
Also, if I choose to downgrade, will it be an in-place downgrade and keep all of my settings and files, etc (just like the upgrade was) or will it wipe everything? I have no issue downgrading, I didn't dislike Android 10; I just want to make sure I won't have to setup everything from scratch.
Thanks for your time!
Click to expand...
Click to collapse
Can't comment on your Jeep, if it's Android Auto I'm advised that 11 works fine, however my centre clock mod does break the icons.
In regards to the downgrade.. no you will have to wipe, it's not possible to retain system data, I'm not sure about data but I would assume not.
Although I was able to upgrade to 11 from 10 without losing storage data, I don't believe it's possible in reverse, it also carries an inherent risk so be sure this is the right thing to do..
You will have to set up again.
In regards to your Jeep how are you connected?
Is it android auto? Or simply Bluetooth?
I would obtain another Android device also on Android 11 and see if it exhibits the same symptoms.
There are some Bluetooth options in developer options, they may be worth exploring.
If it's Android auto then I would make sure that android auto isn't being optimised for battery in settings
Settings /apps /android auto /battery /
Set to don't optimise.
Failing at 3 mins consistently is a telling symptom.
Hope this helps
dladz said:
Can't comment on your Jeep, if it's Android Auto I'm advised that 11 works fine, however my centre clock mod does break the icons.
In regards to the downgrade.. no you will have to wipe, it's not possible to retain system data, I'm not sure about data but I would assume not.
Although I was able to upgrade to 11 from 10 without losing storage data, I don't believe it's possible in reverse, it also carries an inherent risk so be sure this is the right thing to do..
You will have to set up again.
In regards to your Jeep how are you connected?
Is it android auto? Or simply Bluetooth?
I would obtain another Android device also on Android 11 and see if it exhibits the same symptoms.
There are some Bluetooth options in developer options, they may be worth exploring.
If it's Android auto then I would make sure that android auto isn't being optimised for battery in settings
Settings /apps /android auto /battery /
Set to don't optimise.
Failing at 3 mins consistently is a telling symptom.
Hope this helps
Click to expand...
Click to collapse
It's just a straight Bluetooth connection. I used with my old 1+6 (android 10) and always works great.
I have the same problem with my Jeep Renegade.
Also, when the phone is connected via bluetooth, the USB input doesn't work.
The system is "Uconnect 5.0 System"
I am having the same issue with my 2016 Jeep Renegade using Uconnect 5.0. My phone is a OP 8 Pro
Same here, 2016 renegade and OP 6T, head unit randomly restarts after Bluetooth connection is made.
I've turned of media sharing off on the phone as someone suggested as workaround.
Is there a solution?
thanks to @Shackleboyrusty
Like many here, the android 11 /oxygen 11 update to my 7T crashed my car's uconnect system. Here's a fix that worked for me:
1) Unlock developer mode: settings > about phone > repeatedly tap "build number" until it unlocks
2) Go back to settings, then system > developer options
3) Scroll down to "Bluetooth AVRCP Version" and change it to "AVRCP 1.3"
Alternate 2/3 - search settings for "Bluetooth AVRCP" and change to 1.3
That's it, good luck!
I have an Atoto S8, and this is my first Android powered head unit (coming from their linux-based F7, which was more of an appliance UI instead of a smart OS). I love the extra functionality it gives me, running apps and video players directly on the unit. But Bluetooth support is wonky.
My wife and I share the car, and ever since swapping to the Android powered unit, it only reconnects to whoever drove last. So if I drive the car all the time, its fine. But when my wife drives, she says bluetooth isn't working, so I have to go into settings on the BT app (BT1 as they call it) and see the three phones listed as paired (my old phone, my new phone and my wife's phone), and click on hers. Wait a bit, and then she is good to go. But then next time I drive, I realize my phone isn't connecting now, so I have to go do it again. Which means she's going to complain next time that her phone isn't working again.
I've installed a few bluetooth powered head units before, and even the Android Auto supporting F7 before this one, worked as expected: If the last device isn't available, try to connect to another recent paired one. It seems to just get stuck on the last one for some reason. Is this a limitation of how bluetooth works on these units?
have you solved this issue
i am finding it very frustrating
i thought i would solve it using the app "automate"
this would star a sequence of checks and sytematic attempted connections
but, oddly enough you cant automate the triggering o fthe flow
so it would only start if actioned
Yes, or rather THEY solved it.
Reach out to customer support. There is an update to the Bluetooth module that makes this work the way I described.
I got an A6pf in my other car and had them make an update for that one too. Much happier now.