Hi People
I have an issue on my S3 mini with Carbon 4.4.2 OS. When I sync to my car with Bluetooth, the Bluetooth process keeps stopping and restarting.
Never had this with the stock rom.
Any idea to solve this?
Thanks in advance!
Greetings
Locutix
Locutix said:
Hi People
I have an issue on my S3 mini with Carbon 4.4.2 OS. When I sync to my car with Bluetooth, the Bluetooth process keeps stopping and restarting.
Never had this with the stock rom.
Any idea to solve this?
Thanks in advance!
Greetings
Locutix
Click to expand...
Click to collapse
Try Carbon 4.4.2 20140409 instead.
Thank you for the tip. Unfortunately after updating to Carbon 4.4.2 (20140409-1234) the problem remained.
I also tried to un-pair the phone, deleting it from the car and re-pair it again, but no success.
Then I tried to enable only phone, so no music or internet. Again no success
com.android.bluetooth keeps crashing.
Locutix said:
Thank you for the tip. Unfortunately after updating to Carbon 4.4.2 (20140409-1234) the problem remained.
I also tried to un-pair the phone, deleting it from the car and re-pair it again, but no success.
Then I tried to enable only phone, so no music or internet. Again no success
com.android.bluetooth keeps crashing.
Click to expand...
Click to collapse
Then you'll need to wait, because some users are reporting that BT is not working very well on CM11, so as carbon has the same sources as cm, we need to wait till Maclaw & Marcin or other dev to fix it. Have a nice weekend.
Also no GPS
Thank you for the information.
Today I found out that also the GPS is not working properly. I use Strava to track my bike rides and the app couldn't get any signal
Greetings and have a nice weekend too!
Hi, there. Basically just spent all of last night slaving away trying to fix my phone only to make everything progressively worse, and all of this morning having someone (thank you, BD619!) help me fix it, all because of me trying out some new roms.
Anyway i'm looking for something with a built-in tether that works off of USB (my laptop's wifi is broken). And having something with working GPS is pretty important for me too. I was on CM10.2 previously and the USB tether worked fine, but i couldn't get the GPS to work right for the life of me. And Viper's rom is the one that essentially sent me into non-stop boot loop mode, so that's out of there as far as what i'm willing to try.
I have tried other variations of CM like PA and slim, but i'd always end up having some kind of issues with the broadband or GPS. Others didn't even plain install. FWIW before today i did not have s-off, but now i do.
Would greatly appreciate any advice here. Please let me know if this is in the wrong section. Thanks
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.
Are major problems solved in the latest firmware? (Restarts, wi-fi & BF dropping...)
Hi,
I want to buy XZ1 compact but I am reading this phone is restarting on its own, and has wi-fi and bluetooth problems. Can anybody please say, if those or other "critical" bugs are solved? I searched but it is hard to say for sure...
Basically I am quite depended on the phone and I really want it to be reliable. My current Motorola restarted maybe once in three years, so I am bit nervous about this.
Thanks
I'm on the latest firmware and I don't have any of that.
That said, I was on the November one for the last few months and also never had any of that.
That's the problem with forums like that, you're likely to only see the rare negatives of any device.
No issues for me.. smooth as butter.. great battery life.. LDAC working flawlessly with Sony headphones etc
Just wish I could turn the charging LED off
Also keep in mind if you unlock bootloader and load custom rom you're on your own. I havent gone that route this time and have had literally 0 issues in months
Okay, thank you, it seems it will be fine. I won't do custom rom but yeah root + xposed is a must for me.
I also got dropping WIFI. Really annoying and nothing seems to fix it.
xPandamon said:
I also got dropping WIFI. Really annoying and nothing seems to fix it.
Click to expand...
Click to collapse
Wifi working fine here. Check the settings on your router.
The restarts seem to be fixed. I think it was a regression with the previous one or two versions. The phone was fine, then it went from one or more a day, to none with the latest update. Wifi hasn't improved, but I did not find it that bad to begin with. Once it connects, it stays connected. It's that original connection where it sometimes decides "wifi? I don't have a wifi radio." Bluetooth is still terrible - works fine with a BT speaker, but is nearly useless with a car stereo.
Only 1 problem persists - Smart Lock don't work, it just a blank page. Can be resolved by restarting the device.
Well, I connect a Bluetooth device, such as Bluetooth headphones or Bluetooth in a car. I try to call someone on the phone, but the call doesn't go through. The information panel shows that the SIM cards are not activated, then after a few seconds, they reboot and become active again. If I make calls through the internet, there are no such problems. Restarting the phone doesn't help. Resetting network and Bluetooth settings doesn't help. Resetting Bluetooth devices doesn't help, so please don't suggest obvious solutions, I've already tried everything simple. The problem is definitely not with the headphones; the problem is with the phone itself, but I can't figure out how to solve it. I didn't find anything useful on the internet. The phone is Xiaomi Poco M3 Pro 5G. Android 13.
Does anyone know how to solve the problem?
p.s. everything worked fine several weeks ago.
Android 13? try reflashing the firmware and the MIUI once again from the stock rom from thirdparty websites, or just use the a12.1 custom rom although its not a13, its working and everything is just awesome, no issues at all, and its AOSP so its much better than MIUI