Hey everyone!

Quick preamble: I’m going to be posting a proper bug report. In the spirit of GrapheneOS and this community (privacy) my details will be kind of generic here. Phone is a modern a-series Pixel.

Is anyone having notably more bugs in the last few days or so?

A few examples:

Fingerprint flickering on touch with erratic behaviour, the boot options after holding the side button do not register presses properly making it difficult to even reboot. I was stuck in this cycle for a few minutes. Fix on reboot.

Switching profiles lockscreen bug, when switching back to the owner profile, the home screen with app icons is displayed in the background of the lock screen for a few seconds, before switching back to the proper lock screen background.

Certain notifications, if timed just right while the screen shuts off, persist on the lock screen until they naturally fade.

Now that I’m typing these, they all seem to be related to the lockscreen in some way. Using default launcher.

So, anyone else experienced an uptick in bugginess lately? I read through the recent release notes and didn’t see any obvious indicators, but I’m not certain.

Would like to hear from other GrapheneOS users!

Also, if you want to take your privacy and security seriously, please consider switching to GrapheneOS if you haven’t already and are able to. It’s the best we’ve got right now as far as privacy and security in a mobile OS goes.

Cheers!

  • stinkytofuisgood@lemmy.caOP
    2·
    2 days ago

    You can report at their Github issue tracker page

    There’s a few ways to make your report more useful:

    Try replicating the issue or wait for it to pop up, then save a copy of the logs at Settings - > system - > view logs.

    Include build number found in Settings - > About phone at the very bottom of the page.

    Explain it as best as you can in your own words, and include details you think might potentially be relevant such as how often it occurs, if you’re using any third party apps or launchers (ones that replace stock components), how you tried to fix it, etc.

    Please for the love of all that is private be sure to check and redact any identifying info or other info you don’t want to become public

    If all that sounds like too much work, then just post a super fast report, or post to them on social media if you use whatever they’re on, or do whatever you want. A shitty report is better than no report.