Serious Bluetooth issues after KitKat 4.4.2 update

Search This thread

Blipstein

Senior Member
Apr 5, 2011
192
7
I just updated to 4.4.2. Been having Bluetooth issues in my Lexus ever since. I can establish a connection but my contacts will no longer transfer. The Bluetooth music intermittently disconnects and reconnects. I havent made any BT calls yet so I don't know how that is behavin. My messages won't transfer as well (call logs do though). I have un-paired and re-paired the phone several times. Usually that does the trick. I am a Lexus Technology Specialist and I deal with these little BT issues all of the time. None of my tricks are working. So disappointed with KitKat right now.

Can I go back? Anything else I can try? Any help is appreciated. Thanks
 

cmdauria

Senior Member
Oct 18, 2008
660
255
Tampa
I just updated to 4.4.2. Been having Bluetooth issues in my Lexus ever since. I can establish a connection but my contacts will no longer transfer. The Bluetooth music intermittently disconnects and reconnects. I havent made any BT calls yet so I don't know how that is behavin. My messages won't transfer as well (call logs do though). I have un-paired and re-paired the phone several times. Usually that does the trick. I am a Lexus Technology Specialist and I deal with these little BT issues all of the time. None of my tricks are working. So disappointed with KitKat right now.

Can I go back? Anything else I can try? Any help is appreciated. Thanks

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?
 

Blipstein

Senior Member
Apr 5, 2011
192
7
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?

I'm on KitKat. Just did the official download Sunday. Only other issue so far is that Astro player (music player I use for listening to Howard Stern. Great for bookmarks since the tracks are 4.5 hours long) is acting weird about the music files. Hard to explain but just odd behavior.

If it was a bad download is there a way to re-download it? I suppose the only way to go back would be to root and flash a ROM?

Thanks dude
 

micmars

Inactive Recognized Contributor
May 1, 2013
10,323
19,050
Tampa Bay
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
 
  • Like
Reactions: Blipstein

Blipstein

Senior Member
Apr 5, 2011
192
7
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
 
  • Like
Reactions: micmars

micmars

Inactive Recognized Contributor
May 1, 2013
10,323
19,050
Tampa Bay
Last edited:

Blipstein

Senior Member
Apr 5, 2011
192
7
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

I'm not rooted. Haven't been since my EVO days. Does this mean I'm out of options?
 

micmars

Inactive Recognized Contributor
May 1, 2013
10,323
19,050
Tampa Bay
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
 
  • Like
Reactions: Blipstein

Blipstein

Senior Member
Apr 5, 2011
192
7
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
 
  • Like
Reactions: micmars

micmars

Inactive Recognized Contributor
May 1, 2013
10,323
19,050
Tampa Bay
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

I use bluetooth daily as well, but via a headset, not the setup you've described.

As to reverting to ICS, it doesn't appear to be possible for you on this device, as this phone came with 4.3 out of the box, whereas 4.04 was compatibility ancient. Many core features of Android just are not available, including Google Now.

I am at a loss here, but I wonder if a call to Samsung would at least bear fruit, as they have a lot of phones running KitKat. Hit them with the Lexus disfunctionality, you deal with a lot of cars, and this phenomenon hit when KitKat hit.

Perchance a senior level tech could troubleshoot with you. It's a good demographic to want to please and not irritate. You've got an incentive for them to help.

Sent from my SM-N900P using Xparent BlueTapatalk 2
 
  • Like
Reactions: Blipstein

DAvid_B

Senior Member
Jun 29, 2007
343
106
Have you done a master reset since the update?
It's a pain but that will tell you if it's a compatability issue or just something that hung around after the update.
 

Blipstein

Senior Member
Apr 5, 2011
192
7
I have not. So maybe try a "factory data reset"? Will the device still have the KitKat update?
 

micmars

Inactive Recognized Contributor
May 1, 2013
10,323
19,050
Tampa Bay
I have not. So maybe try a "factory data reset"? Will the device still have the KitKat update?

Yup. Resets everything to either stock in system, or retains any system mods you've made. Thus, if an inverted app resides in system priv-app and the other one is gone, the invert will still be there afterwards.

Sent from my SM-N900P using Xparent BlueTapatalk 2
 

Blipstein

Senior Member
Apr 5, 2011
192
7
Called Samsung. They want me to go to a sprint store and reflash KitKat. Gonna try that. I'll report back
 

RayTrue04

Senior Member
Oct 27, 2010
1,786
523
Hartford, CT
Called Samsung. They want me to go to a sprint store and reflash KitKat. Gonna try that. I'll report back

Have you tried a simple unpairing/repairing after the update? That's one thing I've always had to do a lot on Samsung phones (sometimes over and over like 3 times) after a big update or else it would act stupid and not work correctly.

Sent from my SPH-L900 using xda app-developers app
 

micmars

Inactive Recognized Contributor
May 1, 2013
10,323
19,050
Tampa Bay
Have you tried a simple unpairing/repairing after the update? That's one thing I've always had to do a lot on Samsung phones (sometimes over and over like 3 times) after a big update or else it would act stupid and not work correctly.

Sent from my SPH-L900 using xda app-developers app

I think he indicated that in the OP.

Sent from my SM-N900P using Xparent BlueTapatalk 2
 

Blipstein

Senior Member
Apr 5, 2011
192
7
wondering if the trip to the sprint store fixed your issue because i have the same issue.

Hey... Sorry I didn't get back to you guys. I did a "factory data reset" and that seemed to have fixed it. Didn't go into the sprint store.

My contacts won't update in my car but it did it at least once right after the reset so at least my contacts are there. I bet a re-pairing will take care of that. Bluetooth audio and phone have been consistently working correctly. Hope this helps you out
 

Aloth600

Senior Member
Mar 30, 2009
67
4
Englewood, Colorado
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
 

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