Serious Bluetooth issues after KitKat 4.4.2 update

Search This thread

DanNsk

New member
Aug 13, 2010
4
2
Guys, any stable fix or idea for that ?

I have t-mo version, but the issue is mostly same - my Mazda says pairing failed after kitkat update. And actually it's still possible to connect phone to a car (even if that is not well paired). But only using one of profiles - phone or media, but not both at the same time (that worked flawlessly on JB) and each time that's random - today i was able to use only media, but not as phone.


I have S3 which is still on JB and it's still works pretty well with a same car.

I tried resetting, re-uploading, but issue is still there.
 

beejmeister

Senior Member
I have done almost every fix for blue tooth I can find. The problem I am having is I connect my ear piece and make of receive a call and 10 to 30 seconds later it disconnects. The blue tooth icon still says connected. If I turn the ear piece off and then on it will reconnect only to do the same thing again.
I am on stock 4.2.2 rooted.
Any help would be great.

Things I have done:
Master reset
Pair and unpaired
Odin back to stock and re rooted

Ryan


Sent from my SM-N900P using xda app-developers app

+1 on this problem. I too have this problem. I'll keep watching this place. It looks like I may have to reflash back to stock and do a full factory reset to see if that fixes it. I did that when coming from Jelly Bean... went full stock... rooted that... and now on Josh's KitKat Killer. Had the problem on stock 4.4 but it seems to have gotten worse now with the custom ROM.

Hmmmmmm....
 
Personally for the op I would head to the T-Mobile section because I wouldn't want you to get suggestions and something happen to your phone by flashing not made for your model. As for post #2 try to reflash the nab stock via odin. Then reroot....I'm on Sacs ROM and I have no Bluetooth issues I pair with my stereo every time I get in the car and stream audio.

Sent from my SM-N900P using Tapatalk
 

NePanicPas

Member
Feb 27, 2013
17
14
Tampa Bay
Just chiming in with my observations on my SGS2 (i777). No troubles rooted with ShoStock JB ROM. Then, when I upgraded to KitKat, on both Render's CM and PacMan ROMs, connections are hit and miss. 50% of the time I get a connection (no media) and have to disconnect, turn off bluetooth on the phone, turn it back on, sometimes multiple times before I get a phone and media connection.

I'm trying to figure out if it's KitKat itself, or the individual ROM.
 

osmany21

Member
Nov 19, 2007
14
1
anybody found a solution on this? I just bought a new 2014 Lexus GS 350 and can't transfer contacts over. It says transfer fails. I can make calls and stream music but no contacts. Pretty upsetting. At the dealer they tried with other phones and worked fine seems to be my phone. They have tried with GS4 before and worked but was was before the 4.4.2 update.

Thanks,

Osmany21
 
Last edited:
May 24, 2013
17
0
Iv been facing the same issue with my note 2 as well.
I updated it via ota to 4.4.2, since then my bluetooth has been ****. Range reduced to like 2 feet. and WiFi keeps on getting disconnected.
If anyone has found a solution to then then please share.
Thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I have no idea what the platform edit is.... Lol. Please explain

    If you're rooted, unzip this file, then using root explorer, navigate to system, etc, permissions, rename the platform.xml file that already resides there (add bak to the name), then copy, paste, and set permissions with this file gifted to me by @blackcanopy.

    https://www.dropbox.com/s/enfjwbrxk2skzyu/platform.rar

    Lol®

    Sent from my SM-N900P using Xparent BlueTapatalk 2
    1
    I'm sorry that I don't have advice on how to fix your problem. I just wanted to let you know that I am having zero connection problems with the bluetooth to both of my vehicles. They are both Hyundai's if that makes a difference. Are you on the official KitKat or Freeza's "Stockish" rom. I am on Stockish deodex if that helps.

    Possibly bad download? Are you having any other issues?

    Did you try the platform edit?

    It might very well be that the bluetooth permissions granted by jellybean aren't allowed for KitKat. It would at least rule out that possibility.

    Sent from my SM-N900P using Xparent BlueTapatalk 2
    1
    Did you try the platform edit?

    It might very well be that the bluetooth permissions granted by jellybean aren't allowed for KitKat. It would at least rule out that possibility.

    Sent from my SM-N900P using Xparent BlueTapatalk 2

    I have no idea what the platform edit is.... Lol. Please explain
    1
    I'm not rooted. Haven't been since my EVO days. Does this mean I'm out of options?

    Not at all. I was just testing a theory, and thus it may not even work. If I'm wrong, you've blown Knox for nought.

    You could try reading up a bit on the new restrictive write permissions introduced by this flavor of KitKat (TouchWiz). If that is causing your problem, which it may very well be, then you should contact the manufacturer of your device (the bluetooth, not the phone), as I'm certain that you're not the only guy using that product. If yes, then others will be reporting the same problem, and the company will have to fix it. Time here is your option (ie, waiting for this to be a repeating headache for the manufacturer, so they do something about it).

    Rooting and flashing roms may not solve your issue. I'd suggest taking the approach with which you're most comfortable, and nothing more.

    Sent from my SM-N900P using Xparent BlueTapatalk 2
    1
    Not at all. I was just testing a theory, and thus it may not even work. If I'm wrong, you've blown Knox for nought.

    You could try reading up a bit on the new restrictive write permissions introduced by this flavor of KitKat (TouchWiz). If that is causing your problem, which it may very well be, then you should contact the manufacturer of your device (the bluetooth, not the phone), as I'm certain that you're not the only guy using that product. If yes, then others will be reporting the same problem, and the company will have to fix it. Time here is your option (ie, waiting for this to be a repeating headache for the manufacturer, so they do something about it).

    Rooting and flashing roms may not solve your issue. I'd suggest taking the approach with which you're most comfortable, and nothing more.

    Sent from my SM-N900P using Xparent BlueTapatalk 2

    Well...I am the manufacture of the product basically. The product is Lexus and I am the Technology Specialist for the dealership. I deal with BT all day long. I have not encountered this particular issue with an Android device. And if I have encountered it I have several processes that typically resolve the issue. None of them worked. So I am confident that the product (Lexus) is working correctly.

    I would really love to revert back to ICS. Is that possible somehow? Maybe re-load KitKat? I just want my phone the way it was because this issue is debilitating as I use BT everyday.

    Thanks