[SOLVED] Samsung Galaxy A5 bootloop after battery dies

Using /e/OS Troubleshooting
1

Hey folks,

My phone has gotten stuck in a bootloop a couple times and I think it might be related to the battery running out. As far as I remember, every time the battery on my phone has run out since I switched to /e/ OS, trying to turn it back on gets the phone stuck at the /e/ start screen. Holding down the power button in the bootloop does nothing, the only way I managed to reboot the device was through adb.

Device: Samsung Galaxy A5 (2017)
/e/ OS version: 0.8-p-2020041249359-dev-a5y17lte

Here’s the last lines from logcat from the last time this happened (I hit the characher limit trying to paste in all the lines I have…):

04-18 10:21:40.817  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][HYPERMOTION_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.817  6041  6041 I ExynosCameraSec: [CAM_ID(1)][]-INFO(m_releaseVendorBuffers[8423]):free buffer done
04-18 10:21:40.817  6041  6041 I ExynosCamera: [CAM_ID(1)][]-INFO(m_releaseBuffers[3257]):free buffer done
04-18 10:21:40.817  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][BAYER_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.817  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][BAYER_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.817  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(bayerBufferMgr) destroyed
04-18 10:21:40.817  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][3AS_IN_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.817  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][3AS_IN_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.817  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(3aaBufferMgr) destroyed
04-18 10:21:40.817  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][3AP_OUT_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.817  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][3AP_OUT_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.817  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(ispBufferMgr) destroyed
04-18 10:21:40.817  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][ISP_OUT_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.817  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][ISP_OUT_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.817  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(m_hwDisBufferMgr) destroyed
04-18 10:21:40.817  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][DZOOM_SCALER_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.817  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][DZOOM_SCALER_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.817  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(m_zoomScalerBufferMgr) destroyed
04-18 10:21:40.817  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][ISP_RE_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.817  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][ISP_RE_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.817  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(ispReprocessingBufferMgr) destroyed
04-18 10:21:40.817  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][MCSC_RE_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][MCSC_RE_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(sccReprocessingBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][THUMBNAIL_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][THUMBNAIL_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(sccReprocessingBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][SCC_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][SCC_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(sccBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][GSC_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][GSC_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(gscBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][POSTPICTURE_GSC_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][POSTPICTURE_GSC_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(m_postPictureBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][THUMBNAIL_GSC_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][THUMBNAIL_GSC_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(m_thumbnailGscBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][JPEG_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][JPEG_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(jpegBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][PREVIEW_CB_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][PREVIEW_CB_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(previewCallbackBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][HIGH_RESOLUTION_CB_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][HIGH_RESOLUTION_CB_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(m_highResolutionCallbackBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][RECORDING_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][RECORDING_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCamera: [CAM_ID(1)][]-DEBUG(release):BufferManager(recordingBufferMgr) destroyed
04-18 10:21:40.818  6041  6041 D ExynosCameraFrameManager: [CAM_ID(1)][FRAME MANAGER]-DEBUG(~ExynosCameraFrameManager): FrameManager DELETE(name(FRAME MANAGER) cameraid(1) mode(2)
04-18 10:21:40.818  6041  6041 D ExynosCameraFrameManager: [CAM_ID(1)][CREATE FRAME WORKER]-DEBUG(~CreateWorker): Worker DELETE(name(CREATE FRAME WORKER) cameraid(1) mode(2) 
04-18 10:21:40.818  6041  6041 D ExynosCameraFrameManager: [CAM_ID(1)][DELETE FRAME WORKER]-DEBUG(~DeleteWorker): Worker DELETE(name(DELETE FRAME WORKER) cameraid(1) mode(2) 
04-18 10:21:40.818  6041  6041 D ExynosCameraFrameManager: [CAM_ID(1)][FRAME MANAGER]-DEBUG(m_deinit[1078]): delete m_lock
04-18 10:21:40.818  6041  6041 D ExynosCameraFrameManager: [CAM_ID(1)][FRAME MANAGER]-DEBUG(m_deinit[1083]): delete m_keybox
04-18 10:21:40.818  6041  6041 I ExynosCameraSec: [CAM_ID(1)][]-INFO(m_vendorSpecificDestructor[6405]): -IN-
04-18 10:21:40.818  6041  6041 D ExynosCameraBufferManager: [CAM_ID(1)][HYPERMOTION_BUF]-DEBUG(deinit[123]):IN..
04-18 10:21:40.818  6041  6041 I ExynosCameraBufferManager: [CAM_ID(1)][HYPERMOTION_BUF]-INFO(deinit[126]:OUT.. Buffer is not allocated
04-18 10:21:40.818  6041  6041 D ExynosCameraSec: [CAM_ID(1)][]-HyperMotion_HAL(m_vendorSpecificDestructor):BufferManager(m_hyperMotion_BufferMgr) destroyed
04-18 10:21:40.818  6041  6041 I ExynosCameraSec: [CAM_ID(1)][]-INFO(m_vendorSpecificDestructor[6647]): -OUT-
04-18 10:21:40.818  6041  6041 I ExynosCamera: [CAM_ID(1)][]-INFO(release[736]): -OUT-
04-18 10:21:40.818  6041  6041 D SecCameraPreviewFrameScheduler: (m_release[227] m_vsyncPeriod=0, Drop Count 0)
04-18 10:21:40.819  6041  6041 I ExynosCamera3Interface: INFO(HAL_camera_device_close[867]):camera(1)
04-18 10:21:40.819  6041  6041 I ExynosCamera3Interface: INFO(HAL_camera_device_close[870]): out
04-18 10:21:40.819  6041  6041 D ExynosCamera3Interface: DEBUG:duration time(    3 msec):(HAL_camera_device_close)
04-18 10:21:40.819  6041  6041 I CameraProviderManager: Enumerating new camera device: device@3.3/legacy/1
04-18 10:21:40.819  6041  6041 V CameraWrapper: camera_get_number_of_cameras
04-18 10:21:40.819  6041  6041 V CameraWrapper: check_vendor_module
04-18 10:21:40.819  6041  6041 I CameraProviderManager: Camera provider legacy/0 ready with 4 camera devices
04-18 10:21:40.820  2377  2377 W hwservicemanager: getTransport: Cannot find entry android.hardware.camera.provider@2.4::ICameraProvider/external/0 in either framework or device manifest.
04-18 10:21:40.821  6041  6041 D vndksupport: Loading /vendor/lib/hw/android.hardware.camera.provider@2.4-impl.so from current namespace instead of sphal namespace.
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: load external camera config succeed!
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 6 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 7 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 8 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 9 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 12 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 50 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 51 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 101 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 102 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 110 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 111 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 112 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 130 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 131 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 132 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 160 will be ignored by external camera provider
04-18 10:21:40.822  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 161 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 170 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 171 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 172 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 173 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 174 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 180 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 211 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: device 215 will be ignored by external camera provider
04-18 10:21:40.823  6041  6041 I ExtCamUtils@3.4: loadFromCfg: no external camera device config specified
04-18 10:21:40.823  6041  6085 I CamPvdr@2.4-external: threadLoop start monitoring new V4L2 devices
04-18 10:21:40.823  6041  6041 I CameraProviderManager: Connecting to new camera provider: external/0, isRemote? 0
04-18 10:21:40.824  6041  6041 I CameraProviderManager: Camera provider external/0 ready with 0 camera devices
04-18 10:21:40.824  6041  6041 I CameraService: onDeviceStatusChanged: Status changed for cameraId=1, newStatus=1
04-18 10:21:40.824  6041  6041 I CameraService: onDeviceStatusChanged: Unknown camera ID 1, a new camera is added
04-18 10:21:40.824  6041  6041 I CameraService: onDeviceStatusChanged: Status changed for cameraId=0, newStatus=1
04-18 10:21:40.824  6041  6041 I CameraService: onDeviceStatusChanged: Unknown camera ID 0, a new camera is added
04-18 10:21:40.825  6041  6041 I         : Waiting for activity service
04-18 10:21:40.865  6022  6022 I zygote64: Thread[1,tid=6022,Native,Thread*=0x71c1814c00,peer=0x13000088,"main"] recursive attempt to load library "/system/lib64/libmedia_jni.so"
04-18 10:21:40.865  6022  6022 D MtpDeviceJNI: register_android_mtp_MtpDevice
04-18 10:21:40.866  6022  6022 I zygote64: Thread[1,tid=6022,Native,Thread*=0x71c1814c00,peer=0x13000088,"main"] recursive attempt to load library "/system/lib64/libmedia_jni.so"
04-18 10:21:40.897  6022  6022 F libc    : Fatal signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x71bba90df8 in tid 6022 (main), pid 6022 (main)
04-18 10:21:40.866  6022  6022 I zygote64: Thread[1,tid=6022,Native,Thread*=0x71c1814c00,peer=0x13000088,"main"] recursive attempt to load library "/system/lib64/libmedia_jni.so"
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/0: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/1: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/2: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/3: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/4: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/5: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/6: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/7: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/8: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/9: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/10: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/11: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/12: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/13: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/14: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/15: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/16: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/17: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/18: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/19: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/20: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/21: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/22: Permission denied
04-18 10:21:40.921  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/23: Permission denied
04-18 10:21:40.922  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/24: Permission denied
04-18 10:21:40.922  6088  6088 E DEBUG   : failed to readlink /proc/6022/fd/25: Permission denied
04-18 10:21:40.922  6088  6088 F crash_dump64: crash_dump.cpp:423] failed to attach to thread 6022, already traced by 0 ()
04-18 10:21:40.922  2532  2532 I /system/bin/tombstoned: received crash request for pid 6022
04-18 10:21:40.923  2532  2532 W /system/bin/tombstoned: crash socket received short read of length 0 (expected 12)
04-18 10:21:40.924  6022  6022 F libc    : crash_dump helper failed to exec
04-18 10:21:40.941  2376  2376 I ServiceManager: service 'media.audio_flinger' died
04-18 10:21:40.951  2376  2376 I ServiceManager: service 'media.player' died
04-18 10:21:40.951  2376  2376 I ServiceManager: service 'media.resource_manager' died
04-18 10:21:40.956  2376  2376 I ServiceManager: service 'netd' died
04-18 10:21:40.965  2376  2376 I ServiceManager: service 'wificond' died
04-18 10:21:44.839  2536  2536 E bauth_FPBAuthService: [fp_sigh] : 15
04-18 10:21:44.839  2536  2536 D bauth_FPBAuthService: FPBAuthService, 7295
04-18 10:21:44.839  2536  2536 E bauth_FPBAuthService: [fp_sigh] set_cancel_flags and sleep 200ms
04-18 10:21:44.841  2525  2525 I statsd  : StatsService::Terminating
04-18 10:21:44.853  2376  2376 I ServiceManager: service 'perfprofd' died
04-18 10:21:44.853  2376  2376 I ServiceManager: service 'android.service.gatekeeper.IGateKeeperService' died
04-18 10:21:44.853  2376  2376 I ServiceManager: service 'media.metrics' died
04-18 10:21:44.853  2376  2376 I ServiceManager: service 'media.drm' died
04-18 10:21:44.860  2376  2376 I ServiceManager: service 'incident' died
04-18 10:21:44.863  2376  2376 I ServiceManager: service 'android.security.keystore' died
04-18 10:21:44.863  2376  2376 I ServiceManager: service 'installd' died
04-18 10:21:44.866  2461  2461 I McDaemon: Signal 15 received [hardware/samsung_slsi/exynos7880/mobicore/Daemon/src/MobiCoreDriverDaemon.cpp:152]
04-18 10:21:44.868  2376  2376 I ServiceManager: service 'media.extractor' died
04-18 10:21:44.868  2461  2493 I TeeProxyServer: thread received stop message [hardware/samsung_slsi/exynos7880/mobicore/ClientLib/src/proxy_server.cpp:357]
04-18 10:21:44.869  2376  2376 I ServiceManager: service 'media.extractor.update' died
04-18 10:21:44.869  2461  2492 I McDaemon: Signal 10 received [hardware/samsung_slsi/exynos7880/mobicore/Daemon/src/MobiCoreDriverDaemon.cpp:152]
04-18 10:21:44.870  2461  2491 I McDaemon: Signal 10 received [hardware/samsung_slsi/exynos7880/mobicore/Daemon/src/MobiCoreDriverDaemon.cpp:152]
04-18 10:21:44.870  2461  2491 E TeeDriverClient: Interrupted system call in waitNotification
04-18 10:21:44.870  2461  2491 E TeeFilesystem:   *****************************
04-18 10:21:44.870  2461  2491 E TeeFilesystem:   *** ERROR: void FileSystem::Impl::run(): mcWaitNotification failed, error=0x00000023
04-18 10:21:44.870  2461  2491 E TeeFilesystem:   *** Detected in hardware/samsung_slsi/exynos7880/mobicore/Daemon/src/FSD2.cpp:434()
04-18 10:21:44.870  2461  2491 E TeeFilesystem:   *****************************
04-18 10:21:44.872  2376  2376 I ServiceManager: service 'thermalservice' died
04-18 10:21:44.872  2376  2376 I ServiceManager: service 'drm.drmManager' died
04-18 10:21:44.874  2461  2491 I TeeDriverClient: driver client closed [hardware/samsung_slsi/exynos7880/mobicore/ClientLib/src/driver_client.cpp:113]
04-18 10:21:44.874  2461  2491 W TeeFilesystem: void FileSystem::Impl::run(): Exiting Filesystem thread [hardware/samsung_slsi/exynos7880/mobicore/Daemon/src/FSD2.cpp:475]
04-18 10:21:44.875  2461  2461 I McDaemon: run()<------- [hardware/samsung_slsi/exynos7880/mobicore/Daemon/src/MobiCoreDriverDaemon.cpp:456]
04-18 10:21:44.875  2376  2376 I ServiceManager: service 'storaged' died
04-18 10:21:44.875  2376  2376 I ServiceManager: service 'storaged_pri' died
04-18 10:21:44.910  6091  6091 D vndksupport: Loading /vendor/lib64/hw/android.hardware.light@2.0-impl.so from current namespace instead of sphal namespace.
04-18 10:21:44.914  6091  6091 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-18 10:21:44.899  6091  6091 W blank_screen: type=1400 audit(0.0:2832): avc: denied { search } for name="virtual" dev="sysfs" ino=60 scontext=u:r:blank_screen:s0 tcontext=u:object_r:sysfs_virtual:s0 tclass=dir permissive=0
04-18 10:21:44.917  6091  6091 E SamsungLightsHelper: read_int: failed to open /sys/class/backlight/panel/max_brightness (Permission denied)
04-18 10:21:44.899  6091  6091 W blank_screen: type=1300 audit(0.0:2832): arch=c00000b7 syscall=48 success=no exit=-13 a0=ffffff9c a1=7823245a90 a2=2 a3=0 items=0 ppid=1 auid=4294967295 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=4294967295 exe="/system/bin/blank_screen" subj=u:r:blank_screen:s0 key=(null)
04-18 10:21:44.917  6091  6091 E SamsungLightsHAL: open_lights: failed to read max panel brightness, fallback to 255!
04-18 10:21:44.917  6091  6091 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-18 10:21:44.918  6091  6091 E light   : light_open lights keyboard failed: -22
04-18 10:21:44.918  6091  6091 E light   : Light passthrough failed to load legacy HAL.
04-18 10:21:44.919  6091  6091 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-18 10:21:44.899  6091  6091 W blank_screen: type=1400 audit(0.0:2833): avc: denied { read } for name="max_brightness" dev="sysfs" ino=21576 scontext=u:r:blank_screen:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0
04-18 10:21:44.919  6091  6091 E light   : light_open lights buttons failed: -22
04-18 10:21:44.920  6091  6091 E light   : Light passthrough failed to load legacy HAL.
04-18 10:21:44.920  6091  6091 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-18 10:21:44.920  6091  6091 E light   : light_open lights battery failed: -22
04-18 10:21:44.921  6091  6091 E light   : Light passthrough failed to load legacy HAL.
04-18 10:21:44.921  6091  6091 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-18 10:21:44.921  6091  6091 E light   : light_open lights notifications failed: -22
04-18 10:21:44.921  6091  6091 E light   : Light passthrough failed to load legacy HAL.
04-18 10:21:44.921  6091  6091 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-18 10:21:44.921  6091  6091 E light   : light_open lights attention failed: -22
04-18 10:21:44.921  6091  6091 E light   : Light passthrough failed to load legacy HAL.
04-18 10:21:44.921  6091  6091 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-18 10:21:44.922  6091  6091 E light   : light_open lights bluetooth failed: -22
04-18 10:21:44.922  6091  6091 E light   : Light passthrough failed to load legacy HAL.
04-18 10:21:44.922  6091  6091 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-18 10:21:44.922  6091  6091 E light   : light_open lights wifi failed: -22
04-18 10:21:44.922  6091  6091 E light   : Light passthrough failed to load legacy HAL.
04-18 10:21:44.925  6091  6091 E SamsungLightsHelper: write_int: failed to open /sys/class/backlight/panel/brightness (Permission denied)
04-18 10:21:44.925  6091  6091 E /system/bin/blank_screen: Failed to shut off screen for type 0
04-18 10:21:45.039  2536  2536 I TLC_BAUTH: Call FP cmd 0xa;1509
04-18 10:21:45.040  2536  2536 I TLC_BAUTH: status : 0, cmd : 0x0x0 rsp : 0x0x0;1519
04-18 10:21:45.040  2536  2536 E TLC_BAUTH:   *****************************
04-18 10:21:45.040  2536  2536 E TLC_BAUTH:   *** ERROR: TZ Session is not opened properly - Ignore
04-18 10:21:45.040  2536  2536 E TLC_BAUTH:   *** Detected in BAuth_Cancel/1519()
04-18 10:21:45.040  2536  2536 E TLC_BAUTH:   *****************************
04-18 10:21:45.040  2536  2536 E bauth_FPBAuthService: [fp_sigh] BAuth_Cancel Fail
04-18 10:21:45.040  2536  2536 D bauth_FPBAuthService: FPBAuthService, 5566
04-18 10:21:45.040  2536  2536 I TLC_BAUTH: Call FP cmd 0xc (22);1562
04-18 10:21:45.040  2536  2536 I TLC_BAUTH: set_enroll_session : gSession_Flag = 0;1579
04-18 10:21:45.041  2536  2536 D bauth_FPBAuthService: check_opcode status = 5, opcode = 0, func_ret_val = 0, function_status = 0, timeout = 0
04-18 10:21:45.041  2536  2536 I TLC_BAUTH: Call FP cmd 0xc (30);1562
04-18 10:21:45.041  2536  2536 I TLC_BAUTH: status : 0, cmd : 0x0x0 rsp : 0x0x0;1599
04-18 10:21:45.041  2536  2536 E TLC_BAUTH:   *****************************
04-18 10:21:45.041  2536  2536 E TLC_BAUTH:   *** ERROR: TZ Session is not opened properly - Ignore
04-18 10:21:45.041  2536  2536 E TLC_BAUTH:   *** Detected in BAuth_Control_OP/1599()
04-18 10:21:45.041  2536  2536 E TLC_BAUTH:   *****************************
04-18 10:21:45.041  2536  2536 D bauth_FPBAuthService: check_opcode status = 5, opcode = 30, func_ret_val = 29, function_status = 0, timeout = 0
04-18 10:21:45.042  2536  2536 E bauth_FPBAuthService: check_opcode func_ret_val error = 29
04-18 10:21:45.042  2536  2536 I TLC_BAUTH: Call FUNC ID 0x4;696
04-18 10:21:45.042  2536  2536 I TLC_BAUTH: Trustlet Session is not opened. status : 0;822
04-18 10:21:45.042  2536  2536 I TLC_BAUTH: FUNC ID 0x4 is completed;828
04-18 10:21:45.042  2536  2536 I TLC_BAUTH: FUNC ID 0x2 is completed;463
04-18 10:21:45.042  2536  2536 E (FPLOG) : DeviceEnableInt 0 8 10 1
04-18 10:21:45.042  2536  2536 D bauth_FPBAuthService: [fp_sigh] BAuthSensorControl_DeviceEnableInt Disable Success
04-18 10:21:45.042  2536  2536 E (FPLOG) : 2.0.36.0 DeviceSetClock 0
04-18 10:21:45.042  2536  2536 D bauth_FPDLBAuthSensorControl: FPDLBAuthSensorControl, 220
04-18 10:21:45.043  2536  2536 D bauth_FPBAuthService: [fp_sigh] Sensor Device SpiCtrl off Success
04-18 10:21:45.043  2536  2536 D bauth_FPBAuthService: [fp_sigh] Sensor Device Close Success
04-18 10:21:45.043  2536  2536 D bauth_service: BAuthService, 85
04-18 10:21:45.043  2536  2536 D bauth_FPBAuthService: [fp_sigh] COMPLETED
04-18 10:21:47.827  2376  2376 I ServiceManager: service 'stats' died
04-18 10:21:47.886  2376  2376 I ServiceManager: service 'vold' died

Is this a bug, or a problem with my install? (If it’s a bug, please point me to where I can report it if you know off-hand.)

Thanks!

2

Hello @confusediff,
this failure hasn’t yet occurred with me. Therefore I cannot estimate why this happens to you.

If this would happen to me immediately, I would try the following:

  • Holding the VOL(-) and HOME and POWER buttons simultaneously until the screen goes dark;

  • as soon as the screen goes dark, immediately release the VOL (-) button and press VOL(+) and HOME and POWER simultaneously until the TWRP Recovery start screen is displayed;

  • in TWRP go to > Wipe > Advanced Wipe > activate “Dalvik / ART Cache” and “Cache”, then “Swipe to Wipe” and finally “Reboot System”.

What is the result? Maybe you will tell us?

3

If this won’t work try

  • flash eOS without any other wipe

If it also not working

  • wipe system and flash eOS again.

As long as you don’t wipe or format data nothing will getting lost

4

Thanks! I’ll let the battery drain and give these a try. Report back with results in a while.

5

Does this mean that the above key combination did not produce the desired effect?

6

I haven’t had any problems going into recovery mode in the past, so I decided I would wait until the battery drained since I figured that was when I would see if the solution worked.

After letting the battery drain I turned the phone back on and it worked just fine. Even unplugged it and let it die a couple more times and turned it back on and it didn’t get stuck. Whatever magic was involved here, I guess this problem has been “solved”.

Funny thing that happened while I was killing and resuscitating my phone, one of the times it turned on and booted but then couldn’t load the lock screen. The chin button lights would come on, then the status bar at the top, and sometimes the wallpaper would load for a split second before they all went off again. It just did that on a loop for a little while and didn’t respond to attempts to turn it off in the same way it did before (adb reboot got it done). Not really going to look more into this, since that only happened once out of the few times I let it die. Just thought it was interesting. (I guess it had enough power for boot but not enough power to turn the screen on?) Here are some lines from logcat from when that happened (if you want more lines let me know):

04-19 15:24:51.155 22460 22460 E EffectsConfig: Could not parse effect configuration in any of the default locations.
04-19 15:24:51.155 22460 22460 E EffectsFactoryConfigLoader: Failed to parse XML configuration file
04-19 15:24:51.155 22460 22460 W EffectsFactory: Failed to load XML effect configuration, fallback to .conf
04-19 15:24:51.158 22460 22460 I BufferProvider: found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
04-19 15:24:51.158 22460 22460 I AudioFlinger: Using module 10 as the primary audio interface
04-19 15:24:51.158 22460 22519 I AudioFlinger: AudioFlinger's thread 0xf0919880 tid=22519 ready to run
04-19 15:24:51.158 22460 22519 W AudioFlinger: no wake lock to update, system not ready yet
04-19 15:24:51.159 22460 22519 W AudioFlinger: no wake lock to update, system not ready yet
04-19 15:24:51.159 22460 22460 W AudioFlinger: moveEffects() bad srcOutput 0
04-19 15:24:51.160 22460 22460 I AudioFlinger: openOutput() this 0xf13be000, module 10 Device 0x2, SamplingRate 48000, Format 0x000001, Channels 0x3, flags 0x8
04-19 15:24:51.160 22460 22460 I AudioFlinger: HAL output buffer size 480 frames, normal sink buffer size 960 frames
04-19 15:24:51.161 22460 22521 I AudioFlinger: AudioFlinger's thread 0xf0417ec0 tid=22521 ready to run
04-19 15:24:51.161 22460 22521 W AudioFlinger: no wake lock to update, system not ready yet
04-19 15:24:51.161 22460 22521 W AudioFlinger: no wake lock to update, system not ready yet
04-19 15:24:51.162 22460 22522 I AudioFlinger: AudioFlinger's thread 0xf0103500 tid=22522 ready to run
04-19 15:24:51.163 22458 22458 I PackageBackwardCompatibility: Loaded android.content.pm.OrgApacheHttpLegacyUpdater
04-19 15:24:51.164 22458 22458 I PackageBackwardCompatibility: Could not find android.content.pm.AndroidTestBaseUpdater, ignoring
04-19 15:24:51.167 22460 22460 I bt_a2dp_hw: adev_open:  adev_open in A2dp_hw module
04-19 15:24:51.168 22460 22460 I AudioFlinger: loadHwModule() Loaded a2dp audio interface, handle 18
04-19 15:24:51.168 22460 22460 D vndksupport: Loading /vendor/lib/hw/audio.usb.default.so from current namespace instead of sphal namespace.
04-19 15:24:51.169 22460 22460 I AudioFlinger: loadHwModule() Loaded usb audio interface, handle 26
04-19 15:24:51.169 22460 22460 D vndksupport: Loading /vendor/lib/hw/audio.r_submix.default.so from current namespace instead of sphal namespace.
04-19 15:24:51.170 22460 22460 I r_submix: adev_open(name=audio_hw_if)
04-19 15:24:51.170 22460 22460 I r_submix: adev_init_check()
04-19 15:24:51.170 22460 22460 W DeviceHAL: Error from HAL Device in function set_master_mute: Function not implemented
04-19 15:24:51.171 22460 22460 I AudioFlinger: loadHwModule() Loaded r_submix audio interface, handle 34
04-19 15:24:51.171 22460 22460 D r_submix: adev_open_input_stream(addr=0)
04-19 15:24:51.171 22460 22460 D r_submix: submix_audio_device_create_pipe_l(addr=0, idx=9)
04-19 15:24:51.171 22460 22460 D r_submix:   now using address 0 for route 9
04-19 15:24:51.171 22460 22523 I AudioFlinger: AudioFlinger's thread 0xf011c100 tid=22523 ready to run
04-19 15:24:51.171 22460 22460 D r_submix: adev_close_input_stream()
04-19 15:24:51.171 22460 22460 D r_submix: submix_audio_device_release_pipe_l(idx=9) addr=0
04-19 15:24:51.171 22460 22460 D r_submix: submix_audio_device_destroy_pipe_l(): pipe destroyed
04-19 15:24:51.172 22460 22460 E EffectsConfig: Could not parse effect configuration in any of the default locations.
04-19 15:24:51.172 22460 22460 W AudioPolicyEffects: Failed to load XML effect configuration, fallback to .conf
04-19 15:24:51.172 22460 22460 I         : Waiting for activity service
04-19 15:24:51.365 22458 22458 E ActivityRecognitionHardware: activity_recognition HAL is deprecated. class_init is effectively a no-op
04-19 15:24:51.422 22458 22458 I zygote64: Thread[1,tid=22458,Native,Thread*=0x77da414c00,peer=0x13000088,"main"] recursive attempt to load library "/system/lib64/libmedia_jni.so"
04-19 15:24:51.422 22458 22458 D MtpDeviceJNI: register_android_mtp_MtpDevice
04-19 15:24:51.423 22458 22458 I zygote64: Thread[1,tid=22458,Native,Thread*=0x77da414c00,peer=0x13000088,"main"] recursive attempt to load library "/system/lib64/libmedia_jni.so"
04-19 15:24:51.423 22458 22458 I zygote64: Thread[1,tid=22458,Native,Thread*=0x77da414c00,peer=0x13000088,"main"] recursive attempt to load library "/system/lib64/libmedia_jni.so"
04-19 15:24:51.573 22458 22458 I Zygote  : ...preloaded 6535 classes in 423ms.
04-19 15:24:51.573 22458 22458 I zygote64: VMRuntime.preloadDexCaches starting
04-19 15:24:51.622 22458 22458 I zygote64: VMRuntime.preloadDexCaches strings total=292682 before=12074 after=12074
04-19 15:24:51.622 22458 22458 I zygote64: VMRuntime.preloadDexCaches types total=31449 before=7836 after=7837
04-19 15:24:51.622 22458 22458 I zygote64: VMRuntime.preloadDexCaches fields total=141527 before=9160 after=9160
04-19 15:24:51.622 22458 22458 I zygote64: VMRuntime.preloadDexCaches methods total=248960 before=12783 after=12783
04-19 15:24:51.622 22458 22458 I zygote64: VMRuntime.preloadDexCaches finished
04-19 15:24:51.622 22458 22458 D Zygote64Timing: PreloadClasses took to complete: 472ms
04-19 15:24:51.703 22458 22458 I Zygote  : Preloading resources...
04-19 15:24:51.711 22458 22458 W Resources: Preloaded drawable resource #0x1080265 (android:drawable/dialog_background_material) that varies with configuration!!
04-19 15:24:51.727 22458 22458 I Zygote  : ...preloaded 64 resources in 24ms.
04-19 15:24:51.731 22458 22458 I Zygote  : ...preloaded 41 resources in 4ms.
04-19 15:24:51.732 22458 22458 I Zygote  : ...preloaded 2 resource in 1ms.
04-19 15:24:51.733 22458 22458 D Zygote64Timing: PreloadResources took to complete: 110ms
04-19 15:24:51.733 22458 22458 D vndksupport: Loading /vendor/lib64/hw/android.hardware.graphics.mapper@2.0-impl.so from current namespace instead of sphal namespace.
04-19 15:24:51.734 22458 22458 D vndksupport: Loading /vendor/lib64/egl/libGLES_mali.so from current namespace instead of sphal namespace.
04-19 15:24:51.751 22458 22458 D libEGL  : loaded /vendor/lib64/egl/libGLES_mali.so
04-19 15:24:51.805 22458 22458 I Zygote  : Preloading shared libraries...
04-19 15:24:51.811 22458 22458 I Zygote  : Uninstalled ICU cache reference pinning...
04-19 15:24:51.811 22458 22458 I Zygote  : Installed AndroidKeyStoreProvider in 1ms.
04-19 15:24:51.822 22458 22458 I Zygote  : Warmed up JCA providers in 11ms.
04-19 15:24:51.822 22458 22458 D Zygote  : end preload
04-19 15:24:51.822 22458 22458 D Zygote64Timing: ZygotePreload took to complete: 682ms
04-19 15:24:51.853 22458 22458 I zygote64: Explicit concurrent copying GC freed 42739(2MB) AllocSpace objects, 1(20KB) LOS objects, 72% free, 2MB/8MB, paused 42us total 30.397ms
04-19 15:24:51.880 22458 22458 I zygote64: Explicit concurrent copying GC freed 1726(99KB) AllocSpace objects, 0(0B) LOS objects, 73% free, 2MB/8MB, paused 30us total 25.134ms
04-19 15:24:51.880 22458 22458 D Zygote64Timing: PostZygoteInitGC took to complete: 58ms
04-19 15:24:51.880 22458 22458 D Zygote64Timing: ZygoteInit took to complete: 740ms
04-19 15:24:51.994 22458 22458 I Zygote  : System server process 22525 has been created
04-19 15:24:51.997 22458 22458 I Zygote  : Accepting command socket connections
04-19 15:24:52.017 22525 22525 I Zygote  : Process: zygote socket RESERVED/zygote_secondary opened, supported ABIS: armeabi-v7a,armeabi
04-19 15:24:52.027 22525 22525 I system_server: The ClassLoaderContext is a special shared library.
04-19 15:24:52.108 22525 22525 I SystemServer: InitBeforeStartServices
04-19 15:24:52.108 22525 22525 I SystemServer: Entered the Android system server!
04-19 15:24:52.065 22525 22525 I chatty  : uid=1000 system_server identical 4 lines
04-19 15:24:52.068 22525 22525 I system_server: The ClassLoaderContext is a special shared library.
04-19 15:24:52.275 22525 22525 E UsbAlsaJackDetectorJNI: Can't register UsbAlsaJackDetector native methods
04-19 15:24:52.284 22525 22525 D SystemServerTiming: InitBeforeStartServices took to complete: 177ms
04-19 15:24:52.285 22525 22525 I SystemServer: StartServices
04-19 15:24:52.285 22525 22525 I SystemServer: Reading configuration...
04-19 15:24:52.285 22525 22525 I SystemServer: ReadingSystemConfig
04-19 15:24:52.285 22525 22525 D SystemServerTiming: ReadingSystemConfig took to complete: 1ms
04-19 15:24:52.285 22525 22525 I SystemServer: StartInstaller
04-19 15:24:52.285 22525 22525 I SystemServiceManager: Starting com.android.server.pm.Installer
04-19 15:24:52.286 22525 22538 D SystemServerInitThreadPool: Started executing ReadingSystemConfig
04-19 15:24:52.287  2526  2734 D installd: Found storage mount /data/media at /mnt/runtime/default/emulated
04-19 15:24:52.287 22525 22525 D SystemServerTiming: StartInstaller took to complete: 2ms
04-19 15:24:52.288 22525 22525 I SystemServer: DeviceIdentifiersPolicyService
04-19 15:24:52.288 22525 22525 I SystemServiceManager: Starting com.android.server.os.DeviceIdentifiersPolicyService
04-19 15:24:52.288 22525 22525 D SystemServerTiming: DeviceIdentifiersPolicyService took to complete: 1ms
04-19 15:24:52.288 22525 22525 I SystemServer: StartActivityManager
04-19 15:24:52.288 22525 22525 I SystemServiceManager: Starting com.android.server.am.ActivityManagerService$Lifecycle
04-19 15:24:52.308 22525 22538 W SystemConfig: No directory /product/etc/sysconfig, skipping
04-19 15:24:52.308 22525 22538 W SystemConfig: No directory /product/etc/permissions, skipping
04-19 15:24:52.308 22525 22538 D SystemServerInitThreadPool: Finished executing ReadingSystemConfig
04-19 15:24:52.462 22525 22525 I ActivityManager: Memory class: 128
04-19 15:24:52.469 22525 22525 D BatteryStatsImpl: Reading daily items from /data/system/batterystats-daily.xml
04-19 15:24:52.479 22525 22544 E BluetoothAdapter: Bluetooth binder is null
04-19 15:24:52.480 22525 22544 E BatteryExternalStatsWorker: no controller energy info supplied for telephony
04-19 15:24:52.480 22525 22544 E KernelUidCpuFreqTimeReader: Failed to read /proc/uid_time_in_state: java.io.FileNotFoundException: /proc/uid_time_in_state (No such file or directory)
04-19 15:24:52.485 22525 22544 W KernelCpuProcReader: File not exist: /proc/uid_cpupower/concurrent_active_time
04-19 15:24:52.485 22525 22544 W KernelCpuProcReader: File not exist: /proc/uid_cpupower/concurrent_policy_time
04-19 15:24:52.488 22525 22544 W KernelMemoryBandwidthStats: No kernel memory bandwidth stats available
04-19 15:24:52.490 22525 22544 D vndksupport: Loading /vendor/lib64/hw/android.hardware.power@1.0-impl.so from current namespace instead of sphal namespace.
04-19 15:24:52.496 22525 22544 I SamsungPowerHAL: Initialized settings:
04-19 15:24:52.496 22525 22544 I SamsungPowerHAL: max_freqs: cluster[0]: 1872000, cluster[1]: 1872000
04-19 15:24:52.496 22525 22544 I SamsungPowerHAL: hispeed_freqs: cluster[0]: 902000, cluster[1]: 900000
04-19 15:24:52.496 22525 22544 I SamsungPowerHAL: boostpulse_fd: 49
04-19 15:24:52.496 22525 22544 I SamsungPowerHAL: touchscreen_power_path: /sys/class/input/input1/enabled
04-19 15:24:52.496 22525 22544 I SamsungPowerHAL: touchkey_power_path: /sys/class/input/input0/enabled
04-19 15:24:52.496 22525 22544 I PowerManagerService-JNI: Loaded power HAL 1.0 service
04-19 15:24:52.497 22525 22544 E KernelUidCpuFreqTimeReader: Failed to read /proc/uid_time_in_state: java.io.FileNotFoundException: /proc/uid_time_in_state (No such file or directory)
04-19 15:24:52.550 22525 22525 D vndksupport: Loading /vendor/lib64/hw/android.hardware.memtrack@1.0-impl.so from current namespace instead of sphal namespace.
04-19 15:24:52.551 22525 22525 D vndksupport: Loading /vendor/lib64/hw/memtrack.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.566 22525 22525 I IntentFirewall: Read new rules (A:0 B:0 S:0)
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_1640: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2357: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2381: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2456: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2474: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2480: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2483: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2507: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2520: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2526: Device or resource busy
04-19 15:24:52.572 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2533: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_2540: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_3103: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_22458: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_22459: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0/pid_22463: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_0: Permission denied
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2378: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2379: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2380: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2464: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2472: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2478: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2479: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2484: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2486: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2522: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2539: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000/pid_2543: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1000: Permission denied
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1001/pid_2521: Device or resource busy
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1001: Permission denied
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1003: Permission denied
04-19 15:24:52.573 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1010/pid_22464: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1010: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1013/pid_2477: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1013/pid_2528: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1013/pid_2530: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1013/pid_22462: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1013: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1017/pid_2527: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1017: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1019/pid_2524: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1019: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1021/pid_2519: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1021: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1027: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1036/pid_2377: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1036: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1037: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1040/pid_2529: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1040: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1041/pid_22460: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1041: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1046/pid_2535: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1046: Permission denied
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1047/pid_22461: Device or resource busy
04-19 15:24:52.574 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1047: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1053: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1058/pid_2541: Device or resource busy
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1058: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1066/pid_2532: Device or resource busy
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1066: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1067/pid_2525: Device or resource busy
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1067: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_1068: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_10008: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_10017: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_10020: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_10022: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_10031: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_10044: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_10096: Permission denied
04-19 15:24:52.575 22525 22525 W libprocessgroup: Failed to remove /acct/uid_10097: Permission denied
04-19 15:24:52.576 22525 22525 D AppOps  : AppOpsService published
04-19 15:24:52.577 22525 22525 D SystemServerTiming: StartActivityManager took to complete: 288ms
04-19 15:24:52.577 22525 22525 I SystemServer: StartPowerManager
04-19 15:24:52.577 22525 22525 I SystemServiceManager: Starting com.android.server.power.PowerManagerService
04-19 15:24:52.579 22525 22525 E SamsungPowerHAL: Error opening /sys/class/input/input1/enabled: Permission denied
04-19 15:24:52.579 22525 22525 E SamsungPowerHAL: Error opening /sys/devices/system/cpu/cpu4/cpufreq/interactive/io_is_busy: Permission denied
04-19 15:24:52.580 22525 22525 D SystemServerTiming: StartPowerManager took to complete: 4ms
04-19 15:24:52.580 22525 22525 I SystemServer: InitPowerManagement
04-19 15:24:52.581 22525 22525 D SystemServerTiming: InitPowerManagement took to complete: 0ms
04-19 15:24:52.581 22525 22525 I SystemServer: StartRecoverySystemService
04-19 15:24:52.581 22525 22525 I SystemServiceManager: Starting com.android.server.RecoverySystemService
04-19 15:24:52.582 22525 22525 D SystemServerTiming: StartRecoverySystemService took to complete: 0ms
04-19 15:24:52.582 22525 22525 V RescueParty: Disabled because of active USB connection
04-19 15:24:52.582 22525 22525 I SystemServer: StartLightsService
04-19 15:24:52.582 22525 22525 I SystemServiceManager: Starting com.android.server.lights.LightsService
04-19 15:24:52.583 22525 22525 D SystemServerTiming: StartLightsService took to complete: 0ms
04-19 15:24:52.583 22525 22525 I SystemServer: StartSidekickService
04-19 15:24:52.583 22525 22525 D SystemServerTiming: StartSidekickService took to complete: 0ms
04-19 15:24:52.583 22525 22525 I SystemServer: StartDisplayManager
04-19 15:24:52.583 22525 22525 I SystemServiceManager: Starting com.android.server.display.DisplayManagerService
04-19 15:24:52.585 22525 22525 D SystemServerTiming: StartDisplayManager took to complete: 3ms
04-19 15:24:52.585 22525 22525 I SystemServer: WaitForDisplay
04-19 15:24:52.585 22525 22525 I SystemServiceManager: Starting phase 100
04-19 15:24:52.590 22525 22548 E LocalDisplayAdapter: Default and active color mode is no longer available! Reverting to first available mode.
04-19 15:24:52.593 22525 22548 I DisplayManagerService: Display device added: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 1080 x 1920, modeId 1, defaultModeId 1, supportedModes [{id=1, width=1080, height=1920, fps=59.0}], colorMode -22, supportedColorModes [-22], HdrCapabilities android.view.Display$HdrCapabilities@40f16308, density 480, 422.03 x 424.069 dpi, appVsyncOff 1000000, presDeadline 16949152, touch INTERNAL, rotation 0, type BUILT_IN, state UNKNOWN, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
04-19 15:24:52.594  2484  2484 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x6fe7058000
04-19 15:24:52.595 22525 22548 D vndksupport: Loading /vendor/lib64/hw/android.hardware.light@2.0-impl.so from current namespace instead of sphal namespace.
04-19 15:24:52.598 22525 22548 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.598 22525 22548 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.599 22525 22548 E light   : light_open lights keyboard failed: -22
04-19 15:24:52.599 22525 22548 E light   : Light passthrough failed to load legacy HAL.
04-19 15:24:52.599 22525 22548 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.600 22525 22548 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.600 22525 22548 E light   : light_open lights battery failed: -22
04-19 15:24:52.600 22525 22548 E light   : Light passthrough failed to load legacy HAL.
04-19 15:24:52.600 22525 22548 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.601 22525 22548 E light   : light_open lights notifications failed: -22
04-19 15:24:52.601 22525 22548 E light   : Light passthrough failed to load legacy HAL.
04-19 15:24:52.601 22525 22548 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.601 22525 22548 E light   : light_open lights attention failed: -22
04-19 15:24:52.601 22525 22548 E light   : Light passthrough failed to load legacy HAL.
04-19 15:24:52.602 22525 22548 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.602 22525 22548 E light   : light_open lights bluetooth failed: -22
04-19 15:24:52.602 22525 22548 E light   : Light passthrough failed to load legacy HAL.
04-19 15:24:52.602 22525 22548 D vndksupport: Loading /vendor/lib64/hw/lights.universal7880.so from current namespace instead of sphal namespace.
04-19 15:24:52.603 22525 22548 E light   : light_open lights wifi failed: -22
04-19 15:24:52.603 22525 22548 E light   : Light passthrough failed to load legacy HAL.
04-19 15:24:52.606 22525 22548 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
04-19 15:24:52.607 22525 22525 D SystemServerTiming: WaitForDisplay took to complete: 21ms
04-19 15:24:52.607 22525 22525 I SystemServer: StartPackageManagerService

Thanks for all your help!

Those with the capability to do so may mark this issue as closed.

7

It would be interesting to know if deleting caches with “Dalvik / ART Cache” and “Cache” would produce the same effect.

As long as the Discourse “Solved” plugin is not yet implemented, the topic opener itself must be hand. Click on the pencil and add [SOLVED] to the headline. Thanks.

[SOLVED] Samsung Galaxy A5 bootloop after battery dies