Phone not locking while plugged in

bebop10

Essentially the title. I have a Google Pixel 9 Pro XL and this started happening recently. Basically, when I plug my phone in to charge, I have to either wait for the phone to lock automatically after the 2 minute timeout. OR I have to unplug my phone, press the power button to lock it, then plug it in to charge. It's weird and this just started happening recently (I'm not sure when exactly). I am on version 2026011300. I tried to check in the settings if I had toggled anything to cause this, but I did not find anything. The closest thing I could find was in the "Developer options", and saw the "Stay Awake" option but it was toggled "Off". So I don't think that is causing this. Any help would be appreciated. Thanks.

guser39

bebop10 this sounds like normal behavior. When I plug in my phone, it does not automatically lock. I have to wait for the screen to timeout.

guser39

Also, just to confirm, I did the following:

Unplug phone
Unlock phone
Plug in phone
Press power button to turn off screen
Press power button to turn on screen -> presented with lock screen

And, I also did:

Unplug phone
Unlock phone
Plug in phone
Wait for screen timeout
Press power button to turn on screen -> lockscreen

Build version: 2026011301
I don't have a P9 Pro XL, though.

bebop10

guser39 So step 4 is my problem. My bad I probably should have explained it a little better. So this is what is happening when I repeat the same steps you took.

Unplug phone
Unlock phone
Plug in phone
Press power button to turn off screen <-- This is where I have issues. My screen does not turn off. I have to wait for it to automatically lock or unplug my phone, then press power button to turn off screen then plug my phone back in.
I hope that clears up the issue I am running into.

guser39

I do not mess with or use the developer options, so I cannot comment on if that has any impact.

Novalissoide

bebop10 Press power button to turn off screen <-- This is where I have issues. My screen does not turn off

This is right of the bat abnormal.

Have Adb, Shizuku, or SystemUI-tweaker been in use at any time?
Is Developer options enabled?

Use your Auditor app and verify device integrity now.

bebop10

Normally, I would be able to go through all of the steps you went through with no problem, but for some reason I cannot turn off my screen manually via pressing the power button. I have to unplug my phone then press the power button to turn off my screen.

nandohyphen1

What if you reboot/turn off the phone? Has that been tried?

bebop10

nandohyphen1 Yea I tried that but unfortunately I still get the same behavior.

bebop10

Novalissoide Will do, I am running a remote audit via attestation[.]app. I have used ADB and Shizuku in the past to try to get RCS working on Google Messages with ATT. But since then I have disabled both ADB and deleted Shizuku. I have disabled Developer options after checking the settings to make sure nothing under that option was causing my phone to remain awake after pressing the power button. Going back to the Auditor app, is there anything I should keep an eye out for? This will be my first time using it.

Novalissoide

bebop10

https://attestation.app/tutorial
Take your time, make sure you're certain before done.

bebop10 used ADB and Shizuku in the past
Imo you should thoroughly go through your device, and manually backup any files, accounts and contacts etc, then do a full Factory reset. This will keep GrapheneOS installed, (again, fully audit your device prior to this).

Then setup everything anew using no unsupported measures and means, no Adb, no Shizuku, and keep Dev options turned OFF. This way support from Support will be far more feasible. 😉

Novalissoide

bebop10 checking the settings to make sure nothing under that option was causing my phone to remain awake after pressing the power button

The nasty thing about the developer options is that you'd never know for sure whether any observed issue stems from prior developer options settings, or even from enabling them at all, that's why these things are locked in there.

Watermelon

bebop10 Check my guide here:
https://discuss.grapheneos.org/d/28682-maximum-security-and-anonymity/4
(Item #9)
It's written in mind with local attestation, but it's relevant to remote attestation too. The “verifying device” in this case is the server. If you use the Safe Mode method as I explain there, you'll probably have to disable Airplane Mode.
Don't view the email messages from the attestation server on the “verified device”, that would ruin the security benefit of using Auditor. Don't be logged into the email account on it either.

bebop10

Novalissoide This is a good course of action. I am going to try to do an audit without having to Factory Reset my phone. But if I have to then I will; it'll just be a massive inconvenience. Thank you for the help!

bebop10

Watermelon Thank you for this detailed post, it's extremely valuable. Fingers crossed this can help me diagnose the issue, or at least get closer to finding the root cause. Thanks for your help!

bebop10

[SOLVED] Just wanted to come here and say I found the issue that was causing this. It was the Screen Saver option that was keeping my phone from locking when plugged in. Once I toggled that feature off, I got my normal behavior back.

Novalissoide

bebop10 good catch! 👍🏾 Thanks for reporting.