The problem is allowing the APIs it uses to exist at all in the OS is a huge security hole.
Comment on Custom ROMs have had just about enough of being Android's second-class citizens
Blackmist@feddit.uk 5 weeks agoWell that’s all very well, but I’ve got a bathroom speaker I can no longer access.
So how about instead of Daddy Google deciding what’s best for everyone, they let things run and give you a warning?
Hell, I’ve even got games I’ve paid for that are now gone. Honestly, fuck them for even thinking that’s acceptable.
conciselyverbose@sh.itjust.works 5 weeks ago
Gingernate@programming.dev 5 weeks ago
Why can’t you connect to the speaker with Bluetooth?
Blackmist@feddit.uk 5 weeks ago
It doesn’t allow direct connection. You have to dick about with a stupid app to put it in “speaker mode” first.
LinusSexTips@lemmy.world 5 weeks ago
Gives me Sonos vibes.
I won a Sonos speaker years ago, thing needed (from memory) an app to switch to AUX mode. The speaker sounded great but I didn’t want to install an app just to use the thing.
In a grand spectacle my ex’s cat kicked a potplant off a windowsill into our fish tank. That shorted a power board, we didn’t have breakers (ceramic / wire fuses) which ended up killing the speaker.
Honestly as nice of a speaker it was, good riddance.
TrickDacy@lemmy.world 5 weeks ago
That is not what’s happening. It takes tons of work to maintain backward compatibility but you’re framing it as though it doesn’t and they’re just being a holes on purpose.