Post AuORP9N5jhhB2F87HM by PVTejas@mstdn.social
 (DIR) More posts by PVTejas@mstdn.social
 (DIR) Post #AuMKTh9kyjfgyqC1RI by GrapheneOS@grapheneos.social
       2025-05-22T02:22:22Z
       
       2 likes, 4 repeats
       
       We still need help getting early access to Android 16 sources prior to the stable release in June. Every mainstream Android OEM has it. We're currently spending significant time on reverse engineering Android 16 Beta releases. It's a huge waste compared to having what we need.
       
 (DIR) Post #AuMKTiIIkS6IVdCMOe by boneca_ambalabu@mastodon.social
       2025-05-22T13:29:24Z
       
       0 likes, 0 repeats
       
       @GrapheneOS Why should we trust you?
       
 (DIR) Post #AuMKTjIL1nixc2Du5o by GrapheneOS@grapheneos.social
       2025-05-22T16:24:11Z
       
       0 likes, 0 repeats
       
       @boneca_ambalabu It's really not clear what you're asking in relation to our post.
       
 (DIR) Post #AuMKTkFBV0nOYXktoe by boneca_ambalabu@mastodon.social
       2025-05-22T16:39:05Z
       
       0 likes, 0 repeats
       
       @GrapheneOS It wasn't adressed to the post specifically. I just don't know, why people should trust GrapheneOS in general.
       
 (DIR) Post #AuMKTkrpBLhiUNpl2m by GrapheneOS@grapheneos.social
       2025-05-22T17:08:08Z
       
       0 likes, 0 repeats
       
       @boneca_ambalabu When you reply to a post, you're specifically responding to that post. We were trying to determine what you meant in relation to our thread.We've now taken a look at your profile where we can see you're actively making a series of posts with a mix of false, misleading and unsubstantiated claims about GrapheneOS. You clearly do not know much about GrapheneOS, what we do or why we take the approach that we do. You're making a whole lots of attacks on us without much research.
       
 (DIR) Post #AuMKTlU6t0KSP7kKie by GrapheneOS@grapheneos.social
       2025-05-22T17:17:40Z
       
       0 likes, 0 repeats
       
       @boneca_ambalabu Making a whole bunch of public attacks on our project, organization and team largely based on your incorrect assumptions is not a good way to start a constructive discussion with us. Why should we spend time trying to explain what we do and our decision making process to someone who has already made up their mind before doing research or asking questions? It doesn't look like someone who is engaging with us in good faith. You're also attacking Mullvad and Mike Kuketz too? Why?
       
 (DIR) Post #AuMKTm6kZLEmKxpBwm by GrapheneOS@grapheneos.social
       2025-05-22T17:29:27Z
       
       1 likes, 1 repeats
       
       @boneca_ambalabu Our very reasonable official hardware requirements are listed at https://grapheneos.org/faq#future-devices. There's no point of attacking us because of other manufacturers letting people down by not providing either reasonable security or in most cases any serious support for running another OS. We're actively working on making other hardware available for our usage. One of the barriers to this are ongoing attacks on GrapheneOS scaring away OEMs from working with us. You're not helping with it.
       
 (DIR) Post #AuORP9N5jhhB2F87HM by PVTejas@mstdn.social
       2025-05-23T16:29:03Z
       
       0 likes, 0 repeats
       
       @GrapheneOS is this related to Google no longer publishing AOSP source code while development is active?
       
 (DIR) Post #AuORPAi2lI37BVwMZk by GrapheneOS@grapheneos.social
       2025-05-23T17:44:38Z
       
       1 likes, 1 repeats
       
       @PVTejas No, it's nearly entirely unrelated. They were always doing nearly all the development internally and were never publishing the sources for Developer Preview and Beta releases. Many news articles misreported what was changed with AOSP. The changes have little impact on us overall. We always lacked early access to the sources prior to stable releases. The reason we need it much more this year is because of one of our developers being forcibly conscripted into a war, not because of Google.