Live data from Hacker News

On non-rooted Android 17, ADB uninstall of system apps fails

github.com

131–140 of 203 posts

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#131
post #60

Earlier quoted context omitted.

You can't sideload iOS applications. Meaning there's no point to doing any of the listed things.

You technically can sideload. For 7 days or on TestFlight

This is not a practical way for installing apps though.

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#132

This sucks. I use adb to uninstall all of the system apps like facebook, youtube, web browser, etc. to give myself a minimalist, distraction-free phone that still has niche apps, maps, and communication apps. Might have to look into the expensive light phones as an alternative now if this update hits my phone.

You have never been able to uninstall apps from the /system partition with adb (without root). You have only been able to disable them to stop them from showing up.

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#133
If you don't have root, you are not the device owner, you are a lessor to whatever companies and carriers are subsidizing your out of pocket costs. This includes iPhone and it's walled garden approach (delete Siri - you cannot, GBs of space is permanently wasted on most users and it still drains the battery when fully disabled). Locked, unlocked, and root are terms the general public has no clue about.

Whenever someone buys an unrootable phone, ask them if they enjoy living under HOAs. That's the same level of control they've agreed to without root. Framing it this way will neatly land your point and just maybe reset their concept of what they should have purchased.

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#134
post #29

Earlier quoted context omitted.

And Graphene OS is also anti-user by being tremendously rude about NOT providing root and using the same tired "suck-u-rity" crap Google and Apple also use. If you're smart enough to buy a phone that supports GrapheneOS, AND install it, yeah you should have root. And tools like XPrivacy and plugins allow control of subsystems like GPS spoofing and lying to apps.

If you are technical and want root its very easy to patch a build of GrapheneOS to include whatever mechanism you want. You can even automate this to continue to receive updates. I think the decision of GrapheneOS to maintain the attestation features and not providing user root is what gives it a fighting chance of being accepted as legitimate 3rd choice. See: Revolut and others adding GrapheneOS keys and trusting th…

Just to note Revolut are quite famously anti-security and GrapheneOS have had to work around attempts to ban it on a few occasions. You may have meant the swiss finance app Yuh or something else.

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#135
Could someone explain this bit?

> many system apps run in the background after being uninstalled, but it's unknown whether they do when disabled.

Is this because some real system apps (as opposed to vendor bloat that just got the "system" flag through bribery) have components in the OS outside the "app" framework that genuinely can't be removed?

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#136
post #91
post #86

Earlier quoted context omitted.

Not really. They weren't saying if it existed in the EU it'd have to surveil. They were saying if the EU government created it it'd have to surveil.

Honestly your reading comprehension is not good today. They said if the government “drive the process of forking” which could mean encourage a group of academics to do it, or a commercial consortium. It does not mean the EU government take on the task themselves. * It is self evident from actual EU behaviour that any mobile os that gets to users will be legally required to be a surveillance disaster area, regardless…

If the EU government told a group of academics "hey, go make a phone" it wouldn't have mass surveillance. If it insisted on being closely involved in the process, then it would.

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#137

Earlier quoted context omitted.

Well that was the original android phone idea. Get a hackable open device that you can write apps for your self. Even attach third party hardware to it for extra functionality with lots of customisation. But this idea has mutated quite a bit.

I fully agree with it. But I think Google also understands that the platform is unatractive for businesses. In my case I just don't do Android app because I know it is easy to just take and hack. It is not the case on iPhone. And my app is one time payment so the ability to just copy out the APK leaves me not doing an app at all...

The fact that app piracy is more prevalent on Android has nothing to do with technical differences between iOS and Android side loading, and everything to do with the markets in which iPhones and Android phones are popular.

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#138
I have a Moto, possibly my 10th.

With each new phone, the first thing I do is initiate an ADB session to begin (a futile attempt at) removing all unnecessary bloat. If I thought it wouldn't be flagged, I'd print a list of the unbelievably superfluous slop on a stock Moto (or any Android), and Moto is better than average -- but my comments have been getting flagged a lot lately and it's not worth the work.

Each year, the process becomes more and more restrictive, and what was nuke-able last year, is immutable the following. Because it's much easier and not much less relevant, I will print a list just of the Play Services festering in the background, viewable through 'developer options'. See:

    CrisisAlertsPersistentServices; LifeCycleService; SndDetectionService; GmcService; OfflineBeaconService_Persistent; ContextManagerService; PersonalSafetyService; AuthenticatorService; SuggestionsProvider; ReceiveSurfaceService; SendSurfaceSrvice; IntegrityApiPersistentService; GmsCoreStatsService; LifeCycleService; EmergencyPersistentService; SemanticLocation-Service; LockScreenService; SchedulerService; GoogleLocation-Service; GoogleLocationManagerService; LocationsPersistentService; DiscoveryService; Google Play Services
And that is after ADB removals, and after disabling as many of the related "services" listed above as I can. There are many other "services", eg all the Moto crap, Wireless Emergency Alerts (which is 'disabled' but runs anyway), along with the cached services.

Disabling as many of those as I can, the phone runs fine, with the obvious exceptions, such as google disabling certain apps that depend on the background festival.

The last I commented on this, I was attacked for being anti-Google, or something. But when I acquired this phone, if I remember correctly, I bought it, not leased it. My first smartphone was from 2017, and was a Pixel. I was never satisfied with the liberties it offered, but compared to each proceeding year, it could reasonably be considered utopic. With covid, contact-tracing, or the components thereof, were hard baked into the services suite. And then everything in general just got a lot worse.

My point here is not to rant, even if I am a bit. It's more so me sitting here in a mixture of awe, and cynical awareness, beholding how obtrusive, anti-user, brazen, opportunistic, self-serving, and ridiculous Android has become, and how little can be done about it, and how over time, the user's ability to do something about it, has been progressively chipped away, and is now essentially nothing, and this is all, by general consensus, just fine.

And we keeping getting stronger and faster phones. Imagine how strong and fast these phones would be without the festering festival in the background. And maybe, think of the landfills, and lithium mines. Or, just freedom and dignity, an endangered duo near extinction.

Re: On non-rooted Android 17, ADB uninstall of system apps fails

#140
post #18

GrapheneOS has minimal, private [1] system apps so you don't have to debloat anything yourself. Manual debloating is not a good solution at the user level. Some system apps are being overhauled, so that's something to look forward to. Gallery will be [2] based on ReFra [3]. [1] Except phone and messaging but that's the cell network. GrapheneOS recommends Signal/Molly or SimpleX instead. [2] https://nitter.net/Graphen…

GrapheneOS or other custom ROMs don't solve the actual problem that you can't just buy a smartphone and install any operating system like you can with an actual computer, despite technically being one. Also, GrapheneOS supports device attestation (the non-google kind at least), which is still ridiculous as such systems have no benefit to people, only to technofeudalist corporations.

> install any operating system like you can with an actual computer

This is in practice only true of IBM PC compatibles these days, you really can't install any OS on modern Macs. Maybe you can on (some?) Chomebooks?

Post reply on HN