Develop Bugs

[ROM][NMF26Q][7.1.1][BETA 5] AOSP Nougat-7.1

Android Open Source Project Nougat For Xperia M​
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! 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.
*/
This rom is based on Android Nougat 7.1 source (android-7.1.1_r6)
I have only made changes that needed to support our device other then that it's pure AOSP. it has no custom features to provide you stock android experience.
Device-specific source code:
Device
Kernel
Vendor Blobs
Discussion thread -->
What's working:
So far i have tested:
RIL (Calls, SMS, Mobile Datal)
Dual sim on Xperia M dual
Display
Camera & Camcorder
Audio and video
Wifi
Bluetooth & Bluetooth Audio
OpenGL rendering
Sensors (accelerometer,compass,light,proximity)
Sdcard
Auto brightness
Notification led
Storage
GPS
Mtp/ptp working same as 6.0
NFC
Note:
It's entirely possible that features not used by me (nor the people I've asked to test) are broken, but overall the device should be usable. You have been warned.
This is BETA so don't treat this as stable version.
AOSP is only for 4.3 baseband. If you are on 4.1/4.2 baseband/firmware then Follow this instruction
TWRP FOTA recovery is recommended for installing aosp, follow this thread for instructions
Download:
BETA 5: https://www.mediafire.com/?ltwb5qgqd22ckfi
For dual sim users: Flash this patch get dual sim working https://www.mediafire.com/?aag77t1w7bi7gg0
Install instructions:
Before you install make sure you are on 4.3 firmware 1st with your bootloader is Unlocked and a TWRP recovery installed. if you haven't installed recovery then flash boot.img from this rom zip via fastboot.
boot into recovery
Wipe data and cache
Flash the rom and gapps zip
Reboot
Upgrading from earlier version:
Boot into Recovery
Flash the rom and gapps zip
Reboot
Reporting bugs:
Before Reporting bugs make sure you
Read "note" section
Using stock kernel
Not installed any mods/tweaks - if you have installed mods like xposed you can't report bug
Not modified system files
Checked the posts below for a solution / fix
Read the last 10 pages of this thread for a post with a similar problem
Backup, reflash with a full wipe (do this if mods like xposed is installed) and check if the bug is still there
provide logcat,kmsg. if you reporting radio problem then provide radio log.
Screenshots:
{
"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"
}
Credits:
All developers who is working on sony
Code Aurora Forum
CyanogenMod
XDA:DevDB Information
AOSP Nougat for Xperia M, ROM for the Sony Xperia M
Contributors
PecanCM
Source Code: https://android.googlesource.com/
ROM OS Version: 7.x Nougat
ROM Firmware Required: Stock 4.3 Firmware
Version Information
Status: Beta
Created 2016-08-26
Last Updated 2016-12-21

Changelog
BETA 5 21-12-2016
Updated Platform sources to android-7.1.1_r6(NMF26Q)
Fixed clock app world button force close
Fixed more sepolicy denials
Linux Security fixes
Added missing STK to build
Switched to nougat aosp audio hal
Switched to new xml audio policy configuration
Misc cleanup/fixes/updates
BETA 4 20-11-2016
Updated Platform source to android-7.1.0_r7(NDE63X)
Fixed Video recording "jumping"
Fixed invalid number error
Fixed gapps setup wizard force close
Linux Security fixes
Switched to source built NFC firmware
Updated apn conf from bullhead
Updated adreno renderscript blobs from msm8909 nougat
Misc cleanup/fixes
BETA 3 26-10-2016
Updated Platform source to android-7.1.0_r4(NDE63P)
Attempt to fix RIL with SuperSU on dual sim devices
Linux security fixes
Audio HAL updates from nougat branch
Time service updates
Update other blobs
Misc cleanup/fixes
BETA 2 21-10-2016
Updated Platform source to android-7.0.0_r7(NRD91D)
Security fixes
Time service fixes
Added support for more webviews
BETA 1 19-09-2016
Fixed camcorder
Fixed headset button
Attempt to fix network mode selection on dual sim
ALPHA 3 10-09-2016
Updated Platform sources to android-7.0.0_r4(NRD90S)
Dual sim is now supported
Fixed almost all selinux denials
Fixed FOTA recovery
Fixed Boot led
Security fixes
Added backlight and battery percentage support to offline charging
Updated widevine blobs for Nougat
- apps like netflix/google movies will work now
Updated time-service blobs
Updated camera related blobs
- no more text relocation
Update Power menu
- Added reboot option
- Added airplane mode
- Added ringer modes
ALPHA 2 29-08-2016
Fixed lots of Selinux denials
Fixed stock music app force close
Updated twrp recovery to latest version
Fixed qcril logging (no more diag spam in logcat)
Updated media codec from caf
Security fixes
ALPHA 1 26-08-2016
Initial release

FAQ
Q: Why no root access?
A: This is AOSP rom, not CyanogenMod.
Q: I can't find external sdcard in /ext_card, Why ?
A: Go to /storage you can find there
Q: Where is old browser ?
A: Removed from nougat and replaced with simple shell browser, Use 3rd party browser for all features.
Q: I can't find live wallpapers ?
A: Removed from nougat.

Thank you @PecanCM.
You are really fast. :highfive::highfive:

Yay! FINALLY! We love you Ron
Review: Processing...

Awesome @PecanCM!
Thanks for bringing AOSP Nougat 7.0 to xm!
Smooth and functional for an alpha release!

Thank you!! Gonna test it now!

Thanks for new taste of Android!
Tips:
- Launching persistent TWRP not supported. Only built-in 2.8
So if you have adopted sdcard you can't restore backup.
To fix flash CM13 kernel.
- OpenGapps for 7.0 here
- Feature spotlights here
- File manager in Settings > Storage finally can install APK's, useful for first boot.
- To use 2 apps at same time hold and drag thumbnail in Recents
- Double-tap on Recents works like Alt+Tab (like long press in CM)
- In dev options new option to force move all apps on adopted storage

Bonoboo said:
- Launching persistent TWRP not supported. Only built-in 2.8
So if you have adopted sdcard you can't restore backup.
To fix flash CM13 kernel.
Click to expand...
Click to collapse
FOTA TWRP (recent, most likely 3.0 only) is known & fixed,
logo loops on and on, nothing opening right?
Thanks for confirming.

Thanks a lot, Ron!
GPS is works (tested in Google Maps)

Adrian DC said:
FOTA TWRP (recent, most likely 3.0 only) is known & fixed,
logo loops on and on, nothing opening right?
Click to expand...
Click to collapse
I hadn't adopted sdcard, sorry.
Just noticed old TWRP and therefore possible problem.

Bonoboo said:
Thanks for new taste of Android!
Tips:
- Launching persistent TWRP not supported. Only built-in 2.8
So if you have adopted sdcard you can't restore backup.
To fix flash CM13 kernel.
- OpenGapps for 7.0 here
- Feature spotlights here
- File manager in Settings > Storage finally can install APK's, useful for first boot.
- To use 2 apps at same time hold and drag thumbnail in Recents
- Double-tap on Recents works like Alt+Tab (like long press in CM)
- In dev options new option to force move all apps on adopted storage
Click to expand...
Click to collapse
can you please share cm13 kernel?

Look likes our XM always infront of the other ..

Tried!
Everything's working fine, except:
1. Camera not working.
2. No live wallpapers.
3. Music app crashing every time.

Does anyone have success flashing GApps? On Opengapps wiki is stated that it needs additional ROM patching to disable APK Signature Scheme V2.
---------- Post added at 22:47 ---------- Previous post was at 22:44 ----------
BTW, if FOTA recovery is not working, I can repack the boot image with the latest TWRP 3.0.2-1.

cucumber09 said:
Does anyone have success flashing GApps. On Opengapps wiki is stated that it needs additional ROM patching to disable APK Signature Scheme V2.
---------- Post added at 22:47 ---------- Previous post was at 22:44 ----------
BTW, if FOTA recovery is not working, I can repack the boot image with the latest TWRP 3.0.2-1.
Click to expand...
Click to collapse
i installed GApps, but with error like "command 'log' doesn't exist"
App work fine, but Google Play Services is crashes when i trying add Google account.
And when im rebooting to recovery via terminal, its entered to twrp 2.8 (from this rom) not to fota sadly.

Is it based on 3.4 kernel?

verma.arun833 said:
Is it based on 3.4 kernel?
Click to expand...
Click to collapse
Yes, like all ROMs for our device (and maybe for our entire SoC family).

Can any user test WiFi hopspot for me. And also if pokemon go will work without bugs (sorry I have no time to DL and test myself ATM)

So here are results of my brief testing:
- It booted VERY FAST as there is no ART cache compilation after every update, cache is generated on-the-fly combining JIT and AOT compilation. BTW, not only first boot was fast but the latter ones too, much faster than CM13.
- First boot with Opengapps Pico for 08.26 led to Setup Master's FCs at some moments, yet after some painful experience I've succeed adding Google account and even restoring my apps and settings, which was quite surprising (I was amazed when noticed my ringtone being restored to that from CM13).
- 3G is not working, at least for me. Only EDGE.
- Getting root with the current version of SuperSU appears to be impossible, at least for our device.
- Phone seems to be less responsive, but maybe that's just me, because I regularly use it overclocked to 1.4 GHz.
- TWRP 2.8.0.0 and not working FOTA recovery, seriously? I was forced to repack boot image with the TWRP 3 (just quickly grabbed that from NUI as I'm lazy to repack recovery ramdisk for using in boot image). Some report it working but for me it always booted to the built-in TWRP, both by Vol- and Vol+. BTW, I can upload repacked boot image tomorrow (it is on my personal laptop, I'm writing this from my work one).
I would certainly use it as daily driver if there were root and NUI kernel available. It is very stable for such an early alpha (gosh, Ron started working on it a couple days ago as sources were published) and such an old phone (it debuted 3 years ago), we are very lucky to have so custom-friendly hardware and such a talented developers as Ron and guys working on msm8960 board (another reason I think is that there were no any bringing-pain-in-the-ass changes like ART in 4.4/5.0 and adoptable storage in 6.0). Great work, PecanCM!
I'll continue my testing tomorrow and revert to CM13 later until new SuperSU and NUI are released (or maybe forever if I'll buy new device soon).

[ROM][SNAPSHOT][7.1.2] AOSP Nougat for Xperia X Performance

{
"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.
*/
Requirements
Xperia X Performance : Meant for F8131, others to verify and would need changes
Bootloader : Unlocked bootloader to flash new bootimage
Stock version : Recent Nougat Stock release (39.2.A.0.xxx)​
Downloads Links
AOSP 7.x Nougat (Unlocked Bootloader) :
Test : https://mega.nz/#F!D98GiJrA!trPA7QZGkLEju5Qv_cz-Og
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM64, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
MultiROM TWRP or Normal TWRP : https://forum.xda-developers.com/showpost.php?p=69036502&postcount=2
About AOSP : Repositories available on https://android.googlesource.com/
About GApps : Flash the GApps before the first boot. If not, a clean flash is recommended.​
Flashing and updating
AOSP clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to lose data)
- Flash the AOSP ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
AOSP update / upgrade :
- (Information) Don't wipe anything unless you want to
- Flash the latest AOSP ROM zip from the Recovery
- (Optional) Flash the GApps if you want to, otherwise preserved.
- (Optional) Every additional zip you want to flash
- Reboot​
About the builds
Development project : https://github.com/AdrianDC/aosp_development_sonyaosp
Device tree : https://github.com/AdrianDC/device-sony-dora/commits/master
Kernel sources : https://github.com/AdrianDC/kernel-sony-msm/commits/aosp/LA.UM.5.5.r1
Vendor blobs : http://developer.sonymobile.com/open-devices/list-of-devices-and-resources/​
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​
Q&A - FAQ
Q : Is root access included into AOSP ?
A : No but you can root with SuperSU.
Q : Is the ROM suited for daily usage ? With GApps too ?
A : Not yet, work in progress. OpenGApps recommended.
Q : I see errors during the installation, is it normal ?
A : If it is E:unknown command [log] , ignore it for now
Q : Where can I change the Quick Tiles and Status Bar ?
A : Long press the Settings icon in the notifications drawer.
> You will have access to the SystemUI Tuner from Marshmallow.
Q : The AOSP Keyboard does not support swipe gestures ?
A : UNTESTED YET: Unfortunately the sources for swipe gestures are not available
and Google still requires their prebuilt library to be there for AOSP Keyboard.
Download the following libjni_latinimegoogle.so API 23 from OpenGApps
and push it to /system/lib/libjni_latinimegoogle.so using root access,
or use my one-time install zips : https://mega.nz/#F!ThEAkCRa!byhSwuoTbf6lnC1JxgKrig.​
AOSP available for Dora also thanks to :- The Android Open Source Project
- The Sony Open Devices Program​
XDA:DevDB Information
AOSP Nougat 7.1.2, ROM for the Sony Xperia X Performance
Contributors
Adrian DC
Source Code: https://android.googlesource.com/
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Snapshot
Created 2017-01-29
Last Updated 2020-08-15

Reserved
FEATURES AND ISSUES
Official platform functionality list: http://developer.sonymobile.com/open-devices/current-platform-functionality/
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- WiFi : Ok
- Bluetooth : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok, only Ext4 support missing from AOSP
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Fingerprint sensor : Partially / broken
- AOSP sensors : Ok
- Touchscreen : Ok
- FM Radio : Broken
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Work in Progress
- Graphics : Ok, Work in Progress
- 3D Rendering : Ok, Work in Progress
- Clock : Ok
- Offline Charging : Broken, boots to Android
- USB OTG : Broken
- Encryption : Status unknown
- SEPolicies : Permissive
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds

Reserved
Recent branches commits
Devices + common projects: https://github.com/AdrianDC/aosp_development_sonyaosp/branches/all
Changes log (https://developer.sonymobile.com/open-devices/latest-updates)
09/06 : New release on Android 7.1.2_r17 sources (June CVE patches), new blobs (v05). Improved camera and stability / Fixed video recording
24/04 UNRELEASED : New release on Android 7.1.2_r2 sources (April CVE patches / Pixel), new blobs (v04). Camera minor hardware risk.
13/03 : New release on Android 7.1.1_r25 sources (March CVE patches / Pixel)
25/02 : Maintenance release with update device and kernel sources
15/02 : New release with updated blobs (AOSP_N_MR1_DEV_v03)
11/02 : New release on Android 7.1.1_r20 sources (February CVE patches / Pixel)
29/01 : Initial release for Dora, Android 7.1.1_r9
Original AOSP 7.1 sources with following relevant additions
Build: Backup tool full support (GApps)
Build: Minor improvements for development purposes
Core: Disabled flash_recovery service from AOSP
Music: Minor fix to permissions
Toybox: Support for init_sony boot selection
Current local manifest
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://android.googlesource.com/platform/manifest -->
<manifest>
<!-- See https://github.com/AdrianDC/aosp_development_sonyaosp -->
</manifest>

Hi @Adrian DC, should this be flashed from nougat only?
I flashed from M (.297) last night and roughly five minutes after the amazingly fast boot up, I had a system freeze, had to do power/volume combo to restart. Also had an issue with twrp not responding to touch at all. Im now back on N (.386) and wondering if I should flash from here. Thanks.

Yeaa! Finally some progress on roms for my x performance! Was looking for a ss or htc already

Yes! nice one. will be checking this out!

Great!!! Just wanna know hows the camera quality, and is it stable to use as daily driver?

Is support for dual sim(f8132)?

I want to install this as my primary rom but it is always asking me for a password after the installation. I have performed a clean install and I also wiped the dalvik/cache but nothing.
Is there a way to bypass this?

13lizzard said:
I want to install this as my primary rom but it is always asking me for a password after the installation. I have performed a clean install and I also wiped the dalvik/cache but nothing.
Is there a way to bypass this?
Click to expand...
Click to collapse
Enter recovery and wipe data, dalvik cache and cache at least 3 times. Then reboot.

There's no 3 times cache wiping or such way to fix it.
You have to do a factory reset to have the data partition formatted instead of 'wiped',
that way the encryption sector is properly erased.

Post screenshots

Why 7.1.2 is not out yet?

patrick4a17 said:
Why 7.1.2 is not out yet?
Click to expand...
Click to collapse
Because we're waiting for a new set of vendor blobs.
The current ones do work, but the camera actuator makes a small noise, so not taking any risk with a public build.

When are you going to update? Expect beta or stable version

hellyjia said:
When are you going to update? Expect beta or stable version
Click to expand...
Click to collapse
You have my answer in the previous post .

Consult, F8131 can brush F8331 Rom? Both hardware seems to be the same

Will there be a recent update?

The fingerprint sensor is broken? Can it be used for screen unlock??

ANT+ works?

[JDCTeam][TREBLE][v6 RC2][Gemini] The Full Treble support project

{
"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"
}
The Full Treble Project for MI5 Gemini
Brought to you by Jflte DevConnection Team​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We're 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 TREBLE
* SUPPORT 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.
*
*/
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
Gemini hardware vs Treble implementation:
Gemini is an ARM64 and A-ONLY device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-ONLY system images.
Available GSI downloads:
Up today, thanks to @phhusson and other devs, are available a bunch of Android 9.0 system images that can be flashed on Gemini.
You can find these Gsi at the following links:
- ANDROID Q (Gsi)... Is just a preview... but it works on our Mi5!!
- Phh AOSP 9.0 (Gsi).
- Resurrection Remix v7.0 (Gsi).
- LineageOS 16.0 (Gsi).
- HavocOS v2.0 (Gsi) (Use A only).
- ViperOS v6.0 (Gsi) (Use A only).
- JDC AOSP 9.0 (PURE AOSP Gsi, built from sources, just for testing purpose, no gapps support for this preview version).
- GSI & sGSI List page
Treble implementation and download:
JDCTeam is working from latest months of 2017 to implement on Gemini (un-supported from producer) the full support of Treble.
Thanks to @sir mordred, we reached on MI5 the full working status... from v5 we moved to full versioned vndk v28 (aka PIE support... and Q ready!).
NOTE: just to be clear, it's a work in progress development...
We tested with some available Gsi and we put over here some links to these images.
We are sharing a TWRP flashable zip that include vendor and boot images (flash only through TWRP 3.2.3-0 Official).
NOTE: ONLY with TWRP 3.2.3-0 version is possible to handle the treble flash!​
How to use:
Download the TREBLE zip provided here: Mediafire
Download a GSI image (Remember: ARM64 and A-ONLY version)
Reboot to recovery (TWRP 3.3.1-0 REQUIRED)
Clean the device (wipe Dalvik/Cache/System/Data partitions)
Flash Treble gemini zip
Flash the GSI system image you wish to use
Reboot
---> Video on How to install <---
Screenshots:
Youtube review: (To Be Updated when new links available)
- ANDROID Q Gsi on MI5 (How to Install) ---> Click here to play the video
- ANDROID Q Gsi on MI5 ---> Click here to play the video
- RR v7.0.0 Gsi on MI5 ---> Click here to play the video
- PHH AOSP 8.1 Gsi on MI5 ---> Click here to play the video
- AEX 8.1 Gsi on MI5 ---> Click here to play the video
What's working (... and not working):
The development is now @ an RC status (this is not a rom)... you have the possibility to have a look and test the phone with a GSI rom... let us know what does not work (not related to the GSI itself)!!
Issue reporting:
We already say that this is not the place to report issues or bugs ROM related... but in any case a bug encountered can be linked to the treble support not perfect or missing supported features... be free to post about issues you encountered, and please provide logs with the description of the issue. We will check the logs to understand the reason, and in case of fixes to be done, we will update on post#3 (MISCELLANEA) a kind of todo list for us and for users as a "bug list"... but the meaning is "what has to be checked/fixed to get a better treble support for future".
Any question?
If you have any question about, please check first on the post#2 (FAQ) to see if your question has already an answer... if not, post in the thread and we will give you informations.
Sources
GitHub
Social
YouTube: JDCTeam TV
XDA News: Read article
Credits
JDCTeam
LinageOS
Google
MI5Devs
Special thanks:
@sir mordred (developer)
@musabcel (for his test support)
Team Codefire - JDCTeam-Build03
XDA:DevDB Information
GEMINI Full Treble support project, ROM for the Xiaomi Mi 5
Contributors
smeroni68, sir mordred, mzo, ktulu84
Source Code: https://github.com/Project-Treble-Mi5
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest available
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v6
Stable Release Date: 2019-03-16
Created 2018-03-10
Last Updated 2019-06-27

FAQ Section...
This is the FAQ (Frequently Asked Questions).
Have a look here before asking in the thread... in the worst case you will not find the answer you are searching!
If this section is useful for most users needs, I'll be glad to continue investing time to update this Q/A list!!​​
Q1:Fingerprint wake/home button works?
A: Yes, now we have the complete support and this feature is available on standard GSI roms (treble support is ready for it)
Q2: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img,system and vendor partitions.
Q3: If I revert to a Custom rom, what I need to do to restore treble support?
A: Just flash the Treble zip through TWRP as the first time. Treble support need boot.img and vendor.img to be installed into the phone... nothing more... nothing less...
Q4: Phh GSI rom is quite poor in functionality. Why?
A: The purpose of Phh GSI AOSP rom is not to be a custom/featured rom. It is an experimental project that is born to have a common rom (better to say the same system.img) usable on many devices with treble support.
This support can be native, acquired after an Oreo original update or as we have done a custom integration on an "unsupported" device.
The meaning today of using a GSI rom is not to be a perfect rom for dayly use... or let's say, it can be a dayly rom only for users that like pure vanilla code.
In future we hope that many others custom roms will move to be a GSI (as JDC will try to do), so we will have the treble base to use these new project also on our devices.
Q5: If a new version of treble support is out, did I need to flash it or not?
A: Our project is on the way. This means that if is available a new update from us, it is for sure an enhancement with more support of feature or fixes.
In case you will need to install a GSI rom, check always here if there is any new version and get it.
In case you are running a custom rom without treble support, DO NOT update with treble flash, because most probably you will break your current installation.
Treble flash is 100% safe from the phone point of view... isn't safe for your current installation!! Why? Mainly because your current boot.img will be overwritten with treble support... 99% you will get a bootloop with a not treble rom!
Q6: How to get ROOT on phh gsi?
A: Firstly download the phh-gapps-su image. After installation, go to the market and install "phh superuser" app to manage the su access for the apps that need it. In the other cases, you can flash from TWRP the correct Magisk zip to gain root.
Q7: Where I can find the GSI images available?
A: Have a look in the OP post over here... there you can find the available ones. In any case here the LINK to the Treble Enabled Device Development section on XDA or here on GSI & sGSI List page
Q8: Everytime I entered the password, it says Decryption Unsuccessful!
A: You have internal SD encrypted. If after MIUI stock, you haven't FORMATTED the internal SD (FORMAT is not WIPE... Format will erase all data and files from the phone, so you must know what you are doing before formatting), the phone result as encrypted, so the rom is asking the password to decrypt the datas... Decryption Unsuccesful clearly states that the decryption procedure is not working. Post about the issue on the GSI rom you are using and provide logs to the developer to help digging the problem... if Developer will answer that encryption is not supported, you can only do one thing: backup all your data, files and pictures on an external storage (eg. a PC) and procede with a FORMAT DATA from TWRP to "destroy" the encryption and "free your phone from it"!
Q9: Is Google Camera working on Gsi?
A: Yes. But remember you need to install gapps package to let gcam works as it should.
We tested Gcam up to v6.1.021 on AOSiP Gsi. If you have greenish selfies pics, go in the Settings -> Fix ->and enable the fix for Front Camera and reboot. For SlowMotion, set 120fps.
Q10: Why can't flash a micro gapps and only pico is flashable?
A: If you get an error of Insufficent space on system partition, you need to resize the partition. Do in this way:
Flash the SYSTEM.IMG you wanna use (select a Vanilla based one)
Reboot to RECOVERY
MOUNT the SYSTEM partition
Go in WIPE menu -> ADVANCED WIPE -> select SYSTEM from the list and press the button REPAIR OR CHANGE FILE SYSTEM
select RESIZE FILE SYSTEM
than SWIPE to execute the command...
in case of error (you will see in red), repeat the RESIZE until it goes completed (Resizing... Done)
After this operation, the system partition will be resized to his maximum dimension (on Mi5 is around 2992MB)
before the installation of gapps package, do a REBOOT to recovery and after MOUNT the SYSTEM partition (check that it is really mounted)
Now you can flash the micro gapps without problem.
Q11: Is there any Magisk version working on Treble gsi?
A: Yes, you need to get v18.1 version or newer with treble support (check around).
Q12: VoLTE is working[/B]?
A: Yes. Install this ims.apk to use it!
Q13: ADB Logs are needed in case of Issue reporting...
A: In case you need help and want report an issue (eg. a boot problem), we need logcat of the phone. Just as sample, we report here what to do (but you must able to do by yourself... we are not giving help on how to do...)
prepare a PC (with adb package to support debug via usb connection)
flash on the phone our treble and the GSI image (just these 2 files, not any patch or other stuff)
reboot the phone
connect the usb cable
after the Mi logo screen, wait to hear from PC a sound that means the usb periferial has been recognised
go in a command window and type:
--> adb devices (if the phone is connected, you will see the code written after the command executed)
--> adb shell logcat > bootlog.txt (this will start real time recording of logs into the pc in the bootlog.txt file)
--> when the phone has completed boot/reboot (eg. a boot loop or fastboot), you need to press Ctrl+C from keyboard to stop log recording.
send attached to the issue description post the bootlog.txt
...let's dev check what's happening by reading the logcat.
... list will be updated...

Miscellanea...
Download (public versions history)
Here you can find the shared folder with all the version released of Treble support: GEMINI-TREBLE
Changelog's
v6 (20190316) - Release Candidate 2 full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- FIXED NFC support
- FIXED Ambient Display main icon size and settings menu icons style... Thanks to Subezhj for helping fixing.
- FIXED ConfigPanel - Fingerprint settings menu icons style
v5 (20190308) - Release Candidate full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- Mostly all library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated
- Updated kernel as per treble's kernel docs (enforced)
- Vendor image's version is now 28
- Misc updates and fixes
- GSI Pie roms support (check in OP for some links)
- JDC PIE GSI rom given just as a preview for testing (JDC PIE GSI is build from sources without ANY hack!!)... It's pure AOSP as Google bring to their devices... NOTE: No support for gapps... they do not complete setup... you are advised.
v4 (20180409) - Beta partially versioned_vndk with the following updates:
- VERSİONED_VNDK support is partially implemented
- Lots of library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated, only small number of lib dependencies which needs to be resolved are left
- Updated kernel as per treble's kernel docs
- Vendor image is now using google's stock vndk-sp, ll-ndk libs which are called as treble layer libs
- Vendor image's version is now 27.1.0
- Misc updates and fixes
v3 (20180329) - Beta status with the following updates:
- Updated camera Hal from latest qualcomm 8996 repo
- Hexedited more libs and removed more vendor system dependency (better treble and preparation for versioned vndk)
- Updated wifi configs from lates CAF
v2 (20180318) - Still alpha build with the following updates:
- Upstreamed kernel
- Hexedited blobs to correct path (for treble)
- Linker issues fixed
- Vendor overlays
- Latest device tree updates from CAF and miui oreo beta
- Disabled non-working apps (custom xiaomi doze package and configpanel app which were designed to work with LOS APIs)
- Disabled userspace thermal hal initialization which we dont have in cameraHal (faster cam launch)
- Increased jpeg quality parameters
- other misc. dev tree updates
v1 (20180310) - Initial release (Alpha)
Reported/Known Issues
- Camera works perfectly, but on some apk after a shot is taken with Flash active, the camera do not get more pictures... Close the app will clear the issue and you can get other pictures! Suggestion: do not use the flash with this camera apk if you have the issue! ... or use a working camera apk (is a better solution)!
to be updated...

Big thanx and credits also goes to @smeroni68
All of the story is started with the identifying unused CUST partition which xiaomi left on our device Mi5 https://forum.xda-developers.com/showpost.php?p=74702470&postcount=300
And after we determined that the /cust partiton is unused on AOSP roms, we used it as /vendor partition as per the requirement of Full-Treble https://github.com/sirmordred/android_device_xiaomi_gemini-twrp/commit/5faf9c4e162e8144b71f87d6d21c384931b1ac0c nearly 3 month ago
And that is also the reason of nearly all devices which get Full-Treble support via custom implementation, are Xiaomi devices (Redmi Note 4, Mi5S and our Mi5)
Thanx also to my teammates who contributed this project :good:
Our goal is now separating/isolating all vendor <=> system interactions (which will be enforced on future android releases for treble devices) and stabilizing vendor.img while getting closer to pure AOSP sources
Enjoy

...

...

Finally we are out for both MI5 and MI5S... yeah... now let's go ahead...

Thanks for all JDCTeam

Great Job dude! Finally we got treble. Downloading now. Can't wait flashing.
通过我的 MI 5 上的 Tapatalk发言

Thank you Sir, downloading now

Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?

kishan314 said:
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
Click to expand...
Click to collapse
Good question... I'll report also in post#2 in FAQ section.
Q: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img and the system partition... vendor partition will stay there waiting for your next test!

So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way

atembleque said:
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
Click to expand...
Click to collapse
This is something we can try to build... but only when sources of P will be released and will be good to build an AOSP based on them...

Very very thankful

Thanks for your hardwork, downloading now.

When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk

Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine

MichaelPan01 said:
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Here it is working.
Have you set the battery icon visibility status under the statusbar settings?
StealthHD said:
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
Click to expand...
Click to collapse
1) Phh rom support natively Phh superuser app (from market) with stock kernel and phh-gapps-su gsi image.
2) Gcam require API2/HAL3 support, and on phh gsi hasn't been implemented (as written is an experimental rom with the meaning to be compatible with stock Oreo treble devices). Instead, it has API1/HAL1 support for stock vanilla camera.
3) Stock kernel is HMP. We do not develop till now the EAS kernel on stock treble kernel (we will do for our JDC gsi).
4) Magisk is clearly reported into Phh thread to not be used. In custom development we have a plus, because we can change the kernel (as you have done)...
Thanks for this testing report.

[ROM][Signature Spoofing]LineageOS 18.1 for S10E/S10/S10+ Exynos

{
"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"
}
LineageOS 18.1 for Galaxy S10 Series​
Code:
/*
* 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.
*/
Working:
- Wifi
- Sound
- mali drivers
- USB tethering
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- GPS
- Cameras (All of them)
- HWcomposer (HWC)
- Signal indicator
- Double tap to wake
- Wireless PowerShare
Not Working
- VoLTE and VoWiFi will not be implemented (for now) as they heavily depand on samsungs framework
To properly report a bug (Please dont report things already on the Not Working list)
a) Logcat
b) /proc/last_kmsg (or /proc/kmsg)
c) /data/tombstones
d) dmesg
Please do not report bugs if you have performed any system modifications excluding gapps installation
Installation instructions
Make sure you are on Q stock firmware (All of the Q firmwares are tested and confirmed to be working, This should be the case with new fws too as long as Samsung doesnt significantly change bootloader trustzone bits)
Download Q twrp from this thread
flash twrp as per given instructions
if you are coming from stock and have encryption enabled format data (Note i said format, Wiping it in twrp is not the same as formating it)
wipe cache, dalvik cache and system
flash LineageOS
If you want to have gapps flash them right after flashing the rom before first booting
Reboot the device
Downloads:
Google Drive
Mega.nz
(Select build coresponding to your devices codename, S10e = beyond0lte | s10 = beyond1lte | s10+ = beyond2lte)
sha256 checksums
Code:
c8b961734a7972e9db9110785ba622d48c65a3c8ada9c611165864b0411f6699 lineage-18.1-20211111-UNOFFICIAL-beyond2lte.zip
fea1d76cb049cf3d83b9863da19dd0c46b70f91cec7c2a820915adb8943a671c lineage-18.1-20211111-UNOFFICIAL-beyond1lte.zip
540c111583147e94076959fdf3ff51c3f8fc2f29ec98949c6a105d936882f8ce lineage-18.1-20211111-UNOFFICIAL-beyond0lte.zip
If you need general help or questions feel free to join Telegram group
READ BEFORE INSTALLING MAGISK
Gapps
I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler
Due to requests from some users I added signature spoofing support to the rom which allows usage of MicroG
you can simply install MinMicroG and grant it needed permissions for signature spoofing to make it work as intended
Based On Android R
Changelog
12.11.2021.
- Merged November 2021. security update
- Further Improved bluetooth in call handling
- Added more advanced burn in protection
- Misc performance and stability improvements
- Synced with LOS source
06.10.2021.
- Merged October 2021. security update
- Improved bluetooth in call handling
- Synced with LOS source
10.09.2021.
- Merged September 2021. Security update
- Synced with LOS source
06.08.2021.
- Merged August 2021. Security update
- Synced with LOS source
10.07.2021.
- Merged July 2021. Security update
- Performance and stability improvements
- Changed sensors handling in doze mode to prevent battery drain
- Synced with LOS source
10.06.2021.
- Merged June 2021. Security update
- Synced with LOS source
06.05.2021.
- Added wifi and portable hotspot overlays
- Merged May 2021. Security update
- Synced with LOS source
08.04.2021.
- Fixed USB C audio input/output
- Fixed charging with device powered off (It also has nice new animation now)
- Merged April 2021. Security update
- Misc performance and stability improvements
- Synced with LOS source
08.03.2021.
- Added signature spoofing support
- Synced with LOS source
05.03.2021.
- Merged March 2021. Security update
- Performance and stability improvements
- Synced with LOS source
06.02.2021.
- Merged February 2021. Security update
- Misc performance and stability improvements
- Modernized AdvancedDisplay app codebase
- Cleaned up the source
- Updated magisk boot images
- Synced with LOS source
06.01.2021.
- Merged January 2021. Security update
- Fixed OpenGapps installation from lineage recovery
- Fixed features that broke with initial 18.1 merge
- Misc performance and stability improvements
- Synced with LOS source
09.12.2020.
- Merged December 2020. security update
- Merged December 2020 feature drop
- Merged S9DTK9 vendor blobs
- Switched to full vndk30 vendor
- Fixed ADB inside of lineage recovery
- Improved brightness handling even more
- Performance and stability improvements
- Updated recovery images provided in 3rd post
- Synced with LOS source
10.11.2020.
- Further improved auto brightness handling
- Merged November 2020. security update
- Performance and stability improvements
- Updated recovery images provided in 3rd post
- Synced with LOS source
03.11.2020.
- Fixed issues with overlays and s10 camera cutout
- Enabled access to fingerprint for apps that were looking for secure biometics device (e.g. paypal)
- Improved automatic brightness handling (Switched to calibrated sensor virtual device which calculates brightness more precisely)
- Pinned SystsemUI and SurfaceFlinger to ram to imrpove responsivness
- Added blur to dropdrown notifications panel
- Enabled device controls from power menu
- Synced with LOS source
- Misc performance improvements
22.10.2020.
- Merged october security update
- Added back mDNIe display tuning options
- Added back a lot of previously non working los features
- Misc performance and stability improvements
- Synced with los source
07.10.2020.
- Initial public release
XDA:DevDB Information
[ROM] LineageOS 18.0 for S10E/S10/S10+ Exynos , ROM for the Samsung Galaxy S10
Contributors
Ivan_Meler
Source Code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-18.0
ROM OS Version: 11.0
Version Information
Status: Stable
Created 2020-10-07

Reserved

Magisk
Magisk boot images are provided in this google drive folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine, Source for given kernel is available at GitHub if you want to compile kernel yourself just run source build.sh devicename e.g. source build.sh beyond2lte, It will produce new boot image in build/ folder, To update magisk you can follow instructions given at this commit enjoy
Do note that you will have to reflash magisk boot image when updating rom

Wow ! Man, very nice job !
So, you stop release for Lineage 17 ?

troufiniou said:
Wow ! Man, very nice job !
So, you stop release for Lineage 17 ?
Click to expand...
Click to collapse
Nah will update that too, Just felt like releasing this because i had some time to sort out issues with it

The version of gapps doesnt matter even if this is android R right?
I can still flash android 10.0 gapps right?

Eidluci said:
The version of gapps doesnt matter even if this is android R right?
I can still flash android 10.0 gapps right?
Click to expand...
Click to collapse
there is link for android 11 gapps in first post under download section

Ivan_Meler said:
there is link for android 11 gapps in first post under download section
Click to expand...
Click to collapse
Oh thank you, my bad

Hi @Ivan_Meler i'm looking to change rom (i'm on hades rom but this one is not support anymore). And i just want to know if i need a custom kernel to improve battery life on LoS rom (this one or 17.1)?
Thanks for your precisions and your work to maintain on devices uptodate !

[Legenda] said:
Hi @Ivan_Meler i'm looking to change rom (i'm on hades rom but this one is not support anymore). And i just want to know if i need a custom kernel to improve battery life on LoS rom (this one or 17.1)?
Thanks for your precisions and your work to maintain on devices uptodate !
Click to expand...
Click to collapse
Battery life should be fine with stock kernel too as most of things are improved power hal side of things

Ivan_Meler said:
Battery life should be fine with stock kernel too as most of things are improved power hal side of things
Click to expand...
Click to collapse
Great. Thanks. I'll go on 17.1 LoS for awhile and will install this one when it will be more "polish".

Hi I don't know why but on previous lineage os ROMs, when I use TWRP and boot.img it would always boot back to recovery everytime I flashed a ROM.

Can you use lineage recovery to flash ROMs?

Ivan_Meler said:
If you want to root build you will have to use Magisk Canary from here, Once in app download Lineage Recovery for your device from Google Drive or Mega Patch image within manager and flash patched image to recovery partition, When booting hold recovery key combination till you get to first warning screen after that release keys and let system continue booting normally
Magisk curently has some issues properly detecting 2si devices so thats why we cant use boot.img without need for key combo for magisk right now, I will look into that in coming days but till then this is viable solution
Click to expand...
Click to collapse
Tried but says magisk still isn't installed please help.

Il be installing it soon to test it, very hype for android 11

FreeRunner2017 said:
Tried but says magisk still isn't installed please help.
Click to expand...
Click to collapse
make sure you followed instructions closely
1. Download recovery image
2. Download magisk canary app and patch recovery image
3. Flash magisk patched recovwry image (lineage recovery) to recovery partition
4. reboot and hold key combination for recovery until first warning screen shows up, after that release key combo
5. you should be in system with root
if you need further assistance im sure someone from telegram group can help you a bit more

Ivan_Meler said:
make sure you followed instructions closely
1. Download recovery image
2. Download magisk canary app and patch recovery image
3. Flash magisk patched recovwry image (lineage recovery) to recovery partition
4. reboot and hold key combination for recovery until first warning screen shows up, after that release key combo
5. you should be in system with root
if you need further assistance im sure someone from telegram group can help you a bit more
Click to expand...
Click to collapse
I did that but I still have no magisk

SD cards on the s10e just dont work, they keep saying its corrupted even after you format them in android itself ive also tried formatting in windows and twrp but same problem.
network traffic indicator can be turned on but never actualy shows up.
after installing magisk it takes apps 20 seconds to open.
if you need logs i will be happy to do so (if i can remember how to do so)

Wow, already an android 11 ROM ? Nice !
Is there the same issues as on L17 regarding bluetooth and front camera ?

Hi Ivan
Thanks for the great work! Awesome to have Android R available so early. Rom is solid.
On S10e i can confirm, it does not read MMC, i also tried formatting etc, not a biggy
On Bluetooth i can confirm that devices working, headphone sound, speakers etc. But on call when phoning, the sound does not come over to the headset.
HDMI Out is glitchy, creates flickering on secondary display, but is random....
Other than that, the rom is smooth and fast. Still checking battery...
Looking forward to developments...

[ROM][11] [User build][Signed]Lineage-18.1-X00TD-Asus Zenfone Max Pro M1

{
"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"
}
About LineageOS
Lineage-18.1-X00TD-Asus Zenfone Max Pro M1
Build type : UNOFFICIAL
Build and signed by @[email protected] | Rajesh R
Disclaimer : ROMs are built for development purpose only. Use at your own risk.
This ROM completely compiled on lineage source code and with minimum workarounds for a successful build. Builds are signed with release-keys.Before installing, refer instructions and changelog for each builds.
About build variants
ROM-Signed release key-user build
My Projects
lineage-18.1-20210726-X00TD-user-signed.zip
fastboot-lineage-18.1-20210604-X00TD-user-signed-images.zip
lineage-18.1-20210604-recovery-X00TD.img
TWRP recovery X00TD @Vivekachooz
Features
* Changelog-25
*Enforcing selinux and user build properties
* Certified device status under google play
* SafetyNet Test is passed
* Smooth ROM experience
Instructions
Backup procedure and precaution information
Must read before unlocking bootloader and flashing custom ROM
Some explanation regarding the whole widewine L1-L3-Qbeta etc ( Info @ https://t.me/ASUSX00TD from a member )
Starting from Q builds Asus has begun wiping DRM keys if bootloader is unlocked on that build, which is actually default behavior among most other OEMs like pixels, oneplus. Flashing Q builds (Stock beta 1 or latest) or custom ROM on unlocked bootloader through TWRP will permanently loose their L1 certification. widewine keys will be wiped by firmware itself as it detects unlocked bootloader. This also explains why some people, who flashed previous stock Q beta before on locked bootloader, even though first stock Q beta had L3 which means they hadn't fixed L1 on that beta that time , retained their L1/DRM keys on reverting to pie via downgrade zip provided by asus. So in conclusion Asus Q builds/custom ROM will wipe your DRM keys if flashed on Unlocked bootloader. Flashing on locked bootloader shouldn't be any problem!
Also those who have their persist partition backed up in pie should have no problem restoring their DRM keys in case thet got wiped by Q firmware/builds
How to Backup Persist ?
Dump all partitions and make complete backup | Partition layout and structure
Recovery method
use recoveries which support persist partition backup (eg. Orangefox)
Go to recovery > Backup > tick persist > backup > store it safe somewhere with multiple copies.
How to Restore Persist ?
Go to recovery > Restore menu > select backup > tick persist partition > Restore (process similar/different for different recoveries)
Upgrading to LineageOS 18.1
1. Make a backup of your important data
2. Download the build and also Gapps.
3. Download proper addons packages GApps for Android 11/Lineage OS 18.1
4. Make sure your recovery and firmware are up to date
5. For clean flash, Format your system,vendor,data and cache partition partition to install ROM and Gapps.
6. For installing updates format system,vendor and cache partition. keep data partition intact to flash ROM and Gapps.
Secure ROM experience
Avoid permissive selinux and rooting methods for secure ROM experience.
Refer
1. Root & SELinux Risks
2. TWRP password protection
3. TWRP encryption
Screenshots
Upcoming builds ( Only for volunteer testers )
lineage-18.1-20210529-X00TD-user-signed.zip
* To test Safetynet
To test any ROM
Requirements:
Windows/linux Pc
adb drivers
Usb cable.
Steps to take log:
1. Install adb drivers in pc and enable usb debugging mode in phone. Also enable root debugging if needed.
2. Connect phone through usb and type the command "adb logcat -d>logcat.txt" in adb command window.You can choose any name you want for txt file. If needed give admin privilege for adb command window.
3. This procedure can also be used to watch occurance of bugs at realtime by connecting phone at adb mode to pc.
Steps to take boot log:
1. Make sure adb is enabled in phone. Connect the phone in usb mode to pc and open adb command window.
2. Switch off the phone and type "adb logcat -d>bootlog.txt".
3. Initially "waiting for the device" message is noticed on adb command window and switch on the phone now. once the device powers on, boot log is recorded.
log text files are stored in location where adb drivers are installed.
Note : Test builds are released here and intended to test upcoming fixes and features.
Source Code
Kernel source code : https://github.com/LineageOS/android_kernel_asus_sdm660
Kernel developer credits : @SagarMakhar, Lineage Team
Credits
Google's AOSP Project.
Lineage OS for the source code and The Open GApps Project.
Contribute to Lineage OS at https://paypal.me/LineageOS
Contribute to Gapps at https://www.paypal.com/donate/?toke...EScTbkNmciIDl9n5LyDW&country.x=US&locale.x=US
Thanks to developers and their contribution on custom ROM development for Asus zenfone max pro M1.
Special thanks for the build server admin and @abhishekt295
Tester credits
1. @Orion281
2. @patkk
It's all free, but donations are welcome
Donations will be contributed to server maintenance
Support developers on their respective threads
Feedback and bug reports are welcome
Kindly use english language on comment section​

Changelog​
1. lineage-18.1-20210409-UNOFFICIAL-X00TD.zip
* Initial build.
* Engineering build properties
* Permissive selinux.
2. lineage-18.1-20210412-X00TD-user-signed.zip
* Enforcing selinux and user build properties
* Release-key signed.
* Android Verified Boot (AVB)
3. lineage-18.1-20210413-X00TD-user-signed.zip
* Fixes and kernel updates
4. lineage-18.1-20210418-X00TD-user-signed.zip
* New fixes
5. lineage-18.1-20210419-X00TD-user-signed.zip
* Fixes on DTW and battery status LED notification.
* Screen density.
* Vibration intensity control on accessibility settings.
* Clean flash recommended
* OTA support added for upcoming builds
6. OTA : lineage-18.1-20210423-X00TD-user-signed.zip
* Fixes on DTW and battery status LED notification.
* Fixes on SafetyNet Test
* Screen density.
7. OTA : lineage-18.1-20210428-X00TD-user-signed.zip
* Synced with source updates.
8. OTA : lineage-18.1-20210504-X00TD-user-signed.zip
* Synced with source updates.
* lineage recovery and fastboot zip support added.
* Safetynet fixes and lineage kernel updates.
9. OTA : lineage-18.1-20210511-X00TD-user-signed.zip
* Android Verified Boot (AVB) Enabled
* Security patch update
* Kernel updates
10. OTA : lineage-18.1-20210514-X00TD-user-signed.zip
* Updated device fingerprint and vendor patch level from latest asus android 10 beta.
* OTA link fixes.
11. OTA : lineage-18.1-20210517-X00TD-user-signed.zip
* Synced with source updates.
12. OTA : lineage-18.1-20210520-X00TD-user-signed.zip
* OTA Fixes and Synced with source updates.
13. Build : lineage-18.1-20210523-X00TD-user-signed.zip
* Test build with new features.
14. Build : lineage-18.1-20210525-X00TD-user-signed.zip
* AVB disabled and Verity Enabled.
* Locking bootloader supported. Works only with lineage recovery.
Note : Lock only if lineage recovery is flashed. If bootloader locked with twrp. Device fails to boot and only fastboot mode helps to solve the issue to unlock bootloader again.
* Dirty flash on previous build wont work. It is not OTA release. Only clean flash recommended.
* Added variable vibration control.
* Sound control features added.
* New features on dialer app.
* Adaptive sleep features.
15. OTA : lineage-18.1-20210528-X00TD-user-signed.zip
* Safetynet Fix.
* OTA supported only to lineage-18.1-20210525-X00TD-user-signed.zip
16. OTA : lineage-18.1-20210604-X00TD-user-signed.zip
* Synced with source updates and fixes.
17. OTA : lineage-18.1-20210726-X00TD-user-signed.zip
* Synced with source updates and fixes.

I already tested it and have sent you feadback.

SafetyNet is passing on latest build i.e. lineage-18.1-20210412-X00TD-user-signed.zip,

Everything is fine but pubg footsteps sound is very low.

Is GPS working? I couldn't get current location on Maps app...

MISONLN41 said:
Is GPS working? I couldn't get current location on Maps app...
Click to expand...
Click to collapse
Yes, it's working fine for me.

Orion281 said:
Yes, it's working fine for me.
Click to expand...
Click to collapse
Thank you. I'll try clean flash again.

DT2W isn't working in the lockscreen. Any fix?

russelldlongno said:
DT2W isn't working in the lockscreen. Any fix?
Click to expand...
Click to collapse
Checkout bugs. Did you check on other custom kernel?

russelldlongno said:
DT2W isn't working in the lockscreen. Any fix?
Click to expand...
Click to collapse
It's working. I just checked again before replying to you. There's as option "Tape to wake" in display settings. Check if you it enabled. Also make sure you're on latest build.

Orion281 said:
It's working. I just checked again before replying to you. There's as option "Tape to wake" in display settings. Check if you it enabled. Also make sure you're on latest build.
Click to expand...
Click to collapse
I reflash it again using TWRP 3.4.0 by KudProject and currently I'm on firmware 87, yet still not working. What firmware are you using?

Orion281 said:
It's working. I just checked again before replying to you. There's as option "Tape to wake" in display settings. Check if you it enabled. Also make sure you're on latest build.
Click to expand...
Click to collapse
I still can't fix it. I tried flashing firmware 087 via ASUS flash tool, clean flash everything, tried other custom roms if DT2W is working, still this specific ROM gives me headache. I can't find any solutions online either. Tried to flash multiple custom kernels, no luck. So how did you do it?

russelldlongno said:
I still can't fix it. I tried flashing firmware 087 via ASUS flash tool, clean flash everything, tried other custom roms if DT2W is working, still this specific ROM gives me headache. I can't find any solutions online either. Tried to flash multiple custom kernels, no luck. So how did you do it?
Click to expand...
Click to collapse
I'm also on the same firmware as you. I did a clean flash (wiped System, Vendor, Data, and caches). I use OrangeFox recovery. May I ask which build are you using?

Orion281 said:
I'm also on the same firmware as you. I did a clean flash (wiped System, Vendor, Data, and caches). I use OrangeFox recovery. May I ask which build are you using?
Click to expand...
Click to collapse
The latest one (20210413). Still not working. haha

russelldlongno said:
The latest one (20210413). Still not working. haha
Click to expand...
Click to collapse
That's strange. Btw 20210413 build was re uploaded because previous build had some issue. Can you match this MD5 hash (9e92c5deb689891958a7ebfe150c337f) against your zip. Also, can you please post a screenshot of your display settings.

Orion281 said:
That's strange. Btw 20210413 build was re uploaded because previous build had some issue. Can you match this MD5 hash (9e92c5deb689891958a7ebfe150c337f) against your zip. Also, can you please post a screenshot of your display settings.
Click to expand...
Click to collapse
The md5 that you gave is the same with my ZIP file. I can't give you any screenshots, at the moment, 'cause I don't know where's the setting for that. LineageOS seemed to remove it from the power menu. Anyway, there's an option in the "Display" section called "Tap to wake" (disabled by default when you first install the ROM) and I enabled it. I tested it multiple times, on and off, still no luck. What device variant are you using? Mine is 4GB/64GB. It's says on the box, "ZB602KL", but it doesn't support NFC. AFAIK, my model's supposed to support NFC. WEIRD.

russelldlongno said:
The md5 that you gave is the same with my ZIP file. I can't give you any screenshots, at the moment, 'cause I don't know where's the setting for that. LineageOS seemed to remove it from the power menu. Anyway, there's an option in the "Display" section called "Tap to wake" (disabled by default when you first install the ROM) and I enabled it. I tested it multiple times, on and off, still no luck. What device variant are you using? Mine is 4GB/64GB. It's says on the box, "ZB602KL", but it doesn't support NFC. AFAIK, my model's supposed to support NFC. WEIRD.
Click to expand...
Click to collapse
Mine is also 4GB/64GB midel, but it says ZB601KL on its box. This may be the cause of issue that you're facing.

Orion281 said:
Mine is also 4GB/64GB midel, but it says ZB601KL on its box. This may be the cause of issue that you're facing.
Click to expand...
Click to collapse
Maybe? hahaha. Thanks for the reply though. As so you know, I tested some Android 11 ROMs too. I tested DotOS and crDroidand their DT2W feature doesn't work either. I also tested ArrowOS, but it's SELinux status is in "Permissive", so I can't use it. It's DT2W feature works though. Maybe some Android 11 ROMs share the same trees as this one? Who knows? Guess gotta live with it? haha
P.S. I want to use the LineageOS 17.1 from the same dev, but when I crank up the volume in full, the speaker starts to crack and it's pretty annoying.