Great, missed another hospital call because Android *again* spontaneously failed to make any noise when I got a call, even though the phone was literally right next to me the entire time
How the fuck do you develop a phone OS and make the *primary functionality* of a phone not work reliably
So I just caught my Android in the process of breaking; it went off, made no noise, "getting called" animation was showing on the screen, but swiping up did nothing, it just bounced back down and didn't pick up the call. Didn't matter how often I tried.
So yeah, it's definitely just the phone app that's fucked.
I am clearly not the only one with this problem: https://support.google.com/pixelphone/thread/144103327/unable-to-answer-calls-when-phone-rings?hl=en
@zarel I haven't, but there's exactly the problem described in that thread: it's a non-deterministic failure and I can't just keep it running in safe mode forever.
(My phone is not a Pixel, it's an Oukitel, and it seems to be manufacturer-independent)
@joepie91 You have a Pixel but haven't installed GrapheneOS?
@freakazoid My phone is not a Pixel, no.
@joepie91 did you try to boot in failsafe mode?
happened to me as well (pixel 6a). It's really annoying.
I like the experience overall but I hope to find another manufacturer for the next phone, some things are really stupid e.g. I can't know what is connected to the hotspot or put a limit on the number of devices