I rooted my galaxy s3 when I got it. sometimes the screen turns on and it is unresponsive to touch. As soon as I turn the screen off and back on with the lock button then it works fine. It does it randomly, for instance when somebody calls I can't answer it sometimes I have to hurry up and turn the screen off and back on so I can swipe to answer. Also when I'm playing a game like hill climb racing it works then after a minute it stops responding completely until I lock and unlock the screen. Everything was working fine until I rooted it. That is my only issue. Any suggestions? Thanks
Are you using a custom recovery? Wipe cache / dalvik cache? Are you using a custom rom that modifies the touch responsiveness / better accuracy when
pressing? Or better yet using a utility that changes governor settings of your phones CPU?
I have the same issue but it was only linked with governor CPU settings and UV OV / OC'ing the device.
Spark91 said:
Are you using a custom recovery? Wipe cache / dalvik cache? Are you using a custom rom that modifies the touch responsiveness / better accuracy when
pressing? Or better yet using a utility that changes governor settings of your phones CPU?
I have the same issue but it was only linked with governor CPU settings and UV OV / OC'ing the device.
Click to expand...
Click to collapse
No i am rooted only no rom or custom recovery just went back to stock and updated to 4.1.2 and re rooted and it still does the same thing.
It does it on stock rooted? Sounds like a hardware issue, especially since you unrooted and then rerooted and it still persists
Get an app that traces screen touch points to verify that the phone isnt detecting it at all
bump
CNexus said:
It does it on stock rooted? Sounds like a hardware issue, especially since you unrooted and then rerooted and it still persists
Get an app that traces screen touch points to verify that the phone isnt detecting it at all
Click to expand...
Click to collapse
Ok I turned the developer option on to track touchs and sure enough when the screen touch "freezes" it is still responsive to touch it's just way off. And even though it is way off I can get it right about where I originally am trying to touch, and it still does respond. Also when it freezes, there are two touch spots and they are way off of where I am touching..! Any Ideas???
I am having an issue on 4.1.2 TW; has happened on both TPR and JellyBomb... when phone boots or I wake it up with home or power button, lockscreen is in landscape mode and unresponsive to touch. Have to pull battery and wipe cache/Dalvik. Is this just from multiview?
Using CWM with KT Kernel (it has happened on various KT builds, including 14MAR, 27MAR and 11APR).
Anyone know what's causing this?
EDIT: well, as usual, a quick PM to Kennyglass123 has solved the issue! I forgot to uncheck the "ripple effect" and I'm using AOSP lockscreen. Nothing like feeling like a schmuck to start your weekend!
Mucho thanks to Kenny, as per usual...
Related
I've been having this problem lately since I re-flashed the stock rom on my G2, whenever I press my lock button, sometimes the 4 capacitive buttons at the bottom turn on, but my screen remains black. When I press the lock button again, the screen will flash on and off as if it was on the whole time and the lock button locked it. I usually just have to spam the lock button a few times until it turns on correctly, is anybody else having this problem?
Also, I'm able to press on the unlocking button on the screen and drag it to the other side and I'll have all of the haptic feedback and swipe to different homescreens, I just can't see anything on the screen.
I came from one of the thrown together Desire Z roms and I flashed paul's stock rom, the one with superuser preloaded. I also flashed Cyanogen's addon shortly after the rom. I'm looking for a solution that doesn't require any factory resets, thanks for the help.
Bump
Help please, it's getting worse
Sent from my T-Mobile G2 using XDA App
You aren't the only one with this problem. Are you running an overclocked kernel? It seems like when I run an overclocked kernel I get this problem and when I'm running stock, I don't
Did u flashed back to stock kernel?
How would I flash back to stock kernel? Would I just re flash the stock rom?
Sent from my T-Mobile G2 using XDA App
Flippy125 said:
You aren't the only one with this problem. Are you running an overclocked kernel? It seems like when I run an overclocked kernel I get this problem and when I'm running stock, I don't
Click to expand...
Click to collapse
same problem with mine, i think it has something to do with the kernel. many people reported watching youtube videos or having youtube open in the back also caused the same problem
i rooted my htc evo GB and flashed cm7. had all kinds of problems with the touch screen and keyboard. the pull down bar for notifications is still not working. i have since flashed myn's warm 2.2. everything works fine except the pull down bar still wont work.
any thoughts? your help is greatly appreciated.
Possible touch screen failure for that part of the screen.
Try returning to stock and see if you still have the issue.
I've seen this problem talked about a few times before so it's definitely possible.
Turn on auto-rotate if it's off, rotate the screen, then try to pull down the notifications. If it'll work that way, it's your screen.
I really can't think of anything else that it could be. If you need a temporary solution, you can use auto-rotate to open your notifications or put the status bar at the bottom if you're on CM7.
You'll need to unroot & take it to Sprint or try to fix it yourself.
Sent from my PC36100 using Tapatalk
the pull down does work when screen rotates. i should clarify that i am currently using the myn's warm twopointtwo mod right now.
My first thought is did you do a thorough and proper wipe before you flashed the ROM?
trappedndroid said:
the pull down does work when screen rotates. i should clarify that i am currently using the myn's warm twopointtwo mod right now.
Click to expand...
Click to collapse
Every so often the top half of my screen will become completely unresponsive. I either wait about 5 mins, or do a hot restart, and it starts working again.
Edit: It has been doing it with every rom, Eclair, froyo, and gingerbread. It could be an overheating issue, or the hardware could be starting it's descent.
if i'm reading right a fresh wipe is wiping the user data and delvik right?
trappedndroid said:
if i'm reading right a fresh wipe is wiping the user data and delvik right?
Click to expand...
Click to collapse
Data/Cache/Dalvik
I would recommend doing each 3x just to be sure.
Elw00d said:
Data/Cache/Dalvik
Click to expand...
Click to collapse
I would include /system /boot as well for good measure.
android.secure and sd-ext [if it's used] as well.
if the "stupid person of the year" is still up for grabs i'll take it. you see, i often get drunk and wake up with my phone acting all funny. this problem had nothing to do with hardware, firmware, or software. it happened bcuz i changed the swipe settings!
i'll take that award now
sorry xda!
How do you change the swipe settings..?
Deck's + SZ + SuperCharger script + ViperMod script.
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.
I'm still relatively new to rooting, so please forgive my lack of knowledge of terminology and such. I decided to give MIUI a try and flashed it on my phone. It was buggy, but not anything too crazy. Two nights ago, I flashed the newest update for it and ever since, the vibration when I touched the soft keys and when I entered my unlock pattern has gotten significantly weak. I went into the settings and changed the vibration level to strong but it did nothing. It was really bothering me, so I did a data wipe and flashed the latest build of AOKP. The vibration is still weak when I touch the soft keys and unlock pattern. I also have the stock ICS lock screen set up too, but when I slide the ring to unlock the phone, the vibration is normal again. I went into the device settings and changed the vibrations settings, but that didn't do anything either. I did a data wipe, wiped the dalvik cache, formatted the system and reinstalled the ROM, yet it's still the same. Is there a way to fix this? Sorry for being so long winded, I hope it made sense lol Thank you for any help
Did you drop the phone or cause any other physical damage to the phone? Because any control over the vibration would be reset after installing a new rom/wiping data.
Sent from my Galaxy Nexus using Tapatalk 2
AyyEmBee said:
I'm still relatively new to rooting, so please forgive my lack of knowledge of terminology and such. I decided to give MIUI a try and flashed it on my phone. It was buggy, but not anything too crazy. Two nights ago, I flashed the newest update for it and ever since, the vibration when I touched the soft keys and when I entered my unlock pattern has gotten significantly weak. I went into the settings and changed the vibration level to strong but it did nothing. It was really bothering me, so I did a data wipe and flashed the latest build of AOKP. The vibration is still weak when I touch the soft keys and unlock pattern. I also have the stock ICS lock screen set up too, but when I slide the ring to unlock the phone, the vibration is normal again. I went into the device settings and changed the vibrations settings, but that didn't do anything either. I did a data wipe, wiped the dalvik cache, formatted the system and reinstalled the ROM, yet it's still the same. Is there a way to fix this? Sorry for being so long winded, I hope it made sense lol Thank you for any help
Click to expand...
Click to collapse
Probably because of the kernel. That's my best guess. Flash trinity kernel and see how the vibration is for that one.
did you flash miui.us or miuiandroid? have you tried to flash any different roms since this issue started to see if its a rom issue or hardware issue?
theking_13 said:
Did you drop the phone or cause any other physical damage to the phone? Because any control over the vibration would be reset after installing a new rom/wiping data.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I didn't drop the phone. Held it in my hand the whole time I flashed MIUI
sd0070 said:
did you flash miui.us or miuiandroid? have you tried to flash any different roms since this issue started to see if its a rom issue or hardware issue?
Click to expand...
Click to collapse
I flashed miui.us, but I thought the faint vibration was a result of the miui update so I wiped and flashed AOKP 39. I still have the faint vibration when I touch the soft keys or enter my unlock pattern. However, for everything else it vibrates normal.
If you haven't dropped your phone, then probably it's the kernel. Haptic Feedback sometimes lessens on certain kernels. Try flashing another one.
I flashed Trinity kernel with 1536MHz CPU And 512MHz GPU clock. I wasn't sure which one to pick so I just chose the one at the top of the list. Anyway, since doing so I can't change any settings under the device options, except for 'color hack presets' Everything else is grayed out and I can't select them. Is there something I missed or should've done? I didn't wipe data or the dalvik cache, because I read that it wasn't necessary.
I think Trinity is not compatible with MIUI, which follows CM team very closely.
Sent from my i9250
bk201doesntexist said:
I think Trinity is not compatible with MIUI, which follows CM team very closely.
Sent from my i9250
Click to expand...
Click to collapse
I couldn't deal with MIUI anymore, so I flashed aokp b39.
I've had this issue for quite a while now.. at first I figured it was just a bug as my screen would no longer rotate but I've flashed and tried several different roms (Probam jelly bean, KitKat, and now on Temasek V28 KitKat) and have tried a few different Kernels such as Devil 2.3.2 and currently using the stock Temasek kernel.
I've downloaded some sensor apps and they list my sensors, but whenever I go to test them such as the accelerom3534, gyroscope, compass.. they don't work at all.. They just say "waiting for data"
The Proximity sensor still appears to be working though.
Anyone had this issue? My phone I don't think is damaged.. I've dropped it on some small falls in the past but it's been in a nice cover as well.
Small update:
Went back to a rooted stock 4.1.2 AT&T ROM, stock kernel, stock modem.. no change. Must be the hardware being broken
epix1718 said:
Small update:
Went back to a rooted stock 4.1.2 AT&T ROM, stock kernel, stock modem.. no change. Must be the hardware being broken
Click to expand...
Click to collapse
Is it your home screen that doesn't rotate or will no apps work.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
ShrekOpher said:
Is it your home screen that doesn't rotate or will no apps work.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
None of the apps will rotate, or say a picture in "gallery". Home screen I know was never designed to rotate.
Also just tried the 1-Click ODIN restore to unrooted stock rom, no difference Screen still does not rotate in any apps.
Sounding like a hardware issue...
Sorry to hear that ...g
epix1718 said:
None of the apps will rotate, or say a picture in "gallery". Home screen I know was never designed to rotate.
Also just tried the 1-Click ODIN restore to unrooted stock rom, no difference Screen still does not rotate in any apps.
Click to expand...
Click to collapse
the only other option I can suggest is to check and make sure all of your settings that effect screen rotation of cleared. Make sure you don't have smart stay on and you have screen rotation enabled in your settings. You may also want to turn them on if they are off and reboot your phone. Then turn them back off and reboot your phone again. If that doesn't fix it I would assume its a hardware issue.
Did you drop your phone recently or get it wet or damp. That's the only thing I have heard can cause the hardware issue.
bringing this thread back to life sense I couldn't do the same for my sensors
Hello there! So I have had a similar experience with the Note 2. It is not hardware related as far as I can determine because I swapped out the prox sensor on mine and it did not help. I feel that it is kernel related. On my previous Note 2, I flashed some kernel, prox sensor stopped working. I flashed back to stock AT&T and it worked for one call before quitting again. That's when I tried a new sensor and camera unit. The phone was under warranty so I triangled away and traded it. With the current Note 2, I flashed Sky note 9.3 and then after a while the prox sensor stopped working, I just thought okay with whatever maybe it's the kernel I'm using. I wanted to upgrade to Sky note Air, so I did. Got all settled in and decided to see if their provided kernel fixed my call sensor, no cigar. So I went into *#0*# and realized that none of my sensors were working. Tried using Devil Kernel, stock, stock ROM, all sorts of configurations and I can't revive any of them. Feeling very defeated.