Bluetooth connection issues after MF9 - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

After the MF9 update the bluetooth in my phone have been sporadic to say the least. After getting it to connect to my BlueAnt Q3 finally. I've tried to get it to reconnect to my Toyota Venza and all I'm getting is errors. I've tried deleting the phones stored in the system to see if that solves it, but it hasn't. Keeps giving me "Errors connecting to Multi-car". Any ideas? I havent installed anything new at all.

any other bluetooth issues?

The MF9 update went fairly smooth for me, and no BT issues to report.
Did you perform factory reset after rebooting?
Are you rooted? (any mods?) How did you install the update? (OTA? Or did you flash?)

Related

Anyone having Wifi issues since update?

Installed the OTA update and re-applied unRevoked root. I can't maintain a wireless connection for long. I initially thought it was my router and rebooting the router actually does temporarily fix the problem but it happens again. How do I know it is not the router? My other wireless devices are working! I disable wifi on my phone and reconnect but still have no service. Rebooting the router is the only temporary fix. Gah.
I would say it may be the Rom over the OTA. That is of you're running a custom Rom or anything that's not stock. Are you running the latest radio? The .09.10,check to make sure. If your other devices are working without dropping then that eliminated the router for the equation. If you want to make sure then try connecting to any open WiFi connection to see if you have the same issue. If you do then u know for sure it's not your router.
I would try doing a nandroid first then wipe cache and davlik and flash your Rom again. Do not do a factory reset. Once you boot up just test the WiFi again b4 doing anything. If it works then just restore your apps if needed via Titanium backup.
If u have the same issue then at that point u can do a nandroid restore.
Multiple option,am confident one of them will work,good luck.
Sent from my PC36100 using Tapatalk
i had the same issue running fresh 3.3.0 .. and what i saw that my phone wasnt connecting at all but my laptop and my sisters top were all connecting. So i went into the wireless router ip address .. whatever yours may be. re-entered my password and WALA.. it started connecting to my phone again.. it was strange but thats what worked for me

Iconia keeps rebooting after stock ICS update

OK, I did search for this so...be nice if there is already a thread for this. lol
But, after updating my Iconia to the stock ICS rom, whenever I connect to any type of internet connection (wifi or bluetooth) my tablet reboots. Was wondering if this happened to anyone else and what I can do to fix it. Thanks for the help.
Same reboot issue after ICS upgrade
Hi,
I have just received my OTA update to ICS 4.0.3, and am having the exact same issue; the device is rebooting non-stop; it appears to do so right when trying to connect to wifi.
ACER - What gives? Any solutions? And preferably solutions NOT involving a hard reset.
TB.

[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.

Contacts not syncing via bluetooth to car now on 7.1.1

Just updated to 7.1.1 from 7.0 where all was well with the car (BMW 530 - E60), but now I have no contacts viewable from the car.
I've tried deleting the phone and repairing but still the problem persists, I can't see any contacts anymore on 7.1.1
Anybody have any idea how to fix?
Thanks in advance
Paul
my bluetooth isn't working with my 2011 GMC now that I've flashed 7.1.1 It connects for a second or two, then disconnects. This was an issue on the Pixel, but now its fixed on 7.1.1 not sure why 6P got screwed up
Google makes me mad
Bluetooth connects no problems in 7.0 to my 2011 Chev Cruze. Update to 7.1.1, drops every second. Flash factory image of 7.1.1 in hope that it might have been an OTA issue, and no luck. Flash 7.0 factory image, and bluetooth works and stays connected with my car. But after downgrading I lost the ability to restore all my apps and data, just had the Gapps. There wasn't an option to restore the info from my 6P previous to factory imaging it.. So now I have to manually search the apps out and reinstall them.
I just don't understand how Google keeps screwing this up. I'm grateful to have a Nexus and I can rescue myself, but it would be a piss off if I was not aware of how to get myself back to a place when the phone actually WORKED. It's just nonsense.
TREMER said:
Bluetooth connects no problems in 7.0 to my 2011 Chev Cruze. Update to 7.1.1, drops every second. Flash factory image of 7.1.1 in hope that it might have been an OTA issue, and no luck. Flash 7.0 factory image, and bluetooth works and stays connected with my car. But after downgrading I lost the ability to restore all my apps and data, just had the Gapps. There wasn't an option to restore the info from my 6P previous to factory imaging it.. So now I have to manually search the apps out and reinstall them.
I just don't understand how Google keeps screwing this up. I'm grateful to have a Nexus and I can rescue myself, but it would be a piss off if I was not aware of how to get myself back to a place when the phone actually WORKED. It's just nonsense.
Click to expand...
Click to collapse
If possible, can you post the 7.0 factory image? Thank you in advance
Sent from my SM-G928T using Tapatalk
2012 GMC Sierra. No Bluetooth issues at all with MM or Nougat 7.0. Side-loaded 7.1.1 OTA this morning, now my Bluetooth connection drops/connects repeatedly (every 2-3 seconds). Have deleted the BT device from phone & repaired, wiped cache, & rebooted with no success. Stock/no root here.
skydog1970 said:
2012 GMC Sierra. No Bluetooth issues at all with MM or Nougat 7.0. Side-loaded 7.1.1 OTA this morning, now my Bluetooth connection drops/connects repeatedly (every 2-3 seconds). Have deleted the BT device from phone & repaired, wiped cache, & rebooted with no success. Stock/no root here.
Click to expand...
Click to collapse
I have been having the same issue, but apparently no one in the threads of the roms I have flashed do not appear to be having that issue
Sent from my SM-G928T using Tapatalk
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work

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...

Categories

Resources