AOSP on Blueline not working properly

[GullsForSale]

Hi,

I am trying to build and run AOSP on blueline (build PQ2A.190305.002, android-9.0.0_r34). It builds successfully but I have no audio on calls. Furthermore, if I sign my release with custom keys, the device don't boot (crash immediately after the Google logo).

I used the provided vendor binaries corresponding to my branch and followed the guidelines for setting up the environnement, building, signing and flashing.

Here are my steps (Ubuntu 18.04) :

1/Fetching sources

repo init -u https://android.googlesource.com/platform/manifest -b android-9.0.0_r34
repo sync --jobs=12

2/Creating keys

subject='/C=...'
for x in releasekey platform shared media; do \
    ./development/tools/make_key ~/Android/keys/$x "$subject"; \
done
openssl genrsa -out avb.pem 2048

3/Getting vendor binaries

https://developers.google.com/android/drivers
Untar & execute self extracting scripts in the root of the tree

4/Building

source build/envsetup.sh
lunch aosp_blueline-user

make -j12
make dist

5/Signing

./build/tools/releasetools/sign_target_files_apks -o -d ~/Android/keys --avb_vbmeta_key ~/Android/keys/avb.pem --avb_vbmeta_algorithm SHA256_RSA2048 --avb_system_key ~/Android/keys/avb.pem --avb_system_algorithm SHA256_RSA2048 out/target/product/blueline/obj/PACKAGING/target_files_intermediates/aosp_blueline-target_files-eng.zip signed-target_files.zip

6/Making image

./build/tools/releasetools/img_from_target_files signed-target_files.zip signed-image.zip

7/Flashing

fastboot -w update signed-image.zip

If anybody successfully ran signed AOSP on this device, please help me.

Regards

[Mohammad Saleh Dehghanpour]

Hello

Did you find any answer for your problem?

I have the same problem too

I tried another workaround: I replaced my keys with default ones in build/target/product/security/ and built an image. But when bootanimation ends up, the system continously show ANR of system apps. (System UI, settings,...)

I know if signature of system apps do not match with signature of build , this would occur. But I still wonder why the system is not signed with my keys!