Google pushes a new feature to Android where phones wake up at 2:22 AM every night to play a blood-curdling scream at maximum volume, regardless of settings. An issue is created and gets assigned, into which Google employees regularly butt in to explain the feature exists to keep users safe from night break-ins. Nothing changes. People have to start modifying their lives around this problem—most have to shut off their phones during the night, many had to buy a separate alarm clock—and masses of disappointed customers eventually make their way to the bug tracker to voice their concern. The issue gets locked as "too heated".
replyApple has had this feature for three years on iOS. What else should they have done?
>What else should they have done?
replyUse an AOSP fork like grapheneos or lineageos. Barring that, voting with their wallets and buying a HarmonyOS phone. If for whatever reason they're doing that too, there's probably more powerful forces behind this change (eg. government mandates) that won't be helped by spamming an issue tracker.
Downside is those specific forks only work on very specific devices, when there's countless great hardware in the wild with shit software.
replyAnd apparently a lot of people can't access their savings with grapheneOS. I know eventually I'm going to end up carrying 2 devices.
replyI have bad news for you if you think GrapheneOS isn't going to accept this patch from upstream if it lands.
replyGraphene would probably make it an option, like how it asks you if apps should be able to access the internet.
replyThat's a non-issue because you can build (or patch+resign) grapheneos yourself.
replyBut if you do it fails attestation which turns the phone into a paperweight.
replyYou think wrong, "mob" is a collective way of criticizing a policy.
replySure, there are differences in types criticisms, but then try to actually articulate those and address whatever you think the issues with those are