Develop Bugs

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

[HELP] [DEV] Seems MIUI Lollipop is possible to port

while i porting miui lollipop from lenovo a6000 (qualcomm) then following the tutorial how to port miui
the rom is stuck at miui logo (bootloop)
seems a good news for zenfone 5 users
logcat
PHP:
I/DEBUG ( 243): property debug.db.uid not set; NOT waiting for gdb.
I/DEBUG ( 243): HINT: adb shell setprop debug.db.uid 100000
I/DEBUG ( 243): HINT: adb forward tcp:5039 tcp:5039
I/DEBUG ( 243): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 243): Build fingerprint: 'asus/miui_a500cg/ASUS_T00F:5.1.1/LMY48Y/770526b4d4:userdebug/test-keys'
I/DEBUG ( 243): Revision: '0'
I/DEBUG ( 243): ABI: 'x86'
I/DEBUG ( 243): pid: 6304, tid: 6304, name: main >>> zygote <<<
I/DEBUG ( 243): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 243): Abort message: 'art/runtime/jni_internal.cc:769] JNI FatalError called: RegisterNatives failed for 'android/content/res/AssetManager'; aborting...'
I/DEBUG ( 243): eax 00000000 ebx 000018a0 ecx 000018a0 edx 00000006
I/DEBUG ( 243): esi b7782c48 edi 00000002
I/DEBUG ( 243): xcs 00000073 xds 0000007b xes 0000007b xfs 00000007 xss 0000007b
I/DEBUG ( 243): eip b753dcd6 ebp 000018a0 esp bff29bb0 flags 00000206
I/DEBUG ( 243):
I/DEBUG ( 243): backtrace:
I/DEBUG ( 243): #00 pc 00085cd6 /system/lib/libc.so (tgkill+22)
I/DEBUG ( 243): #01 pc 0002cbe3 /system/lib/libc.so (pthread_kill+163)
I/DEBUG ( 243): #02 pc 0002e745 /system/lib/libc.so (raise+37)
I/DEBUG ( 243): #03 pc 00026665 /system/lib/libc.so (abort+85)
I/DEBUG ( 243): #04 pc 0037d1d7 /system/lib/libart.so (art::Runtime::Abort()+295)
I/DEBUG ( 243): #05 pc 000ec134 /system/lib/libart.so (art::LogMessage::~LogMessage()+1892)
I/DEBUG ( 243): #06 pc 002dc52a /system/lib/libart.so (art::JNI::FatalError(_JNIEnv*, char const*)+122)
I/DEBUG ( 243): #07 pc 00001ee6 /system/lib/libnativehelper.so (jniRegisterNativeMethods+182)
I/DEBUG ( 243): #08 pc 0006b2a3 /system/lib/libandroid_runtime.so (android::AndroidRuntime::registerNativeMethods(_JNIEnv*, char const*, JNINativeMethod const*, int)+51)
I/DEBUG ( 243): #09 pc 000d0149 /system/lib/libandroid_runtime.so (android::register_android_content_AssetManager(_JNIEnv*)+681)
I/DEBUG ( 243): #10 pc 0006cbf3 /system/lib/libandroid_runtime.so (android::AndroidRuntime::startReg(_JNIEnv*)+83)
I/DEBUG ( 243): #11 pc 0006cde2 /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, android::Vector<android::String8> const&, bool)+418)
I/DEBUG ( 243): #12 pc 000018c1 /system/bin/app_process32
I/DEBUG ( 243): #13 pc 0000f39c /system/lib/libc.so (__libc_init+108)
I/DEBUG ( 243): #14 pc 00001b8d /system/bin/app_process32
I/DEBUG ( 243): #15 pc 00000004 <unknown>
I/DEBUG ( 243):
I/DEBUG ( 243): Tombstone written to: /data/tombstones/tombstone_06
I/ServiceManager( 179): service 'media.audio_flinger' died

OMG.
It will never boot because it uses ART for arm.

tank0412 said:
OMG.
It will never boot because it uses ART for arm.
Click to expand...
Click to collapse
Can we build this https://github.com/FlymeOS/manifest ?

TechGenius said:
Can we build this https://github.com/FlymeOS/manifest ?
Click to expand...
Click to collapse
Theoretically if use my AOSP 5.0.2 rom as base you will be able to port a FlymeOS.

tank0412 said:
Theoretically if use my AOSP 5.0.2 rom as base you will be able to port a FlymeOS.
Click to expand...
Click to collapse
Flyme OS is fluid if u can port will be nice

tank0412 said:
Theoretically if use my AOSP 5.0.2 rom as base you will be able to port a FlymeOS.
Click to expand...
Click to collapse
If i using libart.so from cm or something then will it boot?
I will upload this rom if it still bootloop then looking for help

jizz
it seems we need to disable ssse3 because dex2oat doesnt know what is ssse3
E/dex2oat ( 531): Unknown instruction set feature: 'ssse3'
E/dex2oat ( 531): Command: /system/bin/dex2oat --image=/data/dalvik-cache/x86/[email protected]@boot.art --dex-file=/system/framework/core-libart.jar --dex-file=/system/framework/conscrypt.jar --dex-file=/system/framework/okhttp.jar --dex-file=/system/framework/core-junit.jar --dex-file=/system/framework/bouncycastle.jar --dex-file=/system/framework/ext.jar --dex-file=/system/framework/framework.jar --dex-file=/system/framework/telephony-common.jar --dex-file=/system/framework/voip-common.jar --dex-file=/system/framework/ims-common.jar --dex-file=/system/framework/mms-common.jar --dex-file=/system/framework/android.policy.jar --dex-file=/system/framework/apache-xml.jar --dex-file=/system/framework/com.intel.config.jar --dex-file=/system/framework/com.intel.multidisplay.jar --oat-file=/data/dalvik-cache/x86/[email protected]@boot.oat --instruction-set=x86 --instruction-set-features=ssse3,movbe --base=0x703ac000 --runtime-arg -Xms64m --runtime-arg -Xmx64m --image-classes=/system/etc/preloaded-classes
E/dex2oat ( 531): Usage: dex2oat [options]...

HagameHyuma said:
jizz
it seems we need to disable ssse3 because dex2oat doesnt know what is ssse3
E/dex2oat ( 531): Unknown instruction set feature: 'ssse3'
E/dex2oat ( 531): Command: /system/bin/dex2oat --image=/data/dalvik-cache/x86/[email protected]@boot.art --dex-file=/system/framework/core-libart.jar --dex-file=/system/framework/conscrypt.jar --dex-file=/system/framework/okhttp.jar --dex-file=/system/framework/core-junit.jar --dex-file=/system/framework/bouncycastle.jar --dex-file=/system/framework/ext.jar --dex-file=/system/framework/framework.jar --dex-file=/system/framework/telephony-common.jar --dex-file=/system/framework/voip-common.jar --dex-file=/system/framework/ims-common.jar --dex-file=/system/framework/mms-common.jar --dex-file=/system/framework/android.policy.jar --dex-file=/system/framework/apache-xml.jar --dex-file=/system/framework/com.intel.config.jar --dex-file=/system/framework/com.intel.multidisplay.jar --oat-file=/data/dalvik-cache/x86/[email protected]@boot.oat --instruction-set=x86 --instruction-set-features=ssse3,movbe --base=0x703ac000 --runtime-arg -Xms64m --runtime-arg -Xmx64m --image-classes=/system/etc/preloaded-classes
E/dex2oat ( 531): Usage: dex2oat [options]...
Click to expand...
Click to collapse
Disable it in build.prop, change ssse3,movbe to default

tank0412 said:
Theoretically if use my AOSP 5.0.2 rom as base you will be able to port a FlymeOS.
Click to expand...
Click to collapse
Okay but your aosp 5.0.2 have a graphic problem
Android easter egg too is laging :/

dgadelha said:
Disable it in build.prop, change ssse3,movbe to default
Click to expand...
Click to collapse
still detected as ssse3
edit : after replacing dex2oat from original miui it's works but still getting crash issue
logcat : https://drive.google.com/file/d/0B5tYrl4qar2lem93WHctODFpNXc/view?usp=sharing

HagameHyuma said:
still detected as ssse3
edit : after replacing dex2oat from original miui it's works but still getting crash issue
logcat : https://drive.google.com/file/d/0B5tYrl4qar2lem93WHctODFpNXc/view?usp=sharing
Click to expand...
Click to collapse
Code:
JNI FatalError called: RegisterNatives failed for 'android/content/res/AssetManager'; aborting...
some libraries need to be replaced

art have too many error

dgadelha said:
Code:
JNI FatalError called: RegisterNatives failed for 'android/content/res/AssetManager'; aborting...
some libraries need to be replaced
Click to expand...
Click to collapse
what libs should i replace?if i surrender i will upload this rom and looking for help

HagameHyuma said:
what libs should i replace?if i surrender i will upload this rom and looking for help
Click to expand...
Click to collapse
Try to build flyme os. It will be better.

Esk1mOo said:
Try to build flyme os. It will be better.
Click to expand...
Click to collapse
I think MIUI is better but flyme os is more easy to do and is good to

marceloz5 said:
I think MIUI is better but flyme os is more easy to do and is good to
Click to expand...
Click to collapse
Yes, that's what I meant.

HagameHyuma said:
what libs should i replace?if i surrender i will upload this rom and looking for help
Click to expand...
Click to collapse
Try to replace the highest amount of libraries you can.
You can use my CM12.1 libraries as source.
You also need libmultidisplay.so for the multidisplay engine.
Don't forget /system/lib/hw/ libraries.

TechGenius said:
Okay but your aosp 5.0.2 have a graphic problem
Android easter egg too is laging :/
Click to expand...
Click to collapse
and what this: https://github.com/FlymeOS/manifest/tree/lollipop-5.1 this is for 5.1..
---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------
tank0412 said:
Theoretically if use my AOSP 5.0.2 rom as base you will be able to port a FlymeOS.
Click to expand...
Click to collapse
https://github.com/FlymeOS/manifest/tree/lollipop-5.1 and this? can be used vendor and system files from cm12.1 tree?

kihope12 said:
and what this: https://github.com/FlymeOS/manifest/tree/lollipop-5.1 this is for 5.1..
---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------
https://github.com/FlymeOS/manifest/tree/lollipop-5.1 and this? can be used vendor and system files from cm12.1 tree?
Click to expand...
Click to collapse
I will try to port flyme os if i surrender with miui

HagameHyuma said:
I will try to port flyme os if i surrender with miui
Click to expand...
Click to collapse
good, and are you porting or building from source?

Problems porting H2OS Oreo rom

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.

Problem Flashing new Android 11 magisk_patched.img

Hello, I'm trying to update my pixel 2xl to the latest Android 11 using Magisk Cannary 20426 and everytime I've tried to either patch boot.img or install the magisk,zip using TWP I'm getting this similar error in my `adb logcat`. I'm able to still aceess the phone after a failure to flash the new boot.img but flashing the stock. This means that I donot have root on my phone anymore.
Things I've tried:
Reinstalling the magisk app using cannary
different usb port / cable
updated platformtools
any advice to assist in debugging this would be greatly appreciated
Code:
12-31 19:42:47.054 2244 2244 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-31 19:42:47.054 2244 2244 F DEBUG : Build fingerprint: 'google/taimen/taimen:11/RP1A.200720.009/6720564:user/release-keys'
12-31 19:42:47.054 2244 2244 F DEBUG : Revision: 'rev_10'
12-31 19:42:47.054 2244 2244 F DEBUG : ABI: 'arm'
12-31 19:42:47.055 2244 2244 F DEBUG : Timestamp: 1969-12-31 19:42:47-0500
12-31 19:42:47.055 2244 2244 F DEBUG : pid: 2209, tid: 2209, name: app_process32 >>> /system/bin/app_process32 <<<
12-31 19:42:47.055 2244 2244 F DEBUG : uid: 0
12-31 19:42:47.055 2244 2244 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3
12-31 19:42:47.055 2244 2244 F DEBUG : Cause: null pointer dereference
12-31 19:42:47.055 2244 2244 F DEBUG : r0 00000003 r1 00000003 r2 00000000 r3 00000005
12-31 19:42:47.055 2244 2244 F DEBUG : r4 ff955690 r5 f646837c r6 00000300 r7 f5f42f50
12-31 19:42:47.055 2244 2244 F DEBUG : r8 00000003 r9 00000000 r10 f6468680 r11 f6468310
12-31 19:42:47.055 2244 2244 F DEBUG : ip 80000000 sp ff955618 lr f63dc38b pc f644595a
12-31 19:42:47.056 2244 2244 F DEBUG : backtrace:
12-31 19:42:47.056 2244 2244 F DEBUG : #00 pc 0008395a /apex/com.android.runtime/bin/linker!ld-android.so (offset 0x1a000) (__dl_strlen_a15+22) (BuildId: 24c8b5ac82b22718002810e56f914352)
12-31 19:42:47.056 2244 2244 F DEBUG : #01 pc 0001a387 /apex/com.android.runtime/bin/linker (__dl__ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEC2IDnEEPKc+18) (BuildId: 24c8b5ac82b22718002810e56f914352)
12-31 19:42:47.060 1203 1203 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
12-31 19:42:47.060 1267 1267 I ServiceManager: Waiting for service 'sensorservice' on '/dev/binder'...
12-31 19:42:47.060 2178 2240 D audio_hw_primary: out_set_parameters: enter: usecase(29: audio-playback-voip) kvpairs: routing=2
12-31 19:42:47.063 2185 2185 I AudioFlinger: openOutput() this 0x7c12bc8a30, module 10 Device type:0x10000,@:, SamplingRate 48000, Format 0x000001, Channels 0x3, flags 0x10000
12-31 19:42:47.063 2178 2240 E voice_extn: voice_extn_check_and_set_incall_music_usecase: Invalid session id 0
12-31 19:42:47.064 2185 2185 I AudioFlinger: HAL output buffer size 240 frames, normal sink buffer size 960 frames
12-31 19:42:47.065 2185 2185 E AudioFlinger: Failed to add event callback
12-31 19:42:47.065 2185 2251 I AudioFlinger: AudioFlinger's thread 0x7d94509040 tid=2251 ready to run
12-31 19:42:47.065 2185 2251 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.065 2185 2251 D AudioFlinger: ro.audio.silent is ignored since no output device is set
12-31 19:42:47.065 2185 2251 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.065 2185 2251 D AudioFlinger: ro.audio.silent is ignored since no output device is set
12-31 19:42:47.094 2178 2240 D audio_hw_primary: out_set_parameters: enter: usecase(31: incall-music-uplink) kvpairs: routing=65536
12-31 19:42:47.097 2185 2252 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2252 ready to run
12-31 19:42:47.097 2185 2252 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.098 2185 2252 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.099 2185 2254 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2254 ready to run
12-31 19:42:47.100 2185 2254 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.100 2185 2254 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.101 2185 2256 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2256 ready to run
12-31 19:42:47.101 2185 2256 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.101 2185 2256 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.101 2185 2185 E APM_AudioPolicyManager: onNewAudioModulesAvailableInt: Input device list is empty!
12-31 19:42:47.103 2244 2244 E crash_dump32: unable to connect to activity manager: Connection refused
12-31 19:42:47.103 2185 2259 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2259 ready to run
12-31 19:42:47.103 2185 2258 E FastThread: did not receive expected priority boost on time
12-31 19:42:47.103 928 928 E tombstoned: Tombstone written to: /data/tombstones/tombstone_17
12-31 19:42:47.103 2246 2246 I crash_dump64: performing dump of process 2208 (target tid = 2208)
12-31 19:42:47.108 2246 2246 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-31 19:42:47.108 2246 2246 F DEBUG : Build fingerprint: 'google/taimen/taimen:11/RP1A.200720.009/6720564:user/release-keys'
12-31 19:42:47.108 2246 2246 F DEBUG : Revision: 'rev_10'
12-31 19:42:47.108 2246 2246 F DEBUG : ABI: 'arm64'
12-31 19:42:47.109 2185 2261 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2261 ready to run
12-31 19:42:47.109 2246 2246 F DEBUG : Timestamp: 1969-12-31 19:42:47-0500
12-31 19:42:47.109 2246 2246 F DEBUG : pid: 2208, tid: 2208, name: app_process64 >>> /system/bin/app_process64 <<<
12-31 19:42:47.109 2246 2246 F DEBUG : uid: 0
12-31 19:42:47.109 2246 2246 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7e54c33f08
12-31 19:42:47.109 2185 2261 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.109 2246 2246 F DEBUG : x0 0000007bef61a210 x1 0000000000000101 x2 0000000000000000 x3 0000007e54891db8
12-31 19:42:47.109 2246 2246 F DEBUG : x4 0000000000000000 x5 0000007e55dc41a8 x6 f2aa9131d283ec11 x7 d61f0220f2c00fd1
12-31 19:42:47.109 2246 2246 F DEBUG : x8 0000007e54c34000 x9 0000000000000031 x10 0000007bef61a210 x11 0000000000000000
12-31 19:42:47.109 2246 2246 F DEBUG : x12 00000000000000c4 x13 f4beda67985e8bfb x14 0000000000000008 x15 0000000000000001
12-31 19:42:47.109 2246 2246 F DEBUG : x16 0000007e4ffda130 x17 0000007e54891f60 x18 0000007e54803c50 x19 95440998b0b39c01
12-31 19:42:47.109 2246 2246 F DEBUG : x20 0000007bef61a210 x21 0000007bef61a210 x22 0000007e54ad0000 x23 0000007e54ad0000
12-31 19:42:47.109 2246 2246 F DEBUG : x24 0000007e54748508 x25 0000007e5085edc2 x26 0000007e5087a000 x27 0000007d1f61128b
12-31 19:42:47.109 2246 2246 F DEBUG : x28 0000007e5085eda5 x29 0000007fc5dc2fe0
12-31 19:42:47.109 2246 2246 F DEBUG : lr 0000007e54891f98 sp 0000007fc5dc2f80 pc 0000007e54c33f08 pst 0000000000000000

trying this in the morning
https://forum.xda-developers.com/pixel-2-xl/help/stuck-flashing-patched-magisk-t4019013

Are you flashing the debug.zip (magisk)?
You could try changing the A/B slot.
Also, boot twrp.img, do not install it.

I dunno why people insist on doing things the hard way...moving the boot image to and from the device and patching it manually with magisk
If you fastboot TWRP, and just flash the magisk zip file, guess what it knows what to do and none of that slot swapping and other nonsense
Copy twrp-*.img and magisk-*.zip to folder on PC with platform tools (fastboot and adb etc), then:
Code:
ren magisk*.zip magisk.zip
ren twrp*.img twrp.img
adb reboot bootloader
fastboot boot twrp.img
adb push magisk.zip /tmp
adb shell twrp install /tmp/magisk.zip
adb reboot

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