So I'm watching youtube on the dual screen using landscape and I want to sleep the main screen so i touch sleep main screen option on the dual screen tab tool, it shows a prompt saying main screen will dim to save battery and swipe to dismiss. I dont touch or swipe anything and the prompt swipes itself away and screen undims or sometimes doesn't even dim. This is also the case with Call of duty mobile, when I'm playing the game in battle royal mode the mini map enlarges randomly even if I don't touch it, and the voice chat options will engage and open without me touching those as well. Anyone else has this problem? Any solutions?
I could have sworn I saw a post earlier about ghost touches, though I can't seem to find the thread it was in at the moment.
I've been using the phone heavily since I got it on April 1st, and I have not experienced this issue at all.
Any chance you had an LG phone prior to this and used LG Switch to transfer over all of your stuff?
I've read reports here that doing so can cause some pretty serious battery drain and/or lag issues, so there could be other bugs as another side-effect.
Have you tried a factory reset?
Mejilan said:
I could have sworn I saw a post earlier about ghost touches, though I can't seem to find the thread it was in at the moment.
I've been using the phone heavily since I got it on April 1st, and I have not experienced this issue at all.
Any chance you had an LG phone prior to this and used LG Switch to transfer over all of your stuff?
I've read reports here that doing so can cause some pretty serious battery drain and/or lag issues, so there could be other bugs as another side-effect.
Have you tried a factory reset?
Click to expand...
Click to collapse
Yeah I think I read that thread. I haven't tried a reset since I already used so much data to download apps and don't want to setup the phone again. I did use the google cloud restore for my contacts and I also had the t mobile April security update. Mejilan can you tell me if you can put your main screen to sleep while watching a youtube video on the dual screen? Please tell me what kind of result you get. Thanks
Lowe941 said:
Yeah I think I read that thread. I haven't tried a reset since I already used so much data to download apps and don't want to setup the phone again. I did use the google cloud restore for my contacts and I also had the t mobile April security update. Mejilan can you tell me if you can put your main screen to sleep while watching a youtube video on the dual screen? Please tell me what kind of result you get. Thanks
Click to expand...
Click to collapse
I set aside the the dual-screen accessory because it's just too uncomfortable to hold for most use-cases.
I'll go dig it up, plug it in, and give it a shot later, when I have some free time, and report back.
https://forum.xda-developers.com/lg-v60-thinq/help/phantom-home-button-presses-t4082573
Above is the link for the other thread.
Lowe941 said:
Yeah I think I read that thread. I haven't tried a reset since I already used so much data to download apps and don't want to setup the phone again. I did use the google cloud restore for my contacts and I also had the t mobile April security update. Mejilan can you tell me if you can put your main screen to sleep while watching a youtube video on the dual screen? Please tell me what kind of result you get. Thanks
Click to expand...
Click to collapse
If you play a YT video on the second screen and lock/sleep your phone, the second screen goes to sleep as well.
I didn't bother with headphones for this test, and noticed that the audio comes out of the phone's speakers.
It appears that the second screen doesn't have speakers of its own.
So yeah, you cannot watch something on the second screen while having the phone asleep.
And it make sense. It's just a screen. No second pair of speakers. No second headphone jack. No separate battery. No second set of modems, etc.
Mejilan said:
I set aside the the dual-screen accessory because it's just too uncomfortable to hold for most use-cases.
I'll go dig it up, plug it in, and give it a shot later, when I have some free time, and report back.
Click to expand...
Click to collapse
It actually was working for me last night as far as the putting main screen to sleep function but call of duty still acts up I'm hoping the update for the game on May 1St will fix, but sure whenever you get a chance...
Lowe941 said:
It actually was working for me last night as far as the putting main screen to sleep function but call of duty still acts up I'm hoping the update for the game on May 1St will fix, but sure whenever you get a chance...
Click to expand...
Click to collapse
I answered your YT question one post above yours that I just quoted.
Mejilan said:
I answered your YT question one post above yours that I just quoted.
Click to expand...
Click to collapse
Actually you CAN watch youtube on the second screen and sleep/dim the main screen by using the floating dual screen button. It has an option asking if you want to sleep dim the main screen to conserve battery life. It does work for me now, I'm not sure why it was going wonky on me when I first posted but hopefully that it doesn't do it anymore. I'm guessing the tmobile April security update did the trick. It's just I have phantom touches on call of duty still.
Lowe941 said:
This is also the case with Call of duty mobile, when I'm playing the game in battle royal mode the mini map enlarges randomly even if I don't touch it, and the voice chat options will engage and open without me touching those as well. Anyone else has this problem? Any solutions?
Click to expand...
Click to collapse
This is happening to me as well when I'm playing PubG Mobile. The ghost touches are happening not on the map but to the left of that. On another LG V60, the device would get random dead zones as well.
I'm going to do the following test and suggest you do the same and report back your results.
1. wait until the ghost touches start happening and flip the phone around. hopefully the ghost touch continues to happen in the same exact location of the physical screen, and it triggers a different button
2. remove the screen protector and try the tests again
are you using a screen protector?
might process a warranty replacement if the results are reproduceable
Lowe941 said:
Actually you CAN watch youtube on the second screen and sleep/dim the main screen by using the floating dual screen button. It has an option asking if you want to sleep dim the main screen to conserve battery life. It does work for me now, I'm not sure why it was going wonky on me when I first posted but hopefully that it doesn't do it anymore. I'm guessing the tmobile April security update did the trick. It's just I have phantom touches on call of duty still.
Click to expand...
Click to collapse
Oh, that is good to know. I'm not using the dual-screen attachment anymore (typing in portrait mode is IMPOSSIBLE with it), but I only ever used the Dual-Screen notification shade tile to enable the second screen, not the pill button thing. I should have explored our options more thoroughly. Thank you for correcting me.
Edit - I have recently added a tempered glass screen protector to my phone, and while it completely screwed with my fingerprint biometrics (I had to delete the fingerprints and redo them), the protector itself is not causing any ghost touches for me. And once I redid the fingerprints, there have been no further issues there either.
jd254 said:
This is happening to me as well when I'm playing PubG Mobile. The ghost touches are happening not on the map but to the left of that. On another LG V60, the device would get random dead zones as well.
I'm going to do the following test and suggest you do the same and report back your results.
1. wait until the ghost touches start happening and flip the phone around. hopefully the ghost touch continues to happen in the same exact location of the physical screen, and it triggers a different button
2. remove the screen protector and try the tests again
are you using a screen protector?
might process a warranty replacement if the results are reproduceable
Click to expand...
Click to collapse
Yes I am using a screen protector and I was actually thinking that might be the problem, although it seems like a solid install. I just got the update for cod season 6 and I'm downloading now. I'll see if that solves the problem. I'll also try what you suggested and then post results
Update: so the cod update did not fix the issue, but I tried doing as you suggested and flipped the phone around and the problem went away. I then tried flipping it back to original and problem persisted. I think it is the tempered glass. I don't want to remove it since it cost me 40 bucks. Any suggestions?
Mejilan said:
Oh, that is good to know. I'm not using the dual-screen attachment anymore (typing in portrait mode is IMPOSSIBLE with it), but I only ever used the Dual-Screen notification shade tile to enable the second screen, not the pill button thing. I should have explored our options more thoroughly. Thank you for correcting me.
Edit - I have recently added a tempered glass screen protector to my phone, and while it completely screwed with my fingerprint biometrics (I had to delete the fingerprints and redo them), the protector itself is not causing any ghost touches for me. And once I redid the fingerprints, there have been no further issues there either.
Click to expand...
Click to collapse
So I installed the update for cod and it still had the ghost touch problem with the top right side of the screen, iflipped the phone per what jd254 suggested and I didn't get the phantom touches. I'm assuming it is the tempered glass that is causing it. I dont want to remove it cause it cost me 40 bucks.
2nd update: so I tried taking it out of the dual screen case and notice it doesn't have phantom touch ( I played a full game of battle royale) so I'm not sure if its the tempered glass or the case. Need to investigate more
Lowe941 said:
So I installed the update for cod and it still had the ghost touch problem with the top right side of the screen, iflipped the phone per what jd254 suggested and I didn't get the phantom touches. I'm assuming it is the tempered glass that is causing it. I dont want to remove it cause it cost me 40 bucks.
2nd update: so I tried taking it out of the dual screen case and notice it doesn't have phantom touch ( I played a full game of battle royale) so I'm not sure if its the tempered glass or the case. Need to investigate more
Click to expand...
Click to collapse
Is the case touching the tempered glass anywhere around the the edges? If the case is pressing on the screen protector and lifting or peessing it even the smallest amount that could cause phantom touches maybe..just an idea
FWIW, I'm using both a tempered glass screen protector and a case that wraps around to grip the front of the phone a bit, and I'm not getting any phantom touches at all.
The case is NOT rubbing up against the edges of the screen protector, however. Which is fine, because if it were, it could potentially dislodge it.
Or, I suppose, cause phantom touches.
Ryano89 said:
Is the case touching the tempered glass anywhere around the the edges? If the case is pressing on the screen protector and lifting or peessing it even the smallest amount that could cause phantom touches maybe..just an idea
Click to expand...
Click to collapse
Ok more investigating and playing codm I notice that the mini map opens up when i perform a touch combination with my thumbs. So the map gets triggered when I press and hold up on the left side virtual joystick to sprint and press the jump virtual button on the right simultaneously. I can't recreate what button presses open the voice chat box, but now I have to strike the dual case as being the problem along with the tempered glass, at least i assume those aren't causing the ghost touches.
For anyone having touch issues, as a troubleshooting aid: enable developer options, and then toggle on "Show touches" and "Show touch data". Might help figure out what is going on.
bilbo60 said:
For anyone having touch issues, as a troubleshooting aid: enable developer options, and then toggle on "Show touches" and "Show touch data". Might help figure out what is going on.
Click to expand...
Click to collapse
Awesome thanks I forgot how to enable developer options...
Never mind developer option enabled
bilbo60 said:
For anyone having touch issues, as a troubleshooting aid: enable developer options, and then toggle on "Show touches" and "Show touch data". Might help figure out what is going on.
Click to expand...
Click to collapse
I'm getting VERY interesting results.
1. dead spots: I moved my finger up the right side of the screen to look up. my character did not look up, which I would assume there was a dead spot before. This is incorrect. I can see the screen registered using that option mentioned above. the screen registered the action, but didn't pass it to the software?
2. FPS drops: I assume it's an FPS drop because everything was laggy when this happened. (PubG mobile was set to max settings, and runs 100% fine, until now) I was flying the helicopter, so I had several fingers on the screen at the same time, with a lot of rotational movements. the screen doesn't clear all of these movement data until I literally take all my fingers off the screen for half a sec. When I did that, it stop lagging.
3. ghost touches: Each touch on the screen has an x and y axis point to tell the software where it's being touched. With several finger on the screen (sometimes 2, but commonly with three or more), I noticed that the y axis for my left thumb and the x axis for my right thumb was creating those ghost touches! The screen would combine the x and y axis from different fingers to create a touchpoint on the screen.
so I don't care too much about 1 and 2, but... what can I do about 3?
jd254 said:
I'm getting VERY interesting results.
1. dead spots: I moved my finger up the right side of the screen to look up. my character did not look up, which I would assume there was a dead spot before. This is incorrect. I can see the screen registered using that option mentioned above. the screen registered the action, but didn't pass it to the software?
2. FPS drops: I assume it's an FPS drop because everything was laggy when this happened. (PubG mobile was set to max settings, and runs 100% fine, until now) I was flying the helicopter, so I had several fingers on the screen at the same time, with a lot of rotational movements. the screen doesn't clear all of these movement data until I literally take all my fingers off the screen for half a sec. When I did that, it stop lagging.
3. ghost touches: Each touch on the screen has an x and y axis point to tell the software where it's being touched. With several finger on the screen (sometimes 2, but commonly with three or more), I noticed that the y axis for my left thumb and the x axis for my right thumb was creating those ghost touches! The screen would combine the x and y axis from different fingers to create a touchpoint on the screen.
so I don't care too much about 1 and 2, but... what can I do about 3?
Click to expand...
Click to collapse
Yeah I noticed a combination of touches triggers the ghost touch on call of duty, I could also be having the combinations trigger ghost touches in other game but I need to test more
Related
Am I the only one having really poor touch recognition on my A43? Whether I use a finger or stylus, it often happens--about once in five keystrokes or more--that after releasing the touch on an on-screen keyboard, a different key additionally gets registered, sometimes not even a neighboring key. It is very hard to type in a password.
My touchscreen also has this problem. I'll hit one key and it will add another key somewhere entirely else on the screen. Menus will spaz out when I try and scroll through them.
Oh yeah, remember that problem I was having where strange spots showed up on the screen and I had to get it RMA'd? That came back on my BRAND NEW unit. I'm getting sick of the crappy screen on this otherwise great unit =[ Maybe Archos will just give me a refund and I can spend my funds on an unlocked/off contract phone with similar specs.
Sadly, I think this is a hardware issue. I'm not sure there's anything firmware can do besides ignore half of the inputs. But then, you have a non-responsive issue ...
Have you guys tried to calibrate the screen through SDE?
I have a similar issue with my A101, although it's not as bad as you guys describe - sometimes the screen just won't register my touch at all, mostly in the edges of the screen - sometimes I think it's the calluses on my fingers from playing guitar, sometimes I think it's the horrible screen they gave us....
My $0.02
So does anyone not have this problem with an A43?
wokker666 said:
Have you guys tried to calibrate the screen through SDE?
I have a similar issue with my A101, although it's not as bad as you guys describe - sometimes the screen just won't register my touch at all, mostly in the edges of the screen - sometimes I think it's the calluses on my fingers from playing guitar, sometimes I think it's the horrible screen they gave us....
My $0.02
Click to expand...
Click to collapse
You might be having better luck because the A101 has a capacitive screen with multi-touch capabilities. They're known to be more reliable than the resistive screens the 43IT's have.
arpruss said:
So does anyone not have this problem with an A43?
Click to expand...
Click to collapse
I have a 43IT, which is why I posted Sorry I wasn't clear. I feel your pain. Also, I suggest using your nail or a stylus, as the pinpoint hardness of either are better than the soft, blob your fingertip makes on the screen sensor array.
ddukki said:
I have a 43IT, which is why I posted Sorry I wasn't clear. I feel your pain. Also, I suggest using your nail or a stylus, as the pinpoint hardness of either are better than the soft, blob your fingertip makes on the screen sensor array.
Click to expand...
Click to collapse
I generally use a stylus. The problem is probably due to the way the plastic digitizer flexes which generates ghost movement data on release. A glass digitizer would be much better.
By the way, it is possible to ameliorate the problem slightly in software. I did that in the myKbd app for PalmOS. Basically, you filter out some very rapid motions. It doesn't affect sensitivity in any significant way.
The reason I'd like to know if everyone has this problem is because I'm going to send my A43 in for warranty repairs, and I am wondering if I should include this problem (in addition to the annoying bright 1/4" area on the screen, and the occasional timeouts when writing to internal flash that result in the device hanging).
Hi all, sorry my first post is asking for help, but I'm lost on this one.
It doesn't happen all the time, but I randomly get a dead spot on the bottom right corner of my phone.
It happens when I touch the app drawer, and the L key when I'm texting. It only randomly acknowledges I touched the screen.
Restarting the phone usually helps, but does that mean it's software or hardware?
Should I have it replaced?
Stock VZW Note II, no apps installed.
Ty for any and all help.
-edit-
It was replaced for a bad digitizer.
When using Multitouch visibility test, if you put more then 4 fingers on the screen, it locked up the phone requiring removal of the battery.
Perhaps instead of software, could it be heat?
It sounds like a dead/dying pixel to me. If it is only there on certain screens, then probably not, but if its there on say the boot screen or something, then I'd take it back.
silhet ingliil
I'm sorry I should have been more specific.
It's not a screen blemish.
It's when I go to tough the screen.
Like if I hit the L key on the keyboard during a text message, it will only register a touch like 50% of the time.
Or if I touch the app drawer, I have to hit it multiple times to open it up.
The actual screen is perfect, no dead or stuck pixels at all.
LiTDiE said:
I'm sorry I should have been more specific.
It's not a screen blemish.
It's when I go to tough the screen.
Like if I hit the L key on the keyboard during a text message, it will only register a touch like 50% of the time.
Or if I touch the app drawer, I have to hit it multiple times to open it up.
The actual screen is perfect, no dead or stuck pixels at all.
Click to expand...
Click to collapse
I'd return to Verizon, especially if you're not rooted so it won't be any trouble returning to stock etc.
It's probably mildly annoying to you now and it's only going to get worse over time. If there's no physical damage to the phone I don't see them giving you any trouble.
phind123 said:
I'd return to Verizon, especially if you're not rooted so it won't be any trouble returning to stock etc.
It's probably mildly annoying to you now and it's only going to get worse over time. If there's no physical damage to the phone I don't see them giving you any trouble.
Click to expand...
Click to collapse
No damage at all, and I actually went through 3 screen protectors before I figured out it wasn't them.
Kinda bummed I have to drive 45 miles to return this damn thing though.
LiTDiE said:
No damage at all, and I actually went through 3 screen protectors before I figured out it wasn't them.
Kinda bummed I have to drive 45 miles to return this damn thing though.
Click to expand...
Click to collapse
You don't. Call VZ and they will ship you another and give you a prepaid box to ship the old one back in.
TonikJDK said:
You don't. Call VZ and they will ship you another and give you a prepaid box to ship the old one back in.
Click to expand...
Click to collapse
I actually called them, and they told me to just take it back to the store in case the replacement has issues.
Which is troubling to hear.
I have a youtube video demonstrating the problem, but I won't let me post it so ohwell.
Will have to wait til I get 10 posts.
Basically, using multitouch visibility test, I roll my finger around the bottom right corner while never lifting it off, and it won't recognise my trying to touch the specific spot.
After I life my finger and move it around the screen it will recognise the spot. It's very random.
Here's the video.
http://www.youtube.com/watch?v=SGl9RoBLpjA
-edit-
The youtube tags aren't working?
So what do you all think?
Hardware or software?
After further messing around in Multitouch Visibility test, I can replicate this all over the screen, but it's easiest to do at the bottom right corner where L shows up on the keyboard.
Do u have a case with any magnets on it?
Sent from my SCH-I605
Jay A whY said:
Do u have a case with any magnets on it?
Sent from my SCH-I605
Click to expand...
Click to collapse
That would only affect the S-Pen, from what I understand.
Jay A whY said:
Do u have a case with any magnets on it?
Sent from my SCH-I605
Click to expand...
Click to collapse
Nah, it was a bad digitizer they said.
Whenever you put multiple fingers on screen, it would lock up, and require yanking the battery to reboot.
When you notice this are you holding the S-pen? I noticed if you get the pen near the screen (close enough for air hover to work) that the screen and buttons quit working to touch. For a little while I thought the home button was having problems, turned out the way I was holding the pen would result in it being placed near the screen when I hit the button.
Wyatt W.
edit:see this was taken care of
wyatt57350 said:
When you notice this are you holding the S-pen? I noticed if you get the pen near the screen (close enough for air hover to work) that the screen and buttons quit working to touch. For a little while I thought the home button was having problems, turned out the way I was holding the pen would result in it being placed near the screen when I hit the button.
Wyatt W.
edit:see this was taken care of
Click to expand...
Click to collapse
The main reason I noticed it was when I was texting.
Whenever I went to type words like sleep, or talk, they would be missing the letter L.
Or when I would go to open the app drawer, and it would only work half the time.
All while the pen was in the phone.
The lockup doesn't sound normal but as far as dead spots if you have a screen protector on have you tried removing it? Marginal screen protectors will cause touch input issues.
The touchscreen on my Verizon G3 started acting up recently. In the lower portion of the screen there's a space where it doesn't register my touches well (take a look at pics the space in between the lines don't really 'register' my touches. You can see in the second pic I'm currently touching the part where its not really working and it looks like I'm touching the screen with two fingers even though I'm only using one). When I type sometimes two letters are pressed at the same time or its like I didn't touch the screen at all which makes typing difficult and takes a lot of time. The whole screen sometimes doesn't hold a touch, like I tap and hold but it only 'holds' like I only tapped the screen. Other times when I'm sliding my finger across the screen, it starts jumping around. Now the top row of the keyboard/screen doesn't even register touches anymore so can't really do much now. I've reset the phone and didn't fix anything. Is this something LG would fix if I sent the phone in? If so how long is turnaround and will I have to reset it back to stock/unroot it?
if you have any type of glass screen protector on, take it off and verify the issue.
some tg screen protectors are junk, and have caused issues like this.
bweN diorD said:
if you have any type of glass screen protector on, take it off and verify the issue.
some tg screen protectors are junk, and have caused issues like this.
Click to expand...
Click to collapse
I had a $5 glass screen protector on it from ebay and thought that was the problem but when I took it off the problems ensued
Some g3s do have or develop touchscreen issues. Check under the back cover that there is nothing putting pressure on the display from behind, like a swelling battery.
It is probably a warranty issue, though.
Sent from my VS985 4G using Tapatalk
Sometimes if my G5 has not been used for an hour or so, it is refusing to wake up from double tap, power button or volume button quick shortcut. Only plugging it in has seemed to wake it up on these occasions.
Has anyone else had this issue?
Not yet.
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Same problem, same case.
What I have found is if you pull the phone out of the case it wakes up. Thinking proximity sensor.
Sent from my LG-H830 using XDA-Developers mobile app
Yup. It really doesn't take much extra coding for them to allow the power button to "Always Wake" the device... I imagine there will be an update in the near future.
As for me... jumping ship to the S7 edge. I really liked the G3, and was hoping this phone could have been that for me... Well, not like I really swap batteries out often anyway
Same case. Same issue. Take the phone out of the case and throw a blanket over yourself and the phone. (Simulating night) and my screen unlocks easy peasy. Something about this lifeproof case. You would think this issue would have been caught in testing and QC.
Yes the phone has a built prox. override. But it only becomes an issue at night. Outside of the case I have no issues with prox. sensor.
I have experuenced this exact same issue with my g5. Whenever its in the dark the power button nor the double tap will wake the screen when in the lifeproof fre case. When out of the case the phone works just fine.
Word to the wise though if you have a zagg glass screen protector and drop your phone both the screen protector and the screen with shatter even if in the lifeproof case. I just experienced this and now have a replacement phone. Just a heads up.
soninja8 said:
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Click to expand...
Click to collapse
I have the rs988 variant and I have noticed this behavior when screen is in always on mode: if I suddenly change from light to dark by covering sensors, the always on clock goes out and nothing I do will allow it to wake up, until I allow brighter light again and the clock reappears. and I can use the double tap and power button again to see the screen. I also notice that the always on clock seems to have an auto brightness independent of the screen settings - I leave screen at 50% no auto brightness, yet I still see clock light levels dim in low light, One other thing - I notice that when I answer a call the screen blanks out (the way it is supposed to ) but does not reappear until I press the power button, just taking away from my ear does not bring display back; I also have the lifeproof case. and just removed it and verified my display now works when I take away from my ear; I just took some spray lens cleaner and cleaned all the surfaces of the phone and case with a microfiber cloth and put it back together and has vastly improved the issue, maybe gone, not sure yet. Update: seems like no matter how clean it is there is still a problem with the case doing something to the proximity detector, cleaning made it better. I can always wake up with the power button for the calling screen(sometimes swiping across top sensor too), wonder if the sensor is a passive light sensor or active (rf/infrared emission)
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
There are allot of other cases you can use but not waterproof. That really sucks good thing for this thread I was going to buy a lifeproof case. Using a otterbox defender right now. Thanks for the post guys saved me some grief.
still under warranty?
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
if still under warranty, see if they will honor it. They did with mine but that was right at the beginning when these problems were linked to the case; mine was in the first 3 months, but the new one worked well for a while, now a little flakey again but not enough to bother me...too bad, a great case otherwise
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
It's not a bug and not poor implementation. Its not light for "dark rooms" lol.. As far as I know it's the proximity sensor. When it is blocked it means the phone is in a pocket or bag and should not register taps. It really makes sense. If you dont xover the sensor and double tap doesn't work ..well.. Well, eother you have defective device or sensor , or the sensor is blocked (maybe bad screen protector?). This didnt happen with my G5 even once. It works 100% (assuming I tapped the same place)
Are the problems as described in this thread still manifesting on current firmware?
I've bought a used S9+ like 3 days ago and run a QA test inside the phone. The screen was fine and it responds normally, however after 2 days I couldn't use a keyboard because of its issues while typing. Basically, when I'm typing a longer sentence, I have to either slow down or sometimes press a button 3-5 times for it to respond. It stared to occur yesterday and I don't know if that's the touch control issue or something with the display. P.S. I've tested it on Gboard, Samsung keyboard and Grammarly keyboard, all with the same issue.
Is there any fix I can do without paying for a new display? It will cost me the same amount of money as the phone itself.
Thanks!
Are you using a screen protector? If not, try it. Maybe touch sensitivity is turned on in display settings, try changing it to see if it's better. I've noticed that on some screen protectors, they retain a lot of humidity so I have to constantly clean the screen to get rid of "ghost touches"
ShaDisNX255 said:
Are you using a screen protector? If not, try it. Maybe touch sensitivity is turned on in display settings, try changing it to see if it's better. I've noticed that on some screen protectors, they retain a lot of humidity so I have to constantly clean the screen to get rid of "ghost touches"
Click to expand...
Click to collapse
No, I don't use any screen protectors. My phone has a Spigen case, which is slightly over the screen both at top and the bottom. I tried to turn on and off touch sensitivity and it didn't help. Funny part is that it sometimes stops and goes again.
Had this myself, especially with the space bar ?
Same here, have to press space up to three times (intermittent issue). Screen protector on, sensitivity does nothing.