Related
Hello,
I am posting here in hopes someone has the wisdom to help me in solving this issue, because I have barely found anything on this forum, the G4 subreddit, etc.
When I first had my LG G4 everything worked perfectly: no bootloops, no camera issues, it was occasionally sluggish but I just changed the launcher to fix it. After about a month ago, my Pokemon Go app started having connectivity issues so I reset the phone to factory default settings. This reset fixed those connectivity issues, but now the glance view feature doesn't work 98% of the time. Specifically, if I attempt to "pull" from the top of my screen on my lock screen, it never works; once or twice I've seen it appear for a brief second when I was cleaning my phone with a cloth. The odd thing is my knock to wake still works and I can still pull notifications from the screen when the phone is unlocked.
Things I have attempted to resolve this problem:
changing lock screen types
resetting the phone to factory defaults and trying the glance view from stock after the reset
varying "pull" speeds to try to get the glance view to show
re-cleaning the screen
I'm kind of just trying to get this feature to work again. I do have a screen protector on, but I have had it on since the day I got my phone. I have the LG-H811 model with Android 6.0 SW version H81120p. Any tips would be appreciated.
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
andygold said:
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
Click to expand...
Click to collapse
By any chance are you using VZW Messenger?
I'm having the same issue with the fingerprint sensor. The only workaround I've found is to reboot the phone, then it will start functioning again for a little awhile. Very bizarre.
I also recently started having issues with the fingerprint scanner. Since a lot of people have this issue I'm starting to think it is software related.
andygold said:
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
Click to expand...
Click to collapse
By any chance are you using VZW Messenger? It was an update to VZW Messenger that caused the issue for me. Next update resolved it.
OnceAMatrixMan said:
By any chance are you using VZW Messenger? It was an update to VZW Messenger that caused the issue for me. Next update resolved it.
Click to expand...
Click to collapse
I do have Messenger on the phone. It is NOT set as my default messaging app as I do not like it. Only reason I have it is because too many of my colleagues send me messages through it, which I can't open any way else that I know of. I'll look for an update and see if that helps. If not, I'll delete it and check again.
Thank,
Andy
Last update to Messenger I have is from April 9th. I looked for a more recent update but no luck.
Just deleted Messenger, and rebooted. After the initial need to enter the knock code, I slept the phone by tapping the power button (sorry if my terminology is off). 4 different fingers then and no joy (from the sleeping phone). If I hit the power button, the screen lights up and leaves me at what I guess is the lock screen showing recent email and calendar events. From there, I can successfully (still about 95% of the time) use the fingerprint sensor or the knock code to unlock the phone. But from a screen-off, sleeping mode, the fingerprint is still in a maybe it will work, maybe it won't situation.
If I have the same problem for about two weeks approximately install youtube vanced and yowhatsapp I do not know if it will be that but it is very annoying I hope lg update soon but I do not think I have the Indian version
Have same model and had same issues. I recently found out that I was missing 3 updates. December update started these issues. I'm now on the 10j version and so far haven't noticed the issue. But it's only been a day or so.
redbar0n11 said:
Have same model and had same issues. I recently found out that I was missing 3 updates. December update started these issues. I'm now on the 10j version and so far haven't noticed the issue. But it's only been a day or so.
Click to expand...
Click to collapse
I am also on 10j, and the issues are still there in regards to the fingerprint sensor....although for some unknown reason, after weeks of no WiFi at work, my phone finally decided to hook up to my work WiFi yesterday afternoon, and this morning when I got into work it instantly hooked up to it again. So, hopefully the WifI issue has been rectified. I guess I should somewhat count my blessings as WiFi is more important to me than fingerprint sensor, in the big scheme of things!
There has to be a software/firmware issue going on though as the sensor seems to be most troublesome when the phone is sleeping. Once the lockscreen is on, although there are still issues, it works 95% of the time. That makes me believe it's not a hardware issue.
I have Verizon also. It may help if all of you download the latest kdz for Verizon and reflash it vs factory reset. Using the lg up method by lamemonster. I do it all the time when I cross flash kdz as well as flashing back to Verizon. Hope this helps.
My G7 EAW is the same, fingerprints flicker. However, I removed the back cover and corrected the fingerprint, and it worked normally
netookska05 said:
I have Verizon also. It may help if all of you download the latest kdz for Verizon and reflash it vs factory reset. Using the lg up method by lamemonster. I do it all the time when I cross flash kdz as well as flashing back to Verizon. Hope this helps.
Click to expand...
Click to collapse
can you link to or specify that exact flashing method? nothing works for me, second piece of new hardware, no results.
Hello all,
It seems i have a issue with my 6 month old Galaxy Watch 46mm, 1 week after the ONE UI update, all sensors (accelerometer, gyro and HR sensor) stopped working, only the ambient light sensor was working.
So i had no more step counter, turn your wrist to wake the screen (the one i missed the most), HR monitor, nothing.
After couple of restarts, 3 factory resets and waiting for 2 days, all sensors started working again.
Everything was fine for 1 week.
And now since 3 days ago the issue reappeared. no restarts, factory resets, hard restarts helped, till now.
What I noticed is if the Watch is powered OFF and charging the screen rotates accordingly, but if it is powered ON, the screen remains in the same position as it is on your hand, it does not turn 90 degrees.
So for me it seems to be a software/firmware bug.
Does anyone else have this issue?
How did you solve it?
Thanks
Hi,
i have similar problem on my GWA (SM-R500).
Now its four days and many restarts/Factory resets since my sensors died...
I was on Vacation/camping when my last HR reading history shows it happens while sleeping... I've noticed this next day when going for a walk and no notifications go to my watch (i've set to send notifications to watch only when wearing and not using phone). Then noticed that HR sensor is not blinking (set to always on). So i've tried to switch on manual and it starts measuring but in the end shows a "generic" error message (Can't read, try again) - no "dirty sensor" or similar messages... https://www.youtube.com/watch?v=9zo4pOisX_k
Now when i'm at home and searching for help and found this thread. So i've edited my Watchface to test other sensors (accelerometer, gyro) and they dont show any movement either...
I've tried even switch different options in the menus (like detecting workouts, sensors authorisations, etc) what i've found that helped others, but no avail...
According to Galaxy Wearable app i'm runing latest FW
OneUI v1.0
Tizen 4.0.0.3
FW R500XXU1BSD3
a new 15 MB update seems to be comming out,
Samsung’s changelog for the update read:
• Improved system reliability
• Disabled automatic sync of alarm from paired smartphone or watch
• Improved tracking for swim
maybe it will also make our sensors alive again ?
Question is when it will be out in EU
no clue, is it only for US? i am in Europe/Romania also
btw, my sensors started workin for 1 whole day, then went dead again, and now for the last 5 days, they are working 1 hour in 24 hours...which is kind of nice ?? just kidding
It looks like its update only for your (R800) type of watch... My R500 don't have any new update since April...
I'm thinking if there is some way to downgrade Samsung Health because last day it drain my battery in 22 hours, so i think problem is there...
BRazvy said:
a new 15 MB update seems to be comming out,
Samsung’s changelog for the update read:
• Improved system reliability
• Disabled automatic sync of alarm from paired smartphone or watch
• Improved tracking for swim
maybe it will also make our sensors alive again ?
Click to expand...
Click to collapse
Well, it really screwed up the floor count. There's another thread on this here but I normally don't get any counts. Today without climbing any floors at all, I have 173 floors.
I've tried Samsung's CZ Tech support and they responded, that this problem (at least my version) is really caused by last update of SHealth app, they know about it, but sadly there is no way to rollback to previous version, se we must only wait for new update
BRazvy said:
a new 15 MB update seems to be comming out,
Samsung’s changelog for the update read:
• Improved system reliability
• Disabled automatic sync of alarm from paired smartphone or watch
• Improved tracking for swim
maybe it will also make our sensors alive again
Click to expand...
Click to collapse
True that
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
ententeak said:
It looks like its update only for your (R800) type of watch... My R500 don't have any new update since April...
I'm thinking if there is some way to downgrade Samsung Health because last day it drain my battery in 22 hours, so i think problem is there...
Click to expand...
Click to collapse
Yep, my friend has the same problem
whenever i reset my watch to factory settings, the latest samsung health version appears as an update, but i left it with the older version for days, and it still didn't help, are we talking about a much earlyer version?
BRazvy said:
whenever i reset my watch to factory settings, the latest samsung health version appears as an update, but i left it with the older version for days, and it still didn't help, are we talking about a much earlyer version?
Click to expand...
Click to collapse
Thats why i said "At least my version". I have different model (Galaxy Watch Active vs Galaxy Watch 46mm) than you, but similar error...
BTW: today i've wakeup with them "dead" - after 1 day and 10 hours in "battery saver mode" was battery drained from 100% to 0% mostly by SHealth app..
ententeak said:
I've tried Samsung's CZ Tech support and they responded, that this problem (at least my version) is really caused by last update of SHealth app, they know about it, but sadly there is no way to rollback to previous version, se we must only wait for new update
Click to expand...
Click to collapse
ententeak said:
Thats why i said "At least my version". I have different model (Galaxy Watch Active vs Galaxy Watch 46mm) than you, but similar error...
BTW: today i've wakeup with them "dead" - after 1 day and 10 hours in "battery saver mode" was battery drained from 100% to 0% mostly by SHealth app..
Click to expand...
Click to collapse
seems you will get the update also:
https://www.reddit.com/r/GalaxyWatch/comments/cgplgu/new_update_on_my_gwa/
Sadly not yet available in CZ
ententeak said:
Sadly not yet available in CZ
Click to expand...
Click to collapse
got the update 2 days ago, installed it,but nothing changed...
but about 1 week ago, i deleted the Alti-Barometer widget and then uninstalled the Alti-Barometer App thatcomes from the factory, and after several restarts everything started working, except for the floor count, which i can leave without, other sensors still working after 1 week, without any issues
also tested this again after the SW Update from 2 days ago, watch reset, tried to configure Alti Barometer app, sensors crashed, deleted Alti-Barometer app, 5 restarts plus several shutdowns later, everything started working again
so i am 99% happy now, maybe this post will help others
P.S. also with latest Samsung Health App installed, everything besides floor count works fine.
Good to know & glad it's sorted! Cheers
i "forced" that update with changing CSC code from XEZ (CZ) to XAR (US) and get the Tizen 4.0.0.5 update and no luck either... (Changing XAR to XEZ was a little pain in the ass because they use different WiFi bands so i've needed to reconfigure my router to be able to connect to sdb)
and GWA don't have Alti-barometer preinstalled, so i've tried to install it, calibrate (via GPS), tried to measure pressure (no data), tried few restarts with no luck... Now, when Alti-Bar uninstalled, i'm trying more restarts without change...
The sensors are dead even in the service menu (*#0*#)
(BTW: i've got since my last reply 2 days working, one day not and then 5 days in a row when it worked. Then dead again, so i've tried that CSC-updated method...)
Hi all.
I bought a Galaxy Watch 46mm in April 2019 and updated recently :
SM-R800
One UI 1.0
Tizen 4.0.0.4
R800XXU1CSE1
For my part I have the following problem: the number of floors climbed is completely wrong for several weeks now. I do not know if it's from the One UI 1.0 version but when i bought it it worked fine.
So according to you it comes from Samsung Health and not the OS, firmware?
Have you tried to go back on updating the watch by trying to flash it with a previous version?
My watch is still under warranty samsung.
It was sent for repair and they changed the brightness sensor which of course did not change anything !
Attached a screenshot of my watch : you can see 72 floors climbed on the 05/08/2019...
Thank you for your feedback.
I have the sensor issues (HR, lift-to-wake, step count, et al) for almost two months now. countless reboots didn't fix my problem. I then read somewhere that completely switching off the watch, or turning it to 'watch only' mode for 2-3 days fixes the problem. I did just that and voila! Everything works fine. UNTIL, I went to the gym and recorded my workout. I stopped recording my workout and all sensors died again. Followed the process once again, made sure not to record my workout again but it auto detected it this time and died again. I'll turn on my watch again over the weekend to see if the issue auto-fixes again, but I think I have identified atleast one thing that causes this incredibly annoying issue!
EDIT: I've read a lot of people (both on this thread and otherwise) mentioning how the Health app is the culprit. Does anybody have an apk of a previous version to test out this theory?
I give a shot to the "Watch-only mode"... and after few minutes in that mode, turned back on and its working
Edit: it was working for almost same time as it was turned off :/
BTW: I was asking at Samsung's support if there is some way how to rollback (at least like on any android phone - uninstall all updates for default apps) and she say there is no other way than "Factory settings"
If u uninstall Alti Barometer app all works except floor counts. But if u live in building on 4th floor when u go to the apartment gyro sensors goes off and stop working. The same situation is when u go down from 4th floor. Then u must restart GW (on ground or apartment) to start sensors working. Frustrated.
Hi
I'm searching for anyone else having the same problem as me and other people that i've seen in Lenovo Forums
I'm having different problems, but the most important for me is the proximity sensor, because once I answered a phone call, it makes impossible to hang up because the display turns black and it doesn´t "wakes" until the phone call has ended. The same problem with audios in whatsapp.
Another problem is that Moto Actions like turn on the flashlight with a shake, and open the camera with a twist doesn´t work anymore. Plus, the vibrator started to fail, having an unusual behavior until it just stopped.
And the device is not recognized correctly in any computer I've tried, it just appears as "unknown device", and the device doesn't show the options that use to appear when connected to a computer, it just says "charging".
I want to think that all of them are software problems, and not hardware problems, because they all started after the june 2019 update, and, as I said, there are other people having the same problems, and I think it would be a big coincidence if all of us have the same problems with our hardware.
If any of you have had the same problems, could you tell me if you could find a way to fix it? Or, anyone has any idea how could I solve, at least the proximity sensor problem, it would be better if the device don't turn off the screen anymore during phone calls.
I've tried reinstalling the drivers in 3 different pc's, and any of them worked, but when I tried with another device (Moto z2 force) they all worked. I've done factory reset three times, and one hard reset, with no changes. Could someone help me?
Thanks for reading.
Well, sound like... simply failing phone ? RMA ?
emcom said:
Well, sound like... simply failing phone ? RMA ?
Click to expand...
Click to collapse
Do you think that? I've had this phone for a year and a half, and I've never had any issue, until the last update on june 2019.
Maybe is a coincidence and my phone started to fail just after the update, but to be sure, I want to know if there's someone else having the same issue, and maybe someone could fix it.
I've had these problems a few months ago too, but back then I was thinking it was related to a hardware problem cause I had to send my phone to fix the screen (broken glass) and after that I noticed that the moto actions wasn't working properly, as the flash light from the frontal camera and the most annoying of the problems, the proximity sensor that would stop working when I got a call or audios in whatsapp. All of these was solved a couple weeks ago tho, after I had to fix my screen again (yes, 2 times in 3 months, congrats), just days before the android pie was released, so I can't say exactly what fixed it
Hi all, I have the LE2127 T-Mobile version of the OP9 Pro, and recently I have been having a strange issue with it. I am using the stock firmware, locked bootloader, nothing significant changed on it, running OxygenOS 12 (LE2127_11_C.19).
Sometimes, when I wake the phone from sleep, one of two things will happen:
1. The fingerprint sensor will not light up properly, and will instead remain the same brightness as the rest of the screen and appear as a dull white circle.
2. The entire display will get set to maximum brightness, and remain that way until I reboot the phone.
Nothing really screams at me in logcat, and removing and re-enrolling the fingerprint doesn't seem to work either. I also have factory reset the phone, to no avail. The bug happens intermittently with no real way to reliably reproduce that I've found. The only way to get the screen back to normal and to make the fingerprint sensor work again is to reboot.
Any ideas?
My last time updating to the current A12 on TMO LE2127, I couldn't get the fingerprint sensor to work once I set it up in settings. I went back to 11.2.9.9. Fully rooted.
I'm too.
BCXB said:
Hi all, I have the LE2127 T-Mobile version of the OP9 Pro, and recently I have been having a strange issue with it. I am using the stock firmware, locked bootloader, nothing significant changed on it, running OxygenOS 12 (LE2127_11_C.19).
Sometimes, when I wake the phone from sleep, one of two things will happen:
1. The fingerprint sensor will not light up properly, and will instead remain the same brightness as the rest of the screen and appear as a dull white circle.
2. The entire display will get set to maximum brightness, and remain that way until I reboot the phone.
Nothing really screams at me in logcat, and removing and re-enrolling the fingerprint doesn't seem to work either. I also have factory reset the phone, to no avail. The bug happens intermittently with no real way to reliably reproduce that I've found. The only way to get the screen back to normal and to make the fingerprint sensor work again is to reboot.
Any ideas?
Click to expand...
Click to collapse
I'm too
No9p ✨ said:
I'm too.
I'm too
Click to expand...
Click to collapse
That's A12 for you, I suggest going back to 11.2.9.9 A11 and staying there for awhile. I hated A12. Latest is not always the greatest!
I've also been dealing with this issue. Talked to support and they said just to restart the phone when it happens. They are working on a fix