That doesn't make any sense, sorry. A developer is working on code that's not on your phone and their absence won't just cause random bugs out of the blue.
Login to reply
Replies (2)
Really? It couldn't happen if gos is compromised? As some are suggesting here. Don't hacked phones and devices act buggy when hacked and compromised?
GrapheneOS isn't compromised, the developer never had access to the signing infrastructure to push his own updates or code without peer review.
Hacked devices also don't need to be buggy. A hack showing signs of change or compromise to the user is a pretty terrible hack and is something an attacker would avoid. Most people targeted under an attack wouldn't even know it happens until it's too late.
If you're having issues with buggy components, or crashes, I recommend sending them to one of our support channels or emailing logs at GrapheneOS dot org. Users often don't report them directly to us despite us having open alpha/beta testing periods.