After rooting with instructions found here, my bluetooth doesn't stay on. If I hit on, it will turn off after a second. Do this a couple times and it freezes on "Turning Bluetooth On".
Things I have done:
Restarted
Fixed permissions (from TWRP and from other apps)
Force closed all BT related services
Checked logcat but found nothing related to BT
When I fix permissions from TWRP, the BT does turn on but it's like its stuck on connecting to a device it was last connected to before root. Then it turns off after a minute. It never actually connects to the device.
Ideas:
Recovering the BT services/apps from my original stock backup
Replacing BT services/apps with new apks
I am pretty familiar with rooting. I've rooted an S3, a Nook, a Kindle, etc. I understand the basics. But this is a little beyond me. Any help is much appreciated.
Related
So, before rooting, my One X had great Wifi connection. No issues. Now that I'm rooted, I can't connect to wifi to save my life. I tried the wifi fix (not the ROM, but the 3 files instead) and still nothing.
I've tried turning off Mobile Network while wifi was on, turning mobile network on while wifi was on, tried restarting the wifi....
I cannot get a connection to the Store, browsers won't open webpages, it's essentially done for. Yet every other device in my house can access the router just fine (and it's not just here, it's elsewhere.)
Anyone have any ideas how to fix this short of flashing the new ROM (which I can't do from my house since the HTC drivers always fail to install.)
Have you tried running fix permissions to see if there's some sort of error holding things up? The only other thing I could think to do is to do a factory restore of the phone, unfortunately...
I know there were some bluetooth issues in the past with 4.2.x roms.
Do we still have some lingering bluetooth issues?
I have searched for my problems however there seems to be no information that I can find yet.
I have had this issue where I can connect to my Zephyr heart rate monitor (same issue with my Polar as well) for the first time. All subsequent tries to connect to either HRM fails until I reboot the phone. Once rebooted, all works well again.
I had this issue with CM 10.1.2 stable, LS 2.9 (LS2.9 both with the LS kernel and KT747). Each rom was properly wiped and no Titanium backup.
This phone is actually a replacement due to the previous SGS3 getting messed up by my wife.
I had this issue with the previous phone, AND this replacement phone as well.
I have not tried this issue on the stock rom (replacement phone was on the stock rom for about 5 minutes before it got rooted.)
I have also not tried this on another 4.1.2 TW rom such as CleanRom. My assumption is that the TW/4.1.2 roms do not have this issue, but I have not troubleshot it to that level yet.
Does someone have a link to this issue? Or any other information about it? Anything is appreciated. Search seems to be failing me at the moment. I have been searching for several days for this info.
By the way, I did flash to stock last night to take my phone in to get a new SIM card. This replacement phone was not getting 4g. At least one of my issues is fixed now
I have loaded CleanRom onto the phone this time and I will be testing bluetooth today.
So far so good. I tested re-connecting several times with no issues.
As an aside, god I hate TW roms!
Anyway, it occurs to me that the app that I am using may be causing the issue with 4.2.2.
I am using Sportstracklive and it does have a setting that enables Bluetooth Insecure mode for SGS3 phones. I had this setting checked. My thought is that this setting on an SGS3 running an AOSP rom may be causing the bluetooth lockups.
I will nandroid back to LS2.9 and find out.
I think I have figured it out. It is the app that is causing the issue.
Sportstracker has a workaround that allows HRM bluetooth to use insecure mode instead of secure mode.
This works wonderfully in 4.1.x.
Evidentally, in 4.2.x Google totally redid the bluetooth stack.
If the app uses insecure mode on 4.2.x, when the app tries to shut off bluetooth (the app turns on/off bluetooth as needed) this causes bluetooth to appear on to the app, but the phone sees the status as "shutting down" effectively hanging bluetooth until a reboot. The next time I try to use bluetooth with the app, of course, it does not work.
If I shut off insecure mode, (and reboot, clear caches, etc.) and use the app, it works just fine. However when I exit the app, it cannot shut off bluetooth. So it leaves bluetooth on. Although I don't like bluetooth to be left on, this leaves bluetooth in a state to be used by Sportstracker next time. So it works. Looks like the app dev needs to do some work.
Insecure mode=Can turn on bluetooth, hangs bluetooth when trying to shut it down.
"Secure" mode=Can turn on bluetooth, cannot turn off bluetooth.
Oh well, I hope this helps someone. I might switch to another cardio program and test. I have pretty much bought them all, so I have a lot to choose from.
FYI, my workaround for managing bluetooth automatically is to set up a tasker profile to turn on bluetooth when the app is active, and to turn it off when the app is no longer active. Works very well.
I've been scouring the internet for solutions and honestly I find I rarely ever have to ask questions but looks like this time I need to put one up here.
I'm suspecting that my phone's wi-fi chip is pretty much bricked.
I get a situation some people have had here before where when I turn on the wi-fi, it kind of stays there and then turns back off, so never turning on. For some people this happened to here I understand it was the wi-fi only and the bluetooth still worked - but in my situation however the bluetooth is acting the same way. I'm aware that the Wi-Fi and BT chip are the same on the XT925 so it would seem like a hardware issue.
The "MAC address" setting in Wi-Fi > Advanced shows "unavailable". But get this: when I go to About > Phone status, "Wi-FI Mac Address" is also showing as "Unavailable". Indicating the chip may have fried or something.
I have literally no idea how this happened. I was kind of sitting down outside a Starbucks in Namba, Osaka when my wi-fi was suddenly no longer able to connect to anything. Been 14 days since. Wi-fi is pretty much essential for me to be able to use this phone at all since I'm out-of-country and I don't have an active 3G/data plan (not that a Canadian modem RAZR would work on Japanese airwaves anyway).
I'm on a Canadian XT925 and was running GZR Validus 6.0 (4.4 KitKat), but the problem persists no matter ROM what I put on - even CM12 Lollipop - and through factory resets, etc. Even when my system is pretty much black and freshly installed, wi-fi and bluetooth won't turn on. Any thoughts, possible solutions? I've tried numerous solutions from deleting/replacing numerous files and even preparing "Wi-fi rescue zips" with files from other ROMs to no avail. On another forum, a whole bunch of RAZR HD users were having this precise issue on the stock ROM and solved it by deleting this flashlight app (weird, right?). Ofc I don't have any such flashlight app on my device.
If anyone knows where exactly the wi-fi chip is on the motherboard (or is it a separate component connecting to the mobo, that maybe got dislodged) I can open up the phone and have a look.
Rooted Nexus 5 running stock 4.4.4
Until now I've had Bluetooth turned off to save battery but I now want to use it in my car. However it is grayed out in the phone settings and will not turn on. If I select to turn it on in settings, it switches to a grayed out "on" (see screenshot) and 2 seconds later goes back to off. I've checked my apps such as xprivacy, etc. and cannot find a reason for this. Any suggestions how to troubleshoot?
Hi
To be sure that you didn't remove system components or you don't have corrupted data, flash the KK factory images.
Also check other threads about wifi that cant' be enabled. The problem could be the same.
Thank you. I'll keep checking. Don't want to reflash. I probably turned something off somewhere. Will see if I froze something in Titanium backup. I know it's something I did because I had no need of Bluetooth - until now.
SOLVED
I finally found that the Bluetooth service was disabled in Servicely. Now all is well. It was a puzzle to track down.
This problem has been going on for over a month, happened while I was on mashmallow, I have upgraded to nougat to hopefully fix the issue, it still happens. When I go into WiFi settings and flip the switch is says "turning on" and will do so endlessly. It will never show me any networks or even say no networks available, just "turning on".
Things I've tried:
Booting into safe mode
uninstalling all apps (works temporarily even if i turn autoupdates off)
clearing cache
resetting network settings
factory reset (through bootloader, temporarily works)
flash to stock
I have seen other people with the same problem but no solutions. Can anyone provide some insight? Being that it works after doing resets and stuff i imagine its not hardware related. If it was, am I able to replace the wifi module in this phone?
I have just flashed back to Samsung_G930x_QC_Rooted_BOOT.TAR engineer image via odin, and it is working again. But I am skeptical that it will continue working, I will update here.
I have preemptively turned off auto system update in settings and auto app update in the play store, are there others that im missing? Could really use some help and/or advice here.
edit: It is also stuck saying "software update available", which ive tried in the past and it always fails, can i get rid of that somehow? I'm willing to root if necessary
just flashed QC1 using this thread < https://forum.xda-developers .com/verizon-galaxy-s7/development/rom-t3576124 >. Will report back.