Join now - be part of our community!

XE9005 Crash when exit from sleep

profile.country.NL.title
Cioclul
Explorer

XE9005 Crash when exit from sleep

Hello all,

My XE9005 started crashing when it wakes up from sleep. But it only does so once per day: the first time in a day that I push the power button. I see the loading screen, the big "Android" logo and then I can use it.

If I turn off the TV and turn it on again, it exists sleep without a crash. So only after sleeping overnight.

It's as though over night it has a resource allocation problem (like memory) or some sort of buffer that fills up.

 

I already tried updating the software, and I even did a factory reset, it's the same. I also pulled all USB devices from the ports (some keyboard dongle) to make sure that was not the cause.

 

I enabled developer options and got the logs of the crash. I am looking for someone that can read the logcat of the crash and give me some idea of what can be wrong, and if I can fix it. It looks to me like the problem starts here:

06-25 08:36:41.256  1629   379 D WificondControl: Scan result ready event
06-25 08:36:41.260  1629  1736 E memtrack: Couldn't load memtrack module
06-25 08:36:41.260  1629  1736 W android.os.Debug: failed to get memory consumption info: -1
06-25 08:36:41.265  1629  1736 E memtrack: Couldn't load memtrack module
06-25 08:36:41.266  1629  1736 W android.os.Debug: failed to get memory consumption info: -1
06-25 08:36:41.269  2337  2337 I SSServ_BraviaBluetoothModule: Screen On/Off Bug occurred. Request Cancelled
06-25 08:36:41.273  2337  2952 I SSServ_IntentDeliverer: send redeliver intent : com.sony.dtv.intent.action.SCREEN_ON / com.sony.dtv.timers / ALL
06-25 08:36:41.279  1629  3227 E ActivityManager: Sending non-protected broadcast com.sony.dtv.intent.action.SCREEN_ON from system 2337:com.sony.dtv.sonysystemservice/1000 pkg com.sony.dtv.sonysystemservice
06-25 08:36:41.279  1629  3227 E ActivityManager: java.lang.Throwable
06-25 08:36:41.279  1629  3227 E ActivityManager: 	at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:19043)
06-25 08:36:41.279  1629  3227 E ActivityManager: 	at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:19648)
06-25 08:36:41.279  1629  3227 E ActivityManager: 	at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:19790)
06-25 08:36:41.279  1629  3227 E ActivityManager: 	at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:240)
06-25 08:36:41.279  1629  3227 E ActivityManager: 	at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2936)
06-25 08:36:41.279  1629  3227 E ActivityManager: 	at android.os.Binder.execTransact(Binder.java:674)
06-25 08:36:41.296  1629  1736 E memtrack: Couldn't load memtrack module
06-25 08:36:41.296  1629  1736 W android.os.Debug: failed to get memory consumption info: -1
06-25 08:36:42.017  2957  2957 I crash_dump32: obtaining output fd from tombstoned
06-25 08:36:42.023  1357  1357 I /system/bin/tombstoned: received crash request for pid 1629
06-25 08:36:42.027  2957  2957 I crash_dump32: performing dump of process 1629 (target tid = 1629)
06-25 08:36:42.028  2957  2957 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-25 08:36:42.028  2957  2957 F DEBUG   : Build fingerprint: 'Sony/BRAVIA_ATV2_EU/BRAVIA_ATV2:8.0.0/OPR2.170623.027.S30/665451:user/release-keys'
06-25 08:36:42.028  2957  2957 F DEBUG   : Revision: '0'
06-25 08:36:42.028  2957  2957 F DEBUG   : ABI: 'arm'
06-25 08:36:42.028  2957  2957 F DEBUG   : pid: 1629, tid: 1629, name: system_server  >>> system_server <<<
06-25 08:36:42.028  2957  2957 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
06-25 08:36:42.042  2957  2957 F DEBUG   : Abort message: 'Status.cpp:142] Attempted to retrieve value from failed HIDL call: Status(EX_TRANSACTION_FAILED): 'DEAD_OBJECT: ''
06-25 08:36:42.042  2957  2957 F DEBUG   :     r0 00000000  r1 0000065d  r2 00000006  r3 00000008
06-25 08:36:42.042  2957  2957 F DEBUG   :     r4 0000065d  r5 0000065d  r6 bed87d58  r7 0000010c
06-25 08:36:42.042  2957  2957 F DEBUG   :     r8 00000000  r9 b0269000  sl 144b6cf0  fp 70b12e58
06-25 08:36:42.042  2957  2957 F DEBUG   :     ip 00000000  sp bed87d48  lr b2d2e637  pc b2d5ec00  cpsr 20030010
06-25 08:36:42.062  1255  1255 D [BT]    : mtk_bt_op: BT_VND_OP_POWER_CTRL 0
06-25 08:36:42.062  1255  1255 D [BT]    : mtk_bt_cleanup: Close fw dump file : 
06-25 08:36:42.062  1255  1255 W [BT]    : mtk_bt_cleanup #327
06-25 08:36:42.078  2957  2957 F DEBUG   : 
06-25 08:36:42.078  2957  2957 F DEBUG   : backtrace:
06-25 08:36:42.078  2957  2957 F DEBUG   :     #00 pc 0004ac00  /system/lib/libc.so (tgkill+12)
06-25 08:36:42.078  2957  2957 F DEBUG   :     #01 pc 0001a633  /system/lib/libc.so (abort+54)
06-25 08:36:42.078  2957  2957 F DEBUG   :     #02 pc 0000752b  /system/lib/libbase.so (_ZN7android4base14DefaultAborterEPKc+6)
06-25 08:36:42.078  2957  2957 F DEBUG   :     #03 pc 00007e09  /system/lib/libbase.so (_ZN7android4base10LogMessageD2Ev+456)
06-25 08:36:42.078  2957  2957 F DEBUG   :     #04 pc 000067d5  /system/lib/libhidlbase.so (_ZNK7android8hardware7details13return_status8assertOkEv+160)
06-25 08:36:42.078  2957  2957 F DEBUG   :     #05 pc 0002126f  /system/lib/libandroid_servers.so (_ZN7android17HdmiCecController11getVendorIdEv+50)
06-25 08:36:42.078  2957  2957 F DEBUG   :     #06 pc 00b0e52f  /system/framework/oat/arm/services.odex (offset 0x538000)

Then all Android start failing and the VM is killed:

06-25 08:36:46.957  3370  3382 E JavaBinder: *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
06-25 08:36:46.957  3370  3382 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
06-25 08:36:46.961 31807 31807 D LedControlLib: #onServiceDisconnected
06-25 08:36:46.964  1091  1091 I ServiceManager: service 'media.camera.proxy' died
06-25 08:36:46.964  1091  1091 I ServiceManager: service 'account' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'content' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'settings' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'vibrator' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'consumer_ir' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'alarm' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'input' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'window' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'vrmanager' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'pinner' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'accessibility' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'input_method' died
06-25 08:36:46.965  1091  1091 I ServiceManager: service 'mount' died
...
06-25 08:36:46.982  3333  3333 D AndroidRuntime: Shutting down VM
06-25 08:36:46.984  3446  3446 I Process : Sending signal. PID: 3446 SIG: 9
06-25 08:36:46.985  3333  3333 E AndroidRuntime: FATAL EXCEPTION: main
06-25 08:36:46.985  3333  3333 E AndroidRuntime: Process: com.google.android.tvlauncher, PID: 3333
06-25 08:36:46.985  3333  3333 E AndroidRuntime: java.lang.RuntimeException: android.os.DeadObjectException
06-25 08:36:46.985  3333  3333 E AndroidRuntime: 	at android.os.storage.StorageManager.isUserKeyUnlocked(StorageManager.java:1283)
06-25 08:36:46.985  3333  3333 E AndroidRuntime: 	at android.app.ContextImpl.getSharedPreferences(ContextImpl.java:386)
06-25 08:36:46.985  3333  3333 E AndroidRuntime: 	at android.app.ContextImpl.getSharedPreferences(ContextImpl.java:370)
...

 

Unfortunately I am not familiar with Android TV, and I don't have a good understanding of Android in general. 

 

You can find the full log here: https://andreibasangiu.stackstorage.com/s/sdvNvwaptHflTME

1 REPLY 1
profile.country.GB.title
Sean_Mc
Moderator

Hi there,

 

Welcome to the Sony Community.

 

As you've said you've already tried updating the software and resetting your TV, I would suggest you contact the support team for further advice here.

 

Best wishes,

Sean