Database Develop

[Q] Touchscreen phantom touches

Sometimes my NC will start registering phantom touches, opening apps or links at random. If I sleep/wake it, it will again be OK for a few minutes. It seems to also appear if I use pinch zooming.
I first noticed it on Froyo, and now also on CM7 nightlies. I have tried the fix with ADB to recalibrate it, but it seems to always come back. I'm not sure if I'm not doing it right, or if it's because I flash a new ROM nearly every night.
Is the calibration setting something in firmware that stays set, or am I wiping it out every time I flash a new ROM?

claudius753 said:
Sometimes my NC will start registering phantom touches, opening apps or links at random. If I sleep/wake it, it will again be OK for a few minutes. It seems to also appear if I use pinch zooming.
I first noticed it on Froyo, and now also on CM7 nightlies. I have tried the fix with ADB to recalibrate it, but it seems to always come back. I'm not sure if I'm not doing it right, or if it's because I flash a new ROM nearly every night.
Is the calibration setting something in firmware that stays set, or am I wiping it out every time I flash a new ROM?
Click to expand...
Click to collapse
The Nook screen is incredibly sensitive to Moisture of any kind, Greasy Finger Prints, Water in the Air, Spit... Ect ect... Most People see a Huge leap in screen usability after installing a Good Screen Protector, many will recommend the Anti-Glare kit that B&N sells. I would also recommend it, as it has fixed 90% of my Screen problems.
Also there is a Known issue with Defective Chargers and you will see this type of Behavior while using the Charger on the Nook. Some have gotten replacements from B&N and say that it fixes the screen issues while charging.

I witnessed it today in my friend's office. Later found out that it only happened when he plugged in a different power source. The problem went away after he plugged it back to the B&N adapter.
Sent from my PC36100 using XDA App

My issue happens both when charging and when not charging. Though the moisture issue is a distinct possibility, I do notice that the screen gets very greasy compared to my phone's screen.
Have either of you tried the screen calibration through ADB? I'm still curious as to whether that setting is persistent or if it gets wiped with a rom flash.
I've never been one to use screen protectors, as I find they usually make the screen worse to use, and screw up the "feel" of the screen, if that makes sense. But it may be worth it to try one.

I'm having the same problems. Phantom touches and also the screen sometimes stops responding to touch. I just put it to sleep and then wake it up and all is fine. I'm definitely going to try a screen protector. I'm thinking it's related to moisture/etc.

I had the same problem. Made it next to impossible to get through a pdf on adobe. I had 1.0.1 stock, so I returned the nook color to factory default (the 8 failed boots + button/power on), upgraded to 1.1.0 through a sideloader, and then rooted. So far no more phantom touches after a day of use!
I think what might have been the cause was using 1.0.1 rooted stock NC and trying out HC. But I'm not sure. Mostly it's an educated guess that whomever did the custom rom made the screen more sensitive because they are running their unit with a screensaver.
I would try going back to factory default if you still have it or original rom, trying to update to 1.1.0 and then go from there.

Unresponsive touchscreen on CM7 nightly#13

I just got my $199 Ebay NC last night, and loaded CM7's newest nightly #13 on it.
Everything seems to be in working order, including market and whatnot, but there is one problem: some areas of the screen would become unresponsive. I noticed it repeatedly in three scenarios:
1. When the notification bar is pulled down, the "clear" button can be unresponsive
2. In market, the "install" and the subsequent "ok" to give permission buttons in an app page can be unresponsive
3. the search button on the top right corner of the market (the magnifying class) can be unresponsive
The weird thing is that the rest of the screen is fine, i.e. I can scroll up and down in the market, and I can click on individual notifications fine, but just those buttons are unresponsive.
I am using the Kernel that came with CM7, and LCD density is at default 161.
Any suggestions are appreciated.

Sounds to me like it is just the bad responsiveness of the NC around the edges of the screen? Stock, with Froyo, and now with CM7 that's been the case for me.

tarheeldan said:
Sounds to me like it is just the bad responsiveness of the NC around the edges of the screen? Stock, with Froyo, and now with CM7 that's been the case for me.
Click to expand...
Click to collapse
I see. Good to know Im not the only one having this problem.
Did you ever get this resolved? or just live with it haha

To fix the touch screen issues try Dalgrin's OC kernel over in the development forum. He fixed some of the touch screen issues with it...maybe it would fix whatever problem you are having. You can run at stock speeds if you want of course, just go to Cyanogen settings>performance>cpu and set it to stock.

pfcwintergreen said:
To fix the touch screen issues try Dalgrin's OC kernel over in the development forum. He fixed some of the touch screen issues with it...maybe it would fix whatever problem you are having. You can run at stock speeds if you want of course, just go to Cyanogen settings>performance>cpu and set it to stock.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried it and it "somewhat" helped. The problem inside the market is mostly gone, but the clear notification button is still buggy. Wondering if Nookie Froyo would make a difference.

Just saw this thread:
http://forum.xda-developers.com/showthread.php?t=980222
and tried out the app and it seems to work.

cuoreesitante said:
Thanks for the suggestion. I tried it and it "somewhat" helped. The problem inside the market is mostly gone, but the clear notification button is still buggy. Wondering if Nookie Froyo would make a difference.
Click to expand...
Click to collapse
If you notice the clear button also changes size. When it is big it's very easy to hit, but when it is small it has a very small area to hit. The upper left hand corner of the button seems to be the best location to hit.
Sent from my NookColor using Tapatalk

[Q] Erratic Touchscreen Issues

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!

Well...that freaked me out...

I'm sitting on the couch...look over at the phone and the screen is off, but there's all these weird yellow-ish, orange-ish vertical lines all over the screen. Power button does nothing. Plug it into the puter and adb reboot-bootloader it and the bootloader looks all jacked up. All kinds of crazy colored bars going up and down and a funky, zoomed in resolution.
0.0
I DIDN'T EVEN TOUCH IT!
I get into TWRP, which also looks pretty jacked up and flash my most recent backup.
Everything's fine again.
What in the SERIOUS **** was that?!!?!

rmp5s said:
I'm sitting on the couch...look over at the phone and the screen is off, but there's all these weird yellow-ish, orange-ish vertical lines all over the screen. Power button does nothing. Plug it into the puter and adb reboot-bootloader it and the bootloader looks all jacked up. All kinds of crazy colored bars going up and down and a funky, zoomed in resolution.
0.0
I DIDN'T EVEN TOUCH IT!
I get into TWRP, which also looks pretty jacked up and flash my most recent backup.
Everything's fine again.
What in the SERIOUS **** was that?!!?!
Click to expand...
Click to collapse
Imminent hardware failure. RMA it -before- it does it again.

c0LdFire said:
Imminent hardware failure. RMA it -before- it does it again.
Click to expand...
Click to collapse
DON'T SAY THAT! lol
It's fine now, though...

i wouldnt say that at all .... do you UV at all?

Lg...
Sent from my Nexus 4

Its probably a screen problem. So its RMA time lol

same exact thing happened to me twice in the first month I had the phone (had mine since Nov). I was running cm10 at the time, freaked me out pretty bad. screen was flickering too afterward, I had to reboot a few times to get it back to normal. after the second time I went back to stock completely (no root, locked boot loader, stock recovery) and never had this or any problem again
Sent from my Nexus 4 using xda app-developers app

Hmm...
Yes, I am undervolted. I was running AOKP Mako jb-mr1_build_3 when it happened. Flashed my most recent backup and it's fine. I was running build 2 of that ROM when I made the backup.
I tried to flash back to the build 3 version of this ROM after getting the phone back to normal but was getting the UI force close thing (flash a ROM or kernel and, when you reboot, you get repeated, rapid fire UI force closes...anyone else have that happen?) so I'm just going to leave it at build 2 for now.

That's what happen when you underclock

supersain08 said:
That's what happen when you underclock
Click to expand...
Click to collapse
Definitely sounds like an UV issue. Do you have a nominal or fast processor? What kernel and UV settings you running?
Sent from my Nexus 4

Was it .. hot?

Hot? No.
It isn't underclocked, it's undervolted.
Well...it was. I put it back to stock. Hopefully this won't happen anymore.

My phone does the same about every other week...
Sent from my Nexus 4 using xda app-developers app

I've had my screen flicker for several minutes before. I was undervolted and on CM at the time. Putting it to sleep and turning it back on, didn't help. However after a restart it was perfectly fine again. I undervolted back to the same level right after and am currently running it at that level (been about 2 months) and it's never done it again.
I don't recall the screen ever changing colors like you mentioned though. I have a fast binned cpu and my kernel was motely. I'm thinking it was just a glitch with CM.

I've noticed that one out of maybe 100 wake-ups doesn't turn the screen on when you press the power button. One day I left it like this for 30 seconds thinking it will come on, but instead the screen started fading to white from black - sort of like the brown starts on burning paper - and then when I pressed the power button again the screen was flickering. Seems to be a custom ROM/Kernel thing.

Invisiblek's 4.4 12-30-13 Nightly Impression

I can't post this on the Milaq thread (where most of the invisiblek discussion is) so I thought I would post it here to give anyone else a heads up.
The Good:
It's a fairly stable kernel and all my apps run seemingly just fine. I mean I've only been running it about 5 hours but not a single FC. I did have a weird bootup glitch that locked it up right away after install but after that I loaded all the apps just fine. Super exciting to see it so far!
The Bad:
Screen pixelation/tearing from left to right, especailly on grey backgrounds. Something is up with the video driver/gpu voltage. Certain icons like the Settings sprocket will have a few pixels that will flash and other times you'll see lines all the way across the screen. It might be color specific. I was playing Quadropus Rampage and never noticed it but then went back to the home screen or typing an e-mail and it's very much there.
Pandora plays music fine. If you turn off the screen while playing, horrific things happen like ZZZZZZZZZZZZ and then hard lock. I didn't like that station anyway..
The "OK Google" voice command doesn't seem to work though voice typing does. I'm pretty sure this worked on the Milaq build of the same date.
It's a bit slow and CPU is stuck to 1188. There is a bit of a lag switching apps but I don't notice any core functions slow.
The Different:
The home button doesn't wake up the TP. Only the power button.
Can't say anything about battery life quite yet but I'll keep a gander on it. Battery hasn't been a super concern of mine because I plug it in ever night

The Different:
The typical 15 second reset switch mult-button key is more like 3 seconds now. I like this a lot better.

Positive:
--backup and restore work
--it is getting much better.
Negatives:
--Microphone does not work, so I could not use any vioce search or voice dialer/sound recorder.
--Free game "F.S. Xtreme" has black box issue.
--Youtube still has reboot issue.
--TV streams app "syncbak" has similar reboot issue.

My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.

Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.

Waiting on Flintmans as it is the only non data media rom. Not a big fan of all the repartitioning. For several reasons. Good to see choices still available. God bless the developers for all their time and effort. Wish I could do what they do.

goog888 said:
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Click to expand...
Click to collapse
I flashed 3.4 rom (0103) over 3.0, and tried briefly.
--3.4 rom seems running OK, except it runs relatively slower at 1.1Ghz.
--camera is not working on both 3.0/3.4 rom.
--Free game "F.S. Xtreme" seems not compatible with 3.x kernel. It also cannot run on Samsung S3.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Turn off WiFi Optimization in settings.

EbolaCola said:
Turn off WiFi Optimization in settings.
Click to expand...
Click to collapse
Still does it. Did that soon as rom booted as per the Op.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Same here. Also double check that the setting took. I swear I unchecked it and it went back or didn't take the first time. Perhaps give it a toggle or two. I also noticed that if wifi turns off, it won't turn back on.

Anyone else having a problem with rebooting from within CM and it just goes to a blank screen?

Dirty flashed to the 1/5 nigthly. Reboot issues seems gone now, or just that a reflash has fixed mine specifically.

Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!

sokratz said:
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
Click to expand...
Click to collapse
Negative on the posting. I'm still seeing the bzzzz when the screen shuts off while playing music. Have disabled the mic (I think). Curious that nobody on that thread has reported that quite yet.

I'm very excited to see all of this development on our old TPs! I'm currently running Milaq's latest 3.0 kernel test build. It is running almost perfectly for me! I cannot wait for 3.4 to finish getting smoothed out. I've tried Invisiblek's builds out, and they currently seem a little laggy compared to Milaq's 3.0 test build. Great work all around though! Thanks to Invisiblek, Flintman, Milaq, JCSullins, Dorregary, and all of the others that I haven't mentioned who have contributed so much of their time and skill toward keeping our Touchpads relevant, even competitive with the current crop of tablets on the market!
Sent from my TouchPad using Tapatalk 4