Database Users

[Q] Bluetooth turns off 4.4.2

Any one experiencing any problems with Bluetooth on 4.4.2?
The problem I am having is that I can't turn on my Bluetooth without rebooting the phone and when I do reboot the phone and turn on the bluetooth it turns off by itself even if something is connected to it
I side loaded 4.4.2 to my nexus 4 with 4.4.1 using the 4.4.1 to 4.4.2 update image.
I hadn't had any problems with the previous releases 4.4 (16O or 16S) or 4.4.1.

martyd1901 said:
Any one experiencing any problems with Bluetooth on 4.4.2?
The problem I am having is that I can't turn on my Bluetooth without rebooting the phone and when I do reboot the phone and turn on the bluetooth it turns off by itself even if something is connected to it
I side loaded 4.4.2 to my nexus 4 with 4.4.1 using the 4.4.1 to 4.4.2 update image.
I hadn't had any problems with the previous releases 4.4 (16O or 16S) or 4.4.1.
Click to expand...
Click to collapse
i had that problem after i sideloaded the update 4.4.2.
reboot to cwm and wipe dalvik cache and cache of system (worked for me).

sid.8491 said:
i had that problem after i sideloaded the update 4.4.2.
reboot to cwm and wipe dalvik cache and cache of system (worked for me).
Click to expand...
Click to collapse
sorry forgot to mention that i was running ART so i switched it back to dalvik after you metioned about it and it seems to have worked. its still holding the bluetooth connection.
thanks

martyd1901 said:
Any one experiencing any problems with Bluetooth on 4.4.2?
The problem I am having is that I can't turn on my Bluetooth without rebooting the phone and when I do reboot the phone and turn on the bluetooth it turns off by itself even if something is connected to it
I side loaded 4.4.2 to my nexus 4 with 4.4.1 using the 4.4.1 to 4.4.2 update image.
I hadn't had any problems with the previous releases 4.4 (16O or 16S) or 4.4.1.
Click to expand...
Click to collapse
Ive got the same problem. My nexus has never been rooted. i had to go back to 4,4 to get it to work.

I have a Bluetooth-related problem, in that the music player launches any time a Bluetooth device connects. Even my smartwatch, which doesn't have any audio functions. I guess I should try wiping the caches and see if that helps. That's the only problem I've noticed. Haven't had any trouble with Bluetooth disconnecting while using it.

I have the same issues with my bluetooth connectivity.
Yesterday I updated my rooted 4.4 16S via OTA Update to 4.4.2 KOT49H and bluetooth worked just fine. But today it switched itself off and wouldn't let me turn it on again unless I rebooted the device.
Will keep an eye on that and if it isn't bearable, I will have to go back to 4.4

The same problem. BT drops connection or swiched off by itself and then impossible to turn it on without reboot.
Fixed it by flashing old radio from 4.4. Now testing. So far no issues.

[HELP] Samsung S5 [SM-G900M] Sound issues after latest Marshamallow 6.0.1 update

Hi!
After the latest Marshmallow Update 6.0.1 I'm facing some sound related problems. My phone doesn't recognize the headphone/earphones when connected.
During calls, when I plug the conector, the icon of headphone doesn't appear in the upper side and the sound still being release from speakers.
After some google research, several users of several phone brands reported the same issue. I installed SoundAbout app to test and worked fine, except for the calls.
I'm using official stock ROM and tried to several reboots, wipe cache, factory reset and nothing happened.
Could someone please help me?
Thanks and regards!

And the saga continues...
UPDATE:
- Rolled back to firmware 5.0 and the issue continues.
- Forced new update through OTA, issue still happening.
I have a guess that this new firmware update changed the headphone/earphone hardware driver, so even with several actions the problem wasn't fixed.

syneval said:
UPDATE:
- Rolled back to firmware 5.0 and the issue continues.
- Forced new update through OTA, issue still happening.
I have a guess that this new firmware update changed the headphone/earphone hardware driver, so even with several actions the problem wasn't fixed.
Click to expand...
Click to collapse
Try a full wipe

Dramane Traoré said:
Try a full wipe
Click to expand...
Click to collapse
Thanks for the reply!
I've already done it.
Factory reset; wipe data; wipe cache partition.
I don't know what else I can do...

Any news?
Hey guys... Any news?
Even in safe mode, Android doesnt recognize the earphone/headphone connected...
I downgraded version, updated through OTA... updated all security patches and nothing...

Your hardware is probably broken, you should try replacing connector in the phone,

I've had similar issues. headphones work but the wired remote controls don't and the sound is like its under water. Music is all messed up like it's being really heavily processed. through the speaker it's fine. Calls and music are all the same through headphones. Tried different headphones!
Stock Marshmallow firmware, tried re-flash and factory default.

wielku said:
Your hardware is probably broken, you should try replacing connector in the phone,
Click to expand...
Click to collapse
I tested with different earphones/headphones... and the same problem happened. At first, I thought it could be an hardware problem... but with SoundAbout I could use the phones to listen music... now the problem is only with the mic.
Change the audio connector is not an option, since its too risky opening the board and it will make me lose the "water protection" not talking about the costs...
I'm still thinking it's a software problem, Today I'll try to perform a clean re-flash the marshmallow firmware factory dfault and see what happens...

How do i get off the beta?

I am currently on the newest beta 7.0, however I am experiencing echoed audio quality through Bluetooth in my car after I updated. I spend a lot of time driving an listening so this echo is driving me insane. So i de-registered from the beta, however how do I now roll back to marshmallow? I have tried factory resetting, and also manually checking for system update and no luck. Any help would be appreciated.

You will have to download and install smart switch on your PC. Once connected it will downgrade you to marshmallow or you can use odin to install the current marshmallow firmware

Robisgnarly said:
I am currently on the newest beta 7.0, however I am experiencing echoed audio quality through Bluetooth in my car after I updated. I spend a lot of time driving an listening so this echo is driving me insane. So i de-registered from the beta, however how do I now roll back to marshmallow? I have tried factory resetting, and also manually checking for system update and no luck. Any help would be appreciated.
Click to expand...
Click to collapse
I'm on the beta too and use BT audio in my car as well without a problem, so you might want to investigate if something else could be causing the problem. Have you tried clearing the cache in recovery?

Robisgnarly said:
I am currently on the newest beta 7.0, however I am experiencing echoed audio quality through Bluetooth in my car after I updated. I spend a lot of time driving an listening so this echo is driving me insane. So i de-registered from the beta, however how do I now roll back to marshmallow? I have tried factory resetting, and also manually checking for system update and no luck. Any help would be appreciated.
Click to expand...
Click to collapse
Just so you know, if you download Smart Switch and revert back to the last update (not Nougat) all of your info will be erased. I hopped off the Beta and thought it would simply revert me back to pre-nougat and it completely wiped everything and I never did a backup. So if you go back, make a backup if you can.

Robisgnarly said:
I am currently on the newest beta 7.0, however I am experiencing echoed audio quality through Bluetooth in my car after I updated. I spend a lot of time driving an listening so this echo is driving me insane. So i de-registered from the beta, however how do I now roll back to marshmallow? I have tried factory resetting, and also manually checking for system update and no luck. Any help would be appreciated.
Click to expand...
Click to collapse
All i use is odin no need for smart switch
Sent from my SM-G935P using XDA Free mobile app

As the others said. You will have to use smart switch to back up, download the stock sprint ROM, then load up Odin and flash the 6.0.1 stuff again. I was having the same issue. Try going into settings for sounds and turn on and off the concert hall setting and see if that helps. Also, even though you de register, my phone still downloaded the same PLN 7.0 beta 5 all over again and tried to install it all over....It's like your phone is always going to be a beta tester.

dhonzik said:
You will have to download and install smart switch on your PC. Once connected it will downgrade you to marshmallow or you can use odin to install the current marshmallow firmware
Click to expand...
Click to collapse
This worked perfectly, thank you! My audio in my car is again spot on!

Ramer said:
I'm on the beta too and use BT audio in my car as well without a problem, so you might want to investigate if something else could be causing the problem. Have you tried clearing the cache in recovery?
Click to expand...
Click to collapse
I did a full wipe of the phone while on the beta, and even on a brand new installation of 7.0 it was doing the same thing. once I got off the beta though and did the smartswitch back to marshmallow the Bluetooth issue cleared up.

Proximity sensor stays in "close" position

Nexus 6p, unlocked bootloader and running 8.1DP.
Whenever I make a call and put the phone to my ear the screen turns off and never comes back on. I tested the sensor with the device info app and I the sensor stays in the "close" position when engaged untill the app is restarted.
I did some research and I found that some users had this issue with the Nougat update but no relevant solutions were found and the 7.1.1 update fixed the problem.
I would like to avoid factory reset or locking the bootloader if possible.
Can anyone think of a possible solution?
I tried the Proximity sensor reset app from the play store and that does absolutely nothing.
EDIT: Stable 8.1 doesn't fix the issue, even after clean install and manual flash and wipe.

I'm on SuperXe 8.0 Oreo built and it works flawlessly. I remember having that issue on nougat ROMs use to drive me nuts. Every time I needed the keypad I had to fight to get the screen back on. ?

Not a factory reset. Manually wipe the phone and apply the latest 8.0 image.

So after manually flashing the 8.0 image everything worked. I thought id give 8.1 DP2 a shot and I wiped and flashed this manually. It worked during the restore but stopped working after all my apps were back, so I thought it may be an app that's causing the problem. Strated in safe mode, issue is still there. I guess Ill just have to wait for the stable 8.1 release. If anyone else is facing the issue please post here.

Bluetooth keeps closing/crashing....

Hey everyone,
since some days I'm having a problem with my Bluetooth. I can only enable it whenever my device is started but after that it keeps crashing whenever I turn it off/on. Runnign magisk on Stock Rom (Feb Update). Is there a way to reinstall just the Bluetooth app ?

Me too facing same issue , was not facing this when device was not rooted

I can use bt on my phone for a while until it randomly turns off and then sometimes on again after 10 seconds or so.
It started about 2 months ago. I think I was on 8.0.0 with feb update. Updates for march/april failed to install. May update installed successfully and unrooted my phone but the problem still persists.

My Bluetooth keeps turning off by itself, I don't understand why. I am on stock no root. I tried safe boot and it seems to not have the problem. How can I find out if and which app might be causing it?

Have the same issue
I just setup bluetooth tethering and all of a sudden app crashes. Stok 8.1.0 with July update

Anyone find a solution to this that doesn't involve rolling back updates?
Is it caused by root, or are non-root users getting it too?

Same issue, non root...