Problems porting H2OS Oreo rom - Xiaomi Mi 6 Questions & Answers

Hello everyone,I'm trying to port H2OS Oreo rom from oneplus 5.I know it's a crazy idea to port oreo roms now,but it's worth to have a try.Now the rom stucks at the boot logo,and seems graphic driver isn't working.
Here are the tombstones I got from /data/tombstones.
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'unknown'
Revision: '0'
ABI: 'arm64'
pid: 920, tid: 920, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'no suitable EGLConfig found, giving up'
x0 0000000000000000 x1 0000000000000398 x2 0000000000000006 x3 0000000000000008
x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 8000000000000000
x8 0000000000000083 x9 2254a3d8b426a2e9 x10 0000000000000000 x11 0000000000000001
x12 ffffffffffffffff x13 0000000000000000 x14 ffffffffffffffff x15 0000283320732804
x16 00000074e07932e8 x17 00000074e0734d00 x18 0000000000000000 x19 0000000000000398
x20 0000000000000398 x21 0000000000000001 x22 0000000000000000 x23 00000074dfe5e1d0
x24 0000000000000000 x25 00000000000f4240 x26 0000000000000000
...
I have replaced all the graphic/hwcomposer hals,egl stuffs but no luck.
Anyone can help,please?

Hello, Sounds Like a good idea.. I'm Not a Developer but you could try joining mi6 telegram Group.. Maybe there is some developer on there, which helps you.. And one question why are you trying to port the chinese H2OS not the Global OxygenOS ?

Hey,
I'm not developer either, but have pretty good idea with IT. Do you tried to use RR/Los15 configs that are already ported to Mi6? From this log I don't see much info except that it can't find a driver specific for Mi6, I suppose it tries to load OP5 somehwere in the configs.

Related

Unfortunately Google Play Services has stopped.

I have cm11 installed on my Xperia M. Since few days I have been getting a message randomly saying - "Unfortunately Google Play Services has stopped'. It constantly keeps flashing and not only it is annoying, it also makes the phone sluggish sometimes. It is flashing even when I am typing this problem in this thread. I have tried uninstalling updates and reinstalling them and also clearing cache and data. Any solutions anybody?!?
I have the same problem - i think there is a connection between switching on Wi-Fi and this, but i don't really sure about this
error
Code:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Sony/C1905/C1905:4.3/15.4.A.1.9/eng.user.20140509.125022:user/release-keys'
Revision: '0'
pid: 15539, tid: 15551, name: Binder_2 >>> com.google.android.gms.unstable <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr b6cc5704
r0 b6cc5700 r1 5f4e8938 r2 5b663440 r3 5b663440
r4 5b663440 r5 5b3970e0 r6 5f4e8938 r7 35600001
r8 26400005 r9 5b5d4e74 sl 5b5ce500 fp 5f4e8984
ip 5d3059b4 sp 5f4e8928 lr 5d2e7e65 pc 40156a54 cpsr 900d0030
d0 00720064006e0061 d1 002e00640069006f
d2 002e006d00720064 d3 006d007200440049
d4 e1c97466582e7bdf d5 bf55596a4c1f5b56
d6 5cc5f9ab3da651f2 d7 f8e475e852222227
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 ce4ad679a98befed d17 ed211dd5dc27c8a3
d18 006900640065006d d19 004d0049002e0061
d20 0061006900640065 d21 00790061006c0050
d22 0065005300720065 d23 0063006900760072
d24 0000000000000000 d25 4008000000000000
d26 ffffffffffffffff d27 ffffffffffffffff
d28 00000000000000e6 d29 0000000000000002
d30 0000000000000001 d31 0000000000004000
scr 80000010
backtrace:
#00 pc 0000da54 /system/lib/libutils.so (android::RefBase::incStrong(void const*) const+1)
#01 pc 00017e61 /system/lib/libmedia_jni.so
#02 pc 0001ea10 /system/lib/libdvm.so (dvmPlatformInvoke+116)
#03 pc 0004f6cf /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
#04 pc 00027ea0 /system/lib/libdvm.so
#05 pc 0002f3e4 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#06 pc 0002ca48 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#07 pc 00061afd /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
#08 pc 0004e42d /system/lib/libdvm.so
#09 pc 00072133 /system/lib/libandroid_runtime.so
#10 pc 000775d7 /system/lib/libandroid_runtime.so
#11 pc 00019cc5 /system/lib/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+60)
#12 pc 0001e239 /system/lib/libbinder.so (android::IPCThreadState::executeCommand(int)+508)
#13 pc 0001e5b7 /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+38)
#14 pc 0001e62d /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+48)
#15 pc 000224b1 /system/lib/libbinder.so
#16 pc 0000f3e9 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+216)
#17 pc 00052495 /system/lib/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+68)
#18 pc 0000ef1b /system/lib/libutils.so
#19 pc 0000d1c0 /system/lib/libc.so (__thread_entry+72)
#20 pc 0000d358 /system/lib/libc.so (pthread_create+240)
code around pc:
40156a34 46206060 bf00bd10 00006e42 4604b510
40156a44 ffe2f7ff f7fd4620 4620e916 b510bd10
40156a54 1d206844 ea1cf7fd f7fd4620 f1b0ea1a
40156a64 d1085f80 f04f4621 f7fd4070 68a0ea18
40156a74 68996803 bd104788 6844b510 f7fd1d20
40156a84 4620ea08 ea04f7fd f1b0b138 d1085f80
40156a94 4070f04f f7fd4621 68a0ea02 68996803
40156aa4 bd104788 68186843 30044770 bf1af003
40156ab4 4604b538 460d3004 e9f6f7fd d1192801
40156ac4 07d968e3 6823d409 5f80f1b3 e00cd100
40156ad4 e8bd4620 f0034038 68a0bf0d 694a6801
40156ae4 47904629 07c268e0 68a0d504 6801b110
40156af4 4790684a b570bd38 68444605 4620460e
40156b04 e9d2f7fd d10b2801 463168a0 68da6803
40156b14 68e04790 d40307c0 46286829 4798684b
40156b24 46314620 4070e8bd bfc2f7ff 4604b570
code around lr:
5d2e7e44 463a4629 ae0a4633 f92af7ff 4d20f846
5d2e7e54 6820b134 1c0cf850 46311860 eed8f7f9
5d2e7e64 69539a02 d13d2b00 6820e034 1c0cf850
5d2e7e74 a9031860 eeccf7f9 ac0a9b03 8008f8dd
5d2e7e84 3d18f844 681ab133 f8524621 18180c0c
5d2e7e94 eebef7f9 46404621 fa0ff7ff f7fb4620
5d2e7ea4 4629fc81 463a4620 f7fe4633 4620facb
5d2e7eb4 fc78f7fb b1319903 f853680b 18882c0c
5d2e7ec4 f7f9a903 4630eeac fc6cf7fb f7fea805
5d2e7ed4 e014f9d5 4628490f 44794a0f f7fb447a
5d2e7ee4 e7f0f9ab f7f92014 4604eeca 463a4629
5d2e7ef4 f7fe4643 9403fe91 d1b62c00 b00ae7bc
5d2e7f04 81f0e8bd 00013c42 000156b0 00013c22
5d2e7f14 000155ce 000155f1 00015618 2108b538
5d2e7f24 4d052200 f7fa4604 4b04e90e 58e8447d
5d2e7f34 60203008 bd384620 0001da60 ffffff50
logcat
same here
Am having same issue......it very annoying.....
And it is happening every time I connect to a WiFi
It started after updating the gapps that I flashed...
Someone pls help
I had a similar issue with Google play. Try cleaning the app data of:
-Google plat services
-Google play
-Google play framework
Reboot.
Hope it works
It only takes 2 taps to thank somebody here.
I can confirm that issue. It doesn't make any sense to me. It happens on both CM11 and CM12, so it can't be directly connected with the CM sources. @PecanCM
It doesn't happen on SGS3 tho, so I either suspect device tree problem or google.
RedLedLight said:
I had a similar issue with Google play. Try cleaning the app data of:
-Google plat services
-Google play
-Google play framework
Reboot.
Hope it works
It only takes 2 taps to thank somebody here.
Click to expand...
Click to collapse
Cleaning app data does'nt help, i think g analytics may also be involved in.
RedLedLight said:
I had a similar issue with Google play. Try cleaning the app data of:
-Google plat services
-Google play
-Google play framework
Reboot.
Hope it works
It only takes 2 taps to thank somebody here.
Click to expand...
Click to collapse
It didn't work. Can anyone devise a sure-working solution to this really annoying problem?
I just not using em.... my life is beautiful anyway without gapps
---------- Post added at 10:58 PM ---------- Previous post was at 10:53 PM ----------
JustArchi said:
I can confirm that issue. It doesn't make any sense to me. It happens on both CM11 and CM12, so it can't be directly connected with the CM sources. @PecanCM
It doesn't happen on SGS3 tho, so I either suspect device tree problem or google.
Click to expand...
Click to collapse
But bro, it doesn't happen on your v2.5.3 ROM. the latest update have that issue. i've stuck on your rom for almost a month n then get back to stock cm 11 without gapps:victory:
I found this in an other topic :
1. Launch Terminal (preinstalled in ROM)
2. Type su and press Enter
3. Give root rights
4. Paste this text:
pm disable com.google.android.gms/com.google.android.gms.droidguard.DroidGuardService
5. Press Enter
6. Crashing must stop
Click to expand...
Click to collapse
My problem stops after installing Lollipop, no annoying messages
My problem solved after updating to lollipop
Sent from my C1904 using XDA Free mobile app
Atimen33 said:
I found this in an other topic :
Click to expand...
Click to collapse
I tried this but still get an error
if you using Kitkat try this
[ROM][KTU84P][4.4.4][NIGHTLY/FXP341] Official CyanogenMod 11 - http://forum.xda-developers.com/showthread.php?p=57606460
[ROM][KTU84P][4.4.4][NIGHTLY/FXP341] Official CyanogenMod 11
it worked for me

Any insight? Discord app crashes. Logs provided

Hello,
I'm unsure of where to seek help for this. I open the discord app and it crashes. Doesn't matter if it's a fresh install or a backup. alogcat below.
--------- beginning of main
--------- beginning of system
F/art (14321): art/runtime/stack.cc:860] Check failed: instrumentation_frame.method_ == GetMethod() (instrumentation_frame.method_=0x719d8d50, GetMethod()=0x71a852b0) Expected: void android.view.LayoutInflater.rInflateChildren(org.xmlpull.v1.XmlPullParser, android.view.View, android.util.AttributeSet, boolean) Found: <runtime method>.<runtime internal callee-save reference and argument registers method><no signature>
F/art (14321): art/runtime/stack.cc:860] Check failed: instrumentation_frame.method_ == GetMethod() (instrumentation_frame.method_=0x719d8d50, GetMethod()=0x71a852b0) Expected: void android.view.LayoutInflater.rInflateChildren(org.xmlpull.v1.XmlPullParser, android.view.View, android.util.AttributeSet, boolean) Found: <runtime method>.<runtime internal callee-save reference and argument registers method><no signature>
F/art (14321): art/runtime/runtime.cc:404] Runtime aborting --- recursively, so no thread-specific detail!
F/art (14321): art/runtime/runtime.cc:404]
--------- beginning of crash
F/google-breakpad(14456): Microdump skipped (uninteresting)
F/libc (14321): Fatal signal 6 (SIGABRT), code -6 in tid 14321 (com.discord)
F/DEBUG (14469): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
F/DEBUG (14469): Build fingerprint: 'htc/pmewl_00617/htc_pmewl:7.0/NRD90M/942117.1:user/release-keys'
F/DEBUG (14469): Revision: '0'
F/DEBUG (14469): ABI: 'arm64'
F/DEBUG (14469): pid: 14321, tid: 14321, name: com.discord >>> com.discord <<<
F/DEBUG (14469): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
F/DEBUG (14469): Abort message: 'art/runtime/stack.cc:860] Check failed: instrumentation_frame.method_ == GetMethod() (instrumentation_frame.method_=0x719d8d50, GetMethod()=0x71a852b0) Expected: void android.view.LayoutInflater.rInflateChildren(org.xmlpull.v1.XmlPullParser, android.view.View, android.util.AttributeSet, boolean) Found: <runtime method>.<runtime internal callee-save reference and argument registers method><no signature>'
F/DEBUG (14469): x0 0000000000000000 x1 00000000000037f1 x2 0000000000000006 x3 0000000000000008
F/DEBUG (14469): x4 0000000000000003 x5 0000800000000000 x6 0000007fa1d4a000 x7 0000000000000000
F/DEBUG (14469): x8 0000000000000083 x9 ffffffffffffffdf x10 0000000000000000 x11 0000000000000001
F/DEBUG (14469): x12 ffffffffffffffff x13 0000000000000000 x14 0000000000000000 x15 001b08c6c4583bde
F/DEBUG (14469): x16 0000007f9f02fed8 x17 0000007f9efd947c x18 00000000ebad6082 x19 0000007fa1dfeb40
F/DEBUG (14469): x20 0000000000000006 x21 0000007fa1dfea98 x22 0000000000000002 x23 0000007f9e1ebaa3
F/DEBUG (14469): x24 0000007fa1a9f680 x25 0000007f9e2192e2 x26 0000007f9e2192eb x27 0000007fcfabde21
F/DEBUG (14469): x28 0000007f9e2192ab x29 0000007fcfabdd40 x30 0000007f9efd690c
F/DEBUG (14469): sp 0000007fcfabdd20 pc 0000007f9efd9484 pstate 0000000060000000
F/DEBUG (14469):
F/DEBUG (14469): backtrace:
F/DEBUG (14469): #00 pc 000000000006c484 /system/lib64/libc.so (tgkill+8)
F/DEBUG (14469): #01 pc 0000000000069908 /system/lib64/libc.so (pthread_kill+64)
F/DEBUG (14469): #02 pc 0000000000024438 /system/lib64/libc.so (raise+24)
F/DEBUG (14469): #03 pc 000000000001ce54 /system/lib64/libc.so (abort+52)
F/DEBUG (14469): #04 pc 0000000000433c7c /system/lib64/libart.so (_ZN3art7Runtime5AbortEv+352)
F/DEBUG (14469): #05 pc 00000000000e6a30 /system/lib64/libart.so (_ZN3art10LogMessageD2Ev+1248)
F/DEBUG (14469): #06 pc 000000000044aec0 /system/lib64/libart.so (_ZN3art12StackVisitor9WalkStackEb+4072)
F/DEBUG (14469): #07 pc 0000000000455494 /system/lib64/libart.so (_ZNK3art6Thread9DumpStackERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEbP12BacktraceMap+440)
F/DEBUG (14469): #08 pc 0000000000443560 /system/lib64/libart.so (_ZNK3art10AbortState10DumpThreadERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEPNS_6ThreadE+56)
F/DEBUG (14469): #09 pc 0000000000443380 /system/lib64/libart.so (_ZNK3art10AbortState4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE+576)
F/DEBUG (14469): #10 pc 0000000000433ba8 /system/lib64/libart.so (_ZN3art7Runtime5AbortEv+140)
F/DEBUG (14469): #11 pc 00000000000e6a30 /system/lib64/libart.so (_ZN3art10LogMessageD2Ev+1248)
F/DEBUG (14469): #12 pc 000000000044aec0 /system/lib64/libart.so (_ZN3art12StackVisitor9WalkStackEb+4072)
F/DEBUG (14469): #13 pc 00000000004c6d90 /system/lib64/libart.so (_ZN3art25GetCalleeSaveMethodCallerEPPNS_9ArtMethodENS_7Runtime14CalleeSaveTypeEb+1112)
F/DEBUG (14469): #14 pc 00000000005507f4 /system/lib64/libart.so (artQuickToInterpreterBridge+940)
F/DEBUG (14469): #15 pc 00000000000dc52c /system/lib64/libart.so (art_quick_to_interpreter_bridge+92)
F/DEBUG (14469): #16 pc 00000000000dc67c /system/lib64/libart.so
Click to expand...
Click to collapse
I'm getting a similar experience, no idea what's going on. I also tried KIK and I have the same thing happen there as well
I got that problem too. Discord crashed every single time I try to turn it on since I rooted my phone [Xiaomi Redmi Note 4 Snapdragon Android 7.0]

Facebook app keeps crashing

My Facebook app keeps crashing when i try to start it. Uninstalled and reinstalled via Google Playstore but doesn't work. On ResurrectionRom 12 June build with Magisk installed
Here is the log of events. Let me know if more info is needed
build.board: sdm636
build.bootloader: unknown
build.brand: Xiaomi
build.cpu_abi: arm64-v8a
build.cpu_abi2:
build.device: whyred
build.display: rr_whyred-userdebug 8.1.0 OPM2.171026.006.C1 6568cf4ffd test-keys
build.fingerprint: xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/8.4.27:user/release-keys
build.hardware: qcom
build.host: jagermiest3r
build.id: OPM2.171026.006.C1
build.manufacturer: Xiaomi
build.model: Redmi Note 5 Pro
build.product: whyred
build.radio: unknown
build.serial: 4283a9b1
build.tags: release-keys
build.time: 1528791108000
build.type: user
build.user: shahan
version.codename: REL
version.incremental: 6568cf4ffd
version.release: 8.1.0
version.sdk_int: 27
--------- beginning of system
--------- beginning of crash
06-16 16:54:45.086 F/libc (7632): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 7785 (fresh_feed_stor), pid 7632 (facebook.katana)
06-16 16:54:45.165 F/DEBUG (7826): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-16 16:54:45.166 F/DEBUG (7826): LineageOS Version: 'unknown'
06-16 16:54:45.166 F/DEBUG (7826): Build fingerprint: 'xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/8.4.27:user/release-keys'
06-16 16:54:45.166 F/DEBUG (7826): Revision: '0'
06-16 16:54:45.166 F/DEBUG (7826): ABI: 'arm'
06-16 16:54:45.166 F/DEBUG (7826): pid: 7632, tid: 7785, name: fresh_feed_stor >>> com.facebook.katana <<<
06-16 16:54:45.166 F/DEBUG (7826): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-16 16:54:45.166 F/DEBUG (7826): Cause: null pointer dereference
06-16 16:54:45.166 F/DEBUG (7826): r0 00000000 r1 00000000 r2 003cc7f0 r3 3ff00000
06-16 16:54:45.166 F/DEBUG (7826): r4 cdd44610 r5 cf9f4204 r6 00000000 r7 cf9f41e0
06-16 16:54:45.166 F/DEBUG (7826): r8 cf9f4234 r9 cf9f41f8 sl cf9f42b4 fp cf9f434c
06-16 16:54:45.166 F/DEBUG (7826): ip 00000000 sp cf9f4108 lr d42af5c1 pc d42af734 cpsr 600d0030
06-16 16:54:45.167 F/DEBUG (7826):
06-16 16:54:45.167 F/DEBUG (7826): backtrace:
06-16 16:54:45.167 F/DEBUG (7826): #00 pc 0052a734 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:45.167 F/DEBUG (7826): #01 pc 0052a5bd /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:45.167 F/DEBUG (7826): #02 pc 00364bb1 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:45.167 F/DEBUG (7826): #03 pc 00364c01 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:45.167 F/DEBUG (7826): #04 pc 00364b31 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:45.167 F/DEBUG (7826): #05 pc 00215873 /data/app/com.facebook.katana-rPcNMz6O3cl5P0ob90w4HA==/oat/arm/base.odex (offset 0x211000)
06-16 16:54:51.025 F/libc (7936): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 8020 (fresh_feed_stor), pid 7936 (facebook.katana)
06-16 16:54:51.121 F/DEBUG (8096): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-16 16:54:51.121 F/DEBUG (8096): LineageOS Version: 'unknown'
06-16 16:54:51.121 F/DEBUG (8096): Build fingerprint: 'xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/8.4.27:user/release-keys'
06-16 16:54:51.121 F/DEBUG (8096): Revision: '0'
06-16 16:54:51.121 F/DEBUG (8096): ABI: 'arm'
06-16 16:54:51.121 F/DEBUG (8096): pid: 7936, tid: 8020, name: fresh_feed_stor >>> com.facebook.katana <<<
06-16 16:54:51.121 F/DEBUG (8096): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-16 16:54:51.121 F/DEBUG (8096): Cause: null pointer dereference
06-16 16:54:51.121 F/DEBUG (8096): r0 00000000 r1 00000000 r2 003cc7f0 r3 3ff00000
06-16 16:54:51.121 F/DEBUG (8096): r4 d09bb580 r5 d16ef204 r6 00000000 r7 d16ef1e0
06-16 16:54:51.121 F/DEBUG (8096): r8 d16ef234 r9 d16ef1f8 sl d16ef2b4 fp d16ef34c
06-16 16:54:51.121 F/DEBUG (8096): ip 00000000 sp d16ef108 lr d44705c1 pc d4470734 cpsr 600d0030
06-16 16:54:51.124 F/DEBUG (8096):
06-16 16:54:51.124 F/DEBUG (8096): backtrace:
06-16 16:54:51.124 F/DEBUG (8096): #00 pc 0052a734 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:51.124 F/DEBUG (8096): #01 pc 0052a5bd /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:51.124 F/DEBUG (8096): #02 pc 00364bb1 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:51.124 F/DEBUG (8096): #03 pc 00364c01 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:51.124 F/DEBUG (8096): #04 pc 00364b31 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:51.124 F/DEBUG (8096): #05 pc 00215873 /data/app/com.facebook.katana-rPcNMz6O3cl5P0ob90w4HA==/oat/arm/base.odex (offset 0x211000)
06-16 16:54:54.981 F/libc (8130): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 8215 (fresh_feed_stor), pid 8130 (facebook.katana)
06-16 16:54:55.104 F/DEBUG (8564): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-16 16:54:55.104 F/DEBUG (8564): LineageOS Version: 'unknown'
06-16 16:54:55.104 F/DEBUG (8564): Build fingerprint: 'xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/8.4.27:user/release-keys'
06-16 16:54:55.104 F/DEBUG (8564): Revision: '0'
06-16 16:54:55.104 F/DEBUG (8564): ABI: 'arm'
06-16 16:54:55.104 F/DEBUG (8564): pid: 8130, tid: 8215, name: fresh_feed_stor >>> com.facebook.katana <<<
06-16 16:54:55.104 F/DEBUG (8564): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-16 16:54:55.104 F/DEBUG (8564): Cause: null pointer dereference
06-16 16:54:55.104 F/DEBUG (8564): r0 00000000 r1 00000000 r2 003cc7f0 r3 3ff00000
06-16 16:54:55.104 F/DEBUG (8564): r4 d3105840 r5 d1f311d4 r6 00000000 r7 d1f311b0
06-16 16:54:55.104 F/DEBUG (8564): r8 d1f31204 r9 d1f311c8 sl d1f31284 fp d1f31314
06-16 16:54:55.104 F/DEBUG (8564): ip 00000000 sp d1f310d8 lr d44b05c1 pc d44b0734 cpsr 600d0030
06-16 16:54:55.107 F/DEBUG (8564):
06-16 16:54:55.107 F/DEBUG (8564): backtrace:
06-16 16:54:55.107 F/DEBUG (8564): #00 pc 0052a734 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:55.107 F/DEBUG (8564): #01 pc 0052a5bd /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:55.107 F/DEBUG (8564): #02 pc 00364bb1 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:55.107 F/DEBUG (8564): #03 pc 00364c01 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:55.107 F/DEBUG (8564): #04 pc 00364b31 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:54:55.107 F/DEBUG (8564): #05 pc 00215873 /data/app/com.facebook.katana-rPcNMz6O3cl5P0ob90w4HA==/oat/arm/base.odex (offset 0x211000)
06-16 16:57:56.034 F/libc (10608): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 14669 (fresh_feed_stor), pid 10608 (facebook.katana)
06-16 16:57:56.169 F/DEBUG (14775): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-16 16:57:56.169 F/DEBUG (14775): LineageOS Version: 'unknown'
06-16 16:57:56.169 F/DEBUG (14775): Build fingerprint: 'xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/8.4.27:user/release-keys'
06-16 16:57:56.169 F/DEBUG (14775): Revision: '0'
06-16 16:57:56.169 F/DEBUG (14775): ABI: 'arm'
06-16 16:57:56.169 F/DEBUG (14775): pid: 10608, tid: 14669, name: fresh_feed_stor >>> com.facebook.katana <<<
06-16 16:57:56.169 F/DEBUG (14775): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-16 16:57:56.170 F/DEBUG (14775): Cause: null pointer dereference
06-16 16:57:56.170 F/DEBUG (14775): r0 00000000 r1 3ff00000 r2 00000000 r3 00000000
06-16 16:57:56.170 F/DEBUG (14775): r4 d5ad6558 r5 cd0bfb20 r6 cb3c91a0 r7 cb3c90c8
06-16 16:57:56.170 F/DEBUG (14775): r8 cb3c9244 r9 cb3c91ac sl cb3c91e8 fp f306f1b8
06-16 16:57:56.170 F/DEBUG (14775): ip 00000000 sp cb3c90a8 lr d5886b93 pc d5886bc8 cpsr 60070030
06-16 16:57:56.171 F/DEBUG (14775):
06-16 16:57:56.171 F/DEBUG (14775): backtrace:
06-16 16:57:56.171 F/DEBUG (14775): #00 pc 00481bc8 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:57:56.171 F/DEBUG (14775): #01 pc 00481b21 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:57:56.171 F/DEBUG (14775): #02 pc 00380c99 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:57:56.171 F/DEBUG (14775): #03 pc 0009ac79 /system/lib/libart.so (offset 0x35f000)
06-16 16:58:01.396 F/libc (14938): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 15156 (fresh_feed_stor), pid 14938 (facebook.katana)
06-16 16:58:01.523 F/DEBUG (15333): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-16 16:58:01.523 F/DEBUG (15333): LineageOS Version: 'unknown'
06-16 16:58:01.523 F/DEBUG (15333): Build fingerprint: 'xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/8.4.27:user/release-keys'
06-16 16:58:01.523 F/DEBUG (15333): Revision: '0'
06-16 16:58:01.523 F/DEBUG (15333): ABI: 'arm'
06-16 16:58:01.523 F/DEBUG (15333): pid: 14938, tid: 15156, name: fresh_feed_stor >>> com.facebook.katana <<<
06-16 16:58:01.523 F/DEBUG (15333): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-16 16:58:01.523 F/DEBUG (15333): Cause: null pointer dereference
06-16 16:58:01.524 F/DEBUG (15333): r0 00000000 r1 3ff00000 r2 00000000 r3 00000000
06-16 16:58:01.524 F/DEBUG (15333): r4 dac98558 r5 d12246c0 r6 d11fe1e0 r7 d11fe108
06-16 16:58:01.524 F/DEBUG (15333): r8 d11fe284 r9 d11fe1ec sl d11fe228 fp f306f1b8
06-16 16:58:01.524 F/DEBUG (15333): ip 00000000 sp d11fe0e8 lr daa48b93 pc daa48bc8 cpsr 60070030
06-16 16:58:01.525 F/DEBUG (15333):
06-16 16:58:01.525 F/DEBUG (15333): backtrace:
06-16 16:58:01.525 F/DEBUG (15333): #00 pc 00481bc8 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:58:01.525 F/DEBUG (15333): #01 pc 00481b21 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:58:01.525 F/DEBUG (15333): #02 pc 00380c99 /data/data/com.facebook.katana/lib-xzs/libcoldstart.so
06-16 16:58:01.525 F/DEBUG (15333): #03 pc 0009ac79 /system/lib/libart.so (offset 0x35f000)
My Wife's FB app just started this today too. Have wiped Data/Cache for the app, uninstalled, re-installed, wiped cache partition. Would like to not have to wipe it back to factory as there is no guarantee it won't crash again. We logged in with another user and it works just fine so it seems like it is something tied to her account.
---------- Post added at 07:19 AM ---------- Previous post was at 07:03 AM ----------
Just a quick update. Since it worked with another account and she uses Samsung Pass to log in we decided to take her password out of Samsung Pass and then wiped FB from the phone, rebooted and logged in and it worked. So if you are using Samsung Pass, try removing the password there (so SP doesn't pop up when logging into the app) and see if that works.
Robertsonland said:
My Wife's FB app just started this today too. Have wiped Data/Cache for the app, uninstalled, re-installed, wiped cache partition. Would like to not have to wipe it back to factory as there is no guarantee it won't crash again. We logged in with another user and it works just fine so it seems like it is something tied to her account.
---------- Post added at 07:19 AM ---------- Previous post was at 07:03 AM ----------
Just a quick update. Since it worked with another account and she uses Samsung Pass to log in we decided to take her password out of Samsung Pass and then wiped FB from the phone, rebooted and logged in and it worked. So if you are using Samsung Pass, try removing the password there (so SP doesn't pop up when logging into the app) and see if that works.
Click to expand...
Click to collapse
im not using Samsung pass, sorry. many other users are reporting the same thing on twitter too. guess Facebook must have messed up the update somehow.
Here's hoping they fix it. I just wanted to report what worked for us in case someone else ran into it.
I have the same issue, just delete the app data and delete the facebook folders on android/data
Seems like its working properly now, even without a PlayStore update. Think facebook must have fixed something on their side of their servers

Pixel Xl Bluetooth does not work, at ALL.

Whenever I try to turn it on, it never does, and just says "Bluetooth keeps stopping" with this log
Code:
time: 1593372413360
msg: Native crash: Aborted
stacktrace: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/marlin/marlin:8.1.0/OPM1.171019.021/4565141:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2020-06-28 15:26:52-0400
pid: 8827, tid: 8851, name: alarm_default_c >>> com.android.bluetooth <<<
uid: 1002
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
x0 0000000000000000 x1 0000000000002293 x2 0000000000000006 x3 000000735f4ff210
x4 b975e33461ee3c1e x5 b975e33461ee3c1e x6 b975e33461ee3c1e x7 b975e33461ee3c1e
x8 00000000000000f0 x9 b975e33461ee3c1e x10 b975e33461ee3c1e x11 b975e33461ee3c1e
x12 0000001000000000 x13 ffffffe0fffffbdf x14 b975e33461ee3c1e x15 b975e33461ee3c1e
x16 000000744c0efcf0 x17 000000744c0ca240 x18 000000735f0f4028 x19 00000000000000ac
x20 000000000000227b x21 00000000000000b2 x22 0000000000002293 x23 00000000ffffffff
x24 00000073b75e79c0 x25 000000735f500020 x26 0000000002251464 x27 00000073c9986b30
x28 0000007363fbf23c x29 000000735f4ff2c0
sp 000000735f4ff1f0 lr 000000744c073cc4 pc 000000744c073ce4
backtrace:
#00 pc 0000000000073ce4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: 31b21112cad9859ed337ff8a0d05073d)
#01 pc 000000000027e6b4 /system/lib64/libbluetooth.so (startup_timer_expired(void*) [clone .cfi]+84) (BuildId: e96eb8253ee19c41be58fa436d877776)
#02 pc 00000000003672dc /system/lib64/libbluetooth.so (alarm_ready_generic(alarm_t*, std::__1::unique_lock<std::__1::mutex>&)+424) (BuildId: e96eb8253ee19c41be58fa436d877776)
#03 pc 00000000003673f8 /system/lib64/libbluetooth.so (alarm_queue_ready(fixed_queue_t*, void*) [clone .cfi]+120) (BuildId: e96eb8253ee19c41be58fa436d877776)
#04 pc 000000000036a7ac /system/lib64/libbluetooth.so (internal_dequeue_ready(void*) [clone .cfi]+108) (BuildId: e96eb8253ee19c41be58fa436d877776)
#05 pc 000000000036c2dc /system/lib64/libbluetooth.so (run_thread(void*) [clone .cfi]+700) (BuildId: e96eb8253ee19c41be58fa436d877776)
#06 pc 00000000000e08ec /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) (BuildId: 31b21112cad9859ed337ff8a0d05073d)
#07 pc 00000000000757dc /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 31b21112cad9859ed337ff8a0d05073d)
Any suggestions?
I am also facing this issue.How did you resolved it

GL Error makes apps crash on CUSTOM ROM

i got a problem while trying to enter on Incognite Mode on Chrome, or when I try to play a song on Spotify while I got my headphones connected through bluetooth on Spotify, Chrome and Spotify crashes and they have the same error, which says "GL errors frameworks/base/libs/hwui/renderthread/CanvasContext.cpp:550"
My device is a MTK Processor MT6580 Kernel 3.18.19 Official Android version 6.0.1 but I ported it to 7.1.2 and running OS fine except this issue I dont know how to fix
the problem generated on the logs is this:
Process: com.spotify.music
Flags: 0x38d83e44
Package: com.spotify.music v85204766 (8.7.18.1138)
Foreground: Yes
Build: 'BLU/xxx/xxx:7.1.2/xxxx/xxx:userdebug/release-keys'
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Cardinal-AOSP Version: '4.5'
Build fingerprint: 'BLU/xxx/xxx:7.1.2/xxxx/xxx:userdebug/release-keys'
Revision: '0'
ABI: 'arm'
pid: 5099, tid: 5220, name: RenderThread >>> com.spotify.music <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'GL errors! frameworks/base/libs/hwui/renderthread/CanvasContext.cpp:550'
r0 00000000 r1 00001464 r2 00000006 r3 00000008
r4 8f5f0978 r5 00000006 r6 8f5f0920 r7 0000010c
r8 94ae0b80 r9 00000000 sl 973882fc fp 973882f8
ip 00000000 sp 8f5eff38 lr b4384ec7 pc b4387748 cpsr 20070010
backtrace:
#00 pc 0004a748 /system/lib/libc.so (tgkill+12)
#01 pc 00047ec3 /system/lib/libc.so (pthread_kill+34)
#02 pc 0001d6f5 /system/lib/libc.so (raise+10)
#03 pc 00019241 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 000171f8 /system/lib/libc.so (abort+4)
#05 pc 0000c1dd /system/lib/libcutils.so (__android_log_assert+112)
#06 pc 00024077 /system/lib/libhwui.so
#07 pc 00025a73 /system/lib/libhwui.so
#08 pc 00029035 /system/lib/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+80)
#09 pc 0000e3fd /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+140)
#10 pc 00066c11 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+80)
#11 pc 00047993 /system/lib/libc.so (_ZL15__pthread_startPv+22)
#12 pc 00019c8d /system/lib/libc.so (__start_thread+6)
Do u have any idea what file is causing that on the ported rom and what i have to replace from stock to there? I'd appreciate any help from you, I like porting and stuff so I wish i could fix this I'd appreciate any help
I fixed the issue years ago and shared it for mt6580 community. You can grab my fixcrash patch for mt6580 on Kernel 3.18.19.
You will find some other patches too, If you need it. A bit late, but maybe it helps someone.
MT6580 - Google Drive
drive.google.com
Otherwise port my latest LineageOS 14.1 which has newest / latest patches from LineageOS included (Security Patch Level is from 2022).
Also all issues are fixed, media codec issues (Video Playback), FM Radio works, no App crashes, power profiles are included and GPS is working as well. Lot of crashes in background are fixed, which i found with logcat (improves the speed and battery lifetime).
ROM LineageOS 14.1 | [Custom]-[Updated] add the 02/27/2022 on Needrom

Categories

Resources