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.
Related
Hiya folks,
Just wondering if anybody has been experiencing random reboots on the OP3. Have been experiencing em on 3.2.1 and 3.2.2 about twice a day since I got the phone four days ago. Tried a cache wipe/hard reset but to no avail. Haven't been able to reproduce the reboots. Just happen at completely random times, while writing an email, making a call, or connecting to the car Bluetooth. Phone is perfectly responsive and stable otherwise!
Have asked Amazon for a replacement, but I'm wondering if this is something that's been noticed by anybody else. No mods done, completely stock. Running dual sims (Vodafone and Jio VoLTE).
Attaching a screenshot of how the battery page shows the reboots.
Yeah, they happen for me periodically. Not nearly as often as yours though. Mine is maybe once or twice a week max. But yes, slightly annoying.
Phone is completely stock, locked, unrooted. Running 3.2.2.
mrhohoha said:
Hiya folks,
Just wondering if anybody has been experiencing random reboots on the OP3. Have been experiencing em on 3.2.1 and 3.2.2 about twice a day since I got the phone four days ago. Tried a cache wipe/hard reset but to no avail. Haven't been able to reproduce the reboots. Just happen at completely random times, while writing an email, making a call, or connecting to the car Bluetooth. Phone is perfectly responsive and stable otherwise!
Have asked Amazon for a replacement, but I'm wondering if this is something that's been noticed by anybody else. No mods done, completely stock. Running dual sims (Vodafone and Jio VoLTE).
Attaching a screenshot of how the battery page shows the reboots.
Click to expand...
Click to collapse
Haven't had a single random reboot yet, had the phone for about a month now. Started with 3.1.3, then 3.2.1, now 3.2.2, rooted, running xposed (not a lot of modules).
What are you doing when the reboots happen (an app issue)?
Hw4ng3r said:
Haven't had a single random reboot yet, had the phone for about a month now. Started with 3.1.3, then 3.2.1, now 3.2.2, rooted, running xposed (not a lot of modules).
What are you doing when the reboots happen (an app issue)?
Click to expand...
Click to collapse
It's been all over the place, but often when the screen was actually off! The way I would know would be I'd pick up the phone and see that it asks for the PIN post reboot. If it helps, I've enabled encryption. I also have a work (exchange) email account set up as a device admin
I know there's ways of investigating this with logcats and last_kmsg, but I've had the phone 4 days and I cant imagine why it's spontaneously rebooting while doing literally nothing. Seeing as hardly anybody has had similar reboots (on XDA/OnePlus forums), could this be a hardware issue at all? I could possibly try reflashing the entire phone, but that would essentially be the same as a wiping data/cache, right?
Here's an idea - my LTE data/VoLTE is extremely spotty (on Reliance Jio which is in a beta test stage) - disconnects and connects VERY frequently, could that be triggering reboots at the baseband level? Now throwing ideas at the wall!
mrhohoha said:
Hiya folks,
Just wondering if anybody has been experiencing random reboots on the OP3. Have been experiencing em on 3.2.1 and 3.2.2 about twice a day since I got the phone four days ago. Tried a cache wipe/hard reset but to no avail. Haven't been able to reproduce the reboots. Just happen at completely random times, while writing an email, making a call, or connecting to the car Bluetooth. Phone is perfectly responsive and stable otherwise!
Have asked Amazon for a replacement, but I'm wondering if this is something that's been noticed by anybody else. No mods done, completely stock. Running dual sims (Vodafone and Jio VoLTE).
Attaching a screenshot of how the battery page shows the reboots.
Click to expand...
Click to collapse
Mine had random reboot issues recently on a trip. It only seemed to happen when I was using Google navigation combined with listening to music on my bluetooth headphones. I haven't tried that combination since the trip and haven't had any reboots since then.
Here's an idea - my LTE data/VoLTE is extremely spotty (on Reliance Jio which is in a beta test stage) - disconnects and connects VERY frequently, could that be triggering reboots at the baseband level? Now throwing ideas at the wall!
same issue
the reboots are random, and i could only know that the phone has rebooted itself if it ask for a pin upon scanning finger, went to service center and has OS flashed, but the problem still persist, for me some time when the phone hangs, some kind of pixels form on the screen, attaching a sample photo for reference, anybody experiencing this issue or am i the only one, and today the phone has completely stopped working, it is not switching on.
sbzrsd said:
the reboots are random, and i could only know that the phone has rebooted itself if it ask for a pin upon scanning finger, went to service center and has OS flashed, but the problem still persist, for me some time when the phone hangs, some kind of pixels form on the screen, attaching a sample photo for reference, anybody experiencing this issue or am i the only one, and today the phone has completely stopped working, it is not switching on.
Click to expand...
Click to collapse
Wow that is substantially worrying, and almost certainly not just a software issue I reckon. Try getting a replacement maybe? - or atleast ask the service folks for a mainboard replacement. Anybody else with reboot issues?
Doesn't really seem to be an OS bug, unless it happens in very niche use cases which I don't have anyway! Getting the replacement on Tuesday, fingers crossed for that one!
My friend and I both got a one plus 3. He does not have this problem but I have.
The reboot is random but usually happens during charging. Sometimes it even turns off.
I have tried to ask for a replacement but they rejected me. Still communicating with the support staffs
mrhohoha said:
Wow that is substantially worrying, and almost certainly not just a software issue I reckon. Try getting a replacement maybe? - or atleast ask the service folks for a mainboard replacement. Anybody else with reboot issues?
Doesn't really seem to be an OS bug, unless it happens in very niche use cases which I don't have anyway! Getting the replacement on Tuesday, fingers crossed for that one!
Click to expand...
Click to collapse
Went to service center in Gurgaon, getting a replacement for motherboard, as oneplus policy doesn't give replacement handset, have to SETTLE for this, i dont know how many days this whole process is going to take, will update you guys about it when i get the phone back.
I have the same issue, random reboots usually when screen is off.
3.2.1, root + xposed... for me it started with 3.2.0 update
marleyfan61 said:
Mine had random reboot issues recently on a trip. It only seemed to happen when I was using Google navigation combined with listening to music on my bluetooth headphones. I haven't tried that combination since the trip and haven't had any reboots since then.
Click to expand...
Click to collapse
I experienced a similar scenario twice, only seems to happen on long trips, 3+ hours. I was using Waze with Plex streaming audio over car Bluetooth. I have not had this on shorter trips, 1-2 hours. I'm typically plugged into the dash car charger. Otherwise, haven't had issues. Never rooted 3.2.2.
Situation Update
Got the replacement OP3 on August 9. Have now seen 2 random reboots since. Once while paired to the car Bluetooth, once after finishing a call.
I have till August 19 to decide whether to keep this device or ask for replacement number two! Overall, the reboot situation is a lot better on this device, but I can't help wonder - why any at all?
Seems at this point to either be a bug with the Bluetooth implementation AND/OR with the dual SIM functionality where repeated switching between SIMs for every call. (I use one SIM for calls and texts, another for data)
Can anyone confirm the situation on a custom ROM as opposed to stock? I'm running stock 3.2.2
Aaaaand now we have an ota claiming to fix 'auto-reboot issues' - 3.2.4 :laugh:
The reboots were so sparsely documented compared to the other stuff that I ended up getting a replacement for a s/w issue!
Anyway - you folks reboot free now? Post results with 3.2.4 please
I had three back to back random reboots while using Google Maps and Amazon Kindle in the background. Weird.
I've yet to have a random reboot on 3.2.4
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Got my very first reboot :crying:
I'm on 3.2.4 with bl unlocked, rooted, Xposed, twrp
Had several reboots while driving and navigating on google maps one after the other. Maybe it is to do with the GPS sensor but its annoying coz you need it most when u r navigating turn by turn
jonynoname said:
Had several reboots while driving and navigating on google maps one after the other. Maybe it is to do with the GPS sensor but its annoying coz you need it most when u r navigating turn by turn
Click to expand...
Click to collapse
Agree. It happens only when I drive with gmaps running on background. When the screen times out, the phone, instead of shutting down the display, goes to hard reboot.
I've never had this issue until I moved to the latest update. Weird. Annoying.
I had my first reboot a few hours ago (with 3.2.4). I was connected to Bluetooth in my Car. Noticed it, as my car told me that mein Phone is now connected. No gmaps or something with GPS runinng.
Looks like Bluetooth is the Problem.
Hi everyone,
I have 2 Galaxy S8+ from Verizon and here are my issues:
Past issues:
One of them did not come with the Galaxy Apps store (Not the plays store), and that phone also experienced the DQA issue
Current issues:
If I turn on Fingerprint gestures, the fingerprint sensor will stop working, this was an issue I had from the day I got the phone and has continued even through the updates. Here's a thread I made about it a while ago : https://forum.xda-developers.com/galaxy-s8+/help/fingerprint-sensor-t3595614
My internal speaker has detached, or at least I think that is the issue, as sometimes when I am in a phone call and shake the phone just a little bit, it will either start making a weird buzz sound or completely cut off the sound. Shaking it again will fix it, that's why I think it's a physical issue. I haven't dropped my phone and just in case I ever do, I have a case and a screen protector on it, and neither of them (phone, case, screen protector) have any damage marks on them.
The Biggest Issue: Currently this is the most annoying bug I am experiencing is that whenever I go to lock screen and security in the setting app, it crashes the settings app. I also can't use the search function in the settings app, as it crashes the app withing a few seconds. The lock screen and security is the only menu in which I experience this, I am 99% sure this is due to me turning on Secure startup. I had it turned on a few days after I got the phone and it worked great, I had to turn it off once, about a month ago in order to get a quicker boot. After that I was experiencing issues turning it back on (meaning I turned it on, rebooted the phone and it would not work) , after some persistence, I was able to get it to work and it has worked and still works.
One thing to mention is that I had done the most recent system update, I am not sure this issue was caused by at, since the inability so search in the setting menu has happened prior to the latest update.
I have tried everything other than a full factory reset (wiping all cache, wiping apps cache, reset setting, reset network settings), which I refuse to do, It is absolutely unacceptable for me to pay this much for this phone and have so many issues with it, I have factory resetted my phone (Samsung's recommendation) in order to fix the first issue listed above, multiple times and it did not work.
At this point I really don't know what to do, Samsung support has been useless in this, I don't wish to replace my phone right now as I need it to much to even give up for one day, If anyone has any advice/fix other than factory resetting, I'll happily try it.
Thank you,
GGgamer16
Sounds like a factory reset is needed. I just tried all you mentioned with zero problems on the newest update w/ navbar options and experienced none of that. Speaker problem is most likely hardware related.
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
*Hooligan* said:
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
Click to expand...
Click to collapse
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
brandonc0526 said:
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
Click to expand...
Click to collapse
Yeah I have tried changing channels. It didn't matter. I'm on 2.4 GHz.
I found a possible fix from another forum. I changed my wifi encryption from wpa2 AES/tkip to wpa2 tkip only last night and was rock solid after that point. I didn't have any more wifi issues... Just wanted to mention this change for other people. I usually got 5+disconnects every night. I'm gonna try just the AES option tonight and see how it acts.
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!
Me and my wife are experiencing random restarts quite often. It began with buying smart band and smart watch - but it may be unconnected.
The screen suddenly becomes bright, the phone vibrates and restarts so we have enter the pin again.
potworny said:
Me and my wife are experiencing random restarts quite often. It began with buying smart band and smart watch - but it may be unconnected.
The screen suddenly becomes bright, the phone vibrates and restarts so we have enter the pin again.
Click to expand...
Click to collapse
Hasn't happened to me once since November 2017.
A little more information wouldn't hurt: Are you rooted, do you use a custom Kernel or custom ROM?
I use the January security patch, stock Kernel, rooted with Magisk, modified the build.prop so the phone shows up as Pixel 3 XL and have Substratum running with Swift Black.
If you are unrooted, you can try a factory reset. Don't install any apps to make sure that there isn't a rogue app causing the problem. If the phone works, install your apps one by one to check what makes trouble.
potworny said:
Me and my wife are experiencing random restarts quite often. It began with buying smart band and smart watch - but it may be unconnected.
The screen suddenly becomes bright, the phone vibrates and restarts so we have enter the pin again.
Click to expand...
Click to collapse
Did you by any chance activated private DNS on both of your phone (for exemple CloudFlare secure DNS or Adguard) ?
That happened to me a lot this whole month ago, Pixel 2XL stock. It "fast rebooted" several times a day until I stopped using the Adguard private DNS.
My phone is not rooted and not running any special ROM. Bootloader locked.
For about the last month I have been/was having this problem as well, but I couldn't tie it to anything. Sometimes happened a lot, sometimes not so much, but everyday at least once. It was not a total reboot where you get the white screen with the Google "G". I would notice the clock/screen go dark, and then within a couple seconds, back to the lock screen. Try to unlock with fingerprint, and I would get the message that I would have to input my PIN after a reboot. I frequently use Android Auto, and I noticed that while using Android Auto or while listening to the Sirius app it would not reboot, so for some reason the only time I would get a reboot was when the phone was idle.
Eventually called Google support, who suggested I put the phone into safe mode and see if it continued. It did, but not as frequent. So then I bit the bullet and did a factory reset/flash-all to factory, but the problem continued. So Google agreed to a warranty replacement, and I got my new phone 3 days ago.
First thing I did was a flash-all to the latest factory ROM. And.....within the first hour.....reboots. So then I was going on the theory that the reboots were being caused by a wonky app......but I really don't have any obscure apps or non-Play Store apps installed. I checked reviews for some of the more suspect apps, but found nothing about reboots.
Then I saw this thread, and especially the reference to using AdGuard for the DNS. Well, I was using AdGuard (which actually made a big difference in the amount of data I am using on my 6GB plan). So this morning after reading this I set the DNS to "automatic" (BTW, can someone tell me if the default "Private DNS" setting is "Off" or "Automatic"?), and I have not had any reboots since then. But it's only been about 6 hours now. I will report back after a couple more days. But you may be on to something about AdGuard's DNS.
Shame. Google will likely not fix this because AdGuard interferes with their business model, but it is an OS flaw that should be fixed.
Google is apparently already aware of this and says it is fixed. No ETA of rollout.
https://issuetracker.google.com/issues/122141885
I did activate the private dns!
Guys. Thanks for the advise. I think this is it.
You guys should use Blokada (not the one on play store, but the one on the web) for your ads blocking solution.
It won't reduce battery life (it will most likely increase if because no ads) and its free
Hi, i have a big issue with this phone, i bought it like 2 weeks ago.
Since the 2nd day of use, i started to experience this issue, sometimes and usually when im not using wifi but mobile data, the screen goes to lockscreen, if i try to unlock it will lock again and that happens a couple of times, maybe 2, 3, 4, 5 times, sometimes i have to press lock button and try again. its really annoying, because somtimes it doesnt happen in a lot of time and then after 1 hour in the street and while im using it it locks and unlocks like crazy.
i did a soft factory reset but didnt work, i even tried in safe mode and it still happens.
yesteday i noticed that it even wakes up for no reason, that happened while i was driving in a highway, it suddenly wakes up like if i touched it, i disabled every feature about auto waking (like 2 touch, motion detection) but it still happens.
the only thing that makes it stop is if i switch airplane mode, so i guess maybe its something related to network (not wifi or location or mobile data because i disabled those and still happened), but when it is in airplane mode it will work fine, obv thats not a real solution.
i tried disabling and uninstalling a lot of apps but i cant figure out whats making this, im pretty sure its software problem, something related to network but i dont know.
do you have any ideas? even if i take it to tech service it will be hard to show them because sometimes it doesnt happen in hours.
anybody has an idea what could be causing my phone to lock for no reason while using it on the street?
Your phone gone kaboom
I have same problem, the problem is caused by the weak signals,which means that your phone connectivity is constantly changing, for example on a highway or in a basement. Solutions I have none, just waiting samsung to make a fix
Yes, thats exactly the problem. When signal is weak the phone locks or unlocks. I asked for a new phone at the store and they gave me a new one.
Look
htt ps://r2.community.samsung.com/t5/Galaxy-A/Samsung-a50-locks-and-unlocks-automatically/td-p/1701267
Are you having this issue?
htt ps://photos.app.goo.gl/5veszyLb4UGJZRV9A
(Delete spaces in link between htt and ps)
Btw i don't think this is a software problem because if it was a software problem all phones would having this issue. I think it's a problem with some hardware failing in some phones. IMEI of failed phone is 356711101439414 check if yours is similar