T00F/T00J - Asus Zenfone 5¶
Here only one or two sentences. What makes the device special? Is it a reference device?
Halium 7.1 is being worked on by Ilya Bizyaev and as of august 2017, he’s got a working x86 rootfs and LXC container but test seem to fail. Here are Device files and kernel. The local manifest has the following form
<manifest> <remote name="zf" fetch="http://github.com/zenfone-legacy" revision="refs/heads/cm-14.1"/> <project name="Halium/android_device_asus_T00F" path="device/asus/T00F" remote="hal"/> <project name="Halium/android_kernel_asus_T00F" path="kernel/asus/T00F" remote="hal"/> <project name="proprietary_vendor_asus" path="vendor/asus" remote="zf"/> <project name="android_external_stlport" path="external/stlport" remote="los"/></manifest>
There is an issue in halium/projectmanagement for the T00F.
The following entries are just a placeholder, exactly as this sentence.
|Distribution||Device Specific Files||Kernel||What works||What doesn’t work|
|Hammerhead on LineageOS Wiki <https://wiki.lineageos.org/devices/hammerhead>`_||android_device_placeholder||android_kernel_placeholder based on vX.Y.Z||?||?|
Kernel & Hardware¶
Mainline (version TODO)¶
Cyanogemod based kernels (LOS & UBP)¶
If other kernels exist, just make up headlines with a name that describe the origin (Cyanogemod, LineageOS, UBports, Canonical, …) and which is the underlying mainline version. Afterwards describe what’s been improved or altered and if possible why or what is still missing.
This should be populated with guides how to get into different boot modes and similar. For this device this can be pulled from the LOS device database.
Some devices show strange behaviour of some kind, try to find this (for example in the xda-developers forum) and document it
If anything might be usefull but didn’t fit above you can just throw in some links here.