Develop Bugs

File based encryption or Full Disk encryption

I flashed Nougat's factory image on my 5x a week ago. After playing for a while i noticed the encryption change option in 'Developer Options'.
Also, read that new devices will be coming with File based encryption since it allows direct boot mode.
Is there any performance difference if change the encryption to 'File based' ? I read few user reviews and they were saying that changing encryption to file based did improved little performance.

I'm also interested in this. So bump for a more knowledgeable member to comment.

I think this thread proved pretty conclusively that there is no real world performance benefit in decrypting.
I activated file encryption on my N5X, specifically to allow for direct boot. I had N with full disk encryption on my N5X for about 72 hours before switching. I see no performance difference -- it was smooth before, and it is smooth now.

rockhardy said:
I flashed Nougat's factory image on my 5x a week ago. After playing for a while i noticed the encryption change option in 'Developer Options'.
Also, read that new devices will be coming with File based encryption since it allows direct boot mode.
Is there any performance difference if change the encryption to 'File based' ? I read few user reviews and they were saying that changing encryption to file based did improved little performance.
Click to expand...
Click to collapse
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.

sfhub said:
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
Click to expand...
Click to collapse
Thanks for your comment.
In that case i think i will be switching to File-based encryption to enjoy direct boot feature.

sfhub said:
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
Click to expand...
Click to collapse
Hey but can you tell me why the phone reboots in pocket ?
My phone also reboots in midnight when I set a fingerprint on it .
So will decryption solve this issue ?
Thanks in advanced

ABSathe said:
Hey but can you tell me why the phone reboots in pocket ?
My phone also reboots in midnight when I set a fingerprint on it .
So will decryption solve this issue ?
Thanks in advanced
Click to expand...
Click to collapse
My phone never reboots, but some people have set ups that do. It is usually some bug in Android that is triggered by some software you are running or there is some data corruption in your system.
First thing to try would be booting in "safe mode"
https://support.google.com/nexus/answer/2852139?hl=en
If the reboots stop, then it is some app you are running.
If that doesn't narrow it down, try factory reset, then install under new android account, install a couple of apps at a time, until you see reboot. If it reboots right away on fresh install on new account, then you might have hardware issue.
I seriously doubt decrypting your user partition will help with your reboots, but you are welcome to try. If it does help, it will probably be coincidence because you had to format user partition to decrypt your phone which is equivalent of factory reset.

sfhub said:
My phone never reboots, but some people have set ups that do. It is usually some bug in Android that is triggered by some software you are running or there is some data corruption in your system.
First thing to try would be booting in "safe mode"
https://support.google.com/nexus/answer/2852139?hl=en
If the reboots stop, then it is some app you are running.
If that doesn't narrow it down, try factory reset, then install under new android account, install a couple of apps at a time, until you see reboot. If it reboots right away on fresh install on new account, then you might have hardware issue.
I seriously doubt decrypting your user partition will help with your reboots, but you are welcome to try.
Click to expand...
Click to collapse
Actually this issue is there from the first day I started using my phone .. but booting in safe mode does not give any reboots so far and also fingerprint is working nicely too
So I guess I will try factory reset .. can I do it using the option already present in settings ? Or should I flash a factory image ?
Thanks

ABSathe said:
Actually this issue is there from the first day I started using my phone .. but booting in safe mode does not give any reboots so far and also fingerprint is working nicely too
So I guess I will try factory reset .. can I do it using the option already present in settings ? Or should I flash a factory image ?
Thanks
Click to expand...
Click to collapse
Before you do factory reset, I suggest you get rid of any pin/pattern/password you might have configured. This will disable the factory reset protection, just to be on safe side.
You can do it from android.
If you say this problem was there from beginning, then it probably migrated over from existing account restoration of apps. You might want to try installing onto a new google account to test that theory out. The install a couple of apps at a time while verifying everything remains stable.

Hi,
Do folks think that switching to File Based Encryption might help avoid this issue - a decryption failure on reboot with Factory Reset the only solution? My phone is 13 months old and now out of warranty and this has happened 5 times to date - once about 6 months ago, once about 3 months ago and then worryingly 3 times in the last month. Stock unmodified on 7.1.1

Hey, When will TWRP support this? I've been waiting for ages.....

8.1 OTA reset my tablet

This morning I received the Android 8.1 OTA, it took over an hour to process and when it had finished my tablet had been wiped.
Not happy!

Hi same thing happened to me . I called Google up and they gave me a useless answer.
All I can say to others is do not update to 8.1 just yet or back up your data.
Did you by any chance have your bootloader unlocked?

Bhushan8128 said:
Did you by any chance have your bootloader unlocked?
Click to expand...
Click to collapse
I can't remember, it's possible...

Reset for me, and bootloader is NOT unlocked for either device we have (at least I was the first to take the update, so can plan for my girlfriend). Didn't expect this. Especially after the update to 8.0 left things alone. I had JUST started to install apps with data (long time flasher... left these stock, so I tend to avoid non-cloud apps, especially without root backup options).

Wish I'd come on here half an hour ago. Just got the notification about the update and has wiped mine as well.
Sent from my Pixel 2 using Tapatalk

Same here. Just did the OTA. Basically new tablet, never unlocked the bootloader etc..
Interestingly I could not initialize the tablet as new device.
The error I got was that the device was resetted and only the previous owner can go on with the setup (something like this).
I logged into my Google account and now my Pixel C is loading the backup.
But I highly doubled that many of my apps settings were backuped.

In the same boat. Jumped straight into the OTA when prompted, ended up with factory reset and all internal storage wiped. Stock ROM, only thing possible unusual we that when I first went to install it complained I didn't have free space. Fixed that and tried again, ended up reset and wiped.

with my Pixel C it is looping between "Google" and "erasing" and getting no further

Got the OTA update too and it wiped my device, good thing I just brought it so had nothing on it

Amazingly incompetent - who do they think they are - Apple?!

TimSharrock said:
with my Pixel C it is looping between "Google" and "erasing" and getting no further
Click to expand...
Click to collapse
I tried factory reset, and it seemed to make no difference, but I left it looping for several more hours, and it eventually booted into a wiped state. I reconnected it to my account, and is now merrily reinstalling everything from the backup

I just updated with adb sideload and full OTA Image. No wipe for me.

Apparently this is now fixed, time will tell.
https://productforums.google.com/forum/#!topic/nexus/rwWqnT_397c

constant "Bluetooth keeps stopping"

I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.

iwestfall7062 said:
I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.
Click to expand...
Click to collapse
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation

billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.

billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
The error happened once immediately after a full factory image flash before I had downloaded a single program or changed a single setting, so I don't see how it could be bluetooth settings, battery optimization, wifi/bluetooth scanning, or a rogue app. Oddly enough, since posting this last night I've managed to go 12 hours without an errors after flashing the Sept 2018 factory image. buuuuuuuut now I'm afraid to upgrade to Android 10 again.
jd1639 said:
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.
Click to expand...
Click to collapse
Thank you for making sure I understood this. Yeah, I generally factory reset my phone and laptop once a year so I always back everything up before a reset. And yeah, I haven't changed anything from stock on this phone since I've had it, so unlocking and locking the bootloader should never cause any issues. As I told Billy, the Sept 2018 image seems to have fixed the problem, fingers crossed.
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.

iwestfall7062 said:
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.
Click to expand...
Click to collapse
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.

jd1639 said:
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.
Click to expand...
Click to collapse
Yeah, I mean I would much prefer being on Android 10 and having the latest updates, I normally update as soon as they come out. But, given that I flashed the Jan 2020 image and bluetooth was still broken, and then flashed the Sep 2018 which seems to have fixed it, I'm hesitant to go back to the Jan 2020 updates. Kind of tending towards the if it isn't broken, don't fix it philosophy right now. If I had time to monkey around with my phone all the time I wouldn't mind, but the semester just started and I use my phone for everything at school so I don't really have time for it to be not working. >.< Such an odd issue and odd fix.

Looks hardware related, like the cable is loose.

wangdaning said:
Looks hardware related, like the cable is loose.
Click to expand...
Click to collapse
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.

iwestfall7062 said:
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.
Click to expand...
Click to collapse
What do you have Bluetooth connected to when it happens?

jd1639 said:
What do you have Bluetooth connected to when it happens?
Click to expand...
Click to collapse
Nothing. It doesn't matter whether anything is connected or not. It literally happened on first boot up of a fresh flashed Jan 2020 factory image, before I had put a single thing on the phone.
Generally I have my Fitbit Versa connected, I got 2 tiles awhile ago, but first troubleshooting thing I did was remove the app and delete those from bluetooth since those were my latest additions to bluetooth. I have backbeat fit headphones I use sometimes, the same with bose soundlink ii headphones, ps4 controllers, a jbl pulse 3, my car radio. But I factory restored all of those items so they weren't trying to connect to my phone, and then flashed the factory image. So I don't see how it has anything to do with an actual bluetooth connection.

Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10

JJT211 said:
Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10
Click to expand...
Click to collapse
Yeah, I wish this thread held a solution for you. I've searched and searched and tried every solution I've found on google and nothing has worked, and really none of the threads I have found have ever had a concrete solution either, just one or two people going "well I did THIS and it worked", and a bunch of people saying it didn't work for them. I just cannot fathom how a full factory flash back to the very first image would not revert the changes that came with Android 10. That's why I was questioning whether or not a factory flash replaces driver binaries. It's the only way I could see the factory flash to Sept 2018 not fixing our issue. (Other than it really being a hardware issue, but that doesn't seem possible to me.)

Oh wow, you're still having same issues on Android 9??
Im still on Android 10, most recent update. I did do a full factory flash a few weeks ago and it was quite the improvement. But I still do have the Bluetooth/radio issue every once in a while, like yesterday.
I wonder if it's a hardware issue and/or substandard hardware performance that Android 10 made more prevalent? That's something we'll probably never know

I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.

wangdaning said:
I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.
Click to expand...
Click to collapse
Oh no, I didn't think for a second you were being rude. And I appreciate your idea, just with what I'm experiencing with my specific phone it doesn't seem to be a hardware issue.
Strangely enough, the issue has been tapering off as of late, after the factory resets I just continued to use my phone while I wait to figure out if I can get a refund or a warranty replacement, etc. The issue has been occurring with much less frequency since then. Still happens, but not like it was.

Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.

JJT211 said:
Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.
Click to expand...
Click to collapse
Yeah, mines been better for like 4 days, and then it just crashed and rebooted by itself earlier today.

has anyone gotten to the bottom of this yet? it seems to be a result of the play store system update being "stuck" on Sept 1st...even if you get it to download to the current version, currently March 1st, after a reboot it will not show the March update has been applied. And should it actually show that the March update has been applies, within a day the phone will reboot and the bluetooth bug will return, strangely the update to the play store system reverts to Sept 1st.
I'm having this issue with my son's phone. I tried unlocking the bootloader and flashing the factory img from April but of course the bug is still there, and after signing in the Play Store system is of course dated Sept 1st

There is no fix. I made an official Android Issue Tracker thread.
https://issuetracker.google.com/issues/151033055
and a Google Pixel Phone Help thread.
https://support.google.com/pixelphone/thread/32828289?hl=en
Google's being ****ty about it. I eventually just bought a new Pixel 4 XL. I needed a functional phone for school and work, and as much as I hate to spend money on another Google product after this mess, they do make the most powerful pure android phones with the best camera. Ebay FTW, $600, never giving them another penny directly.
If you still have warranty, get it warrantied immediately, and don't take no for an answer. I dawdled around thinking it would get fixed and even though I reported that I was having issues with it directly to Google's phone support BEFORE the warranty expired, by the time I called a second time and pushed a manager to see if they could warranty it, my warranty had expired so they told me to go jump in a lake.

to make it worse, Google told me the phone still has an extended warranty but I'm not the original owner and have no way to contact that individual. But you need that person's email address for it to work. So it was purchased but because of this technicality it's null and void. I get the security of it but it's still garbage

Question Boot to bootloader after update

Hi,
Last week, when my OnePlus 9 Pro updated OTA to OOS 11.2.8.8.LE15BA, I have had an issue.
At the end of update, when the phone has rebooted, it rebooted to bootloader.
My phone is not rooted, bootloader locked, never unlocked.
During at least 30 minutes, I've tried to reboot it, by the bootloader menu. Every time, it rebooted to the bootloader.
After 10 or 15 tries, it rebooted well, on OOS.
It's very strange (but I'm happy that it works great now)...
No problem now if I reboot my phone.
So I would like to know if someone has had that kind of issue... What could be the cause?
And now I'm afraid of future OTAs. Do you think that if it happens one time, it could happen every time?
And if it happens again, is there a method to reboot it with success, and no stress
Thanks in advance for your help

You have to be patient.

Can happen due to a messed-up upgrade, happened once to me on my OnePlus Nord. Your best bet is to go to recovery and erase data if nothing managed to work. Make sure to backup any important data before updating. I can only hope that things go well, considering how our future updates can be directly based off on Color OS, instead of AOSP.

Thank you @oddlyspaced .
2 things to do when the next OTA will be pushed : save everything and pray .
So if there's an unsolvable issue, I would erase all data and reboot

Question February Update caused my phone to reboot all the time

Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?

How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com

fil3s said:
How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Directly through the phone's regular system update.

WHOneedsSOX said:
Directly through the phone's regular system update.
Click to expand...
Click to collapse
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked

WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?

fil3s said:
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked
Click to expand...
Click to collapse
That's correct, it isn't unlocked.
RetroTech07 said:
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?
Click to expand...
Click to collapse
I have done absolutely no modifications other than typical downloading of apps and modifying through there but even that is just theming. By "try again," just wipe and then reinstall the update?

WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).

As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.

Morgrain said:
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).
Click to expand...
Click to collapse
I'd be happy with 2 random reboots per day. Not even kidding, I must be at 100 a day. It's super random too. None from 9 am until around 1pm and then all of a sudden 10 in a row.
I'm pretty sure it's a software issue, had no random reboots before I installed the February update. Will probably try reformatting the entire phone first and see how that goes.
DanielF50 said:
As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.
Click to expand...
Click to collapse
Thanks, will try this out if a reformat doesn't work.

Try safe mode and see if it still happens.

neyes said:
Try safe mode and see if it still happens.
Click to expand...
Click to collapse
Still happened in safe mode.

I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.

RetroTech07 said:
I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.
Click to expand...
Click to collapse
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?

WHOneedsSOX said:
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?
Click to expand...
Click to collapse
Official Google Android Flash Tool

roirraW edor ehT said:
Official Google Android Flash Tool
Click to expand...
Click to collapse
Thanks!