[ROM][11][UNOFFICIAL] AICP 16.1 UNNOFICIAL FOR MOTO ONE (DEEN) - Motorola One ROMs, Kernels, Recoveries, & Other De

[ROM][11][UNOFFICIAL] AICP 16.1 UNNOFICIAL FOR MOTO ONE (DEEN) - Motorola One ROMs, Kernels, Recoveries, & Other De

{
"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 (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android 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.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/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:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://sourceforge.net/projects/moto-one-deen/files/AICP-11/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
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 for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP is recommended, the lineage recovery is a great alternative however, it will not decrypt the internal storage so you will have to flash the rom with adb sideload or usb OTG or with an external sdcard).
3. Wipe the System (DO NOT WIPE THE SYSTEM ON A/B DEVICES!), Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file (reboot to recovery before flashing anything else if you have an "A/B" device).
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device.
7. You can then reboot to recovery and flash the root solution of your choice if you want to, and then boot back to the system.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on A/B Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/jro1979oliver/kernel_motorola_deenDevice tree source:
GitHub - jro1979oliver/device_motorola_deen
Contribute to jro1979oliver/device_motorola_deen development by creating an account on GitHub.
github.com
Vendor source:
GitHub - jro1979oliver/aicp_vendor_motorola
Contribute to jro1979oliver/aicp_vendor_motorola development by creating an account on GitHub.
github.com
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on GitHub
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
Information:
ROM OS Version: 11.x
Kernel: 3.18.140
ROM Last stock Rom required:
Status: STABLE
Release Date: 05-31-2022
You want to see a "normal" night at the "DEV office", click here!!

Q&A:
1: It's stable?
Yes, it's currently running with selinux enforcing and no major bugs
2: Can I use encryption?
Yes, it's not enforced by default because twrp still can't decrypt, but if you prefer you can do it via settings
3: From where I can find a twrp for first install?
From here. NOTICE: Aicp also ships it's own recovery and it is functional. Besides extreme stable, deen kernel still has a bug where when you are on slot a, recovery can't switch to slot b by it's own, so you need to use fastboot --set-active=b with latest adb tools from google (Download).
From b to a, you can just reboot system. At first install, I recommend a format data to fix selinux contexts that twrp may bork and avoid storage issues

AICP 16.1 (android 11)
Moto One deen
Changelog:
June security patch
Signed build;
Enabled verity checks; added the hability to lock bootloader (do it at your own risk -
fastboot flashing lock and fastboot flashing unlock (this kill your data as stock does));
Added Dolby (settings/sound/dolby atmos);
Working usb internet tethering,
Selinux enforcing;
Reworked paddings;
Enabled proccess reclaim;
Gesture navigation as default;
Enabled LiveDisplay (again)
Bugs:
*
Currently, recovery can't change slot from a to b;
You tell me
May be few more changes idk
https://sourceforge.net/projects/moto-one-deen/files/AICP-11/aicp_deen-16.1_signed.zip/download

I've been away from the xda community for a while and got a Motorola One XT-1941-3 (retail from Brazil).
Is this AICP the most stable custom rom available?
Thanks!

jeferson1979 said:
AICP 16.1 (android 11)
Moto One deen
Changelog:
June security patch
Signed build;
Enabled verity checks; added the hability to lock bootloader (do it at your own risk -
fastboot flashing lock and fastboot flashing unlock (this kill your data as stock does));
Added Dolby (settings/sound/dolby atmos);
Working usb internet tethering,
Selinux enforcing;
Reworked paddings;
Enabled proccess reclaim;
Gesture navigation as default;
Enabled LiveDisplay (again)
Bugs:
*
Currently, recovery can't change slot from a to b;
You tell me
May be few more changes idk
https://sourceforge.net/projects/moto-one-deen/files/AICP-11/aicp_deen-16.1_signed.zip/download
Click to expand...
Click to collapse
Bro have Deen too?

zahidm said:
Bro have Deen too?
Click to expand...
Click to collapse
Yeah, more one moto

jeferson1979 said:
Q&A:
1: It's stable?
Yes, it's currently running with selinux enforcing and no major bugs
...
Click to expand...
Click to collapse
This is a very nice rom and gives more life to my moto one.
However, I'm trying to build it locally and having some issues with the manifest.
Do you mind sharing your manifest for the rom?
Thank you.

I'm trying to rebuild your rom locally with your repositories. Maybe I don't use the correct manifest, and I'm getting selinux policy violation.
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=11
AICP_VERSION=aicp_deen_r-16.1-UNOFFICIAL-20220728
TARGET_PRODUCT=aicp_deen
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.15.39-1-pve-x86_64-Ubuntu-20.04.4-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
KERNEL_TOOLCHAIN=gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin
HOST_BUILD_TYPE=release
BUILD_ID=RQ3A.211001.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/motorola/deen device/motorola/deen hardware/qcom-caf/msm8996 vendor/qcom/opensource/data-ipa-cfg-mgr vendor/qcom/opensource/dataservices packages/apps/Bluetooth
============================================
wildcard(out/target/product/deen/clean_steps.mk) was changed, regenerating...
$(shell date +%H%M%S) was changed, regenerating...
[100% 26280/26280] writing build rules ...
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/hw/audio.primary.msm8953.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/hw/audio.primary.msm8953.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/libsensorndkbridge.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/libsensorndkbridge.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/libtinycompress.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/libtinycompress.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib64/libsensorndkbridge.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib64/libsensorndkbridge.so'
[ 60% 26285/43481] build out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests
FAILED: out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests
/bin/bash -c "(out/host/linux-x86/bin/sepolicy_tests -l out/host/linux-x86/lib64/libsepolwrap.so -f out/target/product/deen/system/etc/selinux/plat_file_contexts -f out/target/product/deen/vendor/etc/selinux/vendor_file_contexts -f out/target/product/deen/system/system_ext/etc/selinux/system_ext_file_contexts -f out/target/product/deen/system/product/etc/selinux/product_file_contexts -p out/target/product/deen/obj/ETC/sepolicy_intermediates/sepolicy ) && (touch out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests )"
The following types on /system/ must be associated with the "system_file_type" attribute: clean_scratch_files_exec
12:07:01 ninja failed with: exit status 1
#### failed to build some targets (01:56 (mm:ss)) ####
My local manifest is as follows:
Code:
<manifest>
<remote name="kernel" fetch="https://github.com" revision="r11.1" />
<remote name="device" fetch="https://github.com" revision="r11.1" />
<remote name="vendor" fetch="https://github.com" revision="r11.1" />
<remote name="github_fetch" fetch="https://github.com/" revision="lineage-18.1" />
<project name="jro1979oliver/kernel_motorola_deen.git" path="kernel/motorola/deen" remote="kernel" />
<project name="jro1979oliver/device_motorola_deen.git" path="device/motorola/deen" remote="device" />
<project name="jro1979oliver/aicp_vendor_motorola.git" path="vendor/motorola" remote="vendor" />
<project path="external/bson" name="LineageOS/android_external_bson" remote="github_fetch" revision="lineage-18.1" />
<project path="hardware/motorola" name="LineageOS/android_hardware_motorola" remote="github_fetch" revision="lineage-18.1" />
<project path="system/qcom" name="LineageOS/android_system_qcom" remote="github_fetch" revision="lineage-18.1" />
</manifest>
Could you point me in the right direction? Is the manifest good or am I missing something?
Your help will be much appreciated.
Thanks.

xdadevc said:
I'm trying to rebuild your rom locally with your repositories. Maybe I don't use the correct manifest, and I'm getting selinux policy violation.
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=11
AICP_VERSION=aicp_deen_r-16.1-UNOFFICIAL-20220728
TARGET_PRODUCT=aicp_deen
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.15.39-1-pve-x86_64-Ubuntu-20.04.4-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
KERNEL_TOOLCHAIN=gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin
HOST_BUILD_TYPE=release
BUILD_ID=RQ3A.211001.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/motorola/deen device/motorola/deen hardware/qcom-caf/msm8996 vendor/qcom/opensource/data-ipa-cfg-mgr vendor/qcom/opensource/dataservices packages/apps/Bluetooth
============================================
wildcard(out/target/product/deen/clean_steps.mk) was changed, regenerating...
$(shell date +%H%M%S) was changed, regenerating...
[100% 26280/26280] writing build rules ...
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/hw/audio.primary.msm8953.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/hw/audio.primary.msm8953.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/libsensorndkbridge.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/libsensorndkbridge.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/libtinycompress.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/libtinycompress.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib64/libsensorndkbridge.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib64/libsensorndkbridge.so'
[ 60% 26285/43481] build out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests
FAILED: out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests
/bin/bash -c "(out/host/linux-x86/bin/sepolicy_tests -l out/host/linux-x86/lib64/libsepolwrap.so -f out/target/product/deen/system/etc/selinux/plat_file_contexts -f out/target/product/deen/vendor/etc/selinux/vendor_file_contexts -f out/target/product/deen/system/system_ext/etc/selinux/system_ext_file_contexts -f out/target/product/deen/system/product/etc/selinux/product_file_contexts -p out/target/product/deen/obj/ETC/sepolicy_intermediates/sepolicy ) && (touch out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests )"
The following types on /system/ must be associated with the "system_file_type" attribute: clean_scratch_files_exec
12:07:01 ninja failed with: exit status 1
#### failed to build some targets (01:56 (mm:ss)) ####
My local manifest is as follows:
Code:
<manifest>
<remote name="kernel" fetch="https://github.com" revision="r11.1" />
<remote name="device" fetch="https://github.com" revision="r11.1" />
<remote name="vendor" fetch="https://github.com" revision="r11.1" />
<remote name="github_fetch" fetch="https://github.com/" revision="lineage-18.1" />
<project name="jro1979oliver/kernel_motorola_deen.git" path="kernel/motorola/deen" remote="kernel" />
<project name="jro1979oliver/device_motorola_deen.git" path="device/motorola/deen" remote="device" />
<project name="jro1979oliver/aicp_vendor_motorola.git" path="vendor/motorola" remote="vendor" />
<project path="external/bson" name="LineageOS/android_external_bson" remote="github_fetch" revision="lineage-18.1" />
<project path="hardware/motorola" name="LineageOS/android_hardware_motorola" remote="github_fetch" revision="lineage-18.1" />
<project path="system/qcom" name="LineageOS/android_system_qcom" remote="github_fetch" revision="lineage-18.1" />
</manifest>
Could you point me in the right direction? Is the manifest good or am I missing something?
Your help will be much appreciated.
Thanks.
Click to expand...
Click to collapse
Just revert this commit. Also, use this repo for hardware/motorola

I made some progress (thanks). There seems to be another selinux issue:
Code:
[ 4% 400/9625] build out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0
FAILED: out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0
/bin/bash -c "(out/host/linux-x86/bin/treble_sepolicy_tests -l out/host/linux-x86/lib64/libsepolwrap.so -f out/target/product/deen/system/etc/selinux/plat_file_contexts -f out/target/product/deen/vendor/etc/selinux/vendor_file_contexts -f out/target/product/deen/system/system_ext/etc/selinux/system_ext_file_contexts -f out/target/product/deen/system/product/etc/selinux/product_file_contexts -b out/target/product/deen/obj/ETC/built_plat_sepolicy_intermediates/built_plat_sepolicy -m out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/26.0_mapping.combined.cil -o out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/built_26.0_plat_sepolicy -p out/target/product/deen/obj/ETC/sepolicy_intermediates/sepolicy -u out/target/product/deen/obj/ETC/built_plat_sepolicy_intermediates/base_plat_pub_policy.cil ) && (touch out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0 )"
SELinux: The following domains violate the Treble ban against use of the binder_in_vendor_violators attribute: mm-qcamerad
14:04:29 ninja failed with: exit status 1
Looking at the sepolicy/vendor/mm-qcamerad.te file I see:
Code:
# TODO(b/36599434): Remove this once mm-qcamerad stops using Binder services
typeattribute mm-qcamerad binder_in_vendor_violators;
allow mm-qcamerad binder_device:chr_file { read write };
What would be the proper fix here? (sorry if I bother you, I understand I'm way out of my league).

xdadevc said:
I made some progress (thanks). There seems to be another selinux issue:
Code:
[ 4% 400/9625] build out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0
FAILED: out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0
/bin/bash -c "(out/host/linux-x86/bin/treble_sepolicy_tests -l out/host/linux-x86/lib64/libsepolwrap.so -f out/target/product/deen/system/etc/selinux/plat_file_contexts -f out/target/product/deen/vendor/etc/selinux/vendor_file_contexts -f out/target/product/deen/system/system_ext/etc/selinux/system_ext_file_contexts -f out/target/product/deen/system/product/etc/selinux/product_file_contexts -b out/target/product/deen/obj/ETC/built_plat_sepolicy_intermediates/built_plat_sepolicy -m out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/26.0_mapping.combined.cil -o out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/built_26.0_plat_sepolicy -p out/target/product/deen/obj/ETC/sepolicy_intermediates/sepolicy -u out/target/product/deen/obj/ETC/built_plat_sepolicy_intermediates/base_plat_pub_policy.cil ) && (touch out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0 )"
SELinux: The following domains violate the Treble ban against use of the binder_in_vendor_violators attribute: mm-qcamerad
14:04:29 ninja failed with: exit status 1
Looking at the sepolicy/vendor/mm-qcamerad.te file I see:
Code:
# TODO(b/36599434): Remove this once mm-qcamerad stops using Binder services
typeattribute mm-qcamerad binder_in_vendor_violators;
allow mm-qcamerad binder_device:chr_file { read write };
What would be the proper fix here? (sorry if I bother you, I understand I'm way out of my league).
Click to expand...
Click to collapse
Remove typeattribute mm-qcamerad binder_in_vendor_violators;

jeferson1979 said:
Remove typeattribute mm-qcamerad binder_in_vendor_violators;
Click to expand...
Click to collapse
This fixed the compile problem. Thank you so much. I've been struggling with compiling an updated aicp for deen for two whole days.
I had a few other issues with a modified api, hence my delay, but I was able to compile, and flash the moto one. It seems to work. No boot loops
I ended up with a few gapps installed in the system (youtube, photos, maps) but there was no google services. This is weird. Why did those apps get included in the first place and how do I remove them?

xdadevc said:
This fixed the compile problem. Thank you so much. I've been struggling with compiling an updated aicp for deen for two whole days.
I had a few other issues with a modified api, hence my delay, but I was able to compile, and flash the moto one. It seems to work. No boot loops
I ended up with a few gapps installed in the system (youtube, photos, maps) but there was no google services. This is weird. Why did those apps get included in the first place and how do I remove them?
Click to expand...
Click to collapse
You may want to use my TWRP with oem wipe option built in, this gapps are coming from stock installation

jeferson1979 said:
You may want to use my TWRP with oem wipe option built in, this gapps are coming from stock installation
Click to expand...
Click to collapse
Formatting the oem partition made them disappear. Most/all things seem to work, including all the hardware. I'm going trough your github commit history. You did quite a bit of work there over the last few months. Impressive. Thank you again !

I see on aicp page that there is latest version 17.1. I think this is android 12 aicp_deen_s-17.1-WEEKLY-20220713.zip
https://sourceforge.net/projects/moto-one-deen/files/latest/download
Someone have tested this version on our moto?

Ok,
jeferson1979 said:
You may want to use my TWRP with oem wipe option built in, this gapps are coming from stock installation
Click to expand...
Click to collapse
I was trying to sign my build and I made something stupid and hard-bricked my xt1941-3 deen.
I have fastboot. fastboot devices shows something but there is no partition table. No A/B slots and no imei/baseband or any other thing. The serial number changed as well. It's still seend as a "deen" product with variant 000000000000000
In linux the phone is recognized as
Bus 001 Device 055: ID 22b8:2e80 Motorola PCS Fastboot deen S
Blankflash will not work in either linux or windows. It waits for the device (I quess the qualcomm flashing device) which is not there.
Is there a way out?
PS: What I did was I flashed the A slot with my boot/system/vendor.img. Then erased the B slot partitions, then booted into TWRP, activated the B slot and flashed the signed ota update, thinking that it would go to the A slot. In the middle of the flash, my phone rebooted and I got a faled boot, no gpt.bin etc.

xdadevc said:
Is there a way out?
Click to expand...
Click to collapse
So, I managed to get my bootloader back. The issue with a partial bootloader was that it was not accepting the blankflash command. No QCOM serial inteface etc.
I found out that "fastboot oem blankflash" will put the bootloader into blankflash mode, and pull up the serial interface. However there's a timing issue. blankflash must start almost immediately after going into this mode. To same me the hassle I made a small script:
Code:
#!/bin/bash
fastboot oem blankflash
for i in `seq 1 1000` ; do
./qboot blank-flash --debug=4 $*
done
Now this is sub-optimal, but worked first time for me. Just power on the phone, wait for the bootloader to come up, then start the script. It will require a ctrl-c after the phone reboots into fastboot again, this time with a proper partition table, imei, gpt etc all working.
Back to business. I'm trying to sign AICP with my own keys, then enable AVB verifier and relock the bootloader. Perhaps blankflash can be used to actually flash my own boot in place of the motorola one?
For now I'm trying to understand how to exactly sign the image with my keys. Then how to enable AVB.
PS: The "blankflash" command from fastboot oem disappeared as soon as I had a working gpt. I guess it's a failsafe. Trying to put it again into blankflash mode resulted in an error. YMMV

Hi, it's been a long weekend here. I'm up and running now. ROM compiles and works nicely. I have one residual issue when updating from a build generated by me. The recovery accepts it (keys verify) but fails at the last stage (3/3) after updating some of the partitions. After this the moto will not boot any more and requires a full image file upload. Not sure why this is and if it's only on my own phone.
But overall, things look nice. Great job @jeferson1979 and for the help in setting this up.

There's an issue with TWRP 3.6.9. I tried to use it to make a nandroid backup of a running AICP (test keys) and I skipped the data partition. The backup seemed properly done (no errors).
However, rebooting the phone never gets past the initial bootloader screen. This is only after making a backup, no restore.
I tried restoring the boot image, then system and it failed with an error. Second thing I tried was flashing my current build of AICP (different keys that original). Booting works, but decoding the data (which is encrypted) resulted in an error. The message says "password is correct, but the data is corrupt and cannot be decoded". This is weird because it says the same even with a totally bogus password.
So, seems that booting in TWRP will damage the data partition. Is this due to the different selinux context? Any other suggestion for making a nandroid backup? Recompile TWRP for Moto Deen ?
I'm be willing to help/compile/work on this. Let me know where to dig
I'm trying to get my moto up to standard of being a daily driver and reliable enough to be safe with the data in it.
I think there's a lot of life left in it.
Let me know. Thank you.

xdadevc said:
There's an issue with TWRP 3.6.9. I tried to use it to make a nandroid backup of a running AICP (test keys) and I skipped the data partition. The backup seemed properly done (no errors).
However, rebooting the phone never gets past the initial bootloader screen. This is only after making a backup, no restore.
I tried restoring the boot image, then system and it failed with an error. Second thing I tried was flashing my current build of AICP (different keys that original). Booting works, but decoding the data (which is encrypted) resulted in an error. The message says "password is correct, but the data is corrupt and cannot be decoded". This is weird because it says the same even with a totally bogus password.
So, seems that booting in TWRP will damage the data partition. Is this due to the different selinux context? Any other suggestion for making a nandroid backup? Recompile TWRP for Moto Deen ?
I'm be willing to help/compile/work on this. Let me know where to dig
I'm trying to get my moto up to standard of being a daily driver and reliable enough to be safe with the data in it.
I think there's a lot of life left in it.
Let me know. Thank you.
Click to expand...
Click to collapse
It's a know issue of TWRP last years, also, encryption doesn't work either. And you're right, TWRP makes selinux contexts goes nuts

Related

[DEVONLY] LineageOS 16

This is the development thread for Lineage 16.
Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches!
Device Trees
https://github.com/cryptomilk/android_kernel_sony_msm8998
https://github.com/cryptomilk/android_device_sony_common-treble
https://github.com/cryptomilk/android_device_sony_yoshino
https://github.com/cryptomilk/android_device_sony_lilac

I've started to get TWRP building.

I've finally successfully started TWRP based on Android 9.0. However the data partition doesn't get upgraded. So I'm trying to figure out what is failing there now ...

I think I got a working TWRP recovery. First step towards Pie done. I think @derf elot has the Kernel update almost ready. We are just waiting for Customized DE update to Android Pie to start building a new Lineage 16.

modpunk said:
I think I got a working TWRP recovery. First step towards Pie done. I think @derf elot has the Kernel update almost ready. We are just waiting for Customized DE update to Android Pie to start building a new Lineage 16.
Click to expand...
Click to collapse
Thank you very much, I just want to ask if there will gcam HDR+ support in this version?

modpunk said:
I think I got a working TWRP recovery. First step towards Pie done. I think @derf elot has the Kernel update almost ready. We are just waiting for Customized DE update to Android Pie to start building a new Lineage 16.
Click to expand...
Click to collapse
The new 47.2.A.0.306 stock kernel is merged into an up-to-date LA.UM.7.4.r1 kernel following both CAF and Linux updates (thank again @nathanchance ). Sony is also using LA.UM.7.4.r1 as a base now, so the switch made sense (we/Sony used LA.UM.6.4.r1 before). But we will always be updated to upstream, as is the case for 15.1 already, sometimes even months before some patches for security issues make it on to the ASB.
So far, the kernel builds fine. Will now test it on stock, then "LOS'ify" it - which is pretty straightforward - and we are ready to go.

Hi, first of all, thank you very much for your work on LineageOS!
I'm reposting a message from LineageOS 15.1 thread as it is EOL and you probably missed it and it contains two bugs not listed in OP that I believe are worth investigating on next release or so:
- On calls, we can't hear with headset (unless you unplug and plug back in). It was noted that it worked with beta4 so I investigated and found that this commit was added between beta 4 and 5 so you may have a look at it: https://github.com/cryptomilk/andro...mmit/c4a8569c492b343a0e22b31dd51d0821c9b75b47
- Some apps can't write on their own data folder (/storage/emulated/0/Android/data/<appname>/) if READ/WRITE_EXTERNAL permission not listed in Manifest, so the workaround you mentioned in Known Issues of the thread doesn't work + even if it is listed, it's a privacy issue because we don't want the app to look at other folders.
Examples of apps trying to write in its own data folder with no READ/WRITE_EXTERNAL permission in Manifest:
- com.tinyco.potter (instantly crash)
- com.c4mprod.rtm (instantly crash)
The only workaround possible it to apktool the app, add permission to the Manifest, and in some cases (Harry Potter for example) remove the license verification due to wrong signature after new signing, but the privacy issue remains.
Android documentation about this: https://developer.android.com/reference/android/Manifest.permission#WRITE_EXTERNAL_STORAGE
Starting in API level 19, this permission is not required to read/write files in your application-specific directories returned by Context.getExternalFilesDir(String) and Context.getExternalCacheDir().
Click to expand...
Click to collapse
That's why older versions of apps targeting a lower API than 19 works because they have the writing external permission

This is a DEVONLY thread and not the appropriate place to discuss bugs in a completely different version of the ROM.

Gairtial said:
This is a DEVONLY thread and not the appropriate place to discuss bugs in a completely different version of the ROM.
Click to expand...
Click to collapse
Why do you say it is a "completely different version of the ROM"?
Device and kernel trees are based on 15.1 work, look at the commits, there is almost no differences, so the same bugs will be inherited on 16.
I'm not sure I understand what you mean by "DEVONLY", I'm a dev and I talked of the bugs from a developer point of view (link to commit from the tree, logs, Android documentation).

I don't want to derail the thread (my original goal was to stop the thread from being derailed) but to explain myself some more (and this will be my last post on the matter, this has gotten bad enough as it is):
Yurienu said:
Why do you say it is a "completely different version of the ROM"?
Device and kernel trees are based on 15.1 work, look at the commits, there is almost no differences, so the same bugs will be inherited on 16.
Click to expand...
Click to collapse
16 is in a very early state and we don't know for sure whether the bugs can be reproduced on 16. We can't verify them, we can't diagnose them, we can't test fixes. We can't take any action on them, therefore they don't really belong here. They'd be much better suited to the LOS 15.1 thread, or left until 16 is functional enough that they can at least be verified.
Yurienu said:
I'm not sure I understand what you mean by "DEVONLY", I'm a dev and I talked of the bugs from a developer point of view (link to commit from the tree, logs, Android documentation).
Click to expand...
Click to collapse
I brought up DEVONLY because you're presenting bugs (discussion really belongs in a user thread) rather than fixes, or even work towards fixes (discussion totally belongs in a developer thread). You've presented one bug with some details but nothing that really contributes to fixing it and one with a possibly related commit. However you haven't done anything to determine whether that commit is actually the problem. You could verify for sure by building and testing before and after it. If you did that, you could even look into offering a fix.
I'm not saying this to pick a fight with you or because I hate you or think you're an idiot, I just want to make sure the right discussions are in the right threads so that devs are able to communicate with us and each other without too much pain. Putting your bug report in the 15.1 thread where it belongs ensures that this thread can be used to discuss LOS 16 development, as was clearly the intention of creating it.

Time to fork xD
Do you have a gerrit?

modpunk said:
We are just waiting for Customized DE update to Android Pie to start building a new Lineage 16.
Click to expand...
Click to collapse
It just arrived. :good:

beggar23 said:
It just arrived. :good:
Click to expand...
Click to collapse
Download is already running ...

The deep sleep bug affecting Yoshino platforms on Pie is being fixed here: https://github.com/kholk/kernel/commits/232r14-sleep-bug-research
According to the pull request to official kernel, this should mitigate the issue.
Please keep us informed if there is anything else preventing a release.
I was not able to boot LineageOS 16 compiled from your repos but if you can provide a flashable package, I can help testing if you need help?

Can you provide a status update please? How are things going? Is there something bootable at least (even if self-compiling is required)?

There is something which can be compiled. I dunno if it boots yet.

Read on Reddit that what's holding back LOS16 is "LineageHW deprecation in favor of new "treble-ready" HALs".
From the thread "What's holding back the LOS16 release ?" posted 9 days ago in r/LineageOS by u/FishTheFish152.

Any news here? How to participate?

building LineageOS 16.0 including TWRP for pie
I am sharing my steps used to build los16 with repos provided by @modpunk in the OP, in the hope that more devs could participate in the development.
Disclaimer: the result of this does not boot, so I am not sure at all if my howto and modifications are good or wrong.
Still hoping it might be useful to someone or maybe @modpunk or @derf elot could provide some hints to reach current status of this project?
Big thanks to @modpunk and @derf elot for working on this project.
Basically I tried to follow los15 howto as provided in the README.md of the modpunk's android_device_sony_lilac repository - just adapting it for los16 instead of los15:
initialize repo: used branch "lineage-16.0", first sync was done on 2019-03-18 with resync on 2019-03-19 (for the record of the los16, twrp and modpunk's repos source tree state)
for local manifest I've used this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- SONY -->
<project name="cryptomilk/android_kernel_sony_msm8998" path="kernel/sony/msm8998" remote="github" revision="lineage-16.0-LA.UM.7.4.r1" />
<project name="cryptomilk/android_device_sony_common-treble" path="device/sony/common-treble" remote="github" revision="TESTING" />
<project name="cryptomilk/android_device_sony_yoshino" path="device/sony/yoshino" remote="github" revision="TESTING" />
<project name="cryptomilk/android_device_sony_lilac" path="device/sony/lilac" remote="github" revision="TESTING" />
<!-- Pinned blobs for lilac -->
<project name="cryptomilk/android_vendor_sony_lilac" path="vendor/sony/lilac" remote="github" revision="lineage-16.0" />
<!-- TWRP recovery -->
<remove-project path="bootable/recovery" name="LineageOS/android_bootable_recovery" groups="pdk" />
<project name="omnirom/android_bootable_recovery" path="bootable/recovery" remote="github" revision="android-9.0" />
<remove-project path="vendor/qcom/opensource/data-ipa-cfg-mgr" name="LineageOS/android_vendor_qcom_opensource_data-ipa-cfg-mgr" groups="qcom,pdk-qcom" />
</manifest>
Please note, I've used TESTING branch instead of lineage-16.0 as it seems that the newest changes happen there for los16 development. Similarly I tried to guess the right kernel branch based on the most recent commits: lineage-16.0-LA.UM.7.4.r1 - hopefully that is right.
Also I tried to build TWRP in the process, so replacing los recovery with upstream twrp for pie one in the local manifest.
There has been a conflict in los source tree with data-ipa-cfg-mgr that has been pulled also from modpunk's local manifest, so that is why I am removing the los one in my local manifest here.
to speed up the sync and reduce the disk space, I am using this command:
Code:
repo sync --no-tags --no-clone-bundle -c -j8
in the Extract vendor blobs step, I am using
Code:
SRC=/path/to/unpacked-fw/xz1c-pie-8.24 ./extract-files.sh
command, having full fw unpacked into plain files all readable for normal user including fixes for symlinks to be relative instead of pointing to / directory. As I was not sure about the right fw version, I've tried pie 4.45 too for the blobs extraction. During the build, some blob was missing, so I've added proprietary-files-rootfs.txt file into device/sony/lilac directory with following content:
Code:
# ROOTFS_TRIMAREA
-sbin/tad_static;rootfs
for Setup the environment, I am using following:
Code:
unset JDK_HOME
unset JAVA_HOME
unset JAVAC
export OUT_DIR_COMMON_BASE=/path/to/lineageos/output
export WITH_TWRP=true
source build/envsetup.sh
lunch lineage_lilac-userdebug
Those unset's I had to use to avoid build problem complaining about javac different versions for .mk and soong - quite difficult to find that workaround.
The OUT_DIR_COMMON_BASE is to make compiled stuff to go outside the source tree to speed up greping there.
The WITH_TWRP option seems to be needed to let some makefiles know we like to build twrp recovery.
I've tried lineage_lilac-userdebug first, after lots of fixes during the build, the result did not boot, so I tried lineage_lilac-eng lunch target too with basically the same result unfortunately.
before Build LineageOS step, you may try to apply my changes/fixes that I had to use to avoid build errors (some were quite tricky actually) - please see the attachment here for the combined patch.
This is my repo status after the changes:
Code:
project bootable/recovery/ (*** NO BRANCH ***)
-m applypatch/Android.bp
-m applypatch/applypatch.cpp
-m crypto/lollipop/cryptfs.c
-m minui/events.cpp
-- mtdutils/Android.bp
-m otautil/Android.bp
-m otautil/Android.mk
-m updater/Android.mk
-m updater/install.cpp
project build/make/ (*** NO BRANCH ***)
-m tools/releasetools/common.py
project device/sony/common-treble/ (*** NO BRANCH ***)
-m sepolicy/vendor/file.te
project device/sony/lilac/ (*** NO BRANCH ***)
-- proprietary-files-rootfs.txt
project device/sony/yoshino/ (*** NO BRANCH ***)
-m recovery/twrp.fstab
-m sepolicy/vendor/file.te
-m sepolicy/vendor/hal_livedisplay_default.te
-m sepolicy/vendor/startup-logger.te
-m sepolicy/vendor/toolbox.te
project vendor/sony/lilac/ (*** NO BRANCH ***)
-m proprietary/framework/qti-telephony-common.jar
following command would build los16 including twrp recovery:
Code:
make -j5 bacon
The built images and installation zip can be found under ${OUT_DIR_COMMON_BASE}/lineage-16.0/target/product/lilac directory:
twrp recovery image: recovery.img
kernel boot image: boot.img
los16 installation zip: lineage-16.0-20190321-UNOFFICIAL-lilac.zip
Here are the results for lineage_lilac-eng build:
tried to boot recovery.img first, got hanging on twrp splash screen.
Installed the zip file via modpunk's twrp, tried to boot it, got a hanging black screen after SONY splash screen.
Flashed userdata from stock fw to do an erase: that made built twrp bootable and actually working - installed the built los16 zip just fine.
So this twrp is the only working thing for me so far. But it seems my built twrp is not that flexible as modpunk's as mine needed userdata erase to boot while modpunk's did not.
I tried to get some logs from main los16 boot, but logcat is not reachable. Have seen also the commit to redirect logcat into /cache for charging boot mode - tried that, but the log file was not created there.
The lineage_lilac-userdebug behaved similarly if I remember correctly (tried that build first), only twrp I could not boot as the userdata erase thing has been discovered with the -eng build. But re-tested that, it helped also with -userdebug twrp build, so both variants seem to behave the same.
The blobs from pie 8.24 vs pie 4.45 did not make a difference (after a quick rebuild followed the extraction).
In order to check my build environment, I tried similarly to build sony's aosp-9.0 - it also needed some fixes, but the result has been working (needed the special oem partition image flashed as described in sony's howto to make it boot - it would hang without it).
Attached result of following command (git added the new files first):
Code:
repo diff -u >my-changes.diff
Hopefully this helps anybody who likes to participate.
Thanks for any hints.

hi there,
yes those are the right branches you are using there. I was planning to PR some of the changes needed to build to the testing branches this weekend. I'll also look more closely at your patches, but from what I can tell you fixed the neverallow selinux issues - great!
the main issue right now is still the init, I know of at least a couple of crucial things missing from stock (there is more than one fstab now, for example - this is not implemented yet), but I was waiting for modpunk to push his recent changes before working on it again. he also told me that he has some uncommitted stuff, but hasn't had the time yet to sort them out.
also, feel free to PR your patches to modpunk's git. any help is much appreciated!
edit: instead if re-adding the proprietary-files-rootfs.txt, you can just remove the references to it from extract-files.sh and setup-makefiles.sh

[ROM][13.0][Daredevil] LineageOS 20.0 [UNOFFICIAL]

Note - please take your data backup and do clean flash as per the instructions linked in the main thread. On top of it, my builds will boot on any stock firmware as base. So there is no special recommendation towards which stock rom you need to be on.
Changelog - Sun Jan 22 19:01:23 UTC 2023
============================
• Initial Android 13 build
• Based on android-13.0.0_r20
• Improved system stability
• User interface enhancements
• Google security patch 2023-01
• Selinux enforced
• Vendor built from Source
• Imported CTS profile patches
• Safety net pass by default & no need zygisk
• Updated build fingerprint from Pixel 7 Pro (cheetah)
Reminder - for reporting bugs please mention the issue and attach the logcat.
Thank you!

Awesome..!

Any chance it would run on Nokia 8.1 after unlocking/rooting with Hikari files ?
I'm mean ... someday / when updates are over .

Changelog Sat Apr 3 08:41:31 UTC 2020
===================================
1. Initial stable build
2. March security patch
3. Comes with stock kernel
4. Linux version 4.4.194
5. Vendor image from 2250
6. System blobs from 2250
7. Ota support available
Note- Installation process changed so please go ahead and follow the instructions as I mentioned in installation section

I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?

overclockA said:
I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?
Click to expand...
Click to collapse
Thanks, saved me some time. Defeats the entire purpose for me.

xe500linux said:
Thanks, saved me some time. Defeats the entire purpose for me.
Click to expand...
Click to collapse
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.

overclockA said:
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.
Click to expand...
Click to collapse
Ah I see. Any chance you still have a copy of your non-g build?

xe500linux said:
Ah I see. Any chance you still have a copy of your non-g build?
Click to expand...
Click to collapse
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.

overclockA said:
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.
Click to expand...
Click to collapse
Much appreciated!!

i posted already in the twrp thread of my problem "touch not working with twrp", that's still persisting.
so i got another idea. i used adb commands to control twrp. like you know, adb shell twrp sideload and then do the adb sideload commands for installing lineageos 17.1.
what did i do so far is:
*flash twrp 3.4.0
*boot up to twrp 3.4.0
*use adb shell twrp remountrw
*use adb to sideload lineageos 17.1 zipfile with commands (adb shell twrp sideload and then adb sideload lineageos.zip) - but the progress bar only goes to 47% and say like it would have "finished" - i dont believe in it
*use adb to sideload vendor zipfile zipfile with commands (adb shell twrp sideload and then adb sideload vendor.zip) - that one works normally
*changed slot from B (i was on before) to A on fastboot and flashed the vbmeta to current slot (A)
*reboot without wiping system partition and installing lineageos only brings up normal stock rom
*even wiped system partition one time (or should i say system_root?) - and installed lineageOS via adb sideload. but nothing was in the system_root folder as i mounted it back again
*wiping system partition and reboot only brings up android one loading screen endlessly
so basically, the installer says it has installed the rom, but in reality it didnt seem to touch the system partition at all. am i doing something wrong or may it be that because i dont have touch access i miss to move some unlock slider which is not implemented via adb shell twrp? i think something along these lines might be the case but.. i was able to adb shell twrp wipe system. so basically it should not be a big deal to write to system partition or system_root in general.
oh and of accusation that the adb sideload probably doesnt send data correctly (from which i heard lots of stories of the past), i even pushed the zip file via adb push to / and installed it with adb shell twrp install /lineageos.zip. same result.
what i would really like to see is an debug log of the installer zip. you only see "part 1 and part 2" installing and percentage, but no informations what the installer is doing currently. this would help a lot if there would be a switch for the installer like "verbose information"
edit again.
I finally managed to do the install. You know what? it is possible without the touch gui. what i did was:
*reflashed via fastboot the stock rom
*booted normally, installed the latest upgrade (Stock ROM OTA - took a long while) - (may be obsolete)
*booted to fastboot, flashed newest twrp to boot
*booted to recovery
*adb shell twrp remountrw
*adb shell twrp remountrw (the /tmp/recovery.log showed interestingly at first remountrw the page set of readonly, at second time not - why?)
*adb shell
*entered in adb shell mount /system
*adb shell twrp wipe data
*adb push lineageos.zip /data/
*adb shell twrp install /data/lineageos.zip
*adb push ddv.zip /data/
*adb shell twrp install /data/ddv.zip
*adb shell getprop ro.boot.slot_suffix (to get the actual boot slot)
*adb reboot bootloader
*fastboot --set-active=_a (for me i was on b before, so i needed to go to a)
*fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
*fastboot reboot
*then the phone - now on lineage - asked me to factory reset, i did
*booted finally successfully up to lineage 17.1 - wlan, mobile network working just fine
if you want gapps on it, install them ideally direct after your custom rom is able to boot. in my case gps didnt worked with gapps and other apps till i did another factory reset. and the original launcher that comes with the cust-rom doesnt work anymore after installing the gapps. use the pixel launcher instead. after that, it works like a charme
in conclusion: a bit odd how the install not works as in the description was told. maybe the TA-1196 is just a bit different.

Hello Together,
i've installed LineageOs yesterday and i realy like it . I just can't find an camera App that supports the wideAngle Camera at the back.
Open Camera only recognizes 2 Cameras, and GCam 7.0 Nokia 7.2 Mod can't seem to access it either.
Is there a solution to this?
Best regards
Alex

Changelog Fri Nov 13 23:24:47 IST 2020
==============================
- based on latest lineage sources
- November 2020 security patch
- fixed bluetooth audio
- fixed mic
- fixed RIL
- fixed headset
- based on android 10 prebuilt vendor for now ( DDV2.340 )
- Comes with stock kernel
- linux version 4.4.192
- compiled using gcc
- fixed battery drain
- fixed styles and wallpapers
- selinux enforced
- banking apps working
- use NikGapps

Got brand new nokia 7.2 yesterday, developer loaded old android build 1_130 and unlocked bootloader, didnt recommend twrp as this wol break wi-fi. Can I flash this OS on my phone directly without twrp ? will wifi and camera work as it should? Sorry for the questions I am new here and just started reading this Thank you

Nokia is nowadays very slow in giving security patch updates to its devices. Its a high time we switch to custom rom..?
I'm waiting for my phone's warranty to get over. Anyways, do anyone have any eta on when this rom will get official?

I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..

dariuslapsys said:
I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..
Click to expand...
Click to collapse
I agree for tapp to wake up and selinux.
Nevertheless, bluetooth and microphones and fingerprint sensors are working like a charm.
NFC is not mentioned anywhere, but I don't need this function at all.
I installed the build from 14/11.
@Raghu varma: Can we help you out sending logfiles for some issues? Do you need testers?

Raghu varma said:
Note - Iam Not Responsible for bricked devices
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation procedure
Note - I don't recommend you people to flash any other custom kernels on this ROM untill Nokia release kernel sources. Because this ROM supports only stock kernel .
1. Download Rom.zip , twrp.img & vbmeta.img
2. power off your phone boot in to bootloader mode and flash twrp
3. Boot in to Twrp
4. Format data by typing yes
5. Wipe everything
6. Flash rom.zip & vendor.zip
7. Now tap on reboot and check your current active slot.
Example - if twrp shows current active slot A change to B if B change to A
8. Tap on reboot and tap on bootloader ( this will reboots your phone to bootloder mode )
9. Now open cmd in pc flash vbmeta using this command
for slot-a > fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
for slot-b> fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
( thanks to @singhnsk for this step )
10. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* LineageOS & CO (For Source Code)
* All the authors in my git sources
* Nokia For Prebuilt Vendor & Kernel Source
* Moderators (For Giving Freedom To Post Threads)
* My entire Nokia 7.2 community Thank you all for your massive support Again
Join Nokia 7.2 Community

Download Rom
Download Vendor
Download vbmeta
Download GApps
Download Official Twrp
Android OS version: 11.0.0_r17
Security patch level: November 2020
Build author: Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Kernel Source code: https://github.com/RaghuVarma331/android_kernel_nokia_sdm660
Source code: https://github.com/LineageOS
Click to expand...
Click to collapse
When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this

When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this

[ROM][UNOFFICIAL][9.0.0_r56] [F500,LS991,H81x,US991,VS986] AOSiP 9.0 Final

Pie-related bugs
https://github.com/Suicide-Squirrel/issues_pie/issues
TWRP for Pie
https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
LG G4 Users Group on Telegram
A Telegram group for us to hang out and discuss and share logs relating to the LG G4
https://t.me/joinchat/EwLibA3rnTMbuY4KHC2R8Q
This ROM is compatible with UsU
[F500,LS991,H81x,US991,VS986]

Frequently Asked Questions (FAQ)
Note, I have shamelessly kanged this from the LOS16 thread by @steadfasterX
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP!
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
If you encountered a kernel panic follow FAQ #6 in this post instead.
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #04: I get a kernel panic or green/purple/blue screen how to grab logs for this?
You need a ROM with pstore fully enabled and working (pstore = debug kernel panics/oops happened in a ROM)!
All builds starting from 2019-08-15 on support pstore due to: commit#1, commit#2, commit#3
This is a 2-site change if you want to make use of it in TWRP you must install the latest TWRP "PREVIEW" release as well (TWRP is only able to show pstore logs when the ROM is able to write them so I needed to fix pstore in the ROM first (see above commits #1 + #2 )).
Besides those 2 patches these kernel configs were set: PSTORE
You can check if a ROM does support writing pstore logs by:
as soon as possible on a fresh boot:
Code:
adb shell
dmesg | grep "ramoops|pstore"
Code:
[ 0.000000] cma: Found [email protected], memory base 0x000000001fe00000, size 2 MiB, limit 0xffffffffffffffff
[ 0.000000] cma: CMA: reserved 2 MiB at 0x000000001fe00000 for ramoops_mem
[ 0.200846] cma: Assigned CMA region at 0 to ramoops.78 device
[B][ 3.957553] console [pstore-1] enabled[/B]
[B][ 3.957939] ramoops: attached [email protected], ecc: 16/0[/B]
[ 3.958079] drv probe : 200 ramoops 3744
[ 6.262463] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts
or (if you are not fast enough) this ensures mostly the same check:
Code:
adb shell
ls -la /dev/pmsg0
Code:
crw-rw-rw- 1 camera camera 254, 0 2015-01-05 04:54 /dev/pmsg0
If you get no output your ROM does not support pstore logs.
From now on when you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM):
1) reboot (without taking out the battery!) to either TWRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 > readable-pmsg.txt

Here are some useful apps:
GCam with night sight
Velis Auto Brightness

DT2W is back
Hello all,
New h811/h815 builds uploaded today with Double Tap to Wake reimplemented.
I have rebased on SFXs trees, so now the device should be even more stable..
Enjoy!!

aoleary said:
Hello all,
New h811/h815 builds uploaded today with Double Tap to Wake reimplemented.
I have rebased on SFXs trees, so now the device should be even more stable..
Enjoy!!
Click to expand...
Click to collapse
Very happy to see that DT2W is back! This is 1 of the 3 features I can't stand without!
The other 2 are:
- Power button-long presso to turn on torch
- Metadata working for bluetooth car device
Are these features workin? If yes I will test this ROM immediately!

gioyann said:
Very happy to see that DT2W is back! This is 1 of the 3 features I can't stand without!
The other 2 are:
- Power button-long presso to turn on torch
- Metadata working for bluetooth car device
Are these features workin? If yes I will test this ROM immediately!
Click to expand...
Click to collapse
Long press should be there. Its a pretty standard feature for custom ROMs.. I'm on Havoc-OS at the moment..
What do you mean by metadata for Bluetooth phone call?

Please can you add full automatic internal call recording feature to any of pie based rom ?

aoleary said:
What do you mean by metadata for Bluetooth phone call?
Click to expand...
Click to collapse
When you play MP3 on the car stereo (for ex.), those info talking about name of the artist, title of the song and name of album!

Linux version
What does linux 4.x stand for? What's the difference with linux 3.10?

gioyann said:
When you play MP3 on the car stereo (for ex.), those info talking about name of the artist, title of the song and name of album!
Click to expand...
Click to collapse
It works on Havoc-OS which has the same device trees. I'll have to load AOSiP again, but it would surprise me that it doesn't work..

Biber_Golge said:
What does linux 4.x stand for? What's the difference with linux 3.10?
Click to expand...
Click to collapse
I used the thread for a different device as a base. I forgot to edit that, because as the G4 is a 3.10 kernel and a 4.x kernel would never be compatible

mkrts said:
Please can you add full automatic internal call recording feature to any of pie based rom ?
Click to expand...
Click to collapse
If the ROM doesn't already have it, I probably won't add it..

I got black screen while calling so hang up is imposible. Someone else?
Edit: it was a proximity sensor failure. Nothing to do with the rom, my excuses.

i have just tried to install this rom but it gives an error that says 'This package is for device g4, p1, 811; this device is h815'.
I have H815TR. How can i fix this issue ?

Please add jio India volt file
aoleary said:
I used the thread for a different device as a base. I forgot to edit that, because as the G4 is a 3.10 kernel and a 4.x kernel would never be compatible
Click to expand...
Click to collapse

ogun281 said:
i have just tried to install this rom but it gives an error that says 'This package is for device g4, p1, 811; this device is h815'.
I have H815TR. How can i fix this issue ?
Click to expand...
Click to collapse
The H815TR is not able to be officially bootloader unlocked, I suspect. In order to install this custom rom, you need to unlock your bootloader first, before you can do anything.
If you have not already unlocked your bootloader unofficially with the process referred to in this thread, [UNLOCK] [UNOFFICIAL] [G4] Unlock ** ANY ** LG G4 device with UsU refer to it now and read everything very carefully and make sure you understand it fully.
When you have unoffocially unlocked your bootloader, you can install TWRP for the Pie preview version and proceed to flash the H815 rom (not the H811) that is referred to in the Downloads section at the beginning of this thread.

sdembiske said:
The H815TR is not able to be officially bootloader unlocked, I suspect. In order to install this custom rom, you need to unlock your bootloader first, before you can do anything.
If you have not already unlocked your bootloader unofficially with the process referred to in this thread, [UNLOCK] [UNOFFICIAL] [G4] Unlock ** ANY ** LG G4 device with UsU refer to it now and read everything very carefully and make sure you understand it fully.
When you have unoffocially unlocked your bootloader, you can install TWRP for the Pie preview version and proceed to flash the H815 rom (not the H811) that is referred to in the Downloads section at the beginning of this thread.
Click to expand...
Click to collapse
I have already unofficialy unlocked my bootloader with all nececity stuff. I can install the other custom roms such as lineage rom AOSCP etc. But this rom gives the error i said.

ogun281 said:
I have already unofficialy unlocked my bootloader with all nececity stuff. I can install the other custom roms such as lineage rom AOSCP etc. But this rom gives the error i said.
Click to expand...
Click to collapse
FAQ #13 in the UsU thread.
Sent from my OnePlus 6T using XDA Labs

Hi guys,
Uploading new builds of AOSiP with the DT2W fixes, much improved HDR processing speeds in Google Cam and some other small stuff.

[ROM][testing] AICP 15.0 - q10.0 - apollo (Sony XZ2 Compact)

{
"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 (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android 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.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't LineageOS supported, so there is no need to report errors/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:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
AOSiP team
Community
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
Note: No official builds for now.
Test builds: https://androidfilehost.com/?w=files&flid=309318
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
- You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
No.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behaviour on flashing a new official build by (or using) the build-in updater service. However, please make sure to backup your device regularly in case something goes wrong.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions 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 please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
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 for the first time:
(Again: Don't do it if you don't know!)
0. Install the latest stock ROM, ideally to both slots or use the LineageOS copy-partitions.zip
1. Boot a current TWRP
2. Factory reset
3. Flash the ROM zip
4. Optional: Reboot to recovery, then flash add-ons like GApps, Magisk etc.
How to upgrade from an older AICP build to a newer test build:
1. Make sure you have advanced reboot enabled: Settings/AICP Extras/Auxiliary buttons/Power menu/Advanced Reboot
2. Press the power button, select "Advanced" and "Recovery" to enter the inbuilt TWRP recovery
3. Flash the ROM zip
4. Optional: Reboot to recovery, then flash add-ons like GApps, Magisk etc.
Old instructions:
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
1. Flash latest stock ROM (52.1.A.0.672)
-> either with sony flashtool ("emma") or xperifirm + newflasher
2. Unpack the ROM tar
Code:
> tar -xzvf the_file_you_downloaded.tar.gz
2. Flash the ROM
Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash userdata userdata.img
Skip flashing userdata if you are comming from an older AICP 15.0 build and want to upgrade without losing your data!
3. Reboot to the ROM
Code:
> fastboot reboot
First boot might take a few minutes.
4. Optional: flash GApps and/or Magisk
- Enable Advanced Reboot in Settings / AICP Extras / Hardware buttons / Power menu
- Press power button, select Advanced > Recovery
- Use the inbuilt TWRP recovery to flash zips
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
Note: no official builds for now.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_sony_sdm845/tree/q10.0
Device tree source:
https://github.com/AICP/device_sony_apollo/tree/q10.0
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
- Olivier
- Sjll
- MartinX3 - thanks to him for allowing me to include his TWRP
- The sony open devices team and contributors
- LineageOS team
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
Android Ice Cold Project (AICP) 15.0 (q10.0) apollo (Sony XZ2 Compact), ROM for the Sony Xperia XZ2 Compact
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Version Information
Status: Testing
Created 2020-04-26
Last Updated 2020-10-18

Nice job!
SpiritCroc said:
Offline charging is broken, your device will boot when you connect a charger to a switched off
Click to expand...
Click to collapse
You may want to cherry-pick this kernel patch - it will fix offmode charging.

Olivier said:
Nice job!
You may want to cherry-pick this kernel patch - it will fix offmode charging.
Click to expand...
Click to collapse
Great, thank you!

Nice work!
(Damn! Not the first who comment!)
[emoji2957][emoji12]

don't need to flash sony oem? ( https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-tama/ )

nikkdib said:
don't need to flash sony oem? ( https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-tama/ )
Click to expand...
Click to collapse
No
It's a stock based ROM

MartinX3 said:
No
It's a stock based ROM
Click to expand...
Click to collapse
so in this rom will never be a gcam?

nikkdib said:
so in this rom will never be a gcam?
Click to expand...
Click to collapse
Yes, on the other side SODP and stock doesn't share the same bugs

nikkdib said:
so in this rom will never be a gcam?
Click to expand...
Click to collapse
In case the sony open devices program at any point in the future catches up with stock-based solutions concerning performance and functionality, I might switch to it as well.
For now, I experience the best results with a stock-based approach.

Would flashing this ROM fix the quiet microphone issue?

pakman5391 said:
Would flashing this ROM fix the quiet microphone issue?
Click to expand...
Click to collapse
The microphone is loud enough for me, but I don't know your issue personally, so your best bet is to try it out I guess

I uploaded a new build.
I have not tested a dirty flash this time, so I recommend to do a full backup to external storage in case something goes wrong if you try to upgrade from the previous AICP build (otherwise, you need a clean flash either way).
This time, it's a flashable zip (instead of images for fastboot), I have updated the install instructions accordingly.
This update features enforcing sepolicy (thanks to @Olivier and @Sjll for their work on the offcial lineage trees).
It might be ready for official AICP builds, but I don't know if it's worth it since I have not received any user feedback yet and don't know if there is actually demand... so if you use AICP, would be great if you could provide some feedback

I will definitely flash this when i'm in vacation. Needed a working phone to manage things because of a car accident.
Things are done now and it's time to say goodbye to pie.

Bug report: Proximity sensor not working
Edit: it seems that are other sensors too...

shamllakh said:
Bug report: Proximity sensor not working
Edit: it seems that are other sensors too...
Click to expand...
Click to collapse
These are working for me. Have you flashed the latest stock ROM (52.1.A.3.49) to both slots before flashing latest AICP?

SpiritCroc said:
These are working for me. Have you flashed the latest stock ROM (52.1.A.3.49) to both slots before flashing latest AICP?
Click to expand...
Click to collapse
I flashed the 52.1.A.3.49 using xperiafirmware flasher.
Then, i used the old method (fastboot method) to flash the AICP rom...
Did i miss anything?

shamllakh said:
I flashed the 52.1.A.3.49 using xperiafirmware flasher.
Then, i used the old method (fastboot method) to flash the AICP rom...
Did i miss anything?
Click to expand...
Click to collapse
So you flashed the old build (20200425_1435)? That one might need older firmware (around 52.1.A.0.672).
For the newest AICP build (20200731_1348), you need the new firmware (52.1.A.3.49) and the new instructions.

SpiritCroc said:
So you flashed the old build (20200425_1435)? That one might need older firmware (around 52.1.A.0.672).
For the newest AICP build (20200731_1348), you need the new firmware (52.1.A.3.49) and the new instructions.
Click to expand...
Click to collapse
Thanks a lot for the hint
I re-flashed the 25.1.A.3.49 via newflasher33, then flashed the AICP ROM via fastboot.
Now it works fine.
:fingers-crossed:

I finally found the time to flash my xz2c with this great rom and first i want to thank @Olivier for the official LOS base and second @SpiritCroc making this possible on this device!
As i use Aicp since years as my main Rom on my HTC One M8 i know what i'm getting with this.
However i had problems with installation: no matter what i did, i could not get the "zip" flashing to boot.
I first used Newflasher to update to the latest stock Rom, then i booted it twice to finish the carrier installation.
then i booted up twrp and flashed the zip file. Once, for the unused slot, then on the other slot. Spent a whole evening without succes...don't know what was wrong. Unfortunately i'm not used to this A/B flashing.
I then used this guide/files to extract the img files and flashed them with fastboot. That worked like a charm!
All in all this Rom has almost no problems and is faster than stock to me. Some things i noticed so far:
- biggest (and only real) problem (and as far as i heard it is the same on the LOS base) the ringtone/notification sound is is quieter than stock. I hope this can be solved, because stock was not really loud already
- flashlight brightness is not really bright, same like stock rom i think. I used some modded lib files from an Android 9 mod to make it brighter.
- i miss the option to change the visual appearance of the navbar button which was available until Android 9 in Aicp
- screen colors seems to be much more brighter, it looks much more better than stock to me
I will continue testing and see what i'll find.
All in all this Rom with it's many features is definitely worth flashing it!!!

!!! KUDOS !!!
AICP-q10.0_apollo_20200731_1348 is the first the most customizable and fully working ROM for Xperia XZ2C, if not the only one at all. I have not tested all the goods yet, but the most important features are here:
* fully working TWRP v3.4.0.0 - no issues with touch every time! until now the only TWRP working for me was the one booted with fastboot, all the flashed TWRPs had either touch issues or SD card issues
* SafetyNet basicIntegrity passed! - ctsProfile can be easily fixed with MagiskHide Props Config and therefor we have a full SafetyNet passed along with Magisk, allowing the banking and all the other sensitive apps to work
* WIFI
* Bluetooth (audio and calling)
* GPS
* fingerprint
* camera (but not the Sony one )
* encryption with TWRP decryption working
* SD card with exFAT
* notification LED
A few installations points from me
The ROM Installation was very easy and quick, but I was doing a total clean install. Here is what I did
1. Install Sony's stock ROM 52.1.A.3.49 with newflasher
2. Boot TWRP v3.4.0.0 stock version with fastboot
3. Flash AICP-q10.0_apollo_20200731_1348.zip (please note the messages, it should flash to "inactive slot B")
4. In TWRP select Reboot => Slot B => Recovery... to reboot the phone into recovery in Slot B
5. Flash Gapps
6. Format data (just in case, many times without format with other ROMs I got bootloop)
If you need fully working Magisk with full SafetyNet pass (steps are not logical and obvious but it works, tried it w few times):
1. Flash Magisk v20.1 or v20.3.... later versions breaks the basicIntegrity! If you have flashed later Magisk version simply use Magisk Unistaller zip in TWRP and flash v20.1 or v20.3
2. Boot the phone and update Magisk Manager to the latest version 8.0.2 (307) with an option inside the Magisk Manager
3. Go back to the TWRP and now you can flash Magisk v20.4 or v21.0 - this time flashing does not break the basicIntegrity and those versions are required to fix the ctsProfile
4. Install MagiskHide Props Config module in Magisk Manager
5. Install Terminal Emulator
6. Run terminal and enter the commands su followed by props
7. Change fingerprint to XZ2C with the following options: 1 => f => 27 => 20 => reboot
Ok, so what are the drawbacks? Well not much and more personal preferences I think:
1. Missing Sony's stock camera app. I tried to flash those zips below but I get "unknown error" when I try to launch the app. Do you think it would be possible to make the Sony camera work with your ROM?
https://androidfilehost.com/?w=search&s=semccamera
2. Missing custom navigation bar buttons. On the RR ROMs I used to work the most it was possible to add extra navigation buttons and assign customized actions for tap, long press, etc.
3. Slow auto brightness reaction (I can live with that)
4. Veeery low flashlight level (there was a solution for XZ1C to fix that, I have to dig a little bit to see if it can be done here as well)
5. Ambient Display - to show notifications on blocked screen
Please don't give up the project. There is not much going with the XZ2C custom development, the last and only "normal size" Android phone.
Do you think you can take a look at some of my "drawbacks" and try to fix them?
Do you think you will make some other ROMs for XZ2C in the future, like ResurrectionRemix, EvolutionX, HavocOS?

[ROM + KERNEL][ginkgo + willow][Official] AICP

{
"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 (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android 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.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't LineageOS supported, so there is no need to report errors/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:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behaviour on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions 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 please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
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 for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work), GApps are already included for some a/b devices.
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/celtare21/kernel_xiaomi_ginkgo
Device tree source:
https://github.com/celtare21/device_xiaomi_ginkgo
Vendor source:
https://github.com/celtare21/vendor_ginkgo
Personal paypal:
https://www.paypal.me/AdumitroaieVlad
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
AICP Rom, ROM for the Redmi Note 8
Contributors
KuranKaname
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-05-06
Last Updated 2020-05-15

Reserved 1

Reserved 2

Nice

I will love it with willow support!

Lucas_Maximiliano said:
I will love it with willow support!
Click to expand...
Click to collapse
It should work fine on willow.

KuranKaname said:
It should work fine on willow.
Click to expand...
Click to collapse
Nice, I will try so, thanks!

Encryption forced?

Great ROM, but it takes quite a lot of device's RAM.

peter-k said:
Encryption forced?
Click to expand...
Click to collapse
It's like the other roms, didn't modify anything related to that.

ahileo said:
Great ROM, but it takes quite a lot of device's RAM.
Click to expand...
Click to collapse
And how is that a bad thing? Unsused ram is wasted ram so that's the whole idea.

Nice!!!!
Edit: Working great so far, gapps, magisk, feels good to have SlimRecents back on action. Is it possible to swap navigation buttons?
Edit2: Anyone else ended up with the SD card corrupted? Getting the same issue, even with other SD cards.
Logcat if needed
https://drive.google.com/open?id=1iUPTZZQWAX3kDR-K9i6HCT6e8ZTFeyQF
05-07 16:11:27.974 459 459 D vold : DISK mbr
05-07 16:11:27.974 459 459 D vold :
05-07 16:11:27.974 459 459 D vold : PART 1 c
05-07 16:11:27.974 459 459 D vold :
05-07 16:11:27.977 459 459 D vold : /system/bin/blkid
05-07 16:11:27.977 459 459 D vold : -c
05-07 16:11:27.977 459 459 D vold : /dev/null
05-07 16:11:27.977 459 459 D vold : -s
05-07 16:11:27.977 459 459 D vold : TYPE
05-07 16:11:27.977 459 459 D vold : -s
05-07 16:11:27.977 459 459 D vold : UUID
05-07 16:11:27.977 459 459 D vold : -s
05-07 16:11:27.977 459 459 D vold : LABEL
05-07 16:11:27.977 459 459 D vold : /dev/block/vold/public:179,65
05-07 16:11:28.004 459 459 E vold : Process exited with code: 2
05-07 16:11:28.004 459 459 W vold : blkid failed to identify /dev/block/vold/public:179,65
05-07 16:11:28.006 459 459 W vold : public:179,65 unsupported filesystem check, skipping
05-07 16:11:28.007 459 459 E vold : public:179,65 failed to mount /dev/block/vold/public:179,65: No such device
Edit3: reflashed AICP w/o the card and the issue remained, reverted to MIUI11 and the card is working fine, gonna reflash AICP and see how it works out.
Edit4: Reflashed AICP after going back to the stock ROM, issue persists. I just noticed I still see files in the SD card through TWRP, even tho I had formatted the card through the phone.
RN8T (Willow)

Corrupt SD too

Did anyone try the ROM without being encrypted?
Wiped everything, entire internal, format data, no boot-up.

peter-k said:
Did anyone try the ROM without being encrypted?
Wiped everything, entire internal, format data, no boot-up.
Click to expand...
Click to collapse
I booted successfully on decrypted storage.

kostas gp said:
I booted successfully on decrypted storage.
Click to expand...
Click to collapse
May I ask, which recovery you do use, and which ROM was there before?

peter-k said:
May I ask, which recovery you do use, and which ROM was there before?
Click to expand...
Click to collapse
I use orange fox recovery and my previous rom was a bootleggers test build, but I don't think this detail has any use. Perhaps you forget flashing dfe.

kostas gp said:
I use orange fox recovery and my previous rom was a bootleggers test build, but I don't think this detail has any use. Perhaps you forget flashing dfe.
Click to expand...
Click to collapse
I don't even know what is dfe ... ?

peter-k said:
I don't even know what is dfe ... ?
Click to expand...
Click to collapse
Disable forced encryption. You need to flash it after every time you flash a ton if your storage is decrypted. Here's the link for the thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page96

kostas gp said:
Disable forced encryption. You need to flash it after every time you flash a ton if your storage is decrypted. Here's the link for the thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page96
Click to expand...
Click to collapse
Thanks!
I will try, I thought with OF we don't need that anymore.

Develop Bugs

welcome