Android Automotive

Ok for patches :ok_hand: Everything builds without any problems now.

I flashed everything.
fastboot flash boot out/target/product/hikey960/boot.img
fastboot flash dts out/target/product/hikey960/dt.img
fastboot flash system out/target/product/hikey960/system.img
fastboot flash cache out/target/product/hikey960/cache.img
fastboot flash userdata out/target/product/hikey960/userdata.img

Still system HMI not startingā€¦

Working here, so need logs.

Which kind of logs? logcat & kernel ?

Unless you can think of any other logs, then you can add those as well.

I donā€™t know but I feel that the build of kernel I did is not that way? Did you check my steps #EDIT 2 of my previous post ? Maybe Iā€™m wrongā€¦ ?

Iā€™ll update the logs on my changes branch

Use a gist for your logs. Donā€™t mix them in a source code repository.

https://gist.github.com/AhmedX6/7e66e2d07ee226d06a068e979c611b9e

That is not the full logcat.

I think I canā€™t have more than that one.
https://gist.github.com/AhmedX6/142493ef9f9c4430a772b4b161bc7dbd

Kernel Logs seems ok for you now ?

Nothing stands out in the kernel log.
I canā€™t do much without the full logcat. There is definitely more to it than that.

Try this;
delete the file /system/bin/swid

I donā€™t have any way to test without the sensors mezzanine installed, but that is the only part that interacts with it in case you donā€™t have it installed.

Oh yes I know that when I execute the logcat, I donā€™t have the logs from the start of the machineā€¦

I deleted the swid program from /system/bin but still locked at the starting animationā€¦

Do you know if there is any way to get the full logcat from the start of the machine ?

Your logs are from the start. The problem is that theyā€™re not to the end.

01-01 01:18:31.593 2215 2218 E adbd : Could not start mdnsd.
01-01 01:18:34.596 2215 2218 E adbd : Could not register mDNS service (-65563).
--------- Some news appeared here --------
01-01 01:22:59.412 2215 2220 E adbd : remote usb: read terminated (message): Cannot send after transport endpoint shutdown
01-01 01:22:59.412 2215 2220 I adbd : : read failed: Cannot send after transport endpoint shutdown
01-01 01:22:59.413 2215 2215 I adbd : : offline
01-01 01:22:59.414 2215 2215 I adbd : BlockingConnectionAdapter(): stopping
01-01 01:23:17.115 2215 2221 E adbd : remote usb: 1 - write terminated: Cannot send after transport endpoint shutdown
01-01 01:23:17.119 2215 2215 I adbd : BlockingConnectionAdapter(): stopped
01-01 01:23:17.119 2215 2215 I adbd : BlockingConnectionAdapter(): destructing
01-01 01:23:17.119 2215 2215 I adbd : BlockingConnectionAdapter(): already stopped
01-01 01:23:17.119 2215 2215 I adbd : closing functionfs transport
01-01 01:23:17.191 2215 2216 I adbd : initializing functionfs
01-01 01:23:17.192 2215 2216 I adbd : functionfs successfully initialized
01-01 01:23:17.192 2215 2216 I adbd : registering usb transport
01-01 01:23:17.201 2215 2371 I adbd : : read thread spawning
01-01 01:23:17.205 2215 2372 I adbd : : write thread spawning
01-01 01:25:22.730 2215 2215 I adbd : : already offline

#edit
Useless theses onesā€¦ Maybe itā€™s when I connected with adbā€¦

Actually, there is one thing in your kernel log that looks a bit oddā€¦
[ 1113.105754] EXT4-fs (sdd10): re-mounted. Opts: data=ordered

Thatā€™s your system partition. Why was it remounted 1113 seconds after it started up?

That looks like it happened about an HOUR after it booted?

I want you to try running one of the official builds. Make sure that there isnā€™t something wrong with your board.

An official build is running correctly. The Android P from Google Source is ok and runs correctly. I wanted to test with Android Automotive nowā€¦

It might also help you to get yourself a UART interface for debugging rather than using the USB-C port, which has too much involvement with other elements of the system (plugging into the USB-C shuts off the host ports).

I want you to try again now.

Because I kept the device running on boot animationā€¦ So maybe, some things happened after some times.

I will try right now to flash the official builds and see of all goes well. I have a backup of the .img files already build

#EDIT
Flashed the Android P, system is running correctly : HMI is showing.