Related
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.
Hi folks,
I'm not sure what's up with my phone. I have CM10 beta on it and since earlier today the D button on the keyboard is completely unusable. Also, I have a hard touch hitting R. I have tried touching the same area in other apps and it seems to work fine. Maybe there's a tool out there I could use to confirm this?
I had this happen before on an earlier build of CM10. When it happened before (and as of now), rebooting doesn't fix it. Last time I gave up and just upgraded my CM10 ROM, and it has been working ever since (around a month or so).
Today, the touch screen experienced some "glitches". What I mean is, I took it out to use it and it seemed like it was detecting touch/drag events in various spots, and I had to put it to sleep to get it working again.
I have no idea where to start with diagnosing this. It doesn't seem to be a hardware issue, since re-flashing before fixed it. Any ideas?
Go back to stock, if you have the same problem then it will probably be hardware issues.
Sent from my One V using xda premium
Few days earlier I started to notice this problem after 5 months of use of my device. My screen starts rapidly shaking left to right and front touch panel stop working, it happen when I freshly open an apps. To temporarily fixed it, I have to press power button to turn off the screen. Is it a hardware or software problem?
Did you flashed any rom or kernel?
Do you use trickster?
Some people sayed that uninstalling trickster solved their ghost touches on the keyboard (may not work in your case).
I had a similar problem and was because of a kernel.
If you had modified anything try to use stock for a while and see if the problem persist
Enviado do meu Optimus G através de Tapatalk
Stock, I guess I should wait for official kitkat. Dont have time thinkering my fone atm.
I was ghosts touches on my screen. One was pressed on all sides. To fix it I had to turn off and turn on the screen. I decided to change the touchscreen and the problem was fixed. Now it works ok.
Sorry my english.
Enviado desde mi LG-E975 mediante Tapatalk
where do you get you're replacement touchscreen? any online site that offer spare parts?
yawako said:
where do you get you're replacement touchscreen? any online site that offer spare parts?
Click to expand...
Click to collapse
I bought it on ebay. Screen+touch+ frame. This option:
http://pages.ebay.com/link/?nav=item.view&id=111278902215
But You can buy other options.
1. Touch + screen+ frame (medium dificult)
2. Touch + screen without frame (best option)
3. Only touch screen. (very dificult option)
Many people have told me that the best option is 2, without frame to not be taking off parts that are originally attached to the frame.
You can see totorials on youtube
Ghost Touch now keeps rapidly pulsing at the buttom edge of my screen (portrait) my phone is sometimes uncontrollable. I never thought this kind of newer high end device gets broken so easily under short period of time. I never experienced this from my good old Galaxy Y, Xperia mini and X8 that I accidentally deep under water even now still working in mint condition. So sad with LG products. I was planning to buy LG G Pad but because of this I probably get Nexus 7 instead.
Im going to sell this for $155
Reflash it again with stock firmware twice, problem still persist
Its now a hardware issue
Touch screen seems deteriorating overtime. At first Ghost Touch, then on the next day a dead touch portion just above the home screen panel where the ghost touch first occurred rapidly moving back and then after few days a ghost touch appeared again just below in the middle of the screen (portrait) then after an hour probably about 1.5mm size thickness dead touch. Now a I have 2 horizontal dead touch portion of my screen and probably more to come if I keep using it.
Few days ago i'v got first phaton/ghost touch problem. I used Omni 4.4.4 so
- reflash to clean OmniRom (try few kernels) - the same
- flash to Android L Preview - the same
.....
fu***
Install - ARTMod ROM so 99,9%of stock - and as for now all its ok.
Strange.
Update:
One day and zero problems.
htomasz said:
Few days ago i'v got first phaton/ghost touch problem. I used Omni 4.4.4 so
- reflash to clean OmniRom (try few kernels) - the same
- flash to Android L Preview - the same
.....
fu***
Install - ARTMod ROM so 99,9%of stock - and as for now all its ok.
Strange.
Update:
One day and zero problems.
Click to expand...
Click to collapse
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
dashcsn said:
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
Click to expand...
Click to collapse
On this ROM 0 phantom/ghost touch
http://forum.xda-developers.com/optimus-g-intl/development/rom-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
OK, this is freakin' weird...
I have been running KitKat on my F180S pretty much from the time it got released (different versions: full stock, VDT, Sling...). Yesterday, out of the blue, my digitizer started getting crazy with ghost touches in the upper portion of the screen (around the strip where Q-slide apps usually are in the notification shade, or the clock area on a weather widget where most people have it). This made the phone 100% unusable, as it was constantly registering touches. Rebooted to recovery to do a factory reset, and the problem was persistent in the recovery, too (I am using PhilZ Touch). So, at that point it looked like a hardware issue to me. To clear my consciousness, I opened the phone, disconnected the digitizer, cleaned the connectors, plugged it in again. No dice. Still, I thought about reflashing a full stock KDZ, just for the heck of it (no root, no custom recovery, locked BL). Here is what happened:
1. F180S V30c KitKat - same problem.
2. F180S V30b KitKat (downgraded a notch) - same problem.
3. F180S V20n Jelly Bean - everything is working fine, no ghost touches. Huh?!?
4. Rooted V20n, unlocked BL (Mako method) and flashed CWM using FreeGee - no problem, everything is still OK.
5. Flashed my favourite JB ROM - no problem, everything is still OK.
So, the phone is now running on rooted JB, with unlocked BL and CWM recovery, with no touchscreen problems whatsoever. I may try going to KK again at some point, but will just leave it for now, as I need a stable working phone.
WTF??? I am just scratching my head, trying to understand where the issue came from. It appears to be directly related to KitKat, since eliminating unlocked BL and custom recovery didn't solve the issue, but going back to JB (either full stock, or unlocked BL with CWM) totally cured it. The most bizarre thing is that it started out of nowhere, as I didn't do anything to my phone recently, apart from installing some apps here and there...
kt-Froggy said:
OK, this is freakin' weird...
I have been running KitKat on my F180S pretty much from the time it got released (different versions: full stock, VDT, Sling...). Yesterday, out of the blue, my digitizer started getting crazy with ghost touches in the upper portion of the screen (around the strip where Q-slide apps usually are in the notification shade, or the clock area on a weather widget where most people have it). This made the phone 100% unusable, as it was constantly registering touches. Rebooted to recovery to do a factory reset, and the problem was persistent in the recovery, too (I am using PhilZ Touch). So, at that point it looked like a hardware issue to me. To clear my consciousness, I opened the phone, disconnected the digitizer, cleaned the connectors, plugged it in again. No dice. Still, I thought about reflashing a full stock KDZ, just for the heck of it (no root, no custom recovery, locked BL). Here is what happened:
1. F180S V30c KitKat - same problem.
2. F180S V30b KitKat (downgraded a notch) - same problem.
3. F180S V20n Jelly Bean - everything is working fine, no ghost touches. Huh?!?
4. Rooted V20n, unlocked BL (Mako method) and flashed CWM using FreeGee - no problem, everything is still OK.
5. Flashed my favourite JB ROM - no problem, everything is still OK.
So, the phone is now running on rooted JB, with unlocked BL and CWM recovery, with no touchscreen problems whatsoever. I may try going to KK again at some point, but will just leave it for now, as I need a stable working phone.
WTF??? I am just scratching my head, trying to understand where the issue came from. It appears to be directly related to KitKat, since eliminating unlocked BL and custom recovery didn't solve the issue, but going back to JB (either full stock, or unlocked BL with CWM) totally cured it. The most bizarre thing is that it started out of nowhere, as I didn't do anything to my phone recently, apart from installing some apps here and there...
Click to expand...
Click to collapse
Kinda like my situation.
I have the sprint version of the phone,in every kitkat GEE ROM I have ghost touches, but not in Gproj kitkat ROMs neither in stock or JB.
some weird sh*t is happening here lol
FcoEnrique said:
Kinda like my situation.
I have the sprint version of the phone,in every kitkat GEE ROM I have ghost touches, but not in Gproj kitkat ROMs neither in stock or JB.
some weird sh*t is happening here lol
Click to expand...
Click to collapse
Yeah... But at least in your case the problem seems to be consistent. I was using my phone without any issues, and then it just crapped out for no apparent reason. Nothing changed, same ROM that was working fine before...
kt-Froggy said:
Yeah... But at least in your case the problem seems to be consistent. I was using my phone without any issues, and then it just crapped out for no apparent reason. Nothing changed, same ROM that was working fine before...
Click to expand...
Click to collapse
It started the same way for me.
....
The same thing happened to me. Are you guys familiar with Sky Vega phones? I had a Vega Iron before and also it began having ghost touch issues after upgrading to kitkat. I was frustrated, i also flashed any custom rom i could search and no luck at all. I just sold it recently! and i heard this ghost touch issue is also a common on Nexus 4.
dashcsn said:
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
Click to expand...
Click to collapse
http://forum.xda-developers.com/optimus-g-intl/development/rom-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
Hello everybody,
I have the same problem with my LG - ghost touch and dead zones on the display. First installed the ROM from this link - http://forum.xda-developers.com/opti...te-10-t2811342 , but the issue still exist.
Then change the display with a new one. Dead zones vanished but ghost touch doesn't. Tried some other ROMs even the original stock ROM.
When I installed the new display the ghost touch is mostly when I use Facebook Messenger.
What can I do in this situation?
I rooted my girlfriend's S3 with no problems. I can install a TW rom and everything works as expected. If I installed a ASOP rom, when a call is made or received the screen turns off. If you pull the phone away from your ear the screen stays off. I've browsed around the forums, but have not found anything to resolve the issue. Any ideas of what might cause this on ASOP roms ?
Thanks in advance,
Richard
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
You could test the proximity sensor response. It might be flaky?
I use this app,
https://play.google.com/store/apps/details?id=com.tbs.activity
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
audit13 said:
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
Click to expand...
Click to collapse
The only time it has been an issue is with ASOP roms. If I use a TW rom, there is an option to leave the screen on during a call. This is what I clicked to get the screen on during calls. However, with ASOP roms there is not an option for this. I don't think it's the proximity sensor since the screen stays on with calls on a TW rom. I forgot to mention that the ASOP was KK rom, but I have the same phone different cell provider and do not have this issue. I think I tried a JB rom with the same effect.
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
audit13 said:
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
Click to expand...
Click to collapse
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
riche1 said:
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
Click to expand...
Click to collapse
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
audit13 said:
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
Click to expand...
Click to collapse
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
riche1 said:
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
Click to expand...
Click to collapse
Without making any changes to the stock TW ROM dialer settings, does the screen go black when you place the phone next to your ear and come back on when you move it away from your ear?
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
riche1 said:
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
Click to expand...
Click to collapse
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
audit13 said:
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
Click to expand...
Click to collapse
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
riche1 said:
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
Click to expand...
Click to collapse
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
audit13 said:
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
Click to expand...
Click to collapse
she said it was not a problem until the phone was updated to 4.3 through ATT software update. This was way before I rooted the phone. The same thing started with her sister's phone. So.. I'm stumped as to what the problem could be. I rooted it because I thought CM11 might fix the issue and that was not the case. I don't know how I can go about fixing it. I don't want to take a chance in bricking the phone.
I have the Chinese version of the Find 7 currently running MoKee 44.4 because I thought this issue was caused by AOSPA, which I flashed for the first time yesterday. Anyway when I make a call the screen turns off as it should and will not come back on no matter what I do. I have to reboot the phone every time. I looked through similar threads but they all seem to be unrelated to having a custom rom; this problem only started occurring after I flashed one & everything worked fine when I was running Color OS 2.0. I tried installing a new dialer but the same problem happened.
Does anyone know of a way not to have the screen turn off when making a call or better yet how to fix the issue?
Thanks very much!
I'm having a very similar situation with Paranoid Android 4.6 (both beta4 and latest beta6).
If I long-press home button, I'm sent back to the lock screen, but only after the call is finished.
Maybe there's a problem with AOSPA's proximity sensor during calls?
Sometimes, the screen will not turn off, but the screen will not react to any touch input during the call.
Power button will turn screen off but not back on again.
This is a problem coming from ColorOS 2.0.x.
I will try to flash back to and older version of ColorOS. After that try an AOSP rom.
Sent from my X9006 using Tapatalk
same problem
Whit all rom use CM11 based or similar, I have black screen when I call, and no input possible!
the only ROM stable is the Kakulay, bet it have several problem whit the contacts management! it confuse the name and numbers in the memory and SIM card!