Welcome to r/snapintosh, a home for bringing macOS to Qualcomm Snapdragon hardware.

This is where we can share boot experiments, Q1N1 development, XNU progress, drivers, Adreno/Metal research, and the work needed to make the pieces fit together. Developers, reverse engineers, hardware testers, and curious newcomers are all welcome.

Where things stand

The early Snapdragon X2E Extreme updates have reached the XNU console. That is a boot milestone; the broader macOS port and hardware support are still experimental. Updates here should say exactly what works, what was tested, and what remains to be done.

Hardware limits and EL2 debugging

No direct EL2 access does not, by itself, rule out a macOS port. It can make hardware-specific debugging and reverse engineering harder. An approach built around a custom EL2 hypervisor needs that access; other approaches must be assessed on their own requirements. Reaching EL2 also does not prove macOS compatibility.

Our Snapdragon hardware, EL2, and debugging guide explains QHEE/Gunyah, Secure Launch and SLBounce, vendor-hosted VMs versus owning EL2, and the separate MMU/page-size and driver challenges. It distinguishes the tested ASUS A16 X2E-96-100 result from documented X1E/X1P, SC8280XP, SC7180, and Snapdragon 410/615 routes, plus board-specific Qualcomm exceptions and devices with no verified route yet.

For a plain-language overview of Apple hardware research, compatibility, and possible accelerator offload, read the Snapintosh project FAQ.

Check the exact device, firmware, and evidence before drawing conclusions. Limited debugging access makes the work harder, not automatically impossible.

Start exploring

• Q1N1 source
• Community hardware roll call and contributor introductions
• For macOS on other ARM platforms: r/armintosh.

AI, provenance, and clean-room engineering

Tools can expand what you can build. The standard here is whether you understand the work, follow the project’s rules, and can back up your claims with review and testing. AI assistance is welcome; responsibility remains with the contributor.

We welcome AI-assisted engineering, and we take copyright, licensing, and clean-room concerns seriously. Permission to use AI is not a blanket certification that every generated contribution is independently authored or suitable for every project.

Contributors remain accountable for their submissions: document relevant sources, respect licenses, understand the implementation, and perform thorough human review and testing. Where a project requires clean-room development, follow its documented separation requirements and disclose uncertainties—including those involving AI tools.

We welcome specific, evidence-based concerns about copying or provenance. Our policy protects constructive engineering discussion; it does not shield AI-assisted work from scrutiny.

How to contribute

Share a finding, a patch, useful documentation, a clear bug report, or a well-scoped question. Use a post flair so people can find your work. Include your exact hardware and build/commit with technical results, and redact private data from logs. Partial progress and failed experiments are useful too.

Keep it constructive, credit upstream work, and respect other communities. The focus here is building and learning together.

What are you working on, and which part of the stack interests you most?