Hi!
For past two-three days I am experiencing this problem. Touch sensor just randomly stops working. Top side of the screen is very very difficult to control, sometimes even impossible. Sometimes it feels like sensor recognizes multiple touches at the same time which results random pages or menus opening and closing.
After short usage with screen up or after long downtime (like when I go to sleep) I'm not able to use sensor at all. I cannot shut down the alarm clock, I cannot answer the calls. I still can use the power button tho.
Now what is the most retarded is that nearly all that vanishes after phone reboot. The only thing that remains is that top side of the screen is still quite difficult to control. For example I cannot open that top slide-bar comfortably. I have to slowly move my finger over the screen in order to do so.
Phone specifications:
Custom ROM: Cyanogen 11-20140702-nightly
sdcard partition type: FAT32
bootloader version: 2.14
Security-OFF
CID: 11111
Custom recovery: TWRP 2.7.0.8
P.S.: tried to re-insall ROM did not help. Phone havent been damaged by any means recently.
Did u over or under clock..flash a mod to control kernel? That's what it sounds like
I'm assuming you're using the stock kernel? What you're describing is an ongoing issue with the CM kernel, flash a custom kernel (Torched or Bubba) and your problem should cease.
Sent from my Evita
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Look under Tims sig
marknoll said:
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Click to expand...
Click to collapse
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
SoulSurvivors said:
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Click to expand...
Click to collapse
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
timmaaa said:
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
You can try flashing a different ROM, or rolling back to the last build of CM that you remember being ok.
Sent from my Evita
SoulSurvivors said:
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
Click to expand...
Click to collapse
Maybe reflashing the ROM and the kernel would be a good idea. I've had to do that too. Its annoying,but sometimes I had to do that. Good luck.
Nop..
I've done the factory reset. Installer fresh ROM, Gapps and kernel.
Same ****. I Guess That is indeed hardware damage to sensor.
/sadpanda
There's a way to diagnose it. Download an app called sensor on play store
Related
When I try to type on landscape mode the "t" will not respond when touching. Could this be an issue with a Rom or screen?
I had mine do that with the backspace button, i flashed another rom and the problem went away, not saying that this your problem just a thought...
Bamatide2007 said:
I had mine do that with the backspace button, i flashed another rom and the problem went away, not saying that this your problem just a thought...
Click to expand...
Click to collapse
Thanks. I'm on coredroid 7 right now. I may try another Rom to see if it goes away.
Though I haven't experienced this personally, thankfully, this sounds like the "unresponsive keyboard" problem experienced by others across several different roms.
Most people tend to automatically assume the ROM they are running at that moment is responsible, when in actuality, it just happens to be the first time the problem surfaced for them.
It is suspected to be a bug in the touchscreen driver for the phone itself, not ROM-specific.
If we're talking about the same thing...
I believe Scott_S to be correct, LeeDroid reverted the kernel to the older FroYo touchscreen drivers on his kernel a revision or so ago and since then my screen has not had any "dead spots"
So you could possible try his kernel on your ROM of choice and see if the problem goes away
Sent from my Inspire 4G using XDA Premium App
I have had this happen on random letters with completely random ROMs. A reboot usually fixes the problem for me. Sometimes just opening and closing the app I am using will correct it as well.
Whatever wad going on has stopped. My guess is the kernel too. For some reason my phone doesn't like the leedroid kernel.
Hi folks, running CM7 with Faux's kernel and the entire front of the phone becomes unresponsive at times, seemingly randomly. Side buttons still work, turning the screen off and then back on fixes the issues. Capacitive buttons stop responding too.
Is there any reason for this to happen? It seems to occur on every nightly I've ever used, and I believe on several kernels.
Updated with logcat taken from right after I turned the screen back on.
Old bump, but still looking for help on this matter.
I've narrowed it down to being a hardware issue. Before cutting out, the touchscreen will often make seemingly random presses (hitting random keys onscreen, for example) for a second, and then crap out.
Applying higher than comfortable force to the top third of the screen restores touch temporarily, but hitting the power button on and off is the only way to reliably fix it (if only for a minute or 2). I'm ready to shell out $40 for a new digitizer, but can anyone else suggest what might be up or alternate methods of fixing it?
If it's still under warranty then try to get a warranty replacement.
Волк said:
If it's still under warranty then try to get a warranty replacement.
Click to expand...
Click to collapse
Alas, I'm using a T-Mobile USA phone in Canada, so no warranty for me.
What are your frequency settings via setcpu? Maybe your min to max is too high of a jump causing instability.
dylyxcore said:
What are your frequency settings via setcpu? Maybe your min to max is too high of a jump causing instability.
Click to expand...
Click to collapse
816 - 216 on Faux's kernel. Happens on stock and UV.
I still think it's the touch module itself since physically squeezing the phone gets a response.
Sent from my LG-P999 using XDA App
Bring it up to 389(or 4-whatever, whatever's next) and see how that works.
Or try another kernel?
Although I'm sure these were things you've tried. I give basic possible solutions.
SefEXE said:
Bring it up to 389(or 4-whatever, whatever's next) and see how that works.
Or try another kernel?
Although I'm sure these were things you've tried. I give basic possible solutions.
Click to expand...
Click to collapse
Thanks, but I've already covered those bases :-(
Sent from my LG-P999 using XDA App
You need a new digitizer. Mine would do something similar. After replacing it, everything worked fine.
buru898 said:
You need a new digitizer. Mine would do something similar. After replacing it, everything worked fine.
Click to expand...
Click to collapse
Thank you. Will this do the job?
As the title suggests, I have a Nexus S i9023 (no root, perfectly clean) and the major problem is that i've upgrade the phone to ICS manually and now there are some things that don't work (recovery, light sensor, etc.). I know that there are a lot of threads like this, i know that the problem of the recovery is a problem of brightness, but i wanna know which ROM i've to flash. I'm using the build IML74K.
Another problem is that sometimes the keyboard freezes. Is it caused by the wrong build?
Which rom did you flash?
Try lastest version of ics
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
alfax21 said:
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am using the same on my i9023 with no issues, only difference is I am rooted and have clockwork recovery. I suggest a re flash.
I'll try to re-flash the same ROM. If it won't work i'll root the phone and i'll flash CM9.
Anyway, how can i solve the problem of the keyboard? I don't think it's a problem of the build.
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
alfax21 said:
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
Click to expand...
Click to collapse
Only thing I can suggest is installing clockwork recovery, rooting etc and flashing another rom to see if the problem persists, if so then it probably a hardware issue.
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Ok maybe there's no solution (i'm new in this forum so i can't post link as the one below):
code.google.com/p/android/issues/detail?id=23065&can=1&q=ics%20nexus%20s%20i9023%20recovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
So I think it will be fixed in the next release. I ask confirmation if someone knows something.
CONTACTMC said:
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Click to expand...
Click to collapse
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
alfax21 said:
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
Click to expand...
Click to collapse
Yeah that's the one, flash the full rom package. You may just have a corrupt .zip.
Alredy done two times, but the problem remains. Mmmh i don't think it's a corruption problem, i mean, i've tried to put the update in the phone from two PC.
Sent from my Nexus S using XDA App
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Harbb said:
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Click to expand...
Click to collapse
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
alfax21 said:
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
Click to expand...
Click to collapse
Mine doesn't remain open though,. It just stays for say half a second, then animates away. Would be much more perfected if it went away while animating the previous window away, not a second later. I've not experienced the keyboard causing those kind of problems.
Might be wise to try SwiftKey or some other kind of keyboard alternative? That is easily enough to sway me away from stock.
Harbb said:
That is easily enough to sway me away from stock.
Click to expand...
Click to collapse
I agree. I'll wait for an Experimental Mod of CM9, then i'll root the phone.
Ok i'll make the thread as solved. I want to thanks Harbb for his help, i quote his post for those who will read this thread.
Harbb said:
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Click to expand...
Click to collapse
If you have problems (like the recovery one and the light sensor) with ICS 4.0.3, build IML74K, on your Nexus S i9023 there's nothing you can do, probably Google will fix it on his next update 4.0.5.
I'll just add that many custom ROMs allow light sensor manipulation. I hear there are great, working settings, its just the stock calibration that sucks. I've not tried this myself, but should be available in cm9, cna, etc.
..
Election Day said:
This is how I have my i9023 set up. These settings work very well, so feel free to use them.
Click to expand...
Click to collapse
Are these settings of the stock ROM?
..
hi everyone - not a new issue, but seems like most ppls phone has this figured out now after 44s.
Getting ghost touches and very slow/laggy scroll/swipe response...basically have to press and drag the finger to get anything working.
Currently running stock CM11s 44s with a locked bootloader, completely flashed back to stock using the zip file from cyanogens website. but i have tried CM, Omni, paranoid, and have tried diff kernels including franco, but it doesnt seem to wanna work.
here is a link to my screencast - kinda hard to see but i tried to record what happns when i imitate typing.
https://drive.google.com/file/d/0B1quWiDbFcajdkdTaGhwZzc4M1k/view?usp=sharing
any help would be appreciated! i have seen other posts on this, but nothing seems to be working! what am i missing!?!? :crying:
I have seen other people complain about this and it seems to be a bug, there is no fix at the moment. Wipe the screen clean with a microfiber/lint free cloth while the phone is off. If you think it's hardware damage then use your warranty and send it in.
hmm. I have contacted one plus and have submitted a ticket a while ago, but they are extremely slow in responding. its been over 20days now. Since the touchscreen works fine for the first 15 20mins, i thought it would be a software issue that i could somehow fix....
There will be a new Touchscreen firmware soon
nice!! where did u hear/read this? any ideas when?
hassan3216 said:
nice!! where did u hear/read this? any ideas when?
Click to expand...
Click to collapse
it's a known problem. I have it too. I don't think a firmware update is going to fix it.
http://gadgets.ndtv.com/mobiles/new...defect-affecting-touchscreen-digitiser-625211
https://forums.oneplus.net/threads/touch-screen-issues-were-listening.186829/
Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.
Nikouy said:
Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.
Click to expand...
Click to collapse
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.
You_got_owned123 said:
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.
Click to expand...
Click to collapse
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Happy to know I am not the only one having this issue , good that we are on the same boat.
I'm travelling in a few days and can't go abroad with the phone in this "working" conditions so I will have to downgrade for sure. Any 5.0 ROM to recommend? A solution for 5.1 would be better
haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!
guih said:
haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!
Click to expand...
Click to collapse
I flashed Slim ROM, touches delay improved a bit but I was experiencing some lag on the hardware keys.
I just flashed last bacon firmware (from April 09) and RobbieL811 ROM and seems to be running smoothly, I wonder if it was a firmware issue. Thoughts?
Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..
Infinityyy said:
Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..
Click to expand...
Click to collapse
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?
gsmyth said:
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?
Click to expand...
Click to collapse
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.
guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Infinityyy said:
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.
Click to expand...
Click to collapse
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.
Nikouy said:
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.
Click to expand...
Click to collapse
we're not alone man, multiple threads are popping up with people suffering from similar issues, including on reddit: http://www.reddit.com/r/oneplus/comments/33ky0u/open_post_to_oneplus_with_all_our_love_and/
I am having the same severe issues as well.
The nightmare begun after the 05Q update.
Ever since that update, no matter what I've tried, the touch problem is here.
I've tried numerous Roms + kernels combinations with no use.
OP support was trying twice to reset my phone to full factory reset to both Oxygen & CM11s with no use.
That is so frustrating.
i have the same problem, but only when i go outside and the weather is nice