zlacker

Google Pixels are no longer the AOSP reference device

submitted by tripdo+(OP) on 2025-06-12 16:53:08 | 218 points 141 comments
[view article] [source] [go to bottom]

NOTE: showing posts with links only show all posts
◧◩
3. bitpus+Z3[view] [source] [discussion] 2025-06-12 17:13:17
>>PaulHo+q
From https://news.ycombinator.com/newsguidelines.html

Don't be curmudgeonly. Thoughtful criticism is fine, but please don't be rigidly or generically negative.

◧◩
5. codeth+r4[view] [source] [discussion] 2025-06-12 17:15:06
>>yellow+o2
Yup, especially given what they posted: https://x.com/GrapheneOS/status/1932596516390072669?t=Tw_clE...
16. nixass+M6[view] [source] 2025-06-12 17:30:27
>>tripdo+(OP)
Kinda dupe

>>44254540

18. ChrisA+r7[view] [source] 2025-06-12 17:33:39
>>tripdo+(OP)
Related:

AOSP project is coming to an end

>>44254540

◧◩◪
23. bitpus+q8[view] [source] [discussion] 2025-06-12 17:38:29
>>oharap+r6
Graphene's claim of "AOSP is dead" is easily verifiable.

> This also marks the availability of the source code at the Android Open Source Project (AOSP). You can examine the source code for a deeper understanding of how Android works, and our focus on compatibility means that you can leverage your app development skills in Android Studio with Jetpack Compose to create applications that thrive across the entire ecosystem.

https://android-developers.googleblog.com/2025/06/android-16...

This was posted 2 days back.

◧◩◪
32. ChadNa+ha[view] [source] [discussion] 2025-06-12 17:47:56
>>rgreek+d8
https://open.substack.com/pub/astralcodexten/p/if-its-worth-...
◧◩◪◨⬒⬓
55. philod+Lm[view] [source] [discussion] 2025-06-12 18:37:45
>>seabro+dg
But as of the M4 Macs, Apple is preventing the Asahi team from learning how the drivers work with a “bug” in the bootloader: https://social.treehouse.systems/@sven/114278224116678776
◧◩
69. fph+QC[view] [source] [discussion] 2025-06-12 19:45:13
>>shrx+z7
In part. The stated reasons[1] are: (1) best hardware security features, such as memory tagging (2) quick patches (3) many years of official device support.

[1]: https://grapheneos.org/faq#future-devices

◧◩◪◨⬒⬓⬔
102. lipowi+t91[view] [source] [discussion] 2025-06-12 23:36:41
>>bitpus+u81
Huh? Google gives everyone in the world instructions to make derivatives of AOSP and they could install them[1] on the reference devices which were all nexus/pixel. Google said nothing until they suddenly didn't deliver for those devices.

They made related announcements in March and certainly saw interpretations of their announcement by interested AOSP derivative maintainers.

That's not remotely the same as I figured how to boot X against so and so's wishes and now it stopped working.

[1] https://source.android.com/docs/setup/test/running

◧◩◪◨
107. nichol+il1[view] [source] [discussion] 2025-06-13 01:59:57
>>kelnos+We1
Admittedly, that part was a bit tongue in cheek. Rather, I wish that is "what one does now", as I think we might live in a somewhat nicer world rather than one driven by whatever has been happening as many of us get sucked into our algorithmically-driven feeds across various web properties and apps.

Also, fwiw, you can install Play Services after installing GrapheneOS[0]. It runs in a sandbox without the same deep system access that it has on less secure versions of Android. There's no requirement here to authenticate with any Google account. You'd just have the Play Services running/available, which can be a requirement for some apps.

[0] https://grapheneos.org/features#sandboxed-google-play

◧◩◪◨⬒⬓⬔
131. Anthon+q86[view] [source] [discussion] 2025-06-15 17:14:08
>>UmGuys+cy1
> ICE kidnaps people without showing documentation on who they are or why they're being kidnapped.

Which is, again, a longstanding problem rather than some novelty introduced just now.

> Also, despite the insane cruelty that seems to be the process, both Obama and Biden deported more people than Trump.

And that's kind of my point:

https://law.ucla.edu/news/no-fair-day-damning-new-report-rev...

[go to top]