Every other thread I see about a wifi problem kinda describes something different. My wifi messes up coming out of sleep. It will just keep connecting and disconnecting. Is their a fix for this? This is the only reason I left CM7.
This seems to be a common issue. I just turn off wifi before I hit the power button to sleep my nc. When I bring it out of sleep, I just turn wifi back on and it usually connects pretty quickly.
Which build are you using? And have you tried using a newer build?
The same issue with Nookie Froyo.
double post, please delete
buffnutz1 said:
Every other thread I see about a wifi problem kinda describes something different. My wifi messes up coming out of sleep. It will just keep connecting and disconnecting. Is their a fix for this? This is the only reason I left CM7.
Click to expand...
Click to collapse
I had the same problem with earlier builds of CM7, but switched Wifi sleep policy to never and am running CM7 nightly 19 and it no longer happens (still takes 30 seconds to a minute to reconnect if the nook has been sleeping for a long time). Now I have problems when I first turn the nook/wifi on!
I suggest updating to the newest CM7 and see if it's fixed. It doesn't seem to be specific to any one setup, but actually comes down to the individual nook.
I had the same problem with Froyo.
The problem went away after I swapped the OC kernel with stock one.
Hi! Can you tell me how you flush the stock kernel. I did the stock 1.0.1 via Rom Manager and it will just shutdown as soon as I login. Thanks.
I have the same wifi issue. I'm using Nookie Froyo 0.6.8. Everytime when I start my NC, the wifi turn on and off. Seems it's searching the signal? SOmetime it takes 1 or 2 mins. to reconnect! Originally, I thought that's hardware issue. It seems now this is a common issue for NC?
I read some post here, is to keep the wifi on, even when the NC sleep, but this will drain more battery.
Is there any better solution?
This happens with my rooted eclair NC as well. I'm now 99% sure it's an inherent NC issue. I though it was because I use Juice Defender to manage Wifi, but if manually turning it off can produce the same effect without the twitching wifi signal, then I'll do that instead.
Is there any app or method to make the wifi work better? Or is there any rom that can solve this issue?
Related
To my knowledge, there is no thread dedicated to the new numerical releases of CM. Let us start with the newest, CM 6.0.2.
Please post your anecdotal data, including benchmarking scores, bugs, and glowing experiences. Perhaps this will serve as an unofficial repository for issues that prove consistent.
Note: After modifying my WiFi settings, specifically disabling sleep mode while the screen is off, I've encountered no related instability.
Mail FC Fix: http://forum.xda-developers.com/attachment.php?attachmentid=394316&d=1283500340
Systemic issues yet to be addressed:
-LEDs do not work save for charging
-Outgoing calls initially drop before reconnecting
-Lockups or reboots, likely stemming from SetCPU
-OS does not recognize internal storage
Does this version fix the wifi not staying on?
Did you change your settings to Never sleep for wifi and just left the wifi on? Thanks...I want to try different settings and see if I can eliminate reboots/shut downs.
are we waiting for the nightly for the newest fixes like LEDs or is there gonna be a new release like .3?
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
seanmcd72 said:
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
Click to expand...
Click to collapse
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I would have to second the issue with SetCPU. As soon as I overclocked it and began using the rom I noticed the phone would get hot abnormally fast and would reboot a few times within the first few hours. Not sure what is going on here as it worked fine on the RC.
Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I didn't even notice setcpu till you said that. Phone was back to 998mhz
Sent from my INCREDIBLE using XDA app
My phone doesn't vibrate when I receive an incoming call when the phone is set to vibrate.
Has anyone else noticed the keyboard lag when using the Messaging app? Browser and this xda app seem to work fine with no lag..
Other than that, smooth.
dnoyeb said:
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
Click to expand...
Click to collapse
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
I get random reboots and freezes every thirty minutes if so on a fresh wipe of 6.0.3 I tried with setcpu and without but always with the built in hotspot running. Same issue since RC3
LED notifications dont work. LauncherPro Plus FCs on every reboot, other then those things im good with it, great wallpapers , great rom
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Panda Fuzz said:
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Click to expand...
Click to collapse
And you know the issue is the kernel because...?
mp3sum said:
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Click to expand...
Click to collapse
actually if you read the thread, you'll see koush himself is in there dealing with 6.0.2, offering up kernels and fixes...
he just hasn't updated the topic title.
Okay this may be a stupid question but how do I apply the mail fix?
mp3sum said:
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
Click to expand...
Click to collapse
Battery life was down to 81% 11 hours later, and the phone had been placed in Airplane mode while running Gentle Alarm and a few widgets (no auto task killer).
Breakdown:
System 0.6%
System Processes 0.3%
System Panel 0.3%
android.process.acore 0.1%
Plus several honorable mentions with 0.0%. I have yet to perform this experiment with Ruby or ID.
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.
Hi all;
I hope someone could point me to the right direction to fix this problem:
After installing & booting CM7, everything works fine. The problem is that when I put the NookColor into standby/sleep(one quick power button push), the LCD seems there's still dim light -- it doesn't go total black as the stock version.
The next morning, all my battery juice is gone. I believe the LCD dim on standby is the cause.
Also, anyone have good experience w/ Bluetooth? Mine skipping in & out every 2 seconds -- connection keep dropping. I tried turning off WIFI still didn't help.
Thanks in advance.
I assume this is your first time using a custom rom. Stock is able to turn off more of the hardware processes than the custom rom.
The reason for this, is because when the custom rom was set up to turn off the same processes, it would lead to the sleep of death, requiring a complete reboot. So you will lose more battery since it can't turn off all the processes like stock can.
As far as bluetooth... Try a hard reboot, and if that doesn't work. Then go into CWM and goto advanced>fix permissions.
Thanks for the reply,
I was able to turn on the BlueTooth. My problem is the connection -- keep dropping in & out.
Also it's my first time doing the custom rom. So everyone is turning off his/her NC once done using it?
Well I don't really know about the bluetooth, I'm merely suggesting you try those to see if they help. However, the range isn't very long with the bluetooth, so it could be just the item is to far away... What are you trying to connect it too?
Well, the custom rom does still preserve some battery by putting it into sleep mode. However, yes you could turn it off. I usually get it through a 8hr day through putting it into sleep mode, with some battery to spare.
Can Phiremod work on an sd boot or does it have to wipe out stock nook os?
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!
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.