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.
Related
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!
My stylus frequently does not register with my Galaxy Note. At first, I thought it was a stylus issue, so I bought a replacement (also tried my pen from my Thinkpad tablet). The replacement had the same behavior: the stylus works after reboot for a while, then it stops. It seems to stop randomly, and then it starts working again randomly. The *only* consistent behavior I have found is that it works frequently after reboot and.. get this.. it works after I toggle my Wifi. I've been monitoring battery temp/voltage to see if there is any correlation, and also CPU speed, but I haven't noticed anything. I also tried a full reset, expecting it to work fine and the stylus had problems right from the beginning (on the device setup screen) without reinstalling any software or restoring from backup. I did have a protective screen, but I removed that and it made no difference. My phone is in otherwise good condition and hasn't been abused in any manner. Thoughts?
Recently I have read quite a few posts stating the problem of s-pen/digitizer? Is it true? I mean do these problem occur (where s-pen loses its potential of functionality) over time? Hence making it of no use. The main catch for Note is obviously the S-pen. Hence might disturb the consumers.
Maybe, it's the rom, try flashing another stock rom, I have trouble (and more with me), with the KKA rom so maybe that helps n
Sent from my GT-N7000 using Tapatalk
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
To clarify, I think this might be two separate issues...
I'm not as concerned with the CM9 issue, as it is only a mild annoyance and everything else is outstanding. CM10 is virtually unusable, however, so I'm hoping someone can help me out there.
thatdumbguy said:
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
Click to expand...
Click to collapse
I've not had this issue, but this might help. Go here : http://goo.im/devs/jcsullins/cmtouchpad/testing
Download the touch pressure utility (should be the last one) and flash it. Hope it helps.
Good luck.
As an update, after shelving the touchpad for a few months, I have revisited it, and, after doing a clean install of jcsullins' CM10.1 w/BT Fix (20130808), the same issues as above still persist. I've done the following, although I didn't really expect most of them to work:
Switching to stylus mode (no difference)
Changing the accessibility settings for touch & hold delay
Even went so far as to install another launcher (nova) to ensure it wasn't trebuchet (not that I think it was)
Same for the keyboard
This has never been an issue I've seen in webOS... additionally, I don't remember ever having any issues in CM7 either. I did play with webOS for some time today to make sure it wasn't some kind of hardware failure between now and the last time I used it frequently, but I failed to reproduce the problem there.
Is there any light someone can shed on the subject? Thanks!
Thanks for that Chicle_11... I don't know why I failed to mention it, but I did also try the patches with CM9, but it is to my understanding that they were rolled into cm9 nightlies at some point?
I wonder if I could be having a minor hardware issue that just isn't severe enough to display in webOS, because I can't seem to find anything else about this, especially the keyboard problem with CM10. Its bizaar for sure.
Started experiencing the same issues after upgrading from cm9
I recently upgraded from cm9 to cm10.2 and immediately noticed this issue. There were no such issues with cm9. When swyping on the keyboard (any - Google, Swype, etc.), the system registers that I lifted my finger, and so garbage gets typed - you can also see the effect in the trace. When typing instead, letters sometimes double-up for a single press. When playing games like PvZ2, dragging a plant results in a release of the plant before I've lifted my finger, and sometimes the plant gets planted across the screen from where my finger is pressing.
I bought a used Droid Bionic off eBay cheap as a temporary replacement for my broken Samsung S3 to last until contract renewal time. But, this thing is just a turd. It's a PITA to use.
I'm running SlimKat in Slot 1. That's the only custom ROM I have installed. But it's just as slow if I boot the stock rom (and was before I rooted or did any customizing).
When I get a call, it rings several times before the screen wakes up so I can answer it. A couple times, the call has gone to voicemail before the screen woke up so I could answer the call. The capacitive buttons light up, it vibrates, the ringtone plays, but the screen stays dark until the 3rd ring.
Sometimes it takes 10 or 15 seconds just to get the keyboard to come up when I touch a text entry box. Doesn't matter what app or what keyboard I use.
Sometimes it takes so long for it to respond to a touch that I don't know if it registered my touch so I touch the screen again then a few seconds later it registers both touches which totally screws up whatever I was trying to do and I have to start over.
Sometimes I just want to throw this thing against a brick wall. It would be very satisfying to watch it shatter into pieces. It's frustrating me so much, I'm seriously thinking of borrowing a friend's old iPhone... Just typing that made me feel dirty, but that's how bad it is.
I don't see anybody else complaining. What's wrong with my phone?
HeathicusF said:
I bought a used Droid Bionic off eBay....
....I don't see anybody else complaining. What's wrong with my phone?
Click to expand...
Click to collapse
Have you tried running LagFix (from the Play Store; I am unable to post a link)? My phone slowed significantly over time while running CM11 nightlies; I occasionally boot into stock and run LagFix and it does clear up a fair number of slowdowns. This seems the most likely cause which would impact both stock and slot performance.
It's not ROM but the battery that makes phone slow over the time... Old battery creates static charge and unable to generate enough discharge to run the phone.
Replace the battery with the new one.. And you are good to go...
Sent from my DROID BIONIC HD using Tapatalk
I tried LagFix, but got an error saying it was incompatible.
My battery does die awfully fast, so I've ordered a replacement. I have doubts about that fixing the slowness, but I needed a new battery anyway so it won't be a total loss if it doesn't work.
HeathicusF said:
I bought a used Droid Bionic off eBay cheap as a temporary replacement for my broken Samsung S3 to last until contract renewal time. But, this thing is just a turd. It's a PITA to use.
I'm running SlimKat in Slot 1. That's the only custom ROM I have installed. But it's just as slow if I boot the stock rom (and was before I rooted or did any customizing).
When I get a call, it rings several times before the screen wakes up so I can answer it. A couple times, the call has gone to voicemail before the screen woke up so I could answer the call. The capacitive buttons light up, it vibrates, the ringtone plays, but the screen stays dark until the 3rd ring.
Sometimes it takes 10 or 15 seconds just to get the keyboard to come up when I touch a text entry box. Doesn't matter what app or what keyboard I use.
Sometimes it takes so long for it to respond to a touch that I don't know if it registered my touch so I touch the screen again then a few seconds later it registers both touches which totally screws up whatever I was trying to do and I have to start over.
Sometimes I just want to throw this thing against a brick wall. It would be very satisfying to watch it shatter into pieces. It's frustrating me so much, I'm seriously thinking of borrowing a friend's old iPhone... Just typing that made me feel dirty, but that's how bad it is.
I don't see anybody else complaining. What's wrong with my phone?
Click to expand...
Click to collapse
Not sure what you are doing to your Bionic to make it so slow. Mine is by far no speed demon but definitely not slow. Do you have a lot of unnecessary crap such as widgets, themes, etc.. running?
matriX1218 said:
It's not ROM but the battery that makes phone slow over the time... Old battery creates static charge and unable to generate enough discharge to run the phone.
Replace the battery with the new one.. And you are good to go...
Sent from my DROID BIONIC HD using Tapatalk
Click to expand...
Click to collapse
That is debatable.
mikemikemikexxx said:
Not sure what you are doing to your Bionic to make it so slow. Mine is by far no speed demon but definitely not slow. Do you have a lot of unnecessary crap such as widgets, themes, etc.. running?
Click to expand...
Click to collapse
Not at all. The only widget I use is the calendar widget. I use Nova launcher, trimmed down to one home screen. No themes. No games. Only a handful of apps and most of those are utilities (ES File Explorer, Swifkey, Dropbox, XBMC remote, an alarm clock, etc.). Facebook is the only social media app.
HeathicusF said:
Not at all. The only widget I use is the calendar widget. I use Nova launcher, trimmed down to one home screen. No themes. No games. Only a handful of apps and most of those are utilities (ES File Explorer, Swifkey, Dropbox, XBMC remote, an alarm clock, etc.). Facebook is the only social media app.
Click to expand...
Click to collapse
That is bizarre, must be Slim Kat. I am on CM M8 and while it does have some minor slow downs sometimes but nothing what you describe.
(A good time to update SafeStrap if you are not on the newest version)
HeathicusF said:
I tried LagFix, but got an error saying it was incompatible.
...
Click to expand...
Click to collapse
LagFix has to be run from the stock install, rather than from a custom rom slot; it will then work only on the /data partition, which is normal.
Concerning the delay in pulling up the screen for an incoming call, I also have that same issue inconsistently on CM11 nightlies - it's often the third pulse of the motor before the screen wakes up. I haven't found a good solution to this, as it seems to be related to the phone being in deep sleep with the second core hot-unplugged. You may be able to increase the responsiveness at the cost of battery life by increasing the minimum processor speed or using a different governor, but I haven't experimented with this systematically enough to make a recommendation.
I found a solution!!
A new Samsung Galaxy S5 will be here tomorrow.
[emoji23][emoji23][emoji23][emoji23][emoji23]
Sent from my M2 using Tapatalk
Battery effecting speed seems quite farfetched. If you say it's "static charge" that really means nothing. Maybe you mean it won't source enough current. Therefore effecting processor speed? If so then plugging in would fix you up.
Bought my One Plus 3t almost 14 days ago.
I am running latest freedom rom with xceed kernel.
This annoyance has kept going on intermittently. I noticed it when I'm on calls , but it still happens when I'm not.
I'll turn on the screen, use fingerprint, it unlocks phone, soft buttons work and UI responds, but the screen itself, won't respond to any of my touches. If i turn the screen off and on twice, it will begin responding.
WTH right?
Edit, def happens when i'm on a phone call way more, just happened twice while on the phone with OPO. could it be my glass screen protector?
anyone?
Never had that. You can't really do much warranty-wise unless you can replicate it with the stock ROM, as it could be a software issue (though it's unlikely).
Never had this. But I've only been running stock until 4.0.1 and from there clean Lineage OS with stock and Boeffla kernel.