Not sure if it is the same issue, but I have been having a similar problem except instead of a black screen the GOS logo comes up like the phone is rebooting (except without the sha256 code), and then boots to the owner profile. Pixel 7

    Reproduce it doesn't necessarily mean by taking specific actions known to cause it, but by using it for a few days in its default state and seeing if it happens again.

      csis01 point taken...im gonna wait till the next update and see if it continues, I get about a half a day of phone use, and a half a day of black screen out of it as of now...when is the next scheduled update btw

        freedom_warrior when is the next scheduled update btw

        About a month to coincide with the monthly security updates, unless there's new code to ship before then.

        f13a-6c3a an app crashing cannot impact the os after a hard reboot. The screen is still black even before the bootloader starts.....after doing some testing, it appears to be related to the proximity sensor on the front of the phone. When I move my hand over the proximity sensor, the phone screen goes from black, to distorted green/white, then back to black

          freedom_warrior When I move my hand over the proximity sensor, the phone screen goes from black, to distorted green/white, then back to black

          Sounds like you have a hardware failure.

            csis01 doubtful, its a brand new phone...and started within the same day as the latest update to my phone, which I think was Monday morning

              I also have a weird proximity sensor from time to time in my new Pixel 7. Usually a reboot helps.

              But after the latest beta update, what really scared me was that watching a video from Vanadium froze my screen. Like I could turn it on or off, but nothing let me get out of that screen. No back, home, reset, restart, I couldn't press anything, nor even go to the boot screen. Until I made someone call me and it just worked of after that. Man, I thought I've lost that phone! No issues after that.

                alex_herrero 1 out of every 5 times that will work for me, where an incoming call will turn the screen on...definitely a bug that needs to be fixed...i will deal with the problem for now, my only concerns is if I have to make an emergency call or something like that and cant see the screen to make it

                freedom_warrior
                Have you changed anything in developer options? Theres previously been bad UI bugs that made the device unusable that only hit people whod changed display settings in developer options.
                Its generally best to avoid changing anything in dev options as it can cause unexpected breakages. Turning off developer options may well help in this case, as I think it resets everything?

                Similarly problems can hit if you start changing settings via adb - using adb at all opens up a big hole in the security architecture of the phone and is also always best avoided.

                Finally changing permissions for system apps can also cause unexpected breakages, but it doesnt really sound likely to be the problem in this case.

                  dazinism the only developer option i had adjusted, over a month ago, was to disable the loudness by app setting

                  freedom_warrior doubtful, its a brand new phone...and started within the same day as the latest update to my phone, which I think was Monday morning

                  Hardware failures usually hit when new. If hardware survives the first month or two, then its usually good for years.

                    csis01 wiped and reinstalled and even restored same backup, with no further issue. So clearly software related. Thanks for confirming

                    The issue is specific to your setup so it almost certainly has to do with how you configured the device such as using an accessibility service causing the issue, a certain developer option or some configuration done via ADB.