Device Requirements
If you are applying for a currently unsupported device or AXP.OS flavor, some requirements must be met before the request is (possibly) accepted.
Soft requirements
Android version
- oldest supported: Android 9
- newest supported: Android 13
- in progress: Android 14
At the moment Android 9 is the oldest supported version and Android 13 the newest supported version, regardless of the device age.
If your device does not fit between these versions but matches all other requirements feel free to request anyways. Just expect a way longer bring-up time then.
Note: This might also take more of your time when it comes to debugging issues during the process.
Hard requirements
The request itself
The only way to request a new device or AXP.OS flavor is by the projects issue tracker.
Requests over Chat, Forum, Mail etc will be ignored.
The request form must be properly filled with all required information and the user must be responsive to questions (either via the issue tracker or ideally using the official support room)
LineageOS
There must be an official or properly working unofficial LineageOS build for that device.
Other custom OS variants (e.g. AOSCP, etc.) cannot be used as a basis and will be rejected.
Specific for Unofficial LineageOS builds (requests get rejected if any of these does not apply):
- must provide a proper (local) manifest or link to all(!) sources used
- must not be heavily customized
- must not have critical bugs or missing features
Build & Test
- there must be a user willing to test all core Features of the requested AXP.OS flavor
- if it builds properly and the user testing went fine it will become finally a community-level supported device.
Removals
There are situations when a device which was previously supported gets removed again. Here a non-exclusive list of reasons why that might happen:
- the sources (Android and/or Kernel) cannot be patched properly anymore
- patches (especially backported ASB ones) which breaks booting or core features of Android (e.g. WiFi etc)
- any other critical issue (e.g. important core features don’t work anymore, device is not booting anymore, …) and there is no user willing to help in debugging
- devices with AXP.OS community - level support will be released to the unstable channel first and require a feedback by the community before they are released to the stable channel. If there is no feedback by the community the device will likely get removed from the next build run and even from the support list if there is no feedback for longer time
Processing requests
The exact order in which processing takes place and how long it takes for a device to be accepted is not exactly specified, but this is a rough guide:
| Type | Duration |
|---|---|
| AXP.OS flavor of an already supported device | Fast |
| new device supported by LineageOS | Medium |
| new device not supported by LineageOS | Long |
| new device with an unsupported Android version | Longest |
Major Release processing
When LineageOS supports a higher Android version for an already supported device it will likely get the corresponding AXP.OS version, too.
Keep in mind that due to the massive amount of changes needed to bring up a new Major Release it will take a while until all AXP.OS dependencies support the new Major Release.
AXP team supported devices
Devices with AXP.OS team - level support will get a new Major Release automatically (i.e. no request is required).
As soon as a device got migrated to the new Major Release there will be no builds released anymore for its previous Android version.
AXP community supported devices
Devices with AXP.OS community - level support will not get new Major Releases automatically.
Users owning such a device must open a new device request to get them migrated to a later Android version and so participate in testing and debugging.