Hi everyone,
I was up to ICS Rom yesterday, but everytime i unlock screen, i cant touch in the bottom of the screen, cant typing with h, g, j and somewhere around it, but on the right, left or top screen i can still use normal. Does anyone know what happen and how to fix it?
When im in CM7 Rom is was fine and has no problem
PS: Sr for my bad english i really not good in grammar.
Same problem but different area
I have the same issue.
On Apex i had no issues but when i upgraded to SlimICS 3.2. The right side of the screen ocasionally becomes unresponsive.
That is, on any keyboard from approximately the 'i' to backspace horizontally, and from enter to the top of the screen.
This whole zone randomly decides not to work. the only fix is to turn the screen off and then turn the screen on again, or backing out of the application and reloading it. The application can be anything, chrome browser, swiftkey, messages, whatsapp.
Does anyone know what the issue could be?
I'm running slimics3.2 with semaphore ics 1.0
I'm also running slim 3.2 and had the same issue with the sephamore kernal. I just reflashec the essentials and everything worked perfectly for me.
Sent from my SGH-I897 using XDA
I used the essentials kernel first and experienced the issue, i thought it was a kernel issue so I flashed semaphore afterwards. But I still have the issue...
arse87zx said:
I'm also running slim 3.2 and had the same issue with the sephamore kernal. I just reflashec the essentials and everything worked perfectly for me.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I tryed AOKP 3.0 and didn't modify anything, also some another ROM but it still have a problem with the touchscreen
KunNuK said:
Hi everyone,
I was up to ICS Rom yesterday, but everytime i unlock screen, i cant touch in the bottom of the screen, cant typing with h, g, j and somewhere around it, but on the right, left or top screen i can still use normal. Does anyone know what happen and how to fix it?
When im in CM7 Rom is was fine and has no problem
PS: Sr for my bad english i really not good in grammar.
Click to expand...
Click to collapse
I hate to say this, but its probably the fact the phone does not like ICS, it is more than likely some sort of hardware incompatibility issue.
I went through this exact same thing, it was on a 1009 or so build number captivate, no matter what flavor of ICS, none of them would work properly with the touchscreen hardware, there was always a spot of the screen, at the lower center 1/4 portion of the screen, that was unresponsive. Flashing a Froyo or Gingerbread rom, the touchscreen was perfect.
So.. I sold that Captivate, purchaced a refurb Captivate off Ebay, and touchscreen is perfect with ICS (CM9 is what I run).
Wish I had something more helpful, but that's my experience. Good luck with it.
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
Hello guys,
I've been testing all lolipop roms that had listed everything as working. Such as crDroid, CandyRom, SlimLP. On every of those lolipop roms pretty much most of the important stuff worked. There were stuff like equalizer not working or too dim notification LED, but from time to time I got touchscreen freezes. I mean I could use phone for a couple hours and then the touchscreen would freeze really often, sometimes it froze for couple of seconds and that was it and sometimes it could last for 10 minutes. This is really annoying and unacceptable if developer says that the touchscreen works.
I ended up contacting crDroid developer - davidteri81 and he said that the touchscreen works fine for him. I asked in the thread and I got only a single response saying he doesn't have this issue, but the sensivity is too high.
I've tried like literally 4 lolipop roms on my Z1 and each one of them had those touchscreen freezes. I even ended up flashing liquidsmooth in which I didn't had this issue, or it just didnt had the chance to happen since most stuff doesn't work there and it isn't usable as a daily driver so I quickly got rid of it.
My question here is:
Do you get touchscreen freezes? Please reply only after minimum 24h of usage. If you don't have any touchscreen freezes on lolipop rom on the Z1 then please, tell me what Lolipop rom do you use as I couldn't find any that wouldn't have a buggy touchscreen.
Please tell me if it works for you without issues or do you also have this issue on the Z1 as I'm puzzled because it couldn't be just me since I did a full phone wipe, flashed the phone clean, even wiping internal memory, but it still happens and I cant find a way to use any Lolipop rom everyday on my Z1. The more replies I get, the better.
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
schickel said:
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
Click to expand...
Click to collapse
Same for me, although, the touch screen did freeze once, but I locked it and unlocked it and it worked again. It's probably hardware since I got my Z1 replaced because of this issue that even happened on stock ROM occasionally.
using CandyRom 5.0.2
I never faced any touch freezes issue
@olokos: I'm on 20150214 and now I've got touchscreen freezes. This is the first time for me on Z1.
But I think that this could be a global Cm12 issue, because my Nexus 7 also get some freezes and I thought that something is wrong with my fingers or tempered glass.
The problem is how to debug this?
im on candy 5 and my screen dont freeze, but my screen percieves touches from nowhere... but only if i have earphone plugged in .. thats more than just annoying
anyone has the same prob?
sry for my really bad english
Touchscreen freezing issue definitely isn't hardware issue on custom roms. I haven't tried CM12 or any other apart from those listed on XDA, but I will propably build some lolipop rom from source by myself if I get enough reports that will be useful for me. If touchscreen works for you then please, tell me what rom you are using and for how long you use it, what't the way you flashed it.
I only need those 3 things. If touchscreen doesn't work just for me then I'll build my own stock based rom based on Sony sources. I just have to make sure that the touchscreen issue isn't just on my side.
All I need is:
Do you have touchscreen issues? Yes/no
What ROM/Kernel you are using? CandyRom 5.0
For how long? 5 weeks
Answer those 3 questions, legitimately and I'll consider that. I'm not sure If I'll have enough time to work on this, so please, be honest with your answers because I'm not going to fix the touchscreen, or maybe I will if it doesn't happen for everyone.
I experience dramatic touch screen freezes as well since the first time I installed Lollipop nightlies. (4 weeks now). Tried clearing cache, factory restores, de- and reinstalling apps. Reflash kernel, format SD, reinstalling gapps, puzzeling at logcat logs etc. Nothing helps. Random freezes from seconds till minutes. Only thing that 90% of the time will help is keep pressing powerbutton until screen becomes responsive. It happens more when I have a lot of (hangout or whatsapp) notifications, or when trying to type something (stock keyboard). Tried other keyboards: no luck. Tried every toggle: WiFi , Bluetooth etc. : no luck.
I experience dozens of freezes a day. Almost to the point that cm12 is completely unusable. Love this ROM, but this is a real showstopper.
1. No
2. AOSP Vanir 5.02
3. Since first availibility (12/14)
I experienced this issue on 2 roms in 2 forms
1. No (coming from Stock 14.4.A.0.108)
2. KitSlim_AMG [Evo 8.1] / iHackers advanced Stock Kernel
3. Since installing the Rom
This was the first time i experienced touch-issues. Not a freeze of the screen, but the screen sometimes started registering touch-events on the wrong places. This was temporarly fixed by locking/unlocking the display.
1. Yes (coming from KitSlim_AMG [Evo 8.1] )
2. crDroid-5.0.2-20150303-honami / 3.4.0-crDroid (packaged with rom)
3. Since installing the Rom a day ago
This time i get freezes. And they are much more frequent than those "ghost-inputs" from KitSlim_AMG. Unlocking the device also fixes it temporarly.
Hello, I ran into some problems when i tried to flash TWRP 3.02 with Odin 3.10.7. The touch screen is not registering the correct touch location. The touch is registering to be lower and the the right of the actual touch. It's off by more the lower and further right to the screen it is touched. (It was a real pain to get past the lockscreen before "show touch" from developer option was enabled) I'm running the June 19 CM 12.1 nightly with DOK2 baseband. Much appreciated if someone can tell me how I may fix this. Thanks in advance!
somewhere on this site is the answer to your problem I had to calibrate the screen....all i can recall at the moment is using the s pen which oddly enough works just fine but its a known issue with a fix so dont worry too much
http://forum.xda-developers.com/showthread.php?t=2144166
Thank you so much! Finally typing now! I'll try calibration tonight.