Related
Since I upgraded my AT&T Galaxy S3 with the official Jelly Bean update last week, my bluetooth pairing with my car has not worked.
At first, I was continuing to use the existing pairing which was set up and perfectly working in ICS. Whenever I made a call from my car ('09 BMW 3-series, bluetooth phone via built in nav system), there would be a loud pitch sound when the call was answered and then connection lost.
So I unpaired, and re-paired.
But now it does not work at all. Connection keeps dropping every few seconds. I have not even managed to get the data sync (transferring of contact data from phone to car) to complete.
This is beyond me. Jelly Bean is great, but it is not worth the price of not having properly functioning bluetooth.
Any suggestions? Anyone with similar issue? Is it possible to somehow roll back to ICS?
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
nsmith4 said:
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Thanks for your response.
I have not (yet) tried a factory reset, was sort of hoping to avoid the hassle of having to restore my data and apps. But I will eventually resort to it, if nothing else can fix it.
Good suggestion with regards to erasing from car memory. I am not sure if or how that can be done, but I will try and look through the settings to see if I can. (what I have done so far is just "remove" the device from the list of paired devices...
nsmith4 said:
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Pretty sure this is the actual cause of your problem.
HiKsFiles said:
Pretty sure this is the actual cause of your problem.
Click to expand...
Click to collapse
I went through all possible options in my car's nav system (xDrive) and I do not see any options to delete the car's memory.
So the only option as far as I know is to remove the device from the list of paired devices before pairing it again. And I tried that already...
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Ok. So I resorted to restoring to factory settings.
With it clean, before restoring backup (made with Titanium), I went to my car and paired.
It worked - it synced the (very few, AT&T default) contacts, and no dropping (as far as I waited, a few minutes).
This was good news.
So I went back up and restored all app data, signed into Google account to sync all contacts etc.
Then back down in car and connected.
Problem is back It won't sync the contacts and continously drops and reconnects.
Well at least I have a reference point to go back to now and perhaps take one step at the time.
I was thinking next step is to restore to factory settings again, then ~only~ add google account to sync up contacts, then try. If that works, restore one app at a time to see if I can isolate the issue.
I will do this tomorrow.
mrhaley30705 said:
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Click to expand...
Click to collapse
I just did this. I am however too tired for the day and will check first thing in the morning, if this resolved it (as I am back in the problem state) - before resetting and starting all over (ref. my above mentioned thoughts of how to do a gradual restore)...
Thanks all for your input so far - I cannot tell you how much I appreciate it. This forum rocks so far.
/Lars
Progress this morning:
First of all, I tried as suggested clearing data for Bluetooth Share. Didn't fix the problem.
I know now that if I pair the phone and connect after factory reset, with the contacts list on the phone at default/almost empty (11 pre-defined AT&T numbers), it works.
So what I did this morning:
I factory reset the phone again. Then I added my Google account to sync up contacts list from my GMail account.
I ~only~ did this. No apps installed or restored.
Paired and connected. And I have the problem.
So this seem to somehow be caused by my contacts list after it has synced up with Google.
Any suggestions?
I am thinking that if I cannot get this resolved, I want to roll back to ICS. Having no functional bluetooth pairing with my car is not an acceptable tradeoff, no matter how great JB is. Is there a way to roll back? Can I get the official ICS ROM from AT&T, if needed?
But of course - this will be my final solution; I much prefer to get this resolved. I am open to any suggestions re. my contacts/google account.
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Deoxlar said:
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your feedback.
Can I ask, if you know where this problem is perhaps discussed?
I looked in the developer forum, but must admit I am confused which thread/which ROM you are referring to. Are you talking about a modified stock ROM? I would greatly appreciate a link if it is...
Today's update:
At work we have a Galaxy S3 AT&T device (identical to my own) for testing purposes.
I just upgraded it to Jelly Bean today and then added my gmail account to it, paired to my car - and the same problem.
So at least that rules out an issue with my specific hardware/phone.
I also tried using a Galaxy Nexus (Verizon version) from work. Issue did NOT happen.
I then flashed my own phone with the stock Jelly Bean ROM downloaded from here:
http://forum.xda-developers.com/showthread.php?t=1739426
Same issue happens
So my final solution (at least for now):
I flashed to the stock Ice Cream Sandwich ROM (downloaded from same place as listed above).
It works now.
Funny how one can be so happy with a downgrade, but I am
Thanks all for all your input.
I am still open to any suggestions (as I would love to be on Jelly Bean in the future), and I have an easy way to test possible solutions on my work test device...
Thanks again!
Lars
Hey, I am having Bluetooth problems as well. I have the sprint s3 stock jb. My blue tooth will not connect to my moga controller. Everything I have been reading points at it being a software issue on Samsung JB devices. Can anybody else confirm this?
Sent from my SPH-L710 using xda premium
Aren't the bluetooth "drivers" in the kernal? Perhaps using a different, or going back to a stock kernal.
I was having a similar issue with my phone not automatically connecting with my car. It would connect if I cycled BT off then on. All this on Tasks 4.1 rom & KT's kernal.
Flashed with the new 4.2 rom & kernal and it seems to be fixed.
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
crazililazn said:
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
Click to expand...
Click to collapse
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Bluetooth in car only has voice audio, no ability to control the phone
Ansextra said:
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Click to expand...
Click to collapse
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
rohanverma said:
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
Click to expand...
Click to collapse
It's a know JB problem. No solution right now
Ironically, I had the same exact bluetooth problem the OP describes, but it happened with my stock ICS ROM. Made trying to call someone extremely frustrating since I have a stickshift!
The problem disappeared with my upgrade to the 4.1.1 stock ROM. I have also had no issues at all with any 4.1.2 JB custom ROM.
I believe it is a generalized issue with Android, because the problem I had with ICS was not reproducible when using a different bluetooth headset. Only my own would cause the problem. As soon as I realized that the problem no longer existed in 4.1, I began using my own headset again, and have done so without a single dropped call.
BWolf56 said:
It's a know JB problem. No solution right now
Click to expand...
Click to collapse
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
rohanverma said:
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
Click to expand...
Click to collapse
Umm just to clarify, firmware goes like this (in order): Eclair, Froyo, GB, ICS, JB. So JB is the latest.
Here's a JB fix for BT: https://dl.dropbox.com/u/28275651/REVERT-MY-ALSA.zip
Flash it in recovery, clear cache and dalvik and hopefully it will work.
Does anyone know if the Bluetooth SMS MAP protocol is supposed to work in 4.2.2 AOKP (I'm running milestone 1)? My Honda Civic doesn't think the phone supports it, so I'm guessing it's not working, but wanted to make sure there wasn't something I was missing. Also, I'd love to know if anyone is working on it or knows what the status is. I moved from an old hacked-up CM10.1 over to AOKP hoping maybe this had been fixed/was working, but alas, it looks like I'm still out of luck.
If I had more time, I'd offer to fix it up myself (and may still) if someone could point me in the right direction to get started. From what I saw in old posts back during the CM9 days this was working, so it seems that it'd be possible to revive without too much deep knowledge of the protocol itself (some already did the hard work)...
-Daniel
Okay, does anyone know if any of the 4.2.x ROMs support bluetooth sms map?
dath1974 said:
Okay, does anyone know if any of the 4.2.x ROMs support bluetooth sms map?
Click to expand...
Click to collapse
well there are known bluetooth issues with 4.2.2 roms
I have a bluetooth headset which seems to work fine...
however I have a bluetooth mouse which recognizes but doesn't work in 4.2.2 roms
All 4.1.2 roms built off official stock seem to have bluetooth working fine...
hope this helped m8
In JB, a new Bluetooth stack was implemented. The MAP profile code, which was added to AOKP in ICS, is no longer valid. From what I have read, the new BT stack is not open source, so devs will not be able to reimplement MAP, at least for now.
Sent from my SGH-T959 using Tapatalk 2
Hi and thanks for help first off,
Bought a T-Mobile S3 flashed to CSROM Tha BMB v.1.2 with Hardware version: REV 0.4
I flashed a few phones previously but barely knew what I was doing then and haven't a clue now TBH.
So - bought a new Nav/Phone/Stereo for my car this weekend (Pioneer AVIC-X9310BT). Has BT phone support but can't get it to recognize/talk with the stereo at all. Phone says it's rejected or can't communicated with the stereo but stereo has no troulble connecting to other phones so it's something with the hack/Rom I'm guessing.
My pref. would be to do something to my current rom to make it work (done all the reboots and such - no luck). If this is possible - tell me what to do. (Remember, I'm an idiot on this stuff now days)
If not - my Q is - what current ROM would you guys suggest I DL and install to try and get it to work with my stereo.
In truth there's only two things I need from my S3.
- Ability to tether to my ipad
- Ability to be used with my stereo
Other than that - I'd really be fine with stock S3 wares... but... as I know - to have the ipad tether (without paying extra... I'm on Solavei service)... I have to at least stay hacked... so...beyond that... what's EASY to install, can tether and has the BEST chance (stable/near stock) to syncing up via BT with my stereo.
TIA
jtiis
jtiis said:
Hi and thanks for help first off,
Bought a T-Mobile S3 flashed to CSROM Tha BMB v.1.2 with Hardware version: REV 0.4
I flashed a few phones previously but barely knew what I was doing then and haven't a clue now TBH.
So - bought a new Nav/Phone/Stereo for my car this weekend (Pioneer AVIC-X9310BT). Has BT phone support but can't get it to recognize/talk with the stereo at all. Phone says it's rejected or can't communicated with the stereo but stereo has no troulble connecting to other phones so it's something with the hack/Rom I'm guessing.
My pref. would be to do something to my current rom to make it work (done all the reboots and such - no luck). If this is possible - tell me what to do. (Remember, I'm an idiot on this stuff now days)
If not - my Q is - what current ROM would you guys suggest I DL and install to try and get it to work with my stereo.
In truth there's only two things I need from my S3.
- Ability to tether to my ipad
- Ability to be used with my stereo
Other than that - I'd really be fine with stock S3 wares... but... as I know - to have the ipad tether (without paying extra... I'm on Solavei service)... I have to at least stay hacked... so...beyond that... what's EASY to install, can tether and has the BEST chance (stable/near stock) to syncing up via BT with my stereo.
TIA
jtiis
Click to expand...
Click to collapse
Probably ROM issue, try S3Rx or Dandroid.
Yup, I hear about BT problems all the time on CM/aosp roms. Try aerowinders suggestions first, but if you don't like the roms, just make sure you stick to stock, touchwiz based ones and BT should work.
Sent from my SGH-T999V using Tapatalk 4
Hi, I have a Chevy Volt and a Galaxy Note 2. When I was on a 4.1.2 based ROM, the integration with the car worked automagically (once BT paired). I recently updated to a 4.4 ROM (OmniRom), and now the link is broken. I can play audio through the BT as before, but the push to dial commanding will no longer dial the phone. The car just says "dialing failed", but the phone never even tries to dial! I think this may be a 4.4 issue because I had the same problem with another 4.4 CM based ROM.
Anybody have similar experiences, know of a workaround or way to get it to work?
Thanks!
lrsmr2 said:
Hi, I have a Chevy Volt and a Galaxy Note 2. When I was on a 4.1.2 based ROM, the integration with the car worked automagically (once BT paired). I recently updated to a 4.4 ROM (OmniRom), and now the link is broken. I can play audio through the BT as before, but the push to dial commanding will no longer dial the phone. The car just says "dialing failed", but the phone never even tries to dial! I think this may be a 4.4 issue because I had the same problem with another 4.4 CM based ROM.
Anybody have similar experiences, know of a workaround or way to get it to work?
Thanks!
Click to expand...
Click to collapse
Probably just go back to a Touchwizz based rom (Lots of 4.3 available) and you should be fine. But there may be other options but thats a suggestion
Yes as a test, works on 4.3, but
As a test, I loaded a 4.3 ROM and after I set the BT options for both media and phone it worked fine. I'm going to reload a 4.4 rom and see if it was simply that I did not have the BT set for audio and phone. duh.
Remember to update once you've tried it out. Could help out others in your situation.
no 4.4 yet, plan to though
Still running 4.3. SkyNote works pretty well, so I'm reluctant to move now.
Lots of threads about 4.4 BT problems. Sorry.
when I had kitkat on my Note 3 I had my phone paired via Bluetooth to my car radio. When playing music it would show the song name, artist, album etc and I could play, pause etc the song. I got the lollipop update, and it deleted all of my Bluetooth connections. So I paired my phone back up to my radio and now it doesn't show anything, no song, artist, album etc and I can't control the music anymore. I have done all of the troubleshooting steps I have been told to do and nothing has worked. Are other people experiencing the same issue? Is there a fix? Please help! Thanks in advanc!!
Bump.
Th3Nigh7Stalk3r said:
when I had kitkat on my Note 3 I had my phone paired via Bluetooth to my car radio. When playing music it would show the song name, artist, album etc and I could play, pause etc the song. I got the lollipop update, and it deleted all of my Bluetooth connections. So I paired my phone back up to my radio and now it doesn't show anything, no song, artist, album etc and I can't control the music anymore. I have done all of the troubleshooting steps I have been told to do and nothing has worked. Are other people experiencing the same issue? Is there a fix? Please help! Thanks in advanc!!
Click to expand...
Click to collapse
Have you tried clearing the data for bluetooth apps and reconnecting to the car? Is under settings, applications.
I have cleared the data and cache from the Bluetooth app. Impaired the radio from the phone and vice versa. Still hasn't fixed it. It will play music through the radio. Just no info or metadata as people call it.
That means your Bluetooth radio is not compatible with lollipop... Simple features that are universal like calls and pairing will work but that's it. ..It's got nothing to do with your phone and you can't do anything to fix that. ..
Thank you for the help! Would have never guessing that! Guess I need to get a new radio now.
How did you update to lollipop?
Kies?
OTA?
Odin?
Have you tried a reflash?
Pp.
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
What kind of car radio?
Factory?
Aftermarket?
Pp.
Th3Nigh7Stalk3r said:
Thank you for the help! Would have never guessing that! Guess I need to get a new radio now.
Click to expand...
Click to collapse
Yeah I had a Pioneer from 3 years ago 7 inch screen top of the line and the same thing happened, so last week I went and bought the new Pioneer same type just a newer version and everything works again so it's definitely the radio... Unless they have updates for the radio, the updates for your phone will supersede the radio because they didn't have lollipop in mind when they made the radio and there are things that have changed in the software... I hope that helps
These functions are bluetooth standard functions, not something that is lollipop or kitkat specific. If that were the case, all of your accessories (BT headsets, etc.) would lose the ability to control music as well.
OP: What is your baseband version, and your actual ROM version? It's possible that when you got your update, your baseband didn't update, and thus the BT interaction via the SDK in the os isn't passing the data to the BT radio correctly.
toastido said:
These functions are bluetooth standard functions, not something that is lollipop or kitkat specific. If that were the case, all of your accessories (BT headsets, etc.) would lose the ability to control music as well.
OP: What is your baseband version, and your actual ROM version? It's possible that when you got your update, your baseband didn't update, and thus the BT interaction via the SDK in the os isn't passing the data to the BT radio correctly.
Click to expand...
Click to collapse
Not true I've been in car stereo for 25 years and I'm MECP certified... There's Bluetooth 1.0, 2.0, 3.0 and now 4.0... Lollipop is 4.0 and it is different and they will have different effects on other versions of Bluetooth... You can say I'm wrong, but I'm not and you will never get it to work no matter what your baseband phone or anything like that is... Lots of manufacturers have updates to make their Bluetooth compatible if you don't update your Bluetooth device it will become obsolete and only the basic features will still work
Ohhhhkay. Lol.
I have both a Note 4 that has upgraded to Lollipop and a new S6 (obviously with Lollipop), and both pair and connect find to 2 different cars, but I have lost music controls with apps such as Slacker and Pandora. Interestingly enough, music controls are okay with Google Play Music. I can't even control the music with Android Wear. I don't think wiping cache or factory resetting will affect any of this since it's happening with the S6, which is brand new. This has to be a Samsung Lollipop thing, because the HTC One M9 has no issues like this.
It's probably more of a Google / Samsung thing, I like controlling all my music apps especially pandora from my Kenwood DDX719 which doesn't play well with my Note 3 on lollipop.
So far using my S4 still running kitkat but have a S6 edge on my radar for June, hope there's a workaround by June.
Pp.
Omg I've been in car stereo for 25 years and I'm trying to tell you guys has nothing to do with the phone, older radio will not be compatible with lollipop no matter what you do so stop wasting your time get a new radio or deal with it please this guessing is is killing me... You must check your manufacturer of your radio to see if its compatible with lollipop, doing something to your phone is not going to make it work... I really hope this helps all of you
The only thing to do is to revert back to kitkat, as far as the phone is concerned or new stereo hu.
I'm good with that.
Until I get the S6 edge, then it's curtains for the Kenwood I have, just hope Kenwood comes out with something that's lollipop friendly.
Pp.
PanchoPlanet said:
The only thing to do is to revert back to kitkat, as far as the phone is concerned or new stereo hu.
I'm good with that.
Until I get the S6 edge, then it's curtains for the Kenwood I have, just hope Kenwood comes out with something that's lollipop friendly.
Pp.
Click to expand...
Click to collapse
Try the pioneer nex line. I just got the 4100 and it has android auto and it's great made only for lollipop...
I'm going to wait for Kenwood to take the next step concerning Android functionality and move in that direction.
Been buying and using Kenwood for over 30 yrs, can't see myself buying pioneer.
Pp.