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 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. At the moment this means this build is optimized for oneplus3t - and it runs only on oneplus3t.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) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps). Since LineageOS lacks a theme engine this rom comes with OMS patches applied and is Substratum ready.
NLOS is shipped with Camera2 (atm I recommend the modded Google Camera from Modded Google Camera with HDR+, 60FPS video and Slow Motion by @S4turno or the modded OnePlusCamera from my downloads - do NOT! install both the same time: it's GCam XOR OPCam.
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.
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 14.1 builds for oneplus3t - it is not for oneplus3. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano (read this.)
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 bigger then opengapps-nano)
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the ROM below in the downloads section (or from a mirror; see posting #2)
If you have downloaded a build with "firmware" in it's name, the needed firmware is included and installed while flashing. If you have downloaded a build without "firmware" in it's name, you need to flash the needed firmware BEFORE flashing the rom. You'll find the firmware flashable zips near the end of this posting. New files are added on top of the list.
Download exactly Beans Dynamic Mini Gapps (Note that any other version of Google Apps are known to have wide spread side effects - see posting #4; section "gapps' known issues"
Install exactly this TWRP.
Reboot into recovery.
Backup your current ROM and make sure you have backups of your data you want to keep.
Flash firmware if not using a build with "firmware" in it's name.
Wipe system, data and cache. (Before flashing anything, make sure the system partition is NOT mounted: TWRP-home->mount->uncheck system)
Flash LineageOS
Flash Google Apps (see posting #4; section "gapps' known issues") If you want to use microG skip this step and install microG (How to use Android without Google Apps).
Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery and flash a newer LineageOS zip. Settings, apps and even google apps should be 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/14.1/
Since my time is quite limited till end of October, the update frequency is reduced to 7 to 10 days.
Build 20180309
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
This is most propably the last NLOS-14.1 build. I want to say "Thanx" to all users. Please feel invited to to use NLOS-15.1!
EOL.
Changelog:
Sync to upstream: March Security Patch.
boeffla_wl_blocker: defconfig: enable wl_blocker. — nvertigo
wl_blocker: add more wakelocks to the default block list — Francisco Franco
boeffla_wl_blocker: update to wakelock blocker driver v1.1.0 — andip71
boeffla_wl_blocker: update to wakelock blocker driver v1.0.1 — andip71
boeffla_wl_blocker: add generic wakelock blocker driver v1.0.0 — andip71
WG: squash WireGuard-0.0.20180304. — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
History
Build 20180214
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
There has been some confusion on twrp versions, lately. For nlos always use the "original nougat twrp-3.2.1-0".
If you have issues with bootloops or access to data with some apps, use "original nougat twrp-3.2.1-0" to FORMAT(!) the data partition of the device:
Backup all your data (eveything under /sdcard/; i.e. Downloads, Vodeo, DCIM, etc...)
Boot to "original nougat twrp-3.2.1-0".
Tap on "Wipe".
Tap on "Format Data".
Confirm with swipe. This actually clears your complete data partition, including all data and encyption.
Check if the newly created fs is the type you want (ext4 and f2fs is supported) - eventually change it to your liking.
Just follow the OP's procedure for first installs from OP's "Installation" section (clearing data is allready done, of course).
Changelog:
Sync to upstream: Feb. Security Patch
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Build 20180206
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
There has been some confusion on twrp versions, lately. For nlos always use the "original nougat twrp-3.2.1-0".
If you have issues with bootloops or access to data with some apps, use "original nougat twrp-3.2.1-0" to FORMAT(!) the data partition of the device:
Backup all your data (eveything under /sdcard/; i.e. Downloads, Vodeo, DCIM, etc...)
Boot to "original nougat twrp-3.2.1-0".
Tap on "Wipe".
Tap on "Format Data".
Confirm with swipe. This actually clears your complete data partition, including all data and encyption.
Check if the newly created fs is the type you want (ext4 and f2fs is supported) - eventually change it to your liking.
Just follow the OP's procedure for first installs from OP's "Installation" section (clearing data is allready done, of course).
I have reintroduced lineageos Snpdragon Camera (Snap), because of it's new implemented QuickReader - the issue with crashes on one of the first ff-cammtaken pics is still present. Wiping system and reflashing BeansGapps-Mini-7.1.x-20170725.zip is highly recommended!
Changelog:
op3: Address SELiunx denials — dianlujitao
op3: Unbreak perfd — dianlujitao
Revert "Drop LineageOS/CAF SnapCam aka Snap." — nvertigo
qcacld-2.0: Update to LA.UM.5.5.r1-06700-8x96.0 — dianlujitao
Merge tag 'LA.UM.5.5.r1-06700-8x96.0' into cm-14.1 — dianlujitao
ANDROID: xattr: Pass EOPNOTSUPP to permission2 — Daniel Rosenberg
ANDROID: sdcardfs: Move default_normal to superblock — Daniel Rosenberg
ANDROID: sdcardfs: Fix missing break on default_normal — Daniel Rosenberg
f2fs: Reset to v4.14-rc1-3.18 — dianlujitao
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Build 20180131
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Mantainance: synced to los.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
P.S.: chagallwifi build is updated as well - f2fs for cache and data fixed.
Build 20180120
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Revert "Track our own version of android_vendor_codeaurora_telephony." — Nvertigo
Update WireGuard to 0.0.20180118.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Build 20180116
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Xtra Fixes - https, version check & version 3 — Wyatt Riley
January security update.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
P.S.: chagallwifi build is updated as well - aptx enabled.
Happy flashing!
Build 20180109
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Some new fs, fs-crypt and sdcardfs patches has been merged upstream. Perhaps these also solve the remaining issues with bootloops, though I have only very little hope these will avoid the necessity of reformatting the user-data partition.
Changelog:
fscrypt: move to generic async completion — Gilad Ben-Yossef
crypto: introduce crypto wait for async op — Gilad Ben-Yossef
fscrypt: lock mutex before checking for bounce page pool — Eric Biggers
fscrypt: new helper function - fscrypt_prepare_setattr(
fscrypt: new helper function - fscrypt_prepare_lookup(
fscrypt: new helper function - fscrypt_prepare_rename(
fscrypt: new helper function - fscrypt_prepare_link(
fscrypt: new helper function - fscrypt_file_open(
fscrypt: new helper function - fscrypt_require_key(
fscrypt: remove unneeded empty fscrypt_operations structs — Eric Biggers
fscrypt: remove ->is_encrypted(
fscrypt: switch from ->is_encrypted(
fs, fscrypt: add an S_ENCRYPTED inode flag — Eric Biggers
fscrypt: clean up include file mess — Dave Chinner
fscrypt: fix dereference of NULL user_key_payload — Eric Biggers
fscrypt: make ->dummy_context(
ANDROID: sdcardfs: Add default_normal option — Daniel Rosenberg
ANDROID: sdcardfs: notify lower file of opens — Daniel Rosenberg
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
P.S.: chagallwifi build is updated as well.
Happy flashing!
Build 20180106
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
I've done some testing with toolchains: I couldn't find any advantage using Snapdragon llvm, so I decided to stay with laos stock clang. I also found that using a gcc-6 based cortex-a53 toolchain on the kernel (instead of 4.9) makes the resulting kernel a very little bit more bat friendly. But I did NOT found any advantage of UBERTC/Linaro compared to plain (no Linaro patches and enhancements) gcc-6 build for cortex-a53.
Considering those observations, I decided to use:
kernel: cortex-a53 optimized gcc-6.4.1 (crosstool-ng, config: https://bitbucket.org/nvertigo/aarc...og.bz2?at=master&fileviewer=file-view-default)
All other c- and c++-code in the rom: stock laos llvm/clang
Your milleage may vary, but to me this combination is CURRENTLY giving the best ballance of performance and bat life. Let me know your impressions.
Changelog:
Remove Snapdragon LLVM. — Nvertigo
Add aarch64-linux-android-6.4: stock gcc version 6.4.1 20171215 (crosstool-NG crosstool-ng-1.23.0-288-gadaa3a5d
Remove aarch64-linux-android-6.x. — Nvertigo
Remove aarch64-linux-android-5.x. — Nvertigo
Remove aarch64/aarch64-linux-android-4.9. — Nvertigo
Remove aarch64-linux-android-4.9-kernel. — Nvertigo
Fix derp in opting in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo
Opt in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo
Use GNU gcc 6.4.1 for kernel building. — nvertigo
gcc-6.4.1: disable unused-const-variable warnings. — nvertigo
gcc-6.4.1: remove unsed variable fsm_en. — nvertigo
gcc-6.4.1: fix a bunch of (misleading) indents. — nvertigo
bluetooth: hci_sock: Fix warning detected by gcc 5.3.1 — NewEraCracker
tfa9890: tfa_container: Fix warnings detected by gcc 5.3.1 — NewEraCracker
treewide: Fix code errors detected using Linaro GCC 6.3.1 — Sultan Alsawaf
treewide: Properly fix use of uninitialized variables — Sultan Alsawaf
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Build 20171230
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
mcpu: use cortex-a53 with stock clang/llvm. — nvertigo
Revert "msm: camerav2: isp: Reserve rdi ub based on image size" — nvertigo
Revert "msm: camera: Synchronize v4l2 subscribe and unsubscribe event in camera.c" — nvertigo
Revert "msm: camera: isp: Allocate kernel page and map to userspace" — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
May the source be with you and yours in 2018!
Build 20171223 (xmas-firmware)
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Firmware requirementsnhave not changed, but to avoid unneseccary hussles during Xmas I included the firmware (with nlos bootlogo) again for this build.
disable SDCLANG and UBERTC for now (to minimize any issues).
Bootlogo: add NLOS bootlogo. — nvertigo
net/wireguard: add wireguard importer — nvertigo
Revert "msm: mdss: Do not attempt to request TE irq again if already requested" — dianlujitao (laos/cm-14.1
op3: Regen defconfig — dianlujitao
ANDROID: ion: Fix uninitialized variable — Daniel Rosenberg
drivers: staging: Update qcacld-2.0 driver — Luca Stefani
Merge tag 'LA.UM.5.5.r1-06400-8x96.0' of https://source.codeaurora.org/quic/la/kernel/msm-3.18 into cm-14.1 — dianlujitao
sepolicy: allow apps to stat processes. — nvertigo (nvertigo/nlos-14.1, github/nlos-14.1, nlos-14.1
sepolicy: allow cameraserver to search mpctl socket directories. — nvertigo
sepolicy: add a bunch of denials need for different apps. — nvertigo
sepolicy: allow hostapd to access diag_device. — nvertigo
gps: update to LA.UM.5.5.r1-06400-8x96.0. — nvertigo
Revert "IMS: fix derp: remove some test settings again." — nvertigo
sepolicy: allow time_daemon to connect to unix_stream_socket. — nvertigo
sepolicy: allow mediacodec to search mpctl. — nvertigo
sepolicy: allow system_server to use setsched. — nvertigo
init: set downmigrate after upmigrate. — nvertigo
init: remove some artefacts from eas. — nvertigo
oneplus3: Enable framework sched boost — Sultanxda
BoardConfig.mk: remove out-commented SDCLANG. — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Firmware
NVertigo's Oxygen Firmware Archive
Renamed blobs (for use with custom kernels build for unified roms)
NVertigo's UniBlob Archive
TWRP
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Google Apps:
Beans Dynamic Mini Gapps
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/cm-14.1 (If you want to build this rom yourself, consult the file named README)
Aytex, who made all of the banners on this post.
team-exynos5429 for the OP templete.
All the LineageOS-Team.
@Lord Boeffla for patiencely answering my questions.
@koenkk
@Sultanxda
@TheFrozen4 for documentation and optimizing this OP.
@m0d hipp¥ for mirroring.
@mad-murdock for first testings.
The microG Team
Nathan Chancellor for LineageOMS, especially for this wonderfull piece of software.
@joshuous for introducing and explaing EAS to me and making VoxPopuli public. Last and not least for running EAS-Project.
@RenderBroken for providing EAS patches for EAS-Project's LineageOS based kernel.
@UnbracedTundra for all the awesome NLOS-ArtWork.
@zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
...and everybody I forgot.
Happy flashing!
I will be putting the latest mirror's of nvertigo67's rom on here.
Additional FilesOxygenOS - ob8 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob8-firmware.zip
OxygenOS - ob7 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob7-firmware.zip
OxygenOS - ob6 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob6-firmware.zip
OxygenOS - ob5 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob5-firmware.zip
OxygenOS - ob4 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob4-firmware.zip
4.0.3 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-4.0.3-firmware.zip
TWRP 3.0.4-1 - http://x-null.net/xda/nvertigo67/Other/twrp-3.0.4-1-oneplus3.img
TWRP 3.1.0-1 - http://x-null.net/xda/nvertigo67/Other/twrp-3.1.0-1-oneplus3t.img
Open Gapps Nano 01-20-2017 - http://x-null.net/xda/nvertigo67/Other/open_gapps-arm64-7.1-nano-20170120.zip
Newest will be on top
June 6 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170606-UNOFFICIAL-nvertigo-oneplus3t.zip
June 6 2017http://www.x-null.net/xda/nvertigo6...06-UNOFFICIAL-nvertigo-gps-test-oneplus3t.zip **GPS TEST**
June 2 2017http://www.x-null.net/xda/nvertigo6...02-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
May 24 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170524-UNOFFICIAL-nvertigo-oneplus3t.zip
May 18 2017http://www.x-null.net/xda/nvertigo6...18-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
May 15 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170515-UNOFFICIAL-nvertigo-oneplus3t.zip
May 9 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170509-UNOFFICIAL-nvertigo-oneplus3t.zip
May 3 2017http://www.x-null.net/xda/nvertigo6...03-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Apr 26 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip *Experimental with OMS*
Apr 22 2017http://www.x-null.net/xda/nvertigo6...NOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip *Experimental*
Apr 18 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170418-UNOFFICIAL-nvertigo-oneplus3t.zip
Apr 11 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 7 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170407-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 4 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170404-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 1 2017http://www.x-null.net/xda/nvertigo6...01-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 30 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170330-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 28 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170328-UNOFFICIAL-mad-murdock-oneplus3t.zip
Mar 24 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170324-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 20 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170320-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 16 2017http://www.x-null.net/xda/nvertigo6...16-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 12 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170312-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 7 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170307-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 4 2017http://www.x-null.net/xda/nvertigo6...04-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 1 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170301-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 25 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170225-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 24 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170224-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 18 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170218-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 14 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170214-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 10 2017http://www.x-null.net/xda/nvertigo6...10-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Feb 6 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170206-UNOFFICIAL-nvertigo-oneplus3t.zip
https://mega.nz/#!aYNkERIb!QyFzj6IZAchSL0TqIn-ZDIrsZulStkbDZi0RF1oyJcg - credit to @t-shock
Feb 3 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170203-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 1 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170201-UNOFFICIAL-nvertigo-oneplus3t.zip
https://mega.nz/#!jRdB1aRZ!-QzqNBaP_7QWZPxpuFQz1X3a7IghVy21xLDqyTlJew8 - credit to @t-shock
3T only - why that?
Since the latest changes in init and overlay, I don't think this posting is true any longer.
I don't like to publish a rom for a device I have not my hands on. So this is still 3t-only.
I completely understand all devs doing unified builds. I completely understand it was so annoying, that oneplus launched 3T half a year after 3, and devs wanted to preserve their work, or don't want to buy just another device. So if you think unified builds are your way, I understand and appriciate that!
For me, on the other hand, it looks like this: I've come from bacon to 3t, I have no 3 and my personal policy is building only for devices I have my hands on. I like OOS - indeed for me it's one of the best stock roms I've ever seen - but it lacks some features I learned to love in cm times, like privacy, app-ops, automatic do not disturb rules and much more.
I lurked some time around in the threads, build OSS from source and tried to dig in the sources. I tried hard to understand the differences of 3 and 3t. What I found in most of the sources was @Sultanxda's and @Graraks patches to load different adreno firmware.
Then I pulled blobs from OOS-4 for 3t and ran diff against the onplus3 blobs from themuppets. I don't say they were completely different, but they differed in about 4/5th of the files (as you can see in this commit: https://github.com/nvertigo/proprie...mmit/17c7609f79167c02041736306b18f52bca5b9ac6). Then I compared the specs of 3 and 3t - surprise: they are different...
Let me give you an example: the battery is different. That means power_profile.xml has to be different for 3 and 3t, too. If you got traped by the hoax, that the 3t comes with a 3000 mAh battery read this.
So I decided to build a rom with all blobs beeing native and configuration optimized for 3t. To my surprise my first attempt ended in a build so smooth with all features I missed, that I fell in love instantly. So I spent even more time on this, added busybox (not as toybox' replacement, but just as binary in /system/xbin/busybox) and used native qcom SnapDragon llvm for CLANG and UBERTC/linaro for kernel.
At this point @mad-murdock tested the build. I wasn't sure about my own perception, because it was my own rom. He ensured me though, it was stable and smooth. So I was happy with the build.
I don't say it's not possible to achieve all this with an unified build. But I'm absolutely sure, that 3 and 3t differ in more aspects then graphic blobs. These differences need to be addressed in unified builds (RR seems to be a step ahead compared to laos). This is far behind my scope (and to stick to my personal policy to build only for devices I have hands on, I would need to get a 3 and a second sim), so here we are: LineageOS for 3t only.
I surely don't want to start a religous debate on "the right way" of building roms for 3 and 3t - there are always many ways to build awesome roms - this is just my way for the moment.
Known Issues
General known issues
If you want to report an new issue provide logs. If you don't know what logcat is or how to deal with it this posting is for you.
The following stroked isaues may or may not be present on Snap - to avoid all Snap hazards, NLOS is shipped with Camera2 (atm I recommend the modded Google Camera from Modded Google Camera with HDR+, 60FPS video and Slow Motion by @S4turno or the modded OnePlusCamera from my downloads - do NOT! install both the same time: it's GCam XOR OPCam:
camera: continuous shot not working select sports mode[/STRIKE]
camera: HDR on front camera just produces a green picture
camera: front camera in HAL1 mode: one of the first two or three shots, let the camera server crash - following shots are perfectly ok til next reboot.
Workarounds:
The ugly one: use OnePlusCamera or Snap and take pictures (mostly one to three) til camereserver crashes, wait 7 seconds and use your prefered HAL1 cam as usual.
The more elegant one: use a cam app that supports HAL3 (api2) like opencamera by @mdwh (recommended: it's opensource and free of charge - don't forget to donate, if you decide to use it on a regular basis) or one of the closed source apps.
camera: first still while taking a video is broken.
sRGB-Mode is not setable from Settings; workaround: https://forum.xda-developers.com/showpost.php?p=70799426&postcount=53You find sRGB as color mode in LiveDisplay
encrypting an unencrypted data partition is currently NOT working - no matter if ext4 or f2fs. Workaround: restore your oos nandroid, encrypt your phone by setting pin or password to something new, and tap on "secure phone on startup" (might not be the accurate phrase, but you know, what I mean when you see it.)
Gapps known issues
You can easily avoid all of this - and propably much more - if you stick to the recommended gapps package!
The notification slider isn't working.
webview is stuttering and lagging
first time setup can't be completed.
dialer is not working as expected
unpredictable behavior of UI
random (or not so random) fc's of system components (apps and/or services)
I did not flash the correct Google Apps version!
Some Google App versions overwrite critical system components, which leads up to all kind of random issues. One of the most obvious issues, is gapps preventing Lineage setup to start, and will instead guide you through the AOSP Setup Wizard. This will cause issues, amongst others the Alert Slider on the left side of the phone will not work. If you encounter this or other problems, you need to wipe system, data and caches, before you reflash the ROM and the suggested version of Google Apps linked in the download section of OP. After initial setup, the google apps will update via playstore so don't worry about that. With this package installed, you can install all your missing gapps from playstore. The great advantage is, that the added gapps from playstore will be installed as user-apps and therefore won't mess up your system.
HOWTO: build this rom from source
See the README in
https://github.com/nvertigo/local_manifest
UPDATED: Camera Mods
To give the user more freedom of choice, OnePlusCamera and onePlus Gallery are removed from the rom. In this posting I provide additionally installable apks, to allow the user to install them as any other apk.
@kxzxx's mod (use to get the same cam setup we use for four months - callbacks removed):
https://drive.google.com/open?id=0B_f72wz8rwc6SV9VTXRXMVdfeFk
This should work on all laos based roms. Recommended, if you want the very same setup as before.
Update Version 1.5.0 (ob14): https://drive.google.com/file/d/0B_f72wz8rwc6dEpHUGVlQ2hYY28/view?usp=drivesdk
Plain stock OOS gallery - op3/t (dng support):
https://drive.google.com/file/d/0B_f72wz8rwc6QWNWUDhpQWhJa3M/view?usp=drivesdk
This should work on any rom without OnePlusGallery not installed.
Update Version 1.8.4 (ob14): https://drive.google.com/file/d/0B_f72wz8rwc6S2VkV1VsaHNNYzA/view?usp=drivesdk
Some candy:
Plain stock OOS 4.5.x cam - op5 (sometimes glitchy, flash not working reliable - raw working [set iso and shutter manually in pro-mode]):
https://drive.google.com/file/d/0B_f72wz8rwc6UzBoUlNhT0NabWs/view?usp=drivesdk
Outdated and obsoleted - just for reference: If you want to check this out on our current rom, needs to remove OnePlusCamera&Gallery first. Flash this in recovery:
https://drive.google.com/file/d/0B_f72wz8rwc6b2xUSUZQMXNuck0/view?usp=drivesdk
@homebuilders and all interessted people:
This is neither a HOWTO, nor a script (op3t/op5 is hardcoded, because I havn't parsed arguments), but gives at least an impression on what is needed to make a other roms system app an user installable app. As you can see, I sign the apk with laos test keys. The key does not really matter, as long as the apk is signed at all.
Code:
cat build.sh
#!/bin/bash
S1="-decompiled"
S2="-unaligned-unsigend.apk"
S3="-unaligned.apk"
S4="-v1.4.0-op3-nvertigo.apk"
for i in $*; do
apktool d -f -v -t oxy -o $i$S1 $i.apk
cp -av lib $i$S1
apktool b -f -o $i$S2 $i$S1
../.signing/sign.sh $i$S2 $i$S3
zipalign -f -v 8 $i$S3 $i$S4
done
cat sign.sh
#!/bin/bash
java -Xmx2048m -Djava.library.path=/mnt/export/data/src/cm14/out/host/linux-x86/lib64 -jar /mnt/export/data/src/cm14/out/host/linux-x86/framework/signapk.jar -w /mnt/export/data/src/cm14/build/target/product/security/testkey.x509.pem /mnt/export/data/src/cm14/build/target/product/security/testkey.pk8 $1 $2
@kxzxxx: if you still read here and if you have plenty of (spare-)time, would you be so awesome to look into op5 cam for callbacks on flash? I tried based on op3 cam, but failed. No need to hurry. Thanx in advance.
You should also checkout these:
MI5 camera mods (by @Arnova8G2): https://forum.xda-developers.com/mi-5/themes/app-collection-camera-modded-t3591177
OxygenOS Camera Mod (by @siankatabg): https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
Pixel Google Camera: https://www.xda-developers.com/google-camera-hdr-ported/
nvertigo67 said:
Since my time is quite limited till end of October, @mad-murdock is providing you with new builds.
Click to expand...
Click to collapse
I build these ROMs from source for quiet a while for myself. So I am the build slave or OP now. I use nvertigo's sources unchanged. Using the 141-work branch - in case you want to build yourself.
Mirror: posting #2. I assume @m0d hipp¥ will update it like usual.
Build 20170522
Some advice on Theme/OMS/Substratum users. You can ignore this, if you don't use themes:
Make sure you disable all overlays in substratum BEFORE dirty flashing.
If you ignore this, you get a force close of system-ui on boot.
To fix such errors, flash /sdcard/substratum/SubstratumRecovery.zip in TWRP. This will remove any OMS overlays and allow you to boot again.
To enable your Theme again, you must BUILD it, not only enable. Enabling it without building will make system-ui force-close again and requires you to flash the recovery zip in TWRP.
Changelog
I am a bit confused about changes. This part will be updated soonish.
Updated to latest LaOS and OMS sources.
Note on firmware: This build requires OOS beta 7 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 7 firmware first. It was included for users having flashed lineage-14.1-20170518-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170522-UNOFFICIAL-mad-murdock-oneplus3t.zip
MD5: 4f6208f56b4a1fce39a34830f03ec294
Mirror: posting #2
Happy flashing!
Experimental Build 20170426
This is an updated experimental build with OMS. See nvertigo's post of last build for details.
Some advice on Theme/OMS/Substratum users. You can ignore this, if you don't use themes:
Make sure you disable all overlays in substratum BEFORE dirty flashing.
If you ignore this, you get a force close of system-ui on boot.
To fix such errors, flash /sdcard/substratum/SubstratumRecovery.zip in TWRP. This will remove any OMS overlays and allow you to boot again.
To enable your Theme again, you must BUILD it, not only enable. Enabling it without building will make system-ui force-close again and requires you to flash the recovery zip in TWRP.
Changelog
I don't have changes. Shame on me. Rebooted Windows for gaming.
Of course updated to latest LaOS and OMS sources.
Note on firmware: This build requires OOS beta 5 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 5 firmware first. It was included for users having flashed lineage-14.1-20170422-UNOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip
MD5: 8aa8df7ed35999ec47c8ea23d659f78e
Mirror: posting #2
Happy flashing!
Build 20170411
It's that time again to update your ROM. No side-effect reported from last test-build, so we consider it stable.
Changelog
No changes, except updated to latest LaOS sources
Note on firmware: This build requires OOS beta 4 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 4 firmware first. It was included for users having flashed lineage-14.1-20170401-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t.zip
MD5: 6b76cd3366c9beb3df1aa30d6a8deb2a
Mirror: posting #2
Happy flashing!
Thanks!!
your rom is best!!
Thanks guy ! Great
Great to see you started your own thread afterall. Going to flash this today, also because @mad-murdock approves this rom so much . Can't wait!
edit: found a small typo in the instructions. Check the year @nvertigo67 :
"Install the Google Apps addon package (Optional. Use opengapps nano package from 20160120)"
Update: Wipe before you install.
You might want to know that I flashed this ROM dirty over koenkk's ROM.
I have no problems doing so. Be advised though, that this isn't recommended and can result in stuff not working. You can try a dirty flash, if it works, fine. If not, just wipe as in official instructions.
Just flashed your Rom. Fluent and feels natural! Thanks Developer
Glad to see you posting a thread on XDA
mad-murdock said:
You might want to know that I flashed this ROM dirty over koenkk's ROM.
I have no problems doing so. Be advised though, that this isn't recommended and can result in stuff not working. You can try a dirty flash, if it works, fine. If not, just wipe as in official instructions.
Click to expand...
Click to collapse
I like experimenting, I like dirty flashing, I like custom kernels (indeed I'd love to see Boeffla cm/laos-14.1 kernel) and I want to encourage everybody to home-build, experiment, dirty flash, try mods, kernels or what ever: he, who never bricked an android device, has not flashed hard enough.
The only problem with that is support: I can't test any combination, reproduce issues and so on. Also if everybody reports on his very own combination, the thread becomes unreadable/unundestandeble.
So I kindly ask you to try whatever you want; but if reporting an issue, stick to OP rules, please.
HOWTO: build this rom yourself
The "homegrow"-howto is here in the file named README.
nvertigo67 said:
break for me now.
Click to expand...
Click to collapse
Well deserved. Take care.
Has anyone installed this ROM after formatting system and cache to F2FS?
System and cache as f2fs is rare. No idea which Roms support this. I would say, just try, if it won't work, format system and cache. It's no extra effort.
Just make sure not to reboot recovery while system is blank, since TWRP pulls crypto lib from system
nvertigo67 said:
I surely don't want to start a religous debate on "the right way" of building roms for 3 and 3t - there are always many ways to build awesome roms - this is just my way for the moment.
Click to expand...
Click to collapse
Hi. I like the way, that you chose. Hope you will doing it in future. Like and you, I came from oneplus one.
Btw. What about sRGB mode? Is it here ? I'm hate oversaturated colors. After opo it's looks so ****ty..
sorry to be a pain but how long does it take for first boot? I've been waiting for 15 mins so I'm not sure if I've done something wrong...
hassan_1000 said:
sorry to be a pain but how long does it take for first boot? I've been waiting for 15 mins so I'm not sure if I've done something wrong...
Click to expand...
Click to collapse
it depends on how many apps you had installed. still, 15 minutes sounds pretty long. did you dirty flash without wiping? if so, you should probably go and wipe now.
{
"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"
}
Dorimanx OP3/T Kernel for STOCK 7.1.1 OOS/H2OS 4.1.6+7+4.5.1 + BETA!
NO > Oxygen 3.x.x or CM/LineAge/OREO BETA SUPPORT!!! GO AWAY NOW!
My PM box, is for Emergency ONLY! do not send me PM's just because you cant post! that is lame, post something useful and post in thread.
My kernel was based on OP3/T Stock Kernel 4.1.6+7+4.5.0 + BETA 15/24 Source.
Kernel Tree is 3.18.140, + OP3/T and CAF updates + my tweaks and lots of tuning!
Global Credits!
Flar2 for many kernel mods
Cyanogen/LineAge/Code Aurora for many kernel mods
Andip71
Franciscofranco
SultanXDA
OP3 Devs for Stock kernel base!
To all my sources in GITHUB!
Linus Torvalds for Linux source!
WHAT INSIDE:
Kernel support OOS/H2OS 4.1.x
Kernel compiled with Linaro GCC 7.1.1 Android Bionic 64Bit adapted for OP3/T
Kernel includes all new security patches.
Kernel updated up to 3.18.140 build.
Kernel includes all original last 7.1.1 changes by OP3/T Devs.
Kernel operate in 300HZ + all needed fixes to do that.
Kernel has DASH charge and USB Fast Charge (USB mode up to 900mA with MTP on)
Kernel support charging up to 2500ma with any charger! stock locked to 1500ma
Kernel has swipe to wake features by @flar2 (up,down,right,left,and dual tap).
Kernel include Sweep2Sleep allows sweeping from right to left and backwards!
on soft buttons to turn off the screen. by @flar2
Kernel has support for screen color change app. (KCAL Interface).
Kernel has support for touch keys light delay, default 6sec. by @andip71
Kernel include KGSL fixes and reworked GPU driver (use 133MHz min freq to save juice, goes to idle @ 100MHz)
Kernel include all latest patches from Code Aurora source for 3.18.y
Kernel include Enhanced TCP methods
Kernel include IPA/TIMERFD/WIFI/NETLINK wakelocks removal code by @franciscofranco
Kernel include open source QUALCOMM Wi-Fi driver updated to max without debugs.
Kernel include advanced binder driver from main line 4.10.y kernel.
Kernel include CDROM emulation on mass_storage (compatible with DriveDroid 0.10.18+)
Kernel include latest F2FS driver for 3.18.y with fixes for speed and stability.
Kernel include ZEN,NOOP,BFQ,DEADLINE,CFQ,FIOPS,SIO I/O govs tuned for SSD.
Kernel includes Elementalx, Blu_active, Interactive, Conservative, Ondemand, Performance CPU GOVS.
Kernel support FSYNC mode for FS. (Off by default)
Kernel includes ARM enhanced performance and battery patches
Kernel support Backlight Dimmer feature.
Kernel supports CPU OverClock/UnderClock for both clusters.
Kernel support thermal driver tuning, max heat for cores.
Kernel includes advanced crypto drivers and latest qseecom decryption driver.
Kernel includes updated EXFAT and FUSE + NTFS drivers.
Kernel support for not forcing encryption and verity checks.
Kernel includes support for CIFS driver.
Kernel includes fast finger print sensor mod when screen is off.
Kernel includes support for Haptic Feedback (vibrate) tuning (more/less)
Kernel includes massive code update for sound driver, and @flar2 sound/mic gain control interface.
Kernel include boost to I/O by mounting partitions with optimized flags, and updated MMC driver.
Kernel includes updated BT and NET/PPP/VPN/DATA drivers.
Kernel include mode to ignore home and touch keys when finger is pressed against the screen.
Kernel includes Aroma Installer for easy install with few simple changes that can be selected.
Kernel includes many patches to camera, GPU, and screen drivers.
Kernel has OTG enabled by default internally.
Kernel has Notification LED Control driver by @andip71
Kernel include usage of power efficient workqueues in many drivers by @franciscofranco
Added Support For INIT.D Scripts see /data/init.d folder
Kernel will switch to NOOP I/O Sched during screen Off time to save power. by @Sultanxda
Kernel will boost CPU frequency when screen wakeup to improve user experience, by @Sultanxda
Kernel will set max allowed apps in RAM to 60 from 32
Kernel will add advanced busybox binary in /sbin/busybox for advanced users and my scripts
Known BUGS!
Post reports, i will fix.
Standard disclaimer:
By installing this kernel YOU will take full responsibility for any damage to your device!
Hardware or software! no one forcing you to install it.
So please do not blame me if you read wrong! or didn't read at all the instructions that i have written for YOU.
But you can feel SAFE to use it, as I test every release on my phone!
Before I publish it for download.
Your warranty will be void by installing custom kernel as my.
Kernel Sources:
KERNEL GITHUB
TO DOWNLOAD GO DOWN!!! YES MORE DOWN...(do i need to repeat?)
How To Install:
You will need to have device with Latest Recovery installed! Please install the 3.1.1.x BUILD!
>>>Here is the Recovery you need!<<<
Old recovery can corrupt your DATA partition as my kernel using latest F2FS driver. new recovery has updated driver.
YOU MUST UNLOCK OEM BOOTLOADER!!! OR YOU WILL BE STUCK ON BOOT!
Refer to other threads for recovery install process and for oem bootloader unlock.
Download kernel, upload it to your SDCARD, anywhere.
Always have STOCK Kernel for your ROM!
Reboot to Recovery.
THINK AGAIN! did you made backup? NO!!!!??? DO IT NOW!
If you had any other Custom kernel, Install STOCK kernel or dirty flash your ROM,
to clean any trace from other kernel. then install ROOT/Magisk if you wish! then install my kernel ALWAYS THE LAST.
Do not clean any cache or dalvik (needed for ROM only!).
Reboot!
If you wish to UNINSTALL my kernel, there is a uninstaller ZIP for you.
it's will remove all ramdisk changes, and install last 4.1.6 stock kernel, preserving ROOT if was installed!
Have Fun and report.
Honored Fearless BETA Testers! without them i would be lost in dark kernel space:
dimberr
Diechel
misterepicwin
vampire36
RyperX
siggey
bipinbedi
Chris7
Leicxan
Radon94
Donation Board:
ME donated 150+ hours to update stock to now.
Dimberr HUGE Donation!
Betadr X2
Diechel
RyperX
misterepicwin
Cultofluna
Andrej666
Aagato86
Thread Rules:
This is a Kernel development thread ONLY.
Allowed:
1) Any kernel reports with LOGS in case of crash from /sys/fs/pstore/console file.
2)Any satisfaction reports with picks and suggestions about kernel.
3)Any questions related KERNEL.
4)Any important information that may improve this kernel.
5)Any issues you have with STOCK Stable ROM. this what i use and test, all the rest are BONUS.
6)Sound mods and root access. i think it's good information that can improve user experience with my kernel.
Not Allowed:
1) extreme off topic about some ROM mods, APPS, Magisk non ROOT modules,
2)Comparing kernels, other vs other, my vs other.
3)Trolling!, Spamming, hate toward other users, flaming, feeding trolls. posting not in English, NOOB calling other users.
4)Disrespect of any beta tester listed in OP.
All recognized developers Allowed to manage there own threads without bothering forum administrators.
I can, and I will, remove all not allowed posts without blinking.
Mirror #1 by willflint
Mirror #2 by GITHUB!
Info for Web Hackers,
in my mirrors, there is nothing to take!
My work is public and for the people!
Please let my mirrors work in peace.
Thanks.
Please consider supporting my work by tipping
Mirror #1
Mirror #2
Change logs:
26/6/19
Kernel 3.5 Stable
* Merged linux code update from 3.18.137 to 3.18.140.
* Merged mega patch for F2FS file system driver.
31/3/19
Kernel 3.4 Stable
*Merged all main line linux patches up to 3.18.137
*Merged latest updates to WIFI Driver LA.UM.5.5.r1-09000-8x96.0
16/4/18
Kernel 3.3 Stable
*Reverted some touch screen mods to fix few issues.
*Merged 3.18.85 to 90 from main line.
*Merged aosp updates.
*Merged F2FS Updates.
28/11/17
Kernel 3.2 Stable
*Merged patches 3.18.80+81+82+83+84!
Including: ARM64,BLOCK,I2C,FS,LIB,SECURITY,SOUND,TTY,USB,
*Merged latest F2FS driver updates from source.
*Merged many updates to BINDER code for CAF source.
*Merged mods to touch screen driver by sultanxda, great work for optimization and power save.
*Merged new updates from CM14 including: MDSS,VIDC,
DIAG,CRYPTO,NET,ADSPRPC,SCSI,SOUND,POWER,IPA,MMC,LOCKING core.
*Merged latest WIFI driver updates. ver 06300
08/11/17
Kernel 3.1 Stable
*Merged main stream patches 3.18.74 to 3.18.79
Including: BLOCK,CRYPTO,MMC,NET,TTY,USB,FS,BASE,SECURITY,HID,IOMMU,SOUND,KERNEL CORE,I2C,LIB,SCSI.
Tons of changes! it's 400 commits compressed to patches.
*Merged optimizations to BINDER code from CAF.
*Merged Camera,MMC,KGSL,SOUND,IPA,MDSS,DIAG,QCOM,USB,FS updates from CAF.
*Merged latest Qualcom WIFI driver v06100
06/10/17
Kernel 3.0 Stable
*Reverted changes to SDCARDFS to get rid of bug with folders in storage.
Beta team reporting that all good now.
*Merged patches 3.18.72+73 including:
BLOCK,NET,PCI,SCSI,TRACE,ARM64,FS,SECURITY fixes.
*Merged BINDER updates from CAF and Mainline kernel.
*Merged wakelocks shut when drivers shift operations, by franciscofranco
26/09/17
Kernel 2.9 Stable
*Merged AOSP and CAF updates including:
FS,BlueTooth,Trace,DIAG,Thermal,ASOC,CAMERA,MDSS,
QSEECOM,KGSL,IPA,SOUND,ARM64,TIME,BINDER,NET,
QCOM,SDHCI,USB.
*Merged patch 3.18.71 including:
SCSI,USB,FS,Kernel Core,MM.
*Merged OP3 Dev BETA OBT24+OBT15 color updates.
*Merged latest WIFI driver updates.
*Merged massive update to F2FS from 4.14.y kernel
*Merged latest updates to SDCARDFS from CAF and AOSP.
*Merged latest OEM OP3 4.5.0 kernel updates.
09/09/17
Kernel 2.8 Stable
*Merged OP3/T BETA branch OBT23+OBT14
It's updates to colors switch Srgb and nightmode.
*Merged main line update 3.18.68+69+70!
Many changes to: FS,Kernel Core,NET,BT,SOUND,ARM64,SCSI,LIB,MM
*Merged updates to BINDER CORE from Aosp and main line source.
*Merged updates to F2FS driver.
28/08/17
Kernel 2.7 Stable
*Added busybox mount function to help with working with /system folder.
*Merged latest patches from CAF and AOSP including:
CPUFREQ,DIAG,LOCKS,USB,CAMERA,SOC,NET,KGSL,SOUND,I PA,WIFI updates.
*Merged 3.18.67 patch including: NET,SCHED,Kernel CORE,MM,SOUND updates.
*Fixed selinux not enforced if Magisk installed on EXT4 Data partition!
23/08/17
Kernel 2.6 Stable
*Merged patches 3.18.64 to 3.18.66
Including many many updates to all core drivers and functions.
See GIT if you like to dig in too code changes.
*Merged many updates from CAF and AOSP branches for our device.
*Merged latest OEM OP3/T 4.1.7 update to kernel. (will work just fine with 4.1.6 and BETA too)
*Added new STOCK 4.1.7 kernel to mirror, and new uninstall zip including 4.1.7 stock kernel.
to install this build on 4.1.7 ROM! make sure you had 4.1.7 stock kernel to get all ramdisk updates by OP3!
06/08/17
Kernel 2.5 Stable
*Merged CAF updates including:
ISP,CAMERA,MDSS,IPA,MMC,USB,KGSL,ION,NET,SOUND,PERF,INPUT,REGULATORS
*Fixed ROM dev ram access to used RAM by apps, no longer show 0B
*Merged updates to F2FS driver from Android dev list.
*Merged OP3 Devs BETA 12 update that focused on color update for night mode.
*Updated Busybox from source.
31/07/17
Kernel 2.4 Stable
*Merged fix for low CPU frequency after deep sleep for short delay.
*Merged Patch 3.18.62 including: CRYPTO,TTY,FS,KERNEL CORE,MM,NET updates/fixes.
*Merged update for F2FS driver from source.
*Merged update to BINDER driver from CAF big improvement in code structure and functions.
Binder is directly responsible in running apps and services, memory allocator.
*Merged patch for android-verity mount check.
*Merged new code that will shrink and compact RAM each time screen goes off after 3sec.
And only once in 15min! This will help to have always fresh and fast device. For very long time of use 150hours+
*Merged fix for QCOM driver to prevent possible memory leak.
*Merged patch 3.18.63 including: POWER DOMAIN,OF,SPMI,PCI,USB,FS,KERNEL CORE,NET, BT+NFC,SOUND.
*Merged new update to WIFI driver LA.UM.5.5.r1-05400-8x96.0 open source perfect module!
*Merged massive fix by Awesome DEV @Sultanxda for debug fs code.
*Compiled new Linaro GCC 7.1.1 = new libs and Android Bionic Core, first time such thing was possible!
And compiled Kernel with this massive native android toolchain!
Noticeable speed and global stability feeling!
My BETA team is impressed! 3 days no words in our discord channel hehehe
*Updated Busybox 1.28.0 from source using GCC Linaro 7.1.1
Now it's possible to use OTA Kernel Update App by @Diechel
It's will auto download kernel, install it via TWRP, and show you the change log
Really cool thing! it's donation app. 1$ feel free to donate, or use the website as before
>>> https://play.google.com/store/apps/details?id=com.diechel.xda.dorimanxota3t.pro <<<
16/07/17
Kernel 2.3 Stable
*Merged latest update to F2FS driver from source. sync with 4.13.y tree.
*Merged fix for min sched windows when kernel using 300HZ.
*Merged CAF patch to fix bugs and security issues in:
CAMERA,MDSS,USB,ADSP,CHARGER,IPA,QCOM,NFC,QCDEV,SOUND
*Merged latest WIFI opensource update LA.UM.5.5.r1-05300-8x96.0
*Merged mods to WIFI driver to reduce battery usage.
*Merged mainline patch 3.18.61 including:
NET,USB,IPC,TRACE,SECURITY
*Merged mod to boost CPU freqs after suspend on wakeup.
*Added SeLinux mode changer in Aroma Installer.
You can set Enforce or Permissive. no apps/magisk modules needed!
*Updated Uninstaller to include selinux mods cleanup.
*Added mount command to be linked to busybox, so apps can remount system and root.
If they are allowed to use ROOT.
09/07/17
Kernel 2.2 Stable
*Merged kernel updates 3.18.59 + 3.18.60
Including USB,FS,Kernel Core,LIB,NET,IOMMU,MM
*Set to deny access from perfd ROM service that can brake CPU gov tuning.
*Tuned Interactive GOV on boot for both cluster,
To deliver great Performance and balanced battery save.
*Tuned Blue_Active Gov default tuning.
*Fixed init.d support from /data/init.d/
*Updated busybox to 1.28.0 made with Linaro gcc 7.1.1 64Bit
*Merged many updates from CAF source for our soc.
Including MDSS,CAMERA,IPA,VIDC,INPUT,QCOM,USB,DIAG,SCHED
*Updated WIFI driver to latest opensource LA.UM.5.5.r1-05100-8x96.0
*Fixed my boot script load on boot to allow better tuning of kernel.
*Fixed not working touch when screen is in half wake state. (liftup, wave gesture)
*Added new driver to allow to limit max freq on both clusters so no other app
or ROM service can set higher. for now not used! and not forced.
I will add controls for it in my app.
*Merged updates to F2FS driver from main source.
*Updated new GCC Linaro 7.1.1 kernel builder 64Bit and made kernel with it.
*Added new controls for CHARGING LIMIT in Aroma installer.
You can set max allowed charge back to 1500ma if you wish!
28/06/17
Kernel 2.1 Stable
*Merged 3.18.58 patch including RAM,USB,NET,FS updates.
*Added overclocking for OP3 Model, one step higher for both clusters, not used by default!
25/06/17
Kernel 2.0 MEGA BOMB Build
Kernel will work with BETA STOCK ROMS!
Including All the in WHAT INSIDE LIST
Tested for long time by fearless beta testers!
And crowned as STABLE.
=============================
XDA:DevDB Information
[KERNEL] Dorimanx V3.4 OP3+T Nougat 7.1.1 STOCK 4.5.1 Tree 3.18.137 [31 MAR] PWR CORE, Kernel for the OnePlus 3T
Contributors
dorimanx, dimberr, Diechel, misterepicwin, vampire36, RyperX, siggey, bipinbedi, Chris7, Leicxan, Radon94
Source Code: https://github.com/dorimanx/DORIMANX-OP3T-KERNEL/commits/master_7.x.x
Kernel Special Features: See What Inside list.
Version Information
Status: Stable
Current Stable Version: 3.4
Stable Release Date: 2019-03-31
Created 2017-06-25
Last Updated 2017-11-28
One for ME :silly:
Some INFO:
ONLY for OP3T!!! do not do this for OP3 model!
If you have Verity Alert on boot that says it's not enforced. and you like to fix it!
Here is how to by @RyperX and @Leicxan
Download modem + firmware 4.02 and the 4.1.6 here:
https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
Reboot to Recovery!
Connect your device to PC with USB cable.
1. Install modem 4.0.2
2. boot to fastboot/bootloader (from recovery menu)
3. apply the 2 commands in this order ("fastboot oem disable_dm_verity", then "fastboot oem enable_dm_verity") using fastboot exe file in your PC
C:\Users\admin>fastboot oem disable_dm_verity
...
OKAY [ 0.031s]
finished. total time: 0.032s
C:\Users\admin>fastboot oem enable_dm_verity
...
OKAY [ 0.032s]
finished. total time: 0.034s
C:\Users\admin>
Click to expand...
Click to collapse
4. reboot directly to recovery again using the volume keys and then power key to select recovery!
5. flash modem 4.1.6! or 4.1.7!
6. reboot
Warning of the verity not enforced is gone.
And one more for me
Great you are here
Lets get the OP3t the same lifetime as our LG G2 had
Let the game begin....
Hmm definitely interesting... Will check this kernel out! Nice work by the way...
Happy to see it public ?
Sent from my OnePlus 3T using XDA Labs
Seems amazing!
Just installed, will edit with small review after few days.
Boom Shakalaka
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
RyperX said:
Great you are here
Lets get the OP3t the same lifetime as our LG G2 had
Click to expand...
Click to collapse
Should be exceptional until at least Q4 2020, bring people nicely to the OnePlus 8/8T
<Deleted>
Congratulations buddy [emoji111]
Congratulations man
Thank you so much.
Daym, how many kernels did you combine into this ? xDD
nice nice nice .... waiting long time for this
good job
want to try it....on my op3t
long long long time ago i had this awesome kernel on my Samsung S3.......Damn.....long time ago
Thanks Dori for the Nougat release
cheers
Can this be made for the op3?
Miksel12 said:
Can this be made for the op3?
Click to expand...
Click to collapse
It's a unified build working perfectly on the OP3.
@dorimanx just wow.
I have never encountered this kind of smoothness with my op3. I'm using Open Beta 18.
Not sure how this kind of level of buttery smoothness is even possible to achieve.
Hands down, this kernel is on whole another level of smoothness for op3.
Thank you so much! Any plans to support LineageOS?
Edit: CPU governor was set to performance by default but still very well performing kernel
First LG G2 with the Dorimanx power and finally with OP3, back to the heaven.
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features and my sources linked below.
Bugs:
VoLTE (IDK How it broke suddenly, but will be looked at)
SELinux
Note:
LineageOS LiveDisplay does work but I recommend keeping it disabled because it causes lags in many cases.
I don't have any proper fix for it. If you want to use the Night Mode, please use a third party app which utilizes the KCAL driver or overlays.
All these builds are 32 bit.
Moto Camera from Google Play doesn't work, so either use a modded moto camera apk or use the camera app built in.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds :
Sourceforge
Root addon :
Latest Stable Magisk Zip
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
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][athene][8.1.0] LineageOS 15.1, ROM for the Moto G4/Plus
Contributors
LineageOS Team of course!
Team athene:
rajatgupta1998
Nikit
lcrd512
golden-guy
Jleeblanch
Our former developers:
vache, rahulsnair, SileshNair, Shreps, regalstreak, ashwin007
Other developers: Alberto97, squid2, flar2, oadam11 , LineageOS team and all other contributors whom I might have missed.
All other friends and supporters in the XDA and Motorola Community! :victory:
Source Code:
LineageOS ROM Source
Device specific sources:
Device tree: https://github.com/rajatgupta1998/android_device_motorola_athene
Kernel source: https://github.com/rajatgupta1998/android_kernel_motorola_msm8952
Vendor blobs: https://github.com/rajatgupta1998/vendor_motorola_athene
ROM OS Version: Android 8.1.0 Oreo
Version Information
Status:Beta
XDA:DevDB Information
LineageOS 15.1 Athene, ROM for the Moto G4 Plus
Contributors
rajatgupta1998, @Nikit
Source Code: http://github.com/lineageos
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Stock firmware
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2020-09-20
Created 2018-03-25
Last Updated 2020-09-20
Changelog Timeline
Major items to be concerned about. Can say the HIGHLIGHTS. Check the commits on my Github for more details.
16 Aug 2020
05 Aug 2020 Security Patch
Bluetooth stack update from Stock O 8.1
Add Qcom ANT+ Blobs
Update aptX, aptX HD Blobs
Update power profile from stock O 8.1
Update few overlays from stock O 8.1
07 April 2020
05 April 2020 Security Patch
Enable some missing kernel configs
Regenerate proprietary-files.txt and follow it
Update ADSP
Build Health HAL
Update Alarm and Health blobs
Fix audio callibration files loading
Update Audio blobs and configs
Remove unnecessary code
05 Jan 2020
Camera delays are fixed upto an extent
LiveDisplay is back but still lags. Since few people tend to use it, enabled it anyway. But if you get irritated by the lags, keep it disabled.
December 2019 Security Patches are here
12 Oct 2019
October Security Patches are here
08 Sep 2019
05 September 2019 Security Patch
25 Aug 2019
Kill LiveDisplay (Only Outdoor mode will work from now on, removed the night mode color shift because it causes severe lags in many cases)
Switch to QTI perf stack from stock O
Also add QTI I/O Prefetcher.
Switch back to Motorola's stock kernel for now with basic driver functionality like KCAL Support and fingerprint as home button.
08 Aug 2019
August Security Patch
Fix loading of IMS Shim
Minor code cleanup
04 Aug 2019
Fix video recording and QS Flash light toggle finally.
07 July 2019
July Security Patch merged
Disabled some useless logging
30 June 2019
Update and fix the DRM HAL for playing like Netflix
24 June 2019
Use a binderized biometric HAL
Update fingerprint blobs and JARs from stock O
Update keylayout for FPC1020 Touch fingerprint sensor driver from stock O
Add a custom trim value from stock O
Use CAF QTI Power HAL now
Update Media DRM HAL and QSEECOM
Update ADSP Blobs from stock O, hence the ROM now uses updated Qualcomm's Hexagon DSP blobs for Oreo.
Enable and update Media CAS HAL, Gatekeeper and Keymaster HAL
Update the blobs for the above mentioned HALs
Enable Pinner service: Pins key files into memory to prevent having to fetch from flash after boot. Improves system performance by preventing page cache thrash.
Switch to the Motorola's stock O kernel source (No, Video Camera doesn't work right now :3 )
Merge latest sources from CAF: LA.BR.1.3.7-05010-8976.0
Merge all the relevant patches from AOSP (Google's kernel/common for linux-3.10)
Linux upstream on top of this with msm-3.10 as 3.10.108
All updates to various drivers like cpufreq, mdss, audio and more and more.
Various fixes and updates to the Wifi drivers from CAF Pie sources for Qualcomm Atheros Prima/Pronto WLAN module.
Various patches to the memory subsystem and updates to stuff like ZRAM, ZSWAP, VNSWAP
Updates for Pie's ext O_TMPFILE support
Enable support of SDFAT driver v2.1.8
Multiple changes to the binder interface, kernel functions and other upstream patches.
16 June 2019
June 05 2019 Security Patches
LineageOS upstream
20 April 2019
* Update audio, display, graphics and actuator blobs from stock O
25 March 2018: Initial Changes from Nikit's build
* Merge 5 March 2018 security patch with AOSP 8.1.0_r18 release
* Increase ZRAM to 1 GB
* Disable Speaker Protection
* Disable Auto Brightness and Live Display on first boot
* Fix Safetynet temporarily : Use walleye's (Google Pixel 2) build fingerprint.
* Enable Spectrum Support and port Lightning Blade to Oreo
* Add sound control (maybe broken)
* Allow home button to be changed for various actions.
* Add more CPU frequencies.
* Disable Wakelocks by default
* TCP Congestion Avoidance controls ( not tested )
* Update VoLTE properties
* Use LZMA Compression for Recovery Ramdisk
* Disable add_random from kernel. Not required on SSDs. (eMMCs in our case)
* Enable Arch Power
* Adreno idler ramps down more aggressively now
* Enhance linux topology for multicore decision making
* Enable Arch Power
* Some speed and time efficient changes :3 hard to explain here.
* LineageOS upstream
* Use latest HALs from CAF release LA.BR.1.3.7-03810-8976.0
Reserved
Screenshots
@Nikit Just to confirm, this is correct?
And @rajatgupta1998 when you say "take over" do you mean that nikit is stopping? And can I help out? I have got much of the selinux going on my thread.
Sent from my athene using XDA Labs
hackintosh5 said:
@Nikit Just to confirm, this is correct?
And @rajatgupta1998 when you say "take over" do you mean that nikit is stopping? And can I help out? I have got much of the selinux going on my thread.
Sent from my athene using XDA Labs
Click to expand...
Click to collapse
Yep I have his permission to continue! Also, SE Linux is not on the top most priority right now for me. But yes, surely SELinux will be set to Enforcing soon. Omni and probably your build got it to boot, so yeah; I'll look over it. Hit me up on telegram or email :good:
hackintosh5 said:
@Nikit Just to confirm, this is correct?
And @rajatgupta1998 when you say "take over" do you mean that nikit is stopping? And can I help out? I have got much of the selinux going on my thread.
Click to expand...
Click to collapse
Yes. I don't own this device anymore, so @rajatgupta1998 will continue the development from now.
Ok, thanks for the confirmation!
Sent from my athene using XDA Labs
---------- Post added at 12:20 PM ---------- Previous post was at 12:11 PM ----------
What is "lightning blade / spectrum"
Sent from my athene using XDA Labs
rajatgupta1998 said:
Screenshots
Click to expand...
Click to collapse
can you remove that device is HD capable notification please? & Thanks for the great work to you and Nikit...!
Any chance of getting gcam HDR+ working.
This build has memory leak fixes?
hackintosh5 said:
What is "lightning blade / spectrum"
Click to expand...
Click to collapse
Take a look here, this should explain it.
https://github.com/rajatgupta1998/a...mmit/9e47c5bdff8d5eaed4716b53a9650bfce239031c
BTW maybe you could build an building aliance and help out togehter...
Sent from my Moto G4 using XDA Labs
sgspluss said:
Take a look here, this should explain it.
https://github.com/rajatgupta1998/a...mmit/9e47c5bdff8d5eaed4716b53a9650bfce239031c
BTW maybe you could build an building aliance and help out togehter...
Click to expand...
Click to collapse
Ok, looks like this will need LOTS of work to have sepolicy.
@Rajagupta1998 two things. Can I call you a shorter name as I'm on mobile?, and it would be great to form an "alliance" if you are cool with it!
Sent from my athene using XDA Labs
An aliance is just an idea, bundle both knowlegends in one rom is better, than build 2 roms with different bugs.
Just a thought but you know what you do
Sent from my Moto G4 using XDA Labs
Can i dirty flash this over Nikit's build? I know it's better to clean flash, just asking
Josercl said:
Can i dirty flash this over Nikit's build? I know it's better to clean flash, just asking
Click to expand...
Click to collapse
Yes, you can as it is based off the same sources, although much stuff may not work.
Sent from my athene using XDA Labs
Josercl said:
Can i dirty flash this over Nikit's build? I know it's better to clean flash, just asking
Click to expand...
Click to collapse
hackintosh5 said:
Yes, you can as it is based off the same sources.
Click to expand...
Click to collapse
Not really recommended. Lots of changes from Nikit's build. Check post 2 for details.
The One Plus Camera does not work flawllessy i ger Green Photos and iwhen i tap the preciew of the photn i took it says no photos
Notification bar drop down lags event after turning off live display.
I'm too tempted, is it daily driver capable?
teckgiik101 said:
I'm too tempted, is it daily driver capable?
Click to expand...
Click to collapse
Based on other 8.1 ROMs this one Is pretty good. Same flashlight issue that is on the other ROMs and you can fix the memory leak by making a reboot when its neccesary. Also, the implementation of Spectrum Is helpful.
Any other doubts, ask me, im on it and i will till tomorrow.
CRUEL KERNEL S10 V2.3
The development moved to this thread. From V3 kernel supports multiple devices.
Introduction
This kernel is based on BTA8 samsung sources. Only G973F device for now. It is possible to use it on BSKO, BSL4, BTA8 firmware. All sources are open on GitHub.
Continuous integration with GitHub Actions is set up. This means you can customize the kernel from browser and build the version suitable for you without leaving the browser (see сustomization section).
Features
Customizable build with config presets
Only part of samsung security features disabled (DEFEX, Process Authentification, root restrictions)
Switchable SELinux (by default it's locked in "always enforcing" mode in samsung sources)
Built-in in Magisk
Wireguard for VPN
CIFS for SMB
Iptables TTL and HL editing modules for bypassing tethering restrictions
Build commands (configuration presets) used for V2.3 kernel:
Code:
$ ./build mkimg name=CRUEL-V2.3-BTA8 +magisk +nohardening +wireguard +ttl +cifs
$ ./build mkimg name=CRUEL-V2.3-BTA8-CANARY +magisk+canary +nohardening +wireguard +ttl +cifs
Installation Instructions
First of all, TWRP Recovery + multidisabler should be installed in all cases. This is a preliminary step. Backup your existing kernel. You will be able to restore it in TWRP Recovery in case of any problems.
Dowload an *.img file and
With TWRP: Reboot to recovery. Install > Install Image > CruelKernel.img > BOOT.
With Heimdall: Reboot to Dowload mode.
Code:
sudo heimdall flash --BOOT CruelKernel.img
With FK Kernel Manager: Flasher > Manual Flasher.
ChangeLog
V1 is based on BSKO sources and was privately used. You can find V1 by the link.
V2 is based on BTA8 sources. nohardening, nohardening2, cifs configuration presets added.
V2.1 is for internal use only (testing release) +nohardening preset activated by default
V2.2
Canary Magisk updated to 20305 version
MALI_KUTF kernel driver removed (it's required only for kernel developers)
Pin code problem fix (thanks geiti94)
+nohardening (disable samsung protections)
V2.3
Canary Magisk updated to 20306 version
Small fixes for image format
Downloads
CruelKernel-G973F-BTA8-v2.3
CruelKernel-G973F-BTA8-v2.3-CANARY
Sources
How to customize the kernel build
It's possible to customize the kernel and build it from the browser. First of all, create and account on GitHub. Next, fork this repository. Switch to the "Actions" tab and activate GitHub Actions. At this step you've got your own copy of the sources and you can build it with GitHub Actions. You need to open github actions configuration file (.github/workflows/main.yml) and edit it from the browser. For example, to alter the kernel configuration you need to edit lines:
Code:
- name: Kernel Configure
run: |
./build config name=CRUEL-V2-BTA8
+magisk
+ttl
+wireguard
+cifs
You can change the name of the kernel by replacing name=CRUEL-V2-BTA8 with, for example, name=my_own_kernel. You can remove wireguard from the kernel if you don't need it by changing "+" to "-" or by removing the "+wireguard" line and "" on the previous line.
Available configuration presets can be found at kernel/configs folder. Only the *.conf files prefixed with "cruel" are meaningful. For example:
magisk - integrates magisk into the kernel. This allows to have root without booting from recovery. Enabled by default.
magisk+canary - integrates canary magisk into the kernel.
ttl - adds iptables filters for altering ttl values of network packets. This helps to bypass tethering blocking in mobile networks.
wireguard - adds wireguard VPN module to the kernel.
cifs - adds CIFS (SMB) support.
nohardening - removes Samsung kernel self-protection mechanisms. Potentially can increase the kernel performance. You can enable this config if you face rooting or some other kind of restrictions. Other kernels usually use settings from this config by default. It's safe to enable this config, it just makes your system less secure.
nohardening2 - removes Android kernel self-protection mechanisms. Potentially can increase the kernel performance. Don't use it if you don't know what you are doing. Almost completely disables kernel self-protection. Very insecure.
nodebug - remove debugging information from the kernel.
300hz - increases kernel clock rate from 250hz to 300hz. Potentially can decrease response time. Disabled by default, untested.
1000hz - increases kernel clock rate from 250hz to 1000hz. Potentially can decrease response time. Disabled by default, untested.
For example, you can alter default configuration to something like:
Code:
- name: Kernel Configure
run: |
./build config name=CruelCanary
+magisk+canary
+wireguard
+nohardening
After editing the configuration in the browser, save it and commit. Next, you need to switch to the "Actions" tab. At this step you will find that GitHub starts to build the kernel. You need to wait about 25-30 mins while github builds the kernel. If the build is successfully finished, you will find your boot.img in the Artifacts section. Download it, unzip and flash.
To keep your version of the sources in sync with main tree (following updates), please look at this tutorial.
Support
This thread. Feature requests accepted.
Telegram (testing and intermediate releases).
GitHub Pull Requests if you want to contribute.
Credits
Samsung for kernel sources
topjohnwu for Magisk
geiti94 for showing that it's possible to built-in Magisk into the kernel. Initially I experimented with ASIG kernel, but ASIG+Magisk on ASIG firmware just stucks on boot with an SELinux initialization problem. At that time I doubted that built-in Magisk will work.
geiti94 for his help and advices
franciscofranco for FK Kernel Manager
XDA:DevDB Information
CRUEL KERNEL S10 , Kernel for the Samsung Galaxy S10
Contributors
evdenis, evdenis
Source Code: https://github.com/CruelKernel/exynos9820-beyond1lte
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: v2.3
Stable Release Date: 2020-02-12
Created 2020-02-10
Last Updated 2020-03-16
Reserved
How to build the kernel locally on your PC
This instruction assumes that you are using Linux. Install: mkbootimg, heimdall (if you want to flash the kernel with it).
Next:
Code:
$ git clone https://github.com/CruelKernel/exynos9820-beyond1lte
$ cd exynos9820-beyond1lte
# List available branches
$ git branch -a | grep remotes | grep cruel | cut -d '/' -f 3
# Switch to the branch you need
$ git checkout samsung-g973f-bta8-cruel
# Install compilers
$ git submodule update --init --recursive
# Compile (install mkbootimg first)
$ ./build mkimg name=CustomCruel +magisk+canary +wireguard +ttl +cifs +nohardening
# You will find your kernel in boot.img file after compilation.
$ ls -lah ./boot.img
# You can automatically flash the kernel with heimdall
# if you connect your phone to the PC and execute:
$ ./build :flash
# Or in a single command (compilation with flashing).
# ./build flash name=CustomCruel +magisk+canary +wireguard +ttl +cifs +nohardening
Boots phone but after entering pin goes to black screen then right back to the pin screen.g973f
gillim74 said:
Boots phone but after entering pin goes to black screen then right back to the pin screen.g973f
Click to expand...
Click to collapse
What ROM are you using? I tested it mostly on samsung BTA8 firmware.
evdenis said:
What ROM are you using? I tested it mostly on samsung BTA8 firmware.
Click to expand...
Click to collapse
Ambassadi same firmware but i think i know what it is.i never uodated the bootloader.i will try that first
gillim74 said:
Ambassadi same firmware but i think i know what it is.i never uodated the bootloader.i will try that first
Click to expand...
Click to collapse
If your phone was able to boot to pin screen, then I doubt the problem is in bootloader. Could you try V1 kernel https://github.com/CruelKernel/exynos9820-beyond1lte/releases/tag/v1.0
If it will work, then probably V2 will also work with +nohardening option. V1 compiled with this option, V2 without it. I will rebuild V2 then.
evdenis said:
If your phone was able to boot to pin screen, then I doubt the problem is in bootloader. Could you try V1 kernel https://github.com/CruelKernel/exynos9820-beyond1lte/releases/tag/v1.0
If it will work, then probably V2 will also work with +nohardening option. V1 compiled with this option, V2 without it. I will rebuild V2 then.
Click to expand...
Click to collapse
Same thing with version 1.could it be the twrp im using?
gillim74 said:
Same thing with version 1.could it be the twrp im using?
Click to expand...
Click to collapse
No, it's definitely not related to twrp. Well, I don't know what is an exact problem here, but some guys told me they were able to flash the kernel on ambassadi with data wipe or immediately after flashing the rom itself.
It would be very nice if people will just write if the kernel works or not on their roms. This will be a huge help for me.
evdenis said:
No, it's definitely not related to twrp. Well, I don't know what is an exact problem here, but some guys told me they were able to flash the kernel on ambassadi with data wipe or immediately after flashing the rom itself.
Click to expand...
Click to collapse
Data wipe or format data
gillim74 said:
Data wipe or format data
Click to expand...
Click to collapse
Data wipe should be enough. I will test compatability with Ambassadi today-tomorrow and will provide more detailed feedback. Thanks!
hello installation successfully the nikel kernel market for now
evdenis said:
Data wipe should be enough. I will test compatability with Ambassadi today-tomorrow and will provide more detailed feedback. Thanks!
Click to expand...
Click to collapse
Worked with data wipe
evdenis said:
It would be very nice if people will just write if the kernel works or not on their roms. This will be a huge help for me.
Click to expand...
Click to collapse
write me on telegram so i can say you why all get the pin code problem so you can fix it
Does this work with BSL7? Or know of kernel that will. Need my su permission to work
Paulturn84 said:
Does this work with BSL7? Or know of kernel that will. Need my su permission to work
Click to expand...
Click to collapse
Hi, no it will not work on BSL7. This kernel is for S10 (G973F) device. This device has only BSL6 firmware. BSL7 is for other devices. Try to look at nemesis kernel.
Is it possible to build magisk rooted kernel for pie (9) roms? Or it's only for Q like LOS 17?
vomad said:
Is it possible to build magisk rooted kernel for pie (9) roms? Or it's only for Q like LOS 17?
Click to expand...
Click to collapse
Download: https://cruelkernel.org/release/special/CruelKernel-G973F-ASJG-v1.1-LOS.img
This version is based on Android 9 (ASJG) sources and should work on ASIG firmwares. I've included some patches from ivanmeler LOS tree specifically for LOS. Features: Magisk v20.3, wireguard, ttl modules and cifs. Not tested
will he s10+ every be supported with this kernel?
Introduction
Based on samsung sources and android common tree. Supported devices: G970F/N, G973F/N, G975F/N G977B/N, N970F, N975F, N971N, N976B/N. All sources are open on GitHub.
Continuous integration with GitHub Actions set up. This means you can customize the kernel from browser and build the version suitable for you without leaving the browser (see сustomization section).
Features
Customizable build with config presets
Only part of samsung security features disabled (DEFEX, Process Authentification, root restrictions)
Switchable SELinux (by default it's locked in "always enforcing" mode in samsung sources)
Built-in in Magisk v21.1
Various toolchains (cruel,arm,samsung,proton,arter97...) supported
Wireguard for VPN
CIFS for SMB
Iptables TTL and HL editing modules for bypassing tethering restrictions
NTFS module for OTG usb drives
Moro sound module
Boeffla WakeLock Blocker
sdfat driver for vfat and exfat filesystems
reiser4 filesystem added. reiser4progs (https://github.com/CruelKernel/reiser4progs/releases)
DEX cable vendor lock for WQHD resolution removed
ZIP installer with XZ compression
ZIP installer with automatic os_patch_level patching
Build commands (configuration presets) used for V3.9 kernel:
Code:
$ ./cruelbuild pack model=<MODEL> name=CRUEL-V3.9 +magisk +nohardening +force_dex_wqhd +ttl +cifs +ntfs +sdfat +nodebug +noaudit +noksm +nomodules +wireguard +usb_serial +sched_powersave +sched_performance +morosound +boeffla_wl_blocker +fake_config +dtb
Where model can be one of G970F/N, G973F/N, G975F/N G977B/N, N970F, N975F, N971N, N976B/N.
Installation Instructions
First of all, TWRP Recovery + multidisabler should be installed in all cases. This is a preliminary step. Backup your existing kernel. You will be able to restore it in TWRP Recovery in case of any problems. Download an *.zip file. Reboot to TWRP. Install > Install ZIP > Flash CruelKernel.zip. Reboot to system.
ChangeLog
V3 - Support for G970F, G975F, G977B, N970F, N975F, N976B models.
V3.1 - Boeffla wl blocker, BTB5 sources for N10 models.
V3.2 - Magisk update v20.4, wireguard update, sdfat for VFAT, exFAT, ntfs module.
V3.3 - CTC9 sources. The camera will work only on CTC9 based firmwares.
V3.4 - CTE9/CTF1 sources. Small fixes, overall improvements, more customization configs for building on github.
V3.7 - Various toolchains added (arm, arter97, samsung, proton, system, default)
V3.8 - DTI1 sources added for N971N, N976N.
DTH7 sources added for G977N model.
Some debugging flags disabled. performance config fixed (-O3).
Cruel toolchain added (gcc 10.2 with PGO/LTO and inlining params from gcc 9 branch)
simple_lmk added (github.com/kerneltoast/simple_lmk)
V3.9 - G977N, G973N models added.
G970F/N, G975F/N, G973F/N updated to DTJA.
N976B, N970F, N975F updated to DTJ4.
Magisk updated to v21.1 version.
Vendor lock for dp cable for DEX removed (thanks, fart1-git).
Zip installer implemented.
Automted os_patch_level level patching in installer (https://github.com/CruelKernel/clone_header).
Downloads
OS Patch Level: 2020-11
V3.9 Download folder
Sources
If you like the work and want to help me with hosting: https://www.paypal.me/evdenis Hitting star button on GitHub and thanks button on XDA really helps to stay motivated.
Instructions here could be outdated a bit, one can find the latest version in project's readme at github.
How to customize the kernel build
It's possible to customize the kernel and build it from the browser. First of all, create and account on GitHub. Next, fork this repository. Switch to the "Actions" tab and activate GitHub Actions. At this step you've got your own copy of the sources and you can build it with GitHub Actions. You need to open github actions configuration file (.github/workflows/main.yml) and edit it from the browser. For example, to alter the kernel configuration you need to edit lines:
Code:
- name: Kernel Configure
run: |
./build config
model=G973F
name="CRUEL-V3.3"
+magisk
+nohardening
+ttl
+wireguard
+cifs
+sdfat
+ntfs
+tcp_cibuc
+morosound
+boeffla_wl_blocker
First of all, you need to change G973F model to the model of your phone. Supported models: G970F/N, G973F/N, G975F/N G977B/N, N970F, N975F, N971N, N976B/N.
You can change the name of the kernel by replacing name="CRUEL-V3" with, for example, name="my_own_kernel". You can remove wireguard from the kernel if you don't need it by changing "+" to "-" or by removing the "+wireguard" line and "" on the previous line. OS patch date can be changed with os_patch_level=2020-02 argument, the default current date is in build.mkbootimg.G973F file.
Available configuration presets can be found at kernel/configs folder. Only the *.conf files prefixed with "cruel" are meaningful. For example:
+magisk - integrates magisk into the kernel. This allows to have root without booting from recovery. Enabled by default.
magisk+canary - integrates canary magisk into the kernel.
bfq - enable bfq I/O scheduler in the kernel.
sched_... - enable various (conservative, ondemand, powersave, userspace, performance) CPU schedulers in the kernel.
ttl - adds iptables filters for altering ttl values of network packets. This helps to bypass tethering blocking in mobile networks.
wireguard - adds wireguard VPN module to the kernel.
cifs - adds CIFS (SMB) support.
tcp_cubic - use CUBIC as default TCP congestion control.
tcp_westwood - use WestWood as default TCP congestion control.
sdfat - use sdfat for exFAT and VFAT filesystems.
ntfs - enable ntfs filesystem support (read only).
boeffla_wl_blocker - enable boeffla wakelock blocker module.
morosound - enable moro sound control module.
+nohardening - removes Samsung kernel self-protection mechanisms. Potentially can increase the kernel performance. Enabled by default. Disable this if you want to make your system more secure.
nohardening2 - removes Android kernel self-protection mechanisms. Potentially can increase the kernel performance. Don't use it if you don't know what you are doing. Almost completely disables kernel self-protection. Very insecure.
nodebug - remove debugging information from the kernel.
noksm - disable Kernel Samepage Merging (KSM).
nomodules - disable loadable modules support.
noaudit - disable kernel auditing subsystem.
300hz - increases kernel clock rate from 250hz to 300hz. Potentially can improve ui responsiveness.
1000hz - increases kernel clock rate from 250hz to 1000hz. Potentially can improve ui responsiveness.
For example, you can alter default configuration to something like:
Code:
- name: Kernel Configure
run: |
./build config
os_patch_level=2020-12
model=G975F
name="OwnKernel"
+magisk+canary
+wireguard
+nohardening
+1000hz
After editing the configuration in the browser, save it and commit. Next, you need to switch to the "Actions" tab. At this step you will find that GitHub starts to build the kernel. You need to wait about 25-30 mins while github builds the kernel. If the build is successfully finished, you will find your boot.img in the Artifacts section. Download it, unzip and flash.
To keep your version of the sources in sync with main tree, please look at one of these tutorials:
How can I keep my fork in sync without adding a separate remote?
How do I update a GitHub forked repository?
Support
This thread. Feature requests accepted.
Telegram (testing and intermediate releases).
GitHub Pull Requests if you want to contribute.
Credits
Samsung for kernel sources
fart1-git for disabling DEX cable vendor lock
corsicanu for default blocklist of wakelocks for boeffla_wl_blocker driver
Nico (@NicoMax2012) for porting moro sound module
bamsbamx for porting boeffla_wakelock_blocker
thehacker911 for general improvements and advices
ExtremeGrief for overall improvements, porting maple scheduler
geiti94 for his advices
topjohnwu for Magisk
franciscofranco for FK Kernel Manager
and testers.
I'm sorry if I missed someone, just write me and I will update the list.
XDA:DevDB Information
[KERNEL] CRUEL KERNEL S10/Note10, Kernel for the Samsung Galaxy S10
Contributors
evdenis, evdenis
Source Code: https://github.com/CruelKernel/samsung-exynos9820
Kernel Special Features:
Version Information
Status: Testing
Current Stable Version: v3.9
Stable Release Date: 2020-12-01
Created 2020-03-08
Last Updated 2020-12-01
How to build the kernel locally on your PC
This instructions assumes you are using Linux. Install mkbootimg (AIK tool) from osm0sis, heimdall (if you want to flash the kernel automatically).
Next:
Code:
# Install prerequisites
# If you use ubuntu or ubuntu based distro then you need to install these tools:
$ sudo apt-get install build-essential libncurses-dev libtinfo5 bc bison flex libssl-dev libelf-dev
# If you use Fedora:
$ sudo dnf group install "Development Tools"
$ sudo dnf install ncurses-devel ncurses-compat-libs bc bison flex elfutils-libelf-devel openssl-devel
# Install mkbootimg
$ wget https://github.com/osm0sis/mkbootimg/archive/master.zip
$ unzip master.zip
$ cd mkbootimg-master
$ sed -i -e 's/-Werror//g' Makefile
$ make
$ sudo mv mkbootimg /usr/local/bin/mkbootimg
# Get the sources
$ git clone https://github.com/CruelKernel/samsung-exynos9820
$ cd samsung-exynos9820
# List available branches
$ git branch -a | grep remotes | grep cruel | cut -d '/' -f 3
# Switch to the branch you need
$ git checkout cruel-v3
# Install compilers
$ git submodule update --init --recursive
# Compile
$ ./build mkimg name=CustomCruel model=G973F +magisk+canary +wireguard +ttl +cifs +nohardening
# You will find your kernel in boot.img file after compilation.
$ ls -lah ./boot.img
# You can automatically flash the kernel with heimdall
# if you connect your phone to the PC and execute:
$ ./build :flash
# Or in a single command (compilation with flashing)
# ./build flash name=CustomCruel model=G973F +magisk+canary +wireguard +ttl +cifs +nohardening
Pin problem
The problem is not in sources. It's due to os_patch_level mismatch with you current kernel (and/or twrp). CruelKernel uses common security patch date to be in sync with the official twrp and samsung firmwares. You can check the default os_patch_level in build.mkbootimg.* files. However, this date can be lower than other kernels use. When you flash a kernel with an earlier patch date on top of the previous one with a higher date, android activates rollback protection mechanism and you face the pin problem. It's impossible to use a "universal" os_patch_level because different users use different custom kernels and different firmwares. CruelKernel uses the common date by default in order to suite most of users.
How can you solve the problem? 5 ways:
You can restore your previous kernel and the pin problem will gone
You can check the os_patch_level date of your previous kernel here https://cruelkernel.org/tools/bootimg/ and patch cruel kernel image to the same date. If your previous kernel is nemesis, patch cruel to 2099-12 date.
You can reboot to TWRP, navigate to data/system and delete 3 files those names starts with 'lock'. Reboot. Login, set a new pin. To fix samsung account login, reinstall the app
You can rebuild cruel kernel with os_patch_level that suites you. To do it, you need to add the line os_patch_level="<your date>" to the main.yml cruel configuration. See the next section if you want to rebuild the kernel.
You can do the full wipe during cruel kernel flashing
Good job!
Thanks Dev! Does this kernel work also with LineageOS and AOSP roms?
evdenis said:
...
After that you need to add the line os_patch_level="<your date>" to the main.yml cruel configuration and rebuild it. See the customization section if you want to rebuild the kernel.
Click to expand...
Click to collapse
Did you checked it if it works for you? For me the oneliner didnt work in main.yml. I must edit the build.mkbootimg.G975F file and rebuild. Then i got no pin problems cause the OPL was now changed.
hanspampel said:
Did you checked it if it works for you? For me the oneliner didnt work in main.yml. I must edit the build.mkbootimg.G975F file and rebuild. Then i got no pin problems cause the OPL was now changed.
Click to expand...
Click to collapse
Yes, I checked that it works. Here you did't use os_patch_level setting and the date is 2020-02. Next, you updated os_patch_level and you can see the date changed if you unfold "Show information about build" section in build log. In the third commit you removed the os_patch_level and cancelled the build, so the date reverted to default one 2020-02. And in finial commit the date was changed in build.mkbootimg.G975F file. If you doubt the date changed, you can check the build settings either in "Show information about build" section in build log or in "Kernel Configuration Info" file next to the kernel image in "Artifacts". Thanks!
Valentino911 said:
Thanks Dev! Does this kernel work also with LineageOS and AOSP roms?
Click to expand...
Click to collapse
As for now, it compatible only with Samsung based firmwares. Works on native samsung firmwares, BeyondROM, on Ambasadii it's better to use Nemesis kernel (you will face pin problem if you try to install cruel). The kernel doesn't work on LOS.
Anybody want gcam for exynos.. u can see tgis video it for android Q one ui 2.0 for s10plus exynos
I have a question . The hadest rum was established, respectively the hadest kernel. I install the cruel kernel, but after the reboot the kernel of the hadest returns. Why? The first time I encounter this phenomenon, How to solve the problem?
Before rebooting the cruel core, the necessary functions work. After a reboot, the hades kernel returns.
@evdenis
I got problems with your latest sources (3.0 and 3.1). It doesnt boot to recovery with an app. This works for a few commits earlier(last week or so). Now its not working. And the OSPL in main.yml doesnt work for me too. Doesnt pass the restart pin. But thats not a problem, changed it in the other side.
Cant test your compiled versions, pin problem, i was on nemesis kernel, so i have to compile it myself.
Another problem ive saw, the device doesnt shut down. It only reboots. Compiled with 3.0 and 3.1 sources. With the older source a week ago, it works.
Edit: So tried your released v3.1 and changed the OSPL manually for PIN Fix, seems to work(recovery and shutdown). Maybe something went wrong on my side till compiling. Have no clue atm.
hanspampel said:
Another problem ive saw, the device doesnt shut down. It only reboots. Compiled with 3.0 and 3.1 sources. With the older source a week ago, it works.
Edit: So tried your released v3.1 and changed the OSPL manually for PIN Fix, seems to work(recovery and shutdown). Maybe something went wrong on my side till compiling. Have no clue atm.
Click to expand...
Click to collapse
This could be due to enabling non-default configuration presets, like +nodebug or +nohardening2.
elchinemil said:
I have a question . The hadest rum was established, respectively the hadest kernel. I install the cruel kernel, but after the reboot the kernel of the hadest returns. Why? The first time I encounter this phenomenon, How to solve the problem?
Before rebooting the cruel core, the necessary functions work. After a reboot, the hades kernel returns.
Click to expand...
Click to collapse
Hades rom uses very good kernel. Technically, I don't see any reason to change it on hades rom, unless you really want to experiment with, for example, +1000hz or +bfq scheduler.
The reason the previous kernel restores back could be again due to patch level mismatch.
I will update installation method in the next version to dynamically repack kernel during installation procedure. Hope, this will solve os_patch_level problem (pin issue) once and for all.
nice kernel
Thanks for this wonderful kernel! It is an honour for me to be able to participate in this!
G975N
Working in 975N or not
hamidru said:
Working in 975N or not
Click to expand...
Click to collapse
If it works om F/FD devices. It will work on N devices
hamidru said:
Working in 975N or not
Click to expand...
Click to collapse
If it's an exynos device ... no reason to this