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!
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.
For me it also “blocks” input to the homescreen… I don’t know if is the OS thought as I can freely pull down the notification thingy and click everywhere. Lawnchair bug…?
About the only thing I’ve noticed is sometimes I’ll tap the display but it doesn’t light up. I had this issue on my 6a. It’s more frequent on my 10a. Pressing the power button turns on the display. A reboot temporarily fixing the problem.
My dad has a 6a running GrapheneOS and hasn’t mentioned this happening to him.
This explains some things. Yay fixes!
Good to know. I was noticing stuttering and slowdown type issues since the update
Praise the privacy gods! And the GrapheneOS devs too hehe
I hope this fixes the majority of recent issues. Thanks for the link.
no problem!
Ahh so it’s not just me! Glad a fix is on the way, I’ve been having a bunch of performance issues since the last update.
I’ve been having some problems as well lately. For example sometimes I just can’t take a Screenshot or more general performance drops
Now that you mention it, I was also having a performance issue where my phone was heating up quite a bit for no apparent reason. I stopped all background apps and tried battery saver, etc.
But my phone was eating more mA than usual. Restart helped.
So maybe there’s a common bug that’s recently popped up.
Not those issues, but I think there are some performance issues. On my Pixel 10 Pro I’m seeing a lot of apps with screen flickering issues. I turned down the screen resolution and killed a few apps with the force stop option and this seems to have resolved it temporarily.
The most annoying issues were in the Transit app which works way better than Google Maps for transit navigation in my city and another city I’m currently visiting. Also noticed it in Finch and a couple of games. I’ve seen it before in GrapheneOS, but never this bad or even at all on this particular device.
I’ve been informed in this thread that a (pretty important) fix is on the way. Hopefully that is the root of what seem like some pretty widespread issues.
This is happening currently, might explain some of the behavior: https://lemmy.dbzer0.com/post/76359803
Oh mah gawd yesterday I had a sneaking suspicion about Android 17 QPR 1 because of how Google is fucking everyone using AOSP over. But the devs seemed confident (if not frustrated) in their implementation, and I’m not a security researcher.
If this is actually the cause of so many issues, that’s a relief to know but also really sad because it’s something the devs are gonna have to contend with until god knows when…
IT feels kinda laggy and badly responding at Times since the Last update. Rebooted a few Times already
Agreed! By the way, if you’re using a non-stock launcher, maybe try checking if stock fixes any of that for you. I noticed with Lawnchair 16 (stable and nightly) that I had real issues with app switching being buggy.
Obviously use whatever launcher you want, but it’s a troubleshooting step!
Thanks for pointong Out. I’m on the stock launcher. There has been a new Update a few hours ago and it seems to be fixed
I haven’t seen anything like this either, though I have noticed that when I stop listening to music or a podcast that the lock screen controller seems to stay on there longer than it used to. It might be related to your notification bug. I’m running a Pixel 7 if that is anything to note.
Interesting. Not that I’m glad you’re having bugs too but a widespread bug is a high-priority bug.
Side note, I wish it was possible to disable album art and thumbnails on the lockscreen and control panel controls with the default launcher!
Idk anything about privacy or security but I switched to GrapheneOS over a year ago and have no complaints. I do get some minor things like arcane “attestation failure” warnings but nothing that has really affected my phone usage. I will note that I’ve been using the Nova Launcher for like ten years so idek what the difference is from the normal launcher
Any reason somebody switches to GrapheneOS is a good reason!
If you’re up to it, you might want to submit that attestation failure issue. Somebody will see it, and it might just get fixed. Or at the very least, somebody might be able to help you troubleshoot.
It’s just a toast with a warning, do you know where I’d find a full error log and where to submit it?
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.
I’m having an issue where if I get that lockscreen switchover bug, it tries to open my keyboard and then half - loads the background with black cutoff below it. Also if the phone rings while I’m in the middle of an action (can’t recall specific at the moment) but sometimes I won’t actually be able to see the incoming call notif at all.
Yes this is very similar to one of the bugs I’m getting! So I’m not alone in that. Gives me confidence that a fix is likely in the works. Will obviously still submit my own bug report though. The devs earned that bit of telemetry haha
Haven’t ever had anything like this on my Pixel running Graphene. Seems more like some odd corruption of OS files than an implementation bug in the OS’s code itself to me.
This reminds me that I’ve yet to set up complete backup of my phone.
It’s not Halloween yet please don’t mention OS corruption 👻
Using what for full phone backup?
I use Synology Drive for much of my stuff which backs up to my (really old) NAS. I also use cryptomator for some things. I also do a lot of manual backups because I made the habit and some things just aren’t easy or necessary to automate.
For the record, I know Synology sucks but I bought this NAS before they started pulling that BS about third party drives and removing codecs etc. I keep the NAS offline, tailscale only (sorry not doing Headscale). And for anyone in the same boat about the codecs, there’s a Github project I helped a tiny bit on which patches back in the old codecs and prevents synology from updating over it. If you want the link lemme know!
Edit: while I’m on the tangent of Synology I want to add that somebody came up with a script to activate many of the features which require device registration. All of it can be done offline and with no external scripts. Here it is!
I haven’t been having any bugs lately. What kind of phone do you have?
A modern a-series Pixel. How about you?
