The touchscreen does not work after the lock screen, if you restart the phone, the sensor starts to work again, but once again no longer lock. I tried a lot of firmware, such as android n and m stock, aospa, pure nexus. The problem is solved, if you put a custom kernel, but if you disable the settings core gestures (for example wake2sleep on elementalx kernel), then the problem returns. Sensor itself works well, but before the block a screen. What to do? I can not understand what the problem is. I think is not a hardware problem, because touchscreen working nice.
Android touchscreen doesn't work on twrp recovery(any version)
I don't understand what the problem is either. Can you please try explaining it again?
dahawthorne said:
I don't understand what the problem is either. Can you please try explaining it again?
Click to expand...
Click to collapse
Touch screen dont work, if i lock the screen after rebooting (by power button). If i rebooting phone, touch will work, but if i again lock phone by power button, touch screen again dont work. This problem in all roms, and if i flash custom kernel, problem disappears. Sorry for my english.
Related
Hey guys,
a friend of mine gave me his Optimus Black. Someone installed a bricked rom on it.
It has some absolutely strange behaviour, cause the Screen doesnt respond in any logical reason.
Sometimes i manage to unlock the screen, but i cant do anything cause the 'hardware'-buttons are not recognized either.
Due to non responsive hardware buttons, i'm unable to enter any kind of recovery...
Volume control does work.
Is there any way i could possibly do sth about this problem?
Will post Screenshots or Video of the Rom later.
Thanks in Advance
Hi, maybe you can use SmartFlash tool and flash a rooted gingerbread rom with a recovery and from there, do a complete wipe then flash a new custom rom. You can refer to http://forum.xda-developers.com/showthread.php?t=1111771. Hope it helps.
Are you sure that the power button is working?
Try to push the battery cover next to the camera flash and press the power button at the same time.
If it works then its a hardware problem .
Seems like it is a Problem with The Touchscreen. Someone changed it and did something wrong, tgread can be closed
Sent from my XT925 using xda app-developers app
Hi all, i have a BIG problem. Straight to the point, first of all, this problem exists in 4 ROMS that i had (its impossible but somehow) I had existenZ, existenZ black, Hashuan and Liquid 3.0 (4.4.2). The problem begins, when i try to call somebody, then my screen is turning off and it doesnt recover, i MUST w8 after someone will hung up and then after 3 minutes everythings back to normal. This happens only when i try to call somebody. I flashed nyaka kernel, dooslord kernel and nothing really works...somebody please help.
Whats could be the reason i will try to change something.
Any ideas?
Thanks for helping
styku468 said:
Hi all, i have a BIG problem. Straight to the point, first of all, this problem exists in 4 ROMS that i had (its impossible but somehow) I had existenZ, existenZ black, Hashuan and Liquid 3.0 (4.4.2). The problem begins, when i try to call somebody, then my screen is turning off and it doesnt recover, i MUST w8 after someone will hung up and then after 3 minutes everythings back to normal. This happens only when i try to call somebody. I flashed nyaka kernel, dooslord kernel and nothing really works...somebody please help.
Whats could be the reason i will try to change something.
Any ideas?
Thanks for helping
Click to expand...
Click to collapse
Dial *#*#7378423#*#* and go to service test menu.
There u'll find "proximity switch" option... Test it,if it is working.
One more thing u can do is flashing stock firmware...
Recently i put cm11 on my i9000 and now the screen is constantly turning on. As soon as the screen lock is turned on, the phone wakes again.
Sometimes this happens indefinitely and sometimes it only happens once then the screen will sleep after a second press of the lock/power button.
The only consistent thing appears to be that when the lock screen is unlocked the recent apps are always shown.
I've tried formatting/wiping and different night lies and the m4 snapshot but it all happens exactly the same.
Any help would be greatly appreciated.
use this and see if it's the rom or an app that's keeping the phone awake http://forum.xda-developers.com/showthread.php?t=2179651
pryerlee said:
use this and see if it's the rom or an app that's keeping the phone awake http://forum.xda-developers.com/showthread.php?t=2179651
Click to expand...
Click to collapse
Thanks, I've installed this earlier today and I don't quote understand it.
According to wake lock detector, under screen wake lock, running and usage, phone - system (radio) is number one.
Does this mean it's the rom keeping the phone awake?
Not sure how wakelock works to be honest but I don't think it's the rom that's the problem, it sounds like its the radio (modem) try flashing a different baseband for your region and see if that fixes the problem? http://forum.xda-developers.com/showthread.php?t=1870460 http://forum.xda-developers.com/showthread.php?t=1158783
pryerlee said:
Not sure how wakelock works to be honest but I don't think it's the rom that's the problem, it sounds like its the radio (modem) try flashing a different baseband for your region and see if that fixes the problem? http://forum.xda-developers.com/showthread.php?t=1870460 http://forum.xda-developers.com/showthread.php?t=1158783
Click to expand...
Click to collapse
Tried several different radios without any success I'm afraid.
Just tried flashing stock JVU rom and then back to CM11 without any success. Exactly the same issue.
Oddly, if you hold the home key whilst pressing the lock key, the screen turns off and stays off for a while, then wakes after a minute or so again.
New Method
Try going into settings>Applications (or Apps)> Running and check which application(s) is taking up the most memory, it may be that a application from an unknown source is waking up the device, like a virus or your phone is consuming too much RAM. If this is the case try and delete it or run a security scan from the play store such as BitDefender.
Another option is to run a more stable version of CyanogenMod instead of a Nightly, I had problems with Nightly builds and changed back to a stable build. Try the new 4.4 snapshot of CyanogenMod, it is more stable. DOWNLOAD from the official cyanogenmod website, don't update using the option in settings as it always sends my phone into a boot loop. Hope it helps
Try another ROM
Let me know if switching to another ROM helps. I'd suggest Paranoid Android or OmniROM.
The thanks button is right there! just saying...
Gokulbalram said:
Let me know if switching to another ROM helps. I'd suggest Paranoid Android or OmniROM.
The thanks button is right there! just saying...
Click to expand...
Click to collapse
No luck unfortunately, I think I've narrowed it down, and the menu button keeps activating itself.
kcajjones said:
No luck unfortunately, I think I've narrowed it down, and the menu button keeps activating itself.
Click to expand...
Click to collapse
Try Flashing Stock.
Gokulbalram said:
Try Flashing Stock.
Click to expand...
Click to collapse
Stock is doing exactly the same thing
kcajjones said:
Stock is doing exactly the same thing
Click to expand...
Click to collapse
Have you erased each and everything? /data and stuff? also, just see if Touchwake is enabled by any chance
I don't mean to drag this old thread back up, but I've come to use my i9000 again as a backup device and it still has this same problem.
Is there anyway I can prove that it's a button that's faulty (for instance)?
I thought maybe a logger that would show if it detected/logged the home button being pressed when I notice the screen turning itself on, but I can't find such an app.
Hi all,
So I have an S3 i9305 sitting around doing nothing. Thought I'd play with it. I had and older build of Miui running on it fine.
Decided to put on CM11, and that's when my issues started. The phone boots, but as soon as I get to any sort of setup screen I can touch anything on the screen. The physical buttons work fine, but the screen isnt.
I flashed a touch CWM and TWRP, both of which loaded fine by I couldnt touch anything.
I flashed back to stock kernel and stock rom
Kernel from - http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265
ROM from - http://forum.xda-developers.com/gal...5/roms-updated-17-08-2013-pre-rooted-t1942150
Still unresponsive touch.
Anything else I can try before I write this off as bricked
Thanks!
pieinthesky10 said:
Hi all,
So I have an S3 i9305 sitting around doing nothing. Thought I'd play with it. I had and older build of Miui running on it fine.
Decided to put on CM11, and that's when my issues started. The phone boots, but as soon as I get to any sort of setup screen I can touch anything on the screen. The physical buttons work fine, but the screen isnt.
I flashed a touch CWM and TWRP, both of which loaded fine by I couldnt touch anything.
I flashed back to stock kernel and stock rom
Kernel from - http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265
ROM from - http://forum.xda-developers.com/gal...5/roms-updated-17-08-2013-pre-rooted-t1942150
Still unresponsive touch.
Anything else I can try before I write this off as bricked
Thanks!
Click to expand...
Click to collapse
1 more thing...get the RIGHT firmware from HERE - get the one for your country.....flash that and do a factory reset after it..and wipe cache....
happened to a friend with galaxy ace....but phone was back to normal after flashing stock firmware from samsung.
Thanks mate!
So I tried some more flashes, no luck.
Took the phone to the local repair place, they told me the screen is broken. They attached a different temp screen and it worked. They attached my screen to a different phone and it didn't work.
Quoted me $189 to replace the screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
Im sure i flashed wrong kernel.
Enviado do meu GT-I9300 através de Tapatalk
SnowPluralism said:
Im sure i flashed wrong kernel.
Enviado do meu GT-I9300 através de Tapatalk
Click to expand...
Click to collapse
Dont think so... tired a few from the SamMobile site with no success. The setup screen shows up fine - but cannot continue with the setup as I cannot touch the screen.
pieinthesky10 said:
Dont think so... tired a few from the SamMobile site with no success. The setup screen shows up fine - but cannot continue with the setup as I cannot touch the screen.
Click to expand...
Click to collapse
so it is a hardware problem....not software - you can flash whatever you like...won't solve it...
if you like the phone consider repairing it...
spiderman07 said:
so it is a hardware problem....not software - you can flash whatever you like...won't solve it...
if you like the phone consider repairing it...
Click to expand...
Click to collapse
Thanks for your help
I am having the same problem.
Even after installing new firmware.
The phone boots, screen is working. But the touch is not responding... I also did a factory reset + wipe cache.
Before that it was on CyanogenMod (4.2.2) and the screen was working properly.
What else can I do TT ?
I changed the front panel.
And it is working perfectly well...
How can modification to the software affect the hardware and brake the digitizer/touch function ?
via kernel man...kernel is the interface between software and hardware....
maybe a frequency or voltage got changed by kernel and something happened....no one can know for sure...
gidam said:
I changed the front panel.
And it is working perfectly well...
How can modification to the software affect the hardware and brake the digitizer/touch function ?
Click to expand...
Click to collapse
When wrong kernel is flashed, the touch sensor get disconnected and unrecongnised by the phone. Thats why the hardware is broken even though correct kernel is flashed afterwards. Best thing to do is replace the screen instead of trying over and over again.
Hope it helps
I use the Samsung GT 19305 LTE myself.
Hey,
I just noticed that when I'm pressing the screen with one finger, then trying to hold another finger while still holding onto the screen, there is a small delay in recognising the 2nd finger...
This only happens after 30 minutes of usage, as the multitouch works just fine for a while after powering up.
The delay is not that much, but is enough to not recognise when I'm simply tapping the screen, which makes it impossible to play games like fifa 14 properly, since I have to hold down the button for a while to have a response...
I'm currently rooted, on stock 12.1.A.1.205, on the stock kernel.
Any ideas?
Thanks in advance
Yeah I also have multitouch problem.Can't play games that require multitouch(fifa,mc5 etc)
I think it is hardware problem
Quick question dude...did you try a factory reset?
I'm thinking of trying it but I don't want to lose my data without fixing it...
Can anyone confirm that this is a hardware problem?
I have the same problem, and I'm sure isn't a hardware problem because it started when I updated the phone to the 12.1.A.1.205 version.
I also have a problem with the back key, it works for a couple of clicks and it stop working until I press the home key. This happens after the update as well, before all has working fine. It's annoying!
TLDGames said:
I have the same problem, and I'm sure isn't a hardware problem because it started when I updated the phone to the 12.1.A.1.205 version.
I also have a problem with the back key, it works for a couple of clicks and it stop working until I press the home key. This happens after the update as well, before all has working fine. It's annoying!
Click to expand...
Click to collapse
I thought I was the only one with the back key problem. The multitouch one I never tested.
This is why I moved to CM11 (also because of ThemeChooser :silly: )
Bruno_Puzoni said:
I thought I was the only one with the back key problem. The multitouch one I never tested.
This is why I moved to CM11 (also because of ThemeChooser :silly: )
Click to expand...
Click to collapse
Sorry to ask this, but, what is CM11?
CM11 is a custom ROM (basically a whole new operating system). And it's based on android 4.4.4
I used to be on CM11, it is so good, but I prefer Sony's UI.
Also, thanks for the help. Since this isn't a hardware problem I'll try a factory reset and see what happens...
LoizosAristides said:
CM11 is a custom ROM (basically a whole new operating system). And it's based on android 4.4.4
I used to be on CM11, it is so good, but I prefer Sony's UI.
Also, thanks for the help. Since this isn't a hardware problem I'll try a factory reset and see what happens...
Click to expand...
Click to collapse
I see! Thanks for the info.
Please post your results after the factory reset, I will do the same if it works for you!
LoizosAristides said:
Quick question dude...did you try a factory reset?
I'm thinking of trying it but I don't want to lose my data without fixing it...
Can anyone confirm that this is a hardware problem?
Click to expand...
Click to collapse
I don't think factory reset would work because I keep flashing different roms with complete wipe.
Apparently a factory reset didn't help...neither a firmware upgrade...
So it has to be another thing causing it....
Any other ideas?
LoizosAristides said:
Apparently a factory reset didn't help...neither a firmware upgrade...
So it has to be another thing causing it....
Any other ideas?
Click to expand...
Click to collapse
Bad news with the reset then
I had to reboot my phone in safe mode (I think this is the name in English, "modo seguro" in Spanish) and the multitouch seems that doesn't fail in this mode. So I think is some program that is loaded with a normal boot which is causing the trouble.
TLDGames said:
Bad news with the reset then
I had to reboot my phone in safe mode (I think this is the name in English, "modo seguro" in Spanish) and the multitouch seems that doesn't fail in this mode. So I think is some program that is loaded with a normal boot which is causing the trouble.
Click to expand...
Click to collapse
Yeah but when I start the phone it works just fine...It's after a while that the problem happens...
Even if I don't open an app, it's still happening...
LoizosAristides said:
Yeah but when I start the phone it works just fine...It's after a while that the problem happens...
Even if I don't open an app, it's still happening...
Click to expand...
Click to collapse
Hmm But there are programs that start automatically. I killed every process I don't use, and I'm testing if it works.
I'm fresh out of a factory reset, so I don't really have any apps installed except titanium backup and es file explorer. I also killed every app except the ones that the phone needs to work properly....still no change.
After a random amount of minutes it works fine, without doing anything...
Also a question: How did you test it in safe mode? You can't have your downloaded app on safe mode to test it..
LoizosAristides said:
I'm fresh out of a factory reset, so I don't really have any apps installed except titanium backup and es file explorer. I also killed every app except the ones that the phone needs to work properly....still no change.
After a random amount of minutes it works fine, without doing anything...
Also a question: How did you test it in safe mode? You can't have your downloaded app on safe mode to test it..
Click to expand...
Click to collapse
I'm testing with my own game, it works in safe mode
TLDGames said:
I'm testing with my own game, it works in safe mode
Click to expand...
Click to collapse
Well safe mode isn't the solution....you can't be onto safe mode for ever...
It's funny cuz the multitouch thing is actually working, but you have to hold the screen to do so not tap it. If u tap it it wont recognise ur finger
Any one got something before I actually give up on this?
LoizosAristides said:
Well safe mode isn't the solution....you can't be onto safe mode for ever...
It's funny cuz the multitouch thing is actually working, but you have to hold the screen to do so not tap it. If u tap it it wont recognise ur finger
Any one got something before I actually give up on this?
Click to expand...
Click to collapse
The weird thing is that after rebooting from the safe mode to the normal mode and kill every app in execution that I don't use, it works. The multitouch and the back key is working. I have no idea what to think.
TLDGames said:
The weird thing is that after rebooting from the safe mode to the normal mode and kill every app in execution that I don't use, it works. The multitouch and the back key is working. I have no idea what to think.
Click to expand...
Click to collapse
When I start up the phone and start a game like Shadow Fight, it works fine for me too. But when I launch another game that's where it starts to delay...
I don't know what else to do...thanks for your help man
Sad news...
After trying everything, from settings to scripts and touch boosting apps, I left my hopes on changing the ROM i use...
I had a stored backup of my 4.3 stock rom in the past. I restored it today and the problem persists...
I also flashed a fresh new build of cyanogenmod 11, which I used in the past aswell. No help...
I can now conclude that this is a hardware problem.
But what I don't understand is...why does this only happen after 30+ minutes of usage of the phone?
I mean it works perfectly fine on games when I start up the phone...
Thanks to everybody for the help...
LoizosAristides said:
After trying everything, from settings to scripts and touch boosting apps, I left my hopes on changing the ROM i use...
I had a stored backup of my 4.3 stock rom in the past. I restored it today and the problem persists...
I also flashed a fresh new build of cyanogenmod 11, which I used in the past aswell. No help...
I can now conclude that this is a hardware problem.
But what I don't understand is...why does this only happen after 30+ minutes of usage of the phone?
I mean it works perfectly fine on games when I start up the phone...
Thanks to everybody for the help...
Click to expand...
Click to collapse
Have you tried this one: http://forum.xda-developers.com/showpost.php?p=48066948&postcount=6
OOPS that's for unresponsive touch, sorry