If Google actually takes away the ability to run unsigned code, my next phone will be an iPhone. And I rarely even run unsigned code.

Honestly, it might finally result in me fully exiting the Google ecosystem.

▲

still_grokking 7 minutes ago | parent | next [-]

Just to switch to an even more aggressively monitored and tightly controlled walled garden?

People sometimes act as if the one would be an viable alternative to the other. Even both are effectively the exact same shit for the exact same reasons.

How about we move instead to open systems?

▲

matheusmoreira 5 hours ago | parent | prev | next [-]

> If Google actually takes away the ability to run unsigned code, my next phone will be an iPhone. And I rarely even run unsigned code.

Same here. If I must be in a walled garden, then I will choose the better kept garden and it sure as hell isn't one of Google's crappy platforms.

The only reason to put up with the shittiness of Android is freedom. The same freedom they keep eroding with their constant, never ending attempts to force remote attestation and sideloading limits.

GrapheneOS is the last hope for Android as far as I'm concerned. Hopefully Google won't find ways to screw that up.

> it might finally result in me fully exiting the Google ecosystem

Don't wait for them to push you away. Start exiting now. Setting up mail on my own domain and distancing myself from gmail is one of the best things I've ever done. Highly recommended.

▲

b112 4 hours ago | parent [-]

I've noticed with GrapheneOS, that more recent builds are exhibiting weird issues. This isn't their fault, it's upstream ASOP issues. For example, just in the last few weeks:

* The date has now gone missing from my lockscreen, only showing the time.

* I can no longer see signal strength on my phone for mobile, if wiki is off. I turn wifi on, and now I can. I use a larger font, but it used to be just fine.

There are all sorts of little changes like this I've noticed recently.

It makes me wonder if Google is slowly mangling default ASOP so projects like GrapheneOS will have a crappier daily build experience.

And GrapheneOS doesn't have time to manage features changes like this, they focus on their key security improvements and fixes. If Google is doing this on purpose, it has real potential to seriously degrade ASOP as usable without lots of fixes and changes.

They already rug-pulled security updates or whatever it was a few months back.

And it really seems like the sort of sneaky, underhanded way Google would handle things.

▲

garciansmith 3 hours ago | parent [-]

Odd, I don't have those issues (date is on the lock screen, network signal strength when wifi is off is there). Played around with font settings but that changed nothing. Up to date stable version of Graphene on an 8a. Are these beta versions? Or maybe it's phone dependent.

▲

b112 2 hours ago | parent [-]

Do you have 'Receive security preview updates' on?

Google stopped publishing any info about security updates until (I think) quarterlies come out. GrapheneOS had to sign some sort of non-disclosure for them, in order to roll them into updates.

If you don't have that on, then you're not fully up to date with security updates. This could be the difference.

	▲	still_grokking a few seconds ago \| parent [-]
		> GrapheneOS had to sign some sort of non-disclosure for them, in order to roll them into updates. So doesn't this mean GrapheneOS is effectively controlled by Google now? Also, how is keeping anything secret under NDA possible at all if you want to know what's in a security update and be actually able to build that update yourself from source?

▲

state_less 7 hours ago | parent | prev | next [-]

Buy a cheap unlocked smartphone and run GrapheneOS[0]. I want my smartphone to be like my linux computers where I run them for as long as the hardware works and is still relevant. My iPhone 12 is getting close to its end of life support, yet it is still working well. We should expect better from trillion dollar companies. So I'm not supporting them with dollars wherever I can afford not to. That and I think it's more enjoyable to run something off the beaten path. I like to explore the space a little.

I swapped out my MBP for an Asus Pro Art running linux last year and that's been working out pretty well. Hopefully my cheap motorola phone will be supported by GrapheneOS soon and that will work out too.

https://news.ycombinator.com/item?id=47241551

	▲	drnick1 5 hours ago \| parent \| next [-]
		> Buy a cheap unlocked smartphone and run GrapheneOS Note that this needs to be a Pixel at the moment.
	▲	ysnp 3 hours ago \| parent \| prev [-]
		GrapheneOS will support future Morotola phones that meet a subset of their requirements, rather than existing phones. Less likely to be budget lines for now.

▲

ipaddr 5 hours ago | parent | prev [-]

One walled garden to a bigger walled garden.

	▲	intrasight 4 hours ago \| parent [-]
		That is the human condition - up to the scale of the planet, which is the ultimate walled garden at the moment.