Help: my Pixel 8 Pro just dead this morning

fruitjammer

When I woke up this morning, I noticed my P8P was (and still is) in a completely dead mode. Nothing was displayed (I have always on display) and no matter what button (power button, volume up/down, power + volume up/down) I pressed, it just remains black. I usually put it on wireless charger before I go to sleep and I put 80% cap on battery (so I wouldn't worry about over charging). It's been working well until this morning. It was on 2025042500 before it died.

I was wondering what could have caused it and is there any way that I can bring it back?

Not sure if it's related - I have a metal plate between the phone and the case for the magnetic phone holder on my car and when I need to charge it wirelessly, I slide it down to the bottom so it would not block the charging.

other8026

fruitjammer try pushing and holding the power button for a long time, something like 30+ seconds. If it's still "on" then that'll force it to turn off.

If it doesn't turn on again, then it sounds like hardware failure.

Dominique

An idea I would suggest to try is to move your phone away from the wireless charger, and try to power it up.
Another thing to try would be to connect the USB-C charging wire in the phone, and try to power it up.
Yet another thing to try is connect the USB-A connector in a computer (instead of the transformer charger) to see if your computer can detect the phone.

fruitjammer

Dominique Thanks for the reply! Those are the things I tried immediately, but it's still not working. I guess I will have to take it to Google for warranty, it's been less than a year.

grayway2

I experienced a kernel crash with my Pixel 8 Pro today. I moved my phone from stable release to Alpha. My phone was then mmediately downloading the last update but my battery was around 10℅ so I plugged a charging cable and right away after that my phone was off.

fruitjammer

grayway2 In my case, it is not even booting up, nothing happens when I press any of the keys. I noticed that it still can charge (the wireless charger's light turned on when I put the phone on it) but that's about it.

other8026

grayway2 I experienced a kernel crash with my Pixel 8 Pro today.

If it only happens once, then there may be nothing to worry about.

Desertstorm

Hallo,

Does it help pressing fof 30seconds volume nutton when starting? My experience it did

fruitjammer

Desertstorm I think I did that, not sure if it's 30 seconds though. This morning when I press the power button, in a few seconds the 0% battery icon showed up and I plugged in the charging cable immediately and it started charging and also booted up.

Here's my wild guess ... the phone wasn't really dead, it's just not displaying anything, at all, nor it was powered down. (Maybe a super long press on the power button was able to shut it down but I'm not sure.) So within a day or so after the battery drained completely, it shut itself down and I was able to boot it up again normally.

ProfessorMonks

This happened to me yesterday too. My phone was 'dead' for 16 hours, honestly thought it was a goner.

The way I resolved was by leaving it off for a period of time (few hours) then plugging in a high powered charger (I used a 90W charger) and it sprung back to life. For some reason it was 0% battery, but had been about 40% when it suddenly froze and went black on me.

edit: I also have 80% charging option turned on. Build 2025042500. Kernel 6.1.134.

fruitjammer

ProfessorMonks This is exactly what happened to me too. I left it unplugged for a day and pressed on power button, it showed up with the charging icon of 0%. Then I plugged in the charging cable, it started to charge and booting up as well.

It is still being charged (8% now) and I'll see what will happen when it reaches 40%.

Dominique

ProfessorMonks Thanks for sharing! Workarounds like these are very useful. :-)

aintonio77

I have the same problem.

I have a brand new Pixel 8a. I tested it on the factory OS for a certain period and everything worked flawlessly. When I install GOS on it, instability starts immediately - it suddenly freezes and the touchscreen does not respond for a while, or not at all. Often the screen goes black, and I cannot turn it on for 10 - 20 minutes. I am mostly able to turn it on by putting it on the charger for 10 - 20 minutes and then trying to hold the power button for 30+ seconds or using the Power + Vol + button combination. Otherwise, after returning it to the stock OS and using it, I do not notice any problem.

Also, I am in contact with people who also use GOS, and I know of at least 3 - 4 similar cases in the last 10 - 15 days.

What could be the problem?

other8026

aintonio77 instability starts immediately

Something doesn't add up here. GrapheneOS has a fairly large number of users, so we'd know if there was an issue with the OS causing the issues you're describing here, not to mention the developers would have noticed these issues when testing. Could it be that the OS works fine but you make some changes like disabling system apps or that you installed the OS following instructions other than what's on the website?

edit: Maybe I'm wrong. See the project account's post below, though some of the things you mentioned like the phone freezing and being unresponsive may not be related.

TrustExecutor

fruitjammer I had the same issue one time with my P8Pro. It was just "dead" and I had to hold the power button for a very long time until it suddenly booted up. The battery was still decent, around 30-50% when it happened.

@"GrapheneOS"#p145843

It was around this time period it happened. It hasn't happened again since.

GrapheneOS

There are recent reports of 8th gen Pixels having their display turn off while powered on due to a recent firmware or driver bug introduced in the March or April Android updates. You can hold power + volume up in that situation to force it off.

We don't know when this 8th gen Pixel firmware/driver bug got introduced and have no details about the issue since there are 0 relevant crash reports or logs submitted at this point. We need the logs from the boot when it happens, not after rebooting, so someone would probably need to have an existing ADB connection established when it happens to obtain the logs that are needed.

GrapheneOS

Please let us know if it ever happens again on the latest 2025050300 release. It's possible the issue is caused by an upstream Linux kernel bug introduced via the Linux LTS revisions. It seems more likely that it's from an Android/Pixel update in March or April.

fruitjammer

GrapheneOS Will do. Looking forward to 2025050300 release. Unfortunately I am not well versed on how to do the ADB thing, I'll see if I can learn about it a bit more.

aintonio77

GrapheneOS

My problems persist and continue. I've tried everything, but the phone just dies at some random moment (the screen goes black). It's becoming harder to wake it up. Today, I couldn't manage for several hours, and when I finally did, I was met with a crash log. I hope it can be helpful.

I'm experiencing random freezes and black screen crashes on my Pixel 8a running the latest GrapheneOS build 2025050300.

I managed to capture a crash log showing a fatal audioserver crash caused by a HAL timeout:

TimeCheck timeout for IAudioFlinger::setParameters scheduled 13:01:36.156
HAL pids [ 819 ]
Blocked directly due to HAL call: DeviceHalAidl::setParameters

Stack trace includes:

DeviceHalAidl::filterAndUpdateScreenParameters
DeviceHalAidl::setParameters
AudioFlinger::setParameters

Full crash log indicates a 5-second hang during a HAL parameter update, followed by SIGABRT of audioserver.

This seems consistent with recent reports about display/power/audio issues caused by upstream firmware or driver changes on 8th gen Pixels.

Could this be part of the broader HAL-level bug affecting device stability?

I will try to catch logcat output.

type: crash
flags: dev options enabled
osVersion: google/akita/akita:15/BP1A.250405.007.B1/2025050300:user/release-keys
uid: 1041 (u:r:audioserver:s0)
cmdline: /system/bin/audioserver
processUptime: 0s

abortMessage: TimeCheck timeout for IAudioFlinger::setParameters scheduled 13:01:36.156 on thread 3351\12Timeout ms 5000.00 (3000.00 + 2000.00) elapsed steady ms 5000.4292 elapsed system ms 5000.4399\12HAL pids [ 819 ]\12now 13:01:42.293\12secondChanceCount 1\12analysis [ Blocked directly due to HAL call: DeviceHalAidl::setParameters scheduled 13:01:36.156 deadline tid 3351 ]\12timeout [ { IAudioFlinger::setParameters scheduled 13:01:36.156 deadline :39.156 tid 3351 } ]\12pending [ { DeviceHalAidl::setParameters scheduled 13:01:36.156 deadline tid 3351 } ]\12retired [ { DeviceHalAidl::setParameters scheduled 12:57:34.542 deadline tid 3351 } { DeviceHalAidl::setParameters scheduled 12:57:34.542 deadline tid 3351 } { DeviceHalAidl::setParameters scheduled 12:57:34.542 deadline tid 3351 } { IAudioFlinger::setParameters scheduled 12:57:34.541 deadline :37.541 tid 3351 } ]\12timeout/blocked(3351) callstack [\12 #00 pc 00000000000d6c4c /apex/com.android.runtime/lib64/bionic/libc.so (ioctl+12) (BuildId: 76b3eba33cd561e774657995ea2278a4)\12 #01 pc 00000000000752d0 /apex/com.android.runtime/lib64/bionic/libc.so (ioctl+160) (BuildId: 76b3eba33cd561e774657995ea2278a4)\12 #02 pc 0000000000070290 /system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel, unsigned int)+928) (BuildId: 2cd513dc58381b06245e5d299a023ead)\12 #03 pc 0000000000069cc0 /system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel, unsigned int)+160) (BuildId: 2cd513dc58381b06245e5d299a023ead)\12 #04 pc 0000000000014164 /system/lib64/libbinder_ndk.so (AIBinder_transact+356) (BuildId: 6e2311b16a352a4ccfb8cd8b477d59c4)\12 #05 pc 0000000000031bc8 /system/lib64/android.hardware.audio.core-V3-ndk.so (aidl::android::hardware::audio::core::BpModule::updateScreenState(bool)+184) (BuildId: d7f6fb28341a3231b0e2d234b3975e58)\12 #06 pc 0000000000139758 /system/lib64/libaudiohal@aidl.so (android::DeviceHalAidl::filterAndUpdateScreenParameters(android::AudioParameter&)+664) (BuildId: 53b2a699defb22a185d0ebf20a1ebd02)\12 #07 pc 0000000000118d50 /system/lib64/libaudiohal@aidl.so (android::DeviceHalAidl::setParameters(android::String8 const&)+624) (BuildId: 53b2a699defb22a185d0ebf20a1ebd02)\12 #08 pc 00000000000bbf80 /system/bin/audioserver (android::AudioFlinger::setParameters(int, android::String8 const&)+1232) (BuildId: b05d2b90b85236fede0957821f627869)\12 #09 pc 00000000000dfdec /system/lib64/libaudioclient.so (android::AudioFlingerServerAdapter::setParameters(int, std::1::basic_string<char, std::1::char_traits<char>, std::1::allocator<char>> const&)+348) (BuildId: c7ab771374405850805c294791999ae4)\12 #10 pc 000000000003d36c /system/lib64/audioflinger-aidl-cpp.so (android::media::BnAudioFlingerService::onTransact(unsigned int, android::Parcel const&, android::Parcel, unsigned int)+11228) (BuildId: 8568a30cd6cd2a276ec3336a7fed47c2)\12 #11 pc 00000000000c99b8 /system/bin/audioserver (android::AudioFlinger::onTransactWrapper(android::AudioFlingerServerAdapter::Delegate::TransactionCode, android::Parcel const&, unsigned int, std::1::function<int ()> const&)+952) (BuildId: b05d2b90b85236fede0957821f627869)\12 #12 pc 00000000000e4b2c /system/lib64/libaudioclient.so (non-virtual thunk to android::AudioFlingerServerAdapter::onTransact(unsigned int, android::Parcel const&, android::Parcel, unsigned int)+172) (BuildId: c7ab771374405850805c294791999ae4)\12 #13 pc 000000000004cdf8 /system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+904) (BuildId: 2cd513dc58381b06245e5d299a023ead)\12 #14 pc 0000000000062728 /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+392) (BuildId: 2cd513dc58381b06245e5d299a023ead)\12 #15 pc 000000000006257c /system/lib64/libbinder.so (android::PoolThread::threadLoop()+28) (BuildId: 2cd513dc58381b06245e5d299a023ead)\12 #16 pc 00000000000174b0 /system/lib64/libutils.so (android::Thread::_threadLoop(void)+256) (BuildId: 274a8cdc4c5e66e75ecd8c9a36dfd8ff)\12 #17 pc 000000000001b088 /system/lib64/libutils.so (libutil_thread_trampoline(void) (.uniq.226528677032898775202282855395389835431)+24) (BuildId: 274a8cdc4c5e66e75ecd8c9a36dfd8ff)\12 #18 pc 000000000007b134 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_start(void*)+180) (BuildId: 76b3eba33cd561e774657995ea2278a4)\12 #19 pc 000000000006bc64 /apex/com.android.runtime/lib64/bionic/libc.so (start_thread+68) (BuildId: 76b3eba33cd561e774657995ea2278a4)\12]

signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: binder:902_5
MTE: enabled

backtrace:
/apex/com.android.runtime/lib64/bionic/libc.so (ioctl+12, pc d6c4c)
/apex/com.android.runtime/lib64/bionic/libc.so (ioctl+160, pc 752d0)
/system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel, unsigned int)+928, pc 70290)
/system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel, unsigned int)+160, pc 69cc0)
/system/lib64/libbinder_ndk.so (AIBinder_transact+356, pc 14164)
/system/lib64/android.hardware.audio.core-V3-ndk.so (aidl::android::hardware::audio::core::BpModule::updateScreenState(bool)+184, pc 31bc8)
/system/lib64/libaudiohal@aidl.so (android::DeviceHalAidl::filterAndUpdateScreenParameters(android::AudioParameter&)+664, pc 139758)
/system/lib64/libaudiohal@aidl.so (android::DeviceHalAidl::setParameters(android::String8 const&)+624, pc 118d50)
/system/bin/audioserver (android::AudioFlinger::setParameters(int, android::String8 const&)+1232, pc bbf80)
/system/lib64/libaudioclient.so (android::AudioFlingerServerAdapter::setParameters(int, std::1::basic_string<char, std::1::char_traits<char>, std::1::allocator<char>> const&)+348, pc dfdec)
/system/lib64/audioflinger-aidl-cpp.so (android::media::BnAudioFlingerService::onTransact(unsigned int, android::Parcel const&, android::Parcel, unsigned int)+11228, pc 3d36c)
/system/bin/audioserver (android::AudioFlinger::onTransactWrapper(android::AudioFlingerServerAdapter::Delegate::TransactionCode, android::Parcel const&, unsigned int, std::1::function<int ()> const&)+952, pc c99b8)
/system/lib64/libaudioclient.so (non-virtual thunk to android::AudioFlingerServerAdapter::onTransact(unsigned int, android::Parcel const&, android::Parcel, unsigned int)+172, pc e4b2c)
/system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+904, pc 4cdf8)
/system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+392, pc 62728)
/system/lib64/libbinder.so (android::PoolThread::threadLoop()+28, pc 6257c)
/system/lib64/libutils.so (android::Thread::_threadLoop(void)+256, pc 174b0)
/system/lib64/libutils.so (libutil_thread_trampoline(void) (.uniq.226528677032898775202282855395389835431)+24, pc 1b088)
/apex/com.android.runtime/lib64/bionic/libc.so (pthread_start(void*)+180, pc 7b134)
/apex/com.android.runtime/lib64/bionic/libc.so (start_thread+68, pc 6bc64)

EDIT: I don't see option to upload log file.

Elgoog

I have a similar problem today with my p8a after having let the battery run down over night:

I either air charge or plug the phone into a charger; battery is warm and it does charge (see item 3, below), but screen is completely blank.
I hold the ON button for about 30 seconds and see the usual sequence of screens "Your device is loading a different operating system...", Google splash, animated GrapheneOS logo, and finally the usual lock screen, showing a charge of 52% at last try.
After a few seconds, the screen goes black, and I'm back to square one.
If I touch the fingerprint reader immediately after the lock screen appears, the PIN screen comes up, as it should. But the phone still shuts down before I can enter the PIN.

I've been through this cycle 5 times now, and still can't get the phone to work.

If I hold VOLUME DOWN during boot up, the words "Safe Mode" appear on the lock screen, but the phone still shuts down within a few seconds.

Three days ago, the screen repeatedly blacked out for a few seconds when I tried to view a calendar while on a phone call.

I'm now looking for solutions online.

Help!

Elgoog

Elgoog Technique no. 2 in this video:

https://www.youtube.com/watch?v=5lJVSS6iUkc

has rescued me:

Once the lock screen appears, tap the POWER button firmly 4 (four) times (not 5: that might place a call to the emergency services).

Dominique

Elgoog Thanks for the workarround! :-)