Touch input temporarially stops working until after phone goes to sleep - G3 Q&A, Help & Troubleshooting

Sprint LG G3, the 990 version. Stock ui.
So yesterday this all started. The touch sensor suddenly stopped registering inputs. From my testing on it (this problem has happened dozens of times since yesterday afternoon) eventually after a few minutes of use the input will just stop working, but the phone functions still work. Videos and games continue to play, phone and video calls still keep running properly, and the home screen clock will keep running while the touch input is disabled. I can volume up and down, but cannot interact with the screen. The power button will not put the screen to sleep.
Eventually the screen will timeout, now I can interact with it again. I hit the power button like normal, and get a vibration, then the screen turns on and I get the dialog box to turn off or restart the phone over my lock screen, as if I long-pressed the power button. I can click away from this and start using the phone again like normal.
But it will happen again. I can get a few minutes of use usually before the touch input disables itself again.
I didn't download anything recently. I did disable notifications for my LINE app yesterday through the app drawer, but after this started I reverted that, just to be sure. Some apps might have auto updated, but this is happening in any app I use.
I have looked around lots of places, but can't find anyone else saying they have this particular problem. Any idea what is going on and how I can troubleshoot this short of trying a factory reset?

superbelt said:
Sprint LG G3, the 990 version. Stock ui.
So yesterday this all started. The touch sensor suddenly stopped registering inputs. From my testing on it (this problem has happened dozens of times since yesterday afternoon) eventually after a few minutes of use the input will just stop working, but the phone functions still work. Videos and games continue to play, phone and video calls still keep running properly, and the home screen clock will keep running while the touch input is disabled. I can volume up and down, but cannot interact with the screen. The power button will not put the screen to sleep.
Eventually the screen will timeout, now I can interact with it again. I hit the power button like normal, and get a vibration, then the screen turns on and I get the dialog box to turn off or restart the phone over my lock screen, as if I long-pressed the power button. I can click away from this and start using the phone again like normal.
But it will happen again. I can get a few minutes of use usually before the touch input disables itself again.
I didn't download anything recently. I did disable notifications for my LINE app yesterday through the app drawer, but after this started I reverted that, just to be sure. Some apps might have auto updated, but this is happening in any app I use.
I have looked around lots of places, but can't find anyone else saying they have this particular problem. Any idea what is going on and how I can troubleshoot this short of trying a factory reset?
Click to expand...
Click to collapse
Boot.into safemode i cant remeber the key sequence google itll disable all 3rd party apps then if it work u know its in a app
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
Further more if it does not help then a factory restore is in the pic. Then of that dont work try restoring stock tot.kdz method and flash tool it is possible for system to corrupt files and reset still not fix.
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Are u root ed stock rom cm kernals ?

TheMadScientist420 said:
Boot.into safemode i cant remeber the key sequence google itll disable all 3rd party apps then if it work u know its in a app
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
Further more if it does not help then a factory restore is in the pic. Then of that dont work try restoring stock tot.kdz method and flash tool it is possible for system to corrupt files and reset still not fix.
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Are u root ed stock rom cm kernals ?
Click to expand...
Click to collapse
Hey, thanks for the reply. So I did what you said. I ended up doing a factory restore of my device.
I have had this phone since about a month after it was released two years ago. I rooted way back then, did not install any rom over it yet... and then a few weeks later my kid went and clicked through a software update one day and removed my root, so I just left it go.
Anyway, I did the full factory reset, and started setting my phone up again, and a couple times the problem resurfaced. No apps from the store yet installed, the phone just stopped responding to any touch inputs. I wait for it to go to sleep, and then wake it up to use it again.
This sucks, I guess this is forcing me to upgrade when the G5 releases. But any ideas still? I dread being stuck with the phone being buggy like this for another two months or so. It's not app related, it doesn't SEEM to be hardware based, since everything works perfect up until it just locks up. The problem happens with different batteries I use. There doesn't appear to be any physical damage to the phone at all.

Related

[Q] Updated to stock JB - Now phone freezes/crashes

Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Castaway78 said:
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Click to expand...
Click to collapse
This sounds somewhat familiar to my experiences with JB. I rooted right away with the stock JB and had freezing / crash issues. So I then went pure stock and had issues (un-rooted). I then tried a custom TW-based ROM called BlackJelly and had issues. Now I am on CM10.1 which is AOSP JB4.2.1 based and things are even worse.
There seems to be no JB ROM that is stable for my phone. Getting very tired of this.
See my thread for details:
http://forum.xda-developers.com/showthread.php?t=2044769
- Ed
Strangely enough, my issue ended up going away. I think it was a rogue program that needed it's dalvik cache rebuilt. Once uninstalled, the phone worked great. Not sure what app it was.

Screen timeout setting won't stick

I set my screen timeout setting to "Keep Screen Turned On" but it keeps resetting to "30 seconds". It happens every day, but so far I haven't been able to nail down what's causing it. The setting survives reboots. I thought I had narrowed it down to RocketPlayer, because I started launching the apps I use most and then checking the setting after each one and it changed after I launched RocketPlayer. However, I can't make it duplicate that behavior.
Any ideas on how to figure this out? I installed LogCat Extreme, but I'm not seeing anything obvious in there. Then again, I'm not too familiar with using LogCat apps anyway, so maybe I'm not looking for the right thing?
Found this entry in the log:
ActivityManager: Killing 10126:com.lge.lockscreensettings/u0a108 (adj 15): empty #17
Could that be the issue? If so, how do I fix it?
Well, I narrowed down the problem to the "Screen Off and Lock" app that I was using to restore the double-tap screen off functionality that I had lost when I switched to Nova. I restored a Nandroid from before installing that app and my screen timeout settings stay as they are set with no problem. I've written to the dev to see if they can find a fix. In the meantime, I am using a Screen Lock widget from Extended Controls . It's not as slick, but it's better than using the power button every time.
If anyone has a suggestion for an alternative app, I'm all ears!
Turns out Screen Off and Lock wasn't the problem. It's still doing it intermittently despite not having this app installed. Any thoughts or suggestions great appreciated!
Use titanium and wipe data for the lock screen settings and it has seemed to work. I mean it works for sometime but then you have to redo it I don't know why it is like this it has been like this since I bought the phone
---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------
I also have problems changing the lock screen wallpaper to anything that does not come preinstalled on the phone. This solves that as well. Temporarily.
I ended up getting an OTA and having to go back to stock. This time when I rooted and BUMP'd, I made sure to disable OTAs and then make a clean nandroid backup in case this behavior starts up again. I'm pretty sure it was from something I had installed or possibly from a conflicting setting in an some of the Xposed modules I was using.
Since the reflash, I haven't had any problems with the timeout setting staying where I put it.
Thanks though!

Fingerprint sensor not working occasionally

I've been recently getting some instances where I would lock the phone and the fingerprint sensor won't respond to my finger.
This really started when I changed my lock to pattern swiping. Anyone have the same issue? I rebooted and changed it back to pin lock and it seems to be working all the time again, but I don't know what caused it in the first place.
Thoughts?
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
jbdan said:
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
Click to expand...
Click to collapse
It's not that it doesn't recognize my fingerprints, but it doesn't recognize fingerprints in general. So when I put my finger on it, it doesn't do the double buzz, it's just non responsive.
this happened to me yesterday several times. And i received phone yesterday... . I have two prints. Left and right index fingers. It didnt fail, just was as my finger wasnt in the reader
MDB08L
experienced the same thing this morning. phone was plugged charging and finger print would not detect, had to manually hit the power button then it worked. i find there are a lot of issues when the phone is charging though, screen sometimes becomes very unresponsive while charging. i think there was a similar thread about that as well.
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
ajmalott said:
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
Click to expand...
Click to collapse
Any luck? I did a system wipe after unlocking, and flashed new factory images but still happening.
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
ajmalott said:
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
Click to expand...
Click to collapse
I was able to find a bit more about this issue. When it happened again, I pressed the power button and quickly checked the fingerprint icon at the bottom of the lockscreen and it turned red and said "fingerprint hardware not available" for a split second before turning white again. I searched that error message and got this thread https://www.reddit.com/r/nexus5x/comments/3pm3lv/fingerprint_hardware_not_available/
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
jadesocket said:
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
Click to expand...
Click to collapse
I'm not much of a tinkerer, but I'll give this a shot. If it clears it up then okay, but if it happens again I'll probably RMA too. Not willing to put up with such inconsistencies on a brand new phone with such a highly touted feature.
Unrelated, this is actually already my second Nexus 5X. The first one I received would not take a charge, and I didn't have another USB Type-C cable to test, so they sent me an entirely new package. If wiping cache doesn't do it, I'm really not sure if I should bother with a third Nexus 5X. Kind of disheartening. I really enjoy the device otherwise.
So far so good for me, Let me know how it goes for you!
jadesocket said:
So far so good for me, Let me know how it goes for you!
Click to expand...
Click to collapse
Still happening today.
ajmalott said:
Still happening today.
Click to expand...
Click to collapse
That's a bummer. It actually happened again today for me too.
jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
ajmalott said:
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
I had hope Looks like RMA imminent for me. I put that glass screen protector on so well...
ajmalott said:
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
Lots of apps updated in the past week. The problem hasn't resurfaced for a whole 48 hours now. Hoping I can put this behind me
jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
It happened to me too, stock phone, no third apps installed. I will keep an eye on this.
off-topic: the discoloration of the back of the phone it's very bad!
ajmalott said:
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
Click to expand...
Click to collapse
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
jadesocket said:
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
Click to expand...
Click to collapse
Did a factory reset, and the problem came back almost immediately. Google tech support wanted me to reinstall OS entirely, but I don't have the right cable (type C to type A) to hook up to computer, so they just gave RMA. Got the new one on Friday, so far so good. But then, with the last phone, the issue didn't appear until after a week or two. Fingers pressed. Tech support really seemed to take my case as a rarity, and they were unable to recreate it with their own device. Here's hoping it's just limited to a few devices.
P.S. Off topic, but Google support wouldn't give me anything for the Black Friday deal. I asked multiple times in multiple ways. Oh well.

Upgrade to Nougat already? Hows it working for you?

For those who have upgraded already, how did the upgrade process go and how are you liking it so far?
This is a big upgrade and I'm nervous about pulling the trigger until this is vetted out a bit.
Chris
The process went well. I had to play with the display resolution and zoom to get things looking right. I had to re install my theme store theme to get it back. Other than that, it runs great. Only a few apps not compatible with n. But I have like 400 apps. So not bad! Oh yes, I did need a couple of reboots too.
Sweet! Well... having to go five steps back first was a PITA but when finished (and thank God for the Samsung Cloud Backup System - I had just done a backup three days before this project and it saved my arse!) Once I finished the AT&T OTA of QB2, I did a Restore from the Samsung Cloud and the phone looked EXACTLY like it had with Nougat PL4! Desktop, Apps, (most) settings... awesome!
Going good, process went smooth. I'd just say plug up and stay plugged during upgrade
Just did the upgrade. I have to say guys, this was BY FAR the smoothest stock upgrade I've ever experienced from Samsung. They did a nice job on this.
I'm just running into the issue of UI Lag. The update went smooth enough though. I will also say I am having issue with video playback in chrome if I flip to fullscreen then the ability to control the video is gone and i cant minimize it i have to hit the home key to get out of the video.
I just finished installing QB2. Everything works smoothly except one annoying bug. The Activity Zone app launch not in full screen. It's like 70% of the screen. I tried to change the display resolution but the same.
Anyone having the same issue?
snugroho3 said:
I just finished installing QB2. Everything works smoothly except one annoying bug. The Activity Zone app launch not in full screen. It's like 70% of the screen. I tried to change the display resolution but the same.
Anyone having the same issue?
Click to expand...
Click to collapse
No, mine launches full screen!
---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------
CFoote said:
Just did the upgrade. I have to say guys, this was BY FAR the smoothest stock upgrade I've ever experienced from Samsung. They did a nice job on this.
Click to expand...
Click to collapse
DITTO!
jimd1050 said:
No, mine launches full screen!
---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------
DITTO!
Click to expand...
Click to collapse
Yes, it launch in full screen but the content of the app is not. Please see attached picture. Do you have the same?
It was full screen in marshmallow
That is quite strange, my Activity Zone is full screen, do you have your Zoom function under "Display" set to small?
Upgrade went smooth , i did it manually and not OTA , all working good with good battery life.
What i did is as follows :
1- Odin the PI2 as a base line
2- Then via recovery from the device I used "update from SD card" and upgraded to PK2
3- Then i did it again via recovery from the device I used "update from SD card" and upgraded to QB2
Download the needed files from the following thread
https://forum.xda-developers.com/s7-active/how-to/s7-active-sm-g891a-ota-updates-firmware-t3540866
I updated to the BQB2 build via OTA about a week after it became available. I'm generally pleased with it, but there are a few things here and there that make me think that perhaps I'm due for a factory reset and start over.
Battery life is slightly down for me, which doesn't match up with reports I'm hearing from others. It's not much lower, but it's noticeable.
UI seems to be slightly more 'laggy'. Reduced the animation scales in the dev options to compensate. Maybe because I was running 'Good Lock' when the update happened?
Seems like wifi connection is not 100% stable. I see the notification bar 'flicker' from time to time, and it keeps re-posting the notification about what network I'm connected to.
Seems to get warmer while charging wirelessly, to the point that it pauses the wireless charging. But, this is in a cradle in my car, with Waze running, and it's warmer than it had been for a few months so not really sure if the update is involved in this or not.
Probably one or two other smaller things that I'm not thinking of at the moment. Obviously they weren't showstoppers, since I can't recall right now.
I like that they included the mobile hotspot toggle again (finally!), but they still don't have a 'mobile data' one. System UI Tuner is still gone, although I've read some people think that's the case with Nougat in general, so not sure.
All that being said, it updated to the BQC2 build today. The wifi thing seems to be resolved, despite this being only a 'security update'. I'll let it shake out for a few days or so and see if I still think it's worthwhile to start all over.
Went smooth for me, took literally less then 2 minutes.
All my apps/settings are working flawlessly and I experienced no issues thus far.
I updated to Nougat since it was released and I can't say I'm happy. Battery looks slightly worse and at least 1 or 2 twice a week my phone slows down getting almost unresponsive. I have to restart it.
That never happened with Marshmallow. I'll try it for one more month and if not I will go back to Marshmallow. Is that still possible?
That is a good question. I know that with small version upgrades the phone keeps the original version stored for a full wipe, but on a big OS upgrade I am not sure. Hopefully someone will know. I want to say yes it can be done.
Im on QD4, loving Noguat at how quick it is. But, i hate how all the menus and settings are all bunched and i have use search to find basic things.
I actually am having some issues with my s7 active I installed the 7.0 update a few months back and never looked back because the 7.0 stock rooms great no issues except recently last week's my phone started rebooting on its own . I though no biggie cause it did every once in a while , but now it has greatly increased . What happen was it froze on Facebook messenger app when I was trying to reply to a message and would not unfreeze so I had too force restart it that is when the problems really begun. The moment I force restarted it and it rebooted and i got into hone screen i keep getting notifications that apps were crashing over and over and the phone decided to restart on its own and keep doing the same thing . So I was like wtf maybe it's a app or something so I decided to do a factory reset and clear cache and rebooted the phone looked like that fixed the problem for a whole 2 minutes then the crashing of apps and random restarts . I was tired so.i was like ok I just turned the phone off and notice that it was kinda warm and decided to go to bed and mess with it tomorrow . So when I woke up I booted the phone up and it was acting normal no crashing or anything no reboots but after 2 hours it randomly started rebooting and sometimes the apps crash bit currently the phone is working but i get random freezes and reboots all day . I have tried searching for a solution but no luck. Some people claim its a app but when I have no apps Installed and it still does it its not a app problem . Some people say it could be the mother board flus faulting out or bad battery can't send it in for repair cause I bought the phone off eBay. Is anyone else having these issues and know of a fix maybe thanks sorry for the long post.
Upgraded to BQB2 a week ago, I am very happy with everything, it's smoother, faster and manages RAM better (well I was Rooted on 6.0.1 so it was laggy) all my apps work perfectly and I've disabled many things with Package Disabler Pro, I've been testing running music, google maps chrome, whatsapp, messenger, face all at the same time, very smooth BUT I must say it does drain battery much faster than before.
Now my phone wont make it through the day, it even drains on standby, I've already flashed 7.0 twice and wiped cache, I'm still, thinking if I will keep this or go back to 6.
Yesterday alone, my battery went from 89% at 1:30am to 52% at 10:30am, only on standby. When I check Battery use my com.android.systemui is the one eating up most of it, I even set my resolution low to HD. If anybody has a solution, any help would surely be appreciated, I don't wanna go back to Marshmellow, but if I must......
Upgraded and everything was fine apparently, then I saw the huge battery drain, tried averything I found and decided to go back to marshmallow.
KGB7 said:
i hate how all the menus and settings are all bunched
Click to expand...
Click to collapse
Can you please provide screen shots?
There are 2 more ups after QD4 (side load), I need to know if I should be prepared to go that far if I proceed with QD4.

Home screen Looping Turns Off On It's Own

Anyone had this happen. Mine does it every few days and I have to go into home screen settings and toggle the switch back on. It does it on my wife's phone also. I saw in a Reddit thread a few people having the same issue. Have also had the issue where I can't use my fingerprint to unlock my phone and have to use my pin like the phone rebooted but it didn't. Not sure if the 2 issues are connected because I run into them at different times.
truckerdewd said:
Anyone had this happen. Mine does it every few days and I have to go into home screen settings and toggle the switch back on. It does it on my wife's phone also. I saw in a Reddit thread a few people having the same issue. Have also had the issue where I can't use my fingerprint to unlock my phone and have to use my pin like the phone rebooted but it didn't. Not sure if the 2 issues are connected because I run into them at different times.
Click to expand...
Click to collapse
Are you sure that the SystemUI crashes?
LameMonster82 said:
Are you sure that the SystemUI crashes?
Click to expand...
Click to collapse
Nothing crashes, it just randomly turns the home screen looping off.
Same issue here
My LG G7 is doing that, too, as is my daughter's. I'm guessing it's an app that has access to modify system settings, so I am going to remove permissions to modify system settings to a couple apps. I'll give a little time and see if that works. If not, I'll try a couple different apps. Maybe I'm on the wrong track, but since there aren't any other solutions out there...
This happens to my G7 and my daughter's Sylo4. Did you ever fix the issue?
Tje31483 said:
This happens to my G7 and my daughter's Sylo4. Did you ever fix the issue?
Click to expand...
Click to collapse
Seems like the only fix is to go into home screen settings and turn it back on when it turns itself off. Sorry, I know it's not an actual fix. It has to bee some sort of bug.
I'm beginning to think there is a flaw in the software. Seems like there are a lot of things that happen randomly with this phone - wifi shuts off, wifi calling will drop mid call, keyboards reset sizing, random reboots, the screen looping thing you mentioned. I'm sure there are many more too
---------- Post added at 02:23 PM ---------- Previous post was at 02:14 PM ----------
I'm beginning to think there is a flaw in the software. Seems like there are a lot of things that happen randomly with this phone - wifi shuts off, wifi calling will drop mid call, keyboards reset sizing, random reboots, the screen looping thing you mentioned. I'm sure there are many more too
OnceAMatrixMan said:
I'm beginning to think there is a flaw in the software. Seems like there are a lot of things that happen randomly with this phone - wifi shuts off, wifi calling will drop mid call, keyboards reset sizing, random reboots, the screen looping thing you mentioned. I'm sure there are many more too
---------- Post added at 02:23 PM ---------- Previous post was at 02:14 PM ----------
I'm beginning to think there is a flaw in the software. Seems like there are a lot of things that happen randomly with this phone - wifi shuts off, wifi calling will drop mid call, keyboards reset sizing, random reboots, the screen looping thing you mentioned. I'm sure there are many more too
Click to expand...
Click to collapse
I ended up going back to the Galaxy S9 cause I got tired of the weird. LG issues. I had bluetooth issues with both the G7 and the V30 where they would randomly disconnect during a phone call which sucks, especially when you're on an important call with your doctor and it disconnects bluetooth while you're on the interstate

Categories

Resources