Database Info

Browser not working on recent roms 32B

Hey there,
I did post about the issue I'd been having with all recent ROM's in the CyanogenMod thread, but am posting my own thread as I've seen no one else bring up the issue.
Essentially, on all ROM's I've tried since but not including nk02's 4.0, including CyanogenMod 3.9.x and nk02's 4.1.x, I cannot run the browser or anything dependant on it, like Market, opening email, completing the initial wizard.
This is the output of logcat while starting Browser:-
Code:
I/ActivityManager( 127): Starting activity: Intent { action=android.intent.acti
on.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com
.android.browser/com.android.browser.BrowserActivity} }
I/ActivityManager( 127): Start proc com.android.browser for activity com.androi
d.browser/.BrowserActivity: pid=404 uid=10034 gids={3003}
I/ActivityThread( 404): Publishing provider browser: com.android.browser.Browse
rProvider
I/DEBUG ( 108): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 108): Build fingerprint: 'tmobile/kila/dream/trout:1.5/CRC1/150275:
user/ota-rel-keys,release-keys'
I/DEBUG ( 108): pid: 404, tid: 416 >>> com.android.browser <<<
I/DEBUG ( 108): signal 11 (SIGSEGV), fault addr 010867e8
I/DEBUG ( 108): r0 45017a34 r1 001bfd9c r2 001cec24 r3 00000000
I/DEBUG ( 108): r4 001bfd9c r5 00000007 r6 00217e00 r7 aa073e55
I/DEBUG ( 108): r8 45017d9c r9 423afed8 10 423afec4 fp 00000001
I/DEBUG ( 108): ip 7fe00000 sp 45017a34 lr aa1c4739 pc 010867e8 cpsr 000
00010
D/dalvikvm( 404): GC freed 1976 objects / 148848 bytes in 134ms
I/DEBUG ( 108): #00 pc 010867e8
I/DEBUG ( 108): #01 pc 001c4736 /system/lib/libwebcore.so
I/DEBUG ( 108): stack:
I/DEBUG ( 108): 450179f4 00000001
I/DEBUG ( 108): 450179f8 00000000
I/DEBUG ( 108): 450179fc afe2defc /system/lib/libc.so
I/DEBUG ( 108): 45017a00 aa16fed3 /system/lib/libwebcore.so
I/DEBUG ( 108): 45017a04 aa16fec1 /system/lib/libwebcore.so
I/DEBUG ( 108): 45017a08 00000000
I/DEBUG ( 108): 45017a0c 001ceb28 [heap]
I/DEBUG ( 108): 45017a10 00000000
I/DEBUG ( 108): 45017a14 001cf4c8 [heap]
I/DEBUG ( 108): 45017a18 00000984
I/DEBUG ( 108): 45017a1c aa170389 /system/lib/libwebcore.so
I/DEBUG ( 108): 45017a20 00000000
I/DEBUG ( 108): 45017a24 001c0a08 [heap]
I/DEBUG ( 108): 45017a28 df002777
I/DEBUG ( 108): 45017a2c e3a070ad
I/DEBUG ( 108): 45017a30 00000000
I/DEBUG ( 108): #01 45017a34 001c0a08 [heap]
I/DEBUG ( 108): 45017a38 aa073e55 /system/lib/libwebcore.so
I/DEBUG ( 108): 45017a3c aa14bf1b /system/lib/libwebcore.so
I/DEBUG ( 108): 45017a40 001c0a08 [heap]
I/DEBUG ( 108): 45017a44 001bfd08 [heap]
I/DEBUG ( 108): 45017a48 001c0a08 [heap]
I/DEBUG ( 108): 45017a4c aa1aa761 /system/lib/libwebcore.so
I/DEBUG ( 108): 45017a50 001c0a08 [heap]
I/DEBUG ( 108): 45017a54 aa183c9b /system/lib/libwebcore.so
I/DEBUG ( 108): 45017a58 0000000a
I/DEBUG ( 108): 45017a5c 45017aa8
I/DEBUG ( 108): 45017a60 aa3db598 /system/lib/libwebcore.so
I/DEBUG ( 108): 45017a64 00000000
I/DEBUG ( 108): 45017a68 00000000
I/DEBUG ( 108): 45017a6c 00000000
I/DEBUG ( 108): 45017a70 00000000
I/DEBUG ( 108): 45017a74 00000000
I/DEBUG ( 108): 45017a78 00000000
I/ActivityManager( 127): Process com.android.browser (pid 404) has died.
I/WindowManager( 127): WIN DEATH: Window{438c7088 com.android.browser/com.andro
id.browser.BrowserActivity paused=false}
I/DEBUG ( 108): debuggerd committing suicide to free the zombie!
D/Zygote ( 110): Process 404 terminated by signal (11)
I/DEBUG ( 417): debuggerd: May 13 2009 19:02:52
W/InputManagerService( 127): Window already focused, ignoring focus gain of: co
[email protected]
D/dalvikvm( 208): GC freed 196 objects / 8496 bytes in 128ms
Any idea what could be causing this? My phone is running the 32B engineering SPL and RAv1.1.2 recovery. I have tried mounting over usb, adb, and putting the card in a reader to upload the update.zip to the card. I have tried wiping several times before flashing. I have tried different mSD cards, and using different computers to push the files. I am really stumped as to why I cannot run Browser yet seemingly everyone else with a 32B phone can.
I'm willing to test updates in an attempt to fix the problem. Any help really appreciated!

Using nk02's rom, this is the logcat output of the wizard after pressing next on the screen where it asks if google can collect location data. If I've not skipped giving it the google login details, the phone will get stuck on a screen saying 'Signed in!', with a dimmed next button. If I skip giving it the google login details, and attempt to pass the collect location data screen, it'll show 'Date & Time settings' briefly at the top before looping back to the sign in screen with the same output to logcat
Code:
I/ServiceStateTracker( 119): Auto time state changed
I/ActivityManager( 56): Starting activity: Intent { comp={com.android.settings
/com.android.settings.DateTimeSettingsSetupWizard} }
I/ActivityManager( 56): Start proc com.android.settings for activity com.andro
id.settings/.DateTimeSettingsSetupWizard: pid=445 uid=1000 gids={3002, 3001, 300
3}
D/dalvikvm( 34): GC freed 277 objects / 10448 bytes in 342ms
D/dalvikvm( 34): GC freed 42 objects / 1864 bytes in 164ms
D/dalvikvm( 34): GC freed 2 objects / 56 bytes in 187ms
I/DEBUG ( 325): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 325): Build fingerprint: 'google_ion/google_ion/sapphire/sapphire:1
.5/CRB43/148830:user/adp,test-keys'
I/DEBUG ( 325): pid: 445, tid: 445 >>> com.android.settings <<<
I/DEBUG ( 325): signal 4 (SIGILL), fault addr ad494ce8
I/DEBUG ( 325): r0 bef87f00 r1 bef87ee0 r2 00000000 r3 00000002
I/DEBUG ( 325): r4 001a78c4 r5 fff8df51 r6 ad4abbf8 r7 bef87778
I/DEBUG ( 325): r8 bef88124 r9 bef88124 10 ad4abdd0 fp ad4abdd0
I/DEBUG ( 325): ip ad4abf20 sp bef87698 lr ad496e3d pc ad494ce8 cpsr 800
00030
I/DEBUG ( 325): #00 pc 00094ce8 /system/lib/libicui18n.so
I/DEBUG ( 325): #01 lr ad496e3d /system/lib/libicui18n.so
I/DEBUG ( 325): stack:
I/DEBUG ( 325): bef87658 afe39dd0
I/DEBUG ( 325): bef8765c bef88124 [stack]
I/DEBUG ( 325): bef87660 ad4abdd0
I/DEBUG ( 325): bef87664 00000000
I/DEBUG ( 325): bef87668 bef87f00 [stack]
I/DEBUG ( 325): bef8766c 00000003
I/DEBUG ( 325): bef87670 001a78c4 [heap]
I/DEBUG ( 325): bef87674 ad533619 /system/lib/libicuuc.so
I/DEBUG ( 325): bef87678 00000000
I/DEBUG ( 325): bef8767c 00000000
I/DEBUG ( 325): bef87680 001a78a0 [heap]
I/DEBUG ( 325): bef87684 001a78c4 [heap]
I/DEBUG ( 325): bef87688 ad53a4a5 /system/lib/libicuuc.so
I/DEBUG ( 325): bef8768c 001a78c4 [heap]
I/DEBUG ( 325): bef87690 df002777
I/DEBUG ( 325): bef87694 e3a070ad
I/DEBUG ( 325): #00 bef87698 bef88124 [stack]
I/DEBUG ( 325): bef8769c 00000000
I/DEBUG ( 325): bef876a0 00000000
I/DEBUG ( 325): bef876a4 00000000
I/DEBUG ( 325): bef876a8 ffffffff
I/DEBUG ( 325): bef876ac 00000000
I/DEBUG ( 325): bef876b0 00000000
I/DEBUG ( 325): bef876b4 00000000
I/DEBUG ( 325): bef876b8 00000000
I/DEBUG ( 325): bef876bc 00000000
I/DEBUG ( 325): bef876c0 00000000
I/DEBUG ( 325): bef876c4 00000000
I/DEBUG ( 325): bef876c8 00000000
I/DEBUG ( 325): bef876cc 00000000
I/DEBUG ( 325): bef876d0 00000000
I/DEBUG ( 325): bef876d4 bef87c78 [stack]
I/DEBUG ( 325): bef876d8 000005b8
I/DEBUG ( 325): bef876dc 00000000
I/ActivityManager( 56): Process com.android.settings (pid 445) has died.
D/Zygote ( 34): Process 445 terminated by signal (4)
W/InputManagerService( 56): Window already focused, ignoring focus gain of: co
[email protected]
I/ActivityManager( 56): Displayed activity com.android.setupwizard/.CloseAndLa
unchActivity: 117600 ms
If anyone has any idea what I'm doing wrong can they please inform me. Is my phone faulty? Everything else appears to be working fine. The flash completes without errors and the phone boots into a usable state with all hardware functioning fine.
nk02's ROM is unusable as I cannot get past the setup wizard. It just respawns if I kill it.
I'd love to get this sorted as my phone is useless at the moment

Just had a similar issue with SuperD v1.8. Browser and market would crash on startup. Library file /system/lib/libwebcore.so was causing it due to corruption during rom flashing. Not sure why this suddenly started to happen but if you check the file size it is correct, but the md5sum will differ from one extracted from the rom zip file. I pushed the extracted library to /system/lib and it fixed the issue. Of course you have to do this with /system mounted r/w.
The only thing I can think of is the recovery image is causing it since unzipping this file on my linux box produces a working library. Unzipping from recovery produces a corrupt file.

Just had a similar issue with SuperD v1.8. Browser and market would crash on startup. Library file /system/lib/libwebcore.so was causing it due to corruption during rom flashing. Not sure why this suddenly started to happen but if you check the file size it is correct, but the md5sum will differ from one extracted from the rom zip file. I pushed the extracted library to /system/lib and it fixed the issue. Of course you have to do this with /system mounted r/w.
The only thing I can think of is the recovery image is causing it since unzipping this file on my linux box produces a working library. Unzipping from recovery produces a corrupt file.

tmusall said:
Just had a similar issue with SuperD v1.8. Browser and market would crash on startup. Library file /system/lib/libwebcore.so was causing it due to corruption during rom flashing. Not sure why this suddenly started to happen but if you check the file size it is correct, but the md5sum will differ from one extracted from the rom zip file. I pushed the extracted library to /system/lib and it fixed the issue. Of course you have to do this with /system mounted r/w.
The only thing I can think of is the recovery image is causing it since unzipping this file on my linux box produces a working library. Unzipping from recovery produces a corrupt file.
Click to expand...
Click to collapse
Here's what I tried:
Using fastboot erase the recovery partition. Again from fastboot flash recovery-RA-sapphire-v1.5.2G.img. This is for a myTouch 3G, so if you've got a G1 use the proper recovery image. Reboot.
Reboot into recovery and flashed rom NexusSuperD18.zip.
From adb shell:
md5sum of /system/lib/libwebcore.so - 96a7cef79de087111c84c76f50353b18 (Correct checksum)
Reboot and let rom initialize. Fire up Browser and is still crashes!
Reboot back to recovery and check md5sum again:
/system/lib # md5sum libwebcore.so
03e1950b02dd5fb1f00750065aea66d1 libwebcore.so (WRONG!)
Something during first boot initialization has corrupted this library. I've got no idea what is causing this, but for now the only way to get it working is to push a good library in its place.

[Q] Katkis 4.4.2 023c - Watch ESPN crashing

Been running this ROM for the last 3 weeks, works great. Couple of issues with GPS not working and occasional reboots but main issue is Watch ESPN app crashes after watching the video stream only for a couple of seconds. It is consistently crashing the same way everytime. I managed to grab a log cat, seems like a graphics driver issue. I suspect the following lines in the attached log file,
05-29 08:36:43.859 E/OMXNodeInstance(107): OMX_SetParameter() failed for StoreMetaDataInBuffers: 0x80001006
05-29 08:36:43.859 E/ACodec (3858): [OMX.Nvidia.h264.decode] storeMetaDataInBuffers failed w/ err -2147483648
leading to the following 40 lines later,
05-29 08:36:53.739 F/libc (3858): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4041 (MediaCodec_loop)
05-29 08:36:53.839 I/DEBUG (103): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-29 08:36:53.839 I/DEBUG (103): Build fingerprint: 'asus/US_epad/TF101:4.0.3/IML74K/US_epad-9.2.1.27-20120615:user/release-keys'
05-29 08:36:53.839 I/DEBUG (103): Revision: '0'
05-29 08:36:53.839 I/DEBUG (103): pid: 3858, tid: 4041, name: MediaCodec_loop >>> air.WatchESPN <<<
05-29 08:36:53.839 I/DEBUG (103): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
05-29 08:36:54.049 I/DEBUG (103): r0 fffffffc r1 00000000 r2 64c35040 r3 00000000
05-29 08:36:54.049 I/DEBUG (103): r4 64c04970 r5 64c04a60 r6 00000000 r7 64c04a64
05-29 08:36:54.049 I/DEBUG (103): r8 64c34c9d r9 5c63571c sl 624ede6c fp 00000001
05-29 08:36:54.049 I/DEBUG (103): ip 00000004 sp 64d37b58 lr 64c34c85 pc 00000000 cpsr 00000010
05-29 08:36:54.049 I/DEBUG (103): d0 0000000000000000 d1 0000000000000000
05-29 08:36:54.049 I/DEBUG (103): d2 33d6bf9500000000 d3 000000003f800000
05-29 08:36:54.049 I/DEBUG (103): d4 33d6bf953f800000 d5 0000000000000000
05-29 08:36:54.049 I/DEBUG (103): d6 000000003f800000 d7 0000000000000000
05-29 08:36:54.049 I/DEBUG (103): d8 0000000000000000 d9 0000000000000000
05-29 08:36:54.049 I/DEBUG (103): d10 0000000000000000 d11 0000000000000000
05-29 08:36:54.059 I/DEBUG (103): d12 0000000000000000 d13 0000000000000000
05-29 08:36:54.059 I/DEBUG (103): d14 0000000000000000 d15 0000000000000000
05-29 08:36:54.059 I/DEBUG (103): scr 20000013
Any suggestions on what to do are much appreciated (perhaps a newer DEV version like 029 or something).
Thanks much.

Try KK #24 non-Linaro build - that seems to sort out app / game crashes
http://downloads.timduru.org/android/tf101/K.A.T/KatKiss/4.4/dev/KatKiss-4.4.2_024-NonLinaro.zip

*Detection* said:
Try KK #24 non-Linaro build - that seems to sort out app / game crashes
h t t p : / / downloads.timduru.org/android/tf101/K.A.T/KatKiss/4.4/dev/KatKiss-4.4.2_024-NonLinaro.zip
Click to expand...
Click to collapse
No luck, I tried this ROM you suggested, Watch ESPN still crashes after a few seconds of watching any LIVE event.

Sorry no idea then, I can't test it being in the UK, it needs a US provider login

dhruwa said:
05-29 08:36:53.739 F/libc (3858): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4041 (MediaCodec_loop)
05-29 08:36:53.839 I/DEBUG (103): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-29 08:36:53.839 I/DEBUG (103): Build fingerprint: 'asus/US_epad/TF101:4.0.3/IML74K/US_epad-9.2.1.27-20120615:user/release-keys'
05-29 08:36:53.839 I/DEBUG (103): Revision: '0'
05-29 08:36:53.839 I/DEBUG (103): pid: 3858, tid: 4041, name: MediaCodec_loop >>> air.WatchESPN <<<
05-29 08:36:53.839 I/DEBUG (103): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
05-29 08:36:54.049 I/DEBUG (103): r0 fffffffc r1 00000000 r2 64c35040 r3 00000000
05-29 08:36:54.049 I/DEBUG (103): r4 64c04970 r5 64c04a60 r6 00000000 r7 64c04a64
05-29 08:36:54.049 I/DEBUG (103): r8 64c34c9d r9 5c63571c sl 624ede6c fp 00000001
05-29 08:36:54.049 I/DEBUG (103): ip 00000004 sp 64d37b58 lr 64c34c85 pc 00000000 cpsr 00000010
05-29 08:36:54.049 I/DEBUG (103): d0 0000000000000000 d1 0000000000000000
05-29 08:36:54.049 I/DEBUG (103): d2 33d6bf9500000000 d3 000000003f800000
05-29 08:36:54.049 I/DEBUG (103): d4 33d6bf953f800000 d5 0000000000000000
05-29 08:36:54.049 I/DEBUG (103): d6 000000003f800000 d7 0000000000000000
05-29 08:36:54.049 I/DEBUG (103): d8 0000000000000000 d9 0000000000000000
05-29 08:36:54.049 I/DEBUG (103): d10 0000000000000000 d11 0000000000000000
05-29 08:36:54.059 I/DEBUG (103): d12 0000000000000000 d13 0000000000000000
05-29 08:36:54.059 I/DEBUG (103): d14 0000000000000000 d15 0000000000000000
05-29 08:36:54.059 I/DEBUG (103): scr 20000013
Any suggestions on what to do are much appreciated (perhaps a newer DEV version like 029 or something).
Thanks much.
Click to expand...
Click to collapse
Looks like the same issue than NetFlix,
it should not crash anymore with the next KatKiss version 026
Test and report back when I post the new version

*Detection* said:
Sorry no idea then, I can't test it being in the UK, it needs a US provider login
Click to expand...
Click to collapse
No problem. Appreciate looking at it. Thanks.

timduru said:
Looks like the same issue than NetFlix,
it should not crash anymore with the next KatKiss version 026
Test and report back when I post the new version
Click to expand...
Click to collapse
Super!! Will wait for 026 stable. Will it also bring a functional ART runtime
Keep up the good work timduru !!.

timduru said:
Looks like the same issue than NetFlix,
it should not crash anymore with the next KatKiss version 026
Test and report back when I post the new version
Click to expand...
Click to collapse
I'm happy to report that Watch ESPN works now with no crashing after I flashed the latest KatKiss 028 stable ROM. Thanks a lot.

Recent Broadcom driver for >4.4.4 ROMs

Said ahead, I would have posted this in http://forum.xda-developers.com/galaxy-s2-plus/orig-development/rom-cyanogenmod-12-1-t3084287 where it belonged, since the bug was reproduced on that ROM, if it wasn't for that stupid "You must spam 10 times before you may properly report bugs" setting on this forum.
There appears to be some crashes in Chromium in >4.4.4 ROMs, related to this:
https://code.google.com/p/chromium/...er_bug_list_json.cc&sq=package:chromium&l=913
These crashes can be triggered by aggressive scrolling in either Chromium itself or any application utilizing libwebviewchromium.so. It will produce something along the lines of:
Code:
E/chromium( 4906): [ERROR:gl_renderer.cc(466)] Reached limit of pending sync queries.
--- snip, several repetions ---
E/chromium( 4906): [ERROR:gl_renderer.cc(466)] Reached limit of pending sync queries.
E/chromium( 4906): [ERROR:gl_fence_egl.cc(34)] Failed to get EGLSync attribute. error code:12300
E/chromium( 4906): [ERROR:gl_fence_egl.cc(50)] Failed to wait for EGLSync. error:EGL_BAD_PARAMETER
F/chromium( 4906): [FATAL:gl_fence_egl.cc(52)] Check failed: g_ignore_egl_sync_failures.
W/google-breakpad( 5032): -----BEGIN BREAKPAD MICRODUMP-----
W/google-breakpad( 5032): V WebView:45.0.2454.95
--- snip ---
F/libc ( 4906): Fatal signal 6 (SIGABRT), code -6 in tid 4961 (RenderThread)
I/DEBUG ( 146): property debug.db.uid not set; NOT waiting for gdb.
I/DEBUG ( 146): HINT: adb shell setprop debug.db.uid 100000
I/DEBUG ( 146): HINT: adb forward tcp:5039 tcp:5039
I/DEBUG ( 146): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 146): Build fingerprint: 'samsung/s2vepxx/s2vep:4.2.2/JDQ39/I9105PXXUBNG1:user/release-keys'
I/DEBUG ( 146): Revision: '5'
I/DEBUG ( 146): ABI: 'arm'
I/DEBUG ( 146): pid: 4906, tid: 4961, name: RenderThread >>> com.google.android.gm <<<
I/DEBUG ( 146): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 146): Abort message: '[FATAL:gl_fence_egl.cc(52)] Check failed: g_ignore_egl_sync_failures.
I/DEBUG ( 146): '
I/DEBUG ( 146): r0 00000000 r1 00001361 r2 00000006 r3 00000000
I/DEBUG ( 146): r4 52ea8dd8 r5 00000006 r6 00000016 r7 0000010c
I/DEBUG ( 146): r8 402c4de4 r9 52ea7ff4 sl 00000000 fp 000001eb
I/DEBUG ( 146): ip 00001361 sp 52ea7b48 lr 40280c59 pc 402a67fc cpsr 600f0010
I/DEBUG ( 146):
I/DEBUG ( 146): backtrace:
I/DEBUG ( 146): #00 pc 000397fc /system/lib/libc.so (tgkill+12)
I/DEBUG ( 146): #01 pc 00013c55 /system/lib/libc.so (pthread_kill+52)
I/DEBUG ( 146): #02 pc 000149b3 /system/lib/libc.so (raise+10)
I/DEBUG ( 146): #03 pc 000110ed /system/lib/libc.so (__libc_android_abort+36)
I/DEBUG ( 146): #04 pc 0000f5cc /system/lib/libc.so (abort+4)
I/DEBUG ( 146): #05 pc 002b8bf9 /data/app/com.google.android.webview-1/lib/arm/libwebviewchromium.so
The "EGL_KHR_fence_sync" EGL extension is supposed to be fixed in all Broadcom based devices shipping with Android >4.4.4. Obviously this isn't the case with this platform, as the driver fix got never backported.
There is no point in reporting this upstream to the Chromium team. So .... what to do?
EDIT:
OK....
The broken extension is announced in /vendor/lib/egl/libGLES_vc4.so @0x6F78A-0x6F79C
Somebody is probably going to smack me for suggesting to fiddle around in binary content, but it looks like the sanest approach to fix the bug.
Copy 0x1F bytes from (src start) 0x6F79D to (dest start) 0x6F78A (beware of overlap when performing the copy)
Set 0x13 bytes to 0x00 at (start) 0x6F7A9
That removes the extension from the string, moves the trailing extension list forward, and fills the resulting gap with null bytes in order not to break alignment.
The extension isn't mandatory, the existing implementation is broken, so let's just get rid of that thing.
Change is not tested yet. Someone feel like trying?
EDIT2:
That thing isn't as easy to deactivate as I expected. And it turns out, it actually is a mandatory feature in EGL 1.5 ...
But if the driver isn't announcing it any longer, who is then? Broken software emulation as well?
Next step: Patching it out of libwebviewchromium.so, getting that Android <=4.4.4 workaround back in.
EDIT3:
Meh, too much work for me. Then it's back to <=4..4.4 for me. May someone else try to work around that bug.

Xiaomi redmi 7A apps crash

Hello guys ,this is just a request,does anyone know how to solve issue with xiaomi redmi 7A apps crashing?!It has android 10 and miui 12.0.1 update.
It gives this error message:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/pine/pine:10/QKQ1.191014.001/V12.0.1.0.QCMMIXM:user/release-keys'
Revision: '0'
ABI: 'arm'
Timestamp: 2021-03-23 04:46:54+0100
pid: 9437, tid: 9437, name: miui.msa.global >>> com.miui.msa.global <<<
uid: 10111
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
r0 beeab4fc r1 85e834da r2 00000000 r3 00000006
r4 00000003 r5 00000000 r6 beeab4fc r7 3c444a70
r8 897cace4 r9 3c427064 r10 3c42706c r11 3c408088
ip 00000002 sp beeab4f8 lr 877b4ba1 pc 8840ceba
backtrace:
#00 pc 02919eba /data/app/com.google.android.trichromelibrary_438909030-5XbUikOv66vxlsu1GzkAwQ==/base.apk!libmonochrome.so (offset 0x645000) (BuildId: 98fedb7d52a7c50d74bd90494d1bac32f1fc82e9)

Can someone tell me what file from system/libs or any other folder is causing this error on my custom ROM

I'm not able to play videos on google without it glitching out, I just think it's an open GL error but im not rly sure, does someone knows about 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)