Related
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.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://drive.google.com/uc?id=1Fr914YU8yXks6paaS-sGtm7jwHqoZFUR&export=download
GApps: https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500
Bugs:
- Cast/Miracast
- FPC fingerprint dead after a reboot
- Goodix fingerprint fully dead
- VoLTE working on Jio, not working on airtel
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][mido][10] LineageOS 17.0, ROM for the Xiaomi Redmi Note 4
Contributors
GiaSen, DD3Boh, Lucchetto00
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.1
Beta Release Date: 2019-09-22
Created 2019-09-22
Last Updated 2019-10-05
Reseverd
What is partially working? It works or it doesn't.
Gesture navigation works or is there an option to disable hardware navigation ?
k3lcior said:
What is partially working? It works or it doesn't.
Click to expand...
Click to collapse
fpc is dead after a reboot
Awesome work devs, everything I need works perfectly. Can't believe the smoothness for an early build. Hope FPS will be fixed soon
Gestures working or not?
Nice! Looking forward to stable builds ?
Thanks for your efforts!
You are pretty good!
I am getting a black screen after boot with a bootloop after few minutes. I use beta 6 Bitgapps.
Thanks the great job, I installed BitGapps 10.0 beta 6, working smooth.
Another mirror would be nice! Thanks dev for your work, it's really awesome that you made this.
EDIT: Actually to bypass this, just save the file to your drive then hit Make a Copy then download the copy.
EDIT 2: Flashed. I did a reboot after the initial boot since that cleared up a lot of errors. Some things I noticed:
Back gesture does not work.
I don't see the option to add the fingerprint. I read the OP so I know its partially working, but did not think it was completely removed.
No option to chose a different accent color other than the default.
All of that said, insane how well this first build runs. Remarkable work dev
GPS Fix / Accuracy issue
Hi; Lineage17, bitgappsv6 - anyone having GPS fix/accuracy issues? All permissions were granted to apps, but unable to get proper GPS location fix; tried with a few apps. Satellites seems to be seen, but location not - currently not sure whether it is gapps related, ROM, some other permission or just my phone. Will someone be so kind as to test? attached is screenshot from gps test
jdstrydom said:
Hi; Lineage17, bitgappsv6 - anyone having GPS fix/accuracy issues? All permissions were granted to apps, but unable to get proper GPS location fix; tried with a few apps. Satellites seems to be seen, but location not - currently not sure whether it is gapps related, ROM, some other permission or just my phone. Will someone be so kind as to test? attached is screenshot from gps test
Click to expand...
Click to collapse
Gps is fixed and working fine for me. With gps locker: inview-31, in use: 12. fixed 4 seconds....
joselap said:
Gps is fixed and working fine for me. With gps locker: inview-31, in use: 12. fixed 4 seconds....
Click to expand...
Click to collapse
Tried with GPS Unlocker now (attached)
in-view 14
in use 0
not fixing
which makes me think this is some kind of permission problem on my side. My installation process with installation was:
1. Reboot to TWRP & wipe system, vendor (vendor is included in LOS17), data, cache, dalvik & cache
2. Flash Lineageos 17.0 20190922
3. Flash BitGAPPS Beta 6 (latest)
4. Flash Magisk 19.5 (as instructed)
5. Reboot & setup gmail account etc.
Did you do anything different from what I did above?
Thanks for testing
EDIT: The issue was resolved. I had the weekly chinese firmware flashed to my phone for a previous ROM. After I reflashed V10.2.3.0 (Global) firmware, and rebooted; GPS came right for me, and fixing fast.
Is it possible to use virtual navbar (and disable HW keys) on this build?
Can anybody release screenshots pls
varun_77 said:
Can anybody release screenshots pls
Click to expand...
Click to collapse
There's a video review already.
https://www.youtube.com/watch?v=z81VWkuBu84
Another Mirror: https://drive.google.com/open?id=1QUQJrKTftLNr3_duWkhaNw_3OOKkFF2E
C-Ph87 said:
There's a video review already.
Click to expand...
Click to collapse
Thanks
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
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.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Whats works:
Booting
Audio
Graphics
RIL (calls, sms, mobile data)
Wi-Fi, Wi-Fi Direct
Bluetooth
GPS, GLONASS
FM Radio
Sensors
Camera
Face Unlock
Video recording
Screen cast
Offline charging
SELinux (enforcing)
SafetyNet (with hidden Magisk or without root)
Tell me, if something does not work.
FAQ
Q: Does this ROM supports double tap to wake? A: No. And will not in future.
Q: Cannot add widgets to home screen. Widgets is not supported? A: Widgets is not supported in builtin launcher. Download any third-party home app (like Nova Launcher) and enjoy!
Q: Why split screen mode is not available? How to enable? A: Due to Android Go limitations, all forms of multiwindowing is not available on this edition of Android.
Q: When my app "foo" asks permission to access to notifications or to run on top of other apps, I see "This feature is disabled"... A: This is limitations of Android Go to save memory.
Q: Cannot use my sdcard as primary storage! A: This feature is unstable and excluded from ROM.
Q: Flashed this ROM but phone don't booting! A1: Boot to recovery and wipe /data, then reboot. A2: If your /data is formatted to f2fs, format it to ext4 and boot your phone.
Q: What is "Gapps for Android Go"? A: This is Gapps set, extracted as-is from Nokia 1 Plus Android 11 Go firmware and packaged for Lenovo A6000. Nothing removed, just fixed some permissions and added Google Camera Go.
Installation
Flash latest recovery (if needed), based on TWRP >= 3.2
Reboot to recovery
Wipe /cache and /data. If your /data is formatted in f2fs, format it in ext4, otherwise OS will not boot.
Flash the rom
Flash Gapps (Gapps for Android Go or OpenGapps ARM/Android 11/pico or nano)
Flash Magisk (also if needed)
Reboot to ROM
Spoiler: Latest changes
Build 05.09:
August security patch level
ROM is signed with release-keys
Build variant now is user, not userdebug
Updates from Lineage OS team
Clipboard access notification
USB fast charging toggler
Some OEM Android Go tweaks (from Nokia, ZTE)
New default wallpaper
Stricten background limits: 2 apps for 1/8 and 4 for 2/16
Recents is limited to 4 apps
Reworked WiFi and Tethering configuration overlays
Added overlays for Gboard, MessagesGo
Disabled caching in Trebuchet (launcher is fast enough to allow us to save some amount of memory)
zRam switched to Zstandart compression algorithm
Implemented clean page protection to reduce lags under memory pressure
Disabled rounded corners in UI
SEPolicy fixes
Misc...
NOTE: Strongly not recommended "dirty" updating. If you want to do this anyway, flash migration script before flashing the ROM!
Migration script: https://drive.google.com/file/d/15hB63RkyRpCljho9jyFTHoYWvCl4cDWe/view?usp=drivesdk
Download ROM: https://drive.google.com/file/d/1vUHuS18vDowwCSIWl8Dl4xxRHR4EHir0/view?usp=drivesdk
Gapps: Gapps for Android Go(updated!) or OpenGapps (ARM, pico or nano)
Credits to:
twain55
Moto-M8916 guys
Teo Flo
dev_harsh1998
SkepticOne
Nitrogradient
IvanHephaestus
Our Telegram discussion group: Lenovo A6000/Plus Community Discussions
Contributors
acroreiser
dev_harsh1998
Source code
Device tree: https://github.com/acroreiser/android_device_lenovo_a6000
Kernel tree: https://github.com/acroreiser/android_kernel_lenovo_a6000
Vendor tree: https://github.com/acroreiser/android_vendor_lenovo_a6000
ROM OS Version: Android 11 Go
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Hex Firmware Patch, TWRP >= 3.2
Based On: LineageOS
Version Information
Status: Stable
Created 2021-05-12
Last Updated 2021-09-13
Finally android 11 for a6000 thank you
Wow, I thought the previous version (17.1) is the last one for this device.
I am really happy I was wrong!
Thank you so much for your work acroreiser and dev_harsh1998. Also thanks to everyone who is credited!
First of all thanks to all the Devs who have kept this device still alive by providing it with those up to date roms...
Well I am using this rom for last 3 days i must say its super smooth apps are opening blazing fast, all major functions are working properly and it can be used as a daily driver for sure...
Now I encounter one bug so far its in Camera Go app the thing is when i change the storage location to SD card and start video recording than it suddenly freezes after some seconds by saying "Something went wrong " than i need to restart the app for using it again, by the way when i change the storage location back to internal than video recording is working fine so its really not bothering me that much....
There is one more thing well its not a bug its just my observation with this rom that during charging its heat up more than expected even when its charging at 90% to 100% slot which i never experience with any other roms.
All in all still its worth a shot everything's working fine, thanks to the devs again...
[email protected] said:
First of all thanks to all the Devs who have kept this device still alive by providing it with those up to date roms...
Well I am using this rom for last 3 days i must say its super smooth apps are opening blazing fast, all major functions are working properly and it can be used as a daily driver for sure...
Now I encounter one bug so far its in Camera Go app the thing is when i change the storage location to SD card and start video recording than it suddenly freezes after some seconds by saying "Something went wrong " than i need to restart the app for using it again, by the way when i change the storage location back to internal than video recording is working fine so its really not bothering me that much....
There is one more thing well its not a bug its just my observation with this rom that during charging its heat up more than expected even when its charging at 90% to 100% slot which i never experience with any other roms.
All in all still its worth a shot everything's working fine, thanks to the devs again...
Click to expand...
Click to collapse
The problem is in the application itself. in the firmware the application is of the old version and there should be no problems with the video. But it is automatically updated to the latest version in the Playmarket and there is a problem. Remove the app update and it will work as expected.
Teo Flo said:
The problem is in the application itself. in the firmware the application is of the old version and there should be no problems with the video. But it is automatically updated to the latest version in the Playmarket and there is a problem. Remove the app update and it will work as expected.
Click to expand...
Click to collapse
Thanks for the info, I will try that for sure...
Hey devs,
Thanks for this brand new ROM! I use this phone as a daily driver and wanted your advice on this version or the 17.1 version. Which one is likely to be maintained in the future? I understand that 17.1 is stable but will it still get more updates or security patches or should I go ahead with this 18.1 version, please?
Thank you for your help and also for keeping this phone alive in 2021.
Cheers,
S
santoshwins said:
Which one is likely to be maintained in the future?
Click to expand...
Click to collapse
Currently Lineage OS 18.1 is maintained.
Both 17.1 and 18.1 is based on my Go device tree (forked from @dev_harsh1998 lineage-16.0 tree) but lineage-17.1 branch is not maintained since february 2021.
I don't know is @twain55 can maintain 17.1 builds for a long time (better ask him).
Lineage OS 18.1 is pretty stable for daily usage by user reports and my experience with a6010 (I don't have a6000 and primarily maintaining a6010 with merging stable changes to a6000 tree).
Can a dirty flash be done from 17.1 ?
Zack316 said:
Can a dirty flash be done from 17.1 ?
Click to expand...
Click to collapse
Of course no.
New build is up!
Changes:
June security patch level
Updates from Lineage OS team
Memory and performance optimizations for 1/8 devices
Forward-ported qcom memory optimizations (frameworks/base)
Updated Binder driver (kernel)
Implemented automatic background apps memory reclaim (kernel)
Restored Qualcomm VP8 and HEVC codecs
Updated Bluetooth HAL from Nokia 1.3
Updated some media blobs
Some kernel tweaks from other low ram devices (Redmi Go, Nokia 1.3)
Workaround for broken video recording in recent versions of Google Camera Go
Recent apps screen is limited to 5 apps to save memory
Killed multiuser support - Go devices should not have this. Also this feature is pointless in our ancient phones...
Download: https://drive.google.com/file/d/1IqRTbY9CYH9Je3bmqaavjQHnn-763bx5/view?usp=drivesdk
Wow, thank you so much for the android 11 version. It is minimalistic and smooth. Loved the rom. Also thank you devs for keeping this device alive.
Needs Undervolting.
Even the standby drain is around 600ma.
Also I've bought a new battery for this, even that cannot survive more than an hour of SOT.
Please optimised the kernel or just undervolt it a bit.
Also only one of the back speaker is working,
Hi , Dear
Thank you for your your creativity
For Lenovo A6000 1G Ram & 8Gb Rom
Which version is the best 17.1 or 18.1 ??
Can i flash Twrp 3.2 on kitkat or must to be on Lolipop ??
Cheers ^_^
so this rom i cannot use my sd card right? that's super bad for me!
-ARiCK- said:
so this rom i cannot use my sd card right? that's super bad for me!
Click to expand...
Click to collapse
There is no problem with the firmware for using the SD card
I keep getting the "This build is signed with public key" error notification every time at startup.
New build us up!
Quick changelog:
August security patch level
ROM is signed with release-keys
Build variant now is user, not userdebug
Updates from Lineage OS team
Clipboard access notification
USB fast charging toggler
Some OEM Android Go tweaks (from Nokia, ZTE)
New default wallpaper
Stricten background limits: 2 apps for 1/8 and 4 for 2/16
Recents is limited to 4 apps
Reworked WiFi and Tethering configuration overlays
Added overlays for Gboard, MessagesGo
Disabled caching in Trebuchet (launcher is fast enough to allow us to save some amount of memory)
zRam switched to Zstandart compression algorithm
Implemented clean page protection to reduce lags under memory pressure
Disabled rounded corners in UI
SEPolicy fixes
Misc...
Read notes in OP before installing!
Installed the latest build. Thank you. Great work . Everything is working very good. Battery life is extremely good. Got 7-8 hours full HD youtube playback on 4g. Go version is working very smoothly ( previously was using android 5.0 stock )
...
I also have another device 10or.E which has similar SoC SD430. Can you tell me step by step instructions. Kernel source is available. ( I read about building but did not clearly understand various terms like vendor etc... Tried to create initial .mk files for the board but errors at luch command itself )
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.