Hi folks,
I've been struggling for almost two weeks to got OP3T work with Android Auto. I know it's not only me who is having such issue. The connection itself may be established be it randlomy disconnects after few minutes or even seconds.
Do you have any clue what is going on?
There is a ticket open on OP forums, people are having exactly the same issue.
Link to the discussion: https:// forums.oneplus .net/threads/android-auto-does-not-work.479503
Do you know any workarounds? I can't live without Android Auto anymore
kmajewski said:
Hi folks,
I've been struggling for almost two weeks to got OP3T work with Android Auto. I know it's not only me who is having such issue. The connection itself may be established be it randlomy disconnects after few minutes or even seconds.
Do you have any clue what is going on?
There is a ticket open on OP forums, people are having exactly the same issue.
Link to the discussion: https:// forums.oneplus .net/threads/android-auto-does-not-work.479503
Do you know any workarounds? I can't live without Android Auto anymore
Click to expand...
Click to collapse
Sorry but what is android auto
cultofluna said:
Sorry but what is android auto
Click to expand...
Click to collapse
It is an interface in your car. It lets you mirror android to the built in mulitmedia system in a vehicle. There are only main features like dialer, maps, spotify. Works great if you travel a lot and the voice commands helps. Totally hands free.
You gotta have a car which supports Android Auto obviuosly.
I drive Opel Astra MY2017.
kmajewski said:
It is an interface in your car. It lets you mirror android to the built in mulitmedia system in a vehicle. There are only main features like dialer, maps, spotify. Works great if you travel a lot and the voice commands helps. Totally hands free.
You gotta have a car which supports Android Auto obviuosly.
I drive Opel Astra MY2017.
Click to expand...
Click to collapse
I have Volvo V40.....I will try it...
Install through Playstore... or apk?
cultofluna said:
I have Volvo V40.....I will try it...
Install through Playstore... or apk?
Click to expand...
Click to collapse
Please check if your car is supported: android [dot] com [slash] auto
(Sorry I'm still below 10 posts, can't write links)
I had to download an apk, since AA is not yet officialy released where I live.
Android auto works flawless for me now that I have a Oneplus 3t. It Never worked when I had the LG V10. You may want to see if it's a problem with the headunit itself and bring it to the dealer.
I have a 2017 Ford Fusion.
I never had any problems on LG G4 and same vehicle. Once switched to OP3T start having difficulties. It's not only me.
Doesn't work with OOS.
I tried, and tried to get my op3t to work with android auto, but everything I tried failed. I recently started rooting, and was able to use android auto with LineageOS, and RR roms. Turns out these
two are based on ASOP, not OOS.
So far Resurrection Remix 5.8.2 has been the most stable, and have had zero issues with Android Auto.
I don't know why OOS doesn't handle this well (at least for me), but I hope they fix it. I really like OOS, except for that one bug which is a big one for me.
Have the issue..Have not found a work around.
On any OOS build i got it to work but it will freeze when phone gets hot... When I use any other rom it works flawlessly... Right now I'm on Phoenix AOSP extended and works great..
kmajewski said:
Hi folks,
I've been struggling for almost two weeks to got OP3T work with Android Auto. I know it's not only me who is having such issue. The connection itself may be established be it randlomy disconnects after few minutes or even seconds.
Do you have any clue what is going on?
There is a ticket open on OP forums, people are having exactly the same issue.
Link to the discussion: https:// forums.oneplus .net/threads/android-auto-does-not-work.479503
Do you know any workarounds? I can't live without Android Auto anymore
Click to expand...
Click to collapse
No issue here. I'm using cheap 3rd party USB and on a Kenwood unit.
Sent from my ONEPLUS A3000 using Tapatalk
Well this is disappointing. Android Auto is one of the main features I'm looking for in my next car which I plan to get this year...
Works without a problem on my Nexus 6p and now on my 3t Car is a Civic 2016
Sent from my OnePlus 3T
Recently purchased a 3T and having the same issue with OOS 4.1.3. My (soon to be sold unless I go refund my 3T) Nexus 6p never had an issue with AA w/ 2016 Golf GTI.
After reading the official forum's support thread (linked in OP), I updated to the recent Open 5 Beta and gave the "change to MIDI" for USB options a shot and it works for a period of time ~10-15 min but then the OS switches back to USB charging. I have to do the same procedure again to get another short successful duration out of AA. I have roughly a dozen different branded Type C cables and only 2/10 of them work with this method (the official Dash cable being one of them).
I'm going to give RR / Lineage a go and see if they can produce steady AA connections. Since I'm also still playing Pokemon Go I can't root / will have to try the Magisk route. I currently can't seem to get my Pokemon Go Plus to Bluetooth sync with the Go app on either 4.1.3 or Open 5.
Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-
Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues
So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?
As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.
I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk
@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.
@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.
Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.
I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks
This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.
My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place
You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.
Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post
I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.
I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks
Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.
It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.
@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.
larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.
@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.
Hello XDA,
I'm having issues with my Android Auto. I'm using it with OnePlus 7T Pro (with the latest OOS 10.0.13 and the latest AA 5.9.604634).
After a click or few inside an application (no matter if it is a Phone, Spotify, Waze,...), the cursor disappears from the app. I can control the bottom bar only - that one works flawlessly. When this happens, the application still normally works, it doesn't freeze or anything, I just cannot control it. It behaves the same wired and wireless.
I recorded a quick video presenting the issue:
YouTube
The thing is, when I tried it with Samsung Galaxy S8 and there were no issues, so it looks to be something wrong with my OnePlus.
Do you have any idea how to troubleshoot this? How to find out what is causing it and possibly how to fix this?
I tried to delete all data from AA application on my phone, but no luck.
I'll be happy for any advice, thank you.
Issue fixed by installing AA AIO TWEAKER link
Not sure what exactly it did to fix it, I just enabled wallpapers and removed speed limitation. I had 6 taps limitation disabled at first and thought this is what helped, but I re-enabled it and the interface still works as expected
Same bug with my OnePlus 7T, I tried to back to version 5.8 and works for a while, but then it failed again. I reset my phone to factory default and seems to working fine now, and upgraded to Android Auto 6.0
Hi all guys, I've been missing a long time from here, so please be care enough to forgive me if I posted the thread in the wrong place.
I'm currently using Android Auto and enjoying very much the amazing work made from Gabriele (AAAD, of which I payed the PRO version in order to help the developer's job).
I'm running AA version 6.3.611314 (downgraded from 6.4, because otherwise AAAD didn't work, since AA 6.4.... doesnt' let you show the apps installed apart from the official ones); Ford Focus Active with Sync 3 updated to 3.4 version, a Galaxy Note 20 Ultra5G (European) with Android 11.
Everything works fine, even AAAD installed programs.
The only problem is that every time I unlock the phone it disconnects from AA and then it starts again from the beginning. I opened the DEv Options in the phone settings and chose as standard setting for the usb - File transfer / Android Auto.
My question is: Why this disconnections happen and HOW can I fix it? I currently drive with the phone unlocked and, useless to say, it doesn't charge as much as it would if the screen had been off. I alredy tried with other cables, even with a Sam S9+ original one.
Thanks in advantage, any help is appreciated.
Same here, S10+ latest official, AA 6.4.611714-release, Ford Sync 3.x .
Doing so for about a week (or some more). At phone unlock, AA is crashing to Sync interface, and phone is asking for permissions in order to start Android Auto again (need to press Allow, otherwise AA will not start!)
Thx!
Same here , s10
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
gidannifico said:
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
Click to expand...
Click to collapse
I can confirm that the issue is related to the last Sammy update , I have downgraded to may update , now aa works perfect
Guys, Google just updated the discussion thread three days ago:
Thanks for all the reports. We informed the Samsung team and they have applied a fix on an upcoming upgrade as part of the regular July maintenance release to resolve this issue. Please keep checking for system updates on the device.
Click to expand...
Click to collapse