Develop Bugs

Wifi connecting/slow issues

Ok in my house hold, I have a note 4 and a note 3, both phones drop wifi connections, and has very slow internet, sometimes its fine, but more often its not. Wifi is full bars.
I know its the phones, and not the wifi, At work my note 4 also does the same thing on my companys wifi, and the note 3 as well.
What the heck is wrong, Ive tried everything on both phones to fix it. Factory reset being the biggest thing that should have solved the issues.
Whats going on?

Yeah have you seen the massive thread here: http://forum.xda-developers.com/note-4-att/help/wifi-performance-horrible-t2921653/page4
About 1/3rd are having WiFi issues, the 2/3rd like to say its not their problem go buy another phone.

No answers in that thread. Just a bunch of blah blah blah lol.

I'm also having this issue. Seems random but its causing me to use alot of extra data.
Seems like when the phone locks or sleeps that is when it disconnects. I have went into the settings and changed to to stay connect in sleep but that didn't fix it. I have also factory reset.

sparky16 said:
I'm also having this issue. Seems random but its causing me to use alot of extra data.
Seems like when the phone locks or sleeps that is when it disconnects. I have went into the settings and changed to to stay connect in sleep but that didn't fix it. I have also factory reset.
Click to expand...
Click to collapse
Don't have that "smart Switch" option checked, do you? I had this problem when that was selected. unchecked it and it went away.

sparky16 said:
I'm also having this issue. Seems random but its causing me to use alot of extra data.
Seems like when the phone locks or sleeps that is when it disconnects. I have went into the settings and changed to to stay connect in sleep but that didn't fix it. I have also factory reset.
Click to expand...
Click to collapse
I have the same issue and don't wanna take my phone back if this is a confirmed software issue.

Wifi problems after mm update

I've checked around and have seen other phones with the issue, but I've tried the fixes like forgetting network and resetting network settings. Ever since mm, every time my phone screen shuts off, it disconnects from wifi, kind of. I will still be connected jn settings, but it says no Internet available. I have to reconnect every time, and then it will work until my screen goes off again. I feel like this is killing my data since I don't always notice it. Has anyone had this problem and fixed it? I'm completely stock, no root or anything. Just did a factory reset a week ago and hoping I don't have to do it again since I'm finally set back up.

Have this issue with both wifi and mobile data. Mine doesnt matter whether the screens been off or not. Its like it goes to sleep periodically no matter what. Never had the issue until the latest update. Its not tied to a specific app, so its either the radio or a bug in the phone.

Long delay when attempting to make a phone call - just started

Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S

sb1893 said:
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
Click to expand...
Click to collapse
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.

sb1893 said:
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
Click to expand...
Click to collapse
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.

sb1893 said:
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
Click to expand...
Click to collapse
The saga continues. The issue occurs immediately after the first call I attempt when connected to my BMW bluetooth system. From that point on, I experience a 30 sec to 3 min delay between attempting to make a call and the Pixel XL actually initiating the call. The quickest way I have found to resolve the issue is to plug the phone into a charger for a few seconds and I am then again able to place calls. I have verified that the BMW bluetooth software is up to date and has not been updated in over a year. (Again - this issue just started happening yesterday...and I've been on Feb security patch for several weeks). I just cleared cache from within Titanium Backup. Will see if that improves the situation. Very weird. I also was just able to recreate the issue using just a simple Plantronics headset. So I continue to think it is something related to the Bluetooth stack on the phone. But I am not sure how to check to see if any of that has been updated via app update since I upgraded to Feb security patches. (I reproduced the issue at my desk using the headset after clearing cache.)
S

Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.

Racermanz said:
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Click to expand...
Click to collapse
No - but I'm at least somewhat encouraged to know I am not the only one dealing with the issue. Today I flashed factory images (but preserved my data by removing the -w from the flash-all.bat)...that did not resolve. I've tried the reset app preferences, reboot suggestion I found elsewhere - no dice. Google pushed a new Phone app yesterday - that also did not resolve. I've even tried uninstalling Magisk completely and dropping back to 15.4 - also no help. I'm running out of ideas. I've taken to carrying a charging cable in my car...so if I absolutely need to make a call when the phone isn't behaving, I can just quickly plug it in...which does clear up the issue temporarily. Also keep a charging cable at my desk now...so I'm limping along..but for an issue that just appeared out of nowhere this week...it's been pretty frustating to deal with. Also - I no longer believe being currently connected to Bluetooth is related to the issue. I've been able to get the issue to occur today while not connected to any bluetooth devices.

Try
settings>system>developer options>media>disable USB audio routing

DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Thanks bros. This is such a strange bug. Right now it works before I have turned off USB audio routing. I have turned off USB audio routing. I will report back if this DOESNT work. If I don't post again we can assume this works.
Thanks DR3W5K1, great name bro.

DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Just tried to toggle on, which looks to mean Disable. Then rebooted. No luck. Issue still occurs. Thanks for the suggestion. Willing to try anything even to just eliminate as possibility at this point.

Well - I have found a better workaround. When you attempt a call, if you get no response, you can toggle Airplane mode "ON"....You will then see the call you attempted fail. When you turn Airplane mode back "Off" you can can successfully make calls again. Better than having to plug into a charger cable to get the attempted call "unstuck"....still no idea what is going on....but this workaround at least is more palatable, portable, and take a few seconds...hope someone can figure out root cause soon and a proper fix becomes available.
EDIT: Even better workaround. Toggling Mobile Data OFF and ON has the same effect of clearing the issue. And works better when connected to Bluetooth in car as those connections will be maintained vs. using Airplane mode toggle. So - issue seems to be related to Mobile Data somehow - but I have already had Advanced Calling / LTE, etc...turned off as one of my first steps in troubleshooting this issue.

Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?

Try changing the network mode in the secret menu dial *#*#4636#*#* to get there

The.Yield said:
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Click to expand...
Click to collapse
I have tried that. Sorry for not mentioning it in this thread. At one point I revoked "Phone" permission from all apps other than Phone, Carrier Services, and Contacts. Rebooted. Issue still occurred.

DR3W5K1 said:
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
Click to expand...
Click to collapse
Ahhh...I had forgotten about this secret menu. Looks like I could permanently toggle off VoLTE, WifiCalling, etc...here. But - not sure I want to go that route...I'm OK at present with Toggling Mobile Data via Quick Settings tile. And hopefully this issue eventually gets solved as mysteriously as it was introduced via some update.

Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.

tesla45 said:
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
Click to expand...
Click to collapse
Interesting....I'm on Verizon and I do believe that they route calls over Mobile data at times. I'm going to stay tuned, but likely done with much more deep investigation at the moment. I've spent enough time down this particular rabbit hole and the Mobile Data toggle is workable for me (not ideal, obviously)...hopefully a permanent fix materializes soon. Thanks to all for their suggestions and moral support. Much appreciated.

OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.

Install the stock again clearing all the data. Don't restore anything with titanium or install any extra apps. Then make a call.

tesla45 said:
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Click to expand...
Click to collapse
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)

sb1893 said:
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
Click to expand...
Click to collapse
Glad the workaround helps you too. My emphasis CAPS in my last post was clearly misleading, I was actually suggesting NOT to reinstall/factory reset because I don't believe that solves the problem long term and its a huge ask for a customer (when really Google should be solving this problem for us).
Based on this little workaround its clearly a software problem that Google needs to address, I've raised the issues on many threads in their product forums ... hope it gets to the right people ASAP because I believe lots of Pixel users are running into the problem (both Pixel 2 and 1st gen, another indication its NOT a HW problem).
Keep the workarounds coming folks!

Fingerprint sensor issues, and WiFi issues "Obtaining IP address"

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.

Question Graphical glitches on A52s (Culprit found)

Update: Found the culprit! When the phone is on a 2G network, it happens always when there is any (voice or data) communication and glitches are stronger when the signal is weaker. It's probably caused by an interference and bad shielding of components. Similarly how 2G network makes buzzing sound in radio speakers, on A52s it makes a mess on the screen.
At least one user (bellow) solved it by RMA - sending the phone to service and getting back new/fixed one.
Update 2: Problem fixed. I sent the phone to service center with description how to replicate the issue (phone must be on 2G network, ideally low signal, data or voice transfer is happening). Got it back after 2 weeks. Report says they replaced the display and also battery for "construction" reason (as they described it) and issue seems to be solved!
To conclude: It is indeed hardware issue and is fixed by replacing the display. If this happens to you too, don't wait for software update or anything else, send it to a service for a fix covered by the warranty!
Since few weeks ago, maybe since last update a month ago (security update from 1st October 2021), I'm randomly getting graphical glitches on my A52s.
It usually happens when I wake my phone after few hours of screen off but today I also saw few flashes even when playing a (graphically not demanding) game.
There is colour noise flashing over parts of the screen. It is usually just few random quick couple of 1/100 sec flashes, sometimes it stays a second and it disappears and everything is okay after that.
I also saw noise not covering the screen but flashing instead of wallpaper... Like there's a corruption in graphical memory, driver or whatever.
It doesn't make a difference whether the phone is freshly rebooted or running a week or two.
Does anybody else have this issue?
Is my phone (the memory, screen cable or something else) dying or is ist just a bug in current system update? I don't experience any other instabilities or problems.
(I'd send my phone to RMA but since I didn't find any consistent way to replicate this, it would make just as much of a difference as locking my phone in a drawer for a month.)
I'm appending mock-up screen shots how some of the flashing glitches look.

Clear system cache, hard reboot.

Huh, I didn't really ask for help, but yeah, that's a good idea with clearing the cache.
I rebooted to recovery and wiped the cache partition.
(I also accidentally hard rebooted when trying different button combos to enter the recovery LOL, so I did both things. In the end I had to enter the recovery using "adb reboot recovery" command because none of the button combos I found worked for me.)
I'll report back in few days whether it solved the issue or not.

Your screen is dying. This is hardware issue

Easy fixes are a good thing...

EugenStanis said:
Your screen is dying. This is hardware issue
Click to expand...
Click to collapse
A possibility as is a mobo failure but no harm in trying a few simple fixes first.
Samsung has been having a lot of issues with their displays this year...

It doesn't really feel like screen itself is dying when glitches can appear under the home screen icons in wallpaper or in the application area with status and nav bars being untouched. But I guess it can be; I have no idea how the image on screen is being redrawn.
But it happens especially after phone display is off for longer period of time. The phone then is quite sluggish, presumably because the system paused or killed some apps and is waking them up. And glitches mainly appear then.
That would suggest to me either a system memory being corrupted or something weird happening in the cache, depending on where these apps go when they're paused/killed.

jenda.69 said:
It doesn't really feel like screen itself is dying when glitches can appear under the home screen icons in wallpaper or in the application area with status and nav bars being untouched. But I guess it can be; I have no idea how the image on screen is being redrawn.
But it happens especially after phone display is off for longer period of time. The phone then is quite sluggish, presumably because the system paused or killed some apps and is waking them up. And glitches mainly appear then.
That would to me suggest either a system memory being corrupted or something weird happening in the cache, depending on where these apps go when they're paused/killed.
Click to expand...
Click to collapse
Factory reset. Before loading apps confirm if ok.
Then be careful what 3rd party apps you load.
If the reset doesn't work, reflash it to a known good version.
If all that fails it's likely hardware.

The most likely cause is a 3rd party app given right to overlap other apps and this 3rd party app has crashed. Uninstall apps in opposite order of installing until problem is solved. Or factory reset.

I have the same problem, sent phone for repair.
In my case, the issue is occurring when phone is on 2g network. You could try going to network and set it to 2g only, check if it's happening, and then set it to 3g and see.
Cheers!

Bvid said:
I have the same problem, sent phone for repair.
In my case, the issue is occurring when phone is on 2g network. You could try going to network and set it to 2g only, check if it's happening, and then set it to 3g and see.
Cheers!
Click to expand...
Click to collapse
So is it a hardware issue or software?

abood.mhd said:
So is it a hardware issue or software?
Click to expand...
Click to collapse
It was a hardware issue, got a new phone.

Bvid said:
It was a hardware issue, got a new phone.
Click to expand...
Click to collapse
I have the same problem, and I can't replace the phone, the question is here, will this problem increase and affect the screen more?

Same problem here...but mostly when I am on 2G network (anyone please try and post results)...Thinking of sending phone to service...will see how it goes

Huh, I didn't get notifications for my thread, so I didn't know about all the replies!
I tested different things in last few weeks and I came to the same conclusion - that it only and always happens when my phone is on 2G network. If 2G signal is strong, it's occasional small glitchy line here and there. When the signal is really bad, it just messes up the whole screen - I had my phone ringing with screen being all just noise and mess. So I guess it's probably because of interference similarly how the 2G network connection makes buzzing sound in a radio speakers. Except here it makes a mess on the screen.
Now that I know how to reliably replicate the problem, I'll back the phone up and RMA it after christmas.

i have the same problem from the first day, it happens only in 2g signal ...and only if 2g signal is weak... i sent the phone to Samsung , they inform me that they know the problem and it will be fix ..on another update ...it s software problem they told....from this day i have take 3 updates and nothing happened....the phone still have the problem

Same here, took my a52s to a Samsung authorized repair center, after 3 repairs (the third one being the display change) it seems that the problem is solved. To me, it has nothing to do with software.

So, it's a hardware issue, I face the same problem for almost 2 months, and I don't know what to do

Only solution is to contact Samsung and have it fixed

VirtualGamer20 said:
Only solution is to contact Samsung and have it fixed
Click to expand...
Click to collapse
Its not that simple...Some people send phone for repair...twice and still not fixed