Database Develop

XPosed didn't started

Please help ! Recently i was using xposed properly with my gnex with resurrectionremix. But suddenly xposed can't started. Even after the new update still do nothing. Here's the log.
03-09 15:17:25.699 I/Xposed ( 170): -----------------
03-09 15:17:25.699 I/Xposed ( 170): Starting Xposed binary version 61, compiled for SDK 21
03-09 15:17:25.699 I/Xposed ( 170): Device: Galaxy Nexus (samsung), Android version 5.0.2 (SDK 21)
03-09 15:17:25.699 I/Xposed ( 170): ROM: cm_maguro-userdebug 5.0.2 LRX22G 86141ace61 test-keys
03-09 15:17:25.699 I/Xposed ( 170): Build fingerprint: google/yakju/maguro:4.3/JWR66Y/776638:user/release-keys
03-09 15:17:25.699 I/Xposed ( 170): Platform: armeabi-v7a, 32-bit binary, system server: yes
03-09 15:17:25.699 I/Xposed ( 170): SELinux enabled: yes, enforcing: no
03-09 15:17:28.153 E/Xposed ( 170): Found /data/data/de.robv.android.xposed.installer/conf/disabled, not loading Xposed
03-09 15:17:28.434 I/Xposed ( 170): Forcing image recompilation because /data/dalvik-cache/arm/[email protected]@boot.art is not compiled for the current Xposed version
03-09 15:31:50.620 F/libc ( 1895): Fatal signal 6 (SIGABRT), code -6 in tid 1895 (main)
03-09 15:31:50.739 I/DEBUG ( 162): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-09 15:31:50.739 I/DEBUG ( 162): Build fingerprint: 'google/yakju/maguro:4.3/JWR66Y/776638:user/release-keys'
03-09 15:31:50.739 I/DEBUG ( 162): Revision: '9'
03-09 15:31:50.739 I/DEBUG ( 162): ABI: 'arm'
03-09 15:31:50.739 I/DEBUG ( 162): pid: 1895, tid: 1895, name: main >>> /system/bin/dex2oat <<<
03-09 15:31:50.739 I/DEBUG ( 162): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-09 15:31:50.822 I/DEBUG ( 162): Abort message: 'art/compiler/dex/ssa_transformation.cc:444] Incompatible set properties'
03-09 15:31:50.822 I/DEBUG ( 162): r0 00000000 r1 00000767 r2 00000006 r3 00000000
03-09 15:31:50.822 I/DEBUG ( 162): r4 4007110c r5 00000006 r6 00000002 r7 0000010c
03-09 15:31:50.822 I/DEBUG ( 162): r8 0000001b r9 41e22d60 sl 40020078 fp 43695710
03-09 15:31:50.822 I/DEBUG ( 162): ip 00000767 sp beef0aa8 lr 40085685 pc 400ab438 cpsr 600f0010
03-09 15:31:50.822 I/DEBUG ( 162):
03-09 15:31:50.822 I/DEBUG ( 162): backtrace:
03-09 15:31:50.823 I/DEBUG ( 162): #00 pc 00039438 /system/lib/libc.so (tgkill+12)
03-09 15:31:50.823 I/DEBUG ( 162): #01 pc 00013681 /system/lib/libc.so (pthread_kill+52)
03-09 15:31:50.823 I/DEBUG ( 162): #02 pc 000143df /system/lib/libc.so (raise+10)
03-09 15:31:50.823 I/DEBUG ( 162): #03 pc 00010ad5 /system/lib/libc.so (__libc_android_abort+36)
03-09 15:31:50.823 I/DEBUG ( 162): #04 pc 0000f2a4 /system/lib/libc.so (abort+4)
03-09 15:31:50.823 I/DEBUG ( 162): #05 pc 002143ed /system/lib/libart.so (art::Runtime::Abort()+160)
03-09 15:31:50.823 I/DEBUG ( 162): #06 pc 000a7cdf /system/lib/libart.so (art::LogMessage::~LogMessage()+1066)
03-09 15:31:50.823 I/DEBUG ( 162): #07 pc 00139fdf /system/lib/libart-compiler.so (art::MIRGraph::ComputeSuccLineIn(art::ArenaBitVector*, art::ArenaBitVector const*, art::ArenaBitVector const*)+66)
03-09 15:31:50.823 I/DEBUG ( 162): #08 pc 0013a09b /system/lib/libart-compiler.so (art::MIRGraph::ComputeBlockLiveIns(art::BasicBlock*)+98)
03-09 15:31:50.823 I/DEBUG ( 162): #09 pc 0013a28b /system/lib/libart-compiler.so (art::MIRGraph::InsertPhiNodes()+186)
03-09 15:31:50.823 I/DEBUG ( 162): #10 pc 0012accf /system/lib/libart-compiler.so
03-09 15:31:50.823 I/DEBUG ( 162): #11 pc 00133239 /system/lib/libart-compiler.so
03-09 15:31:50.823 I/DEBUG ( 162): #12 pc 0012ea49 /system/lib/libart-compiler.so (art::MIRGraph::CalculateBasicBlockInformation()+208)
03-09 15:31:50.823 I/DEBUG ( 162): #13 pc 0012b2b1 /system/lib/libart-compiler.so
03-09 15:31:50.823 I/DEBUG ( 162): #14 pc 0012cd6f /system/lib/libart-compiler.so
03-09 15:31:50.824 I/DEBUG ( 162): #15 pc 0012d247 /system/lib/libart-compiler.so (ArtQuickCompileMethod+38)
03-09 15:31:50.824 I/DEBUG ( 162): #16 pc 001435bb /system/lib/libart-compiler.so (art::CompilerDriver::CompileMethod(art:exFile::CodeItem const*, unsigned int, art::InvokeType, unsigned short, unsigned int, _jobject*, art:exFile const&, art:exToDexCompilationLevel)+942)
03-09 15:31:50.824 I/DEBUG ( 162): #17 pc 00143d5b /system/lib/libart-compiler.so (art::CompilerDriver::CompileClass(art:[emoji14]arallelCompilationManager const*, unsigned int)+1458)
03-09 15:31:50.824 I/DEBUG ( 162): #18 pc 0013aac1 /system/lib/libart-compiler.so
03-09 15:31:50.824 I/DEBUG ( 162): #19 pc 0022d9b1 /system/lib/libart.so (art::ThreadPool::Wait(art::Thread*, bool, bool)+172)
03-09 15:31:50.824 I/DEBUG ( 162): #20 pc 0013da47 /system/lib/libart-compiler.so
03-09 15:31:50.824 I/DEBUG ( 162): #21 pc 0013e2bb /system/lib/libart-compiler.so (art::CompilerDriver::Compile(_jobject*, std::__1::vector<art:exFile const*, std::__1::allocator<art:exFile const*> > const&, art::ThreadPool*, art::TimingLogger*)+146)
03-09 15:31:50.824 I/DEBUG ( 162): #22 pc 00146a75 /system/lib/libart-compiler.so (art::CompilerDriver::CompileAll(_jobject*, std::__1::vector<art:exFile const*, std::__1::allocator<art:exFile const*> > const&, art::TimingLogger*)+64)
03-09 15:31:50.824 I/DEBUG ( 162): #23 pc 0000c7c9 /system/bin/dex2oat
03-09 15:31:50.824 I/DEBUG ( 162): #24 pc 0000ea3f /system/bin/dex2oat
03-09 15:31:50.824 I/DEBUG ( 162): #25 pc 0000f161 /system/lib/libc.so (__libc_init+44)
03-09 15:31:50.824 I/DEBUG ( 162): #26 pc 00006844 /system/bin/dex2oat
03-09 15:31:51.214 I/DEBUG ( 162):
03-09 15:31:51.214 I/DEBUG ( 162): Tombstone written to: /data/tombstones/tombstone_02
Hope that's help !

Understanding random reboots via logcat

Hello there,
I am, like others, experiencing random reboots, at the tune of about 5 times per day.
Since this happened before and after software upgrades (even major ones such as OOS 4), I initially thought it was a hardware issue, but the fact that the reboot is only a soft one (no need to re-enter the decryption password or the SIM lock PINs), makes me rather think that the issue is in the software.
I have thus looked into the logs and found something perhaps interesting that I need help understanding. This is in fact NOT meant to be the start of another generic thread about reboots on the OP3T...
All my crashes can be found in the crash ring buffer with logcat -bcrash (dump to file with logcat -bcrash -d -f filename.log), and they all look like this:
Code:
01-29 02:34:02.764 5014 5018 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 5018 (Binder:5014_2)
01-29 02:34:02.824 27337 27337 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-29 02:34:02.825 27337 27337 F DEBUG : Build fingerprint: 'OnePlus/OnePlus3/OnePlus3T:7.0/NRD90M/12311021:user/release-keys'
01-29 02:34:02.825 27337 27337 F DEBUG : Revision: '0'
01-29 02:34:02.826 27337 27337 F DEBUG : ABI: 'arm64'
01-29 02:34:02.826 27337 27337 F DEBUG : pid: 5014, tid: 5018, name: Binder:5014_2 >>> /system/bin/surfaceflinger <<<
01-29 02:34:02.826 27337 27337 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-29 02:34:02.826 27337 27337 F DEBUG : x0 0000000000000000 x1 000000000000139a x2 0000000000000006 x3 0000000000000008
01-29 02:34:02.826 27337 27337 F DEBUG : x4 0000007fac47aac5 x5 0000007fa9ffeb40 x6 0000000000000000 x7 0000007faba0f800
01-29 02:34:02.826 27337 27337 F DEBUG : x8 0000000000000083 x9 ffffffffffffffdf x10 0000000000000000 x11 0000000000000001
01-29 02:34:02.827 27337 27337 F DEBUG : x12 ffffffffffffffff x13 000000008000002f x14 0000007fac28a0e8 x15 0000007fac289d8c
01-29 02:34:02.827 27337 27337 F DEBUG : x16 0000007fac2a5ed0 x17 0000007fac24f8c0 x18 00000000000000bc x19 0000007fa9fff4f8
01-29 02:34:02.827 27337 27337 F DEBUG : x20 0000000000000006 x21 0000007fa9fff450 x22 0000000000000016 x23 0000000000000000
01-29 02:34:02.827 27337 27337 F DEBUG : x24 0000000000000000 x25 bd40e3ea6c4cd196 x26 0000000000000000 x27 0000000000000000
01-29 02:34:02.827 27337 27337 F DEBUG : x28 0000000000000000 x29 0000007fa9ffec70 x30 0000007fac24cd50
01-29 02:34:02.827 27337 27337 F DEBUG : sp 0000007fa9ffec50 pc 0000007fac24f8c8 pstate 0000000060000000
01-29 02:34:02.855 27337 27337 F DEBUG :
01-29 02:34:02.855 27337 27337 F DEBUG : backtrace:
01-29 02:34:02.855 27337 27337 F DEBUG : #00 pc 000000000006b8c8 /system/lib64/libc.so (tgkill+8)
01-29 02:34:02.855 27337 27337 F DEBUG : #01 pc 0000000000068d4c /system/lib64/libc.so (pthread_kill+64)
01-29 02:34:02.855 27337 27337 F DEBUG : #02 pc 00000000000242b8 /system/lib64/libc.so (raise+24)
01-29 02:34:02.855 27337 27337 F DEBUG : #03 pc 000000000001ccd4 /system/lib64/libc.so (abort+52)
01-29 02:34:02.855 27337 27337 F DEBUG : #04 pc 000000000000d220 /system/lib64/libui.so (_ZNK7android6Region4dumpERNS_7String8EPKcj+140)
01-29 02:34:02.855 27337 27337 F DEBUG : #05 pc 0000000000035134 /system/lib64/libsurfaceflinger.so
01-29 02:34:02.855 27337 27337 F DEBUG : #06 pc 000000000004f588 /system/lib64/libsurfaceflinger.so
01-29 02:34:02.855 27337 27337 F DEBUG : #07 pc 000000000004e8bc /system/lib64/libsurfaceflinger.so
01-29 02:34:02.855 27337 27337 F DEBUG : #08 pc 000000000004fa3c /system/lib64/libsurfaceflinger.so
01-29 02:34:02.855 27337 27337 F DEBUG : #09 pc 000000000004a310 /system/lib64/libbinder.so (_ZN7android7BBinder10onTransactEjRKNS_6ParcelEPS1_j+256)
01-29 02:34:02.855 27337 27337 F DEBUG : #10 pc 0000000000050160 /system/lib64/libsurfaceflinger.so
01-29 02:34:02.855 27337 27337 F DEBUG : #11 pc 0000000000049e44 /system/lib64/libbinder.so (_ZN7android7BBinder8transactEjRKNS_6ParcelEPS1_j+132)
01-29 02:34:02.855 27337 27337 F DEBUG : #12 pc 0000000000055c40 /system/lib64/libbinder.so (_ZN7android14IPCThreadState14executeCommandEi+980)
01-29 02:34:02.855 27337 27337 F DEBUG : #13 pc 00000000000557b0 /system/lib64/libbinder.so (_ZN7android14IPCThreadState20getAndExecuteCommandEv+156)
01-29 02:34:02.855 27337 27337 F DEBUG : #14 pc 0000000000055e58 /system/lib64/libbinder.so (_ZN7android14IPCThreadState14joinThreadPoolEb+72)
01-29 02:34:02.855 27337 27337 F DEBUG : #15 pc 0000000000072d70 /system/lib64/libbinder.so
01-29 02:34:02.855 27337 27337 F DEBUG : #16 pc 0000000000012430 /system/lib64/libutils.so (_ZN7android6Thread11_threadLoopEPv+272)
01-29 02:34:02.855 27337 27337 F DEBUG : #17 pc 0000000000068554 /system/lib64/libc.so (_ZL15__pthread_startPv+196)
01-29 02:34:02.855 27337 27337 F DEBUG : #18 pc 000000000001df18 /system/lib64/libc.so (__start_thread+16)
01-29 02:34:02.897 27338 27338 F libc : CANNOT LINK EXECUTABLE "/system/bin/sh": can't enable GNU RELRO protection for "": Permission denied
However, I don't quite understand what's going on here. Who's linking to what? And where is RELRO being enabled? sh already has it enabled:
Code:
$ file sh
sh: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /system/bin/linker64, BuildID[md5/uuid]=31393afb600e5f7fb8fd5699b343bfbf, stripped
$ ./checksec.sh --file sh
RELRO STACK CANARY NX PIE RPATH RUNPATH FILE
Full RELRO Canary found NX enabled PIE enabled No RPATH No RUNPATH sh
If anybody has any idea I would be really glad! The reboots are kinda driving me crazy and I'd rather not have to go through the pain of a replacement (which might not even help).
My phone is stock OOS 4.0.2 + TWRP + SuperSU.

8.1 bluetooth issue

Tried Nitrogen and Beltz, and experienced on both.
In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.
20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16
20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)
20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone
20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210
20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)
20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'
20:03:10.590 F/DEBUG (15485): Revision: '0'
20:03:10.590 F/DEBUG (15485): ABI: 'arm'
20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<
20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'
20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008
20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c
20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0
020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030
20:03:10.634 F/DEBUG (15485):
20:03:10.634 F/DEBUG (15485): backtrace:
20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)
20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)
20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)
20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)
20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/[email protected] (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)
20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)
Sometimes different packet type (i.e. 104).
Any help appreciated...

xduser1 said:
Tried Nitrogen and Beltz, and experienced on both.
In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.
20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16
20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)
20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone
20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210
20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)
20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'
20:03:10.590 F/DEBUG (15485): Revision: '0'
20:03:10.590 F/DEBUG (15485): ABI: 'arm'
20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<
20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'
20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008
20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c
20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0
020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030
20:03:10.634 F/DEBUG (15485):
20:03:10.634 F/DEBUG (15485): backtrace:
20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)
20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)
20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)
20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)
20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/[email protected] (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)
20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)
Sometimes different packet type (i.e. 104).
Any help appreciated...
Click to expand...
Click to collapse
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.

xduser1 said:
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.
Click to expand...
Click to collapse
I have the same issue with every 8.1 build I have tried. I think LOS is less problematic and I have fewer disconnects reconnects. Glad I'm not the only one with the issue. I was going to flash back to stock to see if the issue persists, but I'm pretty sure Bluetooth is incomplete for the N6 and 8.1. Every ROM i have tried also misreports Bluetooth battery drain.

I can say, I use a Bluetooth headset and external gps and connect to my ODBII port all simultaneously without any disconnects. I'm using ABC for shamu and it's been rock solid. I also do not get misreported numbers.
If that's one of the rooms you've tried, and you've clean flashed, then think about trying inn safe mode. Maybe some app is interfering. Safe mode will reset your settings and desktop. You probably want to take a nandroid first.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Several data points:
On 8.1, I only experience this issue with this one car, all other bluetooth devices and cars that I've tried worked perfect.
I do not experience this issue with this car on 7.1.2..
All ROMs were clean flashed.
Also tried friend's Pixel 2 with stock 8.1, and it worked with this car without any issues.

Not opening the camera

My camera is not working. How can I fix the problem.

Marvelouswimpy said:
My camera is not working. How can I fix the problem.
Click to expand...
Click to collapse
Try clear data camera app.

Hi, I have the same problem. When I try to open camera app, it closes instantly without any message. I tried to stop it, clear data, reboot phone - no effect. App version - 8.0.0.301, VTR-L29 8.0.0.365 (C432).
Camera works in non native apps - like Viber (so it is not physically damaged).
Any ideas?

Any ideas?
Below - extract from adb logcat catching the attempt of opening camera app:
Code:
05-16 09:20:32.765 11504 11504 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 11504 (m.huawei.camera)
05-16 09:20:32.791 11530 11530 I crash_dump32: obtaining output fd from tombstoned
05-16 09:20:32.791 801 801 I /system/bin/tombstoned: received crash request for pid 11504
05-16 09:20:32.795 11530 11530 I crash_dump32: performing dump of process 11504 (target tid = 11504)
05-16 09:20:32.796 11530 11530 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-16 09:20:32.796 11530 11530 F DEBUG : Build fingerprint: 'HUAWEI/VTR-L29/HWVTR:8.0.0/HUAWEIVTR-L29/365(C432):user/release-keys'
05-16 09:20:32.796 11530 11530 F DEBUG : Revision: '0'
05-16 09:20:32.796 11530 11530 F DEBUG : ABI: 'arm'
05-16 09:20:32.796 11530 11530 F DEBUG : pid: 11504, tid: 11504, name: m.huawei.camera >>> com.huawei.camera <<<
05-16 09:20:32.796 11530 11530 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
05-16 09:20:32.799 11530 11530 F DEBUG : Abort message: 'art_method.cc:535] Check failed: found_virtual Didn't find oat method index for virtual method: java.lang.String[] android.icu.impl.ICUResourceBundle.getStringArray()'
05-16 09:20:32.799 11530 11530 F DEBUG : r0 00000000 r1 00002cf0 r2 00000006 r3 00000008
05-16 09:20:32.799 11530 11530 F DEBUG : r4 00002cf0 r5 00002cf0 r6 e8614a28 r7 0000010c
05-16 09:20:32.799 11530 11530 F DEBUG : r8 e8614af0 r9 7006c020 sl 6feccea0 fp e8614b5f
05-16 09:20:32.799 11530 11530 F DEBUG : ip 00000000 sp e8614a18 lr e54bc477 pc e54ed2f4 cpsr 200f0010
05-16 09:20:32.803 11530 11530 F DEBUG :
05-16 09:20:32.803 11530 11530 F DEBUG : backtrace:
05-16 09:20:32.803 11530 11530 F DEBUG : #00 pc 0004b2f4 /system/lib/libc.so (tgkill+12)
05-16 09:20:32.803 11530 11530 F DEBUG : #01 pc 0001a473 /system/lib/libc.so (abort+54)
05-16 09:20:32.803 11530 11530 F DEBUG : #02 pc 0033a8bb /system/lib/libart.so (_ZN3art7Runtime5AbortEPKc+370)
05-16 09:20:32.803 11530 11530 F DEBUG : #03 pc 0033aeb3 /system/lib/libart.so (_ZN3art7Runtime7AborterEPKc+10)
05-16 09:20:32.803 11530 11530 F DEBUG : #04 pc 003f3419 /system/lib/libart.so (_ZN7android4base10LogMessageD1Ev+456)
05-16 09:20:32.803 11530 11530 F DEBUG : #05 pc 000ad5ff /system/lib/libart.so (_ZN3artL16FindOatMethodForEPNS_9ArtMethodENS_11PointerSizeEPb+462)
05-16 09:20:32.803 11530 11530 F DEBUG : #06 pc 000ada43 /system/lib/libart.so (_ZN3art9ArtMethod23GetOatQuickMethodHeaderEj+154)
05-16 09:20:32.803 11530 11530 F DEBUG : #07 pc 001588dd /system/lib/libart.so (_ZN3art12FaultManager17IsInGeneratedCodeEP7siginfoPvb+696)
05-16 09:20:32.803 11530 11530 F DEBUG : #08 pc 00158445 /system/lib/libart.so (_ZN3art12FaultManager11HandleFaultEiP7siginfoPv+44)
05-16 09:20:32.803 11530 11530 F DEBUG : #09 pc 00002403 /system/bin/app_process32 (_ZN3art11SignalChain7HandlerEiP7siginfoPv+382)
05-16 09:20:32.803 11530 11530 F DEBUG : #10 pc 00018af4 /system/lib/libc.so
05-16 09:20:32.803 11530 11530 F DEBUG : #11 pc 002eedae /system/lib/libart.so (_ZNK3art15TypeLookupTable15IsStringsEqualsEPKcj+25)
05-16 09:20:32.803 11530 11530 F DEBUG : #12 pc 002eda95 /system/lib/libart.so (_ZN3art10OatDexFile12FindClassDefERKNS_7DexFileEPKcj+72)
05-16 09:20:32.803 11530 11530 F DEBUG : #13 pc 000ead55 /system/lib/libart.so (_ZN3art11ClassLinker29FindClassInBaseDexClassLoaderERNS_33ScopedObjectAccessAlreadyRunnableEPNS_6ThreadEPKcjNS_6HandleINS_6mirror11ClassLoaderEEEPNS_6ObjPtrINS8_5ClassEEE+808)
05-16 09:20:32.803 11530 11530 F DEBUG : #14 pc 000ebc6f /system/lib/libart.so (_ZN3art11ClassLinker9FindClassEPNS_6ThreadEPKcNS_6HandleINS_6mirror11ClassLoaderEEE+810)
05-16 09:20:32.803 11530 11530 F DEBUG : #15 pc 000dd301 /system/lib/libart.so (_ZN3art11ClassLinker11ResolveTypeERKNS_7DexFileENS_3dex9TypeIndexENS_6HandleINS_6mirror8DexCacheEEENS6_INS7_11ClassLoaderEEE+212)
05-16 09:20:32.803 11530 11530 F DEBUG : #16 pc 000ad319 /system/lib/libart.so (_ZN3art11ClassLinker11ResolveTypeENS_3dex9TypeIndexEPNS_9ArtMethodE+352)
05-16 09:20:32.803 11530 11530 F DEBUG : #17 pc 001f092d /system/lib/libart.so (_ZN3art22ResolveVerifyAndClinitENS_3dex9TypeIndexEPNS_9ArtMethodEPNS_6ThreadEbb+40)
05-16 09:20:32.803 11530 11530 F DEBUG : #18 pc 003b9adb /system/lib/libart.so (artInitializeTypeFromCode+38)
05-16 09:20:32.803 11530 11530 F DEBUG : #19 pc 003e0d8f /system/lib/libart.so (art_quick_initialize_type+30)
05-16 09:20:32.803 11530 11530 F DEBUG : #20 pc 0020830f /data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex (offset 0x164000)
05-16 09:20:32.809 769 1418 D DE N ABT: addOperating:478: Cache[ COMPONENT_CONTRAST ][ HIGH_BIT_AL_MODE ]| 1 / 1 | DE_FEATURE_SRE | 0 |0x100
05-16 09:20:32.809 769 1418 D DE N HWC: apply:62: set FEATURE_CONTRAST mAmbientLux:758
05-16 09:20:32.809 769 1418 D DE N HW : setEffect:71: FEATURE_CONTRAST mode:0x23 size:4
05-16 09:20:32.809 684 684 D DE H DE : setHardwareEffect:212: FEATURE_CONTRAST 0x23
05-16 09:20:32.809 684 684 I DE H DisplayEngineImpl: setContrast:606: Ambient light = 758
05-16 09:20:32.810 769 1418 D DE N HWC: apply:72: FEATURE_CONTRAST: start dimming <mode:0x100 | END:0x100> <frames:90>
05-16 09:20:32.826 769 1418 D DE N HW : setEffect:64: FEATURE_CONTRAST dimming mode:0x101 frame:(0/90) size:12
05-16 09:20:32.826 684 684 D DE H DE : setHardwareEffect:205: FEATURE_CONTRAST dimming:0/90 0x101
05-16 09:20:32.826 684 684 D DE H DisplayEngineImpl: handleContrastNormalMode:500: level:2, mode:0, threshold:500
05-16 09:20:32.826 684 684 D DE H DisplayEngineImpl: handleContrastNormalMode:520: set params.idosre : 1, idoLCE:0
05-16 09:20:32.826 684 684 D DE H DisplayEngineImpl: operateHiaceState:548: [effect] set hiace Enable in enable = 1
05-16 09:20:32.836 684 684 D DE H LT : start:41: Count=0
05-16 09:20:32.836 684 684 D DE H LT : start:44: wake up
05-16 09:20:32.836 684 27518 D DE H ACEThreadImpl: init:51: [ACE] step in
05-16 09:20:32.939 1152 1322 V WindowManager: Exit animation finished in Window{944eaf1 u0 com.teslacoilsw.launcher/com.teslacoilsw.launcher.NovaLauncher EXITING}: remove=false
05-16 09:20:32.945 1502 1502 D ImageWallpaper: onVisibilityChanged: mVisible, visible=true, false
05-16 09:20:32.945 1502 1502 D ImageWallpaper: Visibility changed to visible=false
05-16 09:20:32.961 769 5885 D DE N SR : setAmbientParam:919: DE_SCENE_ACTION_AMBIENT_CHANGE set mLux:753 mCt:7656
05-16 09:20:32.961 769 1415 D DE N HWC: onNotify:122: set FEATURE_CONTRAST mAmbientLux:753
05-16 09:20:32.961 769 1415 D DE N HW : setEffect:71: FEATURE_CONTRAST mode:0x23 size:4
05-16 09:20:32.961 684 684 D DE H DE : setHardwareEffect:212: FEATURE_CONTRAST 0x23
05-16 09:20:32.961 684 684 I DE H DisplayEngineImpl: setContrast:606: Ambient light = 753
05-16 09:20:33.166 801 801 E /system/bin/tombstoned: Tombstone written to: /data/tombstones//tombstone_00
05-16 09:20:33.167 1152 11531 W ActivityManager: Force finishing activity com.huawei.camera/com.huawei.camera
05-16 09:20:33.168 1152 1183 I BootReceiver: Copying /data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)
05-16 09:20:33.171 1152 1178 W ActivityManager: Skipping native crash dialog of ProcessRecord{2ca3532 11504:com.huawei.camera/u0a29}
05-16 09:20:33.172 1152 1183 W DropBoxManagerService: Dropping: SYSTEM_TOMBSTONE (10 > 0 bytes)
05-16 09:20:33.173 1152 11532 W DropBoxManagerService: Dropping: system_app_native_crash (3059 > 0 bytes)
05-16 09:20:33.193 1152 12170 I ActivityManager: Process com.huawei.camera (pid 11504) has died: vis +99TOP
05-16 09:20:33.193 515 515 I Zygote : Process 11504 exited due to signal (6)
05-16 09:20:33.194 1152 12170 D ActivityManager: cleanUpApplicationRecord app: ProcessRecord{2ca3532 11504:com.huawei.camera/u0a29}, app.bad: false, restarting: false, allowRestart: true

Just to let you know - I did a factory reset and it helped... It cost me couple of hours spent on backups and restoring but everything works now.

Android system keeps stopping

Hi there,
I've just received the mi pad 4 plus and I'm generally impressed, however I'm experiencing crashes when I click on links from my email, both in the mail app and outlook app. Also when I try and share a page from chrome. (It says Android system has stopped or keeps stopping and sometimes power app has stopped.)
Here is the log from chrome when trying to share:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/polaris/polaris:8.0.0/OPR1.170623.032/V9.5.19.0.ODGMIFA:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 29340, tid: 29340, name: main >>> zygote64 <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'jni_internal.cc:593] JNI FatalError called: frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:652: selinux_android_setcontext failed'
x0 0000000000000000 x1 000000000000729c x2 0000000000000006 x3 0000000000000008
x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0080808080808080
x8 0000000000000083 x9 b650e91d1636e798 x10 0000000000000000 x11 0000000000000001
x12 ffffffffffffffff x13 0000000000000008 x14 ffffffffffffffff x15 000062c4d4aa08d8
x16 000000095ef4efa8 x17 0000007968a7464c x18 0000000000000001 x19 000000000000729c
x20 000000000000729c x21 0000000000000000 x22 000000796acbaa40 x23 0000007ffda9f249
x24 0000000000000040 x25 0000000000000081 x26 0000000000000079 x27 0000007969663da8
x28 0000007969662f00 x29 0000007ffda9f1f0 x30 0000007968a29eac
sp 0000007ffda9f1b0 pc 0000007968a29ec8 pstate 0000000060000000
backtrace:
#00 pc 000000000001dec8 /system/lib64/libc.so (abort+104)
#01 pc 0000000000474118 /system/lib64/libart.so (art::Runtime::Abort(char const*)+552)
#02 pc 0000000000569fa8 /system/lib64/libart.so (android::base::LogMessage::~LogMessage()+996)
#03 pc 0000000000341490 /system/lib64/libart.so (art::JNI::FatalError(_JNIEnv*, char const*)+192)
#04 pc 00000000001784c4 /system/lib64/libandroid_runtime.so ((anonymous namespace)::RuntimeAbort(_JNIEnv*, int, char const*)+392)
#05 pc 0000000000179850 /system/lib64/libandroid_runtime.so ((anonymous namespace)::ForkAndSpecializeCommon(_JNIEnv*, unsigned int, unsigned int, _jintArray*, int, _jobjectArray*, long, long, int, _jstring*, _jstring*, bool, _jintArray*, _jintArray*, _jstring*, _jstring*)+4864)
#06 pc 0000000000177bb4 /system/lib64/libandroid_runtime.so (android::com_android_internal_os_Zygote_nativeForkAndSpecialize(_JNIEnv*, _jclass*, int, int, _jintArray*, int, _jobjectArray*, int, _jstring*, _jstring*, _jintArray*, _jintArray*, _jstring*, _jstring*)+536)
#07 pc 000000007313f588 /data/dalvik-cache/arm64/[email protected]@boot.oat (offset 0xa13000)
And here is the log when trying to click a link from my email:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/polaris/polaris:8.0.0/OPR1.170623.032/V9.5.19.0.ODGMIFA:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 29903, tid: 29903, name: main >>> zygote64 <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'jni_internal.cc:593] JNI FatalError called: frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:652: selinux_android_setcontext failed'
x0 0000000000000000 x1 00000000000074cf x2 0000000000000006 x3 0000000000000008
x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0080808080808080
x8 0000000000000083 x9 b650e91d1636e798 x10 0000000000000000 x11 0000000000000001
x12 ffffffffffffffff x13 0000000000000008 x14 ffffffffffffffff x15 0000b55756fed6e4
x16 000000095ef4efa8 x17 0000007968a7464c x18 00000078db6010d0 x19 00000000000074cf
x20 00000000000074cf x21 0000000000000000 x22 000000796acbaa40 x23 0000007ffda9f249
x24 0000000000000040 x25 0000000000000081 x26 0000000000000079 x27 0000007969663da8
x28 0000007969662f00 x29 0000007ffda9f1f0 x30 0000007968a29eac
sp 0000007ffda9f1b0 pc 0000007968a29ec8 pstate 0000000060000000
backtrace:
#00 pc 000000000001dec8 /system/lib64/libc.so (abort+104)
#01 pc 0000000000474118 /system/lib64/libart.so (art::Runtime::Abort(char const*)+552)
#02 pc 0000000000569fa8 /system/lib64/libart.so (android::base::LogMessage::~LogMessage()+996)
#03 pc 0000000000341490 /system/lib64/libart.so (art::JNI::FatalError(_JNIEnv*, char const*)+192)
#04 pc 00000000001784c4 /system/lib64/libandroid_runtime.so ((anonymous namespace)::RuntimeAbort(_JNIEnv*, int, char const*)+392)
#05 pc 0000000000179850 /system/lib64/libandroid_runtime.so ((anonymous namespace)::ForkAndSpecializeCommon(_JNIEnv*, unsigned int, unsigned int, _jintArray*, int, _jobjectArray*, long, long, int, _jstring*, _jstring*, bool, _jintArray*, _jintArray*, _jstring*, _jstring*)+4864)
#06 pc 0000000000177bb4 /system/lib64/libandroid_runtime.so (android::com_android_internal_os_Zygote_nativeForkAndSpecialize(_JNIEnv*, _jclass*, int, int, _jintArray*, int, _jobjectArray*, int, _jstring*, _jstring*, _jintArray*, _jintArray*, _jstring*, _jstring*)+536)
#07 pc 000000007313f588 /data/dalvik-cache/arm64/[email protected]@boot.oat (offset 0xa13000)
Also I just noticed that it says on the listing that it doesn't support OTA update but firmware can be changed..?
Any help would be greatly appreciated! :good:

I have the same error.
I can not find any fixes.
Please let me know if you find one, and I'll do the same.

I flashed the Xiaomi.eu ROM after installing TWRP recovery, I found a guide of what to do... and it's a lot more stable now, sharing works and links work.. it came preinstalled with a fake ROM. Using Evie launcher now and it's a bit glitchy at times but otherwise good!

Jowlimowli said:
I flashed the Xiaomi.eu ROM after installing TWRP recovery, I found a guide of what to do... and it's a lot more stable now, sharing works and links work.. it came preinstalled with a fake ROM. Using Evie launcher now and it's a bit glitchy at times but otherwise good!
Click to expand...
Click to collapse
hey, I have just bought a xiaomi mi pad 4 plus and same is happening to me. Could yo please tell me how you did it. Thank you

Having the exact same problem - seems to crash constantly. I've just bought two Mi Pad Plus 4s from Gearbest and they both seem to take massive exception to the use of any other launcher (Nova, Evie).

I hlave same problem! Wtf¿
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/polaris/polaris:8.0.0/OPR1.170623.032/V9.5.19.0.ODGMIFA:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 24289, tid: 24289, name: main >>> zygote64 <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'jni_internal.cc:593] JNI FatalError called: frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:652: selinux_android_setcontext failed'
x0 0000000000000000 x1 0000000000005ee1 x2 0000000000000006 x3 0000000000000008
x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0080808080808080
x8 0000000000000083 x9 6fec259a1850431f x10 0000000000000000 x11 0000000000000001
x12 ffffffffffffffff x13 0000000000000008 x14 ffffffffffffffff x15 000100f1626905b1
x16 0000000220a01fa8 x17 00000078bd3fb64c x18 0000000000000008 x19 0000000000005ee1
x20 0000000000005ee1 x21 0000000000000000 x22 00000078c05c5a40 x23 0000007fceaab899
x24 0000000000000040 x25 0000000000000081 x26 0000000000000079 x27 00000078be156da8
x28 00000078be155f00 x29 0000007fceaab840 x30 00000078bd3b0eac
sp 0000007fceaab800 pc 00000078bd3b0ec8 pstate 0000000060000000
backtrace:
#00 pc 000000000001dec8 /system/lib64/libc.so (abort+104)
#01 pc 0000000000474118 /system/lib64/libart.so (art::Runtime::Abort(char const*)+552)
#02 pc 0000000000569fa8 /system/lib64/libart.so (android::base::LogMessage::~LogMessage()+996)
#03 pc 0000000000341490 /system/lib64/libart.so (art::JNI::FatalError(_JNIEnv*, char const*)+192)
#04 pc 00000000001784c4 /system/lib64/libandroid_runtime.so ((anonymous namespace)::RuntimeAbort(_JNIEnv*, int, char const*)+392)
#05 pc 0000000000179850 /system/lib64/libandroid_runtime.so ((anonymous namespace)::ForkAndSpecializeCommon(_JNIEnv*, unsigned int, unsigned int, _jintArray*, int, _jobjectArray*, long, long, int, _jstring*, _jstring*, bool, _jintArray*, _jintArray*, _jstring*, _jstring*)+4864)
#06 pc 0000000000177bb4 /system/lib64/libandroid_runtime.so (android::com_android_internal_os_Zygote_nativeForkAndSpecialize(_JNIEnv*, _jclass*, int, int, _jintArray*, int, _jobjectArray*, int, _jstring*, _jstring*, _jintArray*, _jintArray*, _jstring*, _jstring*)+536)
#07 pc 00000000741dc588 /data/dalvik-cache/arm64/[email protected]@boot.oat (offset 0xa13000)

I found setting all the default apps fixed a lot of the crashes. In the settings find Installed Apps -> Default Apps, then set all the apps to something. The error in a lot of cases was due to Android not knowing which app to use when opening links, etc.
Still crashes when I try to use the share button, sometimes, so I think I'll be installing the xioami.eu ROM anyway, which will hopefully fix these.

I installed TWRP and the Xiaomi.eu ROM (MIUI 10.2) and the tablet works perfectly now.

Where can I find it? Please guide