Related
Is anyone experiencing this?? I have 'swipe to unlock' but sometimes it doesn't unlock. But the weird thing is when this happens, you can still unlock when you swipe near the bottom of the scree(not shortcut). I can do a restart and it'll be fine again but it's annoying! I actually got a 2nd S4 and returned the first one hoping it's was just that phone. But apparently it's not. So someone else mush have this problem?
Yea it happen to also nd when u reset it. Its fine Samsung messed up with the s4 so much lags n software problems im on my 3rd s4 in 3 weeks got it may 25. There no where it should b laggy or any problems my s3 is faster sometimes. Im getting the htc one tomorrow. And the battery life is terrible with little use only last 10 hours
E46M3 said:
Is anyone experiencing this?? I have 'swipe to unlock' but sometimes it doesn't unlock. But the weird thing is when this happens, you can still unlock when you swipe near the bottom of the scree(not shortcut). I can do a restart and it'll be fine again but it's annoying! I actually got a 2nd S4 and returned the first one hoping it's was just that phone. But apparently it's not. So someone else mush have this problem?
Click to expand...
Click to collapse
Are you talking about when you slide over and there is a little lock symbol on the bottom of the screen and that is the only thing you can unlock with?
phillyman said:
Yea it happen to also nd when u reset it. Its fine Samsung messed up with the s4 so much lags n software problems im on my 3rd s4 in 3 weeks got it may 25. There no where it should b laggy or any problems my s3 is faster sometimes. Im getting the htc one tomorrow. And the battery life is terrible with little use only last 10 hours
Click to expand...
Click to collapse
^right glad youre leaving.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
phillyman said:
Yea it happen to also nd when u reset it. Its fine Samsung messed up with the s4 so much lags n software problems im on my 3rd s4 in 3 weeks got it may 25. There no where it should b laggy or any problems my s3 is faster sometimes. Im getting the htc one tomorrow. And the battery life is terrible with little use only last 10 hours
Click to expand...
Click to collapse
I'm sure HTC1 is a great phone, but if you're hoping the battery will last longer, I think the 1 will be a bigger disappointment. My S4 has be great with everything other than this little problem. Battery is phenomenal, too!
phillyman said:
Yea it happen to also nd when u reset it. Its fine Samsung messed up with the s4 so much lags n software problems im on my 3rd s4 in 3 weeks got it may 25. There no where it should b laggy or any problems my s3 is faster sometimes. Im getting the htc one tomorrow. And the battery life is terrible with little use only last 10 hours
Click to expand...
Click to collapse
elesbb said:
Are you talking about when you slide over and there is a little lock symbol on the bottom of the screen and that is the only thing you can unlock with?
Normally you can swipe the screen anywhere to unlock. But sometimes I can't no matter how much I swipe the screen. But the weird thing is you can still unlock by swiping near the bottom of the screen(not the lock icon) or by swiping the shortcuts. It's just annoying!
Click to expand...
Click to collapse
E46M3 said:
elesbb said:
Are you talking about when you slide over and there is a little lock symbol on the bottom of the screen and that is the only thing you can unlock with?
Normally you can swipe the screen anywhere to unlock. But sometimes I can't no matter how much I swipe the screen. But the weird thing is you can still unlock by swiping near the bottom of the screen(not the lock icon) or by swiping the shortcuts. It's just annoying!
Click to expand...
Click to collapse
Well, the widgets on the lockscreen block the area from being unlocked. You can only unlock from below them. You might however be able to set it to just a clock (under my device > lockscreen) and that may enable unlocking from the top.
Click to expand...
Click to collapse
elesbb said:
E46M3 said:
Well, the widgets on the lockscreen block the area from being unlocked. You can only unlock from below them. You might however be able to set it to just a clock (under my device > lockscreen) and that may enable unlocking from the top.
Click to expand...
Click to collapse
But I don't understand why it happens so randomly. And I don't know what you mean by widgets. Widgets(which are shortcuts right?) are located on the bottom of the screen. And that's the part that's not effected by this as I could still unlock either by opening up a widget or swipe just above it.
Click to expand...
Click to collapse
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!
Ever since I've updated to 8.1, I've had a strange problem with swiping up to unlock my phone. It doesn't happen every time, but when it does, I have to do a full swipe from the bottom almost to the top of the screen. Here's a video demonstrating this intermittent problem:
https://photos.app.goo.gl/ZA4Gyv9COepsw8aE3
You can see the touches on there showing how I am swiping in a way that normally would have "flung" the screen up and unlocked, but instead I have to do a long swipe up. Anyone else having this problem or have any ideas as to what could fix it?
That's a feature or some **** of 8.1. Gotta swipe up farther to unlock.
I say to everyone, stop using this garbage release. I came back to 8.0. There are so many things which are utterly stupid on 8.1.
ithehappy said:
That's a feature or some **** of 8.1. Gotta swipe up farther to unlock.
I say to everyone, stop using this garbage release. I came back to 8.0. There are so many things which are utterly stupid on 8.1.
Click to expand...
Click to collapse
Dang. so that's really a known "feature" of 8.1?
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
kickenwing13 said:
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
Click to expand...
Click to collapse
I have noticed this sometimes as well on DP2. I have a fingerprint setup but my phone is usually lying on my desk so i swipe up and enter the pattern. Sometimes it just refuses to swipe up and stay there.. its sort of bounces back down. I have to pick up the phone and use the fingerprint scanner.
They lock screen swipe issue was fixed for me recently on a security update but on dp2 sometimes it's worst then it ever was before the fix.
Just tap the lock, no need to swipe
Ah never noticed that. If you have the fingerprint enabled, tap the fingerprint icon.
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
And this is why you're a senior member, that's pretty helpful. Now swiping away notifications would be wonderful
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
Are they not allowed to test and provide feedback? Why does it bother you?
Anyways, to be fair, I've been experiencing this issue off and on ever since I purchased the phone. And no, I'm not running beta firmware.
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
The lockscreen swiping is definitely an issue with the Pixel 2 XL. I always had this issue on Oreo but on P DP2 it's gone. It's interesting how it's the opposite for others in this thread.
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
E30Nova said:
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
Click to expand...
Click to collapse
Oreo Lock Screen Fix (Substratum) from Arol Wright fixed it for me.
skimminstones said:
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
Click to expand...
Click to collapse
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
To be fair....even before I jumped on dp2....I had these same lockscreen issues on Oreo. It's just worse on dp2.
kickenwing13 said:
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
Click to expand...
Click to collapse
Nope, No issues on mine
Yeah the swipe up issue definitely does happen once in a while for me but it's not often or consistent. Now that I know the tap the fingerprint/lock does the same thing, I just do that.
Sent from my Pixel 2 XL using Tapatalk
No issues here. If i'm looking for perfection ill go purchase one of those $25,000 phones and even then you'll find something wrong.
Hello,
I have been struggling recently to answer or reject calls when given the swipe up or down option.
When its unlocked and I get the tap to answer or reject as a notification its fine.
I'm just wondering if anyone else had a similar issue or had found a fix.
I'm on the official firmware, running 8.1.0
I've experienced something similar too. Sometimes I find myself swiping over and over again just to get one call answered or rejecte I have no idea why it does that, or when, it seems to be random on mine
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
I've found you can swipe down from the top of the screen and can answer it from the notification menu instead.
Just takes longer.
cobben said:
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
Click to expand...
Click to collapse
Just after having written the above, the phone corrected itself.
Now I can answer calls on the first swipe.
Interesting . . .
Sometimes my phone will let me answer normally. most of the time however I have to use the notification bar.
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Yup, been having the same issue. Stock phone, no root. What's frustrating is there as no further updates.
iliais347 said:
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Click to expand...
Click to collapse
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
cobben said:
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
Click to expand...
Click to collapse
What i did is i added the google dialer app to my phone, then to game booster and set its fps to 40. Now i can answer the calls.