When turning on Bluetooth the toggle slides over for 10 seconds or so (still greyed out) before sliding back to off (the Bluetooth never actually comes on). It started yesterday out of the blue. At the time it started, I was running 6.0.0 (MRA58K) and had been for several weeks without an issue. Reboots don't fix it. Safe mode doesn't fix it. Wipe Bluetooth cache/data doesn't fix it. As part of my attempts to get it working, I upgraded to MRA58N. Then a round of trying all the above stuff all over again. Still no go.
I attached a log of an attempt to enable Bluetooth (trimmed). I waited until 0149 before I hit the toggle to turn it on and the log is from that point on. The point I see the obvious failure is 01:49:18.131 with the error message "Error enabling Bluetooth (enable timeout)" but I can't make enough out from the rest of the log to figure out why it's timing out.
Experiencing same issue on my Nexus 6. Worked fine for several days after upgrading to MRA58K. Then it quit. Same BT toggle symptom you described. Just did the OTA to MRA58N this morning. Tried reboot/safe mode/wiping BT cache and data. Still no workie.
I know none of this is really very helpful to you, but just wanted you to know you aren't the only one with this problem.
I ended up having to do a full wipe and re-install to fix it.
I'm having the same problem for weeks.
I tried for days to straighten it out. Uninstalled apps one by one and rebooted until I'd uninstalled everything, dug through logs, and did everything I could think of and nothing works. The silver lining was that wiping it and re-installing fixed it so it wasn't a problem with the hardware. I don't know if it was a bug or a glitch but I couldn't resolve it without a reinstall. Been over two weeks and I haven't had a problem since.
I had a similar problem, except Bluetooth wouldn't connect nor would it connect to anything. Toggle would act as though it turned off or connected, but 20-30 sec later, it'd go back to on and disconnected. A simple reboot fixed it for me, and this was on Lollipop a few months ago.
Sent from my Nexus 6
Related
When I was using Helmi's 1.3.2 rom (I have since switched back to the latest WM2003 rom) I had some odd, seemingly hardware related, Issues:
*Back light randomly turned on and off, programs opened and closed and did random things, then the device would reboot.
*It would just randomly reboot.
*I would get a "Problem with bluetooth hardware" Error message when trying to scan for new devices some times, and I would have to soft reset.
*I could not turn off the screen in WMP while using A2DP
*The device would shut off completely and wouldn't turn back on occasionally, and the only way I could get to turn back on was to plug it in. After doing that, all the version numbers on the first boot screen would read "NONE" and I would have to soft reset the device several times to get the wireless working again.
I have taken very good care of my SX66 (I have only dropped it once), and these problems worry me...has anyone else experienced these?
I had also a lot of trouble after having installed a new version of WM5, because I forgot to wipe the memory clean (check step 9 - and especially 9.2 - in http://wiki.xda-developers.com/index.php?pagename=Helmi). Just repeating this step will solve it... it dit for me. that's another thing I won't forget anymore
I'm not gonna BS anyone. I'm clueless!!
I lent my phone to a friend for a few days and he installed one of the ICS roms on it. A few days later I realized that it would no longer keep wifi active. Anytime I'd attempt to turn wifi on it would say error and time out.
I figured no biggie I'll just Odin back. So I Odin'd back to Eclair and still no wifi. Even worse... when I boot the phone it takes exactly 33 minutes to get past the "Galaxy S" screen. It isn't frozen as I can see the S throbbing.
Another symptom of my problems is that the haptic feedback is gone.
In recap, No wifi, no haptic and a loooong boot.
As I said earlier, the problems persist in stock form as well as CM7.
Any help would be greatly appreciated.
OK, The weirdness continues. I decided to try roms I've used in the past to see if anything changed. I started off with Andromeda 1.0. The boot time is now back to normal and I've regained haptic feedback.
Unfortunately I still don't have wifi. It'll now allow me to enable wifi and it'll attempt a scan but comes back with "unable to scan networks". I attempted to manually add multiple networks and get the error "unable to save the network" then wifi gets disabled.
I'm at a loss at this point so I'm hopeful someone can come through.
Antiph3d said:
OK, The weirdness continues. I decided to try roms I've used in the past to see if anything changed. I started off with Andromeda 1.0. The boot time is now back to normal and I've regained haptic feedback.
Unfortunately I still don't have wifi. It'll now allow me to enable wifi and it'll attempt a scan but comes back with "unable to scan networks". I attempted to manually add multiple networks and get the error "unable to save the network" then wifi gets disabled.
I'm at a loss at this point so I'm hopeful someone can come through.
Click to expand...
Click to collapse
When you Odin'd back to Stock, did you Master Clear too?
Thanks for the reply.
Yes, I did do a master clear. Internal SD has been wiped but the problems continue.
The haptic feedback and boot time return to normal when I flashed Andromeda 1.0 but go bad again when I go back to stock.
Just went back to stock and am waiting the 30 minutes for the phone to boot so I can do another master clear. Can't see the second finding any residual files that the first didn't get but you never know I guess.
I just noticed that my Bluetooth isn't working either.
Data and cell work just fine though.
so... latest recap...
Currently running Andromeda3. The phone boots just fine in a nice fast timeframe. Haptic feedback is working fine.
Wifi and Bluetooth are no go's. Just don't get it
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium
Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium
Hey there.
I have a stock Samsung Galaxy S4 Active on the AT&T network. Recently, I've been plagued by a number of troubles.
Bit of background:
For a while, I had the most bizarre issue: the screen thought I was touching it when I wasn't, near the bottom-middle of the screen, and would attempt to open/click on anything in that area. Often turning the screen on and off would help, for a little while. I was reaching my wits' end, because that would obviously be very frustrating to someone who uses their phone frequently throughout the day.
I thought maybe it had been new software I had installed, so I did a factory reset. Problem remained. I factory reset with NO backups. Problem remained. I updated to 4.4.2 via OTA. Problem remained...
And then mysteriously went away on its own.
I've been working in tech for a decade now, mainly in PC and server architecture, so I know better than to look a gift horse in the mouth - but I also know better than to think a problem that "mysteriously" goes away is gone for good. So the first part of my question: does anyone know what could have possibly been causing this?
I'm not super phone-savvy. I've rooted and flashed a few phones in the past couple years, but I'm by no means developer-level.
---------------------
Which brings me to my next problem... around the time that this issue went away, another one cropped up. Randomly, my phone will stop sending/receiving texts/calls, and the data connection will not function. This will continue until I turn on airplane mode and turn it off--at that point I receive all my missed texts, and it works again... sometimes for 5 minutes, sometimes for nearly 2 days. It's really frustrating. I've tried factory resets, I've tried restoring default APNs... but I'm at my wit's end with this. Can anyone help?
Thanks!
I should add that, with my last issue, it still shows a data connection in the notification bar - but there is none, or at least, no activity on it. It doesn't simply act as if it's in airplane mode and go "wah no data network" as soon as I try using it--it just simply hangs for ~30 seconds, then times out. Messages don't get received, webpages don't load, calls don't get placed, etc.
After the update a few issues have risen. I've attempted to search for solutions for each one, with no avail.
These are issues that never happened before the update, and started right on the next day.
1. Audio apps close when locking the screen.
When I have a podcast running (on beyondpod) and I lock the screen from the off button, the app will either keep running, or close.
I have found a few questions like this on here and other forums, but none with a definative answer.
I've done a few of the suggestion, like cleared the cache. But is there an actual solution to this?
2. Bluetooth turns off/loses connection to my pebble 2. I think these might be connected.
While using a bluetooth headset, there are no issues. However I constantly (should) have my pebble connected to my phone. However, very quickly it loses the connection. It randomly finds the connection again randomly, but it wont stay connected for very long. Sometimes I catch my phone with the bluetooth turned off, however turning it back on wont neccessarily connect it to the pebble. I also tested out with IFTT, and everytime the phone cut the bluetooth connection it woul send me a notification. And it happened multipe times within the hour. Sometimes taking tens of minutes to reconnect, sometimes not reconnecting it at all.
3. Google Timeline (the thing that draws a map of where you've been and how you've traveled)
I used this to follow my cycling and walking, since step counters dont recongnize cycling very well or at all. However since the update the pages are all empty. It just wont recognize my movement at all. I later noticed that the location gathering accesses had been reset, but even after giving them access again there is absolutely nothing saved onto my timelines.
Please, if you have any ideas what is doing this, or any ideas how to fix one, or each of these, leave a reply...
If nothing else I'll have to rollback to Marshmallow... And I've really grown to like the split screen!
hi, having same problem as #3 on my brand new Huawei Mate 10 pro. did you ever solve the issue? thanks