Related
I'm curious if others are seeing their EVO reboot with random use. It doesn't seem to be related to one specific application although it is hard to say if a background app is the cause. I will be using navigation or an Internet-based app, then the screen goes black and the phone reboots.
I originally thought it was due to rooting, but I'm seeing it on different ROMs. I've wiped the cache and data when flashing the new ROMs and I've tried running with limited apps loaded with my recent move to the OMJ ROM. Everything actually runs great with the exception of the reboots.
I'm posting the issue here since it doesn't seem to be ROM specific and I'm curious if it may be hardware related. Is there a tool that would allow me to easily catch a log of the potential error to seek further help? A point in the right direction would be greatly appreciated.
I'm running stock 2.2 no root, and with gps on my phone reboots in the middle of 911 calls. (Thank God I wasn't calling about an immediate emergency) but it happened twice, once when I called and the other when they called me back. After turning off GPS, it worked fine. I thought this was a bug in 2.1 before update1, I didn't receive the problem until the 2.2 update.
adb logcat might see an error, but I'm not really sure.
Seeing it here. Not Rom or application specific.
try a factory reset.
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
AzmatEQ said:
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
Click to expand...
Click to collapse
Correction... I meant to say that the reason I rooted (not rebooted) was to get tethering without running into the Error Code 67. I tried the various solutions posted for the Error Code 67, but nothing seemed to work. But I'm curious if this may be part of the underlying issue if my device reboots based on a faulty account configuration when using some aspect of the Sprint network.
sprink0281 said:
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
Click to expand...
Click to collapse
The exact same thing happened to me last night. I sent a text, switched to my GMail and then boom. Error message about failure to send an SMS then reboot. Stock unrooted FroYo.
I had reboots only when using Undervolted kernels.
Seemed to be triggered by GPS + Phone call.
Yes, I was also having this problem. Definitely GPS related. Usually it would happen only if I was using the GPS for a long amount of time (navigating) - so I imagine it may be conflicting with cellular data if I received a txt while navigating or something. Who knows.
It was driving me crazy because A. I got lost and B. It started rebooting constantly and would randomly get caught in a boot-loop. I even had the problem after wiping EVERYTHING (even my SD) and reinstalling various ROMs (I tried 5 different ones).
The only solution I found in the end was to find the latest radio and wimax updates, wipe, re-install those - and then install the ROM again.
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
AzmatEQ said:
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
Click to expand...
Click to collapse
Don't go back to stock. I did and it did not fix the rebooting problem. Now I have the rebooting problem and don't have root anymore. Out of the frying can and into the fire.
What's funny is that my phone went through a few days where it would randomly reboot, and this was before I rooted. When it rebooted for the second time in a meeting, I pulled the battery, and didn't put it back in until the meeting was over a few hours later. Don't know if that did anything, but it hasn't rebooted on its own since.
Sent from my blah blah blah blah
Having same issue and my theory is that its sd card related in my case at least... I think it might have to do with froyo netarchy based kernals found in most of the newer froyo roms combined with a slow sd card. (on hardware rev 2)... try flashing a 2.1 rom like fresh 1 or one of the 2.2 roms with an htc based kernal like the am evolution or cyanogen with snap5 or 7.11 (onyl 7based kernal ive tried so far, was panicking because i thought my evo was wrecked). those have both worked for me and i had that issue with 1.3 baked snack, fresh 3, evio and damage control. got random reboots when phone is totally idle, in use, charging or not. evio runs super smooth but the restarts...)
edit for spelling and update roms that gave me the reboot issue.
+1 for random reboots here... it is CERTAINLY more prevalent during GPS use, but I've gotten it without.
Fresh 3 + King BFS#4 got me in a bootloop requiring wipe reflash, standard baked snack 1.5+whatever kernel it comes with has been doing it.
I dig the battery life I was getting... but if undervolting is causing this... ugh.
I'm also getting the boot loop problem. Stock 2.2, all updates.
I've even done the hard reset.. twice!
I tried to follow it with LogCat, but reboot disconnects adb. I was thinking it was the SprintZone app. The P.O.S. app is doing all sorts of non-sense while booting, but eventually it'll reboot around the 11th time and freeze at the "htc EVO 4G" screen.
I wish we could get some resolve here D;
Random Reboots
Thanks for all the input and I'm sorry to hear that I'm not alone, but it is a bit comforting to know I'm not the only one that is frustrated.
I took gleax's advice and I dropped down to the stock 2.1 release found in the thread number 715915. (Sorry, the forum won't let me paste the link.)
I did the required wipes prior to installing the new ROM and I'm still seeing reboots. I now see the OTA update for Android 2.2 and I'm tempted to accept, then send the phone back to Sprint in the even this is a hardware issue. I'd prefer not to, but there doesn't seem to be a way to identify the issue and work towards a resolution. I've tried logcat, but the log seems to start clean after each reboot. That being the case, I don't know how to capture the log leading up to the reboot that would help identify the issue. Any suggestions on a logging tool and where to post to help several of us that are seeing this issue?
Gleax suggested this is may be SD related, so I bought a class 4 card in addition to dropping down to 2.1. I'll give that a shot and try another clean 2.1 install. I'll post the results here in the event they may help others. I'll likely give it a week before unrooting and seeking help from Sprint. I really need a usable device more than I need root access (although both would be ideal).
I had this problem on a very regular basis when I was running OTA 1.32, 2.1 android.. but since I rooted and went to SteelH's stock 2.2, no issues at all. Updated radios when I did that as well.
Hrm, I may have to try flashing to a stock build for awhile... it'll KILL me, but even fully wiping, new radios, cyanogen, still get crazy reboots.
So for the past 2 weeks I am having issues that basically render my phone unusable for 99% of the reasons I bought it. Posted a thread before but I think it got lost when the forums were having some instability around that time...
My 3g connection will NOT stay up. I did nothing to provoke this. No system changes. The sequence of events:
-Went out of the country with my phone on airplane mode the whole time
-Got back, a day or two later had an incorrect timestamp on my incoming SMS (they were showing up +3 hours)
-Called customer service, she activated a tester phone and confirmed that it was a system-side issue on the incoming SMS (somehow they were getting a timestamp from the system where my number is located, in Eastern time, while I am actually located in Pacific nowadays).
-Put in a trouble ticket after 2 hours trying to solve the SMS issue over the phone.
-Next day, my 3g connection begins dropping CONSTANTLY. As it stands, it won't stay connected more than 30 seconds. It will cycle to 1x sometimes, and then drop to a basic-service-only.
-Tried reinstalling my ROM several times to no effect.
-Started experiencing some very strange noises in SOME calls, such as it sounding like a chainsaw when the other person is talking. Happens very sporadically.
-Just today I found some instructions here for correcting my NAM settings, which were actually messed up as it turns out, but didn't fix anything.
At this point I actually have the phone unrooted and back to factory default everything, with no change. I've got a warranty replacement phone coming in shortly, but I'd still rather keep this one if I'm able to.
Is there anything I haven't tried that might be the case on my end? Has anyone seen this problem before? Has my phone antenna simply gone belly-up, or is this something that might still be fixed at some deep system-setting level, or with further calls to tech support?
So... I guess that's a no?
Gornul said:
So... I guess that's a no?
Click to expand...
Click to collapse
Had the same problem with my phone before I rooted my phone and starting to apply ROM's. I havent had a problem since. But when I had that problem, I would just keep turning on and off the 3g and it would stay for a while. It was just a quick fix but it worked. Off subject how did you unroot your phone and put it back top stock?
My phone just started doing this this yesterday. Whenever I reboot it, it'll come up, switch to 1x mode. After a while it'll try to switch to 3g mode, fail, switch to no service, and then either go to just basic voice with no data or back into 1x mode. I've tried updating the radio, switching roms, dialing *228, nothing seems to help.
Jager, instructions on a full reset are right here under section 6. I'm not sure why it's struck out. Definitely suggest poking around more first.
New phone's in and still having major connectivity issues. The SMS timestamp remains as it was, and I can't get (steadily) more than like 35kbps. I'll occasionally bump to 500kbps for a quick spurt, and then my connection will drop entirely and struggle to get back up to 35kbps. My wife's Incredible works perfectly fine in the exact same locations, too, so this is something that absolutely has to be on Verizon's side, specific to my line.
Me too
My phone has also been experiencing the loss of 3G service as well. I checked my wife's Moto Droid 1 and it was also having difficulty connecting as well. I called Verizon and they were absolutely no help whatsoever. I am either getting nothing or 1X in places where I have always had 3G. This is very frustrating. I have flashed 3 different ROMs (all of which have worked fine in the past), but the result always seems to be the same. Anyone else out there with this issue?
khukman said:
My phone has also been experiencing the loss of 3G service as well. I checked my wife's Moto Droid 1 and it was also having difficulty connecting as well. I called Verizon and they were absolutely no help whatsoever. I am either getting nothing or 1X in places where I have always had 3G. This is very frustrating. I have flashed 3 different ROMs (all of which have worked fine in the past), but the result always seems to be the same. Anyone else out there with this issue?
Click to expand...
Click to collapse
Someone help! Same issue! I can no longer get data....PERIOD. I have to stay connected to wifi, or I don't get my emails, internet, etc.
Need to fix this!
3G connection issues
I just got off the phone with Verizon Tech support. They are CONVINCED that it is an issue with my phone (and my wife's). Gee, how can 2 different phones, from different manufacturers have the SAME issue at the SAME time? Hmm, doesn't sound very promising to me.
They are sending out a replacement for my wife's Moto Droid to see if it is a phone issue (she has been having other issues with it anyway...). If hers improves, I may send mine back, but I don't want to have to unroot, etc. Plus I like the Super-Amoled screen . When did trouble-shooting turn to "replace the hardware first" ???
Regards!
This happened to me recently as well and was fixed with a factory reset.
I am rooted with S-off, so a normal factory reset via Menu->Settings->SD & Phone Storage-> Factory Data Reset didn't go well for me. Not sure of the exact reason, but I just followed the instructions in this post to restore: http://forum.xda-developers.com/showthread.php?t=786436
Programming your phone by dialing *228 is necessary afterwards as well, as khukman states below. Thanks for pointing that out.
After I completed this, I redid root, restored my nandroid backup and didn't lose a thing, plus my 3G is working again!
*A fair warning: Doing this formats the internal storage (emmc). I'd recommend backing up any photos, music, etc that you have stored on emmc before doing this!
Sent from my Droid Incredible
So I tried the above suggestion about going back to completely stock 2.2 and I have the same results. On one hand, I am now back to S-ON and stock Froyo, so if I want to send it back to Verizon, they are none the wiser that I was rooted, but on the other hand I STILL HAVE CRAPPY 3G SERVICE!!! Man, I feel like I'm on AT&T or something LOL! I'll keep an eye on it for the rest of the day and see how it does and report back.
Back in 3G!!!!!
After getting back to stock Froyo, as described in the previous post, I was still unable to get a good 3G lock. I read in another thread where someone did a 'Factory Data Reset' and it took care of it. When you do this, you have to dial #228 and let it program your phone as it did the first time when you got it. Once I did this, I had (and still have) a solid lock on 3G like I used to. I think that it was one of the Sprint ROMs that screwed this up in the first place (the OP states that you have to backup your PRLs, etc. before installing, then re-install them afterwards). I can't remember if I did this or not, so it may be my fault after all, but regardless, I am thrilled that once again I have a connected smartphone thanks to the resources contained on XDA!
Regards!
I myself am now rocking a refurb that has no trouble at all... A complete revert to stock did absolutely nothing to resolve my trouble.
Though I didn't try doing a factory reset AFTER reinstalling the stock ROM. Hmm. Maybe there was something in the cache still. I suppose in my case I'll never really know, but I'm glad you guys were able to resolve the situation with your original hardware.
Gornul said:
I myself am now rocking a refurb that has no trouble at all... A complete revert to stock did absolutely nothing to resolve my trouble.
Though I didn't try doing a factory reset AFTER reinstalling the stock ROM. Hmm. Maybe there was something in the cache still. I suppose in my case I'll never really know, but I'm glad you guys were able to resolve the situation with your original hardware.
Click to expand...
Click to collapse
Did you follow the steps in the thread I posted above? Doing that should completely format and re-image your phone. Much more than just installing a stock ROM. I myself tried so many different variations of ROMs, radios, etc and nothing did the trick until I followed that thread.
Sent from my Droid Incredible
I've been seeing this problem for a few weeks now, with several different ROMs, including the original rooted stock ROM now. In nearly all of my recent calls, I get disconnected one or more times with the message "Call disconnected" and a "Dismiss" button. I'm thinking that this is because of my EVO and not the other side, since usually if they accidentally hang up or something the call just ends without a message box. As far as I can tell, I have good reception (at least according to the bars), and this is happening at home, where I've not had the problem before.
Does anyone know what could be causing this? My wife's EVO is not rooted, and she does not seem to be having this problem. But then again, I've not had the problem until fairly recently either. I've tried updating my profile and PRL with each new ROM, but it doesn't seem to have made a difference. Anyone have any suggestions as to how to stop this from happening?
Go into the settings menu andbupdate both your PRL and your profile. That *should* help with reception related issues.
posting & replying via the XDA Premium app.
Unfortunately, I've tried both of those things. I just did some testing today, and it seems that my phone is unable to stay connected during a phone call for more than five minutes before disconnecting, even if I don't touch the phone and just leave it sitting on a table.
Any other ideas? As far as I know, I haven't ever flashed my radio away from its default (2.15.00.11.19), and I'm currently using the leaked stock gingerbread ROM (build number 4.12.651.1 CL41771 release-keys and kernel 2.6.35.10-gaa602b7 [email protected] #1).
Maybe it's time to unroot and contact Sprint?
You can try downgrading from 2.15.00.11.19 to 2.15.00.09.01. You can download it from http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Afterwards, go into recovery, wipe cache & dalvik cache then flash the zip. You will be taken to the radio update screen and appear to hang. don't worry or get impatient. After it is finished, you will reboot into recovery and see the words "clearing cache" at the top of the screen. Simply select reboot and then you will boot to your homescreen. The initial boot will take a tad longer since it will be rebuilding the dalvik.
Hmm... I'm hesitant to downgrade my radio because my wife has an EVO with the same radio version number and hers doesn't have this problem. Granted, she is not rooted...
I understand. I've downgraded and upgraded everything several times for testing purposes and troubleshooting purposes and have never had a problem. The only hing about flashing radios is patience and not to pull the battery. Anyway, you can always call Sprint and see if they can troubleshoot it for you from their end.
posting & replying via the XDA Premium app.
I would contact sprint @ 877-809-6696 (advanced tech supp). Ask them to push a full reprovision to your device. See if that helps any. I was having issues when when on the airave, I was unable to receive incoming calls. This corrected it. I did try all the other steps listed above without any success.
This is interesting. I unrooted to test things out before calling Sprint, and the problem went away. I was able to stay connected for an hour (where before I couldn't last longer than 10-15 minutes). Yay, fixed, right? So, I rooted again and didn't install any ROMs or anything, just rooted, and the problem came back.
So, I have a solution, but I don't like it very much because it means I need to stay unrooted. Anyone have any idea why simply rooting the phone with Unrevoked 3 (and doing nothing else) could cause calls to disconnect? I'd love to be able to root again, but I can't deal with a phone that randomly disconnects all the time.
I am interested in this as well as I am rooted using unrevoked and get disconnected as well. I do find that it mainly happens though talking to people who have service on AT&T.. Quite wierd. All I hear is a beep then disconnected. This happens when I first place a call and it rings once or twice then beep, disconnected...
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
KingFunderberk said:
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
Click to expand...
Click to collapse
So whats the final call on this ..?
Is it Rooting , Is it network .. i am too getting psyche with this .
I'm pretty sure it is not rooting. But I don't yet know for certain what it is. Sprint thought there might be something wrong with the antenna on my phone, but they had already replaced the phone, so I think that is unlikely. They gave me a femtocell range extender to use in my house. Basically, I plug it into my broadband connection, and it is like having a mini cell tower in my house, giving me a very strong connection. Sure enough, when connected to that, I haven't had any calls drop. However, my phone still sometimes doesn't connect to the femtocell and instead connects to some other tower for some reason. My wife's phone doesn't do this, so I still think there is something wrong with my phone. I may contact Sprint again about this. ...sigh...
What is your area some area evo don't work properly like on rahim yar khan in this time connection don't work properly some signal drop and some time up i sure after few day signal work properly then problems will be solve.
My phone EVO is doing this now as well. Has anyone heard/read a solution?
greg_99 said:
My phone EVO is doing this now as well. Has anyone heard/read a solution?
Click to expand...
Click to collapse
I am having the same issue, out of the blue. No problems up until a few days ago. I'm wondering if it is maybe an issue with a certain version of the Evo. I have a version 002. Thoughts?
Greg_99 any progress on what might be causing this issue?
Hello,
I've searched around the Epic 4G Touch forums as best I could, but sadly I couldn't find anything that was exactly this problem (although I found some interesting articles about wifi sleep time but they don't seem to apply). I'm experiencing an annoying issue where I can connect Wifi just fine, but if the phone is left for a small period of time (~10 minutes), wifi appears as if it's still connected, however it cannot send/receive data. When this happens, the wifi status says it's "connected", but there is no data connection. The only way to to get the data back is to turn off wifi, wait for 3/4G connection to initialize, then turn Wifi back on to refresh it...then it's fine again until I set the phone down again.
I had this problem on stock EL29, so I rooted and flashed Phantom Blazer ROM (very cool ROM, but I'm still experiencing the same issue). After reading the threads on here about wifi sleep times (apparently they're backwards with ICS roms), I've experimented with every setting, yet I still have the same issue--Wifi is fine as long as I'm using the phone, I set it down, after about 10 minutes pick it back up, says it's still connected, but no data connection.
has anybody experienced this problem with this phone? I'm about to unroot my phone/go back to factory so I can take it in to a Sprint store, the problem is they (trying not to be offensive) don't seem to know very much about this device. I thought I'd ask the pros before I return it, get an iPhone, and have to eat my words about how cool Android is vs. iPhone in front of all my friends. I'm hoping there's a reliable ROM or app that can resolve this vs. having to just replace the device!
Thanks for your help!
I'm not the only one
I'm not the only one with this problem:
edit: I can't post links to androidforums.com or anywhere else, but this same problem is all over the interwebs and nobody has a solution.
I'm sure it's not my router as my ASUS tablet/laptops/girlfriend's iPhone experiences no connectivity problems. I'm thinking this is a hardware problem with some of these devices. I will unroot/reset to factory tonight and let you know what happens.
What channel is your router on? And what type is it A/B/G/N?
This is s known TW ICS bug, most likely kernel related. Almost everyone is having this issue and there is no fix until Samsung decides to repair it. There are quite a few posts similar to this one. If you're using XDA's search function, it's not very good. Try using Google next time and search XDA that way.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Hey guys, thanks for the response. Just before I unrooted/reset to factory I tried one last solution--download an app called "Wifi Fixer". It has resolved a lot of these problems. It's not 100%, but after testing it for a day so far, I've only had to manually refresh the connection once or twice. It's a lot better, even liveable, and I won't be resetting to factory afterall, at least not until Samsung provides an update. So if anyone is having the same problem, try Wifi Fixer, hopefully it gives you a similar level of success...I'm not super happy about having to run another background process all the time, but it doesn't seem to affect battery, and the fix it provides is worth it to me.
Cheers!
Huh - a couple of things. Noticed this problem crept back in FF18 and didn't know why until I went back and checked the wpa_supplicant.conf that I'm using. The line ap_scan=2 was missing; after adding it back in the signal strength is back to full and stable.
I'll bump the thread but it appears the config changes here still hold after all:
http://forum.xda-developers.com/showthread.php?t=1569348
This should also avoid having the WiFi fixer there as you can specify the country in wpa_supplicant.conf manually.
Thanks for looking in to this! A couple questions from a noob like me though:
When you say the problem crept back in FF18 ... what does that mean? Is that something that exists in the "stock" version of the Epic 4G touch from Sprint?
The manual config file tweaks you're describing ... is that something I can perform myself?
Basically I'm wondering if it's "safe" to revert to stock in order to get consistent wifi signal, or if it's something I'm experiencing because of the ROM I'm using.
Thanks!
so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
I'm not trying to threadjack here, but I just wanted to share my experiences.
I've been have the exact same thing happen to my phone (Nexus maguro). I've tried every JB rom I could find, several different kernels and my wifi eventually always goes grey on me. All network activities stop. I'm back on stock everything right now and it still happens.
It happens on my home wifi as well as work wifi.
I'm about to puttstock ICS on my phone and try that out for a couple days.
Anyway, good luck with your problems, i'm going to follow this thread in hopes you'll get a solution that may help me.
If I do figure anything out i'll post back.
jrmacarthur said:
I'm not trying to threadjack here, but I just wanted to share my experiences.
I've been have the exact same thing happen to my phone (Nexus maguro). I've tried every JB rom I could find, several different kernels and my wifi eventually always goes grey on me. All network activities stop. I'm back on stock everything right now and it still happens.
It happens on my home wifi as well as work wifi.
I'm about to puttstock ICS on my phone and try that out for a couple days.
Anyway, good luck with your problems, i'm going to follow this thread in hopes you'll get a solution that may help me.
If I do figure anything out i'll post back.
Click to expand...
Click to collapse
seems that this is a topic that has been posted on a bit over time with no real single culprit or fix. I'll post back if I figure anything out... I know in the Cyanogen thread, I saw info that stated that the MAC address of the phone was changing and I'm going to try and determine if that is happening to mine.
I have the same issue. Sometimes even when i pick up the phone, if i look fast enough i see that the Wi-Fi bars weren't even there! Thats only 1 out of 5 times though. The other time its usually just grey bars. Sometimes it actually will click back and they'll flash to blue and grey 2-3 times and then go solid blue. Then sometimes like you, they'll stay grey. I've tried everything too...reverting to stock, Different kernels, ROMs, routers, static IP, 2.4 or 5ghz, full auto mode. The only fix that makes it a little more reliable, is using Wi-Fi PM Fast. But even that, is not reliable. I'd say its about 50% reliable then, for a huge sacrfice in battery life. For me i've noticed this started to happen with 4.2. Before that i never had a problem. All other devices though no problem. My Nexus 7 is just fine. But the galaxy nexus, no matter what router or where i am, the Wi-Fi is totally unreliable. For me, it happens within 2 minutes that it will disconnect most times. Then 1 in 10 times it'll be fine for 10 hours.
In all honesty, i've given up. Just come to deal with it. Use mobile networks when i'm not needing to download. I can download files and stream music just fine too. If there is traffic going through, it never disconnects. But when its just sitting there without traffic, it disconnects, or, loses connection to google servers i should say.
well that's not good to hear...
I installed stock 4.0.4 a couple days ago and have not had my wifi go grey on me yet.
Sent from my Galaxy Nexus using Tapatalk 2
jrmacarthur said:
I installed stock 4.0.4 a couple days ago and have not had my wifi go grey on me yet.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah, I love Cyanogen so not willing to go back to stock... waiting for them to finish 10.1 and I guess I'll see how it behaves then.
Hi all,
Just to say that I have the same problem. I have been upgraded from ICS to 4.2 and nothing had happened but I had to downgrade to 4.1.1 (AOKP Build 4) due to other issues and after that I started notice the WiFi problem.
At first I thought it was when the screen went off, but I has happened with screen on too. I have to turn WiFi off and the back on to connect properly again, very annoying.
As I said I started noticing this after I downgraded, but then again, I had used AOKP 4.1.1 before without this issue. I think that it is time to change my phone :/
tgeery said:
so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
Click to expand...
Click to collapse
I'm on Muzzy 4.2.2 and I'm currently having the same problem. It's not a new problem since I remember having it months ago (disabled my phone's WiFi because I kept missing emails and other notifications - grew tired of dealing with it). I thought it was my router, so I swapped it with a newer one recently, but it carried forward (old router was TRENDnet Draft N and the new one is ASUS RT-N66U).
I would like to know how to properly troubleshoot this problem.
I'm glad I didnt have to create a thread for this. I have been facing this problem quite a lot. I can confirm that WiFi works absolutely fine until 4.1.2, whether it is stock or CM10 (I havent tried the other ROMs yet). I have faced this problem only from 4.2. It still exists on 4.2.2. Happens on all the ROMs I have tried till now including CM10.1 nightly as well as the stock factory image.
When the phone is sleeping, it seems to lose WiFi connectivity and when woken up, the WiFi bars is grey though it is full. If I am very lucky, it will turn blue automatically. Most of the times, I have to switch WiFi off and back on for it to connect properly.
Anyone knows the root cause for this? In case this has been discussed in any other thread?
subhramani said:
I'm glad I didnt have to create a thread for this. I have been facing this problem quite a lot. I can confirm that WiFi works absolutely fine until 4.1.2, whether it is stock or CM10 (I havent tried the other ROMs yet). I have faced this problem only from 4.2. It still exists on 4.2.2. Happens on all the ROMs I have tried till now including CM10.1 nightly as well as the stock factory image.
When the phone is sleeping, it seems to lose WiFi connectivity and when woken up, the WiFi bars is grey though it is full. If I am very lucky, it will turn blue automatically. Most of the times, I have to switch WiFi off and back on for it to connect properly.
Anyone knows the root cause for this? In case this has been discussed in any other thread?
Click to expand...
Click to collapse
have you posted this information over in any of the threads where the developers are working such as Cyanogen in an effort to bring this issue to the forefront for more visibility?
I have had those wifi problems with every android version and rom I had on my GNex as far as I can remember.
Sometimes it will be able to reconnect but sometimes I have to disable and re-enable wifi to get it back.
I too thought that it might have been my crappy router as I have had multiple problems with it over the years (some Linksys router).
This is really annoying because it won't receive any e-mails until I randomly decide to have a look at my phone. :/
Fabur87 said:
I have had those wifi problems with every android version and rom I had on my GNex as far as I can remember.
Sometimes it will be able to reconnect but sometimes I have to disable and re-enable wifi to get it back.
I too thought that it might have been my crappy router as I have had multiple problems with it over the years (some Linksys router).
This is really annoying because it won't receive any e-mails until I randomly decide to have a look at my phone. :/
Click to expand...
Click to collapse
trust me, I understand your frustration... some days, I can go almost all day without loosing wifi data throughput and other days it won't last 10 minutes without going to gray bars.
unfortunately, no one is sharing any fixes which tells me that no one has a good handle on the problem.
Same issue for me on stock Android 4.2.2. Leave WiFi on overnight and when I wake up its connected to WiFi but gray bars...
Sent from my Galaxy Nexus using xda premium
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
tgeery said:
so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
Click to expand...
Click to collapse
same thing happened to me on toroplus sourcery 5.1, after trying everything i could think of and talking to one of the devs, i finally did a fresh download of rom and gapps. wiped cache,wiped dalvik, factory reset, wipe system, deleted android folder off of storage then installed the fresh download of rom and gapps and its been working great for me since. hope this helps.
M3drvr said:
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
Click to expand...
Click to collapse
Can you elaborate on this? I've flashed 5 different modems and still get this problem... it happens to my cell service bars, as well. Would love to know what the cause is.
aqcon said:
Can you elaborate on this? I've flashed 5 different modems and still get this problem... it happens to my cell service bars, as well. Would love to know what the cause is.
Click to expand...
Click to collapse
i just know ever since moving to a 4.2.2 kernel that has the 4.2.2 drivers my wifi has been stable. I know there was a post in the anarkia thread with the ak kernel that had the drivers. but i believe most any 4.2.2 kernel would have them implemented. i do have the newest bootloader and radio too. but i know as soon add i got the 4.2.2 drivers all issues were resolved wifi wise. of course i think if you have a 4.2.2 kennel you'll have them.
M3drvr said:
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
Click to expand...
Click to collapse
I'm looking forward to that update - I've been watching the Cyanogen threads for when I think the 10.1 has matured enough to become my daily driver... good to know you've had positive results!
Temporary solution
me facing same issues , Solution would be to use an app called wifi fixer by zanish-g1 from the play store ...
it worked for me !! :good: