Devices and contribute
Which phones run it, and how to help
Only the Pixel 3a XL is ported. Other phones are a shortlist, chosen by SoC family and bootloader. Reports from people who test other phones go into the same matrix.
Device matrix
The Pixel 3a XL status comes from the roadmap. Shortlist rows are candidates, not ports.
| Phone (codename) | SoC | Status | New work |
|---|---|---|---|
| Google Pixel 3a XL (bonito) | SDM670 | kernel, storage, Wi-Fi, LTE calls | Calling C7, power, daily use |
| Google Pixel 3a (sargo) | SDM670 | candidate | Same SoC: the SoC support carries over |
| OnePlus 6 (enchilada) | SDM845 | candidate | A UFS storage driver, the main cost of the family |
| Google Pixel 3 (blueline) | SDM845 | candidate | As OnePlus 6 |
| Fairphone 4 (fp4) | SM7225 | candidate | UFS and newer clock and power blocks |
From the device survey. Phones with AArch64-only cores are out, because the 2010 user side runs as 32-bit code.
Report a phone you tested
Tried NeoSymbian on another phone, or on the Pixel? Tell us what worked. Fill in only what you know.
How a change gets in
Work happens in forks under the NeoSymbian org. Upstream branches stay as they are, and nothing goes back to SymbianSource.
- 01
Fork
Fork the repo under your account and branch from
main. - 02
Gate
Run the gate for that repo before you commit. The gates are listed below.
- 03
Commit
Commit only your own files. Changes to Symbian files are marked
NeoSymbian. - 04
Pull request
Open a PR against
NeoSymbian/<repo>. Say what you tested, and on which phone. - 05
Review
A maintainer merges. Kernel changes also need a QEMU or phone run.
e32-rs, telephony, neolink
cargo fmt --check cargo clippy -- -D warnings cargo test cargo arm
neoui
cargo fmt --check cargo clippy --all-targets -- -D warnings cargo test
kernel
neo kernel qemu neo qemu <secs> then re-pin build/sources.lock
docs
No gate. Update the roadmap and the org profile when a milestone lands.
Get in touch
Questions, a phone to lend, or something the issue tracker doesn't fit. Bugs and code questions go best in a GitHub issue.
Licences and legal
Our code is Apache-2.0. Symbian code is EPL-1.0, and the Symbian files we change become EPL-2.0. Our Syborg board files in QEMU are MIT, inside GPL-2.0 QEMU. The UI links Slint under GPL-3.0, so ROM images with it are not published. NeoSymbian is not affiliated with Nokia, Accenture, the former Symbian Foundation, or Google.