YiQiuYes / android_device_xiaomi_enuma

0 stars 0 forks source link

FCM Issues #2

Open alghiffaryfa19 opened 1 day ago

alghiffaryfa19 commented 1 day ago

I try build risingos with this device tree, but error like this

` vendor.qti.hardware.radio.qcrilhook@1.0::IQtiOemHook/oemhook1 vendor.qti.hardware.radio.qtiradio@1.0::IQtiRadio/slot1 vendor.qti.hardware.radio.qtiradio@1.0::IQtiRadio/slot2 vendor.qti.hardware.radio.qtiradio@2.4::IQtiRadio/slot1 vendor.qti.hardware.radio.qtiradio@2.4::IQtiRadio/slot2 vendor.qti.hardware.radio.uim@1.2::IUim/Uim0 vendor.qti.hardware.radio.uim@1.2::IUim/Uim1 vendor.qti.hardware.radio.uim_remote_client@1.0::IUimRemoteServiceClient/uimRemoteClient0 vendor.qti.hardware.radio.uim_remote_client@1.0::IUimRemoteServiceClient/uimRemoteClient1 vendor.qti.hardware.radio.uim_remote_server@1.0::IUimRemoteServiceServer/uimRemoteServer0 vendor.qti.hardware.radio.uim_remote_server@1.0::IUimRemoteServiceServer/uimRemoteServer1 vendor.qti.hardware.sensorscalibrate@1.0::ISensorsCalibrate/default vendor.qti.hardware.soter@1.0::ISoter/default vendor.qti.hardware.tui_comm@1.0::ITuiComm/default vendor.qti.hardware.vpp@1.3::IHidlVppService/vppService vendor.qti.hardware.wifi.wifilearner@1.0::IWifiStats/wifiStats vendor.qti.hardware.wifidisplaysession@1.0::IWifiDisplaySession/wifidisplaysession vendor.qti.hardware.wifidisplaysession@1.0::IWifiDisplaySessionAudioTrack/wifidisplaysessionaudiotrack vendor.qti.hardware.wifidisplaysession@1.0::IWifiDisplaySessionImageTrack/wifidisplaysessionimagetrack vendor.qti.hardware.wifidisplaysession@1.0::IWifiDisplaySessionVideoTrack/wifidisplaysessionvideotrack vendor.qti.imsrtpservice@3.0::IRTPService/imsrtpservice vendor.qti.qspmhal@1.0::IQspmhal/default vendor.xiaomi.hardware.mlipay@1.1::IMlipayService/default Suggested fix:

  1. Update deprecated HALs to the latest version.
  2. Check for any typos in device manifest or framework compatibility matrices with FCM version >= 5.
  3. For new platform HALs, add them to any framework compatibility matrix with FCM version >= 5 where applicable.
  4. For device-specific HALs, add to DEVICE_FRAMEWORK_COMPATIBILITY_MATRIX_FILE or DEVICE_PRODUCT_COMPATIBILITY_MATRIX_FILE.: No such device 04:52:06 ninja failed with: exit status 1

failed to build some targets (05:02 (mm:ss)) ####`

YiQiuYes commented 15 hours ago

i will see soon

YiQiuYes commented 14 hours ago

you try update manifest_phome.xml from lineage device sm8250 common