i haven't come across anyone experiencing anything quite like this, even after searching the dev forums. after locking my screen, everything goes black, just like it should, but everytime, I'll look at the screen a few minutes laterr to find that the screen is powered on, but onky displaying black. its not a huge problem, but it eats battery. Has anyone found a solution for this problem or even experienced it?
Im using regular nookie froyo 0.6.8 (3/18) flashed to an 8gb sdcard, stock kernels and everything
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.
In used the eMMC install of Froyo (2/25), for reference.
So, I saw a few threads about various issues, but my main question regards Droidwall, though I have a few other issues as well.
1. Droidwall was working great on Eclair, but now it refuses to work at all. Is there any workaround for this?
2. Also, the screen flicker when I put it to sleep and turn it back on is pretty awful, and this was never an issue on my OC Eclair install. Is there a way to minimize this? It was totally manageable on stock. Maybe flicker is the wrong terminology as it's not the constant screen flicker others have noted.
3. I also attempted to use the app SamuelHaff posted to fix market issues, but it didn't seem to do much. I installed flash from the market right when I first booted and it worked, but now no apps will install anymore. The market itself loads and searches just fine, but installation always, always fails now.
I realize that this is a laundry list of questions, but I'd really appreciate some help since making the jump to Froyo has been mostly nice. It's really, really speedy. If I could get these ironed out, it'd be awesome as my daily!
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!
Having a major issue here with my NC. Running CM 7.1 and I'm getting random hangups during normal use. The touchscreen becomes completely unresponsive, and I can't turn the display on or off. If I'm listening to music, however, the music continues to play. The only way to fix it is to reboot the NC. Has anyone heard of this and can offer me a fix?
Thanks in advance
oriz
Is it an SD card install? If so what is the brand of your card.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Yes, I had the exact same problem with a new install on emmc, and uninstalling Beautiful Widgets on the advice of another thread I found here completely solved the problem. I had forgotten that BW did the same thing to my Incredible when I tried it a long time ago. If you don't have BW installed then take this as a warning not too
Very interesting...
I've had the exact same problem myself for awhile now, and couldn't figure out the cause. I even wiped the Nook and reflashed CM7.1, but the problem still popped up once and awhile.
I'm also using Beautiful Widgets. I think we have a pattern developing here. Can the OP confirm/deny he has BW installed?
Beautiful Widgets messed me up too...hung the hell out of my nook color. They even know of the issue and did nothing about it. Got it on Amazon as a paid app.
Hi everyone,
I was up to ICS Rom yesterday, but everytime i unlock screen, i cant touch in the bottom of the screen, cant typing with h, g, j and somewhere around it, but on the right, left or top screen i can still use normal. Does anyone know what happen and how to fix it?
When im in CM7 Rom is was fine and has no problem
PS: Sr for my bad english i really not good in grammar.
Same problem but different area
I have the same issue.
On Apex i had no issues but when i upgraded to SlimICS 3.2. The right side of the screen ocasionally becomes unresponsive.
That is, on any keyboard from approximately the 'i' to backspace horizontally, and from enter to the top of the screen.
This whole zone randomly decides not to work. the only fix is to turn the screen off and then turn the screen on again, or backing out of the application and reloading it. The application can be anything, chrome browser, swiftkey, messages, whatsapp.
Does anyone know what the issue could be?
I'm running slimics3.2 with semaphore ics 1.0
I'm also running slim 3.2 and had the same issue with the sephamore kernal. I just reflashec the essentials and everything worked perfectly for me.
Sent from my SGH-I897 using XDA
I used the essentials kernel first and experienced the issue, i thought it was a kernel issue so I flashed semaphore afterwards. But I still have the issue...
arse87zx said:
I'm also running slim 3.2 and had the same issue with the sephamore kernal. I just reflashec the essentials and everything worked perfectly for me.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I tryed AOKP 3.0 and didn't modify anything, also some another ROM but it still have a problem with the touchscreen
KunNuK said:
Hi everyone,
I was up to ICS Rom yesterday, but everytime i unlock screen, i cant touch in the bottom of the screen, cant typing with h, g, j and somewhere around it, but on the right, left or top screen i can still use normal. Does anyone know what happen and how to fix it?
When im in CM7 Rom is was fine and has no problem
PS: Sr for my bad english i really not good in grammar.
Click to expand...
Click to collapse
I hate to say this, but its probably the fact the phone does not like ICS, it is more than likely some sort of hardware incompatibility issue.
I went through this exact same thing, it was on a 1009 or so build number captivate, no matter what flavor of ICS, none of them would work properly with the touchscreen hardware, there was always a spot of the screen, at the lower center 1/4 portion of the screen, that was unresponsive. Flashing a Froyo or Gingerbread rom, the touchscreen was perfect.
So.. I sold that Captivate, purchaced a refurb Captivate off Ebay, and touchscreen is perfect with ICS (CM9 is what I run).
Wish I had something more helpful, but that's my experience. Good luck with it.