Live data from Hacker News

Android/Linux Dual Boot

wiki.postmarketos.org

11–20 of 169 posts

Re: Android/Linux Dual Boot

#11
post #10
post #3

This will become increasingly important as Google has boiled the frog too fast while trying to force its new store policies + banning sideloading; however, all of the pieces are now in place for them to try again in a year or 2, which history shows us they will. It’s certainly time to start toying with Linux phones if you haven’t already. This year I picked up an Xperia 10 to flash Sailfish OS on—which has rough edge…

What I never get is: why not prepare to fork AOSP? I like the security model of AOSP :-).

Some people (like myself) prefer the desktop userland which is more familiar and works like you would expect as opposed to the android quirks.

eOS is basically what you are looking for for most phones or GrapheneOS (pixel only)

Re: Android/Linux Dual Boot

#12
post #10
post #3

This will become increasingly important as Google has boiled the frog too fast while trying to force its new store policies + banning sideloading; however, all of the pieces are now in place for them to try again in a year or 2, which history shows us they will. It’s certainly time to start toying with Linux phones if you haven’t already. This year I picked up an Xperia 10 to flash Sailfish OS on—which has rough edge…

What I never get is: why not prepare to fork AOSP? I like the security model of AOSP :-).

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.

Re: Android/Linux Dual Boot

#13
I installed PmOS on my old Xiaomi redmi note 9 with KDE Plasma Desktop. It works remarkably well, with the exception of sound. I am using it as a full Linux PC when I am on the go with my large power bank and a full sized folding keyboard/track pad.

For my use case it's beyond great, albeit the small screen and the aarch architecture I can develop small projects as if I was on my PC.

My current phone OP13r doesn't is supported yet by PmOS, when someone does it Im gonna try to install it on one of the slots.

Re: Android/Linux Dual Boot

#14
post #10

Earlier quoted context omitted.

What I never get is: why not prepare to fork AOSP? I like the security model of AOSP :-).

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.

> That's already happening today.

That's not a hard fork. They always rebase on top of AOSP when there's a new AOSP source release

Re: Android/Linux Dual Boot

#15
post #10

Earlier quoted context omitted.

What I never get is: why not prepare to fork AOSP? I like the security model of AOSP :-).

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.

or they already have hardware which postmarketOS supports and grapheneOS does not (or they would just prefer that hardware)

Re: Android/Linux Dual Boot

#16
post #10

Earlier quoted context omitted.

What I never get is: why not prepare to fork AOSP? I like the security model of AOSP :-).

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 to 4g didn't solve this issue. Changing all the GPS settings didn't help either.

- The obnoxious green GPS active icon makes the notification bar useless if using a GPS tracking app (or even gps navigation). The request for a whitelist was either ignored or rejected, the teams communication can come off a bit rough.

No normal user is going to be happy with Grapheneos. From what I've seen postmarketos is much more user friendly.

Re: Android/Linux Dual Boot

#17
post #3

This will become increasingly important as Google has boiled the frog too fast while trying to force its new store policies + banning sideloading; however, all of the pieces are now in place for them to try again in a year or 2, which history shows us they will. It’s certainly time to start toying with Linux phones if you haven’t already. This year I picked up an Xperia 10 to flash Sailfish OS on—which has rough edge…

> sideloading

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

Re: Android/Linux Dual Boot

#18

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…

> 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).

Re: Android/Linux Dual Boot

#19
post #14

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.

> That's already happening today. That's not a hard fork. They always rebase on top of AOSP when there's a new AOSP source release

Nobody really want a hard fork, if you can't run Android apps, you might as well use a Linux distribution.

Re: Android/Linux Dual Boot

#20
post #14

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.

> That's already happening today. That's not a hard fork. They always rebase on top of AOSP when there's a new AOSP source release

It doesn't have to be. Most of Android is fine.
Post reply on HN