NLOS 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://forum.xda-developers.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://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty 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://forum.xda-developers.com/on...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
Build 20210714
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.6 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):
Oneplus 3T: OxygenOS 9.0.6 firmware without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files
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.6. 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.6 firmware, but you don't need to reformat the userdata partition (for details see: https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164).
Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://forum.xda-developers.com/on...-nlos-16-0-t3879405/post78433987#post78433987 .
Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.
If you want to use Alipay with fingerprint authentication, follow @Galiis' directions in posting #6.
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 14 Jul 2021, 15:39:59 CEST / 14 Jul 2021, 13:39:59 UTC):
my_build.sh: remove jack-server hanling; update mktemp call. — Nvertigo
Patch up: P_asb_2021-07. — Nvertigo
Revert "nlos.xml: add Bromite System Webvoew from MSe1969's repo." — Nvertigo (Thanx @MSe1969
kernel: patches mentioned in https://source.android.com/security/bulletin/2021-07-01?hl=en(ASB 2021 07):
qcacld-2.0: Send assoc reject upon failing to post ASSOC_IND — Paul Zhang
WG: squash WireGuard-linux-compat-1.0.20210606. — Nvertigo
Patch up: P_asb_2021-05. — 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!
Build 20210620
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.6 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):
Oneplus 3T: OxygenOS 9.0.6 firmware without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files
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.6. 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.6 firmware, but you don't need to reformat the userdata partition (for details see: https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164).
Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://forum.xda-developers.com/on...-nlos-16-0-t3879405/post78433987#post78433987 .
Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.
If you want to use Alipay with fingerprint authentication, follow @Galiis' directions in posting #6.
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 20 Jun 2021, 08:27:07 CEST / 20 Jun 2021, 06:27:07 UTC):
nlos.xml: add Bromite System Webvoew from MSe1969's repo. — Nvertigo
nlos.mk: use Bromite System Webvoew from MSe1969's repo. — Nvertigo
kernel: patches mentioned in https://source.android.com/security/bulletin/2021-06-01?hl=en(ASB 2021 06):
qcacld-2.0: Add eapol checking for intra-bss fwd & indicate in IPA exc path — Tiger Yu
qcacld-2.0: Add eapol sanity checking for intra-bss forwarding & indicate — Lihua Liu
qcacld-2.0: Drop mcast and plaintext frags in protected network — Tiger Yu
qcacld-2.0: Discard frag frames if the PN is not consecutive — Tiger Yu
qcacld-2.0: Flush RX packets for peer after key installation — Tiger Yu
qcacld-2.0: Initialize preauth node — Liangwei Dong
qcacld-2.0: Fix SAP data tx block issue — Brandon Huang
qcacld-2.0: Fix a compile error — lihual
crypto: Fix possible stack out of bound error — Tanwee Kausar
HID: make arrays usage and value to be the same — Will McVicker
WG: squash WireGuard-linux-compat-1.0.20210606. — Nvertigo
Patch up: P_asb_2021-05. — 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!
Build 20210509
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.6 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):
Oneplus 3T: OxygenOS 9.0.6 firmware without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files
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.6. 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.6 firmware, but you don't need to reformat the userdata partition (for details see: https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164).
Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://forum.xda-developers.com/on...-nlos-16-0-t3879405/post78433987#post78433987 .
Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.
If you want to use Alipay with fingerprint authentication, follow @Galiis' directions in posting #6.
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 9 Mai 2021, 10:22:49 CEST / 9 Mai 2021, 08:22:49 UTC):
Update webview to 90.0.4430.204. — Nvertigo
see https://bitbucket.org/nvertigo/android_external_chromium-webview/src/master/patches/ for a complete list of patches
kernel: patches mentioned in https://source.android.com/security/bulletin/2021-03-01?hl=en(ASB 2021 02):
tty: Fix ->pgrp locking in tiocspgrp() — Jann Horn
WG: squash WireGuard-linux-compat-1.0.20210424. — Nvertigo
Patch up: P_asb_2021-05. — 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!
Build 20210305
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.6 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):
Oneplus 3T: OxygenOS 9.0.6 firmware without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files
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.6. 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.6 firmware, but you don't need to reformat the userdata partition (for details see: https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164).
Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://forum.xda-developers.com/on...-nlos-16-0-t3879405/post78433987#post78433987 .
Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.
If you want to use Alipay with fingerprint authentication, follow @Galiis' directions in posting #6.
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 5 Mär 2021, 15:43:32 CET / 5 Mär 2021, 14:43:32 UTC):
Update webview to 88.0.4324.207. — Nvertigo
see https://bitbucket.org/nvertigo/android_external_chromium-webview/src/master/patches/ for a complete list of patches
kernel: patches mentioned in https://source.android.com/security/bulletin/2021-03-01?hl=en(ASB 2021 02):
ANDROID: xt_qtaguid: Remove tag_entry from process list on untag — Kalesh Singh
WG: squash WireGuard-linux-compat-1.0.20210219. — Nvertigo
op3/t: gps: use ntp.org auto-selection. — Nvertigo
op3t: gps: XTRA: use https and check for version 3. — Nvertigo
op3/t: use https for downloading gps XTRA data. — Nvertigo
Patch up: P_asb_2021-03. — 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!
Build 20210207
Releasenotes:
This build relies on OxygenOS firmware. OxygenOS 9.0.6 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):
Oneplus 3T: OxygenOS 9.0.6 firmware without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files
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.6. 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.6 firmware, but you don't need to reformat the userdata partition (for details see: https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164).
Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files
If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://forum.xda-developers.com/on...-nlos-16-0-t3879405/post78433987#post78433987 .
Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.
If you want to use Alipay with fingerprint authentication, follow @Galiis' directions in posting #6.
For a complete list of additional cherry picks see: current.pick.sh.
Changelog (Last repo sync: 7 Feb 2021, 14:00:53 CET / 7 Feb 2021, 13:00:53 UTC):
Update webview to 88.0.4324.152. — Nvertigo
see https://bitbucket.org/nvertigo/android_external_chromium-webview/src/master/patches/ for a complete list of patches
kernel: patches mentioned in https://source.android.com/security/bulletin/2021-02-01?hl=en(ASB 2021 02):
WG: squash WireGuard-linux-compat-1.0.20210124 — Nvertigo
usb: dwc3: ep0: Return from handle_status if ep0_delegate_req succeeds — Udipto Goswami
msm: kgsl: Remove VM_MAYWRITE flag to restrict mprotect — Indira Biruduraju
current.pick.sh: use prebuilt python-2.7 instead of system python. — Nvertigo
Revert "current.pick.sh: system/nfc: SDCLANG-6: fix declaration." — Nvertigo
Add full-featured linux x86 64bit Python 2.7.18. — Nvertigo
Use freshly added full-featured linux x86 64bit Python 2.7.18. — Nvertigo
Patch up: P_asb_2021-02. — 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!
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-18
5GHz Tethering Hotspot
Symptom:
If you start the Tethering Hotspot (TS) on the 5GHz band, your clients can't see the TS, though it's fired up according to logcat.
Background:
The TS is run on a channel to high to be visible on the clients:
nvertigo67 said:
For me (vodafone.de; mcc=262, mnc=02) the 5GHz hot spot is always fired up on channel 157/5785MHz. Besides the fact that no European wifi device can use this channe/freq, in Germany it's prohibitted to broadcast on this channel, if one hasn't been licenced to do so. In Germany using this freq without being licenced, isn't a minor breach of law, but a crime.
Considering this it should be a high priority task to either fix this, or disable the selection of 5GHz all together. I've tried to debug this, but now I'm stuck and need help.
To see what's hap0ening I've added aome debugging, and tried to force a (European/German) legal freq: channel 44/5220MHz.
https://github.com/nvertigo/android...mmit/950adab4d870ecd83564f3e6c5ba77d9f2f57430
https://github.com/nvertigo/android...mmit/a4829959a3333c0a0d553f7f468f37c49b38a0a0
The first problem is here (obviously the countrycode is set, but not honored):
Code:
01-29 20:31:57.861 2523 3390 E ApConfigUtil: nvertigo: updateApChannelConfig: default band: 0; default channel: 6
01-29 20:31:57.862 2523 3390 E ApConfigUtil: nvertigo: updateApChannelConfig: band: 1; channel: 0
01-29 20:31:57.863 2523 3390 D ApConfigUtil: nvertigo: Forcing channel 44; computed freq: 5745; computed channel: 149
01-29 20:31:57.863 2523 3390 D ApConfigUtil: nvertigo: allowed freqs: [5180, 5200, 5220, 5240, 5745, 5765, 5785, 5805, 5825, 5845]; allowed5GFreqList.length: 10
01-29 20:31:57.863 2523 3390 E ApConfigUtil: nvertigo: config.apChannel: 44
01-29 20:31:57.869 2523 3390 D WificondControl: nvertigo: startHotspot: true
01-29 20:31:57.869 2523 3390 D WificondControl: nvertigo: startHotspot: successfull
01-29 20:31:58.001 6441 6441 I hostapd : ACS: nvertigo: hostapd_drv_do_acs succeeded.
01-29 20:31:58.002 2523 3390 D SoftApManager: nvertigo: Soft AP is started: wlan0channel: 44
01-29 20:31:58.202 6441 6441 I hostapd : wlan0: ACS-COMPLETED freq=5785 channel=157
01-29 20:31:58.435 2026 2026 I wificond: New channel on frequency: 5785 with bandwidth: 80MHz
01-29 20:31:58.495 6441 6441 I hostapd : wlan0: IEEE 802.11 driver had channel switch: freq=5785, ht=1, offset=1, width=3 (80 MHz), cf1=5775, cf2=0
01-29 20:31:58.495 6441 6441 I hostapd : wlan0: IEEE 802.11 driver had channel switch: freq=5785, ht=1, offset=1, width=3 (80 MHz), cf1=5775, cf2=0
01-29 20:31:58.495 6441 6441 I hostapd : wlan0: AP-CSA-FINISHED freq=5785 dfs=0
The allowed freqs are just wrong: it is "5180, 5200, 5220, 5240, 5745, 5765, 5785, 5805, 5825, 5845", while for country code EU or DE only "5180, 5200, 5220, 5240" are allowed for wifi.
I circumvent this the ard way: I force the channel to 44, no matter whats randomly picked from the wrong allowed list.
Now it gets awarkned: no matter what channel is requested by the framework, after hostapd has completed this part:
https://github.com/nvertigo/android...553f7f468f37c49b38a0a0/src/ap/acs.c#L911-L919
the hotspot is started on 157.
Any help is highly appriciated!
I also wonder if this is an op3/t specific issue, or if this is a general issue.
Next question: if frameworks/opt/net/wifi is calculating the channel, why is the Automatic Channel Selection (ACS) passed down to the wlan driver? And (most confusing me): where, when and how is the countrycode passed down to tne driver?mAnd one more: on boot (before even touching the hotspot switch the log shows:
Code:
01-29 20:31:09.628 2026 2026 I wificond: 2.4Ghz frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472
01-29 20:31:09.628 2026 2026 I wificond: 5Ghz non-DFS frequencies: 5180 5200 5220 5240 5745 5765 5785 5805 5825 5845
01-29 20:31:09.628 2026 2026 I wificond: 5Ghz DFS frequencies: 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 56
Immidiatly after touching the switch, the log shows:
Code:
01-29 20:31:57.747 2026 2026 I wificond: 2.4Ghz frequencies:
01-29 20:31:57.747 2026 2026 I wificond: 5Ghz non-DFS frequencies:
01-29 20:31:57.747 2026 2026 I wificond: 5Ghz DFS frequencies:
Click to expand...
Click to collapse
Though I'm wrong on the legal impact (EU laws replace old German regulations), the problem stays the same: the TS channel is to high to be seen by my (older) in Germany bought clients.
Workaround/Hack:
The easiest (and dirty) way to force the TS to be starzed on chanmels <100 is to set the country code used for the TS to Israel (IL9, because no channels >=100 are allowed). To do that uncomment line 238 and set it to IL:
Code:
gAPCntryCode=IL
Or use this flashable zip (does exactly whats described above):
ZIP: https://drive.google.com/open?id=1BSldodjxahxWdrYtCvDEzmTYEhNCodvu
MD5: https://drive.google.com/open?id=1frCinyMBsRyJR0p9_3e4SV35Vl0AC0A7
Happy flashing and tethering!
Safetynet 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!
Magisk with locked bootloader
Magisk versions up to - at least - 20.0 doesn't sign the boot image, if initiated from addon.d (on every dirty flash, aka update).
If you want to use Magisk with a locked bootloader, flash the attached VerifiedBootSigner-v8.01-aosp-key.zip after each Magisk addon.d installation. Keep in mind, that updating the rom (aka dirty flashing) reinstalls Magisk (from addon.d), which requites reflashing VerifiedBootSigner-v8.01-aosp-key.zip!
VerifiedBootSigner-v8.01-aosp-key.zip signs the bootimage with the required aosp verity key.
Happy flashing!
The "Error 7" error
If a flashable zip is flashed in recovery, the rcobery extracts the zip and executes
Code:
META-INF/com/google/android/update-binary
If "update-binary" doesn't return successfully twrp based recoveries retrun a red line on the twrp console
Code:
Updater process ended with error: 7, Error installing zip file
This just means that "update-binary" hasn't completed successfully - nothing more, nothing less. It doesn't say anything on the reason, why it has failed.
There can be multiple reasons "update-binary" fails. Some of the more common (the list is neither complete, nor does it show any priorities)
Firmware too old
Device not matching
broken zip file
insufficient free blocks in the fs
wrong fs type on system, data and/or cache
typo in the updater script (extensivly tested by myself)
incompatible rom (i.e. zip is fpr system-as-root mount layout, but installed rom has no system-as-root mount layout - or vice versa)
[...]
As a logical consequence, there can't be a single or universal solution to "Error 7".
Fortunately twrp allows "update-binary" to write to te twrp console. This means the output (including error messages) of "update-binary" is written to the twrp console prior to the red "Error 7" line. Even more details on the reason why "update-binary" fails is the recobery log from twrp (Main Twrp page->Advanced->Copy log to SD).
This also means, that every answer, guide, yt-video etc. claimimg it can fix "Error 7", without asking for the last 2 to 4 lines before the red "Error 7" line may be right by accident, but not by knowledge.
The worst of all advices to fix "Error 7" is to edit "updater-script":
On all source build roms I know of "update-binary" is a edify interpreter reading "updater-script" as input(*). The updater script for nlos looks like this:
Code:
assert(getprop("ro.product.device") == "OnePlus3" || getprop("ro.build.product") == "OnePlus3" ||
getprop("ro.product.device") == "oneplus3" || getprop("ro.build.product") == "oneplus3" ||
getprop("ro.product.device") == "OnePlus3T" || getprop("ro.build.product") == "OnePlus3T" ||
getprop("ro.product.device") == "oneplus3t" || getprop("ro.build.product") == "oneplus3t" || abort("E3004: This package is for device: OnePlus3,oneplus3,OnePlus3T,oneplus3t; this device is " + getprop("ro.product.device") + "."););
assert(op3.verify_modem("2019-11-04 21:20:14") == "1" || abort("Error: This package requires firmware version OxygenOS 9.0.6 or newer. Please upgrade firmware and retry!"););
ui_print("Target: OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1907311932:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup", "/system");
unmount("/system");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore", "/system");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
If the cause for "Error 7" is a device mismatch (line 1 - 5), this may be caused because you don't flash it on an op3/t, or because the recovery you are using doesn't provide the properties "ro.product.device" or "ro.build.product". Though a flash would work when deleting these 5 lines from "updater script", the first case results in a bricked device, the second in a rom flash with an outdated or otherwise incompatible recovery.
If you flash nlos on top of a firmware not matching the blobs nlos uses, this will lead to unwanted side effects like not correctly working hardware parts like sensors including fingerprint scanner and camera. To avoid this "updater-script" has line 6. Deleting line 6 will allow you to flash nlos on an outdated firmware...
Obviously the better way is using a zip only for devices, recoveries and/or firmwares, they are made for.
Conclusion:
In order to solve "Error 7" it's mandatory to solve the "real" error. For this task it's inevitable to know the last lines before the red "Error 7" line on the twrp console and/or the revoery log (Main Twrp page->Advanced->Copy log to SD). The revovery log is always prefered, since it is more detailed then just the console output.
(*)in opposite to i.e. opengapps zips or magisk zips, where "uodate-binary" is a shell script. Both methods - edify interpreter or shell scripts - have their own advantages and drawbacks, generally spoken shell scripts are more flexible. Discussing the technical details is not part of this posting.
Original Post
If you are addicted to Alipay or Wechat pay, I'm highly recommend you switch to other ROMs (like OOS/LOS) which have ifaa and soter components.
Without ifaa and soter components, but your fingerprint sensor is working. There is a 3rd-party method using magisk module implement fingerprint payment for Alipay and Wechat pay. (Use at your own risk!)
Test environment:
ROM: nlos-16.0-20200312 build
Firmware: oxygenos-9.0.6-firmware-3T
Bootloader: Locked
Alipay: 10.1.88.5821 (Google Play)
Magisk: v20.3
Requirements:
Magisk
Rooted Android 6.0+ devices
Installation (for Alipay):
Download Riru-core (v19.7) and Fingerprint-pay-magisk-alipay (v3.9.9) modules. (Links below)
https://github.com/RikkaApps/Riru/releases
https://github.com/eritpchy/Fingerprint-pay-magisk-alipay/releases
Install modules in magisk manager, then enable them and reboot.
Usage:
Open Alipay app, go to the settings, enable it in fingerprint and type your payment password (see attachments).
Pay for a drink to test if it works.
References:
https://github.com/RikkaApps/Riru
https://github.com/eritpchy/Fingerprint-pay-magisk-alipay
https://github.com/eritpchy/Fingerprint-pay-magisk-wechat
PS:
1. This module stores your payment password at your local device (encrypted).
2. It may not work after Alipay or Wechat update.
3. I didn't test Wechat pay module, you can have a try (see references).
Thanks to those module developers for their work.
General thoughts on gapp packages
Note: Consider "Bit Gapps" as place holder for any other gapps vendor then opengapps.
dark'em said:
There is nothing wrong with Bit Gapps, but Open Gapps package is updated daily so it's better to go with it.
Click to expand...
Click to collapse
From my expirience the nightly (or daily for that matter) automatic builds are the biggest drawback of open gapps:
Since these builds arn't tested but just automatic build. This results in quite some broken packages. I've made it my personal habbit to stick with a build, after it has proofed to work (once installed gservices as well as gapps are updated from play store - this means: if you use e.g. an one year old (proofed to work) gapps build used on a clean flash is updated to latest gservices/gapps shortly after first boot.
The lack of knowing about the playstore updates makes users think it's a good idea to "update" the flashable gapps zip, which may lead to issues: some of the gapps and gservices settings are stored in a sqlite db. If the playstore updates contain a sqlite update, which is not present in the new nightly gapps zip and you wipe system but not data to flash that zip (and call it an "update), the db engine is downgraded below the version of the db on data you will get strange side effects and only a clean flash will recover (some of the more common issues in that situation are "lost" notifications, issues with (also third party) apps using cloud messaging gservice and/or switched or absent sounds).
This doesn't mean that bitgapps are better then opengapps - but nightly/daily updated gapps packahes are more prune to user error then gapps builds updated every few months and receive thoroughly testing before shipping.
dark'em said:
Try nano or pico, the rest you can install after from playstore.
Click to expand...
Click to collapse
I completely agree here. If one looks at e.g. https://github.com/opengapps/opengapps/wiki/Stock-Package and search for "replaces", you'll see what is replaced in the system partition. The more obvious drawbacks are, that if you install stock opengapps e.g. the rom shipped webview is gone (in opposite to installing chrome webview from playstore, which let you choose at runtime which webview should be used - this also goes for launcher, telephone app, email, contacts, etc).
Even worse (and much less obvious) is the point, that if you install an app with own libs (*.so) and c-bindings (*.jni) from playstore they are installed within the app and are used only in the app's sessions. If you use the same app from the gapps flashable zip, those libs and bindings are installed outside the app dir in the system partition replacing their rom shipped counterparts: all services and apps - even the rom shipped services and apps - need to use the ones from the gapps package. The rom is massively changed in a way not controlable (and not supportable) by the rom dev.
A last word of warning: never ever downgrade a gapps package (e.g. from stock to nano) and install the missing apps from playstore. The gapps db entries for a system gapp (flashable zip) are different from user gapp (playstore install). Upgrading from e.g. nano to stock (not recommended; see above!!!) will work, iff all stock contained apps are uninstalled before the upgrade.
Again this doesn't mean bit apps is supiror to opengapps or vice versa. It just means the nightly/daily updates arn't an advantage by it's own. You are always safe as long as you know what you are doing; this includes to check exactly what each package installs and replaces. Obviously it doesn't make any sense to complain about e.g. laggy webview in the rom's thtead when using opengapps stock package.
nvertigo67 said:
stuff
Click to expand...
Click to collapse
1st. Thx downloading now. Is this ROM optimized for 3/3T or 3T only ?
Some screenshots would be greatly appreciated.
'
Thx Dev
Ayy! That was quick. Time to flashhhh!
As long as the dark theme works, no reason to switch back to Oreo. Bye bye bad recents menu xD
Edit: since you tagged me for debugging OP lol..
Might want to change the cmxlog link to LOS 16.
And first time flashing instructions says NLOS 15 instead of 16.
If 16 is already on feature parity with 15, then I'll be pretty amazed lol.
So how should we update from nlos 15.1 to 16? Dirty flash gonna work?
Edit, dirty flashed nlos 16 over 15.1 and pico gapps then magisk.
Works
Yay! Finally. Gonna flash soon
There's a few minor issues as expected from a first alpha. FC's on apps like the inbuilt sounds app and the Android setup app for the first time after a gapps flash. Everything works fine after that one FC on the setup app, although the sounds app still doesn't work. Lots of duplicate sounds in the notification sounds section. Some oddities like using the notification sound as the charging sound by default, although I guess that isn't a bug. All major LOS features that I used on Oreo seem to be working fine on Pie. There's an issues with the slider settings logic when you use priority only; it never exits that muted mode when you switch back to none. As for NLOS features, substratum doesn't seem to be working for me, is the OMS service mode already in? I denied root and got this screen.
Complete clean flash without gapps to test, and then another clean flash with opengapps nano and magisk to set everything up. Only 4 apps from Oreo restored via titanium backup to Pie. They all seem to work so hopefully doing that isn't a problem? (All 3 chrome builds had open tabs so I didn't want to install them from scratch or I'd lose the tabs. And Pulse, my SMS app has my chat history so I restored that too. Others I clean installed.)
Pie has so many small cool UI additions. From text editing to call UI to volume slider UI. Oh and the buttery smooth animations.... I'm not sure which features are part of AOSP Pie and which ones are LOS features at this point haha.
Performance, battery, stability, all seem great till now.
Also looking for a new gallery app. Any recommendations?
Edit: audio ducking behavior on notifications is also different. Notifications completely stop any other audio. I can't figure out how to change that behavior.
IDK if it's a pie or LOS feature but the settings app has a black theme for the system, so I'm happy. Should I use root for substratum if OMS isn't in yet, or is OMS in and that's a bug?
Thanks for the excellent ROM! I just installed it, and it seems to be working fairly well for me, but I did run into a few issues:
- the OOBE crashed several times, although it eventually managed to get to the end
- the Swift Dark installed failed to install any themes at all
- I get a notification from org.codeauora.ims saying that "SIM 1 is HD capable", but all options to turn it off are disabled
- I had issues getting FDE working, and documented the process I used to get it fixed in the android stackexchange, at a question titled "Device encryption fails, gives no error and just restarts" (won't let me post links). This issue was something you already briefly covered in the first post.
Otherwise, I'm super happy with 16.0, it feels great, and I haven't run into any bugs that make it unusable.
kash_si said:
1st. Thx downloading now. Is this ROM optimized for 3/3T or 3T only ?
Some screenshots would be greatly appreciated.
'
Thx Dev
Click to expand...
Click to collapse
Works for both devices. Blobs (especially cam blobs and carrier mbns) are taken from 3t OOS image.
Looks like los. My imtend is not to have some graphical chamges, but to enpower the users to make this "their" rom.
Themes, microg or gapps... The "out of the box"-look is the same as los.
Sadly I can't get substratum service mode working, currently, so you need root, but with the additional exposures and Magisk pie ready themes work like charme.
( @knpk13: you need root currently for substratum)
64ashg said:
So how should we update from nlos 15.1 to 16? Dirty flash gonna work?
Edit, dirty flashed nlos 16 over 15.1 and pico gapps then magisk.
Works
Click to expand...
Click to collapse
The standard rules of thumb apply:
If you dirty flash with no issues, you are fine. If issues show up: clean flash!
Whenever you wonder if it's time for a clean flash: the answer is yes.
knpk13 said:
There's a few minor issues as expected from a first alpha. FC's on apps like the inbuilt sounds app and the Android setup app for the first time after a gapps flash.
Click to expand...
Click to collapse
I had two fcs from setupwizard during first time setup - I just redid my inputs and it went through: no reflashing, no reboot.
org.lineage.eleven (shows as "Music" in app drawer) is working (flac fix is missing - will be in the next update, I've missed that one) as well as org.lineage.audiofx. Or do you mean an other sound app?
knpk13 said:
Lots of duplicate sounds in the notification sounds section.
Click to expand...
Click to collapse
Not for me. Perhaps you have /sdcard/Alarms and/or /sdcard/Notifications filled with same named audio files?
knpk13 said:
There's an issues with the slider settings logic when you use priority only; it never exits that muted mode when you switch back to none.
Click to expand...
Click to collapse
I have that only for Alarms. If I set bottom to none, and Middle AND Top both to priority it works like intended. I'm planing to keep priority but rename it to dnd and use Alarm as vibrate mode. The slider logic definetly needs some work.
knpk13 said:
As for NLOS features, substratum doesn't seem to be working for me, is the OMS service mode already in? I denied root and got this screen.
Click to expand...
Click to collapse
See the thread's subject and the OP:
nvertigo67 said:
Hopefully soon: NLOS features OMS Service Mode - the successor of ThemeInterfacer. This means you don't need root and/or andromeda to have full Substratum Theming! It's faster then andromeda and does not rely on a tethered pc-connection. It has more exposueres (items exposed to the themers) then the rooted solution. If substratum should ask for root previlegs, deny it. All exposures are allready implemented.
Click to expand...
Click to collapse
knpk13 said:
Complete clean flash without gapps to test, and then another clean flash with opengapps nano and magisk to set everything up. Only 4 apps from Oreo restored via titanium backup to Pie. They all seem to work so hopefully doing that isn't a problem? (All 3 chrome builds had open tabs so I didn't want to install them from scratch or I'd lose the tabs. And Pulse, my SMS app has my chat history so I restored that too. Others I clean installed.)
Click to expand...
Click to collapse
If you have no issue, you have no issue - if you have issues, you have issues... Time will show, I guess...
knpk13 said:
Edit: audio ducking behavior on notifications is also different. Notifications completely stop any other audio. I can't figure out how to change that behavior.
Click to expand...
Click to collapse
No clue - not even sure, if it's intended or not.
aOa0LU said:
Thanks for the excellent ROM! I just installed it, and it seems to be working fairly well for me, but I did run into a few issues:
- the OOBE crashed several times, although it eventually managed to get to the end
- the Swift Dark installed failed to install any themes at all
- I get a notification from org.codeauora.ims saying that "SIM 1 is HD capable", but all options to turn it off are disabled
- I had issues getting FDE working, and documented the process I used to get it fixed in the android stackexchange, at a question titled "Device encryption fails, gives no error and just restarts" (won't let me post links). This issue was something you already briefly covered in the first post.
Otherwise, I'm super happy with 16.0, it feels great, and I haven't run into any bugs that make it unusable.
Click to expand...
Click to collapse
I have no clue what OOBE is.
How do you install swift dark? It's my main testing them and works great, installed from sunstratum follwing swift dark's directions to the point (secomd reboot not necessary).
For the annoying hd notification we need to wait for an upstream fix. I don't expirience that, so not much I can do about.
FDE is working out of the box. Since data is encrypted on my device, I wouldn't be able to boot... ???
For the link: just use host.domain.top/some/where instead of https://host.domain.top/some/where .
nvertigo67 said:
Sadly I can't get substratum service mode working, currently, so you need root, but with the additional exposures and Magisk pie ready themes work like charme.
( @knpk13: you need root currently for substratum)
I had two fcs from setupwizard during first time setup - I just redid my inputs and it went through: no reflashing, no reboot.
org.lineage.eleven (shows as "Music" in app drawer) is working (flac fix is missing - will be in the next update, I've missed that one) as well as org.lineage.audiofx. Or do you mean an other sound app?
Not for me. Perhaps you have /sdcard/Alarms and/or /sdcard/Notifications filled with same named audio files?
Click to expand...
Click to collapse
Additional exposures? Ooh it installs a magisk module. Guess I need to reboot every time to apply themes. Unfortunate. Well at least it's all black now haha. Funny thing is in P, I find the spacing of notifications to be quite large. The P-ify module on O was more compact and nice, better than original P lol. Maybe there's way to change it, or I'll just get used to it. Everything else seems great.
This sounds app in the screenshot. I tried to change my ringtone and it asked me to pick between media storage and sounds. Media storage works, sounds crashes.
I don't have any audio files in the alarms or notifications folders. Only the inbuilt LOS sounds. Here's one example of a duplicate, Platinum.
So I shouldn't be worried about the setup wizard FC's? I had only one FC.
yes !! hope it gets stable as 15.1 or even better.. any screens ??
Last question before update from nlos 15. Does call recording feature works out of the box?
I have the network speed indicator at a slight offset. Is anybody else having this problem?
The first screenshot is of the default settings, and the next one is of me having the display size small and font large.
I dirty flashed over nlos 15.1 so anyone with the same experience. Or clean flashers, having this issue. I remember someone having this problem in the los16 beta thread.
Thanks in advance
64ashg said:
I have the network speed indicator at a slight offset. Is anybody else having this problem?
Click to expand...
Click to collapse
All the reports in the LOS 16 thread say it doesn't work at all. The feature seems to work for me on NLOS 16 (I don't use it, just downloaded an app to check if the monitor showed any info) and this is the position I get on a clean flash.
Related
Wakelock+Alarm _Blocker & DozeEditor patch: Official2017 CM14(Lineage), CM13/12/11
Wakelock Blocker for Official 2016, Nightly CM11
All thanks to
@faust93 : BASE.diff http://review.cyanogenmod.org/#/c/109898/ SETTINGS.diff http://review.cyanogenmod.org/#/c/109897/ (official rejections for CM12)
@scott.hart.bti (Beanstalk_base) @Cristiano Matos (crDroid_settings) for Github sources.
If you fell donate then it should be to @maxwen, which seems to be the real ghost creator of wakelockblocker (Nov 2013) https://github.com/scotthartbti/and...mmit/2022015c1d7890873c54e7290ec0ca1391c6dc50
While mixing all this (cherry-picked from github) together, I finally succeed a 2x patch diff
to implement a working Wakelock Blocker in cm-11-2016xxx-NIGHTLY under Parameter/Performance/System.
I check the efficiency OK, on LGp880 & ASUStf700t with @chamonix' BetterBatteryStats.
The base diff includes inverted broken xposed & SELinuxModeChanger from zygote d8130142.diff http://review.cyanogenmod.org/#/c/118800/
There were 19 devices + 27 samsung on official 2016 KK nightly run, I hope some will patch theses 2 diff WITH 100% compatible:
- mar-V-in fake signature for nogapp microG https://github.com/microg/android_p...r/patches/android_frameworks_base-KK-LP.patch
That edition will keep same CVE as the official one and will stay untouched apart +3 above.
If you are baking a KK cm11-based rom , it should also be compatible. You tell me.
Lineage14.1 CM13 & CM12 patches 2017
CM12.1 2016 WakelockBlocker and microG : post12 / attached .diff
*(Omni's double patch microG option-able on/off re-hunked for CM12.1.1 : post14 / attached .diff)
CM13 2017 Wakelock+Alarm _Blocker and microG : post19 / 1&2) attached .diff
CM14 DozeSettingsEditor : post19 / 3) attached .diff
Caution & Warnings*
Caution: blocking critical wakelocks can lead to bootloop; so always proceed full backup from recovery before unknown tries.
Also, be aware that if you over-flash original cm (without WakelockBlockers), your rom will work as new ota (without bootloops); but if you flash again modified cm with WakelockBlockers, you will find back your precedent settings on ticked wakelocks.
Warnings: before sharing logs with other, ensure that your log does not include some personal data under blocked wakelocks' description; ex: xxx @ gmail.com ...
Code:
packages/apps/Settings/src/com/android/settings/applications/WakeLockBlocker.java
...Log.d("maxwen", pm.getSeenWakeLocks());
(nota: there are no analytics or any network exchanges on your blocked wakelock list; conversely WakelockBlocker can definitively help to stop such intrusive behaviours.)
wip
How does it work
How to 2x your battery
The equation is simple 2xbattery=50%=20%a+20%b+10%c:
a) 20% thank to @MaR-V-iN for microG project ie nogapps
Not only the multiple google packages are pinging together, but the worse is the auto-updating ghost process (which sometimes leads in automatic battery drain due to obligatory “linux-reboot-post-validation-like").
Also, the use of your personal data stay unclear.
Thanks to @Bonoboo there are >100 gapp_pkg in MM
With original KK (3years ago) it was >60 gapp_pkg.
Of course microG won’t bring you all the fancy and amazing usages, but it should cover all your basic exigencies with privacy.
b) 20% thank to CyanogenMod’superuser (root)
DATA/LOCAL/userinit.sh (persistent to ota):
rm /dev/log/*;
rm /data/tombstones/*;
sysctl -w vm.dirty_writeback_centisecs=2000;
sysctl -w vm.dirty_expire_centisecs=1000;
Then using Greenify + f-droid : Adaway Autostarts FasterGPS will finalize an equivalent snappy ‘interactive’ on a ‘conservative’ frugal mode (cpu scaling_governor).
c)10% miscellaneous tips
SETTINGS/WIFI/MENU/ADVANCED: switch always to never
LAUNCHER : Smart Launcher (for phones) or craziest TinyLaunch from @arpruss (for tablet)
PRIVATE BROWSING : internal cm-made
FAST BROWSING 3G : Uc browser mini
GENERAL BROWSING wifi : Dolphin + Jetpack + Companion (Jetpack will supply missing Lollipop’s live webview on KK & Companion will bring WOT and trigger to reduce freeze) with option ‘open in new Tab’ to avoid excessive back-reload pages.
Try to avoid DLNA activity in background and track, with BetterBatteryStats, unnecessary wakelocks (once done you can greenify or disable it).
For more security, cm11 is fully compatible with these xposed modules: AppSettings, DirectApkInstall, Greenify, LightningWall, XposedMediaScanner and XposedRecentTasksRAM.
What's next
Once upgraded with these 2 transparency in-core modifications: microG & WakelockBlocker, privacy setup, on cm11, is OK.
Thanks to @noname81 no one is missing pie to use a phone/tablet easily: LMT Launcher (it’s funny to see many OEM copying Huawei for the mini-screen and they will discover pie...).
But a fundamental functionality is still missing for all ROMs: a basic sound mix table per apk. I can’t believe that Google Inc. did not make that already, (they must wait for a world marketing hit).
In simple words: play music or phone with relatives while watching TV or youtube… (for real!). I guess, once again, it’s question to DRM’s duty (you watch => you listen). Maybe, one day VLC will catch this in an all-in-one solution.
Does java, using stream.hasvideo Boolean attribute, in the right place, can dress a list to duck or mute /apk ?
This is the thread’s poll, since AppSettings is too far from the android core ?
If you want to get first similar rom, without unofficial build, you can follow these instructions (custom recovery is strongly recommended!):
Check whole thread http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895/page12 to reverse zygote(2015 Nov 8);
download Xposed version >=2.6.1. via the in-app updater or from http://dl.xposed.info/latest.apk and
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Once you install/reboot the framework you should get a green 58/54 for xposed/framework.
For wakelock control, use @t2k269
http://repo.xposed.info/module/org.t2k269.perapphacking
If you block to many things and face bootloop just proceed (with caution!) :
reboot in recovery go to twrp menu/advanced/file manager /data/app and select org.t2k269.perapphacking__.apk for delete then once reboot successful finishes, re-install perapphacking and uncheck your last moves.
For @MaR-V-iN microG, use
https://github.com/thermatk/FakeGApps/releases
and enjoy FLOSS atmosphere:
http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
http://forum.xda-developers.com/showthread.php?t=1715375
If you find this useful, then flash :
MapsApi https://github.com/mar-v-in/MapsAPI/releases/download/v0.5/mapsapi.flashable.zip
Freecygn http://forum.xda-developers.com/showthread.php?t=2550769
Be sure to respect modular CyanogenMod’ “alternativity”, and to understand http://www.xda-developers.com/remove-the-google-from-cyanogenmod-with-freecygn/
My patches for CM11:
1) Add fake sign functionality (from OmniROM)
2) Add Wakelock Blocker (from this thread)
Dalvik still alive: cm-11-20160612-NIGHTLY
remittor said:
My patches for CM11:
1) Add fake sign functionality (from OmniROM)
2) Add Wakelock Blocker (from this thread)
Click to expand...
Click to collapse
Cool...
For end users, I will be glad, if some can report a checked OK with BetterBatteryStats_2.1.0.0 (/partial wakelock) or Wakekock Detector(/cpu wakelock) with their device_name, in this thread.
Thanks in advance, and re-joy your battery & privacy.
oF2pks said:
There are >550 gapp_pkg in MM
With original KK (3years ago) it was >60 gapp_pkg.
Click to expand...
Click to collapse
Just a note: it's not correct to count lines in my script for deleting gapps.
It contain a lot duplicates that cover different names / locations of APK's. Plus .odex and .lib files.
In nature there are ~100 real apps from Google, checked by parsing script.
Correction updated
Bonoboo said:
In nature there are ~100 real apps from Google, checked by parsing script.
Click to expand...
Click to collapse
Post' quote updated to 100 for MM; many thanks for that evaluation. Your work help many people moving to microG.
btw: it would be amazing to automate adDetector on Google packages; actually system webview is exception to the rule: no noisy addons or permissions.
2015-3636 Pingpong root
If VTS return:
2015-3636 Pingpong root
https://github.com/torvalds/linux/commit/a134f083e79fb4c3d0a925691e732c56911b4326
grab this
Code:
diff --git a/net/ipv4/ping.c b/net/ipv4/ping.c
index 39b403f..46f8f3f 100644
--- a/net/ipv4/ping.c
+++ b/net/ipv4/ping.c
@@ -138,6 +138,7 @@ static void ping_v4_unhash(struct sock *sk)
if (sk_hashed(sk)) {
write_lock_bh(&ping_table.lock);
hlist_nulls_del(&sk->sk_nulls_node);
+ sk_nulls_node_init(&sk->sk_nulls_node);
sock_put(sk);
isk->inet_num = isk->inet_sport = 0;
sock_prot_inuse_add(sock_net(sk), sk->sk_prot, -1);
Source github
Tested-by: Linus Torvalds <[email protected]>
Reported-by: Wen Xu <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Nota: for 2014-3153 Futex looks to be hand-made/device; for 2013-6282 Aurora PM me for it(T<->TUSER).
Common Vulnerability and Exposures (CVE) June 2016 CM11
Except the misses related to old kernels (<3.4), like 3.1.10; ALL Nexus Security Bulletins are included in latest nightly 2016-06-12.
For cve-2015-6616, since KK doesn't have decoder/ih264d_parse_headers.c, vts returns red for ANDROID-24157524 Critical 6.0 only Sep 08, 2015:
https://github.com/AndroidVTS/android-vts/issues/129
https://android.googlesource.com/platform/external/libavc/+/2ee0c1bced131ffb06d1b430b08a202cd3a52005
All other CVE-2015-6616 related bugs are patched
ANDROID-24630158 Critical 6.0 and below Google Internal
ANDROID-23882800 Critical 6.0 and below Google Internal
ANDROID-17769851 Critical 5.1 and below Google Internal
ANDROID-24441553 Critical 6.0 and below Sep 22, 2015
Many thanks to CM11' team: security with 'alternativity'....
Caution & Warnings
Caution: blocking critical wakelocks can lead to bootloop; so always proceed full backup from recovery before unknown tries.
Also, be aware that if you over-flash original cm (without WakelockBlockers), your rom will work as new ota (without bootloops); but if you flash again modified cm with WakelockBlockers, you will find back your precedent settings on ticked wakelocks.
Warnings: before sharing logs with other, ensure that your log does not include some personal data under blocked wakelocks' description; ex: xxx @ gmail.com ...
(nota: there are no analytics or any network exchanges on your blocked wakelock list; conversely WakelockBlocker can definitively help to stop such intrusive behaviours.)
CM12.1 20160710 bandwagon WakelockBlocker and microG
Attached are base.diff & settings.diff re-hunked lifted WakelockBlocker' patches for latest cm12; source:
http://review.cyanogenmod.org/#/c/109898/
http://review.cyanogenmod.org/#/c/109897/
When home-building cm12-20160710 you will probably need:
-- media/libstagefright/data/media_codecs_ffmpeg.xml
-m kernel/timeconst.pl
-- /prebuilts/gcc/linux-x86/arm/arm-eabi-4.7 symlink to arm-eabi-4.8.
I check OK mar-V-in fake signature for nogapp microG: single patch https://github.com/microg/android_p...r/patches/android_frameworks_base-KK-LP.patch
Once patched, run make update-api (following the CM's quail first build) and re-build: check attached re-hunked gitdiffHEAD_frameworks_baseCURRENTXmicroG.txt.
Hope @MaR-V-iN and @faust93 won't see offence.
WakelockBlocker's option is located in Developer Options before Process Stats.
Nota: will upload soon Omni's double patch microG option-able re-hunked for CM12.
WakelockBlocker and FakeSing patches for CM12.1
Link: https://github.com/jsr-d10/android_device_jsr_d10f/commits/cm-12.1/patches (see commits for 2016-06-12)
Omni's double patch microG option-able on/off re-hunked for CM12.1.1
CM12.1 is moving to CM12.1.1 : https://www.cmxlog.com/12.1/grouper/ (with changes to PackageManagerService.java : https://review.cyanogenmod.org/#/c/155579)
Attached are microG option-able re-hunked for CM12.1.1 (from Omnirom)
Option on/off is under Developer_options
Single original patch : https://github.com/microg/android_p...r/patches/android_frameworks_base-KK-LP.patch
Hope @MaR-V-iN won't see offence.
Nota: check post 13 for included Russian strings.
CM13 WakelockBlocker and microG 2016/2017
Attached are base.diff & settings.diff re-hunked lifted WakelockBlocker' patches for latest cm13; source:
base/bs6 : https://github.com/scotthartbti/and...mmit/5fb687ae0940a12c8f7c9e457b6d5f12f028736b
settings/cm12 : http://review.cyanogenmod.org/#/c/109897/
MaR-V-iN' fake signature for nogapp microG: single patch https://github.com/microg/android_p...aster/patches/android_frameworks_base-M.patch
Any love planned for nougat?
HaoZeke said:
Any love planned for nougat?
Click to expand...
Click to collapse
Remember that on KK, all the app were triggering wakelocks , so it was very useful to "break" intrusive or non-frugal ones with WakelockBlocker.
On LP, only very aggressive app are intrusive (like UCbrowser or GoogleNews&Weather)
On MM&N with doze (& Greenify), WakelockBlocker is almost useless but can still prevent intrusions or infections.
So actually on Nougat(, even if this add-on gives informative true list of all wakelocks triggered once), this didn't show up yet, but Beanstalk has always been favourite for mods...
CM13 2017 cve patches
Thx to @Sultanxda you can grab cm13 cve patches : https://github.com/sultanxda/patcher/tree/stable/cm-13.0-oneplus3/ZNH5Y/security
HaoZeke said:
Any love planned for nougat?
Click to expand...
Click to collapse
I don't have nougat on my devices, but the "hardest" seems already done:
https://github.com/crdroidandroid/a...android/server/power/PowerManagerService.java
https://github.com/ResurrectionRemi...android/server/power/PowerManagerService.java
CM13 Wakelock+Alarm _Blocker and microG 2017 / CM14 DozeSettingsEditor
For latest cm13, attached are base.diff & settings.diff re-hunked lifted Wakelock+Alarm _Blocker' patches, with MicroG, from
BASE :
Wakelock : https://github.com/scotthartbti/and...mmit/5fb687ae0940a12c8f7c9e457b6d5f12f028736b
Alarm https://github.com/ResurrectionRemi...mmit/0ed31d619a0ed418ba129039f65de6487e45bfc5
SETTINGS :
Wakelock https://github.com/ResurrectionRemi...mmit/6d4080e7b3477adae21c7181f0801f544cfef7de
Alarm https://github.com/ResurrectionRemi...mmit/7109caa4848f99d5a7daadad66158bd4c83da3e3
MaR-V-iN' fake signature for nogapp microG: single patch https://github.com/microg/android_p...aster/patches/android_frameworks_base-M.patch
For CM14.1 attached is settings.diff re-hunked lifted DozeSettingsEditor, from https://github.com/omnirom/android_...mmit/6206ccdfa4aee098713dd0b999f3e42b327278f2
(base.diff & settings.diff re-hunked lifted Wakelock+Alarm _Blocker' patches, with MicroG, for latest cm14.1 are coming soon with light modification for Nougat new metric logger.)
thank you for support xz1 community
do this rom included the wakelock blocker ? or i have to install zip patch
NLOS is an unofficial 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.
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.
My priorities are stabillity, battery, performance - in that order. This build is optimized for oneplus3t - it will flash and run on a oneplus3, because it's an unified build, but it's optimized for 3t!
In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch, ported to Oreo) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps).
NLOS doesn't require any mods to work with @Arnova8G2's GoogleCamera Mod (more details in S4turno's thread ). Just install the modded Gcam - no need to flash twrp-front-fix-oreo-op3-3t.zip, nor to use the magisk module.
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.
NLOS features OMS Service Mode - the successor of ThemeInterfacer. This means you don't need root and/or andromeda to have full Substratum Theming! It's faster then andromeda and does not rely on a tethered pc-connection. It has more exposueres (items exposed to the themers) then the rooted solution. If substratum should ask for root previlegs, deny it.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://forum.xda-developers.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://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty 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 Unofficial LineageOS 15.1 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 15.1 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 current MindTheGapps for arm64. If you insist on using gapps, don't use a package larger then nano.
Download and flash twrp-3.2.3-0!
Download and flash latest OxygenOS Oreo firmware.
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 are insisting to use f2fs see: https://forum.xda-developers.com/on...1-20180223-t3754855/post75688089#post75688089 - NOT recommended!
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.cmxlog.com/15.1/
Build 20190208
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
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.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 8 Feb 2019, 14:09:19 CET / 8 Feb 2019, 13:09:19 UTC):
Merge tag 'v3.18.134' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
ARM: dts: msm: FIxup GPU 0mhz clock — Nvertigo
drivers: video: mdss: Fix direct references to HZ — celtare21
drivers: ipa: Fix direct references to HZ — Humberto Borba
drivers: platform: gsi: Fix direct references to HZ — Humberto Borba
drivers: hwmon: Fix direct references to HZ — Humberto Borba
drivers: i2c: Fix direct references to HZ — Humberto Borba
Convert few critical drivers to use msecs_to_jiffies insted of HZ — Dorimanx
msm: kgsl: Remove POPP — Sultan Alsawaf
current.pick.sh: O_asb_2019-02. — Nvertigo
current.pick.sh: introduce a safer repopick. — Nvertigo
op3/t: nfc: advertise support for extended length NFC — Paul Keith
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
History
Build 20190127
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
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.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 27 Jan 2019, 13:01:40 CET / 27 Jan 2019, 12:01:40 UTC):
current.pick.sh: force picking abandoned battery customisation commits (220407, 220422, 219299) — Nvertigo
op3: Restore better load balancing after boot — Thomas Shum
WG: squash WireGuard-0.0.20190123. — Nvertigo
Merge tag 'v3.18.133' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — 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!
Firmware
NVertigo's Oxygen Firmware Archive
TWRP
Latest official twrp
Thread for official twrp
Google Apps:
MindTheGapps-8.1.0-arm64-20180223_195845.zip
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/nlos-15.1 (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.
...and everybody I forgot.
Happy flashing!
XDA:DevDB Information
NLOS-15.1, ROM for the OnePlus 3
Contributors
nvertigo67, dianlujitao
Source Code: https://github.com/nvertigo/local_manifest/tree/nlos-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: latest
Based On: LineageOS 15.1
Version Information
Status: Stable
Created 2018-12-04
Last Updated 2018-12-04
Known Issues
fixed: NLOS can't initially encrypt f2fs data partitions (though ext4 is working flawlessly).
fixed: NLOS can't change the encryption passphrase for f2fs/ext4 data partitions (though ext4 is working flawlessly).
fixed: adb and mtp doesn't work out of the box. Workaround:
put in QS-tile "adb over network"
disable wifi
enable "adb over network" with the added tile (tile shows 0.0.0.0)
connect usb cable
an expandable notification shows up
expand it, tap it and select "file transfer": voila.
If you've run through the above adb and mtp are working fine - even trough reboots... automagicaly...
If secure boot password, pin or pattern is set: LiveDisplay's Settings show color profile as "Standrad" after a reboot, though the configuered LiveDisplay's color profile is correctly aplied.
Notification lights have hickups.
fixed: With no substratum themes applied and dark mode enabled the qs edit page is in stealth mode (white text on white background). For reference see: https://forum.xda-developers.com/ap...um-support-t3606400/post76619564#post76619564
Where has "keep wifi on during sleep"?
Sadly this isn't working anymore.
The maker of betterbatterystats offers also a tool to accomblish this task and much more:
betterwifionoff
When switching from lineage-14.1 to lineage-15.1 I found idle bat usage doubled: what has been 0.4 % per hour on nougat increased on oreo to 0.8 to 1.0 % per hour.
On n I've always used "only if charging" for "keep wifi on during sleep", but the access to this setting has been vanished by google. So I exprimented with wifi conf file, kernel driver and wakelock blocking on kernel level. Nothing really solved the adsitional idle drain.
I'm still surprised, what I found while searching settings (cli): the setting "wifi_sleep_policy" is still there! Google has just droped the access via Settings->Network&Internet->Wi-Fi and makes "Always" the default , but the setting is still available and is working like on n.
Value: Function
0: Never
1: only when plugged in
2: Always
To get restore my n setting (keep wifi on while sleep only when plugged in), I only need to connect via adb (I prefer adb over network, but it works as well with usb), and issue this command:
Code:
adb shell settings put global wifi_sleep_policy 1
After spending endless hours on kernel and debugging, this simple command brought back 0.4%/h idle bat usage.
How To: format data with f2fs with current official TWRP
Current twrp (3.2.1-0) can't change the data fs to f2fs. The reason for this breakage is, that twrp expects a mkfs.f2fs command that knows "-r size" as cli-option, but the image is shipped with a version that doesn't know about "-r".
To get data formated as f2fs with space for the encryption footer, you just need to follow these simple steps:
Download attached mkfs-f2fs.zip.
Unzip and place the contained mkfs.f2fs in /sdcard/Download.
Boot to current twrp-3.2.1-0.
In twrp:
Home-Screen->Advanced->Terminal
Code:
cp -vi /sdcard/Download/mkfs.f2fs /tmp
chmod 0755 /tmp/mkfs.f2fs
/tmp/mkfs.f2fs -t 0 -r 16384 /dev/block/bootdevice/by-name/userdata #for the lazy, if on op3/t can use /dev/block/sda15
flash rom (or use the installed rom, which is factory reseted by formating data), reboot t system amd encrypt your device.
The mkfs.f2fs binary is taken from the original twrp-3.2.1-0. This will only work for 64-bit devices:
Code:
file mkfs.f2fs
mkfs.f2fs: ELF 64-bit LSB pie executable ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /sbin/linker64, BuildID[md5/uuid]=46b5f32d88973c91f79744258599a19a, stripped
stuff.
UPDATE
Build 20180225
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta03 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
Update GoogleCamera to GoogleCamera-Pixel2Mod-Arnova8G2-V6.apk — Nvertigo
Bring back busybox. — Nvertigo
Switch kernel branch to linux-stable/nlos-15.1. — Nvertigo
Merge tag 'v3.18.96' into linux-stable/merge-15.1 — 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!
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.
With the version from 18th February the setup wizard is working, if you are going for a fresh installation.
vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
crian said:
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.
Click to expand...
Click to collapse
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).
nvertigo67 said:
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).
Click to expand...
Click to collapse
Will this work on op3 too?
Aasresh said:
Will this work on op3 too?
Click to expand...
Click to collapse
Most propably: yes.
I don't have my hands on a 3, and I made it my self a rule to only build and push for devices I have my hands on. That's why I stay in 3t forum though it's essentially an unified build. On the other hand: whenever a setting can be tuned for either for sd820 or sd821, I go for sd821. Other then that, NLOS should work on both models, and I try my best to give you support here.
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
Nope
doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.
OMS service mode
TheGatorade said:
Can't wait for rootless OMS patch
This rom looking good, surprisingly stable for a beta
Click to expand...
Click to collapse
Stay tuned. Need to cleanup the sources and make a clean build.
nvertigo67 said:
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.
Click to expand...
Click to collapse
Gotcha. Good to know that plain LOS is just as good with battery life. Thank you
For people having trouble with gapps try flashing the rom then complete the setup wizard then flash gapps.
Worked for me.
UPDATE (OMS Service Mode)
Build 20180226
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta04 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
OMS Service Mode is still work in progress. Sometimes you need to activate a theme once again after "compile&activate". Some themes (i.e. flux - though it's working flawlessly) refuses to deactivate, but flashing /sdcard/substratum/SubstratumRescue.zip removes all activated overlays. Rebooting is sometimes neccessary. Wiping caches and dalvik may be a good idea, too. SwiftDark and Flux seem to work otherwise.
Special thanx to @danieldmm for helping me out of my brainlock with pointing me to https://substratum.review/ . Without his help I would be still searching for commits currently not meeged... ...that would have taken looooong.... *lol*
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
OMS Service Mode: https://substratum.review/#/q/branch:o+(status:merged+OR+status:open) and https://github.com/nvertigo/android_frameworks_base/commit/e5cc87691ea4ba482914adee36821243fe39f7b4
op3: Use exfat-nofuse — dianlujitao
Merge remote-tracking branch 'lneageos/lineage-15.1' into linux-stable/merge-15.1 — 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!
EDIT:
HOTFIX:
Set sepolicy temporary to permissive, if you want to deactivate an overlay.
Dirty flashed nlos-15.1 20180226 over 20180225 cause some bugs.
Op3T boots but few seconds after the screen becomes black and the phone reboot to recovery.
Revert to 20180225.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 17.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 17.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Changelog:
2019.10.24
Initial release
2019.10.25
Sync latest source
Fix bluetooth
2019.11.20
Sync latest source
Fix wifi display
Ship Snap
Fix vulkan graphics
Pass safetynet
Fix crash of some native services
2019.12.31
Sync latest source
SELiunx working in enforcing mode now
Update kernel to LA.UM.8.6.r1-02900-89xx.0
Update blobs from OOS 9.0.6
Fix suspend when AOD is on
Happy new year!
2020.1.12
Sync latest source
Fix ril of the last build
Update blobs from LA.UM.8.6.r1-02900-89xx.0
Add backuptools
Other trivial fixes
2020.4.2
Official nightlies started
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: Android 10
Version Information
Status: Nightly
Created 2019-10-24
Last Updated 2020-06-26
Any recommendations which gapps to use?
Why not the official ones? https://sourceforge.net/projects/opengapps/files/arm64/beta/20191006/
is this with kernel 4.4?
helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
https://github.com/LineageOS/android_kernel_oneplus_msm8996/blob/lineage-17.0/Makefile#L1-L3
helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
dianlujitao said:
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T.
Click to expand...
Click to collapse
OP needs some changes its for LOS 17 instead of 16 [emoji3][emoji39]
Sent from my ONEPLUS A3003 using Tapatalk
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Master_TC said:
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
Click to expand...
Click to collapse
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
mady51 said:
ya i built it once but it didn't booted. after that didn't spent time on it. may be ill give it another try soon
Click to expand...
Click to collapse
Anyway amazing work @dianlujitao you're one of our heroes ???
Viper The Ripper said:
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
Anyway amazing work @dianlujitao you're one of our heroes ???
Click to expand...
Click to collapse
https://github.com/dianlujitao/android_kernel_oneplus_msm8996 @dianlujitao did bring up a 4.4 kernel but it has issues.
Jus asked because of this
mvalda01 said:
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Click to expand...
Click to collapse
Can you provide more info such as logs, my aptx headset works fine here.
Thanks for the effort,nice rom for nice phone.
From Op3 owner
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the report, bluetooth should be fixed in 1025 build, for Digital Wellbeing crash you should probably report to opengapps devs, I'm not sure.
NFC works fine for me, it wound be nice if you could grab related logs.
Well done @dianlujitao!
Thanks for your work @dianlujitao! I'll probably flash next build
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
MJPollard said:
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
Click to expand...
Click to collapse
You need to pick - at least - https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/255737 from https://review.lineageos.org/q/project:LineageOS%2Fandroid_device_oneplus_oneplus3+status:open, maybe all.
There's a good reason why OP calls it an experimental build instead of alpha or beta... Rebuilding experimental needs skilld and patience...
EDIT:
For the blobs commits (i.e. https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/260573 and https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/262330) see also https://github.com/dianlujitao/proprietary_vendor_oneplus/commits/lineage-17.0 .
BillGoss said:
- Digital Wellbeing keeps stopping (logs attached)
Click to expand...
Click to collapse
On some other Android 10 ROM, force stopping, disabling and then re-enabling solved this issue.
This thread is deprecated - please refer to its LineageOS 18.1 successor thread
This thread is dedicated to provide hardened Lineage-OS 17.1 builds with microG included for the OnePlus 3/3T with current security patches.
It is the successor of my Lineage 16.0 thread.
It may be worth to also look there, if you are looking for information.
Features of this ROM
Download here
Pre-installed microG and F-Droid like LineageOS for microG project (own fork)
Pre-installed AuroraStore
OTA Support
eSpeakTTS engine
Bromite as default browser
Additional security hardening features listed below
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Kernel kept up to date with ASB patches and Google kernel/common 'android-3.18' branch
Debloated from Oneplus blobs for Alipay, WeChatpay, Soter and IFAA
Hardened bionic lib and constified JNI method tables
Current release levels
Security string: 2021-10-05
AOSP tag: 10.0.0_r41
Bromite System Webview: M93
Source-code and build instructions
Kernel: https://github.com/lin17-microg/android_kernel_oneplus_msm8996/tree/lin-17.1-mse3
Build manifest: https://github.com/lin17-microg/local_manifests/tree/lin-17.1-microG
Installation Instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty of information available.
Pre-Requisites
If you come from OxygenOS Stock ROM, make sure to update to the latest offered software version (if not, no issue).
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
An unlocked bootloader (see e.g. LineageOS install instructions)
OxygenOS 9.0.6 firmware, which is needed for LineageOS 17.1 - see next section
Download the most current .ZIP file of the ROM and place it to your phone's internal memory
OxygenOS 9.0.6 Firmware
If you come from my LineageOS 16.0 build - or any Android 9 or 10 based ROM, you most probably have already the proper firmware.
And yes, LineageOS 17.1 is Android 10, but the latest firmware for this device has been published by Oneplus for Android 9.
How to find out about your current firmware, if you use a Custom ROM:
Connect as root via adb to your phone and enter the command adb shell cat /system/vendor/firmware_mnt/verinfo | grep Time_Stamp
If the result is "Time_Stamp": "2019-11-04 21:25:29", you are on the latest firmware, if the date/time is earlier, you need to update the firmware. THIS THREAD has got more information for you.
If you come from an Oreo (Android 8.x) Custom ROM, READ THE OP OF THIS THREAD CAREFULLY !
I can't explain it better and I am not going to repeat or summarize this. It really is in your interest to carefully read it - you have been notified and warned. Please also pay attention to the last section named "Alipay, WeChatpay, Soter and IFAA" - I strongly recommend to use the debloated firmware.
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. I recommend to use the TWRP recovery for the OnePlus 3/3T. The following instructions are based on TWRP.
To install TWRP, download the twrp-x.x.x-x-oneplus3.img file (Note: replace "x.x.x-x" in the following instructions with the respective values from the real file name) to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
Code:
fastboot flash recovery twrp-x.x.x-x-oneplus3.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and hold Power and vol.down) - DO NOT boot into the phone's Android system after having flashed TWRP! Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP must be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory". Swipe to confirm the deletion and get back into the main menu.
DO NOT flash Gapps!
This ROM comes with pre-installed microG. So don't attempt to flash Gapps.
Install ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard). Choose the .ZIP file of our ROM and swipe to flash.
If you update from a previous version of my ROM, including my LineageOS 16.0 build, you don't need to perform a wipe. If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 17.1 - be patient, the first boot after flashing a new ROM takes quite long!
Dealing with signed builds
Please note, that this builds is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash" (recommended), or - you do this on your own risk - you may try the below steps.
This happens at your own risk - make a backup with TWRP before!
Download and extract the file migration.sh from this archive
This file helps you to migrate from a build signed with the publicly available test keys (i.e. all builds around, which do not state that they are signed). If you come from another signed build (e.g. official LineageOS), you have to adapt the file accordingly (see below links).
boot into TWRP
push the migration.sh file to the directory /data/local on your device and mount the /system partition in TWRP (you can do so using the dedicated TWRP's menu entry)
launch the built-in terminal in TWRP, cd into /data/local, make migration.sh executable (chmod +x) and execute the command ./migration.sh official
(In case you receive an error, try sh ./migration.sh official instead)
flash the ROM .zip
wipe Cache and Dalvik/ART Cache
reboot system
More background information and the "theory behind" can be found in the LineageOS wiki and AOSP reference.
Bug reports:
If you have a problem, please create a post with these informations:
Original Kernel shipped with this rom:
Build Date:
And try to get log as described here
Please note that I can't and won't support issues with builds using a different kernel or Xposed.
In regards to microG, I will try my best to help when it is related to this ROM (I use it myself), but any questions of the type "the YXZ-app can't do <some sort of fancy xyz Google functionality> properly" are better asked in the respective microG forums.
Credits
AOSP project
LineageOS project
microG project
Graphene OS project
csagan5 (Bromite)
WhyOrean (Aurora)
nvertigo67 (for the modded 9.x firmware and for collaboration)
Change log
2021-10-14 - FINAL
ASB Security string 2021-10-05
Bromite System Webview and Browser updated to 93.0.4577.83
Kernel upstreamed (note: tag equals last months tag)
2021-09-12
ASB Security string 2021-09-05
Kernel upstreamed to tag ASB-2021-09-05_3.18
microG microG 0.2.22.212658-2
2021-08-08
ASB Security string 2021-08-05
Kernel upstreamed to tag ASB-2021-08-05_3.18
Bromite System Webview and Browser updated to 92.0.4515.134
F-Droid updated to 1.13
Fix in WiFi randomization
2021-07-10
ASB Security string 2021-07-05
Kernel upstreamed to tag ASB-2021-07-05_3.18
Bromite System Webview and Browser updated to 91.0.4472.146
microG 0.2.21.212158-2
AuroraStore 4.0.7
2021-06-13
ASB Security string 2021-06-05
Kernel upstreamed to tag ASB-2021-06-05_3.18
Kernel WLAN driver (qcacld-2.0) patched to include mitigations against "Frag" vuln.
Bromite System Webview and Browser updated to 91.0.4472.102
microG 0.2.19211515-9
2021-05-09
ASB Security string 2021-05-01
Kernel upstreamed to tag ASB-2021-05-05_3.18
Bromite System Webview and Browser updated to 90.0.4430.204
microG upstreamed (no version change)
Update: AuroraServices 1.1.1
2021-04-10
ASB Security string 2021-04-01
Kernel upstreamed to tag ASB-2021-04-05_3.18
Bromite System Webview and Browser updated to 90.0.4430.59
F-Droid updated to 1.12
Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
2021-03-08
Security string 2021-03-05
Kernel upstreamed to tag ASB-2021-03-05_3.18
Bromite System webview updated to 88.0.4324.207
Bromite Browser updated to 88.0.4324.207
F-Droid 1.11
microG 0.2.18.204714
2021-02-04
Security string 2021-02-05
Kernel upstreamed to tag ASB-2021-02-05_3.18
Bromite System webview updated to 88.0.4324.141
Bromite Browser updated to 88.0.4324.141
F-Droid 1.10-alpha-234
microG 0.2.17.204714-5
2021-01-15 - Initial build
Pre-installed microG (0.2.16.204713-10) and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
Bromite as default browser (87.0.4280.106)
eSpeak TTS engine (FOSS TTS solution)
Additional security hardening features listed below:
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView (87.0.4280.131)
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Constified JNI method tables and hardened bionic lib
Security Hardening Features - Details
1. Pre-installed microG and F-Droid
same as the LineageOS for microG project
2. Pre-installed AuroraStore
works w/o having to enable the "unknown sources feature"
3. Extra control of sensor access for additionally installed user apps
Special access under app permissions
4. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
5. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 17.1 (all settings can be changed at any time later):
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sensitive information is hidden on the lock screen
Camera app: Location tagging disabled by default
Further, when a lock screen protection is set (PIN, pattern, password), the Nfc, Hotspot and airplane mode tiles require authentication and cannot be set without
6. Optional blocking of Facebook- and Google-Tracking
Settings => Network & Internet (scroll down)
When activated, all outgoing connection attempts to Facebook servers will be suppressed.
Same applies to Google, but certain apps on an internal exception list will still be able to connect (AuroraStore, microG, or e.g. NewPipe, if installed)
7. Optional disable captive portal detection and to select Captive portal server URL provider
Settings => Network & Internet (scroll down)
When deactivated, the system will not ping a specific Google server any longer when establishing a WiFi connection to determine, whether a captive portal is being used. Further, the captive portal URL provider can be set (default is GrapheneOS and not Google; Settings - Network & Internet)
8. No submission of IMSI or phone number to Google when GPS is in use
GPS also works fine, if no SIM card is present, so there obviously is no benefit for the phone holder (different from other involved parties ) to provide this data . . .
9. Default hosts file with many blocked ad/tracking sites
The system's hosts file redirects a comprehensive list of URLs known to be adware, tracking, etc. to 127.0.0.1 (ipv4) and ::1 (ipv6)
10. Privacy-enhanced Bromite SystemWebView
Instead of the default Chromium System Webview component, the Bromite SystemWebView is used offering more privacy, more ad blocking and less Google tracking.
11. Bromite as shipped Browser
A chromium based browser with many privacy features.
12. Firewall UI
Settings => Privacy - Firewall
Lists all apps and allows to restrict Internet access per app in regards to WiFi, mobile network or VPN
This per-app feature is a standard feature in LineageOS, but the UI to show all apps is an Extra (taken from a topic in LineageOS's Gerrit - it may, or may not, become part of the official LineageOS one day)
13. Maximum password length increased to 64
Thanks a lot!! Will flash and report tomorrow!!
Hello!
Does this ROM allow to lock a bootloader?
Clean flashed this morning. So far so good!
zhenev said:
Hello!
Does this ROM allow to lock a bootloader?
Click to expand...
Click to collapse
I would like to refer you to the below post from the 16.0 predecessor thread:
[CLOSED] EOL [ROM][Unofficial][9.0.0][microG][signed]hardened LineageOS 16.0 for Oneplus 3/3T
Thread is discontinued: Please visit the my LineageOS 17.1 successor thread This thread is dedicated to provide hardened Lineage-OS 16.0 builds with microG included for the OnePlus 3/3T with current security patches. It is the successor of my...
forum.xda-developers.com
Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.
WM-Sef said:
Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.
Click to expand...
Click to collapse
What phone and firmware? Works like a charm for me on OP3 and OOS 9.0.6 firmware.
WM-Sef said:
Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.
Click to expand...
Click to collapse
USB works fine on my own device. As suggested by @Anghirrim - what firmware are you on?
MSe1969 said:
USB works fine on my own device. As suggested by @Anghirrim - what firmware are you on?
Click to expand...
Click to collapse
How do I check for the firmware version? It's not under Settings -> Build Number, only the Android Version.
Solved the problem by switching the default USB action to 'MTP'. After that, it suddenly started working.
Still no clue about the Termux issue.
WM-Sef said:
How do I check for the firmware version? It's not under Settings -> Build Number, only the Android Version.
Click to expand...
Click to collapse
The OP of this OP3(T) firmware thread indicates to look at the file /system/vendor/firmware_mnt/verinfo/ver_info.txt
WM-Sef said:
Still no clue about the Termux issue.
Click to expand...
Click to collapse
Their docu indicates issues with Android 10.
WM-Sef said:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
Click to expand...
Click to collapse
I had the same issue but just enabling USB-Debugging from the developer options fixed it. I was a bit surprised too and that shouldn't be normal I guess.
SenseSei said:
I had the same issue but just enabling USB-Debugging from the developer options fixed it. I was a bit surprised too and that shouldn't be normal I guess.
Click to expand...
Click to collapse
As indicated before, I do not experience such an issue with my own device, so I can't reproduce this issue.
This is actually fascinating, thank you!
How is the exact steps to install? I'm coming from another rom.. Please help.
1) Advanced Wipe >> flash fw >> flash rom
or
2) Flash fw >> Advanced wipe >> flash rom
Confused after see this thread and fw installation's thread linked above.
vkey.ptr said:
How is the exact steps to install? I'm coming from another rom.. Please help.
1) Advanced Wipe >> flash fw >> flash rom
or
2) Flash fw >> Advanced wipe >> flash rom
Confused after see this thread and fw installation's thread linked above.
Click to expand...
Click to collapse
The above order does not matter, as the firmware is flashed to different partitions than those to be wiped.
EDIT:
If you have already 9.0.6 firmware, there is no need to flash it again.
this is just what I need for my old OP3. Running a degoogled 6T as daily and still need occasional apps that do not work w/o google. flashing without hesitation and reporting back.
EDIT: a question. can I flash twrp right back after flashing the rom? I know im giving up over the air updates, but im fine with that.
I am on LineageOS 17.1 for microG, unlocked bootloader, rooted with Magisk, 9.0.6 official firmware, but I would love to try this ROM.
Few questions, please:
- can I install modded firmware, because this sounds good: "The modem firmware contains some alipay* and soter* files used for Alipay and WeChatpay. Since these are suspect to be a privacy hazard, I've modified NON-HALOS.bin to not contain any of these files any more"
- this ROM can be rooted with Magisk 20.4 or newer?
- do I have to do "clean install", and finally
- is wiping internal sd card (pics, videos etc.) obligatory?
Thanks in advance
This thread is dedicated to provide hardened Lineage-OS 18.1 builds with microG included for the OnePlus 3/3T with current security patches.
It is the successor of my Lineage 17.1 thread.
It may be worth to also look there, if you are looking for information.
Download here
Features of this ROM
Pre-installed microG like LineageOS for microG project (own fork)
Pre-installed AuroraStore, AuroraDroid and AuroraServices
OTA Support
eSpeakTTS engine
Additional security hardening features listed below:
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Mulch System Webview
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Kernel kept up to date with ASB patches of Google kernel/common 'android-4.14-q-release' branch
Debloated from Oneplus blobs for Soter and IFAA
Hardened bionic lib and constified JNI method tables
Option to only use fingerprint unlock for apps and not for the device
Optional timeout for Bluetooth and WLAN connections
Per connection WiFi randomization option
Current release levelsSecurity string: 2023-06-05
AOSP tag: 11.0.0_r46
Mulch System Webview: M114
Source-code and build instructionsKernel: https://github.com/lin18-microg/android_kernel_oneplus_msm8996/tree/lin-18.1-mse3
Build manifest: https://github.com/lin18-microg/local_manifests/tree/lin-18.1-hmalloc
Installation Instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty of information available.
Pre-Requisites
If you come from OxygenOS Stock ROM, make sure to update to the latest offered software version (if not, no issue).
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
An unlocked bootloader (see e.g. LineageOS install instructions)
OxygenOS 9.0.6 firmware, which is needed for LineageOS 18.1 - see next section
Download the most current .ZIP file of the ROM and place it to your phone's internal memory
OxygenOS 9.0.6 FirmwareIf you come from my LineageOS 17.1 build - or any Android 10 based ROM, you most probably have already the proper firmware.
And yes, LineageOS 18.1 is Android 11, but the latest firmware for this device has been published by Oneplus for Android 9.
How to find out about your current firmware, if you use a Custom ROM:
Connect as root via adb to your phone and enter the command adb shell cat /system/vendor/firmware_mnt/verinfo | grep Time_Stamp
If the result is "Time_Stamp": "2019-11-04 21:25:29", you are on the latest firmware, if the date/time is earlier, you need to update the firmware. THIS THREAD has got more information for you.
If you come from an Oreo (Android 8.x) Custom ROM, READ THE OP OF THIS THREAD CAREFULLY !
I can't explain it better and I am not going to repeat or summarize this. It really is in your interest to carefully read it - you have been notified and warned. Please also pay attention to the last section named "Alipay, WeChatpay, Soter and IFAA" - I strongly recommend to use the debloated firmware.
Install TWRP recoveryIf you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. I recommend to use the TWRP recovery for the OnePlus 3/3T. The following instructions are based on TWRP.
To install TWRP, download the twrp-x.x.x-x-oneplus3.img file (Note: replace "x.x.x-x" in the following instructions with the respective values from the real file name) to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
Code:
fastboot flash recovery twrp-x.x.x-x-oneplus3.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and hold Power and vol.down) - DO NOT boot into the phone's Android system after having flashed TWRP! Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP must be TWRP in recovery mode.
Advanced WipeONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM![/B]
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory". Swipe to confirm the deletion and get back into the main menu.
DO NOT flash Gapps!
This ROM comes with pre-installed microG. So don't attempt to flash Gapps.
Install ROMIn the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard). Choose the .ZIP file of our ROM and swipe to flash.
If you update from a previous version of my ROM, including my LineageOS 17.1 build, you don't need to perform a wipe. If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 18.1 - be patient, the first boot after flashing a new ROM takes quite long!
Dealing with signed buildsPlease note, that this builds is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash" (recommended), or - you do this on your own risk - you may try the below steps.
This happens at your own risk - make a backup with TWRP before!
Download and extract the file migration.sh from this archive
This file helps you to migrate from a build signed with the publicly available test keys (i.e. all builds around, which do not state that they are signed). If you come from another signed build (e.g. official LineageOS), you have to adapt the file accordingly (see below links).
boot into TWRP
push the migration.sh file to the directory /data/local on your device and mount the /system partition in TWRP (you can do so using the dedicated TWRP's menu entry)
launch the built-in terminal in TWRP, cd into /data/local, make migration.sh executable (chmod +x) and execute the command ./migration.sh official
(In case you receive an error, try sh ./migration.sh official instead)
flash the ROM .zip
wipe Cache and Dalvik/ART Cache
reboot system
More background information and the "theory behind" can be found in the LineageOS wiki and AOSP reference.
Why no Android 12 / LineageOS 19 build ?The answer can be found here: https://lineageos.org/Changelog-26/ (section "Let’s talk about legacy devices…").
Bug reports:If you have a problem, please create a post with these informations:
Original Kernel shipped with this rom:
Build Date:
And try to get log as described here
Please note that I can't and won't support issues with builds using a different kernel or Xposed.
In regards to microG, I will try my best to help when it is related to this ROM (I use it myself), but any questions of the type "the YXZ-app can't do <some sort of fancy xyz Google functionality> properly" are better asked in the respective microG forums.
CreditsAOSP project
LineageOS project
microG project
Graphene OS project
csagan5 (Bromite)
WhyOrean (Aurora)
nvertigo67 (for the modded 9.x firmware and for collaboration)
SkewedZeppelin (Kernel patches)
Change Log
June 2023
ASB Security string 2023-06-05
Some kernel patches
Mulch Webview 114.0.5735.61
microG on 0.2.28.231657-5
FakeStore 0.2.0
AuroraStore 4.2.3
May 2023
Security string 2023-05-05
Some kernel patches
Mulch Webview 113.0.5672.77
April 2023
Security string 2023-04-05
Some kernel patches
Removed Bromite browser and shipped LineageOS' Jelly instead
Mulch Webview 112.0.5615.48
March 2023
Security string 2023-03-05
Some kernel patches
Bromite Webview replaced by Mulch Webview 111.0.5563.58
February 2023
ASB Security string 2023-02-05
microG on 0.2.27.223616-3
Some kernel patches
Spoof apps installed by G*PlayStore
January 2023
Security string 2023-01-05
Bromite Browser and Webview updated to 108.0.5359.156
Some kernel patches
microG 0.2.26.223616-16
December 2022
Security string 2022-12-05
Bromite Browser and Webview updated to 108.0.5359.106
Some kernel patches
microG 0.2.26.223616-2
November 2022
Security string 2022-11-05
Bromite Browser and Webview updated to 106.0.5249.163
Some kernel patches
microG 0.2.25.223616-10
October 2022
Security string 2022-10-05
Bromite Browser and Webview updated to 105.0.5195.147
Some kernel patches
microG 0.2.24.223616-61
September 9th, 2022
Security string 2022-09-05
Bromite Browser and Webview updated to 104.0.5112.91
Kernel: Some patches and also hardening (GrpaheneOS patches)
microG 0.2.24.214816-30
Contacts app slightly 'de-Googled'
August 6th, 2022
Security string 2022-08-05
Bromite Browser and Webview updated to 103.0.5060.140
Some kernel patches
July 14th, 2022
Security string 2022-07-05
Some kernel patches
June 15th, 2022
Security string 2022-06-05
Some kernel patches
Bromite Browser and Webview on 102.0.5005.96
microG updated to 0.2.24.214816-11
May 9th, 2022
Security string 2022-05-05
Some kernel patches
Bromite Browser and Webview on 101.0.4951.53
microG updated to 0.2.24.214816-10
Mozilla Location provider on 1.5.0
April 15th, 2022
Security string 2022-04-05
Some kernel patches
Bromite Browser and Webview on 100.0.4896.57
March 15th, 2022
Bromite Browser and Webview on 99.0.4844.58 (bugfix build)
March 12th, 2022
Security string 2022-03-05
Some kernel patches
Bromite Browser and Webview on 99.0.4844.55
microG 0.2.24.214816-2
AuroraStore 4.1.1
Janaury 20th, 2020
Security string 2022-01-05
Some kernel patches
A couple of patches and fixes from LineageOS
December 19th, 2021
Security string 2021-12-05
Bromite Webview and Browser on 96.0.4664.54
microG 0.22.214516-21
November 13th, 2021
Security string 2021-11-05
Bromite Webview and Browser on 94.0.4606.109
October 15th, 2021
Initial build:
Security string 2021-10-01
AOSP tag 11.0.0_r46
Pre-installed microG (0.2.22.212658-2) like LineageOS for microG project (own fork)
Pre-installed AuroraStore (4.0.7), AuroraDroid (1.0.8) and AuroraServices (1.1.1)
OTA Support
eSpeakTTS engine
Bromite (93.0.4577.83) as default browser
Additional security hardening features listed below:
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView (93.0.4577.83)
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Debloated from Oneplus blobs for Soter and IFAA
Hardened bionic lib and constified JNI method tables
Option to only use fingerprint unlock for apps and not for the device
Optional timeout for Bluetooth and WLAN connections
Per connection WiFi randomization option
Tips & tricks
Please refer to the FAQ section here
Hi
Thanks for this amazing rom! Have not had any major issues that I can report. I think you forgot to add the download link? Could not find it here but got it from your Los 17 thread.
lin18-microG - Browse /oneplus3 at SourceForge.net
sourceforge.net
This is a solid build until we see A12 betas/alpha coming soon, hope you'll fork the same flavor for those roms
rudolf895 said:
Hi
Thanks for this amazing rom! Have not had any major issues that I can report. I think you forgot to add the download link? Could not find it here but got it from your Los 17 thread.
lin18-microG - Browse /oneplus3 at SourceForge.net
sourceforge.net
This is a solid build until we see A12 betas/alpha coming soon, hope you'll fork the same flavor for those roms
Click to expand...
Click to collapse
Oops, thanks for the hint! Must have gone lost, when I edited the thread, adding it again.
Edit:
I am a little bit "conservative", when it comes to providing new versions. That means: Eventually yes (assuming my device continues to work smoothly), but definitely not before LineageOS officially releases 12 for the OP3(T) and not before microG is supported for 12.
And even if those prerequisites are met, it may take several weeks, so expect at least another 6-7 months from now, before we can seriously talk about a 12 flavor for this build.
MSe1969 said:
Oops, thanks for the hint! Must have gone lost, when I edited the thread, adding it again.
Edit:
I am a little bit "conservative", when it comes to providing new versions. That means: Eventually yes (assuming my device continues to work smoothly), but definitely not before LineageOS officially releases 12 for the OP3(T) and not before microG is supported for 12.
And even if those prerequisites are met, it may take several weeks, so expect at least another 6-7 months from now, before we can seriously talk about a 12 flavor for this build.
Click to expand...
Click to collapse
fair assessment of the timeline. I have AOSP build (A12) running on my Op5 and it is so good.
H
MSe1969 said:
Oops, thanks for the hint! Must have gone lost, when I edited the thread, adding it again.
Edit:
I am a little bit "conservative", when it comes to providing new versions. That means: Eventually yes (assuming my device continues to work smoothly), but definitely not before LineageOS officially releases 12 for the OP3(T) and not before microG is supported for 12.
And even if those prerequisites are met, it may take several weeks, so expect at least another 6-7 months from now, before we can seriously talk about a 12 flavor for this build.
Click to expand...
Click to collapse
How long did you wait for A10 and A11?
borisSweden said:
H
How long did you wait for A10 and A11?
Click to expand...
Click to collapse
To bring up the build flavor to a new version, I first start with emulator builds to bring all the features up (if still possible and applicable) and to look for features from other ROMs, which I consider meaningful in regards to hardening/data privacy. Next, I try to build for the devices, I support. For the OP3T, the kernel was a bigger issue, as I wanted to keep the entirely upstreamed one (which I didn't succeed with, so I came up with plan B). Depending on personal time and motivation, you can assume ~2 months before the start of the thread as point in time, where I started developing...
I might as well update but I want to fix my mbn auto select problem (I live in Sweden, have a Swedish SIM and EU phone), Bluetooth needs to repair after some time and slwo WiFi. My base is Debloated OOS but should I do a wipe before installing 18.1? As always I use 17.1 hardened edition.
edit: Im a novice but why does the ROM replace Twrp with LOS native recovery. If its installed from twrp it should stay put. And yeah I know, flash Magisk or TWRP app after flashing the ROM.
borisSweden said:
I might as well update but I want to fix my mbn auto select problem (I live in Sweden, have a Swedish SIM and EU phone), Bluetooth needs to repair after some time and slwo WiFi. My base is Debloated OOS but should I do a wipe before installing 18.1? As always I use 17.1 hardened edition.
Click to expand...
Click to collapse
What do you mean exactly with "Debloated OOS"? You mean the debloated firmware linked in the OP?
You can " dirty-flash" my 18.1 build over 17.1.
As indicated already in my 17.1 thread, I haven't experienced your described issue. I am right now using my OP3T as a hotspot in PL using a PL SIM card without any issues...
borisSweden said:
edit: Im a novice but why does the ROM replace Twrp with LOS native recovery. If its installed from twrp it should stay put. And yeah I know, flash Magisk or TWRP app after flashing the ROM.
Click to expand...
Click to collapse
There is a setting in the Updater app, which you need to switch off to keep TWRP untouched.
MSe1969 said:
And yes, LineageOS 18.1 is Android 11, but the latest firmware for this device has been published by Oneplus for Android 9.
Click to expand...
Click to collapse
Cant you salvage something from the MSM8996plus OG Pixel 1? Last update was Android Q. Let me guess, signed drivers?
MSe1969 said:
What do you mean exactly with "Debloated OOS"? You mean the debloated firmware linked in the OP?
You can " dirty-flash" my 18.1 build over 17.1.
As indicated already in my 17.1 thread, I haven't experienced your described issue. I am right now using my OP3T as a hotspot in PL using a PL SIM card without any issues...
Click to expand...
Click to collapse
Lets see if Gabeldorsche fixes Bluetooth. Nvertigo said that the region selecter works as intended but on PDC I got mostly Chinese and US carriers. I had to do a wipe install so its to late do a "dirty install". i forgot Seedvault was a thing.
MSe1969 said:
There is a setting in the Updater app, which you need to switch off to keep TWRP untouched.
Click to expand...
Click to collapse
Doh! Cant you remove that option because TWRP is more useful. I was able to change recovery after installing your ROM thankfully didnt brick or wipe my install.
borisSweden said:
Cant you salvage something from the MSM8996plus OG Pixel 1? Last update was Android Q. Let me guess, signed drivers?
Click to expand...
Click to collapse
No. Firmware is device - not only soc - dependent. For details on what exactly firmware contaims see my thread on (patched) firmware in the general forum.
I.g. the bootloader and the modem partitions are part of the firmware. Overwriting these with otjer devives versions will brick your device, and youu will need to use the msm tool to bring it back to life.
Please read the general forum and all los threafs in the dev forum to get the basics to start messing with firmware.
I don't mean to offend you, but some of your questions seem to me that your current questions are three steps ahead of your current knowledge.
Might as well write stuff I found wrong in the ROM as Im returning to OOS. Aurora F-droid lags to much and the F-droid privilege module doesn't work with it. Manually accepting every install and update isnt that fun so I would recommend going back to the OG app.
Also in the update app for LOS, the timestamp is wrong. It says last update 1970 January 1. Should say 10 October.
Idk what my cellular network bug is but on the to right corner the icon is just wrong. Its 4G then the triangle with a X. In preferred network type settings NR/5G is still present. Doesn't make sense that you can chose 5G.
Bluetooth works as intended but in dev settings Enable Gabeldorsche doesnt do anything. Does it even work?
borisSweden said:
Might as well write stuff I found wrong in the ROM as Im returning to OOS. Aurora F-droid lags to much and the F-droid privilege module doesn't work with it. Manually accepting every install and update isnt that fun so I would recommend going back to the OG app.
Click to expand...
Click to collapse
The ROM comes with AuroraServices, but you have to enable that in the app's setings, then it'll work.
If you try flashing the F-Droid privileged extension, that won't work for sure!
borisSweden said:
Also in the update app for LOS, the timestamp is wrong. It says last update 1970 January 1. Should say 10 October.
Click to expand...
Click to collapse
This normally should only happen, if you haven't fetched any update before (or deleted the app cache). Btw, I took over the LineageOS Updater app "as is" and only overlaid the updater URI.
borisSweden said:
Idk what my cellular network bug is but on the to right corner the icon is just wrong. Its 4G then the triangle with a X. In preferred network type settings NR/5G is still present. Doesn't make sense that you can chose 5G.
Click to expand...
Click to collapse
Tend to agree - will have a look, but I did not change/alter anything here. Will get back...
borisSweden said:
Bluetooth works as intended but in dev settings Enable Gabeldorsche doesnt do anything. Does it even work?
Click to expand...
Click to collapse
No idea, haven't changed anything in that area - this seems original Android code.
MSe1969 said:
No idea, haven't changed anything in that area - this seems original Android code.
Click to expand...
Click to collapse
In theory less battery usage but it could be Fushsia snakeoil. It written in cleaner code. But everyone knows that a higher BT version is more efficient in battery usage. To bad SBC HD isnt working as intended , APTX take to many resources.
MSe1969 said:
The ROM comes with AuroraServices, but you have to enable that in the app's setings, then it'll work.
If you try flashing the F-Droid privileged extension, that won't work for sure!
Click to expand...
Click to collapse
Did I make a mistake? Yes I did.
>Tend to agree - will have a look, but I did not change/alter anything here. Will get back...
I would like to have a carrier volte profile selector or enable Diag mode for PDC button but that is LOS team job.
Hello my favorite "kernel-upstreamer" ,
android-3.18 has been gone and deprecated/android-3.18 has shown up:
Code:
[email protected] /usr/local/src/los16/kernel/oneplus/msm8996 $ LANG=C.UTF-8 git fetch https://android.googlesource.com/kernel/common android-3.18
fatal: couldn't find remote ref android-3.18
[email protected] /usr/local/src/los16/kernel/oneplus/msm8996 $ LANG=C.UTF-8 git fetch https://android.googlesource.com/kernel/common deprecated/android-3.18
From https://android.googlesource.com/kernel/common
* branch deprecated/android-3.18 -> FETCH_HEAD
My educated guess is that support for 3.18 has been finally droped.
As far as I can see caf for 3.18 for 8x96 hasn't seen any updates for at least 14 months.
I've merged 380bbf94c0fc..839523fca2ef from the deprecated branch on top of your lin-17-mse3 - works great. I've also tried to merge the commits from the 4.x.y branches mentioned here: https://source.android.com/security/bulletin/2021-11-01#kernel-components (but to no advance).
Do you have more information? What are your thoughts?
Take care.
nvertigo67 said:
android-3.18 has been gone and deprecated/android-3.18 has shown up:
Click to expand...
Click to collapse
My question about "how long will 3.18 be supported" was way close to this decision. Did I jinx it?
nvertigo67 said:
Hello my favorite "kernel-upstreamer" ,
android-3.18 has been gone and deprecated/android-3.18 has shown up: [...] My educated guess is that support for 3.18 has been finally droped.
Click to expand...
Click to collapse
Well, that is also my conclusion. Pitty, but expectable one day...
nvertigo67 said:
As far as I can see caf for 3.18 for 8x96 hasn't seen any updates for at least 14 months.
Click to expand...
Click to collapse
Hmmm... not really good news either...
nvertigo67 said:
I've merged 380bbf94c0fc..839523fca2ef from the deprecated branch on top of your lin-17-mse3 - works great. I've also tried to merge the commits from the 4.x.y branches mentioned here: https://source.android.com/security/bulletin/2021-11-01#kernel-components (but to no advance).
Do you have more information? What are your thoughts?
Click to expand...
Click to collapse
The source, where I get the few patches for this 18.1 ROM's kernel is the divested-mobile org. on GH (but the guy in fact was also making use of the kernel/common 3.18 repo...), so no real good idea. We may from time to time see some back ports of certain 4.4 commits, but I'm afraid the good times of getting patches f. 3.18 are over...
MSe1969 said:
The source, where I get the few patches for this 18.1 ROM's kernel is the divested-mobile org. on GH (but the guy in fact was also making use of the kernel/common 3.18 repo...), so no real good idea. We may from time to time see some back ports of certain 4.4 commits, but I'm afraid the good times of getting patches f. 3.18 are over...
Click to expand...
Click to collapse
Ironic as it been 5 years since the 3T was released. Do all SoC specific kernels only have 5 years of patches?
Well there is still 4.4 commits or going full 4.4 but then you would only get 1 extra year of commits when the OP5 turns 5 years old.
On the issue of the USB port and Dash not working with 4.4, finding a New old Stock Dash charger is hard and nobody wants to fork out 50 Euros for a Warp 65 charger. Supporting proprietary charging tech is verbose for now.
Only supporting USB-PD is enough also is the phone USB2.0 because of physical limitations?
That's my 2 cents.
New build with November 2021 ASB patches
Hi all, a new build for the OP3(T) containing the November 2021 ASB patches has been released:
https://sourceforge.net/projects/lin18-microg/files/oneplus3/lineage-18.1-20211113-UNOFFICIAL-microG-signed-oneplus3.zip/download
The Updater app should soon indicate it to offer an OTA update.
Security string 2021-11-05
Bromite Webview and Browser on 94.0.4606.109
Some kernel patches
Happy flashing,
Regards, M.