Open raffles496 opened 1 month ago
I did some debugging of this and Android dropped including the compatibility_matrix.3.xml and compatibility_matrix.4.xml files. Changing the target-level to 5 in device/sony/common/vintf/manifest.xml removes quite many of the errors. I also noticed that nothing appears to be installing the vendor_framework_compatibility_matrix.xml file located in vendor/qcom/opensource/core-utils and adding that to DEVICE_FRAMEWORK_COMPATIBILITY_MATRIX_FILE solves quite many of the issues left after changing the target-level but not all. What is still left is
The following HALs in device manifest are not declared in FCM <= level 5:
android.hardware.cas.IMediaCasService/default (@1)
android.hardware.configstore@1.1::ISurfaceFlingerConfigs/default
android.hardware.light@2.0::ILight/default
android.hardware.power@1.3::IPower/default
android.hardware.vibrator@1.0::IVibrator/default
android.hardware.wifi.IWifi/default (@2)
android.hardware.wifi.hostapd.IHostapd/default (@2)
android.hardware.wifi.supplicant.ISupplicant/default (@3)
vendor.nxp.nxpnfc@1.0::INxpNfc/default
vendor.qti.hardware.radio.qtiradio@2.7::IQtiRadio/slot1
vendor.qti.hardware.radio.qtiradio@2.7::IQtiRadio/slot2
vendor.qti.ims.factory@2.2::IImsFactory/default
vendor.somc.hardware.miscta@1.0::IMisctaGlobal/default
vendor.somc.hardware.modemswitcher@1.0::IModemSwitcher/default
ERROR: files are incompatible: The following instances are in the device manifest but not specified in framework compatibility matrix:
android.hardware.configstore@1.1::ISurfaceFlingerConfigs/default
android.hardware.light@2.0::ILight/default
android.hardware.power@1.3::IPower/default
android.hardware.vibrator@1.0::IVibrator/default
vendor.nxp.nxpnfc@1.0::INxpNfc/default
vendor.qti.hardware.radio.qtiradio@2.7::IQtiRadio/slot1
vendor.qti.hardware.radio.qtiradio@2.7::IQtiRadio/slot2
vendor.qti.ims.factory@2.2::IImsFactory/default
vendor.somc.hardware.miscta@1.0::IMisctaGlobal/default
vendor.somc.hardware.modemswitcher@1.0::IModemSwitcher/default
Out of these android.hardware.configstore is not available in any compatibility matrix and appears to be obsolete. Some hardware interfaces i.e. android.hardware.light, android.hardware.power and android.hardware.vibrator are now AIDL-only and the custom implementations probably need to be adapted to be AIDL. The remaining vendor instances probably need be added to that vendor_framework_compatibility_matrix.xml file. Not sure about those android.hardware.cas and android.hardware.wifi ones.
@mlehtima Thanks for you support and tips. Edit my "device/sony/common/vintf/manifest.xml" changing of target-level to 5 and manually adding the instances to my "vendor/qcom/opensource/core-utils/vendor_framework_compatibility_matrix.xml". After this steps, the error previously dissappear, and the compilation finishim with this files:
The problem now is that after the flashing of this IMGs the phone not boot, is stuck on SONY logo, also somes IMGs is impossible of flashing given that mark an error.
as the guide suggests depending on the device not all images are available or should be flashed
as the guide suggests depending on the device not all images are available or should be flashed
Exactly, I read it in the guide, the problem is that I am not sure which ones I need and which ones I should discard or if the compilation simply has errors and that is why the Smartphone does not start.
I have made a new build hoping this will help solve any errors, the build finishes without errors but it does report several "warnings" during the process. Then I run a "fastboot flashall" letting the system choose which IMGs to flash, the process is done without errors, but now the only difference is that the Smartphone goes from the Sony logo and gets stuck on the "Android" boot logo . Is there any way to know what is preventing the system from starting on the Smartphone?
$ fastboot flashall
--------------------------------------------
Bootloader Version...: xboot
Baseband Version.....:
Serial Number........: HQ626A6D77
--------------------------------------------
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.022s]
Sending 'boot_a' (98304 KB) OKAY [ 2.150s]
Writing 'boot_a' OKAY [ 0.295s]
Sending 'dtbo_a' (24576 KB) OKAY [ 0.546s]
Writing 'dtbo_a' OKAY [ 0.066s]
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.157s]
Writing 'vendor_boot_a' OKAY [ 0.295s]
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.002s]
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.018s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'system_ext_a' OKAY [ 0.004s]
Resizing 'vendor_a' OKAY [ 0.005s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.006s]
Sending sparse 'system_a' 1/4 (262140 KB) OKAY [ 5.750s]
Writing 'system_a' OKAY [ 0.786s]
Sending sparse 'system_a' 2/4 (262140 KB) OKAY [ 5.736s]
Writing 'system_a' OKAY [ 0.716s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 5.770s]
Writing 'system_a' OKAY [ 0.719s]
Sending sparse 'system_a' 4/4 (64276 KB) OKAY [ 1.421s]
Writing 'system_a' OKAY [ 0.241s]
Resizing 'system_ext_a' OKAY [ 0.003s]
Sending 'system_ext_a' (176948 KB) OKAY [ 3.874s]
Writing 'system_ext_a' OKAY [ 0.593s]
Resizing 'vendor_a' OKAY [ 0.005s]
Sending 'vendor_a' (148640 KB) OKAY [ 3.259s]
Writing 'vendor_a' OKAY [ 0.530s]
Resizing 'product_a' OKAY [ 0.005s]
Sending sparse 'product_a' 1/2 (262140 KB) OKAY [ 5.743s]
Writing 'product_a' OKAY [ 0.789s]
Sending sparse 'product_a' 2/2 (24252 KB) OKAY [ 0.540s]
Writing 'product_a' OKAY [ 0.143s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 42.362s
Platform: Android 14 Device: XQCC54 Kernel version: 5.4 Android version: 14
Description After following the steps to compile AOSP 14 described by SONY on its official website, I encounter this error in the final steps.
Symptoms No such file or directory: Cannot find framework matrix at FCM version 4.
How to reproduce Following the official steps for compiling AOSP 14.
Additional context