Is the Official Android for Zero an ATV customisation?
It has support for touchscreen devices?
it’s possible to convert the image to flash with Amlogic USB Burning tool?
Is the Official Android for Zero an ATV customisation?
Yes, you can revert these two uboot commit, and build your own image.
I made a comment in another post of you, I can provide the steps to build lineage non-tv version for radxa zero if you want.
I used a digital ocean machine to build it and it worked perfectly.
@karlosoliveira you need a Linux (Ubuntu) machine with at least 16GB of RAM and at least 100GB of disk space (SSD) and at least 4 CPU cores.
You can compile LineageOS with less than that but it will be ridiculous slow.
I have a Apple Silicon M1 machine so I had to resort to a cloud provider for it, but since you pay by hour, it’s really cheap.
I’m personally using https://digitalocean.com and therefore I can provided the steps to build it there.
And I added a volume to store the Lineage source code:
PS: Be aware that they provide you $100 of bonus for you first account but it doesn’t allow you to use bigger machines like this one.
I had to add my CC and add $100 and open a ticket to have access to it. Not a big deal, though since I use this credit for other things.
After having the machine running, you can read the steps of any device, like this one: https://wiki.lineageos.org/devices/Amber/build
BUT for to the Radxa0/Digital Ocean you have to change some things:
Use the volume you added to the droplet to clone the source code, in my case it was
cd /mnt/volume_tor1_01/instead of
But Digital Ocean will provided you the correct path after you create the volume.
Also, to configure the
ccache, be sure to set its directory also to the volume you created, you can add
export CCACHE_DIR=/mnt/volume_tor1_01/to the
Be sure to exit and reconnect the ssh again after doing so to take effect
lineage-17.1(the guide I recommended to read doesn’t mention 18.1 but we need it instead of 17.1)
After doing the
repo sync, edit the file
.repo/local_manifests/roomservice.xmland add this line before the
<project depth="1" name="TheMuppets/proprietary_vendor_amlogic" path="vendor/amlogic" />
breakfast lineage_radxa0-eng(instead of
No need to call
m aml_upgrade(instead of
If that happens to succeed (it will be obviously at the end of the command), you have the ATV version on
Be sure to flash it and test if it is working before anything else, so we know that the Lineage is compiling as expected.
If something wrong happens at any command, do not proceed and ask for help and I will try to help here.
If it succeeds, you can try to build the non-TV version and for that you need to edit the file
device/radxa/radxa0/lineage_radxa0.mk and change its content to that: https://gist.github.com/sobrinho/d37296f76f3ce0fbfa3cbf15730d639b
And also, change
device/amlogic/g12-common/BoardConfigCommon.mk there is a line like:
BOARD_KERNEL_CMDLINE := androidboot.dtbo_idx=0 androidboot.boot_devices=ffe07000.emmc otg_device=1
That you need to add the permissive mode to the end of it:
BOARD_KERNEL_CMDLINE := androidboot.dtbo_idx=0 androidboot.boot_devices=ffe07000.emmc otg_device=1 androidboot.selinux=permissive
Be aware that the non-TV version doesn’t include GApps (I didn’t even try since I don’t need it).
After doing these changes, you need to call only
m aml_upgrade again.
If that happens to succeed (it will be obviously at the end of the command), you have the non-ATV version on
If that doesn’t work, ask for help and I will do my best to help.
repo sync take hours here and the first time you call the
m aml_upgrade it took like a day.
If you try to build the non-TV version after you build the TV one, it will took 30 minutes to complete.
I did everything in a tmux session (or screen session) to not worry about my connection dropping or anything like that.
Like I said, you need minimal Linux knowledge to build it.
Alternatively, someone can build this and provide you the final image, but where is the fun on that?
If you really resort to the Digital Ocean, be aware to delete (not just power off) the machine to stop charges in you CC.
I’m keeping mine around for a couple of weeks now because I might want to rebuild it at some point but I will delete it as soon as I’m done with it.
I’ll write a vendor neutral guide later based on this. Thanks.
Forgot to mention, you have to compile the u-boot and not use the one provided by Radxa.
Clone this one https://github.com/Stricted/deadpool_u-boot_build
cp uboot-bins/u-boot.bin /mnt/volume_tor1_01/android/lineage/device/radxa/radxa0/factory
That’s before calling the
Otherwise the device wont boot.
I have completed the guide . Please take a look.
looks fine, small change i would do tho,
4. Run breakfast lineage_radxa0-eng instead of breakfast I01WD.
change that to
4. Run breakfast radxa0 instead of breakfast I01WD.
Done. BTW you can create an account on Wiki if you feel like editing some articles
maybe when i mess around with more radxa devices planning on messing around with lineage on the rockchip ones at some point
Way to build and not use the aml-flash-tool.sh?
I’m trying to flash from a macOS machine but no luck so far.
Hello the Android versión cpu is for Aach64 ?
why radxa not provide android rom standard. I only find ATV rom
I think this is because the SDK default to Android TV (the SoC is designed for that market). I’ll ask our Android developer if he could release a normal Android build.
[…] I’ll ask our Android developer if he could release a normal Android build."
… with a Wi-Fi that works and that does not disconnect every five minutes, please