7 Known Bugs

NOTE

These are known issues and may be resolved in the future depending on their impacts.

1. Sepolicy output while the device is running:
   ~/ti-processor-sdk-android-<board>-<version>/board-support/emmc_files$ sudo ./adb shell dmesg | grep denied | audit2allow -p <Android_FS>/out/target/product/beagle_x15/obj/ETC/sepolicy_intermediates/sepolicy
   1. May see the following:
   #============== carservice_app ============== allow carservice_app runtime_event_log_tags_file:file map; #============== hal_vehicle_default ============== allow hal_vehicle_default node:tcp_socket node_bind; allow hal_vehicle_default self:tcp_socket { accept bind create listen };
   2. These cannot be resolved at this time due to SEPolicy neverallow.
2. Power manager service is failing.
   1. May see the following errors:
E CarPowerManagerNative: Received unknown bootReason = 0 E PowerTestService: ERROR: Could not read bootReason!!
3. CTS test_result_failures.html output when tested on pie-core-release branch with an AM57xx BeagleBoard-X15 and an AM65x EVM.
   • test_result_failures.html returned one failed test.
     • android.car.cts.CarBluetoothTest#testRequiredBluetoothProfilesExist
   • Details:
     • java.lang.NullPointerException: Attempt to invoke virtual method ‘boolean android.bluetooth.BluetoothAdapter.disable()’ on a null object reference
   • This is expected since the AM57xx BeagleBoard-X15 and AM65x EVM do not natively support bluetooth at this time.