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...
Hi everyone,
i searched on the forum before write this post, I hope this is the right section.
I updated my galaxy to 2.3.5 (I9000NEJVB, 2.6.35.7-I9000NEJVK-CL649158) starting from 2.2 with Samsung kies.
After this operation the phone works a lot better, but a serius problem is started to be present (always reproducible) with bluetooth.
In 2.2 version I only used one time the bluetooth, with a wireless mini keyboard. It's the only item i've paired.
After the firmware upgrade, when i start the bluetooth, android crashs and restarts cyclically: crash, restart, take network, scan media and crash.
Also removing the battery the cicle remain the same, because when i startup it remembers the bluetooth conf to be on.
If i try to switch bluetooth off in the few second when you can operate the phone, the bluetooth doesn't reach to be switch off .
The only way I found to break the cycle is connect to te pc in debug mode, and wait (if it comes) a popup screen with the confirmation request to turn off immediately the bluetooth, and fortunately this opearation works.
But sometimes I waited more than 10 minutes, with dozens of reboots, one every 5-10 seconds.
On http pastebin dot com slash rFvD81iN you can find the debug log, and the log starts few seconds befere i switched the bluetooth on.
I tried to remove the files in /etc/bluetooth as suggested in one post, but the problem is still present (now the folder is empty, there are not 'grey' paired devices in the list of bluetooth settings; the log was taken when the paired device was in the list).
Can anyone tell me how can I solve this issue? I can use all the feature of the phone, when bluetooth is off, otherwise it became unusable, and I have difficult to recover it.
thanks a lot,
regards
Francesco
I'm having the exact same problem (also on galaxy s i9000). Also just upgraded to android 2.3.5 from version 2.2. I managed to get out of the cylce of crashing eventually after about 10 cycles the phone actually booted sucessfully. I was then able to turn off bluetooth. Re-activating bluetooth then caused the crash cycle again. Oddley, it has now stopped crashing but I can't conect bluetooth properly to my iControl Pad device, now it just says it's paired but not conected. However, I fear the crashing cycle could begin again at anytime I try and use bluetooth.
My bluetooth worked fine as well as my iControl device on version 2.1, only issue was it lagged a lot!
I have the exact same problem, but with Galaxy SII (i9100).
I have Romanian Vodafone Galaxy SII with official software. I upgraded via Kies from 2.3.3 to 2.3.5 and everytime I turn on Bluetooth Android goes through successive crash-restart cycles. During every cycle, BT seems to be on and even if I try to turn BT off, nothing hapens. After a 8-10 cycles, at some point, randomly as far as I can see, it starts normally with Bluetooth turned off.
Any ideas on this?
Thanks,
Razvan
thanks nickmaymusic and razvancd, I'm surprised no one have any indication to how the problem can be adressed.
Anyway in my case the cycles continue for many minutes, and sometimes the phone became unusable.
I think to reflash the phone with odin, but I was try to found another solution, i need the bluetooth.
Try installing Android 2.3.6 using Odin. It's easier with Odin than using Kies.
I also have the same symptoms on Galaxy S2 Android 2.3.5 and Baseband I9100XXKI4 with Kernel version 2.6.35.7.I9100JPKJ2-CL655700 [email protected]#2 Build Number: GINGERBREAD.JPKJ2
This was upgraded via Kies in the UK in Dec 2011.
Bluetooth is effectively unusable and the device simply reboots repeatedly. I have managed to catch the unit during media scan stage and switch off bluetooth and this seems to (if lucky timing) allow the device to fully boot and remain stable.
In my view this is a high priority bug and the Android community really need to solve it quickly to preserve the reputation of an otherwise strong O/S.
Flash a newer relase with odin and the semaphore kernel!
Hello. I've only joined today as a result of the Samsung 9305 Jellybean Update 4.3.
I am on an EE T-Mobile UK i9305 LTE handset in factory condition, no rooting or any other modifications. I have just upgraded to the new update on 20 Jan 2014.
Apart from all the usual observations such as WI FI and battery life, I have another issue which I cannot find anywhere else.
Before the update and for the last year my i9305 worked fine with the bluetooth in my car. I have a 2004 X3 E83 BMW and the car paired absolutely fine. I would talk and connect with no problems. Since the update the phone connects to the bluetooth then drops after 3 seconds.
I have done the following:
Unpaired the phone and repaired;
Deleted the cache for bluetooth
Deleted the cache from the engineers mode
Samsung tells me that I now need to go to the dealer to ask them to upgrade my bluetooth software in the BMW, I explained that 1st I'm not sure if that could be done and second that would cost me money and time for something that was working perfectly fine 3 days ago for over a year. The only change is the update. Therefore I explained that there should be another update to correct this and all other problems immediately.
Has anyone encountered this issue with a car's bluetooth and anyone been able to figure out a fix. I don't really want to go down the avenue of trying a factory reset and testing if that works.
Many thanks
Havent had any issues like that with stock 4.3 and bluetooth so may or may not help but try clear the data for bluetooth share in application manager as well as un pair and re pair the device again after that has been done
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 everyone,
So I've been having some troubles with Bluetooth on two devices running nougat, and I haven't really found any good resolutions.
I've been practicing app development lately and was originally Bluetoothing the apk to my phones to test out (email or cord has been the obvious solution but I get obsessive and wanted to figure out why bt would not work). Weird thing is it was working fine for a couple attempts then it would not work. Laptop is an msi apache, it will connect and transfer to other devices running marshmallow and cyanogenmod no problem. But my s6 and note 5 on nougat will not work. It will attempt to send, time out and say device disconnected AND THEN I'll get the prompt on my phone asking to accept the file, but of course it's already disconnected.
Tried clearing cache, resetting network connections, disabling Wi-Fi, re pairing devices on the phones.
On my laptop I changed the device type from 128bit encryption to 40-58 or what ever it was.
Repaired, restarted, tried changing support services to a local service login type, reinstalled the bt driver... I'm assuming it's the phone but just wanted to list a couple things I tried.
Any ideas or just an android 7.0 issue?
Thanks.
Edit- first post and I put it in the wrong section, sorry about that! Should be in qa
What rom are you using? Try another perhaps, I've had lots of issues with Bluetooth over the years due to buggy roms.
Just installed latest firmware (ERC1) on my Note 5 SM-N920T and bt don't work plz help. Just came off a wipe ESF lost IMEI LOST ALL carrier signal no sim card detected. Finally got it back and no bluetooh.
Something similar happens to me
Ghost19841984 said:
Just installed latest firmware (ERC1) on my Note 5 SM-N920T and bt don't work plz help. Just came off a wipe ESF lost IMEI LOST ALL carrier signal no sim card detected. Finally got it back and no bluetooh.
Click to expand...
Click to collapse
Something similar happens to me I installed the ERC1 in my note5 N920T, the wifi does not work well, and the bluethooth either. sorry for my English