[ROM][H830|H850|RS988] UNOFFICIAL LineageOS 18.1 for LG G5 - LG G5 ROMs, Kernels, Recoveries, & Other Developme

[ROM][H830|H850|RS988] UNOFFICIAL LineageOS 18.1 for LG G5 - LG G5 ROMs, Kernels, Recoveries, & Other Developme

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

Related

[ROM][UNOFFICIAL][7.1.2] OmniROM

{
"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"
}
OmniROM is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance, reliability and features over stock Android for your device. It's also about options, which is the beauty of Android.
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. Hard. A lot.
*/
OmniROM 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.
All the source code for OmniROM is available in the OmniROM Github repo.
Homepage:
=================
http://omnirom.org/
Wiki:
=================
http://docs.omnirom.org/Main_Page
Gerrit:
=================
https://gerrit.omnirom.org/
Bugtracker:
=================
http://jira.omnirom.org
Use this thread to report bugs as this is UNOFFICIAL
IRC:
=================
irc.freenode.net #omnirom
Be Advised:
=================
Root access is not included by default. Please flash SuperSU for root (See below).
If problems arise from your use of custom kernels, "performance scripts", etc. etc., we can't be responsible.
Screenshots:
=================
http://abload.de/img/screenshot_20170814-2qlsi5.png
http://abload.de/img/screenshot_20170814-2mssai.png
Installation Instructions:
=================
First time installing OmniROM to your Shield Tablet or coming from another ROM:
- Read known issues and FAQs
- Make sure you're running a proper working Team Win Recovery Project (TWRP) - https://twrp.me/devices/nvidiahshieldtablet.html
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Don't restore system data using Titanium Backup!
Upgrading from earlier version of OmniROM:
- Copy the OmniROM zip to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot
Downloads:
=================
UNOFFICIAL builds
omni-7.1.2-20171110-shieldtablet-HOMEMADE.zip md5:196df454441117da0962015063573a95
omni-7.1.2-20170901-shieldtablet-HOMEMADE.zip md5:02b22807016a3e39d0b0e46986fb24d9
omni-7.1.2-20170818-shieldtablet-HOMEMADE.zip md5:1ebc771fa3626a2a2bd7e68d72df9f7b
omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip md5:4710c3ec9347e1c9ca7dc4013fde0bbf
MIRROR: omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip
Gapps: Open Gapps
http://opengapps.org/
SuperSU:
http://www.supersu.com/download
Device Source Code:
=================
Device trees:
https://github.com/Lolzen/android_device_nvidia_shieldtablet
https://github.com/Lolzen/android_device_nvidia_shield-common
Kernel:
https://github.com/Lolzen/android_kernel_nvidia_shield
Nvidia hardware:
https://github.com/Lolzen/android_hardware_nvidia_power
https://github.com/Lolzen/android_hardware_nvidia_thermal
https://github.com/Lolzen/android_hardware_nvidia_libstagefrighthw
Vendor blobs:
https://github.com/Lolzen/proprietary_vendor_nvidia
Credits:
=================
Steel01 for providing device trees and blob sources and doing an excellent job maintaining them
BitOBSessiOn and OmniROM folks for pointing me in the right direction getting past the Black Screen
OmniROM Project for code base and being #swag in General

Thanks ! The only problem is that the video is not working

marcostesvk said:
Thanks ! The only problem is that the video is not working
Click to expand...
Click to collapse
Thanks for reporting! Could you specify which app? I do have mixed results on this, on one hand YT / MX Player are working on the other one Clover can't play webM's.
I'll certainly look into it.

The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?

marcostesvk said:
The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?
Click to expand...
Click to collapse
I'd advice against that, personally.
However, i have a workaround for the videos. There's some problem with the hardware decoding, i still have to figure out why.
For now i simply disabled hardware decoders, the software decoding seems to work fine, but this isn't a fix by any means.
I'll add the link to the download once the upload finished.
added to OP
Another bug i've encountered is that the Shield Camera's pictures are distorted, however when you activate HDR everything is fine. Again, just a workaround for now. The alternative is to use AOSP Camera.

Charging issue fix available?
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.

fmcgregor said:
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.
Click to expand...
Click to collapse
Seems weird.
Does anybody else have this issue?

klo_lol said:
Seems weird.
Does anybody else have this issue?
Click to expand...
Click to collapse
Thanks for trying. And thanks to anyone for replying. In terms of self help, I downloaded some battery apps to see if they can re-align the battery so it can charge up to 100%. Still only charging up to 89%. Tried cleaning the input ports and the chargers. I have wiped cache partitions. I have the latest TWRP. I'm scared to try to re-flash because it was so difficult - "setup wizard keeps stopping."

you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!

klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!

fmcgregor said:
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!
Click to expand...
Click to collapse
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?

klo_lol said:
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?
Click to expand...
Click to collapse
Yes TWRP 3.1.1-1. Thx very much for the OTA link. Just fyi, the battery zip link was dead. But I'll find a working link now that I know the general name..

klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
Hi, just an update. I re-flashed and used bean gapps this time. No problems this time, but the battery still won't charge above 89%. Just as a by the way, the clock and date start up at factory until I get it on the wifi and it syncs. Every time. If there's no wifi, it's set to Dec. 31, 2012. Anyone else with this?

uploaded a new build. Link in OP.
No major changes, just up2date with omni source as of today

new build in OP.
*updated with latest omni 7.1 changes
*updated with some device changes from Aaron Kling
*updated kernel with latest nvidia kernel sources
i'm still bumping my head against a wall why hwencoders seem to have some sort of problems. You can play media, it's just not working with the configs it's supposed to.

[ROM][UNOFFICIAL][7.1.2][nx551j] LineageOS 14.1 for Nubia M2 [17/09/2018]

{
"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.

[ROM][UNOFFICIAL]LineageOS-15.1[Evert][Moto G6 Plus]

Copy Partition- Initial Setup
Flash the attachement via TWRP

Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok

Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?

Coldstream said:
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Click to expand...
Click to collapse
This device is an A/B device which means it does have two slots.One will be active (running slot) and other will be used for updating system (if any OTA is available) Opengapps doesn't support A/B devices yet.
AB zipfile makes a backup of your active slot so that your device won't get bricked after flashing lineage.

I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense

david.gs.gm said:
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Click to expand...
Click to collapse
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Coldstream said:
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
Click to expand...
Click to collapse
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Click to expand...
Click to collapse
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far

Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.

Do you mind upload the ROM to an alternative file hosting website?
AFH is really slow even with an gigabit internet connection and it always ends up as Failed - Network error.

If you become a developer, join our group at Telegram:
https://t.me/joinchat/GdyK5BB44joobth3umlAJA

The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
WYPIERDAALAAC said:
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Click to expand...
Click to collapse
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.

Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
If I do understand right moto gestures are intergrated in system settings of lineageOS? What about face recognition ?

Lineage alternative links:
Google Drive:
https://drive.google.com/file/d/1hKeKp5WmWhGkkHAVfSgDu10GObQv_QiK/view?usp=drivesdk
Mega:
https://mega.nz/#!SNt3hLxR!AJ5k0krEiCvHG9MiE3MsirYxhHO9z_j9vYsr-pbRjBo

Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?

smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Is everything working so far?
Click to expand...
Click to collapse
If there's anything i've learned so far from the A/B system, it's a good improvement. Nothing i'd be affraid of. What makes u scared? I've ran a lot of the treble roms with different outcomes but going back to full stock is fairly easy so far and right now i'm running this rom.
Obviously i'm not going to say that you can't brick it or should take things too easy, but with just simply understanding the actions your taking it's nothing to be affraid of. Besides, when you flash stock running on A straight to B, and run into troubles with something flashed on A u can switch rather easy is my experience.

Coldstream said:
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Click to expand...
Click to collapse
At this time the dev has had issues building an updated zip installation for twrp but it will probably be resolved soon.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
You can flash magisk 16.7 beta and root will work fine.
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
Click to expand...
Click to collapse
Nothing to worry about with AB. It's a good thing.
Bluetooth calling is being worked on.
Sent from my moto g(6) plus using Tapatalk

Guys, Is it possible do a similar port to ALJETER (Moto G6 Play) variant too?

Anyone running xposed? Any issues?

Updated process ended with ERROR: 1
When I try to flash this rom to my moto g6 plus, I get this error: error applying update: 7 (errorcode:: kInstallDeviceOpenError) Updated process ended with ERROR: 1
What's wrong here?

[ROM][H830,H850][UNOFFICIAL] LineageOS4Microg 15.1 [8.1] - 2020 Build (by Bernie_nix)

{
"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, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* 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.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), 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.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/
Click to expand...
Click to collapse
Rom Built by Bernie_nixWhy build Oreo Now? What about other variants of the G5?:
Oreo is very stable on the h830 and works great with microg. I'm using this build now. This is also a build I am interested in maintaining and comparing to a future Pie build with microg built-in. Unfortunately, Android 17/Q is not yet fully compatible with microg.
Working:
5ghz WiFi, camera, calling, bluetooth, great battery life. USB-C audio earbuds work great. Reported that NFC works.
You tell me.
Known issues:
Please test WiFi, NFC. IR blaster not working for me but I may need to find a suitable app; please test. FM radio reported not working.
Automatic updates not yet implemented but will be in next build.
You tell me.
Install Instructions (If coming from another rom):
Prerequisites: Coming from another rom with Developer settings enabled, android debugging enabled.
(1) Boot into twrp (or ofox)
(2) Wipe your device. Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these (if in twrp. if in ofox, wipe system but do not wipe system 10)
(3) Select Format Data Button. Type yes
(4) Select Install button. Choose rom zip. Swipe to confirm flash.
(5) Install Magisk if you choose.
(5) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(6) Reboot. Phone may or may not mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then boot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM. Reinstall of TWP/Ofox should not be required if upgrading (at least on Ofox).
Upgrade Instructions (If coming from my previous build):
Prerequisites: Developer settings enabled, android debugging enabled.
(1) Boot into twrp (or ofox)
(2) Select Install button. Choose rom zip. Swipe to confirm flash.
(3) Wipe caches.
(4) Magisk should persist after reboot but if not, go back into twrp/ofox and flash it.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM. Reinstall of TWP/Ofox should not be required if upgrading (at least on Ofox).
Tips for Use
1. Root can be enabled in this build (if not installing Magisk) by going to Developer Settings->Manage Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you 4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. I've found Hypercam to take excellent pics with our cameras. Please download for the G5 here: https://gcambrasil.com.br/lg
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thread Purpose & Limits
This thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A; doing so allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
New Builds:
Mar. 5, 2020 Change log
1. Latest security update
Status: Stable
ROM OS Version: 8.x Oreo
Security Patch level: Mar. 5, 2020
H830 Download link: https://www.androidfilehost.com/?fid=4349826312261742170
H830 MD5: 8bd86770d84b94a5d999489c7f993db6
H850 Download link: https://www.androidfilehost.com/?fid=4349826312261742710
H850 MD5: 6fe7febb5b4f994a1f32af18390a988c
Older Downloads:
Feb 29, 2020 Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 8.x Oreo
Security Patch level: Feb. 5, 2020
H830 Download link: https://androidfilehost.com/?fid=4349826312261734920
H830 MD5: 017e4f8352f670e1d409bbce34490178
H850 Download link: https://www.androidfilehost.com/?fid=4349826312261735367
H850 MD5:fb428e8a245e06d66037a4254b519ebf
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android_device_lge_msm8996-common
Last Updated Mar. 11, 2020
Thanks to x86cpu's posts, Dark98, Electimon, Gabi and the countless others who helped me out!

Will test the h850 build as soon as you release it! :good:

I would love this for the h840! Oreo and security patches sounds great.

ml11ML said:
Will test the h850 build as soon as you release it! :good:
Click to expand...
Click to collapse
Build posted. See link in first post.

LollipopLover said:
I would love this for the h840! Oreo and security patches sounds great.
Click to expand...
Click to collapse
I would love to build for the h840, unfortunately it seems harder to build for. Not seeing a whole lot of sources or development on that variant.

Thank you anyway. I'll always have hope.

Thanks, @Bernie_nix this rom is super stable I was wondering how you build LineageOS4Microg the instructions on their website didn't make sense to me. Thanks so much for this rom. Will you make Pie builds?

ROMSG said:
Thanks, @Bernie_nix this rom is super stable I was wondering how you build LineageOS4Microg the instructions on their website didn't make sense to me. Thanks so much for this rom. Will you make Pie builds?
Click to expand...
Click to collapse
Yes I will continue forward to make an los 16 microg build. As far building yourself, please read the first post. I will not answer any questions related to building in this current thread after my response below.
I'm going to put together some info on GitHub with required files and some instructions to build on Ubuntu. In a nutshell, you install docker on Ubuntu, install the microg docker container and then supply a manifest file for the docker to download sources, etc.
I don't provide support for building in my threads because it's off-topic and really adds quite a bit of support that is better provided in its own unique thread where many members can help. I would be happy to answer questions in a Q/A thread of its own, on GitHub or in a telegram group.
If anyone is reading this and knows of an active telegram group for the g5 please message me and I'd be happy to provide assistance there. Otherwise wait until I update on GitHub. I have my reasons but do happily share in the spirit of open source. A ROM release thread is not the place to do it.

Amazing rom! Just installed on my h850 and it works great! The suggested GCAM is also very good. I have tested NFC and it does work fine (tested only between 2 phones). The IR however seems to work very strange... I tested with the app irplus which does seem to transmit something the first time you press a button but then it just starts loop blinking the IR led like a notification led on off on off on off about every second until a reboot. You can see this by pointing another camera at it. Also i was just wondering if it's possible for you to somehow add fm radio? It worked great on the stock rom but I noticed that no custom roms seem to have it. It isn't something that would cause me to not use this great rom but it would be nice to have. Also.. I wiped everything in orange fox before installing including system10 before I noticed the warning about keeping that but it works fine so far. Do I need to do something about it or can I just ignore it? What even is system10? First time I've ever seen it on any device.

ml11ML said:
Amazing rom! Just installed on my h850 and it works great! The suggested GCAM is also very good. I have tested NFC and it does work fine (tested only between 2 phones). The IR however seems to work very strange... I tested with the app irplus which does seem to transmit something the first time you press a button but then it just starts loop blinking the IR led like a notification led on off on off on off about every second until a reboot. You can see this by pointing another camera at it. Also i was just wondering if it's possible for you to somehow add fm radio? It worked great on the stock rom but I noticed that no custom roms seem to have it. It isn't something that would cause me to not use this great rom but it would be nice to have. Also.. I wiped everything in orange fox before installing including system10 before I noticed the warning about keeping that but it works fine so far. Do I need to do something about it or can I just ignore it? What even is system10? First time I've ever seen it on any device.
Click to expand...
Click to collapse
Thank you for your kind words! I've been testing it on my h830, and it really has brought some new life to my device. Even my pictures aren't coming out yellow like they were on stock! Thank you for testing NFC, and I am glad to hear that works for you. I had similar results with the IR blaster, and that's one of the features I love about this phone; I will try to see if I can improve the functionality as at least it does turn on but unfortunately can't give an ETA; this will involve looking into some lg and lineage sources if they are available. I will also look into fm radio. As most custom roms are built off of a similar base, that explains why it doesn't work in most. It may not be possible to pull the files and include them in the rom, but I may be able to create a magisk module with some lg files; again can't give an ETA as I don't know what I will find or how long it will take. I will investigate though. As for system 10 in ofox, I haven't been able to find much if any documentation on it. As I didn't erase it on install and it booted, I figured best to be on the safe side

Bernie_nix said:
Thank you for your kind words! I've been testing it on my h830, and it really has brought some new life to my device. Even my pictures aren't coming out yellow like they were on stock! Thank you for testing NFC, and I am glad to hear that works for you. I had similar results with the IR blaster, and that's one of the features I love about this phone; I will try to see if I can improve the functionality as at least it does turn on but unfortunately can't give an ETA; this will involve looking into some lg and lineage sources if they are available. I will also look into fm radio. As most custom roms are built off of a similar base, that explains why it doesn't work in most. It may not be possible to pull the files and include them in the rom, but I may be able to create a magisk module with some lg files; again can't give an ETA as I don't know what I will find or how long it will take. I will investigate though. As for system 10 in ofox, I haven't been able to find much if any documentation on it. As I didn't erase it on install and it booted, I figured best to be on the safe side
Click to expand...
Click to collapse
I see. Anyway thank you for looking into the IR issue as I agree that it's a great feature and also the fm radio. I would not have any problems with it being a magisk module if it can't be added to the rom. And yes, the phone runs great with this rom so far. Very responsive and minimal battery drain even with my half dead battery that dies at 50%. It is definitely my new daily driver.

New build released to update to March 2020 security update. See 1st post for download links.

Bernie_nix said:
New build released to update to March 2020 security update. See 1st post for download links.
Click to expand...
Click to collapse
Installed on my h850 over the old build and wiped cache and it works. :good:

ml11ML said:
Installed on my h850 over the old build and wiped cache and it works. :good:
Click to expand...
Click to collapse
Great to hear. Thanks for your feedback!

Cnt install googleplay store.

mie_ayam said:
Cnt install googleplay store.
Click to expand...
Click to collapse
Its microg....a Google play replacement. Read the first post. That's the whole point of this ROM! I think you may be looking for regular lineageos.

this rom have low mic issue and low sound issue?

Zorcnecrophades said:
this rom have low mic issue and low sound issue?
Click to expand...
Click to collapse
I know that Los usually has lower sound. Haven't experienced the lower mic myself but I could be wrong. You could probably easily edit some mixer_path volumes if it is not to your liking.

Hi, real cool rom. thanx a lot. But: PicoTTS does not work. App shuts down in test. And Hdmi (or Slimport??) on an OTG does not work.
And the LG Camera Plus add-on-piece is not recognized
Is H850_v2.2-mk2000.zip compatible with this rom? or maybe H850_v0.3-BETA2-mk2000.zip?
(after Test) No its not, camera is not working with both kernels and Android says, thats the Vendor Image is not right, when i reboot. What ever that means
P.S. The rest is really stable after 2 days of testing.#
P.P.S. Changing BT Connections from one (Airpods Gen 2) to another (JBL Charge 2) while playing music reboots the phone.

Bernie_nix said:
Its microg....a Google play replacement. Read the first post. That's the whole point of this ROM! I think you may be looking for regular lineageos.
Click to expand...
Click to collapse
yes. because I am accustomed to downloading apps on Playstore. and some applications when we want to log in using a google account. can't log in using a google account that is included in the Google Microg app.
Thank this rom great . mybe this is litel bug.

[ROM][Official][Nightly] LineageOS 18.1 for OnePlus 3/3T

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.

Database Info

welcome