Related
Anyone else having this same issue where your unlock screen shifts so that not all the number pad is visible to unlock the phone? I keep having this happen to me.
I'm completely stock
http://imageshack.us/photo/my-images/827/screenshot2012080409201.png/
konga056 said:
Anyone else having this same issue where your unlock screen shifts so that not all the number pad is visible to unlock the phone? I keep having this happen to me.
I'm completely stock
http://imageshack.us/photo/my-images/827/screenshot2012080409201.png/
Click to expand...
Click to collapse
Time to root!
Whoa. I never even knew you could get the number pad to show up on the lock screen. I have had my lock screen sift before. It happened once about 2 weeks ago. I just reset the phone and it hasn't happened since. Is this something that keeps happening to you?
Unfortunately this happens quite often and requires me to reboot the phone to unlock it.
I had this issue once with the pattern lock as well. Shifted up and right leaving only the lower left exposed and had to reboot.
Sent from my SGH-T999 using xda app-developers app
+1 it's happened to me a few times. Had to restart phone to get it properly aligned again.
Sent from my SGH-T999 using xda app-developers app
Yup.happens here to..... once in a while
Sent from my SGH-T999 using xda premium
konga056 said:
Anyone else having this same issue where your unlock screen shifts so that not all the number pad is visible to unlock the phone? I keep having this happen to me.
I'm completely stock
http://imageshack.us/photo/my-images/827/screenshot2012080409201.png/
Click to expand...
Click to collapse
This has never happened to me on the lock screen personally, but my girl had this happen to her phone randomly one day at work and afterwards she found out her IMEI code on the phone had been blocked, had to send it back in for a replacement.
It's possible if you lose your data connection under certain conditions this may happen. I'm assuming this might also occur if the screen turns on while trying to change it's orientation as this has happened to me in certain programs which required a reboot to fix (this occurred while reading during the 5 second period between the screen shutting off automatically and the screen locking therefore the screen had not yet locked before it was turned back on).
Yes, have had it happen to be as well. Am rooted. Reboot seems to be the only solution.
Sent from my SGH-T999 using Tapatalk 2
Happened to me once too, and I'm stock, just a glitch
After upgrading from 4.0 to 4.1 I found that my phone won't switch on until I press the power button three times although sometimes it does switch on first go. Then, I installed the latest OTA patch to 4.1.1, software number 3.14.401.31 (international version) and found that accessing the camera from the lock screen, with security pattern enabled, is very slow. That is when you drag the camera to the unlock ring and release, the lock ring pauses for about 5 seconds before the camera starts up. This didn't happen before the last update.
So far I have taken the camera out of the unlock bar and rebooted the phone and turned off geo-tagging photos. None of these options helped.
If I turn off the pattern unlock then accessing the camera from the lock screen is normal so this appears to be something to do with accessing the camera with the pattern unlock enabled.
Hi,
I have encountered the same thing - seems like you're the only one who has reported it on these forums so far. I hadn't tried disabling the pattern unlock, thanks for the tip. I'll try this. But I'm quite unhappy about this new bug that just came out of nowhere with the 4.1 update, especially knowing that the camera quick start was one of the features HTC boasted about so much!
Yeah, not much on it at the moment but the upgrade is quite recent. Hopefully more people will find this thread and we can get some traction.
Same problem here, me and my wife. Wery annoing!
Sent from my HTC One X using xda app-developers app
I emailed HTC and they replied the next day which was good. They asked me to reset the camera app, reboot the phone and then factory reset the phone if the other things didn't work. It didn't fix it yet so I'll see what they come up with next.
exazonk said:
I emailed HTC and they replied the next day which was good. They asked me to reset the camera app, reboot the phone and then factory reset the phone if the other things didn't work. It didn't fix it yet so I'll see what they come up with next.
Click to expand...
Click to collapse
Exazonk,
please let us know if it works!
Thanks!
:good:
Pietje_1985 said:
Exazonk,
please let us know if it works!
Thanks!
:good:
Click to expand...
Click to collapse
No factory resetting my phone didn't work. HTC rang me back and said that I need to return it to who I bought it from. In other words no fix and returning certainly won't prove anything. I think I'll just have to wait it out until it is fixed with another update ... hopefully.
Or maybe we should looking at getting an app that provides the same functionality?
Have te same bug guys :/
Sent from my HTC One X using xda premium
I tried the factory reset too, to no avail. Seems like disabling the phone lock is the only solution, but that's not really what I would call a satisfactory solution, since I'm using a VPN on my phone and that requires a lock + I just don't want to go lock-free.
We need this issue to be known to HTC and hopefully a fix will come.
Ps I don't think this problem was present in the JB update, but only came in the small FW update that followed.
Sent from my HTC One X using Tapatalk 2
benitorios said:
I tried the factory reset too, to no avail. Seems like disabling the phone lock is the only solution, but that's not really what I would call a satisfactory solution, since I'm using a VPN on my phone and that requires a lock + I just don't want to go lock-free.
We need this issue to be known to HTC and hopefully a fix will come.
Ps I don't think this problem was present in the JB update, but only came in the small FW update that followed.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah it only came in the small update after the JB update. But another problem that I'm having is that to turn my phone on via the power button, sometimes I have to press the power button three times. It doesn't always happen, but sometimes after the phone has been off for a while, I hit it once and nothing, hit it again, nothing and then on the third press it comes on. I'm not sure if they are related to the "quick" camera launch problem.
One work around for this bug, if you use your camera a lot, is to leave your camera in standby mode. That is turn your phone off while the camera is active and then when you hit the power button it will go straight to camera. I don't use this myself as I have the lock pattern on to prevent my phone from turning on in my pocket which is common on HTC phones
HTC support are a waste of space
I have this issue too. HTC told me to factory reset it, then when that didn't work they told me to return it to the store to be sent away for repair. They really don't have a clue at HTC support.
The phone was returned to Vodafone yesterday and the repair centre said "no fault found" What are they on!!! The Vodafone store confirmed the issue was still there.
I now have the phone back with no resolution.
Going to call Consumer and get some advice.
I have this problem too, quite annoying.
Sent from my HTC One X
Ok, they fixed this bug with the latest 30MB update that I got this morning.
exazonk said:
Ok, they fixed this bug with the latest 30MB update that I got this morning.
Click to expand...
Click to collapse
:good: Great news!
May I ask where you're based? I've got a UK CID and haven't seen this update yet. Did you do anything special or did it just come as OTA?
Thanks!
benitorios said:
:good: Great news!
May I ask where you're based? I've got a UK CID and haven't seen this update yet. Did you do anything special or did it just come as OTA?
Thanks!
Click to expand...
Click to collapse
I'm in Brisbane, Australia and ordered my phone through kogan.com.au. It popped up as an OTA on my phone.
Thanks. Looks like that 3.18 OTA is seeding at the moment, shouldn't be long before I get it. Fingers crossed....
Sent from my HTC One X using Tapatalk 2
So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).
^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.
Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.
@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?
I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96
Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.
This is happening when the screen is on right? Or is the screen turning off and then not turning I again?
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...
Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...
icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?
Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.
Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.
Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!
Hi!
I Have a ZE550ML with stock rom in the last firmware version released and its not rooted... since nearly a month im facing some ghost touches randomly in the touchscreen... The phone and the touchscreen works perfectly but, sometimes, witouth an aparently reason, the screen becomes "crazy" and after activate "Show touches" in developer options, i can see the screen is being touched by... nothing? x'D
Anyone else is facing this issue? Can anyone help me? I've already contacted with Zenfone 2 support in beta forum but... no answer..
Thank you,
Regards
not getting that issue, even after several falls. must be hardware related.
Sent from my ASUS_Z008D using Tapatalk
same issue here.
I've boot loader unlock, rooted. Flash different ROMs still same problem.
It's time look for other phone.
tsaibru said:
same issue here.
I've boot loader unlock, rooted. Flash different ROMs still same problem.
It's time look for other phone.
Click to expand...
Click to collapse
Im not sure if it is a digitalizer problem (HW problem) because it happens randomly and not 2 much often.. (lets say, 1 time every 40 mins of screen) and after lock & unlock the phone, the problem its gone)
WW-16.0631.1910.44 officially came out this week, i wonder why no one is talking about it! Its got a major major bug, at random times when you unlock your device, it will unlock but not respond to your touches. I have noticed this with face unlock at the moment. I updated yesterday, and have faced thi like every 5 out if 10 times while the device detects my face to unlock.
Is it a bug? Or am i just too ugly? ?
https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_BIOS/
Thugsin313 said:
WW-16.0631.1910.44 officially came out this week, i wonder why no one is talking about it! Its got a major major bug, at random times when you unlock your device, it will unlock but not respond to your touches. I have noticed this with face unlock at the moment. I updated yesterday, and have faced thi like every 5 out if 10 times while the device detects my face to unlock.
Is it a bug? Or am i just too ugly? ?
https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_BIOS/
Click to expand...
Click to collapse
I always use face unlock and I do not have this issue.
I can confirm that, already posted on ASUS forums. Disabling unlocking via fingerprint "fixes" the issue for now.
I never had this issue, I've been with this version for a long time and always used fingerprint unlock.
1910.63 CN is out and fixes this issue so lets hope the WE version gets released soon if not today
stealthj said:
1910.63 CN is out and fixes this issue so lets hope the WE version gets released soon if not today
Click to expand...
Click to collapse
i think no, because ww is have beta (android 10) this week
For me face unlock working just fine.
happened only once to me after updating and wasn't sure what to make of it so thank you for reporting it
I updated to 10.44 recently but haven't faced this issue. Do you have the fingerprint enabled as well? I only use face unlock by the moment.
Same issue here. Yes fingerprint is enabled and so is face recognition. Seems to happen when a call is received as well. Cannot answer the call either then.
I experienced 2 or 3 times before and I had to restart my phone. Hoping the new OTA fixes the issue
https://forum.xda-developers.com/rog-phone-2/how-to/1910-64-ww-update-t4021947
Anyone experiencing being disconnected from wifi network and mobile sim signal are disappearing as well while in the middle of the game. Im on 1910.44. The only solution i founds is to turn on Airplane mode and Turn on wifi alone. Any help pls
The screen unlock issue is gone in WW.64 for me.
Barbatos19 said:
Anyone experiencing being disconnected from wifi network and mobile sim signal are disappearing as well while in the middle of the game. Im on 1910.44. The only solution i founds is to turn on Airplane mode and Turn on wifi alone. Any help pls
Click to expand...
Click to collapse
I have the same issue. Using single sim and wifi, suddenly it all disconnects for some seconds. However it didn't happen today. Dunno if that's caused by the recent update, or the fact that I forced 2G only mode via external app as there is no such option in network settings.