Develop Bugs

[ROM][Official] AICP - 12.1 - N 7.1 amami

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the rebrand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or LAOS team, if it concerns their code base. This rom isn't LAOS supported, so no need to report errors or bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
maxwen
DU team
SlimRoms team
Resurrection Remix team
OmniRom team
SuperLamic, Sony-Lineage-3.4 team, Hazou, Sonyxperiadev
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 12.1
Download link: http://dwnld.aicp-rom.com/?device=amami
No more official Nougat support since focus shifted to Oreo! You can still get my unofficial Nougat builds here:
https://basketbuild.com/devs/SpiritCroc/amami/AICP-n7.1
Full Changelog link: http://dwnld.aicp-rom.com/?device=amami
Google Apps:
Beans gapps
Or
Open GApps (ARM or ARM64 7.1 pico or nano, depending on your phone's architecture)
If you experience a black screen in some apps (e.g. in Youtube or in camera app), please go to Developer options and enable "Disable HW overlays". Alternatively, you can also add a quick setting for this setting after having enabled developer settings. This setting is not persistent, so you will have to set it after each boot!
Reboot to recovery not working
You tell...
The ROM should contain everything you need to enjoy Android Nougat. You don't need to install any Add-Ons, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
Make sure you have real recovery!
Download the ROM and GApps and transfer them to your device
Boot to recovery (TWRP recommended)
Wipe system, Cache, data and ART/Dalvik cache
Flash ROM Zipfile
Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
Flash/Install the root solution of choice (optional)
Reboot to system
The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)!
Supported root solutions:
Magisk v13.x
SuperSU - stable and beta available (Site by CCMT that took over the the marketing from chainfire)
SuperSU - direct download link for the latest SuperSU directly from the dev (chainfire)
Lineage SU-addon (check your needed version: 14.1 arm or arm64) -> the removal zip is available here too.
PREREQUISITE FOR OTA:
To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. Zip gets saved in the "AICP_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery.
If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)
IceColdJelly AICP G+ community
Kernel source: https://github.com/AICP/kernel_sony_msm8974/tree/n7.1
ROM & Additional links:
Gerrit Code Review
Github
You want to see a normal night at the "DEV office", click here!!​
XDA:DevDB Information
Android Ice Cold Project (AICP) 12.1 Amami, ROM for the Sony Xperia Z1 Compact
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked bootloader, real recovery
Based On: AOKP, CyanogenMod, LineageOS, Omni-ROM, DirtyUnicorns
Version Information
Status: No Longer Updated
Created 2016-07-29
Last Updated 2018-03-02

another new rom How is it going with the camera?

NeoAqr said:
another new rom How is it going with the camera?
Click to expand...
Click to collapse
I heard that it's similar to du

Someone have some Screenshots from this ROM ?

FotoMichi said:
Someone have some Screenshots from this ROM ?
Click to expand...
Click to collapse
It looks like normal marshmallow, but wait, I'll install it and give you some

Here are screenshots!
 @SpiritCroc why SIM card don't working? o

CmDaRkShAdOw said:
@SpiritCroc why SIM card don't working? o
Click to expand...
Click to collapse
It's working for me, although the SIM is not recognized immediately, but a few seconds after boot.
Have you tried a reboot? Clean flash? SIM was working for you on DU, am I right? Have you modified the ROM (Xposed, ...)?

SpiritCroc said:
It's working for me, although the SIM is not recognized immediately, but a few seconds after boot.
Have you tried a reboot? Clean flash? SIM was working for you on DU, am I right? Have you modified the ROM (Xposed, ...)?
Click to expand...
Click to collapse
I was waiting a few minutes. Tried reboot, clean flash(wipe system, data,cache, art) on DU was fine, not modified

CmDaRkShAdOw said:
Here are screenshots!
@SpiritCroc why SIM card don't working? o
Click to expand...
Click to collapse
whoop. new SnapDragon camera UI. I wonder if the camera is more stable than DU's . if it doesn't freeze frequently I will go get it now

NeoAqr said:
whoop. new SnapDragon camera UI. I wonder if the camera is more stable than DU's . if it doesn't freeze frequently I will go get it now
Click to expand...
Click to collapse
Yes. It's more stable than du,and photos are better.

SIM is working for me. AudioFX is crashing when starting to play music. Music playing works, but the crash is annoying and I guess equalizer doesn't work.
Also my bluetooth MAC address has a lot of zeros. Is that normal?
Overall looks like a good MM ROM! Thank you!
EDIT: oh. Very important! Flashing this ROM will overwrite your recovery with CM recovery. I hope that the ROM creator can remove it.

SpiritCroc said:
AICP
Click to expand...
Click to collapse
Sudden battery drain a couple of times on 7/24 build, but love it overall, (i usually assume stuff like that has simething to do with Xposed, etc. anyway). Using newest build now. What would really wrap this up nicely is M5 kernel. The idea has been tossed around a little. @Myself5 has said he's willing to build if someone will maintain, (he doesn't have Z1c anymore). Maybe you'd be a candidate...
[GER]Roxxor said:
SIM is working for me. AudioFX is crashing when starting to play music. Music playing works, but the crash is annoying and I guess equalizer doesn't work.
Also my bluetooth MAC address has a lot of zeros. Is that normal?
Overall looks like a good MM ROM! Thank you!
EDIT: oh. Very important! Flashing this ROM will overwrite your recovery with CM recovery. I hope that the ROM creator can remove it.
Click to expand...
Click to collapse
We all should use real recovery by now - can't be overwritten.

levone1 said:
We all should use real recovery by now - can't be overwritten.
Click to expand...
Click to collapse
Of course real recovery can be overwritten, why shouldn't it? It just depends if the flashing procedure writes a new recovery to the recovery partition or not. This is the first time that a ROM flash overwrote my recovery.
And I am using it. I did the Emma bootloader upgrade once and didn't have any compatibility problems with ROMs requiring real recovery. And I used TWRP 3.0.2 and flash it by "fastboot flash recovery".
Didn't this flashing procedure overwrite the recovery for anybody else? I flashed the 29.07 build.
EDIT: Ok. I do not get what is happening here... I flashed TWRP via fastboot and it is still launching CM recovery. I did not experience this strange behavior with CM12.1, DU MM and FXP MM AOSP. With all those ROMs TWRP started without issues.
EDIT2: I found the issue. I think this ROM installs a "unreal recovery" in system. If I push the VolDown Button from the moment I push Power, then TWRP starts. If I only push VolDown when the violet light appears, then CM recovery starts. I find this quite confusing, and I guess this is aimed at people without real recovery. Would be nice if @SpiritCroc could clarify if this is intentional.
I figured that CM recovery is in system, because if I install RR kernel (boot.img) and TWRP (recovery.img) still CM recovery is started if pressing on violet light. It is the only partition I did not overwrite.

levone1 said:
What would really wrap this up nicely is M5 kernel. The idea has been tossed around a little. @Myself5 has said he's willing to build if someone will maintain, (he doesn't have Z1c anymore). Maybe you'd be a candidate...
Click to expand...
Click to collapse
Well, I don't have any experiences with modifying kernel (I've always used the kernel that comes with the ROM in the past).
I can build the kernel together with the ROM, anything else I'd have to learn first...
[GER]Roxxor said:
Of course real recovery can be overwritten, why shouldn't it? It just depends if the flashing procedure writes a new recovery to the recovery partition or not. This is the first time that a ROM flash overwrote my recovery.
And I am using it. I did the Emma bootloader upgrade once and didn't have any compatibility problems with ROMs requiring real recovery. And I used TWRP 3.0.2 and flash it by "fastboot flash recovery".
Didn't this flashing procedure overwrite the recovery for anybody else? I flashed the 29.07 build.
EDIT: Ok. I do not get what is happening here... I flashed TWRP via fastboot and it is still launching CM recovery. I did not experience this strange behavior with CM12.1, DU MM and FXP MM AOSP. With all those ROMs TWRP started without issues.
EDIT2: I found the issue. I think this ROM installs a "unreal recovery" in system. If I push the VolDown Button from the moment I push Power, then TWRP starts. If I only push VolDown when the violet light appears, then CM recovery starts. I find this quite confusing, and I guess this is aimed at people without real recovery. Would be nice if @SpiritCroc could clarify if this is intentional.
I figured that CM recovery is in system, because if I install RR kernel (boot.img) and TWRP (recovery.img) still CM recovery is started if pressing on violet light. It is the only partition I did not overwrite.
Click to expand...
Click to collapse
Real recovery isn't touched by AICP, it still can be accessed the usual way (first press volume button before pressing power & hold until sony logo appears). It's the same way as in DU. In DU, you cannot reboot to recovery or boot to recovery when the sony logo appears after a normal power on. AICP has an inbuilt recovery (CM recovery in this case) that can be accessed via reboot to recovery or when the notification LED is showing during boot up, which can be used instead of real recovery, but doesn't replace it. That's the intended behaviour. If I find the time I might look into replacing the built-in CM recovery with TWRP.
First press & hold volume button, power on -> device boots recovery partition
Power on while not pressing volume buttons -> device boots into ROM
Power on while not pressing volume buttons, then press volume when notification LED lights up -> tell the ROM you want to access recovery, which has no access to real recovery, but uses inbuilt recovery instead

SpiritCroc said:
AICP has an inbuilt recovery (CM recovery in this case) that can be accessed via reboot to recovery or when the notification LED is showing during boot up, which can be used instead of real recovery, but doesn't replace it. That's the intended behaviour. If I find the time I might look into replacing the built-in CM recovery with TWRP.
Click to expand...
Click to collapse
Thank you very much for clarifying!
About the AudioFX issue(somehow I cant attach files):
Code:
11:22:04.332 819 2920 I MediaFocusControl: AudioFocus requestAudioFocus() from [email protected][email protected] req=1flags=0x0
07-30 11:22:04.335 336 6146 D NuPlayerDriver: reset(0xb3a38120)
07-30 11:22:04.335 336 6146 D NuPlayerDriver: notifyListener_l(0xb3a38120), (8, 0, 0)
07-30 11:22:04.335 336 6198 W AMessage: failed to post message as target looper for handler 0 is gone.
07-30 11:22:04.335 336 6198 D NuPlayerDriver: notifyResetComplete(0xb3a38120)
07-30 11:22:04.337 5999 6011 E MediaPlayer-JNI: JNIMediaPlayerFactory: bIsQCMediaPlayerPresent 0
07-30 11:22:04.337 5999 6011 E MediaPlayer-JNI: JNIMediaPlayerFactory: bIsQCMediaPlayerPresent 0
07-30 11:22:04.338 6181 6181 I HeadsetService: Starting service.
07-30 11:22:04.347 336 3033 W AudioFlinger: createEffect() effect not found
07-30 11:22:04.347 6181 6181 E AudioEffect: set(): AudioFlinger could not create effect, status: -22
07-30 11:22:04.347 6181 6181 E AudioEffects-JNI: AudioEffect initCheck failed -3
07-30 11:22:04.348 6181 6181 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
07-30 11:22:04.348 6181 6181 E HeadsetService: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.348 6181 6181 E HeadsetService: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.media.audiofx.Equalizer.<init>(Equalizer.java:139)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService$EffectSet.<init>(HeadsetService.java:95)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService.saveDefaults(HeadsetService.java:521)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService.onCreate(HeadsetService.java:389)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.handleCreateService(ActivityThread.java:2923)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.-wrap4(ActivityThread.java)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1446)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.os.Handler.dispatchMessage(Handler.java:102)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.os.Looper.loop(Looper.java:148)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.main(ActivityThread.java:5475)
07-30 11:22:04.348 6181 6181 E HeadsetService: at java.lang.reflect.Method.invoke(Native Method)
07-30 11:22:04.348 6181 6181 E HeadsetService: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
07-30 11:22:04.348 6181 6181 E HeadsetService: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-30 11:22:04.350 336 336 W AudioFlinger: createEffect() effect not found
07-30 11:22:04.350 6181 6181 E AudioEffect: set(): AudioFlinger could not create effect, status: -22
07-30 11:22:04.350 6181 6181 E AudioEffects-JNI: AudioEffect initCheck failed -3
07-30 11:22:04.350 6181 6181 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
07-30 11:22:04.351 6181 6181 D AndroidRuntime: Shutting down VM
07-30 11:22:04.352 6181 6181 E AndroidRuntime: FATAL EXCEPTION: main
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Process: org.cyanogenmod.audiofx, PID: 6181
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Theme: themes:{default=, iconPack:org.twelf.cmtheme}
07-30 11:22:04.352 6181 6181 E AndroidRuntime: java.lang.RuntimeException: Unable to start service [email protected] with Intent { act=android.media.action.OPEN_AUDIO_EFFECT_CONTROL_SESSION cmp=org.cyanogenmod.audiofx/.HeadsetService (has extras) }: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3073)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.-wrap17(ActivityThread.java)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1461)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5475)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Caused by: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.media.audiofx.Equalizer.<init>(Equalizer.java:139)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService$EffectSet.<init>(HeadsetService.java:95)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService.addSession(HeadsetService.java:208)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService.onStartCommand(HeadsetService.java:431)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3056)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: ... 8 more
07-30 11:22:04.354 819 835 W ActivityManager: Process org.cyanogenmod.audiofx has crashed too many times: killing!
EDIT: Additional question: Why did you go for omnirom sources and not directly for sonyxperiadev?

[GER]Roxxor said:
EDIT: Additional question: Why did you go for omnirom sources and not directly for sonyxperiadev?
Click to expand...
Click to collapse
I'm a bit lazy and they have inline kernel building while sonyxperiadev use a prebuilt kernel.
Additionally, they have some more modifications like TWRP configs which can become handy when building some custom ROMs, and they even have some commits cherry-picked from CM device tree (e.g. in order to enable reboot to recovery), while sonyxperiadev is clearly aimed at pure AOSP.
It worked fine when I was experimenting with different device trees for DU, and for now I just stick with it.
I think I'm going to directly fork sonyxperiadev when Nougat arrives, though

Now this thead has explained a lot of my confusion regarding recovery i have tried ACIP but because there was only 2-3 Cpu gouvernors and device was always hot (something is causing increased temps and batt drain)anyway there are 2 recoverys one that we call real recovery and that one after power on which flashes alongside ROM.
And if you lower the freq of cpu you will get random reboots
Sent from my D5503 using XDA-Developers mobile app

Verry nice Rom. Camera is a bit more stable than the du one.
For me Autorotation don't work.

I'm sorry. SIM Card works fine. Last time I had issue while flashing and I ignored it. Today SIM card didn't work on DU. Don't know why.

New build is up.
- Fix sensors not working (e.g. no working auto-rotation)
I was surprised by how few people noticed/complained about that...

[DEBUGGING] LineageOS 14.1 disscusion

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
Took some pics with mom's phone (S3 neo running CM 11). They're attached to this post.
I've found out that when I use Live Display (night mode), the screen doesn't flicker.
I'm not sure yet, but I think auto brightness works fine. Here are some other bugs I've discovered:
1) Flashlight doesn't work.
2) Once the screen goes off, you can't power it on anymore. You have to reboot it in order to see the screen.
3) Fingerprint settings doesn't appear, so there's problems with it too.
Yesterday I've made some progress regarding audio. Audio is working fine when headphones are connected, but speaker still broken.
EDIT:
Dunno why the pics got rotated when I've attached them.

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

[BUILDING][OMNI9]Help building omni 9 for daisy

I need help Building omnirom9.0 for daisy, got it to compile and boot (bootlooping bootanimation, logs can be found below) but need help in interpreting the logs.
Sources:
Kernel mi kernel with disabled verity and FEC
Devie combined msm8953-common and daisy (branch los15) from lineage build and adjusted to omni
Vendor took vendor from v10.0.1.0.PDLMIFJ, added everything to copy files, adjusted with apps and missing files from system and deleted the obsolete
OMNIROM
Logcat
Saw that some libraries are missing, will search them in vendor/system from stock and add them when i have time. If someone finds a solution for an error please copy&paste the line(s) in logcat leading to the solution, so me (and probably others) can learn from it and be of more use next time.
@ada12
@reujea0
@Hakkinan
ada12 and me made a Telegram group for mi a2 lite developing, who wants to join can pm me or ada12.

I've never compiled for a treble device but as i know vendor tree is useless because all needed blobs are in vendor partition, you shouldn't take things from stock system.
In fact GSI works at 100% with only vendor libraries (ok, code is patched but that's not the point).
I think we should target GSI instead, researching and giving fixes for roms that have litte issues and compiling new ones (also for the joy of others device's owners).
If you don't think so please explain why, i'm open to dialog

It is clear from the log that there is an issue with gnss(Global Navigation Satellite System). SO location won't most likely work, for the time being try to disable/remove everything related to gnss, this should let you at least boot or go further in the boot process. I will investigate further.
---------- Post added at 05:35 PM ---------- Previous post was at 05:18 PM ----------
I think we might have to patchelf https://github.com/NixOS/patchelf to replace the dependencieng, like this https://github.com/LineageOS/androi...mmit/369faf695b355d1d341a09082272ef25d3ad3e7a . I don't really have the time, but try to patchelf this with some of the values in the logcat.

reujea0 said:
It is clear from the log that there is an issue with gnss(Global Navigation Satellite System). SO location won't most likely work, for the time being try to disable/remove everything related to gnss, this should let you at least boot or go further in the boot process. I will investigate further.
---------- Post added at 05:35 PM ---------- Previous post was at 05:18 PM ----------
I think we might have to patchelf https://github.com/NixOS/patchelf to replace the dependencieng, like this https://github.com/LineageOS/androi...mmit/369faf695b355d1d341a09082272ef25d3ad3e7a . I don't really have the time, but try to patchelf this with some of the values in the logcat.
Click to expand...
Click to collapse
Whoa, thanks a lot i already have an idea on how to fix gnss and i will try to patch elf when i have time (tomorrow or so)

mac12m99 said:
I've never compiled for a treble device but as i know vendor tree is useless because all needed blobs are in vendor partition, you shouldn't take things from stock system.
In fact GSI works at 100% with only vendor libraries (ok, code is patched but that's not the point).
I think we should target GSI instead, researching and giving fixes for roms that have litte issues and compiling new ones (also for the joy of others device's owners).
If you don't think so please explain why, i'm open to dialog
Click to expand...
Click to collapse
Yes, you are right, all blobs needed for a gsi are in vendor partition. Many of those blobs are however, not needed or can be compiled open source with customisations like improved battery life/performance and an open source code.
Also, to add new features which our hardware supports but xiaomi did not build into they'r software for license or other reasons, we need a completely source built kernel and an adapted rom. Additionally, a properly built and optimized rom with as much open source code as possible and improved from a ****load of developers around the world will always perform better than an overlay rom depending on features built from oem and therefore optimized for theyr stock rom.
Also, you need files from system for a proper full vendor because you need some configuration files for the rom itself to adapt to the vendor blobs. Sometimes you can also fix a gsi by copying the right file (look logcat) from stock system to the gsi system partition .

wertus33333 said:
Yes, you are right, all blobs needed for a gsi are in vendor partition. Many of those blobs are however, not needed or can be compiled open source with customisations like improved battery life/performance and an open source code.
Click to expand...
Click to collapse
Ok, i got it,
so you are trying to create a ROM that don't use vendor partition and have all needed blobs into /system?
wertus33333 said:
Also, to add new features which our hardware supports but xiaomi did not build into they'r software for license or other reasons, we need a completely source built kernel and an adapted rom. Additionally, a properly built and optimized rom with as much open source code as possible and improved from a ****load of developers around the world will always perform better than an overlay rom depending on features built from oem and therefore optimized for theyr stock rom.
Click to expand...
Click to collapse
Which features do you mean?
As i know all hardware features have to be implemented in kernel (like dt2w and fingerprint gestures) and all software features have to be implemented in ROM (like long press for flashlight, dt2s in statustbar ecc..).
Am i wrong?
wertus33333 said:
Also, you need files from system for a proper full vendor because you need some configuration files for the rom itself to adapt to the vendor blobs. Sometimes you can also fix a gsi by copying the right file (look logcat) from stock system to the gsi system partition .
Click to expand...
Click to collapse
This happens when OEM forgot to move something vendor, as i know .
EDIT: looking at your logcat i found this:
Code:
F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
This is a fatal issue and probably the cause of bootloop, copying libaudiopolicymanagerdefault.so from stock may help but i think it could be built.

mac12m99 said:
EDIT: looking at your logcat i found this:
Code:
F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
This is a fatal issue and probably the cause of bootloop, copying libaudiopolicymanagerdefault.so from stock may help but I think it could be built.
Click to expand...
Click to collapse
I saw this one as well in the logcat, I do agree that it seems like it can't find the audioserver file, which would probably cause no audio. But I do not think that it causes the bootloop, not only can most roms cope with not finding some executables, but also it is not the one coming up forever towards the end of the logcat. This is an error it does not try to fix, in the logcat, the rom is trying to start the GPS over and over, which makes it bootloop, stuck at the omni logo. We either have to kill it in the boot.rc files temporarily to boot or to find a way to fix it.

reujea0 said:
I saw this one as well in the logcat, I do agree that it seems like it can't find the audioserver file, which would probably cause no audio. But I do not think that it causes the bootloop, not only can most roms cope with not finding some executables, but also it is not the one coming up forever towards the end of the logcat. This is an error it does not try to fix, in the logcat, the rom is trying to start the GPS over and over, which makes it bootloop, stuck at the omni logo. We either have to kill it in the boot.rc files temporarily to boot or to find a way to fix it.
Click to expand...
Click to collapse
Ok i got it, i hope you succeed

log interpretation
the interpretation is need globally to fix vendor error and issue with gnss(Global Navigation Satellite System). the source is no good .
I think the solution to speak regularry in work omni rom daisy , is create group Mi a2 lite dev in Telegram app . For exemple group telegram for Redmi note 5a( my secondary device ), have many help dev and good community .
you can see error here for your logcat :
1-08 15:44:04.528 463 463 E DrmLibFs: Error: Invalid config file
01-08 15:44:04.528 463 463 E DrmLibFs: Data path not parsed: Using default data path: /data/vendor/tzstorage/
01-08 15:44:04.528 463 463 E DrmLibFs: Persist path not parsed: Using default persist path: /mnt/vendor/persist/data/
01-08 15:44:04.740 479 479 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
01-08 15:44:04.750 479 483 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare user 0 storage
01-08 15:44:05.583 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
1-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter64.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
01-08 15:44:05.703 570 570 D QSEECOMAPI: App is not loaded in QSEE
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 E SoterUtils: QSEECom_start_app failed
01-08 15:44:05.704 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IGnss/default in either framework or device manifest.
01-08 15:44:45.509 708 708 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:44:50.519 718 718 W [email protected]: Failed to register IGnss 1.1 service: 1, try IGnss 1.0
01-08 15:45:05.518 729 729 E [email protected]: Could not get passthrough implementation for [email protected]::IVr/default.
01-08 15:45:15.550 751 751 E [email protected]: Error while registering gnss vendor hal service: 1
01-08 15:45:30.536 769 769 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:45:30.542 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IVr/default in either framework or device manifest.
01-08 15:45:30.543 771 771 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-08 15:45:30.544 771 771 E VrService: hw_get_module vr failed: -2
01-08 15:47:30.685 906 906 E [email protected]: Could not get passthrough implementation for [email protected]::ILocHidlGnss/gnss_vendor.
01-08 15:47:30.685 906 906 E [email protected]: Error while registering gnss vendor hal service: 1
wertus33333 said:
I need help Building omnirom9.0 for daisy, got it to compile and boot (bootlooping bootanimation, logs can be found below) but need help in interpreting the logs.
Sources:
Kernel mi kernel with disabled verity and FEC
Devie combined msm8953-common and daisy (branch los15) from lineage build and adjusted to omni
Vendor took vendor from v10.0.1.0.PDLMIFJ, added everything to copy files, adjusted with apps and missing files from system and deleted the obsolete
OMNIROM
Logcat
Saw that some libraries are missing, will search them in vendor/system from stock and add them when i have time. If someone finds a solution for an error please copy&paste the line(s) in logcat leading to the solution, so me (and probably others) can learn from it and be of more use next time.
@ada12
@reujea0
@Hakkinan
Click to expand...
Click to collapse
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
+ I see Vendor took vendor from v10.0.1.0.PDLMIFJ , is a beta rom pie for Daisy . I recommand change to vendor from v10.0.2.0 + fix after in source the other bug

Thanks for the answer, last time i could not find the v10.0.2.0 vendor anywhere but if it is officially avaiable now i'll defenitely switch.
A telegram group would defenitely be of help and easier to communicate than here. More people reviewing/contributing to the code on github (i don't always really know what i am doing ) would also be useful (i'd be happy to add more people, just pm me if u want to).
I dont have that much time for continuing with the rom in the next 1-2 weeks but i'll defenitely continue as soon as possible.
ada12 said:
the interpretation is need globally to fix vendor error and issue with gnss(Global Navigation Satellite System). the source is no good .
I think the solution to speak regularry in work omni rom daisy , is create group Mi a2 lite dev in Telegram app . For exemple group telegram for Redmi note 5a( my secondary device ), have many help dev and good community .
you can see error here for your logcat :
1-08 15:44:04.528 463 463 E DrmLibFs: Error: Invalid config file
01-08 15:44:04.528 463 463 E DrmLibFs: Data path not parsed: Using default data path: /data/vendor/tzstorage/
01-08 15:44:04.528 463 463 E DrmLibFs: Persist path not parsed: Using default persist path: /mnt/vendor/persist/data/
01-08 15:44:04.740 479 479 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
01-08 15:44:04.750 479 483 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare user 0 storage
01-08 15:44:05.583 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
1-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter64.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
01-08 15:44:05.703 570 570 D QSEECOMAPI: App is not loaded in QSEE
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 E SoterUtils: QSEECom_start_app failed
01-08 15:44:05.704 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IGnss/default in either framework or device manifest.
01-08 15:44:45.509 708 708 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:44:50.519 718 718 W [email protected]: Failed to register IGnss 1.1 service: 1, try IGnss 1.0
01-08 15:45:05.518 729 729 E [email protected]: Could not get passthrough implementation for [email protected]::IVr/default.
01-08 15:45:15.550 751 751 E [email protected]: Error while registering gnss vendor hal service: 1
01-08 15:45:30.536 769 769 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:45:30.542 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IVr/default in either framework or device manifest.
01-08 15:45:30.543 771 771 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-08 15:45:30.544 771 771 E VrService: hw_get_module vr failed: -2
01-08 15:47:30.685 906 906 E [email protected]: Could not get passthrough implementation for [email protected]::ILocHidlGnss/gnss_vendor.
01-08 15:47:30.685 906 906 E [email protected]: Error while registering gnss vendor hal service: 1
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
+ I see Vendor took vendor from v10.0.1.0.PDLMIFJ , is a beta rom pie for Daisy . I recommand change to vendor from v10.0.2.0 + fix after in source the other bug
Click to expand...
Click to collapse

Android 10 ROM

Thanks all for testing.

These?
https://androidfilehost.com/?fid=1899786940962602774
https://github.com/svlog/device_lge_bullhead

imknown said:
These?
https://androidfilehost.com/?fid=1899786940962602774
https://github.com/svlog/device_lge_bullhead
Click to expand...
Click to collapse
Yes.
Branch for selinux enforcing is in WIP and is not pushed to github yet.

equlog said:
Yes.
Branch for selinux enforcing is in WIP and is not pushed to github yet.
Click to expand...
Click to collapse
Just post it in development with a [alpha] tag and let people decide if they want to test it.
Few will see this thread in this forum.

Hi, I find this: NexusROM-10-bullhead-1.5a-M10-20191011.zip
https://androidfilehost.com/?fid=1899786940962606653
I flashed this build and it boots.
But the GNSS/GPS location function does not work with no FC/ANR.
Logcat posted below:
--------- beginning of main
10-13 12:04:11.836 1498 1498 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
--------- beginning of system
10-13 12:03:50.006 545 545 I chatty : uid=1010(wifi) /system/bin/wificond expire 1 line
10-13 12:03:50.008 545 545 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
10-13 12:04:14.967 828 828 V SettingsProvider: Notifying for 0: content://settings/secure/location_mode
10-13 12:04:11.886 1498 1498 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
10-13 12:04:14.968 447 447 W GnssHAL_GnssInterface: setCallback called more than once. Unexpected unless test.
10-13 12:04:14.971 828 938 D GnssLocationProvider: gnssSetCapabilitesCb: 71u
10-13 12:04:14.971 447 447 E LocSvc_eng: loc_eng_init: log_eng state error: instance already initialized
10-13 12:04:14.973 447 447 E LocSvc_eng: loc_eng_agps_init: log_eng state error: agps instance already initialized
10-13 12:04:14.973 828 938 I GnssLocationProvider: Unable to initialize IGnssGeofencing interface.
10-13 12:04:14.975 828 938 I GnssLocationProvider: Unable to initialize IAGnssRil interface.
10-13 12:04:14.980 828 938 I GnssLocationProvider: restartRequests
10-13 12:04:14.980 828 828 V SettingsProvider: Notifying for 0: content://settings/secure/location_providers_allowed
10-13 12:04:19.819 1498 1498 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
10-13 12:04:19.885 1498 1498 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
10-13 12:04:22.869 1498 1498 W View : requestLayout() improperly called by com.android.systemui.statusbar.policy.NetworkTraffic{3d20962 V.ED..... ......ID 0,23-91,81} during layout: running second layout pass
10-13 12:04:30.013 545 545 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES

imknown said:
Hi, I find this: NexusROM-10-bullhead-1.5a-M10-20191011.zip
https://androidfilehost.com/?fid=1899786940962606653
I flashed this build and it boots.
But the GNSS/GPS location function does not work with no FC/ANR.
Click to expand...
Click to collapse
Thanks for the log, gps/gnss location fixed.

equlog said:
Thanks all for reports, my job is done
Click to expand...
Click to collapse
Give us a download link please.

mahyarmo said:
Give us a download link please.
Click to expand...
Click to collapse
Updated

Download link?

sinkoo1979 said:
Download link?
Click to expand...
Click to collapse
https://androidfilehost.com/?a=show&w=files&flid=216711

imknown said:
https://androidfilehost.com/?a=show&w=files&flid=216711
Click to expand...
Click to collapse
tried to flash the rom but it did not pass the flashing stage. When back to LOS15.1
Update: Flashed the newest build (October 24, 2019) and everything working.

Nice ROM, gapps?

PuTo said:
Nice ROM, gapps?
Click to expand...
Click to collapse
Join «NexusROM For Bullhead» on Telegram: https://t.me/NexusROM

equlog said:
Thanks for the log, gps/gnss location fixed.
Click to expand...
Click to collapse
@equlog, how was this fixed above?
I found my the problem for my tablet. I was missing 2 proprietary blobs being copied over to /system/lib. They are
libloc_api_v02.so
libloc_ds_api.so

No audio output since upgrading to 17.1 — while all system sounds do play all right

Playing media makes no sound in VLC, Firefox, YouTube, NewPipe, you name it.
In the meantime, all system sounds do play all right, and vocal messages too.
Device: Lenovo P2 “kuntao”
ROM: LineageOS 17.1 ♥ with Open GApps nano, installed with `adb sideload` and TWRP.
Rooted: yes
Prior to the 17.1, I was a happy user of the version 16, always up-to-date, and didn't experience any issues with sound.

Here's an essential excerpt from `adb logcat` output when launching VLC:
Code:
...
04-28 07:31:16.322 1205 5907 E audio_hw_utils: send_app_type_cfg_for_device: Couldn't get the backend index for snd device speaker ret=-14
04-28 07:31:16.328 1205 5907 E audio_hw_primary: start_output_stream: pcm_prepare returned -1
04-28 07:31:16.423 1205 5907 E audio_hw_utils: send_app_type_cfg_for_device: Couldn't get the backend index for snd device speaker ret=-14
04-28 07:31:16.430 10437 10504 W VLC : [00000077ba41e690/2908] libvlc audio output: timing screwed, reset positions
04-28 07:31:16.430 10437 10504 W VLC : [00000077ba41e690/2908] libvlc audio output: playback too late (71136): up-sampling
04-28 07:31:16.431 1205 5907 E audio_hw_primary: start_output_stream: pcm_prepare returned -1
04-28 07:31:16.524 1205 2504 E /vendor/bin/hw/[email protected]: Failed to get IAshmemDeviceService.
...

Workaround
As a workaround, all you need to do to get the speaker to work properly is to enable the “Do not disturb / Total silence” mode, and then disable it.