The pixel phones aren’t tied to google after you drop the graphene open source operating system on them, that’s the entire point. There are tech enthusiasts here that could explain it better than I.
But android is open source, google used it, forked it off, and are trying to make their fork proprietary or something idk, but the phones can be used without being compromised by google. They are working on sabotaging graphene quite predictably.
Google didnt fork Android, they own it. It’s also not really open source anymore since the aosp codebase is only updated every few months and doesn’t accept contributions.
I would not build something new from that. I would rather pour money into fixing the few issues with Ubuntu mobile or something similar and be rid LF Google
Motorolla has been building a phone just for graphene os, and these pixels are safe to use as such I’ve been assured, there are a lot of people in on the collaberation that know what they are doing.
Idk about ubuntu. But graphene will get the economy of scale which is key. It’s already fairly big.
The issue is not what specific vendor produces the OS, but that it should not be based upon something that Google controls. If Google stops publishing the code for the Pixel tree, GraphenOS is fucked. They already had great issues when Google stopped using a public repo and only published updates on a quarterly basis
The pixel phones’ software is not controlled by google after you download graphene, which has it’s own code, and own updates. It’s not reliant on google, as I understand it, and the soon to come motorolla phones will negate being reliant on google for anything at all.
I just looked up this ubuntu, I’ve seen the name before. From what I skimmed it’s not hardened, and 10 years behind graphene, but I don’t actually know.
You keep saying this and then repeat the same argument.
GraphenOS is entirely reliant on the devs at Google, because they update the device tree, drivers and patch security issues. If Google stopped doing that tomorrow, Graphen is fucked. They would be stuck on whatever driver they had last with all the issues that one brings.
The “only” thing Graphen adds is additional hardening and some customization and sandboxing code.
I just looked up this ubuntu
Lol, this ubuntu. Not knowing one of the, if not the single most well known Linux distro is already telling enough.
From what I skimmed it’s not hardened, and 10 years behind graphene, but I don’t actually know.
It’s not “behind” GraphenOS, it’s something entirely different. And the hardening is what money could be poured into, along with the other issues it still has. Still, none of these issues is being owned by Google.
Of course they do, especially compared to stock android. I would run it if they supported my phone.
I am not saying Graphen is bad or anything like that. Its just build on a shaky foundation. But if you have a phone that supports it, it’s a great alternative to stock
The pixel phones aren’t tied to google after you drop the graphene open source operating system on them, that’s the entire point. There are tech enthusiasts here that could explain it better than I.
But android is open source, google used it, forked it off, and are trying to make their fork proprietary or something idk, but the phones can be used without being compromised by google. They are working on sabotaging graphene quite predictably.
Google didnt fork Android, they own it. It’s also not really open source anymore since the aosp codebase is only updated every few months and doesn’t accept contributions.
I would not build something new from that. I would rather pour money into fixing the few issues with Ubuntu mobile or something similar and be rid LF Google
Motorolla has been building a phone just for graphene os, and these pixels are safe to use as such I’ve been assured, there are a lot of people in on the collaberation that know what they are doing.
Idk about ubuntu. But graphene will get the economy of scale which is key. It’s already fairly big.
The issue is not what specific vendor produces the OS, but that it should not be based upon something that Google controls. If Google stops publishing the code for the Pixel tree, GraphenOS is fucked. They already had great issues when Google stopped using a public repo and only published updates on a quarterly basis
The pixel phones’ software is not controlled by google after you download graphene, which has it’s own code, and own updates. It’s not reliant on google, as I understand it, and the soon to come motorolla phones will negate being reliant on google for anything at all.
I just looked up this ubuntu, I’ve seen the name before. From what I skimmed it’s not hardened, and 10 years behind graphene, but I don’t actually know.
You keep saying this and then repeat the same argument.
GraphenOS is entirely reliant on the devs at Google, because they update the device tree, drivers and patch security issues. If Google stopped doing that tomorrow, Graphen is fucked. They would be stuck on whatever driver they had last with all the issues that one brings.
The “only” thing Graphen adds is additional hardening and some customization and sandboxing code.
Lol, this ubuntu. Not knowing one of the, if not the single most well known Linux distro is already telling enough.
It’s not “behind” GraphenOS, it’s something entirely different. And the hardening is what money could be poured into, along with the other issues it still has. Still, none of these issues is being owned by Google.
I will take all of that under advisement. I only know what I’ve heard from OS enthusiasts, and they pump graphene principally.
Of course they do, especially compared to stock android. I would run it if they supported my phone.
I am not saying Graphen is bad or anything like that. Its just build on a shaky foundation. But if you have a phone that supports it, it’s a great alternative to stock