Live data from Hacker News

Android/Linux Dual Boot

wiki.postmarketos.org

61–70 of 169 posts

Re: Android/Linux Dual Boot

#61
post #37

Earlier quoted context omitted.

How about calling the other one "installing from the play store"? installing was there first.

Exactly. Let's invent a word for "installing from play store". Playstoring? So we can rewrite the story to something like: Google wants to prohibit app installation on Android phones. The only way to get an app would be through playstoring.

Restricted installing

Re: Android/Linux Dual Boot

#62

Earlier quoted context omitted.

The whole selling point of Android up until now was that it allowed you to install any app you want. The point of the above comment is that Google intentionally introduced the word "sideload" to make "installing an app on your own device which Google did not curate" sound more risky and sinister than it is, and I'm inclined to agree. I "make" coffee on my keurig. If Keurig decides that making any single-serve coffe p…

"The whole selling point of Android up until now was that it allowed you to install any app you want." we can debate whether this is bad thing or good thing, it would have no ends what matters is reality, the reality is google have the right to change it.

You've changed the subject. We were discussing whether one ought to use Google's term for it, or the term that's been used to describe this action since (I assume) the beginning of personal computing. Not whether Google is legally allowed to make the change.

My reason for bringing up the "selling point" was to bring attention to the language -- "You can install any app you want" has always been the common refrain when I see friends get into a debate about IOS vs Android. People are already using the term because it makes the most sense.

Re: Android/Linux Dual Boot

#63
post #17

Earlier quoted context omitted.

> sideloading It's called installing. Language matters and I see no reason to concede this point in Google's favour.

I agree with the ethos but "banning installing" wouldn't have been correct here. There should be terminology for installing from the source of your choice which doesn't carry the marginal or sinister connotations of "sideloading" though. "Freeloading" would have been a good one but... yeah

"banning installing from anywhere but play store"

Re: Android/Linux Dual Boot

#64

Earlier quoted context omitted.

At least in regards to the security model, it is decades out of date. For example any app can listen to your microphone and spy on you at anytime. Programs can act as ransomeware or destroy all of your files. Stealers can steal your login credentials and access tokens for all your sites including banking ones.

...except in virtually any case where you'd run something untrusted there you'd use Flatpak or something similar where what you wrote doesn't apply.

> untrusted

I think the important distinction is _everything_ should be considered untrusted because even trustworthy software can become malicious. For example, the XZ Utils backdoor[0].

On Android, everything I run is subject to the permission model and sandboxed. That is not the case on Linux.

[0] https://en.wikipedia.org/wiki/XZ_Utils_backdoor

Re: Android/Linux Dual Boot

#65

Earlier quoted context omitted.

...except in virtually any case where you'd run something untrusted there you'd use Flatpak or something similar where what you wrote doesn't apply.

> untrusted I think the important distinction is _everything_ should be considered untrusted because even trustworthy software can become malicious. For example, the XZ Utils backdoor[0]. On Android, everything I run is subject to the permission model and sandboxed. That is not the case on Linux. [0] https://en.wikipedia.org/wiki/XZ_Utils_backdoor

It's not the case on Android either and it could be subjected to a XZ-like backdoor just as anything else.

Re: Android/Linux Dual Boot

#66
post #33
post #22

Earlier quoted context omitted.

You can also install through the Play store. Sideloading is more specific.

Like hacking, sideloading is now a loaded & misunderstood term. It is considered as something only nerds or bad actors do. Let's just call it alternate install.

Or "open install", correctly implying the alternative is closed.

Re: Android/Linux Dual Boot

#67
post #18

Earlier quoted context omitted.

I really wanted to like Graphene OS but I ended up bouncing off it due to a few major pain points that badly effected battery life. - Using the default 5g setting resulted in far worse battery life than stock, telling people to choose 4g isn't a solution. They desperately need something like the adaptive connectivity service. - Using Homeassistant's GPS tracking feature just destroyed the battery life, even switching…

> No normal user is going to be happy with Grapheneos. I am a normal user, extremely happy with GrapheneOS. I just don't use HomeAssistant, which seems to have been your dealbreaker in this case. I genuinely don't see a difference between Stock Android and GrapheneOS, except that I get more updates and I have more privacy controls (like scopes, but honestly I haven't had a need to use them yet).

I'd wager nobody on HN is a normal user. If you know what AOSP is, you are already way too nerdy to qualify.

Re: Android/Linux Dual Boot

#68
post #17

Earlier quoted context omitted.

> sideloading It's called installing. Language matters and I see no reason to concede this point in Google's favour.

I agree with the ethos but "banning installing" wouldn't have been correct here. There should be terminology for installing from the source of your choice which doesn't carry the marginal or sinister connotations of "sideloading" though. "Freeloading" would have been a good one but... yeah

Wouldn't it be accurate to say that you can no longer install apps on your phone, only Google can?

Re: Android/Linux Dual Boot

#69

Earlier quoted context omitted.

That's already happening today. https://grapheneos.org/ But for the reason an antiquated os like postmarketos are suggested is that the project is being opportunistic thinking this is a chance they can be relevant. Additionally, the population of HN has more sentimental view on these legacy operating systems and view it as a chance to go back to the past and use software they are familiar with.

I really wanted to like Graphene OS but I ended up bouncing off it due to a few major pain points that badly effected battery life. - Using the default 5g setting resulted in far worse battery life than stock, telling people to choose 4g isn't a solution. They desperately need something like the adaptive connectivity service. - Using Homeassistant's GPS tracking feature just destroyed the battery life, even switching…

I don't know what to say about your battery life issue, other than that I don't have any such problems.

What's obnoxious about the green GPS icon? How does it make the notification bar useless? It is on all the time while I'm using Google Maps, it's small and not in the way and is a good reminder if I have accidentally left Google Maps open in the background. What's the problem?

Re: Android/Linux Dual Boot

#70

Earlier quoted context omitted.

"The whole selling point of Android up until now was that it allowed you to install any app you want." we can debate whether this is bad thing or good thing, it would have no ends what matters is reality, the reality is google have the right to change it.

You've changed the subject. We were discussing whether one ought to use Google's term for it, or the term that's been used to describe this action since (I assume) the beginning of personal computing. Not whether Google is legally allowed to make the change. My reason for bringing up the "selling point" was to bring attention to the language -- "You can install any app you want" has always been the common refrain whe…

"You can install any app you want"

the asnwer is not anymore

Post reply on HN