Related
Dear XDA community,
Recently my LG G4 H818 (dual sim) started causing troubles after 8 monthes of use. Everything started a week ago, when during the call I couldn't hear the other person. The other person could hear me well. It didn't matter if I was calling or I was receiving a call. It didn't depend of which sim I was using, call sounds from both sims were silent. After reboot this issue was resolved. Temporarily... After couple days everything started again and again reboot helped.
Yesterday, after regular reboot due to this issue, my phone showed an error - "Process isn't responding. Do you want to close it?". This is where nightmare started. Everything froze or started lagging badly, I couldn't unlock the phone, I couldn't launch any app, even notification drawer was not coming down, the phone was useless. I could receive calls, but I couldn't pickup (phone freezes instantly). When I tried to launch an app, it would say "This app isn't responding. Do you want to close it?" before freezing for couple minutes. It was happening to every single app (Phone, Contacts, Shazam, Whatsapp, etc.). I barely managed to save my data to pc using usb cable and decided to hard reset (erase all, format data, etc.).
After hard reset, during the first launch everything seemed ok, no lags, no errors... BUT this morning I received a call, picked it up and sound was missing again. I did the reboot and now I'm back again to freezing, huge lagging, errors, and phone is useless.
Everything is stock, latest Androd 6.0 is installed. Not rooted, bootloader is locked - I have not done any changes to the firmware at all. I did drop it once on the hard floor (only once) after a month of purchase, but until last week everything was working ok. I must mention that battery wasn't lasting long enough, but it might be due to my heavy use (9GAG, Chrome, Corporate email app, gaming sometimes) - charging 3-4 times in 2 days.
Has anybody faced same issue? Can anybody help me? Couldn't find any results on google and on forum here. Please help.
P.S. rooting and installing a different ROM is not an option, since dual sim LG's have limited available custom ROMs. Also, I use a corporate email app that cannot be installed on rooted phones (it is really annoying).
Thanks in advance!
Some update. It turns out speakers and microphone works if on speakerphone. If I switch back to headset, sound dissappears. Seems like more of a software problem, than hardware.
anyone?
fizic said:
Dear XDA community,
Recently my LG G4 H818 (dual sim) started causing troubles after 8 monthes of use. Everything started a week ago, when during the call I couldn't hear the other person. The other person could hear me well. It didn't matter if I was calling or I was receiving a call. It didn't depend of which sim I was using, call sounds from both sims were silent. After reboot this issue was resolved. Temporarily... After couple days everything started again and again reboot helped.
Yesterday, after regular reboot due to this issue, my phone showed an error - "Process isn't responding. Do you want to close it?". This is where nightmare started. Everything froze or started lagging badly, I couldn't unlock the phone, I couldn't launch any app, even notification drawer was not coming down, the phone was useless. I could receive calls, but I couldn't pickup (phone freezes instantly). When I tried to launch an app, it would say "This app isn't responding. Do you want to close it?" before freezing for couple minutes. It was happening to every single app (Phone, Contacts, Shazam, Whatsapp, etc.). I barely managed to save my data to pc using usb cable and decided to hard reset (erase all, format data, etc.).
After hard reset, during the first launch everything seemed ok, no lags, no errors... BUT this morning I received a call, picked it up and sound was missing again. I did the reboot and now I'm back again to freezing, huge lagging, errors, and phone is useless.
Everything is stock, latest Androd 6.0 is installed. Not rooted, bootloader is locked - I have not done any changes to the firmware at all. I did drop it once on the hard floor (only once) after a month of purchase, but until last week everything was working ok. I must mention that battery wasn't lasting long enough, but it might be due to my heavy use (9GAG, Chrome, Corporate email app, gaming sometimes) - charging 3-4 times in 2 days.
Has anybody faced same issue? Can anybody help me? Couldn't find any results on google and on forum here. Please help.
P.S. rooting and installing a different ROM is not an option, since dual sim LG's have limited available custom ROMs. Also, I use a corporate email app that cannot be installed on rooted phones (it is really annoying).
Thanks in advance!
Click to expand...
Click to collapse
Have you been able to fix it? Since I updated my H815 firmware's, I have been having same issue.
Sometime during night silent mode goes on, and it's on when I wake up. Then I have to use the slider to get the phone back on normal state. Quite annoying. Slider was in normal mode all the night. Anyone else? How to stop that behavior?
This happened to me too. Did you have Do Not Disturb settings set on your prior device and then restore the back up to your OP3? I have read that this is the cause of the problem - the old setting transfers over and there is no way to change them. I went into the global setting for app notifications and reset all apps. This worked for others and appears to have worked for me as well.
Having the same issue here.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Yes, actually I had it on on my OPO and I transferred apps from it to the OP3 using the installation wizard's nfc method. I did the reset, let's see if it did help..
I tested resetting notifications, did not help
Me too. Migrated from my old phone using the NFC transfer wizard. Old phone was setup to go to silent 10pm - 7am. It appears the setting is transferred over but at 7am the OP3 doesn't exit silent mode. I then have to toggle the switch to take the phone out of silent but still seem to have issues with notifications sounds afterwards.
I solved it by installing new custom rom and I didn't use restore function this time..
i too am having this issue. i attempted resetting all apps settings but that didn't work.
has anyone figured out how to fix this without factory reset or installing a custom rom?
Add me to the list and I set it up as a new device. Only had the phone a day before I applied the 3.2.0 update so I can't say if was happening before. Hope there is a fix for this soon.
IMO this is because Google is syncing the DND preferences from your Google account, regardless of whether you used the the whole "set up nearby device" thing
I have this issue except Silent mode automatically turns on throughout the day for me. I have factory reset my device and setup the device as new and the issue continues. Now I'm really unsure how to fix this.
Same issue and updating to 3.2.1 didn't fix it.
I've the same issue!
I've noticed that the sound (also from the notifications) can be turned on again (for that day) by switching off, and on the Alert Slider, and then adjusting the volume-sliders in settings.
I don't think it's a Google issue as I have 4 different phones on my account in the last month and none have done this. Just ordered another 6P while they were 20% off in warehouse deals so I'll swap over to this phone Monday and see if the issue follows. For now I'm playing with Tasker to reset all the volumes at 7am.
I've got the same issue. But I did not transfer any settings to my op3.
There's nothing in my "do not disturb" menu, and nowhere to set up automatic silent mode, as far as I can see.
Same issue faced, no solution or fix found up till now.
Me too facing the same problem.. Even in day time it goes automatically to silent mode. So incoming calls doesn't sound and it solves only when I restart the phone.. And after sometime the problem is occurring again and again.. Does anyone found the solution?
I had the same problem in my opo too..
Same here. Since the 3.2.1 update my OP3 sets to Silent overnight. Some has said it's True Caller Spam Blocker, but as I don't have this it's not a solution for me. Tried the usual reset but no luck. Really need a fix for this as I need to get important calls/texts overnight. Not a hardware problem that I can see as fine before update; broken afterwards, and the physical switch works very well.
Also, I've not used any restore function whist setting up.
It would be useful if people experiencing this problem could mention it on the OP support forum. I'm using the threads...
https://forums.oneplus.net/threads/do-not-disturb-notifications-problem.451989/page-7
https://forums.oneplus.net/threads/possible-bug-with-oxygen-3-2-1.455413/
yes - please do and add @oneplus to your answer to adresse OP team directly. Thanks.
This is related to OOS only, i installed custom rom CM based nd didn't face this issue. Then installed.OOS no restore setup as new device still same issue with no ringtone.
The fix should come from Oneplus
Hello folks,
I have encountered a weird behaviour of my beloved 5X when on mobile data.
It occured for the first time approximately 8 or 9 days ago (well, at least that's where I really noticed for the first time since I am on WiFi for 80-90% of the day).
Suddenly everything Google-related stopped working. I could not get into my mails (blank screen and the loading circle for an eternity), I could not get google now to work properly, facebook didn't work (also blank screen + loading circle) and and and....finally google now and facebook showed some content but without any pictures. The same happened when I tried to use Chrome to browse the web. Either I could not get a connection to any website I tried to enter or something showed up but without pictures loading and veeeeeery slowly.
Strange thing was that everytime I just searched for something via Google, the results showed up almost immediately, but then again as soon as I tried to enter a webpage nothing was working.
This happened a lot of times until now, sometimes a reboot is helping, sometimes not. Sometimes airplane mode on/off is helping, sometimes not.
This is driving me crazy and I don't know how to proceed.
Is there any app for mobile data diagnostics or some kind of tool which can monitor the in- and out-data of my mobile network?
My carrier is Vodafone in Germany and this is definitely not a carrier-problem since I know a lot of people with Vodafone who did not have any problems in the couple last days.
Any advice on how to proceed in order to delimit the possible causes for this behaviour would greatly by appreciated.
Thank you in advance. :fingers-crossed::fingers-crossed::fingers-crossed:
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