Hi everyone.
I bought a sgs about 7 months ago. Since I bought this phone, I am having some bluetooth issues with it.
The problem is;
when you first try to connect the device with any other bt devices, it connects without having any problems and operates normally.
Then, when you disconnect sgs from the device, it never connects again. it does not even search for the nearby devices. you can also not unpair the previously connected device, the command "unpair" does not work.
the 120 seconds counter, doesnt count down when you switch the phone to visible mode.
I tried to re-boot but it did not work.
I re-flashed the same rom, it did not work as well.
I changed the rom with another one and flashed 2.2.1, but it s still the same.
the only way, to make the device connect with a nearby device is to re-flash the rom and it only helps me to connect to any device for just 1 time. then bt becomes useless when you disconnect and to re-connect, you have to flash the rom again..
Please help me in solving this.
Honestly I have similar issues with my phone. This thread fixed the connectivity issues: http://forum.xda-developers.com/showthread.php?t=795691&highlight=bluetooth
However, my phone consistently drops its connection...very annoying.
Honestly, I never had a connection, thus, I am not familiar with the saying "connection droppings"
I tried the things written in the thread but it did not work. still the same and really annoying.
Hi, did you solve this issue? I'm having the same problem on 2.3.3. and it's very annoying...
Search function is currently unavailable, so apologies if this is a dupe...
Anyways, I'm currently running Rooted Stock 2.3.4 on my N1, and I've noticed that whenever I connect to my friend's DLink router (DIR-655, I think) the Wireless will work for some amount of time, but eventually it will stop working. And not just on my phone, either - the entire router stops working (at least for Wireless requests. Didn't have any wired devices connected to it). Thing is, last time I noticed it, it worked for quite a while - hour or two, maybe - then everything broke about 10 minutes after I received an email... At that point, the router needs to be rebooted, after which it continues working just fine.
The router is using WPA2 encryption, for what it's worth.
I've noticed this with previous versions of Android, so it's not a breaking change introduced with 2.3.4 or anything.
Unfortunately, I don't have an awful lot of Wireless routers to test with, and I haven't yet found an opportunity to test at home, so I'd be hard-pressed to say whether it's a router/D-Link problem, or if it's a device problem...
Has anyone else experienced this? Would flashing a custom ROM (e.g. CM7) fix this? Or would I need a new device? Any thoughts on what else I could do to debug this problem? As I said, this is a rooted device, with an unlocked bootloader and the latest version of Busybox installed.
I'm running 2.3.4 and haven't had this issue with this version or any previous ones.
I've had my phone disconnect from Google Services (the icons turn white instead of green), but the internet stays on and all other devices work just fine.
I have a Netgear router at home and a Linksys one at work and I'm connected to both the whole time I'm at either place.
Hmm... That's interesting.
I've never had Google Services disconnect, but I do have another issue with data randomly turning off. That's not a big deal, as I can just turn it actually off then back on again, and all is good.
Anyone else able to chime in with their experiences?
I have had this happen with cheap, crappy routers. Sometimes upgrading the router to DD-WRT helps, sometimes it doesn't. I had an ASUS this would happen to all the time, and an Airlink that this would happen to occasionally.
This doesn't ever happen to my Linksys WRT610N, and it never happened to an old ZyXEL X550.
I'm going to say, it's just a crappy router.
Thanks. Not really what I was hoping to hear, but that's life.
Did either bad router ever have this issue with other devices? One of the other folks living there has an iPad, and never has this issue, so I'm inclined to say it's at least partly my N1s fault. Also doesn't happen with any of the PCs connected to it.
Yeah, they actually did occasionally have issues with other devices. Hard to narrow it down because I have a ton of Wifi devices. The ASUS also seemed to go down based on time... after so long, it would just stop working properly. The Airlink seemed to get stuck based on demand and range. If I had my phone or laptop at the far end of the house and started using it a lot, it would get stuck. It was as if the router decided it was too much work to pump its signal that far and it would get tired.
Stock ROM on my N1 doesn't seem to allow it, but if you have a custom ROM, you might see if there is any way to set the Wifi to G-only. I had noticed on my old router that G wireless devices seemed less demanding for it.
My SM-N900A has been working great for a few years now and is running Android 5.0 from an OTA update (maybe a year ago). A few weeks ago I started having trouble with the wifi. Sliding the wifi control to "on" will sometimes work, but more often it can't find any networks. Often rebooting will fix it, and the wifi will connect (showing a strong wifi signal). Sometimes I see it rescanning several times when I don't think it should be scanning. Then after a few minutes or occasionally up to an hour it will disconnect from the wifi entirely and refuse to show any networks as before. Sometimes I have thought that disconnecting the battery is a surer way to restart the wifi than just rebooting, but it is hard to be sure. This happens with my home wifi, as well as with several other wifi networks I have tried. I haven't dropped or damaged my phone, so I'm wondering if this could be a software problem. I have tried rebooting in safe mode, but the problem persists so I don't think this is caused by an errant application. I have also tried swapping in my spare battery, but that didn't change the problem (although neither battery is a genuine Samsung). If I leave wifi off and just stick to the cellular connection, the phone seems to work as it should. Would there be any logic to trying one of the alternate ROMs on this forum to see if this could fix the wifi problem? One reason I haven't tried this already is that the directions I've seen for installing these ROMs seem to be written for people who have done this dozens of times (which I have not). If this is a reasonable tack, is one of these ROMs known for its ease of installation, or perhaps for the quality and detail of its installation instructions? Are there any less drastic things I should be trying first (other than buying a new phone of course)?
Got the same issue. used odine reinstall 5.0 modem/radio and when that did work, i reinstalled 5.0 and 4.4.4 but nothing worked. i think its a hardware failure. time for a new phone.
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.