Question Still experiencing random reboots - Google Pixel 6

Hi everyone,
like many other Pixel 6 and 6 Pro owners, I have experienced frequent random reboots with my Pixel 6 since getting it November 2021. They became less frequent with the monthly updates, but never went fully away and occur often when it's very inconvenient. But as reports about this seem to be quieting down, I'm now worrying that for me it's not a software problem after all. So I'm reaching out to see if anyone has a suggestion for me to try out before RMA'ing it.
The reboot frequency varies from sometimes multiple reboots per day to sometimes a whole week without a single reboot. They do occur seemingly random without any apparent causal connection to a specific app. It frequently happens at night while charging when not in use, which I only notice the next morning when I get prompted to enter my SIM PIN. I feel as if it happens more often, when I open up a app which was not running before (independent on which it is) or when I try to share a resource (e.g., an image) from one app to another. Although this might only be a skewed perception on my end, as it is a bit more annoying when trying to get something done in contrast to it happening when checking the time.
The phone mostly reboots quite fast and seems back to normal, but it is also common to reboot multiple times before being able to fully enter the pin. There have also been around 6 times since November, where it bootlooped for a couple of minutes and in the process either partially corrupting the file system or executing some type of silent system restore, which causes some apps (not all) to loose state. Most notably for me is that I have to log into Spotify again, whereas most other apps tend to keep their state. One time this week it actually managed to corrupt the Google Photos app, so that it did not start even when booted into safe mode, with adb logs showing a failure to load an asset:
Code:
java.io.IOException: Failed to load asset path /data/app/~~vPG9I1zFLLjLpeetfcyDEw==/com.google.android.apps.photos-toH31kBPyggrkw-bTY1jdw==/split_config.xxhdpi.a
However, this was easily resolved by reinstalling it (or rather uninstalling and reinstalling updates) via the play store. It's more an example on how far reaching the effects of the reboots are.
Far more common is it for some apps to refuse to open app, after such a reboot until I manually reboot the phone again. Google Chrome is the app I notice it the most with, but it occasionally happens, with other apps as well. The stacktrace seems to point to an issue with GMS:
Code:
Abort message: 'Check failed: found_virtual Didn't find oat method index for virtual method: <<invalid-method-idx-314717208>>'
For troubleshooting I so far attempted the following steps:
Factory reset: While it seemed to decrease the frequency at first it went back to the usual amount of reboots within a a few day. I did restore a backup, but I don't really have the time to not do this without knowing for certain, that it would fix the issue.
Safe mode: I have not yet been able to reproduce a crash while booted in safe mode, but it was also difficult to purposefully get a reboot while booted normally.
Uninstalled certain apps: I did remove certain apps, which are not that common or are targeted towards an older Android version. This did not result in any noticeable change. Testing every app individually (as suggested by the Pixel phone help) is obviously unfeasible.
Launcher: I recently also tried out a third-party launcher instead of the stock launcher, as the launcher also regularly crashed on me and I've read in a post that this this could help. Unfortunately, this had no impact on the issue.
In the first few months, I was patiently waiting for new system updates to increase stability, since this seemed also really common. While these updates did fix some issues, e.g., frequent camera related crashes, the reboots described where not addressed. While there are some posts about such issues, I haven't found any detailed reports of a issue similar to mine. I hence tried to use adb to look into it myself. It took me a while to purposefully crash the system, while having adb logcat running, but eventually I succeeded (first time I was really happy to see a crash ). As a disclaimer, my phone is neither rooted nor having an unlocked bootloader, but I enabled the developer settings solely for the purpose of debugging this issue. I have not installed or sideloaded any apps, so all software running on the device originated from the Google Play Store. I also tried to irregularly submit crash logs via the phone settings app, but this unfortunately often resulted in another crash.
Unfortunately, I did not find any obvious cause in for the crashes in the logs:
Spoiler: adb log of reboot
Code:
05-21 22:34:10.360 27825 27835 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfe2a3f72ff1577a2 in tid 27835 (ReferenceQueueD), pid 27825 (system_server)
05-21 22:34:11.145 3626 3626 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-21 22:34:11.146 3626 3626 F DEBUG : Build fingerprint: 'google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys'
05-21 22:34:11.146 3626 3626 F DEBUG : Revision: 'MP1.0'
05-21 22:34:11.146 3626 3626 F DEBUG : ABI: 'arm64'
05-21 22:34:11.146 3626 3626 F DEBUG : Timestamp: 2022-05-21 22:34:10.510538789+0200
05-21 22:34:11.146 3626 3626 F DEBUG : Process uptime: 0s
05-21 22:34:11.146 3626 3626 F DEBUG : Cmdline: system_server
05-21 22:34:11.146 3626 3626 F DEBUG : pid: 27825, tid: 27835, name: ReferenceQueueD >>> system_server <<<
05-21 22:34:11.146 3626 3626 F DEBUG : uid: 1000
05-21 22:34:11.146 3626 3626 F DEBUG : tagged_addr_ctrl: 0000000000000001
05-21 22:34:11.146 3626 3626 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfe2a3f72ff1577a2
[...]
05-21 22:34:11.146 3626 3626 F DEBUG : backtrace:
05-21 22:34:11.146 3626 3626 F DEBUG : #00 pc 0000000000169138 /system/lib64/libandroid_runtime.so (Binder_destroy(void*)+32) (BuildId: 12e324c49b27b9ecc2ae009f81539f74)
05-21 22:34:11.146 3626 3626 F DEBUG : #01 pc 0000000000011978 /apex/com.android.art/javalib/arm64/boot-core-libart.oat (art_jni_trampoline+104) (BuildId: 4e753cd7907e1b76a7c177f849bba17384e0f9f6)
05-21 22:34:11.146 3626 3626 F DEBUG : #02 pc 0000000000032dd8 /apex/com.android.art/javalib/arm64/boot-core-libart.oat (libcore.util.NativeAllocationRegistry$CleanerThunk.run+72) (BuildId: 4e753cd7907e1b76a7c177f849bba17384e
0f9f6)
05-21 22:34:11.146 3626 3626 F DEBUG : #03 pc 0000000000308af8 /apex/com.android.art/javalib/arm64/boot.oat (sun.misc.Cleaner.clean+136) (BuildId: ad9ee401645a5135206a62ff86fc2ef5cdc29120)
05-21 22:34:11.146 3626 3626 F DEBUG : #04 pc 00000000000cbd1c /apex/com.android.art/javalib/arm64/boot.oat (java.lang.ref.ReferenceQueue.enqueueLocked+236) (BuildId: ad9ee401645a5135206a62ff86fc2ef5cdc29120)
05-21 22:34:11.146 3626 3626 F DEBUG : #05 pc 00000000000cbe1c /apex/com.android.art/javalib/arm64/boot.oat (java.lang.ref.ReferenceQueue.enqueuePending+172) (BuildId: ad9ee401645a5135206a62ff86fc2ef5cdc29120)
05-21 22:34:11.146 3626 3626 F DEBUG : #06 pc 00000000000472d4 /apex/com.android.art/javalib/arm64/boot-core-libart.oat (java.lang.Daemons$ReferenceQueueDaemon.runInternal+244) (BuildId: 4e753cd7907e1b76a7c177f849bba17384e0f9
f6)
05-21 22:34:11.146 3626 3626 F DEBUG : #07 pc 000000000001f32c /apex/com.android.art/javalib/arm64/boot-core-libart.oat (java.lang.Daemons$Daemon.run+332) (BuildId: 4e753cd7907e1b76a7c177f849bba17384e0f9f6)
05-21 22:34:11.146 3626 3626 F DEBUG : #08 pc 00000000001bf19c /apex/com.android.art/javalib/arm64/boot.oat (java.lang.Thread.run+76) (BuildId: ad9ee401645a5135206a62ff86fc2ef5cdc29120)
05-21 22:34:11.146 3626 3626 F DEBUG : #09 pc 00000000002ca764 /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+548) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb)
05-21 22:34:11.146 3626 3626 F DEBUG : #10 pc 000000000030e980 /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+156) (BuildId: 34e3dd028e2e682
b63a512d6a4f1b5eb)
05-21 22:34:11.146 3626 3626 F DEBUG : #11 pc 00000000003c1db4 /apex/com.android.art/lib64/libart.so (art::JValue art::InvokeVirtualOrInterfaceWithJValues<art::ArtMethod*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobje
ct*, art::ArtMethod*, jvalue const*)+380) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb)
05-21 22:34:11.146 3626 3626 F DEBUG : #12 pc 00000000004578ec /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+992) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb)
05-21 22:34:11.146 3626 3626 F DEBUG : #13 pc 00000000000b1590 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 53a228529316d67f22e241dd17ea9b9e)
05-21 22:34:11.146 3626 3626 F DEBUG : #14 pc 0000000000050fac /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 53a228529316d67f22e241dd17ea9b9e)
05-21 22:34:11.353 28015 28111 E AndroidRuntime: FATAL EXCEPTION: SysUiBg
05-21 22:34:11.353 28015 28111 E AndroidRuntime: Process: com.android.systemui, PID: 28015
05-21 22:34:11.353 28015 28111 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-21 22:34:11.456 30401 30438 E AndroidRuntime: FATAL EXCEPTION: highpool[1]
05-21 22:34:11.456 30401 30438 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 30401
05-21 22:34:11.456 30401 30438 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-21 22:34:11.465 30401 3636 E AndroidRuntime: FATAL EXCEPTION: [com.google.android.gms.chimera.container.intentoperation.PersistentIntentOperationChimeraService-Executor] idle
05-21 22:34:11.465 30401 3636 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 30401
05-21 22:34:11.465 30401 3636 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-21 22:34:11.475 21792 21857 E AndroidRuntime: FATAL EXCEPTION: XmppMessageRouter
05-21 22:34:11.475 21792 21857 E AndroidRuntime: Process: com.whatsapp, PID: 21792
05-21 22:34:11.475 21792 21857 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-21 22:34:11.483 28999 28999 E AndroidRuntime: FATAL EXCEPTION: main
05-21 22:34:11.483 28999 28999 E AndroidRuntime: Process: com.google.android.googlequicksearchbox:interactor, PID: 28999
05-21 22:34:11.483 28999 28999 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
This pattern seems to be consistent for every reboot, while the originating process seems to vary with mostly being Google Apps (YouTube/Google Photos) or built in services, such as search, phone, or wellbeing. The tombstones also don't reveal any more helpful information (at least to me).
I'm now at the point where I exhausted all options that I have and I'm not sure how to proceed. I have been hesitant on RMA'ing, because other people shared that this hasn't resolved the issue for them and it would be a larger inconvenience. My remaining theories are either that I have faulty hardware (e.g., bad memory), there is still a bigger os/firmware bug that causes these crashes, or if there really is an app that I installed that is causing this.
I was hoping that with this rather detailed post, someone may be able to point me in a direction on how to proceed and if my third theory is correct, how to investigate which app is the culprit. Thanks to everyone who takes the time to read this rather lengthy post, I really appreciate it!

---

ech0_de said:
I'm now at the point where I exhausted all options that I have and I'm not sure how to proceed. I have been hesitant on RMA'ing,
Click to expand...
Click to collapse
Random restarts shouldn't be tolerated with a Pixel running stock Android unmodified. Even modified the phone should be more stable than what you described. I've had a few problems, I root and sideload an app or two, but never had random restarts except for the time an OTA update borked the phone. Clean flashing the factory build fixed me up and it's been fine since. Maybe clean flashing the latest factory build (released today?) will fix yours too. If not Google owes you a stable replacement.

---

manjaroid said:
Random restarts shouldn't be tolerated with a Pixel running stock Android unmodified. Even modified the phone should be more stable than what you described. I've had a few problems, I root and sideload an app or two, but never had random restarts except for the time an OTA update borked the phone. Clean flashing the factory build fixed me up and it's been fine since. Maybe clean flashing the latest factory build (released today?) will fix yours too. If not Google owes you a stable replacement.
Click to expand...
Click to collapse
my pixel 6 is heavy modified and tweaked and i have 200 user apps installed
as far as i know i have never had a random reboot.
send that in for repair, or replacement.

---

Hi! I'm having this issue as well, since day one. Still haven't figured out a pattern, it happens while using the phone, while idle, hot and cold. I know the phone is gonna restart because it gets laggy for a couple seconds.
Funny thing is these reboots don't affect the up time. It may go for hundreds of hours even if I got many restarts.
Around a month ago the reboots stopped for around a week but then started happening again.
It is more frequent while using Twitter, Instagram and heavy games for a while. Already factory restored but still.
I contacted google but they told me this is not a known issue and I should send it for repair. The lack of patterns and frequency gave me the hope of this not being a hardware issue but I'm losing it after six months.

---

Hi! Hope this helps you: after running logcat and experiencing three reboots during it, seems that I finally found the APK that was generating the random reboots, a DirecTV app. Already uninstalled it and today is my third day in a row w/o reboots. I honestly hope this finally solves the issue, and encourage you to keep searching for the app causing the same on your pixel.

---

Thanks for the replies. After the latest update that manjaroid mentioned, I only had two reboots, but still fully random. I now gave up and RMA it, to see if they find an issue (or hopefully replace the faulty phone).
@nova90 how did you narrow it down to this app? Did the the exception stack traces in the logs originate from this app? Might be helpful for me or others, stumbling across this post in the future

---

Hi! I used my pixel for a couple of hours while connected to my laptop running logcat. Got two or three reboots and the errors pointed to that app (something like "com.directv... fatal exception..." "The system has died"). There where more than one error in every reboot, but only one repeating was the one related to DirecTV. Currently two weeks in a row with no reboots. It was actually my only issue with pixel, so I'm pretty happy with it.