I've been searching and searching with no answers. Every thread on BT connection issues die off unsolved.
Well, hopefully this thread doesn't end that way.
I have a Jabra Cruiser 2 and early on it was the only thing I had paired. Press the connect button on the Jabra and my phone would connect right up with no user intervention. Later I flashed a couple other roms and found this auto connect stopped working. I don't think its worked since UnNamed 1.3 but not exactly sure. I also tried flashing different modems for a while but can't say if that matches up with this failing to work.
Does the modem have anything to do with BT?
Anyway, I've tried flashing ICScrewed 2.0.1 from scratch with a complete wipe of everything and it still doesn't work. I've flashed Entropy's last few DD's in a row and those didn't help either.
When Jabra is powered on and ready to connect my phone sits there saying "Paired" but doesn't try to connect on its own. I press the Jabra selection in BT Settings and it then changes to "Connected" and I can stream music through it. Even at this point I can't use the Jabra for telephone calls. I've made sure the options for music and telephone are checked under the Jabra settings.
...and yes I've deleted the BT pairing and paired from scratch. I did restore BT pairing once from Titanium but that was several roms and wipes ago. So unless it saves information to a folder, there shouldn't be any remnants.
Is there a folder somewhere that holds BT settings that can be wiped? Should I flash a new modem? Any ideas at all would be helpful at this point.
Nobody has problems with their BT? There has to be a way of clearing the BT settings from everywhere and pairing from scratch beyond the obvious.
Guess I set this thread up for failure by saying, I hope this doesn't die like every other BT thread.
...Maybe someday the BT problems of the I777 world will be solved.
Have you tried pairing your phone with any other BT device other than your Jabra Cruiser?
Have you tried going back to the same ROM (stock or otherwise) that used to work with your Cruiser?
That should narrow down the causes of your problem.
I use Jawbone headset and ever since I've started using it, I need to click it once to connect with my phone (I have set to turn off bluetooth automatically after every call.). But I don't have any problem with that.
I have a Galaxy S3 I9300 for a couple of weeks now and I love it, other than the fact that I keep having a strange issue with the Bluetooth connection with my carkit. I've been searching forums for similar issues and I found a variety of carkit related problems, but none of the ones I found describe the same problem as what I'm having:
- Initially the Bluetooth connection works fine and I can play music or make a call through the carkit just fine
- When I switch off the car's systems and don't use any apps on the phone in the meanwhile, and then start the car's systems again, it establishes the Bluetooth connection just fine again
- When I switch off the car's systems and I use other apps for a while and then start the car again, it won't work. Bluetooth does appear to connect, but after that it just doesn't play ball. When I try to play a song at this point, the phone shows the song is playing, but neither the phone nor the car audio produces any sound
So anyway, every morning before leaving to work and every evening before going home, I reboot my phone first. Then I step into the car and it establishes the Bluetooth connection just fine. But if I don't reboot the phone first, it just won't work. Now I guess I could setup a tasker profile to automatically reboot the phone, but I'd rather just get the problem fixed.
I run a Galaxy S3 I9300 with stock Android 4.1.1, rooted. I have already tried to run the "Bluetooth Fix Repair" app and afterwards had to pair the phone with the carkit again, but that made no difference.
Any help would be greatly appreciated!
*bump*
Some additional info:
This issue has now also happened a few times while driving. While music (through Spotify) was playing over the bluetooth carkit, it would sometimes just stop working when I opened a different app (like for example opening an SMS). Spotify was still running (and the song was still ongoing) and also the bluetooth connection still showed as being connected, but it just wouldn't produce any sound anymore.
Anyway, it seems clear to me that this is a bluetooth issue, but I have no idea how I can troubleshoot this beyond what I've already done.
I would be happy to pay whoever can fix this problem..
With an issue like you are describing it may be helpful to list the headunit model too. I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
ItzCrooK2UxD said:
With an issue like you are describing it may be helpful to list the headunit model too.
Click to expand...
Click to collapse
My car is a Renault Megane RS, the carkit was built in. I believe it's called Renault Carminat TomTom.
ItzCrooK2UxD said:
I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Click to expand...
Click to collapse
I've covered everything like that in about 100 different ways, none of which made any difference.
ItzCrooK2UxD said:
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
Click to expand...
Click to collapse
Good point. It does have an SD card slot, but as far as I know that's only to update the maps of the navigation system. I'll see if I can figure that out.
Thanks for the tips!
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Apoc_ said:
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is in fact very possible that it is your phone, but wanted to throw it out there that bluetooth headunits can be troublesome on their own. Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me. Also do you have other bluetooth devices in the car, such as the 3GS you mentioned?
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
ItzCrooK2UxD said:
Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me.
Click to expand...
Click to collapse
Yeah I had read that too in some other thread (I went through just about every bluetooth related thread I could find, before I posted this topic). Mine saves up to 5. It didn't have anything in there except for my previous phone, which I had cleared. I also tried re-pairing the S3 several times, that didn't make any difference either.
Now, I just read somewhere that some people are having disconnection issues on the same carkit. In their case, in the end the problem turned out to be that their carkit will import all of their contacts from their phone (so you can call people even while your phone is in your pocket), and this would cause trouble when there are contacts without a phone number associated with it (just like my thousands of Exchange contacts). The people in question are talking about random disconnects though, whereas in my case it happens after doing some stuff on my phone. So it's probably unrelated, but I'll give that a try anyway just to rule it out. I just need to figure out a way to stop the carkit from importing contacts, because removing thousands of email contacts is obviously not an option.
I'll keep this topic updated with any progress. If anyone has any other ideas, please keep em coming. Thanks for the help so far!
ItzCrooK2UxD said:
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
Click to expand...
Click to collapse
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Apoc_ said:
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Click to expand...
Click to collapse
It reads a file that is being constantly updated (which happens to be the logcat file). Typically I will clear it right before doing what it took to cause the failure, like in your case in your car with the bluetooth on.
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
YoghurtPL said:
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
Click to expand...
Click to collapse
Yep - I have that too. The weird thing is that in that situation the phone does seem to think it is connected, while it really isn't. Just to be clear: this is not the only way to cause this issue (because it also happens when trying to reconnect the Bluetooth while on the phone it hasn't been disabled in the meanwhile).
So far I haven't been able to pull anything related from the logcat.
Also, while reading up on common bluetooth issues, I came across some posts of people who were saying that some phone/carkit combinations are having trouble with 2-way communication (because I can stream music from the phone to the carkit, but I can also change a song using the carkit or initiate a phonecall from the carkit). I'm going to try to only use communication initiated from the phone, and see whether that makes any difference. In the meanwhile: does anyone happen to know anything about 2-way communication issues with bluetooth, and how to overcome such issues?
Update:
- Updated carkit to latest firmware. No change, still same problem
- Have not been able to capture anything unusual in the logs
- I have a Bose Soundlink now, which is a wireless speaker. Whenever my S3 is connected to the Soundlink (with bluetooth), wifi doesn't work. Upon turning off bluetooth, wifi instantly works fine again. So this definitely confirms this is a problem with bluetooth on the phone, not on the carkit.
- Wanted to upgrade to Android 4.1.2 but Samsung won't let me, as it says the device is modified (rooted). Triangle away isn't helping. Damn you, Samsung. This is *the* reason I moved away from Apple, as I don't like companies who don't let you use your stuff any way you like. And now Samsung is moving down the same route. Idiots. Anyway, I guess the only option left, is to start using a custom ROM.
Does anyone happen to have experience in terms of solving bluetooth problems by using a custom ROM? I'm thinking of using Cyanogenmod 10.1
In the meanwhile I have upgraded to Android 4.1.2: still the same problem.
I have also discussed this matter with quite a few other Samsung smartphone owners, and all of them appear to be having the same issue. Most of them just don't seem to be bothered to spend time on looking for a fix.
Also, I have figured out that this problem is specific to media streaming. I'm able to use my phone on the carkit for calls at any time, without having to reboot first. Only when I try to listen to music, the problem occurs.
Anyway, I have ruled out that this problem is specific to me or my devices - this appears to be a global issue. So I'm completely puzzled as to why there's not a lot more fuss going on about this.
If anyone has any more suggestions for a resolution of this problem, please share.
S3 bluetooth connection problem
Had the same problem with my S3 and renault megane III handsfree bluetooth system.(Arkamsys software version 2.2.0.19 auditorium)
I downgraded to 4.0.4 baseband I9300CELH1 (stock) and problem seems fixed
hope this helps.
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Carkit bluetooth issue
Apoc_ said:
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Click to expand...
Click to collapse
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Bennes18 said:
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Click to expand...
Click to collapse
BB only, try this :
http://forum.xda-developers.com/showthread.php?t=2106424
Confirmed the update thing, i have updated the S3 to version 4.1.2 BB I9300CEELL1 and have no bluetooth issue whatsoever, car audio still on 2.2.0.19 byt the way
Pretty strange ... , but glad its working !
I have the same issue with a Ford Focus =/
also, while using CM or Omega, the music title never changes.
Anyone else having problems with the LG G Watch re connecting to their phone? Recently my watch doesn't re connect after I've walked away from the phone far enough to loose the blue tooth signal but then return to the phone.
Sometimes if I turn off blue tooth for about a minute and turn it back on it connects and other times once the blue tooth is off it won't turn back on and can even seem to knock out the wifi connection on the phone as well. A full reboot of the phone seems to bring it back. Toggling the connection within Android Wear doesn't re establish the connection.
I've just upgraded to KGW42Q (4.4W.1) on the LG G Watch (Gohma 1.1 b1) and Cyanogenmod nightly from the 11th of September on my S4 I9505 however it was happening before both of these updates. Even tried a full data wipe and factory reset on the phone and a resets on the watch but this hasn't helped either.
Any advice will be gratefully received
Same problem. Anyone know the solution?
Do you install BeeLink for android wear? These was my problem. I uninstall, and solve the problem
ruben_limit said:
Same problem. Anyone know the solution?
Click to expand...
Click to collapse
In the end I solved it by going back to a backup I had based on a cyanogenmod nightly from July. Really odd but I think it must have been some kind of rom compatability.
I had the same problem with gohma 1.1 b1.
I have stock rom now and no problems.
My RAZR worked perfectly with CM12, but ever since I started using CM13, my Bluetooth begins to stutter or will not remember paired devices. I will need to reboot, then my paired device is not present, I need to Repair. I turned OFF Smart Lock (Trust Agent) from Google, this seems to make it worse.
When I do have BT working, it will work for a while ( < 15 min ) then it will start to stutter, and will not reconnect when I turn off BT then back on, I need to reboot.
I tried Clean Flashing numerous times, with no luck, It's definitely a coding error since I tried my phone on numerous BT devices, and it does it every time.
I turned off Smart Lock (Google Trust Agent) since this was always asking to setup every time I pair my device and I thought this was the problem but the problem remains.
My last build was 20160304-Nightly-spyder, (Yesterday's build).
I had the same problem on latest CM13 umts spyder. I was fed up and went back to stock ROM (ICS), which works perfectly not only with bluetooth, but in every other respect as well. It's a much smoother experience to CM13.
EDIT: Oh man. 4.0.4 doesn't support TLS 1.1 or 1.2.
I think I might go back to CM11/12/12.1.
EDIT2: I'm going to try MoKee ROM: http://forum.xda-developers.com/showthread.php?t=2596176
I'll get back to you and see how bluetooth is.
EDIT3: MoKee ROM killed itself (it started doing weird things from the get go, like asking me for my google account during the welcome phase after I had already logged in), and I didn't have enough time to test bluetooth with my cars headunit, which is where your symptoms occur for me, but I was able to test it on my PC's bluetooth dongle, where it showed the exact same symptoms as CM13 did. That is, I would have to reinitiate the pair every single time my phone connected, and not only that, but I would end up in a pairing loop, where as soon as I'd accept the pair, it would ask me again to accept a new pair, ad infinitum. Given this, I'm going to conclude that MoKee ROM's bluetooth is not the answer for our problem. By the way, the next time I booted MoKee ROM it reinitated the updating apps thing at startup, like I had just wiped cache (which I hadn't), and after I let it finish, it never booted properly.
The latest CM13 has an interesting commit: http://review.cyanogenmod.org/#/c/137459/
It might just solve one aspect of our problem so I'm going to test it and come back to you.
EDIT4: Nope. Same problem with headunit and dongle. FYI headunit is Pioneer MVH-X380BT (not old).
EDIT5: I'm on LiquidSmooth KitKat and I've called it a day. Bluetooth works as it should.