Related
OmniROM is our Android custom ROM variant, feature-packed but always with stability as #1 priority in mind.
Based on the Android Open Source Project (AOSP) and enriched by our developers with lots of custom enhancements, OmniROM has set out to give you a great Android experience on your mobile.
Code:
* 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.
Compatible device?:
Code:
[LIST]
[*]P8 Lite 2017.
[*]P9 Lite 2017.
[*]P10 Lite.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
TWRP, flash my latest build to avoid error 7 from here.
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
Working:
Audio.
Bluetooth.
Camera: it's fully works with stock or other apps .
Display.
Graphis: both gralloc & hwcomposer.
Lights.
NFC.
RIL.
Sensors.
Storages.
Wifi
Bugs:
tell me.
Downloads:
Code:
[B][I]**21/05/2018**[/I][/B]
[LIST]
[*][URL="https://www.haky86.com/2018/05/21/omnirom-nougat-hi6250/"]From Haky's Blog[/URL]
[/LIST]
Changelogs:
Code:
[B][I]**21/05/2018**[/I][/B]
[LIST]
[*]re-works
[/LIST]
Source Code:
Device Tree:
https://github.com/hak86/android_device_huawei_hi6250
Kernel GPL:
https://github.com/hak86/android_kernel_huawei_prague
Vendors:
https://github.com/hak86/android_vendor_huawei_hi6250
XDA:DevDB Information
OmniROM for PRA-LX1, ROM for the Huawei P8lite/P8 Lite
Contributors
haky 86, Meticulus
Source Code: https://github.com/hak86?tab=repositories
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 5.x "C432B161"
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-01-17
Created 2018-01-17
Last Updated 2018-01-17
ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.
*reserved v2*
Download Link is not working
Edit: There is a " in the end of the link that shouldn't be there.. Maybe you should edit the link
Zillinda said:
Download Link is not working
Edit: There is a " in the end of the link that shouldn't be there.. Maybe you should edit the link
Click to expand...
Click to collapse
fixed
I have a totally weird issue on this ROM. I don't have this issue on any of your ROMs except this one.
When i use your vendor my SIM Card is not detected (even if i disable Dual Sim and reboot)
But the weird thing is, when i flash my stock vendor from P10 Lite the Sim is working BUT the sound is not working.
I flashed this one like every ROM from you, and every ROM worked but not this one :/
Are you using the latest Code of Meticulus? Because i had this issues with earlier builds of Meticulus' ROMs
Except that everything works fine. I will go back to your fully working SlimROM until you release AOSPExtended.
Zillinda said:
I have a totally weird issue on this ROM. I don't have this issue on any of your ROMs except this one.
When i use your vendor my SIM Card is not detected (even if i disable Dual Sim and reboot)
But the weird thing is, when i flash my stock vendor from P10 Lite the Sim is working BUT the sound is not working.
I flashed this one like every ROM from you, and every ROM worked but not this one :/
Are you using the latest Code of Meticulus? Because i had this issues with earlier builds of Meticulus' ROMs
Except that everything works fine. I will go back to your fully working SlimROM until you release AOSPExtended.
Click to expand...
Click to collapse
In your case you must edit the /vendor/phone.prop file
* search for [0X3B412000]
* and make sure to set the following string.
persist.radio.multisim.config=single
persist.dsds.enabled=false
* save and reboot.
you get this problem because my vendor.img is designed to run with single sim devices only.
AOSPE will be available after AOSPA Paranoid, isn't available on any hi6250 device as I see.
Edit: remove persist.radio.multisim.config=single, save and reboot.
haky 86 said:
In your case you must edit the /vendor/phone.prop file
* search for [0X3B412000]
* and make sure to set the following string.
persist.radio.multisim.config=single
persist.dsds.enabled=false
* save and reboot.
you get this problem because my vendor.img is designed to run with single sim devices only.
AOSPE will be available after AOSPA Paranoid, isn't available on any hi6250 device as I see.
Edit: remove persist.radio.multisim.config=single, save and reboot.
Click to expand...
Click to collapse
Thanks, i will try it now.
But why don't i have this issue with your other ROMs?
Zillinda said:
Thanks, i will try it now.
But why don't i have this issue with your other ROMs?
Click to expand...
Click to collapse
it's releated to vendor.img partition since it's designed to run on single sim.. just fix the flags I wrote and will get fixed.
a thing you should do manually on dual sim phones.
haky 86 said:
it's releated to vendor.img partition since it's designed to run on single sim.. just fix the flags I wrote and will get fixed.
a thing you should do manually on dual sim phones.
Click to expand...
Click to collapse
I get error, that it's Read-Only File system and if i want to change the permission of the file with Root Browser it says Changing permissions was not successful. Both the Editor and the Root Browser have root permissions.
Edit: i see the file is symlinked to /hwvendor/phone.prop so i edited it inside there but it's still not working
Zillinda said:
I get error, that it's Read-Only File system and if i want to change the permission of the file with Root Browser it says Changing permissions was not successful. Both the Editor and the Root Browser have root permissions.
Edit: i see the file is symlinked to /hwvendor/phone.prop so i edited it inside there but it's still not working
Click to expand...
Click to collapse
set via adb shell and tell us if fixed
setprop persist.radio.multisim.config single
setprop persist.dsds.enabled false
haky 86 said:
set via adb shell and tell us if fixed
setprop persist.radio.multisim.config single
setprop persist.dsds.enabled false
Click to expand...
Click to collapse
nope, i don't know if i am too stupid or if it's really not working, but none of this methodes is working.
Zillinda said:
nope, i don't know if i am too stupid or if it's really not working, but none of this methodes is working.
Click to expand...
Click to collapse
well, as you see it's working for me in screenshots.
I finally got it working by replacing the /hwvendor/phone.prop file from my STOCK vendor into the vendor of @haky 86.
@haky 86
Intalled the C432B161 firmware, then proceed to flash this rom with your instructions, everything works except video recording on camera, also for whatsapp, facebook, messenger, etc
Any hints ? Maybe I missed something
rubentkato77 said:
@haky 86
Intalled the C432B161 firmware, then proceed to flash this rom with your instructions, everything works except video recording on camera, also for whatsapp, facebook, messenger, etc
Any hints ? Maybe I missed something
Click to expand...
Click to collapse
Enable Google H264 in Settings -> Extra
Sent from my hi6250 using XDA Labs
Zillinda said:
Enable Google H264 in Settings -> Extra
Sent from my hi6250 using XDA Labs
Click to expand...
Click to collapse
Already did that and reboot the phone, but the problem persist.
[/ATTACH]
rubentkato77 said:
Already did that and reboot the phone, but the problem persist.
[/ATTACH]
Click to expand...
Click to collapse
what is your device?also did you flash my vendor partition?
haky 86 said:
what is your device?also did you flash my vendor partition?
Click to expand...
Click to collapse
I bought it as P9 Lite 2017 PRA-LX3C69B110 branded from Telcel Mexico, then converted PRA-LX1C432B110 dual sim unbranded and got updated to B170.
Then unlock bootloader, instal your latest TWRP, follow your unbrick guide fro C432B161.
Then flash omni ROM + pico gapps.
In some point I didn flash your vendor img (how did I miss that !#@$!) do I needto flash it again before omni rom or after?
Regards. :good:
rubentkato77 said:
I bought it as P9 Lite 2017 PRA-LX3C69B110 branded from Telcel Mexico, then converted PRA-LX1C432B110 dual sim unbranded and got updated to B170.
Then unlock bootloader, instal your latest TWRP, follow your unbrick guide fro C432B161.
Then flash omni ROM + pico gapps.
In some point I didn flash your vendor img (how did I miss that !#@$!) do I needto flash it again before omni rom or after?
Regards. :good:
Click to expand...
Click to collapse
well yes, you have to flash my own vendor from unbrick guide!
but before doing that pull /vendor/phone.prop from converted firmware and paste into system/vendor/ to avoid sim problems.
as you see my screenshot the camera is fully works without enable google codecs.
Paranoid Android is a custom ROM aiming to extend the system, working on enhancing the already existing beauty of Android and following the same design philosophies that were set forward by Google for Android Open Source Project.
Code:
* 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.
Compatible device?:
Code:
[LIST]
[*]All devices that use hi6250 chipset and use kernel 4.1.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
TWRP.
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
This ROM is provided by CodeOfHonor
Installation Guide:
Make sure to the stock backup saved on pc, I'm not responsible for any bricked or damage.
Reboot to TWRP.
Go to Wipe.
Choose Advance Wipe.
Check on Data and change file system to EXT4, will not ever boot with F2FS.
Wipe cache, data, dalvik and system.
Flash the rom.
Reboot and have fun then.
Working:
Audio.
Bluetooth.
Camera: it's fully works with stock or other apps .
Display.
Graphis: both gralloc & hwcomposer.
Lights.
NFC.
RIL.
Sensors.
Storages.
Wifi
Bugs:
Dual sim might will not work all variants, so don't waste your time by asking me to fix it.
You don't like it?, easy revert to Emui 5.x.
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Source Code:
Device Tree:
https://github.com/codeofhonor-dev/android_device_huawei_hi6250
Kernel GPL:
https://github.com/codeofhonor-dev/android_kernel_huawei_hi6250
Vendors:
https://github.com/codeofhonor-dev/android_vendor_huawei_hi6250
XDA:DevDB Information
AOSPA Paranoid for Hi6250, ROM for the Honor 6X
Contributors
haky 86, HassanMirza01, felix-development
Source Code: https://github.com/codeofhonor-dev, Meticulus and the stuff of CodeOfHonor.
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Emiui 5.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.3.1
Stable Release Date: 2018-04-27
Beta Release Date: 2018-04-27
Created 2018-04-27
Last Updated 2018-04-27
ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.
I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out
MadMurl0c said:
I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out
Click to expand...
Click to collapse
10% mark?
Did you entirely remove all the fingerprints before flashing this Tom?
Go back to Elite or Stock, remove all fingerprints and reinstall the Rom
For Root, you can try changing recovery or using an older version of Magisk that worked for you
I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't
After I downgrade from emui 8 to emui 5 in 5 minutes now I can fix this rom so expect a build within these days
hoping to try this rom , following for updates
Hey guys I just installed the rom, but I did notice that I don't have access to any Gapps. How to I install them? I'm using TWRP. I was just able to get my unlock code from Honor today, so I unlocked and rooted, and flashed your rom as the first thing, so I'm running a fresh flash of the latest version.
Flash package with Twrp: https://opengapps.org/
Thanks guys, I realized that yesterday right after I posted lol. So far I'm really loving the plain stock-ness of this rom, hopefully it give the device some more life so I won't have to upgrade soon.
MadMurl0c said:
I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't
Click to expand...
Click to collapse
Yeah I'm having the same issue to, with no root.
Can someone tell me why this rom is different to all others ? Why is this one using stock vendor and can we easy revert to Emui ? Why don't all others ?
I'm on stock now.
How is the quality of the photos compared to stock rom? It is possible to install Emui camera or other huawei cameras?
** Note **
developments of hi6250 is end reason: switch to another phone, have phone.
** Note **
Developments for hi6250 has been resumed but just for this ROM, sorry for the inconvenience.
I'm already downloading the source for releasing new build but AOSPA will take a wile since have bigger source.
** Note **
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Had anyone tried installing Xposed yet?
Support BLL version? Honor 6X
The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.
MadMurl0c said:
The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.
Click to expand...
Click to collapse
Guys to flash magisk or superSU use Meticulus TWRP, other twrp like eliteTwrp show an error when it is recompilling the boot.img
{
"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:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Images
Here are some Screenshots of this ROM.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Format data to get rid of encryption.
Install ROM.
Install 9.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional
Update:
Get the latest build
Boot into TWRP
Flash the downloaded build
Reboot, if you don't wipe system backuptool will handle to reapply your modifications, for example: GApps.
Changelog
Code:
Changelog 2019-10-07
* Fixed offmode charging at Wall chargers (previously bright screen)
* Fixed offmode charging at computers (previously reboot loop)
Old Changelogs
Code:
Changelog 2019-10-06
* Fixed camera for everyone
* Set media volume steps to 25 and voice call volume steps to 7
* Actually use our cache partition, previously we were using a link to /data/cache instead of mounting the cache partition as /cache
* Cleanup of rootdir scripts
Code:
Changelog 2019-08-28
* Rolled fingerprint back to Sony's 5.1.1 fingerprint
-> safetynet CTS check works again
* Set original shipping API level to KitKat
* Minor cleaning
Code:
Changelog 2019-08-14
* Singificantly improved GPS
* August Android Security Bulletin
* Cleaned, script generated vendor
Code:
Changelog 2019-08-05
* Attempt to fix ANT+
* Added settings to control the camera button
Code:
Changelog 2019-07-08
* July Android Security Bulletin
* Rebased Linux 3.4.113 Kernel
-> Solved video recording lags with Snap
Code:
Changelog 2019-06-15
* Fixed Audio problems
* LED Notifications work again
* Manual Network selection fixed
Code:
Changelog 2019-06-07
* June Android security Bulletin
* LED seems to work with notifications now
* 4.0 Audio HAL -> NO, this does NOT fix our problems :/
Code:
Changelog 2019-05-10
* Enforcing sepolicy
* Fixed sensors
* Fixed FM Radio
* Fixed EXFat, sdfat and vfat
* Camera works fine
* May Android Security Bulletin
* Sound seems fixed - Maximum Volume still decreases still after a few seconds when using internal speakers
Code:
Changelog 2019-05-06
* Fixed AudioFX
* Fixed Camera
Code:
Changelog 2019-04-24
* Fixed Notification LED
Code:
Changelog 2019-02-19
* Fixed GPS
* Fixed Video Playback
Code:
Changelog 2019-01-09
* Fixed Bluetooth
Downloads
Download the ROM
Sources
DEVICE:
https://github.com/z3c-pie/device_sony_z3c
https://github.com/z3c-pie/device_sony_msm8974-common
https://github.com/z3c-pie/device_sony_shinano-common
KERNEL:
https://github.com/z3c-pie/kernel_sony_msm8974
Addons
OpenGapps
Magisk
SU-Addon
Thanks
Whole LineageOS Team for this amazing ROM
@rcstar6696
@Myself5
@drakonizer
@tomascus
@koron393
@nailyk
@SpiritCroc
I hope I haven't forgot anyone
Bugs
WHAT'S BROKEN
4K Video recording doesn't work in stock camera, but works for example in OpenCamera.
You tell me.
FAQ
Q: Why i can't reboot into the recovery from advanced reboot?
A: Because you have installed Magisk 19.1 which breaks it. Keep up to date here: https://github.com/topjohnwu/Magisk/issues/1418 - fixed by @Myself5 since 2019.05.20
XDA:DevDB Information
[9] LineageOS 16.0 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: lineage-16-20190510
Stable Release Date: 2019-05-10
Created 2019-01-05
Last Updated 2019-10-10
TWRP 3.3.1 for our z3c out of an Android 9.0 environment!
Changes:
Code:
3.3.1-0.4-z3c
* Fixed fastboot boot
* Added bootlogo
* Dropped TWRP App
Code:
3.3.1-0.3-z3c
* Fixed encryption when security patch level doesn't match the recovery's
- [url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/411862532c247aea2c7b48d52aa596b40305e9ea[/url]
Code:
3.3.1-0.2-z3c
* Added a script to handle the CPU
-> increased the battery life significant ([url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/63f864068ad2f17ae2f1202b4edc311d74e2803d[/url])
Code:
3.3.1-0.1-z3c
* Fixed time
* Further Clean up's
Code:
3.3.1-0-z3c
* Switched from Android 6.0 to Android 9.0 environment
* Completely reworked tree
* Working decryption
The latest build is attached to this post.
Old builds are available here: https://sourceforge.net/projects/ephedraceae/files/z3c/twrp/
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-9.0
How to install this build:
Rename the downloaded twrp image to twrp.img
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse
Reserved
Hi, I can't open your thread in XDA Labs app, I suppose that's the case of many people and that's why there is not much views and comments on this thread.
I didn't tried yet your ROM but it sound great and will try it ASAP.
Also which recovery do you recommend to avoid errors like error 7 (if I remember) ?
Also will you continue to work on RR ?
EDIT : after posting this comment via browser, I can now open this thread in XDA Labs
EDIT 2 : everything is working
SUPER KOKA said:
Hi, I can't open your thread in XDA Labs app, I suppose that's the case of many people and that's why there is not much views and comments on this thread.
I didn't tried yet your ROM but it sound great and will try it ASAP.
Also which recovery do you recommend to avoid errors like error 7 (if I remember) ?
Also will you continue to work on RR ?
EDIT : after posting this comment via browser, I can now open this thread in XDA Labs
Click to expand...
Click to collapse
I use twrp-3.2.3 from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192.
I don't know yet about RR. I wanna see first whether we can get Bluetooth and gps working as soon as possible.
https://sourceforge.net/projects/ep...age-16.0-20190109-UNOFFICIAL-z3c.zip/download
Another build was uploaded with the latest lineageos updates including the January android security bulletin. On the device side Bluetooth was fixed
Installed without any problems
You did a great job!
Installed without any problems. It seems all functions work fine!
update
I've been in lineage, whether for the latest version update I have to hard reset or like the ota update
SUPER KOKA said:
EDIT 2 : everything is working
Click to expand...
Click to collapse
Great to hear!
CDLion said:
You did a great job!
Installed without any problems. It seems all functions work fine!
Click to expand...
Click to collapse
Thanks!
muhibbuddin irsyad said:
I've been in lineage, whether for the latest version update I have to hard reset or like the ota update
Click to expand...
Click to collapse
To be honestly I can't follow you. Do you mean that you don't know how to update the build? For this case you have to download manually and flash it in TWRP. There are no wipes needed.
Hi, thanks for this and how is the battery performance?
Any plans for making an LineageOS for microG rom?
Thanks for the ROM, I am using it right now, everything is working good except the camera. Can take photos, but video is not working. When I'm switching to video, the app is freezing and stuck. I tried to use the stock camera with magisk, it can't take photos or video neither. Tried manual camera too, it can take photos but no video.
etram said:
WOW ... !!!
Great Job.
What about the notification LED?
Click to expand...
Click to collapse
Just tested shortly, it seems to be broken, I will add to broken things list. Thanks to notify (?)
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
frht5382 said:
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
Click to expand...
Click to collapse
I try and I install 20180105 build but I cant install new build why ?
twrp 255 error
frht5382 said:
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
Click to expand...
Click to collapse
frht5382 said:
I try and I install 20180105 build but I cant install new build why ?
twrp 255 error
Click to expand...
Click to collapse
Are you sure that you use the recovery from here?
https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192
NeoArian said:
Are you both sure that you use the recovery from here?
https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192
Click to expand...
Click to collapse
Solved.I dowloaded false file which 632 mb.Now I re download true file and it work thank you
frht5382 said:
Yes I am sure.I install 2019 01 05 build it work but I try 20190109 fail everytime error code 255
edit
I've just realized I clik download button and if I download latest version green color button I download 631 mb but down of button lineage-16.0-20190109-UNOFFICIAL-z3c.zip 448 mb which one should I download ?
why different size ?
Click to expand...
Click to collapse
The 631mb Rom is for my Xiaomi Mi 6, you have to use the one for z3c
NeoArian said:
Tue 631mb Rom is for my Xiaomi Mi 6, you have to use the one for z3c
Click to expand...
Click to collapse
I installed thank you .How to enable root access? Or magisk work ?
frht5382 said:
I installed thank you .How to enable root access? Or magisk work ?
Click to expand...
Click to collapse
Magisk works.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 17.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 17.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Changelog:
2019.10.24
Initial release
2019.10.25
Sync latest source
Fix bluetooth
2019.11.20
Sync latest source
Fix wifi display
Ship Snap
Fix vulkan graphics
Pass safetynet
Fix crash of some native services
2019.12.31
Sync latest source
SELiunx working in enforcing mode now
Update kernel to LA.UM.8.6.r1-02900-89xx.0
Update blobs from OOS 9.0.6
Fix suspend when AOD is on
Happy new year!
2020.1.12
Sync latest source
Fix ril of the last build
Update blobs from LA.UM.8.6.r1-02900-89xx.0
Add backuptools
Other trivial fixes
2020.4.2
Official nightlies started
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: Android 10
Version Information
Status: Nightly
Created 2019-10-24
Last Updated 2020-06-26
Any recommendations which gapps to use?
Why not the official ones? https://sourceforge.net/projects/opengapps/files/arm64/beta/20191006/
is this with kernel 4.4?
helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
https://github.com/LineageOS/android_kernel_oneplus_msm8996/blob/lineage-17.0/Makefile#L1-L3
helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
dianlujitao said:
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T.
Click to expand...
Click to collapse
OP needs some changes its for LOS 17 instead of 16 [emoji3][emoji39]
Sent from my ONEPLUS A3003 using Tapatalk
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Master_TC said:
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
Click to expand...
Click to collapse
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
mady51 said:
ya i built it once but it didn't booted. after that didn't spent time on it. may be ill give it another try soon
Click to expand...
Click to collapse
Anyway amazing work @dianlujitao you're one of our heroes ???
Viper The Ripper said:
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
Anyway amazing work @dianlujitao you're one of our heroes ???
Click to expand...
Click to collapse
https://github.com/dianlujitao/android_kernel_oneplus_msm8996 @dianlujitao did bring up a 4.4 kernel but it has issues.
Jus asked because of this
mvalda01 said:
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Click to expand...
Click to collapse
Can you provide more info such as logs, my aptx headset works fine here.
Thanks for the effort,nice rom for nice phone.
From Op3 owner
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the report, bluetooth should be fixed in 1025 build, for Digital Wellbeing crash you should probably report to opengapps devs, I'm not sure.
NFC works fine for me, it wound be nice if you could grab related logs.
Well done @dianlujitao!
Thanks for your work @dianlujitao! I'll probably flash next build
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
MJPollard said:
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
Click to expand...
Click to collapse
You need to pick - at least - https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/255737 from https://review.lineageos.org/q/project:LineageOS%2Fandroid_device_oneplus_oneplus3+status:open, maybe all.
There's a good reason why OP calls it an experimental build instead of alpha or beta... Rebuilding experimental needs skilld and patience...
EDIT:
For the blobs commits (i.e. https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/260573 and https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/262330) see also https://github.com/dianlujitao/proprietary_vendor_oneplus/commits/lineage-17.0 .
BillGoss said:
- Digital Wellbeing keeps stopping (logs attached)
Click to expand...
Click to collapse
On some other Android 10 ROM, force stopping, disabling and then re-enabling solved this issue.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
Flashing Instructions:-
TinyFastbootScript:-
Make sure to wipe userdata
1. Download TinyFastbootScript
2. Download the ROM named *Images*
3. Unpack TinyFastbootScript and the ROM into the same directory
4. Run the bat file for TinyFastbootScript
5. Choose latest fastboot version
6. Place device in bootloader mode
7. Run the command for flashing custom firmware
8. Done!
Lineage Recovery:-
Make sure to wipe userdata, ensure you have at least taken one stock OTA!
1. Download LOS Recovery image
2.
Code:
fastboot flash boot LOSrecovery.img
3.
Code:
fastboot reboot recovery
4. Touch Apply Update -> Apply from ADB
5.
Code:
adb sideload lineage-18.1-20210712-HOMEMADE-nio.zip
6. Reboot and Done!
Bugs :
YOU TELL ME
* Drop a comment down below if you need any help, you can also Join https://t.me/electimonrel on telegram if you need any help.
Downloads:
Lineage-Modded:
https://build.lolinet.com/file/lineage/nio/
Lineage-Modded Recovery:
https://build.lolinet.com/file/lineage/nio/LOSrecovery.img
Contributors
@Electimon, @erfanoabdi
Source Code: moto-sm8250
Version Information
Status: Stable
Updated: June 21 2021: Fixed safetynet, and June Patch
June 25: Fix some audio issues and readd pixel live walls
July 7: ↓ Build: 131
Updated Vendor Blobs to May Security Patch
Updated GPS/Location to LA.UM.9.12.r1-11500-SMxx50.0
Enabled Touch in LineageOS Recovery
Allow for unsigned packages to be flashed in LineageOS Recovery (e.g. Magisk)
Updated GPS Configuration files
Merged Latest CAF Tag to kernel
Upstream Sched / Improved Performance
Add SIM Switch Tile
Enabled Notification and Battery LED
July 12: ↓ Build: 138
Improved Memory Management
Misc Kernel Improvements
July Security Update
October -2: ↓ Build: 156
• Hopefully fixed Android Auto
• Updated blobs to pstar
• Added Assistant key remapping and double tap fingerprint gestures
• Added my new VoidKramel Venus kernel built with clang 12 and fully upstreamed
• Switched to source built DTB/DTBO
• Improved refresh rate timers
• ModSettings has a brand new adaptive icon
• Switched ZRAM sizes per ram variant
• Lastly, updated security patches
Excited to hear this~ have been using Lineage in my old OP X & OP 3T
Amazing news, the first ROM for our G100/EdgeS arrived, I will test 4 sure , thanks dev !
If anyone succeeds at rooting with this ROM can you provide instructions? TIA
Timmons said:
If anyone succeeds at rooting with this ROM can you provide instructions? TIA
Click to expand...
Click to collapse
Just to know, I guess this rom will remove support for the "Ready For" platform for games and app and also other moto specific modules?
draxema said:
Just to know, I guess this rom will remove support for the "Ready For" platform for games and app and also other moto specific modules?
Click to expand...
Click to collapse
It will retain gestures and moto camera
June patch read post
-130 build, read post
may I ask: Does the ROM come without Google dependencies / GApps?
Hiajen said:
may I ask: Does the ROM come without Google dependencies / GApps?
Click to expand...
Click to collapse
Comes with
Electimon said:
Comes with
Click to expand...
Click to collapse
Hello, keep the motorcycle camera? but I will lose some functions of series I have in moto edge s 5g chinese version but I like to fiddle I already have my motorcycle unlocked and I want to test the rom thank you very much for working but I have to do memory to reinstall the chinese rom that I have as standard I suppose I want the boot img there will be root in lineage thank you very much
• Improved Memory Management
• Misc Kernel Improvements
• July Security Update
Updated, please reread post
Hello
Please tell me what is the difference between
lineage-18.1-2021xxxx-HOMEMADE-nio.zip
and
Lineage-images-18-2021xxxx-xxxx-nio-1xx.zip?
There is a 300M difference in size.
dfert said:
Hello
Please tell me what is the difference between
lineage-18.1-2021xxxx-HOMEMADE-nio.zip
and
Lineage-images-18-2021xxxx-xxxx-nio-1xx.zip?
There is a 300M difference in size.
Click to expand...
Click to collapse
One is most obviously a set of images and the other a OTA package.
Hello, 2 more questions:
1, "July 7: ↓ Build: 131 Enabled Notification and Battery LED"
my Edge S do not have a LED, how it show after flash this ROM?
2, How large the GApps it has? Only google service and google play or have a lot of google apps like gmail/youtube/maps/driver/assistant etc?
dfert said:
Hello, 2 more questions:
1, "July 7: ↓ Build: 131 Enabled Notification and Battery LED"
my Edge S do not have a LED, how it show after flash this ROM?
2, How large the GApps it has? Only google service and google play or have a lot of google apps like gmail/youtube/maps/driver/assistant etc?
Click to expand...
Click to collapse
It does have a LED, it just isn't enabled by default.
The GApps is a standard package you will find on stock.
Electimon said:
It does have a LED, it just isn't enabled by default.
The GApps is a standard package you will find on stock.
Click to expand...
Click to collapse
Nice, LED is very useful!
But I hate youtube/assistant/one, etc, could you please only contain google service and google play in the new release ROM? Thanks!
dfert said:
Nice, LED is very useful!
But I hate youtube/assistant/one, etc, could you please only contain google service and google play in the new release ROM? Thanks!
Click to expand...
Click to collapse
Unfortunately not. You can uninstall the apps with magisk.
Touch screen fixed???