{
"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'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (nougat), which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera (Photo/Video/Flashlight)
Audio
Fingerprint sensor
DT2W
Keydisabler
Notification LED
Torchlight
Broken
You tell me
Source code:
device tree: https://github.com/HighwayStar/android_device_nubia_nx551j
device-common: https://github.com/HighwayStar/android_device_nubia_msm8953-common
kernel: https://github.com/HighwayStar/android_kernel_nubia_msm8953
vendor: https://github.com/HighwayStar/android_vendor_nubia
Clean code with kernel rebased on top of latest caf nougat msm8953 tag. Warning! this rom uses forceencrypt flag for /data partition, same as global stock rom. If you coming from Chinese ROM or other not encrypted /data ROM your first boot can take long. Do not reboot while encrypting, or you will lost all your data. It's recommend to make backup.
Download
2018-09-17
Fixed headset detection issue
Updated Lineage code
gdrive: lineage-14.1-20180917-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180917-UNOFFICIAL-nx551j.zip
Previous versions:
2018-08-22
Moved to common device tree with Nubia Z11 mini s nx549j
Removed unused camera libraries
Fixed Neocharge in offline-charging mode
Updated Lineage code
gdrive: lineage-14.1-20180822-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180822-UNOFFICIAL-nx551j.zip
2018-07-20
* Fixed Google camera crash in HDR+ mode in low-light conditions
* Fixed color "jumps", "blinks", "grayish color" in all HAL3 apps
* Looks like fully working HAL3 mode here
gdrive: lineage-14.1-20180720-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180720-UNOFFICIAL-nx551j.zip
2018-07-16
* Test build with opensource camera HAL. It enables HAL3 mode, but may also add some issues, please test if camera apps you are using is still working fine. Google camera mods working too, with HDR+ in Nexus 5X or Nexus 6P mode(tested with MGC_5.1.018.177624777-41364271.apk (BSG, 2018-07-12) version)
gdrive: lineage-14.1-20180716-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180716-UNOFFICIAL-nx551j.zip
2018-07-10
* Fixed phone crash when using dual sim.
* Set LTE mode on first run to allow to use mobile data for setup
* Added thermal daemon configs to control device temperature
gdrive:lineage-14.1-20180710-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180710-UNOFFICIAL-nx551j.zip
2018-07-09
* Fixed Phone app crash on Enable/Disable Airplane mod
* Fixed torchligh
* Fixed notification LED. Now buttons backlight red leds blinking on notification
gdrive: lineage-14.1-20180709-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180709-UNOFFICIAL-nx551j.zip
2018-07-04
Fixed high CPU load and high CPU frequencies issue
Removed FM Radio app
Added LTE option to SIM network menu
Fixed call recording
Fixed displayed battery capacity
gdrive: lineage-14.1-20180704-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180704-UNOFFICIAL-nx551j.zip
2018-07-02
Initial build
gdrive: lineage-14.1-20180702-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180702-UNOFFICIAL-nx551j.zip
To install this you have to install TWRP first. I can recommend this version, built with same kernel as ROM. nx551-twrp-3.2.1.img
If you want to use google apps use ARM64 Android 7.1 opengapps package https://opengapps.org/.
If you need root use Lineage addonsu or Magisk
XDA:DevDB Information
[ROM][UNOFFICIAL][7.1.2][nx551j] LineageOS 14.1 for Nubia M2 [17/09/2218], ROM for all devices (see above for details)
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_kernel_nubia_msm8953
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: No Longer Updated
Created 2018-07-02
Last Updated 2018-09-17
Thanks for the work you've done. In the future, plan to go to the official assembly?
Big thanks.
LuigeUA said:
Thanks for the work you've done. In the future, plan to go to the official assembly?
Click to expand...
Click to collapse
Yes, code is done as clean as possible way to be able to go official. To go official it has to be rebased to oreo first. It should be not that hard now.
I can not adjust my fingerprint, go to my home screen when scanning
LuigeUA said:
I can not adjust my fingerprint, go to my home screen when scanning
Click to expand...
Click to collapse
Had this issue too. Have not found fix yet. Workaround is to setup one fingerprint on first boot, it not goes home here. Second fingerprint can be added anytime later, , there is no such issue with second and later fingeeprints.
Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.
estuardo4 said:
Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.
Click to expand...
Click to collapse
Please install twrp from the first post. It should help.
Api
Hi , amazing work bringing nougat for us , thanks...
I'm testing for few hours and i tried many camera apps without lucky.. tried to enable camera2api for gcam and get force stopped in all cameras , could you help me ?
Another question is , will you bring future updates by OTA ?
Thanks a lot , wonderfull job.
estuardo4 said:
Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.
Click to expand...
Click to collapse
it only works with the twrp that is for download on the linage rom downloadpage ,had the same issue.
i did flash the twrp that is advised and did work perfectly.
rolandvb said:
it only works with the twrp that is for download on the linage rom downloadpage ,had the same issue.
i did flash the twrp that is advised and did work perfectly.
Click to expand...
Click to collapse
Is there other way to install? Yesterday I flashed the persistance.img posted by Mauronofrio without problems and now, for the life of me, I can't get my Win10 machine to recognize my device. I uninstalled, restarted with the option of not checking for signature files, installed, nothing. Uninstalled and installed old drivers and nothing. Uninstalled and installed the newest versions from Google and nothing. My win10 pc can't recognize my Nubia
And yes, I tried to make a working USB live image with FWUL but I don't have the technical knowledge to know whats going on and why I can't use it with my Nubia.
Did test this android 7.1 OS this evening, and there are some bugs,the camera did not work on my phone and goty black screen,with other app camara did work
fingerprintscanner did not work properly and could not remove or add fingerprints ,also phone sometimes loses and has to search again for 4g network while using phone
and got symcard message while sym alreddy did work.
hope you can do something about these issues.
i can say the phone is a lot faster an snappyer compaired to all other roms i did test
it would be great if android 8 will come available with this OS, this will make this phone a up to date phone for a bargain!
I think the M2 will even be faster on android 8
afther testing and tryed to restore my older rom i just backed up my the phone it did not boot and ended with a bick
i did restart phone in twrp and did flash the twrp i did use before and everything was ok again.
So the`re seem to be TWRP ussues between different versions, i did use the original twrp that was relased by TWRP app
First, thanks for the good work. I have found a serious bug, there is no processor frequency control and it is always full. Then heat the phone and drain the battery.
bumperiano said:
First, thanks for the good work. I have found a serious bug, there is no processor frequency control and it is always full. Then heat the phone and drain the battery.
Click to expand...
Click to collapse
Yes, something broken here, will check it out.
The processor constantly operates at the maximum frequency. The battery capacity is 3000 mA/h and not 3630.
Woah great work! Will be running this as soon as that CPU util bug is squashed Just a thought, you've posted this in the general Android misc thread although we have our own dedicated sub-forum, any chance of moving it there? Might get better visibility? https://forum.xda-developers.com/t/zte-nubia-m2
estuardo4 said:
Is there other way to install? Yesterday I flashed the persistance.img posted by Mauronofrio without problems and now, for the life of me, I can't get my Win10 machine to recognize my device. I uninstalled, restarted with the option of not checking for signature files, installed, nothing. Uninstalled and installed old drivers and nothing. Uninstalled and installed the newest versions from Google and nothing. My win10 pc can't recognize my Nubia
And yes, I tried to make a working USB live image with FWUL but I don't have the technical knowledge to know whats going on and why I can't use it with my Nubia.
Click to expand...
Click to collapse
i confirm the issue that the phone is not recognized in windows 10 ,you can see the partitions but when opening there is nothing so see and empty while it is not and no files can be added.
this is a good start but at the moment this rom is not realy a usable rom, also very strange that it only can be flashed with the twrp provided. you get error 7 and also the message this rom is not suitable
for this phone and i am using the original TWRP provided bij TWRP itself. i don`t want to reflash my phone between different twrp versions to be able to restore my phone.
i had the official TWRP installed and did not work with this rom, so i think this must be corrected to and be compatable with the original released twrp , by twrp.
the twrp provided on the rom downloadpage also does load very slow and takes 3 times longer to load.
LuigeUA said:
The processor constantly operates at the maximum frequency. The battery capacity is 3000 mA/h and not 3630.
Click to expand...
Click to collapse
The battery capacity is 3630 and not 3000
mauronofrio said:
The battery capacity is 3630 and not 3000
Click to expand...
Click to collapse
I know, but Kernel Adiutor showing 3000 mah
LuigeUA said:
I know, but Kernel Adiutor showing 3000 mah
Click to expand...
Click to collapse
nubia ui stock also shows 3000. Do not worry about that.
Related
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), 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 official LineageOS 14.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
Known bugs:
Front camera is buggy, due to the buggy camera HAL Fixed by OnePlus
Installation:
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (See #2 for details)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao, Grarak
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-11-09
Last Updated 2017-03-27
Release note:
New builds (after 2017/1/15) uses F2FS backported from 4.10 kernel, you may meet compatibility problems such as deadlocks, if you do, flash TWRP provided in OP and choose "Wipe -> Format Data" to format(not just wipe) your /data partition, this will clean the entire /data partition, including the emulated sdcard, so don't forget to backup your data before. After that, your data partition will be formatted into ext4, if you want to keep using f2fs, just convert fs type normally in TWRP.
[*]For oneplus3, my unofficial TWRP is recommended, as it's what I use. For 3T, TWRP 3.0.4 is recommended.
As of 2017/6/17, official TWRP for OnePlus 3(https://dl.twrp.me/oneplus3/) is updated with latest LineageOS kernel and OxygenOS decryption stuff, it builds against Omni 7.1.2 and supports both op3&3t, now it's the recommended recovery.
20170120 build includes sdcardfs, security fixes and camera fixes&improvements, touch to focus is fixed as well, if it's still not working, clean Snap's data. BTW N kernel source is released now, I'll take days to bring up, don't ask for ETA.
Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution. Visit http://lineageos.org/Update-and-Build-Prep/for more details
Started from lineage-14.1-20170207-nightly-oneplus3-signed.zip, we provide unified builds for both 3&3T, and you need to install certain firmware to pass the TrustZone assertion. Currently they're the OxygenOS Open Beta 19/11 ones. As oneplus won't update them every time new OTAs are rolling out, firmware from other versions might also pass the assertion.
FAQs:
My status bar quick pulldown and notification slider are broken, why?
See https://github.com/opengapps/opengapps/wiki/Notes-for-CMSetupWizard
Why the builds are unified?
Tell me the difference between OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883 and OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8, why not?
{
"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"
}
Latest Firmware files for oneplus3/oneplus3t -5.7.2017-
Make a nandroid backup before you proceed
Flash the following files using the latest official twrp to avoid any recovery related issues.
Make sure to do a clean flash if your rom requires an updated firmware.
Don't ever flash an oneplus3 firmware on oneplus3t or an oneplus3t firmware on oneplus3.
Oneplus3
Instructions only for oneplus3!
1-clean flash is recommended.
2-Falsh OnePlus3_OpenBeta19-FIRMWARE+MODEM-flashable.zip.
3-Flash the latest laos nightly.
4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.
5-Wipe Dalvik/cache and reboot.
Oneplus3t
Instructions only for oneplus3t!
1-clean flash is recommended.
2-Flash OnePlus3T_Beta10-(4-7-17)-FIRMWARE-flashable.zip.
3-Flash the latest laos nightly
4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.
5-Wipe Dalvik/cache and reboot.
For people who rather use the oxygenos camera:
Get OnePlusCameraV8-siankatabg.apk and OnePlusGallery-V8-siankatabg.apk
If you have problems after flashing any custom kernels please provide a log in the thread where you got the kernel from and not here!
Credits:
@nvertigo67 @djsubterrain @Eliminater @kamilmirza op3t firmware
@jamal2367 op3 firmware
@siankatabg oos camera/gallery port
Maybe let a CM member start the official thread?
@dianlujitao : Thanks for maintaining this.
Currently call audio is broken by sound trigger commit.
Even when that revert, noise cancellation not working / echo happens while in calls.
please fix this only issue.
RohanAJoshi said:
@dianlujitao : Thanks for maintaining this.
Currently call audio is broken by sound trigger commit.
Even when that revert, noise cancellation not working / echo happens while in calls.
please fix this only issue.
Click to expand...
Click to collapse
Steve is investigating on that
dianlujitao said:
Steve is investigating on that
Click to expand...
Click to collapse
That's great, waiting for noise cancellation fix.
I have a custom TWRP from the OOS 3.5.5 (OnePlus thread),
twrp-3.0.2-22-oneplus3.img
I think only that is working correctly with CM 14.1 Official ROM ?
osr.arora said:
I have a custom TWRP from the OOS 3.5.5 (OnePlus thread),
twrp-3.0.2-22-oneplus3.img
I think only that is working correctly with CM 14.1 Official ROM ?
Click to expand...
Click to collapse
Yes, 3.0.2.19 & 3.0.2.22 should work with every rom.
So use always this twrp versions to get sure.
dianlujitao said:
Steve is investigating on that
Click to expand...
Click to collapse
Finally someone official is here
Thank you very much!!!
Can you just tell me,
Is that included baseband/firmware inside the rom, 3.5.5 or 3.2.7 or mixed or sth else?
Thanks
Cheers
Is possible flash 14.1nightly on experimental? I have from 2 weeks
alteus83 said:
Is possible flash 14.1nightly on experimental? I have from 2 weeks
Click to expand...
Click to collapse
It is possible, but you can get some unexpected bugs...
Better to do a clean start, with full wipe.
And dirty flash upcoming nightlys.
Cheers
When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/
yooouuri said:
When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/
Click to expand...
Click to collapse
known issue with cm14.1
yooouuri said:
When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/
Click to expand...
Click to collapse
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
5. Srgb colors not working
Cheers
Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
Agree! :good:
Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
You guys may need to wait because cm14.1 is still highly experimental
So its waiting for OP to release some of their HAL?
Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
Add on
5. In call volume slider not working in speaker or headset mode.
dianlujitao said:
You guys may need to wait because cm14.1 is still highly experimental
Click to expand...
Click to collapse
You have right, but that's the actual bug list that users know what's not working atm
I don't think that next few builds will not be highly experimental
yooouuri said:
So its waiting for OP to release some of their HAL?
Click to expand...
Click to collapse
Yes, till they release nougat.
mgear356 said:
Add on
5. In call volume slider not working in speaker or headset mode.
Click to expand...
Click to collapse
I know, but this bug is only since yesterday, there is a commit that broke it... I think it will be fixed on next 1-2 builds...
Cheers
I would appreciate if op could add link to supported twrp in the first post.. It would be really helpful..
{
"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"
}
Disclaimer
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.
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. More info.
Install
Update recovery to the latest TWRP or Lineage Recovery build
Format data if coming from an UNOFFICIAL or non-Lineage build.
Flash the ROM
Flash any addons
Reboot
Bugs
If you encounter issues/bugs that are not known, please report. If I can replicate your issue then I can track it down.
If I cannot, please provide as much detail as possible. Logcats are a must.
Please indicate what g5 variant you have (h830, h850, rs988), the dated version, and any third party mods.
I am aware people run mods or change things. If needed I may ask you to data wipe or remove a mod that might be interfering.
Please avoid bringing up issues with your favourite gapps package. If a bug only exists with gapps, it's not my problem.
Changelog
Code:
[03/03/2021]
March security patch (android-11.0.0_r32)
[20/12/2021]
January security patch (android-11.0.0_r27)
Fixed camera crashes
[04/12/2021]
Updated LineageOS apps and frameworks
[13/12/2020]
LineageOS 18.1 - Android 11 QPR1
[30/11/2020]
Fixed boot after encrypting with a lockscreen set
Updated LineageOS apps and frameworks
[B]16/11/2020[/B]
First release
Downloads
Official builds
Archived unofficial builds: sourceforge
Sources
Gerrit
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_g5-common
h830
h850
rs988
Will los 18.0 be coming to g6
hi will this work on h845 as well? if not, is it okay to flash h850 or h830 on my h845?
lgg5.845lol said:
hi will this work on h845 as well? if not, is it okay to flash h850 or h830 on my h845?
Click to expand...
Click to collapse
No, it won't work, don't try flashing an h830/h850 ROM as flashing a ROM not meant for the variant of your device will most likely land you in an unfixable hard brick. Ask me how I know.
Great to see you with new topics! I will try soon as possible :good:
ROMSG said:
No, it won't work, don't try flashing an h830/h850 ROM as flashing a ROM not meant for the variant of your device will most likely land you in an unfixable hard brick. Ask me how I know.
Click to expand...
Click to collapse
damn...sorry for that... its weird there's no new custom rom for h845, at least. on android 8 or 9 :laugh:
lgg5.845lol said:
damn...sorry for that... its weird there's no new custom rom for h845, at least. on android 8 or 9 :laugh:
Click to expand...
Click to collapse
The h845 is very different from the G5 h850/h830/rs988 instead of the sdm 820 it uses the sdm 652. A much cheaper and slower soc. So you see the sources listed in the op.
Sources
Gerrit
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android...msm8996-common
https://github.com/LineageOS/android..._lge_g5-common
h830
h850
rs988
Even though @synescu has made a twrp pot almost all of these would have to be heavily modified to work with the g5 se. I tried to build android 7 for the se but the only device tree available is horribly out of date and even android 7 wouldn't build successfully ( @synescu who wrote this tree and made twrp for the g5 se has been inactive for a year). It also doesn't help that the g5 SE is very rare in the united states as it was a Europe exclusive and even using sites that will import from Europe the g5 se is super overpriced (sometimes even more than $300!) on the used market. So unless someone can find a g5 se for cheap a rom for the se won't be happening anytime soon, unfortunately.
When I try to build 18.0, all goes well. Then there is an error when it comes to signing the build. (I'm using the same scripts I use for 17.1, except s/17.1/18.0/g.)
Code:
ERROR: Failed to run signapk.jar: return code 1:
Error: Unable to access jarfile /home/rfrazier/android/lineage/lineage-18.0/build/make/tools/framework/signapk.jar
And here's the command.
Code:
## Signing
echo "Signing the APK."
time ./build/tools/releasetools/sign_target_files_apks -o -d ~/.android-certs \
$OUT/obj/PACKAGING/target_files_intermediates/*-target_files-*.zip \
signed-target_files.zip &>>${LOGFILE}
I suspect that it is operator error, but any suggestions would be welcome.
Best wishes,
Bob
PS signapk.jar exists in the directory in which I think i should be looked for: out/host/linux-x86/framework
So, I suspect that an environmental variable is being incorrectly set. Something to look into when I get some more time.
RLF
Great to see more development for the G5, thanks!
How is the stability of this compared to Lineage 17.1?
H820?
How about H820?
ajasei said:
How about H820?
Click to expand...
Click to collapse
As far as I know the H820 is not bootloader unlockable. There aren't any lineage builds for h820 anyway.
I think that the signing problem is related to a change in /build/tools/releasetools/common.py, and more particularly in changes to the following.
class Options(object):
def __init__(self):
Now if I could only read it (not being a programmer). I guess I'll give it a go later.
Best wishes,
Bob
Yes, something is definitely going on there. I hardwired in the path in /build/tools/releasetools/common.py , and it was built and signed just fine.
Code:
class Options(object):
def __init__(self):
# Set up search path, in order to find framework/ and lib64/. At the time of
# running this function, user-supplied search path (`--path`) hasn't been
# available. So the value set here is the default, which might be overridden
# by commandline flag later.
exec_path = sys.argv[0]
if exec_path.endswith('.py'):
script_name = os.path.basename(exec_path)
# logger hasn't been initialized yet at this point. Use print to output
# warnings.
print(
'Warning: releasetools script should be invoked as hermetic Python '
'executable -- build and run `{}` directly.'.format(script_name[:-3]),
file=sys.stderr)
# self.search_path = os.path.realpath(os.path.join(os.path.dirname(exec_path), '..'))
self.search_path = "out/host/linux-x86"
The last commented out line
self.search_path = os.path.realpath ...."
was replaced with
self.search_path = "out/host/linux-x86"
I haven't figured out the logic of the rest of the stuff, so don't know what's wrong with it.
Best wishes,
Bob
PS I tried a dirty update (on my spare phone), but it didn't work. I had to format data. It might have been because I had Magisk installed and that messed up the recovery partition, but I'm not sure. In any case, after formatting data it came up just fine. I haven't checked much yet, but WIFI works.
RLF
PPS It looks like a mistaken assumption about the location of the .jar file related to the file which calls it, i.e., that the files should be in the same subdirectory as common.py(c), which calls it, i.e., build/make/tools/<framework ...>. While, actually, the files are in out/host/linux-x86*/<framework ...>.
*Or, whatever platform is being used.
Unless, of course, one is supposed to do something to get those files (.jar lib) into the correct directories.
In any case. hardwiring isn't ideal, but at least it works.
RLF
Since it was working okay on my spare phone, I decided to give it a go on the phone I used. It installed okay, I set it up okay, got all the apps installed okay, etc. NFC works (yubico), BT works (keyboard). Unfortunately, I decided to encrypt. Wouldn't work. Said my data may be corrupted, I would have to format data and start again. Bummer.
And, of course, it was harder than ever to back up settings, including app settings, so, mostly, they aren't. There's an area ripe for improvement.
Note to self. Try encryption on the spare phone before even contemplating putting it on the main phone.
Best wishes,
Bob
PS I have /tmp/recovery.log, if anyone wants to see it. Although it may not be as useful as it could have been, as I reinstalled system on a whim before the last time of giving it a shot.
RLF
PPS I reinstalled, and everything seems to be working smoothly. Although I haven't tried much beyond basic call, NFC, BT, wifi, and the like. I'll try encrypting again, on my spare phone, in a couple of weeks, perhaps when the December security update comes out.
RLF
Thank you for the time you spent trying to check what's working and what's not. There was an annoying bug in the previous LineageOS versions: IR blaster doesn't work, or works once and then you need to reboot the phone to use it again. Can you please test if it works in 18.0? It's an underestimated feature that I use on a daily basis. This bug was the main reason, together with the lack of camera apps better than the G5's default (and G7's camera port, also based on LG framework), why I never used Lineage for more than a couple of days before reverting to stock based roms.
I didn't see IR blaster in the pull-down from the status bar, and didn't see it in the connected devices section. Also, I don't think that I have anything amenable to being blased by IR.
Best wishes,
Bob
wifi - works
bluetooth - works, and so does AudioFX, listening to music works great
ir blaster - not working |Confirmed working (with bug, can only blast one command before losing functionality, restarting device restores functionality for one blast) in latest 17.1 build|
encryption - not working, hangs after reboot on animation boot |Confirmed working in latest 17.1 build|
nfc - unknown, couldn't test since my G3's seem to have issues also
auto rotate - works
camera - works, front and back
torch - works
testing done on h830
quite the shame about how bugged the ir blaster is, my G3 running latest lineageos build blasts great.
NFC works - G5 (h850) Yubico Authenticator, with YubiKey 5 NFC.
whoops, reflashed between 17.1 and 18 a lot, during one of the quick setups of 18 I forgot to uncheck the box for lineageos custom recovery, but went back to uncheck it before finishing the rest.
TWRP still got erased and now with LineageOS recovery, whats the easiest way back to getting TWRP?
(I know I could reflash 20A and dirtycow, but i'm hoping for a cleaner way)
DrowningInFreedom said:
whoops, reflashed between 17.1 and 18 a lot, during one of the quick setups of 18 I forgot to uncheck the box for lineageos custom recovery, but went back to uncheck it before finishing the rest.
TWRP still got erased and now with LineageOS recovery, whats the easiest way back to getting TWRP?
(I know I could reflash 20A and dirtycow, but i'm hoping for a cleaner way)
Click to expand...
Click to collapse
Just flash it using fastboot. Look at the lineage wiki entry for your device.
Best wishes,
Bob
LineageOS is a free, community-built, aftermarket firmware distribution of Android 11, 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 18.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 an 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 18.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 and Download:
2021/2/8 (Initial release): https://androidfilehost.com/?fid=17248734326145731516Known issues:
This build is HIGHLY EXPERIMENTAL and NOT WELL TESTED.
Wifi display not work, don't ever attempt to use it or the system will crash.
VoLTE is not tested and I don't know if it ever works, please give feedback if you're able to verify.
2021/4/2: https://download.lineageos.org/oneplus3
Fixed the sensor_SMD wakelock
Fixed ringtone when bluetooth headset connected
Wow !!! , i'm on LOS 17.1 Official now but waiting for LOS 18.1 Official
OP3 is my daily driver..
Thank you @dianlujitao
Thanks for this great Rom.
One issue.
It displays a popup with the following message: "This build was signed with public keys".
Should i ignore it?
Keyvannn said:
Thanks for this great Rom.
One issue.
It displays a popup with the following message: "This build was signed with public keys".
Should i ignore it?
Click to expand...
Click to collapse
Yes, you should
josepmaria said:
Yes, you should
Click to expand...
Click to collapse
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...
Jan_L said:
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...
Click to expand...
Click to collapse
Yes, the key for signing the build doesn't matter.
My initial testing of this rom is that everything is working (based on my usage): WiFi, phone calls, SMS, NFC (Google Pay) all work.
I had a bit of problem setting the wallpaper initially (FCed), but the problem went away on its own after waiting a bit of time.
I'm missing the settings option to specify the duration of the capacitive key backlight, but that's no big deal.
I'm using Opens Gapps pico 210130 and Magisk 21047.
I've seen evidence of the sensor_SMD kernel wake lock issue that I've seen on all Android 11 roms I've tested previously. I'll post more details on this once I've captured a logcat of the problem.
BillGoss said:
sensor_SMD kernel wake lock issue
Click to expand...
Click to collapse
Nap time by Franco mostly solved this for me.
Sideload TWRP 3.5.0, wipe dalvik & cache, flash 18.1. All good
Jan_L said:
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...
Click to expand...
Click to collapse
Update to official build requires a clean install and an unlocked bootloader
raz123 said:
Nap time by Franco mostly solved this for me.
Click to expand...
Click to collapse
Last time I used NapTime, it drains more battery than it should and my phone was almost all the time in idle untouched with WIFI and everything else off
Regarding the sensor_SMD wake lock:
Generally, the rom can go for long periods without this wake lock showing up:
{
"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"
}
But the wake lock can start at random times:
And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.
However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
Fortunately, a reboot gets rid of the wake lock.
josepmaria said:
Update to official build requires a clean install and an unlocked bootloader
Click to expand...
Click to collapse
If the plattform key is changed a clean flash is highly recommended (though not required if you use a migration script or zip - NOT!!! recommended). Since los recovery (as well as current twrp for that matter) and los boot image are signed with aosp verity key, you don't need to unlock bl if you run any version of los with a locked bl.
I've explained the three different keys and signatures used in a single build in depth in the llos 17 thread: https://forum.xda-developers.com/t/...or-oneplus-3-3t.3990061/page-60#post-82568467
BillGoss said:
Regarding the sensor_SMD wake lock:
Generally, the rom can go for long periods without this wake lock showing up:
View attachment 5215977View attachment 5215981
But the wake lock can start at random times:
View attachment 5215983View attachment 5215985
And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.
However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
View attachment 5215983View attachment 5216001
Fortunately, a reboot gets rid of the wake lock.
Click to expand...
Click to collapse
Nice finding. Just check the source and that should be the Significant Motion Detector if I'm not wrong. Dunno if there are any drawbacks but you should be able to disable it by adding " ro.vendor.sensors.smd=false" to /vendor/build.prop, please try if it helps.
dianlujitao said:
Nice finding. Just check the source and that should be the Significant Motion Detector if I'm not wrong. Dunno if there are any drawbacks but you should be able to disable it by adding " ro.vendor.sensors.smd=false" to /vendor/build.prop, please try if it helps.
Click to expand...
Click to collapse
I set the property as you suggested. After more than 12 hours, including a full recharge, there's no sign of the wake lock. It's looking good.
Thank you!
May be a stupid question and definitely not belonging here, but can not find the answer anywhere else....
When is /vendor/build.prop used and when /system/build.prop?
It seems settings of /vendor/build.prop are used earlier in the boot process and are vendor specific, where afterwards /system/build.prop settings are added later in the boot process and are OS specific.
A lot of people are messing with build.prop settings but have no idea what they are doing and if settings are even working or not. As I see it, some settings put in /system/build.prop are in fact settings which belong in /vendor/build.prop, but I do not know if everything put in /system/build.prop will overrule /vendor/build.prop or the other way around....
In some Android 10 code I found the order default.prop, build.prop, vendor.prop, where /vendor/build.prop is loaded after /system/build.prop, though not sure if this is the default then....
You see, no idea what I am talking about; I hope someone can clear things up...
Jan_L said:
May be a stupid question and definitely not belonging here, but can not find the answer anywhere else....
When is /vendor/build.prop used and when /system/build.prop?
It seems settings of /vendor/build.prop are used earlier in the boot process and are vendor specific, where afterwards /system/build.prop settings are added later in the boot process and are OS specific.
A lot of people are messing with build.prop settings but have no idea what they are doing and if settings are even working or not. As I see it, some settings put in /system/build.prop are in fact settings which belong in /vendor/build.prop, but I do not know if everything put in /system/build.prop will overrule /vendor/build.prop or the other way around....
In some Android 10 code I found the order default.prop, build.prop, vendor.prop, where /vendor/build.prop is loaded after /system/build.prop, though not sure if this is the default then....
You see, no idea what I am talking about; I hope someone can clear things up...
Click to expand...
Click to collapse
First of all: since op3/t has no dedicated vendor partition /vendor is a symlink to /system/vendor.
/default.prop is read first and contains settings necessary for basic boot (historically this file has been part of the root partition which has been ramfs contained in the boot image as cpio archive prior to system as root, which allows to set these props before system was mounted - obviously that's not longer the case with system as root.
/system/vendor/build.prop is read as second source containing vendor specific props. Systematically this should contain settings specific to the vendor(s) of the device and the actual os (which are the same, as long as you use stock roms, but obviously differ if you use an custom source build rom like los).
/system/build.prop is reaf as third source and should contain general android settings.
If the same prop is set in more then one file the last one wins as long as it's no read only prop (ro.*). For ro.* prop the first one wins, because it can't be changed after setting. Exeption: if you use magisk, you can alter ro.* props (by command from the commamdline or a script).
Additionally to these three sources some props are set by init (first os process started by the kernel and controlling the boot process). See:
android_device_oneplus_oneplus3/init_oneplus3.cpp at lineage-18.1 · LineageOS/android_device_oneplus_oneplus3
Contribute to LineageOS/android_device_oneplus_oneplus3 development by creating an account on GitHub.
github.com
nvertigo67 said:
First of all: since op3/t has no dedicated vendor partition /vendor is a symlink to /system/vendor.
Click to expand...
Click to collapse
Thanks for the clear explanation nvertigo!
Does this rom support encryption?
Thank you for your hard work and look forward to the arrival of offical los18.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.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. Linked below is a package that has come from another Android project that restore the Google parts. 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 organization.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.You can also view the changelog for a full list of changes & features.Official LineageOS website : http://lineageos.orgAbout LineageOS Legal : http://lineageos.org/legal
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.2. This ROM does not intended to support Google Camera, but you can try some mods.Downloads Links
LineageOS 19:Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-19.1/kugoGoogle Applications (optional):MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 12.1 -> arm64)XDA post about GApps: https://xda-developers.com/download-google-apps-gappsRecommended Recovery (optional):TWRP 3.x: https://forum.xda-developers.com/-/-t3793837
Flashing and updating
Please install the latest version of TWRP to avoid further issues with recovery!
LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 12.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Stable
FEATURES AND ISSUES
Boot: Ok
Bluetooth: Ok
WiFi: Ok
WiFi Hotspot: Ok
RIL - Phone - Data: Ok
GPS: Ok
Camera: Ok
Camcorder: Ok
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Ok
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing
what the ...!?
i downloaded los18 just yesterday, installed it this morning and now i see los19 sneaked by
thank you so much chippa_a, i will try it out tomorrow
unbelievable what your doing to this oldschool device.
Gcam works perfectly on it. Thanks a lot for this device!!!
This works beautifully and is really smooth. Never thought I'd see another rom for the XC again.
Can confirm that GCam 8.x with HDR actually works! (No crashes, or stuttering) Unlike previous roms with the most recent kernel before this new one. I don't know what magic you pulled to make this happen but thank you!
Thanks for this rom! It is very fast.... Only Chrome browser is laggy...
decsimon said:
Thanks for this rom! It is very fast.... Only Chrome browser is laggy...
Click to expand...
Click to collapse
I haven't experienced this. For me normal browsing was pretty smooth.
Have you also flashed the kernel from the .zip?
I must say that for now everything seems to work fine for me (incl. Gapps).
Tested fingerprint reader, 4G, DRM with Tidal, smooth and responsive Maps / Android Auto, smooth Chrome. No sudden reboot for now.
konstruktor said:
I haven't experienced this. For me normal browsing was pretty smooth.
Have you also flashed the kernel from the .zip?
I must say that for now everything seems to work fine for me (incl. Gapps).
Tested fingerprint reader, 4G, DRM with Tidal, smooth and responsive Maps / Android Auto, smooth Chrome. No sudden reboot for now.
Click to expand...
Click to collapse
Ok, what steps for flash kernel i must to follow? Rom, gapps, kernel? Magisk is a problem or i can flash it? (i need it for apk bank)
decsimon said:
Ok, what steps for flash kernel i must to follow? Rom, gapps, kernel? Magisk is a problem or i can flash it? (i need it for apk bank)
Click to expand...
Click to collapse
You won't need to flash the kernel separately, it's included in the zip:
1. Boot to TWRP.
2. Install the Lineage zip file.
3. Reboot to recovery.
4. Optional: In TWRP, install/flash Magisk 24.1 and/or MindThe GApps.
That's it. No issues with Chrome lag either. I've tried a few browsers and they all work well.
I've tested a few GCams, I find these two work best so far:
Parrot043: MGC_7.6.008_Parrot043_V7.apk
Download MGC_7.6.008_Parrot043_V7.apk by Parrot043.
www.celsoazevedo.com
Parrot043: PMGC_7.2.014_Relesed_V1.apk
Download PMGC_7.2.014_Relesed_V1.apk by Parrot043.
www.celsoazevedo.com
In the Advanced Settings, make sure to change AI White Balance to "Pixel 3 XL" for best colour accuracy.
Note: For the front selfie cam to work, you'll need to disable HDR first.
Please post here if you find any other good ones!
how if i try nfc on ex japan S0-02 j ?
Little adventure said:
how if i try nfc on ex japan S0-02 j ?
Click to expand...
Click to collapse
Not sure what you're asking but NFC is located under:
Settings > Connected Devices > Connection Preferences > NFC
If it doesn't turn on, you might have to flash the last Sony stock firmware first then install this rom.
Someone with the JA model might be able to help.
It works great! Very fast boot time. Everything is smooth, so far haven't noticed any bugs. Fingerprint unlock is faster than on stock and LOS 16.
Camera quality with the first GCam is also the best out of all custom ROMs I've tested. Great job! A new life for my old Xperia.
betacrypt said:
I've tested a few GCams, I find these two work best so far:
Parrot043: MGC_7.6.008_Parrot043_V7.apk
Download MGC_7.6.008_Parrot043_V7.apk by Parrot043.
www.celsoazevedo.com
Parrot043: PMGC_7.2.014_Relesed_V1.apk
Download PMGC_7.2.014_Relesed_V1.apk by Parrot043.
www.celsoazevedo.com
In the Advanced Settings, make sure to change AI White Balance to "Pixel 3 XL" for best colour accuracy.
Note: For the front selfie cam to work, you'll need to disable HDR first.
Please post here if you find any other good ones!
Click to expand...
Click to collapse
First , thanks for this Rom I'm very happy to See Android 12 on my phone.
I have tried Encryption and it doesn't work for me. I have a bootloop.
Has anyone else tested it?
And on the Encrypt page , I had astrange bug : I wasn't able to access to the"Encrypt" button at the bottom of the page . I had to set the police size at the smallest size to see it.
Maciek602 said:
It works great! Very fast boot time. Everything is smooth, so far haven't noticed any bugs. Fingerprint unlock is faster than on stock and LOS 16.
Camera quality with the first GCam is also the best out of all custom ROMs I've tested. Great job! A new life for my old Xperia.
Click to expand...
Click to collapse
Agree, fingerprint detection and unlocking is incredibly fast, didn't think it could ever be improved this much.
betacrypt said:
Not sure what you're asking but NFC is located under:
Settings > Connected Devices > Connection Preferences > NFC
If it doesn't turn on, you might have to flash the last Sony stock firmware first then install this rom.
Someone with the JA model might be able to help.
Click to expand...
Click to collapse
thanks for the answer sir
I have ex japan status bootloader yes, now position in custom rom lineage 16.0 android pie, this rom very smooth in my old device , i try turn on nfc in this rom, nfc doesnt turn on , but nfc working fine in ex global
Maybe hardware nfc ex japan different with ex global , so that maybe build tree and config specific for ex japan , correct me if i wrong sir
my experience with gapps 12.1 12L
open gapps stock - not working (endless bootanimation)
open gapps pico - unusable (loop before setting up fingerprint)
flame gapps full - unusable (loop before setting up fingerprint)
flame gapps basic - unusable (loop before setting up fingerprint)
mindthegapps - working
nik gapps omni - working
nik gapps stock - working fine so far
I have this problem...my bank apk its OK with last magisk (and fingerprints setting and Hide zygisk), but gpay dont work when i insert my card code cvv, it say that is not possibile continue because possible root phone....i try to hide all with zygisk of magisk .....
OK i resolved with module safetynet....
Toggles for me is too big, ....is possible return to standard lineageos toggles 16/17/18?
So when swipe down one time, i can see 6 toggles and not only 4....
decsimon said:
Toggles for me is too big, ....is possible return to standard lineageos toggles 16/17/18?
So when swipe down one time, i can see 6 toggles and not only 4....
Click to expand...
Click to collapse
That's Android 12. I wouldn't hold my breath that someone could port an older System UI over. You would have to get used to it I'm afraid.
{
"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"
}
Evolution X 6.5 for the Lenovo Xiaoxin Pad Plus (Lenovo P11 5G WiFi) [TB-J607F]
Code:
/*
* Your warranty is void. Or valId, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@RealAkito
@AnierinB
Reach us on Twitter! @EvolutionXROM
Just flash and check "The Evolver". We have tons of features combined together from different ROMs.
DO NOT FLASH GAPPS, ALREADY INCLUDED
* Probable lost frames when dragging the apps from app drawer to the home screen.
* If you open the Wallpaper Picker in 2-Pane layout (Like open it via Settings), the Wallpaper will be zoomed incorrectly and look blurry. (Note: if you want to set the wallpaper, open the wallpaper picker from the Launcher).
First Time Install / Clean Flash
1. Reboot to Recovery
2. Download the zip for your device
3. Flash whichever recovery you desire in both slots
4. Format Data
5. If you are going to flash from stock ROM, switch to the other slot in recovery, then reboot to recovery
6. Enable ADB Sideload feature, then Sideload the package to your tablet
Code:
adb sideload <path to the flashable zip>
7. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the update for your device
3. Flash the ROM via ADB Sideload
4. Reboot to System and #KeepEvolving
Android OS version: 12.1.0_r11
Security patch level: July 2022
Build author: bigsaltyfishes
Source code: https://github.com/Evolution-X
Kernel Source code: https://github.com/bigsaltyfishes/kernel_lenovo_J607Z
ROM Developer: Joey Huab
Changelog:
2022-07-07:
Notes: Clean Flash Required
Device Changes:
1. Switch to Proton Clang
2. Switch to SkiaGL Threaded Renderer
3. Import Vulkan Overlay from Pixel 5
4. Enable DT2W
5. Import missing governor script from stock rom
6. Import Lenovo side changes to init scripts
Kernel Changes:
1. Upstream kernel to 4.19.250
2. Merge Tag LA.UM.9.12.r1-14300-SMxx50.0
Very good work. Is it possible to get an EvolutionX rom for the tb-j706f ?
Can we get 606f support as well?
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
LegendOcta said:
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
Click to expand...
Click to collapse
I've already recover my device. Here are the screenshot of Device info Hw, hope it is helpful for you.
LegendOcta said:
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
Click to expand...
Click to collapse
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Marci344 said:
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Click to expand...
Click to collapse
I don't think you can't directly use this J607 kernel source as the soc of J606(sm6115) is different from J607(sm7225), but I found that the kernel version of J606 in stock rom is same as J607, maybe the J607 kernel source code can serve as a reference for you to fix the J606 kernel source code. Also, If you want to fix touchscreen in TWRP/OrangeFox, you need to import touchscreen firmware from stock rom.
bigsaltyfishes said:
I don't think you can't directly use this J607 kernel source as the soc of J606(sm6115) is different from J607(sm7225), but I found that the kernel version of J606 in stock rom is same as J607, maybe the J607 kernel source code can serve as a reference for you to fix the J606 kernel source code. Also, If you want to fix touchscreen in TWRP/OrangeFox, you need to import touchscreen firmware from stock rom.
Click to expand...
Click to collapse
Hi!
Yes I've seen your kernel source. I think it will help me for the building, because there is many similarity. Even the filesystem is 1:1 same. I've got final exams in the next few weeks in the Uni too, but after that I will try to make it.
One question tho. How can you export the touchscreen files from the stock rom? I dont know how look your tablet's firmware, but the J606L has a very stupid firmware structure, with superpartitions, and I cannot get any useful stuff out from it, just the vbmeta, boot/recovery images.
Thank you, and sorry for the offtopic.
Marci344 said:
Hi!
Yes I've seen your kernel source. I think it will help me for the building, because there is many similarity. Even the filesystem is 1:1 same. I've got final exams in the next few weeks in the Uni too, but after that I will try to make it.
One question tho. How can you export the touchscreen files from the stock rom? I dont know how look your tablet's firmware, but the J606L has a very stupid firmware structure, with superpartitions, and I cannot get any useful stuff out from it, just the vbmeta, boot/recovery images.
Thank you, and sorry for the offtopic.
Click to expand...
Click to collapse
You can find firmware you need in /vendor/firmware. If it is hard for you to extract them from your tablet, you can simply extract them from 9008 Images. Partitions in super partition are simply named as super_*.img in 9008 package, they are raw images, you can directly mount them with ro option (They have share_blocks feature, you can't mount them in rw mode).
can i flash it on j706f?
Marci344 said:
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Click to expand...
Click to collapse
The thing that's missing is the kernel module for the NT356(something)_HostDL or something in the kernel's {SRCROOT}/drivers/input/touchscreen/NT35something_HostDL.
The driver, IS available in a P11 LTe or something's kernel source available in lenovo downlooad page. (Sorry, my memory is very inaccurate, I was trying bunch of stuffs when I bought my P11 last year, it's a bit hazy now)
I made the driver located there, modded Makefile, got some kernel compile issue, and I somehow solved it, but the spi read only got value 00000000 and it didn't work. (You can get more info from postmarketOS-offtopic Matrix chatroom, chat history is logged in there, I got help from somebody a long time ago and there are conversations about this)
I got touchscreen to work with a prebuilt kernel (Lost the device tree) but that's it..
I hope we make something out of lenovo's junky kernel source codes.. The device has potentials!
bigsaltyfishes said:
I've already recover my device. Here are the screenshot of Device info Hw, hope it is helpful for you.View attachment 5625467
Click to expand...
Click to collapse
Wonderful that you recovered it!
Thanks a lot for the screenshot. It seems like that you have the himax touchscreen variant. (I was trying to ask you to test the driver for nt365blahblah touch screen, if your variant was the one that had it)
hi sir, i flashed crdroid gsi on my j706f, but the settings doesnt look like your rom which show in two pane, can i edit build.prop to get it show as your rom settings? or what should i edit? thank you very much.
sabosanbosocho said:
hi sir, i flashed crdroid gsi on my j706f, but the settings doesnt look like your rom which show in two pane, can i edit build.prop to get it show as your rom settings? or what should i edit? thank you very much.
Click to expand...
Click to collapse
You can't enable it by simply editing build.prop. This feature related to an optional package called androidx.window.extensions. Ask GSI builder add this package or build it yourself.
great work!
overall pretty pleasant experience, and nice feature set. However, two problems
1. as mentioned, adding app icon to the homescreen doesn't work sometimes and it laggs out
2. this is the deal breaker for me, as the volume slider doesn't work. and video play back stuffers probably due to this.
---
update:
the second issue ragarding to the volume slider, it only breaks after playing emby, not sure if other app also break it but that's the only one i found so far. a reboot would fix it
Please make Evolution X happen to TB-J606F also! it's with an older SOC, and we don't get A12 update. A lot of people have it, but not much support
Does widevine security L1?
bigsaltyfishes said:
You can't enable it by simply editing build.prop. This feature related to an optional package called androidx.window.extensions. Ask GSI builder add this package or build it yourself.
Click to expand...
Click to collapse
did you add that by yourself or that was included in evox source code?
mdve123 said:
Please make Evolution X happen to TB-J606F also! it's with an older SOC, and we don't get A12 update. A lot of people have it, but not much support
Click to expand...
Click to collapse
you can flash google gsi (android 12), its works good.
Generic System Image releases | Platform | Android Developers
developer.android.com