Android Automotive 12L - Snapp Automotive build

[Imron Gamidli]

Hello everyone,

There is an automotive build for the Raspberry Pi 4 provided by the Snapp Automotive guys. 

https://github.com/snappautomotive/firmware-device_snappautomotive_rpi/tree/sa-arpi-12L

Was anyone able to build and run on the Raspberry Pi their Android 12L version? 

I have built it successfully, but when I run it on Raspberry Pi, it gets stuck on booting screen.

Any tips are appreciated.

Best Regards, 

Imron

[Imron Gamidli]

I have connected over serial, but there are a lot of outputs and I don't know which keywords I should search for in the debugging to know what is the problem.

[Gabriel Oliveira Almeida]

Any news at your journey?

I've tried the same steps from snappautomotive instruction page Android 12L, and after flash at Raspberry Pi  4 B, also got stuck at booting screen as you reported, but I don´t have UART cable do debug,

I had success with Android 11...

Thanks

Lucio Gabriel

[Imron Gamidli]

Hello Gabriela,

Yeah it is same. I cannot run on Raspberry Pi 4B. I talked to Snapp Automotive guys, they said that script is not maintained, so there maybe some things needs to be fixed. They are using Samsung Phone for testing internally, so they don’t need AAOS on raspberry. I was quite disappointed, but it is what it is. 

If you get any success in the future, let me know as well!

Kind Regards

Imron Gamidlli

--
You received this message because you are subscribed to a topic in the Google Groups "Android-rpi" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-rpi/Wf_ZoXFnHzc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-rpi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-rpi/88d32196-7e4a-4d8c-b1e5-d4952e4099ffn%40googlegroups.com.

[Al Sutton]

Here is what we, at Snapp Automotive, actually emailed to you;

"We're planning to make a 12L image, but, at the moment, we don't have the work scheduled, so I can't give you an estimate as to when it would be available.

If you're seeing some build errors you could share them on the Android rpi Google Group (https://groups.google.com/g/android-rpi) where I, or someone else, might be able to work out what's going wrong and offer some suggestions."

The Raspberry Pi isn't suited to long-term automotive use for many reasons (e.g. RF interference, robustness), and we found that many developers prefer to use a tablet, which comes with all the parts they need, rather than trying to source individual components for a display, GPS, etc.. This is why, at the moment, the work on creating a 12L build for the RPi is considered a low priority for us, but we would be happy to support a community effort where we can.

You received this message because you are subscribed to the Google Groups "Android-rpi" group.

To unsubscribe from this group and stop receiving emails from it, send an email to android-rpi...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-rpi/3b1ce37f-debf-476d-bec9-f77908e0aed6%40Spark.

[Imron Gamidli]

Hello Al,

Forgive me if I misunderstood or misquoted you. 

I will try to share some parts of adb logs here. Maybe it is an easy fix. 

Generally speaking, you are right. For developers it is easier to use a tablet instead of a raspberry pi, display and bunch of cables . But in my thesis, i was focusing on an open-source hardware, therefore samsung tablet is not a fit. 

I would be really glad if you could update the 12L instructions in the near future. 

Kind Regards

Imron Gamidlli

[Imron Gamidli]

Hello Al,

I see that you pushed some commits to the Android 12L branch. Thank you for the update!

After building, I run the image on the Raspberry Pi, but only the rainbow screen shows up, as shown in the attachment. 

I have additionally attached the log file of the first 10 seconds of boot time after entering the logcat command. 

Could you look at it and tell me what might be the problem? 

Sincerely,

Imron

[Gabriel Oliveira Almeida]

Dears,

Bellow follow my logs taken witn UART Serial at Raspberry Pi 4 model B, I've made 2 tries, with same result, one with android-12.1.0_r21, and another android-12.1.0_r27, both same result, stay at boot animation screen forever, and 

by the log seems that service vendor.audio-hal-4-0-msd , audio_proxy_service cannot be found, logs shared by Imron show similar error related to audioserver and shows that audioserver is always trying to start but never complete.

Logs:

[  133.066212] init: processing action (init.svc.audioserver=running) from (/system/etc/init/audioserver.rc:38)
[  133.083387] init: Command 'start vendor.audio-hal-4-0-msd' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:40) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[  133.108372] init: Command 'start audio_proxy_service' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:41) took 0ms and failed: service audio_proxy_service not found
[  133.132407] init: starting service 'netd'...
[  138.024215] init: starting service 'zygote'...
[  138.030775] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[  138.039860] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 1000
[  138.061877] init: starting service 'audioserver'...
[  138.074708] init: starting service 'media'...
[  138.085842] init: starting service 'vendor.audio-hal'...
[  138.098156] init: processing action (init.svc.audioserver=running) from (/system/etc/init/audioserver.rc:38)
[  138.116173] init: Command 'start vendor.audio-hal-4-0-msd' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:40) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[  138.145090] init: starting service 'netd'...
[  138.150601] init: Created socket '/dev/socket/dnsproxyd', mode 660, user 0, group 3003
[  143.056596] init: starting service 'zygote'...
[  143.062687] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[  143.071980] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 1000
[  143.090073] init: starting service 'audioserver'...
[  143.104560] init: starting service 'media'...
[  143.117441] init: starting service 'vendor.audio-hal'...
[  143.131698] init: processing action (init.svc.audioserver=running) from (/system/etc/init/audioserver.rc:38)
[  143.147891] init: Command 'start vendor.audio-hal-4-0-msd' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:40) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[  143.173288] init: starting service 'netd'...
[  143.181745] init: Created socket '/dev/socket/dnsproxyd', mode 660, user 0, group 3003
[  143.541963] selinux: SELinux:  Could not stat /sys/devices/virtual/net/ipsec_test/queues/rx-0: No such file or directory.
[  143.556271] selinux:
[  148.084721] init: starting service 'zygote'...
[  148.090603] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[  148.099238] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 1000
[  148.119892] init: starting service 'audioserver'...
[  148.131609] init: starting service 'media'...
[  148.144590] init: starting service 'vendor.audio-hal'...
[  148.156494] init: processing action (init.svc.audioserver=running) from (/system/etc/init/audioserver.rc:38)
[  148.174231] init: Command 'start vendor.audio-hal-4-0-msd' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:40) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[  148.228595] init: starting service 'netd'...
[  148.234172] init: Created socket '/dev/socket/dnsproxyd', mode 660, user 0, group 3003
[  153.112879] init: starting service 'zygote'...
[  153.119252] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[  153.128129] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 1000
[  153.144184] init: starting service 'audioserver'...
[  153.158184] init: starting service 'media'...
[  153.170020] init: starting service 'vendor.audio-hal'...
[  153.182058] init: processing action (init.svc.audioserver=running) from (/system/etc/init/audioserver.rc:38)
[  153.199974] init: Command 'start vendor.audio-hal-4-0-msd' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:40) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[  153.229376] init: Command 'start audio_proxy_service' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:41) took 0ms and failed: service audio_proxy_service not found
[  153.251971] init: Command 'start vendor.audio-hal-2-0' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:43) took 0ms and failed: service vendor.audio-hal-2-0 not found
[  158.144977] init: starting service 'zygote'...
[  158.150562] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[  158.159123] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 1000
[  158.176885] init: starting service 'audioserver'...
[  158.189040] init: starting service 'media'...
[  158.200424] init: starting service 'vendor.audio-hal'...
[  158.223368] init: processing action (init.svc.audioserver=running) from (/system/etc/init/audioserver.rc:38)
[  158.239984] init: Command 'start vendor.audio-hal-4-0-msd' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:40) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[  158.264224] init: Command 'start audio_proxy_service' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:41) took 0ms and failed: service audio_proxy_service not found
[  158.287845] init: Command 'start vendor.audio-hal-2-0' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:43) took 0ms and failed: service vendor.audio-hal-2-0 not found
[  163.176393] init: starting service 'zygote'...
[  163.182541] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[  163.190846] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 1000
[  163.205268] init: starting service 'audioserver'...
[  163.219210] init: starting service 'media'...
[  163.230191] init: starting service 'vendor.audio-hal'...
[  163.253712] init: processing action (init.svc.audioserver=running) from (/system/etc/init/audioserver.rc:38)
[  163.267886] init: Command 'start vendor.audio-hal-4-0-msd' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:40) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[  163.295373] init: Command 'start audio_proxy_service' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:41) took 0ms and failed: service audio_proxy_service not found
[  163.320271] init: starting service 'netd'...
[  168.204091] init: starting service 'zygote'...
[  168.210512] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[  168.219024] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 1000

If you have any clue how to solve will be appreciated,

Thanks and Regards,

Lucio Gabriel

[Gabriel Oliveira Almeida]

Still stuck at same problem,

Did anyone had success to boot up Android Automotive 12 for raspberry pi 4?

Thanks and Regards,

Lucio Gabriel

[sarath chandu]

Hi Snapp,

snapp AAOS 12 image stuck at boot screen and following errors are seen.Any suggestions for a proper boot

On Thursday, September 22, 2022 at 12:21:04 PM UTC+5:30 al.s...@alsutton.com wrote:

Here is what we, at Snapp Automotive, actually emailed to you;

"We're planning to make a 12L image, but, at the moment, we don't have the work scheduled, so I can't give you an estimate as to when it would be available.

If you're seeing some build errors you could share them on the Android rpi Google Group (https://groups.google.com/g/android-rpi) where I, or someone else, might be able to work out what's going wrong and offer some suggestions."

The Raspberry Pi isn't suited to long-term automotive use for many reasons (e.g. RF interference, robustness), and we found that many developers prefer to use a tablet, which comes with all the parts they need, rather than trying to source individual components for a display, GPS, etc.. This is why, at the moment, the work on creating a 12L build for the RPi is considered a low priority for us, but we would be happy to support a community effort where we can.

On 21 Sep 2022, at 22:02, Imron Gamidli <gamidl...@gmail.com> wrote:

Hello Gabriela,

Yeah it is same. I cannot run on Raspberry Pi 4B. I talked to Snapp Automotive guys, they said that script is not maintained, so there maybe some things needs to be fixed. They are using Samsung Phone for testing internally, so they don’t need AAOS on raspberry. I was quite disappointed, but it is what it is. 

If you get any success in the future, let me know as well!

Kind Regards

Imron Gamidlli

On 21. Sep 2022 at 22:52 +0200, Gabriel Oliveira Almeida <gabrieloliveiraalmeida@gmail.com>, wrote:

Any news at your journey?

I've tried the same steps from snappautomotive instruction page Android 12L, and after flash at Raspberry Pi  4 B, also got stuck at booting screen as you reported, but I don´t have UART cable do debug,

I had success with Android 11...

Thanks

Lucio Gabriel

On Monday, September 5, 2022 at 10:01:32 AM UTC-3 gamidl...@gmail.com wrote:

I have connected over serial, but there are a lot of outputs and I don't know which keywords I should search for in the debugging to know what is the problem.

On Monday, September 5, 2022 at 2:58:10 PM UTC+2 Imron Gamidli wrote:

Hello everyone,

There is an automotive build for the Raspberry Pi 4 provided by the Snapp Automotive guys. 

https://github.com/snappautomotive/firmware-device_snappautomotive_rpi/tree/sa-arpi-12L

Was anyone able to build and run on the Raspberry Pi their Android 12L version? 

I have built it successfully, but when I run it on Raspberry Pi, it gets stuck on booting screen.

Any tips are appreciated.

Best Regards, 

Imron

--

You received this message because you are subscribed to a topic in the Google Groups "Android-rpi" group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-rpi/Wf_ZoXFnHzc/unsubscribe.

To unsubscribe from this group and all its topics, send an email to android-rpi+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-rpi/88d32196-7e4a-4d8c-b1e5-d4952e4099ffn%40googlegroups.com.

--

You received this message because you are subscribed to the Google Groups "Android-rpi" group.

To unsubscribe from this group and stop receiving emails from it, send an email to android-rpi+unsubscribe@googlegroups.com.

[Tu-Anh Hoang]

Hello everyone,

I wanna add something, that might be beneficial to you, because I am currently building Android Automotive 12 as well.
I found a way to get logging out of the Android, that is stuck in a bootloop.

First of all, I didn't used the Snapp build, but I used to do it as well. Nowadays I use a modified version of an AOSP build from Konstakang (Can be found here)

I added in device/brcm/rpi4/device.mk the following stuff:
```

# Car

$(call inherit-product, packages/services/Car/car_product/build/car.mk)

 

PRODUCT_CHARACTERISTICS := automotive

 

PRODUCT_PACKAGES += \

    Gear

 

 

# Automotive

PRODUCT_PACKAGES += \

    android.hardware....@2.0-service

 

PRODUCT_COPY_FILES += \

    frameworks/native/data/etc/android.hardware.type.automotive.xml:$(TARGET_COPY_OUT_VENDOR)/etc/permissions/android.hardware.type.automotive.xml \

    frameworks/native/data/etc/android.hardware.screen.landscape.xml:$(TARGET_COPY_OUT_VENDOR)/etc/permissions/android.hardware.screen.landscape.xml \

    frameworks/native/data/etc/android.software.activities_on_secondary_displays.xml:$(TARGET_COPY_OUT_VENDOR)/etc/permissions/android.software.activities_on_secondary_displays.xml

 

PRODUCT_SYSTEM_SERVER_JARS += car-frameworks-service

 

PRODUCT_PROPERTY_OVERRIDES += \

    android.car.drawer.unlimited=true \

    android.car.hvac.demo=true \

    com.android.car.radio.demo=true \

    com.android.car.radio.demo.dual=true

 

PRODUCT_PACKAGES += \

    Gear \

 

PRODUCT_PACKAGES += \

    vehicle.default \

    GearApp \

    CarGearApp \

    CarSettings \

    CarLauncher \

    CarService \

    CarTrustAgentService \

    android.hardware....@2.0-service \

    CarDialerApp \

    CarRadioApp \

    OverviewApp \

    CarLensPickerApp \

    LocalMediaPlayer \

    CarMediaApp \

    CarMessengerApp \

    CarHvacApp \

    CarMapsPlaceholder \

    CarLatinIME \

    CarUsbHandler \

    DirectRenderingCluster \

    android.car \

    car-frameworks-service \

    com.android.car.procfsinspector \

    libcar-framework-service-jni \

    NoCutoutOverlay

```

and while debugging, I noticed Android is trying to open this service, which fails because it doesn't have GPS. So I removed in  frameworks/base/services/core/java/com/android/server/timedetector/GnssTimeUpdateService.java line 83
`mService.requestGnssTimeUpdates();`

which is the method call for this service.

After that it booted as usual.

Hopefully it helps with fixing it.

On 21. Sep 2022 at 22:52 +0200, Gabriel Oliveira Almeida <gabrieloliv...@gmail.com>, wrote:

Any news at your journey?

I've tried the same steps from snappautomotive instruction page Android 12L, and after flash at Raspberry Pi  4 B, also got stuck at booting screen as you reported, but I don´t have UART cable do debug,

I had success with Android 11...

Thanks

Lucio Gabriel

On Monday, September 5, 2022 at 10:01:32 AM UTC-3 gamidl...@gmail.com wrote:

I have connected over serial, but there are a lot of outputs and I don't know which keywords I should search for in the debugging to know what is the problem.

On Monday, September 5, 2022 at 2:58:10 PM UTC+2 Imron Gamidli wrote:

Hello everyone,

There is an automotive build for the Raspberry Pi 4 provided by the Snapp Automotive guys. 

https://github.com/snappautomotive/firmware-device_snappautomotive_rpi/tree/sa-arpi-12L

Was anyone able to build and run on the Raspberry Pi their Android 12L version? 

I have built it successfully, but when I run it on Raspberry Pi, it gets stuck on booting screen.

Any tips are appreciated.

Best Regards, 

Imron

--

You received this message because you are subscribed to a topic in the Google Groups "Android-rpi" group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-rpi/Wf_ZoXFnHzc/unsubscribe.

To unsubscribe from this group and all its topics, send an email to android-rpi...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-rpi/88d32196-7e4a-4d8c-b1e5-d4952e4099ffn%40googlegroups.com.

--

You received this message because you are subscribed to the Google Groups "Android-rpi" group.

To unsubscribe from this group and stop receiving emails from it, send an email to android-rpi...@googlegroups.com.

[yammanuru karthik]

Hi Tu-Anh Hoang

Please do reply back if are able to see my message

I have followed the same steps mentioned by you, I was able to boot the Android but once I enter the android UI it is just displaying " Android is Starting " screen. 

And could you please elobrate more on how to collect logs when Android is running on Raspberry Pi 4. cause the blog which you have attached as an reference is for Raspberry Pi OS , which may not work for Android running on RPI. 

Thank you !! 

[Daniel Gaiteiro]

Which is the difference between Android Automotive and Snapp Automotive build ?

I am working in an automotive research centre and we want to test the feasibility of AAOS in our projects. Is there a way to contact Google for this?


Would testing with build the Snapp Automotive be the same? Is it a 100% reliable environment?