Contribute: Device Bring-Up

You want to contribute and help making AXP.OS better?! That is awesome and greatly appreciated!

Here some steps and tasks which would help in bringing up a new device more quickly!

First of all you could help adding as much information as possible. Bringing up a new device requires several steps and costs time.

There is no need to walk through all steps if you do not like to, it is up to you how much you want to do or you want/have to skip one or more, of course. Any contribution counts ;)

Pre-requirements

Before you can start you must register an account (this is already required for opening a device request anyways, so you might have that already):

• register a code.binbash.rocks (click) account

Prepare additional information

In order to speed up your device request to be worked on you can:

1. prepare additional information (listed in the next topics) to your own request
2. add the same for other device requests which are older than your own (usually the order of processing is from oldest->newest - with exceptions though)

Prepare your own request

Firmware

Legacy devices/versions not receiving vendor firmware updates anymore

1. open https://github.com/TheMuppets
2. find the repo with the codename
3. select the correct branch (axp-a13 = lineage-20.0, etc)
4. find the Android.mk within

update your request:

Update your request with the following information:

• TheMuppets: <link-to-Android.mk>

(e.g.: https://github.com/TheMuppets/proprietary_vendor_google_blueline/blob/lineage-20/Android.mk)

Devices which still gets vendor firmware updates

This topic covers mostly Fairphone / SHIFTphone but even then that has to be verified first! For example Fairphone recently released A15 for the FP4 model and so stopped providing updates for A13. If A13 is the suggested Android version it means you have to follow the “Legacy devices/versions not receiving vendor firmware updates anymore” above instead, otherwise (i.e. if the Android version matches what the vendor provides updates for, go on).

For these devices AXP.OS automatically downloads and includes the latest available firmware and live-extract all required blobs.

No action required here but you have to fill in the whole Firmware info block in the copytemplate of the next topic “Automation”

Automation

update your request:

Update your request as follows:

1. copy the whole content of this copytemplate (click to open)
2. add a new comment to your request and paste it there (do not save yet)
3. select the whole block, then click the <> icon, from now on you can save that comment or directly proceed with 4:
4. fill in what you can, related blocks are marked with DEFINE-IF-YOU-CAN. If you have no idea ask or simply skip it. ensure you ignore any DO NOT TOUCH blocks (do not remove them though).

Prepare other requests

After you have done all for your own request you might find that there is a queue of requests before yours. You can do the same as the above with these requests, because the sooner they will be finished the sooner yours will.

The following are helpers, i.e. preset searches which can be used to identify device requests and their order (there is no static / fixed process order but chances are high they go like this).

Low hanging fruits (top in processing order)

Pre-filtered which shows just those which are 90% sure to be added:

• Issue tracker (top->down: oldest->newest)

Good enough (high in processing order)

Pre-filtered (official) LineageOS ones which are 80% sure to be added:

• Issue tracker (top->down: oldest->newest)

Problematic ones (low in processing order)

Pre-filtered unofficial LineageOS ones which are 40% sure to be added:

• Issue tracker (top->down: oldest->newest)