Hey there,
- I have successfully cloned and build the Android 14 Automotive NXP code in Linux server by following the documentation provided on the official website AAUG_14.0.0_2.1.0_2024-10-02_14-28.pdf.
- Code downloaded from this link: https://www.nxp.com/pages/alpha-beta-bsps-for-microprocessors:IMXPRERELEASES
- (Android Automotive 14.0.0_2.1.0 (L6.6.23 BSP) Supports i.MX95 19x19 EVK Alpha Link:https://www.nxp.com/webapp/Download?colCode=automotive-14.0.0_2.1.0_image_95evk_car2&appType=license)
- I have tried with both the build targets for automotive.
1. evk_95_car-trunk_staging-userdebug
2. evk_95_car2-trunk_staging-userdebug
- After flashing the board, the process completed successfully and I am able to see the Android 14 Automotive UI.
- Command used for flashing : sudo ./uuu_imx_android_flash.sh -f imx95 -e -t emmc
- However, when i try to enable Bluetooth on UI, I am getting a crash in adb logcat. Bluetooth never gets enabled.
Attaching the logs: bt.log and bt-on.log. - Board information :
i.MX 95 19x19 evk reference board.
I am using JODY-W377-00B u-blox chip for WiFi and BT.
Could you please confirm if this is an expected behavior or a known issue?
Please let me know if any additional information is required. I am currently blocked and i need processed only if BT is working.
Thank you.
Adding additional information of the board as UI screenshots for Android automotive OS install success, BT not working and WIFI working.
Please let me know if more information is required.
JODY-W377:
BT NOT working:
Android Automotive up via Android 14:
WiFi working:
Hi, @ni3
Thanks for your detailed info.
Please allow me some time to check logs and your setup.
Once have any updates, I will let you know.
Best regards,
Christine.
Hi， @ni3
Your shared logs seems there is HAL initialization failure.
Would you mind have a try with below release:
You are using now is Alpha / Beta BSPs, it might have some issues, please have a try with above release, and let me know your results, Thanks.
Best regards,
Christine.
Hello @Christine_Li ,
Thanks for the reply.
I went through the comment by you and realized that you provided me Android OS image and not the Android automotive one which i am looking for.
I have tried the image though because i am not able to bring the board up with Android 16.
What i tried:
Flash the Android image from link you provided. Here is the screenshot:
Then I tried with (optionally) Android automotive 16 prebuilt DEMO images. Here is screenshot:
I have UART switch set to ON (means JTAG is OFF)
I have SW7 switch for download as 1001 and for emmc boot - 1010
Here is screenshot:
Till now - Android 16 has always failed with LIBUSB error, and I had to switch to Android 14 alpha image.
For Android 14 - once I switch to UART - ON on board then Bluetooth started working and enabled by default.
Now my concern is something different.
Bluetooth speakers i have does not connect with the board but just shows notification of connected and disconnected.
Here is screenshot:
My iPhone does connect and process call+media but my headphone BT speakers does not receive any data.
Is it that BT sink does work and source does not work at all in Android automotive?
Is there a way that I can use BT as source? Any config changes required?
Thanks in advance.
Hi @Christine_Li ,
Please find the logs attached and let me know if there is anything that needs to be done further.
I have few more queries actually if this is design limitation due to BT sink profile for Android automotive.
1. Can I route zone 1 output to 3.5mm jack and zone 2 output to J10 connected external speaker? Is there configuration and routing changes required?
2. Do I need to use pipewire to define and route the audio independently with 3.5mm jack and USB soundcard?
The whole purpose is to achieve Audio Multizone implementation on imx95 EVK REV A board. Please suggest and let me know if further information required.
Thanks.
Hi， @ni3
Can you please help to provide me the failed HCI logs and also logcat logs when you trying to connect to your headset？
On Android, you can capture HCI logs by enabling Bluetooth HCI snoop log in Developer Options , toggling Bluetooth once to start capture, and then exporting the log with adb .
Steps:
- Open Developer Options
- Enable Bluetooth HCI snoop log
- Toggle Bluetooth off and on once
- Trying to reproduce the issue.
- Pull the log file with ADB commands.
Let's have a look the connection failed logs then try to find the connection failed reason.
Best regards,
Christine.
Hi,
I tested it locally with I.MX95-EVK 19*19, and Android 16 Auto release:
It can work as expected.
Please see below screenshot for your reference.
Best regards,
Christine.
I had a try at the Android 16 prebuilt you insisted but it's a LIBUSB error mentioned earlier which blocks the flashing using uuu.
Hi, @ni3
I checked your current logs, and found that the
=======
Line 838: 06-19 07:25:06.044 1294 1486 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:67:36 BOND_BONDING => BOND_BONDED
Line 841: 06-19 07:25:06.077 1181 1357 D CachedBluetoothDevice: updating profiles for XX:XX:XX:XX:67:36
Line 844: 06-19 07:25:06.084 1673 1673 D CachedBluetoothDevice: updating profiles for XX:XX:XX:XX:67:36
Line 853: 06-19 07:25:06.099 1181 1357 D CachedBluetoothDevice: No profiles. Maybe we will connect later for device XX:XX:XX:XX:67:36
Line 868: 06-19 07:25:06.284 1673 1673 D CachedBluetoothDevice: No profiles. Maybe we will connect later for device D7:88:75:A1:67:36
Line 886: 06-19 07:25:06.401 1544 1571 D CachedBluetoothDevice: updating profiles for XX:XX:XX:XX:67:36
Line 888: 06-19 07:25:06.411 1544 1571 D CachedBluetoothDevice: No profiles. Maybe we will connect later for device XX:XX:XX:XX:67:36
Line 903: 06-19 07:25:08.919 1673 1673 D CachedBluetoothDevice: No profiles. Maybe we will connect later for device D7:88:75:A1:67:36
Line 909: 06-19 07:25:09.953 1673 1673 D CachedBluetoothDevice: No profiles. Maybe we will connect later for device D7:88:75:A1:67:36
Line 911: 06-19 07:25:10.014 1294 1426 I btm_acl : packages/modules/Bluetooth/system/stack/acl/btm_acl.cc:205 - disconnect_acl: Disconnecting peer:xx:xx:xx:xx:67:36 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
Line 914: 06-19 07:25:10.054 1294 1426 I btif_av : packages/modules/Bluetooth/system/btif/src/btif_av.cc:4101 - btif_av_acl_disconnected: btif_av_acl_disconnected: Peer xx:xx:xx:xx:67:36 : ACL Disconnected
Line 915: 06-19 07:25:10.054 1294 1426 I btif_av : packages/modules/Bluetooth/system/btif/src/btif_av.cc:1503 - FindOrCreatePeer: BtifAvPeer *BtifAvSink::FindOrCreatePeer(const RawAddress &, tBTA_AV_HNDL): Create peer: peer_address=xx:xx:xx:xx:67:36 bta_handle=0x41 peer_id=0
Line 920: 06-19 07:25:10.054 1294 1426 I btif_av : packages/modules/Bluetooth/system/btif/src/btif_av.cc:1575 - DeleteIdlePeers: DeleteIdlePeers: Deleting idle peer: xx:xx:xx:xx:67:36 bta_handle=0x41
Line 922: 06-19 07:25:10.055 1294 1460 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:890 - btif_dm_get_connection_state: Acl is not connected to peer:xx:xx:xx:xx:67:36It means it already paired and connected successfully, but ACL link is disconnected by Android host due to the SDP responds that “SdpManager: sdpRecordFoundCallback: Search instance is NULL” no profiles.
To debug further, please help to provide me the HCI snoop logs.
Can you please help to provide me the failed HCI logs and also logcat logs when you trying to connect to your headset？
On Android, you can capture HCI logs by enabling Bluetooth HCI snoop log in Developer Options , toggling Bluetooth once to start capture, and then exporting the log with adb .
Steps:
- Open Developer Options
- Enable Bluetooth HCI snoop log
- Toggle Bluetooth off and on once
- Trying to reproduce the issue.
- Pull the log file with ADB commands.
And also, at the same time, you can have a try with below Android 16 Auto release. I suspect the issue might be related to your Android 14 auto release.
- i.MX 95 (B0) 19x19 EVK – demo images with EVS in Arm Cortex-M7 core
- i.MX 95 (B0) 19x19 EVK – demo images with EVS in Arm Cortex-A core
Best regards,
Christine.
Hi, @ni3
That was my mistake. Last time I share to you the link is for Android 16, not for Automotive Android 16.
And you can get the Automotive Android release by below link:
Software for Android Automotive | NXP Semiconductors
And yesterday I shared to you the link is specially for I.MX95-EVK Automotive Android 16. Here I paste the link below again for your convenience.
If still have LIBUSB related issue, please have a try by changing another USB Type-C cable, or changing another USB port on your windows PC, or reboot the board after plug out then plug in again. Sometimes we also meet such kind of LIBUSB error, but after changing another USB Type-C cable, or changing another USB port on our windows PC, or reboot the board after plug out then plug into the PC port again, the issue is resolved.
Best regards,
Christine.
Hi @Christine_Li ,
I had a try at the Android 16 prebuilt you insisted but it's a LIBUSB error mentioned earlier which blocks the flashing using uuu.
I am attaching the BT HCI logs here as a zip file.
Thanks for your support.
Regards.
Hi, @ni3
I checked your logs, it doesn't including your connect failed process.
Can you please help to capture HCI logs by re-enable Bluetooth, then reproduce the issue(Connect your Headset but showing disconnected in UI), then save the logs and share to me?
I am not sure why you can not flash it into your board, but I can flash it successfully with the link I shared to you the Automotive Android 16 Image.
Below is the flashing screenshot on my side showing that flash successfully.
And you are also right with:
Change the board's SW7 (boot mode) to 1001 (1-4 bits) to enter serial download mode.
Change SW7 to switch the board back to 1010 (form 1-4 bit) to enter eMMC boot mode.
Best regards,
Christine.
Hello @Christine_Li,
Tried to flash the same as you from my Ubuntu 22.04 since I cannot use Windows for flashing.
It did show me LIBUSB error as per the attached screenshot in the zip.
After enabling BT snoop logs in settings, I did the following:
1. Delete the existing log file from /data/misc/bluetooth/logs/btsnoop_hci.log
2. Disable the BT from UI - No log generated
3. Enable the BT + Click on connect to Airdopes 141 earbuds from UI - Logfile generated (attached the same in zip)
4. The earbuds on UI show connecting and then disconnected after this process.
Thanks for your support
Hi, @ni3
I don't know why in your HCI logs, there is no any logs related to connection.
Please see below for the screenshot:
I think the difference between your side and my side is you are using Ubuntu to flash, and I am using Windows to flash.
Let me have a try with Ubuntu 22.04, then let you know my results.
Another request, do you have another I.MX95 19*19 EVK? If possible, would you please have a try with another EVK board?
Or, would you please have a try with Windows PC to flash?
Best regards,
Christine.