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.
I am using Android Auto on a Mazda. AA is not supported on Mazda at the moment, but thanks to the comunity, it works very well.....
That means, it works well if I use Android Nougat on my device. But if I use a (custom) Android Oreo, I have a problem. I have tried several Oreo roms....
The problem:
I can receive messages (textmessage, Hangouts, Whatsapp). If I let Android read aloud the message, sometimes it works, but often not if it works, it is only once.....
I see the coloured dots rotating, but no text is being read and AA seems to freeze.....I have to close everything and mostly need to reboot the phone also....
Does somebody has the same problem? Or does somebody know how I can discover what is the cause of this?
As said, it works fine with Android Nougat.
Phone: Oneplus One
Car: Mazda2, with AA port
I received my Android 10 update and have a strong password to get into the phone. After the phone rebooted the keyboard will not come up. I made sure the Samsung keyboard is on and do have the same third party keyboard as before the update. Has anyone else experienced this issue?
I was able to use a bluetooth keyboard... but looks like i have to use the stock keyboard for now.
I use nothing but SwiftKey and it worked fine after the update. I vaguely remember seeing someone mention the same problem I the beta community though.
Oh great, bugs? Figures. I got the notification for the update earlier today from AT&T. Good thing I wasn't on wifi or else I would be on this boat too.
Hello All,
So since switching to the EU rom, I noticed that I am having issues with the RING app.
Not sure how many of you guys have RING cameras and use the RING app, but hoping that someone does.
Just curious to know, if you are using it, does your doorbell cam (or any other cams) work on the phone?
It works on my S10+ without an issue, while a few minutes later it does NOT work on the Mi 11 Ultra.
The timer is ticking and I can END the live call/view, but the camera picture is not working.
When I click on Live > Tap to Go Live > I get the following error where the video feed is supposed to be: Failed to connect. We're having trouble connecting to your Front Doorbell
Though if I go to the other phone I have, it works just fine.
So clearly its a phone issue and not the application or camera issue.
I am currently on Miui 12.5.17 EU rom, rooted, with LSposed installed. I've tried hiding magisk from Ring, but that did not solve the issue.
Any ideas?
I'm experiencing the same issue on the same ROM, no root, same version your on.
elite-fusion said:
Hello All,
So since switching to the EU rom, I noticed that I am having issues with the RING app.
Not sure how many of you guys have RING cameras and use the RING app, but hoping that someone does.
Just curious to know, if you are using it, does your doorbell cam (or any other cams) work on the phone?
It works on my S10+ without an issue, while a few minutes later it does NOT work on the Mi 11 Ultra.
The timer is ticking and I can END the live call/view, but the camera picture is not working.
When I click on Live > Tap to Go Live > I get the following error where the video feed is supposed to be: Failed to connect. We're having trouble connecting to your Front Doorbell
Though if I go to the other phone I have, it works just fine.
So clearly its a phone issue and not the application or camera issue.
I am currently on Miui 12.5.17 EU rom, rooted, with LSposed installed. I've tried hiding magisk from Ring, but that did not solve the issue.
Any ideas?
Click to expand...
Click to collapse
Do you have your work email, or any work related setup on your phone? Do you have a VPN app on your phone? These can cause this issue.
Hey, so I dont know what I did but the ring app started to work without issues later that day. or maybe the following day. This week has been a big blur at this point.
To further answer your question, yes, I do have a work profile set up through MS and all the MS apps, including InTune which I was able to install fine regardless of having the phone rooted, by using MagiskHide
I also have 2 sim cards in my phone, one personal TMO and one work from ATT
I dont know what combination of steps or actions I took to get it to work, but i was surprised myself that it started to work....
One thing I do remember doing is downloading an OLDER version of the app, which also did NOT work, but I figured I would just leave it installed for now since i didnt have time to go through any app updates. Then when I received a notification that someone was at the door, so I decided to just see if the video will work LIVE as someone was there, as opposed to a recorded motion (which did work on the phone without issue), and viola, it worked live... then eventually I did get around to updating to the latest version just to check and see if it will still work, and it did....
With regards to what the version of the Ring app was that I installed, I do not remember and I just checked the APKs I have on my phone and i do not see one. I think i might have used Aptoide app to download and install the older version. But I want to say it was from March of this year, so quite old, but I may be mistaken.
Nevermind, just found what the version was... Ring - Always Home v3.35.1
Ring - Always Home 3.35.1 (arm64-v8a + arm-v7a) (nodpi) (Android 5.0+) APK Download by Ring.com - APKMirror
Ring - Always Home 3.35.1 (arm64-v8a + arm-v7a) (nodpi) (Android 5.0+) APK Download by Ring.com - APKMirror Free and safe Android APK downloads
www.apkmirror.com
It's Intune and the work profile that installs phone security. The network masking that occurs causes the problems. Try removing it and testing it again.
I know that's the only changes I made on my phone before it stopped working.
I am 99.9 % sure that I tried the RING app BEFORE installing the work profile and thats when the issue was occurring...
not 100% thought, but 99.9%
But regardless..... as mentioned before.... It is currently working fine for me on the latest version of the Ring app... Not sure what I did to get it there, as I was not doing anything specific to fix the Ring app, but clearly something was done and everything now works as expected.
elite-fusion said:
I am 99.9 % sure that I tried the RING app BEFORE installing the work profile and thats when the issue was occurring...
not 100% thought, but 99.9%
But regardless..... as mentioned before.... It is currently working fine for me on the latest version of the Ring app... Not sure what I did to get it there, as I was not doing anything specific to fix the Ring app, but clearly something was done and everything now works as expected.
Click to expand...
Click to collapse
Congratulations, I meanwhile still have the same issue. Let me know if you ever find out how you fixed it.
Thank you.
See above...try to download the older version and run it for a day, hopefully that will get it to working? thats what i did, whether that was exactly what fixed the issue, i dont know, but worth a shot.
elite-fusion said:
See above...try to download the older version and run it for a day, hopefully that will get it to working? thats what i did, whether that was exactly what fixed the issue, i dont know, but worth a shot.
Click to expand...
Click to collapse
Old version of the app works. Maybe I'll wait until a new update is pushed. Last updated in September.
Actually, I lied before.... it DID NOT work on latest version. I just checked and it was NOT working....
I uninstalled and installed the older version and its back to working.
So i'll be using the older version.... As they say, if it ain't broke, dont fix it. so the old version will perfectly suffice
Any luck? Still struggling with this.
I've noticed that 12.5.17 has a lot of bugs. Waiting for another update desperately.