Database Develop

ADP - Cannot display while real keyboard is closed!!!

Hi all,
I have troublesome problem. Could you help me. My phone is ADP1.
If the real keyboard is closed, and phone is locked then I cannot use menu button to unlock, it does not display anything , keyboard is bright
If the real keyboard is opened, and phone is locked then I can use menu to unlock, it displays, keyboard is bright as normal.
While the phone is unlocked, whether the real keyboard is opened or closed, it works as normal.
The problem is I cannot unlock the phone while the real keyboard is closed. It' really crazy
I also try to downgrade to 1.0, upgrade to 1.5, the result is the same.
Please help me
Thanks in advance.

That's horrible, I have to slide the keyboard to take a call
I still wait for god

Unable to Unlock Screen (Epic Unlock Screen)

I am using Darky's ROM 9.2 and all has been fine until today.
Normally I use the Android unlock screen but I was a bit bored of it, so just changed to the bottom option (Epic? Unlock screen).
Now, I am unable to unlcock the screen. The buttons cause the screen to come on, but touching the screen gets no response. Have tried rebooting but no joy.
Can anyone think of any options without flashing a new ROM using CWM/Odin?
Thanks

Hmm, eventually started responding, just VERY VERY slowly. Then did it again and same result. Changed to a different lock screen now and working again, lol

different rom but same problem, tx for the heads up, saved much headache

Dead Touch Screen??

Hello,
My Touch screen doesn't respond to touching since an hour ago.
I see no logical reason for this fault,
My screen is guarded and nothing happend to it.
I tried to remove battery and insert it with no luck, I booted my phone into CWM touch recovery, and it also doesn't recognize touching.
update2:
The problem appeared again.

just flash a kdz to return to stock rom

naeem86 said:
just flash a kdz to return to stock rom
Click to expand...
Click to collapse
The problem appeared again I tried a lot of times to remove battery&insert but it doesn't help.
Please help me.

I've just flashed my phone to stock rom,
I'm still having the same touchscreen issues - the screen won't respond to touching.
Any suggestion please?
Is it possible that the touchscreen issue is caused because of the screen protector?

ohadz said:
I've just flashed my phone to stock rom,
I'm still having the same touchscreen issues - the screen won't respond to touching.
Any suggestion please?
Is it possible that the touchscreen issue is caused because of the screen protector?
Click to expand...
Click to collapse
Screen protector protects screen If you have got stock FW back on the phone, just bring it to your carrier and they should do it on warranty.

N00BY0815 said:
Screen protector protects screen If you have got stock FW back on the phone, just bring it to your carrier and they should do it on warranty.
Click to expand...
Click to collapse
Thanks for the advice,
I flashed stock rom and now when I turn on my phone It shows me the "Android Welcome Screen", Is there a method how to bypass this screen without touching the screen? (If I'm taking phone to my carrier, it might seem strange to them that my phone shows the "Welcome screen" whether the touchscreen doesn't work so they could know I flash my phone and not to accept my phone's warranty)

ohadz said:
Thanks for the advice,
I flashed stock rom and now when I turn on my phone It shows me the "Android Welcome Screen", Is there a method how to bypass this screen without touching the screen? (If I'm taking phone to my carrier, it might seem strange to them that my phone shows the "Welcome screen" whether the touchscreen doesn't work so they could know I flash my phone and not to accept my phone's warranty)
Click to expand...
Click to collapse
You can try on-screen phone, which is a software by LG, but i think, that this also needs to be setup first... Otherwise, just tell them, that you did a factory reset, because your phone wasnt working properly anymore, and thats when your error occured.
I dont see another way... Maybe repair it on your own

N00BY0815 said:
You can try on-screen phone, which is a software by LG, but i think, that this also needs to be setup first... Otherwise, just tell them, that you did a factory reset, because your phone wasnt working properly anymore, and thats when your error occured.
I dont see another way... Maybe repair it on your own
Click to expand...
Click to collapse
I'm going to take my phone back to carrier
But there's very strange thing: the touchscreen rarely works.
I removed the battery for a night and when I got up in the morning and I inserted the battery and turned the device on, for a few seconds the touch worked . What does it tell about phone?

I've just received my phone from repairing, and my touch screen has been replaced.
I'm a little disappointed because I expected for getting new phone(I have a warranty). I've also noticed that the screen is a little thicker, about few mm, which is weird.
Is it right that phone with replacement touch screen won't be as smooth and good as normal one, or not necessarily?

Same problem of Freezing screen
Disappointing but i too have this very same problem with my brother's P970... any ideas how or why?
though sometimes it would respond but leaving it a few minutes would again make it freeze. The hardware buttons work but the 4 touch buttons wont. now i cannot get thru the rom manager to make it into Bootloader mode so i can install another rom...
some things i did a few days before this happened:
1. flashed CWM recovery successfully.
2. installed a lot of apps and happened to fill up the SD card.
3. installed a new ROM Gingerbread Repackaged V20N
I can still get to S/W Upgrade but all I need is the Bootloader Mode. I honestly dont think this would be a digitizer malfunction since it works well in a given time. It's like it lagggggs much and unresponsive. I cannot get past the lock screen. Any ideas or any other way to get to the B/L mode? Thanks.

arzakem said:
Disappointing but i too have this very same problem with my brother's P970... any ideas how or why?
though sometimes it would respond but leaving it a few minutes would again make it freeze. The hardware buttons work but the 4 touch buttons wont. now i cannot get thru the rom manager to make it into Bootloader mode so i can install another rom...
ARZAKEM i have the very same problem too i was also doing the same stuff which you atempted and end up with none responsive touchscreen.
my phone is since then lives in a my draft in the kitchen and i was also curious about the malfunctionality because it worked sometimes and other times not.
I just thumbled upon the post when i search the web i know its too late to ask but could you please please tell me what you done with that phone ???
I ordered a new touchscreen from ebay and it will arrive soon but i was wondering wether you managed to fix it or not? could you please tell me what was the real problem did you replace the touchscreen or is it not the touchscreen?
Click to expand...
Click to collapse

I have this problem occasionally as well, but only occasionally and only with cm10
Sent from my LG-P970 using xda app-developers app

my phone has somehow the same issue, the touch screen works normally,but out of nowhere it stops responding,i mean the hole screen and also the 4 touch buttons on the bottom just wont work like they supposed to,but here is the catch,i lock the phone with power button and the screen and the buttons start to work normally for a while......but then the problem happens again!!! could someone tell me what the heck is wrong?? is it the software or the physical touch sensor thing is broken?? HELP!!

albertwesquer said:
my phone has somehow the same issue, the touch screen works normally,but out of nowhere it stops responding,i mean the hole screen and also the 4 touch buttons on the bottom just wont work like they supposed to,but here is the catch,i lock the phone with power button and the screen and the buttons start to work normally for a while......but then the problem happens again!!! could someone tell me what the heck is wrong?? is it the software or the physical touch sensor thing is broken?? HELP!!
Click to expand...
Click to collapse
You need to indicate your current ROM. Then can the issue be accessed
Sent from my LG-P970 using Tapatalk 2

stock 4.4.2 home screen flip or rotate or both

i just bought a used vzw lg2 (vs980) and its updated to 4.4.2 already and Not rooted.
the bottom 2/3 of the screen does not respond to touch but surprisingly i did do a wipe and i got through to the ui.
isnt the home screen supposed to auto rotate (flip would be great).
i havent used this phone to much but most of you guys probably know what i need with the bottom 2/3 of the digitizer not working.
im gonna order a glass or maybe lcd assy but until then would like to play with it.
if i order glass from china that will take close to 3 weeks
thanks

You need to enable rotation by disabling potrait mode only in Settings, Home Screen

Double tap to wake. Or more like quadruple tap to wake, eh?

I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?

If you move your phone first, then it will work by double tapping.
I think that quadruple tap works because one of those first two taps moves the phone.

Not from my experimentation. It doesn't seem to matter if i've moved it first or tapped it directly when it's sitting on the table. Then only factor that seems to matter is time since screen off.
Thanks for the input though.

It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.

pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
Click to expand...
Click to collapse
I'm on A.5.77, which is the latest, right?
I have this issue about 5% of the time, 95% of the time even if I have the phone lying still on the table double tap works. Must be something (also) else than the firmware!

pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake
Click to expand...
Click to collapse
double tap works first time every time even if the phone has been sitting still and idle for 10 hours.
I know theres a few people who have this problem but its something other than just the new firmware.

I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.

pipspeak said:
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
Click to expand...
Click to collapse
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...

had a tempered glass protector on from day one, phone has always been stock, no other launcher. T2W worked brilliantly until the latest firmware update. frustrating when the phone is the car mount, i have to hit the power button to get the screen on instead of just tap-tap.

quarrymanpaul said:
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
Click to expand...
Click to collapse
Full day's use now and replacing Nova launcher with Apex has definitely improved things.
Might help others in the same situation who are scratching their heads wondering why everyone else seems to have perfect tap2wake.

Tried Apex for a day as well. No different than Nova for me.

hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap

AM Radio said:
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Not working here.
I have a Nillkin tempered glass on mine though.

quack3d said:
I have a Nillkin tempered glass on mine though.
Click to expand...
Click to collapse
me too. weird. fingers crossed the next update takes care of this, properly.

AM Radio said:
...TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Works for me too. [emoji4]

Did Lollipop fix this problem?

quack3d said:
Did Lollipop fix this problem?
Click to expand...
Click to collapse
Not really. In fact it got worse.

quarrymanpaul said:
I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
Click to expand...
Click to collapse
Well, I can tell you why this is happening. this happened to me, because I just had too many xposed modules.. once I got rid of them, everything went back to normal

Been a long time since I've posted here but found this thread as had the same issue when the phone is flat on a table.
Anyway, think I've found a solid solution or work around, depends how you look at it. If you use just an extended finger, all other fingers closed or away from the phone, it's very inconsistent but mostly unresponsive.
Solution: grip the top and bottom of the phone lightly with your thumb and middle or 4th finger at the same time as tapping the screen with your index finger. Works every time for me.
So Sony's reduced the sensitivity to the point where it needs additional capacitance so it knows you are holding the phone and it won't unlock in your pocket. Makes sense.

pretty frastrating here too.. but really can't find out the main reason of the problem here as immediately when I got the phone I rooted it, flashed .77, replaced stock launcher with nova, installed expsed and 2-3 modules :crying:
will try the three-taps and olding-phone+index-finger-tapping workarounds, thanks for the hints