Will you post that timeline here?
Shouldnt you be able to build the latest android using link below:
https://source.android.com/setup/build/devices
1 Like
@Yasir_Javed you can build it of course, but for non-experienced people, its difficult to flash it, hence we are waiting for the official build from Gouwa and Terry,
current problem is we don’t have a a way to package it into a image file, and flash to the VIM3/3L, as the USB burning tool won’t accept any other image that is not packaged in the proper aml-raw format…
1 Like
Yes I have built it and flashed it.
It is not a useable system, memory errors, only uses half the pro memory etc.
It has not evolved enough to be more than an interesting diversion.
You will probably have to apply all the custom patches on top of it done by Fenix scripts and superceleron etc to make it usable enough
Too much work, I took the time to learn what I did to repo sync, compile etc fun enough learning Ubuntu and stuff but I can only push so much time into this, I need a working Android system for my project and building one myself is takeing just too long.
@Terry what is the current status of AOSP other than the issue of not being able to package it into a single flashable image out of it ?
if AOSP runs somewhat stable on the VIM3 right now, I am interested in making a simple seamless solution to flash it on the VIM3 with USB-C
cheers
1 Like
Hi,
I build AOSP using instructions here:
I upload and flash, based on instructions. Now the problem is that screen is blinking and icons go up and down with each blink. Can you help me find the solution please?
I can build AOSP which is in khadas GitHub, but unfortunately it has not ARM GPU config in kernel configs (My purpose is to enable devfreq of GPU).
Best,
Ehsan
Thanks for your reply.
Is there a stable branch working fine?
Thanks a lot. Your answer help me a lot. I test binary files and also compile them using your instruction on branch 11-r31, and both work fine. ( I use kernel 5.4).
However, now I have 3 problems and appreciate if you could help me please.
1- I want to modify and compile kernel, is it possible that compile and build boot.img separately( not placing the generated image into Yukawa-kernel and building aosp to generate boot.img). If yes what command should be used to generate boot.img from generated uImage file?
2- I download the kernel source code using instruction here:
https://source.android.com/setup/build/devices
compile with make meson_defconfig and put generated uImage in yukawa-kernel/5.4/ dir. along with .dtb files based on guide instructions. Then I try to boot boot.img file using: fastboot flash boot boot.img
but this cause that board does not boot up. what is the problem? (should I download the kernel source code from here?):
git clone https://android.googlesource.com/kernel/hikey-linaro -b android-amlogic-bmeson-5.4
3- In AOSP which exists in khadas aosp there are fan settings but in this OS I cannot find fan settings. Is there a way to config fan settings?
4- As I said with default kernel it works fine, but it gives following warning when running adb remount command. Is it important or is there a way to fix the warning? ( my board is khadas vim3 pro but storage shows 16GB!).
[liblp]Device size does not match (got 1879048192, expected 2415919104)
[liblp]Block device super size mismatch (expected2415919104, got 1879048192)
[libfs_mgr]add partition scratch
Using overlayfs for /system
[liblp]Device size does not match (got 1879048192, expected 2415919104)
[liblp]Block device super size mismatch (expected2415919104, got 1879048192)
[libfs_mgr]add partition scratch
Best regards,
Ehsan
1- I use instruction compile kernel.
2- Please provide error log.
3-The fan funtion is not OK.
4-At present, AOSP is only for VIM3.
1 Like
编译主线的aosp还需要添加vendor目录下的文件吗，还是直接拉最新的代码直接编译即可
Msater分支的不需要，直接下载后，编译即可。
aosp master是不是就不能用npu了
Hi,
Is NPU supported in the Google Android11 branch?
Best,
Ehsan
Is there a chance that it could be supported soon?
I need gpu dvfs and npu.
Khadas version of AOSP has support of npu but has not support of GPU dvfs.
On the other hand Google AOSP has support of GPU dvfs( still required work but there is potential) but has not support npu.
I should work on supporting GPU dvfs on Khadas AOSP or supporting npu on Google AOSP.
Which one do you suggest?
Best Ehsan