[ROM][Unofficial][5.1.1] CyanogenMod 12.1

[ROM][Unofficial][5.1.1] CyanogenMod 12.1 - Xiaomi Mi 2

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
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.
*/
Introduction
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Images
{
"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"
}
Features (Device Specific)
LCD Color/Gamma Settings
LCD Adaptive Backlight
LCD Color Enhancement
LCD QCOM PostProcessing(PP) support
Disable Touch keys and enable NavigationBar
Set Vibrator Intensity
1+1 QuickBoot
Differences to CM11
Removed TrueDualBoot(TDB) support. And pls don't try to bring it back by using TDB enabled versions of CWM or TWRP. It's dead and will be replaced by GRUB4Android in March.
CM12 still supports Dualsystem the way Xiaomi designed it. That means that it can be installed to both System partitions but the userdata partition will be shared.
SDCARD filesystem detection You now can format your internal sdcard to whatever filesystem is supported by VOLD and the CM kernel. The only alternative that would make sense is F2FS though.
Improved Power consumption Use Xiaomi's MPDecision, thermald and libqc-opt together with QCOM's power HAL.
Added QCOM time services
Added Oppo QuickBoot
Use Xiaomi blobs I replaced some Nexus4 blobs with the originals from Xiaomi'S MIUIv5 ROM to prevent some unpredictable bugs
Encryption support another reason why TDB is dead now
Known Bugs
Bluetooth connection and Audio issues
Installation instructions
!ATTENTION!
There are two (annoying) problems with GoogleApps:
1) CM12 is huge and doesn't leave much space for GAPPS on MI2
2) recovery ignores errors in update.zip's which means even though it tells you the installation was successful it failed.
this means you have two options:
1) resize your system partition(recommended) this miflash package resizes your system partition without taking space from your data partition by removing the system2 partitions:
http://forum.xda-developers.com/mi-2/orig-development/flashtools-miflash4linux-recovery-qdl-t3036730
2) install very small gapps packages and check /tmp/recovery.log and the remaining space after the installation to make sure it was successful.
Click to expand...
Click to collapse
First time flashing CyanogenMod 12.1 your device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Issues?
Report them on github:
https://github.com/M1cha/android_device_xiaomi_aries/issues
IMPORTANT: if you use xposed - pls disable it and try again because it can cause problems in some cases.
Also the issue must contain important information like your phone model(mi2(s)(c)), and the exact build version of the ROM.
Download
DevHost
Changelog
Code:
20150730:
[changed] total rewrite
[changed] new kernel: CAF(LA.AF.1.1_rb1.18) + 3.4.108(upstream) + android-3.4(kernel/common)
[changed] support for merged partitions
[bug] some features like hw tunables are still missing
20140228:
[fixed] fix audio HAL by comparing values with MIUIv5
[changed] fix ACDBLoader
[changed] update WIFI config
[changed] update system.prop from CAF (should improve battery life a little bit)
[changed] rename CM perf profile properties for Xiaomi's thermald
[changed] use CM's default wallpaper
[changed] update kernel from mako
Older changelogs:
Code:
20140218:
[changed] set SELinux to Enforcing mode
[changed] disable flashing FMRadio FW
[fixed] Haptic Feedback for touch keys
[changed] disable ACDBLoader as an attempt to fix random call bugs
[fixed] attempt to fix Atmel touchscreen driver crash
Code:
20140217:
[new] F2FS support
[fixed] Installation on resized system partitions
[changed] switch to CAF HAL's and add FMRadio support
[changed] Update WLAN driver to LA.AF.1.1_rb1.12
Code:
20140216.
[new] Initial Release
Thanks To/Credits
Code:
* CyanogenMod
* Nexus 4 Maintainers
* QCOM for generic Sources
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Xiaomi Mi 2
Contributors
m11kkaa
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2015-02-16
Last Updated 2015-07-30

First
Sent from my A0001

Oh wow, finally

You are just awesome thanks for your work

Thank you very much M1cha for you excellent work and dedication! I will try this rom immediately.
Can I ask you a question? Where did you learn to mess with the kernel and the firmwares? Did it took long for you to learn it? I have always wanted to mess with these things myself, but I always get overwhelmed with the required knowledge

_Roysten said:
Thank you very much M1cha for you excellent work and dedication! I will try this rom immediately.
Can I ask you a question? Where did you learn to mess with the kernel and the firmwares? Did it took long for you to learn it? I have always wanted to mess with these things myself, but I always get overwhelmed with the required knowledge
Click to expand...
Click to collapse
Since there's not much documentation for such things u just have to start doing it and learn everything by yourself.
Also, these projects are too big to study them or trying to find a task just for learning.
The best way is to find a project idea and then u have to work on it until u succeed

Thank you M1cha,
2bad no dualboot and xposed (yet).

Dualboot(the Xiaomi way) works, and TDB shouldn't be used anymore.(u have to wait for G4A).
The information about Xposed doesn't mean that Xposed isn't compatible(it should be), it just means that before reporting any crashes you should disable Xposed and check if u still have the same problem.

incall working , also quick-boot

SWADED said:
Thank you M1cha,
2bad no dualboot and xposed (yet).
Click to expand...
Click to collapse
Hi,
You're wrong ! TDB is working (even if it shoudln't be now, GRUB is coming thanks to @m11kkaa) and xposed is now available for Lollipop : http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Btw, thank you for your job michael ! :good:

[Now that we dont have TDB (with kitkat i only used it a few times) is there any way to eliminate the system 1 and increase the system0 and sdcard partitions?

softkey vibration doesn't work.
I reserve to test this build as a daily driver and report any issue tomorrow.
m1cha, you won't let me swap my mi2s and I'm so happy with this
thanks a lot for your work!!

thx you for you work!

acastrocab said:
[Now that we dont have TDB (with kitkat i only used it a few times) is there any way to eliminate the system 1 and increase the system0 and sdcard partitions?
Click to expand...
Click to collapse
I'm wondering the same
And thanks m11kkaa for your great work!!!
Sent from my MI 2S using XDA mobile app

m11kkaa said:
Dualboot(the Xiaomi way) works, and TDB shouldn't be used anymore.(u have to wait for G4A).
The information about Xposed doesn't mean that Xposed isn't compatible(it should be), it just means that before reporting any crashes you should disable Xposed and check if u still have the same problem.
Click to expand...
Click to collapse
xposed for lollipop generates a bootloop on your CM12.
working fine on Ivan's AOSP rom.
so, don't try to flash it over m1cha's CM12!!

Reserved
Sent from my MI 2S using Tapatalk

acastrocab said:
[Now that we dont have TDB (with kitkat i only used it a few times) is there any way to eliminate the system 1 and increase the system0 and sdcard partitions?
Click to expand...
Click to collapse
Yeah but u should wait g4a
mehdoux said:
Hi,
You're wrong ! TDB is working (even if it shoudln't be now, GRUB is coming thanks to @m11kkaa) and xposed is now available for Lollipop : http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Btw, thank you for your job michael ! :good:
Click to expand...
Click to collapse
Tdb is not supported anymore because cm policies ask for encryption support, and this feature would break tdb. About xposed we will not provide support or let users report bug if this fw is installed, because it breaks many things
Sent from my A0001

linuxxxx said:
Yeah but u should wait g4a
Tdb is not supported anymore because cm policies ask for encryption support, and this feature would break tdb. About xposed we will not provide support or let users report bug if this fw is installed, because it breaks many things
Sent from my A0001
Click to expand...
Click to collapse
No ! I'm not saying that TDB is supported, I wrote that this ROM is working with TDB (even if it shoudln't be because G4A is coming) because I've tested it and it's true.
Concerning xposed, if it's not asking too much, what does this framework break ? Thank you.

mehdoux said:
No ! I'm not saying that TDB is supported, I wrote that this ROM is working with TDB (even if it shoudln't be because G4A is coming) because I've tested it and it's true.
Concerning xposed, if it's not asking too much, what does this framework break ? Thank you.
Click to expand...
Click to collapse
It "just" replaces the runtime with another one with tons of hacks that will cause huge security issues, then apps will have tons of npe or other fc cuz xposed hacks them for these modules. So when u get a bug andnure running xposed the 80% of times it's xposed, the 20% is a real bug
Sent from my A0001

mehdoux said:
No ! I'm not saying that TDB is supported, I wrote that this ROM is working with TDB (even if it shoudln't be because G4A is coming) because I've tested it and it's true.
Concerning xposed, if it's not asking too much, what does this framework break ? Thank you.
Click to expand...
Click to collapse
Before anybody tries to use TDB, I explain why you shouldn't:
You won't be able to format or backup data from CM12 with a TDB-enabled Recovery.(it would backup a empty data folder). And if you will make a data backup of CM12 with a NON-TDB Recovery this backup will contain System1 and System2 data too which makes them really big.
And ofc, If you wipe Data for CM12, System1 and System2 data are gone too.
The reason is that CM12 ignores the data location set by CWM.

Related

[ROM][CANCRO][6.0.1] AOSP-CAF [STABLE][May13]

{
"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 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.
*/
What is Code Aurora Forums ?Code Aurora Forum (CAF) is a consortium of companies with projects serving the mobile wireless industry. Software projects it concerns itself with are e.g. Android for MSM, Femto Linux Project, LLVM, MSM WLAN and Linux-MSM. Code Aurora is basically AOSP plus all Qualcomm specific enhancements and optimization.
What is AOSP-CAF ?AOSP-CAF is meant to join AOSP and CAF projects into a widely usable repository,
stored on https://github.com/AOSP-CAF/. It also benefits from a few CyanogenMod updates.
Q&A - FAQ
How to use layers on AOSP-CAF
TWRP gives me no OS installed error after flashing rom.
No problem. Just swipe to reboot or flash roms+gapps and reboot, you wont have this issue
Can I flash a custom kernel?
Not recommended, you can try but then don't come to me crying on battery
Is rom prerooted?
No, Flash from here
Can you add blah blah app or blah blah feature to the rom?
No, not at all.
When will you update the rom?
No ETA as always
Is the ROM suited for daily usage ?
Yes.
Where can I change the Quick Tiles and Status Bar ?
Long press the Settings icon in the notifications drawer.
You will have access to the SystemUI Tuner from Marshmallow.
Downloads Links
aosp-mm6.0.1-20160513-cancro.zip
Google Applications (optional) :
SLIM GAPPS : (Use packages for ARM, Android 6.0, Micro or Pico)
Flash the GApps before the first boot. If not, a clean flash is recommended.
SuperSU (optional) :
SuperSU
ROM is not pre rooted, SuperSu v2.52 & SuperSu v2.65 both work flawless.
Flashing and updatingAOSP-CAF clean install :
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the AOSP-CAF 6.0.1 ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Flash the SuperSU zip (recommended, see Q&A informations)
- (Optional) Every additional zip you want to flash
- Reboot
AOSP-CAF update / upgrade :
- (Information) Don't wipe anything unless you want to
- Flash the latest AOSP-CAF 6.0.1 ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Flash the SuperSU zip (recommended, see Q&A informations)
- (Optional) Every additional zip you want to flash
- Reboot
About UNOFFICIAL buildsDevice tree : https://github.com/ShivamKumarJha/izer_device_xiaomi_cancro/tree/aosp-mm
Kernel sources : https://github.com/ShivamKumarJha/android_kernel_xiaomi_cancro
Vendor blobs : https://github.com/ShivamKumarJha/proprietary_vendor_xiaomi
Issues and reports- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
Thanks to :
- AOSP and CodeAurora Forums
- The CyanogenMod Team
- Men_in_black007 and the AOSP-CAF Team
- Everyone involved in the sources used
XDA:DevDB Information
[ROM][CANCRO][6.0.1] AOSP-CAF [STABLE][May13], ROM for the Xiaomi Mi 3
Contributors
Shivam Kumar Jha, linuxxxx, Men_in_black007
Source Code: https://github.com/AOSP-CAF
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader, TWRP
Based On: AOSP
Version Information
Status: Stable
Created 2016-05-13
Last Updated 2016-05-13

SCREENSHOTS

Nice one!! Installing!!
The only thing I miss is SnapDragon Camera :crying:

Hey
Will layers themes work on this?
Update : Sorry. Didn't read OP properly. You've mentioned about it in the OP.
Thanks for the ROM.

google play services FC even when all permissions are provoided

satvikvg said:
google play services FC even when all permissions are provoided
Click to expand...
Click to collapse
That is because of the Gapps you would have used.
I used Slim Gapps and had no issues whatsoever.

Shivam Kumar Jha said:
That is because of the Gapps you would have used.
I used Slim Gapps and had no issues whatsoever.
Click to expand...
Click to collapse
while installing i get a error message
"assert failed: run_program("/temp/install/bin/device_check.sh") == 0"
"Updater process ended with ERROR: 7"
But rom will be installed properly
and why cant we install openGapps Stock rather than pico, i want full nexus experience

satvikvg said:
while installing i get a error message
"assert failed: run_program("/temp/install/bin/device_check.sh") == 0"
"Updater process ended with ERROR: 7"
But rom will be installed properly
and why cant we install openGapps Stock rather than pico, i want full nexus experience
Click to expand...
Click to collapse
You don't have the new miui mm partition size. Flash it via fastboot to get it. Google how or go to Mi3 General MIUI MM thread, it's been discussed millions of times. Or to be simple, follow this guide
https://jrizzoli.github.io/dotfiles/

diongdyh said:
You don't have the new miui mm partition size. Flash it via fastboot to get it. Google how or go to Mi3 General MIUI MM thread, it's been discussed millions of times. Or to be simple, follow this guide
https://jrizzoli.github.io/dotfiles/
Click to expand...
Click to collapse
i have miui mm partition, 1.2gb
but after flashing stock Opengapps play services FC,
Even after flashing Pico gapps packege, google apps work perfectly but sensors wont work, Auto-rotate, Gyro,Proximity

satvikvg said:
i have miui mm partition, 1.2gb
but after flashing stock Opengapps play services FC,
Even after flashing Pico gapps packege, google apps work perfectly but sensors wont work, Auto-rotate, Gyro,Proximity
Click to expand...
Click to collapse
Don't log your google account in on setup wizard.

Super Stable daily driver.:good:

pille1 said:
Nice one!! Installing!!
The only thing I miss is SnapDragon Camera :crying:
Click to expand...
Click to collapse
Ringford said:
Don't log your google account in on setup wizard.
Click to expand...
Click to collapse
Use slim gapps, I used it and logged into google in the setup itself and did not face any issue whatsoever
nikhilsnigam said:
Super Stable daily driver.:good:
Click to expand...
Click to collapse
Thanks.
I've personally done some changes on top of AOSP-CAF repo's to my liking:
Snap Camera instead of AOSP Camera
CM Gallery
Replaced Launcher with Trebuchet
Reboot Menu (Reboot, Soft Reboot, Recovery & Bootloader)
Chain fire SuperSU v2.65 inbuilt
Layers Manager inbuilt
Added Browser (it was not present by default)
Added SlimFileManager (no file manager was present by default)
Viper4Android (preactivated)
Removed Tethering & Portable hotspot from launcher
I've been using ROM for hours and have not seen any issues ..
If you guys want the new changed build, lemme know

Shivam Kumar Jha said:
Use slim gapps, I used it and logged into google in the setup itself and did not face any issue whatsoever
Thanks.
I've personally done some changes on top of AOSP-CAF repo's to my liking:
Snap Camera instead of AOSP Camera
New Gallery App
Replaced Launcher with Trebuchet
Reboot Menu (Reboot, Soft Reboot, Recovery & Bootloader)
Chain fire SuperSU v2.65 inbuilt
Layers Manager inbuilt
Added Browser (it was not present by default)
Added SlimFileManager (it was not present by default)
Viper4Android (preactivated)
Removed Tethering & Portable hotspot from launcher
I've been using ROM for hours and have not seen any issues ..
If you guys want the new changed build, lemme know
Click to expand...
Click to collapse
it would be nice although i myself managed to get those things done.

Shivam Kumar Jha said:
Thanks.
I've personally done some changes on top of AOSP-CAF repo's to my liking:
Snap Camera instead of AOSP Camera
New Gallery App
Replaced Launcher with Trebuchet
Reboot Menu (Reboot, Soft Reboot, Recovery & Bootloader)
Chain fire SuperSU v2.65 inbuilt
Layers Manager inbuilt
Added Browser (it was not present by default)
Added SlimFileManager (no file manager was present by default)
Viper4Android (preactivated)
Removed Tethering & Portable hotspot from launcher
I've been using ROM for hours and have not seen any issues ..
If you guys want the new changed build, lemme know
Click to expand...
Click to collapse
Are you going to add these changes in new update or they are present this 13th may update only, because I can't find any. (Hopefully you must be talking about new update, right?)
Also,
1- I am not able to add security lockscreen, in first try I was able to add pattern as security but on going again into setting security on lockscreen, it FC the settings app. (using Open Gapps Nano)
2- We can only edit tasks of home button, nothing for menu & back key.
3- When you tap on low system space warning, it showed Messages App FC & then open the app itself. (there are 2 warning shown for this low system space)
Thanks for another clean AOSP ROM.

Shivam Kumar Jha said:
Use slim gapps, I used it and logged into google in the setup itself and did not face any issue whatsoever
Thanks.
I've personally done some changes on top of AOSP-CAF repo's to my liking:
Snap Camera instead of AOSP Camera
New Gallery App
Replaced Launcher with Trebuchet
Reboot Menu (Reboot, Soft Reboot, Recovery & Bootloader)
Chain fire SuperSU v2.65 inbuilt
Layers Manager inbuilt
Added Browser (it was not present by default)
Added SlimFileManager (no file manager was present by default)
Viper4Android (preactivated)
Removed Tethering & Portable hotspot from launcher
I've been using ROM for hours and have not seen any issues ..
If you guys want the new changed build, lemme know
Click to expand...
Click to collapse
What is the 'new gallery app' ?

well thanks a lot for your replay @Shivam Kumar Jha
I want a Pure Nexus experience on my Mi4, any suggestion for that..?

satvikvg said:
well thanks a lot for your replay @Shivam Kumar Jha
I want a Pure Nexus experience on my Mi4, any suggestion for that..?
Click to expand...
Click to collapse
Use this rom
---------- Post added at 12:04 AM ---------- Previous post was at 12:02 AM ----------
Shivam Kumar Jha said:
If you guys want the new changed build, lemme know
Click to expand...
Click to collapse
It would be NICE :good::good:

diongdyh said:
You don't have the new miui mm partition size. Flash it via fastboot to get it. Google how or go to Mi3 General MIUI MM thread, it's been discussed millions of times. Or to be simple, follow this guide
https://jrizzoli.github.io/dotfiles/
Click to expand...
Click to collapse
i am on rr 5.6.8 currently with 1.2 gb extended partation...as rr is based on cm13
can i directly flash this cm13 github script for miui mm partation on rr??

Jay sharma said:
i am on rr 5.6.8 currently with 1.2 gb extended partation...as rr is based on cm13
can i directly flash this cm13 github script for miui mm partation on rr??
Click to expand...
Click to collapse
I flashed the script on DU. It worked, so you should be fine

diongdyh said:
I flashed the script on DU. It worked, so you should be fine
Click to expand...
Click to collapse
it doesnt erase internal storage right with its flash_all.bat command?

[ROM] CM-12.1 for Meizu M2 Note [5.1.1]

{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1(LP), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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!
*/
CyanogenMod 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. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Unofficial build of CyanogenMod 12.1 (Android 5.1.1) for the M2 Note
Working:
Everything :victory:
Hardware acceleration
SELinux enforced
RIL for SMS/Calls/Internet
GPS
WiFi
Vibration
Audio
Bluetooth / A2DP
MTP and Mass Storage mode
External SD
Camera (Videos & Photos)
All Sensors
Tethering
USB Otg
Gestures!
mBack button!
LiveDisplay (natively smooth)
Download:
Build 15 (Stable 3 "Elpun") : Download
/! Make a backup, This build needs a full wipe /!
[security] November Security Bulletin from CM
[usb] Charge Only can be enabled (and usb can be renabled)
[fix] Zram should be working correctly now (reduces longterm slowdowns)
[camera] Recording in stereo should work now (Thanks @goodoane)
[kernel] security feature : now uses CC_STACK_PROTECTOR_STRONG, more info
[signed-build] the build is now using release-keys instead of public "test-keys" meant for debug, improves a bit security and fixes some bugs in Google Apps (ex: Android Wear refusing to work, asking for an "user/signed" or "userdebug/unsigned" rom)
Build 14 (Stable 2 aka "Ololo") : Download
/! Make a backup, dirty update works but if not, do a clean wipe or don't complain about bugs/crash/FC/whatever /!
[security] Dirty COW fixed (CVE-2016-5195)
[battery] small improvements, battery stats should be more accurate
[stability] Clock wakelocks should be fixed
[improvement] built as user instead of userdebug (rom size is a bit smaller, less logs)
[SafetyNet] is properly "suported", banking apps and pokemon Go perfectly works without installing anything else (no more systemless root, xposed or w/e to make it work )
[kernel] general updates (3.10.104)
Build 13 (Stable 1 aka "Olala") : Download
/! Make a backup and do a clean wipe or don't complain about bugs/crash/FC/whatever /!
[LiveDisplay] is now natively working (perfectly smooooooth)
[kernel] general updates, security updates, cleanup, Live Display Implementation
[stability] CM updates
[usb] Charging mode only should work correctly when plugged in usb.
[decoder] AwesomePlayer is now enabled by default instead of NuPlayer (known to cause Google Photos crash, etc.)
[gestures] CMActions is now correctly using Russians strings, Spanish translation added.
[misc] root should be allowed from Dev Options now, anyway if not, flash SuperSU
Build 12 (Release Candidate 2) : Download
/! Make a backup and wipe /system before you flash this RC to be sure you got rid off the ANT+ files /!
This RC2 will probably be renamed "stable 1" if no major problem arise.
[kernel] general updates, cleanup , disabled KSM & UKSM for battery performance
[removed] ANT+ was only partially working and caused battery drain (it seems)
[battery] disabled both ANT (see above) and a few unneeded kernel features that might have caused a bit of draining issues, this should be better now ! :good:
[stability] overall cleanup (overlays, values, etc..)
[gestures] CMActions was cleaned and a few bugs were fixed, the gestures are now enabled/disabled by a switch but remains customisable when you press on them :good:
[misc] adb is not root by default anymore (this might help those who play PoGo) use the dev settings to change that
Build 11 (Release Candidate 1) : Download
(I told you I wouldn't release a beta next time)
changelog :
[bugfix] wifi hotspot is working (both in secured and unsecured AP mode)
[bugfix] fix the back button not being active at first touch when home was pressed to wake the device (elexogic)
[bugfix] back button vibration renabled
[improvement] Gestures are fully customisable now, choose what app/action is triggered (thanks elexogic again)
[kernel] general updates, config_aio disabled for security
[battery] IOscheduler reverted to "deadline" for better battery life
[stability] wifi, mobile, bluetooth, gps stability improved (blobs update to 5.1.10G)
Build 10 (latest beta before stable ) :
Download
(changelog : trully fixed back button for all M2 Note variants)
Issues
Data on second sim in a dual-sim configuration. (hardware limitation)
If you find a bug please check if there's no issue already mentioning it and create one with details and logs here : Bug reports @ Github issues
BUT FIRST :
Do a clean install first, wipe everything.
Make sure you don't use modifications (flash clean, try again)
Check the closed issues
Check google first, there might already be solutions
Explain and give details, add logs as much as possible
How to install:
It's usually a good idea to download the newest build version. Just install it via recovery. I tested it on TWRP but it should also work on other recoveries.
You will also need gapps if you want to use Google services. stock OpenGApps - use the arm64 versions.
How to install TWRP - I don't support unlocking bootloader, installing TWRP or the ROM, you should know what you do first or start learning.
Sources:
Device Tree: https://github.com/Moyster/android_device_meizu_m2note
Kernel: https://github.com/Moyster/android_kernel_m2note
Thanks to:
@BlueFlame4
@Elexogic for his fixes on back button and gestures
@scafroglia93 for his kernel updates
Meizu & Mediatek for releasing their sources!
Appendix:
If you want to mirror the files or port the ROM to another device, I encourage you to do so! Only please respect my work and give proper credits. Thank you!
XDA:DevDB Information
[STABLE] CM-12.1 for Meizu M2 Note [5.1.1], ROM for the Meizu MX
Contributors
Moyster, BlueFlame4, Elexogic, Everyone I forgot, those who translated the gestures modules (Alex Lartsev (RU), LBA97 (ES))
Source Code: http://github.com/Moyster
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Current Stable Version: Stable two
Stable Release Date: 2016-11-09
Created 2016-09-10
Last Updated 2017-02-05

Great job was visiting your github daily downloading now
Sent from my M2 Note using XDA-Developers mobile app

Thanks a lot for hard work!
You could add a link for the recovery twrp?
Inviato dal mio m2 note utilizzando Tapatalk

ro11er said:
Great job was visiting your github daily downloading now
Sent from my M2 Note using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my M2 Note using XDA-Developers mobile app

ro11er said:
Sent from my M2 Note using XDA-Developers mobile app
Click to expand...
Click to collapse
done

Moyster said:
done
Click to expand...
Click to collapse
Moyster nega quota exceeded any chance of uploading somewhere else?
Sent from my M2 Note using XDA-Developers mobile app

Good job ...thanks you

COOL JOB!!!!!!
THX
Please port MIUI rom the M2 Note........
Soory my bad English!!
Grat!
The new cm 12.1 rom!!!

Thanks for hard work.

:< My SIM1 tray was broken, I won't be able to use this rom.
Anyway, thanks for your hard work.

ro11er said:
Moyster nega quota exceeded any chance of uploading somewhere else?
Sent from my M2 Note using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't really have time to post it anywhere else now, if someone is kind enough to do it, you're welcomed
I'll try to find a way and have them online, maybe OTA too, if anyone is kind enough to host all that ^^
qamu74 said:
COOL JOB!!!!!!
THX
Please port MIUI rom the M2 Note........
Soory my bad English!!
Grat!
The new cm 12.1 rom!!!
Click to expand...
Click to collapse
I don't port roms, sorry.
Next step :
1. fixing bluetooth
2. stable CM-12.1 release
3. CM13

Moyster said:
I don't really have time to post it anywhere else now, if someone is kind enough to do it, you're welcomed
I'll try to find a way and have them online, maybe OTA too, if anyone is kind enough to host all that ^^
I don't port roms, sorry.
Next step :
1. fixing bluetooth
2. stable CM-12.1 release
3. CM13
Click to expand...
Click to collapse
OH cm13 Very COOL!
Good Job Bro.!!!!

fantasticlord said:
:< My SIM1 tray was broken, I won't be able to use this rom.
Anyway, thanks for your hard work.
Click to expand...
Click to collapse
Good to know, I didn't try both slots but it will be fixed that's why it's a beta and reviews are welcome, I can't test everything alone

Nice!

Moyster sim not detected in sim2. Unfortunately on my way out and need phone when back will get catlog.
Sent from my M2 Note using XDA-Developers mobile app

My sim isn't recognized and the m-back button is off. Will you fix this bugs?
Enviado desde mi m2 note mediante Tapatalk

ro11er said:
Moyster sim not detected in sim2. Unfortunately on my way out and need phone when back will get catlog.
Sent from my M2 Note using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello, I just fixed the second simcard I'll upload a clean build during the night so :
easy fix : wait tomorrow, flash beta 2
"I'm not gonna wait" fix : flash the rom, edit /system/build.prop
and delete the line :
(line ~148)
"persist.radio.multisim.config=dsdsro.mediatek.platform=MT6735"
Edit :
m-back button is off.
Click to expand...
Click to collapse
touch doesn't act for now, simple press is home, long press is "app drawer", It's not off, only back doesn't work, eventually will be fixed

Moyster said:
touch doesn't act for now, simple press is home, long press is "app drawer", It's not off, only back doesn't work, eventually will be fixed
Click to expand...
Click to collapse
Please try to repair the touch, it is a very useful feature!
Thanks a lot for your work!
Inviato dal mio m2 note utilizzando Tapatalk

Moyster said:
Hello, I just fixed the second simcard I'll upload a clean build during the night so :
easy fix : wait tomorrow, flash beta 2
"I'm not gonna wait" fix : flash the rom, edit /system/build.prop
and delete the line :
(line ~148)
"persist.radio.multisim.config=dsdsro.mediatek.platform=MT6735"
Edit :
touch doesn't act for now, simple press is home, long press is "app drawer", It's not off, only back doesn't work, eventually will be fixed
Click to expand...
Click to collapse
Are you gonna fix the back function for tomorrow's update?
Enviado desde mi m2 note mediante Tapatalk

Great job...
The ROM work fine... My second Sim is recognized but only works on "edge" or GSM and the internet connection speed is too slow..

[ROM][TREBLE][8.1][03/06/2018]RESURRECTION REMIX v6.0-UNOFFICIAL FOR LENOVO P2

{
"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"
}
Warnings:-
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, dead cats,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and no point
* in pointing the finger at me for messing up your device
*/
Resurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters.
BRIEF INRODUCTION
I started working on treble for almost about a month, after developing beta builds of Lineage OS. At the initial development, I keep developing those builds in the view of project treble, using latest blobs from other devices, move HAL's to /system/vendor(no /vendor at that time), binderize everything etc. Those experiments arose some issues and I managed to fix few issues and few are left. I dont think I know everything, but its quite challenging as it is my first development on qcom. I am constantly learning by doing.
USING /PRELOAD AS /VENDOR?
Initially, I thought of using preload partition as /vendor and it was only 400M. I thought it wouldn't be sufficient. There was about 50M unallocated space after /preload. We can append 50M to preload to increase its size. I started looking the size of vendor image from other devices. I noticed that vendor images of some devices was less than 400M. So 400M would work if I remove some unused 32 and 64 bit blobs. I cleaned up some useless blobs and build twrp. It was successful
EXISTING ISSUES
After having a seperate /vendor, I changed everything to /vendor from /system/vendor. Haxxx blobs using sed to solve dependencies and added VNDK-SP HALS. I got stuck at two major issues, NFC and sensors. I noticed that mike started working on official lineage build. I got a fix for sensor service. Thanks to @mikeioannina. Regarding NFC, I have used Stock HAL in my previous builds as passthrough HAL. OSS HAL is not working for some unknown issue(need to look at it later). NFC is not working after treble is implemented. I noticed that the stock HAL depends on libhardware_legacy.so and [email protected]. And those are expected to be present at /vendor in sphal namespace(as dynamic linker search at /vendor in sphal namespace). I added those two to EXTRA_VENDOR_LIBRARIES so that they will be shipped to /vendor. NFC is working now. But the problem is that the HAL load nfc configs from /system. I guess we cant haxx using as sed only work for the same size of string replacement. Replacing /etc with /vendor/etc will cause issues as address references will shift. I flashed phhusson GSI(Vanilla without Gapps) and it worked fine. Altogether current issues are
1. NFC HAL loads configs from /system.
2. Versioned VNDK using BOARD_VNDK_VERSION := current is not yet implemented. That means framework and vendor is not strictly isolated. Enabling the flag in BoardConfig enables the full VNDK support and restricts global headers. Android Oreo not strictly enforces isolation between /vendor and framework. This is strictly enforced in Android P and above. Vendor HAL dependencies on framework must be resolved.
3. Selinux is still in permissive mode.
INSTALLATION INSTRUCTIONS
Make a BACKUP of current /boot, /data and /system partition first partition using TWRP.
Flash the treble enabled TWRP located here.
Do a factory reset (wipe /data , /system, /vendor and /cache).
Flash the ROM.
Flash the Gapps.
Flash the custom magisk
NFC configuration files requires if any GSI is flashed.
Note : It is highly recommended to clean flash the ROM(Wipe /data, /system, /vendor /cache)
INSTALLATION FILES
RESURRECTION REMIX - BETA v1
CREDITS
mikeioannina for provinding fix for sensors.
abhishek987 for his custom magisk.
vovka36 for fp gestures.
Donations:
Help Supporting me. Any donations are highly appreciated.
Donate via PayTM
Sources:
Resurrection Remix
Kernel
XDA:DevDB Information
RESSURECTION REMIX-TREBLE, ROM for the Lenovo P2
Contributors
CodeElixir
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: Lineage
Version Information
Status: Beta
Beta Release Date: 2018-06-03
Created 2018-06-03
Last Updated 2018-06-03

CHANGELOG
What works:
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
GPS
NFC
Volte
DT2W
FP Gestures
Fastcharging
Known Issues:
One Key Slider
Permissive Selinux
May be more ...

Thanks a lot

Sounds like a fantastic project. Thanks very much.

Wooohoo

Treble???? Superrr....thanks bro

And... let's get started with the stupid q what's treble and if any advantages, just search google!

No need to be rude.
911-Future_Maker said:
And... let's get started with the stupid q what's treble and if any advantages, just search google!
Click to expand...
Click to collapse
Just a question. I ve heard of treble and I knw how it works for mainstream devices. I just dont understand how its being implemented in custom roms. If u cant give a proper answeru should just ignore and move on.

CodeElixir said:
What works:
Click to expand...
Click to collapse
Hi mate
Great work. Hats off to you. This is great mate especially your explanation in the beginning, this is simply great news. I congratulate you for being the first to release treble for kuntao publicly.
I have heard firelord was working on treble as well but I'm not sure how much work has been done as I don't know his GitHub . Maybe that can result in some improvements??
For who aren't sure what this means : treble Or simply treble is a way of arranging blobs (which are responsible for camera , sensors etc) separately from system. Thus when you need to update to New version of Android, you need to work from scratch. That means you need to import blobs and make changes again in blobs to be compatible with newer Android version. Also you need to update Android system version as well. Thus it delays development.
Treble works by separating these two so once a fully functional blobs are made, you never need to update blobs again and only need to update system as blobs will be compatible with all new version of Android
Thus faster updates and better camera quality like stock rom if treble implementation is from vendor already.
This means we can have treble for all Oreo ROMs but for Android Phone we need some more work to have a fully working treble because Oreo doesn't have very clear sense of separating blobs and system but it gives concept and works on enforcing it in Android P. Thus, for fully functional treble , we need to address the issues by development community to completely separate blobs.
venu44 said:
First to comment. I have a question. can someone explain whats the purpose of treble and why is there a custom twrp for it.
Click to expand...
Click to collapse
Get a lollipop. Grow up mate ! Already explained above. Discussion should be to the point and being first to post isn't an achievement unless you have something important to tell us.
Sutcliffe9 said:
Sounds like a fantastic project. Thanks very much.
Click to expand...
Click to collapse
Sohit5s said:
Wooohoo
Click to expand...
Click to collapse
balugudidiot said:
Treble???? Superrr....thanks bro
Click to expand...
Click to collapse

Hnk1 said:
Hi mate
Great work. Hats off to you. This is great mate especially your explanation in the beginning, this is simply great news. I congratulate you for being the first to release treble for kuntao publicly.
I have heard firelord was working on treble as well but I'm not sure how much work has been done as I don't know his GitHub . Maybe that can result in some improvements??
For who aren't sure what this means : treble Or simply treble is a way of arranging blobs (which are responsible for camera , sensors etc) separately from system. Thus when you need to update to New version of Android, you need to work from scratch. That means you need to import blobs and make changes again in blobs to be compatible with newer Android version. Also you need to update Android system version as well. Thus it delays development.
Treble works by separating these two so once a fully functional blobs are made, you never need to update blobs again and only need to update system as blobs will be compatible with all new version of Android
Thus faster updates and better camera quality like stock rom if treble implementation is from vendor already.
This means we can have treble for all Oreo ROMs but for Android Phone we need some more work to have a fully working treble because Oreo doesn't have very clear sense of separating blobs and system but it gives concept and works on enforcing it in Android P. Thus, for fully functional treble , we need to address the issues by development community to completely separate blobs.
Get a lollipop. Grow up mate ! Already explained above. Discussion should be to the point and being first to post isn't an achievement unless you have something important to tell us.
Click to expand...
Click to collapse
Sorry if I ve offended someone. I hope its cool and I was just excited. I ve done a lot of researching and even this explanation helps a lot. Thanks guys. Sorry again.

Can I flash GSI image of only a partition of any 64bit rom on top of that?

Wow roms are raining I love resurrection remix rom ?

Is the camera Raw working? And Gcam hdr+?

I have a small doubt can flash the treble twrp Kuntao as the same way as normal twrp flashing form ADB and fastboot terminal and this treble enabled twrp can be used for flashing other ROMs
Great work by the developer thanks for p2 support:good: TQ very much

Subho166 said:
Can I flash GSI image of only a partition of any 64bit rom on top of that?
Click to expand...
Click to collapse
Yeah

Woaah great, I hope there NFC work correctly

I tried to understand the issues but couldn't understand them completely. And wanted to know suppose this issues get resolved now..and when new Android version comes.. then the developer only needs to compile that with the blobs(sensors n all) ..that's it? that's what project treble is about? Sounds really exciting. I would like someone to make video about it ...would be great ...
Great work CodeElixir ........hope you resolve issues ..Thanks for the hardwork !

Dolby for oreo not working. Everything else is perfect. Dark video bug is present but playback is smooth.

anilyarki said:
Dolby for oreo not working. Everything else is perfect. Dark video bug is present but playback is smooth.
Click to expand...
Click to collapse
he can you make a video about how you flashed it ?

nareshfree said:
Is the camera Raw working? And Gcam hdr+?
Click to expand...
Click to collapse
Yeah even 4k hdr+ is working><

[ROM][12.1] LineageOS 19.1 for griffin [UNOFFICIAL][18 Feb]

Code:
Changelog:
18th February:
February security patch
add custom dns options
add options to set renderer
double tap to sleep
drop misc debugging
27th January:
January security patch
Add signature spoofing
Fix fingerprint
Bork encryption
Fix misc kernel vulnerabilities
18th December:
CLEAN FLASH MANDATORY
NEW RECOVERY FOR DECRYPTION NEEDED
December security patch
fix encryption
uprev keymaster
exclude audiofx
update gps configs
04th December:
enable secure boot
disable rounded corners
fix buggy lockscreen
12th October:
October security patch
remove warning on each bootup
fix network monitor
add updater strings
some sepolicy changes (not enforcing, but a step in the right direction)
21st September:
initial userdebug build
enable zram
update media codecs
aggressive write caching
initial release

this is my logcat sir. just wanna report again. it getting hot randomly when i doesnt use it.

Thx for reporting your issue, but according to your logs it is chrome/chromium that keeps crashing...

Nvm, there is a lot going on, which I dont understand...
*but gapps are in there a lot.

@SirRGB i use mindthegapps 🫠🫠 i disable many builtin apps. i change jelly browser to chrome, aosp camera i change with google camera from store. nvm? do you mean my network? if yes, my network provider going crazy yesterday, i lose many many times lte network. as you mention that chrome going crash, i never get a notification my chrome force close or anything. but right, i fell little bit hotter after installed chrome. and last night griffin get hot when charging reach 80%. its weird. this is all happening after i dirty flashed 2nd build. well, i'll change the gapps with clean flash and i'll report again. thanks for helping me.

iam so sorry dissapoint you. but after i posted last comment. my network totally gone. really gone. even i searching it manualy. no one network showing up. nothing. so i decide to flash to stockrom via fastboot to see what happen with my. and surprise my network come after done.

update:
i can confirm that network problem on my griffin is not from LOS 19.1. i've tried on many custom rom such /e/, LOS 18.1, 17.1. When my network is gone. It cannot searching anymore. but, reboot system can solve the problem. IDK why, but i never faced this problem on custom rom without vendor e.g OMNIROM 9 or stockrom.

Ok, good to know. I didnt actively use it and just tested the basic functions...
I really hope you had a backup of efs/persist/modem since that could be your issue...

qwek said:
update:
i can confirm that network problem on my griffin is not from LOS 19.1. i've tried on many custom rom such /e/, LOS 18.1, 17.1. When my network is gone. It cannot searching anymore. but, reboot system can solve the problem. IDK why, but i never faced this problem on custom rom without vendor e.g OMNIROM 9 or stockrom.
Click to expand...
Click to collapse
my other moto z (bootloader locked with stock 8.0 rom) also have the similiar same problem like you: random and sudden signal missing, and restart to fix it, IDK but i think its some hardware issue for my moto z, because with my daily moto z (bootloader unlock, carbon rom 10) never have the missing signal problem, and i have try lots of custom rom

blinkerss said:
my other moto z (bootloader locked with stock 8.0 rom) also have the similiar same problem like you: random and sudden signal missing, and restart to fix it, IDK but i think its some hardware issue for my moto z, because with my daily moto z (bootloader unlock, carbon rom 10) never have the missing signal problem, and i have try lots of custom rom
Click to expand...
Click to collapse
what is your sim card bro? i use crazy axiata, when every 2.00am network always gone until 30 minutes. i think its radio band, but when i try to check, its only automatic and US.

SirRGB said:
Ok, good to know. I didnt actively use it and just tested the basic functions...
I really hope you had a backup of efs/persist/modem since that could be your issue...
Click to expand...
Click to collapse
i think so. first i flash fw with retail then flash customrom, then i change fw with EMEA APAC region and flash custom rom again, issue still there, even i change other custom rom.

qwek said:
what is your sim card bro? i use crazy axiata, when every 2.00am network always gone until 30 minutes. i think its radio band, but when i try to check, its only automatic and US.
Click to expand...
Click to collapse
I'm using telkomsel, also if I'm remember correctly, re-insert the sim card will fix this sudden random signal missing, the only thing that i havent test: using the 2nd simcard slot

update:
using more than one week. i change chrome with bromite and use nikgapps. idk but my network problem has gone. but im stick with 4g only now. no phone calls no problem i never use it. i know eta is not allowed. but i hope for the update. latest build deserve official status.

3.18 and below cant get official lineage 19/20/..., so that wont ever happen unless someone backports bpf.
I still dont know selinux and dont know if it is worth it to investigate...
Havent changed anything source wise, so rebuilding wouldnt fix anything. Might do another build with the new security patch once it is released.
Thx for reporting and using it
Feel free to report any issues and share logs.

SirRGB said:
3.18 and below cant get official lineage 19/20/..., so that wont ever happen unless someone backports bpf.
I still dont know selinux and dont know if it is worth it to investigate...
Havent changed anything source wise, so rebuilding wouldnt fix anything. Might do another build with the new security patch once it is released.
Thx for reporting and using it
Feel free to report any issues and share logs.
Click to expand...
Click to collapse
what about mokee? i think they are accept. i saw griffin still got update but no maintainer. honestly, i dont have any skill about coding or anything. just appreciate your amazing work. you very kind, still care to our device.

I think they mostly buildbot .i.e. they take the official lineage trees and build based on that. However I can go for arrow os community. In that case I dont have to worry about sepolicy for now and we all can enjoy monthly ota updates...

found a patch, that makes the network monitor work, will be included in the next build...

SirRGB said:
found a patch, that makes the network monitor work, will be included in the next build...
Click to expand...
Click to collapse
glad to know that. i saw many new commits. i think you prepare something bigger. alright, just waiting. and testing. iam ready for it.

qwek said:
glad to know that. i saw many new commits. i think you prepare something bigger. alright, just waiting. and testing. iam ready for it.
Click to expand...
Click to collapse
If you meant my device tree that was probably just my rebase i.e. I cleaned up the commit history a little.

[UNOFFICIAL][ROM][11] LineageOS 18.1

RESERVED
Changelog 20.06.2023:
• Updated to June ASB
• Improved system smoothness
• Reduce the amount of logging and tracing
• Incall vibration options
• User build
Note:
• User build is made with userdebug sepolicy and some edits to make the recovery functional, this is purely to lower the amount of logs and overhead from the system, no security gains
Changelog 12.03.2023:
• Switched to OSS vendor
• NoName V7 (4.14.307)
• Implemented screen off FOD
• Improved FOD speed
• Improved Wi-Fi range and stability
• Portrait, 48MP and 32s shutter speed now fully work in stock camera
• Fixed multiple logspams
• Added working FM radio
• Re-added OTA updates
Note:
Clean flash is mandatory.
Changelog 18.02.2023:
• Updated to February ASB
• NoName V5 (4.14.305)
• Minor fixes and performance improvements
Changelog 13.12.2022:
• Build is now signed with private keys
• Updated to December ASB
• Switched to NoName kernel
Note:
Due to the new signing keys i used, clean flash is necessary if coming from the October build
I'm currently saving for a new PSU for my PC (goal reached, thanks to everyone who donated <3)
If you like my work consider supporting me on Ko-Fi

Skyblueborb said:
Stock camera included
Click to expand...
Click to collapse
If this works well, this ROM will easily become my goto for my phone. Thank you! I will try it.
Skyblueborb said:
Google apps are pre-included in the GMS variant
Click to expand...
Click to collapse
Are the gapps the only difference between GMS and Vanilla, or is there more to it?

Typhoon_Master said:
Are the gapps the only difference between GMS and Vanilla, or is there more to it?
Click to expand...
Click to collapse
Just gapps, no more differences

Thank you very much for the rom. It's the only up to date one without gapps. I've used it for three weeks now without any problems. I've patched the service.jar so signature spoofing is supported. (Correction: Signature spoofing is supported out of the box for this rom). After installing microg, safetynet can be passed easily with Universal SafetyNet Fix. I'm hoping for updates
P.S. Stock camera is realy nice and battery life is superb.

I have to thank you too. I am using this since one month now and ...
it is rock solid
hassle free included stock camera app
vanilla option for use without gapps (i use it with microG)
slim and free of bloatware
free of xiaomi telemetry
battery life is through the roof
5/5 would recommend and donate
also best phone i bought for about 200 bucks, and hopefully will serve me some more years to come.

donuts12345 said:
Thank you very much for the rom. It's the only up to date one without gapps. I've used it for three weeks now without any problems. I've patched the service.jar so signature spoofing is supported. After installing microg, safetynet can be passed easily with Universal SafetyNet Fix. I'm hoping for updates
P.S. Stock camera is realy nice and battery life is superb.
Click to expand...
Click to collapse
There are newer updates (December patch, February patch will come later this month) , i just need to post them here on XDA (i usually release it on telegram), I'll probably update this post for February build

donuts12345 said:
Thank you very much for the rom. It's the only up to date one without gapps. I've used it for three weeks now without any problems. I've patched the service.jar so signature spoofing is supported. After installing microg, safetynet can be passed easily with Universal SafetyNet Fix. I'm hoping for updates
P.S. Stock camera is realy nice and battery life is superb.
Click to expand...
Click to collapse
Also I'm pretty sure i added signature spoofing by default, didn't mention it here

Typhoon_Master said:
I have to thank you too. I am using this since one month now and ...
it is rock solid
hassle free included stock camera app
vanilla option for use without gapps (i use it with microG)
slim and free of bloatware
free of xiaomi telemetry
battery life is through the roof
5/5 would recommend and donate
also best phone i bought for about 200 bucks, and hopefully will serve me some more years to come.
Click to expand...
Click to collapse
I can confirm your point, totally.
Nowadays this is probably the most solid cusrom available for Laurel, very accurate and fast FOD recognition, everything works properly...battery backup is also spectacular.
Only 2 little CONS (maybe just for me):
~there's no present FM radio app.
~poweroff alarm not working.
In general if you need MI A3 as primary device for daily driving i suggest this (I'm on 13 December release with no name kernel) build over each other, thanks to developer and his amazing work.
Sorry for my English.

autokoise said:
I can confirm your point, totally.
Nowadays this is probably the most solid cusrom available for Laurel, very accurate and fast FOD recognition, everything works properly...battery backup is also spectacular.
Only 2 little CONS (maybe just for me):
~there's no present FM radio app.
~poweroff alarm not working.
In general if you need MI A3 as primary device for daily driving i suggest this (I'm on 13 December release with no name kernel) build over each other, thanks to developer and his amazing work.
Sorry for my English.
Click to expand...
Click to collapse
the fm app i know, i didn't really bother fixing it, i added it for one build but it was completely broken, if i spent more time on it i probably could get it working; what do you mean by poweroff alarm?

I know too the problem about the offline radio app for mi a3, but this is not a basic app for the daily usage.
Poweroff alarm is a specific app (present on every lineage official release for xiaomi devices) which restart the phone from the power off state (I powered off my phone every night during sleep hours) immediately before the alarm ringing.
Thanks again for your much appreciated work on this amazing device.
Pardon for my English.

Skyblueborb said:
Also I'm pretty sure i added signature spoofing by default, didn't mention it here
Click to expand...
Click to collapse
Yes signature spoofing permission is added by default. Sorry, my fault.

New feb update pushed, hope you guys enjoy it

Made an account just to show appreciation on how amazing this rom is. I thought my phone was a goner now it feels brand spanking new.
One issue though, adb sideload does not work in recovery in february update. Is this known or does it only happen to me?

wenekar said:
Made an account just to show appreciation on how amazing this rom is. I thought my phone was a goner now it feels brand spanking new.
One issue though, adb sideload does not work in recovery in february update. Is this known or does it only happen to me?
Click to expand...
Click to collapse
The issue is known, if you are facing it flash this in recovery (you can flash the recovery img in fastboot, then the kernel and it should work just fine, or if you're rooted flash it via fkm or hkf)
I didn't want to build this release a third time to fix it (in the first hours the links pointed to a build with broken camera due to the fact that i had to resync the ROM sources and forgot to remove one thing)
Glad you enjoy the ROM

New update pushed, a lot of good changes, hope you guys enjoy it

Top class release, finally working also offline FM radio app, and PowerOff alarm...thanks for your work...I very appreciate it!!

Still the best rom I've ever used on my A3 after Paranoid. Absolutely loving it! Can't wait for the next update!

I've finally decided to leave stock A11 behind and tried this rom today
unfortunately android auto does not work, it needs to be installed as a system app (communication errore 22)
i've used the gms variant -
should i retry with the vanilla One and install a differenti gapps package?

liPillON said:
I've finally decided to leave stock A11 behind and tried this rom today
unfortunately android auto does not work, it needs to be installed as a system app (communication errore 22)
i've used the gms variant -
should i retry with the vanilla One and install a differenti gapps package?
Click to expand...
Click to collapse
That should work, try something like opengapps or nikgapps, that should have variants with android auto installed as system, or you can root and make it a system app yourself

Database Users

welcome