[Huawei Nova/Nova Plus Guides, News, & Discussion] #Henkate:
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:

# 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

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

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 = com.android.server.policy.PhoneWindowManager$2@890b4b0)
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.

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