Has anyone had any problems with the screen doing its own thing? My nook is rooted using autonooter (1.0.0 eclair) but lately it has been doing things without me touching the screen at all. For example, one time i was in the (Dolphin HD?) browser and I went to go type something and it kept pressing the "O" on the keyboard until I exited the browser. Also, I have prolauncher installed for the home screen and it also spazzed out by switching back and forth between showing the thumbnails of the homescreen and back to the single homescreen view.
(Mine started to do this on 900mhz "screamer" kernel and also on the new 1ghz kernel thats based on that other omap processor (cannot remember right now)
This doesn't seem to be only happening to me. My roommate just bought one too and he said he was reading a book on his and it scrolled through 20 pages on its own. His is also autonootered on 1.0.0. His nook is on stock kernel.
Stumbled upon this thread, recently:
http://bookclubs.barnesandnoble.com...ok-Color-Touchscreen-Freaking-Out/td-p/731993
Related
Hi guys,
I'm on 2.1 Stock ROM, no taskkillers etc.
My homescreen is completely frozen as I type now and I can't open the apps menu (the app drawer with 3D conveyor belt effects) or slide to any other homescreen whether i lock/unlock the screen as many times i want!
On touching any homescreen icon absolutely unrelated apps are launching, eg, on touching messaging icon the stock camera launches (whose icon is on a different homescreen!)...on touching market icon...color flashlight launches (icon not on any homescreen...straight in app menu/drawer) etc etc! So cant launch maps or anything. 8 icons on homescreen and remaining space is taken by weather widget donation HTC style clock.
Wait a min...a call just came through fine and I could answer it...after hanging up I could touch all home screen icons and they were working but then suddenly my entire home screen rotated and went to landscape mode! Like all home menu icons, weather clock etc are in landscape/vertical direction and not alined/fitted to the entire screen...as in the ends of icons are cut off as the whole page looks magnified cos its obv not intended to be like that. Landscape orientation is not supported or needed on homescreens/app menu etc on the N1. Why is this happening (never came across this orientation change issues in any forums inc. xda) , why the hang?! Weird things regarding touch sensitivity and screen behaviour etc keep happening from time to time but I know about all that screen, touch sensor make and quality issues etc etc.
Also, I've noticed that everytime after a restart my phone takes atleast 20 mins to half hour plus to get everything working snappily and respond at full speed, eg, till then homescreen transitions are not smooth, all gallery pics dont load up to show for a long while (16 gig class 2 sandisk card). Is this normal?
Sometimes after switching to 3G my 3G watchdog (mobile data transfer measurement app) doesn't auto launch (app issue maybe?) and sometimes no mater how many times I choose wifi ON, it doesn't turn on! Switching it off from power control widget (i.e., 3G on) and then on again doesn't turn on wifi either even when good signal on my laptop!
Earlier today my phone was lying on the desk and it auto-restarted god knows why! The phone freeze happened like 10-11 hours after the restart today afternoon so memory etc wasn't so full or too many apps launched. The home screen rotation orientation has changed before in the past too so not first time to be clear.
I have still more than 80 mb app memory free in internal memory and dont overload my phone with crappy apps etc etc.
Pls advice and discuss.
I know you're on a stock rom now, but have you previously unlocked the bootloader and flashed anything else like recoveries, roms, etc?
If you have and you just reverted back to a stock rom, you could've downloaded a bad rom.
Have you dropped your phone? banged it around a bit?
mrandroid said:
I know you're on a stock rom now, but have you previously unlocked the bootloader and flashed anything else like recoveries, roms, etc?
If you have and you just reverted back to a stock rom, you could've downloaded a bad rom.
Have you dropped your phone? banged it around a bit?
Click to expand...
Click to collapse
Nope...none of those...fresh as a daisy!
Ok, well 2 options...
Option #1 - Return your phone for a new one if it's under warranty.
Option #2 - Unlock the bootloader, upgrade your recovery, flash the new radio and upgrade to a new rom like cyanogenmod. Come to the Dark Side young skywalker.
mrandroid said:
Ok, well 2 options...
Option #1 - Return your phone for a new one if it's under warranty.
Option #2 - Unlock the bootloader, upgrade your recovery, flash the new radio and upgrade to a new rom like cyanogenmod. Come to the Dark Side young skywalker.
Click to expand...
Click to collapse
So returning or rooting are my only options??? Why does the screen rotate weirdly? Is there any explanation of what's gone wrong?!
See if its a hardware n I root then I'll cry later due to voided warranty n in UK we get a 2 year warranty.
As far as bumps or knocks are concerned...ofcourse the phone takes normal hits or once or twice falls from my laptop to my carpeted floor but that's all.
There has to be logic behind this!
strange sceen happenings...
I've had the same ghost in my machine. In addition, my nexus would lose communication with the network and the cool startup screen with the streaming x would show. I had to pull the battery to get things back to normal. Enom suggested to watch my apps, he thought maybe one had a memory leak.
I found that moving my apps to my sdcard made my phone shot my phone to the streaming x about twice a day. Since wiping and not doing this, I haven't had that problem. I also found that my fav craigslist app was causing my screen to go unresponsive. I think the craigslist app was checking it's update and monopolized the cpu. Since my wipe i havent' installed it and the phone is working better.
Last, I installed nextheme 1.8.1. It also seems to quell the errant screen happenings. The screen still has it's moments, but if i press the off button and turn the phone back on again, i have control back.
I still have problems, but i've gotten them managable. I don't think it's a hardware problem because my rom choise and app selection really affect it. If it were hardware, it would be more consisitant regardless.
Hope this helps...
Hey I just got my current droid about two months ago (my last one the screen gave out and I got it replaced under warranty). Anyways, at first it was working really fast, but lately whenever I exit a app the home screen takes about ten seconds to load the icons. I haven't installed that many apps, just a few games, pandora, and a sports app so I don't think they are the problem. The browser has also slowed down significantly and I'm wondering if that might have something to do with the 2.2 update? Both these problems are driving me nuts and I'm seriously considering going back to my old flip phone again...
Tried out the new nookie froyo and overrall it runs great. Lower quadrants but not really a big deal.
For some reason when I use a browser and start typing in a field (for instance a password field for my colleges website), it lags incredibly slow. Its almost as if the keyboard is lagging, but this isnt a problem in other fields, such as the URL.
Such a big problem I had to uninstall back to eclair.
Installed with Iomonsters, clockwork from the market, used stock kernel, OC kernel, nothing made a difference. Disabling haptic feedback made a small help, but still unusable.
Anyone else getting this problem?
tangomonky said:
Tried out the new nookie froyo and overrall it runs great. Lower quadrants but not really a big deal.
For some reason when I use a browser and start typing in a field (for instance a password field for my colleges website), it lags incredibly slow. Its almost as if the keyboard is lagging, but this isnt a problem in other fields, such as the URL.
Such a big problem I had to uninstall back to eclair.
Installed with Iomonsters, clockwork from the market, used stock kernel, OC kernel, nothing made a difference. Disabling haptic feedback made a small help, but still unusable.
Anyone else getting this problem?
Click to expand...
Click to collapse
You know, I really have no idea why this happens, but I had a similar experience. The first few hours I was running Froyo 0.6.6 it was kinda slow and laggy. But after a few reboots and couple of hours of running it was extremely fast. So all I can suggest is try putting up with it for a day or so and rebooting it every couple of hours. For me it runs extremely smoothly and much faster than eclair now.
Going to try. Ugh why cant I just leave this thing alone.
Just keep using it, it will speed up after a few reboota
Sent from my PC36100 using Tapatalk
I am about 12 hours in and at least 6 reboots now and still the problem is unresolved. Seems to be exasperated on webpages with large images in the background.
All in all I think .59 felt alot more stable then 6.6 and 6.7. Think I will either go back to eclair or try Honeycomb till a better froyo comes out.
edit: if any of you other guys wants to try, goto atlas.valenciacc.edu while viewing a full webpage. Both stock browser, skyfire, and dolphin hd share the problem. I cant easily type in the UN and PW fields.
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!
Read through the "sluggish" thread and did not see my issue mentioned and thatthread seems to have become sidetracked with benchmarks and game responsiveness issues.
I am running stock nook rom, rooted and with sideloading enabled. I also use GOlauncher as opposed to the nook launcher.
What i have noticed is that after 2 to 3 weeks of use the tablet slowly starts to get slow and unresponsive. Dolphin takes time to open, and pages scroll very very slowly. Sometimes they will not scroll at all, even though theyare fully loaded and rendered. Scrolling is also noticeably slow and unresponsive in the engadget app. It is not smooth, but jerky, ifit scrolls at all. Rebooting does not have any effect.
The first time this happened i did bring the free space down to about 300meg. After reading other posts here i decided that was the issue, backed up and started allthe way over from scratch! The issue went away. I re-installed everything, got it running clean and smooth and set up just how i like it. I then took a cwm backup and put it insafe place. Fast forward 3 more weeks and i was back to slow scrolling and unresponsiveness again. At no time in that 3 weeks did i drop below 8 gig free, so i know that is not the issue.
Here is where it gets a little strange. Today, i did a full backup with titanium, then a restore from my fully config and SMOOTH cwm backup. I then did a restore all appps and system data from the titanium i made earlier in the day. I am back to smooth and responsive. This tells me there is something that is getting corrupted or not released, even with a reboot. Anyone have any ideas on what to try next time other than a restore from cwm and a reload from titanium?
I had the same issues with stock 2.1. Besides the slow game loading and random stutter for games, the device would slowly start to accumulate to slow for everything. I would like to test with 10.1 as my native stock OS, rather than 2.1.
I had a similar experience. Even after disabling nook sync apps and making tweaks, stock would eventually slow down. Something about stock 2.1 just doesn't manage its memory/cache properly.
This isn't the solution you may want, but I'd recommend trying emmc Cm10.1. Its plain, but its virtually bug free and hasn't crashed on me yet.
This isn't the solution you may want said:
I've been rooting and bootloader unlocking Android for about 3 years now and this has to be the easiest tablet to put CM 10.1 on with the latest tools. It's actually easier than my Nexus 7 when it first came out. My hair actually turned grey when I was unlocking my Note 2 bootloader. I wish every Android device was just as easy as the Nook HD+. I think part of the confusion is that in the beginning you had one method (running CM off sd card) and you now have the more current method (replacing Rom which is the most common). The development area needs to be cleaned up better because it does look confusing. I've only been a Nook HD+ owner for 24 hours and I have made my custom micro SD card, installed CM 10.1, reverted back to stock with no backup (needed to return for a bright pixel in the middle of the display), repeated process again with new tablet and made proper backups. Sounds like a lot but this is nothing compared to what I've been through.
Click to expand...
Click to collapse
Seems to be because B&N has trim disabled:
http://blog.davidron.com/2013/10/fixing-lag-on-barnes-and-noble-nook-hd.html