How does this affect termux? Is it going to die or is it only going to be able to have packages that are from registered developers?
this post was submitted on 07 Oct 2025
817 points (98.9% liked)
Technology
75967 readers
3597 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
That's actually a really interesting question.
I understand that Apple takes issue with packages that can themselves "take packages". But historically, I don't believe that Google has. Of course, Google also hasn't done the registration thing historically, either.
load more comments
(3 replies)
Thankfully I have root, I'll just simply hook into it runtime via Xposed to bypass this nonsense.
Seriously anyone who doesn't have root on their Android devices these days and age, well may Google have mercy on you lol
I used to root every phone, but by 2025 I've given up. Hard to unlock bootloaders, random apps (especially banking) thinking you will get hacked and stops working, the entire community around rooting and mods is like 10% of what it used to me, hardly any modern phone still gets custom roms, etc.. Recently saw some statistic about custom roms - on average, around 50 phones 5-8 years ago had support for custom roms. By 2025, that number has fallen to 4.
Android is not what it used to be
load more comments
(1 replies)
Are you certain you'll be able to do this? Do you have more info?
Recent AOSP repo added lines of code to Package Installer to handle enforcing restricting whether Package Installer installs an APK file or not based on dev signatures, as well as denying installation if internet isn't available so it can't contact Google's servers for dev signature verification.
So this is enforced by Package Installer, which is already how Google enforces their ridiculous minimal SDK version requirement for installing APK packages, as well as for blocking app update with an APK package with mismatched signature or blocking downgrading an existing app with an APK package, which I already have bypassed via Xposed this way.
Besides, rooting gives YOU total control over your own device like when you have sudo on Linux, even if Google tries some new BS there will be a way to counter it when you have root
load more comments
(4 replies)