Database Info

[EOL][ROM][SDCLANG-6][microg-ready][OMS Service Mode]NLOS-15.1 - 20190208

NLOS is an unofficial LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build.
Thanks to @UnbracedTundra NLOS has it's own logo, bootanimation and wallpapers.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. This build is optimized for oneplus3t - it will flash and run on a oneplus3, because it's an unified build, but it's optimized for 3t!
In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch, ported to Oreo) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps).
NLOS doesn't require any mods to work with @Arnova8G2's GoogleCamera Mod (more details in S4turno's thread ). Just install the modded Gcam - no need to flash twrp-front-fix-oreo-op3-3t.zip, nor to use the magisk module.
The kernel is prepared for Wireguard VPN - to use Wireguard for vpn-tunnels you need to get the WireGuard-apk from playstore. WireGuard developer @zx2c4 runs a dedicated Wireguard Thread.
NLOS features OMS Service Mode - the successor of ThemeInterfacer. This means you don't need root and/or andromeda to have full Substratum Theming! It's faster then andromeda and does not rely on a tethered pc-connection. It has more exposueres (items exposed to the themers) then the rooted solution. If substratum should ask for root previlegs, deny it.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=3
Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty isn't void: we are on an oneplus device.
*
* 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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 15.1 builds for oneplus3 and onepluy3t. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files (i.e. by using gapps larger then opengapps-nano)
First time flashing NLOS 15.1 on your device, or coming from another ROM:
Backup your current ROM and make sure you have backups of your data you want to keep.
Download the ROM below in the downloads section.
Download current MindTheGapps for arm64. If you insist on using gapps, don't use a package larger then nano.
Download and flash twrp-3.2.3-0!
Download and flash latest OxygenOS Oreo firmware.
Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you are insisting to use f2fs see: https://forum.xda-developers.com/on...1-20180223-t3754855/post75688089#post75688089 - NOT recommended!
Wipe system, data and caches.
Flash NLOS.
Flash Google Apps. If you want to use microG skip this step and install microG (How to use Android without Google Apps).
Optional: flash Magisk (if you need root)
Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery (if necesarry flash the firmware zip recommended by the release notes) and flash the updated NLOS zip - don't forget to wipe dalvik and cache. Settings, apps and even google apps are preserved.
Important: if you encounter any issues, a clean install is recommended and even required if you need support.
I won't build on a daily (or nightly) basis. I will publish new builds, if I fixed something, important upstream changes or new security patchlevels.
LineageOS changelog: https://www.cmxlog.com/15.1/
Build 20190208
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 8 Feb 2019, 14:09:19 CET / 8 Feb 2019, 13:09:19 UTC):
Merge tag 'v3.18.134' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
ARM: dts: msm: FIxup GPU 0mhz clock — Nvertigo
drivers: video: mdss: Fix direct references to HZ — celtare21
drivers: ipa: Fix direct references to HZ — Humberto Borba
drivers: platform: gsi: Fix direct references to HZ — Humberto Borba
drivers: hwmon: Fix direct references to HZ — Humberto Borba
drivers: i2c: Fix direct references to HZ — Humberto Borba
Convert few critical drivers to use msecs_to_jiffies insted of HZ — Dorimanx
msm: kgsl: Remove POPP — Sultan Alsawaf
current.pick.sh: O_asb_2019-02. — Nvertigo
current.pick.sh: introduce a safer repopick. — Nvertigo
op3/t: nfc: advertise support for extended length NFC — Paul Keith
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]​
Happy flashing!
History
Build 20190127
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 27 Jan 2019, 13:01:40 CET / 27 Jan 2019, 12:01:40 UTC):
current.pick.sh: force picking abandoned battery customisation commits (220407, 220422, 219299) — Nvertigo
op3: Restore better load balancing after boot — Thomas Shum
WG: squash WireGuard-0.0.20190123. — Nvertigo
Merge tag 'v3.18.133' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]​
Happy flashing!
Firmware
NVertigo's Oxygen Firmware Archive
TWRP
Latest official twrp
Thread for official twrp
Google Apps:
MindTheGapps-8.1.0-arm64-20180223_195845.zip
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/nlos-15.1 (If you want to build this rom yourself, consult the file named README, it's outdated, but still helpfull)
Aytex, who made all of the banners on this post.
team-exynos5420 for the OP templete.
All the LineageOS-Team.
@Lord Boeffla for patiencely answering my questions.
@koenkk
@Sultanxda
@TheFrozen4 for documentation and optimizing this OP.
The microG Team
@UnbracedTundra for all the awesome NLOS-ArtWork.
@zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
@Arnova8G2 for his GoggleCamera port.
@S4turno for this great thread on GoggleCamera Mods.
@knpk13 for debugging this OP.
Substratum Dev Team
@danieldmm for opening my eyes for the obvious...
@mcdachpappe for helping me with additional notification slider options.
...and everybody I forgot.
Happy flashing!
XDA:DevDB Information
NLOS-15.1, ROM for the OnePlus 3
Contributors
nvertigo67, dianlujitao
Source Code: https://github.com/nvertigo/local_manifest/tree/nlos-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: latest
Based On: LineageOS 15.1
Version Information
Status: Stable
Created 2018-12-04
Last Updated 2018-12-04

Known Issues
fixed: NLOS can't initially encrypt f2fs data partitions (though ext4 is working flawlessly).
fixed: NLOS can't change the encryption passphrase for f2fs/ext4 data partitions (though ext4 is working flawlessly).
fixed: adb and mtp doesn't work out of the box. Workaround:
put in QS-tile "adb over network"
disable wifi
enable "adb over network" with the added tile (tile shows 0.0.0.0)
connect usb cable
an expandable notification shows up
expand it, tap it and select "file transfer": voila.
If you've run through the above adb and mtp are working fine - even trough reboots... automagicaly...
If secure boot password, pin or pattern is set: LiveDisplay's Settings show color profile as "Standrad" after a reboot, though the configuered LiveDisplay's color profile is correctly aplied.
Notification lights have hickups.
fixed: With no substratum themes applied and dark mode enabled the qs edit page is in stealth mode (white text on white background). For reference see: https://forum.xda-developers.com/ap...um-support-t3606400/post76619564#post76619564

Where has "keep wifi on during sleep"?
Sadly this isn't working anymore.
The maker of betterbatterystats offers also a tool to accomblish this task and much more:
betterwifionoff
When switching from lineage-14.1 to lineage-15.1 I found idle bat usage doubled: what has been 0.4 % per hour on nougat increased on oreo to 0.8 to 1.0 % per hour.
On n I've always used "only if charging" for "keep wifi on during sleep", but the access to this setting has been vanished by google. So I exprimented with wifi conf file, kernel driver and wakelock blocking on kernel level. Nothing really solved the adsitional idle drain.
I'm still surprised, what I found while searching settings (cli): the setting "wifi_sleep_policy" is still there! Google has just droped the access via Settings->Network&Internet->Wi-Fi and makes "Always" the default , but the setting is still available and is working like on n.
Value: Function
0: Never
1: only when plugged in
2: Always
To get restore my n setting (keep wifi on while sleep only when plugged in), I only need to connect via adb (I prefer adb over network, but it works as well with usb), and issue this command:
Code:
adb shell settings put global wifi_sleep_policy 1
After spending endless hours on kernel and debugging, this simple command brought back 0.4%/h idle bat usage.

How To: format data with f2fs with current official TWRP
Current twrp (3.2.1-0) can't change the data fs to f2fs. The reason for this breakage is, that twrp expects a mkfs.f2fs command that knows "-r size" as cli-option, but the image is shipped with a version that doesn't know about "-r".
To get data formated as f2fs with space for the encryption footer, you just need to follow these simple steps:
Download attached mkfs-f2fs.zip.
Unzip and place the contained mkfs.f2fs in /sdcard/Download.
Boot to current twrp-3.2.1-0.
In twrp:
Home-Screen->Advanced->Terminal
Code:
cp -vi /sdcard/Download/mkfs.f2fs /tmp
chmod 0755 /tmp/mkfs.f2fs
/tmp/mkfs.f2fs -t 0 -r 16384 /dev/block/bootdevice/by-name/userdata #for the lazy, if on op3/t can use /dev/block/sda15
flash rom (or use the installed rom, which is factory reseted by formating data), reboot t system amd encrypt your device.
The mkfs.f2fs binary is taken from the original twrp-3.2.1-0. This will only work for 64-bit devices:
Code:
file mkfs.f2fs
mkfs.f2fs: ELF 64-bit LSB pie executable ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /sbin/linker64, BuildID[md5/uuid]=46b5f32d88973c91f79744258599a19a, stripped

stuff.

UPDATE
Build 20180225
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta03 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
Update GoogleCamera to GoogleCamera-Pixel2Mod-Arnova8G2-V6.apk — Nvertigo
Bring back busybox. — Nvertigo
Switch kernel branch to linux-stable/nlos-15.1. — Nvertigo
Merge tag 'v3.18.96' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]​
Happy flashing!

set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine

vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.

With the version from 18th February the setup wizard is working, if you are going for a fresh installation.

vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
crian said:
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.
Click to expand...
Click to collapse
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).

nvertigo67 said:
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).
Click to expand...
Click to collapse
Will this work on op3 too?

Aasresh said:
Will this work on op3 too?
Click to expand...
Click to collapse
Most propably: yes.
I don't have my hands on a 3, and I made it my self a rule to only build and push for devices I have my hands on. That's why I stay in 3t forum though it's essentially an unified build. On the other hand: whenever a setting can be tuned for either for sd820 or sd821, I go for sd821. Other then that, NLOS should work on both models, and I try my best to give you support here.

Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...

doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
Nope

doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.

OMS service mode
TheGatorade said:
Can't wait for rootless OMS patch
This rom looking good, surprisingly stable for a beta
Click to expand...
Click to collapse
Stay tuned. Need to cleanup the sources and make a clean build.

nvertigo67 said:
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.
Click to expand...
Click to collapse
Gotcha. Good to know that plain LOS is just as good with battery life. Thank you

For people having trouble with gapps try flashing the rom then complete the setup wizard then flash gapps.
Worked for me.

UPDATE (OMS Service Mode)
Build 20180226
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta04 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
OMS Service Mode is still work in progress. Sometimes you need to activate a theme once again after "compile&activate". Some themes (i.e. flux - though it's working flawlessly) refuses to deactivate, but flashing /sdcard/substratum/SubstratumRescue.zip removes all activated overlays. Rebooting is sometimes neccessary. Wiping caches and dalvik may be a good idea, too. SwiftDark and Flux seem to work otherwise.
Special thanx to @danieldmm for helping me out of my brainlock with pointing me to https://substratum.review/ . Without his help I would be still searching for commits currently not meeged... ...that would have taken looooong.... *lol*
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
OMS Service Mode: https://substratum.review/#/q/branch:o+(status:merged+OR+status:open) and https://github.com/nvertigo/android_frameworks_base/commit/e5cc87691ea4ba482914adee36821243fe39f7b4
op3: Use exfat-nofuse — dianlujitao
Merge remote-tracking branch 'lneageos/lineage-15.1' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]​
Happy flashing!
EDIT:
HOTFIX:
Set sepolicy temporary to permissive, if you want to deactivate an overlay.

Dirty flashed nlos-15.1 20180226 over 20180225 cause some bugs.
Op3T boots but few seconds after the screen becomes black and the phone reboot to recovery.
Revert to 20180225.

A.I.C.P 13.1 [Redmi Note 5(China/Global)/Note 5 pro(India)][Unofficial][26-Jul]

{
"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 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 (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so 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:
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Full Changelog link: http://dwnld.aicp-rom.com/
Google Apps:
(link the best one for your device, there are several variants out there right now, pico/nano gapps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
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 ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. 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. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
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", 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 then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Go to Aicp Extras/Navigation bar, and enable it.
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 keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
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. (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 Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
KERNEL:
The kernel in this ROM follows LAOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!​
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
AICP, ROM for the Xiaomi Redmi Note 5 Pro
Contributors
Shahan_mik3, vasishath
Source Code: https://github.com/Whyred-Dev/android_kernel_xiaomi_whyred
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: Lineage OS
Version Information
Status: Stable
Current Stable Version: v1
Stable Release Date: 2018-07-26
Created 2018-06-15
Last Updated 2018-07-25

Latest Stable Release Version 13.1
Download link: https://www.androidfilehost.com/?w=files&flid=276181

Reserved

New rom:fingers-crossed::fingers-crossed: thanks bro...is there inbuilt gcam??

rahulk096 said:
New rom:fingers-crossed::fingers-crossed: thanks bro...is there inbuilt gcam??
Click to expand...
Click to collapse
Nope , you have to download and install after u enabling the Camera2API.
Thank you for this Rom Sur

Nightlies plox!

rahulk096 said:
New rom:fingers-crossed::fingers-crossed: thanks bro...is there inbuilt gcam??
Click to expand...
Click to collapse
No coz there are 100's of gcam variant and everyone has their own favorites. So users can install what they like rather then forcing it on them

This is an awesome ROM :laugh:

so many kinds of ROM popped out for whyred

Thanks for the new rom, Shahan!
Btw, is there an option to disable one of the sim cards without pull it out of the device?

stevebobygeorge said:
This is an awesome ROM, I'm facing one bug the screen takes some time to turn on after FP is authenticated
Click to expand...
Click to collapse
It is caused by pocket mode.... Disable it... It will be fine...
Sent from my whyred using XDA Labs

Awesome rom sir... Thanks for the rom

New build up
*all device specific changes from https://github.com/Whyred-Dev
*Rom changes till date from http://gerrit.aicp-rom.com/q/status:merged

Have been running this ROM, and so far no stability issues.
However I'm facing an issues that seems to be related to sync. If I set an alarm in the default clock and close the APP from recents, maybe the alarm won't ring. Only if the APP is stored in memory. Also, whatsapp messages come with delay or when I open the APP.
Funnily, this issue seems to be related with the ROM, since I Also experienced this behavior while running AICP 13 in my Vince.

genesisalgor said:
Have been running this ROM, and so far no stability issues.
However I'm facing an issues that seems to be related to sync. If I set an alarm in the default clock and close the APP from recents, maybe the alarm won't ring. Only if the APP is stored in memory. Also, whatsapp messages come with delay or when I open the APP.
Funnily, this issue seems to be related with the ROM, since I Also experienced this behavior while running AICP 13 in my Vince.
Click to expand...
Click to collapse
Have u reported it to the rom team? If its rom specific then they will fix it

New build up
Device specific changes
whyred: Enable call recording
whyred: Remove cpuset foreground boost 2018-07-23 16:00 UTC (android_device_xiaomi_whyred) 14 hours ago
whyred: build textclassifier 2018-07-23 16:00 UTC (android_device_xiaomi_whyred) 14 hours ago
whyred: ipacm: Fix memory leaks 2018-07-23 15:59 UTC (android_device_xiaomi_whyred) 14 hours ago
whyred: Reorder tetherable connection types 2018-07-23 15:59 UTC (android_device_xiaomi_whyred) 14 hours ago
whyred: Remove send_mic_mute_to_AudioManager overlay 2018-07-23 15:57 UTC (android_device_xiaomi_whyred) 14 hours ago
whyred: Remove config_no_sim_display_network_modes overlay 2018-07-23 15:56 UTC (android_device_xiaomi_whyred)14 hours ago
whyred: Use mke2fs to create ext4 images 2018-07-23 15:55 UTC (android_device_xiaomi_whyred) 16 hours ago
whyred: import qti privileged app permissions from MIUI 9.5.13 2018-07-23 13:52 UTC (android_device_xiaomi_whyred) 22 hours ago
whyred: Fix typo from CodeAurora in the QTI whitelist 2018-07-23 06:36 UTC (android_device_xiaomi_whyred) 1 day ago
whyred: import qti low power whitelist from MIUI 9.5.13 2018-07-23 06:35 UTC (android_device_xiaomi_whyred) 1 day ago
whyred: Use MIUI poweroff charging animation 2018-07-23 06:35 UTC (android_device_xiaomi_whyred) 1 day ago
whyred: Convert audio_effects.conf to XML 2018-07-23 06:34 UTC (android_device_xiaomi_whyred) 1 day ago
whyred: enable navbar overlay 2018-07-23 06:34 UTC (android_device_xiaomi_whyred) 1 day ago
whyred: Add Line audio device support 2018-07-23 06:27 UTC (android_device_xiaomi_whyred)
Rom changelog
Code:
* packages/apps/OmniSwitch/
8c42af7 Automatic translation import
* vendor/aicp/
e0e1baaf kernel: Allow installing modules on system
* frameworks/base/
8e8d87522af Skype voice can't transfer to carkit after re-connection
35d78d95873 Framework: Restrict warning message
b5913209cd8 ActivityManager: consider not AWAKE as sleep state
5d57a2c3fa3 Avoid the restart process for launching provider killed by AMS
5b4cc5fb58d Toast: Fix duplicated to add View of Toast
8dbe9b60b7e base: ROM size calculation error on 4GB ROM device
54d0c1b7e32 PackageManager: Avoid cache creation null access
cb06fcccb73 WindowManager: Fix redundant orientation change
c5d4d56bd58 core: Fix adb when installing a APK with incompatible abi
24bce271870 media: Use correct filename when adding to ringtone
b96263c71ff Defer deleting a http cache
8f760b8efef Do not setForceUse when a2dp config without change
5511a04fee9 Return null if a provider died before acquisition
5f1db08c630 Speed up the speed of computer MTP query
69cd92a3ff1 Fix problems caused by multithreading in VibratorService
b58beb297c9 MtpDatabase: Fix potential NULL dereference errors
88c6f8aa9a9 Remove unused calling for better performance
d7bc3267da9 Run BackgroundDexOptService with background prio
fcfef6a6c0f Convert between MtpObject and MediaProvider path
013b1554c2c Fix MtpDatabase multithreading NullPointerException
a0b845183fb Optimize AbsListView to reduce click operation latency
fabf3c54e91 display: Disable scaling on display mode switch
c178e9259ea SystemUI: Screen capture in physical resolution
* packages/apps/Dialer/
d1f4bd4a1 Re-add call recording.
* packages/apps/UnifiedEmail/
4ab14c11a Don't re-show search bar on query click.
* vendor/aicp/
0f06a58d privapp-permissions: Add new Dialer permissions
* frameworks/base/
629ac5cf5f3 fwb: Add CarbonGestures
* hardware/lineage/telephony/
24f40ad telephony: Actually pull in telephony-ext into final build
* packages/apps/Recorder/
07eb6ad Recorder: Use native functions to get H264 info
* device/aicp/sepolicy/
55d4f0a sepolicy: recovery: Allow (re)mounting system
* frameworks/base/
1744f38120b base: SystemUI: fix weather padding
* hardware/lineage/telephony/
0f1392f Cleanup usage of static
27c445e Return proper value for isDsdaEnabled
* lineage-sdk/
0ab3ecc ProfileManager: Make PROFILE_SELECTED broadcast explicit
* packages/apps/AicpExtras/
84a8af7 ae: update CarbonGestures
1688679 ae: Add CarbonGestures
* packages/apps/DeskClock/
7dd815f81 Automatic translation import
* packages/apps/Snap/
32b520248 Automatic translation import
* system/sepolicy/
c92320bf sepolicy: public: Exclude Recovery from system mount neverallow
014af6de sepolicy: Allow init to modify system_blk_device
* vendor/aicp/
5386fd84 apns: sprint: Default to legacy n.*, allow x.* as an alternative
Download link
https://www.androidfilehost.com/?fid=5862345805528058275

Sorrry wrong reply

Hi everybody!
Thanks for ur work and thanks for share it
I flashed this rom and works perfectly all,no bugs and only issue its a power button,but all things work correctly,tomorrow ill flash cam api2...
Regards:victory:

ivoxda said:
Hi everybody!
Thanks for ur work and thanks for share it
I flashed this rom and works perfectly all,no bugs and only issue its a power button,but all things work correctly,tomorrow ill flash cam api2...
Regards:victory:
Click to expand...
Click to collapse
power button?

Venu_GopalU said:
power button?
Click to expand...
Click to collapse
Yeah power button not work correctly when i press the button for reboot or lock and unlock not work lock random locks and not on light properly...and adaway no works and magisk not installed...
I back up to Masik...
Regqrds

[ROM][9.0][OFFICIAL] FlokoROM v2.0 [clover/Mi Pad 4]

{
"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"
}
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Features
Floko-specific features:
OmniSwitch included
Kawaii Easter Egg in Floko Settings
Remove Music Player
Remove Font Packages (Did Google release "Product Sans" under open source license???)
crDroid and LineageOS features:
SmartNav(SmartBar, Fling, Pulse...)
Network traffic monitor
switch 4G/LTE icon
Battery bar
Statusbar Quick/Smart pulldown
QS columns
Lockscreen customization
Switch "Recents" style
HW button configurations
Expanded desktop
Rounded corners
Style(Theming)
Volume panel customization
brand-new dashboard
media seekbar
Hardware-specific Features
I have an 8" wifi model of Mi Pad 4. so I can't test other version's hardware-specific features like cellular and fingerprint scanner.
dt2w
smart (magnetic) cover
Night light with LiveDisplay
grayscale (both "Reading Mode" and "Digital Wellbeing")
aptX Audio
Known Issues
Lockscreen is Landscape mode only
Maybe aosp issue, plz tell me if you know "it's fixed in other ROM!"
If you encountered other issues, please tell me
How to Install
MAKE A BACKUP OF ALL YOUR DATA.
(First time) Wipe /system, /data, /cache, Dalvik/ART Cache
Flash ROM, GApps, Magisk(optional), ...
Reboot to System
Enjoy.
Thanks
love. respect. and love.
GuaiYiHu (device & kernel are based on his work)
crDroid
LineageOS
OmniROM
Dirty Unicorns
AICP
Team
@1indwurm (me)
Downloads
FlokoROM: https://mega.nz/#F!hy4wBCqB!cTgzCLZ3IEYEj0a0PjwgKw!srpmWIyY]
Recommended TWRP (Encryption supported): https://mega.nz/#!KBtTmSoR!IjFmSllDIqJa_dyD-OgBQZpPzX9M8n7i7-lG4AsEGOg (mirrored from Mokee)
Source Codes
FlokoROM: github.com/FlokoROM
device: mordiford/device_xiaomi_clover/tree/9.0
kernel: GuaiYiHu/android_kernel_xiaomi_clover/tree/mkp
XDA:DevDB Information
FlokoROM, ROM for the Xiaomi Mi Pad 4
Contributors
1indwurm
Source Code: https://github.com/FlokoROM
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: crDroid
Version Information
Status: Beta
Current Beta Version: v2.0
Beta Release Date: 2019-10-15
Created 2019-02-19
Last Updated 2019-10-15

additional information
FAQ
Why this ROM encrypting my /data partition? How to disable it?
FlokoROM enabled forceencrypt for /data partition as default to avoid the issue ( https://github.com/FlokoROM-Devices...mmit/d83e5ebd7b826d53b3aa49faa3d824c397e4ba2f )
and keep your data securely.
If you don't want encryption, you can use this https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 .
note: This Disabler require formatted /data . you can use it at first time you flash Floko. DO NOT use for already encrypted /data .
first time: in TWRP, Format Data(THIS WILL ERASE YOUR DATA) -> Flash Floko -> OpenGApps(optional) -> Magisk(recommended) -> Flash Disabler .
update: Flash Floko -> OpenGApps(optional) -> Magisk(recommended) -> Flash Disabler.
What is "recommended TWRP"?
some TWRP couldn't decrypt /data correctly. we recommend mokee's one.
Why FlokoROM doesn't support "Fast Charge"?
Hardware issue. Mi Pad 4 DOES NOT support ANY "fast charge", 5V/2A is max (depend on charger and cable).
Changelog
You can read full changelog (Git changes) in FlokoROM. Open Settings -> Floko Settings -> about FlokoROM -> current changelog .
Code:
[SIZE="3"]
Floko-v2.0-clover-20191212_060504-OFFICIAL: 2019.12 release
* Include 2019-12-05 security patch levels
Floko-v2.0-clover-20191114_033716-OFFICIAL: 2019.11 release
* Include 2019-11-05 security patch levels
* added seekbar to media notification: like Android Q
Floko-v2.0-clover-20191015_073807-OFFICIAL: 2019.10 release
* Include 2019-10-05 security patch levels
* no new feature (maintainance)
Floko-v2.0-clover-20190915_100553-OFFICIAL: 2019.09 release
* Include 2019-09-05 security patch levels
* kernel has been rebased
* re-enabled "Force activities to be resizable" (does it work?)
Floko-v2.0-clover-20190817_084433-OFFICIAL: 2019.08 release
* Include 2019-08-01 security patch levels
* Update kernel to 4.4.185
* Gaming Mode: now you can disable ADB when you turned on
Floko-v2.0-clover-20190707_160503-OFFICIAL: 2019.07 release
* Include 2019-07-05 security patch levels
* Update kernel to 4.4.181
* Added Gaming Mode (block notifications, disable automatic brightness, ...)
* Substratum settings integration in "Interface" category (require "substratum theme engine")
Floko-v2.0-clover-20190610_024932-OFFICIAL: 2019.06 release
* Include 2019-06-05 security patch levels
* Update kernel to 4.4.180
* Now you can use OmniSwitch as Recents
* Add Android Q style battery icon
Floko-v2.0-clover-20190515_072709-OFFICIAL: 2019.05 release
* Include 2019-05-05 security patch levels
* Update kernel to 4.4.179
* Renewal bootanimation
Floko-v2.0-clover-20190416_014344-OFFICIAL: april release
* Include 2019-04-05 security patch levels
* Update kernel to 4.4.178
* Use Snap as default camera app
* Show our logo in "about device" dialog
* Add "Restart SystemUI" button
* Fix old style cellular icons
Floko-v2.0-clover-20190318_110436-OFFICIAL: renewal
* v2.0 (based on crDroid)
* Doze and LiveDisplay are back
* Include 2019-03-05 security patch levels
[/SIZE]
old releases changelog (based on AICP):
Code:
[SIZE="3"]
floko_clover_p-9.0-OFFICIAL-20190219_070313: First Official release!
* SELinux is now Enforcing
* Enabled forceencrypt on /data (but your data doesn't encrypt at this time)
* Disable useless DisplayMode settings (finally!)
floko_clover_p-9.0-EXPERIMENTAL-20190207_004509: Initial public release (experimental)
* Support "Night lights" and "Grayscale" screen
(feature does work, but you can see DisplayMode settings that does not work)
* Remove LineageOS LiveDisplay(we don't use lineage-sdk)
[/SIZE]

Great ROM

You forgot to add:
System will encrypt your tablet,
Twrp with encryption support:
?????
Flash no-dm-verity-no-encryption.zip before 1st boot:
GSI Guide.
Thx. @1indwurm

dzidexx said:
You forgot to add:
System will encrypt your tablet,
Twrp with encryption support:
?????
Flash no-dm-verity-no-encryption.zip before 1st boot:
GSI Guide.
Thx. @1indwurm
Click to expand...
Click to collapse
I'm using MoKee's TWRP-20190117-3.2.3.0-4-clover.img
・primary(baidu): https://download.mokeedev.com/?device=clover -> "Download Recovery"
・mirror(Google Drive): https://forum.xda-developers.com/showpost.php?p=78699745&postcount=9
> Flash no-dm-verity-no-encryption.zip before 1st boot:
does it work with Pie??

"flash....zip"
I don't know.
I was very surprised during the booting.
I need to make a full copy int.mem. and do the format data.
Now I see into LRT TWRP thread - it has no verity, no encryption in adv.options. @1indwurm
Mokee's twrp mounts encrypted Internal Memory automatically but doesn't ask for pass/pin/etc. Encryption hasn't any sense.
I can't find option:
Quick settings pulldown - left/right/both sides.

dzidexx said:
"flash....zip"
I don't know.
I was very surprised during the booting.
I need to make a full copy int.mem. and do the format data.
Now I see into LRT TWRP thread - it has no verity, no encryption in adv.options. @1indwurm
Mokee's twrp mounts encrypted Internal Memory automatically but doesn't ask for pass/pin/etc. Encryption hasn't any sense.
I can't find option:
Quick settings pulldown - left/right/both sides.
Click to expand...
Click to collapse
If I flash this rom, it will encrypt my clover automatically?

Yes it will encrypt, all data will not be deleted. You can try to flash mentioneded .zip or option in LRT TWRP.
I didn't do that yet. @dyingbread

dzidexx said:
Yes it will encrypt, all data will not be deleted. You can try to flash mentioneded .zip or option in LRT TWRP.
I didn't do that yet. @dyingbread
Click to expand...
Click to collapse
I am not a fan of enrcypted device. So i am not interested if this rom automatically encrypt my device. I just don't want the trouble of formatting data if I move to a different rom.

After installation and configurations I was forced to purchase another Mi Pad 4 to test software.
Very smooth and responsive. Thank you.

Can someone please explain the difference between this and that: https://treble.andro.plus

stangri said:
Can someone please explain the difference between this and that: https://treble.andro.plus
Click to expand...
Click to collapse
Ok.
First, we provide this officially and this is traditional-style ROM. Release per device, support hardware specific features, and you can flash this ROM for clover only.
...Aaaand, treble.andro.plus provides "phh-treble" style FlokoROM GSI (Generic System Image) unofficially. You can flash it for all Treble-ready (A-only and A/B) devices.

Thank you for the outstanding ROM. I've tried a few Oreo-based ROMs before, so I've had bootloader unlocked for a while. All the other Pie-based ROMs I've tried before failed to support Mi Pad 4 properly.
Flashed Mokee TWRP, from TWRP I wiped data, flashed this ROM, OpenGapps 9.0 micro, Magisk 18.1, wiped cache/dalvik cache, booted in and restored most of my apps/setup from the cloud as if Gapps were installed natively and got the Magisk Manager app after another reboot.
Fantastic ROM, granted I haven't tried BT yet, but WiFi definitely works better than on Oreo AICP Mordiford, screen has rounded corners, etc. Thank you for making this ROM available!

Rom has been near perfect, Thank you 1indwurm
The one thing I have found a problem with is charging. I have tried a few chargers and they are very slow or don't register at all, after been fast on the stock rom. I never checked the charging speed before so can't give a before and after comparison but it seems at least twice as slow. On one of my chargers it seemed to be draining the battery instead of charging it. On the charger that was reasonable speed it was charging at 950mA but that was on a charger that should do 2.4A
@stangri - BT works well, I didn't have any drop outs when I used to have occasional dropouts in busy areas

crass00 said:
The one thing I have found a problem with is charging.
Click to expand...
Click to collapse
@1indwurm -- another thing I've discovered is force-landscape orientation is lost after reboot. If I disable rotation when the device is in the landscape mode it works fine until reboot. After reboot it's stuck in portrait, I have to enable rotation again, rotate into landscape and then lock rotation again.
All other roms I've tried, once you lock the device in landscape mode, it would survive reboots and after reboot would be in landscape mode again with rotation locked.

sorry for the delay in releasing a new build.
First, we have to tell you that we're working on switch to the crDroid-based version (from AICP-based) now.
crDroid use LineageOS device trees(familiar to us), so I wish we can make it more stable and work better than before...
and finally we don't have to nuke LiveDisplay and some Lineage HALs!
Done:
pass the build
flash it over old release (no need to wipe /data !)
boot
Wi-Fi
Grayscale and LiveDisplay
DT2W
Smart cover
basic rebrand
new OTA
WIP or TODO:
WIP: Extra Settings is a little buggy FIXED
WIP: rebranding
TODO: fix screen rotation
TODO: fix charging speed
Screenshot:
need sources?
local_manifests: https://gist.github.com/lindwurm/bca97f055d3704bc17ab592bb79aaef2
stangri said:
@1indwurm -- another thing I've discovered is force-landscape orientation is lost after reboot. If I disable rotation when the device is in the landscape mode it works fine until reboot. After reboot it's stuck in portrait, I have to enable rotation again, rotate into landscape and then lock rotation again.
All other roms I've tried, once you lock the device in landscape mode, it would survive reboots and after reboot would be in landscape mode again with rotation locked.
Click to expand...
Click to collapse
reproduced in the latest release and testing(crDroid-based) ver. Did(or would) you test that on Mokee? (our build is based on mokee's tree, not xiaomi-sdm660)

Looking forward to the new version!

Finally, FlokoROM v2 is released! read OP and download it (and you can flash it over older releases, no need to wipe /data).

Link not working....but I have all day to try and download.

Flashed over v1 and keep saying google play services stop auutomatically, play store either, what it is the problem ? I'll have to do a clean install?

[ROM][9.0][PIE] ZirconiumAosp [IGNITE][WHYRED][r31][21-02-2019]

{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
We are focusing on Stability. We are bringing more Stable ROM for your devices and it got everything that will make you stick to it.
We look forword for precious support of all Users.
@@Professional_Guider(Founder)
@@LordShenron(CoFounder)
@@SunnyRaj84348(CoFounder)
[MENTION=]@ChirayuAggarwal[/MENTION](Developer)
@@Abhijit_Vadera(Graphics Designer)
Support Us if you like our work
[SIZE=+1]Got an issue or suggestion? Reach us at[/SIZE]
Telegram: https://telegram.me/ZirconiumAospChat
Networks And Internet
- Roaming Indicator
- 4G Icon
- VoLTE icon
- Show Data Disabled Icon
Display settings customization
- Font size customization according to percentage
- Lockscreen Charging Info (Toggable)
- 21+ Accents Added
- Omni Themes
- Gradient Accents
- Dark Theme Added
- Black Theme Added
- Ambient Display
Sound settings customization
- Short Cut to prevet Ring added.
- Charging Vibration (Toggable).
- Now Playing Feautre.
Security settings customization
- fingerprint Authentication Viberation (Toggable)
- Lockscreen Powermenue Visibility
- Weather Temp
ZirconiumAosp: ZirconiumAosp
ZirconiumAosp Device Sources: ZirconiumAosp Devices
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
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 ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. 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. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Z€€$HAN, [21.02.19 22:16]
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
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", 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 then reboot.
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. 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. (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).
The ROM should contain everything you need to enjoy Android. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
- Backup your personal data (Important)
- Download the ROM and GApps and transfer them to your device.
- Boot to recovery (TWRP recommended).
- Wipe the System, Cache, Data and ART/Dalvik cache.
- Flash the ROM + Gapps Zipfile.
- Flash the root solution of your choice (optional).
- Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
Z€€$HAN, [21.02.19 22:16]
Thread title: [ROM][9.0][PIE] ZirconiumAosp [IGNITE][CODENAME][r31][DATE]
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
We are focusing on Stability. We are bringing more Stable ROM for your devices and it got everything that will make you stick to it.
We look forward for precious support of all Users.
@@Professional_Guider(Founder)
@@LordShenron(CoFounder)
@@SunnyRaj84348(CoFounder)
[MENTION=]@ChirayuAggarwal[/MENTION](Developer)
@@Abhijit_Vadera(Graphics Designer)
Support Us if you like our work
[SIZE=+1]Got an issue or suggestion? Reach us at[/SIZE]
Telegram: https://telegram.me/ZirconiumAospChat
Networks And Internet
- Roaming Indicator
- 4G Icon
- VoLTE icon
- Show Data Disabled Icon
Display settings customization
- Font size customization according to percentage
- Lockscreen Charging Info (Toggable)
- 21+ Accents Added
- Omni Themes
- Gradient Accents
- Dark Theme Added
- Black Theme Added
- Ambient Display
Sound settings customization
- Short Cut to prevet Ring added.
- Charging Vibration (Toggable).
- Now Playing Feautre.
Security settings customization
- fingerprint Authentication Viberation (Toggable)
- Lockscreen Powermenue Visibility
- Weather Temp
ZirconiumAosp: ZirconiumAosp
ZirconiumAosp Device Sources: ZirconiumAosp Devices
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
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 ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. 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. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Z€€$HAN, [21.02.19 22:16]
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
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", 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 then reboot.
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. 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. (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).
The ROM should contain everything you need to enjoy Android. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
- Backup your personal data (Important)
- Download the ROM and GApps and transfer them to your device.
- Boot to recovery (TWRP recommended).
- Wipe the System, Cache, Data and ART/Dalvik cache.
- Flash the ROM + Gapps Zipfile.
- Flash the root solution of your choice (optional).
- Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
ROM:
Click Here
GApps:
Unofficial OpenGApps
OpenGApps
- Pixel Experience
- Google for AOSP
- Dirty Unicorns
- LineageOS
- LiquidRemix
- SuperiorOS
- Omni
- ArrowOS
- MSM-XTENDED
- AICP & POSP Team for thread template idea
- Please let us know if we forgot to mention your name in credits..​Kernel source:
https://github.com/srfarias/Xiaomi_Kernel_OpenSource
XDA:DevDB Information
ZIRCONIUM, ROM for the Xiaomi Redmi Note 5 Pro
Contributors
Being_Zeeshan, darkstar085, srfarias
Source Code: https://github.com/Zirconium-Project
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2019-02-21
Created 2019-02-21
Last Updated 2019-02-21​

Closed, duplicate.
Thanks
Lupin The Third
Forum Moderator

[ROM][11.0][Perseus][UNOFFICIAL] PixelExperience [AOSP/CAF][2021/11/25]

{
"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"
}
PixelExperience for Xiaomi Mi Mix 3 [Perseus]
What is this?
PixelExperience is an AOSP/CAF based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Disclaimer​
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.
*
*/
Whats working?
Android Auto
Bluetooth
Camcorder
Camera
Face Unlock
Fingerprint Reader
Flashlight
Google Pay
GPS
Hey Google
Lights
Mobile Data
NFC
RIL
Slider
Sound/Vibration
Wi-Fi
Known issues
You tell me
Installation
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download
Download (Plus)
Donate
Rom developer
Liked my work? Give me a beer
Rom mantainer
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Special Thanks
Thanks to PixelExperience project and jhenrique09
Thanks to ArrowOS project and palaych
Thanks to Parrot043 for his GCam Port (Donate, Telegram group)
Thanks to Josevega, jesujopi, rtx4d, Crim Soukyuu, Azev and loipuru for all their help on Telegram
Credits for trees
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Credits for ROM source code
Website: https://download.pixelexperience.org/
Telegram: Chat | News
Github: https://github.com/PixelExperience
Code Review: gerrit.pixelexperience.org
PayPal: Donate to us
Blog: blog.pixelexperience.org​
Build author: sergej_7
Source code: https://github.com/PixelExperience
Trees: https://github.com/sergej3
ROM Developer: jhenrique09
XDA:DevDB Information
PixelExperience 11, ROM for the Xiaomi Mi Mix 3
Contributors
sergej_7
Source Code: https://github.com/PixelExperience
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: AOSP/CAF
Version Information
Status: Stable
Created 2021-03-23
Last Updated 2021-11-25

Changelog 2021/11/25 (PE+):
- Added raise to wake gesture
Changelog 2021/11/12 (PE/PE+):
- Optimized Wi-Fi configuration
Changelog 2021/11/11 (PE/PE+):
- Blocked bluetooth_timer wakelock
- Fixed battery drain when charging is paused and device remains plugged
Spoiler: Old Changelogs:
Changelog 2021/11/08 (PE/PE+):
- Fixed battery drain when charging is paused and device remains plugged (experimental, only included in PE+)
- Reduced and blocked wakelocks
- Added Boeffla wakelock blocker
- Hold qcom-step-chg wakelock only when charging
- Switch back to ArrowOS Kernel
Changelog 2021/11/02 (PE):
- Switch to LineageOS Kernel
Changelog 2021/10/28 (PE):
- kernel: wakelock: Kill wakelocks after 30s have elapsed
- drivers: power: add timeouts to wakelocks (These can get stuck sometimes and prevent system from sleeping.)
- Revert step-chg-jeita: release qcom-step-chg wakelock if device is discharging
Changelog 2021/10/26 (PE):
- step-chg-jeita: release qcom-step-chg wakelock if device is discharging
- Kang qcacld-3.0: Do not allow any wakelocks to be held
- Kang scsi: ufs: Remove 10 ms CPU idle latency unvote timeout
- Kang msm: kgsl: Relax CPU latency requirements to save power
Changelog 2021/10/24 (PE):
- Revert sdm: ensure color mode stays the same after reboot
- Revert sdm: correctly return to previous color mode after HDR/DCI P3
- Update GCam Port by Parrot043 (Version: MGC 8.2.300 Parrot043 V8.1, Telegram Group)
- Sync ArrowOS trees
- Sync PixelExperience trees
Changelog 2021/10/23 (PE+):
- Kang qcacld-3.0: Do not allow any wakelocks to be held
- Kang scsi: ufs: Remove 10 ms CPU idle latency unvote timeout
- Kang msm: kgsl: Relax CPU latency requirements to save power
- Switch to LineageOS kernel tree
Changelog 2021/10/14 (PE / PE+):
- Switch to auto-brightness model from redfin
Changelog 2021/10/13 (PE+):
- Revert display: enable ThinLTO and Whole Program Devirtualization
- Revert Merge tag 'LA.UM.9.3.r1-02800-sdm845.0' of https://source.codeaurora.org/quic/la/platform/hardware/qcom/display
- Revert sdm: ensure color mode stays the same after reboot
- Revert sdm: correctly return to previous color mode after HDR/DCI P3
- Add GCam Port by Parrot043 (Version: MGC 8.2.300 Parrot043 V8.1, Telegram Group)
- Changes in BoardConfig.mk
Code:
BUILD_BROKEN_DUP_RULES := true
BUILD_BROKEN_USES_BUILD_COPY_HEADERS := true
BUILD_BROKEN_PREBUILT_ELF_FILES := true
BUILD_BROKEN_ELF_PREBUILT_PRODUCT_COPY_FILES := true
- Sync android_hardware_qcom_media/tree/arrow-11.0-caf-sdm845 from ArrowOS trees
- common: dynamic: Replace packageblacklist with packageexludelist
- common: Move aux camera whitelist prop to vendor
- common: Expose aux camera {black,white}list props
- sepolicy: Unlabel aux camera whitelist prop
- Sync ArrowOS trees
- Sync PixelExperience Plus trees
Changelog 2021/10/08 (2):
- Revert sdm845-common: Update display and adreno blobs to OnePlus6 R
- Revert sdm845-common: Update display and adreno blobs to OnePlus6 R
Changelog 2021/10/08 (1):
- Sync ArrowOS trees
- Sync PixelExperience trees (October Security Patch)
- Update GCam Port by Parrot043 (Version: MGC 8.2.300 Parrot043 V8.1, Telegram Group)
Changelog 2021/07/08 (PE):
- Changes in BoardConfig.mk
Code:
BUILD_BROKEN_DUP_RULES := true
BUILD_BROKEN_USES_BUILD_COPY_HEADERS := true
BUILD_BROKEN_PREBUILT_ELF_FILES := true
BUILD_BROKEN_ELF_PREBUILT_PRODUCT_COPY_FILES := true
- Sync android_hardware_qcom_media/tree/arrow-11.0-caf-sdm845 from ArrowOS trees
- Revert: Switch to Pixel's thermal 2.0 service
- Revert: Add Pixel Tips
- Update GCam Port by Parrot043 (Version: MGC 8.2.300 Parrot043 V6, Telegram Group)
- Sync ArrowOS trees
- Sync PixelExperience trees (June Security Patch)
- Revert: Revert sdm845-common: Remove prebuilt libplatformconfig
- Revert: sdm845-common: Add missing blobs manually
Code:
proprietary/vendor/lib/libmm-omxcore.so
proprietary/vendor/lib/libOmxCore.so
proprietary/vendor/lib/libOmxVdec.so
proprietary/vendor/lib/libOmxVenc.so
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib64/libmm-omxcore.so
proprietary/vendor/lib64/libOmxCore.so
proprietary/vendor/lib64/libOmxVdec.so
proprietary/vendor/lib64/libOmxVenc.so
Changelog 2021/04/08:
- Switch to Pixel's thermal 2.0 service
Changelog 2021/03/31:
- Add Pixel Tips
- Add GCam Port by Parrot043 (Version: MGC 7.6.008 Parrot043 V9, Telegram Group) [fixes 4K 60fps video recording]
- Remove GCam Port by BSG
Changelog 2021/03/27 (2):
- perseus: Use dipper fp to bypass safetynet
Changelog 2021/03/27 (1):
- Switch to ArrowOS trees (clean flash required)
- Adapt device tree
- Revert sdm845-common: Remove prebuilt libplatformconfig
- Revert common: dynamic: Replace packageblacklist with packageexludelist
- Revert common: Move aux camera whitelist prop to vendor
- Revert common: Expose aux camera {black,white}list props
- Revert sepolicy: Unlabel aux camera whitelist prop
- Remove GCam Port by Parrot043
- Add GCam Port by BSG (Version: MGC_8.1.101_A9_PVo, Celso page, Telegram group)
- sdm845-common: Add missing blobs manually
Code:
proprietary/vendor/lib/libmm-omxcore.so
proprietary/vendor/lib/libOmxCore.so
proprietary/vendor/lib/libOmxVdec.so
proprietary/vendor/lib/libOmxVenc.so
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib64/libmm-omxcore.so
proprietary/vendor/lib64/libOmxCore.so
proprietary/vendor/lib64/libOmxVdec.so
proprietary/vendor/lib64/libOmxVenc.so
Changelog 2021/03/26 (canceled):
- perseus: sepolicy: Adress for secure_element denials
- perseus: sepolicy: allow secure element to call qteeconnector
- perseus: ArrowOS bringup
Changelog 2021/03/24 (2):
- sdm845-common: Update sound trigger blobs
Changelog 2021/03/24 (1):
- perseus: add HotwordEnrollment blobs
- perseus: add HotwordEnrollment blobs
Changelog 2021/03/23:
- perseus: Drop HotwordEnrollment
- Add precompiled APK of GCam Port by Parrot043
Changelog 2021/03/22:
- Initial build
Changelog Pre-release:
- common: dynamic: Replace packageblacklist with packageexludelist
- common: Move aux camera whitelist prop to vendor
- common: Expose aux camera {black,white}list props
- sepolicy: Unlabel aux camera whitelist prop
- sdm845-common: Mark as having overridden commands
- sdm845-common: Remove prebuilt libplatformconfig
- perseus: Define BOARD_AVB_RECOVERY_KEY_PATH and other AVB flags
- sdm845-common: Add missing blobs manually
Code:
proprietary/vendor/lib/libmm-omxcore.so
proprietary/vendor/lib/libOmxCore.so
proprietary/vendor/lib/libOmxVdec.so
proprietary/vendor/lib/libOmxVenc.so
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/vendor.qti.hardware.d[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib/[email protected]
proprietary/vendor/lib64/libmm-omxcore.so
proprietary/vendor/lib64/libOmxCore.so
proprietary/vendor/lib64/libOmxVdec.so
proprietary/vendor/lib64/libOmxVenc.so
- Adapt device tree according to this and this

Recommended Firmware
V12.5.1.0.QEECNXM
Clean flash
1. Reboot in TWRP
2. Wipe cache, dalvik, data, system, vendor and format data
3. Flash Firmware V12.5.1.0.QEECNXM
4. Flash ROM
5. Flash Magisk, if needed
6. Reboot
Update ROM
1. Download new build
2. Reboot in TWRP
3. Wipe cache and dalvik
4. Flash new build
5. Flash Magisk, if needed
6. Reboot
Pro Tips
- Reduce cellular battery drain
- Reduce Wi-Fi and Bluetooth scanning battery drain
- Tasker Power saver mode Project
- Underclock your CPU with Franco Kernel Manager

Nice work

Will it be updated later?I m ready for flash it

Until_You_ said:
Will it be updated later?I m ready for flash it
Click to expand...
Click to collapse
i updated the link already

Excuse my ignorance, but do I need to install the MIUI ROM first?
I get a bootloop installing with or without MIUI ROM.
I tried:
- V12.0.3.0.QEECNXM
- V12.0.2.0.QEEMIXM
1 - Wipe, Advanced Wipe, Dalvik / ART Cache, Cache, System, Vendor, Data
2 - Install MIUI 12 ROM
3 - Install Pixel Experience
4 - Install Magisk
5 - Reboot

peachey said:
Excuse my ignorance, but do I need to install the MIUI ROM first?
I get a bootloop installing with or without MIUI ROM.
I tried:
- V12.0.3.0.QEECNXM
- V12.0.2.0.QEEMIXM
1 - Wipe, Advanced Wipe, Dalvik / ART Cache, Cache, System, Vendor, Data
2 - Install MIUI 12 ROM
3 - Install Pixel Experience
4 - Install Magisk
5 - Reboot
Click to expand...
Click to collapse
dont install MIUI12 ROM, just flash recommended Firmware afterwards flash PixelExperience and Magisk. I have added flash instructions in third post.

sergejschmal said:
i updated the link already
Click to expand...
Click to collapse
Can you put a setting to Change the height of the status bar like on Evolution X OS?

ruben9696 said:
Can you put a setting to Change the height of the status bar like on Evolution X OS?
Click to expand...
Click to collapse
not a PixelExperience feature, therefore it will not be added

Hello, thank you for the build. Can u give more info on "Pixel Launcher At a Glance widget not displaying weather"? I've been using Pixel Experience on mi mix 1 (lithium) and on Redmi Note 8 Pro (begonia), both are displaying weather info properly. Is it a device-specific bug?

Ppkrasyuk said:
Hello, thank you for the build. Can u give more info on "Pixel Launcher At a Glance widget not displaying weather"? I've been using Pixel Experience on mi mix 1 (lithium) and on Redmi Note 8 Pro (begonia), both are displaying weather info properly. Is it a device-specific bug?
Click to expand...
Click to collapse
I don't know unfortunately. After I clean flashed newest build widget displayed weather without any tweaks. Maybe other users can confirm that there is no problem. In my test today this problem was gone.
edit: i have clean flashed again today and the problem seems to be gone.

Has anyone else the bug on PE Os that Whatsapp web only works when the phone is unlocked? How can I fix this?Rest of the Rom good so far

Chikerlein said:
Has anyone else the bug on PE Os that Whatsapp web only works when the phone is unlocked? How can I fix this?Rest of the Rom good so far
Click to expand...
Click to collapse
cant reproduce it on my device, can you send logs?

sergejschmal said:
cant reproduce it on my device, can you send logs?
Click to expand...
Click to collapse
I have no idea how to do that.
I've tried something and can tell you how to force it. Whatsapp web does not work if the mobile phone is in standby mode (display dark and phone locked) for at least 5 minutes.
If you then press the power button (Phone Locked and Display on).
Whats app web works again.

Thank you for doing this, seems to work flawless so far.
Only magisk was a bit confusing as they seem to have changed to an apk completly now. So I've skipped that for the time being.

Razzee said:
Thank you for doing this, seems to work flawless so far.
Only magisk was a bit confusing as they seem to have changed to an apk completly now. So I've skipped that for the time being.
Click to expand...
Click to collapse
Just rename apk to zip and it works like before

sergejschmal said:
dont install MIUI12 ROM, just flash recommended Firmware afterwards flash PixelExperience and Magisk. I have added flash instructions in third post.
Click to expand...
Click to collapse
I've tried the same as the instruction flashing the recommended firmware as a clean flash, but still in bootloop, now way to get the rom boot
EDIT: was the old magisk zip, the rom is perfect now

sergejschmal said:
Recommended Firmware
V12.0.3.0.QEECNXM
Clean flash
1. Reboot in TWRP
2. Wipe cache, dalvik, data, system, vendor and format data
3. Flash Firmware V12.0.3.0.QEECNXM
4. Flash ROM
5. Flash Magisk (optional but recommended)
6. Reboot
Update ROM
1. Download new build
2. Reboot in TWRP
3. Wipe cache and dalvik
4. Flash new build
5. Flash Magisk, if needed
6. Reboot
Pro Tip: Reduce celluar battery drain
- Turn off Mobile data always active in Developer Options
How to fix Pixel Launcher At a Glance widget not displaying weatherHow to fix Device is not Play Protect certified [Fixed with 2021/03/27 (2)]
- Open Lawnchair At a Glance settings
- Enable Google App as weather service and also enable notification dots
- Freeze the Lawnchair App with Titanium Backup or via ADB
Uninstalling Lawnchair will break displaying weather. I have used this fix since LineageOS 17.1. If there is a better way to do it please share the solution in this thread.
How to fix Device is not Play Protect certified [Fixed with 2021/03/27 (2)]
- Flash latest Magisk if you haven't flashed it yet
- Enable Magisk Hide option and hide Magisk App
- Long-press the Play Store app icon and open app info section
- On the app's info section force stop, clear cache and clear data
- Reboot
Device will now show as Play Protect certified
Click to expand...
Click to collapse
I followed exactly your order but still in bootloop
I'm using:
fw_perseus_miui_MIMIX3_V12.0.3.0.QEECNXM_b96755549d_10.0
PixelExperience_perseus-11.0-20210331-0807-UNOFFICIAL
Magisk-v22.0