Back

what made me tweaked enough to post? realising that Google had installed a Bill Gates* in my head:

I'm upgrading a tablet released in 2014 from Android 5 (released in 2014) to Android 7 (released in 2017), and caught myself thinking of this as upgrading an "old" device to "new" software

i.e. the poisonous psychology that's sending us hurtling towards resource wars, climate destruction, and nonexistent computer privacy or security.

*of the infamous "Gates' Law Of Software" http://catb.org/jargon/html/G/Gatess-Law.html

#Google and #Samsung decided they could get away with stopping official updates for this tablet since 2015, so they did, and people are still buying their devices so I guess it worked

By comparison, and obviously #Apple are also gigantic fucking scumbags in other areas, the iPhone 6 released the same year got its last software update 3 months ago, in November 2021.

What does this "fuck it" attitude to #Android updates do?

#1 - Kills security and privacy. Next time someone is doing free PR for Google, crowing about how great Project Zero is, maybe ask how all that work stacks up against the millions and millions of internet-connected devices that Google has left out of security updates for the last *half decade* through their agreement with Samsung and other partners.

#2 - Makes absolutely fine hardware obsolete, planet-destroyingly early (but yay profits for Google and Samsung when people keep needlessly re-buying the same shit again). Extra shout-out to lazy capitalist app developers for playing their part here, taking advantage of Google's nonexistent backwards compatibility policy for the Play Store by dropping support for Android versions whenever the fuck they feel like – Rocket.chat, First Direct bank, looking at you!

"Why is #Android such a hellscape?" Part 1 - Licences

How much does "open source" mean if you have to go through 6 circles of legal hell to publish your work? "Not fucking much", I would say.

I've never had an Android device that doesn't require some kind of "proprietary blobs" to run, and the practical impact of this is a) building your own OS is a soupy hell (bless LineageOS devs for trying to make this easier, but it's still a nightmare) and b) once you've built your image, your choices of where to host it are limited to 1337-w4r3z-y sites that are going to (rightly) scare off almost everyone.

You'd think #Google, one of the world's biggest and creepiest companies could use its wide influence to make companies using Android play ball - "negotiate a licence so that people can freely distribute the drivers for your hardware, otherwise we'll change the first google result for 'samsung' to a dick pic" would be my suggested abuse of their monopoly power - but you would be wrong.

"Why is #Android such a hellscape?" Part 2 - tools

Even the most corporation-friendly interpretation of "open source" means that it needs to include the tools you need to build the software. Otherwise, what's the point?

#Google just about squeaks past on this, although the entire stack is pain... but #Samsung? "How on earth can they not release a Linux version of their tools to maintain a Linux phone", asks a wonderful naïf on XDA-developers... good question m8!

Cue a-million-and-one half-working alternatives, destined to live on in third-party purgatory for all eternity, thanks also to...

"Why is #Android such a hellscape?" Part 3 - open source, closed development

The entire history of Android has been #Google throwing things over a wall at high velocity (see also: Chromium), and with that fine example it's no surprise that device manufacturers have stuck a finger up to the entire concept of collaborative development

Want to file a bug on Samsung's desperately shitty "TouchWiz" UI? Hoping to see some of the gigantic sack of custom (allegedly open source) driver hacks needed by every device appear upstream? Bad news, comrade!

But still, credit to anything that is even *technically* "open source", as I wonder how much Google & co spent on lawyers to find a way to subvert even the limited protections of the GNU GPL - that if someone sells a thing into people's hands that's based on GPL software, they should have to provide the source code for _all_ of the software.

Anyone got a link to a repo for the Google Play Store? How about the Youtube app?

"Why is #Android such a hellscape?" Part 4 - Google Play Services

I guess a logical extension of Part 3 - if you've realised that you can freely mix and match open source / closed source code... why not start #drawbridging core functionality into the proprietary bits too?

#Google Play Services now powers so much functionality on Android (location, notifications, app installations) that it's routine for me to find devices completely non-functional until I install "Google Apps"; on this tablet, missing Google Play Services meant the setup wizard crashed for no legitimate reason.

Blessings and praise to the comrades trying to run an arms race with Google – I managed to get my tablet working with the "Nano" version of OpenGapps¹ – but Jeffrey Horatio Christ, how much Don't-Be-Evil-ade do you need to chug to think this still gives Google the right to call their software "open source" and their cartel the "Open Handset Alliance"?

¹https://opengapps.org/

"Why is #Android such a hellscape?" Part 5 - Locked Bootloaders

And another entry in "does this even count as 'open source' if ..." - how much "openness" is #Google's platform if they provide the tools for manufacturers to prevent people from installing better software, and there's no penalty for companies using them?

None.

I bought a second-hand Android phone earlier this year, released in 2015. There's a forest of better, newer Android builds for the phone... but unlocking the bootloader is entirely at the manufacturer's discretion.

I mean, bad luck and bad research from me that I didn't realise it before buying (after already doing an hour of research to decode all the ridiculous version numbers and feature differences)... but turns out I'm in the only region in the world where they just "computer says no" on unlocking.

Google never needed to allow this, regulators didn't either. Vile.

Anyway I think I'm now finally done with this death-by-wordcount rant.

Thanks again to #LineageOS, and #OpenGApps, and the people's army of posters on XDA-developers, who helped me drag this tablet a few years into the present

And some friendly new year's suggestions:

Don't work at predatory tech companies like Google and Samsung, ...

don't be friends with people who work at predatory tech companies like Google or Samsung, ...

don't do free PR for predatory tech companies like Google and Samsung...

...and maybe we'll live to see a better world

oh no, not done, forgot to explain my clickbaity "Pretend, Prevent, Profit".

It's what Microsoft would have done instead of "Embrace, Extend, Extinguish" if they'd been slightly more forward-thinking in their diabolical scheming.

PRETEND to release your code as open source.

PREVENT the majority of people from doing any of the normal things you can do with open source software, subconsciously dissolving the differences between open-source and proprietary software, diluting the term "open source", and generally sowing confusion and frustration.

PROFIT from the lovely "open" market position you've managed to claim, scooping up all the people who recognise how bullshit the rest of the industry is, and will stan you to the end of the earth for being a single micro-nano-millimetre better in any one single area.

@handle …the complexity of everything, efforts/resources it takes to do a decent job and companies cutting corners for the sake of profit or throwing stuff together to make it work. See https://social.coop/@dazinism/107499208683496497

Given the complexity of everything, I see a couple of approaches that make sense to me

Something like betrusted.io where you try & do everything in a transparent & open way

Also https://grapheneos.org/faq#roadmap as a plan for leveraging all the development in the Android ecosystem

@dazinism I didn't know betrusted, thank you, will check it out

#Graphene is definitely a philosophically right-on project, but their hardware compatibility is junk (for all the not-their-fault reasons elsewhere in the thread).

@handle
check out the updates in the Betrusted/Precursor kickstarter. Theres loads of real interesting details about the practicalities of trying to make open hardware that is as easy as possible for the end user to verify.

@handle
2of3
Maybe I'm spoiled by 30 years of Apple's highly designed OS and UX. But even my old dumb phone seems more accommodating in giving me custom snooze times on different alarms and ringtones on groups of contacts. Right now, wondering whether the cost of a Fairphone is going to be justified by the usefulness of the de-googled device which doesn't even slip into my pocket invisibly.

@handle
3of3
The experience of web browsing on a phone screen, and touch-screen interaction generally, is frustrating and unimpressive, after proper operating systems with WIMPs, desktops and full keyboards. To think that this is what most of the world now understands to be normal . .

Grumpy old man commences 2022 :( Or maybe, with a campaign for #web0 in the air too, it's a new wave ;-)

@mike_hales
Regarding reliability of alarms/reminders. I wonder if you had battery saver turned on?
This is an extreme setting and does all it can to save battery by stopping pretty much everything except the app you are using (almost everything you interact with in android is an app)

As for form factor/usability- took a while to get used to but I did. Also ever more websites are designed to work well on phones
I sometimes plug in a big display, mouse & keyboard
https://hub.libranet.de/wiki/graphene-os/wiki/GrapheneOS-workstation @handle

@dazinism
> ever more websites are designed to work well on phones
While true, many dialogues aren't 100% well thought out, and can have loops, blind alleys, narrow options?

A touch UI does have intrinsically fewer degrees of freedom than keyboard/WIMPs. Personally, I can choose to handle that by using 'a proper computer' not the phone. But I do have a sense that a majority of web users are being dumbed down by phone UI/UX.
Voice interaction? Not for me thanks. 'Writing' rules, yay!
@handle

@dazinism @handle
At last alarms & notifications seem tamed. Not doing what I would like them to do. But at least not insisting on doing what i definitely don't want them to do. I guess that's as much as a digital device user dare hope?

Must admit though, for txting (and writing generally) the android keypad and predictive text UX are way better than Apple's IOS. How come IOS text input is still clunky after all this time?

Beginning to quite like LineageOS as digital text in yr pocket.

@handle better at providing full hardware support (like verified boot) for alternative operating systems running on their phones.

Qualcomm may be a better candidate for criticism

Also the time/effort to get hardware support into mainline linux doesn't help.
https://arstechnica.com/gadgets/2021/09/android-to-take-an-upstream-first-development-model-for-the-linux-kernel/

lol - just noticed you made a load more posts in this thread I havent read yet

@dazinism no worries about the later posts, it turned into a novella

5 years of support for Pixel devices is still just tragic, and a big part of the problem to me, especially when Google has control over every single part of that device.

Original Pixel 2016 phones stopped getting updates in 2021, and it's lower-spec hardware than e.g. a TinyPhone which I could buy right now in 2022. No actual technical limitations there.

Even fucking *#Apple*, whose entire business model is "make people re-buy shit they don't need", is offering longer software support for devices.

& lastly, sure, happy to put #Qualcomm on blast too - but you don't think Google could have used their incredible market dominance to make them play ball?