Random system crashes on OnePlus 5T apparently caused by camera - Android Q&A, Help & Troubleshooting

The system randomly crashes on my OnePlus 5T, it just hangs for a few seconds and then does a reboot (sometimes only a soft reboot). I'm running OxygenOS Open Beta 33 (Android 9) with ElementalX, Magisk and EdXposed. I've finally managed to capture a logcat and it seems like it's something related to the camera, even though I don't actively use it when the crash happens, and I don't have any camera-specific mods installed.
Logcat
07-23 12:27:29.692 1834 11714 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 11714 (Binder:1834_1B), pid 1834 (system_server)
07-23 12:27:29.896 1834 7981 W ActivityManager: Permission Denial: Accessing service ComponentInfo{com.google.android.music/com.google.android.music.dial.DialMediaRoutePro viderService} from pid=4124, uid=10023 that is not exported from uid 10068
07-23 12:27:29.902 15952 15952 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-23 12:27:29.902 15952 15952 F DEBUG : Build fingerprint: 'OnePlus/OnePlus5T/OnePlus5T:9/PKQ1.180716.001/1906100000:user/release-keys'
07-23 12:27:29.902 15952 15952 F DEBUG : Revision: '0'
07-23 12:27:29.902 15952 15952 F DEBUG : ABI: 'arm64'
07-23 12:27:29.902 15952 15952 F DEBUG : pid: 1834, tid: 11714, name: Binder:1834_1B >>> system_server <<<
07-23 12:27:29.902 15952 15952 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
07-23 12:27:29.902 15952 15952 F DEBUG : Abort message: 'monitor.cc:1157] Invalid monitor state ForwardingAddress'
07-23 12:27:29.902 15952 15952 F DEBUG : x0 0000000000000000 x1 0000000000002dc2 x2 0000000000000006 x3 0000000000000008
07-23 12:27:29.902 15952 15952 F DEBUG : x4 000000713de59100 x5 000000713de59100 x6 000000713de59100 x7 000000713de59380
07-23 12:27:29.902 15952 15952 F DEBUG : x8 0000000000000083 x9 46f83f518cc1e292 x10 0000000000000000 x11 fffffffc7ffffbdf
07-23 12:27:29.902 15952 15952 F DEBUG : x12 0000000000000001 x13 000000713de594c0 x14 0000000000000000 x15 00000071e72dd000
07-23 12:27:29.902 15952 15952 F DEBUG : x16 00000071e72d12a8 x17 00000071e71f0954 x18 0000000000000000 x19 000000000000072a
07-23 12:27:29.902 15952 15952 F DEBUG : x20 0000000000002dc2 x21 0000007132592380 x22 00000071324ab000 x23 000000716131d608
07-23 12:27:29.902 15952 15952 F DEBUG : x24 000000000000000b x25 000000716131f048 x26 0000000000000000 x27 00000000c2dc8004
07-23 12:27:29.902 15952 15952 F DEBUG : x28 0000007132fff588 x29 0000007132ffe760
07-23 12:27:29.902 15952 15952 F DEBUG : sp 0000007132ffe720 lr 00000071e71e4084 pc 00000071e71e40ac
07-23 12:27:29.910 1834 1966 E NotificationService: Suppressing notification from package by user request. Package: net.dinglisch.android.taskerm isGroupBlocked: false isRankingImportanceNone: true isRecordImportanceNone: false
07-23 12:27:29.973 15952 15952 F DEBUG :
07-23 12:27:29.973 15952 15952 F DEBUG : backtrace:
07-23 12:27:29.973 15952 15952 F DEBUG : #00 pc 00000000000220ac /system/lib64/libc.so (abort+116)
07-23 12:27:29.973 15952 15952 F DEBUG : #01 pc 00000000004645d8 /system/lib64/libart.so (offset 0x43d000) (art::Runtime::Abort(char const*)+1196)
07-23 12:27:29.973 15952 15952 F DEBUG : #02 pc 0000000000008ce0 /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+724)
07-23 12:27:29.973 15952 15952 F DEBUG : #03 pc 00000000003be624 /system/lib64/libart.so (offset 0x374000) (art::Monitor::MonitorEnter(art::Thread*, art::mirror:bject*, bool)+1456)
07-23 12:27:29.973 15952 15952 F DEBUG : #04 pc 0000000000514b90 /system/lib64/libart.so (offset 0x43e000) (artLockObjectFromCode+36)
07-23 12:27:29.973 15952 15952 F DEBUG : #05 pc 0000000000555c98 /system/lib64/libart.so (offset 0x43e000) (art_quick_lock_object+152)
07-23 12:27:29.973 15952 15952 F DEBUG : #06 pc 0000000000abf000 /system/framework/arm64/boot-framework.oat (offset 0x3da000) (android.os.BaseBundle.writeToParcelInner+160)
07-23 12:27:29.973 15952 15952 F DEBUG : #07 pc 0000000000c1bba0 /system/framework/arm64/boot-framework.oat (offset 0x3da000) (android.os.Bundle.writeToParcel+128)
07-23 12:27:29.973 15952 15952 F DEBUG : #08 pc 0000000000ad8d54 /system/framework/arm64/boot-framework.oat (offset 0x3da000) (android.os.Parcel.writeBundle+116)
07-23 12:27:29.973 15952 15952 F DEBUG : #09 pc 0000000000a19440 /system/framework/arm64/boot-framework.oat (offset 0x3da000) (android.content.ContentProviderNative.onTransact+2272)
07-23 12:27:29.973 15952 15952 F DEBUG : #10 pc 0000000000c17e18 /system/framework/arm64/boot-framework.oat (offset 0x3da000) (android.os.Binder.execTransact+600)
07-23 12:27:29.973 15952 15952 F DEBUG : #11 pc 0000000000555788 /system/lib64/libart.so (offset 0x43e000) (art_quick_invoke_stub+584)
07-23 12:27:29.973 15952 15952 F DEBUG : #12 pc 00000000000cf6c8 /system/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+200)
07-23 12:27:29.973 15952 15952 F DEBUG : #13 pc 000000000045cd00 /system/lib64/libart.so (offset 0x374000) (art:anonymous namespace)::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art:anonymous namespace)::ArgArray*, art::JValue*, char const*)+104)
07-23 12:27:29.973 15952 15952 F DEBUG : #14 pc 000000000045e094 /system/lib64/libart.so (offset 0x374000) (art::InvokeVirtualOrInterfaceWithVarArgs(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, std::__va_list)+440)
07-23 12:27:29.973 15952 15952 F DEBUG : #15 pc 0000000000333df0 /system/lib64/libart.so (offset 0x20c000) (art::JNI::CallBooleanMethodV(_JNIEnv*, _jobject*, _jmethodID*, std::__va_list)+656)
07-23 12:27:29.973 15952 15952 F DEBUG : #16 pc 00000000000c5ec8 /system/lib64/libandroid_runtime.so (_JNIEnv::CallBooleanMethod(_jobject*, _jmethodID*, ...)+116)
07-23 12:27:29.973 15952 15952 F DEBUG : #17 pc 00000000001376dc /system/lib64/libandroid_runtime.so (JavaBBinder:nTransact(unsigned int, android:arcel const&, android:arcel*, unsigned int)+156)
07-23 12:27:29.973 15952 15952 F DEBUG : #18 pc 000000000004fd2c /system/lib64/libbinder.so (android::BBinder::transact(unsigned int, android:arcel const&, android:arcel*, unsigned int)+136)
07-23 12:27:29.973 15952 15952 F DEBUG : #19 pc 000000000005d558 /system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+520)
07-23 12:27:29.973 15952 15952 F DEBUG : #20 pc 000000000005d29c /system/lib64/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+156)
07-23 12:27:29.973 15952 15952 F DEBUG : #21 pc 000000000005d98c /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+108)
07-23 12:27:29.973 15952 15952 F DEBUG : #22 pc 0000000000080074 /system/lib64/libbinder.so (android:oolThread::threadLoop()+24)
07-23 12:27:29.973 15952 15952 F DEBUG : #23 pc 00000000000100dc /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284)
07-23 12:27:29.973 15952 15952 F DEBUG : #24 pc 00000000000b5aa0 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140)
07-23 12:27:29.973 15952 15952 F DEBUG : #25 pc 000000000008ffc8 /system/lib64/libc.so (__pthread_start(void*)+36)
07-23 12:27:29.973 15952 15952 F DEBUG : #26 pc 0000000000023968 /system/lib64/libc.so (__start_thread+68)
07-23 12:27:31.348 1047 15920 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 15920 (CAM_strmDatProc), pid 1047 ([email protected])
07-23 12:27:31.480 16052 16052 I wificond: wificond is starting up...
07-23 12:27:31.534 16045 16045 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-23 12:27:31.534 16045 16045 F DEBUG : Build fingerprint: 'OnePlus/OnePlus5T/OnePlus5T:9/PKQ1.180716.001/1906100000:user/release-keys'
07-23 12:27:31.534 16045 16045 F DEBUG : Revision: '0'
07-23 12:27:31.534 16045 16045 F DEBUG : ABI: 'arm'
07-23 12:27:31.534 16045 16045 F DEBUG : pid: 1047, tid: 15920, name: CAM_strmDatProc >>> /vendor/bin/hw/[email protected] <<<
07-23 12:27:31.534 16045 16045 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
07-23 12:27:31.534 16045 16045 F DEBUG : Abort message: 'Status.cpp:142] Attempted to retrieve value from failed HIDL call: Status(EX_TRANSACTION_FAILED): 'DEAD_OBJECT: ''
07-23 12:27:31.534 16045 16045 F DEBUG : r0 00000000 r1 00003e30 r2 00000006 r3 00000008
07-23 12:27:31.534 16045 16045 F DEBUG : r4 00000417 r5 00003e30 r6 dc99b644 r7 0000010c
07-23 12:27:31.534 16045 16045 F DEBUG : r8 dc99b9c8 r9 00000000 r10 f4c31d4c r11 e1ec4cc0
07-23 12:27:31.534 16045 16045 F DEBUG : ip f47233cc sp dc99b630 lr f468eb7d pc f4684fde
07-23 12:27:31.565 16045 16045 F DEBUG :
07-23 12:27:31.565 16045 16045 F DEBUG : backtrace:
07-23 12:27:31.565 16045 16045 F DEBUG : #00 pc 0001cfde /system/lib/libc.so (abort+58)
07-23 12:27:31.565 16045 16045 F DEBUG : #01 pc 000069f7 /system/lib/vndk-sp-28/libbase.so (android::base:efaultAborter(char const*)+6)
07-23 12:27:31.565 16045 16045 F DEBUG : #02 pc 00007267 /system/lib/vndk-sp-28/libbase.so (android::base::LogMessage::~LogMessage()+494)
07-23 12:27:31.565 16045 16045 F DEBUG : #03 pc 00006ba3 /system/lib/vndk-sp-28/libhidlbase.so (android::hardware::details::return_status::assertOk() const+162)
07-23 12:27:31.565 16045 16045 F DEBUG : #04 pc 0000d615 /vendor/lib/[email protected] (android::hardware::camera::device::V1_0::implementation::CameraDevice::sEnqueueBuffer(preview_stream_ops*, native_handle const**)+160)
07-23 12:27:31.565 16045 16045 F DEBUG : #05 pc 000a3c61 /vendor/lib/hw/camera.msm8998.so (qcamera::QCameraGrallocMemory::enqueueBuffer(unsigned int, long long)+92)
07-23 12:27:31.565 16045 16045 F DEBUG : #06 pc 000b91d9 /vendor/lib/hw/camera.msm8998.so (qcamera::QCamera2HardwareInterface:review_stream_cb_routine(mm_camera_super_buf_t*, qcamera::QCameraStream*, void*)+1124)
07-23 12:27:31.565 16045 16045 F DEBUG : #07 pc 000ad541 /vendor/lib/hw/camera.msm8998.so (qcamera::QCameraStream::dataProcRoutine(void*)+148)
07-23 12:27:31.565 16045 16045 F DEBUG : #08 pc 00072c51 /system/lib/libc.so (__pthread_start(void*)+22)
07-23 12:27:31.565 16045 16045 F DEBUG : #09 pc 0001e005 /system/lib/libc.so (__start_thread+24)
07-23 12:27:32.251 16052 16052 W wificond: No handler for scan result notification from interface with index: 26
07-23 12:27:32.270 16049 16092 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 16092 (HwBinder:16049_), pid 16049 (cameraserver)
07-23 12:27:32.323 16145 16145 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-23 12:27:32.323 16145 16145 F DEBUG : Build fingerprint: 'OnePlus/OnePlus5T/OnePlus5T:9/PKQ1.180716.001/1906100000:user/release-keys'
07-23 12:27:32.323 16145 16145 F DEBUG : Revision: '0'
07-23 12:27:32.323 16145 16145 F DEBUG : ABI: 'arm'
07-23 12:27:32.323 16145 16145 F DEBUG : pid: 16049, tid: 16092, name: HwBinder:16049_ >>> /system/bin/cameraserver <<<
07-23 12:27:32.323 16145 16145 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
07-23 12:27:32.323 16145 16145 F DEBUG : r0 00000000 r1 00003edc r2 00000006 r3 f4e13180
07-23 12:27:32.323 16145 16145 F DEBUG : r4 f4e13180 r5 f5d03ff5 r6 f69e24d0 r7 0000010c
07-23 12:27:32.323 16145 16145 F DEBUG : r8 f4083408 r9 f3f81920 r10 00000001 r11 f3f8192c
07-23 12:27:32.323 16145 16145 F DEBUG : ip f69b6125 sp f3f816e0 lr f5d03fd3 pc f68d5a94
07-23 12:27:32.938 16145 16145 F DEBUG :
07-23 12:27:32.938 16145 16145 F DEBUG : backtrace:
07-23 12:27:32.938 16145 16145 F DEBUG : #00 pc 00062a94 /system/lib/libc.so (tgkill+12)
07-23 12:27:32.938 16145 16145 F DEBUG : #01 pc 00096fcf /system/lib/libcameraservice.so (android::CameraProviderManager:roviderInfo::serviceDied(unsigned long long, android::wp<android::hidl::base::V1_0::IBase> const&)+74)
07-23 12:27:32.938 16145 16145 F DEBUG : #02 pc 00097001 /system/lib/libcameraservice.so (_ZTv0_n16_N7android21CameraProviderManager12ProviderInfo11serviceDiedEyRKNS_2wpINS_4hidl4base4V1_05IBaseEEE+12)
07-23 12:27:32.938 16145 16145 F DEBUG : #03 pc 0001c167 /system/lib/libhidltransport.so (android::hardware::hidl_binder_death_recipient::binderDied(android::wp<android::hardware::IBinder> const&)+66)
07-23 12:27:32.938 16145 16145 F DEBUG : #04 pc 0000dda5 /system/lib/libhwbinder.so (android::hardware::BpHwBinder::reportOneDeath(android::hardware::BpHwBinder:bituary const&)+80)
07-23 12:27:32.938 16145 16145 F DEBUG : #05 pc 0000dd3d /system/lib/libhwbinder.so (android::hardware::BpHwBinder::sendObituary()+336)
07-23 12:27:32.938 16145 16145 F DEBUG : #06 pc 00014253 /system/lib/libhwbinder.so (android::hardware::IPCThreadState::executeCommand(int)+1022)
07-23 12:27:32.938 16145 16145 F DEBUG : #07 pc 00013d57 /system/lib/libhwbinder.so (android::hardware::IPCThreadState::getAndExecuteCommand()+98)
07-23 12:27:32.938 16145 16145 F DEBUG : #08 pc 0000e461 /system/lib/libhwbinder.so (android::hardware::IPCThreadState::joinThreadPool(bool)+64)
07-23 12:27:32.938 16145 16145 F DEBUG : #09 pc 00011355 /system/lib/libhwbinder.so
07-23 12:27:32.938 16145 16145 F DEBUG : #10 pc 0000c6af /system/lib/libutils.so (android::Thread::_threadLoop(void*)+202)
07-23 12:27:32.938 16145 16145 F DEBUG : #11 pc 00072c51 /system/lib/libc.so (__pthread_start(void*)+22)
07-23 12:27:32.938 16145 16145 F DEBUG : #12 pc 0001e005 /system/lib/libc.so (__start_thread+24)
Click to expand...
Click to collapse

Related

Galaxy S3 Rebooting Randomly - LOG

I'd really love some help, because I've spent weeks of trial and error and trying to understand logs, but I just can't figure out what's wrong.
-Samsung Galaxy S3
-Randomly rebooting
Reboots between 5-20 times a day.
Never reboots while connected to power.
3 different batteries tried with same results.
Reboots even while sitting stationary with no intervention.
-Stock ROM
-Phone only recently rooted to aid with logging.
-Logcat taken - see copy at pastebin.com/XryCQViS
Hey, thanks.
@drooble: may be caused by a faulty power button (xda-search would have helped)
rp158 said:
@drooble: may be caused by a faulty power button (xda-search would have helped)
Click to expand...
Click to collapse
Hey thanks for the response
I don't think the power button is the culprit. (It's one of the many things I've tested).
I removed the case to start with and it still occurred.
I left the phone sitting on a desk without touching it and it still occurred.
And finally - when I hold the power button down the screen presents you with a power down menu. The intermittent rebooting occurs without displaying this menu.
Does the log suggest otherwise? I don't know what I'm looking for. I have other logs too - I just linked one of the most recent.
Could be oom error.
Beamed in by telepathy.
shivadow said:
Could be oom error.
Beamed in by telepathy.
Click to expand...
Click to collapse
Okay - does the log show that? Or how do I diagnose that? How would I fix that?
One of my suggestions would be to install TWRP, take a full back-up of the ROM and try to install a custom ROM and see if it also happens on a custom ROM.
Why? Because i see this part of the log that seems weird:
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: Build: samsung/m0xx/m0:4.3/JSS15J/I9300XXUGNB4:user/release-keys
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: Hardware: smdk4x12
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: Revision: 12
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: Bootloader: I9300XXUGNB4
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: Radio: I9300XXUGNA8
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: Kernel: Linux version 3.0.31-2372379 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Mon Feb 17 19:29:50 KST 2014
07-23 11:05:56.460 5091 5177 D CrashAnrDetector:
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: Build fingerprint: 'samsung/m0xx/m0:4.3/JSS15J/I9300XXUGNB4:user/release-keys'
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: Revision: '12'
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: pid: 11432, tid: 11432, name: df >>> df <<<
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: signal 13 (SIGPIPE), code -6 (SI_TKILL), fault addr
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: processName:df
07-23 11:05:56.460 5091 5177 D CrashAnrDetector: broadcastEvent : null SYSTEM_TOMBSTONE
07-23 11:05:56.460 5091 5243 I BootReceiver: Notify a SYSTEM_TOMBSTONE FilePath:tombstone_00
07-23 11:05:56.495 5091 5178 D KeyguardHostView: Show right-most page 0
07-23 11:05:56.500 5091 5178 D LockPatternUtils: isPcwEnable = 10
07-23 11:05:56.510 5091 5178 I KeyguardBackgroundView: *** KeyguardEffectView getInstance ***
07-23 11:05:56.515 5091 5178 D KeyguardHostView: showSecurityScreen(PIN)
07-23 11:05:56.515 5091 5178 D KeyguardHostView: getSecurityView(Invalid)
07-23 11:05:56.515 5091 5178 D KeyguardHostView: getSecurityView(PIN)
07-23 11:05:56.720 11286 11286 I dumpstate: done
07-23 11:05:56.740 8927 8927 D KeyguardClockWidgetProvider: onReceive action=android.appwidget.action.APPWIDGET_UPDATE
07-23 11:05:56.775 5091 5333 I ActivityManager: Notify an ApplicationCrash
07-23 11:05:56.800 5091 5333 I Process : Sending signal. PID: 5091 SIG: 9
Click to expand...
Click to collapse
And then all the services start crashing one by one.
These are my 2 cents for your problem.
---------- Post added at 11:46 ---------- Previous post was at 11:40 ----------
And one more worrying thing:
07-23 11:05:50.411 11347 11347 F libc : Fatal signal 13 (SIGPIPE) at 0x00002c53 (code=0), thread 11347 (ip)
Click to expand...
Click to collapse
07-23 11:05:50.461 1940 1940 I DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-23 11:05:50.461 1940 1940 I DEBUG : Build fingerprint: 'samsung/m0xx/m0:4.3/JSS15J/I9300XXUGNB4:user/release-keys'
07-23 11:05:50.461 1940 1940 I DEBUG : Revision: '12'
07-23 11:05:50.461 1940 1940 I DEBUG : pid: 11347, tid: 11347, name: ip >>> ip <<<
07-23 11:05:50.461 1940 1940 I DEBUG : signal 13 (SIGPIPE), code -6 (SI_TKILL), fault addr --------
Click to expand...
Click to collapse
Something is definitely wrong either with the ROM or the device. But it doesn't look like a device fault.
07-23 11:05:49.851 1940 1940 I DEBUG : #00 pc 0001b29c /system/lib/libc.so (write+12)
07-23 11:05:49.851 1940 1940 I DEBUG : #01 pc 000022cb /system/lib/liblog.so (android_log_printLogLine+50)
07-23 11:05:49.851 1940 1940 I DEBUG : #02 pc 0000105d /system/bin/logcat
07-23 11:05:49.851 1940 1940 I DEBUG : #03 pc 00001215 /system/bin/logcat
07-23 11:05:49.851 1940 1940 I DEBUG : #04 pc 00001a11 /system/bin/logcat
07-23 11:05:49.851 1940 1940 I DEBUG : #05 pc 0000dc4f /system/lib/libc.so (__libc_init+50)
07-23 11:05:49.851 1940 1940 I DEBUG : #06 pc 00000e50 /system/bin/logcat
Click to expand...
Click to collapse
Something is definitely wrong with libc.so because it appears continuously in the logcat. Maybe that's the problem. Check out the attached screenshots.
You certainly are the B0ss!
My heart was telling me the device was faulty, so I think I was reluctant to waste any time on installing ROM's etc, especially as I've never done it before.
You gave me hope that it could be fixed.
* Backed up with CWM
* Installed CM11.2 and GAPPS.
* (Something) reinstalled all my apps automatically - happy days.
Running for 12 hours, it's very responsive, and I've had no reboots yet.
Don't want to count my chickens yet....... but fricken awesome!!!
Honestly my life has been so much better.
drooble said:
Honestly my life has been so much better.
Click to expand...
Click to collapse
Glad to have helped. Logcats give you so much detail if you know what to search for. Cheers and keep running the ol' girl. It's still good even 4 years after it was considered top.

Angry Birds (Seasons/Rio/Space) crashes

I have recently come back to playing Angry Birds Seasons/Rio/Space on my Nexus 9. Unfortunately I get random crashes (FCs) in any of these games. It doesn't happen on my Nexus 5X but I prefer the bigger tablet to play on.
I have only a few apps installed and checked tha RAM usage: there is enough free RAM available. The crashed happen even a few minutes after a fresh reboot.
It seems to be a problem with the GPU. Here is an excerpt of the crash log:
Code:
--------- beginning of crash
05-31 18:50:18.056 5509 2438 F google-breakpad: Microdump skipped (uninteresting)
05-31 18:50:18.113 2383 2438 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x10400000 in tid 2438 (GraphicsThread)
05-31 18:50:18.120 183 183 W : debuggerd: handling request: pid=2383 uid=10099 gid=10099 tid=2438
05-31 18:50:18.229 5510 5510 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-31 18:50:18.229 5510 5510 F DEBUG : Build fingerprint: 'google/volantis/flounder:7.1.1/N4F27B/3853226:user/release-keys'
05-31 18:50:18.229 5510 5510 F DEBUG : Revision: '0'
05-31 18:50:18.229 5510 5510 F DEBUG : ABI: 'arm'
05-31 18:50:18.229 5510 5510 F DEBUG : pid: 2383, tid: 2438, name: GraphicsThread >>> com.rovio.angrybirdsspace.ads <<<
05-31 18:50:18.230 5510 5510 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10400000
05-31 18:50:18.230 5510 5510 F DEBUG : r0 10400000 r1 00000000 r2 103fff80 r3 10400000
05-31 18:50:18.230 5510 5510 F DEBUG : r4 ce980000 r5 00000000 r6 e28ea100 r7 eb74f008
05-31 18:50:18.230 5510 5510 F DEBUG : r8 00000000 r9 ce93c720 sl a5238fe8 fp ce911000
05-31 18:50:18.230 5510 5510 F DEBUG : ip 00000000 sp e8704508 lr dc752161 pc eb6dd9c4 cpsr 280b0010
05-31 18:50:18.266 5510 5510 F DEBUG :
05-31 18:50:18.266 5510 5510 F DEBUG : backtrace:
05-31 18:50:18.266 5510 5510 F DEBUG : #00 pc 000179c4 /system/lib/libc.so (memset+120)
05-31 18:50:18.266 5510 5510 F DEBUG : #01 pc 0072a15d /vendor/lib/libglcore.so
05-31 18:50:18.266 5510 5510 F DEBUG : #02 pc 0072b027 /vendor/lib/libglcore.so
05-31 18:50:18.266 5510 5510 F DEBUG : #03 pc 0072ba5d /vendor/lib/libglcore.so
05-31 18:50:18.266 5510 5510 F DEBUG : #04 pc 001d86d8 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #05 pc 00443a58 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #06 pc 00443bc8 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #07 pc 001d77a0 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #08 pc 0019dcb8 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #09 pc 00198104 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #10 pc 00195658 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #11 pc 0060a658 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #12 pc 0061b3b0 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #13 pc 0060acd4 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #14 pc 0060b040 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #15 pc 00604274 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #16 pc 004a615c /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #17 pc 0008e544 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #18 pc 0006911c /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so
05-31 18:50:18.266 5510 5510 F DEBUG : #19 pc 000feb58 /data/app/com.rovio.angrybirdsspace.ads-1/lib/arm/libAngryBirdsSpace.so (Java_com_rovio_fusion_NativeApplication_nativeUpdate+268)
05-31 18:50:18.266 5510 5510 F DEBUG : #20 pc 00903979 /data/app/com.rovio.angrybirdsspace.ads-1/oat/arm/base.odex (offset 0x85e000)
Any ideas if this is a hardware or software problem?
No FC here :good:
Maybe a software​ problem. Try a factory reset
Or wiping dalvik cache
When those two options fail then you can worry
I am on stock ROM and have no alternate recovery installed, so I cannot wipe the dalvik cache.

Pixel XL run Android O: Core dump because of ATFWD-daemon can't find out the so

Here's part of the log info:
02:35:55.549 6528 6528 F DEBUG : ABI: 'arm64'
02:35:55.549 6528 6528 F DEBUG : pid: 6525, tid: 6525, name: ATFWD-daemon >>> /vendor/bin/ATFWD-daemon <<<
02:35:55.549 6528 6528 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
02:35:55.552 6528 6528 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/vendor/bin/ATFWD-daemon": library "[email protected]" not found'
02:35:55.553 6528 6528 F DEBUG : x0 0000000000000000 x1 000000000000197d x2 0000000000000006 x3 0000000000000008
02:35:55.553 6528 6528 F DEBUG : x4 0080000000808080 x5 0080000000808080 x6 0080000000808080 x7 0000000000000010
02:35:55.553 6528 6528 F DEBUG : x8 0000000000000083 x9 b604bf4045c4800d x10 0000000000000000 x11 0000000000000001
02:35:55.553 6528 6528 F DEBUG : x12 ffffffffffffffff x13 0000000000000001 x14 0000000000000000 x15 001c6810b7c5cc82
02:35:55.553 6528 6528 F DEBUG : x16 0000000000000016 x17 0834cff49920c743 x18 0000007e51a2c010 x19 000000000000197d
02:35:55.553 6528 6528 F DEBUG : x20 000000000000197d x21 0000005ad7e2af61 x22 0000007fdc4a0078 x23 0000005ad7e2fda0
02:35:55.553 6528 6528 F DEBUG : x24 0000007e51baa280 x25 0000007e51bab800 x26 0000007e51bab860 x27 0000007fdc4a1070
02:35:55.553 6528 6528 F DEBUG : x28 0000007e51bab000 x29 0000007fdc49fc40 x30 0000007e51b529ec
02:35:55.553 6528 6528 F DEBUG : sp 0000007fdc49fc00 pc 0000007e51b61e7c pstate 0000000060000000
02:35:55.560 6528 6528 F DEBUG :
02:35:55.560 6528 6528 F DEBUG : backtrace:
02:35:55.560 6528 6528 F DEBUG : #00 pc 000000000009fe7c /system/bin/linker64 (__dl_tgkill+8)
02:35:55.560 6528 6528 F DEBUG : #01 pc 00000000000909e8 /system/bin/linker64 (__dl_abort+88)
02:35:55.560 6528 6528 F DEBUG : #02 pc 00000000000268f4 /system/bin/linker64 (__dl___libc_fatal+116)
02:35:55.566 6528 6528 F DEBUG : #03 pc 000000000001b458 /system/bin/linker64 (__dl___linker_init+3368)
02:35:55.567 6528 6528 F DEBUG : #04 pc 000000000002166c /system/bin/linker64 (_start+4)
Does anyone has the same problem? It seems can't find the [email protected].
This happens repeatedly... very boring...
The same problem as u.

Some APPS crashing with MTK6580 Port

Dear all,
i ported nougat to our MTK6580 Device "Cubot Note S". It works fine all, just have some issues with few apps.
I use lineage OS 14.1
They crashing and i don't know why. For Example Google Play Store crashing if i swipe to "Libary" and Opera hangs heavy into crash.
i created a logcat file with the both problems. can someone give me a hint whats the problem could be?
tell me if you need some more information
Has someone an idea how to fix this issue? i analyzed the log now and the fatal error is the main problem:
Fatal signal 6
01-17 21:51:20.102 3919 5155 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 5155 (RenderThread)
01-17 21:51:20.188 5194 5194 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-17 21:51:20.189 5194 5194 F DEBUG : LineageOS Version: '14.1-20180107-UNOFFICIAL-Note_S'
01-17 21:51:20.189 5194 5194 F DEBUG : Build fingerprint: 'Homtom/lineage_HT16/HT16:7.1.2/NJH47F/a9ae3a28c1:userdebug/test-keys'
01-17 21:51:20.189 5194 5194 F DEBUG : Revision: '0'
01-17 21:51:20.189 5194 5194 F DEBUG : ABI: 'arm'
01-17 21:51:20.189 5194 5194 F DEBUG : pid: 3919, tid: 5155, name: RenderThread >>> com.android.vending <<<
01-17 21:51:20.189 5194 5194 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-17 21:51:20.194 5194 5194 F DEBUG : Abort message: 'GL errors! frameworks/base/libs/hwui/renderthread/CanvasContext.cpp:550'
01-17 21:51:20.194 5194 5194 F DEBUG : r0 00000000 r1 00001423 r2 00000006 r3 00000008
01-17 21:51:20.194 5194 5194 F DEBUG : r4 9737f978 r5 00000006 r6 9737f920 r7 0000010c
01-17 21:51:20.194 5194 5194 F DEBUG : r8 9bbb4e40 r9 9737f83c sl 9b2c2c48 fp 00000000
01-17 21:51:20.194 5194 5194 F DEBUG : ip 0000000b sp 9737eee8 lr b5cdedd7 pc b5ce1634 cpsr 200e0010
01-17 21:51:20.211 5194 5194 F DEBUG :
01-17 21:51:20.211 5194 5194 F DEBUG : backtrace:
01-17 21:51:20.211 5194 5194 F DEBUG : #00 pc 0004a634 /system/lib/libc.so (tgkill+12)
01-17 21:51:20.211 5194 5194 F DEBUG : #01 pc 00047dd3 /system/lib/libc.so (pthread_kill+34)
01-17 21:51:20.212 5194 5194 F DEBUG : #02 pc 0001d635 /system/lib/libc.so (raise+10)
01-17 21:51:20.212 5194 5194 F DEBUG : #03 pc 00019181 /system/lib/libc.so (__libc_android_abort+34)
01-17 21:51:20.212 5194 5194 F DEBUG : #04 pc 00017138 /system/lib/libc.so (abort+4)
01-17 21:51:20.212 5194 5194 F DEBUG : #05 pc 0000c1b1 /system/lib/libcutils.so (__android_log_assert+112)
01-17 21:51:20.212 5194 5194 F DEBUG : #06 pc 00024187 /system/lib/libhwui.so
01-17 21:51:20.212 5194 5194 F DEBUG : #07 pc 00025b83 /system/lib/libhwui.so
01-17 21:51:20.212 5194 5194 F DEBUG : #08 pc 000291b1 /system/lib/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+172)
01-17 21:51:20.212 5194 5194 F DEBUG : #09 pc 0000e3fd /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+140)
01-17 21:51:20.212 5194 5194 F DEBUG : #10 pc 00066d5d /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+80)
01-17 21:51:20.212 5194 5194 F DEBUG : #11 pc 000478a3 /system/lib/libc.so (_ZL15__pthread_startPv+22)
01-17 21:51:20.212 5194 5194 F DEBUG : #12 pc 00019bcd /system/lib/libc.so (__start_thread+6)
Click to expand...
Click to collapse
it's a gpu problem but i dont know which file i have to fix. maybe the system\lib\egl or the system\lib\libhwui?
The device is working with the mm kernel: 3.18.19 and the egl file is "libGLES_mali" (1.151mb) from Stock ROM (Android 6)
"Workarround "is to set the smallest width to 720 and the apps working without problems..

app on android 6.0.1 does not work, but on android 8.0 if

Hello everyone, I made a small app with packed flask for android with python-for-android. The funny thing is that the app compiled for armeabi-v7a, in android 8.0 works perfectly, but in android 6.0.1 it does not work (the phone with android 8.0 is an arm-64 and the phone with 6.0.1 is an armeabi-v7a) . I have connected by ADB and I have extracted the logcat. As I have been able to interpret there is a process that gives error, but I do not finish understanding why it fails.
Code:
cat logcat | grep 765
04-25 22:33:36.733 765 765 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-25 22:33:36.733 765 765 F DEBUG : Build fingerprint: 'samsung/trltexx/trlte:6.0.1/MMB29M/N910FXXU1DQL2:user/release-keys'
04-25 22:33:36.733 765 765 F DEBUG : Revision: '0'
04-25 22:33:36.733 765 765 F DEBUG : ABI: 'arm'
04-25 22:33:36.733 765 765 F DEBUG : pid: 23699, tid: 23978, name: PythonThread >>> org.sanelectric.sanelectric <<<
04-25 22:33:36.733 765 765 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
04-25 22:33:36.753 765 765 F DEBUG : r0 00000000 r1 00005daa r2 00000006 r3 9cfc2978
04-25 22:33:36.753 765 765 F DEBUG : r4 9cfc2980 r5 9cfc2930 r6 00000000 r7 0000010c
04-25 22:33:36.753 765 765 F DEBUG : r8 00000002 r9 9def988a sl 9cfc2148 fp 9cfc1e78
04-25 22:33:36.753 765 765 F DEBUG : ip 00000006 sp 9cfc1e00 lr b6d1dc11 pc b6d20000 cpsr 400f0010
04-25 22:33:36.763 765 765 F DEBUG :
04-25 22:33:36.763 765 765 F DEBUG : backtrace:
04-25 22:33:36.763 765 765 F DEBUG : #00 pc 00042000 /system/lib/libc.so (tgkill+12)
04-25 22:33:36.763 765 765 F DEBUG : #01 pc 0003fc0d /system/lib/libc.so (pthread_kill+32)
04-25 22:33:36.763 765 765 F DEBUG : #02 pc 0001c397 /system/lib/libc.so (raise+10)
04-25 22:33:36.763 765 765 F DEBUG : #03 pc 00019615 /system/lib/libc.so (__libc_android_abort+34)
04-25 22:33:36.763 765 765 F DEBUG : #04 pc 00017568 /system/lib/libc.so (abort+4)
04-25 22:33:36.763 765 765 F DEBUG : #05 pc 001c7db8 /data/app/org.sanelectric.sanelectric-1/lib/arm/libpython3.7m.so (offset 0x83000)
04-25 22:33:37.873 765 765 F DEBUG :
04-25 22:33:37.873 765 765 F DEBUG : Tombstone written to: /data/tombstones/tombstone_06
04-25 22:33:37.873 765 765 E DEBUG : AM write failed: Broken pipe
04-25 22:33:37.873 765 765 E : ro.product_ship = true
04-25 22:33:37.873 765 765 E : ro.debug_level = 0x4f4c
04-25 22:33:37.873 765 765 E : sys.mobilecare.preload = false
Code:
cat logcat | grep PythonThread
04-25 22:33:36.663 23699 23978 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 23978 (PythonThread)
04-25 22:33:36.733 765 765 F DEBUG : pid: 23699, tid: 23978, name: PythonThread >>> org.sanelectric.sanelectric <<<
04-25 22:33:37.883 3953 3953 E audit : type=1701 msg=audit(1556224417.873:2372): auid=4294967295 uid=10248 gid=10248 ses=4294967295 subj=u:r:untrusted_app:s0:c512,c768 pid=23978 comm="PythonThread" reason="memory violation" sig=6
Thanks in advance

Categories

Resources