Develop Bugs

[Porting] CANNOT LINK EXECUTABLE < /system/bin/ file>: cannot locate symbol < ... >

[Porting] CANNOT LINK EXECUTABLE < /system/bin/ file>: cannot locate symbol < ... >
Hi.
I encountered a problem while trying to port AOSP Extended v. 4.1 (Android 7.1.2, kernel 3.10.65+, MTK 6753) on my device (VOYO Q101, 2GB/32GB, kernel 3.10.65+, MTK 6753).
After successfully started the booting process (after one week of research, and a stupid line in /system/build.prop: ro.setupwizard.enterprise_mode=1 which caused stucking at logo), I have managed to get a logcat via adb. LOG (it's 8MB)
It is booting.. and booting... forever. It is not stucked, nor bootlooping. It is just booting (the "Google dots" animations running forever).
I have attached the log. There are a lot of CANNOT LINK EXECUTABLE <....> cannot locate symbol < ... > referenced by <...> and also a lot of:
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Write 56 bytes to slot 0, CCCI_H(0x0)(0x38)(0x801D000F)(0x0)
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from FS device
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from slot 0, CCCI_H(0x0)(0x80)(0x801E000E)(0x0)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): CMPT File name:Z:/NVRAM/NVD_DATA/ULMH_000 opid_map:0x00000013 Flag:0x00000100 Offset:34 Whence:-229154332 Length:16384
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): O: [1010103F282D2C35](0x00000100): (7 1)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): F: 1: 1906 0
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): C: 1: 0
[What I did]
- just copying the kernel from stock ROM (tried also: stock kernel + stock ueventd.rc +/- stock fstab): all caused bootloop or even stucked at logo. Just kernel change works good (at least till the actual stage) .
- compared with old .rc files. No replaces needed (in my opinion)
- From system/build.prop file I have DELETED all lines from ADDITIONAL_BUILD_PROPERTIES section (especially ro.setupwizard.enterprise_mode=1) - which took me 4 DAYS !!! to understand why it was stucked at logo .
- tried with and without patching with init.d (from porting ROM's website)
- tried to put the stock binaries mentioned in errors <CANNOT LINK ...> (/system/bin/mtk_agpsd, xlog) - not booting at all (it even stucks at logo...). Should I try with stock linker.so lib(64) ? But I think it will not boot at all (It really can't).
I hope for your help . Thanks!

up

[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

[ROM][11.0][UNOFFICIAL][Testing] LineageOS 18.1 for Wileyfox Swift

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Remarks:
This thread is thought to collect issues and ideas. It has to be considered being a TESTING version.
Once everything is mature, an official build may be possible.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Also make sure you've got the correct firmware installed before installing LineageOS.
More detailed instructions at:
Install LineageOS on crackling
115ek's test builds (for testers only)
Downloads
Recommended Google Apps package:
none: GApps don't fit at the moment. A repartitioning is needed. Currently thinking about this...
Donate to support development:
Donate via PayPal to LineageOS

Changelog
06.12.2021
updated lineage sources
11.09.2021
fixed livedisplay
updated lineage sources
22.07.2021
initial version

reserved

It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.

petexd said:
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
Click to expand...
Click to collapse
Livedisplay is not working at the moment.

I had to remove it because it wouldn't load my photos and I didn't have time to play around with it. It's actually my only phone. It did, however, instal basic flamegapps.
I also got error 255 when tryin to restore my backup but I'm up and running now with 17.1. I'll try 18.1 again soon when I have more time to mess around with it and if I can sort out error 255

Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.

ajjin0 said:
Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.
Click to expand...
Click to collapse
I've got so less time at the moment. I hope I'll find some to continue the work.

New build is up. Livedisplay is working now.
Download

Wow great work.

@115ek Thank you for the new build.
I tried to compile Lineage18.1 myself, but ended up in a boot loop. I assume this is the relevant part of the log, since it repeats over and over again:
Spoiler
Code:
01-01 21:28:58.399 4357 4357 I [email protected]: LiveDisplay HAL service is starting.
01-01 21:28:58.404 4357 4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.458 4357 4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.458 4357 4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.510 4357 4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.512 220 220 I hwservicemanager: getTransport: Cannot find entry [email protected]::IDisplayModes/default in either framework or device manifest.
01-01 21:28:58.512 4357 4357 E HidlServiceManagement: Service [email protected]::IDisplayModes/default must be in VINTF manifest in order to register/get.
01-01 21:28:58.513 4357 4357 E [email protected]: Could not register service for LiveDisplay HAL DisplayModes Iface (-2147483648)
01-01 21:28:58.514 4357 4357 E [email protected]: LiveDisplay HAL service is shutting down.
01-01 21:28:58.521 0 0 I init : Service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) exited with status 1
01-01 21:28:58.521 0 0 I init : Sending signal 9 to service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) process group...
01-01 21:28:58.521 0 0 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 4357 in 0ms
01-01 21:28:59.391 219 219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:28:59.391 4193 4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
01-01 21:28:59.393 219 4360 W libc : Unable to set property "ctl.interface_start" to "aidl/android.hardware.power.IPower/default": error code: 0x20
01-01 21:28:59.395 0 0 E init : Control message: Could not find 'aidl/android.hardware.power.IPower/default' for ctl.interface_start from pid: 219 (/system/bin/servicemanager)
01-01 21:29:00.392 219 219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:29:00.392 4193 4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
My local manifest looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="115ek/android_device_wileyfox_crackling" path="device/wileyfox/crackling" remote="github" />
<project name="115ek/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" />
<project name="115ek/proprietary_vendor_wileyfox" path="vendor/wileyfox" remote="github" />
<project name="LineageOS/android_kernel_cyanogen_msm8916" path="kernel/cyanogen/msm8916" revision="lineage-17.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" />
</manifest>
Does your manifest look the same? Are there any additional patches I have to apply to get it working? I would highly appreciate it if you could share your steps to build LineageOS 18.1.

mmustermann717 said:
Does your manifest look the same?
Click to expand...
Click to collapse
This should be fine, yes.
mmustermann717 said:
Are there any additional patches I have to apply to get it working?
Click to expand...
Click to collapse
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.

115ek said:
This should be fine, yes.
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Click to expand...
Click to collapse
Thank you very much! That worked.

I increased the system partition, a little while ago and backups were restoring OK so I've decided to try 18.1 again.
I must say, it performs really well for the stuff I need. I also like that I can now do calendar etc backups to my sdcard. Much more sensible IMO.
Thanks 115ek. A great job.
I'd like to have a go at building but I'm not sure where to start without the explicit menu like 17.1

Thanks to 115ek for the 18.1 set up and to mmustermann717 for his local manifest. I have managed to build 18.1 after a few errors which appeared to be out of memory problems.
I fixed that and was able to complete the build.
Thanks both of you
I was too quick to brag. Im getting a boot loop. I made the changes from 115ek's response #12, so I don't know where I've gone wrong.
Can either of you tell me please?

115ek said:
This should be fine, yes.
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Click to expand...
Click to collapse
I've tried all of this several times. I get a successful build but a boot loop every time.
The lineage source says successful, it doesn't actually boot so I have no idea how to find any error? Is there anything I can look for? Or can you guess?
I'd appreciate the help if you can. Thanks.

Hey
petexd said:
how to find any error?
Click to expand...
Click to collapse
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
petexd said:
Or can you guess?
Click to expand...
Click to collapse
You could, but I'm not sure if that really helps.
petexd said:
Is there anything I can look for?
Click to expand...
Click to collapse
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.

115ek said:
Hey
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
This is the line you asked about:
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.selinux=permissive
I've tried my build with your boot.img but it still bootloops.

115ek said:
Hey
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
I've tried again and the last 4 lines of the build are:
2021-10-18 16:11:33 - ota_from_target_files.py - INFO : done.
Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>.
Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>.
Compressing system.new.dat with brotli
warning radio-update: no radio image in input target_files; not flashing radio
[100% 24/24] build bacon
Package Complete: out/target/product/crackling/lineage-18.1-20211018-UNOFFICIAL-crackling.zip
#### build completed successfully
Is this OK? I thought bacon was another phone (oneplus?)

Hey
115ek said:
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
I get this , just bfore the build completes successfully. Do you know if this has anything to do with the problem.
99% 463/464] Package OTA: out/target/product/crackling/lineage_crackling-ota-eng.pet
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/build.prop

[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1

Central project page
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [Alpha]
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :) Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you! Official site...
forum.xda-developers.com

09.02.2022
android-12.0.0_r28 (February security patchlevel)
OEMv1c support
Click to expand...
Click to collapse

14.02.2022
hotfix for the bootloop
Click to expand...
Click to collapse

30.03.2022
android-12.1.0_r1 (March security patchlevel)
Click to expand...
Click to collapse

MartinX3 said:
30.03.2022
Click to expand...
Click to collapse
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1

Carljaynp03 said:
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Click to expand...
Click to collapse
It's 90% aosp.
Please report any bug in the linked issue tracker.

MartinX3 said:
It's 90% aosp.
Please report any bug in the linked issue tracker.
Click to expand...
Click to collapse
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please

Carljaynp03 said:
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Click to expand...
Click to collapse
Thank you, please follow the link in the first post.
There it is also in the first post.

12.04.2022
android-12.1.0_r3 (April security patchlevel)
Click to expand...
Click to collapse

Bug....the touch does not work and it seems to reboot intermittently

Mint rhfo said:
Bug....the touch does not work and it seems to reboot intermittently
Click to expand...
Click to collapse
Bug....report?

MartinX3 said:
Bug....report?
Click to expand...
Click to collapse
Yeah! It's Bug report!

Mint rhfo said:
Yeah! It's Bug report!
Click to expand...
Click to collapse
I don't see a valid bug report according to the instructions.
Or you claim that I'm god and know everything.
But maybe I'm god, who knows.

Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!

BigWoodFarmer said:
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
Click to expand...
Click to collapse
Hey,
I'm sorry and fixed the type.
There was a wrong whitespace character in the manual.
It's `oem_a`, that's correct.
Did you flash everything and wiped the userdata before?
Because other XZ2C owners were able to post logs.
Also it is mandatory to run the latest stock firmware on both slots once before in the lifetime of your phone.

Hi,
Thank you for your fast reply. I flashed everything and wiped as described with "fastboot -w"
I am unsure what you mean by both slots, you mean Firmware and Software Content Erase? I used EMMA to flash: H8324 52.1.A.0.618 Customized_UK 1313-5469 R3C User-Live COM on the device.
Some other questions I had:
a) Do I need Magisk for root on the device?
b) can I use another Version the twrp 3.4.0.0.? If I install this to my recovery partition, I can't use it when booting since the screen seems frozen.

sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all

BigWoodFarmer said:
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
Click to expand...
Click to collapse
Nice that you achieve to flash it.
The camera is currently not implemented because of the russian invasion in the ukraine.
Code:
04-12 19:02:48.363 0 0 I init : starting service 'vendor.camera-provider-2-4'...
04-12 19:02:48.451 3114 3114 I [email protected]: [email protected] legacy service is starting.
04-12 19:02:48.452 3114 3114 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.453 3114 3114 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.452 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc44 returned -22
04-12 19:02:48.453 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc24 returned -22
04-12 19:02:48.489 3114 3114 E [email protected]: Could not load camera HAL module: -2 (No such file or directory)
04-12 19:02:48.489 3114 3114 E [email protected]_64: getProviderImpl: camera provider init failed!
04-12 19:02:48.490 3114 3114 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xb400007a624ceaa0)
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::getCurrentInternal not linked, returning null
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::logStackInternal not linked
04-12 19:02:48.492 3114 3114 E HidlServiceManagement: Could not find instance 'legacy/0' in library [email protected] Keeping library open.
04-12 19:02:48.493 3114 3114 E LegacySupport: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
04-12 19:02:48.501 0 0 I init : Service 'vendor.camera-provider-2-4' (pid 3114) exited with status 1
04-12 19:02:48.501 0 0 I init : Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 3114) process group...
04-12 19:02:48.501 0 0 I libprocessgroup: Successfully killed process cgroup uid 1047 pid 3114 in 0ms
04-12 19:02:48.504 0 0 E init : process with updatable components 'vendor.camera-provider-2-4' exited 4 times in 4 minutes
04-12 19:02:48.513 0 0 I init : processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)
04-12 19:02:48.514 0 0 I init : starting service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...
04-12 19:02:48.541 0 0 I init : SVC_EXEC service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)' pid 3115 (uid 1000 gid 1000+0 context default) started; waiting...
04-12 19:02:48.564 3115 3115 I flags_health_check: ServerConfigurableFlagsReset reset_mode value: 1
04-12 19:02:48.565 3115 3115 I flags_health_check: ServerConfigurableFlagsReset updatable crashing detected, resetting flags.
Please subscribe to
[Tama][XZ2C][AOSP12][4.19] Apollo camera provider init failed (every 5secs) · Issue #751 · sonyxperiadev/bug_tracker
Platform: Tama Device: XZ2C (apollo) Kernel version: 4.19.188-ge73c1a837c4f-dirty Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a (latest official Sony...
github.com
[Tama][4.19][AOSP12] Device reboots for no clear reason any time it is not idle · Issue #755 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a Description The device reboots after a few minutes o...
github.com
[TAMA][12][4.19] Bootloop · Issue #748 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: 12 Software binaries version: v1c Previously working on Stock Description Bootloop and no ADB logs available. The device was flas...
github.com
and firstly this will get fixed: https://github.com/sonyxperiadev/bug_tracker/issues/770

20.05.2022
android-12.1.0_r5 (May security patchlevel)
Click to expand...
Click to collapse
Because of problems with the ftp server the new release is on google drive.
Click to expand...
Click to collapse

Hello, what changes between this rom and the stock based roms ?

Is there any Lineage OS for Lenovo Tab 11 Pro ? [TB-J716F]

Hello,
I was wondering if there is a Lineage OS distribution for Lenovo Tab 11 Pro with the reference TB-J716F. If not, is it possible for me to build one? I'm a noob in custom ROMs, but I'm willing to learn

LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too

Ungeskriptet said:
LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too
Click to expand...
Click to collapse
Thanks, I'll check all of that once I managed to get my tab working.........

Ungeskriptet said:
LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too
Click to expand...
Click to collapse
I managed to install LineageOS. But I cannot install twrp using your image.
These are my logs:
Code:
01-01 08:33:29.842 0 0 I init : starting service 'recovery'...
01-01 08:33:29.847 756 756 F linker : CANNOT LINK EXECUTABLE "/system/bin/vendor.qti.hardware.vibrator.service": library "android.hardware.vibrator-V1-ndk_platform.so" not found: needed by main executable
01-01 08:33:29.847 0 0 I init : Service 'vendor.qti.vibrator' (pid 756) exited with status 1
01-01 08:33:29.847 0 0 I init : Sending signal 9 to service 'vendor.qti.vibrator' (pid 756) process group...
01-01 08:33:29.847 0 0 I libprocessgroup: Successfully killed process cgroup uid 0 pid 756 in 0ms
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.boot" to "1": error code: 0xb
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.version" to "3.6.1_11-0": error code: 0xb
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.boot' from uid:0 gid:0 pid:755: Read-only property was already set
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.version' from uid:0 gid:0 pid:755: Read-only property was already setunsupported, phys idx 0
01-01 08:33:29.900 755 755 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10 in tid 755 (recovery), pid 755 (recovery)
01-01 08:33:29.902 758 758 F libc : failed to exec crash_dump helper: No such file or directory
01-01 08:33:29.903 755 755 F libc : crash_dump helper failed to exec
01-01 08:33:29.908 0 0 I init : Service 'recovery' (pid 755) received signal 11

redblood252 said:
I managed to install LineageOS. But I cannot install twrp using your image.
These are my logs:
Code:
01-01 08:33:29.842 0 0 I init : starting service 'recovery'...
01-01 08:33:29.847 756 756 F linker : CANNOT LINK EXECUTABLE "/system/bin/vendor.qti.hardware.vibrator.service": library "android.hardware.vibrator-V1-ndk_platform.so" not found: needed by main executable
01-01 08:33:29.847 0 0 I init : Service 'vendor.qti.vibrator' (pid 756) exited with status 1
01-01 08:33:29.847 0 0 I init : Sending signal 9 to service 'vendor.qti.vibrator' (pid 756) process group...
01-01 08:33:29.847 0 0 I libprocessgroup: Successfully killed process cgroup uid 0 pid 756 in 0ms
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.boot" to "1": error code: 0xb
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.version" to "3.6.1_11-0": error code: 0xb
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.boot' from uid:0 gid:0 pid:755: Read-only property was already set
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.version' from uid:0 gid:0 pid:755: Read-only property was already setunsupported, phys idx 0
01-01 08:33:29.900 755 755 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10 in tid 755 (recovery), pid 755 (recovery)
01-01 08:33:29.902 758 758 F libc : failed to exec crash_dump helper: No such file or directory
01-01 08:33:29.903 755 755 F libc : crash_dump helper failed to exec
01-01 08:33:29.908 0 0 I init : Service 'recovery' (pid 755) received signal 11
Click to expand...
Click to collapse
You shouldn't need TWRP.

mikefnz said:
You shouldn't need TWRP.
Click to expand...
Click to collapse
Why not? All I have is stock rom recovery....

redblood252 said:
Why not? All I have is stock rom recovery....
Click to expand...
Click to collapse
Just need adb & fastboot
For example:
Download vbmeta.img from google
Reboot to fastboot
Open an cmd:
fastboot flash vbmeta vbmeta.img
fastboot reboot fastboot
fastboot flash system XYZ.img
fastboot reboot recovery
Make an factory reset
Reboot