Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There are three major national carriers (a fourth launching soon), and an absolute glut of smaller MVNOs which offer devices on their own terms. Most of both the national carriers and the MVNOs will also allow you to bring your own device, which as long as isn't running Android, is probably not encumbered by malicious code.

Even if the horrors you suggest are true, consumers would have options to get around them, whilst right now, a single monopoly, Google, controls the entire playing field, and actively attacks anyone who tries to offer a path around (Epic, for instance).

The "ISP bogeyman" issue constantly feels hollow in tech circles considering there's a ton of actual competition in the provider space, and a complete and unassailable monopoly in the tech platform space.



Nearly everything you've said was bullshit.

Google has never restricted sideloading. Android 12 even enables sideloading further by allowing third party app stores to auto update.

AOSP exists. Third party roms exist. All of the devices sold by Google can be unlocked to install third party roms.

LineageOS doesn't exist because 'a complete and unassailable monopoly' allows them to.


Google admits it tries to prevent sideloading as much as possible in their own court filings with Epic. Their own managers called the experience "abysmal", and they considered buying Epic to prevent them from doing it. Also they sent Project Zero out to portray Epic as "insecure" in a bunch of hit pieces across the media.

AOSP is not meaningfully existing on any device sold today.

The fact you can hack your device doesn't change the monopoly Google operates that 99.9% of Android devices are trapped in.


[flagged]


> [citation needed]

https://www.theverge.com/2021/8/6/22612921/google-epic-antit...

> An unlockable bootloader isn't a hack. Try again.

Several apps rely on successful SafetyNet verification to start functioning. A unlocked bootloader will trip this and apps stop functioning. Current solutions to overcome this is a cat and mouse game.

https://www.xda-developers.com/bypass-safetynet-hardware-att...


What was said:

> Google admits it tries to prevent sideloading as much as possible in their own court filings with Epic.

Your citation?

Still shows that sideloading is possible.

Derp.

That's not preventing sideloading. Some one time steps remind the user that there are risks to sideloading something that can't be trusted.

Like I said to the other guy, I knew what he was referring to and it was wholly disingenuous to make the claim that he did.

Sideloading. Is. Not. Prevented.

It is cautioned against.

Big difference.

The article claims 15+ steps, which is absolute bullshit.

-- 1) Open Chrome.

-- 2) Find and Download APK. https://i.imgur.com/ZFZb1uE.png

-- 3) Accept warning and Open APK.

-- 4) Go to settings. (This only has to be done once) https://i.imgur.com/R8FzTzP.png

-- 5) Toggle Install Unknown Apps for Chrome. (This only has to be done once) https://i.imgur.com/K0ADO2q.png

-- 6) Click back (This only has to be done once)

-- 7) Click install. https://i.imgur.com/xVSndex.png

-- Done. https://i.imgur.com/fyasTK9.png

On no. That was really hard.

After the first time it takes a whole whopping, astounding, IMPOSSIBLE.... 4 steps. Open browser, download APK, open APK, click Install.

IMPOSSIBLE, I TELL YOU!

Don't even need to enable Developer Options in Android. No iOS developer cert needed. No host computer or one week expiration like Apple does it.

And guess what? Sideloading has always been possible on Android. Always.

This looks like something Google is doing to make it too difficult to sideload? ("Google tries to prevent sideloading as much as possible" I believe was said) Well, shit, whoever finds this difficult should not be sideloading apps in the first place.

> Several apps rely on successful SafetyNet verification to start functioning. A unlocked bootloader will trip this and apps stop functioning. Current solutions to overcome this is a cat and mouse game.

However, this doesn't change the fact that unlocking the bootloader on a device where a bootloader can be unlocked... is NOT A HACK.

Safetynet as a consequence of unlocking the bootloader is a known trade off. Security vs the ability to modify the system files. Seems completely fair to me.

The way you guys go about this, how you get so much wrong in the process that the disingenuous replies barely mask that your contempt lies with Google regardless of how anything is actually done.

You created an account to jump into a thread where you merely propagated the previous user's fallacies? Really?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: