So i've been trying to figure out why my wifi won't turn on for the past few days. It started randomly turning itself on and off round a month ago and now just doesn't turn on. When i attempt to turn it on, it gets "stuck". If that wasn't enough, the same thing happened with the bluetooth. Now i can't seem to use either. Could anyone tell me what's going wrong and/or how to fix it?? Thx, Im using a D2203
Related
Ever since upgrading to AT&T 2.2, I have a had an issue that on every other reboot, the phone radio does not turn on. I am not getting a SIM error, or any other error indication, nor does the phone go to airplane mode (bluetooth and wifi work). If I check phone settings, I get phone # unknown and no phone signal. Once I shut the phone down and turn it back on again, phone service is back.
I'd suspect a SIM issue, but this did not happen on 2.1. Could this be a bad flash (I could not get Kies Mini to push the firmware, I had to install via Odin)? Has anyone else seen this kind of flakiness?
Bump
Is anyone else seeing intermittent issues of the phone thinking it doesn't have a SIM installed? The good news is that I have not had two reboots in a row with this problem, the bad news is that I do see this on nearly 50% of boots.
I dont have the problem, if it does happens it only happens like once a week for me, it usually fixes it by going into airplane and back to regular
ryanmahan said:
I dont have the problem, if it does happens it only happens like once a week for me, it usually fixes it by going into airplane and back to regular
Click to expand...
Click to collapse
I tried that. On my phone, that does not remedy the situation. The SIM itself has not moved since the update (I can't remember if I pulled it when I ran the upgrade), so I don't think it's a loose contact.
att can fix
Bring the SIM and phone into ATT, they will fix it for you there, hopefully for free, that could work, just unroot before and unflash if you did, then say you have SIM problems and then tell them that you had it in during the update, sometimes that causes problems
I have this same issue. Yesterday after about 5 reboots the phone would not pick up any signal... at times and after several minutes, some signal would show up and then disappear again... After about the fifth time, I turned off WiFi, because it had been on the whole time and that fixed the problem. Signal came back after a while and was stable. Turning WiFi back on did not bring back the problem. I guess Froyo just does not like the WiFi being on when booting the phone. Hopefully this can help others fix this same issue when encountered.
Sent from my SAMSUNG-SGH-I897 using XDA App
I hope I'm posting this in the right section, sorry if I didn't.
I have an AT&T HTC Inspire 4g. It has been rooted and then unrooted but I don't think that is the problem. I have an otterbox defender series. I dropped my phone some months back and I've been having this problem every since.
My wifi and bluetooth do not work anymore. They did before I dropped the phone.
When I go to turn on wifi, it say's "turning on..." and about 15 seconds later it say's "Error". (Note that I am not scanning for wifi simply just turning it on.)
On the bluetooth problem. I go to turn it on and it simply says "turning on..." then about 15 seconds later it says "Turn on Bluetooth" again.
I'm thinking that it is a hardware problem but I didn't want to take the phone apart without checking with someone other than AT&T or HTC, because they want me to send it in to them, to see if anyone else has had any of these problems before and figured out a way to fix it software wise.
Thanks in advance for anyone that may be able to help.
Did you try repeating the battery door and sim cover?
Sent using the power of the dark side
Can anyone tell me anything about bluesleep? From the research I've done, it's apparently something that started showing up with ICS. I haven't found many reporting it with Kit Kat though. The closest I came was a few experiencing it with Pebble.
I did a factory reset on my N5 and tried to connect to my car's bluetooth. It wouldn't auto connect so I found a fix where I could rename my N5 and that fixed it. Now I've noticed bluesleep and a couple of other bluetooth related wakelocks showing up after I connect and use it. They seem to stop after I stop using it. Is this normal? Has anyone else noticed bluesleep?
Sounds normal.... You're basically saying when it's in use it causes battery drain. And when i turn it off all is normal. Aren't you?
Sent from my Nexus 5 using Tapatalk
Yeah. I just wanted to make sure that was normal. If you had an android watch connected wouldn't that always keep it awake and destroy your battery?
wakelocks are how the phone works. wakelocks arent bad, its the wakelocks that get "stuck" that are bad. if your phone didnt produce wakelocks, you wouldnt be able to do most anything with your phone.
Updated to KitKat. Unlocked bootloader, rooted.
Noticed for the last couple days whenever I turn my wifi off (because of poor signal, fact I'm at work, whatever), it turns itself back on within minutes. Tried to find any kind of setting that might be doing this, but no luck. A search reveals similar issues with some sprint phones, but nothing with the Razr Hd. Is there any way to stop the wifi from turning itself back on? If I wanted it on, I'd manually do it.
Never mind. I figured out it was an app I was using causing that. Weird that I first noticed it after I updated to KK.
So I just took the update last night and everything seemed great until this morning. I got up checked emails, headed to work and listened to my phone over bluetooth in my car like usual. Then almost as soon as my phone disconnected from my car it restarted. Thought that was weird but no concern. Then realized that after about 1-3 mins after every restart it would restart again (so not technically bootloop but still just as annoying.
Is anyone else having an issue similar to this?
EDIT: I've narrowed it down to be something wrong with having WIFI on!
I thought since it started doing this after using the bluetooth in my car I would try turning that off. Nope still restarts. Next restart I turned WIFI off and it didn't restart again after letting the phone sit for a little bit. Turn wifi back on and immediately the phone restarted again.
Backing up my files now and will probably attempt a factory reset to see if that fixes it. (unless there's some other solution anyone can think of)?