I've been running CM12.1 for several months in my N910T without any problems. Most of this time I spent on Temasek's unofficial build v18.6, but recently I've been going with the latest official nightlies. Every time I flash (clean flash of course), everything works fine for a few hours or days. Then, spontaneously my wifi will stop working. It won't turn on at all. When I tap the wifi toggle, the switch flips to the on position then instantly flips back to off.
I thought maybe it was a bug with some Xposed module, so I disabled the Xposed framework and rebooted, but no luck. I don't have any automation apps running that could be acting up. Then I thought it must be a bug in the latest nightlies, so I clean flashed the Temasek build I had run for weeks, but lo and behold...the same bug started within a few hours.
Does anyone have any idea what this might be? Or any ideas about how I can find out?
Related
Using Nookie Froyo 0.6.8 eMMC.
I noticed my Wi-Fi takes a couple minutes or more to connect after the Nook had been sleeping. So I went into the Wi-Fi settings and I see "Wi-Fi Turning off...", then it comes on, then it turns off, and repeats over and over.
Eventually it will connect. Any idea what is causing this? This is a freshly install ROM. I've wiped it and reinstalled it and still have the same problem. And it works fine after a reboot, seems to only be a problem when it's gone to sleep.
I also installed Spare Parts and set the Wi-Fi sleep profile to never (this problem was happening before installing Spare Parts by the way) however that doesn't seem to prevent it from sleeping either.
I get the same thing. I'm assuming its a kernel thing, but I don't know, I'm definitely not a dev. Its happened in all the nightlies I've flashed, though.
yep this is a kernel issue i believe as it was better on the older kernels. i think it has something to do with your security settings.
try changing from wpa/wpa2 to something else perhaps?
i went to cm7 17 and so far it has been flawless. earlier builds were almost as bad though so i'm not sure if it will last.
That started happening on mine too. I just installed the newest kernel, that clean black theme, and nookie froyo. Prob the kernel.
It seems to help me on my nooki froyo 0.6.8 to put it back in standby by hitting volume up and power button at same time, then waking it back up and waiting for wifi to turn on usually within 30 seconds. It does not help and actually seems to make it worse to go into wifi settings to watch its progress.
Known issue with dalingrin's kernel. Go look on in the development forums.
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
AndroidDeer said:
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
Click to expand...
Click to collapse
I have had CM7.0.2 installed for a few days now and have not had any issues with it. Did you wipe /system and /data before installing? It sounds like it could be a hardware issue if this is the case.
migrax
Dunno about the apps not running, but the wifi borking like that is a common problem.
You just have to "forget" your known wifi hotspots. I've heard people saying that forgetting just one will work. The one time it happened to me i just took them all out.
See sig...
My wifi works fine after installing 7.0.2 and the OC kernel, but the indicator in the notification bar no longer works. It shows zero bars no matter what. It's the same on two different brands of routers. No big deal though, just an aesthetic thing I guess.
I didn't wipe /system or /data, for whatever that's worth.
edit: forgetting the network and reconnecting fixed it.
I'm having the same issues...
Sent from my NookColor using XDA Premium App
I also noticed the same on 7.0.2. Perhaps is it is just aesthetics but I was noticing other minor glitches (simi clock fails and battery gauge) so fell back to 7.0 and things are moving along swimmingly.
One thing to keep an eye out for is that CM7.0.0 and 7.0.2 apparently dont like AES encryption on wifi. I had a hell of a time getting my wifi to work on my new nook as of Wednesday (omg so much fun) but once I switched my router to TKIP it works great. Kind of annoying, but a simple fix.
2.6.32 is coming *soon* and it allows me to build a new wifi driver. This will hopefully fix the AES issue that some people have.
phiremod's 6.2 has solved this wifi issue.....not sure what build he is using
AndroidDeer said:
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
Click to expand...
Click to collapse
I was in the same pain, but backed down one version to the nightly 55 release and it's been beautiful. Clearly they're working on the new version, since there hasn't been a nightly in about a week. I'm fairly new to CM, and it wasn't hard. Download the ZIP, boot into recovery - flash the ZIP, wipe cache and came right up. Do your backups (nandroid and titanium) just in case, as always. ;-)
I had same problem. Then I did install official Nook Color Stock firmware. Wifi works perfectly... So CM 7.0.2 has software based problem...
By the way, I have never used OCed setting...
nemir said:
I had same problem. Then I did install official Nook Color Stock firmware. Wifi works perfectly... So CM 7.0.2 has software based problem...
By the way, I have never used OCed setting...
Click to expand...
Click to collapse
I've never used the overclocked settings beyond what CM will offer.. the 925mhz. Considering going to the 1.1ghz since others are reporting that's stable.
But seriously - go to the 55 version of the nightly build. In my experience, the WiFi is FAR more stable than the official 7.0.2 release.
http://mirror.cyanogenmod.com/?device=encore&type=nightly
Thanks, worked as a charm
ylixir said:
Dunno about the apps not running, but the wifi borking like that is a common problem.
You just have to "forget" your known wifi hotspots. I've heard people saying that forgetting just one will work. The one time it happened to me i just took them all out.
Click to expand...
Click to collapse
had tried hard reset, multiples on/off of wi-fi
but forgetting one network did the trick
I have a NC that has been rooted since August using CM 7.1.0 (not a nightly build). For the last 2 weeks or so it has shut off randomly, usually when it sits for longer than and hour unplugged (but even sometimes when it's plugged in, too). It's not dead because I can turn it back on and still have over 50% battery left. I've edited the file I needed to in order to prevent OTA updates since B&N released the 1.4 firmware. But could that OTA be the cause of my issues?
If you have CM7 on it there are no OTA updates even seeing you. Sounds like the sleep of death. Try turning off wifi when you leave it unattended.
I've actually noticed the same thing too. I'm running CM7.1 and noticed my NC would not wake up sometimes. It could be a few hours or a whole day, but I think it has not gone more than a few days without locking up. I figured it may be related to something I installed recently, but considering the number of things that have been installed and removed over the last few weeks, it's hard to pinpoint...
I have been running nightly encore 177 since September 1st without any problems until yesterday when my NC started going into sleep of death. I have had to do the N-button + power button hold to get it to restart.
The only changes I made before this started happening was to place about 10 app shortcuts onto the home screen.
I am going to update to nightly encore 253 and hopefully it will stop SOD.
You might as well update to the CM7.2 RC0 Mirage build. It incorporated some fixes that came out post-n253, and it looks like that will be it for updates until either ICS hits, or CM7.2 Final comes out.
I do still get the SoD, but not frequently.
I'll have to check out that build of CM. For that very same reason I'm tempted to go back to the stock software. Not sure if it's the right move, but this constant locking up is becoming very annoying.
Extreme kudos and awesomeness and gratitude to jcsullins and all the folks involved with developing CM10/Android for the TP. Thank you.
I had been watching the forums to figure out a good time to "jump in" and yesterday I took the moments to install CM10.1 (4/18/13) on my TP. I was amazed at how seamless and flawless the installation was. It seemed it took less time to do the install than it did to download CM10 (download was ~100kb (kB?)/s). CM10 came up running without any problems.
Of course, it wasn't without some issues After confirming CM10 was functional (along w/Wi-Fi, etc.) I installed gapps and that's where the problems began. I first tried gapps-jb-20130409-signed (which did not get installed with CM10). After it was installed, I lost the keyboard app (kept getting messages about the keyboard no longer working). I tried suggestions of default/reset and clearing both caches. Didn't fix the problem. Wasn't sure how to uninstall gapps, so I did a complete CM10 reinstall and tried gapps-jb-20130409-signed again. Still no good. I thought maybe it was a compatibility issue (I could never be absolutely clear which gapps would work with which CM version). So, I went with gapps-jb-20130301-signed. Same problems. I then came across gapps-jb-4.2-Gapps-And-Extras-Signed (I changed the name to be sure it would work with ClockWorksMod) mentioned in a posting. This seemed to do the trick. Keyboard remains fully functional.
I'm curious if there are any log files kept on the TP from the install. Each time I installed CM10, I noticed in the messages rolling up the screen that certain directories couldn't be found. And I think a few of them were related to gapps installation. I'd be interested to see what that was about.
The only problem I've noticed in the short time I've played with it is that the Wi-Fi went inactive (and not temporarily). I went into settings and tried to turn it off and then back on. Once I turned it off, I wasn't allowed to turn it on. There are prob'ly 1/2 a dozen or more Wi-Fi sites nearby, but the TP couldn't see any of them. I ended up doing a power down/reboot and that brought back Wi-Fi.
Anyway, I am very pleased with the new OS. And happy to be independent from WebOS, since its future is unknown.
Cheers....Steph
A two years old device with the latest Android, yeah, its definitively a great work!
Log files are saved in the back up and/or in /cache/recovery/last_log . Also do you have the "Keep Wi-Fi on during sleep" setting set to Never? That might be why your wifi is having issues, because I had the same issue when mine was set to Never. Now I usually keep mine set to Always and it hasn't had that issue and doesnt seem to use the battery too much.
Surge1223
Im curious, were you testing CM10 or CM10.1?
Go and read a guide again, you're installing the wrong gapps. The ones it specifically says not to use.
You need this one:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Hey all - long time lurker, first time poster.
I flashed the latest CM9 nightly 7/14 when it came out and things were working pretty well, except the wi-fi was a little laggy when waking up from sleep. I had it set to turn the wi-fi off when sleeping, and it would take 30-45 seconds for the wi-fi to kick back on. Sometimes it wouldn't kick back on at all, and I'd have to turn the wi-fi off completely and then back on, or just totally reboot. Not a single SOD (sleep of death) though.
Anyway, I saw the new wi-fi drivers posted by jcsullins on 7/21, and tried them out yesterday afternoon to see if that helped the wi-fi lagginess. It did seem to help, but I had 3 SOD's (out of 4 sleeps) in less than 24 hours. So, I flashed back to the 7/14 nightly from before, and it looks like things are back the way they work, no more SOD.
I wanted to report it in the dev thread, but can't yet. Anyone else experiencing this issue with the 7/14 nightly, and/or the wi-fi patch?
Also, just to be clear, I installed the wi-fi patch from recovery... meaning, I downloaded the ZIP from goo.im using GooManager, rebooted into CWM, installed the ZIP from within CWM, and then rebooted again back into CM9.