Related
I was wondering if anybody has any issues with bluetooth not been able to reconnect or just not sending sound to the bluetooth device, sometimes on mine I have to reboot the phone cause the BT doesn't turn off....
Here and there
Sent from my SGH-T989 using Tapatalk
off and on... am running digital warfare at the moment... have been wondering if it's something with his kernel as I didn't have this issue with juggernaut 4.1
Using tapatalk on my Galaxy 2 to post this!
me too.
using stock rom.
...I c....I'm running Telus stock, so it seems like is a normal known issue....
Happens to me once in a great while on cm7.
Sent from the neitherworld >:}
Yep, constantly
Sent from my SGH-T989 using xda premium
So I am not the only one this is happening to.
I have the Telus variant of this phone, stock. Talking to their tech support, they would have you believe that this is only happening to you.
When phone is first turned on, bluetooth works fine for trip into work. I turn bluetooth off when I get to work and leave the phone on for the day.
I turn bluetooth back on when leaving work and it is intermittent weather it will connect or not. If you go to the bluetooth screen and tap to turn on bluetooth, it shows "turning on..." but does not turn on, no check mark in the check box. After about 30 seconds it stops trying.
At other times it shows it is on and connected to my speaker-phone. When I get an incoming call, the phone will ring instead of the speaker-phone. If you try to answer using the phone you get nothing because it is connected to the speaker-phone but not transmitting.
I am on my 3rd bluetooth speaker-phone, 2 blueant S4's and a Jabra freeway. I have had connection issues with all devices.
I have sent my phone into Telus repair twice and they did a factory flash the first time. The second time I was given a refurbished S2X. The problem is still there even on the replacement device.
The connection issues don't seem to have any consistency factors, ie after running a certain app and it is hard to recreate for Telus staff at store when trying to show the problem.
Lately if you try multiple times to turn on bluetooth when the connection issue is happening, the phone will lock up and turn itself off. At this point I have to remove and re-install the battery or the phone won't turn on.
We have a hands free driving law in Ontario so I need bluetooth to work.
I hope Telus and Samsung can get their heads together to sort this out. I am really starting to get frustrated with this problem.
I just got my Sprint GN a few weeks ago, and love using the bluetooth to connect to my car audio, but every 3rd or 4th time I get into my car I notice the bluetooth doesn't pair, so I take out my phone and look and the bluetooth icon is gray (instead of blue, indicating it has connected), I toggle the bluetooth off, and then when I try to turn the bluetooth radio back on it just sits there saying "bluetooth is turning on...". Bluetooth stops working until I reboot my phone
Does anyone have any incites into this or anyone else experiencing this?
I have the same issue. It's no solution but you can enable/disable Flightmode to get Bluetooth up and running again (but quicker then reboot).
Sent from my Galaxy Nexus using Tapatalk 2
I'll give that a try (again) next time.. I am 100% certain I had tried that, though, unfortunately.
Yeah, I tried your solution again, and it just keeps saying "bluetooth is turning on..." even after I've turned *on* airplane mode.
Need some more information to be able to help you properly >_>
Stock ROM or Custom?
Rooted/Unrooted?
Or alternatively (Because it sounds like you're running a stock Galaxy Nexus...) ave you tried unpairing, and the repairing the devices?
Hi Zach,
Completely stock & unrooted (so far)
I actually did a complete factory reset a couple days ago, and the problem has yet to resurface, so I'm crossing my fingers and hoping it's gone, but the issue was intermittent so there is no way to be completely sure it won't show up again.
If it does, I'll try your suggestion, thanks
So Sunday I rolled into our family favorite Honda dealership, and I rolled out with a 2012 Honda CR-V AWD EX-L. Didn't get the Navigational system, as per reviews it looked outdated and cheesy, and I have the Galaxy Nexus official car dock with charger coming from expansys any day now.
Paired the phone at the dealership, and was able to play some music. But the connection dropped briefly, causing music to play out of the phone. Then about 20-30 seconds later it reconnected, and a few seconds later the music played out the car speakers.
Didn't think too much of this, but I drove it home and the next day noticed the disconnect / reconnect issue was pretty consistent. And every time it happens, you can't control the Radio or do other things, cause the screens talking about the connection prevent changes. Not life or death, but certainly annoying on occasion.
Yesterday, I determined that by connected an AC Adapter to the phone, the disconnects go away and things work normally. That was a pleasant surprise, and while I don't want to take the phone out of my holster and connect it EVERY time I get in the car, at least I have a work around, right?
The odd thing is, this never happened with my Sony BT Car Deck I had in my Civic. Obviously it wasn't a stock solution, but when the volume knob on the stock deck was failing, a new stock deck was $400. I got the Sony solution for $150 installed at Circult City, and it had bluetooth which allowed me to make and take calls, stream music, etc.
The only catch I've found so far is the car seems to inquire about me transferring my contacts into the car so the phone book is available through the dash. But every time I click allow... it doesn't seem to do anything and the message shows shortly again in the "notification bar" of the phone. I'm ignoring it for now.
I did root the phone and apply the 4.04D update, then the system update saw the 4.04I update and applied that. Wondering if a factory reset might not put me back to 4.01 or something, but might not resolve this issue. Unless I have any advice, I think that's what I'll try next.
I thought about updating the baseband radio, but as I didn't install CMW or anything, pushing the radio update is a little more work that I'm ready for at the moment.
Thanks to any who took the time to look at this. Best wishes!!!
Little update. I had unlocked my phone, but hadn't properly rooted it, flashed the ROM, etc. Took me a while this morning, but I rooted it, installed CWM on the recovery partition, and then updated the radio to UGLA4.
Despite the above, the car still "drops" the BT connection about once every two minutes, and then makes the connection again about 10-20 seconds later. If the phone is plugged into the car so it has extra power, the connection stays up and reliable until it is unplugged or the car is turned off.
Not sure what to try next, if Honda doesn't have a BT update for the radio in this car. Here's hopiing!!!
FIXED!!! So here is the problem AND the solution.
Dunno why, but something about the default bluetooth.apk that is in the Galaxy Nexus, even after the 4.0.4 update was NOT working between my phone and my CR-V.
The "hint" to the fix was found here. http://forum.xda-developers.com/showpost.php?p=14249943&postcount=11
After killing this process, my connectivity issue between phone and car disappeared. But the phonebook STILL wouldn't update.
Feeling I was getting somewhere, I did searches for the BluetoothPbapService, and so forth. After some looking, I finally found THIS site. http://forum.android-rsap.com/viewtopic.php?f=33&t=221
I had unlocked my phone once, but hadn't rooted it properly. While trying to fix this issue, I'd rooted it, installed the CWM recovery menu, and tried a couple different "broadband" software packages that control the radio. That hadn't fixed the problem, but I COULD use Root Explorer with SU rights afterward.
So I downloaded the file for Android 4.0 to the Downloads folder on my GN. Then I created a new folder on the SDCard called backup. I moved the Bluetooth.apk and .odex files that were in /system/app into that directory, moved the .apk file I downloaded from that site back into /system/app, and made sure the permissions were as directed. Then I rebooted the phone.
Once down at my car, I removed ALL Bluetooth profiles from the car, clearing the BT settings completely. And then I deleted the BT profile from my phone. Then I turned on BT on the phone, pressed the phone button on the dash, and paired the phone as before. Only THIS time, the phone paired normally, didn't disconnected, and when I clicked phonebook, it seemed to do nothing as before. But a SECOND click on Phonebook, and instead of trying to download again... I GOT LETTERS to lookup names!!!!!
I tried a couple calls, and people didn't answer, but I can call and use the BT in my car normally!!! OH HAPPY DAY!!!
Took the CR-V in, got my proper plates put on, they washed the car for me (looks great!), and I ran a few errands. Having sat around doing laundry and watching Batman Begins, I wondered about getting the Media option on my Galaxy Nexus to disable like I'd tried in the past. That way, I can listen to the radio, but if I'm using my turn-by-turn directions over Google Maps, I can her Nav instructions through the phone.
I did a BUNCH of searching, and lots of people had similar issues. But one one had found a way to disable the "media" part of the Bluetooth stack. Remembering some people found that killing the PBAP process of the Bluetooth stack in Apps allowed them to sync their phone to their car, I wondered if it would help with my media issue. So I disabled it and went down to the car.
At first, there was no difference. Media went through the car, and nothing was any different. I unpaired the phone from the car, cleared the car BT setup from all devices, and started over. Once again it popped up as it always had, and I tried telling it NOT to pair every time automatically, but don't pop the HandsFreeLink message. This didn't seem to work, as the phone would disconnect and reconnect as it had in the past.
Frustrated, and ready to give up, I cleared the pairing on both sides, and went to put it back how I started. But when I cleared the car and went to pair again, I added my Galaxy Nexus, and waited for the message to come up about pairing going forward. It never came. And ironically, the car was NOT paired for media, just the phone.
Feeling brave, I connected the phone to the car with the media checkbox. It connected, and I was able to play a song through the car stereo. Figuring it wouldn't disconnect, I tried anyway... and it DID! I then turned off the phone, and off the car. Turned the phone on, the car back on, and everything KEPT working!!!
Obviously, I need a little more testing to be certain. But lt looks like I may have stumbled across a setting or something that allows me to use the phone however I wish. And that is a VERY good feeling.
Have no issues in a '12 Civic. You know, other than the recall.
Well, I'm back to having trouble.
Upgraded to Jelly Bean. Love the voice search which works great for me, the speed is still excellent, etc. But even after replacing the bluetooth stack the way I did in 4.0.4, I can't permenantly disconnect bluetooth audio for MUSIC through the phone. I've tried the usual fixes as above, and it just ALWAYS stays connected, assuming the car is on, and bluetooth on the phone is enabled.
SO FRUSTRATING, as then I can't listen to the radio AND use my turn-by-turn directions!!!
The wife and I have been troubleshooting this problem ourselves with weird results.
We purchased GNex's from Bell in Canada at the same time (yakjuux builds). About a month later, we leased a 2012 CR-V. Her phone has always had this connect/disconnect issue, while mine hasn't. We have returned her phone to both Bell and Samsung on separate occasions; all they have done is flashed it and sent it back. Of course that hasn't solved the problem. Provincial law in Newfoundland requires the use of hands-free when on the phone while driving, so this is issue is more than just an annoyance.
I got tired of waiting on Bell and Samsung Canada to get their act together with 4.1.1, and recently rooted my phone and moved it to a 4.0.4 takju build in order to get the system update. No problems with any of that, and it works with our CR-V, same as it always has. We hoped that doing the same to her phone would put this issue to bed once and for all, but after having run hers through the same process this evening, it still does the same trick of connecting and disconnecting endlessly (unless you force-stop the phonebook service, of course).
Now that both phones are rooted, I'm about to try copying my Bluetooth.apk on to her phone and seeing if that fixes anything.
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
TomSilverSpring said:
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
Click to expand...
Click to collapse
Are you using an experimental ROM or stock rooted?
Jedi Mind Trick XI (although the problem has been growing worse and has happened across the last several JMT versions). I will give a stock rooted ICS a try.
I just tried a stock rom and the problem persisted.
I have the same problem
I have scoured the net looking for an answer, any answer, to this problem. It seems that a few people are having the same issue. But before it is ever answered, some dip$#!t always jumps in and says "I have the same problem, my phone won't connect to my car." Then the conversation goes off into other people that can't connect their bluetooth to their car or their headset- or their cat... That is not the same problem!!!
I cannot turn my bluetooth on unless I soft reset the phone. Even after I've gotten the bluetooth working, if I restart my phone the bluetooth turns off and when you try to turn it on, it says "Turning on Bluetooth..." It cycles for about a minute and a half and then goes back to "To see devices, turn on Bluetooth."
I bought this phone on Amazon for what appeared (at the time) to be a reasonable price. Since then, I believe that I have read at least one of the seller's post about bluetooth not coming on (no proof, just an educated guess). The seller probably got rid of the phone because noone could or would give an answer to this problem. Heck, it's possible that every post that I've read so far is by someone who owned this phone at one point or another. :silly:
I am sending this post to XDA because even the adminstrators on android forums say that you guys are the smartest and most responsive forum available. (Okay, they didn't say smartest- it was implied). Please help me resolve this issue.
I rooted this phone the moment that I pulled it out of the box. In other words, I don't know if the bluetooth issue is caused by the root, or if the previous owner didn't root the phone and also couldn't get the bluetooth to work. I believe that, because the phone is rooted, I should be able to remove and reinstall the app that bluetooth is based upon.
I am not a techie, the only reason I know anything about root is because I was complaining to someone about my old phone and how all of the bloatware that seems to constantly run eventually kills my battery. He told me about rooting, and it was easy enough - the rest is history. In other words, if you ask me for more information- I promise that I can give it to you. Yet, have patience with me if I ask you a question that you believe that any person that has rooted their phone should know.
I really hope that you guys can help me without bricking my phone. I truly appreciate any suggestions or thoughts on this matter.
jzxpw6;34880517I cannot turn my bluetooth on unless I soft reset the phone. [/QUOTE said:
I may have figured out what is going on, although I can't understand why it is (maybe someone more versed with processes can help me figure this out).
Using Titanium Backup, I first froze the two bluetooth items (Bluetooth Share and Bluetooth Test). Of course, that didn't remove anything, but I wanted to make sure that I could. Then I wanted to see how Bluetooth Share would react without Bluetooth Test. I unfroze Bluetooth Share.
I was then able to turn on and off Bluetooth fine. I restarted the phone and Bluetooth came in just like it did on my old phone. I guess I want to know:
1) Is the Bluetooth Test the cause of my problem?
2) Why is it there?
3) If I uninstalled it, would I experience a major hiccup?
There is still the possibility that this was simply a fluke, and very soon I will go back to the old bluetooth soft reset problem.
There is, however, one distinct difference between this phone and the last and may be the "drop out" that everyone else seems to be having. I have a Chevy Malibu with bluetooth in the stereo. On my old phone, when I started the car and got going, the word "Bluetooth" would appear on the digital display for about 10 seconds, which means that the vehicle detected and connected the bluetooth pairing. Yesterday, as I was driving in the car, every 5 minutes or so, "Bluetooth" would appear on the digital display.
This leads me to the conclusion that Bluetooth is dropping out and being picked up continuously by my vehicle. Does anyone have any thoughts on this? I'm okay with that as long as when I am talking to someone for more than 5 minutes I don't have to keep calling them back. I simply want to know what you guys think about this issue.
Click to expand...
Click to collapse
I am beginning to think that the problems I have had are related to the condition of the battery contacts.I have several third party batteries with contacts that are somewhat damaged from the pins on an external charger that came with them. I seem to experience a variety of problems when I try to use them.my original factory battery seems to work most of the time. I have several new Samsung batteries on order and will post again if they seem to solve the problem.
Sent from my SGH-T989 using Tapatalk 2
i had the same problem and it started with JMT so I switched roms countless times and the problem kept coming back. It would work for a little bit but when i turned it off it would not turn back on. I decided to go back to stock to see if the problem was still there and it was gone. Since then I have rerooted and once again flashing diff. rom every other day and bluetooth works just fine.
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
enveous said:
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
Click to expand...
Click to collapse
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
aaronchili said:
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
Click to expand...
Click to collapse
Hey thanks! I switched to JMT JB4 and it's not happening (much) now, I'll try to flash it and see if it fixes something :good:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Noticed the same with my 360 and Nexus 5. Both on stock latest versions.
Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.
I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?
I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.
Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.
Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.
this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.
Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.
I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....