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.
Related
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.
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!
Hi
Looked for this issue on the forum and can find instances of it happening occasioinally, but not with the frequency that i have. Symptomns are that the screen will stop responding to input. I.e the screen stays painted but does not respond to my pokes or pros. Flicking the screen on and off for a split second fixes it. I believe its related to software or resource usage -sometimes i can go for ages without issues, however in the last half an hour this has happened around ten times. please help!
I have tried isolating it down to a particular app with no success, and also changed the CPU governance settings, asgin unsuccessfully. I have no such issues in WebOS.
Thanks.
ps running CM9 alpha 2, but had same issue on 0.6
flash the latest nightly.
screen unresponsive281]flash the latest nightly.[/QUOTE]
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
the latest nightly offers quite a few fixes.....
including vibration from sleep and tons of other stuff. not much can go wrong.
Andysan said:
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
Click to expand...
Click to collapse
There has been loads of improvements in CM9 wifi has been fixed sound distortion when the screen off is fixed many speed fixes we now have themes working
Do a nandroid backup in CWM then copy that to your pc for safety then wipe system partition DO NOT FACTORY RESET OR WIPE DATA or you will lose you data, then flash latest nightly and latest gapps then wipe dalvik cache/cache partition's then in advanced fix permission's and reboot system
Well.... I dip my hat to you guys.
Went ahead and installed the latest nightly - even if it doesn't fix my issue, I was suprised by how polished it felt compared with Alpha 2. Typically with bleeding edge stuff I'd have expected to have more issues, but alls I had to do was reinstall YouTUbe and flash the gapps-fixer zip for my Calender sync, plus I see lots of lovely new settings to play with.
Will report back if the screen hangs again, here's hoping...
Frustratingly this issue has started happening for me again running 31 May nightly - touch screen has become unresponsive half a dozen times in the last ten minutes.
Maybe trying wiping it and doing a brand new flash from the latest nightly. (I know it sucks to reinstall stuff, but maybe there are some leftover codes that is causing trouble.. )
i agree either to wiping data or up your min cpu speed as it might the amount of apps you have installed that auto start/resume when turn on the screen..
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I only had that problem once. Rebooted by holding home and power never had it again.
Sent from my YP-GI1 using XDA
Had this issue yesterday for the first time since installing cm9 6(?) months ago.
Tried a nightly build as suggested, but given the rarity in the first place, can't be sure it's fixed
This happens to me all the time across all ROMs I have tested.
This happens in OaT's and turning the screen off/on, fixes it temporarily.
This happens in Butta, but turning the screen off/on does nothing. I have to reboot using power/home.
I have also been unable to find a specific app that causes it, but it does seem to occur more often in graphic intensive games.
I can go for days without it happening, then BAM, it stops responding to touch, from that point forward, no about of reboots or full shutdowns seems to fix it for several hours. I'll reboot and sometimes it'll be immediately, sometimes it will be 3-5 minutes, but it will happen again.
Then a few hours later it'll stop happening and I'm good for a few more days.
Do those of you using CM9 find that screen off/on fixes it, or do you need a full reboot?
I am running the night lies and have to say that the only time I experienced this was with the may nightlies. I have not experienced any issues with the 7/04 nightly.
Sent from my cm_tenderloin using Tapatalk 2
Interestingly enough I think I found out what causes the screen to stop responding. When the TouchPad is locked in landscape and then I turn it portrait while its still locked, then the screen becomes unresponsive. Does that make sense?
Sent from my Touchpad using xda app-developers app
I take it back. The screen became unresponsive even in landscape mode. There goes my well formed and thoroughly investigated theory.
Sent from my Touchpad using xda app-developers app
---------- Post added at 07:54 PM ---------- Previous post was at 07:22 PM ----------
I've been using Nova Launcher ... I switched back to Trebuchet and it appears to be working normally. Of course I may be spouting this half-cocked like I did before. What launcher are you using?
I run SPB 3D launcher and do not experience any response issues with the latest nightlies. I use my touchpad constantly as a laptop replacement so mine gets a workout every day. To my knowledge, no one was ever able to find any one app that was responsable for this behaviour but it was noted in earlier builds.
,
Sent from my cm_tenderloin using Tapatalk 2
I too still have this issue - as per others, fine for days, then it will occur consistently and I keep having to screen off/on and eventually it stops of its own accord. Am sure its a software issue, but someone here says they also had it in WebOS and HP provided a replacement.
http://rootzwiki.com/topic/20740-screen-unresponsive-in-cm9/
For me as simply flapping the screen on/off fixes it and I've never had the issue within WebOS, it has to be software - this started as soon as I first installled CM9.
Bump - still no fix identified for this by anyone with this issue please?
To anyone still following on, followed nevertells advise and completely started again from scratch and it happened after about twenty mins of using the stock browser. I think i've tried not using that app before so am just going to assume that this is either a software bug or a hardware issue that only manifests itaelf within Android
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
iamatechnoob said:
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
Click to expand...
Click to collapse
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
chicle_11 said:
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
Click to expand...
Click to collapse
Wow, you are right, webos has the same problem. I guess I was just in denial that it was a hardware issue and didn't think of checking it in webos. Damn, I don't think HP would want this back right
Sigh guess I should look into the chinapads my friend was recommending just this morning
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
iamatechnoob said:
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
Click to expand...
Click to collapse
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
chicle_11 said:
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
Click to expand...
Click to collapse
Thanks for the help! Will try this after backing up my stuff via Helium.
I have the impression that 10.1 isn't that stable, but I am likely wrong. Dont seem to see any cm10.1 with low deep sleep drain + working camera & mic + most other functions, or I could be looking at the wrong places.
I use milaq's nightlies, and for my needs, it's more than adequate.
Good Evening,
I have a 16GB Touchpad. I've run numerous roms on the system. I currently have Evervolv Nightly 8-17-14 4.4.4 (I think). I have had JCS and Pac-rom on it recently, too.
This problem has happened off and on since CM9 perhaps even before. I don't remember if this did happen in WebOS.
While in use the system will randomly stop responding to touch. I need only hit the sleep (power) button once to put it in sleep, then once again to wake it up and the touch works again for a little while. This is very annoying during games as I have to constantly put the pad to sleep and wake it up to restore the functionality.
Honestly, the pad is used mostly by my son for games and youtube and it has survived several drops. Being a 4 year old he gets very frustrated when the touch stops working, too.
I initially thought this was due to my son installing tons of random games and applications but even after fresh wipes and OS installs it will still freeze.
Is there any way to troubleshoot this? Any linux/android log files that contain information related to the "touch" driver? Should I just try to order a new digitizer? reseat the current digitizer?
Thanks for the help!
Paul