well, the fact is now that I am on OxygenOS 9.0.5 now. and I have the drainage here.
D
Deleted member 4405529
Guest
The way of hunting down the reason of drainage is the same. Check which wake locks are preventing deepsleep and check the (4 Mio) log for the trigger of the deepsleep preventing wake locks.
Great work! Just what I was looking for.
I'm on lineage 16 (official), but I'd like to have some additional features. One of them is signature spoofing, so I can use microG.
Can LOS be updated to NLOS? If so, do you think that if I dirty flash the NLOS rom over the official lineage I'll get to keep all the data? What are the odds I'll have to ease it? It's my dad's phone and he doesn't want to go over the back up - restore process again haha.
Any ideas?
I'm on lineage 16 (official), but I'd like to have some additional features. One of them is signature spoofing, so I can use microG.
Can LOS be updated to NLOS? If so, do you think that if I dirty flash the NLOS rom over the official lineage I'll get to keep all the data? What are the odds I'll have to ease it? It's my dad's phone and he doesn't want to go over the back up - restore process again haha.
Any ideas?
D
Deleted member 4405529
Guest
You can try, but it's neither recommended, nor supported. If you dirty change from los to nlos and get any issues you are on your own. Don't report issues in this thread.
Clean flashing and restoring the data partition from a previous installation's setup is the same as dirty flashing - obviously. Clean flashing is needed to reset all settings and remove all apps including there data. I always recommend to use apps own backup/restore functions (where possible), i.e. I export the settings from k9, after clean flashing I import the settings inside k9 again. The same goes for nova. The only app I restore regulary after a clean flash is navigon, becaise of 6GB offline maps.
I've learned the hard way, that clean flashing and setting up tje device again is much less time comsuming, then dirty changing/migrating and hunting down issues later.
Yeah, I know. That's what I do. I even wipe clean and let android format the sd on my device every time I flash a new rom. This also helps me keep a long term settings and data back up in the event of a device lost or failure (...).
But it's my dad's we are talking about. And he wants to regain his privacy from Google and others with the minimum affect to his daily usage. And now he needs microG for some apps to work properly. The main priority was to be able to take good pictures, and gcam pretty neat (but it needs microG). Luckily, installing it, without signature spoofing, was enough. So he's happy now
So, I've heard lineage 17 (android 10) is about to go public (or is already published, I don't know the status). So I guess there is gonna be a lineage 17 for one plus 3T, eventually. Once this happens, do you plan on working on a NLOS for android 10, too? It'd be great. If so, I'll make him wait patiently for it to come and then we'll clean install it.
D
Deleted member 4405529
Guest
I don't know if and when, yet. I never ship roms without - at the very least - without selinux set to enforcing and hw encryption working. It's the same every year: when the rom is full featured and most issues are ironed out, everybody is searching for the next release... I love using nlos-16.0 and doesn't feel any hurry or need to change to q, yet.
These two are absolutely a must. And having a stable rom is always nice haha. I'm talking long term here. I'm using pie myself and have no intention to update to any time soon. They are releasing new android versions too often (so people have to renew their phones more often not to be left behind if using stock roms).
Updating to an other android version is an excuse to make him back up his data and upgrade to another rom.
But again, long long term. Eventually, the day will come. But it's not in the forseen calendar.
Thank you!
@nvertigo67 How to make IMS status as registered. Sorry for touching volte topic. IMS should be registered to make volte work. Thanks.
D
Deleted member 4405529
Guest
We've been there already. Compare oos' apns-conf.xml and nlos' apns-conf.xml, edit nlos' apns-conf.xml according to oos' apns-comf.xml, check permissions and selinux contexts, reboot, delete network settings and reboot again.
I've ask you to do that two times - this is the third time.
After a quick check I found the ims apn (at least) is missing. I can't test, if adding the ims apn is resolving the issue.
Please use the rom, you've mentioned in https://xdaforums.com/showpost.php?p=80634605&postcount=1164 which has volte working for 404/49 according to your post, or follow the directions in my previous postings.
Hello @nvertigo67
I'm experiencing the phone dying while in my pocket from last 3-4 days. No new app has been installed and no changes have been made. Ive taken logs using SysLog app and the last_kmsg option was greyed out when I started my phone by pressing power button for several seconds. I'm attaching the log here. If the phone dies next time in pocket, let me know if i can pull any log some other way to help you.
I'm experiencing the phone dying while in my pocket from last 3-4 days. No new app has been installed and no changes have been made. Ive taken logs using SysLog app and the last_kmsg option was greyed out when I started my phone by pressing power button for several seconds. I'm attaching the log here. If the phone dies next time in pocket, let me know if i can pull any log some other way to help you.
D
Deleted member 4405529
Guest
op3/t's kernels doesn't support last_kmesg since 14. Use /sys/fs/pstore instead. Keep in mind, that the content of /sys/fs/pstore needs to be copied on the very next reboot, otherwise it's gone. I.e.: if you boot to recovery after a crash, you need to copy pstore in this recovery session; if you tebot to system again, pstore has the logs for the rec9very session, not from the crash.
Sadly a logcat from after a reboot doesn't have any info on what happened before the reboot.
@All: does anybpdy expirience the issue @abhibnl has described? I'm using a flip cover, which may have saved me from the above.
Rock stable on my side. No such problems.
op3/t's kernels doesn't support last_kmesg since 14. Use /sys/fs/pstore instead. Keep in mind, that the content of /sys/fs/pstore needs to be copied on the very next reboot, otherwise it's gone. I.e.: if you boot to recovery after a crash, you need to copy pstore in this recovery session; if you tebot to system again, pstore has the logs for the rec9very session, not from the crash.
Sadly a logcat from after a reboot doesn't have any info on what happened before the reboot.
@All: does anybpdy expirience the issue @abhibnl has described? I'm using a flip cover, which may have saved me from the above.
Just to make sure I perform these steps correctly the next time my phone dies in pocket (I hope it won't). Once i force restart it, do I have to force reboot it into recovery directly or can i reboot it normally and then select recovery by pressing volume up button when prompted?
Once I am in recovery with the correct method, I'll copy the contents of /sys/fs/pstore
If your second option refers to pressing the volume key on the screen shown in the attachment, then, yes, both options are good.
Sent from my OnePlus 3T using XDA Labs
Attachments
Nope, no such issue.
Also I think @All is the name of a user. Poor guy must be getting mentioned so much.
D
Deleted member 4405529
Guest
It's just important, that it's the very next reboot. Some people think "very next reboot" as "next boot to system", which is NOT true. You van also boot ditectly to system and get pstore (if rooted), but it needs to be the very next reboot. I'm recommending recovery, because it doesn't needs root, but the only important point is: it must be taken on the very next reboot.
D
Deleted member 5616867
Guest
Nope
Just a random crash, but it's because xposed/xprivacylua i believe, so i won't bother
Mobile network automatic switching is also good. Seems like the setting must be on LTE/TDSCDMA/CDMA/EVDOGSM/WCDMA in order to work.
D
Deleted member 4405529
Guest
UPDATE (Airtel ims apns; maintainance)
Build 20191102
Note: 20191022 removed because of incomplete patching (curtent.pick.sh wasn't run). If you use 20191022 update as soon as possible to 20191024.
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.5 firmware is required. At this point you have two options:
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 2 Nov 2019, 09:30:50 CET / 2 Nov 2019, 08:30:50 UTC):
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
Happy flashing!
Build 20191102
Note: 20191022 removed because of incomplete patching (curtent.pick.sh wasn't run). If you use 20191022 update as soon as possible to 20191024.
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.5 firmware is required. At this point you have two options:
- You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):
- You want to keep your current setup and like to dirty flash on top of beta builds:
I've created a firmware package from OxygenOS 9.0.5. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.5 blobs, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 2 Nov 2019, 09:30:50 CET / 2 Nov 2019, 08:30:50 UTC):
- current.pick.sh: "APNs: add IMS APNs for Airtel [IN]". — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
55DDeleted member 4405529NLOS is an unofficial unified LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build.
Thanks to @UnbracedTundra NLOS has it's own logo, bootanimation and wallpapers. Thanx to @Syssx for evolving the bootanimation.
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. This build is optimized (i.e. gcc-7.3 is used for kernel building) and has quite some candy (like OMS exPoseres).
In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-P.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch, ported to Pie) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps).
The kernel is prepared for Wireguard VPN - to use Wireguard for vpn-tunnels you need to get the WireGuard-apk from playstore. WireGuard developer @zx2c4 runs a dedicated Wireguard Thread.
The shipped kernel is prepared to comply to googles safetynet api. Since google has started to check if the sec patch level matches the build fingerprint, it's necessary to adjust the aosp based shipped ro.build.version.security_patch to the currently used OxygenOS build fingerprint. For details see posting #3 and the announcment of each build.
Additionally nlos' kernel has been upstreamed to the latest 3.18.y (3.18.140 EOL) patches. Since 3.18.y is no longer supported by kernel.org, I also merge https://source.codeaurora.org/quic/la/kernel/msm-3.18/. This way we get the latest qualcomm fixes and patches. Codeaurora is still supporting and maintaining their msm-3.18 project. To show the current state of the nlos kernel the naming scheme is "3.18.140-[caf tag]-NLOS-g[git hash]", e.g.: "3.18.140-LA.UM.7.6.r1-07000-89xx.0-NLOS-g63a7debca7d7". The staged qcacld-2.0 wifi driver is also updated to the same caf tag from https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0. This way Qualcomm security bullentins (https://www.qualcomm.com/company/product-security/bulletins ) are brought in.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://xdaforums.com/showpost.php?p=58239877&postcount=3
Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://xdaforums.com/showpost.php?p=58239877&postcount=2
Code:#include <std_disclaimer.h> /* * Your warranty isn't void: we are on an oneplus device. * * 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.
This thread is for NLOS-16.0 builds for oneplus3 and onepluy3t. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano
I 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 (i.e. by using gapps larger then opengapps-nano)
First time flashing NLOS 16.0 on your device, or coming from another ROM:
- Backup your current ROM and make sure you have backups of your data you want to keep.
- Download the ROM below in the downloads section.
- Download OpenGapps arm64 Android 9.0 pico or nano don't use a package larger then nano.
- Download and flash official twrp-3.4.0-0.
- Download and flash latest OxygenOS Oreo firmware.
- Optional (mandatory, if you have issues with encryption): Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you want to use f2fs you need to change the fs back to f2fs - it's possible but not recommended (at least if you don't have basic knowledge of fs implementations). Many twrp versions have serious regressions regarding f2fs with encryption footer. Though this should be fixed by now, you can always manually format f2fs with footer. See: https://xdaforums.com/oneplus-3/one...1-20180223-t3754855/post75688089#post75688089.
- Wipe system, data and caches.
- Flash NLOS.
- Flash Google Apps. If you want to use microG skip this step and install microG (How to use Android without Google Apps).
- Optional: flash Magisk (if you need root)
- Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery (if necesarry flash the firmware zip recommended by the release notes) and flash the updated NLOS zip - don't forget to wipe dalvik and cache. Settings, apps and even google apps are preserved.
Important: if you encounter any issues, a clean install is recommended and even required if you need support.
I won't build on a daily (or nightly) basis. I will publish new builds, if I fixed something, important upstream changes or new security patchlevels.
LineageOS changelog: https://www.lineageoslog.com/16.0
History
Firmware
NVertigo's Oxygen Firmware Archive
TWRP
Latest official twrp downloads
Thread for official twrp
(Note: Don't use official twrp-3.2.3-1! Use dianlujitao's inofficial twrp-3.2.3-10 announced here or
latest official twrp.)
Google Apps:
OpenGapps arm64 Android 9.0 pico or nano
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/nlos-16.0 (If you want to build this rom yourself, consult the file named README, it's outdated, but still helpfull)
- Aytex, who made all of the banners on this post.
- team-exynos5420 for the OP templete.
- All the LineageOS-Team.
- @Lord Boeffla for patiencely answering my questions.
- @koenkk
- @Sultanxda
- @TheFrozen4 for documentation and optimizing this OP.
- The microG Team
- @UnbracedTundra for all the awesome NLOS-ArtWork.
- @zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
- @Arnova8G2 for his GoggleCamera port.
- @S4turno for this great thread on GoggleCamera Mods.
- @knpk13 for debugging this OP.
- Substratum Dev Team
- @danieldmm for opening my eyes for the obvious...
- @mcdachpappe for helping me with additional notification slider options.
- @mesziman for helping to get soong play nicely with sdclang.
- @Syssx for evolving the bootanimation.
- Team MOKEE for longshot.
- @MSe1969 for upstreaming the kernel to https://android.googlesource.com/kernel/common/+log/refs/heads/android-3.18 after EOL on kernel.org.
- ...and everybody I forgot.
Happy flashing!
XDA:DevDB Information
NLOS-16.0, ROM for the OnePlus 3
Contributors
nvertigo67
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: OxygenOS 5.0.8
Based On: lineageos
Version Information
Status: Beta
Created 2018-12-15
Last Updated 2018-12-1828DDeleted member 4405529Safetynet api
EDIT: Ive updated the zips. Make sure you use the zips with "v02" in their names! The "v02" versions work with android pie roms as well as with android 10 (system-as-root) roms.
Lately google has started to be more restrictive about build fingerprint and the date of the security patch level. For passing CTS profile match it's now required that ro.build.version.security_patch is the same as in the OxygenOS build the build fingerprint.
Generally the vendor security patch level date is one or more months behind the security patch level date of the (aosp) security patchlevel date of the LineageOS (and therefor NLOS) codd base.
Typically ro.build.version.security_patch is set the the security patch level date of the code base. Sadly this breaks passing CTS profile match, if the aosp/los/nlos security patch level date is different from the vendor security patch level date of the build fingerprint.
To work around this it's mandatory to set ro.build.version.security_patch to the vendor security patch level date. These zips just replace the date string of ro.build.version.security_patch in /system/build.prop. The zips are signed with the (aosp) los test keys.
- "OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1905251415:user/release-keys" and
"OnePlus/OnePlus3/OnePlus3T:9/PKQ1.181203.001/1905250152:user/release-keys" are taken from OOS 9.0.2 which require ro.build.version.security_patch to be 2019-04-01.
Use sec-patch-2019-04-01_v02.zip:
ZIP: https://drive.google.com/open?id=10mE0Wq3s_3bwZHtxBT4tt_q0RiTgOlvK
MD5: https://drive.google.com/open?id=1vsYzc4tYDlQeOhP9LD-TovM6AC1WXvXw
- "OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1907311932:user/release-keys" and
"OnePlus/OnePlus3/OnePlus3T:9/PKQ1.181203.001/1907311932:user/release-keys" are taken from OOS 9.0.5 which require ro.build.version.security_patch to be 2019-08-01. This is what you currently need for nlos-16.0 and lineage-16.0.
Use sec-patch-2019-08-01_v02.zip:
ZIP: https://drive.google.com/open?id=1FW86qprj0KHliNmUOWoic48-p_Frxnkn
MD5: https://drive.google.com/open?id=1OunTG14GvE8eYvDrstyewysfsv6tCudm
- "OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1911042107:user/release-keys" and
"OnePlus/OnePlus3/OnePlus3T:9/PKQ1.181203.001/1911042108:user/release-keys" are taken from OOS 9.0.6 which require ro.build.version.security_patch to be 2019-10-01.
Use sec-patch-2019-10-01_v02.zip:
ZIP: https://drive.google.com/open?id=1P4JKcOp9HNwwk5vyURawUrZ3xslZ4Pm9
MD5: https://drive.google.com/open?id=1TSRNjpB4_ygKRTCd0CEtDKNJua72f232
To return to the rom shipped security patch level date, just dirty flash the rom.
Note:
These zips alone doesn't make your device passing safetynet api. Additionally you need to fullfill at least one of these requirements:- a locked bootloader
- Magisk installed
- a kernel patched to throw away the tripped verity flag (like the shipped nlos kernel)
Happy flashing!27DDeleted member 4405529UPDATE (kernel: 3.18.139-rc2; maintainance)
Build 20190426
Releasenotes:
NLOS-16.0 relays on OxygenOS firmware. OxygenOS 5.0.8 firmware or later is required:
- Oneplus 3T: OxygenOS 5.0.8 firmware
- Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 26 Apr 2019, 09:47:25 CEST / 26 Apr 2019, 07:47:25 UTC):
- Revert "current.pick.sh: pie-lockscreen-shortcuts." — Nvertigo
- Revert "current.pick.sh: "Audio assets: add NFC sounds"." — Nvertigo
- current.pick.sh: p-display-shrink. — Nvertigo (swipe on-screen-navbar to activate - currently no other trigger available)
- op3: Fix keypad fw update denial — dianlujitao
- op3: s/ro.vendor.product/ro.product.vendor/g — Arne Coucheron
- Merge remote-tracking branch 'los/lineage-16.0' into linux-stable/merge-16.0 — Nvertigo (mainly qcalcd-2.0 updates)
- Merge '3.18.139-rc2' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc into linux-stable/nlos-16.0 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!26DDeleted member 4405529UPDATE (automatic call recording; maintainance)
Build 20190823
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.5 firmware is required. At this point you have two options:
- You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):
- You want to keep your current setup and like to dirty flash on top of beta builds:
I've created a firmware package from OxygenOS 9.0.5. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.5 blobs, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 23 Aug 2019, 10:51:50 CEST / 23 Aug 2019, 08:51:50 UTC):
- Revert "NLOS: add for reference /vendor/xiaomi." — Nvertigo
- current.pick.sh: "Dialer: Add autorecord feature". — Nvertigo
- Revert "current.pick.sh: "fix-hwc2-outdoor"." — Nvertigo
- op3/t: Remove config_tether_upstream_types — Sam Mortimer
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!26DDeleted member 4405529UPDATE (one-hand-mode-tile & maintainance)
Build 20190715
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.4 firmware is required. At this point you have two options:
- You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):
- You want to keep your current setup and like to dirty flash on top of beta builds:
I've created a firmware package from OxygenOS 9.0.4. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.4 blobs, but you don't need to reformat the userdata partition.
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 15 Jul 2019, 10:15:54 CEST / 15 Jul 2019, 08:15:54 UTC):
- current.pick.sh: "pie-onehandmode-tile".
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
