Android 10 crash during boot animation

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Android 10 crash during boot animation

3,709 Views
andrew_questps
Contributor III

Hi All,
For my work I have been porting the Android 10 changes from the 10.0.2.3 release onto a custom imx7d device, we already have a working 9.0.2.2-ga release, but we are interested in the new additions to Android 10. We have a requirement in our project to not get too far behind the Google releases and with Android 11 soon to be released we did not want to be out of support from Google with regards to security fixes and kernel patches.

When I run the release on Android 10 - with the changes required to get it to build in that environment similar to the imx7ulp - I am having an issue where the boot animation crashes in one of the NXP supplied drivers /vendor/lib/egl/libGLESv1_CM_swiftshader.so

After this happens there is a period of 30secs where nothing is displayed before an Android prompt that has:

 

 

Android System
There's an internal problem with your device. Contact your manufacturer for details.

 

 

So it doesn't seem that Android is unable to render anything, just that it crashes.

Can you please help me with this issue?

I have attached the relevant section of the log but the excerpt is this:

 

 

09-01 07:00:18.432 274 274 I SurfaceFlinger: Enter boot animation
09-01 07:00:18.457 298 350 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
09-01 07:00:19.289 298 350 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
09-01 07:00:19.337 248 248 E ActivityRecognitionHardware: activity_recognition HAL is deprecated. class_init is effectively a no-op
09-01 07:00:19.392 298 350 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
--------- beginning of crash
09-01 07:00:19.412 384 393 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4 in tid 393 (BootAnimation), pid 384 (bootanimation)
09-01 07:00:19.478 399 399 E cutils-trace: Error opening trace file: No such file or directory (2)
09-01 07:00:19.494 298 350 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
09-01 07:00:19.504 400 400 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
09-01 07:00:19.505 307 307 I /system/bin/tombstoned: received crash request for pid 393
09-01 07:00:19.508 400 400 I crash_dump32: performing dump of process 384 (target tid = 393)
09-01 07:00:19.528 400 400 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-01 07:00:19.529 400 400 F DEBUG : Build fingerprint: 'Android/dev/test:10/QQ2A.200501.001.B2/eng.andrew.20200901.164706:userdebug/dev-keys'
09-01 07:00:19.529 400 400 F DEBUG : Revision: '0'
09-01 07:00:19.529 400 400 F DEBUG : ABI: 'arm'
09-01 07:00:19.529 400 400 F DEBUG : Timestamp: 2020-09-01 07:00:19+0000
09-01 07:00:19.529 400 400 F DEBUG : pid: 384, tid: 393, name: BootAnimation >>> /system/bin/bootanimation <<<
09-01 07:00:19.529 400 400 F DEBUG : uid: 1003
09-01 07:00:19.529 400 400 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4
09-01 07:00:19.529 400 400 F DEBUG : Cause: null pointer dereference
09-01 07:00:19.529 400 400 F DEBUG : r0 00000004 r1 aa1fbc04 r2 00000000 r3 00000010
09-01 07:00:19.529 400 400 F DEBUG : r4 00000000 r5 aa1ecc60 r6 aa1bf000 r7 00000000
09-01 07:00:19.530 400 400 F DEBUG : r8 aa1f9664 r9 aa1fb310 r10 aa1fb31c r11 a62fbca8
09-01 07:00:19.530 400 400 F DEBUG : ip 80000000 sp a62fbba0 lr a4fd188f pc a4fa88d6
09-01 07:00:19.603 248 248 I zygote : Thread[1,tid=248,Native,Thread*=0xadc4de00,peer=0x12c021e0,"main"] recursive attempt to load library "libmedia_jni.so"
09-01 07:00:19.603 248 248 D MtpDeviceJNI: register_android_mtp_MtpDevice
09-01 07:00:19.604 248 248 I zygote : Thread[1,tid=248,Native,Thread*=0xadc4de00,peer=0x12c021e0,"main"] recursive attempt to load library "libmedia_jni.so"
09-01 07:00:19.604 248 248 I zygote : Thread[1,tid=248,Native,Thread*=0xadc4de00,peer=0x12c021e0,"main"] recursive attempt to load library "libmedia_jni.so"
09-01 07:00:19.607 298 350 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
09-01 07:00:19.631 248 248 W Zygote : Class not found for preloading: android.media.audiopolicy.AudioProductStrategies
09-01 07:00:19.631 248 248 W Zygote : Class not found for preloading: android.media.audiopolicy.AudioVolumeGroups
09-01 07:00:19.723 298 350 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
09-01 07:00:19.897 298 350 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
09-01 07:00:19.931 248 248 W Zygote : Class not found for preloading: android.view.-$$Lambda$SurfaceView$Cs7TGTdA1lXf9qW8VOJAfEsMjdk
09-01 07:00:19.937 248 248 W Zygote : Class not found for preloading: android.view.SurfaceView$3
09-01 07:00:19.945 400 400 F DEBUG :
09-01 07:00:19.945 400 400 F DEBUG : backtrace:
09-01 07:00:19.945 400 400 F DEBUG : #00 pc 002288d6 /vendor/lib/egl/libGLESv1_CM_swiftshader.so (rr::Routine::bind()+6) (BuildId: acde8b7ba503815d7e8780ec0f1946f2)
09-01 07:00:19.946 400 400 F DEBUG : #01 pc 0025188b /vendor/lib/egl/libGLESv1_CM_swiftshader.so (sw::LRUCache<sw::VertexProcessor::State, rr::Routine>::add(sw::VertexProcessor::State const&, rr::Routine*)+46) (BuildId: acde8b7ba503815d7e8780ec0f1946f2)

 

0 Kudos
4 Replies

3,651 Views
surmanlive
Contributor I
0 Kudos

3,687 Views
IvanRuiz
NXP Employee
NXP Employee

Hello,

Please accept my apologies, but Android 10 is no longer supported for this device because the characteristics of the MPU might not be the most efficient ones for Android 10, for which it will be helpful to consider switching to a more powerful MPU which is supported on recent versions of Android from the i.MX family, besides, this one does not have a GPU: https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/i-mx-applications-proces...

In case you still need support on the porting for this device, please contact professional services: https://www.nxp.com/support/support/nxp-engineering-services/professional-engineering-services:PROFE...

 

Have a nice day.

 

BR,

Ivan.

0 Kudos

3,667 Views
andrew_questps
Contributor III

That's a shame considering it basically seems to run until this crash. I guess I will just try to fix it then when i have some free time

It's a bit late to decide to change CPUs to a more expensive one in the project now, and then rework boards etc and our usage doesn't require a grunty GPU, we aren't making a phone.

I guess I find it disappointing that NXP support the devices for such a short period.

0 Kudos

3,656 Views
IvanRuiz
NXP Employee
NXP Employee

Hello,

 

The i.MX 8M Nano is not an expensive solution and a viable one compared to the 7 dual. And, it is supported on newer versions of Android, please refer to the following link: https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/evaluation-kit-...

 

But, if you still need help with customizing Android 10 for the i.MX 7D, you can find our professional services on the following link: https://www.nxp.com/support/support/nxp-engineering-services/professional-engineering-services:PROFE...

 

Have a nice day!

 

BR,

Ivan.

0 Kudos