[DEBUGGING] LineageOS 14.1 disscusion - Huawei Nova/Nova Plus Guides, News, & Discussion

[DEBUGGING] LineageOS 14.1 disscusion - Huawei Nova/Nova Plus Guides, News, & Discussion

Hello!
So, on 02.08.2017 ive built LineageOS 14.1, but it doesnt boot yet. When the bootanimation ends, the screen becomes black and after 2-4 seconds, the phone reboots automatically. Ive tried to debug it but i couldnt manage to fix that. Im still trying though.
Since my knowledge is limited/small, im making this thread thinking that together we may be able to solve it.
SOURCES:
- Device tree
- Kernel
- Vendor tree
The blobs were updated to N B350 as you will see in the commits of vendor tree.
The kernel is using newer CAF source from the branch "cm-14.1" left by @Grarak and ive merged his commit called "Import Huawei". I had to fix build errors as you will see in the commits and thats because ive did mistakes initially when ive merged. There might be some mistakes left, but i doubt since the kernel is building successfully. It also has the changes ive did to LOS13 kernel.
DOWNLOADS:
- lineage-14.1-20170802-UNOFFICIAL-can.zip
- boot.img
- LOS14.1_libs.zip
- los14.1_logs.zip
The boot.img is an eng build meant for debugging, so ADB is enabled by default and you can take logcats during boot.
Flash it like LOS13 and then flash boot.img through TWRP. Ive flashed it over LOS13 (so Marshmallow), but you should be able to flash it over Nougat too. I dont think that flashing it over MM can cause issues though.
LOS14.1_libs.zip contain some libs. Ive got rid of some errors from logcats regarding libs (CANNOT LINK EXECUTABLE) by placing those libs. Its a flashable zip, so you can flash it in TWRP.
los14.1_logs.zip contain some logcats taken during boot, but also kmsg (kmsg2 is longest). los14_11 is the last logcat ive took and ive had the libs from LOS14.1_libs.zip when it was taken.
Everyone is welcome to help.

I really want to help, but I know little to nothing lol
I'm trying to understand the errors and trying to find how to fix them though, because it will not only "help" to solve this issues, it will help me understand how to build, as I want build some ROM too.
Enviado de meu HUAWEI CAN usando Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:31 PM ----------
But, from what I saw from the los14_11, libloc_pla.so and loc_launcher continues returning an error. Although it may be not the only thing, the log file mentions that libloc_pla.so seems to be too little to be an ELF file. I'll keep looking [emoji14]
Enviado de meu HUAWEI CAN usando Tapatalk

Wrong symlinks in LOS14.1_libs.zip.
Try this:
1. Remove from zip:
Code:
LOS14.1_libs.zip/system/lib/libloc_pla.so
LOS14.1_libs.zip/system/lib64/libloc_pla.so
LOS14.1_libs.zip/system/lib/libstagefright_soft_flacdec.so
LOS14.1_libs.zip/system/lib64/libstagefright_soft_flacdec.so
2. Add to LOS14.1_libs.zip/META-INF/com/google/android/updater-script:
Code:
symlink("/system/vendor/lib/libloc_pla.so", "/system/lib/libloc_pla.so");
symlink("/system/vendor/lib64/libloc_pla.so", "/system/lib64/libloc_pla.so");
symlink("/system/vendor/lib/libstagefright_soft_flacdec.so", "/system/lib/libstagefright_soft_flacdec.so");
symlink("/system/vendor/lib64/libstagefright_soft_flacdec.so", "/system/lib64/libstagefright_soft_flacdec.so");
after:
Code:
package_extract_dir("system", "/system");

Booted!
So, this evening ive gave a shot again to LOS14.1. I add more missing libs/files which ive seen in logcat till the log got smaller. Then ive seen that com.qualcomm.location apk is missing a library. After ive deleted the apk, the phone booted. Of course, adding the missing library should have solved it too, but ill try it tomorrow.
Its buggy af though. Wifi seems to work.
1) Screen is flickering so much. Everytime you touch the screen, it becomes black and then goes to normal lol.
2) SIM card isnt recognized and prolly RIL is broken as well.
3) Bluetooth doesnt work.
4) NFC seems to crash.
5) Audio doesnt work, but it works partially with headphones and sometimes it produces weird sounds.
6) Auto rotate doesnt work.
7) Camera app doesnt even appear in app drawer, so theres problems with it too.
Tomorrow im gonna work on it and hopefully ill make progress. The fact that i managed to boot it is a huge progress in my opinion because i thought that the problem is in kernel or that ive did mistakes while i merged in kernel. Maybe some of the bugs are related to kernel too, i dont know yet, but now i know that the kernel wasnt causing the phone to not boot.
Ive took a screenshot of Settings > About phone, but after ive restored LOS13 backup it doesnt seems that it got saved. Tomorrow, when ill go back to LOS14.1 to test things, ill take a pic with other phone and post it here, if you dont believe me .

#Henkate said:
So, this evening ive gave a shot again to LOS14.1. I add more missing libs/files which ive seen in logcat till the log got smaller. Then ive seen that com.qualcomm.location apk is missing a library. After ive deleted the apk, the phone booted. Of course, adding the missing library should have solved it too, but ill try it tomorrow.
Its buggy af though. Wifi seems to work.
1) Screen is flickering so much. Everytime you touch the screen, it becomes black and then goes to normal lol.
2) SIM card isnt recognized and prolly RIL is broken as well.
3) Bluetooth doesnt work.
4) NFC seems to crash.
5) Audio doesnt work, but it works partially with headphones and sometimes it produces weird sounds.
6) Auto rotate doesnt work.
7) Camera app doesnt even appear in app drawer, so theres problems with it too.
Tomorrow im gonna work on it and hopefully ill make progress. The fact that i managed to boot it is a huge progress in my opinion because i thought that the problem is in kernel or that ive did mistakes while i merged in kernel. Maybe some of the bugs are related to kernel too, i dont know yet, but now i know that the kernel wasnt causing the phone to not boot.
Ive took a screenshot of Settings > About phone, but after ive restored LOS13 backup it doesnt seems that it got saved. Tomorrow, when ill go back to LOS14.1 to test things, ill take a pic with other phone and post it here, if you dont believe me .
Click to expand...
Click to collapse
When ive built LOS 14 for the first time, ive updated all blobs to N. After few days since that day, ive made a build with the blobs of MM, but it wasnt booting (not even going to bootanimation).
Today, ive tried again that build and managed to boot it. I only needed to replace few blobs with N ones in order to boot it.
Results:
1) Baseband and sim card gets recognized. I can make calls and incall audio works. But when im making / receiving calls, phone enters "Do not disturb" mode automatically and turn it off when call ends automatically too.
2) I can send and receive SMS.
3) Mobile data works (the bug with empty / gray signal icon when using 3G is still there).
4) Auto rotate works.
Screen still flickers, notification led, fingerprint, camera (doesnt even appear in drawer), flash, bluetooth, GPS and NFC doesnt work. Also, cant power on the screen once it goes off.
EDIT:
Fixed audio by using audio files from MM. Both, speaker and headphones are working fine. In future, ill probably try to update everything to N, but at this moment i just want to get everything working.
EDIT 2:
Fixed screen flickering.
EDIT 3:
Ill probably stick with N blobs instead MM ones. The LOS 14.1 with N blobs is way smoother than the one with MM blobs. The audio and flicker fix work on it too. But now i have to fix sim card since is not getting detected (and baseband is unknown). Also, i cant figure out yet whats the problem with powering on the screen. Screen doesnt power on anymore after it gets off and when i press the power button, the screen keep varying between dark colors (i dont know how to explain) and if i press the volume buttons, i can hear the sound (you can hear that when you are on lockscreen).

#Henkate said:
When ive built LOS 14 for the first time, ive updated all blobs to N. After few days since that day, ive made a build with the blobs of MM, but it wasnt booting (not even going to bootanimation).
Today, ive tried again that build and managed to boot it. I only needed to replace few blobs with N ones in order to boot it.
Results:
1) Baseband and sim card gets recognized. I can make calls and incall audio works. But when im making / receiving calls, phone enters "Do not disturb" mode automatically and turn it off when call ends automatically too.
2) I can send and receive SMS.
3) Mobile data works (the bug with empty / gray signal icon when using 3G is still there).
4) Auto rotate works.
Screen still flickers, notification led, fingerprint, camera (doesnt even appear in drawer), flash, bluetooth, GPS and NFC doesnt work. Also, cant power on the screen once it goes off.
EDIT:
Fixed audio by using audio files from MM. Both, speaker and headphones are working fine. In future, ill probably try to update everything to N, but at this moment i just want to get everything working.
EDIT 2:
Fixed screen flickering.
EDIT 3:
Ill probably stick with N blobs instead MM ones. The LOS 14.1 with N blobs is way smoother than the one with MM blobs. The audio and flicker fix work on it too. But now i have to fix sim card since is not getting detected (and baseband is unknown). Also, i cant figure out yet whats the problem with powering on the screen. Screen doesnt power on anymore after it gets off and when i press the power button, the screen keep varying between dark colors (i dont know how to explain) and if i press the volume buttons, i can hear the sound (you can hear that when you are on lockscreen).
Click to expand...
Click to collapse
The device tree has a file called proprietary-files.txt which contain the proprietary libs which goes to vendor tree.
The proprietary-files.txt left by Grarak is this one.
When ive replaced the following blobs with N ones (B350) on the LOS14 build with MM blobs, the sim card wasnt detected anymore, baseband was unknown and auto rotate was broken:
Code:
# QMI
bin/irsc_util
etc/permissions/qti_permissions.xml
lib/libqmi_nv_api.so
-lib/libqmi_oem_api.so
lib64/libqmi_nv_api.so
-lib64/libqmi_oem_api.so
vendor/lib/libdiag.so
vendor/lib/libdsi_netctrl.so
vendor/lib/libdsutils.so
vendor/lib/libidl.so
vendor/lib/libqcci_legacy.so
vendor/lib/libqcmaputils.so
vendor/lib/libqdi.so
vendor/lib/libqdp.so
vendor/lib/libqmi.so
vendor/lib/libqmi_cci.so
vendor/lib/libqmi_client_helper.so
vendor/lib/libqmi_client_qmux.so
vendor/lib/libqmi_common_so.so
vendor/lib/libqmi_csi.so
vendor/lib/libqmi_encdec.so
vendor/lib/libqmiservices.so
vendor/lib/libqti-wl.so
vendor/lib/libquipc_os_api.so
vendor/lib/libsmemlog.so
vendor/lib/libvqzip.so
vendor/lib64/libdiag.so
vendor/lib64/libdsi_netctrl.so
vendor/lib64/libdsutils.so
vendor/lib64/libidl.so
vendor/lib64/libqcci_legacy.so
vendor/lib64/libqcmaputils.so
vendor/lib64/libqdi.so
vendor/lib64/libqdp.so
vendor/lib64/libqmi.so
vendor/lib64/libqmi_cci.so
vendor/lib64/libqmi_client_helper.so
vendor/lib64/libqmi_client_qmux.so
vendor/lib64/libqmi_common_so.so
vendor/lib64/libqmi_csi.so
vendor/lib64/libqmi_encdec.so
vendor/lib64/libqmiservices.so
vendor/lib64/libqti-wl.so
vendor/lib64/libquipc_os_api.so
vendor/lib64/libsmemlog.so
On the LOS14 build with N blobs, ive replaced radio and sensor blobs with MM ones, but they still werent working and in logcat i could see the same errors ive seen on the build with MM blobs after replacing the blobs mentioned before.
So, this sounds like auto rotate and sim card / RIL will be fixed on the build with N blobs if i replace the sensor, radio and QMI blobs with MM ones.
Now i dunno what to do: stick with MM blobs or stick with N blobs and use few MM blobs to get some things working until i can fix them with N blobs (if i can)? I think second, but im still not sure.
I still didnt manage to fix the screen issue: when screen goes off, you cant power it on anymore (well, it gets on, but it stays black).
The logcat show this:
# when screen goes off
Code:
0-01 20:37:06.364 963 1022 V KeyguardServiceDelegate: onScreenTurnedOff()
10-01 20:37:06.369 963 1022 [B][COLOR="Red"]E libEGL : call to OpenGL ES API with no current context (logged once per thread)[/COLOR][/B]
10-01 20:37:06.369 963 1022 D Sensors : activate called handle:3 enable:0
10-01 20:37:06.369 963 1022 D Sensors : bh1745-light calling driver disable
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 283: en=0
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 284: flags=0
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=1
10-01 20:37:06.370 963 1022 E LightSensor: LightSensor disable, event occur num: 49
10-01 20:37:06.376 963 1019 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
10-01 20:37:06.376 494 494 D SurfaceFlinger: Set power mode=0, type=0 flinger=0x7fb4848000
10-01 20:37:06.377 494 494 I SDM : HWCDisplay::SetPowerMode: display = 0, mode = 0
10-01 20:37:06.378 494 494 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 0
10-01 20:37:06.669 963 1260 D SurfaceControl: Excessive delay in setPowerMode(): 292ms
10-01 20:37:06.670 963 1022 I PowerManagerService: Sleeping (uid 1000)...
# when screen goes on
Code:
10-01 20:37:06.844 963 1223 I PowerManagerService: Waking up from sleep (uid 1000)...
10-01 20:37:06.845 963 963 V KeyguardServiceDelegate: onStartedWakingUp()
10-01 20:37:06.845 963 1022 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
10-01 20:37:06.846 963 1022 V KeyguardServiceDelegate: onScreenTurnedOn(showListener = [email protected])
10-01 20:37:06.848 963 1022 D Sensors : batch called handle:3 sample_ns:1000000 latency_ns:0
10-01 20:37:06.849 963 1022 D Sensors : activate called handle:3 enable:1
10-01 20:37:06.849 963 1022 D Sensors : bh1745-light calling driver setDelay 1 ms
10-01 20:37:06.849 963 1022 D Sensors : bh1745-light calling driver enable
10-01 20:37:06.849 963 1022 W LightSensor: LightSensor, enable, 283: en=1
10-01 20:37:06.850 963 1022 W LightSensor: LightSensor, enable, 284: flags=1
10-01 20:37:06.850 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=0
10-01 20:37:06.853 545 2573 D audio_hw_primary: adev_set_parameters: enter: screen_state=on
10-01 20:37:06.855 1532 1532 D wpa_supplicant: wlan0: Control interface command 'SIGNAL_POLL'
10-01 20:37:06.857 963 990 V KeyguardServiceDelegate: **** SHOWN CALLED ****
10-01 20:37:06.871 963 1019 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
10-01 20:37:06.871 494 494 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x7fb4848000
10-01 20:37:06.871 963 994 I WindowManager: OverscanTimeout run
10-01 20:37:06.871 494 494 I SDM : HWCDisplay::SetPowerMode: display = 0, mode = 2
10-01 20:37:06.871 494 494 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 0
10-01 20:37:06.906 963 1022 I DisplayPowerController: Unblocked screen on after 60 ms
10-01 20:37:06.907 963 1022 V KeyguardServiceDelegate: onScreenTurnedOn()
10-01 20:37:07.041 963 1204 E LightSensor: read Events lux: 0.0
10-01 20:37:07.042 963 1022 D Sensors : activate called handle:3 enable:0
10-01 20:37:07.042 963 1022 D Sensors : bh1745-light calling driver disable
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 283: en=0
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 284: flags=0
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=1
10-01 20:37:07.042 963 1022 E LightSensor: LightSensor disable, event occur num: 1
10-01 20:37:07.046 963 1022 D Sensors : batch called handle:3 sample_ns:250000000 latency_ns:0
10-01 20:37:07.047 963 1022 D Sensors : activate called handle:3 enable:1
10-01 20:37:07.047 963 1022 D Sensors : bh1745-light calling driver setDelay 250 ms
10-01 20:37:07.047 963 1022 D Sensors : bh1745-light calling driver enable
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 283: en=1
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 284: flags=1
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=0
10-01 20:37:07.060 963 1022 D LuxLevels: bright hysteresis constant= 0.1, threshold=0.0, lux=0.0
10-01 20:37:07.060 963 1022 D LuxLevels: dark hysteresis constant= 0.2, threshold=0.0, lux=0.0
10-01 20:37:07.176 963 1574 I ActivityManager: Killing 1977:com.android.keychain/1000 (adj 906): empty #17
10-01 20:37:07.194 963 1978 D ActivityManager: cleanUpApplicationRecord -- 1977
10-01 20:37:07.220 963 1260 D SurfaceControl: Excessive delay in setPowerMode(): 349ms
10-01 20:37:07.582 963 1204 E LightSensor: read Events lux: 1.0
10-01 20:37:07.934 963 1204 E LightSensor: read Events lux: 5.0
10-01 20:37:08.286 963 1204 E LightSensor: read Events lux: 6.0
10-01 20:37:08.638 963 1204 E LightSensor: read Events lux: 5.0
10-01 20:37:08.989 963 1204 E LightSensor: read Events lux: 0.0
The following line makes me think that it might be related to some egl lib, but i dont know yet.
Code:
[B][COLOR="Red"]E libEGL : call to OpenGL ES API with no current context (logged once per thread)[/COLOR][/B]
Screen flickering was fixed by using some SDM blobs from mido because with the ones from EMUI 5 B350 it was flickering. Perhaps i should try newer firmware, such as B381/382?

#Henkate said:
The device tree has a file called proprietary-files.txt which contain the proprietary libs which goes to vendor tree.
The proprietary-files.txt left by Grarak is this one.
When ive replaced the following blobs with N ones (B350) on the LOS14 build with MM blobs, the sim card wasnt detected anymore, baseband was unknown and auto rotate was broken:
On the LOS14 build with N blobs, ive replaced radio and sensor blobs with MM ones, but they still werent working and in logcat i could see the same errors ive seen on the build with MM blobs after replacing the blobs mentioned before.
So, this sounds like auto rotate and sim card / RIL will be fixed on the build with N blobs if i replace the sensor, radio and QMI blobs with MM ones.
Now i dunno what to do: stick with MM blobs or stick with N blobs and use few MM blobs to get some things working until i can fix them with N blobs (if i can)? I think second, but im still not sure.
I still didnt manage to fix the screen issue: when screen goes off, you cant power it on anymore (well, it gets on, but it stays black).
The logcat show this:
# when screen goes off
0-01 20:37:06.364 963 1022 V KeyguardServiceDelegate: onScreenTurnedOff()
10-01 20:37:06.369 963 1022 E libEGL : call to OpenGL ES API with no current context (logged once per thread)
10-01 20:37:06.369 963 1022 D Sensors : activate called handle:3 enable:0
10-01 20:37:06.369 963 1022 D Sensors : bh1745-light calling driver disable
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 283: en=0
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 284: flags=0
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=1
10-01 20:37:06.370 963 1022 E LightSensor: LightSensor disable, event occur num: 49
10-01 20:37:06.376 963 1019 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
10-01 20:37:06.376 494 494 D SurfaceFlinger: Set power mode=0, type=0 flinger=0x7fb4848000
10-01 20:37:06.377 494 494 I SDM : HWCDisplay::SetPowerMode: display = 0, mode = 0
10-01 20:37:06.378 494 494 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 0
10-01 20:37:06.669 963 1260 D SurfaceControl: Excessive delay in setPowerMode(): 292ms
10-01 20:37:06.670 963 1022 I PowerManagerService: Sleeping (uid 1000)...
# when screen goes on
# when screen goes on
10-01 20:37:06.844 963 1223 I PowerManagerService: Waking up from sleep (uid 1000)...
10-01 20:37:06.845 963 963 V KeyguardServiceDelegate: onStartedWakingUp()
10-01 20:37:06.845 963 1022 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
10-01 20:37:06.846 963 1022 V KeyguardServiceDelegate: onScreenTurnedOn(showListener = [email protected])
10-01 20:37:06.848 963 1022 D Sensors : batch called handle:3 sample_ns:1000000 latency_ns:0
10-01 20:37:06.849 963 1022 D Sensors : activate called handle:3 enable:1
10-01 20:37:06.849 963 1022 D Sensors : bh1745-light calling driver setDelay 1 ms
10-01 20:37:06.849 963 1022 D Sensors : bh1745-light calling driver enable
10-01 20:37:06.849 963 1022 W LightSensor: LightSensor, enable, 283: en=1
10-01 20:37:06.850 963 1022 W LightSensor: LightSensor, enable, 284: flags=1
10-01 20:37:06.850 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=0
10-01 20:37:06.853 545 2573 D audio_hw_primary: adev_set_parameters: enter: screen_state=on
10-01 20:37:06.855 1532 1532 D wpa_supplicant: wlan0: Control interface command 'SIGNAL_POLL'
10-01 20:37:06.857 963 990 V KeyguardServiceDelegate: **** SHOWN CALLED ****
10-01 20:37:06.871 963 1019 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
10-01 20:37:06.871 494 494 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x7fb4848000
10-01 20:37:06.871 963 994 I WindowManager: OverscanTimeout run
10-01 20:37:06.871 494 494 I SDM : HWCDisplay::SetPowerMode: display = 0, mode = 2
10-01 20:37:06.871 494 494 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 0
10-01 20:37:06.906 963 1022 I DisplayPowerController: Unblocked screen on after 60 ms
10-01 20:37:06.907 963 1022 V KeyguardServiceDelegate: onScreenTurnedOn()
10-01 20:37:07.041 963 1204 E LightSensor: read Events lux: 0.0
10-01 20:37:07.042 963 1022 D Sensors : activate called handle:3 enable:0
10-01 20:37:07.042 963 1022 D Sensors : bh1745-light calling driver disable
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 283: en=0
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 284: flags=0
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=1
10-01 20:37:07.042 963 1022 E LightSensor: LightSensor disable, event occur num: 1
10-01 20:37:07.046 963 1022 D Sensors : batch called handle:3 sample_ns:250000000 latency_ns:0
10-01 20:37:07.047 963 1022 D Sensors : activate called handle:3 enable:1
10-01 20:37:07.047 963 1022 D Sensors : bh1745-light calling driver setDelay 250 ms
10-01 20:37:07.047 963 1022 D Sensors : bh1745-light calling driver enable
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 283: en=1
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 284: flags=1
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=0
10-01 20:37:07.060 963 1022 D LuxLevels: bright hysteresis constant= 0.1, threshold=0.0, lux=0.0
10-01 20:37:07.060 963 1022 D LuxLevels: dark hysteresis constant= 0.2, threshold=0.0, lux=0.0
10-01 20:37:07.176 963 1574 I ActivityManager: Killing 1977:com.android.keychain/1000 (adj 906): empty #17
10-01 20:37:07.194 963 1978 D ActivityManager: cleanUpApplicationRecord -- 1977
10-01 20:37:07.220 963 1260 D SurfaceControl: Excessive delay in setPowerMode(): 349ms
10-01 20:37:07.582 963 1204 E LightSensor: read Events lux: 1.0
10-01 20:37:07.934 963 1204 E LightSensor: read Events lux: 5.0
10-01 20:37:08.286 963 1204 E LightSensor: read Events lux: 6.0
10-01 20:37:08.638 963 1204 E LightSensor: read Events lux: 5.0
10-01 20:37:08.989 963 1204 E LightSensor: read Events lux: 0.0
The following line makes me think that it might be related to some egl lib, but i dont know yet.
Screen flickering was fixed by using some SDM blobs from mido because with the ones from EMUI 5 B350 it was flickering. Perhaps i should try newer firmware, such as B381/382?
Click to expand...
Click to collapse
I think you should try N blobs and use MM just where needed, at least for now, but try updated blobs for N, it is a good shot, in my opinion ^^
I think this week I'll setup a cloud storage machine and try to build something there. Maybe, in the learning process, I can help you here ^^

#Henkate said:
The device tree has a file called proprietary-files.txt which contain the proprietary libs which goes to vendor tree.
The proprietary-files.txt left by Grarak is this one.
When ive replaced the following blobs with N ones (B350) on the LOS14 build with MM blobs, the sim card wasnt detected anymore, baseband was unknown and auto rotate was broken:
Code:
# QMI
bin/irsc_util
etc/permissions/qti_permissions.xml
lib/libqmi_nv_api.so
-lib/libqmi_oem_api.so
lib64/libqmi_nv_api.so
-lib64/libqmi_oem_api.so
vendor/lib/libdiag.so
vendor/lib/libdsi_netctrl.so
vendor/lib/libdsutils.so
vendor/lib/libidl.so
vendor/lib/libqcci_legacy.so
vendor/lib/libqcmaputils.so
vendor/lib/libqdi.so
vendor/lib/libqdp.so
vendor/lib/libqmi.so
vendor/lib/libqmi_cci.so
vendor/lib/libqmi_client_helper.so
vendor/lib/libqmi_client_qmux.so
vendor/lib/libqmi_common_so.so
vendor/lib/libqmi_csi.so
vendor/lib/libqmi_encdec.so
vendor/lib/libqmiservices.so
vendor/lib/libqti-wl.so
vendor/lib/libquipc_os_api.so
vendor/lib/libsmemlog.so
vendor/lib/libvqzip.so
vendor/lib64/libdiag.so
vendor/lib64/libdsi_netctrl.so
vendor/lib64/libdsutils.so
vendor/lib64/libidl.so
vendor/lib64/libqcci_legacy.so
vendor/lib64/libqcmaputils.so
vendor/lib64/libqdi.so
vendor/lib64/libqdp.so
vendor/lib64/libqmi.so
vendor/lib64/libqmi_cci.so
vendor/lib64/libqmi_client_helper.so
vendor/lib64/libqmi_client_qmux.so
vendor/lib64/libqmi_common_so.so
vendor/lib64/libqmi_csi.so
vendor/lib64/libqmi_encdec.so
vendor/lib64/libqmiservices.so
vendor/lib64/libqti-wl.so
vendor/lib64/libquipc_os_api.so
vendor/lib64/libsmemlog.so
On the LOS14 build with N blobs, ive replaced radio and sensor blobs with MM ones, but they still werent working and in logcat i could see the same errors ive seen on the build with MM blobs after replacing the blobs mentioned before.
So, this sounds like auto rotate and sim card / RIL will be fixed on the build with N blobs if i replace the sensor, radio and QMI blobs with MM ones.
Now i dunno what to do: stick with MM blobs or stick with N blobs and use few MM blobs to get some things working until i can fix them with N blobs (if i can)? I think second, but im still not sure.
I still didnt manage to fix the screen issue: when screen goes off, you cant power it on anymore (well, it gets on, but it stays black).
The logcat show this:
# when screen goes off
Code:
0-01 20:37:06.364 963 1022 V KeyguardServiceDelegate: onScreenTurnedOff()
10-01 20:37:06.369 963 1022 [B][COLOR="Red"]E libEGL : call to OpenGL ES API with no current context (logged once per thread)[/COLOR][/B]
10-01 20:37:06.369 963 1022 D Sensors : activate called handle:3 enable:0
10-01 20:37:06.369 963 1022 D Sensors : bh1745-light calling driver disable
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 283: en=0
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 284: flags=0
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=1
10-01 20:37:06.370 963 1022 E LightSensor: LightSensor disable, event occur num: 49
10-01 20:37:06.376 963 1019 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
10-01 20:37:06.376 494 494 D SurfaceFlinger: Set power mode=0, type=0 flinger=0x7fb4848000
10-01 20:37:06.377 494 494 I SDM : HWCDisplay::SetPowerMode: display = 0, mode = 0
10-01 20:37:06.378 494 494 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 0
10-01 20:37:06.669 963 1260 D SurfaceControl: Excessive delay in setPowerMode(): 292ms
10-01 20:37:06.670 963 1022 I PowerManagerService: Sleeping (uid 1000)...
# when screen goes on
Code:
10-01 20:37:06.844 963 1223 I PowerManagerService: Waking up from sleep (uid 1000)...
10-01 20:37:06.845 963 963 V KeyguardServiceDelegate: onStartedWakingUp()
10-01 20:37:06.845 963 1022 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
10-01 20:37:06.846 963 1022 V KeyguardServiceDelegate: onScreenTurnedOn(showListener = [email protected])
10-01 20:37:06.848 963 1022 D Sensors : batch called handle:3 sample_ns:1000000 latency_ns:0
10-01 20:37:06.849 963 1022 D Sensors : activate called handle:3 enable:1
10-01 20:37:06.849 963 1022 D Sensors : bh1745-light calling driver setDelay 1 ms
10-01 20:37:06.849 963 1022 D Sensors : bh1745-light calling driver enable
10-01 20:37:06.849 963 1022 W LightSensor: LightSensor, enable, 283: en=1
10-01 20:37:06.850 963 1022 W LightSensor: LightSensor, enable, 284: flags=1
10-01 20:37:06.850 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=0
10-01 20:37:06.853 545 2573 D audio_hw_primary: adev_set_parameters: enter: screen_state=on
10-01 20:37:06.855 1532 1532 D wpa_supplicant: wlan0: Control interface command 'SIGNAL_POLL'
10-01 20:37:06.857 963 990 V KeyguardServiceDelegate: **** SHOWN CALLED ****
10-01 20:37:06.871 963 1019 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
10-01 20:37:06.871 494 494 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x7fb4848000
10-01 20:37:06.871 963 994 I WindowManager: OverscanTimeout run
10-01 20:37:06.871 494 494 I SDM : HWCDisplay::SetPowerMode: display = 0, mode = 2
10-01 20:37:06.871 494 494 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 0
10-01 20:37:06.906 963 1022 I DisplayPowerController: Unblocked screen on after 60 ms
10-01 20:37:06.907 963 1022 V KeyguardServiceDelegate: onScreenTurnedOn()
10-01 20:37:07.041 963 1204 E LightSensor: read Events lux: 0.0
10-01 20:37:07.042 963 1022 D Sensors : activate called handle:3 enable:0
10-01 20:37:07.042 963 1022 D Sensors : bh1745-light calling driver disable
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 283: en=0
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 284: flags=0
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=1
10-01 20:37:07.042 963 1022 E LightSensor: LightSensor disable, event occur num: 1
10-01 20:37:07.046 963 1022 D Sensors : batch called handle:3 sample_ns:250000000 latency_ns:0
10-01 20:37:07.047 963 1022 D Sensors : activate called handle:3 enable:1
10-01 20:37:07.047 963 1022 D Sensors : bh1745-light calling driver setDelay 250 ms
10-01 20:37:07.047 963 1022 D Sensors : bh1745-light calling driver enable
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 283: en=1
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 284: flags=1
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=0
10-01 20:37:07.060 963 1022 D LuxLevels: bright hysteresis constant= 0.1, threshold=0.0, lux=0.0
10-01 20:37:07.060 963 1022 D LuxLevels: dark hysteresis constant= 0.2, threshold=0.0, lux=0.0
10-01 20:37:07.176 963 1574 I ActivityManager: Killing 1977:com.android.keychain/1000 (adj 906): empty #17
10-01 20:37:07.194 963 1978 D ActivityManager: cleanUpApplicationRecord -- 1977
10-01 20:37:07.220 963 1260 D SurfaceControl: Excessive delay in setPowerMode(): 349ms
10-01 20:37:07.582 963 1204 E LightSensor: read Events lux: 1.0
10-01 20:37:07.934 963 1204 E LightSensor: read Events lux: 5.0
10-01 20:37:08.286 963 1204 E LightSensor: read Events lux: 6.0
10-01 20:37:08.638 963 1204 E LightSensor: read Events lux: 5.0
10-01 20:37:08.989 963 1204 E LightSensor: read Events lux: 0.0
The following line makes me think that it might be related to some egl lib, but i dont know yet.
Code:
[B][COLOR="Red"]E libEGL : call to OpenGL ES API with no current context (logged once per thread)[/COLOR][/B]
Click to expand...
Click to collapse
Spent another day for this, yet havent managed to fix it nor find the culprit (im not sure which is the cause).
Ive also didnt workout (home workout) because this ****, but its obviously my fault. This didnt happen only once, it happened like 3-4 times... Perhaps im also losing motivation, i dont know.
I cant try to fix other bugs unless i fix this issue and right now i have that feel that i wanna give up, but that feel comes and go...
Ive tried egl blobs from B382 and from mido, but still same result. So i guess it isnt related to them, i dont know. When it is booting for the first time, the screen stays black for few seconds till the Setup Wizard appears. There are problems when im unlocking the screen too. When i swipe up to unlock the screen, it stays on the wallpaper for like 5 seconds (without clock etc) and during that period of time i can swipe down and the lockscreen appears. All those issues should be related to that one (screen stays black and gets off in 3-5 seconds when im trying to turn it on after ive turned it off and cant get on anymore unless i reboot).
I may not be able to fix it without help.

#Henkate said:
The device tree has a file called proprietary-files.txt which contain the proprietary libs which goes to vendor tree.
The proprietary-files.txt left by Grarak is this one.
When ive replaced the following blobs with N ones (B350) on the LOS14 build with MM blobs, the sim card wasnt detected anymore, baseband was unknown and auto rotate was broken:
Code:
# QMI
bin/irsc_util
etc/permissions/qti_permissions.xml
lib/libqmi_nv_api.so
-lib/libqmi_oem_api.so
lib64/libqmi_nv_api.so
-lib64/libqmi_oem_api.so
vendor/lib/libdiag.so
vendor/lib/libdsi_netctrl.so
vendor/lib/libdsutils.so
vendor/lib/libidl.so
vendor/lib/libqcci_legacy.so
vendor/lib/libqcmaputils.so
vendor/lib/libqdi.so
vendor/lib/libqdp.so
vendor/lib/libqmi.so
vendor/lib/libqmi_cci.so
vendor/lib/libqmi_client_helper.so
vendor/lib/libqmi_client_qmux.so
vendor/lib/libqmi_common_so.so
vendor/lib/libqmi_csi.so
vendor/lib/libqmi_encdec.so
vendor/lib/libqmiservices.so
vendor/lib/libqti-wl.so
vendor/lib/libquipc_os_api.so
vendor/lib/libsmemlog.so
vendor/lib/libvqzip.so
vendor/lib64/libdiag.so
vendor/lib64/libdsi_netctrl.so
vendor/lib64/libdsutils.so
vendor/lib64/libidl.so
vendor/lib64/libqcci_legacy.so
vendor/lib64/libqcmaputils.so
vendor/lib64/libqdi.so
vendor/lib64/libqdp.so
vendor/lib64/libqmi.so
vendor/lib64/libqmi_cci.so
vendor/lib64/libqmi_client_helper.so
vendor/lib64/libqmi_client_qmux.so
vendor/lib64/libqmi_common_so.so
vendor/lib64/libqmi_csi.so
vendor/lib64/libqmi_encdec.so
vendor/lib64/libqmiservices.so
vendor/lib64/libqti-wl.so
vendor/lib64/libquipc_os_api.so
vendor/lib64/libsmemlog.so
On the LOS14 build with N blobs, ive replaced radio and sensor blobs with MM ones, but they still werent working and in logcat i could see the same errors ive seen on the build with MM blobs after replacing the blobs mentioned before.
So, this sounds like auto rotate and sim card / RIL will be fixed on the build with N blobs if i replace the sensor, radio and QMI blobs with MM ones.
Now i dunno what to do: stick with MM blobs or stick with N blobs and use few MM blobs to get some things working until i can fix them with N blobs (if i can)? I think second, but im still not sure.
I still didnt manage to fix the screen issue: when screen goes off, you cant power it on anymore (well, it gets on, but it stays black).
The logcat show this:
# when screen goes off
Code:
0-01 20:37:06.364 963 1022 V KeyguardServiceDelegate: onScreenTurnedOff()
10-01 20:37:06.369 963 1022 [B][COLOR="Red"]E libEGL : call to OpenGL ES API with no current context (logged once per thread)[/COLOR][/B]
10-01 20:37:06.369 963 1022 D Sensors : activate called handle:3 enable:0
10-01 20:37:06.369 963 1022 D Sensors : bh1745-light calling driver disable
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 283: en=0
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 284: flags=0
10-01 20:37:06.370 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=1
10-01 20:37:06.370 963 1022 E LightSensor: LightSensor disable, event occur num: 49
10-01 20:37:06.376 963 1019 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
10-01 20:37:06.376 494 494 D SurfaceFlinger: Set power mode=0, type=0 flinger=0x7fb4848000
10-01 20:37:06.377 494 494 I SDM : HWCDisplay::SetPowerMode: display = 0, mode = 0
10-01 20:37:06.378 494 494 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 0
10-01 20:37:06.669 963 1260 D SurfaceControl: Excessive delay in setPowerMode(): 292ms
10-01 20:37:06.670 963 1022 I PowerManagerService: Sleeping (uid 1000)...
# when screen goes on
Code:
10-01 20:37:06.844 963 1223 I PowerManagerService: Waking up from sleep (uid 1000)...
10-01 20:37:06.845 963 963 V KeyguardServiceDelegate: onStartedWakingUp()
10-01 20:37:06.845 963 1022 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
10-01 20:37:06.846 963 1022 V KeyguardServiceDelegate: onScreenTurnedOn(showListener = [email protected])
10-01 20:37:06.848 963 1022 D Sensors : batch called handle:3 sample_ns:1000000 latency_ns:0
10-01 20:37:06.849 963 1022 D Sensors : activate called handle:3 enable:1
10-01 20:37:06.849 963 1022 D Sensors : bh1745-light calling driver setDelay 1 ms
10-01 20:37:06.849 963 1022 D Sensors : bh1745-light calling driver enable
10-01 20:37:06.849 963 1022 W LightSensor: LightSensor, enable, 283: en=1
10-01 20:37:06.850 963 1022 W LightSensor: LightSensor, enable, 284: flags=1
10-01 20:37:06.850 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=0
10-01 20:37:06.853 545 2573 D audio_hw_primary: adev_set_parameters: enter: screen_state=on
10-01 20:37:06.855 1532 1532 D wpa_supplicant: wlan0: Control interface command 'SIGNAL_POLL'
10-01 20:37:06.857 963 990 V KeyguardServiceDelegate: **** SHOWN CALLED ****
10-01 20:37:06.871 963 1019 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
10-01 20:37:06.871 494 494 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x7fb4848000
10-01 20:37:06.871 963 994 I WindowManager: OverscanTimeout run
10-01 20:37:06.871 494 494 I SDM : HWCDisplay::SetPowerMode: display = 0, mode = 2
10-01 20:37:06.871 494 494 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 0
10-01 20:37:06.906 963 1022 I DisplayPowerController: Unblocked screen on after 60 ms
10-01 20:37:06.907 963 1022 V KeyguardServiceDelegate: onScreenTurnedOn()
10-01 20:37:07.041 963 1204 E LightSensor: read Events lux: 0.0
10-01 20:37:07.042 963 1022 D Sensors : activate called handle:3 enable:0
10-01 20:37:07.042 963 1022 D Sensors : bh1745-light calling driver disable
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 283: en=0
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 284: flags=0
10-01 20:37:07.042 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=1
10-01 20:37:07.042 963 1022 E LightSensor: LightSensor disable, event occur num: 1
10-01 20:37:07.046 963 1022 D Sensors : batch called handle:3 sample_ns:250000000 latency_ns:0
10-01 20:37:07.047 963 1022 D Sensors : activate called handle:3 enable:1
10-01 20:37:07.047 963 1022 D Sensors : bh1745-light calling driver setDelay 250 ms
10-01 20:37:07.047 963 1022 D Sensors : bh1745-light calling driver enable
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 283: en=1
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 284: flags=1
10-01 20:37:07.047 963 1022 W LightSensor: LightSensor, enable, 285: mEnabled=0
10-01 20:37:07.060 963 1022 D LuxLevels: bright hysteresis constant= 0.1, threshold=0.0, lux=0.0
10-01 20:37:07.060 963 1022 D LuxLevels: dark hysteresis constant= 0.2, threshold=0.0, lux=0.0
10-01 20:37:07.176 963 1574 I ActivityManager: Killing 1977:com.android.keychain/1000 (adj 906): empty #17
10-01 20:37:07.194 963 1978 D ActivityManager: cleanUpApplicationRecord -- 1977
10-01 20:37:07.220 963 1260 D SurfaceControl: Excessive delay in setPowerMode(): 349ms
10-01 20:37:07.582 963 1204 E LightSensor: read Events lux: 1.0
10-01 20:37:07.934 963 1204 E LightSensor: read Events lux: 5.0
10-01 20:37:08.286 963 1204 E LightSensor: read Events lux: 6.0
10-01 20:37:08.638 963 1204 E LightSensor: read Events lux: 5.0
10-01 20:37:08.989 963 1204 E LightSensor: read Events lux: 0.0
The following line makes me think that it might be related to some egl lib, but i dont know yet.
Code:
[B][COLOR="Red"]E libEGL : call to OpenGL ES API with no current context (logged once per thread)[/COLOR][/B]
Screen flickering was fixed by using some SDM blobs from mido because with the ones from EMUI 5 B350 it was flickering. Perhaps i should try newer firmware, such as B381/382?
Click to expand...
Click to collapse
Are your github trees up to date with the changes?
I am bringing them in to build and test on the mla-03.
trying to figure out the sim issue i was seeing on the RR and Los builds.

Cooks_08 said:
Are your github trees up to date with the changes?
I am bringing them in to build and test on the mla-03.
trying to figure out the sim issue i was seeing on the RR and Los builds.
Click to expand...
Click to collapse
Nope, my github trees (cm-14.1 branches) are not up to date. I haven't pushed yet the changes I've made.

Built cm kernel by using stock EMUI 5 kernel source.
Results:
- the bug with power on screen is gone (perhaps ive did mistakes in merging?...)
- flash works
- camera appeared in drawer. I can open it and take pics, but they didnt got saved anymore after first pic and when i toggle flash in camera it works. Camera recording doesnt seems to work. It stops at 00:00, basically not recording anything. When i touch the "start" button, it starts instantly, not like on LOS13 where there is 1-3 secs delay and freezes during recording/playback. Also, 2-3 times i got that error "cant connect to the camera".
- there seems to be more free ram, 1.8 unlike 1.4-1.5 with the other kernel. However, i noticed that once i run the camera, the free ram goes down to 1.4-1.5. When i opened all apps except camera, it went to 1.5 and once i closed them it went to 1.7. In my opinion, it looks like the camera has a memory leak at this moment. Also, logcat is being spammed with errors when camera is running.
The camera problems should be related to the blobs now. I dont know why flash and camera are working with stock kernel, but i think its because it has newer huawei drivers.
Using stock kernel source kinda sux. For example, its harder to upstream it since you dont know from which CAf source to upstream it (maybe there is a way to find out) and you will run into more conflicts. Also, maybe Huawei did some changes which sux compared to CAF ones. I guess ill use it for a while since those issues gets fixed, but sooner or later ill try to update the huawei drivers on the "main" kernel and see how it goes.
I'm not sure, but I think phone is a bit slower with stock kernel source. E.g. settings is opening a bit slower (when I've opened it from notification drawer).
For now, im just happy that the mentioned issues are gone.

Made a new build of LOS14 with N blobs, but still same results. GPS might work, but i cant test it since there is no signal and there was no wifi because the kernel with new ramdisk didnt boot, so i used the previous kernel where ive did a mistake with the wifi.
Ive managed to fix sensors, althought it seems that its rotating kinda slow. I havent managed to fix RIL and right now i think i give up on it. Im wasting too much time on this since i lack knowledge, time in which i should do something useful for myself.
Ill push the changes to github later/someday as maybe someone wants to continue.

#Henkate said:
Made a new build of LOS14 with N blobs, but still same results. GPS might work, but i cant test it since there is no signal and there was no wifi because the kernel with new ramdisk didnt boot, so i used the previous kernel where ive did a mistake with the wifi.
Ive managed to fix sensors, althought it seems that its rotating kinda slow. I havent managed to fix RIL and right now i think i give up on it. Im wasting too much time on this since i lack knowledge, time in which i should do something useful for myself.
Ill push the changes to github later/someday as maybe someone wants to continue.
Click to expand...
Click to collapse
Sorry to hear that but thanks for all your contributions buddy :good::good:!!! it's too bad that there is such a lack of support for that phone...quite frustrating....not sure i'm going back to a Huawei phone after this.....

icutzo said:
Sorry to hear that but thanks for all your contributions buddy :good::good:!!! it's too bad that there is such a lack of support for that phone...quite frustrating....not sure i'm going back to a Huawei phone after this.....
Click to expand...
Click to collapse
Thank you for your words!
Yeah, indeed. Nova isn't the only Huawei phone which lacks support... Nova is my first and last Huawei phone as well.
I'm still thinking about working on LOS14, but I'm simply stuck at debugging it.
Let's say that I use MM blobs. That means that RIL and auto rotate is working fine, but no camera and flash. Camera and flash would probably get fixed by using N blobs / N drivers (kernel), but camera still has problems even with N blobs and stock N kernel (pics doesn't gets saved, video recording starts but stop right away). And there's the other bugs left (notification led, fingerprint, Bluetooth and maybe other issues) where I'll be stuck.
Too bad that we've lost Grarak. It's been one year since Nova has been released and I doubt that another dev will come here.

#Henkate said:
Thank you for your words!
Yeah, indeed. Nova isn't the only Huawei phone which lacks support... Nova is my first and last Huawei phone as well.
I'm still thinking about working on LOS14, but I'm simply stuck at debugging it.
Let's say that I use MM blobs. That means that RIL and auto rotate is working fine, but no camera and flash. Camera and flash would probably get fixed by using N blobs / N drivers (kernel), but camera still has problems even with N blobs and stock N kernel (pics doesn't gets saved, video recording starts but stop right away). And there's the other bugs left (notification led, fingerprint, Bluetooth and maybe other issues) where I'll be stuck.
Too bad that we've lost Grarak. It's been one year since Nova has been released and I doubt that another dev will come here.
Click to expand...
Click to collapse
There was another dev here in Nova forums, EVA I think. But we lost him before the kernel releases :/
Enviado de meu HUAWEI CAN usando Tapatalk

#Henkate said:
Thank you for your words!
Yeah, indeed. Nova isn't the only Huawei phone which lacks support... Nova is my first and last Huawei phone as well.
I'm still thinking about working on LOS14, but I'm simply stuck at debugging it.
Let's say that I use MM blobs. That means that RIL and auto rotate is working fine, but no camera and flash. Camera and flash would probably get fixed by using N blobs / N drivers (kernel), but camera still has problems even with N blobs and stock N kernel (pics doesn't gets saved, video recording starts but stop right away). And there's the other bugs left (notification led, fingerprint, Bluetooth and maybe other issues) where I'll be stuck.
Too bad that we've lost Grarak. It's been one year since Nova has been released and I doubt that another dev will come here.
Click to expand...
Click to collapse
Yesterday ive said that, yet today ive been working on it again...
Ive managed to fix RIL on the build with N blobs. Those two libs from MM unbreak baseband "unknown" and gets RIL working:
Code:
vendor/lib64/libqmiservices.so
vendor/lib64/libril-qc-qmi-1.so
I dont know why it isnt working with N blobs, but since its working fine with those two MM blobs i guess its okay.
The bug with "do not disturb" is still there though. When i make a call, phone enters "do not disturb" mode and exit from it when the call ends. It also happens when i receive a call (after i answer).
GPS is working too, but it seems that only with High accuaracy / Battery saving modes. It doesnt work with "Device only" mode, but this also happens on LOS13 and on stock rom when there is no gapps. Ive tested with Here Wego maps and ill test GPS again someday when ill install gapps.
WORKING:
- RIL (Calls, SMS, Data)
- Wifi
- Camera
- Video recording ( no freezes until now)
- Video playback
- Audio
- Auto rotate ( its a bit slow i think)
- Auto brightness
- Flash
- GPS (still have to confirm if "Device only" works with gapps)
NOT WORKING:
- Fingerprint
- Notification led
- Bluetooth
- NFC ( i think it will be easy to fix, if its same as LOS13)
- FM-Radio (probably ive missed something in the sources)
OTHER ISSUES:
- phone enters "do not disturb mode" when a call is being answered and exit the mode when the call ends
- there is still something wrong with unlocking the screen (only the first time)
- earlier camera was showing the pics/video saved in camera app when touching the thumbnail (near the camera button), but after a reboot it seems that it doesnt show anymore the pics/video taken, but they appear in gallery
- phone stays frozen for few seconds after taking a pic with flash
- while recording a video, it looks like its a bit zoomed and the saved video looks the same
- and maybe some others which i havent experienced yet
NOTES:
- i dont know if front camera is working since my front camera got broken when ive damaged my Nova
- i need to rework the CAF kernel as im not planning to use the stock one forever. CAF one is easier to upstream and its way smoother (stock N kernel compared to CAF N ive tried before)
- i wont publish any build unless i fix fingerprint, notification led, bluetooth and the other issues mentioned above, such camera ones

#Henkate said:
Yesterday ive said that, yet today ive been working on it again...
Ive managed to fix RIL on the build with N blobs. Those two libs from MM unbreak baseband "unknown" and gets RIL working:
Code:
vendor/lib64/libqmiservices.so
vendor/lib64/libril-qc-qmi-1.so
I dont know why it isnt working with N blobs, but since its working fine with those two MM blobs i guess its okay.
The bug with "do not disturb" is still there though. When i make a call, phone enters "do not disturb" mode and exit from it when the call ends. It also happens when i receive a call (after i answer).
GPS is working too, but it seems that only with High accuaracy / Battery saving modes. It doesnt work with "Device only" mode, but this also happens on LOS13 and on stock rom when there is no gapps. Ive tested with Here Wego maps and ill test GPS again someday when ill install gapps.
WORKING:
- RIL (Calls, SMS, Data)
- Wifi
- Camera
- Video recording ( no freezes until now)
- Video playback
- Audio
- Auto rotate ( its a bit slow i think)
- Auto brightness
- Flash
- GPS (still have to confirm if "Device only" works with gapps)
NOT WORKING:
- Fingerprint
- Notification led
- Bluetooth
- NFC ( i think it will be easy to fix, if its same as LOS13)
- FM-Radio (probably ive missed something in the sources)
OTHER ISSUES:
- phone enters "do not disturb mode" when a call is being answered and exit the mode when the call ends
- there is still something wrong with unlocking the screen (only the first time)
- earlier camera was showing the pics/video saved in camera app when touching the thumbnail (near the camera button), but after a reboot it seems that it doesnt show anymore the pics/video taken, but they appear in gallery
- phone stays frozen for few seconds after taking a pic with flash
- while recording a video, it looks like its a bit zoomed and the saved video looks the same
- and maybe some others which i havent experienced yet
NOTES:
- i dont know if front camera is working since my front camera got broken when ive damaged my Nova
- i need to rework the CAF kernel as im not planning to use the stock one forever. CAF one is easier to upstream and its way smoother (stock N kernel compared to CAF N ive tried before)
- i wont publish any build unless i fix fingerprint, notification led, bluetooth and the other issues mentioned above, such camera ones
Click to expand...
Click to collapse
Hello, did you give the last updated romu link that you have made? I want to help as soon as I can.
HUAWEI CAN-L01 cihazımdan Tapatalk kullanılarak gönderildi

Tecnikadamoguz01 said:
Hello, did you give the last updated romu link that you have made? I want to help as soon as I can.
HUAWEI CAN-L01 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I haven't published any build yet.
I may publish a build in the upcoming days (maybe tomorrow) since I need help. We may be able to fix things together.
I'm stuck with fingerprint and it seems that I can't manage to fix it. I've rebooted my phone at least 100 times just to test fingerprint lol.
By the way, it seems that there's another way to fix RIL: by taking libril.so from stock (and another one if I remember properly). However, there seems to be some problems with mobile data (sometimes there's an exclamations at the data icon and network isn't working).
The problem when unlocking the screen for the first time seems to be related to notification led / light sensor because after I disable the notification led, the lockscreen problem is kinda gone.
Sensors are working without the sensor wrapper left by Grarak too, but I haven't tested if proximity is working properly (Grarak's commit regarding sensor wrapper is called "Make sure proximity is a wake up sensor").
Also, I might try to ditch the lights HAL taken from kiwi (honor 5x) by Grarak. According to logcat, it seems that the stock lights.msm8953 is "qdlights". After a google search, it seems that there's lights HAL called "qdlights" written by Google.
That's all I've found until now. No progress yet though. I've spent entire days trying to fix fingerprint (and sometimes notification led), but I haven't succeeded.

Some good news.
#Henkate said:
Yesterday ive said that, yet today ive been working on it again...
Ive managed to fix RIL on the build with N blobs. Those two libs from MM unbreak baseband "unknown" and gets RIL working:
Code:
vendor/lib64/libqmiservices.so
vendor/lib64/libril-qc-qmi-1.so
I dont know why it isnt working with N blobs, but since its working fine with those two MM blobs i guess its okay.
The bug with "do not disturb" is still there though. When i make a call, phone enters "do not disturb" mode and exit from it when the call ends. It also happens when i receive a call (after i answer).
GPS is working too, but it seems that only with High accuaracy / Battery saving modes. It doesnt work with "Device only" mode, but this also happens on LOS13 and on stock rom when there is no gapps. Ive tested with Here Wego maps and ill test GPS again someday when ill install gapps.
WORKING:
- RIL (Calls, SMS, Data)
- Wifi
- Camera
- Video recording ( no freezes until now)
- Video playback
- Audio
- Auto rotate ( its a bit slow i think)
- Auto brightness
- Flash
- GPS (still have to confirm if "Device only" works with gapps)
NOT WORKING:
- Fingerprint
- Notification led
- Bluetooth
- NFC ( i think it will be easy to fix, if its same as LOS13)
- FM-Radio (probably ive missed something in the sources)
OTHER ISSUES:
- phone enters "do not disturb mode" when a call is being answered and exit the mode when the call ends
- there is still something wrong with unlocking the screen (only the first time)
- earlier camera was showing the pics/video saved in camera app when touching the thumbnail (near the camera button), but after a reboot it seems that it doesnt show anymore the pics/video taken, but they appear in gallery
- phone stays frozen for few seconds after taking a pic with flash
- while recording a video, it looks like its a bit zoomed and the saved video looks the same
- and maybe some others which i havent experienced yet
NOTES:
- i dont know if front camera is working since my front camera got broken when ive damaged my Nova
- i need to rework the CAF kernel as im not planning to use the stock one forever. CAF one is easier to upstream and its way smoother (stock N kernel compared to CAF N ive tried before)
- i wont publish any build unless i fix fingerprint, notification led, bluetooth and the other issues mentioned above, such camera ones
Click to expand...
Click to collapse
Regarding fingerprint, ive finally managed to get rid of the following error:
Code:
E libteec : connect() failed, errno 111
E libteec : open device failed
The solution was to add the following line to the teecd service in ramdisk, like stock N has:
Code:
seclabel u:r:tee:s0
Now there is this error, related to teecd:
Code:
E tee_get_app_cert: fopen is error
D AssetAtlas: Rendered atlas in 31.06ms (13.21+17.85ms)
E tee_get_app_cert: fopen is error
E tee_get_app_cert: fopen is error
E libteec : get sign info error
E libteec : recv_cli_context_buffer=7f9a40c300 recv_cli_context_buffer->returns.code=0xffff0000
E libteec : command failed, errno = 0xffff0000
E libteec : open session failed, code=0xffff0000, origin=2
E fpc_tac : open session failed: result:-65536 orgin: 2
E fpc_tac : tee init FAILED:-65536
There are some denials for fingerprintd before those lines. Although the kernel is permissive right now, i dont know why there are those denials.
Then, ive tried to use files_contexts.bin, sepolicy, service_contexts and property_contexts from stock and when i booted i just seen that notification led is working. So, it seems that the notification led wasnt working because selinux. I assume that its same for fingerprint, but i dont know yet. Fingerprint still wasnt working after i used those files from stock and my phone wasnt being recognized (for ADB) anymore, so i couldnt take a logcat to see if the current error(s) are gone.
Ive updated ramdisk from stock and now the phone is way smoother. The settings is opening like instantly (unlike bofore when i had to wait 2-3 seconds to load and i thought that is related to stock kernel since with CAF kernel it wasnt happening).
Last night ive contacted @crpalmer regarding the fingerprint error which ive been stuck at and he answered me:
Can't connect probably means that you have a service that isn't starting correctly.
Click to expand...
Click to collapse
Thats when i started to take a look at the ramdisk and a big thanks goes to him for the progress ive made today.
Time to bring up sepolicy. Its my first time.

Related

Resurrection ROM Skype speakerphone issue

EDIT: this also happens on "Unofficial CM13" build, can't edit the title to reflect this.
Hi, sorry, I can't post in the Resurrection ROM's thread because I don't have enough posts.
Tried on latest stable and unstable Resurrection ROMs (0714), and skype mic does not work when in speakerphone mode. Here are the logs during the switch:
I'm not sure if this is the real reason, but according to the logs, it looks like skype is trying to access "speaker-mic" input, which in turn tries to access ACDB device id 11, which does not exist in audio_platform_info.xml file.
Code:
07-15 18:00:27.433 653 1533 D audio_hw_primary: out_set_parameters: enter: usecase(0: deep-buffer-playback) kvpairs: routing=2
07-15 18:00:27.442 653 1532 D audio_hw_primary: out_set_parameters: enter: usecase(12: audio-ull-playback) kvpairs: routing=2
07-15 18:00:27.563 653 1530 D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
07-15 18:00:27.564 653 1530 D audio_hw_primary: select_devices: out_snd_device(0: ) in_snd_device(52: speaker-mic)
07-15 18:00:27.564 653 1530 D audio_hw_primary: disable_audio_route: reset and update mixer path: low-latency-record
07-15 18:00:27.585 653 1530 D hardware_info: hw_info_append_hw_type : device_name = handset-mic
07-15 18:00:27.585 653 1530 D audio_hw_primary: disable_snd_device: snd_device(43: handset-mic)
07-15 18:00:27.591 653 1530 D hardware_info: hw_info_append_hw_type : device_name = speaker-mic
07-15 18:00:27.591 653 1530 D audio_hw_primary: enable_snd_device: snd_device(52: speaker-mic)
07-15 18:00:27.597 653 1530 I audio_hw_utils: audio_extn_utils_send_app_type_cfg CAPTURE app_type 69938, acdb_dev_id 11, sample_rate 48000
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 11, path = 1, app id = 0x11132, sample rate = 48000
07-15 18:00:27.598 653 1530 D : Failed to fetch the lookup information of the device 0000000B
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> AUDIO_SET_VOL_CAL cal type = 12
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> audstrm_cal->cal_type.cal_data.cal_size = 16
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> GET_AFE_TOPOLOGY_ID for adcd_id 11, Topology Id 112fb
07-15 18:00:27.598 653 1530 D : Failed to fetch the lookup information of the device 0000000B
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 11 path = 1
07-15 18:00:27.598 653 1530 D audio_hw_primary: enable_audio_route: apply mixer and update path: low-latency-record
07-15 18:00:27.611 653 1530 D audio_hw_primary: select_devices: done
07-15 18:00:27.611 653 1530 D audio_hw_primary: select_devices: out_snd_device(2: speaker) in_snd_device(0: )
07-15 18:00:27.612 653 1530 D audio_hw_primary: disable_audio_route: reset and update mixer path: low-latency-playback
07-15 18:00:27.649 653 1530 D hardware_info: hw_info_append_hw_type : device_name = handset
07-15 18:00:27.649 653 1530 D audio_hw_primary: disable_snd_device: snd_device(1: handset)
07-15 18:00:27.653 653 1530 D aud_dev_arbi: releaseOneDevice: not sending command, device argument (1) does not match any registered device
07-15 18:00:27.653 653 1530 D aud_dev_arbi: releaseOneDevice: device 1 owner is 0
07-15 18:00:27.653 653 1530 I msm8974_platform: platform_check_and_set_codec_backend_cfg: Usecase bitwidth 16, samplerate 48000
07-15 18:00:27.653 653 1530 I msm8974_platform: platform_check_and_set_codec_backend_cfg: new_snd_devices[0] is 2
07-15 18:00:27.653 653 1530 I msm8974_platform: platform_check_codec_backend_cfg Codec selected backend: 0 current bit width: 16 and sample rate: 48000
07-15 18:00:27.653 653 1530 W msm8974_platform: platform_check_codec_backend_cfg:Use default bw and sr for voice/voip calls
07-15 18:00:27.653 653 1530 D msm8974_platform: platform_check_codec_backend_cfg: resetting sample_rate back to default, backend_idx: 0
07-15 18:00:27.653 653 1530 I msm8974_platform: platform_check_codec_backend_cfg Codec selected backend: 0 updated bit width: 16 and sample rate: 48000
07-15 18:00:27.653 653 1530 D hardware_info: hw_info_append_hw_type : device_name = speaker
07-15 18:00:27.654 653 1530 D audio_hw_primary: enable_snd_device: snd_device(2: speaker)
07-15 18:00:27.654 653 1530 D aud_dev_arbi: acquireOneDevice: device owner for device 2 is 1
07-15 18:00:27.660 653 1530 I audio_hw_primary: select_devices Selected apptype: 69937
07-15 18:00:27.661 653 1530 I audio_hw_utils: audio_extn_utils_send_app_type_cfg PLAYBACK app_type 69937, acdb_dev_id 15, sample_rate 48000
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 15, path = 0, app id = 0x11131, sample rate = 48000
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> AUDIO_SET_VOL_CAL cal type = 12
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> audstrm_cal->cal_type.cal_data.cal_size = 16
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> GET_AFE_TOPOLOGY_ID for adcd_id 15, Topology Id 1025e
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 15 path = 0
07-15 18:00:27.661 653 1530 D audio_hw_primary: enable_audio_route: apply mixer and update path: low-latency-playback quat_i2s
07-15 18:00:27.701 653 1530 D audio_hw_primary: select_devices: done
07-15 18:00:27.702 653 1530 D audio_hw_extn: audio_extn_set_anc_parameters: anc_enabled:0
07-15 18:00:27.705 653 1530 D ACDB-LOADER: ACDB -> AUDIO_SET_VOL_CAL cal type = 40
07-15 18:00:27.705 653 1530 W msm8974_platform: platform_send_gain_dep_cal: Usecase list is empty
07-15 18:00:27.709 653 8510 D audio_hw_primary: in_set_parameters: enter: kvpairs=input_source=7;routing=-2147483520
07-15 18:00:27.730 653 1530 D AudioFlinger: mixer(0xf23c0000) throttle end: throttle time(2)
07-15 18:00:28.079 3146 3501 D HeadsetStateMachine: Disconnected process message: 10, size: 0
Any help would be greatly appreciated.

Galaxy Nexus Freezes

Hello.
I have installed LineageOS 13.0 on my Samsung Galaxy Nexus (GT-i9250). I use it for running Whatsapp (over wifi) and connect over Whatsapp-Web.
Sometimes it happens that the smartphone freezes and I have to reboot by unplugging the battery. The "asdb logcat" log is attached (XXXX was http). How can I avoid this? Thanks.
01-17 04:00:45.572 502 520 D Tethering: MasterInitialState.processMessage what=3
01-17 04:00:45.579 502 623 D ConnectivityService: notifyType PRECHECK for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.585 1921 1921 I UpdateCheckReceiver: Got connectivity change, has connection: true
01-17 04:00:45.585 1921 1921 I UpdateCheckReceiver: Scheduling future, repeating update checks.
01-17 04:00:45.586 502 623 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.593 1596 1596 I CmaSystemUpdateService: connectivity change: Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) }
01-17 04:00:45.593 1596 1596 I CmaSystemUpdateService: receiver: Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) }
01-17 04:00:45.597 502 5952 D NetworkMonitor/NetworkAgentInfo [WIFI () - 124]: Checking XXXXXconnectivitycheck.gstatic.com/generate_204 on "FUSION", connectivitycheck.gstatic.com=216.58.205.163,2a00:1450:4002:80a::2003
01-17 04:00:45.598 502 5952 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:45.603 2842 2915 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:45.637 1596 2106 I PinnedContentDownloader: Started downloading pinned content.
01-17 04:00:45.639 1086 1105 D PhoneInterfaceManager: [PhoneIntfMgr] getDataEnabled: subId=1 phoneId=0
01-17 04:00:45.640 1086 1105 D PhoneInterfaceManager: [PhoneIntfMgr] getDataEnabled: subId=1 retVal=false
01-17 04:00:45.641 502 515 D TelephonyManager: getDataEnabled: retVal=false
01-17 04:00:45.655 1596 1596 I iu.Environment: update connectivity state; isNetworkMetered? false, isRoaming? false, isBackgroundDataAllowed? true*
01-17 04:00:45.659 1086 2304 D TelephonyProvider: getPreferredApnIdFromApn: for subId 1
01-17 04:00:45.660 1086 2304 D TelephonyProvider: Preferred APN: -1
01-17 04:00:45.664 502 5953 D NetlinkSocketObserver: NeighborEvent{elapsedMs=31948177, 192.168.0.254, [A491B129B92C], RTM_NEWNEIGH, NUD_REACHABLE}
01-17 04:00:45.670 4897 4897 D WeatherUpdateService: onCreate
01-17 04:00:45.678 4897 4897 D WeatherUpdateService: Service started, but shouldn't update ... stopping
01-17 04:00:45.681 4897 4897 D WeatherUpdateService: onDestroy
01-17 04:00:45.686 502 515 E GpsLocationProvider: No APN found to select.
01-17 04:00:45.695 1596 2106 I PinnedContentDownloader: Finished downloading pinned content.
01-17 04:00:45.697 1596 1690 I iu.UploadsManager: num queued entries: 0
01-17 04:00:45.699 1596 1690 I iu.UploadsManager: num updated entries: 0
01-17 04:00:45.700 502 5952 D NetworkMonitor/NetworkAgentInfo [WIFI () - 124]: isCaptivePortal: ret=204 headers={null=[HTTP/1.1 204 No Content], Content-Length=[0], Date=[Wed, 17 Jan 2018 03:00:46 GMT], X-Android-Received-Millis=[1516158045699], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1516158045648]}
01-17 04:00:45.701 502 623 D ConnectivityService: setProvNotificationVisibleIntent null visible=false networkType=MOBILE extraInfo=null highPriority=false
01-17 04:00:45.701 502 623 D ConnectivityService: NetworkAgentInfo [WIFI () - 124] validation passed
01-17 04:00:45.702 502 623 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.706 502 623 D ConnectivityService: sendStickyBroadcast: action=android.net.conn.INET_CONDITION_ACTION
01-17 04:00:45.712 1596 1690 I iu.SyncManager: NEXT; no task
01-17 04:00:46.116 502 621 D IpReachabilityMonitor: watch: iface{wlan0/11}, v{4}, ntable=[192.168.0.1/NUD_REACHABLE, 192.168.0.254/NUD_REACHABLE]
01-17 04:00:46.117 502 623 D ConnectivityService: Adding Route [fd2c:81a5:7139::/64 -> :: wlan0] to network 124
01-17 04:00:46.139 502 623 D ConnectivityService: notifyType IP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:46.202 1596 2106 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:46.567 502 623 D ConnectivityService: NetTransition Wakelock (NetworkAgentInfo [WIFI () - 123] cleared because we found a replacement network
01-17 04:00:46.692 2842 5345 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:53.442 502 623 D ConnectivityService: handlePromptUnvalidated 124

mimu88 said:
Hello. I have installed LineageOS 13.0 on my Samsung Galaxy Nexus (GT-i9250). I use it for running Whatsapp (over wifi) and connect over Whatsapp-Web...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3312784
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Screen regularly turns on

Hello,
a while ago, I started having an issue with my s4 mini (serranolte).
Basically, the screen turns itself on very often. For example, I press the power button to turn it off and after a second or so it turns itself on, stays on for ~10 seconds, turns off due to screen timeout, turns on by itself and so on.
I tried both with Lineage OS 14.1 and crDroid v4.4 (android 8.1) and the issue persists.
Here's a copy of the logcat taken while this happens:
Code:
07-15 12:49:42.350 531 634 I PowerManagerService: Going to sleep due to power button (uid 1000)...
07-15 12:49:42.377 531 558 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
07-15 12:49:42.378 531 558 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8960.so from current namespace instead of sphal namespace.
07-15 12:49:42.384 531 558 W Adreno-EGL: <qeglDrvAPI_eglQueryContext:4373>: EGL_BAD_ATTRIBUTE
07-15 12:49:42.827 531 558 I DisplayPowerController: Blocking screen off
07-15 12:49:42.827 531 558 I DisplayPowerController: Unblocked screen off after 0 ms
07-15 12:49:42.827 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.827 531 558 D Sensors : activate: handle=0, enabled=0
07-15 12:49:42.843 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.843 531 558 D Sensors : activate: handle=4, enabled=0
07-15 12:49:42.843 531 558 D Sensors : LightSensor enable = 0
07-15 12:49:42.843 531 558 D Sensors : LightSensor enableSensor = 0
07-15 12:49:42.857 531 556 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
07-15 12:49:42.858 241 241 D SurfaceFlinger: Set power mode=0, type=0 flinger=0xb364e000
07-15 12:49:42.861 241 241 D qdhwcomposer: hwc_setPowerMode: Setting mode 0 on display: 0
07-15 12:49:42.871 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.871 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.879 531 634 I InputReader: Reconfiguring input devices. changes=0x00000004
07-15 12:49:42.918 531 634 I PowerManagerService: Waking up from dozing (uid=1000 reason=android.policy:KEY)...
07-15 12:49:42.922 531 558 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
07-15 12:49:42.923 531 558 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:42.923 531 558 D Sensors : setDelay: handle=4, delay=250000000
07-15 12:49:42.923 531 558 D Sensors : LightSensor setDelay = 250000000
07-15 12:49:42.923 531 558 D Sensors : LightSensor setSensorDelay = 250000000
07-15 12:49:42.923 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.923 531 558 D Sensors : activate: handle=4, enabled=1
07-15 12:49:42.923 531 558 D Sensors : LightSensor enable = 1
07-15 12:49:42.923 531 558 D Sensors : LightSensor enableSensor = 1
07-15 12:49:42.927 289 289 D audio_hw_primary: adev_set_parameters: enter: screen_state=off
07-15 12:49:42.942 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.942 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.964 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.979 1148 1148 I chatty : uid=10030(com.android.systemui) identical 2 lines
07-15 12:49:42.979 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:43.019 531 615 D Sensors : LightSensor readEvents x = 37.000000, raw = 37
07-15 12:49:43.020 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:43.020 531 558 D Sensors : activate: handle=4, enabled=0
07-15 12:49:43.020 531 558 D Sensors : LightSensor enable = 0
07-15 12:49:43.020 531 558 D Sensors : LightSensor enableSensor = 0
07-15 12:49:43.021 531 558 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:43.021 531 558 D Sensors : setDelay: handle=4, delay=1000000000
07-15 12:49:43.021 531 558 D Sensors : LightSensor setDelay = 1000000000
07-15 12:49:43.021 531 558 D Sensors : LightSensor setSensorDelay = 1000000000
07-15 12:49:43.021 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:43.021 531 558 D Sensors : activate: handle=4, enabled=1
07-15 12:49:43.021 531 558 D Sensors : LightSensor enable = 1
07-15 12:49:43.022 531 558 D Sensors : LightSensor enableSensor = 1
07-15 12:49:43.120 531 615 D Sensors : LightSensor readEvents x = 39.000000, raw = 39
07-15 12:49:43.335 241 241 D qdhwcomposer: hwc_setPowerMode: Done setting mode 0 on display 0
07-15 12:49:43.344 531 1105 D SurfaceControl: Excessive delay in setPowerMode()
07-15 12:49:43.345 531 556 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
07-15 12:49:43.363 531 634 I InputReader: Reconfiguring input devices. changes=0x00000004
07-15 12:49:43.368 241 241 D SurfaceFlinger: Set power mode=2, type=0 flinger=0xb364e000
07-15 12:49:43.368 241 241 D qdhwcomposer: hwc_setPowerMode: Setting mode 2 on display: 0
07-15 12:49:43.981 531 556 W WindowManager: Timeout waiting for drawn: undrawn=[Window{afd67f u0 StatusBar}]
07-15 12:49:43.983 531 549 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:43.983 531 549 D Sensors : setDelay: handle=0, delay=66667000
07-15 12:49:43.984 531 549 D Sensors : activate: acc_enable=1, mag_enable=0
07-15 12:49:43.984 531 549 D Sensors : activate: handle=0, enabled=1
07-15 12:49:44.054 241 241 D qdhwcomposer: hwc_setPowerMode: Done setting mode 2 on display 0
07-15 12:49:44.055 531 558 I DisplayPowerController: Unblocked screen on after 1133 ms
07-15 12:49:44.063 531 1105 D SurfaceControl: Excessive delay in setPowerMode()
07-15 12:49:44.079 531 558 W PowerManagerService: Screen on took 1160 ms
07-15 12:49:44.081 1148 1148 I Choreographer: Skipped 63 frames! The application may be doing too much work on its main thread.
07-15 12:49:44.120 531 615 D Sensors : LightSensor readEvents x = 35.000000, raw = 35
07-15 12:49:44.132 289 389 D audio_hw_primary: adev_set_parameters: enter: screen_state=on
Hoping someone can help
Ask me if you need to know anything else, I really hope this isn't an hardware issue...
Thanks, have a nice day

I've also tried flashing an older ROM, Pacman ROM (android 4.3) and I get the same issue.
This leads me to think it is an hardware related issue. Here's the Sensors output:
Code:
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=4, enabled=0
D/Sensors ( 836): LightSensor enable = 0
D/Sensors ( 836): LightSensor enableSensor = 0
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=1000000000
D/Sensors ( 836): LightSensor setDelay = 1000000000
D/Sensors ( 836): LightSensor setSensorDelay = 1000000000
D/Sensors ( 836): activate: acc_enable=0, mag_enable=0
D/Sensors ( 836): activate: handle=0, enabled=0
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=66667000
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=0, enabled=1
D/Sensors ( 836): setDelay: acc_delay=200000000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=200000000
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=66667000
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=4, enabled=1
D/Sensors ( 836): LightSensor enable = 1
D/Sensors ( 836): LightSensor enableSensor = 1
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=200000000
D/Sensors ( 836): LightSensor setDelay = 200000000
D/Sensors ( 836): LightSensor setSensorDelay = 200000000
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=1000000000
D/Sensors ( 836): LightSensor setDelay = 1000000000
D/Sensors ( 836): LightSensor setSensorDelay = 1000000000
If you know of anything that could solve this, please let me know. Thanks.

[HELP] Google Camera crashing with cam2api enable and rooted on Pixel Experience

Hello everyone!
I need to record 1080p60fps videos on my Redmi Note 5 (pro) global. I have official Pixel Experience rom. I don't really care about Google Cam, but it seems like the only app that allows to record in 60fps (open camera record in 4k, but not in 1080p60), so I tried to install it. I have Magisk v16.0 with Camera2 API Enabler installed (checked using getprop and it is enabled), but I practically every google camera mod I tried is crashing. Here is log (same for all):
HTML:
07-18 11:27:15.713 746 796 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [2, 0]
07-18 11:27:15.779 3205 3475 D AudioService: Stream muted, skip playback
07-18 11:27:15.780 3205 8023 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.Pixel2Mod/com.android.camera.CameraLauncher bnds=[30,880][234,1172]} from uid 10026
07-18 11:27:15.835 3205 3963 I ActivityManager: Start proc 9448:com.google.android.Pixel2Mod/u0a122 for activity com.google.android.Pixel2Mod/com.android.camera.CameraLauncher
07-18 11:27:15.923 4495 4495 I MicroDetector: Keeping mic open: false
07-18 11:27:15.923 4495 4288 I DeviceStateChecker: DeviceStateChecker cancelled
07-18 11:27:15.923 4495 2001 I AudioController: internalShutdown
07-18 11:27:15.924 4495 9439 I MicroRecognitionRunner: Stopping hotword detection.
07-18 11:27:15.924 4495 1171 I MicroRecognitionRunner: Detection finished
07-18 11:27:15.952 720 7863 D audio_hw_primary: in_standby: enter: stream (0xe64c4800) usecase(18: audio-record)
07-18 11:27:15.993 9448 9466 I CameraManagerGlobal: Connecting to camera service
07-18 11:27:16.000 9448 9466 W CameraManagerGlobal: [soar.cts] ignore the status update of camera: 2
07-18 11:27:16.001 9448 9466 W CameraManagerGlobal: [soar.cts] ignore the status update of camera: 3
07-18 11:27:16.003 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:16.007 720 7863 D audio_hw_primary: disable_audio_route: reset and update mixer path: audio-record
07-18 11:27:16.008 720 7863 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_id 18 of type 1 for Event 2, with Raise=0
07-18 11:27:16.008 720 7863 D hardware_info: hw_info_append_hw_type : device_name = voice-rec-mic
07-18 11:27:16.008 720 7863 D audio_hw_primary: disable_snd_device: snd_device(95: voice-rec-mic)
07-18 11:27:16.008 720 7863 D msm8916_platform: platform_split_snd_device: snd_device(95) num devices(0) new_snd_devices(0)
07-18 11:27:16.011 720 7863 I soundtrigger: audio_extn_sound_trigger_update_device_status: device 0x5f of type 1 for Event 0, with Raise=1
07-18 11:27:16.011 720 7863 D sound_trigger_platform: platform_stdev_check_and_update_concurrency: concurrency active 0, tx 0, rx 0, concurrency session_allowed 1
07-18 11:27:16.013 722 1748 I QCamera : <HAL><INFO> getCameraInfo: 397: Camera id 0 API version 256
07-18 11:27:16.013 722 1748 I QCamera : <HAL><INFO> getCamInfo: 10404: camera 0 resource cost is 100
07-18 11:27:16.013 720 7863 D audio_hw_primary: in_set_parameters: enter: kvpairs=routing=0
07-18 11:27:16.014 2715 3296 I SoundTriggerHwService::Module: onCallbackEvent no clients
07-18 11:27:16.015 4495 2002 I MicrophoneInputStream: mic_close SR : 16000 CC : 16 SO : 1999
07-18 11:27:16.017 720 7863 D audio_hw_primary: adev_close_input_stream: enter:stream_handle(0xe64c4800)
07-18 11:27:16.017 720 7863 D audio_hw_primary: in_standby: enter: stream (0xe64c4800) usecase(18: audio-record)
07-18 11:27:16.035 9448 9466 I CAM_MaxNativeMemory: Max native memory overridden (device): 1160
07-18 11:27:16.036 9448 9466 I CAM_MemoryManager: Max native memory: 1160000000 bytes. (1160MB).
07-18 11:27:16.046 9448 9448 I CAM_Instrumentation: CameraActivity: App OnCreate duration: 8ms
07-18 11:27:16.047 9448 9448 I CAM_Instrumentation: CameraActivity: App OnCreate End to Activity OnCreate Start: 24ms
07-18 11:27:16.047 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onCreate
07-18 11:27:16.050 9448 9466 W linker : "/data/app/com.google.android.Pixel2Mod-jEj88MEA0xdz3YI6ZIKzOA==/lib/arm64/libgcam_swig_jni.so" unused DT entry: type 0xf arg 0x46e68
07-18 11:27:16.054 722 1748 I QCamera : <HAL><INFO> getCameraInfo: 397: Camera id 1 API version 256
07-18 11:27:16.054 722 1748 I QCamera : <HAL><INFO> getCamInfo: 10404: camera 1 resource cost is 100
07-18 11:27:16.064 9448 9448 I CAM_CameraUiInflater: Initializing Window Flags
07-18 11:27:16.066 9448 9467 I CAM_PermissionsChecker: Checking for critical permissions.
07-18 11:27:16.076 3205 3963 I ActivityManager: START u0 {act=android.content.pm.action.REQUEST_PERMISSIONS pkg=com.android.packageinstaller cmp=com.android.packageinstaller/.permission.ui.GrantPermissionsActivity (has extras)} from uid 10122
07-18 11:27:16.104 9448 9448 I CAM_CameraUiInflater: Initializing Camera Ui
07-18 11:27:16.106 9448 9466 I CAM_MemoryManager: Registering feature: HDR_PLUS
07-18 11:27:16.108 9448 9466 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.203 9448 9448 I CAM_CameraUiInflater: Initializing Action Bar
07-18 11:27:16.213 9448 9448 I CAM_Instrumentation: CameraActivity: OnCreate duration: 166ms
07-18 11:27:16.213 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onStart
07-18 11:27:16.215 9448 9448 I CAM_Instrumentation: CameraActivity: OnCreate End to OnResume Start: 2ms
07-18 11:27:16.215 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onResume
07-18 11:27:16.216 9448 9448 I CAM_Instrumentation: CameraActivity: OnResume duration: 0ms
07-18 11:27:16.220 9448 9474 D OpenGLRenderer: HWUI GL Pipeline
07-18 11:27:16.226 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onPause
07-18 11:27:16.239 9448 9448 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.239 9448 9448 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.239 9448 9448 D AndroidRuntime: Shutting down VM
07-18 11:27:16.239 9448 9448 E AndroidRuntime: FATAL EXCEPTION: main
07-18 11:27:16.239 9448 9448 E AndroidRuntime: Process: com.google.android.Pixel2Mod, PID: 9448
07-18 11:27:16.239 9448 9448 E AndroidRuntime: java.lang.NullPointerException: Attempt to get length of null array
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at cok.a(Unknown Source:166)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at ccv.a(Unknown Source:54)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at com.a(Unknown Source:58)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at jxg.a(Unknown Source:15)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at con.run(Unknown Source:36)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at gvc.run(Unknown Source:8)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at hzy.run(Unknown Source:2)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at avv.run(Unknown Source:5)
07-18 11:27:16.244 9448 9448 E CAM_SilentFeedback: Could not find SilentFeedbackService, not sending crash info.
07-18 11:27:16.248 3205 3298 I ActivityManager: Showing crash dialog for package com.google.android.Pixel2Mod u0
07-18 11:27:17.333 14120 14231 D ClClient: Not sending keepalive. Current connection state=STOPPED
07-18 11:27:18.877 4495 1171 I EventLogSendingHelper: Sending log events.
07-18 11:27:19.006 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:19.195 4470 4525 I cr_BindingManager: Release moderate connections: 1
07-18 11:27:22.009 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:25.811 3205 3295 W ActivityManager: Launch timeout has expired, giving up wake lock!
07-18 11:27:25.012 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:27.333 14120 14231 D ClClient: Not sending keepalive. Current connection state=STOPPED
07-18 11:27:28.015 833 891 I mmid : select timeout: wait for receiving msg
It immediately crashes right after I open it. It just asks for camera and microphone permissions. I think there is some internal issue (maybe?). Crashing at:
HTML:
java.lang.NullPointerException: Attempt to get length of null array

I've had the same error.
So i enabled cam2api in build.prop manualy
Steps to follow on this ROM, else you will face force closes
1. Go to /system/ & copy build.prop to internal storage for backup
2. Open the system/build.prop with text editor
3. Scroll to the last & leave a space after the last line
4. Add the below lines
#Camera2 API
persist.camera.HAL3.enabled=1
5. reboot

burish said:
I've had the same error.
So i enabled cam2api in build.prop manualy
Steps to follow on this ROM, else you will face force closes
1. Go to /system/ & copy build.prop to internal storage for backup
2. Open the system/build.prop with text editor
3. Scroll to the last & leave a space after the last line
4. Add the below lines
#Camera2 API
persist.camera.HAL3.enabled=1
5. reboot
Click to expand...
Click to collapse
OH YEEEEAAAAAHHH! Thanks a lot! It is working now!

Damm. It's working, but there is no 60fps recording. Any ideas?

Which Version of GCAM do you use?
In https://forum.xda-developers.com/redmi-note-5-pro/themes/app-arnova8g2s-google-camera-port-t3784423 its actually listed as a feature
Maybe you should try the listed gcam from 1 post

I am also on Pixel Experience. For me Arnovas GCAM Pixel2 Mod v.8.1. works without any bugs. I flashed camera2api as zip file trough twrp. Now im waiting for stock camera port.

HTC 10 - Bluetooth Freezing, Stuttering & Stopping - Oreo - Telstra

Hello! I have a Bluetooth Connection Issue with my HTC 10...
Situation:
HTC 10, 8.0
Telstra (Australia)
Randomly when I'm connected to Bluetooth devices (car and speakers) the music or audio playback stutters, freezes or stops completely.
Fixes attempted
Wipe caches, wiped data, uninstalled, reinstalled, cleared Bluetooth caches and data
Reset network preferences (as per recommendation from Telstra crowd support)
3 Factory resets and complete wipes (this year)
2 new car Bluetooth kits (I'm not trying anymore)
The other morning at 9:34 the music froze suddenly as I was driving. I taught myself how to do a logcat and then searched through everything that happened at 9:34am that had to do with Bluetooth and/or errors.
Logcat
07-21 09:34:23.177 1041 20533 29781 W AudioFlinger: write blocked for 2096 msecs, 1 delayed writes, thread 0xf3003240
07-21 09:34:23.178 1041 20533 29781 I bt\_a2dp\_hw: start\_audio\_datapath: state 3
07-21 09:34:23.179 1002 28723 28777 I chatty : uid=1002(bluetooth) uipc-main expire 1204 lines
07-21 09:34:23.180 1041 20533 29781 E bt\_a2dp\_hw: a2dp\_command: A2DP COMMAND A2DP\_CTRL\_CMD\_START error 1
07-21 09:34:23.180 1041 20533 29781 E bt\_a2dp\_hw: start\_audio\_datapath: Audiopath start failed (status -1)
07-21 09:34:23.202 1041 20533 29781 I bt\_a2dp\_hw: start\_audio\_datapath: state 3
07-21 09:34:23.205 1041 20533 29781 E bt\_a2dp\_hw: a2dp\_command: A2DP COMMAND A2DP\_CTRL\_CMD\_START error 1
07-21 09:34:23.205 1041 20533 29781 E bt\_a2dp\_hw: start\_audio\_datapath: Audiopath start failed (status -1)
07-21 09:34:23.227 1041 20533 29781 I bt\_a2dp\_hw: start\_audio\_datapath: state 3
07-21 09:34:23.229 1041 20533 29781 E bt\_a2dp\_hw: a2dp\_command: A2DP COMMAND A2DP\_CTRL\_CMD\_START error 1
07-21 09:34:23.230 1041 20533 29781 E bt\_a2dp\_hw: start\_audio\_datapath: Audiopath start failed (status -1)
07-21 09:34:23.252 1041 20533 29781 I bt\_a2dp\_hw: start\_audio\_datapath: state 3
07-21 09:34:23.254 1041 20533 29781 E bt\_a2dp\_hw: a2dp\_command: A2DP COMMAND A2DP\_CTRL\_CMD\_START error 1
So I'm guessing that those errors have something to do with the Bluetooth in my phone connecting to the Bluetooth Audio Kit in my car. This may explain why I get the 'Bluetooth Has stopped Unexpectedly' Error Report at least once a month from my phone.
It seems that there are similar issues here on XDA & Reddit from people who are either installing custom Roms and kernels, or who have not modified their phones are are going through something similar. I haven't rooted (and I don't plan to). Some of these people have gotten replacement devices but the issue presents itself again.
I have posted the same information on Reddit, Telstra Crowd Support and now here.
I don't suppose HTC are going to release a patch...?
Who else has this issue?
Any suggestions or ideas?
Thank you!

Develop Bugs

welcome