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.

[ROM]{WIP} CyanogenMod 12.1 for ZTE Blade Vec (4G) (DEV Support needed!)

CyanogenMod 12.1 (Android 5.1.1) for ZTE Blade Vec (4G)
Bugs
- Camera not working at all.
- CPU-Z application doesn't start and causes sensor failure.
- Sensors stops working randomly, and fixes itself randomly too.
- If the screen turns off while call, there's no way to turn it on unless end the call.
- Maybe more? You tell me.
How to flash
First of all, you need TWRPv2.8.7.0 installed for your device.
- Just do factory reset and flash the zip via TWRP. No need to flash gapps, included already.
Download: http://d-h.st/KFIp
Technical details for bugs
- For camera; All libraries loads successfully, but when I try to access the camera, it crashes. There's something wrong while setting parameters during startup. Here's the log;
Code:
E/QCameraParameters( 234): Invalid preview size requested: -1x-1
E/QCameraParameters( 234): No Record Size requested, use the preview dimensions
E/QCameraParameters( 234): Invalid video size requested: -1x-1
E/QCameraParameters( 234): Invalid picture size requested: -1x-1
E/QCameraParameters( 234): Invalid preview format value: NULL
E/QCameraParameters( 234): Invalid picture format value: NULL
D/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setJpegThumbnailSize(const qcamera::QCameraParameters&): Could not find optimal size
E/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setJpegQuality(const qcamera::QCameraParameters&): Invalid jpeg quality=-1
E/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setJpegQuality(const qcamera::QCameraParameters&): Invalid jpeg thumbnail quality=-1
D/QCameraParameters( 234): Param m_bNoDisplayMode = 0
E/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setPreviewFpsRange(const qcamera::QCameraParameters&): FpsRange Values:(7500, 30000)
E/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setPreviewFpsRange(const qcamera::QCameraParameters&): Requested FpsRange Values:(-1, -1)
E/QCameraParameters( 234): bool qcamera::QCameraParameters::UpdateHFRFrameRate(const qcamera::QCameraParameters&): CameraParameters - : minFps = 7500, maxFps = 30000
E/QCameraParameters( 234): bool qcamera::QCameraParameters::UpdateHFRFrameRate(const qcamera::QCameraParameters&): Requested params - : minFps = -1, maxFps = -1
E/QCameraParameters( 234): bool qcamera::QCameraParameters::UpdateHFRFrameRate(const qcamera::QCameraParameters&): prevHfrStr - off, hfrStr = (null)
E/QCameraParameters( 234): HFR mode is OFF
E/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setPreviewFpsRange(const qcamera::QCameraParameters&): UpdateHFRFrameRate 0
E/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setPreviewFpsRange(const qcamera::QCameraParameters&): error: FPS range value not supported
D/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setBrightness(const qcamera::QCameraParameters&): Brigtness not set by App
E/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setZoom(const qcamera::QCameraParameters&): invalid value -1 out of (0, 60)
D/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setSharpness(const qcamera::QCameraParameters&): Sharpness not set by App
D/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setSaturation(const qcamera::QCameraParameters&): Saturation not set by App
D/QCameraParameters( 234): int32_t qcamera::QCameraParameters::setContrast(const qcamera::QCameraParameters&): Contrast not set by App
--------- beginning of crash
F/libc ( 234): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 1226 (Binder_2)
I/DEBUG ( 231): property debug.db.uid not set; NOT waiting for gdb.
I/DEBUG ( 231): HINT: adb shell setprop debug.db.uid 100000
I/DEBUG ( 231): HINT: adb forward tcp:5039 tcp:5039
I/DEBUG ( 231): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 231): Build fingerprint: 'zte/cm_bladevec4g/unknown:5.1.1/LVY48C/57ccd15130:userdebug/test-keys'
I/DEBUG ( 231): Revision: '0'
I/DEBUG ( 231): ABI: 'arm'
I/DEBUG ( 231): pid: 234, tid: 1226, name: Binder_2 >>> /system/bin/mediaserver <<<
I/DEBUG ( 231): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
I/DEBUG ( 231): r0 00000000 r1 b6b0d320 r2 00000067 r3 00000001
I/DEBUG ( 231): r4 b5f73e04 r5 00000000 r6 ffffffff r7 00000000
I/DEBUG ( 231): r8 b3504b30 r9 b74ad624 sl b74ada30 fp b3504dd0
I/DEBUG ( 231): ip b6b0d320 sp b3504ae8 lr b5f61577 pc b6deb274 cpsr a00f0010
I/DEBUG ( 231):
I/DEBUG ( 231): backtrace:
I/DEBUG ( 231): #00 pc 00010274 /system/lib/libc.so (strcmp+48)
I/DEBUG ( 231): #01 pc 0002f573 /system/lib/hw/camera.msm8226.so (qcamera::QCameraParameters::setFocusMode(qcamera::QCameraParameters const&)+50)
I/DEBUG ( 231): #02 pc 000315a7 /system/lib/hw/camera.msm8226.so (qcamera::QCameraParameters::updateParameters(qcamera::QCameraParameters&, bool&)+382)
I/DEBUG ( 231): #03 pc 0001cf0b /system/lib/hw/camera.msm8226.so (qcamera::QCamera2HardwareInterface::updateParameters(char const*, bool&)+66)
I/DEBUG ( 231): #04 pc 00021071 /system/lib/hw/camera.msm8226.so (qcamera::QCameraStateMachine::procEvtPreviewStoppedState(qcamera::qcamera_sm_evt_enum_t, void*)+196)
I/DEBUG ( 231): #05 pc 0002283d /system/lib/hw/camera.msm8226.so (qcamera::QCameraStateMachine::smEvtProcRoutine(void*)+136)
I/DEBUG ( 231): #06 pc 0001552b /system/lib/libc.so (__pthread_start(void*)+38)
I/DEBUG ( 231): #07 pc 0001252b /system/lib/libc.so (__start_thread+10)
I/DEBUG ( 231):
I/DEBUG ( 231): Tombstone written to: /data/tombstones/tombstone_04
- for CPU-Z; Sensor causing hang up the application.
- for Sensors; I really don't know what's the problem. I think we need a better sensor hal. I'll provide a log for this soon.
- for Calls; Proximity sensor doesn't report 0, or system can't get it.
Source
https://github.com/forumber

Anybody can help he? I'd help but I don't know about.
Enviado desde mi TURKCELL T50 mediante Tapatalk

GuilleBetico96 said:
Anybody can help he? I'd help but I don't know about.
Enviado desde mi TURKCELL T50 mediante Tapatalk
Click to expand...
Click to collapse
Unfortunately, I also face similar problems
δυστυχως παρόμοια προβλήματα αντιμετοπίζω και εγω

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.

Warning for 8.0 upgrade

Some of you may experience "bluetooth" not able to start after upgrading to oero (8.0) like me. It was because, your device was bricked and recovered. Bricking and restore erase your BT MAC address and Oero enforced address checking of bluetooth. And resulting errors. An wearos watch without bluetooth is essential useless, and you are not given choices to upgrade or not.
If any one has any information to fix this address, please share with us. And you are more than welcome to share your efs partition with me, I need a bluetooth version efs partition.
Code:
04-05 00:44:27.745 W//system/bin/hwservicemanager( 267): getTransportFromManifest: Cannot find entry [email protected]::IBluetoothHci in either framework or device manifest, using default transport.
04-05 00:44:27.753 I/bt_hci ( 5625): hci_initialize: IBluetoothHci::getService() returned 0xa6c63680 (local)
04-05 00:44:27.753 I/[email protected]( 5625): BluetoothHci::initialize()
04-05 00:44:27.756 D/ ( 5625): get_local_address: Trying /nvdata/MACBT
04-05 00:44:27.756 F/zygote ( 5625): bluetooth_address.cc:58] Check failed: bytes_read == kStringLength
04-05 00:44:27.757 F/libc ( 5625): Fatal signal 6 (SIGABRT), code -6 in tid 5657 (hci_thread)
04-05 00:44:27.889 I/PackageManager.DexOptimizer( 437): Running dexopt (dexoptNeeded=1) on: /data/app/vmdl136066528.tmp/base.apk pkg=com.google.android.marvin.talkback isa=arm dexoptFlags=boot_complete,public target-filter=quicken oatDir=/data/app/vmdl136066528.tmp/oat sharedLibraries=/system/framework/com.google.android.wearable.jar
04-05 00:44:27.909 I/crash_dump32( 5662): obtaining output fd from tombstoned
04-05 00:44:27.911 I//system/bin/tombstoned( 349): received crash request for pid 5625
04-05 00:44:27.923 I/crash_dump32( 5662): performing dump of process 5625 (target tid = 5657)
04-05 00:44:27.923 F/DEBUG ( 5662): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-05 00:44:27.924 F/DEBUG ( 5662): Build fingerprint: 'huawei/sawfish/sawfish:8.0.0/OWDD.180215.018/4632152:user/release-keys'
04-05 00:44:27.924 F/DEBUG ( 5662): Revision: '0'
04-05 00:44:27.924 F/DEBUG ( 5662): ABI: 'arm'
04-05 00:44:27.924 F/DEBUG ( 5662): pid: 5625, tid: 5657, name: hci_thread >>> com.android.bluetooth <<<
04-05 00:44:27.924 F/DEBUG ( 5662): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
04-05 00:44:27.936 F/DEBUG ( 5662): Abort message: 'bluetooth_address.cc:58] Check failed: bytes_read == kStringLength '
04-05 00:44:27.936 F/DEBUG ( 5662): r0 00000000 r1 00001619 r2 00000006 r3 00000008
04-05 00:44:27.936 F/DEBUG ( 5662): r4 000015f9 r5 00001619 r6 9ec68a60 r7 0000010c
04-05 00:44:27.936 F/DEBUG ( 5662): r8 9ec68ca0 r9 9ec68c70 sl 9ec68d18 fp 9ec68d60
04-05 00:44:27.936 F/DEBUG ( 5662): ip 00000000 sp 9ec68a50 lr b209a407 pc b20ca96c cpsr 200b0010
04-05 00:44:28.214 F/DEBUG ( 5662):
04-05 00:44:28.214 F/DEBUG ( 5662): backtrace:
04-05 00:44:28.214 F/DEBUG ( 5662): #00 pc 0004a96c /system/lib/libc.so (tgkill+12)
04-05 00:44:28.214 F/DEBUG ( 5662): #01 pc 0001a403 /system/lib/libc.so (abort+54)
04-05 00:44:28.215 F/DEBUG ( 5662): #02 pc 0000752b /system/lib/libbase.so (_ZN7android4base14DefaultAborterEPKc+6)
04-05 00:44:28.215 F/DEBUG ( 5662): #03 pc 00007e09 /system/lib/libbase.so (_ZN7android4base10LogMessageD2Ev+456)
04-05 00:44:28.215 F/DEBUG ( 5662): #04 pc 0000637b /system/vendor/lib/hw/[email protected] (_ZN7android8hardware9bluetooth4V1_014implementation16BluetoothAddress17get_local_addressEPh+378)
04-05 00:44:28.215 F/DEBUG ( 5662): #05 pc 0000685d /system/vendor/lib/hw/[email protected] (_ZN7android8hardware9bluetooth4V1_014implementation15VendorInterface4OpenENSt3__18functionIFvbEEENS6_IFvRKNS0_8hidl_vecIhEEEEESE_SE_+60)
04-05 00:44:28.215 F/DEBUG ( 5662): #06 pc 000067a1 /system/vendor/lib/hw/[email protected] (_ZN7android8hardware9bluetooth4V1_014implementation15VendorInterface10InitializeENSt3__18functionIFvbEEENS6_IFvRKNS0_8hidl_vecIhEEEEESE_SE_+136)
04-05 00:44:28.215 F/DEBUG ( 5662): #07 pc 00005303 /system/vendor/lib/hw/[email protected] (_ZN7android8hardware9bluetooth4V1_014implementation12BluetoothHci10initializeERKNS_2spINS2_22IBluetoothHciCallbacksEEE+482)
04-05 00:44:28.216 F/DEBUG ( 5662): #08 pc 00015ce7 /system/lib/[email protected] (_ZN7android8hardware9bluetooth4V1_014BsBluetoothHci10initializeERKNS_2spINS2_22IBluetoothHciCallbacksEEE+242)
04-05 00:44:28.216 F/DEBUG ( 5662): #09 pc 0009eec7 /system/lib/hw/bluetooth.default.so (_Z14hci_initializev+258)
04-05 00:44:28.216 F/DEBUG ( 5662): #10 pc 0007ed63 /system/lib/libchrome.so (_ZN4base5debug13TaskAnnotator7RunTaskEPKcRKNS_11PendingTaskE+122)
04-05 00:44:28.216 F/DEBUG ( 5662): #11 pc 0008f637 /system/lib/libchrome.so (_ZN4base11MessageLoop7RunTaskERKNS_11PendingTaskE+162)
04-05 00:44:28.216 F/DEBUG ( 5662): #12 pc 0008f825 /system/lib/libchrome.so (_ZN4base11MessageLoop21DeferOrRunPendingTaskENS_11PendingTaskE+18)
04-05 00:44:28.216 F/DEBUG ( 5662): #13 pc 0008f9ff /system/lib/libchrome.so (_ZN4base11MessageLoop6DoWorkEv+190)
04-05 00:44:28.216 F/DEBUG ( 5662): #14 pc 000907af /system/lib/libchrome.so (_ZN4base18MessagePumpDefault3RunEPNS_11MessagePump8DelegateE+26)
04-05 00:44:28.216 F/DEBUG ( 5662): #15 pc 0009f835 /system/lib/libchrome.so (_ZN4base7RunLoop3RunEv+40)
04-05 00:44:28.216 F/DEBUG ( 5662): #16 pc 0009d6d3 /system/lib/hw/bluetooth.default.so (_Z16message_loop_runPv+162)
04-05 00:44:28.217 F/DEBUG ( 5662): #17 pc 0012aeab /system/lib/hw/bluetooth.default.so (_ZL18work_queue_read_cbPv+50)
04-05 00:44:28.217 F/DEBUG ( 5662): #18 pc 00129865 /system/lib/hw/bluetooth.default.so (_ZL11run_reactorP9reactor_ti+216)
04-05 00:44:28.217 F/DEBUG ( 5662): #19 pc 00129761 /system/lib/hw/bluetooth.default.so (_Z13reactor_startP9reactor_t+44)
04-05 00:44:28.217 F/DEBUG ( 5662): #20 pc 0012aa5d /system/lib/hw/bluetooth.default.so (_ZL10run_threadPv+136)
04-05 00:44:28.217 F/DEBUG ( 5662): #21 pc 00047c8f /system/lib/libc.so (_ZL15__pthread_startPv+22)
04-05 00:44:28.217 F/DEBUG ( 5662): #22 pc 0001afad /system/lib/libc.so (__start_thread+32)

My initial though is that system would usually assign a software generated mac address for missing mac address.
But 8.0 up seems not having this feature and thus BT is not usable. On the other hand, WIFI works flawlessly.

what if you flash the nougat stock rom? would be still lost?!

Kianush said:
what if you flash the nougat stock rom? would be still lost?!
Click to expand...
Click to collapse
nougat rom will be working fine. Although the mac address are still invalid, but the system will generate a mock up mac id.
So everything is fine to use. Just that it will keep update by itself.
One more finding, if I flash directly to android P from nougat, the BT will work initially, but not retaining for a few reboots or on/off BT setting.

If any one of you have root your device, would you please share the content (even with mask) of
/nvdata
All my files there are empty, and this would be the major cause of BT issue. I guess.

A work around or fix.
/nvdata/MACBT
you just put a mac address there in the format XX:XX:XX:XX:XX:XX
And it will be recorded and still valid after update.

[WIP] Building a custom ROM for the LeapFrog Epic (CM/LOS)

So, uh, I decided to spin this off to a new thread to keep the other ones from being bloated.
A few days ago I started work on getting at least CyanogenMod to work on the LeapFrog Epic, which runs off the same MT8127 SoC as certain variants of the Amazon Fire tablet amongst other things. CM11 was first on my agenda since it is close to the KitKat build that came from the factory, but compiler issues kept me from pushing on with this one. I then moved on to CM12.1, which was far less of a pain build-wise, but I then faced a number of issues that kept me from getting this to run. Fixed the MTK headers, and added a shim to get rid of that missing function error with the Mali drivers, but now I am stuck with this if I use the stock 1.1.95 libs that came with the Epic Academy Edition. Boot animation does not start at all:
Code:
I/SurfaceFlinger( 2317): SurfaceFlinger is starting
I/SurfaceFlinger( 2317): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 2317): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 2317): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 2317): loaded /system/lib/egl/libGLESv2_mali.so
W/libEGL ( 2317): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
I/[MALI][Gralloc]( 2317): gralloc UREE_CreateSession recount = 0
I/[MALI][Gralloc]( 2317): gralloc call UREE_CreateSession
I/[MALI][Gralloc]( 2317): UREE_CreateSession fail, ret = -65536
I/gralloc ( 2317): [Gralloc] refreshRate = 0, info.pixclock = ffffffff
I/gralloc ( 2317): [Gralloc] info.upper_margin = ffffffff, info.lower_margin = ffffffff
I/gralloc ( 2317): [Gralloc] info.yres = 258, info.hsync_len = ffffffff
I/gralloc ( 2317): [Gralloc] info.left_margin = ffffffff, info.right_margin = ffffffff
I/[MALI][Gralloc]( 2317): ro_dpi: 160.000000
I/[MALI][Gralloc]( 2317): using (fd=13)
I/[MALI][Gralloc]( 2317): id = mtkfb
I/[MALI][Gralloc]( 2317): xres = 1024 px
I/[MALI][Gralloc]( 2317): yres = 600 px
I/[MALI][Gralloc]( 2317): xres_virtual = 1024 px
I/[MALI][Gralloc]( 2317): yres_virtual = 1800 px
I/[MALI][Gralloc]( 2317): bpp = 32
I/[MALI][Gralloc]( 2317): r = 16:8
I/[MALI][Gralloc]( 2317): g = 8:8
I/[MALI][Gralloc]( 2317): b = 0:8
I/[MALI][Gralloc]( 2317): width = 163 mm (159.568100 dpi)
I/[MALI][Gralloc]( 2317): height = 95 mm (160.421051 dpi)
I/[MALI][Gralloc]( 2317): refresh rate = 60.00 Hz
I/[MALI][Gralloc]( 2317): init_framebuffer va: 0xb50f8000 mva: 0xb3700000
E/hwcomposer( 2317): [BLIT] sw_sync_timeline_create failed, aborting
F/libc ( 2317): Fatal signal 6 (SIGABRT), code -6 in tid 2317 (surfaceflinger)
I/DEBUG ( 129): property debug.db.uid not set; NOT waiting for gdb.
I/DEBUG ( 129): HINT: adb shell setprop debug.db.uid 100000
I/DEBUG ( 129): HINT: adb forward tcp:5039 tcp:5039
I/DEBUG ( 129): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 129): Build fingerprint: 'LeapFrog/cm_narnia/narnia:5.1.1/LMY49J/e2909bc29b:eng/test-keys'
I/DEBUG ( 129): Revision: '0'
I/DEBUG ( 129): ABI: 'arm'
I/DEBUG ( 129): pid: 2317, tid: 2317, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 129): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 129): r0 00000000 r1 0000090d r2 00000006 r3 00000000
I/DEBUG ( 129): r4 b6f34e38 r5 00000006 r6 0000000d r7 0000010c
I/DEBUG ( 129): r8 ffffffb4 r9 b5e01d8c sl b608f158 fp bec93a6c
I/DEBUG ( 129): ip 0000090d sp bec937e0 lr b6e8d8f5 pc b6eb08d0 cpsr 60010010
I/DEBUG ( 129):
I/DEBUG ( 129): backtrace:
I/DEBUG ( 129): #00 pc 000378d0 /system/lib/libc.so (tgkill+12)
I/DEBUG ( 129): #01 pc 000148f1 /system/lib/libc.so (pthread_kill+52)
I/DEBUG ( 129): #02 pc 0001564b /system/lib/libc.so (raise+10)
I/DEBUG ( 129): #03 pc 00011cc5 /system/lib/libc.so (__libc_android_abort+36)
I/DEBUG ( 129): #04 pc 0001005c /system/lib/libc.so (abort+4)
I/DEBUG ( 129): #05 pc 00010af9 /system/lib/hw/hwcomposer.mt8127.so (_ZN11BlitManagerC1Ev+140)
I/DEBUG ( 129): #06 pc 0000b8d9 /system/lib/hw/hwcomposer.mt8127.so (_ZN11HWCMediatorC2Ev+12)
I/DEBUG ( 129): #07 pc 0000ba5d /system/lib/hw/hwcomposer.mt8127.so (_ZN7android9SingletonI11HWCMediatorE11getInstanceEv+28)
I/DEBUG ( 129): #08 pc 0000bbfd /system/lib/hw/hwcomposer.mt8127.so
I/DEBUG ( 129): #09 pc 00023d17 /system/lib/libsurfaceflinger.so
I/DEBUG ( 129): #10 pc 00023a0b /system/lib/libsurfaceflinger.so
I/DEBUG ( 129): #11 pc 000195bb /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger4initEv+130)
I/DEBUG ( 129): #12 pc 00000af1 /system/bin/surfaceflinger
I/DEBUG ( 129): #13 pc 0000ff19 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 129): #14 pc 00000c08 /system/bin/surfaceflinger
I/DEBUG ( 129):
I/DEBUG ( 129): Tombstone written to: /data/tombstones/tombstone_08
If I use hwcomposer.mt8127.so, libgralloc_extra.so, libion_mtk.so and libtz_uree.so from @pix106's Lenovo Tab 2 A7-10F vendor tree, I get this additional message:
Code:
E/hwcomposer( 290): [BLIT] UREE_CreateSession failed (Non-specific cause.), aborting
I know there's probably only a few developers here who own a LeapFrog Epic, but I am at a loss here and any help would be very much appreciated. Yes I've read the Lenovo thread here before, but this one is a bit of a clincher, more so as I don't have complete kernel sources and I'm only building against a 3.4.67 kernel. My device tree's here, if anyone is interested: https://github.com/huckleberrypie/android_device_quanta_narnia

blakegriplingph said:
If I use hwcomposer.mt8127.so, libgralloc_extra.so, libion_mtk.so and libtz_uree.so from @pix106's Lenovo Tab 2 A7-10F vendor tree]
Click to expand...
Click to collapse
Tab2 has 3.10.54 kernel, I don't know if you can use these libs with a 3.4 kernel.
When missing a symbol, you can grep it in your device stock rom to find what lib provides it.
From a running device using adv, or using a stock room dumping your computer.
grep -r _Zazertyuiopqsdfghjklmwxcvbn /path/to/libs

pix106 said:
Tab2 has 3.10.54 kernel, I don't know if you can use these libs with a 3.4 kernel.
When missing a symbol, you can grep it in your device stock rom to find what lib provides it.
From a running device using adv, or using a stock room dumping your computer.
grep -r _Zazertyuiopqsdfghjklmwxcvbn /path/to/libs
Click to expand...
Click to collapse
Good call on the grep stuff. And I wonder if I could kang libs off another MT8127 device running KitKat which is a little tiny bit of a stretch to hunt for.

blakegriplingph said:
And I wonder if I could kang libs off another MT8127 device running KitKat which is a little tiny bit of a stretch to hunt for.
Click to expand...
Click to collapse
My "mistake", in a way : Tab2 also had KitKat with a 3.4 kernel, but I used kernel 3.10 and vendor from Lollipop stock rom to build cm-12.1.
You can try to download and extract lenovo's kk rom, or I can search my archives later and try to upload a KitKat stock rom dump somewhere, but I'm not home and have slow internet for now.

pix106 said:
My "mistake", in a way : Tab2 also had KitKat with a 3.4 kernel, but I used kernel 3.10 and vendor from Lollipop stock rom to build cm-12.1.
You can try to download and extract lenovo's kk rom, or I can search my archives later and try to upload a KitKat stock rom dump somewhere, but I'm not home and have slow internet for now.
Click to expand...
Click to collapse
3.4.67 I presume? I do have kernel sources for the Epic but it's missing a few things from what I've been told. The ROM dump does however have what appears to be a build config used by Quanta/LeapFrog to customise the board support package they used, or so I assume.

Apologies for the bump, and I hope they won't mind, but the likes of @superdragonpt are a lot more experienced with MTK than I could muster, so I was wondering if they could at least offer a bit of advice with this.

So I kanged hwcomposer from @pix106's dump of the A7-10F KitKat ROM, and it looks like I got something else other than the usual sw_sync_timeline failure:
Code:
I/SurfaceFlinger( 512): SurfaceFlinger is starting
I/SurfaceFlinger( 512): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 512): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 512): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 512): loaded /system/lib/egl/libGLESv2_mali.so
W/libEGL ( 512): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
I/[MALI][Gralloc]( 512): gralloc UREE_CreateSession recount = 0
I/[MALI][Gralloc]( 512): gralloc call UREE_CreateSession
I/[MALI][Gralloc]( 512): UREE_CreateSession fail, ret = -65536
I/gralloc ( 512): [Gralloc] refreshRate = 0, info.pixclock = ffffffff
I/gralloc ( 512): [Gralloc] info.upper_margin = ffffffff, info.lower_margin = ffffffff
I/gralloc ( 512): [Gralloc] info.yres = 258, info.hsync_len = ffffffff
I/gralloc ( 512): [Gralloc] info.left_margin = ffffffff, info.right_margin = ffffffff
I/[MALI][Gralloc]( 512): ro_dpi: 160.000000
I/[MALI][Gralloc]( 512): using (fd=13)
I/[MALI][Gralloc]( 512): id = mtkfb
I/[MALI][Gralloc]( 512): xres = 1024 px
I/[MALI][Gralloc]( 512): yres = 600 px
I/[MALI][Gralloc]( 512): xres_virtual = 1024 px
I/[MALI][Gralloc]( 512): yres_virtual = 1800 px
I/[MALI][Gralloc]( 512): bpp = 32
I/[MALI][Gralloc]( 512): r = 16:8
I/[MALI][Gralloc]( 512): g = 8:8
I/[MALI][Gralloc]( 512): b = 0:8
I/[MALI][Gralloc]( 512): width = 163 mm (159.568100 dpi)
I/[MALI][Gralloc]( 512): height = 95 mm (160.421051 dpi)
I/[MALI][Gralloc]( 512): refresh rate = 60.00 Hz
I/[MALI][Gralloc]( 512): init_framebuffer va: 0xb50f8000 mva: 0xb3700000
I/hwcomposer( 512): [DPY] Display Information:
I/hwcomposer( 512): [DPY] # fo devices : 1
I/hwcomposer( 512): [DPY] -----------------------------
I/hwcomposer( 512): [DPY] Device id : 0
I/hwcomposer( 512): [DPY] Width : 1024
I/hwcomposer( 512): [DPY] Height : 600
I/hwcomposer( 512): [DPY] xdpi : 160.000000
I/hwcomposer( 512): [DPY] ydpi : 160.000000
I/hwcomposer( 512): [DPY] vsync : 1
I/hwcomposer( 512): [DPY] refresh : 17179179
I/hwcomposer( 512): [DPY] connected : 1
I/hwcomposer( 512): [DPY] subtype : 0
W/hwcomposer( 512): [EVENT] Failed to open vsync device (Permission denied)
W/hwcomposer( 512): [EVENT] HW VSync State(0)
W/hwcomposer( 512): [EVENT] Start to listen uevent, addr.nl_pid(512)
I/6620_launcher( 124): Can't open device node(/dev/stpwmt)
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
I/SurfaceFlinger( 512): Using composer version 1.2
I/hwcomposer( 512): [HWC] getConfigs Display(0)
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
I/hwcomposer( 512): [HWC] getAttributes Display(0)
I/hwcomposer( 512): [HWC] getConfigs Display(1)
I/hwcomposer( 512): [HWC] getAttributes Display(1)
E/hwcomposer( 512): [HWC] Failed to get display attributes (dpy=1 is not connected)
W/SurfaceFlinger( 512): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 512): no suitable EGLConfig found, giving up
F/libc ( 512): Fatal signal 6 (SIGABRT), code -6 in tid 512 (surfaceflinger)
I/DEBUG ( 129): property debug.db.uid not set; NOT waiting for gdb.
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
I/DEBUG ( 129): HINT: adb shell setprop debug.db.uid 100000
I/DEBUG ( 129): HINT: adb forward tcp:5039 tcp:5039
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
I/DEBUG ( 129): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 129): Build fingerprint: 'LeapFrog/cm_narnia/narnia:5.1.1/LMY49J/e2909bc29b:eng/test-keys'
I/DEBUG ( 129): Revision: '0'
I/DEBUG ( 129): ABI: 'arm'
I/DEBUG ( 129): pid: 512, tid: 512, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 129): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 129): Abort message: 'no suitable EGLConfig found, giving up'
I/DEBUG ( 129): r0 00000000 r1 00000200 r2 00000006 r3 00000000
I/DEBUG ( 129): r4 b6fc1e38 r5 00000006 r6 00000000 r7 0000010c
I/DEBUG ( 129): r8 b6482000 r9 00000000 sl 00000000 fp 00000001
I/DEBUG ( 129): ip 00000200 sp be8d34a0 lr b6f1a8f5 pc b6f3d8d0 cpsr 60070010
I/DEBUG ( 129):
I/DEBUG ( 129): backtrace:
I/DEBUG ( 129): #00 pc 000378d0 /system/lib/libc.so (tgkill+12)
I/DEBUG ( 129): #01 pc 000148f1 /system/lib/libc.so (pthread_kill+52)
I/DEBUG ( 129): #02 pc 0001564b /system/lib/libc.so (raise+10)
I/DEBUG ( 129): #03 pc 00011cc5 /system/lib/libc.so (__libc_android_abort+36)
I/DEBUG ( 129): #04 pc 0001005c /system/lib/libc.so (abort+4)
I/DEBUG ( 129): #05 pc 00007a41 /system/lib/libcutils.so (__android_log_assert+88)
I/DEBUG ( 129): #06 pc 0002930d /system/lib/libsurfaceflinger.so
I/DEBUG ( 129): #07 pc 00028f09 /system/lib/libsurfaceflinger.so
I/DEBUG ( 129): #08 pc 000195e7 /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger4initEv+174)
I/DEBUG ( 129): #09 pc 00000af1 /system/bin/surfaceflinger
I/DEBUG ( 129): #10 pc 0000ff19 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 129): #11 pc 00000c08 /system/bin/surfaceflinger

blakegriplingph said:
So I kanged hwcomposer from @pix106's dump of the A7-10F KitKat ROM, and it looks like I got something else other than the usual sw_sync_timeline failure:
Code:
I/SurfaceFlinger( 512): SurfaceFlinger is starting
I/SurfaceFlinger( 512): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 512): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 512): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 512): loaded /system/lib/egl/libGLESv2_mali.so
W/libEGL ( 512): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
I/[MALI][Gralloc]( 512): gralloc UREE_CreateSession recount = 0
I/[MALI][Gralloc]( 512): gralloc call UREE_CreateSession
I/[MALI][Gralloc]( 512): UREE_CreateSession fail, ret = -65536
I/gralloc ( 512): [Gralloc] refreshRate = 0, info.pixclock = ffffffff
I/gralloc ( 512): [Gralloc] info.upper_margin = ffffffff, info.lower_margin = ffffffff
I/gralloc ( 512): [Gralloc] info.yres = 258, info.hsync_len = ffffffff
I/gralloc ( 512): [Gralloc] info.left_margin = ffffffff, info.right_margin = ffffffff
I/[MALI][Gralloc]( 512): ro_dpi: 160.000000
I/[MALI][Gralloc]( 512): using (fd=13)
I/[MALI][Gralloc]( 512): id = mtkfb
I/[MALI][Gralloc]( 512): xres = 1024 px
I/[MALI][Gralloc]( 512): yres = 600 px
I/[MALI][Gralloc]( 512): xres_virtual = 1024 px
I/[MALI][Gralloc]( 512): yres_virtual = 1800 px
I/[MALI][Gralloc]( 512): bpp = 32
I/[MALI][Gralloc]( 512): r = 16:8
I/[MALI][Gralloc]( 512): g = 8:8
I/[MALI][Gralloc]( 512): b = 0:8
I/[MALI][Gralloc]( 512): width = 163 mm (159.568100 dpi)
I/[MALI][Gralloc]( 512): height = 95 mm (160.421051 dpi)
I/[MALI][Gralloc]( 512): refresh rate = 60.00 Hz
I/[MALI][Gralloc]( 512): init_framebuffer va: 0xb50f8000 mva: 0xb3700000
I/hwcomposer( 512): [DPY] Display Information:
I/hwcomposer( 512): [DPY] # fo devices : 1
I/hwcomposer( 512): [DPY] -----------------------------
I/hwcomposer( 512): [DPY] Device id : 0
I/hwcomposer( 512): [DPY] Width : 1024
I/hwcomposer( 512): [DPY] Height : 600
I/hwcomposer( 512): [DPY] xdpi : 160.000000
I/hwcomposer( 512): [DPY] ydpi : 160.000000
I/hwcomposer( 512): [DPY] vsync : 1
I/hwcomposer( 512): [DPY] refresh : 17179179
I/hwcomposer( 512): [DPY] connected : 1
I/hwcomposer( 512): [DPY] subtype : 0
W/hwcomposer( 512): [EVENT] Failed to open vsync device (Permission denied)
W/hwcomposer( 512): [EVENT] HW VSync State(0)
W/hwcomposer( 512): [EVENT] Start to listen uevent, addr.nl_pid(512)
I/6620_launcher( 124): Can't open device node(/dev/stpwmt)
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
I/SurfaceFlinger( 512): Using composer version 1.2
I/hwcomposer( 512): [HWC] getConfigs Display(0)
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
I/hwcomposer( 512): [HWC] getAttributes Display(0)
I/hwcomposer( 512): [HWC] getConfigs Display(1)
I/hwcomposer( 512): [HWC] getAttributes Display(1)
E/hwcomposer( 512): [HWC] Failed to get display attributes (dpy=1 is not connected)
W/SurfaceFlinger( 512): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 512): no suitable EGLConfig found, giving up
F/libc ( 512): Fatal signal 6 (SIGABRT), code -6 in tid 512 (surfaceflinger)
I/DEBUG ( 129): property debug.db.uid not set; NOT waiting for gdb.
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
I/DEBUG ( 129): HINT: adb shell setprop debug.db.uid 100000
I/DEBUG ( 129): HINT: adb forward tcp:5039 tcp:5039
W/hwcomposer( 512): [WKR] Failed to set priority to RR: Operation not permitted
I/DEBUG ( 129): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 129): Build fingerprint: 'LeapFrog/cm_narnia/narnia:5.1.1/LMY49J/e2909bc29b:eng/test-keys'
I/DEBUG ( 129): Revision: '0'
I/DEBUG ( 129): ABI: 'arm'
I/DEBUG ( 129): pid: 512, tid: 512, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 129): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 129): Abort message: 'no suitable EGLConfig found, giving up'
I/DEBUG ( 129): r0 00000000 r1 00000200 r2 00000006 r3 00000000
I/DEBUG ( 129): r4 b6fc1e38 r5 00000006 r6 00000000 r7 0000010c
I/DEBUG ( 129): r8 b6482000 r9 00000000 sl 00000000 fp 00000001
I/DEBUG ( 129): ip 00000200 sp be8d34a0 lr b6f1a8f5 pc b6f3d8d0 cpsr 60070010
I/DEBUG ( 129):
I/DEBUG ( 129): backtrace:
I/DEBUG ( 129): #00 pc 000378d0 /system/lib/libc.so (tgkill+12)
I/DEBUG ( 129): #01 pc 000148f1 /system/lib/libc.so (pthread_kill+52)
I/DEBUG ( 129): #02 pc 0001564b /system/lib/libc.so (raise+10)
I/DEBUG ( 129): #03 pc 00011cc5 /system/lib/libc.so (__libc_android_abort+36)
I/DEBUG ( 129): #04 pc 0001005c /system/lib/libc.so (abort+4)
I/DEBUG ( 129): #05 pc 00007a41 /system/lib/libcutils.so (__android_log_assert+88)
I/DEBUG ( 129): #06 pc 0002930d /system/lib/libsurfaceflinger.so
I/DEBUG ( 129): #07 pc 00028f09 /system/lib/libsurfaceflinger.so
I/DEBUG ( 129): #08 pc 000195e7 /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger4initEv+174)
I/DEBUG ( 129): #09 pc 00000af1 /system/bin/surfaceflinger
I/DEBUG ( 129): #10 pc 0000ff19 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 129): #11 pc 00000c08 /system/bin/surfaceflinger
Click to expand...
Click to collapse
I would not know how to help you but maybe ggow who has compiled lineage 12.1 for amazon fire mt8127 can help you.

Rortiz2 said:
I would not know how to help you but maybe ggow who has compiled lineage 12.1 for amazon fire mt8127 can help you.
Click to expand...
Click to collapse
Does that one run on Kitkat originally? If anything, both the Epic and the MT8127 Amazon Fire tablets are made by the same ODM iirc. I might also try updating the blobs and kernel to version 1.8.45 to see if it helps any, but hwcomposer is apparently still the same.

blakegriplingph said:
Does that one run on Kitkat originally? If anything, both the Epic and the MT8127 Amazon Fire tablets are made by the same ODM iirc. I might also try updating the blobs and kernel to version 1.8.45 to see if it helps any, but hwcomposer is apparently still the same.
Click to expand...
Click to collapse
Amazon Fire tablets came with lollipop 5.1.
Have you tried to port the Rom instead of compiling? It is easier :/ . If you send me the stock bootimg and the stock system.img I can port you some ROM.

Rortiz2 said:
Amazon Fire tablets came with lollipop 5.1.
Have you tried to port the Rom instead of compiling? It is easier :/ . If you send me the stock bootimg and the stock system.img I can port you some ROM.
Click to expand...
Click to collapse
You sure you're able to port a ROM built for newer (prebuilt) kernel on a 3.4.67 device? The only sticking point so far with the LeapFrog CM12 port is hwcomposer/surfaceflinger refusing to cooperate. As of late I recompiled the ROM with no blobs kanged off other devices with the following flags added to BoardConfig:
Code:
TARGET_RUNNING_WITHOUT_SYNC_FRAMEWORK := true
BOARD_EGL_WORKAROUND_BUG_10194508 := true
...and ran logcat on it. Still the same sw_sync issues though it apparently has something to do with SELinux denying those requests as what the attached log seems to imply. It might be a red herring though, and I've read that @pix106 also ran into similar issues before with him trying a myriad of build flags in an attempt to fix this. Any ideas on what to use to get rid of this once and for all and finally get the damn GUI to boot? I'm thinking about using "BOARD_NEEDS_OLD_HWC_API := true" given how the blobs were for KitKat but what do you guys think? If only there were developers here who just happen to own an Epic lol.

...and I got a tiny bit further with the SELinux whitelist applied, though it's still the same "stuck on LeapFrog logo" moment with no sign of the boot animation springing to life. The backtrace mentions something along the lines of "buffer" in the functions called. Could it be that "BOARD_EGL_NEEDS_LEGACY_FB := true" is at fault here?
Also, there's an error in the log saying:
Code:
File size of 0 bytes not large enough to contain ELF header of 52 bytes: '/data/dalvik-cache/arm/[email protected]@boot.oat'

blakegriplingph said:
...and I got a tiny bit further with the SELinux whitelist applied, though it's still the same "stuck on LeapFrog logo" moment with no sign of the boot animation springing to life. The backtrace mentions something along the lines of "buffer" in the functions called. Could it be that "BOARD_EGL_NEEDS_LEGACY_FB := true" is at fault here?
Also, there's an error in the log saying:
Click to expand...
Click to collapse
I'd first check permission issues (/dev/stpwmt : iirc I had a few permission errors at early boot, but quick after it should be working fine), and nvram.

pix106 said:
I'd first check permission issues (/dev/stpwmt : iirc I had a few permission errors at early boot, but quick after it should be working fine), and nvram.
Click to expand...
Click to collapse
Care to explain even further? I'll have to check things on my other Epic to see if I got the permissions right (I have three Epics actually, one for development, one which I keep as stock for reference purposes and another as a parts unit).
Also, any ideas on why ART appears to be failing? Permissions issues as well I presume?

ART does seem to work, but for some reason /dev/stpwmt isn't being loaded properly despite it being declared on the init files. I can however load it manually through ADB shell. Also, even if I did seem to set the right permissions to the display drivers surfaceflinger crashes for a few times until the crash logs cease to show up, and I then get spammed with the following:
Code:
D/hwcomposer( 2058): [DPY] UEventThread::threadLoop poll return 1
I/hwcomposer( 2058): [DPY] UEventThread::threadLoop recv [email protected]/devices/platform/battery/power_supply/ac
D/hwcomposer( 2058): [DPY] handle_uevents : s = 0xb5ce2138, len = 191
D/hwcomposer( 2058): [DPY] UEventThread::threadLoop poll wait
D/hwcomposer( 2058): [DPY] UEventThread::threadLoop poll return 1
I/hwcomposer( 2058): [DPY] UEventThread::threadLoop recv [email protected]/devices/platform/battery/power_supply/usb
D/hwcomposer( 2058): [DPY] handle_uevents : s = 0xb5ce2138, len = 194
D/hwcomposer( 2058): [DPY] UEventThread::threadLoop poll wait
D/hwcomposer( 2058): [DPY] UEventThread::threadLoop poll return 1
I/hwcomposer( 2058): [DPY] UEventThread::threadLoop recv [email protected]/devices/platform/battery/power_supply/battery
D/hwcomposer( 2058): [DPY] handle_uevents : s = 0xb5ce2138, len = 794
D/hwcomposer( 2058): [DPY] UEventThread::threadLoop poll wait
I think the surfaceflinger crash may have something to do with the permissions being loaded a bit too late. Can anyone look into this?

blakegriplingph said:
Care to explain even further? I'll have to check things on my other Epic to see if I got the permissions right (I have three Epics actually, one for development, one which I keep as stock for reference purposes and another as a parts unit).
Also, any ideas on why ART appears to be failing? Permissions issues as well I presume?
Click to expand...
Click to collapse
I remember I had issues with this permission too, and maybe had to modify it from init.mt8127, among other permissions. Check my GitHub, check cm-12.1 branch, which was used as base for the CyanogenMod for Lenovo Tab2A710F repository ; you'll find the commits before cm finally booted.

pix106 said:
I remember I had issues with this permission too, and maybe had to modify it from init.mt8127, among other permissions. Check my GitHub, check cm-12.1 branch, which was used as base for the CyanogenMod for Lenovo Tab2A710F repository ; you'll find the commits before cm finally booted.
Click to expand...
Click to collapse
I'll check that one out. Permissions seem to be the thing that's keeping CM from booting up at all lol. If only LeapFrog did a Lollipop update for the Epic (like seriously, KitKat in 2019 wtf?) that would've saved me the trouble of hacking up fixes and whatnot.

Strange, I applied your edits to init.mt8127 yet /dev/stpwmt isn't being loaded automatically. And HWC/surfaceflinger still spazzes out with complaints about buffers or something along the lines of it. I don't know if I should just suck it up and throw the towel for now, but I've gone too far into this project that it would be a shame to just let it go.
That being said, is it possible to decompile sepolicy and kang whatever it is in there so I don't have to compile a whole list of things to whitelist? And I really do need people who own a LeapFrog Epic and are also interested in porting CM to this damn thing. It's a shot in the dark but I could use all the help I could muster right now.

Seems like we need to adapt what I saw on this repo as the MediatekHacks.cpp I threw in to fix the missing symbols issue may have accounted for why SurfaceFlinger isn't cooperating.
@pix106 - Did you by any chance use the repo I mentioned above when you built your ROM? I've used the vanilla CM android_frameworks_native repo for one and that may have accounted for why my ROM is spazzing out. Also, I saw a commit by thp1997 (along with a patch of similar intent by @Kirito96) which appears to be a patch/shim set for the MT6572 that seems to tackle the same issue as what I've been experiencing with the Epic. The crash log...
Code:
--------- beginning of crash
F/libc ( 127): Fatal signal 7 (SIGBUS), code 1, fault addr 0xb6400189 in tid 127 (surfaceflinger)
I/DEBUG ( 133): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 133): Build fingerprint: 'LeapFrog/cm_narnia/narnia:5.1.1/LMY49J/ad8cbe2f60:eng/test-keys'
I/DEBUG ( 133): Revision: '0'
I/DEBUG ( 133): ABI: 'arm'
I/DEBUG ( 133): pid: 127, tid: 127, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 133): signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0xb6400189
I/DEBUG ( 133): r0 ffffffff r1 b6400189 r2 00000005 r3 00000000
I/DEBUG ( 133): r4 b6400189 r5 ffffffff r6 be827298 r7 b60b30d0
I/DEBUG ( 133): r8 b6d6dc2c r9 be826db4 sl 00000000 fp 00000000
I/DEBUG ( 133): ip b6e02f38 sp be826d60 lr b6e68dbc pc b6e68dbc cpsr 80000010
I/DEBUG ( 133):
I/DEBUG ( 133): backtrace:
I/DEBUG ( 133): #00 pc 00003dbc /system/lib/libcutils.so (android_atomic_add+16)
I/DEBUG ( 133): #01 pc 0000d61f /system/lib/libutils.so (_ZNK7android7RefBase9decStrongEPKv+10)
I/DEBUG ( 133): #02 pc 00028f7b /system/lib/libgui.so (_ZN7android2spINS_13GraphicBufferEEaSERKS2_+22)
I/DEBUG ( 133): #03 pc 000290af /system/lib/libgui.so (_ZN7android19BufferQueueConsumer13acquireBufferEPNS_22IGraphicBufferConsumer10BufferItemEx+270)
I/DEBUG ( 133): #04 pc 0002c411 /system/lib/libgui.so (_ZN7android12ConsumerBase19acquireBufferLockedEPNS_22IGraphicBufferConsumer10BufferItemEx+16)
I/DEBUG ( 133): #05 pc 00023571 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #06 pc 00023679 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #07 pc 0002849b /system/lib/libgui.so (_ZN7android11BufferQueue21ProxyConsumerListener16onFrameAvailableERKNS_10BufferItemE+26)
I/DEBUG ( 133): #08 pc 0002ba2b /system/lib/libgui.so (_ZN7android19BufferQueueProducer11queueBufferEiRKNS_22IGraphicBufferProducer16QueueBufferInputEPNS1_17QueueBufferOutputE+562)
I/DEBUG ( 133): #09 pc 00037423 /system/lib/libgui.so (_ZN7android7Surface11queueBufferEP19ANativeWindowBufferi+254)
I/DEBUG ( 133): #10 pc 00036693 /system/lib/libgui.so (_ZN7android7Surface16hook_queueBufferEP13ANativeWindowP19ANativeWindowBufferi+10)
I/DEBUG ( 133): #11 pc 0000f720 /system/lib/libMali.so
I/DEBUG ( 133): #12 pc 00010218 /system/lib/libMali.so
I/DEBUG ( 133): #13 pc 0005e5d8 /system/lib/libMali.so
I/DEBUG ( 133): #14 pc 0005d70c /system/lib/libMali.so
I/DEBUG ( 133): #15 pc 0005bf58 /system/lib/libMali.so (shim_eglSwapBuffers+64)
I/DEBUG ( 133): #16 pc 000120d7 /system/lib/libEGL.so (eglSwapBuffers+290)
I/DEBUG ( 133): #17 pc 0000f541 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #18 pc 0001c187 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #19 pc 0001b367 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #20 pc 0001a6eb /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #21 pc 0001a459 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #22 pc 00011127 /system/lib/libutils.so (_ZN7android6Looper9pollInnerEi+410)
I/DEBUG ( 133): #23 pc 00011219 /system/lib/libutils.so (_ZN7android6Looper8pollOnceEiPiS1_PPv+92)
I/DEBUG ( 133): #24 pc 00017b95 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #25 pc 0001a04d /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger3runEv+8)
I/DEBUG ( 133): #26 pc 00000b4d /system/bin/surfaceflinger
I/DEBUG ( 133): #27 pc 0000ff19 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 133): #28 pc 00000c08 /system/bin/surfaceflinger
F/libc ( 261): Fatal signal 7 (SIGBUS), code 1, fault addr 0xffffffff in tid 261 (surfaceflinger)
I/DEBUG ( 133): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
...appears to allude to the ones mentioned in the patch files. Maybe this is the cure we needed, short of using a different HWC which I more or less doubt to be necessary.

blakegriplingph said:
Seems like we need to adapt what I saw on this repo as the MediatekHacks.cpp I threw in to fix the missing symbols issue may have accounted for why SurfaceFlinger isn't cooperating.
@pix106 - Did you by any chance use the repo I mentioned above when you built your ROM? I've used the vanilla CM android_frameworks_native repo for one and that may have accounted for why my ROM is spazzing out. Also, I saw a commit by thp1997 (along with a patch of similar intent by @Kirito96) which appears to be a patch/shim set for the MT6572 that seems to tackle the same issue as what I've been experiencing with the Epic. The crash log...
Code:
--------- beginning of crash
F/libc ( 127): Fatal signal 7 (SIGBUS), code 1, fault addr 0xb6400189 in tid 127 (surfaceflinger)
I/DEBUG ( 133): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 133): Build fingerprint: 'LeapFrog/cm_narnia/narnia:5.1.1/LMY49J/ad8cbe2f60:eng/test-keys'
I/DEBUG ( 133): Revision: '0'
I/DEBUG ( 133): ABI: 'arm'
I/DEBUG ( 133): pid: 127, tid: 127, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 133): signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0xb6400189
I/DEBUG ( 133): r0 ffffffff r1 b6400189 r2 00000005 r3 00000000
I/DEBUG ( 133): r4 b6400189 r5 ffffffff r6 be827298 r7 b60b30d0
I/DEBUG ( 133): r8 b6d6dc2c r9 be826db4 sl 00000000 fp 00000000
I/DEBUG ( 133): ip b6e02f38 sp be826d60 lr b6e68dbc pc b6e68dbc cpsr 80000010
I/DEBUG ( 133):
I/DEBUG ( 133): backtrace:
I/DEBUG ( 133): #00 pc 00003dbc /system/lib/libcutils.so (android_atomic_add+16)
I/DEBUG ( 133): #01 pc 0000d61f /system/lib/libutils.so (_ZNK7android7RefBase9decStrongEPKv+10)
I/DEBUG ( 133): #02 pc 00028f7b /system/lib/libgui.so (_ZN7android2spINS_13GraphicBufferEEaSERKS2_+22)
I/DEBUG ( 133): #03 pc 000290af /system/lib/libgui.so (_ZN7android19BufferQueueConsumer13acquireBufferEPNS_22IGraphicBufferConsumer10BufferItemEx+270)
I/DEBUG ( 133): #04 pc 0002c411 /system/lib/libgui.so (_ZN7android12ConsumerBase19acquireBufferLockedEPNS_22IGraphicBufferConsumer10BufferItemEx+16)
I/DEBUG ( 133): #05 pc 00023571 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #06 pc 00023679 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #07 pc 0002849b /system/lib/libgui.so (_ZN7android11BufferQueue21ProxyConsumerListener16onFrameAvailableERKNS_10BufferItemE+26)
I/DEBUG ( 133): #08 pc 0002ba2b /system/lib/libgui.so (_ZN7android19BufferQueueProducer11queueBufferEiRKNS_22IGraphicBufferProducer16QueueBufferInputEPNS1_17QueueBufferOutputE+562)
I/DEBUG ( 133): #09 pc 00037423 /system/lib/libgui.so (_ZN7android7Surface11queueBufferEP19ANativeWindowBufferi+254)
I/DEBUG ( 133): #10 pc 00036693 /system/lib/libgui.so (_ZN7android7Surface16hook_queueBufferEP13ANativeWindowP19ANativeWindowBufferi+10)
I/DEBUG ( 133): #11 pc 0000f720 /system/lib/libMali.so
I/DEBUG ( 133): #12 pc 00010218 /system/lib/libMali.so
I/DEBUG ( 133): #13 pc 0005e5d8 /system/lib/libMali.so
I/DEBUG ( 133): #14 pc 0005d70c /system/lib/libMali.so
I/DEBUG ( 133): #15 pc 0005bf58 /system/lib/libMali.so (shim_eglSwapBuffers+64)
I/DEBUG ( 133): #16 pc 000120d7 /system/lib/libEGL.so (eglSwapBuffers+290)
I/DEBUG ( 133): #17 pc 0000f541 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #18 pc 0001c187 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #19 pc 0001b367 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #20 pc 0001a6eb /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #21 pc 0001a459 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #22 pc 00011127 /system/lib/libutils.so (_ZN7android6Looper9pollInnerEi+410)
I/DEBUG ( 133): #23 pc 00011219 /system/lib/libutils.so (_ZN7android6Looper8pollOnceEiPiS1_PPv+92)
I/DEBUG ( 133): #24 pc 00017b95 /system/lib/libsurfaceflinger.so
I/DEBUG ( 133): #25 pc 0001a04d /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger3runEv+8)
I/DEBUG ( 133): #26 pc 00000b4d /system/bin/surfaceflinger
I/DEBUG ( 133): #27 pc 0000ff19 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 133): #28 pc 00000c08 /system/bin/surfaceflinger
F/libc ( 261): Fatal signal 7 (SIGBUS), code 1, fault addr 0xffffffff in tid 261 (surfaceflinger)
I/DEBUG ( 133): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
...appears to allude to the ones mentioned in the patch files. Maybe this is the cure we needed, short of using a different HWC which I more or less doubt to be necessary.
Click to expand...
Click to collapse
i did not use this repo.
i could build a bootable and usable cm12.1 without any patch.
thp1997 joined afterwards and added patched repos, but they were not strictly needed : they allowed WPS wifi pairing, headset icon, usb mode selection when usb is not plugged.