

I’m even willing to use the web apps or webpages for banking, if the browsers can make the handshakes. I’ll forfeit using the bank first party apps, if their websites are full featured.


I’m even willing to use the web apps or webpages for banking, if the browsers can make the handshakes. I’ll forfeit using the bank first party apps, if their websites are full featured.


And the bootloader is now locked down across Samsung’s ecosystem, as of this year. Sucks.
If you move to using an unsecured “chinaphone” as an alternative to the big three handset vendors, then it’s unlikely they are target devices for the myriad of uncertified ROM’s.
I think we are going to need software solutions that can run on major Androdis distributions across the variety of hardware.
I think we’re going to need something like UTM or Docker (virtualization or containerization) for running our unsigned Android apps and services, and I don’t know how feasible it will be.


This isn’t a scalable solution. There aren’t enough affordable, used Pixels for everyone in the ecosystem to adopt between now and the Goo-lag.


Samsung s22 and s25, checking in. Graphene won’t be viable for the vast, overwhelming majority of Android users today or in the coming seasons.
I hope people figure out some kind of virtualization/docker-containerization solution to the coming Goo-lag.

To be fair, these children also shouldn’t be at work, but I agree with the sentiment.
It’s the closest thing in the union to getting GDPR.
It sucks, it’s always a compromised vision, and I still love us for trying so damned hard to do the right things.