currently the yukawa source is maintained by Bayliber and r37 hasnt been updated in a year. here the build.prop from the image i built about 1~2 weeks ago and it says that the version is 11 at ro.build.version.release
from what i can see atleast, they may be using the same BoardConfigCommon.mk between the master and s beta branches with some changes but forgot to change other bits of the config
####################################
from generate-common-build-props
These properties identify this partition image.
####################################
ro.product.system.brand=Android
ro.product.system.device=yukawa
ro.product.system.manufacturer=SEI Robotics
ro.product.system.model=ATV on yukawa
ro.product.system.name=yukawa
ro.system.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.system.product.cpu.abilist32=armeabi-v7a,armeabi
ro.system.product.cpu.abilist64=arm64-v8a
ro.system.build.date=Tue May 18 20:08:05 UTC 2021
ro.system.build.date.utc=1621368485
ro.system.build.fingerprint=Android/yukawa/yukawa:S/AOSP.MASTER/serv-dan05182008:userdebug/test-keys
ro.system.build.id=AOSP.MASTER
ro.system.build.tags=test-keys
ro.system.build.type=userdebug
ro.system.build.version.incremental=eng.serv-d.20210518.200936
ro.system.build.version.release=11
ro.system.build.version.release_or_codename=S
ro.system.build.version.sdk=30
####################################
from out/target/product/yukawa/obj/PACKAGING/system_build_prop_intermediates/buildinfo.prop
####################################
begin build properties
autogenerated by buildinfo.sh
ro.build.id=AOSP.MASTER
ro.build.display.id=yukawa-userdebug S AOSP.MASTER eng.serv-d.20210518.200936 test-keys
ro.build.version.incremental=eng.serv-d.20210518.200936
ro.build.version.sdk=30
ro.build.version.preview_sdk=1
ro.build.version.preview_sdk_fingerprint=61ba06fc7de6b604982f3f4ef6feb28e
ro.build.version.codename=S
ro.build.version.all_codenames=S
ro.build.version.release=11
ro.build.version.release_or_codename=S
ro.build.version.security_patch=2021-05-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Tue May 18 20:08:05 UTC 2021
ro.build.date.utc=1621368485
ro.build.type=userdebug
ro.build.user=serv-dan
ro.build.host=build-serv
ro.build.tags=test-keys
ro.build.flavor=yukawa-userdebug
ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.wifi.channels=
ro.build.product is obsolete; use ro.product.device
ro.build.product=yukawa
Do not try to parse description or thumbprint
ro.build.description=yukawa-userdebug S AOSP.MASTER eng.serv-d.20210518.200936 test-keys
end build properties
####################################
from variable ADDITIONAL_SYSTEM_PROPERTIES
####################################
Removed by post_process_props.py because ro.product.first_api_level is a disallowed key
Thanks a lot for looking into this! I will try to amend BoardConfigCommon.mk according to your suggestions. Is my understanding correct that it should be the only file i will need to change?
Use the the master branch of device/amlogic-yukawa kernel
cd device/amlogic/yukawa-kernel
git pull aosp
git checkout -f aosp/master
Fixups. There are few things that need tweaking in yukawa repo
because they are meant for the master branch.
Use my work-in-progress branch for device/amlogic/yukawa:
yes i do have all three kernel dirs now after i’ve checked out master. Could be a problem of my build cache, as i’ve already built my branch before and then switch branch of device/amlogic/yukawa according to your suggesion and built again in hope it will take less time.
Thx, i will do a clean build in case the one i’m doing now fails
Successfully flashed 11 on VIM3. But when trying to keep the debugging on (done from UI settings option), the VIM3 keeps restarting. Is this a known issue? Any fix for this?
Hi, I followed all the instructions given by you to generate and flash asop images, I checked out to android-11.0.0_r48 branch. But seems that surflaceflinger keeps Crashing and i am not able to see anything on the HDMI out and scrcpy also throws error
some of the dmesg logs i captured
[ 106.074806] init: starting service ‘surfaceflinger’…
[ 106.075070] init: Could not create socket ‘pdx/system/vr/display/client’: Failed to bind socket ‘pdx/system/vr/display/client’: No such file or directory
[ 106.088275] init: Could not create socket ‘pdx/system/vr/display/manager’: Failed to bind socket ‘pdx/system/vr/display/manager’: No such file or directory
[ 106.102106] init: Could not create socket ‘pdx/system/vr/display/vsync’: Failed to bind socket ‘pdx/system/vr/display/vsync’: No such file or directory
Hi @tenk.wang , I used absolutely the same steps as yours to build android-11.0.0_r31.Build completed successfully
I used the flash script from VIM3_R_AOSP_V210604 to flash images. There is no output from HDMI, and when I used command :svc wifi enable to open WiFi, it showed no wifi service.
But if I flash VIM3_R_AOSP_V210604 image, everything is OK
What’s the difference between VIM3_R_AOSP_V210604 and android-11.0.0_r31?
How can I get the source codes of VIM3_R_AOSP_V210604?