How to official

note: v4 won't provide OFFICIAL build.

Prerequisites for device maintaining as "OFFICIAL"

Maintainer

• Maintainers must have an account on GitHub.
• Maintainers must know how to handle Git correctly, including rebasing / merging / pulling or amending to commits as well as cloning and working with repositories.
• Maintainers must retain proper authorship on commits or changes including the commit history, when using "picked" commits from other sources.
  • Authorship hereby means the original author should be named (commit history!).
  • As authorship is important for us in the open source community, it is mandatory for pushing to GitHub.
• Maintainers must have some basic knowledge about fixing bugs and pulling logs (on device and/or via ADB).
• Maintainers must not spoof other device's fingerprint in build.prop.
  • of course user can modding this, but maintainer must not do dirty hack...
• Maintainers should publish new build at least once a month, include security patch levels update.
• Maintainers can use SourceForge to host OFFICIAL build
  • send me your SourceForge username if you want
• Maintainers (who use SourceForge file releases) should know how to use SFTP/SSH/rsync to upload.

Device

• The device must be buildable by using open sourced dependencies that have a valid commit history.
  • Preferably using crDroid and LineageOS dependencies (incl. vendor) when possible.
• The device must have an official or at least trustable recovery (TWRP preferably) working and publicly available.
• The device should enforce SELinux before going official. If not possible at the moment of adding, it will stay in beta stage until SELinux can be enforced.
• The kernel should be upstreamed, android-linux-stable is a great resource (depending on the kernel version), this is not required though.
  • It is preferred that the kernel can be compiled with clang.
• The device's storage capabilities (internal and/or external) must be fully working.
• The device must have working audio for phone calls(!) on at least handset, speaker, headset (phone jack) and Bluetooth.
• The device must be able to make a data connections via SIM and/or Wifi.
  • If the device has more than one SIM slot, both slots must be working.
• The device must have other features for data transfers/communication working, like Bluetooth / NFC / Wifi Hotspot or USB tethering.
  • This is of course dependent on the device's hardware.
• The device must have a working camera. This includes front and rear cameras, if applicable.
  • This means that all Camera supported features for Photo and Video should be supported and working.
• The device's sensors, including fingerprint / proximity / acceleration / etc., must be working.
• The device tree must not include any unused overlays, but must include the basic overlays to work with FlokoROM features like key configs, pocketmode, doze etc.
• The device tree can include device specific overlays and packages, but not any obsolete packages or unnecessary properties (system.prop, vendor.prop, etc.).

OK, How to make OFFICIAL build?

• please PM me about your xda's thread, device repo or local_manifests link, and SourceForge username if you want.

services	username
Discord	hota#4982
Keybase	@hota
Fediverse	@hota@mstdn.maud.io
Telegram	@hotatech
Twitter	@lindwurm (DM is open)
xda	@1indwurm
Email	admin@maud.io

• if it is ok, you can set export FLOKO_BUILD_TYPE=OFFICIAL.
  • there is no additional feature between OFFICIAL and UNOFFICIAL
  • OFFICIAL can include Updater for OTA.
• We have no buildbot and download portal, sorry.