this post was submitted on 26 Aug 2025
902 points (99.1% liked)
Technology
74524 readers
3964 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Google has already started killing GrapheneOS by removing device trees from AOSP releases. Android 16 works fine, but for how long?
I would imagine the first thing any custom ROM would do is bypass Google's app restrictions.
I wouldn't be surprised if in 3 years I would need to pass hardware attestation to install a calculator app from the Play store.
GrapheneOS still intends to support all the supported devices until EOL. The sideloading change doesn’t affect them. It won’t apply to GrapheneOS. It only applies to certified OSes and GrapheneOS is not certified because it doesn’t license Google Mobile Services. As per the rip out of the device trees for Pixels, that just makes Pixels like other phones. GrapheneOS has been able to expand it’s automation to build that device support themselves. For new devices, making the support will take longer than it did in the past though, but they will still support those Pixels, as long as they meet the hardware requirements and still allow third-party OS support with all security features intact. Besides that GrapheneOS is actively talking with a major Android OEM right now in order to help them reach the security requirements for a subset of their future devices. They are very optimistic about tha
Its Nothing Phone right? It has to be, LG is dead, Sony has a niche, Samsung can get fucked, Moto is budget, HMD wants to be Nokia but I just dont see it, Asus?
I'm not going to participate in speculation and rumouring about this. I have an idea about who it might be myself but prefer to not talk about it. Negotations/talks are still ongoing.
AlrightKeepYourSecrets.gif
Those restrictions don't apply to custom ROMs. Yes, it's clear Google is trying to kill custom ROMs but I think we still have couple of years. Linux phones are improving fast and I think in 5 years we will end up in the same spot we were with PCs 20 years ago: you will be able do most of daily driving on a Linux phones but some apps just won't be possible to run (Authenticator apps, banking apps, Whats App, Android Auto...). Dual booting will not be possible so most probably I will end up with two phones: daily driver and work/car phone.
There are not going to be apps on Linux phones.
Definitely not banking apps.
Tbh situation looks dire as fuck.
Not with that attitude!
Get either your political ass to demand that in your country banks support more than just two OSes, or your coding ass so that you can get into programming work pipeline and one day code the Flatpak for your bank. Either would benefit you and everyone else.
Use a bank with a good web interface...
Some places are killing the web interface entirely and going app-only.
Sorry most people won't be choosing bank based on that
I guess bitcoin finally has a usecase /s
Well, most people use iOS or android, so we are talking about a very specific and dedicated bunch here.