My phone bugged out when navigating in the last few days every now and then (have GrapheneOS installed for about a week now, issue first occured after a few days), I'm presuming the issue lies in the custom launcher I'm using (Ratio).
I forced a reboot of the phone using the power und volume down button as the UI and hardware buttons weren't responding anymore. (Lock button didn't power off the screen).
Since the reboot after a few minutes of trying I manage to make it to the pin entry screen, the only view that (sometimes) works fluidly (but never at first). I can't make it past the home screen.
The phone runs hot and reboots after a few minutes again, coming back to the broken lock screen (doesn't respond/responds very slowly).

Does anyone know of a safe boot mode I can boot into to diagnose the issue, or a way to force the phone to use the stock launcher?

I should add that the vibration always works, regardless of the UI/screen, and it does give off double vibrations seemingly randomly/without user input.

Thanks in advance!

    PS: Push notifications still work and wake up the phone.

    arthurdent

    How do you enter safe mode?

    • Press and hold the power button until power options appear.
    • Tap and hold Power Off.
    • Hold until you see Reboot to safe mode, and then tap on the prompt.
      (The exact wording of the prompt may vary by manufacturer, but the process should be the same.)
    • Once you confirm to reboot in safe mode, wait until your phone restarts. You should now see apps and widgets grayed out, and you will only have access to the first-party features.

    Enter safe mode with device buttons

    • Press and hold the power button, then choose Power Off.
    • Turn your phone back on with the power button, and hold the power button until you see an animated logo appear.
    • Hold the Volume Down button once you see the animated logo appear.
      Continue holding Volume Down until your device boots.

    I managed to reboot by pressing the power button for 30 seconds, which seems to have fixed the issue. Changed the launcher back to default for now, hope this fixes it.