Pixel 10 Pro XLConstant Cashes

Tamatis

I have been searching here and elsewhere for the last few weeks for a solution to my Pixel 10 Pro XL constantly crashing, locking up then requiring a hard restart, but no solution found so far.

Background to this is I bought a brand new phone Christmas 2025. Ran it on Google Android for 2 months to make sure the device was good, then migrated to Graphene OS. I run 3 profiles on the phone and although I use a couple of Google apps in one of the profiles (without Google play of any kind), my main profile, used 90% of the time or more, runs with open source apps only.

I have rebuilt the device from scratch several times but the crashing issues still persist. The only topic I have found on this forum that might relate to my issue is a discussion on kernel crashes; however I am unclear why this should be a persistent issue for the Pixel 10 or what a kernel related solution to fix the problem might be if that is the issue in my case.

I don't want to move away from Graphene OS as the options and privacy the OS gives is immense. Problem I have is I am a key contact for a couple of individuals with serious health issues and on too many occasions now, have found my phone in a crashed state and calls for help missed. Its an issue I cannot run with in the long term.

I would be grateful if anyone has any concrete ideas on how to resolve this problem. If I have missed discussions and solutions on this topic in the forum then please point me to them and I will be happy to read and research to get the right solutions.

If this problem remains unresolved, given my circumstances, I may be forced back into the arms of Google's OS which is a step I am desperate to avoid.

Appreciate any help given. Thank you

Johnnyloans

Tamatis

Going to settings > about phone > build number (very bottom is build number)

What does it say?

Tamatis

@Johnnyloans

Hi Johnnyloans,

Appreciate you helping. Build number is 2026050901.

de0u

Tamatis How often does "constantly crashing" mean? Does it typically run for 10 minutes, 10 hours, 10 days?

Perhaps the device has a hardware issue. Running it for a while on Google's stock OS might reveal that.

Tamatis

de0u

Hi there,

It varies. I can sometimes go for 2 to 3 days with no issues then we have a crash. Yesterday it crashed early evening and within 2 hours of rebooting , had crashed again, ie locked up with no way of accessing anything apart from holding the power button down for some time to get a reset. Overall yesterday, it crashed 4 times, reason unknown.

Re hardware, as I said in my original post, I ran the device as standard from new for 2 months before making the jump precisely because I wanted to be sure the hardware had no issues, which it did not.

I am interested in the experience of other Pixel 10 Pro XL users to see if it mirrors mine, while looking for a solution for my issue.

de0u

Tamatis I am interested in the experience of other Pixel 10 Pro XL users to see if it mirrors mine, while looking for a solution for my issue.

I don't have that device, but I don't believe there are other reports of daily crashes from users of that device.

Tamatis Re hardware, as I said in my original post, I ran the device as standard from new for 2 months before making the jump precisely because I wanted to be sure the hardware had no issues, which it did not.

Did the device start crashing roughly daily as soon as it was switched to GrapheneOS, or was there a lag?

other8026

Tamatis This may sound stupid, but it actually helps people sometimes... If you have developer options enabled, disable them. Disabling developer options resets most of the settings there to their defaults. Some settings there are buggy and can cause issues.

Also, if you have made any changes to system apps, like disabling them or changing their permissions, that can result in unexpected behavior or instability. This is why we advise people not to mess with them. If you did mess with system apps, the easiest way to fix the problem would be to factory reset.

Other than that, seeing logs would be helpful.

Tamatis

de0u

A few days after installing Graphene for the first time, I noticed one morning that the device was non responsive. Thinking the device was permanently bricked, I did a search and found I could recover the device if I went through holding down the power button for some time. Crashes have continued to happen since then for, approximately 3 months now.

Tamatis

other8026

Hi there, I don't have developer mode or developer options enabled nor have I messed around with system apps. I have simply installed the apps I need and run the device as a daily driver.

de0u

Tamatis I would suggest collecting some crash logs (perhaps posting, perhaps not), then flashing back to Google's stock OS. If after a week on Google's OS there are zero crashes then the GrapheneOS crash logs may be of interest to the GrapheneOS developers. My personal hunch is that the crashes will continue on Google's OS.

Aeleon

Tamatis Pixel 10 XL user here, I think I can recall one crash a while ago, but in months of use that has been it. Seems more stable than when I had it on pixel pro 7, 8, and 9 fold.

Tamatis

Aeleon
Thanks for letting me know.

@de0u , I am waiting for @Johnnyloans to come back as he was interested in what build number I was running (not sure if there is a significance there or not, but hoping he can enlighten me). If nothing of note, I will flash back to Google OS then flash back again to Graphene, rebuild, then see how the device behaves.

If the issue raises its head again then, as you suggest, I will capture the logs and see if the developers can help.

Thanks to you all for your help so far, it is appreciated..

de0u

Tamatis I am waiting for @Johnnyloans to come back as he was interested in what build number I was running (not sure if there is a significance there or not, but hoping he can enlighten me).

My hunch is that he wanted to verify that the device wasn't accidentally running a very old release, such as one of the first GrapheneOS releases for the device, which might have had a tendency to crash. But it appears that the device is up to date.

Johnnyloans

Tamatis

Hey, I've been preoccupied.

@de0u's suggestion is a great one. If you're still on grapheneos you can follow the beginning of this message to save all crash reports somewhere not on the phone or in email etc.

https://discuss.grapheneos.org/d/35389-after-auto-reboot-phone-stuck-on-an-unresponsive-fastboot-screen/7

I think you should be safe -- fret not :) -- for you are still under warranty to get a replacement phone should you have crash logs under google stockOS pointing to hardware issues.
(Assuming you can utilize the warranty)

Ignorant_Cormorant

Tamatis

I use the same device. I wouldn't call it crashing, but on average, every three days, my phone becomes unresponsive. The screen is black, and the only way to get out of this state is a forced reboot using the physical buttons.

But it always happened to me while switching profiles, so I knew and could restart the device immediately.

Johnnyloans

the only way to get out of this state is a forced reboot using the physical buttons.

This is the same as pulling the power plug from a desktop computer.
One day you could lose data or corruption causes the phone to not boot and you'll need to sideload the OS to fix the issue.

Ignorant_Cormorant

Johnnyloans This is the same as pulling the power plug from a desktop computer.

Yes. So what's the alternative?

Johnnyloans

All of these don't have to be done:

Back up all important data
Sideloading an OTA update replaces the entire OS
Save a bug report from developer options then turn off developer options after you're done. Keep these crash logs for later. (Changing developer options and simply having them enabled causes weird crashes and issues for some people. It is recommended to disable developer options)
Factory reset and don't change any system app permissions and don't use developer options except for locking the bootloader. (Thisll delete your data even the crash logs if you have the only copy on the phone)
Find a setting or other method to have your phone not crash
Use Google stockOS to see if the crashes still occur
Don't change your workflow and do force power offs

Tamatis

Ignorant_Cormorant
What you describe is very similar to what I have been experiencing over the last few months except mine is random, not linked to anything like changing profiles, etc.

I have been making regular backups of all my data just in case the "pull the plug" option that one is forced to use to get the device up and running again corrupts or loses data.

Seeing someone else with the same issue seems to point to a problem somewhere. As I have said previously, this issue was not there when I was running Google OS to prove the viability of the hardware before making the switch.

I will port back to Google OS over the weekend, then port back to Graphene, rebuild from scratch, then see how we go.

I will let you know how I get on.