This thread is discontinued - Please visit my LineageOS 16.0 Osprey thread
Hi,
this is my unofficial LineageOS 14.1 microG-enabled build series for the Moto G 2015 (osprey) device with current security patches.
The builds here have already a history in Osprey LineageOS 13 with microG patch thread for the 'cm-13.0' branch - it may be worth to scroll through it to find additional information.
The builds have got the following features:
LineageOS 14.1 with current security patches (from official LineageOS repositories)
Security string 2020-05-05, AOSP tag 7.2.1_r36
Squid kernel for the Osprey device (currently own fork with most recent patches)
Adapted LineageOS Jelly Browser (additionally having Startpage and Qwant as search engines)
OTA Support
Root is not included and would need to be flashed separately
VoLTE support is same as in official LineageOS (supposed to work, can't test myself)
System certificates taken from AOSP Oreo branch
Device encryption fully functional
There are three build variants available:
A. Default LineageOS 14.1 with substratum and microG patch
For those who simply want to use LineageOS 14.1 with substratum theme engine
Download here
Patched for the use of microG - you can either flash Gapps or manually install microG as apps (or use neither of those)
Patched for the use of the substratum theme engine (the substratum app and the themes need to be downloaded separately)
System Webview M81
B. Hardened build with pre-installed microG and F-Droid
For the security/privacy focused
Download here
Pre-installed microG same as the LineageOS for microG project
Pre-installed AuroraStore / AuroraServices
Additional security hardening features listed below
SQLite 'secure delete' feature enabled
Access to /proc/net blocked for user apps
Bundled netmonitor app to allow network monitoring
Enhanced Privacy Guard: Switches for motion sensors and other sensors available
Oreo backport: SET_TIME_ZONE permission restricted to system apps
Oreo backport: Access to timers in /proc restricted
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
No submission of IMSI/phone number to Google when GPS is in use
Bromite System Webview M81
C. Above hardened microG build with substratum patch
Download here
Same features as above (B), but . . .
Patched for the use of the substratum theme engine (substratum app and themes need to be downloaded separately)
Source Code links
LineageOS: https://github.com/LineageOS
Kernel: https://github.com/lin14-mGoms/android_kernel_motorola_msm8916/tree/mse_v2
microG patch: https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
microG-Build: https://github.com/lineageos4microg
Patches for Substratum: https://github.com/LineageOMS
local manifest: https://github.com/lin14-mGoms/local_manifests
hardening features: see reserved post further below
Installation instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.
Pre-Requisites
Get familiar with the hardware keys of the Motorola Moto G 2015 (osprey) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume key to the reboot recovery option and select with power key)
Activate the Developer options (Settings, about phone: tap 7 times on the build number), get into the new menu Developer options and activate, if available, the option "OEM unlocking")
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb (you need to activate the option "USB debugging" in the Developer options)
Download the most current .ZIP file of this ROM and place it to your phone's internal memory or SD card
This build variants B and C come with microG pre-installed, so not applicable for Gapps (you can flash Gapps only on build variant A)
An unlocked bootloader (read the warnings carefully and backup your data!
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it.
However - I recommend to use the official TWRP recovery from the TWRP site. The following instructions are based on TWRP.
To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, get it into 'fastboot mode', connect the device via USB to your PC and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (see above) - I recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped.
Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd).
Choose the .ZIP file of this ROM and swipe to flash. If you update from a previous version of this ROM, you don't need to perform a wipe.
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 14.1 - be patient, the first boot after flashing a new ROM takes quite long!
Credits
Android Open Source project (AOSP)
LineageOS project
squid2 (Kernel)
microG project
CopperheadOS project
Substratum team
XDA:DevDB Information
[EOL][ROM][Osprey][LineageOS 14.1][Substratum][microG] (hardened), ROM for the Moto G 2015
Contributors
MSe1969
Source Code: https://github.com/lin14-mGoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2020-05-07
Created 2018-03-22
Last Updated 2020-07-12
Change Log
12.07.2020 - EOL announcement
Please visit my LineageOS 16.0 thread for the Osprey device
07.05.2020 - May 2020 ASB
ASB Security string 2020-05-05
System Webview on 81.0.4044.117 (Build Variant A)
Bromite Webview on 81.0.4044.127 (Build Variants B and C)
AuroraStore updated to 3.2.8 (Build Variants B and C)
10.04.2020 - April 2020 ASB
ASB Security string 2020-04-05
Fix for CVE-2020-8597 (external/ppp)
Kernel: CVE-2019-10638 siphash 128bit for IP generation
System Webview on 80.0.3987.132 (Build Variant A)
Bromite Webview on 81.0.4044.76 (Build Variants B and C)
AuroraStore updated to 3.2.4 (Build Variants B and C)
09.03.2020 - March 2020 ASB
ASB Security string 2020-03-01
System Webview on 80.0.3987.117 (Build Variant A)
Bromite Webview on 80.0.3987.118 (Build Variants B and C)
AuroraStore updated to 3.2.0 (Build Variants B and C)
Added Netguard app (F-Droid version) to SELinux domain allowing /proc/net (Build Variants B and C)
07.02.2020 - February 2020 ASB
ASB Security string 2020-02-01
System Webview on 79.0.3945.136 (Build Variant A)
Bromite Webview on 79.0.3945.139 (Build variants B and C)
Updated AuroraStore 3.1.8 (Build variants B and C)
13.01.2020 - January 2020 ASB
ASB Security string 2020-01-01
System Webview on 79.0.3945.116 (Build Variant A)
Bromite Webview on 79.0.3945.107 (Build variants B and C)
Updated AuroraStore 3.1.7 (Build variants B and C)
Updated AuroraServices 1.0.5 (Build variants B and C)
07.12.2019 - December 2019 ASB
ASB Security string 2019-12-01
System Webview on 78.0.3904.108 (Build Variant A)
Bromite Webview on 78.0.3904.119 (Build variants B and C)
Updated AuroraStore 3.1.5 (Build variants B and C)
10.11.2019 - November 2019 ASB
ASB Security string 2019-11-01
Bromite Webview on 78.0.3904.72 (Build variants B and C)
Updated microG GMS core 0.2.9.x (Build variants B and C)
16.10.2019 - October 2019 ASB
ASB Security string 2019-10-01
System Webview on 77.0.3865.116 (Build variant A)
Bromite Webview on 77.0.3865.104 (Build variants B and C)
Aurorastore 3.1.3 with AuroraServices 1.0.4 (Build variants B and C)
10.09.2019 - September 2019 ASB
ASB Security string 2019-09-01
11.08.2019 - August 2019 ASB
ASB Security string 2019-08-01
Additional patches from AOSP branch 'nougat-mr2-security-release'
OTA Support
Bromite Webview on 76.0.3809.100 (Build variants B and C)
Aurorastore 3.0.9 with AuroraServices install method (Build variants B and C)
Updated microG GMS core 0.2.8.x (Build variants B and C)
05.07.2019 - July 2019 ASB
ASB Security string 2019-07-01
System Webview updated to 75.0.3770.101 (Build variant A)
Bromite Webview on 75.0.3770.109 (Build variants B and C)
13.06.2019 - June 2019 ASB
ASB Security string 2019-06-05
System Webview updated to 74.0.3729.157 (Build variant A)
Bromite Webview on 75.0.3770.86 (Build variants B and C)
Replaced Yalpstore with Aurorastore (Build variants B and C)
Updated F-Droid & priv. extension (Build variants B and C)
Updated microG GMS core 0.2.7.x (Build variants B and C)
10.05.2019 - May 2019 ASB
Security string 2019-05-05
System Webview updated to M74 (Bromite, too)
Build variants B and C only: pre-installed Yalpstore
08.04.2019 - April 2019 ASB
Security string 2019-04-05
12.03.2019 - March 2019 ASB
Security string 2019-03-05
SystemWebView updated (includes CVE-2019-5786): M72 (build variant A) / M73-Bromite (build variants B and C)
Various patches merged from Squid kernel
08.02.2019 - February 2019 ASB
Security string 2019-02-05
18.01.2019 - January 2019 ASB
Security string 2019-01-05
System Webview updated to M71
Additional 'spectre v1' mitigations in kernel
Update of Timezone data
No submission of IMSI/phone number to Google when GPS is in use (only applies to build variants with pre-installed microG)
Privacy-enhanced Bromite SystemWebView M71 (only applies to build variants with pre-installed microG)
Opt-in (instead of opt-out) for apps having the PACKAGE_USAGE_STATS permission (only applies to build variants with pre-installed microG)
08.12.2018 - December 2018 ASB
Security string 2018-12-05
Fix of 'adb root' bug
09.11.2018 - November 2018 ASB
Security string 2018-11-05
20.10.2018 - October 2018 ASB
Security string 2018-10-05
System Webview upgraded to M69
Added Qwant suggestion provider in Jelly browser
Settings: Option in Networks => Datausage to switch off Captive Portal Detection (only applies to build variants with pre-installed microG)
microG updated to 0.2.6 (only applies to build variants with pre-installed microG)
Menu entry for microG in Settings (only applies to build variants with pre-installed microG)
Dialer: Removed Google as forward lookup agent (only applies to build variants with pre-installed microG)
09.09.2018 - September 2018 ASB
Security string 2018-09-05
Squid Kernel r23 (own fork)
microG updated to 0.2.5 (only applies to build variants with pre-installed microG)
11.08.2018 - August 2018 ASB
Security string 2018-08-05
24.07.2018 - July 2018 ASB
Security string 2018-07-05
System Webview upgraded to M67
System certificates from AOSP Oreo branch
21.06.2018 - Added build variants in OP
Substratum-patched default build
Hardened microG-build
microG-build with Substratum-patch
10.06.2018 - June 2018 ASB
Security string 2018-06-05
22.05.2018 - May 2018 ASB
Security string 2018-05-05
System Webview upgraded to M66
27.04.2018 - April 2018 ASB
Security string 2018-04-05
System Webview upgraded to M65
Cloudflare DNS as default (instead of Google)
Privacy-preferred default settings
Privacy-Guard: Motion Sensor AppOp now in 'ask' mode by default
22.03.2018 - Initial upload
AOSP tag android-7.1.2_r36
Security string 2018-03-05
Squid kernel r22c
Pre-installed microG apps
Adapted LineageOS Jelly Browser (additionally having Startpage and Quant as search engines)
SQLite 'secure delete' feature enabled
Access to /proc/net blocked for user apps
Bundled netmonitor app to allow network monitoring
Enhanced Privacy Guard (1): Switches for motion sensors and other sensors available
Enhanced Privacy Guard (2): All available AppOps are shown
Oreo backport: SET_TIME_ZONE permission restricted to system apps
Oreo backport: Access to timers in /proc restricted
Details about additional security hardening
1. SQLite 'Secure Delete' feature
This sanitizes deleted data by overwriting it with zeroes, rather than having it persist within SQLite's free list.
Backport from Oreo, see https://android-review.googlesource.com/q/topic:"secure_delete"
2. Restrict SET_TIME_ZONE permission to system apps
Backport from Oreo, see here
3. Enhanced Privacy Guard - Sensor permission switches
An own sensor template to control access to motion sensors ('ask' mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard. Commits: (1), (2), (3)
4. Restrict access to /proc/net for user apps
An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. This is the main commit. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitorhas been bundled.
5. Access to timing information in /proc restricted
To prevent side-channel attacks as described here, the respective Oreo patch has been back-ported.
6. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS while still supporting DNS-over-TLS.
In the default DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
(Please note: Cloudflare is "less bad than Google by means of privacy" and thus good as a default, but I personally recommend to look for better alternatives if concerned about privacy)
7. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 14.1 (all setting can be changed at any time later):
Privacy Guard is enabled on install (proposal during Setup)
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sensitive information is hidden on the lock screen
Apps having the PACKAGE_USAGE_STATS permission appear by default as "not allowed" under Settings => Security & privacy => Apps with usage access (instead of opting out here, the user needs to explicitly opt-in in order to have the app collecting this data)
8. No submission of IMSI or phone number to Google when GPS is in use
GPS also works fine, if no SIM card is present, so there obviously is no benefit for the phone holder (different from other involved parties, who are always keen on "improving the overall user experience") to provide this data . . .
Any review or some screenshots pls.
ROM installs with no problems. Microg works well. I don't use volte so can't comment.
This ROM would be suitable as a daily driver.
However I find the lack of OMS support to be a major drawback. I use black themes too much to go back to eye blinding white.
It is a rock solid ROM that is kept up to date which is a big plus.
stonny20 said:
Any review or some screenshots pls.
Click to expand...
Click to collapse
Can add some screenshots after my vacations ...
EDIT: Added some screenshots now
jemail said:
ROM installs with no problems. Microg works well. I don't use volte so can't comment.
This ROM would be suitable as a daily driver.
However I find the lack of OMS support to be a major drawback. I use black themes too much to go back to eye blinding white.
It is a rock solid ROM that is kept up to date which is a big plus.
Click to expand...
Click to collapse
Thanks a lot for your review and feedback.
Regarding OMS, as already mentioned in my cm-13.0 thread, there are own support threads on XDA.
I have had a closer look now and it seems that to patch LineageOS to support Substratum is a bigger effort. There are some repositories on github with those patches, it seems however a continuous effort to merge LineageOS patches and features and make OMS working again afterwards.
Since it is no "one-off" effort, but continuous work and even involves to weaken some SELinux settings, I am afraid that I won't go that path.
I am currently on vacation, only mobile access. Can only check after my return. So wil get back on this topic.
New build with April Sec.patches
Hi,
I've uploaded a new build:
https://www.androidfilehost.com/?fid=962187416754477482
Security string 2018-04-05
AOSP tag 7.1.2_r36
System Webview M65
Cloudflare instead of Google default DNS
Privacy-adapted default settings
Is it compatible with substratum?
MSe1969 said:
Hi,
I've uploaded a new build:
https://www.androidfilehost.com/?fid=962187416754477482
Security string 2018-04-05
AOSP tag 7.1.2_r36
System Webview M65
Cloudflare instead of Google default DNS
Privacy-adapted default settings
Click to expand...
Click to collapse
Whatsapp video sharing working ??
jemail said:
However I find the lack of OMS support to be a major drawback. I use black themes too much to go back to eye blinding white.
Click to expand...
Click to collapse
I'll give it a try and will work in making a test build soon, which (hopefully) will support OMS
Hunimix said:
Is it compatible with substratum?
Click to expand...
Click to collapse
No, not at the moment, but working on it...
Vvk380 said:
Whatsapp video sharing working ??
Click to expand...
Click to collapse
I am not using WA, so don't know. However, why shouldn't it?
MSe1969 said:
I am not using WA, so don't know. However, why shouldn't it?
Click to expand...
Click to collapse
It is not working on official nightlies
Vvk380 said:
It is not working on official nightlies
Click to expand...
Click to collapse
Well, then - most probably - it won't work here either...
However, what is the nature of the issue?
I am using a different kernel with this ROM, so maybe worth a try?
Further, have you tried disabling HW overlays in developer settings? Just guessing...
If you have a way of reproducing the issue without having to install WA, I am happy to have a deeper look.
MSe1969 said:
Well, then - most probably - it won't work here either...
However, what is the nature of the issue?
I am using a different kernel with this ROM, so maybe worth a try?
Further, have you tried disabling HW overlays in developer settings? Just guessing...
If you have a way of reproducing the issue without having to install WA, I am happy to have a deeper look.
Click to expand...
Click to collapse
Actual issue is u cant share videos recorded through camcorder(moto camera) on whatsapp
I checked disabling HW overlays..didnt worked
And I'll see if i can reproduce this issue in some other way...
Thnks
MSe1969 said:
Well, then - most probably - it won't work here either...
However, what is the nature of the issue?
I am using a different kernel with this ROM, so maybe worth a try?
Further, have you tried disabling HW overlays in developer settings? Just guessing...
If you have a way of reproducing the issue without having to install WA, I am happy to have a deeper look.
Click to expand...
Click to collapse
Hi.. The issue is related to updated lux OMX blobs.. i have fixed this for Oreo using Aex N blobs as Aex N source have not merged Lux Kernel sources.. As after we have fixed camcorder it's again broken..
OMS-enabled test build
jemail said:
However I find the lack of OMS support to be a major drawback. I use black themes too much to go back to eye blinding white.
It is a rock solid ROM that is kept up to date which is a big plus.
Click to expand...
Click to collapse
Hunimix said:
Is it compatible with substratum?
Click to expand...
Click to collapse
I've prepared an OMS-enabled test build - characteristics as described before, but OMS patches included (taken from https://github.com/LineageOMS and adapted, where necessary):
https://www.androidfilehost.com/?fid=674106145207484704
Please test and feedback.
Thanks M.
deleted
You may have read this XDA story already. The security hardening of this ROM already takes care, see the dedicated reserved post in this thread.
Related
Disclaimer
Code:
/*
* 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
LineageOS needs no introductions. This version of LineageOS-12.1 is a highly customised version solely for the Amazon Fire 7"
- EVEN MORE IMPORTANT: As of January 2019 this ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.
- IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required).
Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- Please report bugs here
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...
Prerequisites for Installation
- Unlocked Bootloader
- TWRP Installed
Downloads
*** Please do NOT create any mirrors ***
Lineage-12.1 for Amazon Fire 7"
Source Code
- ROM Source: https://github.com/cm12-amami
- Kernel Source: https://github.com/ggow/android_kernel_amazon_mt8127-common
- Common Tree: https://github.com/ggow/android_device_amazon_mt8127-common
- Device Tree: https://github.com/ggow/android_device_amazon_ford
- Device Tree: https://github.com/ggow/android_device_amazon_austin
Thanks
- @MSe1969 for the up to date cm-12.1 sources
- @k4y0z and @xyz` for the bootloader hack
- LineageOS
XDA:DevDB Information
LineageOS, ROM for the Amazon Fire
Contributors
ggow
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Stable
Stable Release Date: 2017-08-02
Created 2017-07-20
Last Updated 2020-05-05
Changelog / Release Notes
05 May 2020
- Fixed video recording
15 April 2020
- ASB April 2020 patches (sec. string 2020-04-05)
- Privacy Browser updated to version 3.4.1
- Fix for CVE-2020-8597 (external/ppp)
23 August 2019
- August 2019 ASB patches (sec. string 2019-08-05)
- Additional (backported) security patches from AOSP branch 'nougat-mr2-security-release
- Privacy Browser updated to version 3.2
- SetupWizard rebranded to LineageOS
31 July 2019
- Fix external sdcard not mounting correctly
30 July 2019
- ASB July 2019 patches (sec. string 2019-07-05)
- System Webview M75 - updated to 75.0.3770.101
- Fixed Keyboard Swype functionality
- Front and rear cameras on ford and austin fixed and tested working
24 May 2019
- ASB May 2019 patches (sec. string 2019-05-05)
- Privacy Browser updated to version 3.0.1
- Fixed video recording
- WiFi: Use hardware MAC address
- Bluetooth: Use hardware MAC address
22 April 2019
- Rebased kernel with full history
- Upstreamed kernel to 3.10.108
18 April 2019
- Fix sdcard write permissions
- Fix screen off animation for odd hwrotation
- Add support for amazon fire 7th gen
- Merged common kernel for ford and austin (android_amazon_kernel_mt8127-common)
16 April 2019
- ASB March 2019 patches (sec. string 2019-04-05)
- Privacy Browser updated to version 2.17.1
- Android System Webview updated to M72 (includes CVE-2019-5786)
- This is for unlocked devices only
- Updated OP
18 December 2018
- ASB December 2018 patches (sec. string 2018-11-05)
- Fix of 'adb root' bug (see LineageOS announcements)
- Addl. fix of CVE-2018-9531, CVE-2018-9536 and CVE-2018-9537 from November ASB, which are flagged Android 9 only, but also apply
- Backport of CVE-2017-15835 (skipped in November ASB)
09 November 2018
- ASB November 2018 patches (sec. string 2018-11-05)
29 October 2018
- ASB October 2018 patches (sec. string 2018-10-01)
- Android System Webview updated to M69
- Indication in Settings that Security patch level is unofficial
12 September 2018
- ASB September 2018 patches (sec. string 2018-09-05)
18 August 2018
- ASB August 2018 patches (sec. string 2018-08-05)
- Privacy Browser updated to version 2.12
01 August 2018
- ASB July 2018 patches (sec. string 2018-07-05)
- Privacy Browser updated to version 2.11
- Android System Webview updated to M67
23 June 2018
- ASB June 2018 patches (sec. string 2018-06-05)
- Privacy Browser updated to version 2.10
- Privacy-default setting (at clean install): Sensitive information is hidden on the lock screen
02 June 2018
- ASB May 2018 patches (sec. string 2018-05-05)
- Android System Webview updated to M66
- Privacy Browser updated to version 2.9
- Use Cloudflare DNS 1.1.1.1 as default fallback (instead of Google's 8.8.8.8)
05 May 2018
- Security patches up to April 2018 included
25 March 2018
- Fix privacy guard issue
15 March 2018
- Security patches up to March 2018 included
30 January 2018
- Fix root issue not appearing in developer options
- Flashed clean with FF 0.73 - go figure - it worked for me this time no errors
28 January 2018
- Rebase ROM on https://github.com/cm12-amami - Thanks @MSe1969
- Includes security patches up to Jan 2018
- A clean install is recommended and may be required to function correctly.
02 December 2017
- Port relevant security patches to up November 2017
- Switch to using FireOS 5.4.0.0 update-kindle-37.5.7.9_user_579225620 binaries and boot.img
- Fixed backlight becoming stuck on minimum setting. This needs more users to test. It works for me so far
29 November 2017
- Use bin/wpa_supplicant blob from FireOS 5.4.0.0
27 November 2017
- Ported relevant November Security Patches
- Ported relevant October Security Patches
- Upgraded OpenSSL
- Upgraded Privacy Browser to 2.7.2
- NOTE: KRACK vulnerability is not patched in this one. The patch level for this version of the ROM is 01 November 2017. I am working on the 06 November 2017 patches. When I have it figured out, will do another release very shortly.
28 September 2017
- Ported relevant September Security Patches
12 September 2017
- Ported relevant August Security Patches
- Fixed no way back from Charge Only mode
02 August 2017
- Fixed sdcard write issue
- Fixed odd screen rotation glitch on power off
- ROM status updated to "stable"
20 July 2017
- Initial Release
- Ported security patches up to July 2017
- Fixed up Xposed compatibility
- Too many other fixes to list here
- This ROM release is Alpha and needs a lot of testing that I can't cover off on my own.
- All feedback will be greatly appreciated.
- I have tested flashing using TWRP and FlashFire 0.57 so this should be OK.
- A clean installation is mandatory.
New Build is Up
- Dated 20 July 2017
- Ported security patches up to July 2017
- Fixed up Xposed compatibility
- Too many other fixes to list here
- This ROM release is Alpha and needs a lot of testing that I can't cover off on my own.
- All feedback will be greatly appreciated.
- I have tested flashing using TWRP and FlashFire 0.57 so this should be OK.
- A clean installation is mandatory.
ggow said:
- Dated 20 July 2017
- Ported security patches up to July 2017
- Fixed up Xposed compatibility
- Too many other fixes to list here
- This ROM release is Alpha and needs a lot of testing that I can't cover off on my own.
- All feedback will be greatly appreciated.
- I have tested flashing using TWRP and FlashFire 0.57 so this should be OK.
- A clean installation is mandatory.
Click to expand...
Click to collapse
Wow! Will test when I have a chance
Awesome! Finally an update from CM!
I may try it, but IDK if I better wait a bit.
tonibm19 said:
Awesome! Finally an update from CM!
I may try it, but IDK if I better wait a bit.
Click to expand...
Click to collapse
Even if your on CM-12.1, be aware that a clean install may still be necessary.
Thanks ggow. Was just preparing for a fresh Installation of aicp, but now i will test this rom instead.
Clean install seems to be running fine so far.
FlashFire-v0.57-20170403162805.apk
lineage-12.1-20170720-UNOFFICIAL-ford.zip
open_gapps-arm-5.1-super-20170720.zip (with .gapps-config)
SR1-SuperSU-v2.82-SR1-20170608224931.zip
Sent from my ford using XDA Labs
ggow said:
- Dated 20 July 2017
- Ported security patches up to July 2017
- Fixed up Xposed compatibility
- Too many other fixes to list here
- This ROM release is Alpha and needs a lot of testing that I can't cover off on my own.
- All feedback will be greatly appreciated.
- I have tested flashing using TWRP and FlashFire 0.57 so this should be OK.
- A clean installation is mandatory.
Click to expand...
Click to collapse
Clean flashed this pup w/GAaps Nano and Xposed Framework. Disabled journaling for giggles & grins. Using integrated root manager. Connected and booted up w/o a hitch. Far to early for definitive statements but every operation I have attempted during the past 30 min (mostly set-up stuff, installing apps, configuring Xposed modules, multiple reboots) has gone without a hitch. Hoping to find time for detail testing this weekend. While partial to AOSP ROMs I do find Lineage to be an attractive offering with a nice suite of UI enhancements baked in.
ggow said:
- All feedback will be greatly appreciated.
Click to expand...
Click to collapse
So far while setting it up, Settings crashed just once opening Home but hasn't crashed again. Sadly, automatic LiveDisplay does not work here as well (didn't work in the past October CM build I had), you have to manually toggle it. I just finished setting everything up. The rest is working like a stable build so far. Will let you know if something happens down the line.
What I did:
- Clean flashed thru TWRP
- Flashed the kernel modules, micro OpenGApps, Xposed & V4A
- Cleared journaling from /data & /cache
- Turned off KSM and set up the I/O Sched and governor with Kernel Adiutor
- Slimmed up the ROM and the GApps (current TWRP unable to run AROMA)
I did the
Fresh installation from FireOS or other ROM FlashFire >= 0.57 coming from CM12.1
During the flashing, there were errors of couldn't unmount system, resource busy and things like that.
Now my tablet is stuck on the amazon logo. ;(
tonibm19 said:
I did the
Fresh installation from FireOS or other ROM FlashFire >= 0.57 coming from CM12.1
During the flashing, there were errors of couldn't unmount system, resource busy and things like that.
Now my tablet is stuck on the amazon logo. ;(
Click to expand...
Click to collapse
I guess i had the same error about two weeks ago while going from cm to RR. If you can access stock recovery you need to sideload the original fireos version your tab was running before you installed a costum Rom. There is a tuturial here on xda, can't look for the link right now.
nirogu325 said:
So far while setting it up, Settings crashed just once opening Home but hasn't crashed again. Sadly, automatic LiveDisplay does not work here as well (didn't work in the past October CM build I had), you have to manually toggle it. I just finished setting everything up. The rest is working like a stable build so far. Will let you know if something happens down the line.
What I did:
- Clean flashed thru TWRP
- Flashed the kernel modules, micro OpenGApps, Xposed & V4A
- Cleared journaling from /data & /cache
- Turned off KSM and set up the I/O Sched and governor with Kernel Adiutor
- Slimmed up the ROM and the GApps (current TWRP unable to run AROMA)
Click to expand...
Click to collapse
Couple thoughts:
- inability of LiveDisplay to switch automatically is common to most CM/LOS 12.1 builds, especially on devices that lack a physical GPS or do not utilize Google Location Services in 'High Accuracy' mode; seems the function uses location vs the clock to to determine on/off times
- custom kernel modules are not demonstrated to work with this ROM although there is absolutely no reason to believe there will be any conflicts
tonibm19 said:
I did the
Fresh installation from FireOS or other ROM FlashFire >= 0.57 coming from CM12.1
During the flashing, there were errors of couldn't unmount system, resource busy and things like that.
Now my tablet is stuck on the amazon logo. ;(
Click to expand...
Click to collapse
I'll look into this before next update
Davey126 said:
Clean flashed this pup w/GAaps Nano and Xposed Framework. Disabled journaling for giggles & grins. Using integrated root manager. Connected and booted up w/o a hitch. Far to early for definitive statements but every operation I have attempted during the past 30 min (mostly set-up stuff, installing apps, configuring Xposed modules, multiple reboots) has gone without a hitch. Hoping to find time for detail testing this weekend. While partial to AOSP ROMs I do find Lineage to be an attractive offering with a nice suite of UI enhancements baked in.
Click to expand...
Click to collapse
Another hour of configuration/use did not surface any gremlins. I am always surprised how snappy this device can be under the right conditions given modest specs. Hardware definately likes the deadline scheduler augmented with a 5 sec write delay. Tweaking animation scales under developer options also has a nice effect. Lineage hummed through all that and more without glitching.
Other notes: WiFi connects/disconnects reliably. ROM sleeps as it should with minimal idle drain. Rotation fast and reliable. Bluetooth uneventful.
This weekend I will push a little harder on various apps that sometimes upset the applecart. Given experiences to date not expecting any issues.
nirogu325 said:
So far while setting it up, Settings crashed just once opening Home but hasn't crashed again. Sadly, automatic LiveDisplay does not work here as well (didn't work in the past October CM build I had), you have to manually toggle it. I just finished setting everything up. The rest is working like a stable build so far. Will let you know if something happens down the line.
What I did:
- Clean flashed thru TWRP
- Flashed the kernel modules, micro OpenGApps, Xposed & V4A
- Cleared journaling from /data & /cache
- Turned off KSM and set up the I/O Sched and governor with Kernel Adiutor
- Slimmed up the ROM and the GApps (current TWRP unable to run AROMA)
Click to expand...
Click to collapse
LiveDisplay, as I have come to understand requires modification to the kernel. So will be a no-go unless we find a vulnerability to exploit.
ggow said:
LiveDisplay, as I have come to understand requires modification to the kernel. So will be a no-go unless we find a vulnerability to exploit.
Click to expand...
Click to collapse
Gotcha. Minor stuff but do you remember that old image distortion whenever you turned off the screen? It's been a long while since I had a ROM with that and it's rearing its head again sometimes here.
ggow said:
LiveDisplay, as I have come to understand requires modification to the kernel. So will be a no-go unless we find a vulnerability to exploit.
Click to expand...
Click to collapse
Even with a kernel mod auto behavior may still be erratic without the benefit of full location services if numerous user reports are accurate. Apparently goes beyond simply obtaining sunset/rise info for current location as most phones secure the proper time/zone via network.
nirogu325 said:
Gotcha. Minor stuff but do you remember that old image distortion whenever you turned off the screen? It's been a long while since I had a ROM with that and it's rearing its head again sometimes here.
Click to expand...
Click to collapse
Yes, I remember that screen issue, will be fixed in the next release.
ggow said:
Yes, I remember that screen issue, will be fixed in the next release.
Click to expand...
Click to collapse
I forgot to tell you that it looks like the SDcard fix is not implemented. Several apps gave me trouble, including Titanium Backup (for write purposes) until I applied the SDcard Fix. I have all my backups in my microSD card.
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.
*
*/
This is an unofficial port of LineageOS 15.1 for the Zenfone 3 ZE520KL and ZE552KL.
It's a continuation of the great work on LineageOS 14 by @shakalaca.
In this post you'll find anything related to the ROM itself.
The second post is about extensions like Gapps and Asus Camera and the changelog can be found in the third post.
What's working/features:
Up to date kernel: Linux 3.18.136, CAF Tag LA.UM.7.6.r1-04300-89xx.0
Security patch level: March 5, 2019
User build, signed with my release-keys
Support for F2FS and EXFAT
Flipcover support via FlipFlap.
HW acceleration
WiFi/Hotspot
Bluetooth fully functional, with AptX
ANT+
GPS (+ Glonass)
Camera (Asus Camera mostly working, check the second post.)
Flashlight
Fingerprint
Mobile data and phone
Data roaming - read installation instructions!
Audio fully functional
All sensors working
Double tap to wake, Swipe up to wake
Touch gestures and on-screen nav bar
Notification/Battery LED
LiveDisplay
FM
Gapps
Substratum
Wireguard support
SELinux: Enforcing
Issues:
No major issues
Installation instructions:
Your bootloader has to be unlocked!
Update to the latest oreo stock rom.
In stock rom: Enable data roaming
If you don't do this you'll not be able to use roaming in LineageOS. (This also applies to other custom roms.)
The LineageOS roaming switch can be used normally afterwards.
Backup your internal storage to an external SD card or a computer. Internal storage should not be wiped but better save than sorry.
Download the LineageOS 15 zip file provided in the downloads section to your phone (or use "adb sideload" with a computer).
Flash the TWRP recovery I provided here.
Reboot to TWRP. Backup everything. I recommend storing the backup on a computer or the external SD Card.
Again in TWRP: Wipe Data, Cache, Dalvik/Art Cache and System.
Finally you can install the LineageOS zip file and optionally Gapps. Reboot when finished.
(Always flash LineageOS and Gapps without rebooting in between!)
First boot will take a littler longer - If everything went as expected: Welcome to LineageOS 15.1!
For AsusCamera read the post below about extensions.
Download:
LineageOS 15.1 for the ZE520KL and ZE552KL: https://drive.google.com/open?id=15v4n4NCTnPtwO2xN_UnyKFuDKSVgloVc
How to return to build 2018-06-11 or earlier:
The following information only applies if you want to dirty-flash older builds. Factory-resetting the phone would make key migration obsolete.
If you want to return to build 2018-06-11 or earlier and are running 2018-08-11 or later, you have to migrate your data partition back to the test-keys.
Simply flash the "planet9_keys-to-test_keys.zip" from the "Key Migration" folder on my drive share to do so.
Future updates:
I'll keep maintaining this rom until Android P roms are stable enough for daily use.
Additional credits:
@shakalaca
@makorn645
All the LineageOS and Linux devs who put so much time and effort into development!
All the contributors to these mido and potter device trees. These sources proved to be a great reference!
Commit authorship has been preserved so take a look at my device tree for more information.
Sources:
Device tree: https://github.com/Planet-X/android_device_asus_zenfone3/tree/lineage-15.1
Kernel: https://github.com/Planet-X/android_kernel_asus_msm8953/tree/lineage-16.0
Vendor: https://github.com/Planet-X/proprietary_vendor_asus_zenfone3/tree/lineage-15.1
XDA:DevDB Information
LineageOS 15.1 for ZE520KL/ZE552KL, ROM for the Asus ZenFone 3
Contributors
planet9
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Stable
Created 2018-02-23
Last Updated 2019-03-12
Extensions
Here you'll find information about additional packages.
Advanced Kernel:
An advanced kernel packed with additional features!
Finally available here: https://forum.xda-developers.com/ze...ernel-advanced-kernel-lineageos-15-1-t3760007
Asus Camera:
Asus Camera apk download: https://drive.google.com/open?id=1_4ID3AiPLEGQkxm4WgjWVpFswImiv284
Important:
The new, standalone apk file has all the libraries included so it can be installed like any other user app over the package manager: No flashing through twrp is needed anymore and the app will stay installed even after updating the system.
Before installing the new apk make sure to fully uninstall the old asus camera zip by flashing a rom or the uninstaller zip!
Bugs:
Most of the features should finally work with the new apk.
Still not working:
- Save to MicroSD
- HDR Pro
Gapps:
Official Open GApps for android 8.1 are finally available: http://opengapps.org/
Changelog
2019-03-12:
Update to Android 8.1.0_r52, security patch level March 5, 2019.
Updated kernel to Linux 3.18.136, CAF-Tag LA.UM.7.6.r1-04300-89xx.0
2018-10-11:
Updated vendor blobs to WW-15.0410.1807.75.
Update to Android 8.1.0_r47, security patch level October 5, 2018.
Updated kernel to Linux 3.18.123, CAF-Tag LA.UM.6.6.r1-09900-89xx.0
Thanks to @makorn645:
Fixed SafetyNet CTS check.
Reduced vibration strength.
Updated various blobs.
General cleanup.
2018-08-11:
First enforcing "user" build, signed with my release-keys.
Enabled call recording. (Not available in all regions.)
Fixed displayed battery capacity on the ZE552KL.
Added more SEPolicy for enforcing SELinux.
Fixed wifi stats log spam.
Added the ASUS_Z012DC to the model detection list.
Added SdFat for FAT and exFAT support.
Added updated version of the BFQ I/O scheduler.
Removed asusdebug for a lighter kernel.
Updated F2FS kernel driver.
Imported many more kernel improvements.
Updated vendor blobs to WW-15.0410.1806.68.
Update to Android 8.1.0_r43, security patch level August 5, 2018.
Updated kernel to Linux 3.18.118, CAF-Tag LA.UM.6.6.r1-09500-89xx.0
Thanks to @makorn645:
Updated Vulkan, Adreno and SDM blobs from tissot.
Added missing perf and widevine blobs.
Updated perf blobs from bardock 2.2.0.
Fixed FM radio speaker audio.
Even more SEPolicy.
Optimized shutdown time.
Added "Swipe up to wake".
Added support for power-off alarms.
Switched default I/O scheduler to BFQ.
Added the ASUS_Z017D to the model detection list.
Updated build fingerprint to WW_15.0410.1806.68.
Misc improvements of the kernel defconfig for more performance.
Many more misc improvements...
2018-06-11:
Added FlipFlap.
Tweaked graphics performance.
Enabled the third QS row for the ZE520KL.
Updated vendor blobs to WW_15.0410.1804.62.
Update to Android 8.1.0_r30, security patch level June 5, 2018.
Updated kernel to Linux 3.18.112, CAF-Tag LA.UM.6.6.r1-08600-89xx.0
Thanks to @makorn645:
Added icons to AsusParts.
Moved AsusParts to system settings.
Updated build fingerprint to WW_15.0410.1804.62.
More SEPolicy rules.
2018-05-21:
Added ANT+ support.
Enabled WiFi Passpoint support.
Fixed 4K recording with Asus Camera.
Updated GPS HAL.
Updated GPS configs from WW_15.0410.1804.60.
Updated vendor blobs to WW_15.0410.1804.60.
Updated build fingerprint.
Updated kernel to Linux 3.18.109, CAF-Tag LA.UM.6.6.r1-08500-89xx.0
Thanks to @makorn645:
Added missing proprietary files.
Improved audio configs.
Updated media and bluetooth configs.
2018-05-10:
Improved speakerphone sound quality.
Doubled wifi performance on 40MHz wide 2.4GHz networks and enabled TDLS.
Removed KCal. (LiveDisplay now offers this functionality.)
Properly enabled the Vulkan API.
Fixed 5GHz hotspot option sometimes not selectable.
MTP should now report the proper phone model.
Updated vendor blobs to WW_15.0410.1803.55.
Update to Android 8.1.0_r26, security patch level May 5, 2018.
Rebased and cleaned up the kernel.
Updated kernel to Linux 3.18.108, CAF-Tag LA.UM.6.6.r1-08300-89xx.0
Thanks to @makorn645:
Improved model detection.
Updated media configs from mido.
Improved wifi battery savings.
Defined gmsclient-id.
Properly detect single-sim devices.
Added modem build date assertion.
More SEPolicy rules. (Still permissive due to some missig rules.)
Updated build fingerprint.
2018-04-25:
Improved fingerprint service.
Improved DT2W performance and fixed "Prevent accidental wake-up" switch.
New LiveDisplay implementation with more features.
KCAL is now built-in. (It may be removed again due to new LiveDisplay features making it obsolete.)
Updated vendor blobs to WW_15.0410.1803.53.
Updated kernel to Linux 3.18.106, CAF-Tag LA.UM.6.6.r1-07400-89xx.0
Thanks to @makorn645:
Fixed serial number detection.
Added a built-in app to set vibration strength and KCAL values.
Improved SEPolicy. (SELinux still permissive due to missig rules.)
Updated configs and build fingerprint.
2018-04-06:
Fixed crash when switching mobile data sim card.
Added vibration intensity control: Currently not available within LineageOS settings.
Intensity can be adjusted using "Kernel Adiutor" or other kernel management apps - Advanced Kernel is not needed for that.
Imported many kernel improvements.
Update to Android 8.1.0_r20, security patch level April 5, 2018.
Updated kernel to CAF Tag LA.UM.6.6.r1-07200-89xx.0.
Thanks to @makorn645:
Updated audio configs. (Speakerphone still buggy)
Updated way of setting the build fingerprint.
2018-03-25:
Doing a clean flash is recommended.
New AsusCamera apk: Read the "Extensions" post above for instructions. The old one isn't supported anymore.
Restored default battery led behavior to mitigate flickering. You can change the brightness in the system settings.
Updated vendor blobs to WW_15.0410.1802.44.
Updated kernel to Linux 3.18.102, CAF Tag LA.UM.6.6.r1-06700-89xx.0.
Additional minor updates.
Adopted from XenonHD by @makorn645:
Misc fixes for Amplifier.
Drop hacked up audiohal.
Enabled VoLTE.
Removed forceencrypt from fstab.
Renamed Z017 to zenfone3.
Built SEPolicy. (SELinux still permissive due to missig rules.)
2018-03-11:
Improved spectrum support.
Enabled camera api v2 in Snap. It now features manual mode.
Pulsing low battery light is now toggleable in the settings.
Updated kernel to Linux 3.18.99.
Adopted from XenonHD by @makorn645:
MTP now uses functionfs.
Switched back to OSS bluetooth hal with fixed mac.
2018-03-06:
Improved bluetooth performance and fixed mac issues.
Brand-new notification LED controller.
Fixed battery light for offline charging.
Update to Android 8.1.0_r15, security patch level March 5, 2018.
2018-03-04:
Much newer Lineage sources.
FM, Battery LED and LiveDisplay fixed.
Improved micro-lag at animation beginnings.
Updated kernel to Linux 3.18.98.
Multiple minor improvements/fixes.
2018-03-01:
Hotfix for dialer audio.
2018-02-28:
Regression: Dialer audio stopped working!
Headphone detection finally fixed!
Fixed dialer crash when using in-call keypad.
Touch screen gestures added.
Optional on-screen nav bar added.
Updated kernel to Linux 3.18.97, CAF-Tag LA.UM.6.6.r1-06500-89xx.0
2018-02-24:
All sensors finally working. Thanks to @Harry8242 !
External sd card should behave properly now.
2018-02-23:
Initial release of alpha version.
Nice. Thanks bro. I really appreciate it
:good: God bless you !
Great work buddy !!!!
I'll test this out after my semester exams :lol:
great job, i will test it and give u some feedback....
Im using los14 and never been able to update to stock oreo. Will it work? Or need to go back to stock to install oreo 1st then this?
iamROOTX said:
Im using los14 and never been able to update to stock oreo. Will it work? Or need to go back to stock to install oreo 1st then this?
Click to expand...
Click to collapse
Just flash it via TWRP. Don't forget to flash GApps too.
ZenFone_3 said:
Just flash it via TWRP. Don't forget to flash GApps too.
Click to expand...
Click to collapse
Yeah gonna try it. Even tho he said to update to the latest stock oreo
I'm editing this post because the copy/paste text messed everything up.
@planet9
Haris from the Telegram channel sent the below message.
https://github.com/bhi768/msm8953/commit/2f35825dc36d3b23460298a0d8fca8a34d5f38e2 ask him to try this, so that he can confirm if asus's mdss changes already has live display capability
also https://github.com/Planet-X/android_device_asus_Z017/blob/lineage-15.1/manifest.xml#L226 ask him to try pass through method for sensors like in here https://github.com/harry8242/device_lenovo_A6020/blob/o8.0/manifest.xml#L155
My baseband version is m3.10.47.9 leo which should be .18 libra(on the ss).is it because i didnt install stock oreo 1st?
Good work !! ☺
iamROOTX said:
My baseband version is m3.10.47.9 leo which should be .18 libra(on the ss).is it because i didnt install stock oreo 1st?
Click to expand...
Click to collapse
Flashing stock rom also updates additonal firmware partitions and that's why your baseband is older.
In general this shouldn't be a problem. I just recommended flashing oreo so that everything is fully up to date.
Could this help somehow?
https://forum.xda-developers.com/showpost.php?p=73351949&postcount=87
tkhquang said:
Could this help somehow?
https://forum.xda-developers.com/showpost.php?p=73351949&postcount=87
Click to expand...
Click to collapse
It could definitely point to the right direction. Thanks! :good:
Edit:
Directly using this file on lineage 15 is not a good idea!
Phone services won't work anymore and it will then reboot to recovery! Don't try it.
Great, GREAT ROM! Stable and smooth! Battery endures the whole day.
The update made it almost bug free! And the remaining bugs are cosmetic for the most part.
Can't thank you enough. Keep it up!
Could we roll back oreo stock?
[email protected]@ said:
Could we roll back oreo stock?
Click to expand...
Click to collapse
Flash Oreo RAW
ZenFone_3 said:
Flash Oreo RAW
Click to expand...
Click to collapse
If there is an update about this custom rom, do I have to install it again from the beginning?
Dalendra7 said:
If there is an update about this custom rom, do I have to install it again from the beginning?
Click to expand...
Click to collapse
The updates are flashable via TWRP. No need to reinstall. It's called Dirty Flash.
I'm Not even a developer, but a builder bot
Here is a collection of LineageOS 14.1 and other LineageOS 14.1-based Custom ROMS, these Custom are Compiled from me with the source tree of @Dinolek.
His Device Tree uses MIUI lolipop blobs instead of marshmallow alps blobs which we used for Marshmallow before.
------------------------------------------------------------------------------------------------------------------------
Working :
* Adjustable brightness
* Audio
* Auto brightness
* MTP and Mass Storage modes
* Vibration
* Rotation
* RIL
* Video
* Gallery
* Mic
* Wi-Fi
* Bluetooth
* Internet
* GPS
* Hotspot
* Camera rear/front
* SD Card
* IR Blaster
* Built-in Signature Spoofing (for MicroG)
-----------------------------------------------------------------------------------------------------------------------
Broken/Bugs :
* Camera rear/front while trying to record video from stock camera (but you can record from other camera apps too)
* SafetyNet passes only with Offical Kernel source from Micode
------------------------------------------------------------------------------------------------------------------------
I this link I have included these Custom ROMS:
- LineageOS 14.1
- DotOS 1.2
- ViperOS 3.1.1
- Dirty Unicorns 11.7.2 (AOSP-Based, experimental)
- RR 5.8.5
- crDroid
Download Link: https://mega.nz/#F!0ZgiDaCS!1qISJ4mb9jWnA1W2vfUJcg
Source Trees:
Device Tree:
https://github.com/Azizb750/android_device_xiaomi_hermes
Vendor Tree:
https://github.com/Azizb750/android_vendor_xiaomi_hermes
Kernel Tree:
Official: https://github.com/Micode/Xiaomi_Kernel_OpenSource
Upstreamed: https://github.com/Azizb750/Xiaomi_Kernel_OpenSource
Credits:
@Dinolek for his source tree (don't worry I have already took his permission before)
@Smosia for his new hennessy tree and his fixes
@nofearnohappy
@lokjianming
@danielpinto8zz6
@andrea210701
@l7ssha
@Syl157
@daniel_hk (for his updated gps hal)
@ibilux (for his help to fix the bugs)
MiCode for Publishing Finally the hermes/hennessy kernel source!
Thanks to these developers/maintainers for making our device still alive!
NOTE: The ROM's are not fully stable, So I'm not responsible for the bugs which will occur later
_______________________________________________
Troubleshooting
- Some apps are crashing for a reason what's wrong?
- if you use Magisk root some apps are crashing for a reason, to solve this change Mount NameSpace Mode to Global and disable Magisk Hide and reboot (you cn re-enable it later if you want/need it),
I discovered this solution when I used older RR N 5.8.2 and the apps will not crash anymore, another way is to set ro.debuggable to 1 using MagiskHide Props Config module and reboot. But now the custom kernel is not causing this bug anymore, but in case you will meed it.
- SafetyNet fails what to do?
- If you fail Only CTSProfile, you can use this module
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
This will help you to Pass CTSProfile using custom build fingerprint from other certified devices.
If you use xposed and want to pass CTSProfile, you can use an xposed module called "No Device Check", but as far I know its impossible to pass BasicIntegrity with xposed installed, but using this module is pretty enough to log in via snapchat and using some apps but not for Pokemon GO
Edit: SafetyNet was failing due of kernel, the kernel source from Micode (or from mine upstreamed) passes it.
-what's MicroG?
- MicroG is an lightweight and opensource re-implementation of Gapps
- how do I install it?
- same as Gapps + you will need to wipe cache/dalvik and grant for signature spoofing
- In self check I see that Phonesky/Play Store has not correct signature, why does it happen?
- you need to grant for signature spoofing manually you can do it by going to Settings->Apps->Gear(in top right corner)->App Permissions-> Spoof package signature/(or signature spoofing, depends on the rom) and giving permissions to spoof signature, you can do the same to GMSCore too in case you did still haven't granted for it before
- I have problems with sign in with my account, what to do?
- this happens mostly when you are Replacing Gapps with MicroG or reinstalling MicroG without sign out, if this happened just go and delete using root explorer this files:
/data/system_ce/0/accounts_ce.db
/data/system_de/0/accounts_de.db
/data/system/sync/accounts.xml and reboot, and now you should have sign in to your account successfully
_______________________________________________
Link for MicroG(ale5000): https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360
Link for MicroG(nanodroid): https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
_______________________________________________
Changelog:
-----------------
25082018 (except DirtyUnicorns and LineageOS*)/26082018 (for DotOS)
- Fixed GPS (credit: @daniel_hk, thanks to @ibilux)
- intergrated V1.P2 modem
* Some Users reported that LineageOS 14.1 2508 does not even boot, so I dropped it temporary
-----------------
27082018 (DotOS and RR)
- integrated Audio fix
- Added some init.mt6795.rc tweaks
- Added some new flags on BoardConfig.mk
-----------------
28082018 (LOS, DotOS and RR)
- same as 27082018 + took some .conf files from MIUI 9.6.3.0 and Disabled HW overlays Permanently
-----------------
29082018 (LOS, DotOS and RR)
Dropped as some users reported Bootloops
You can Download 2808 build instead
-----------------
01092018 (LOS, DotOS and RR)
- Added some lines in ramdisk (for video recording)
- updated BoardConfig.mk
- added new keylayout (Thanks ARTEM)
- added new tweaks in build.prop for [email protected] (thanks @ibilux for help) and removed init.d script
-----------------
03092018 (ViperOS)
- Added some lines in ramdisk (for video recording)
- updated BoardConfig.mk
- added new keylayout (Thanks ARTEM)
- added new tweaks in build.prop for [email protected] (thanks @ibilux for help) and removed init.d script
- edited build.prop to make it debuggable
-----------------
04092018 (LOS, ViperOS, DotOS, RR and crDroid)
- added some lines in ramdisk
- fixed bootloop (on 03092018 ViperOS)
------------------
06092018 (LOS, ViperOS, DotOS, RR and crDroid)
- Patched for built-in signature spoofing support for MicroG (LOS, RR and DotOS only, crDroid and ViperOS have already native support for it)
- tried to fix wakelock issues while playing music
------------------
13092018 (LOS, RR, DotOS, ViperOS and crDroid)
- tried to fix colors on camera (for video recording)
- fixed some codecs (not playing flac files)
------------------
22092018 (RR with custom kernel)
Not working:
Audio (trytofixcamera.zip from older RR may solve the problem)
touch atmel
most of sensors
camera
------------------
01102018 (eelo 0.1)
- First release
- used FM libs from @Smosia's tree (thanks @Dinolek for fixing FM and @Smosia for providing them)
- made some changes in ramdisk (init.mt6795.rc only, if you want spectrum support you can flash it by using a seperate zip)
------------------
07102018 (LOS, RR, ViperOS, DotOS)
- fixed FM Radio for sure now (thanks @Smosia and @ibilux)
- used folders from auroraroms device tree so can compile them from source (credits: )
- added camera_wrapper from @daniel_hk's tree
------------------
17102018 (LOS, RR and crDroid)
- updated some patches and some BoardConfig in the device tree (thanks @Smosia and @Dinolek)
· updated and applied newer patch to disable seccomp filtering (Credit: @Dinolek)
· updated and applied newer patch for hotspot (Credit: @Dinolek)
· applied patch to fix airplane mode bug (thanks @Smosia to adding it to the tree)
- black screen seems to be fixed this time (probably it occured due that forgot to add an flag about seccomp in BoardConfig as it was essential to disable seccomp filtering)
------------------
20/21/22/23/26/27/28102018
- reverted camera_wrapper (it makes things worse about screen recording)
all compiled by @dargonswim
------------------
05/06012019
(05012019 crDroid and ViperOS
06012019 LineageOS, DotOS and RR)
- Moved device-specific libs to Vendor as Part of preparations for Oreo and Pie(Credits: @Dinolek for doing it and @Smosia providing the tree)
- fixed triggering ringtone (credits: @Smosia)
- added a expermintal flag during compilation for VideoRecording bug (thanks: @ibilux)
------------------
16012019 (Ghost Kernel0.1)
- Source from Official Xiaomi Open Source
- everything works well
- Upstreamed kernel to 3.10.108
- added dt2w (on Focaltech only)
- Patched for oreo Binders
- Passes BasicIntegrity (Now is possible to pass CTSProfile with custom fingerprints)
------------------
18012019 (for LOS, RR and DotOS, 19012019 for CrDroid and ViperOS)
- kernel from source (thanks xiaomi for releasing kernel source)
- Upgrade Sepolicy 30
- merged some camera fixes (thanks @Smosia)
- SafetyNet passes BasicIntegry
------------------
22012019
(GhostKernel0.12)
- Added new ioscheds (credits: @andrea2107)
- Made some cherry-picks for selinux improvement
- fixed annoying /proc/self/fd/* bug found in logcat
- kernel source now is more hybris friendly
(GhostKernel0.13)
- added some cherry-pick for wifi from launchpad/ubports (with the hope to fix WiFi reconnections)
- disabled dt2w by default (you can enable it using Kernel adiutor)
(GhostKernel0.14)
- fixed kernel version not updating (probably broke the script accidentally, now it applies to system, so now updates the kernel version)
- made "bfq" io-scheduler as default (I learned that it performs much better than "cfq")
- added local version to the kernel
------------------
25012019 (LOS, RR, DOTOS, VOS, CR)
- Added new governors (Credit: @andrea2107)
- added enabled dt2w function on the kernel for focaltech (on atmel doesn't work), disabled by default, use Kernel Adiutor to enable it
- Merged New fixes and features of Ghost kernel0.14(as I use the source for compile the Rom's kernel too)
- fixed stk3x1x alsps bug
------------------
14022019
- Tried to fix Video Recording (on instagram at least it works as I saw, on camera apps still not)
- Ported codec configs to fix flac audio
- Moved modem path from /etc/firmware to /system/etc/firmware on the kernel
------------------
Well, congrats to us - Redmi Note 2 owners -.
Thanks to all contributors and developers.
Is this new version already fixed GPS and intergrated V1.P2 modem ?
LineageOS 14.1 can not read the SIM Contacts book
sanbox said:
LineageOS 14.1 can not read the SIM Contacts book
Click to expand...
Click to collapse
Yeah, but I don't know how to fix it, it looks mostly like a OS Bug
Thanks
How to save a file to external sdcard
Hi @Azizb750
First I read your post here: https://forum.xda-developers.com/showpost.php?p=77463249&postcount=1312
Coming from current RR Nougat ROM for hermes by Dinolek year ago, then I downloaded and clean installed RR-20180829 build and ended with bootloop
After you updated OP, I installed RR-20180828 build > opengapps (armv7, 7.1, pico) > reboot and system booted as it should be! :good:
So far so good, better than older ROM and it satisfied my requirement for daily driver.
Many thanks bro for keeping old Redmi Note 2 alive, even with Nougat. You;re the man. It will be perfect if Security Patch upgraded at least August 5, 2018.
Current security patch December 5, 2017 is too old!
Again, many thanks Azizb750.
Have a great day!
God bless you!
/***********
Now, current ROM is RR-5.8.5 20180828 build.
Launcher: Microsoft, Poco
Google Assistant, Google Photos, works just fine!
Rooted by Magisk 16.7 (1671). SafetyNet: invalid response.
Theme: Substratum, DNA Dark Project.
SOT: 2h 6m
xu3sno said:
Hi @Azizb750
First I read your post here: https://forum.xda-developers.com/showpost.php?p=77463249&postcount=1312
Coming from current RR Nougat ROM for hermes by Dinolek year ago, then I downloaded and clean installed RR-20180829 build and ended with bootloop
After you updated OP, I installed RR-20180828 build > opengapps (armv7, 7.1, pico) > reboot and system booted as it should be! :good:
So far so good, better than older ROM and it satisfied my requirement for daily driver.
Many thanks bro for keeping old Redmi Note 2 alive, even with Nougat. You;re the man. It will be perfect if Security Patch upgraded at least August 5, 2018.
Current security patch December 5, 2017 is too old!
Again, many thanks Azizb750.
Have a great day!
God bless you!
/***********
Now, current ROM is RR-5.8.5 20180828 build.
Launcher: Microsoft, Poco
Google Assistant, Google Photos, works just fine!
Rooted by Magisk 16.7 (1671). SafetyNet: invalid response.
Theme: Substratum, DNA Dark Project.
SOT: 2h 6m
Click to expand...
Click to collapse
Thanks a lot, BTW, about patches is something that came from the Custom ROM and I can't anything for it
DotOs installed, works perfectly thank you very much! An Oreo version soon? Otherwise it's already exellent to have gone from Lolipop to Nougat ?
VoxiBe said:
DotOs installed, works perfectly thank you very much! An Oreo version soon? Otherwise it's already exellent to have gone from Lolipop to Nougat ?
Click to expand...
Click to collapse
+1
Security patch level February 5, 2018! Newer than RR! :good:
However, I preferred RR 5.8.5 good: D
Thanks Azizb750! Thanks devs!
Have a great day!
Just tried crDroid 20180825 build. I like it so much as it's highly customizable as RR. Apart from that, it applied Security patch level July 5, 2018. :good:
It's most likely I prefer to use it as my daily driver.
However, wait until I give a try the other two hermes ROMs, LineageOS and Viper.
Again, thanks a lot Azizb750 for providing N ROMs for our obsolete device!
Have a great day!
Gave a try LineageOS 14.1 for hermes 20180828 build. Everything works just fine, according to my requirements. Sure, you may vary.
Feeling secured as Security patch from August 5, 2018! :good:
Many thanks to @Azizb750 and other devs! ?
Hope, you keep the security patch updated!
Have a great day!
I did try to install ViperOS 20180825, everything works just fine as described on OP.
Security patch of July 5, 2018.
After tried all available N ROMs as provided by OP, I decided to choose crDroid as my daily driver, based on:
1.Highly and easily customizable
2. Not so old security patch (July 5, 2018). Hopefully, Azizb750 will keep updated!
Have a great day!
xu3sno said:
I did try to install ViperOS 20180825, everything works just fine as described on OP.
Security patch of July 5, 2018.
After tried all available N ROMs as provided by OP, I decided to choose crDroid as my daily driver, based on:
1.Highly and easily customizable
2. Not so old security patch (July 5, 2018). Hopefully, Azizb750 will keep updated!
Have a great day!
Click to expand...
Click to collapse
Thanks a lot
But I will not keep them always updated as I would like to stop compiling for a while due of studies after october
But I would like to work on other roms too
viper OS
i tested viper OS, a better rom, smoothly, IR blaster also work well, but fm radio do not work and i cannot make "adb over wifi" work, i hope that can be fixed,thank u
obama88 said:
i tested viper OS, a better rom, smoothly, IR blaster also work well, but fm radio do not work and i cannot make "adb over wifi" work, i hope that can be fixed,thank u
Click to expand...
Click to collapse
adb over wifi doesnot work in Developer options, but third party app as "wifi adb" works after root
Tried latest updated LineageOS 14.1 20180901 and RR 5.8.5 20180901 build.
Security patch August 5, 2018 and December 5, 2017, respectively.
Workings and bugs as described on OP. However, Contacts can't sync, using both methods.
Reverted to crDroid
Anyway, thanks Azizb750 for keeping ROMs for hermes updated!
Have a great day!
Changelog:
-----------------
01092018 (LOS, DotOS and RR)
- Added some lines in ramdisk (for video recording)
- updated BoardConfig.mk
- added new keylayout (Thanks ARTEM)
- added new tweaks in build.prop for [email protected] (thanks @ibilux for help) and removed init.d script
-----------------
03092018 (ViperOS)
- Added some lines in ramdisk (for video recording)
- updated BoardConfig.mk
- added new keylayout (Thanks ARTEM)
- added new tweaks in build.prop for [email protected] (thanks @ibilux for help) and removed init.d script
- edited build.prop to make it debuggable
Click to expand...
Click to collapse
Feel crDroid left behind bro Azizb750!
Have a great day!
i clear all data and flash 03092018(ViperOS) rom, it's bootloop ,but 25082018(ViperOS) rom work,
flash 25082018(ViperOS) firstly, then donot clear data and flash 03092018(ViperOS) rom ,boot into system, but camera crash and adb over wifi still not work ,so 25082018(ViperOS) rom should be keep,until new rom stable
In this thread I'll share with you my personal builds of LineageOS 20, 19.1 and 18.1 for the Essential PH-1 (codename: mata). These builds are unofficial LineageOS builds, customized with my favorite tweaks and features, and with some interesting optimizations.
MAIN FEATURES
LineageOS 20 features:
support for MicroG (signature spoofing) - read the 2nd post!
support for Sandboxed Google Play (taken from GrapheneOS) - read the 2nd post!
Klik and Aperture are both preinstalled
built with global -O3 optimizations and ThinLTO
some debugging/tracing instructions have been removed from ART
loads of updates from AOSP master for ART
improved bionic routines + ARM optimized routines
in-built support for many DNS providers
support for 3-finger swipe to screenshot
PixelPropUtils, to unlock Pixel-only features in Google apps and pass SafetyNet
Mulch System Webview (from DivestOS) replaces the default Chromium WebView
"deGoogling" tweaks: GrapheneOS's captive portal URLs and SUPL server, Cloudflare's DNS nameservers, pool.ntp.org NTP servers are all used by default to replace their Google counterparts
updated 3rd-party libraries: SQLite
in-built F-Droid Privileged Extension
support for poweroff alarm
KERNEL FEATURES
updates for zram/zsmalloc (and for the LZ4 compression backend too)
power-efficient workqueues are implemented in many drivers
simple_lmk by kerneltoast replaces standard LMK
Kcal & Klapse
maple I/O scheduler as default
DDR bandwidth boost when launching apps and in other scenarios
DriveDroid support (not tested)
Wireguard support (not tested)
lots of patches to improve memory allocation-related overhead
hardening against buffer overflows (thanks to the GrapheneOS team)
USB controller driver updated (MTP speed improvements)
memory routines optimized for the arm64 architecture
built with -O3 optimizations
binder driver backported from Linux 5.4
lots of drivers and components only useful for debugging are disabled
many small, miscellaneous patches to improve performance and power consumption
Spoiler: Old info about 18.1
LineageOS 19.1 features:
support for MicroG (signature spoofing) - read the 2nd post!
built with global -O3 optimizations
some debugging/tracing instructions have been removed from ART
some UI changes from ProtonAOSP (ripple effect)
updates and compiler optimizations applied to critical system components (ART, memory management routines, mathematical routines)
bionic libc fixes and updates
updated 3rd-party libraries: SQLite, giflib, zlib
support for poweroff alarm
inbuilt F-Droid privileged extension
integrated Cloudflare and AdGuard (recommended) private DNS
PixelPropUtils, to unlock Pixel-only features in Google apps and pass SafetyNet
debugging/logging code removed from system components (system frameworks, init system) to reduce overhead
other minor tweaks to system frameworks and ART, to maximize performance
LineageOS 18.1 features:
support for MicroG (signature spoofing) - read the 2nd post!
built with the latest Clang 12.0.x
updated & improved libraries: sqlite, zlib, libpng, jemalloc, libvpx, libyuv
critical system components built with -O3 optimizations (art, SurfaceFlinger, bionic)
arm64-optimized bionic routines
Android RunTime (ART) updates and improvements
several debugging & tracing components are removed from the system
partial/full screenshot QS tile
reduced priority of the USB connection type & USB debugging notifications
in-built F-Droid Privileged Extension
removed some links with Google: DNS nameservers & captive portal URL
support for OTA updates
signed with my own keys
other minor tweaks and improvements
BUGS
Common to official/Nolen's builds as well:
NFC quirks (payments with Google Wallet are working, other usecases might or might not) - fixed in the 2023-03-11 build
Updater shows wrong percentage during OTA package installation - fixed in the 2023-04-11 build
microphone issues in some scenarios - WIP
some games do not load - acknowledged, low priority issue for now
Specific of my builds:
Klik misbehaves when rotating the phone while viewing a previously taken picture (low severity bug); Klik sometimes quits when switching to front cam or B&W mode (high severity bug) - under investigation, read more about Klik's status here - updated 2023-04-12
the fullscreen dark background in the notification pull-down view is now transparent - notifications are displayed directly on top of the currently active application. This doesn't affect functionality but is indeed unpleasant to the eye fixed in the 2023-03-21 build
scrcpy gets stuck after some time - under investigation
Spoiler: Bugs of the old 19.1 builds
Common to official builds as well:
VPNs are not supported (can't configure a VPN in Settings) - fixed in my 2022-05-24 build, and in later official nightlies
swiping up on the lockscreen is difficult (a very long swipe is required) - fixed/improved in my 2022-05-24 build, and in later official nighlies
minimum brightness is too high compared to stock firmware - fixed in my 2022-06-09 build and later official builds
HDR+ and Portrait mode make Klik (Essential's camera app) crash - fixed in my 2022-11-16 build, soon in officials too
Klik often lags a lot - work in progress
bad sound quality in video recordings - fixed in my 2022-08-07 build and in officials too
wrong time on boot until you connect to a network - fixed in my 2022-12-24 build, hopefully soon in officials too
Specific of my builds:
none, at the moment
Spoiler: Bugs of the old 18.1 builds
Common to official builds as well:
unaligned recovery logo + black bar at the right of the screen - fixed in my 2021-12-15 build and newer official builds
distorted in-call audio when VoLTE is enabled for T-Mobile users - fixed in my 2022-03-11 build and newer official builds
low microphone volume/distorted audio when recording videos - fixed in 19.1
PPSSPP crashes on startup
Specific of my builds:
recovery "Back" button is difficult to press - workaround: press a little bit above it - fixed in the 2022-01-07 build
speaker misbehaving when listening to voice messages in apps such as Telegram and WhatsApp - fixed in the 2022-02-21 build
CHANGELOG for LineageOS 20:
June 24th
synced with LineageOS, including QPR3 and June's patches
more consistent rounded corners across the UI
delete button next to the screenshot preview
charging control with support for bypass mode
more consistent fonts used across the whole system & apps
Spoiler: Changelog for the old 19.1 builds
June 3rd:
synced with LineageOS
charging control HAL (check Settings > Battery > Charging Control to check what it supports)
minor improvements for screen rendering
Contacts Scopes (picked from GrapheneOS) to grant a fake contacts permission to untrustworthy apps
Material You & Monet colors applied to Calculator, Messages, Dialer, Gallery and Contacts (WIP)
creepy Facebook component removed from Klik
May 5th:
synced with LineageOS (including May's security patches)
all of Klik's bugs are finally fixed! Hooray!
support for call recording
updates for some system components
misc. sepolicy fixes and other fixes for small issues under the hood
minor kernel bug fixes
April 11th:
synced with LineageOS + April's security patches
fixed Klik's lags/freezes and the crashes after taking pictures
misc. updates and improvements for several system components
improved Monet color engine
fix for the Updater showing a wrong percentage during update installation
minor misc. visual updates (icons, animations, etc.)
March 21st:
fix for the visual bug of the previous build
March 20th:
synced with LineageOS (March's security patches + Android T QPR2)
kernel bug fixes and minor tweaks
March 11th:
synced with LineageOS
built with -O3 and ink-time optimization
many updates for ART and bionic taken from AOSP master
more privacy! More links with Google were broken (SUPL & NTP servers)
GPS performance improvements
fixes for NFC
in-built support for many private DNS providers
many kernel bug fixes taken from the Civil Infrastructure Project's backports
February 26th:
first public build
all the feaures listed above are present
January 6th:
synced with LineageOS, including January's security patches
support for poweroff alarm
a few kernel tweaks to improve the responsiveness (taken from Zen kernel)
December 24th:
system clock is correct on boot, even with no network connections
WiFi kernel drivers updated from the official Android 11 kernel for the Pixel 2
other minor fixes in the kernel
December 8th:
synced with LineageOS, including December's security patches
kernel hardening against buffer errors
many vulnerabilities affecting several Qualcomm kernel drivers have been patched
minor optimization for jemalloc (Android's memory allocator)
November 16th:
synced with LineageOS
HDR & Portrait modes in Essential's camera app now work
kernel: several fixes and updates
the kernel now is built using a full LLVM toolchain (even the integrated assembler)
November 5th:
synced with LineageOS + November's security patches
October 17th:
PixelPropUtils + patches from PixelExperience to unlock Pixel-only features in Gapps and pass SafetyNet
a few improvements and fixes in the kernel
October 9th:
synced with LineageOS (+ October's patches)
fixed log spam related to VoLTE (thanks Ricky Cheung)
kernel: disabled debugfs (reduces debugging overhead for many drivers)
kernel: updates for ZRAM and the LZ4 compression driver
kernel: other minor tweaks and updates
kernel: security fixes (thanks to our maintainer Kevin)
September 9th:
synced with LineageOS + September's patches
integrated Cloudflare and AdGuard private DNS
built with global -O3 optimizations
August 7th:
synced with LineageOS + August's security patches
"poor audio quality in video recording" bug has been fixed!
updates for ART
optimizations and improvements for bionic's memory routines
F-Droid privileged extension build in the system
June 9th:
Rebased on the latest tag from Google (android_12.1.0_r7)
June's security patches
new ripple effect from ProtonAOSP
updated and optimized SQLite library
minimum screen brightness reduced
minor tweaks to system frameworks and ART
May 24th:
initial build, 100% equal to LineageOS except for the following aspects
support for signature spoofing
some debugging removed from ART
device-specific bug fix: improved swipe-to-unlock experience (fix has landed in official repos)
device-specific bug fix: VPNs are supported (fix has landed in official repos)
Spoiler: Changelog for old 18.1 builds
May 6th:
May's security patches
various kernel updates and fixes
April 28th:
synced with LineageOS
updated SQLite to v3.37.2
kernel bug fix involving ZRAM
minor kernel tweaks and improvements
April 13th:
synced with LineageOS, April's security patches
some minor tweaks and fixes in the Android frameworks
kernel: binder driver backported from Linux 5.4
kernel: simple_lmk replaces the standard LMK
kernel: updates for the random number generator driver
kernel: other minor fixes and improvements
March 21st:
lots of updates and fixes for the platform code (picked from crDroid)
critical system components/libraries are built with ThinLTO and PGO
improved the energy efficiency of the WiFi chip
synced with LineageOS
March 11th:
synced with LineageOS
March's security patches
fix for distorted in-call audio for T-Mobile users when VoLTE is enabled
February 21st:
synced with LineageOS
a fix by the Lineage team for a telephony bug: more info here
a fix by me for a permission issue that caused the playback of voice messages in messaging apps not to switch properly between the main and the call speakers when the proximity sensor was covered/uncovered
February 11th:
synced with LineageOS
kernel updated to Linux 4.4.302
minor bug fix in the system
January 22nd:
synced with LineageOS
kernel updated to Linux 4.4.299
Google's DNS nameservers have been replaced with Cloudflare's (1.1.1.1, 1.0.0.1)
some security hardening patches taken from GrapheneOS
January 7th:
kernel: Linux 4.4.297
kernel: removed debugging junk from the WiFi chip's driver
kernel: patches for the dwc3 driver (improve MTP transfer speeds)
tentative fix for the camcorder microphone issues
recovery touchscreen issues are fixed
December 15th:
synced w/ LineageOS (incl. December's security patches)
kernel updated to Linux 4.4.294
lots of small kernel improvements and fixes
maple I/O scheduler is now the default
several user interface/user experience improvements (read here)
alignment of visual elements in recovery is fixed (now also in official LineageOS)
November 5th:
synced with LineageOS
November's security patches
kernel: DriveDroid support
kernel: Wireguard support
kernel: DDR bandwidth boost on zygote fork
kernel: several other small updates and improvements
October 23rd:
synced with LineageOS
touchscreen support in Lineage recovery
kernel now supports Kcal and Klapse
October 7th:
initial build with all the above features
October's security patches are included
DOWNLOADS
LineageOS 20: starting from April 2023, my builds are hosted here on Github - older builds on SourceForge
20 recovery images: SourceForge
Spoiler: Old downloads (19.1/18.1)
LineageOS 19.1: SourceForge
19.1 recovery images: SourceForge
LineageOS 18.1: SourceForge
18.1 recovery images: SourceForge
SOURCES
All my repos are on Github. In particular: device tree, kernel sources.
A BIG "THANK YOU" TO
the whole LineageOS team, and the multitude of great developers of the Android custom ROM scene, such as kdrag0n, kerneltoast (Sultanxda), arter97, nathanchance, neobuddy89, flar2, franciscofranco, frap129, the MSM-Xtended project, the crDroid project, the GrapheneOS team, the YAAP team, the DivestOS team and the xda user MuddyDog. I hope I have not forgotten anyone.
POST-INSTALLATION ADVICE
RECLAIM SOME PRIVACY AND BLOCK LOTS OF ADS
19.1 & 20: Open Settings > Neworks & Internet > Advanced > Private DNS and choose "AdGuard DNS"
18.1: Manually set "dns.adguard.com" as the Private DNS.
SETTING UP SANDBOXED GOOGLE PLAY
Open the "Apps" app, tap on the three dots in the top right corner, tap on Show all packages, then choose Google Play Store, and then tap on the install button. This will install Google Play Services, Play Store, and Services Framework as normal, sanboxed user apps, while allowing for an almost complete compatibility with Google Play APIs.
A few notifications will appear, shortly after, asking for some permissions. Just allow what they ask for.
INSTALLING MICROG VIA MINMICROG
Refined MinMicroG package prepared by me: click here
System mode (mandatory for those who don't want Magisk): you must remember to mount /system in Lineage Recovery before attempting to flash MinMicroG.
Systemless mode: just flash MinMicroG as though it was a Magisk module.
SETTING UP MICROG
If you have installed MinMicroG as a Magisk module, just open its Settings, and in the Self Check screen do what is required to enable all tickboxes.
In the Location Modules list, enable all the modules you're interested in using (usually all of them), but be careful that enabling some of them will make a pop up window appear, asking if you want to allow constant access to the location to a given provider. Do not click on the pop up window's main button (which denies access), instead, click on the underlined text, which will take you to a Settings screen in which you can allow the module unconstrained access to the device's location.
I also suggest disabling the "Apps" application, that is bundled in the system, as it will try (and fail) to replace MicroG with normal Google Play Services.
If you have installed MinMicroG in system mode, open an ADB shell and run the npem command, then reboot. It should grant all the necessary permissions.
SETTING UP VIPER4ANDROID
GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.
A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.
github.com
PASSING SAFETYNET
You need to have MindTheGapps or microG installed in order to pass SafetyNet. If you choose microG, enable its SafetyNet toggle in its settings.
That's enough, you should pass SafetyNet out of the box.
The following steps are needed only if you decide to flash Magisk on your phone:
In Magisk's settings, enable Zygisk
Reboot
In Magisk's settings, tap on Configure DenyList
In the three-dot menu, tick Show system apps and Show OS apps
Scroll down and look for Google Play Services.
Tap on it (don't tap on its checkbox!), the list item will expand and show additional sub-items
Tap on the Play Services' main checkbox: all of its sub-items should automatically become enabled
Look for Google Services Framework and tap on its checkbox (there are no hidden sub-items here)
Return to Magisk's settings and enable Enforce DenyList
Reboot
You should now pass SafetyNet!
Wow, I have your ROM installed in my Oneplus One and works amazing, now I can install it in my daily driver phone.
Thank you so much for your awesome work.
Angrydr0id said:
Wow, I have your ROM installed in my Oneplus One and works amazing, now I can install it in my daily driver phone.
Thank you so much for your awesome work.
Click to expand...
Click to collapse
Nice! See you around in both threads then
I just installed the ROM.
I did a clean flash through TWRP with Magisk and Gapps; January firmware and AOSP Vendor.
I only found the next bugs:
OTA always says that the update check failed, so I don't know if its working.
When I am on a call and I use the speaker, I can hear but they do not hear me. (This bug was present in my previous rom that was Carbon but I would like to know why it happens and if it is possible to fix it).
Everything else seems to work flawlessly.
Thanks again and I'll be on the lookout for updates.
If you need me to test, logs or something that can help in the development you can contact me without problem.
Angrydr0id said:
I just installed the ROM.
I did a clean flash through TWRP with Magisk and Gapps; January firmware and AOSP Vendor.
I only found the next bugs:
OTA always says that the update check failed, so I don't know if its working.
When I am on a call and I use the speaker, I can hear but they do not hear me. (This bug was present in my previous rom that was Carbon but I would like to know why it happens and if it is possible to fix it).
Everything else seems to work flawlessly.
Thanks again and I'll be on the lookout for updates.
If you need me to test, logs or something that can help in the development you can contact me without problem.
Click to expand...
Click to collapse
I've just fixed the OTA updater's issue. I had forgotten to push the json file that is used to check the presence of updates, thus the check failed. It's working now.
Issue number 2 is common to many phones and ROMs, on older phones it used to be a problem with some value in the mixer_paths.xml file. I'll look into it.
Just a quick note, you can obviously use an official Lineage recovery image to flash this ROM. Starting from the next build I'll provide my own recovery image for simplicity. I'm also working on restoring touch screen support in Lineage recovery, and I've started working on bringing back TWRP to the Essential PH-1 as well.
Tomoms said:
I've just fixed the OTA updater's issue. I had forgotten to push the json file that is used to check the presence of updates, thus the check failed. It's working now.
Issue number 2 is common to many phones and ROMs, on older phones it used to be a problem with some value in the mixer_paths.xml file. I'll look into it.
Click to expand...
Click to collapse
For issue number 2, it occurs in almost all roms, especially those based in LOS, except AOSPA Ruby Beta 1. Your device tree also uses 3 mics like LOS. So, the problem is the same.
pakpenyo said:
For issue number 2, it occurs in almost all roms, especially those based in LOS, except AOSPA Ruby Beta 1. Your device tree also uses 3 mics like LOS. So, the problem is the same.
Click to expand...
Click to collapse
Thanks for the information. I'll look into it but it's not my main priority right now. Give me a couple of weeks
pakpenyo said:
For issue number 2, it occurs in almost all roms, especially those based in LOS, except AOSPA Ruby Beta 1. Your device tree also uses 3 mics like LOS. So, the problem is the same.
Click to expand...
Click to collapse
supporting info here if needed regarding the speaker issue
hedgecore44 said:
supporting info here if needed regarding the speaker issue
Click to expand...
Click to collapse
I've seen it for a long time, including your posts there. Is the problem solved by removing the 3 mic entry?
Btw, i just made a new issue there. It happens in all LOS based roms, as well as other roms like Carbon, Havoc etc. But that's not the case in AOSPA Ruby Beta 1. I have a logcat, but I don't understand. May it be related to an audio/mic/speakerphone issue?
Hello guys!
I've just uploaded a new build. It brings Kcal/Klapse support, as requested by @Angrydr0id
I've also fixed touchscreen in Lineage recovery, it's working again now
Lineage recovery images are now available for download in a specific folder on SourceForge. They are meant to be flashed with fastboot and then booted with fastboot reboot recovery
Just updated and everything works perfectly also in the recovery, thanks for implementing KCAL.
If someone uses FrancoKernel Manager to modify the values of the screen in "Display Control", I recommend the following settings, I love the saturation of the colors:
Saturation: 275
Value: 251
Contrast: 258
Hue: 0
Thanks.
Tomoms said:
Thanks for the information. I'll look into it but it's not my main priority right now. Give me a couple of weeks
Click to expand...
Click to collapse
Another +1 in hope of fixing this issue, a fix would easily catapult this ROM to top of the charts for this device. I think this is possibly the biggest issue for mata development currently and only AOSPA folks (and stock) seems to have fixed it.
psychic_quark said:
Another +1 in hope of fixing this issue, a fix would easily catapult this ROM to top of the charts for this device. I think this is possibly the biggest issue for mata development currently and only AOSPA folks (and stock) seems to have fixed it.
Click to expand...
Click to collapse
I'll start looking into this issue in the very next days. Keep an eye on this thread
New build available! Featuring November's security patches plus several interesting kernel updates and improvements, such as DDR bandwidth boost on app startup (should improve app launching time a bit), memory allocation speed & overhead improvements, Wireguard support and DriveDroid support. I haven't tested Wiregaurd and DriveDroid, so try them if you can and let me know if they work.
The speakerphone issue is still under investigation, I haven't had enough time to look at it lately.
Tomoms said:
New build available! Featuring November's security patches plus several interesting kernel updates and improvements, such as DDR bandwidth boost on app startup (should improve app launching time a bit), memory allocation speed & overhead improvements, Wireguard support and DriveDroid support. I haven't tested Wiregaurd and DriveDroid, so try them if you can and let me know if they work.
The speakerphone issue is still under investigation, I haven't had enough time to look at it lately.
Click to expand...
Click to collapse
@Tomoms , I've been using official 18.1 for several months, and my impression if that your ROM is a major improvement - smoothness, and esp. battery life. It might be partly due to the fresh install, but so far, so good. Thank you! The phone is a backup to my Pixel 4a, but has been called upon several times, so having an up-to-date Android on the PH-1 is important for me.
As with the other poster(s), the speaker / mic issue is a problem. My dad, very senior and hard of hearing, has another PH-1, and the issue makes video call difficult for him. Hope you have some time to look into it.
mervinb said:
@Tomoms , I've been using official 18.1 for several months, and my impression if that your ROM is a major improvement - smoothness, and esp. battery life. It might be partly due to the fresh install, but so far, so good. Thank you! The phone is a backup to my Pixel 4a, but has been called upon several times, so having an up-to-date Android on the PH-1 is important for me.
As with the other poster(s), the speaker / mic issue is a problem. My dad, very senior and hard of hearing, has another PH-1, and the issue makes video call difficult for him. Hope you have some time to look into it.
Click to expand...
Click to collapse
Glad you're liking my ROM. Yep, don't worry, I've already started to look into the speakerphone issue
Tomoms said:
Glad you're liking my ROM. Yep, don't worry, I've already started to look into the speakerphone issue
Click to expand...
Click to collapse
I'm glad you're looking into it, it's my number 1 gripe atm. Is there a clear path to fix the speakerphone issue that you see?
Hello, a new build is coming tomorrow together with a possible fix for the speakerphone issue. Come back in 24 hours and you'll find it
{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (marlin) (Download from here)
TWRP (sailfish) (Download from here)
GApps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
Unlock the Bootloader.
Download and install the latest version of SDK Platform-Tools.
Download the latest TWRP version to your PC from the link in the OP and boot it using:
Code:
fastboot boot <name_of_twrp_file>.img
Perform a factory reset and also format the data partition using TWRP.
Download the crDroid version of your liking to your PC (Vanilla version is to be used without GApps, the GApps version already has GApps included.)
Sideload the crDroid Zip:
In TWRP enable adb sideload.
On the PC type:
Code:
adb sideload <name_of_crDroid_downloaded_package>.zip
OPTIONAL: Do you want to install Magisk?
Download the version of your choosing from Magisk's repo (link in OP).
In TWRP tap Reboot and then tap Reboot to recovery and swipe the slider to reboot to recovery.
In TWRP enable adb sideload.
On the PC type:
Code:
adb sideload <name_of_Magisk_package>.zip
Reboot
Done
OPTIONAL: If you installed Magisk, you an check out the magisk modules linked in the OP, they include fixes, add-ons and useful mods for the crDroid builds.
Update installation:
Download the latest TWRP version to your PC from the link in the OP and boot it using:
Code:
fastboot boot <name_of_twrp_file>.img
Download the crDroid update to your PC (Vanilla version is to be used without GApps, the GApps version already has GApps included.)
Sideload the crDroid Zip:
In TWRP enable adb sideload.
On the PC type:
Code:
adb sideload <name_of_crDroid_downloaded_package>.zip
Done
Thanks to @Homeboy76 for helping with the updated flashing instructions.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/blckbearx/android_kernel_google_marlin/tree/lineage-18.1-upstream
Device tree: https://github.com/blckbearx/android_device_google_marlin/tree/crdroid-11
Vendor: https://github.com/blckbearx/proprietary_vendor_google/tree/crdroid-11
Download:
marlin:
Vanilla
GApps
sailfish:
Vanilla
GApps
All builds:
marlin
sailfish
Magisk modules:
GApps Add-on: Flash this Magisk module in order to systemlessly install Android System Intelligence and Google app, thus enabling Live Captions and other functions. This should also work on LineageOS 18.1 if for whatever reason your GApps package doesn't already contain these apps.
Camera patches: This Magisk module enables the long exposure for Camera PX, 2K video recording for both front and back cameras (with OpenCamera or similar), it enables near 4K video resolution for the front camera (with OpenCamera or similar) and it gives Camera PX the proper SELinux permissions in order to process HDR+ images faster. Only use this module on crDroid 7.x.
VoLTE: This Magisk module makes the system always show the VoLTE, ViLTE and VoWiFi toggles regardless of your carrier, useful for people whose service provider supports this options but can't enable them for some reason. Your carrier needs to support VoLTE for marlin/sailfish in the first place, this won't make VoLTE work magically on any carrier. This module can be used on any ROM.
Changelog:
crDroid 7.30 (17/05/2023):
May 2023 Security Patch.
Switched back to Stock+ kernel (I mistakenly built the two previous updates with LineageOS' kernel).
crDroid 7.29 (24/04/2023):
April 2023 Security Patch.
crDroid 7.27 (22/02/2023):
February 2023 Security Patch.
crDroid 7.26 (20/01/2023):
January 2023 Security Patch.
crDroid 7.24 (15/11/2022):
November 2022 Security Patch.
crDroid 7.23 (15/10/2022):
October 2022 Security Patch.
Small kernel improvements.
Boot animation is now fixed.
crDroid 7.22 (7/10/2022):
September 2022 Security Patch.
Reduced zRAM size back to 512MB.
Boot animation is broken, this issue is fixed for October's update.
crDroid 7.21 (22/08/2022):
August 2022 Security Patch.
Reverted fingerprint to March 2018, SafetyNet is now fixed.
A bunch of I/O improvements in the kernel.
crDroid 7.20 (20/07/2022):
July 2022 Security Patch.
Removed PixelPropsUtils. You may need MagiskHide Props Config to pass SafetyNet.
A bunch of kernel improvements.
Renamed kernel to Stock+.
Added USB Fast Charging (you need a kernel manager like FKM to enable it).
Increased minimum CPU frequencies.
Set zRAM size to 1GB.
Added High Brightness Mode (you need a kernel manager like FKM to enable it).
Added Westwood TCP algorithm and set it as default.
Added Backlight Dimmer and enabled it as default.
Enabled High Performance Mode for the Audio DAC.
Some small device tree changes.
crDroid 7.19 (1/07/2022):
June 2022 Security Patch.
A bunch of kernel improvements picked from LunarKernel and NeutrinoKernel (Thanks @Lunarixus and @spezi77).
Added schedutil CPU governor and set it as default.
Reduced GPU idle power level. It should now idle at the lowest power level.
Some small device tree changes.
crDroid 7.18 (18/05/2022):
May 2022 Security Patch.
Dirac Sound Enhancer added.
Some small device tree changes.
crDroid 7.17 (28/04/2022):
April 2022 Security Patch.
Upstreamed kernel to v3.18.140 from v3.18.137.
Removed in-built MatLog as it didn't work quite well and this saves some /system space.
Gave SystemUI acces to thermals, now the CPU Info floating widget should show temperature of the CPU.
Some schedtune and hotplug changes to improve boot times and foreground app performance.
Fixed OEM charger detection. Now when plugging a PD compliant charger the phone should always say that it's fast charging.
Removed the forced availability of VoLTE, ViLTE and VoWiFi for all carriers because it cluttered the UI for people that don't have VoLTE. It's now included in a Magisk module available under the Downloads section.
crDroid 7.16 (16/03/2022):
March 2022 Security Patch.
Removed ih8sn from all builds.
Forced availability of VoLTE, ViLTE and VoWiFi for all carriers (your carrier should support it to use it obviously).
Merged all changes to date from Official LineageOS trees.
crDroid 7.15 (03/03/2022):
February 2022 Security Patch.
GApps version now available.
Removed ih8sn from Vanilla builds.
Updated ih8sn.
Using Official LOS 18.1 trees as base.
crDroid 7.14 (03/02/2022):
Enabled Smart Pixels.
Enabled Smart Charging.
Enabled Always On Display.
Enabled Extra Battery Info.
Enabled OEM Fast Charging detection.
Updated ih8sn and it's configs.
crDroid 7.14 (23/01/2022):
Initial build.
January 2022 Security Patch.
ih8sn included.
Known issues:
None
Visit official website @ crDroid.net
Google Pixel/Pixel XL Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Great work man, love CrDroid one of my fav ROMs. Looking forward to trying this on my Pixel when it comes in the mail. Bought is as a backup device and to tinker with and this will probably be my first ROM.
Thank you for this ROM man!
New Update
Changelog:
crDroid 7.14 (03/02/2022):
Enabled Smart Pixels.
Enabled Smart Charging.
Enabled Always On Display.
Enabled Extra Battery Info.
Enabled OEM Fast Charging detection.
Updated ih8sn and it's configs.
blckbear said:
New Update
Changelog:
crDroid 7.14 (03/02/2022):
Enabled Smart Pixels.
Enabled Smart Charging.
Enabled Always On Display.
Enabled Extra Battery Info.
Enabled OEM Fast Charging detection.
Updated ih8sn and it's configs.
Click to expand...
Click to collapse
Nice to see something new and active.
New Update
Changelog:
crDroid 7.15 (03/03/2022):
February 2022 Security Patch.
GApps version now available.
Removed ih8sn from Vanilla builds.
Updated ih8sn.
Using Official LOS 18.1 trees as base.
Notes:
For GApps version the Google App had to be removed, so it's highly recommended to flash the GApps Add-on Magisk module or download the Google App from the PlayStore to get full functionality.
New Update
Changelog:
crDroid 7.16 (16/03/2022):
March 2022 Security Patch.
Removed ih8sn from all builds.
Forced availability of VoLTE, ViLTE and VoWiFi for all carriers (your carrier should support it to use it obviously).
Merged all changes to date from Official LineageOS trees.
Notes:
For GApps version the Google App had to be removed, so it's highly recommended to flash the GApps Add-on Magisk module or download the Google App from the PlayStore to get full functionality.
I have gps bug on last crdroid. Gps not working
OFFSPRINGER3 said:
I have gps bug on last crdroid. Gps not working
Click to expand...
Click to collapse
Could you be more specific please? I've been daily driving this ROM and I've used the GPS online and offline and it works flawlessly, same with the compass, it works without issue. I've used Google Maps and Magic Earth, both online and offline.
New Update
Changelog:
crDroid 7.17 (28/04/2022):
April 2022 Security Patch.
Upstreamed kernel to v3.18.140 from v3.18.137.
Removed in-built MatLog as it didn't work quite well and this saves some /system space.
Gave SystemUI acces to thermals, now the CPU Info floating widget should show temperature of the CPU.
Some schedtune and hotplug changes to improve boot times and foreground app performance.
Fixed OEM charger detection. Now when plugging a PD compliant charger the phone should always say that it's fast charging.
Removed the forced availability of VoLTE, ViLTE and VoWiFi for all carriers because it cluttered the UI for people that don't have VoLTE. It's now included in a Magisk module available under the Downloads section.
Notes:
For GApps version the Google App had to be removed, so it's highly recommended to flash the GApps Add-on Magisk module or download the Google App from the PlayStore to get full functionality.
New Update
Changelog:
crDroid 7.18 (18/05/2022):
May 2022 Security Patch.
Dirac Sound Enhancer added.
Some small device tree changes.
Notes:
For GApps version the Google App had to be removed, so it's highly recommended to flash the GApps Add-on Magisk module or download the Google App from the PlayStore to get full functionality.
I came back to CrDroid after PE and Lineage OS, works perfect! Thanks again!
Firmware works great, the one thing I'd say is to be careful with Smart Pixel as it seems to be "Rendering above all applications". making it impossible to use, say, Google Play to install applications or to set permissions.
blckbear said:
New Update
Changelog:
crDroid 7.18 (18/05/2022):
May 2022 Security Patch.
Dirac Sound Enhancer added.
Some small device tree changes.
Notes:
For GApps version the Google App had to be removed, so it's highly recommended to flash the GApps Add-on Magisk module or download the Google App from the PlayStore to get full functionality.
Click to expand...
Click to collapse
Great job with the rom ty
blckbear said:
New Update
Changelog:
crDroid 7.18 (18/05/2022):
May 2022 Security Patch.
Dirac Sound Enhancer added.
Some small device tree changes.
Notes:
For GApps version the Google App had to be removed, so it's highly recommended to flash the GApps Add-on Magisk module or download the Google App from the PlayStore to get full functionality.
Click to expand...
Click to collapse
Have you been able to install an android 12 or 13 dsu next to the latest build? Every time I try it fails half way through
.. 32gb sailfish... I have 20gb free space... thank you
spiral777 said:
Have you been able to install an android 12 or 13 dsu next to the latest build? Every time I try it fails half way through
.. 32gb sailfish... I have 20gb free space... thank you
Click to expand...
Click to collapse
What's a dsu? I never tried flashing anything related to A12 or A13, I'm just happy with 11 for now lol.
Something that could be an issue may be partition size, newer android versions take lots of space and usually require the device to be repartitioned.
blckbear said:
What's a dsu? I never tried flashing anything related to A12 or A13, I'm just happy with 11 for now lol.
Something that could be an issue may be partition size, newer android versions take lots of space and usually require the device to be repartitioned.
Click to expand...
Click to collapse
Thank you for responding to comments
spiral777 said:
Thank you for responding to comments
Click to expand...
Click to collapse
Well, now that I've seen the video I can tell you that partitions are indeed the problem. The OG Pixel does not have dynamic partitions and does not have a big enough system partition for most A12 GSIs either, so if you want to try A12, you'll need to try phh's GSI with a reparted system.
blckbear said:
Well, now that I've seen the video I can tell you that partitions are indeed the problem. The OG Pixel does not have dynamic partitions and does not have a big enough system partition for most A12 GSIs either, so if you want to try A12, you'll need to try phh's GSI with a reparted system.
Click to expand...
Click to collapse
Again thank you I'm a little hesitant to repartition... Need to learn more about it... Any further details on how to repart the system?
And I guess I don't understand the difference between A/B and dynamic partitions... Thought that's what it was
spiral777 said:
Again thank you I'm a little hesitant to repartition... Need to learn more about it... Any further details on how to repart the system?
And I guess I don't understand the difference between A/B and dynamic partitions... Thought that's what it was
Click to expand...
Click to collapse
You're welcome.
For the partitions, the Pixel has some cloned partitions (A and B partitions. For example: system_a and system_b, boot_a and boot_b, etc.) and then a common partition which is the user data partition.
You can flash different ROMs on each partitions, but it won't work because they both will use the same user data partition generating conflicting data and data corruption if encrypted.
Dynamic partitions are, from what I understand, partitions that can be dynamically resized, which means that you can flash a ROM of any size because the partition will always adapt. With dynamic partitions you can flash big GSIs without issue.
For reparting the Pixel, there's an easy way which is using the repartition script found in the PixelExperience installation guide, or you can follow the following guide on how to do it manually.
The guide was removed