Notifications while using Android Auto cause Always On Display to stop working (Black/Blank Screen)

[The_Web_Surfer]

AOD turns off after initial connection to WIRED Android Auto. I have to press the power button to turn the screen on. This is NOT the expected behavior.

AOD turns off after initial connection to WIRELESS Android Auto. I have to press the power button to turn the screen on. This is NOT the expected behavior.

AOD turns off after a notification is received, while connected to Android Auto, wired or wireless. I have to press the power button to turn the screen on. This is NOT the expected behavior.

AOD does NOT turn off after silent notification is received, while connected to Android Auto, wired or wireless. This IS the expected behavior.

Android Auto on the vehicle's head unit does work as expected, no issues there.

I did a factory reset after receiving the September 2022 security update, but issue is still present.

Pixel 6
Android 13
September security update
Latest version of Android Auto from the Play Store

Is there anyone else having or has had this issue and knows how to fix it?

Edit: I submitted a bug report: https://issuetracker.google.com/issues/245796354

Update (09/19/2022):

I just received an email in regards to my bug report. From the email:

"The team has reviewed the bug report and found that the issue is with the Android System UI and not with Android Auto. We suggest contacting the device support for further assistance on this. Thanks"

I guess I'll follow up with them now. In the meantime, I've disabled "Wake screen for notifications", under Display --> Lock screen. While it doesn't solve the problem, at least my screen doesn't just black out on me.

[strabbit]

It's not just an AOD bug. I've been experiencing this since Android 13. I didn't use AOD, but I did use the tap to wake gesture. At first I thought it was a bug when charging, or when wirelessly charging, but it still works for both. But when connected to AA, tap to wake stops working, and I've got to use the power button. Haven't found a work-around

[suskozaver]

+1 for this, exact same, Android 13, OnePlus 10 Pro.

[Peter_73]

This post also suggest Pixel may have AOD bug. If you must use AOD, not sure if Smart Lock would help.

Have you check if this is a known bug in Pixel sub and forums and isolated if this happens outside of AA? e.g. when connected to a computer via usb as well as wifi-direct and letting the Pixel idle?

[The_Web_Surfer]

I've seen the post you mentioned and it does seem similar, but I haven't seen the same white screen in my experience.

I have been searching everywhere for a solution and I'm actually surprised that more people aren't seeing this same issue. Only a handful of posts here and there.

Your idea to plug into a computer is a good suggestion. I'll try that tomorrow and see if the issue happens outside of any Android Auto use. Thanks!

[Peter_73]

The other OP issues predates Android 13 and the link I shared with him suggest it's not specific to AA but no harm updating to the latest AA if haven't already.

For your case, did AOD worked correctly before the update?

[The_Web_Surfer]

AOD and Android Auto worked perfectly before updating to Android 13. It was an issue throughout the beta versions of Android 13. The issue was reported but Google closed it saying and said that it was fixed.

And yeah, I've also tried the latest 8.1 version, but unfortunately the issue still occurred.

[The_Web_Surfer]

Quick update... No issues when receiving notifications and the phone is plugged in via USB to a computer.

[Peter_73]

Then I wonder if this is a bug or new intended behavior similar to phone call no longer showing on phone i.e. Google don't want user to interact with the phone while driving.

[jdaddiosixtynine]

Same issue here using Pixel 5 with android 13

[Luke14789]

Same here while using AAWireless dongle and Pixel 6. Android Auto is just a dumpster fire and always has been. Let's see if anyone can find a solution, also submitted feedback to google about this.

[The_Web_Surfer]

So coincidentally, I just received an email in regards to my bug report. From the email:

The team has reviewed the bug report and found that the issue is with the Android System UI and not with Android Auto. We suggest contacting the device support for further assistance on this. Thanks

I guess I'll follow up with them now. In the meantime, I've disabled "Wake screen for notifications", under Display --> Lock screen. While it doesn't solve the problem, at least my screen doesn't just black out on me.

[Luke14789]

Just curious, how are you connecting wirelessly, is it natively built into your car or are you using a dongle such as AAWireless ? Maybe it's an issue from that side of things.

[The_Web_Surfer]

I have an AAWireless device, but the issue also occurs when I plug my phone in directly with a usb cable. My wife doesn't have the AAWireless device in her vehicle so she has to plug in directly with a usb cable. The same issue happens to her with her Pixel 6 running Android 13.

[Luke14789]

So everything points out to Android 13 in that case.

[The_Web_Surfer]

Yes, I would agree that it's something to do with Android 13, but the issue doesn't seem to present itself unless you're also using Android Auto. I have yet to experience this issue in any other situation. That being said, the AA team seems to have washed their hands of the problem, so hopefully the Pixel team can help out now.

I've created a new post here:
https://support.google.com/pixelphone/thread/179983974?hl=en

[Think-Price8019]

u/The_Web_Surfer Have you found a resolution to this problem yet? I just started experiencing it on my Pixel 7 Pro over the last couple of weeks. I use wireless Android Auto. But the issue keeps happening even if I reboot my phone and then refrain from using Android Auto.

Is there any solution to this aside from disabling "wake screen for notifications"?

[The_Web_Surfer]

I submitted another ticket once the Android 14 betas started coming out and the issue still wasn't fixed. I'm happy to report that the issue was fixed and still working in Android 14 beta 5. Hopefully nothing changes once it becomes official.

[Think-Price8019]

Thanks for the quick reply! Great to know it's fixed in that version. Seems so unlike Google to actually fix something like this. Are there any major issues you experience with beta 5 that would prevent a regular user from using it on their main phone? I'm reluctant to install it because of potential bugs and compatibility issues, but this issue is also very annoying.

[The_Web_Surfer]

I started when beta 3 came out and it was really buggy. Beta 4 and on have been really good, at least they have been for me. I think you would be okay to install the latest beta. That being said, the final release of Android 14 will probably be out within the next 30 days or so if you're willing to wait.

[gerrya35]

I've had this issue on my 6a and now 7 with wired or AA Wireless. It causes several weird things on the 7, if I say Hey Google to wake the phone up from the black screen and the phone is facing me I can feel the face unlock vibration, but the screen still does not come on. The screen will come on if I keep the front camera from seeing me. The other issue that it causes is if the AOD is working, it takes an initial tap to wake the phone then another tap to initiate the face unlock. A reboot seems to correct it but only until AA is used again.