Disclaimer:
I am not responsible for the outcome of you flashing this software, please backup your current boot partition before flashing this kernel.
Click to expand...
Click to collapse
While I will take some credit for this work, I am not a Developer; I'm a hobbyist - I'll accept any help I can get to improve this kernel.
Downloads are in the download section
Source RUSTY-VNS
Credits:
@twicejr
@kwoktopus
Changes from stock:
2017-03-16 No-Root
2017-03-16 Root
3.10.102
Optimized build flags
Intelliactive CPU Governor
RustyKernel-EMUI4.1_hi6250-2017-03-17
RustyKernel-PA6.0.1_hi6250-2017-03-17 - Lockscreen bug, disable lockscreen security before flashing (PIN/Patten/Password)
Intelliplug Hotplug
Thunderplug Hotplug
PA 6.0.1 Support
Known bugs:
Kernel Adiutor:
Code:
big: Failed to load frequencies
. They're running, just not being logged.
PA version has a lockscreen bug - disable secure lockscreen before flashing
XDA:DevDB Information
P9 Lite Kernel, Kernel for the Huawei P9 Lite
Contributors
Carlyle_f
Source Code: https://github.com/carlyle-felix/RUSTY-VNS
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 2017-03-17
Beta Release Date: 2017-03-16
Created 2017-03-16
Last Updated 2017-03-17
Reserved
Great job, finally some kernels showing up! Please consider making a version with USB OTG and double tap to wake enabled. I like that you have two versions - with and without root.
You can make oeminfo l31c636
pilgrim011 said:
Great job, finally some kernels showing up! Please consider making a version with USB OTG and double tap to wake enabled. I like that you have two versions - with and without root.
Click to expand...
Click to collapse
Thanks man, I will look into OTG. Also, next releases will all have root
Sent from my HUAWEI VNS-L31 using Tapatalk
http://cloud.tapatalk.com/s/58cb6f4e67c55/RustyKernel_hi6250-2017-03-16.zip
Testers please leave feedback
Intelliplug and thunder plug hotplugs
Sent from my HUAWEI VNS-L31 using Tapatalk
Since this kernel supports PA, does it support LineageOS 13, or 14/RR?
dariomrk said:
Since this kernel supports PA, does it support LineageOS 13, or 14/RR?
Click to expand...
Click to collapse
I think this should work for CM13 because it shares the same ramdisk and kernel cmd options but it probably won't work on LineageOS 14. I tried to flash the Avsky's kernel for LOS14 on PA and it didn't work.
dady000 said:
I think this should work for CM13 because it shares the same ramdisk and kernel cmd options but it probably won't work on LineageOS 14. I tried to flash the Avsky's kernel for LOS14 on PA and it didn't work.
Click to expand...
Click to collapse
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
No, not yet, I will try it later. What I tried is the Avsky's kernel.
What are the advantages of using this kernel? And how do you install it? Noob here
SALVO9 said:
What are the advantages of using this kernel? And how do you install it? Noob here
Click to expand...
Click to collapse
Hi, please don't think I'm trying to be funny or mean, if you don't know what you'll gain/lose by flashing a kernel rather steer clear of doing it.
I cannot stop you from doing it anyway but do me a favour and google it first, do some research and see what it's about.
I only advise you not to do so ignorantly because it gives you control of things you don't usually have control of and this has the potential to destroy your device and I really don't want that for the users of my work.
cheers. :good:
Carlyle_f said:
Hi, please don't think I'm trying to be funny or mean, if you don't know what you'll gain/lose by flashing a kernel rather steer clear of doing it.
I cannot stop you from doing it anyway but do me a favour and google it first, do some research and see what it's about.
I only advise you not to do so ignorantly because it gives you control of things you don't usually have control of and this has the potential to destroy your device and I really don't want that for the users of my work.
cheers. :good:
Click to expand...
Click to collapse
I understand your concern and appreciate it, but I NEVER do anything to my device without knowing EXACTLY what I'm doing.. I'm not a total noob, I actually know how to do many things to my phone. I am just not used to kernels since there are almost no custom kernels for p9 lite and I was asking which are the benefits of this one
SALVO9 said:
I understand your concern and appreciate it, but I NEVER do anything to my device without knowing EXACTLY what I'm doing.. I'm not a total noob, I actually know how to do many things to my phone. I am just not used to kernels since there are almost no custom kernels for p9 lite and I was asking which are the benefits of this one
Click to expand...
Click to collapse
Alright, the benefits of this kernel is listed under changelog in OP
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Okey I flashed it and I when I enter the pattern to unlock the device, it just deletes and won't let me in. Kmsg below:
Code:
<13>[ 157.734222s][pid:1,cpu0,init]init: Starting service 'keystore'...
<3>[ 157.838409s][pid:3526,cpu0,keystore]tc_client_ioctl(3526, keystore): invalid cmd!
<6>[ 158.002014s][pid:3526,cpu0,keystore]keystore[3526]: unhandled level 1 translation fault (11) at 0x00000020, esr 0x92000005
<1>[ 158.002014s][pid:3526,cpu0,keystore]pgd = ffffffc02b1d9000
<1>[ 158.002044s][pid:3526,cpu0,keystore][00000020] *pgd=0000000000000000
<4>[ 158.002044s][pid:3526,cpu0,keystore]
<4>[ 158.002044s][pid:3526,cpu0,keystore]CPU: 0 PID: 3526 Comm: keystore Tainted: G W 3.10.102-g247a5fe-dirty #9
<4>[ 158.002075s][pid:3526,cpu0,keystore]task: ffffffc012da2280 ti: ffffffc024370000 task.ti: ffffffc024370000
<4>[ 158.002075s][pid:3526,cpu0,keystore]PC is at 0x7f795c6bd8
<4>[ 158.002075s][pid:3526,cpu0,keystore]LR is at 0x7f795c77cc
<4>[ 158.002075s][pid:3526,cpu0,keystore]pc : [<0000007f795c6bd8>] lr : [<0000007f795c77cc>] pstate: 20000000
<4>[ 158.002075s][pid:3526,cpu0,keystore]sp : 0000007fc690e9c0
<4>[ 158.002105s][pid:3526,cpu0,keystore]x29: 0000007fc690e9c0 x28: 0000000000000000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x27: 0000005587463180 x26: 0000005587463000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x25: 0000007f79563000 x24: 0000007fc690eb60
<4>[ 158.002105s][pid:3526,cpu0,keystore]x23: 0000007f795f7010 x22: 0000007f79562060
<4>[ 158.002136s][pid:3526,cpu0,keystore]x21: 0000007f7956b000 x20: 0000007f7956b020
<4>[ 158.002136s][pid:3526,cpu0,keystore]x19: 0000007f79542000 x18: 0000007f79be8064
<4>[ 158.002136s][pid:3526,cpu0,keystore]x17: 0000007f795c6bbc x16: 0000007f795dbf48
<4>[ 158.002136s][pid:3526,cpu0,keystore]x15: 0000000000000000 x14: 0000007fc690e528
<4>[ 158.002166s][pid:3526,cpu0,keystore]x13: 000000000000002e x12: 0000007fc690e340
<4>[ 158.002166s][pid:3526,cpu0,keystore]x11: 0000007fc690e468 x10: 0000007fc690e42c
<4>[ 158.002166s][pid:3526,cpu0,keystore]x9 : 0000000000000037 x8 : 0000000000000042
<4>[ 158.002166s][pid:3526,cpu0,keystore]x7 : 0000000000000000 x6 : 0000000000000dc6
<4>[ 158.002166s][pid:3526,cpu0,keystore]x5 : 00000000000003f9 x4 : 0000000000000037
<4>[ 158.002197s][pid:3526,cpu0,keystore]x3 : 62d66a6aeb09d6ff x2 : 62d66a6aeb09d6ff
<4>[ 158.002197s][pid:3526,cpu0,keystore]x1 : 0000000000000000 x0 : 0000007f79541fe8
<4>[ 158.002197s][pid:3526,cpu0,keystore]
<13>[ 158.004302s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killed by signal 11
<13>[ 158.004333s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killing any children in process group
<6>[ 158.647033s][2017:03:17 17:46:27][pid:1266,cpu0,Binder_5]binder: 767:1266 transaction failed 29189, size 100-0
<6>[ 158.650329s][pid:921,cpu0,ConnectivitySer]binder: 767:921 transaction failed 29189, size 328-0
<6>[ 158.839477s][pid:767,cpu0,system_server]binder: 767:767 transaction failed 29189, size 84-0
<7>[ 158.987701s][pid:419,cpu0,kworker/u16:3]wifi wakeup cmd send,wakelock cnt 2
<7>[ 159.137084s][pid:419,cpu0,kworker/u16:3]wifi sleep cmd send ,wakelock cnt 1
<4>[ 159.336730s][pid:0,cpu1,swapper/1]CPU1: Booted secondary processor
<7>[ 160.057189s][2017:03:17 17:46:29][pid:465,cpu1,hisi_hcc]wifi wakeup cmd send,wakelock cnt 1
<7>[ 160.063507s][pid:1222,cpu0,wpa_supplicant_][W][vap:0]{wal_cfg80211_get_station::rssi -54.} [F:1205][L:5254]
<38>[ 160.066101s][pid:297,cpu0,logd.auditd]type=1400 audit(1489769189.267:220): avc: denied { sendto } for pid=1222 comm="wpa_supplicant_" ppid=1 ppid_comm="init" path="/data/misc/wifi/sockets/wpa_ctrl_767-1" scontext=u:r:init:s0 tcontext=u:r:system_server:s0 tclass=unix_dgram_socket permissive=1
<6>[ 160.142639s][pid:785,cpu1,Binder_1]hisi_vibrator_enable,value=0
Delete
dady000 said:
Okey I flashed it and I when I enter the pattern to unlock the device, it just deletes and won't let me in. Kmsg below:
Code:
<13>[ 157.734222s][pid:1,cpu0,init]init: Starting service 'keystore'...
<3>[ 157.838409s][pid:3526,cpu0,keystore]tc_client_ioctl(3526, keystore): invalid cmd!
<6>[ 158.002014s][pid:3526,cpu0,keystore]keystore[3526]: unhandled level 1 translation fault (11) at 0x00000020, esr 0x92000005
<1>[ 158.002014s][pid:3526,cpu0,keystore]pgd = ffffffc02b1d9000
<1>[ 158.002044s][pid:3526,cpu0,keystore][00000020] *pgd=0000000000000000
<4>[ 158.002044s][pid:3526,cpu0,keystore]
<4>[ 158.002044s][pid:3526,cpu0,keystore]CPU: 0 PID: 3526 Comm: keystore Tainted: G W 3.10.102-g247a5fe-dirty #9
<4>[ 158.002075s][pid:3526,cpu0,keystore]task: ffffffc012da2280 ti: ffffffc024370000 task.ti: ffffffc024370000
<4>[ 158.002075s][pid:3526,cpu0,keystore]PC is at 0x7f795c6bd8
<4>[ 158.002075s][pid:3526,cpu0,keystore]LR is at 0x7f795c77cc
<4>[ 158.002075s][pid:3526,cpu0,keystore]pc : [<0000007f795c6bd8>] lr : [<0000007f795c77cc>] pstate: 20000000
<4>[ 158.002075s][pid:3526,cpu0,keystore]sp : 0000007fc690e9c0
<4>[ 158.002105s][pid:3526,cpu0,keystore]x29: 0000007fc690e9c0 x28: 0000000000000000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x27: 0000005587463180 x26: 0000005587463000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x25: 0000007f79563000 x24: 0000007fc690eb60
<4>[ 158.002105s][pid:3526,cpu0,keystore]x23: 0000007f795f7010 x22: 0000007f79562060
<4>[ 158.002136s][pid:3526,cpu0,keystore]x21: 0000007f7956b000 x20: 0000007f7956b020
<4>[ 158.002136s][pid:3526,cpu0,keystore]x19: 0000007f79542000 x18: 0000007f79be8064
<4>[ 158.002136s][pid:3526,cpu0,keystore]x17: 0000007f795c6bbc x16: 0000007f795dbf48
<4>[ 158.002136s][pid:3526,cpu0,keystore]x15: 0000000000000000 x14: 0000007fc690e528
<4>[ 158.002166s][pid:3526,cpu0,keystore]x13: 000000000000002e x12: 0000007fc690e340
<4>[ 158.002166s][pid:3526,cpu0,keystore]x11: 0000007fc690e468 x10: 0000007fc690e42c
<4>[ 158.002166s][pid:3526,cpu0,keystore]x9 : 0000000000000037 x8 : 0000000000000042
<4>[ 158.002166s][pid:3526,cpu0,keystore]x7 : 0000000000000000 x6 : 0000000000000dc6
<4>[ 158.002166s][pid:3526,cpu0,keystore]x5 : 00000000000003f9 x4 : 0000000000000037
<4>[ 158.002197s][pid:3526,cpu0,keystore]x3 : 62d66a6aeb09d6ff x2 : 62d66a6aeb09d6ff
<4>[ 158.002197s][pid:3526,cpu0,keystore]x1 : 0000000000000000 x0 : 0000007f79541fe8
<4>[ 158.002197s][pid:3526,cpu0,keystore]
<13>[ 158.004302s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killed by signal 11
<13>[ 158.004333s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killing any children in process group
<6>[ 158.647033s][2017:03:17 17:46:27][pid:1266,cpu0,Binder_5]binder: 767:1266 transaction failed 29189, size 100-0
<6>[ 158.650329s][pid:921,cpu0,ConnectivitySer]binder: 767:921 transaction failed 29189, size 328-0
<6>[ 158.839477s][pid:767,cpu0,system_server]binder: 767:767 transaction failed 29189, size 84-0
<7>[ 158.987701s][pid:419,cpu0,kworker/u16:3]wifi wakeup cmd send,wakelock cnt 2
<7>[ 159.137084s][pid:419,cpu0,kworker/u16:3]wifi sleep cmd send ,wakelock cnt 1
<4>[ 159.336730s][pid:0,cpu1,swapper/1]CPU1: Booted secondary processor
<7>[ 160.057189s][2017:03:17 17:46:29][pid:465,cpu1,hisi_hcc]wifi wakeup cmd send,wakelock cnt 1
<7>[ 160.063507s][pid:1222,cpu0,wpa_supplicant_][W][vap:0]{wal_cfg80211_get_station::rssi -54.} [F:1205][L:5254]
<38>[ 160.066101s][pid:297,cpu0,logd.auditd]type=1400 audit(1489769189.267:220): avc: denied { sendto } for pid=1222 comm="wpa_supplicant_" ppid=1 ppid_comm="init" path="/data/misc/wifi/sockets/wpa_ctrl_767-1" scontext=u:r:init:s0 tcontext=u:r:system_server:s0 tclass=unix_dgram_socket permissive=1
<6>[ 160.142639s][pid:785,cpu1,Binder_1]hisi_vibrator_enable,value=0
Click to expand...
Click to collapse
Hi, please attach both dmsg and kmsg. Also to make it easier is there anything you can do with this logcat i got when i tried it on PA.
Logcat:
Code:
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4263 (keystore)
03-17 20:56:51.589 461 461 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 20:56:51.690 461 461 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 20:56:51.690 461 461 F DEBUG : CM Version: 'unknown'
03-17 20:56:51.690 461 461 F DEBUG : Build fingerprint: 'huawei/pa_hi6250/hi6250:6.0.1/MTC20F/dady03072055:userdebug/test-keys'
03-17 20:56:51.690 461 461 F DEBUG : Revision: '0'
03-17 20:56:51.690 461 461 F DEBUG : ABI: 'arm64'
03-17 20:56:51.691 461 461 F DEBUG : pid: 4263, tid: 4263, name: keystore >>> /system/bin/keystore <<<
03-17 20:56:51.691 461 461 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
03-17 20:56:51.696 461 461 F DEBUG : x0 0000007f851c1fe8 x1 0000000000000000 x2 d5fa989020823a5f x3 d5fa989020823a5f
03-17 20:56:51.696 461 461 F DEBUG : x4 0000000000000037 x5 00000000000003f9 x6 00000000000010a7 x7 0000000000000000
03-17 20:56:51.696 461 461 F DEBUG : x8 0000000000000042 x9 0000000000000037 x10 0000007feda4d68c x11 0000007feda4d6c8
03-17 20:56:51.696 461 461 F DEBUG : x12 0000007feda4d5a0 x13 000000000000002e x14 0000007feda4d788 x15 0000000000000000
03-17 20:56:51.697 461 461 F DEBUG : x16 0000007f8525af48 x17 0000007f85245bbc x18 0000007f85867064 x19 0000007f851c2000
03-17 20:56:51.697 461 461 F DEBUG : x20 0000007f851eb020 x21 0000007f851eb000 x22 0000007f851e2060 x23 0000007f85276010
03-17 20:56:51.697 461 461 F DEBUG : x24 0000007feda4ddc0 x25 0000007f851e3000 x26 000000556cc44000 x27 000000556cc44180
03-17 20:56:51.697 461 461 F DEBUG : x28 0000000000000000 x29 0000007feda4dc20 x30 0000007f852467cc
03-17 20:56:51.697 461 461 F DEBUG : sp 0000007feda4dc20 pc 0000007f85245bd8 pstate 0000000020000000
03-17 20:56:51.699 912 1090 W NativeCrashListener: Couldn't find ProcessRecord for pid 4263
03-17 20:56:51.716 461 461 F DEBUG :
03-17 20:56:51.716 461 461 F DEBUG : backtrace:
03-17 20:56:51.716 461 461 E DEBUG : AM write failed: Broken pipe
03-17 20:56:51.716 461 461 F DEBUG : #00 pc 0000000000001bd8 /system/lib64/libteec.so (TEEC_ReleaseSharedMemory+28)
03-17 20:56:51.716 461 461 F DEBUG : #01 pc 00000000000027c8 /system/lib64/libteec.so (TEEC_FinalizeContext+80)
03-17 20:56:51.716 461 461 F DEBUG : #02 pc 0000000000002eb4 /system/lib64/hw/keystore.hi6250.so
03-17 20:56:51.716 461 461 F DEBUG : #03 pc 0000000000010038 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster16Keymaster1EngineD2Ev+24)
03-17 20:56:51.716 461 461 F DEBUG : #04 pc 0000000000012720 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD2Ev+164)
03-17 20:56:51.716 461 461 F DEBUG : #05 pc 00000000000127d8 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #06 pc 0000000000011a4c /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD1Ev+120)
03-17 20:56:51.716 461 461 F DEBUG : #07 pc 0000000000011a70 /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #08 pc 0000000000007a50 /system/bin/keystore (main+2016)
03-17 20:56:51.716 461 461 F DEBUG : #09 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
03-17 20:56:51.716 461 461 F DEBUG : #10 pc 0000000000007c20 /system/bin/keystore
03-17 20:56:51.762 461 461 F DEBUG :
03-17 20:56:51.762 461 461 F DEBUG : Tombstone written to: /data/tombstones/tombstone_04
Also the only quick workaround i found was removing pin/password/pattern unlock before flashing kernel. huge security breach but should satisfy those who are okay with slide to unlock for now.
Carlyle_f said:
Hi, please attach both dmsg and kmsg. Also to make it easier is there anything you can do with this logcat i got when i tried it on PA.
Logcat:
Code:
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4263 (keystore)
03-17 20:56:51.589 461 461 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 20:56:51.690 461 461 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 20:56:51.690 461 461 F DEBUG : CM Version: 'unknown'
03-17 20:56:51.690 461 461 F DEBUG : Build fingerprint: 'huawei/pa_hi6250/hi6250:6.0.1/MTC20F/dady03072055:userdebug/test-keys'
03-17 20:56:51.690 461 461 F DEBUG : Revision: '0'
03-17 20:56:51.690 461 461 F DEBUG : ABI: 'arm64'
03-17 20:56:51.691 461 461 F DEBUG : pid: 4263, tid: 4263, name: keystore >>> /system/bin/keystore <<<
03-17 20:56:51.691 461 461 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
03-17 20:56:51.696 461 461 F DEBUG : x0 0000007f851c1fe8 x1 0000000000000000 x2 d5fa989020823a5f x3 d5fa989020823a5f
03-17 20:56:51.696 461 461 F DEBUG : x4 0000000000000037 x5 00000000000003f9 x6 00000000000010a7 x7 0000000000000000
03-17 20:56:51.696 461 461 F DEBUG : x8 0000000000000042 x9 0000000000000037 x10 0000007feda4d68c x11 0000007feda4d6c8
03-17 20:56:51.696 461 461 F DEBUG : x12 0000007feda4d5a0 x13 000000000000002e x14 0000007feda4d788 x15 0000000000000000
03-17 20:56:51.697 461 461 F DEBUG : x16 0000007f8525af48 x17 0000007f85245bbc x18 0000007f85867064 x19 0000007f851c2000
03-17 20:56:51.697 461 461 F DEBUG : x20 0000007f851eb020 x21 0000007f851eb000 x22 0000007f851e2060 x23 0000007f85276010
03-17 20:56:51.697 461 461 F DEBUG : x24 0000007feda4ddc0 x25 0000007f851e3000 x26 000000556cc44000 x27 000000556cc44180
03-17 20:56:51.697 461 461 F DEBUG : x28 0000000000000000 x29 0000007feda4dc20 x30 0000007f852467cc
03-17 20:56:51.697 461 461 F DEBUG : sp 0000007feda4dc20 pc 0000007f85245bd8 pstate 0000000020000000
03-17 20:56:51.699 912 1090 W NativeCrashListener: Couldn't find ProcessRecord for pid 4263
03-17 20:56:51.716 461 461 F DEBUG :
03-17 20:56:51.716 461 461 F DEBUG : backtrace:
03-17 20:56:51.716 461 461 E DEBUG : AM write failed: Broken pipe
03-17 20:56:51.716 461 461 F DEBUG : #00 pc 0000000000001bd8 /system/lib64/libteec.so (TEEC_ReleaseSharedMemory+28)
03-17 20:56:51.716 461 461 F DEBUG : #01 pc 00000000000027c8 /system/lib64/libteec.so (TEEC_FinalizeContext+80)
03-17 20:56:51.716 461 461 F DEBUG : #02 pc 0000000000002eb4 /system/lib64/hw/keystore.hi6250.so
03-17 20:56:51.716 461 461 F DEBUG : #03 pc 0000000000010038 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster16Keymaster1EngineD2Ev+24)
03-17 20:56:51.716 461 461 F DEBUG : #04 pc 0000000000012720 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD2Ev+164)
03-17 20:56:51.716 461 461 F DEBUG : #05 pc 00000000000127d8 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #06 pc 0000000000011a4c /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD1Ev+120)
03-17 20:56:51.716 461 461 F DEBUG : #07 pc 0000000000011a70 /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #08 pc 0000000000007a50 /system/bin/keystore (main+2016)
03-17 20:56:51.716 461 461 F DEBUG : #09 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
03-17 20:56:51.716 461 461 F DEBUG : #10 pc 0000000000007c20 /system/bin/keystore
03-17 20:56:51.762 461 461 F DEBUG :
03-17 20:56:51.762 461 461 F DEBUG : Tombstone written to: /data/tombstones/tombstone_04
Also the only quick workaround i found was removing pin/password/pattern unlock. huge security breach but should satisfy those who are okay with slide to unlock for now.
Click to expand...
Click to collapse
Yes, I got the same logcat. Nothing I can do with it. I didn't attach whole dmesg because it's apparent that it is issue with keystore, no other errors shown in dmesg/kmsg.
dady000 said:
Yes, I got the same logcat. Nothing I can do with it. I didn't attach whole dmesg because it's apparent that it is issue with keystore, no other errors shown in dmesg/kmsg.
Click to expand...
Click to collapse
hi can you please try the new build before i include it in OP:
https://forum.xda-developers.com/devdb/project/dl/?id=23699
Considering kernel is essential to make your device work, if you put a incompatible kernel on your device, what are the consequences?
Will the recovery still be bootable considering it has its own partition. In case the recovery is bootable, I'm willing to test on my VNS-L31.
Also in that case i could try on other roms, example CM13, Los14, etc...
Related
Hey, hope anyone here can help.
Have an App called Canvas for pebble https://play.google.com/store/apps/details?id=com.pennas.pebblecanvas&hl=de
Since i start to use 4.3 Based Sense Roms, app crashed when i open it.
After a few tests with different Roms, app crashes only on 4.3 Sense Roms.
Tested Roms are:
MaximusHD12.1 & 13
ARHD 20.2
TrickDroid 10
InsertCoin3.3-1
SinLess ROM SE v1.0
Eragon RC3
On SinLess Rom GE 3.6.2 & CM10 App works fine.
Here is, what Developer of the canvas app says and his crashlog.
I found a crash report on Google Play which seems to be yours. Bad news is that it's a native code crash - i.e. a bug in the firmware/ROM. The only hint of what is wrong is "android::SensorEventQueue::listenerSensor" which suggests that there may be a bug to do with loading sensor data.
Build fingerprint: 'htc/htc_europe/m7:4.3/JSS15J/235216.1:user/release-keys'
Revision: '3'
pid: 5885, tid: 5898, name: AsyncTask #1 >>> com.pennas.pebblecanvas <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
r0 00000000 r1 00000000 r2 80808080 r3 00000000
r4 00000000 r5 6b878bd8 r6 00000001 r7 698c0cd8
r8 6b878c6c r9 698c0ccc sl 687456b8 fp 6b878c84
ip 40137f6c sp 6b878bc0 lr 4012b935 pc 40050610 cpsr 600e0010
d0 0000000000000000 d1 0000000000000000
d2 000003e800000000 d3 0000000000000004
d4 bff0000000000000 d5 4024000000000000
d6 4018000000000000 d7 0000000000000000
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 00720064006e0061 d17 002e00640069006f
d18 002e006900750067 d19 0073006e00650053
d20 007600450072006f d21 00430074006e0065
d22 0065006e006e006f d23 006f006900740063
d24 3fc74721cad6b0ed d25 3fc2f112df3e5244
d26 4000000000000000 d27 547d42aea2879f2e
d28 0000000000000000 d29 0000000000000000
d30 0000000000000000 d31 0000000000000000
scr 20000010
backtrace:
#00 pc 0001e610 /system/lib/libc.so (strlen+72)
#01 pc 00023931 /system/lib/libbinder.so (android:arcel::writeCString(char const*)+8)
#02 pc 00028281 /system/lib/libgui.so
#03 pc 0002aeef /system/lib/libgui.so (android::SensorEventQueue::listenerSensor(char const*, int) const+8)
#04 pc 0008d81b /system/lib/libandroid_runtime.so
#05 pc 0002004c /system/lib/libdvm.so (dvmPlatformInvoke+112)
#06 pc 00056699 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+428)
#07 pc 000294e0 /system/lib/libdvm.so
#08 pc 0002f194 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+232)
#09 pc 0006bee1 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+292)
#10 pc 0006bf0b /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
#11 pc 0005f1f3 /system/lib/libdvm.so
#12 pc 0000cbe0 /system/lib/libc.so (__thread_entry+72)
#13 pc 0000cd5c /system/lib/libc.so (pthread_create+208)
code around pc:
400505f0 e4d3c001 e35c0000 012fff1e e3130003
40050600 e0610003 1afffff9 e3082080 e7df2812
40050610 e4931004 e0400003 f5d3f040 e041c3a2
40050620 e00cc002 e1dcc001 04931004 1a000022
40050630 e041c3a2 e00cc002 e1dcc001 04931004
40050640 1a00001d e041c3a2 e00cc002 e1dcc001
40050650 04931004 1a000018 e041c3a2 e00cc002
40050660 e1dcc001 04931004 1a000013 e041c3a2
40050670 e00cc002 e1dcc001 04931004 1a00000e
40050680 e041c3a2 e00cc002 e1dcc001 04931004
40050690 1a000009 e041c3a2 e00cc002 e1dcc001
400506a0 04931004 1a000004 e041c3a2 e00cc002
400506b0 e1dcc001 04931004 0affffd6 e0800003
400506c0 e31100ff 0a000005 e2800001 e3110cff
400506d0 0a000002 e2800001 e31108ff 12800001
400506e0 e12fff1e e1a03001 eaffffc6 e12fff1e
code around lr:
4012b914 b128ffcf 46224631 e864f7f8 bd702000
4012b924 bd706828 4605b538 460c4608 e908f7f8
4012b934 1c424621 e8bd4628 f7ff4038 b570bfe3
4012b944 6903460e 46144605 d21518d1 429168c2
4012b954 6868d80c 692b4631 18c04622 e842f7f8
4012b964 46214628 4070e8bd ba52f7ff f7ff4621
4012b974 2800ff93 bd70d0ed 0015f06f b537bd70
4012b984 69014604 0508f101 428d68c1 6921d80b
4012b994 18406860 e9c02108 46202300 e8bdb003
4012b9a4 f7ff4030 2108ba35 93009201 ff74f7ff
4012b9b4 9b009a01 d0ea2800 bd30b003 460db538
4012b9c4 46046903 1d1a68c1 d809428a 21046860
4012b9d4 18c26923 60154620 4038e8bd ba18f7ff
4012b9e4 f7ff2104 2800ff59 bd38d0f0 461db570
4012b9f4 46146903 460668c1 0208f103 d80a428a
4012ba04 21086870 18c26933 e9c24630 e8bd4500
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
Click to expand...
Click to collapse
Hope any DEV here can help to solve the problem
Hi,
For long time I had broken camera (purple tint but workaround fix with more copper tape doesn't work) and finally I bought some camera for replacement.
After replace, of course no more purple tint, but on the same system/software/everything - camera apps working one time only. Just take the shot and app (whatever it is, with one exception*) closing with report box.
* Instagram - because go to edit mode after taking picture, not crashing.
I thought - problem with new camera only? But no - taking picture with front camera has the same issue right now.
Doesn't matter ROM (I tried: AICP Marshmallow nightly, XenonHD based Lollipop and Marshmallow, ResurectionRemix based on MM).
Somebody has any idea how this could be fixed?
Full logs from shot taken by base camera app with front and back camera attached.
I think crucial part is here:
Code:
03-23 13:28:38.283 210 210 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-23 13:28:38.283 210 210 F DEBUG : Build fingerprint: 'htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys'
03-23 13:28:38.283 210 210 F DEBUG : Revision: '0'
03-23 13:28:38.283 210 210 F DEBUG : ABI: 'arm'
03-23 13:28:38.284 210 210 F DEBUG : pid: 8063, tid: 8619, name: mm_camera_poll >>> /system/bin/mediaserver <<<
03-23 13:28:38.284 210 210 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x149
03-23 13:28:38.285 749 2723 W NativeCrashListener: Couldn't find ProcessRecord for pid 8063
03-23 13:28:38.303 210 210 F DEBUG : r0 00000101 r1 ffffffff r2 b48402fc r3 80000000
03-23 13:28:38.303 210 210 E DEBUG : AM write failed: Broken pipe
03-23 13:28:38.303 210 210 F DEBUG : r4 afc6a800 r5 af476940 r6 af47694c r7 af476944
03-23 13:28:38.303 210 210 F DEBUG : r8 af475000 r9 b6008024 sl af476938 fp afc6a800
03-23 13:28:38.303 210 210 F DEBUG : ip b483fdb4 sp a71d68d0 lr b481f735 pc b481ef36 cpsr 40070030
03-23 13:28:38.311 210 210 F DEBUG :
03-23 13:28:38.311 210 210 F DEBUG : backtrace:
03-23 13:28:38.311 210 210 F DEBUG : #00 pc 00049f36 /system/lib/hw/camera.vendor.msm8960.so (android::util_get_Hal_obj(camera_device*)+5)
03-23 13:28:38.311 210 210 F DEBUG : #01 pc 0004a731 /system/lib/hw/camera.vendor.msm8960.so (release+52)
03-23 13:28:38.311 210 210 F DEBUG : #02 pc 000046d5 /system/lib/libimage-jpeg-enc-omx-comp.so (handleMessage+164)
03-23 13:28:38.311 210 210 F DEBUG : #03 pc 0003f5f7 /system/lib/libc.so (__pthread_start(void*)+30)
03-23 13:28:38.314 210 210 F DEBUG : #04 pc 00019ccb /system/lib/libc.so (__start_thread+6)
but I don't know how to fix or even go deeper with debug.
Any help?
Thanks in advance
camelek said:
Hi,
For long time I had broken camera (purple tint but workaround fix with more copper tape doesn't work) and finally I bought some camera for replacement.
After replace, of course no more purple tint, but on the same system/software/everything - camera apps working one time only. Just take the shot and app (whatever it is, with one exception*) closing with report box.
* Instagram - because go to edit mode after taking picture, not crashing.
I thought - problem with new camera only? But no - taking picture with front camera has the same issue right now.
Doesn't matter ROM (I tried: AICP Marshmallow nightly, XenonHD based Lollipop and Marshmallow, ResurectionRemix based on MM).
Somebody has any idea how this could be fixed?
Full logs from shot taken by base camera app with front and back camera attached.
I think crucial part is here:
Code:
03-23 13:28:38.283 210 210 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-23 13:28:38.283 210 210 F DEBUG : Build fingerprint: 'htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys'
03-23 13:28:38.283 210 210 F DEBUG : Revision: '0'
03-23 13:28:38.283 210 210 F DEBUG : ABI: 'arm'
03-23 13:28:38.284 210 210 F DEBUG : pid: 8063, tid: 8619, name: mm_camera_poll >>> /system/bin/mediaserver <<<
03-23 13:28:38.284 210 210 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x149
03-23 13:28:38.285 749 2723 W NativeCrashListener: Couldn't find ProcessRecord for pid 8063
03-23 13:28:38.303 210 210 F DEBUG : r0 00000101 r1 ffffffff r2 b48402fc r3 80000000
03-23 13:28:38.303 210 210 E DEBUG : AM write failed: Broken pipe
03-23 13:28:38.303 210 210 F DEBUG : r4 afc6a800 r5 af476940 r6 af47694c r7 af476944
03-23 13:28:38.303 210 210 F DEBUG : r8 af475000 r9 b6008024 sl af476938 fp afc6a800
03-23 13:28:38.303 210 210 F DEBUG : ip b483fdb4 sp a71d68d0 lr b481f735 pc b481ef36 cpsr 40070030
03-23 13:28:38.311 210 210 F DEBUG :
03-23 13:28:38.311 210 210 F DEBUG : backtrace:
03-23 13:28:38.311 210 210 F DEBUG : #00 pc 00049f36 /system/lib/hw/camera.vendor.msm8960.so (android::util_get_Hal_obj(camera_device*)+5)
03-23 13:28:38.311 210 210 F DEBUG : #01 pc 0004a731 /system/lib/hw/camera.vendor.msm8960.so (release+52)
03-23 13:28:38.311 210 210 F DEBUG : #02 pc 000046d5 /system/lib/libimage-jpeg-enc-omx-comp.so (handleMessage+164)
03-23 13:28:38.311 210 210 F DEBUG : #03 pc 0003f5f7 /system/lib/libc.so (__pthread_start(void*)+30)
03-23 13:28:38.314 210 210 F DEBUG : #04 pc 00019ccb /system/lib/libc.so (__start_thread+6)
but I don't know how to fix or even go deeper with debug.
Any help?
Thanks in advance
Click to expand...
Click to collapse
You flashed all kinds of ROMs which have one thing common - camera crashes after taking shot. You could find that out if you read those ROM threads. Try a Sense ROM, and see if the issue remains, but I'm 100% certain it's a bug all those ROMs have in common
dey tuuk ur juurbs
donkeykong1 said:
You flashed all kinds of ROMs which have one thing common - camera crashes after taking shot. You could find that out if you read those ROM threads. Try a Sense ROM, and see if the issue remains, but I'm 100% certain it's a bug all those ROMs have in common
dey tuuk ur juurbs
Click to expand...
Click to collapse
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.
camelek said:
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.
Click to expand...
Click to collapse
Well, backup your current ROM and flash any Sense or GPE ROM and try. I know that all CM or AOSP ROMs have that crashing camera bug
dey tuuk ur juurbs
camelek said:
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.
Click to expand...
Click to collapse
Try with cameringo app first...
Ok, quick summary:
Cameringo (even Lite version) working fine, but I think it's again similar trick is used in Instagram - because always after taking picture there is "picture taken" intent/screen and after press back (or camera button in Instagram) camera is reinitialized. But this app doing this so quick that it's fully acceptable.
With stock ROMs I've came through some hell ride as using AICP or RR my /data was as F2FS partition. So backup whole storage, changing fs, flashing old Lollipop - long story short: never more Anyway camera working fine with HTC app or Lollipop ROM (like Venom), but this unfortunately is not an option, going back to easy hackable system because of camera.
Anyway, thanks for suggestions.
UPDATE: The ROM is now available: http://forum.xda-developers.com/one-mini-2/orig-development/cyanogenmod-13-one-mini-2-t3429360
UPDATE: 30.07.16 1:40Uhr: The camera HAL works now!
UPDATE: 16.07.16 22:02Uhr: Slow SD Card and audio playback fixed!
UPDATE: 16.07.16 21:15Uhr: Data link works now!
UPDATE: 16.07.16 18:30Uhr: Looks good. The modem works now! I could just make the first call. However, I still have problems with the data link.
UPDATE: 11.07.16 18:50Uhr: Good news! CM13 is now booting!
There are still difficulties with the camera, mobile radio, external sdcard and music playback. Pictures can be found here: http://forum.xda-developers.com/showpost.php?p=67699525&postcount=8
UPDATE - 10.07.16 19:05Uhr: Nope, Camera HAL does not work. I fix this later.
UPDATE - 09.07.16 21:04Uhr: Camerawrapper is now working! It was an incorrect kernel HAL configuration. My misstake :laugh:
Unfortunately we still stuck in bootloop...
UPDATE - 09.07.16 20:31Uhr: The CameraWrapper is now starting! However, still with problems:
Code:
07-09 19:33:03.638 750 750 V CameraWrapper: camera_get_number_of_cameras
07-09 19:33:03.638 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.658 750 750 I CameraService: Loaded "Memul Camera Wrapper" camera module
07-09 19:33:03.658 750 750 V CameraWrapper: camera_get_number_of_cameras
07-09 19:33:03.658 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.658 750 750 V CameraWrapper: camera_get_number_of_cameras
07-09 19:33:03.659 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.659 750 750 I CameraFlashlight: Opening camera 0
07-09 19:33:03.659 750 750 V CameraWrapper: camera_get_camera_info
07-09 19:33:03.659 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.659 750 750 V CameraWrapper: camera_device_open
07-09 19:33:03.659 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.786 750 750 E CameraWrapper: vendor camera open fail
07-09 19:33:03.786 750 750 E CameraFlashlight: Could not open camera 0: -19
07-09 19:33:03.786 750 750 E CameraFlashlight: connectCameraDevice: initializing camera 0 failed
07-09 19:33:03.786 750 750 I CameraFlashlight: Destroying camera 0
07-09 19:33:03.786 750 750 E CameraFlashlight: findFlashUnits: failed to check if camera 0 has a flash unit. No such device (-19)
07-09 19:33:03.786 750 750 I CameraFlashlight: Opening camera 1
07-09 19:33:03.786 750 750 V CameraWrapper: camera_get_camera_info
07-09 19:33:03.786 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.787 750 750 V CameraWrapper: camera_device_open
07-09 19:33:03.787 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.926 750 750 E CameraWrapper: vendor camera open fail
07-09 19:33:03.926 750 750 E CameraFlashlight: Could not open camera 1: -19
07-09 19:33:03.926 750 750 E CameraFlashlight: connectCameraDevice: initializing camera 1 failed
07-09 19:33:03.926 750 750 I CameraFlashlight: Destroying camera 1
07-09 19:33:03.926 750 750 E CameraFlashlight: findFlashUnits: failed to check if camera 1 has a flash unit. No such device (-19)
07-09 19:33:03.926 750 750 V CameraWrapper: camera_get_camera_info
07-09 19:33:03.926 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.927 750 750 V CameraWrapper: camera_get_camera_info
07-09 19:33:03.927 750 750 V CameraWrapper: check_vendor_module
UPDATE - 09.07.16 15:19Uhr: I got fixed the initialization. Now I put unfortunately steadily for 2 days at the CameraWrapper. We're here still firmly in bootloop. At the moment I have no idea how to fix it :/
UPDATE - 05.07.16 20:38Uhr: The Boringssl-compat wrapper does not resolve the problem but the new Adreno driver for 3xx / 4xx works fine! I come now to the bootanimation. However, the boot process gets stuck.
Hey,
I'm from Germany and my English is unfortunately not the best. Sorry
For several weeks I try to get cm13 on my memul to run.
I want, as long as I get to run CM13, share the finished rom with you.
I managed yesterday to compile the rom.
Unfortunately, I was stuck in a bootloop.
The Adreno driver still makes problems:
Code:
07-05 04:25:48.238 2395 2395 F libc : page record for 0xb6f0d02c was not found (block_size=16)
07-05 04:25:48.251 2399 2399 F libc : page record for 0xb6ee702c was not found (block_size=16)
07-05 04:25:48.254 2398 2398 F libc : page record for 0xb6f3b02c was not found (block_size=16)
07-05 04:25:48.261 2397 2397 F libc : page record for 0xb6ed102c was not found (block_size=16)
07-05 04:25:48.342 2393 2393 I SurfaceFlinger: SurfaceFlinger is starting
07-04 04:25:48.343 2393 2393 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
07-04 04:25:48.346 2393 2393 E libEGL : load_driver(/vendor/lib/egl/libEGL_adreno.so): dlopen failed: cannot locate symbol "RSA_verify_PKCS1_PSS" referenced by "/system/vendor/lib/egl/libEGL_adreno.so"...
07-04 04:25:48.346 2393 2393 F libEGL : couldn't find an OpenGL ES implementation
07-04 04:25:48.346 2393 2393 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2393 (surfaceflinger)
07-04 04:25:48.346 248 248 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
07-04 04:25:48.346 248 248 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
07-04 04:25:48.346 248 248 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
07-04 04:25:48.447 248 248 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-04 04:25:48.447 248 248 F DEBUG : CM Version: '13.0-20160704-UNOFFICIAL-memul'
07-04 04:25:48.447 248 248 F DEBUG : Build fingerprint: 'htc/htc_europe/htc_memul:4.4.2/KOT49H/355312.1:user/release-keys'
07-04 04:25:48.447 248 248 F DEBUG : Revision: '0'
07-04 04:25:48.447 248 248 F DEBUG : ABI: 'arm'
07-04 04:25:48.447 248 248 F DEBUG : pid: 2393, tid: 2393, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
07-04 04:25:48.448 248 248 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
07-04 04:25:48.453 248 248 F DEBUG : Abort message: 'couldn't find an OpenGL ES implementation'
07-04 04:25:48.454 248 248 F DEBUG : r0 00000000 r1 00000959 r2 00000006 r3 b6fc7b8c
07-04 04:25:48.454 248 248 F DEBUG : r4 b6fc7b94 r5 b6fc7b44 r6 00000002 r7 0000010c
07-04 04:25:48.454 248 248 F DEBUG : r8 00000000 r9 ffff51ea sl 00000000 fp beda6a2c
07-04 04:25:48.454 248 248 F DEBUG : ip 00000006 sp beda64b0 lr b6e13c41 pc b6e16030 cpsr 400f0010
07-04 04:25:48.464 248 248 F DEBUG :
07-04 04:25:48.464 248 248 F DEBUG : backtrace:
07-04 04:25:48.464 248 248 F DEBUG : #00 pc 00044030 /system/lib/libc.so (tgkill+12)
07-04 04:25:48.464 248 248 F DEBUG : #01 pc 00041c3d /system/lib/libc.so (pthread_kill+32)
07-04 04:25:48.464 248 248 F DEBUG : #02 pc 0001b837 /system/lib/libc.so (raise+10)
07-04 04:25:48.464 248 248 F DEBUG : #03 pc 000189e9 /system/lib/libc.so (__libc_android_abort+34)
07-04 04:25:48.464 248 248 F DEBUG : #04 pc 000167c4 /system/lib/libc.so (abort+4)
07-04 04:25:48.464 248 248 F DEBUG : #05 pc 00008af7 /system/lib/libcutils.so (__android_log_assert+86)
07-04 04:25:48.464 248 248 F DEBUG : #06 pc 00047b8b /system/lib/libEGL.so
07-04 04:25:48.464 248 248 F DEBUG : #07 pc 00013e5d /system/lib/libEGL.so
07-04 04:25:48.465 248 248 F DEBUG : #08 pc 00014975 /system/lib/libEGL.so (eglGetDisplay+24)
07-04 04:25:48.465 248 248 F DEBUG : #09 pc 0001cdef /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger4initEv+46)
07-04 04:25:48.465 248 248 F DEBUG : #10 pc 00000ecb /system/bin/surfaceflinger
07-04 04:25:48.465 248 248 F DEBUG : #11 pc 00016671 /system/lib/libc.so (__libc_init+44)
07-04 04:25:48.465 248 248 F DEBUG : #12 pc 00000d90 /system/bin/surfaceflinger
07-04 04:25:48.543 248 248 F DEBUG :
07-04 04:25:48.543 248 248 F DEBUG : Tombstone written to: /data/tombstones/tombstone_05
I will keep you up to date!
This is my first rom here on xda. Should I do something wrong, I am grateful for a hint
Hi And Thank You. Great news. I hope you manage in your project.
nightcore500 said:
UPDATE - 05.07.16 20:38Uhr: The new Adreno driver for 3xx / 4xx works fine! I come now to the bootanimation. However, the boot process gets stuck.
Hey,
I'm from Germany and my English is unfortunately not the best. Sorry
For several weeks I try to get cm13 on my memul to run.
I want, as long as I get to run CM13, share the finished rom with you.
I managed yesterday to compile the rom.
Unfortunately, I was stuck in a bootloop.
The Adreno driver still makes problems:
I will keep you up to date!
This is my first rom here on xda. Should I do something wrong, I am grateful for a hint
Click to expand...
Click to collapse
Welcome! Good to see somebody else porting CM13 for Memul. I tried it myself in the last couple of months, but didn't get it to build the kernel... Great job! Would you mind sharing your source? I really like to know what i did wrong in my device tree adjustments. Did you create the device folder(s) from the scratch? I used Soenisti's source as skeleton - https://github.com/Aronar?tab=repositories
I'm smiling already...
Siluxsept said:
Welcome! Good to see somebody else porting CM13 for Memul. I tried it myself in the last couple of months, but didn't get it to build the kernel... Great job! Would you mind sharing your source? I really like to know what i did wrong in my device tree adjustments. Did you create the device folder(s) from the scratch? I used Soenisti's source as skeleton
Click to expand...
Click to collapse
Yes, I will share the source with you as soon as I get the ROM stable. No, i use dogaozkaraca's configuration for beginning and changed many things. I had the kernel problems also. The kernel config for memul is outdated. Here are some changes needed to compile the kernel.
I have now solved the biggest problems! But we still stuck firmly in bootloop.
The system server is crashing. Looks like a right trouble. If there is no big problem to be fixed that.
I'm stuck here:
Code:
07-10 15:13:27.134 1219 1240 I ServiceManager: Waiting for service sensorservice...
07-10 15:13:27.856 1219 1379 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 1379 (system_server)
07-10 15:13:27.857 247 247 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
07-10 15:13:27.857 247 247 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
07-10 15:13:27.857 247 247 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
07-10 15:13:27.958 247 247 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-10 15:13:27.958 247 247 F DEBUG : CM Version: '13.0-20160710-UNOFFICIAL-memul'
07-10 15:13:27.958 247 247 F DEBUG : Build fingerprint: 'htc/htc_europe/htc_memul:4.4.2/KOT49H/355312.1:user/release-keys'
07-10 15:13:27.958 247 247 F DEBUG : Revision: '0'
07-10 15:13:27.958 247 247 F DEBUG : ABI: 'arm'
07-10 15:13:27.958 247 247 F DEBUG : pid: 1219, tid: 1379, name: system_server >>> system_server <<<
07-10 15:13:27.958 247 247 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
07-10 15:13:27.980 247 247 F DEBUG : r0 00000000 r1 00100472 r2 705cf8b8 r3 a09b1610
07-10 15:13:27.980 247 247 F DEBUG : r4 00000000 r5 00000008 r6 b894c570 r7 00000008
07-10 15:13:27.980 247 247 F DEBUG : r8 a09b16b4 r9 a09b1680 sl 00000000 fp b897e978
07-10 15:13:27.981 247 247 F DEBUG : ip b6e6a440 sp a09b1600 lr b6e1112f pc b6e0d2d2 cpsr 600d0030
07-10 15:13:27.989 247 247 F DEBUG :
07-10 15:13:27.989 247 247 F DEBUG : backtrace:
07-10 15:13:27.989 247 247 F DEBUG : #00 pc 000852d2 /system/lib/libandroid_runtime.so
07-10 15:13:27.989 247 247 F DEBUG : #01 pc 0008912b /system/lib/libandroid_runtime.so
07-10 15:13:27.989 247 247 F DEBUG : #02 pc 000199b1 /system/lib/libbinder.so (_ZN7android7BBinder8transactEjRKNS_6ParcelEPS1_j+60)
07-10 15:13:27.989 247 247 F DEBUG : #03 pc 0001b857 /system/lib/libbinder.so
07-10 15:13:27.989 247 247 F DEBUG : #04 pc 000198bb /system/lib/libbinder.so (_ZN7android13AppOpsManager18permissionToOpCodeERKNS_8String16E+26)
07-10 15:13:27.989 247 247 F DEBUG : #05 pc 000472c3 /system/lib/libgui.so (_ZN7android6SensorC1EPK8sensor_ti+882)
07-10 15:13:27.989 247 247 F DEBUG : #06 pc 00008cb7 /system/lib/libsensorservice.so
07-10 15:13:27.989 247 247 F DEBUG : #07 pc 0000ac7d /system/lib/libsensorservice.so
07-10 15:13:27.989 247 247 F DEBUG : #08 pc 0001592f /system/lib/libandroid_servers.so (_ZN7android10sensorInitEPv+82)
07-10 15:13:27.989 247 247 F DEBUG : #09 pc 0004153f /system/lib/libc.so (_ZL15__pthread_startPv+30)
07-10 15:13:27.989 247 247 F DEBUG : #10 pc 0001906b /system/lib/libc.so (__start_thread+6)
Looks like the sensorservice don't work. Maybe someone has an idea?
Good news! CM13 is now booting!
There are still difficulties with the camera, mobile radio, external sdcard and music playback.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Congrats man for your efforts, Im spreading the word, hopefully someone will show up who might be able to help..
Hey this looks very cool!
There is hope for our memul!
Finally someone with will and skills.
I hope you don't give up....
It's a nice phone but dev support sucks at whistle
Looks good. The modem works now! I could just make the first call. However, I still have problems with the data link.
Update: We have an internet connection!
I'm smiling more now...Keep it coming, keep up the good work...
Thanks man...I'm quite hopeful...
I have just fixed the camera problems. I think we are now ready for the first CM13 build. I now begin the last recompile and will publish the finished rom after a short test tomorrow here in the forum. I look forward to tester.
nightcore500 said:
I have just fixed the camera problems. I think we are now ready for the first CM13 build. I now begin the last recompile and will publish the finished rom after a short test tomorrow here in the forum. I look forward to tester.
Click to expand...
Click to collapse
I'm game for testing. But I do have one question. If you have used any CM12.1 build, how does the camera perform compared to it? One of the reasons I have stuck to the stock ROM is that the camera froze a lot.
I use the camera proprietary files from the a5 device. The hardware of the devices is almost the same
The ROM is now available: http://forum.xda-developers.com/one-mini-2/orig-development/cyanogenmod-13-one-mini-2-t3429360
I've got the following problems:
-There are stutters sometimes ~After reflashing, the stutters disappeared
-Using headphones via AUX, there is a crackle on the right side; with stockrom it worked just fine
Anyway, it's a great ROM
error274 said:
I've got the following problems:
-Sometimes there is a stutter for about an half second
-Using headphones via AUX, there is a crackle on the right side; with stockrom it worked just fine
Anyway, it's a great ROM
Click to expand...
Click to collapse
Sounds like there is some dirt in the headphones port.
Try to blow in the hole or use some other tools to clean it.
But be carefull.
Have not such issues with this rom.
Okay, I will try
At present, Mi Max has 1 important bug fix that no one has been able to handle. Devs and users who know how to fix this work out for Mi Max to work better. How to handle things like this:
https://gitlab.com/Okeys/proprietary_vendor_oneplus/commit/0c52751deacdd97b13f7145816a3a3b673229b1c
Exp for kenzo: https://github.com/aranhid/proprietary_vendor_xiaomi/commit/3f99cec0e893ba4f135538abb2ee030c098ba3d4
If fixed the camera or flashlight in some roms like as aosp will work fast, no lags
Please join us!
Original file not modified (flashable): https://www.androidfilehost.com/?fid=1395089523397946186
Bugs in logcat:
Code:
04-18 18:59:59.841 416 6592 I [email protected]: Closing camera 0
04-18 18:59:59.849 416 6592 I qomx_image_core: OMX_Deinit:119] Complete
04-18 18:59:59.851 416 6592 I Thermal-Lib: Thermal-Lib-Client: Unregisteration is successfull for handle:1
04-18 18:59:59.851 464 608 I ThermalEngine: Thermal-Server: removing client on fd 58
04-18 18:59:59.851 416 6592 I Thermal-Lib: Thermal-Lib-Client: Unregisteration is successfull for handle:2
04-18 18:59:59.872 8492 8801 F libc : FORTIFY: pthread_mutex_destroy called on a destroyed mutex (0xe75322dc)
04-18 18:59:59.873 8492 8801 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 8801 (CAM_stopisp), pid 8492 (mm-qcamera-daem)
04-18 18:59:59.874 413 6339 D audio_hw_primary: start_output_stream: exit
04-18 18:59:59.898 8807 8807 I crash_dump32: type=1400 audit(0.0:2415): avc: denied { ptrace } for uid=1006 scontext=u:r:crash_dump:s0 tcontext=u:r:init:s0 tclass=process permissive=1
04-18 18:59:59.955 8807 8807 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
04-18 18:59:59.948 8799 8799 I CAM_stopsensor: type=1400 audit(0.0:2416): avc: denied { ioctl } for uid=1006 path="/dev/v4l-subdev19" dev="tmpfs" ino=16726 ioctlcmd=56c1 scontext=u:r:init:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
04-18 18:59:59.955 495 495 I /system/bin/tombstoned: received crash request for pid 8801
04-18 18:59:59.956 8807 8807 I crash_dump32: performing dump of process 8492 (target tid = 8801)
04-18 18:59:59.977 8807 8807 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-18 18:59:59.978 8807 8807 F DEBUG : Build fingerprint: 'Xiaomi/hydrogen/hydrogen:6.0.1/MMB29M/V8.2.3.0.MBCCNDL:user/release-keys'
04-18 18:59:59.978 8807 8807 F DEBUG : Revision: '0'
04-18 18:59:59.978 8807 8807 F DEBUG : ABI: 'arm'
04-18 18:59:59.978 8807 8807 F DEBUG : pid: 8492, tid: 8801, name: CAM_stopisp >>> /system/bin/mm-qcamera-daemon <<<
04-18 18:59:59.978 8807 8807 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
04-18 18:59:59.978 8807 8807 F DEBUG : Abort message: 'FORTIFY: pthread_mutex_destroy called on a destroyed mutex (0xe75322dc)'
04-18 18:59:59.978 8807 8807 F DEBUG : r0 00000000 r1 00002261 r2 00000006 r3 00000008
04-18 18:59:59.978 8807 8807 F DEBUG : r4 0000212c r5 00002261 r6 e648188c r7 0000010c
04-18 18:59:59.978 8807 8807 F DEBUG : r8 00000002 r9 0005e848 r10 00000000 r11 0005e848
04-18 18:59:59.979 8807 8807 F DEBUG : ip ee72fd8c sp e6481878 lr ee6a8e49 pc ee6a0c9a
04-18 18:59:59.982 8807 8807 F DEBUG :
04-18 18:59:59.982 8807 8807 F DEBUG : backtrace:
04-18 18:59:59.982 8807 8807 F DEBUG : #00 pc 0001cc9a /system/lib/libc.so (abort+58)
04-18 18:59:59.982 8807 8807 F DEBUG : #01 pc 00064533 /system/lib/libc.so (__fortify_fatal(char const*, ...)+26)
04-18 18:59:59.982 8807 8807 F DEBUG : #02 pc 000643ed /system/lib/libc.so (pthread_mutex_destroy+128)
04-18 18:59:59.982 8807 8807 F DEBUG : #03 pc 00006ffd /system/vendor/lib/libmmcamera2_isp_modules.so
04-18 18:59:59.982 8807 8807 F DEBUG : #04 pc 0000e23d /system/vendor/lib/libmmcamera2_mct.so
04-18 18:59:59.982 8807 8807 F DEBUG : #05 pc 000632c9 /system/lib/libc.so (__pthread_start(void*)+22)
04-18 18:59:59.982 8807 8807 F DEBUG : #06 pc 0001de5d /system/lib/libc.so (__start_thread+24)
04-18 19:00:00.148 1116 2581 W NativeCrashListener: Couldn't find ProcessRecord for pid 8492
04-18 19:00:00.148 495 495 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_18
04-18 19:00:00.165 1116 1492 I BootReceiver: Copying /data/tombstones/tombstone_18 to DropBox (SYSTEM_TOMBSTONE)
ps: I fixed it in the sources
I am not Dev but I can tester
MI MAX cihazımdan Tapatalk kullanılarak gönderildi
I want to join and help, but as of now, I don't have any skills in any programing language. Even though I can build a Roms, it's just using someone else device tree and build with the source.
gothic84 said:
I want to join and help, but as of now, I don't have any skills in any programing language. Even though I can build a Roms, it's just using someone else device tree and build with the source.
Click to expand...
Click to collapse
You try to understand ASM software that dev mentioned?
dungphp said:
You try to understand ASM software that dev mentioned?
Click to expand...
Click to collapse
Yes, I try to understand and want to learn about it. I have downloaded the file and have a look inside the Zip.
it's like a camera driver for our Mi Max and the addon script for fixing the binary.
Some roms has this problem: Nitrogen, MSM Extended, PE Caf, Syberia
EDIT: NO NEED FIX BY THIS METHOD, I FIXED IT FROM SOURCES
dungphp said:
Some roms has this problem: Nitrogen, MSM Extended, PE Caf, Syberia
EDIT: NO NEED FIX BY THIS METHOD, I FIXED IT FROM SOURCES
Click to expand...
Click to collapse
Stable camera coming ?
MI MAX cihazımdan Tapatalk kullanılarak gönderildi
dungphp said:
Some roms has this problem: Nitrogen, MSM Extended, PE Caf, Syberia
EDIT: NO NEED FIX BY THIS METHOD, I FIXED IT FROM SOURCES
Click to expand...
Click to collapse
Genius you are...
madmax59 said:
Stable camera coming ?
MI MAX cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
flashlight, camera bugs in some roms above can be fixed now
ZainBilq said:
Genius you are...
Click to expand...
Click to collapse
For example, I have 2 PE CAF versions, 1 old version has not fix this error and 1 new version has solved this error
https://androidfilehost.com/user/?w=settings-dev-files&flid=292476
dungphp said:
For example, I have 2 PE CAF versions, 1 old version has not fix this error and 1 new version has solved this error
https://androidfilehost.com/user/?w=settings-dev-files&flid=292476
Click to expand...
Click to collapse
i am on your latest superiorOs nemesis...it's perfect balance between battery and performance....
ZainBilq said:
i am on your latest superiorOs nemesis...it's perfect balance between battery and performance....
Click to expand...
Click to collapse
Yes, that build realy smooth !
dungphp said:
flashlight, camera bugs in some roms above can be fixed now
Click to expand...
Click to collapse
great to hear that you already fixed it. you fixed on rom source or device source?
gothic84 said:
great to hear that you already fixed it. you fixed on rom source or device source?
Click to expand...
Click to collapse
in rom sources. i have tested with Nitrogen, PE Caf, MSM extended
dungphp said:
in rom sources. i have tested with Nitrogen, PE Caf, MSM extended
Click to expand...
Click to collapse
Great, thank's for your contribution for our mi max.
We proud to have you here.
dungphp said:
flashlight, camera bugs in some roms above can be fixed now
Click to expand...
Click to collapse
Which rom first coming?
MI MAX cihazımdan Tapatalk kullanılarak gönderildi
dungphp said:
in rom sources. i have tested with Nitrogen, PE Caf, MSM extended
Click to expand...
Click to collapse
Pls release msm extended....I am waiting for long time from you....
ZainBilq said:
Pls release msm extended....I am waiting for long time from you....
Click to expand...
Click to collapse
I will send fix to Alex
What about this logcat from my Mi Max running ViperOS, is there anything to fix?
Code:
--------- beginning of system
--------- beginning of crash
04-20 00:48:51.415 625 625 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.433 637 637 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.471 640 640 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.519 648 648 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.532 660 660 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.544 661 661 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 01:11:30.320 528 11306 F libc : Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xee6197e0 in tid 11306 (Binder:528_2), pid 528 (cameraserver)
04-20 01:11:30.383 11401 11401 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-20 01:11:30.383 11401 11401 F DEBUG : LineageOS Version: 'unknown'
04-20 01:11:30.383 11401 11401 F DEBUG : Build fingerprint: 'Xiaomi/hydrogen/hydrogen:7.0/NRD90M/V10.1.1.0.NBCMIFI:user/release-keys'
04-20 01:11:30.383 11401 11401 F DEBUG : Revision: '0'
04-20 01:11:30.383 11401 11401 F DEBUG : ABI: 'arm'
04-20 01:11:30.383 11401 11401 F DEBUG : pid: 528, tid: 11306, name: Binder:528_2 >>> /system/bin/cameraserver <<<
04-20 01:11:30.383 11401 11401 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xee6197e0
04-20 01:11:30.383 11401 11401 F DEBUG : r0 eda8d06c r1 80050000 r2 ee6197e0 r3 ffffffff
04-20 01:11:30.383 11401 11401 F DEBUG : r4 00000000 r5 ee502168 r6 0000002d r7 00000001
04-20 01:11:30.384 11401 11401 F DEBUG : r8 ee502468 r9 00000000 r10 00000031 r11 00000000
04-20 01:11:30.384 11401 11401 F DEBUG : ip 00000001 sp ed5fee28 lr ee7cb46d pc ee6197e0
04-20 01:11:30.438 11401 11401 F DEBUG :
04-20 01:11:30.438 11401 11401 F DEBUG : backtrace:
04-20 01:11:30.438 11401 11401 F DEBUG : #00 pc 000197e0 [anon:libc_malloc:ee600000]
04-20 01:11:30.438 11401 11401 F DEBUG : #01 pc 0000346b /system/lib/libcamera_metadata.so (validate_camera_metadata_structure+406)
04-20 01:11:30.438 11401 11401 F DEBUG : #02 pc 000c7b33 /system/lib/libcameraservice.so (_ZNSt3__110__function6__funcIZN7android13Camera3Device12HalInterface31constructDefaultRequestSettingsE24camera3_request_templatePP15camera_metadataE3$_4NS_9allocatorIS9_EEFvNS2_8hardware6camera6common4V1_06StatusERKNSC_8hidl_vecIhEEEEclEOSG_SK_+38)
04-20 01:11:30.438 11401 11401 F DEBUG : #03 pc 0001e1cf /system/lib/[email protected] (android::hardware::camera::device::V3_2::BpHwCameraDeviceSession::_hidl_constructDefaultRequestSettings(android::hardware::IInterface*, android::hardware::details::HidlInstrumentor*, android::hardware::camera::device::V3_2::RequestTemplate, std::__1::function<void (android::hardware::camera::common::V1_0::Status, android::hardware::hidl_vec<unsigned char> const&)>)+486)
04-20 01:11:30.438 11401 11401 F DEBUG : #04 pc 0001f89f /system/lib/[email protected] (android::hardware::camera::device::V3_2::BpHwCameraDeviceSession::constructDefaultRequestSettings(android::hardware::camera::device::V3_2::RequestTemplate, std::__1::function<void (android::hardware::camera::common::V1_0::Status, android::hardware::hidl_vec<unsigned char> const&)>)+70)
04-20 01:11:30.438 11401 11401 F DEBUG : #05 pc 000b8721 /system/lib/libcameraservice.so (android::Camera3Device::HalInterface::constructDefaultRequestSettings(camera3_request_template, camera_metadata**)+112)
04-20 01:11:30.438 11401 11401 F DEBUG : #06 pc 000bca91 /system/lib/libcameraservice.so (android::Camera3Device::createDefaultRequest(int, android::CameraMetadata*)+160)
04-20 01:11:30.438 11401 11401 F DEBUG : #07 pc 0009e623 /system/lib/libcameraservice.so (android::camera2::Parameters::getDefaultFocalLength(android::CameraDeviceBase*)+174)
04-20 01:11:30.438 11401 11401 F DEBUG : #08 pc 0009d8ed /system/lib/libcameraservice.so (android::camera2::Parameters::buildFastInfo(android::CameraDeviceBase*)+652)
04-20 01:11:30.438 11401 11401 F DEBUG : #09 pc 0009bb8b /system/lib/libcameraservice.so (android::camera2::Parameters::initialize(android::CameraDeviceBase*, int)+66)
04-20 01:11:30.438 11401 11401 F DEBUG : #10 pc 00095cfb /system/lib/libcameraservice.so (int android::Camera2Client::initializeImpl<android::sp<android::CameraProviderManager>>(android::sp<android::CameraProviderManager>, android::String8 const&)+134)
04-20 01:11:30.438 11401 11401 F DEBUG : #11 pc 00095c3b /system/lib/libcameraservice.so (android::Camera2Client::initialize(android::sp<android::CameraProviderManager>, android::String8 const&)+46)
04-20 01:11:30.438 11401 11401 F DEBUG : #12 pc 0007c547 /system/lib/libcameraservice.so (_ZN7android13CameraService13connectHelperINS_8hardware13ICameraClientENS0_6ClientEEENS_6binder6StatusERKNS_2spIT_EERKNS_7String8EiiRKNS_8String16EiiNS0_8apiLevelEbbRNS7_IT0_EE+1370)
04-20 01:11:30.438 11401 11401 F DEBUG : #13 pc 0007e5bd /system/lib/libcameraservice.so (android::CameraService::connect(android::sp<android::hardware::ICameraClient> const&, int, android::String16 const&, int, int, android::sp<android::hardware::ICamera>*)+120)
04-20 01:11:30.438 11401 11401 F DEBUG : #14 pc 0007e737 /system/lib/libcameraservice.so (_ZTv0_n36_N7android13CameraService7connectERKNS_2spINS_8hardware13ICameraClientEEEiRKNS_8String16EiiPNS1_INS2_7ICameraEEE+46)
04-20 01:11:30.438 11401 11401 F DEBUG : #15 pc 00020185 /system/lib/libcamera_client.so (android::hardware::BnCameraService::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+396)
04-20 01:11:30.438 11401 11401 F DEBUG : #16 pc 00080f75 /system/lib/libcameraservice.so (android::CameraService::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+348)
04-20 01:11:30.438 11401 11401 F DEBUG : #17 pc 00036059 /system/lib/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+72)
04-20 01:11:30.438 11401 11401 F DEBUG : #18 pc 0003d76d /system/lib/libbinder.so (android::IPCThreadState::executeCommand(int)+404)
04-20 01:11:30.438 11401 11401 F DEBUG : #19 pc 0003d4ff /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+106)
04-20 01:11:30.439 11401 11401 F DEBUG : #20 pc 0003da1f /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+38)
04-20 01:11:30.439 11401 11401 F DEBUG : #21 pc 000542dd /system/lib/libbinder.so (android::PoolThread::threadLoop()+12)
04-20 01:11:30.439 11401 11401 F DEBUG : #22 pc 0000c087 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+166)
04-20 01:11:30.439 11401 11401 F DEBUG : #23 pc 00063fd9 /system/lib/libc.so (__pthread_start(void*)+22)
04-20 01:11:30.439 11401 11401 F DEBUG : #24 pc 0001defd /system/lib/libc.so (__start_thread+24)
--------- beginning of main
gothic84 said:
What about this logcat from my Mi Max running ViperOS, is there anything to fix?
Code:
--------- beginning of system
--------- beginning of crash
04-20 00:48:51.415 625 625 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.433 637 637 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.471 640 640 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.519 648 648 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.532 660 660 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 00:48:51.544 661 661 F linker : CANNOT LINK EXECUTABLE "slim_daemon": library "libsensorndkbridge.so" not found
04-20 01:11:30.320 528 11306 F libc : Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xee6197e0 in tid 11306 (Binder:528_2), pid 528 (cameraserver)
04-20 01:11:30.383 11401 11401 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-20 01:11:30.383 11401 11401 F DEBUG : LineageOS Version: 'unknown'
04-20 01:11:30.383 11401 11401 F DEBUG : Build fingerprint: 'Xiaomi/hydrogen/hydrogen:7.0/NRD90M/V10.1.1.0.NBCMIFI:user/release-keys'
04-20 01:11:30.383 11401 11401 F DEBUG : Revision: '0'
04-20 01:11:30.383 11401 11401 F DEBUG : ABI: 'arm'
04-20 01:11:30.383 11401 11401 F DEBUG : pid: 528, tid: 11306, name: Binder:528_2 >>> /system/bin/cameraserver <<<
04-20 01:11:30.383 11401 11401 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xee6197e0
04-20 01:11:30.383 11401 11401 F DEBUG : r0 eda8d06c r1 80050000 r2 ee6197e0 r3 ffffffff
04-20 01:11:30.383 11401 11401 F DEBUG : r4 00000000 r5 ee502168 r6 0000002d r7 00000001
04-20 01:11:30.384 11401 11401 F DEBUG : r8 ee502468 r9 00000000 r10 00000031 r11 00000000
04-20 01:11:30.384 11401 11401 F DEBUG : ip 00000001 sp ed5fee28 lr ee7cb46d pc ee6197e0
04-20 01:11:30.438 11401 11401 F DEBUG :
04-20 01:11:30.438 11401 11401 F DEBUG : backtrace:
04-20 01:11:30.438 11401 11401 F DEBUG : #00 pc 000197e0 [anon:libc_malloc:ee600000]
04-20 01:11:30.438 11401 11401 F DEBUG : #01 pc 0000346b /system/lib/libcamera_metadata.so (validate_camera_metadata_structure+406)
04-20 01:11:30.438 11401 11401 F DEBUG : #02 pc 000c7b33 /system/lib/libcameraservice.so (_ZNSt3__110__function6__funcIZN7android13Camera3Device12HalInterface31constructDefaultRequestSettingsE24camera3_request_templatePP15camera_metadataE3$_4NS_9allocatorIS9_EEFvNS2_8hardware6camera6common4V1_06StatusERKNSC_8hidl_vecIhEEEEclEOSG_SK_+38)
04-20 01:11:30.438 11401 11401 F DEBUG : #03 pc 0001e1cf /system/lib/[email protected] (android::hardware::camera::device::V3_2::BpHwCameraDeviceSession::_hidl_constructDefaultRequestSettings(android::hardware::IInterface*, android::hardware::details::HidlInstrumentor*, android::hardware::camera::device::V3_2::RequestTemplate, std::__1::function<void (android::hardware::camera::common::V1_0::Status, android::hardware::hidl_vec<unsigned char> const&)>)+486)
04-20 01:11:30.438 11401 11401 F DEBUG : #04 pc 0001f89f /system/lib/[email protected] (android::hardware::camera::device::V3_2::BpHwCameraDeviceSession::constructDefaultRequestSettings(android::hardware::camera::device::V3_2::RequestTemplate, std::__1::function<void (android::hardware::camera::common::V1_0::Status, android::hardware::hidl_vec<unsigned char> const&)>)+70)
04-20 01:11:30.438 11401 11401 F DEBUG : #05 pc 000b8721 /system/lib/libcameraservice.so (android::Camera3Device::HalInterface::constructDefaultRequestSettings(camera3_request_template, camera_metadata**)+112)
04-20 01:11:30.438 11401 11401 F DEBUG : #06 pc 000bca91 /system/lib/libcameraservice.so (android::Camera3Device::createDefaultRequest(int, android::CameraMetadata*)+160)
04-20 01:11:30.438 11401 11401 F DEBUG : #07 pc 0009e623 /system/lib/libcameraservice.so (android::camera2::Parameters::getDefaultFocalLength(android::CameraDeviceBase*)+174)
04-20 01:11:30.438 11401 11401 F DEBUG : #08 pc 0009d8ed /system/lib/libcameraservice.so (android::camera2::Parameters::buildFastInfo(android::CameraDeviceBase*)+652)
04-20 01:11:30.438 11401 11401 F DEBUG : #09 pc 0009bb8b /system/lib/libcameraservice.so (android::camera2::Parameters::initialize(android::CameraDeviceBase*, int)+66)
04-20 01:11:30.438 11401 11401 F DEBUG : #10 pc 00095cfb /system/lib/libcameraservice.so (int android::Camera2Client::initializeImpl<android::sp<android::CameraProviderManager>>(android::sp<android::CameraProviderManager>, android::String8 const&)+134)
04-20 01:11:30.438 11401 11401 F DEBUG : #11 pc 00095c3b /system/lib/libcameraservice.so (android::Camera2Client::initialize(android::sp<android::CameraProviderManager>, android::String8 const&)+46)
04-20 01:11:30.438 11401 11401 F DEBUG : #12 pc 0007c547 /system/lib/libcameraservice.so (_ZN7android13CameraService13connectHelperINS_8hardware13ICameraClientENS0_6ClientEEENS_6binder6StatusERKNS_2spIT_EERKNS_7String8EiiRKNS_8String16EiiNS0_8apiLevelEbbRNS7_IT0_EE+1370)
04-20 01:11:30.438 11401 11401 F DEBUG : #13 pc 0007e5bd /system/lib/libcameraservice.so (android::CameraService::connect(android::sp<android::hardware::ICameraClient> const&, int, android::String16 const&, int, int, android::sp<android::hardware::ICamera>*)+120)
04-20 01:11:30.438 11401 11401 F DEBUG : #14 pc 0007e737 /system/lib/libcameraservice.so (_ZTv0_n36_N7android13CameraService7connectERKNS_2spINS_8hardware13ICameraClientEEEiRKNS_8String16EiiPNS1_INS2_7ICameraEEE+46)
04-20 01:11:30.438 11401 11401 F DEBUG : #15 pc 00020185 /system/lib/libcamera_client.so (android::hardware::BnCameraService::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+396)
04-20 01:11:30.438 11401 11401 F DEBUG : #16 pc 00080f75 /system/lib/libcameraservice.so (android::CameraService::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+348)
04-20 01:11:30.438 11401 11401 F DEBUG : #17 pc 00036059 /system/lib/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+72)
04-20 01:11:30.438 11401 11401 F DEBUG : #18 pc 0003d76d /system/lib/libbinder.so (android::IPCThreadState::executeCommand(int)+404)
04-20 01:11:30.438 11401 11401 F DEBUG : #19 pc 0003d4ff /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+106)
04-20 01:11:30.439 11401 11401 F DEBUG : #20 pc 0003da1f /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+38)
04-20 01:11:30.439 11401 11401 F DEBUG : #21 pc 000542dd /system/lib/libbinder.so (android::PoolThread::threadLoop()+12)
04-20 01:11:30.439 11401 11401 F DEBUG : #22 pc 0000c087 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+166)
04-20 01:11:30.439 11401 11401 F DEBUG : #23 pc 00063fd9 /system/lib/libc.so (__pthread_start(void*)+22)
04-20 01:11:30.439 11401 11401 F DEBUG : #24 pc 0001defd /system/lib/libc.so (__start_thread+24)
--------- beginning of main
Click to expand...
Click to collapse
Add libsensorndkbridge to msm8956.mk
does the flashlight slow off icon in qs ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS
ABOUT
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
Camera moto mods (Hasselblad, 360, etc)
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/marcost2/kernel_motorola_msm8953
You can also join our Telegram Channels:
Global: https://t.me/z2play
Moto Z2 Play Custom ROMs group: https://t.me/Z2PlayGSI
Contributors
EmaMaker, erfanoabdi, vacheounet, Npjohnson, JeanGraff30, jefferson1979, JarlPenguin
ROM OS Version: Android 10
ROM Kernel: Linux 3.18.xx
ROM Firmware Required: ALBUS_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Version Information
Status: Stable
26/02
Initial Release
Bluetooth Crasht!
Log:
dogbin - phelleenug
time: 1620404198380 msg: Native crash: Aborted stacktrace: *** *** *** *** *** *** *** *** *** *** *
del.dog
time: 1620404198380
msg: Native crash: Aborted
stacktrace: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'motorola/albus_retail/albus:9/PPS29.133-30/ab8b4:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2021-05-07 18:16:37+0200
pid: 16059, tid: 16099, name: HwBinder:16059_ >>> com.android.bluetooth <<<
uid: 1002
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: '[0507/181637.834676:FATAL:hci_layer_android.cc(88)] Check failed: status == Status::SUCCESS.
#00 0x0000007abb78329f /system/lib64/libchrome.so+0x00000000000b829f
#01 0x0000007abb16b323 /system/lib64/libbluetooth.so+0x000000000026a323
#02 0x0000007b0fdf4c73 /system/lib64/[email protected]+0x000000000001bc73
#03 0x0000007b0fdf5a4f /system/lib64/[email protected]+0x000000000001ca4f
#04 0x0000007ba44dad9f /system/lib64/libhidlbase.so+0x0000000000095d9f
#05 0x0000007ba44de633 /system/lib64/libhidlbase.so+0x0000000000099633
#06 0x0000007ba44dfcc3 /system/lib64/libhidlbase.so+0x000000000009acc3
#07 0x0000007ba44eec53 /system/lib64/libhidlbase.so+0x00000000000a9c53
#08 0x0000007ba14d766f /system/lib64/libutils.so+0x000000000001366f
#09 0x0000007ba318b797 /system/lib64/libandroid_runtime.so+0x00000000000c2797
#10 0x0000007ba496e1f3 /apex/com.android.runtime/lib64/bionic/libc.so+0x00000000000e21f3
#11 0x0000007ba490faf7 /apex/com.android.runtime/lib64/bionic/libc.so+0x0000000000083af7
#12 0xffffffffffffffff <unknown>
'
x0 0000000000000000 x1 0000000000003ee3 x2 0000000000000006 x3 0000007aa8bcbff0
x4 a38ca476fefeff79 x5 a38ca476fefeff79 x6 a38ca476fefeff79 x7 ffffff7f7f7f7f7f
x8 00000000000000f0 x9 b79c13da5833e334 x10 0000000000000001 x11 0000000000000000
x12 fffffff0fffffbdf x13 ffffffffffffffff x14 0000000000000004 x15 ffffffffffffffff
x16 0000007ba497c8c0 x17 0000007ba495a210 x18 0000007aa81fc008 x19 0000000000003ebb
x20 0000000000003ee3 x21 00000000ffffffff x22 0000007aa8bcc580 x23 0000007ba4976620
x24 0000007abb7f4000 x25 0000007aa8bcc0d8 x26 0000007aa8bcc0d8 x27 0000007aa8bcd020
x28 0000000000000009 x29 0000007aa8bcc090
sp 0000007aa8bcbfd0 lr 0000007ba490df8c pc 0000007ba490dfb8
backtrace:
#00 pc 0000000000081fb8 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: c004004d50c333c221e671497f92cd4c)
#01 pc 000000000009f5c0 /system/lib64/libchrome.so (base::debug::BreakDebugger()+20) (BuildId: 4a5ca11c0291f6f4b79b6e1d8c8fa527)
#02 pc 00000000000b86e4 /system/lib64/libchrome.so (logging::LogMessage::~LogMessage()+1240) (BuildId: 4a5ca11c0291f6f4b79b6e1d8c8fa527)
#03 pc 000000000026a320 /system/lib64/libbluetooth.so (BluetoothHciCallbacks::initializationComplete(android::hardware::bluetooth::V1_0::Status)+76) (BuildId: 3b86a3c73b70771a3c03bd58f8b1465b)
#04 pc 000000000001bc70 /system/lib64/[email protected] (android::hardware::bluetooth::V1_0::BnHwBluetoothHciCallbacks::_hidl_initializationComplete(android::hidl::base::V1_0::BnHwBase*, android::hardware:arcel const&, android::hardware:arcel*, std::__1::function<void (android::hardware:arcel&)>)+192) (BuildId: c3730a16195f74115d0661b5f6aabe99)
#05 pc 000000000001ca4c /system/lib64/[email protected] (android::hardware::bluetooth::V1_0::BnHwBluetoothHciCallbacks:nTransact(unsigned int, android::hardware:arcel const&, android::hardware:arcel*, unsigned int, std::__1::function<void (android::hardware:arcel&)>)+484) (BuildId: c3730a16195f74115d0661b5f6aabe99)
#06 pc 0000000000095d9c /system/lib64/libhidlbase.so (android::hardware::BHwBinder::transact(unsigned int, android::hardware:arcel const&, android::hardware:arcel*, unsigned int, std::__1::function<void (android::hardware:arcel&)>)+68) (BuildId: b754fc58689264d008057dfe51f1ea6b)
#07 pc 0000000000099630 /system/lib64/libhidlbase.so (android::hardware::IPCThreadState::getAndExecuteCommand()+1036) (BuildId: b754fc58689264d008057dfe51f1ea6b)
#08 pc 000000000009acc0 /system/lib64/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+152) (BuildId: b754fc58689264d008057dfe51f1ea6b)
#09 pc 00000000000a9c50 /system/lib64/libhidlbase.so (android::hardware:oolThread::threadLoop()+24) (BuildId: b754fc58689264d008057dfe51f1ea6b)
#10 pc 000000000001366c /system/lib64/libutils.so (android::_threadLoop(void*)+288) (BuildId: 848c7838fb7679925f864f64355fa2cf)
#11 pc 00000000000c2794 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140) (BuildId: a6ec011d7dd14db25d82e06f0736b829)
#12 pc 00000000000e21f0 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) (BuildId: c004004d50c333c221e671497f92cd4c)
#13 pc 0000000000083af4 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: c004004d50c333c221e671497f92cd4c)
msebastian2021 said:
Bluetooth Crasht!
Log:
dogbin - phelleenug
time: 1620404198380 msg: Native crash: Aborted stacktrace: *** *** *** *** *** *** *** *** *** *** *
del.dog
time: 1620404198380
msg: Native crash: Aborted
stacktrace: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'motorola/albus_retail/albus:9/PPS29.133-30/ab8b4:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2021-05-07 18:16:37+0200
pid: 16059, tid: 16099, name: HwBinder:16059_ >>> com.android.bluetooth <<<
uid: 1002
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: '[0507/181637.834676:FATAL:hci_layer_android.cc(88)] Check failed: status == Status::SUCCESS.
#00 0x0000007abb78329f /system/lib64/libchrome.so+0x00000000000b829f
#01 0x0000007abb16b323 /system/lib64/libbluetooth.so+0x000000000026a323
#02 0x0000007b0fdf4c73 /system/lib64/[email protected]+0x000000000001bc73
#03 0x0000007b0fdf5a4f /system/lib64/[email protected]+0x000000000001ca4f
#04 0x0000007ba44dad9f /system/lib64/libhidlbase.so+0x0000000000095d9f
#05 0x0000007ba44de633 /system/lib64/libhidlbase.so+0x0000000000099633
#06 0x0000007ba44dfcc3 /system/lib64/libhidlbase.so+0x000000000009acc3
#07 0x0000007ba44eec53 /system/lib64/libhidlbase.so+0x00000000000a9c53
#08 0x0000007ba14d766f /system/lib64/libutils.so+0x000000000001366f
#09 0x0000007ba318b797 /system/lib64/libandroid_runtime.so+0x00000000000c2797
#10 0x0000007ba496e1f3 /apex/com.android.runtime/lib64/bionic/libc.so+0x00000000000e21f3
#11 0x0000007ba490faf7 /apex/com.android.runtime/lib64/bionic/libc.so+0x0000000000083af7
#12 0xffffffffffffffff <unknown>
'
x0 0000000000000000 x1 0000000000003ee3 x2 0000000000000006 x3 0000007aa8bcbff0
x4 a38ca476fefeff79 x5 a38ca476fefeff79 x6 a38ca476fefeff79 x7 ffffff7f7f7f7f7f
x8 00000000000000f0 x9 b79c13da5833e334 x10 0000000000000001 x11 0000000000000000
x12 fffffff0fffffbdf x13 ffffffffffffffff x14 0000000000000004 x15 ffffffffffffffff
x16 0000007ba497c8c0 x17 0000007ba495a210 x18 0000007aa81fc008 x19 0000000000003ebb
x20 0000000000003ee3 x21 00000000ffffffff x22 0000007aa8bcc580 x23 0000007ba4976620
x24 0000007abb7f4000 x25 0000007aa8bcc0d8 x26 0000007aa8bcc0d8 x27 0000007aa8bcd020
x28 0000000000000009 x29 0000007aa8bcc090
sp 0000007aa8bcbfd0 lr 0000007ba490df8c pc 0000007ba490dfb8
backtrace:
#00 pc 0000000000081fb8 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: c004004d50c333c221e671497f92cd4c)
#01 pc 000000000009f5c0 /system/lib64/libchrome.so (base::debug::BreakDebugger()+20) (BuildId: 4a5ca11c0291f6f4b79b6e1d8c8fa527)
#02 pc 00000000000b86e4 /system/lib64/libchrome.so (logging::LogMessage::~LogMessage()+1240) (BuildId: 4a5ca11c0291f6f4b79b6e1d8c8fa527)
#03 pc 000000000026a320 /system/lib64/libbluetooth.so (BluetoothHciCallbacks::initializationComplete(android::hardware::bluetooth::V1_0::Status)+76) (BuildId: 3b86a3c73b70771a3c03bd58f8b1465b)
#04 pc 000000000001bc70 /system/lib64/[email protected] (android::hardware::bluetooth::V1_0::BnHwBluetoothHciCallbacks::_hidl_initializationComplete(android::hidl::base::V1_0::BnHwBase*, android::hardware:arcel const&, android::hardware:arcel*, std::__1::function<void (android::hardware:arcel&)>)+192) (BuildId: c3730a16195f74115d0661b5f6aabe99)
#05 pc 000000000001ca4c /system/lib64/[email protected] (android::hardware::bluetooth::V1_0::BnHwBluetoothHciCallbacks:nTransact(unsigned int, android::hardware:arcel const&, android::hardware:arcel*, unsigned int, std::__1::function<void (android::hardware:arcel&)>)+484) (BuildId: c3730a16195f74115d0661b5f6aabe99)
#06 pc 0000000000095d9c /system/lib64/libhidlbase.so (android::hardware::BHwBinder::transact(unsigned int, android::hardware:arcel const&, android::hardware:arcel*, unsigned int, std::__1::function<void (android::hardware:arcel&)>)+68) (BuildId: b754fc58689264d008057dfe51f1ea6b)
#07 pc 0000000000099630 /system/lib64/libhidlbase.so (android::hardware::IPCThreadState::getAndExecuteCommand()+1036) (BuildId: b754fc58689264d008057dfe51f1ea6b)
#08 pc 000000000009acc0 /system/lib64/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+152) (BuildId: b754fc58689264d008057dfe51f1ea6b)
#09 pc 00000000000a9c50 /system/lib64/libhidlbase.so (android::hardware:oolThread::threadLoop()+24) (BuildId: b754fc58689264d008057dfe51f1ea6b)
#10 pc 000000000001366c /system/lib64/libutils.so (android::_threadLoop(void*)+288) (BuildId: 848c7838fb7679925f864f64355fa2cf)
#11 pc 00000000000c2794 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140) (BuildId: a6ec011d7dd14db25d82e06f0736b829)
#12 pc 00000000000e21f0 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) (BuildId: c004004d50c333c221e671497f92cd4c)
#13 pc 0000000000083af4 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: c004004d50c333c221e671497f92cd4c)
Click to expand...
Click to collapse
You are using Oreo firmware, despite being quite plainly stated in the post, that Pie firmware is required