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.

[SOLVED] [32A] Help with hybrid stock 32A kernel - Google ION 1.6 ROM

I've created a hybrid ROM of my stock 32A (extracted from phone) kernel and the Google ION 1.6 update
Everything works (ie. market, calls, wlan, bluetooth (turns on), data, sound, recording sound, playing music, accelerometer, etc.) except for the camera/camcorder. Here is some log output when starting the Camera app:
Code:
...
(t=0x41504e4d l=40)
D/CameraService( 36): CameraService::connect E (pid 332, client 0x22e78)
D/CameraService( 36): Client::Client E (pid 332)
D/QualcommCameraHardware( 36): createInstance: E
E/QualcommCameraHardware( 36): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
E/QualcommCameraHardware( 36): ioctl error. camfd=-1, type=21, length=4, rc=-1, ctrlCmd.status=1072, Bad file number
E/QualcommCameraHardware( 36): ioctl error. camfd=-1, type=15, length=4, rc=-1, ctrlCmd.status=1128, Bad file number
E/QualcommCameraHardware( 36): ioctl error. camfd=-1, type=14, length=4, rc=-1, ctrlCmd.status=1200, Bad file number
D/QualcommCameraHardware( 36): createInstance: X created hardware=0x201b8
D/CameraService( 36): Client::Client X (pid 332)
D/CameraService( 36): CameraService::connect X
D/Camera ( 332): app passed NULL surface
D/CameraService( 36): setPreviewDisplay(0x0) (pid 332)
D/CameraService( 36): getParameters(antibanding=off;antibanding-
...
E/QualcommCameraHardware( 36): ioctl error. camfd=-1, type=21, length=4, rc=-1, ctrlCmd.status=11664, Bad file number
E/QualcommCameraHardware( 36): ioctl error. camfd=-1, type=15, length=4, rc=-1, ctrlCmd.status=12224, Bad file number
E/QualcommCameraHardware( 36): ioctl error. camfd=-1, type=14, length=4, rc=-1, ctrlCmd.status=12000, Bad file number
V/camera ( 332): startPreview
D/CameraService( 36): startPreview (pid 332)
D/CameraService( 36): startCameraMode(0) (pid 332)
D/CameraService( 36): mSurface is not set yet.
D/CameraService( 36): startPreviewMode (pid 332)
I/QualcommCameraHardware( 36): initPreview E: preview size=384x288
E/QualcommCameraHardware( 36): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 36): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 36): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 36): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 36): ioctl error. camfd=-1, type=1, length=28, rc=-1, ctrlCmd.status=9135, Bad file number
E/QualcommCameraHardware( 36): startPreview X initPreview failed. Not starting preview.
D/CameraService( 36): stopPreview (pid 332)
D/CameraService( 36): stopPreview(), hardware stopped OK
D/Camera-JNI( 332): release camera
D/CameraService( 36): Client::disconnect() E (pid 332 client 0x22e78)
D/CameraService( 36): hardware teardown
D/QualcommCameraHardware( 36): release E
E/QualcommCameraHardware( 36): ioctl CAMERA_EXIT fd -1 error Bad file number
E/QualcommCameraHardware( 36): config_thread exit failure: Bad file number
D/QualcommCameraHardware( 36): release X
D/QualcommCameraHardware( 36): ~QualcommCameraHardware E
D/QualcommCameraHardware( 36): ~QualcommCameraHardware X
E/QualcommCameraHardware( 36): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 36): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 36): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 36): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
D/CameraService( 36): removeClient (pid 332) done
D/CameraService( 36): Client::disconnect() X (pid 332)
W/dalvikvm( 332): threadid=13: thread exiting with uncaught exception (group=0x4001da20)
E/AndroidRuntime( 332): Uncaught handler: thread Thread-7 exiting due to uncaught exception
E/AndroidRuntime( 332): java.lang.RuntimeException: startPreview failed
E/AndroidRuntime( 332): at com.android.camera.Camera.startPreview(Camera.java:1360)
E/AndroidRuntime( 332): at com.android.camera.Camera.access$4000(Camera.java:78)
E/AndroidRuntime( 332): at com.android.camera.Camera$3.run(Camera.java:724)
E/AndroidRuntime( 332): at java.lang.Thread.run(Thread.java:1060)
E/AndroidRuntime( 332): Caused by: java.lang.RuntimeException: startPreview failed
E/AndroidRuntime( 332): at android.hardware.Camera.startPreview(Native Method)
E/AndroidRuntime( 332): at com.android.camera.Camera.startPreview(Camera.java:1357)
E/AndroidRuntime( 332): ... 3 more
D/CameraService( 36): Client::~Client E (pid 36, client 0x22e78)
D/CameraService( 36): Client::disconnect() E (pid 36 client 0x22e78)
D/CameraService( 36): Client::~Client X (pid 36)
I/Process ( 59): Sending signal. PID: 332 SIG: 3
I/dalvikvm( 332): threadid=7: reacting to signal 3
I/dalvikvm( 332): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 59): Added state dump to 1 crashes
I/Process ( 332): Sending signal. PID: 332 SIG: 9
I/ActivityManager( 59): Process com.android.camera (pid 332) has died.
I think the key bit there is 'startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!'
After that, you can see successive ioctl 'Bad file number' errors.
I have a workaround by copying /system/lib/libcamera.so and /system/lib/libqcamera.so from the original, stock image of my phone. This results in a working camera. However, the camcorder can't record video. When pressing record, it freezes. No force close. Can BACK out of the app. Here's the log when that happens. As you can see, mediaserver pukes:
Code:
...
I/ActivityManager( 60): Displayed activity com.android.camera/.VideoCamera: 1260 ms (total 1260 ms)
V/videocamera( 354): initializeRecorder
V/videocamera( 354): Releasing media recorder.
D/CameraService( 495): Client::connect E (pid 495, client 0x373fc)
D/CameraService( 495): Connect to the new client (pid 495, client 0x373fc)
V/videocamera( 354): Current camera video filename: /sdcard/DCIM/Camera/video-2009-12-29-22-22-37.3gp
I/MediaRecorderJNI( 354): prepare: surface=0x1ba9a8 (id=1)
D/CameraService( 495): setPreviewDisplay(0x37800) (pid 495)
I/OMXVenc ( 495): component_init::292 Initializing component OMX.qcom.video.encoder.h263
E/OMXVenc ( 495): get_parameter::922 unsupported index 267887431
E/OMXVenc ( 495): get_parameter::899 unsupported index 117440523
E/OMXVenc ( 495): set_parameter::1099 unsupported index in set_parameter 117440523
E/OMXVenc ( 495): get_parameter::922 unsupported index 100663301
E/OMXVenc ( 495): set_parameter::1142 unsupported index 100663301
E/OMXVenc ( 495): get_parameter::922 unsupported index 100663302
E/OMXVenc ( 495): set_parameter::1142 unsupported index 100663302
I/OMXVenc ( 495): send_command::690 attempt to move to new state 2
E/OMXVenc ( 495): Setting OMX_Video_ControlRateVariable
I/VENC_DRV( 495): venc_drv_malloc::1155 /dev/pmem_adsp
I/VENC_DRV( 495): venc_drv_malloc::1183 phys lookup success virt=0x40e64000 -- FD=21 -- size - 524288
D/CameraService( 495): setPreviewDisplay(0x37800) (pid 495)
D/CameraInput( 495): Intended mFrameWidth=176, mFrameHeight=144
V/QualcommCameraHardware( 495): getParameters: EX
D/CameraService( 495): getParameters(antibanding=auto;antibanding-
...
V/QualcommCameraHardware( 495): setParameters: E params = 0x40c63cf8
V/QualcommCameraHardware( 495): requested size 176 x 144
V/QualcommCameraHardware( 495): actual size 176 x 144
V/QualcommCameraHardware( 495): initCameraParameters: E
V/QualcommCameraHardware( 495): camera hardware has been started already
V/QualcommCameraHardware( 495): initCameraParameters: set parm: CAMERA_PARM_PREVIEW_MODE, 0
V/QualcommCameraHardware( 495): Setting Zoom is 0
I/QualcommCameraHardware( 495): setting thumbnail dimensions to 512x384, quality 30
E/QualcommCameraHardware( 495): LINK_camera_set_thumbnail_properties returned 2
V/QualcommCameraHardware( 495): Setting JPEG-image quality to 100
V/QualcommCameraHardware( 495): initCameraParameters: X
V/QualcommCameraHardware( 495): setParameters: X mCameraState=3
V/QualcommCameraHardware( 495): getParameters: EX
D/CameraService( 495): getParameters(antibanding=auto;antibanding-
...
D/CameraInput( 495): Actual mFrameWidth=176, mFrameHeight=144
D/CameraService( 495): startPreview (pid 495)
D/CameraService( 495): startCameraMode(0) (pid 495)
D/CameraService( 495): startPreviewMode (pid 495)
E/MetadataDriver( 495): isCommandSuccessful: Command id(0 and expected 0) and status (-4 and expected 1), data corruption (false) at state (1).
E/MetadataDriver( 495): isCommandSuccessful: Command id(1 and expected 1) and status (-14 and expected 1), data corruption (false) at state (5).
D/dalvikvm( 60): GC freed 8852 objects / 389392 bytes in 235ms
V/videocamera( 354): startVideoRecording
I/OMXVenc ( 495): send_command::690 attempt to move to new state 3
I/VENC_DRV( 495): venc_drv_open::283 TE version = 1
D/CameraService( 495): startRecording (pid 495)
D/CameraService( 495): startCameraMode(1) (pid 495)
D/CameraService( 495): startRecordingMode (pid 495)
V/QualcommCameraHardware( 495): startPreview E
E/QualcommCameraHardware( 495): startPreview is already in progress, doing nothing.
D/AudioHardwareMSM72XX( 495): audpre_index = 0, tx_iir_index = 0
D/HTC Acoustic( 495): msm72xx_enable_audpre: 0x0000
W/AudioFlinger( 495): write blocked for 66 msecs
I/DEBUG ( 494): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 494): Build fingerprint: 'rogers/htc_magic/sapphire/sapphire:1.5/2.17.631.2/42949:user'
I/DEBUG ( 494): pid: 495, tid: 519 >>> /system/bin/mediaserver <<<
I/DEBUG ( 494): signal 11 (SIGSEGV), fault addr 10000014
I/DEBUG ( 494): r0 00000000 r1 00000001 r2 10000014 r3 ffff0fff
I/DEBUG ( 494): r4 00000000 r5 10000014 r6 a9c8c048 r7 4080bcb4
I/DEBUG ( 494): r8 4070be38 r9 afe39dd4 10 a949bec1 fp 00000001
I/DEBUG ( 494): ip a9d4bcdc sp 4080bc58 lr afe0d46c pc ffff0fc0 cpsr 00000010
I/DEBUG ( 494): #00 pc ffff0fc0
I/DEBUG ( 494): #01 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #02 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #03 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #04 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #05 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #06 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #07 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #08 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #09 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #10 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #11 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #12 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #13 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #14 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #15 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #16 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #17 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #18 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #19 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #20 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #21 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #22 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #23 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #24 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #25 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #26 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #27 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #28 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #29 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #30 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): #31 pc 0000d468 /system/lib/libc.so
I/DEBUG ( 494): stack:
I/DEBUG ( 494): 4080bc18 3fc971ba
I/DEBUG ( 494): 4080bc1c 00000000
I/DEBUG ( 494): 4080bc20 00000000
I/DEBUG ( 494): 4080bc24 00000000
I/DEBUG ( 494): 4080bc28 00000000
I/DEBUG ( 494): 4080bc2c 00000000
I/DEBUG ( 494): 4080bc30 00000000
I/DEBUG ( 494): 4080bc34 00000000
I/DEBUG ( 494): 4080bc38 00000000
I/DEBUG ( 494): 4080bc3c 00000000
I/DEBUG ( 494): 4080bc40 00000001
I/DEBUG ( 494): 4080bc44 00000000
I/DEBUG ( 494): 4080bc48 00000002
I/DEBUG ( 494): 4080bc4c 00000000
I/DEBUG ( 494): 4080bc50 df002777
I/DEBUG ( 494): 4080bc54 e3a070ad
I/DEBUG ( 494): #01 4080bc58 00000000
I/DEBUG ( 494): 4080bc5c a9d398a7 /system/lib/libutils.so
W/AudioRecord( 495): obtainBuffer timed out (is the CPU pegged?) user=00005000, server=00005400
W/AudioRecord( 495): *** SERIOUS WARNING *** obtainBuffer() timed out but didn't need to be locked. We recovered, but this shouldn't happen (user=00005000, server=00005400)
W/AudioSystem( 354): AudioFlinger server died!
I/ServiceManager( 31): service 'media.audio_flinger' died
W/MediaMetadataRetriever( 354): MediaMetadataRetriever server died!
I/ServiceManager( 31): service 'media.player' died
W/Camera ( 354): ICamera died
I/ServiceManager( 31): service 'media.camera' died
W/AudioSystem( 60): AudioFlinger server died!
E/Camera ( 354): Error 100
I/DEBUG ( 494): debuggerd committing suicide to free the zombie!
I/DEBUG ( 531): debuggerd: Sep 21 2009 14:37:06
W/Camera ( 354): Camera server died!
The key bit there can be found by searching for 'SIGSEGV'
Any help on how to fix this would be appreciated! I'd like to fix this 'the right way' (ie. do not want to copy old cupcake camera app, etc.) Also, not against re-compiling the kernel, if that's what it takes.
Thanks!

Guess fix:
Compile a kernel for 32A with source from:
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.29-donut
It has the source for msm_camera, whereas the source from HTC does not.
Sound right?

fastboot'd the new kernel and everything appears to be working now. Just need to compile wlan.ko and I'm done!

[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.