A mobile platform for an open architecture.
Aevornix Mobile is a research and development track for a RISC-V-first mobile software platform derived from open foundations.
Scope
What this track does and does not claim.
A mobile platform derived from open foundations invites assumptions about compatibility. These four statements are the ones that matter, so they are on the page rather than left implicit.
Application compatibility is a research target, not a supported feature.
Native library portability must be tested for each application; it does not follow from the framework.
Google services are not part of the platform.
Aevornix services replace vendor-specific dependencies over time.
The foundation is AOSP-derived: an open-source base, evaluated for what it takes to run on a 64-bit RISC-V profile. It is not a certified build, and it carries no vendor mobile services.
Architecture
Seven layers, application to foundation.
Aevornix services sit where vendor-specific ones would. That substitution is the research question: which services can be replaced, and which turn out to be load-bearing for the applications people actually run.
App layer
Applications, and the compatibility question of what runs unmodified.
Developer SDK
Building, packaging and signing applications for the platform.
Local AI services
On-device speech, vision and text models within a mobile power budget.
Aevornix Store
Distribution and updates, in place of a vendor marketplace.
Aevornix account
One identity across device, Store and developer platform.
Aevornix system services
Permissions, updates, media and network services replacing vendor-specific ones.
Open source foundationfoundation
An AOSP-derived base, evaluated against a 64-bit RISC-V profile.
Subsystems
Ten pieces, none of them finished.
Every subsystem carries its stage. Most are research; the scanner and the emulator are further along because they are shared with the rest of RVStack.
Open mobile foundation
An AOSP-derived base, evaluated for what it takes to run on a 64-bit RISC-V profile.
Aevornix account
The identity already used across the Store and this site, extended to device sign-in.
Aevornix Store
Application distribution and updates through the Aevornix Store rather than a vendor marketplace.
App permissions
A permission model the platform enforces, and that a package declares before it is signed.
Over-the-air updates
Signed system and application updates with a verified rollback path.
Media services
Codec, playback and capture services on the open foundation.
Local AI services
On-device models for speech, vision and text, sized to a mobile power budget.
Developer SDK
Building and packaging applications for the platform from an existing project.
Package readiness scanner
Reports what inside an application package blocks it from running on RISC-V.
RISC-V emulator
The emulated device the mobile shell and its applications are exercised on.
RISC-V