1mo ago

GrapheneOS Developers Left To Reverse Engineer Android Early Releases

GrapheneOS (@GrapheneOS@grapheneos.social)

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.

GrapheneOS @lemmy.sdf.org

cm0002 @lemmy.world

1mo ago

GrapheneOS Developers Left To Reverse Engineer Android Early Releases

grapheneos.social /@GrapheneOS/114549099206535021

8 comments

Is this happening because Google is now developing behind closed doors and then releasing the code?
This would mean forced delay on releases.
- No, it's just a monopoly. Technically Android was already being developed behind the doors, little has changed
@akc3n@lemmy.ml another new OEM, this one using ARM cores: https://www.indiegogo.com/projects/liberux-nexx--3#/
Seems like they are also trying to find their place, they just backed off from a pretty expensive desktop replacement device to offer a more reasonable phone. Maybe an OS partnership would also help them since they are currently rolling their own Linux OS...
- I shared this with them, thanks
Have you guys reached out to Nothing? Looks like they run Android, and are a relatively new company (founded by the former OnePlus founder) that is just starting sales to the US. Maybe an angle GrapheneOS could take is to be an alternate OS install option, they are very focused on growth and attracting the privacy and security community might benefit them as they aim to squeeze out more ROI. They also seem to be cranking out new phone designs at a pretty good rate, so perhaps they could accommodate hardware requests, who knows? business@nothing.tech to inquire
- I forwarded this along. Thank you for this info.
- @ashaman2007@lemm.ee,
  We're open to working with most OEM's, including Nothing.
  Presently, Nothing's devices don't meet our hardware requirements and still have a long way to go. One example and a key main requirements is hardware memory tagging (MTE), which is currently missing on any Snapdragon-based device. We use MTE to provide a lot of our core protections against exploitation. A secure element with the required features is only one of part of our requirements.
  These requirements are part of what we need to provide strong security. Qualcomm needs to do part of that work by implementing memory tagging like Exynos/MediaTek.
  However, they might eventually release devices we could support for GrapheneOS in the future.
  
  Ah I see. One thing I mentioned was that they seem to be iterating quickly on hardware; maybe it would be worth a discussion with them to see if they'd be interested in trying to design a device with compatible hardware, specifically in order to allow GrapheneOS as an alternate option. Maybe they'd be more likely to entertain that vs other older OEMs.

8 comments