[ROM][3t-optimized][OMS][microG-ready]NLOS-14.1 - 20180309 [EOL] - OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve

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 Files​OxygenOS - 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 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170606-UNOFFICIAL-nvertigo-oneplus3t.zip
June 6 2017​http://www.x-null.net/xda/nvertigo6...06-UNOFFICIAL-nvertigo-gps-test-oneplus3t.zip **GPS TEST**
June 2 2017​http://www.x-null.net/xda/nvertigo6...02-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
May 24 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170524-UNOFFICIAL-nvertigo-oneplus3t.zip
May 18 2017​http://www.x-null.net/xda/nvertigo6...18-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
May 15 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170515-UNOFFICIAL-nvertigo-oneplus3t.zip
May 9 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170509-UNOFFICIAL-nvertigo-oneplus3t.zip
May 3 2017​http://www.x-null.net/xda/nvertigo6...03-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Apr 26 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip *Experimental with OMS*
Apr 22 2017​http://www.x-null.net/xda/nvertigo6...NOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip *Experimental*
Apr 18 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170418-UNOFFICIAL-nvertigo-oneplus3t.zip
Apr 11 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 7 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170407-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 4 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170404-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 1 2017​http://www.x-null.net/xda/nvertigo6...01-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 30 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170330-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 28 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170328-UNOFFICIAL-mad-murdock-oneplus3t.zip
Mar 24 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170324-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 20 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170320-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 16 2017​http://www.x-null.net/xda/nvertigo6...16-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 12 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170312-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 7 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170307-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 4 2017​http://www.x-null.net/xda/nvertigo6...04-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 1 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170301-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 25 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170225-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 24 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170224-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 18 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170218-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 14 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170214-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 10 2017​http://www.x-null.net/xda/nvertigo6...10-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Feb 6 2017​http://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 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170203-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 1 2017​http://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.

Related

[JDCTeam][TREBLE][v6 RC2][Gemini] The Full Treble support project

{
"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"
}
The Full Treble Project for MI5 Gemini
Brought to you by Jflte DevConnection Team​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We're 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 TREBLE
* SUPPORT 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.
*
*/
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
Gemini hardware vs Treble implementation:
Gemini is an ARM64 and A-ONLY device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-ONLY system images.
Available GSI downloads:
Up today, thanks to @phhusson and other devs, are available a bunch of Android 9.0 system images that can be flashed on Gemini.
You can find these Gsi at the following links:
- ANDROID Q (Gsi)... Is just a preview... but it works on our Mi5!!
- Phh AOSP 9.0 (Gsi).
- Resurrection Remix v7.0 (Gsi).
- LineageOS 16.0 (Gsi).
- HavocOS v2.0 (Gsi) (Use A only).
- ViperOS v6.0 (Gsi) (Use A only).
- JDC AOSP 9.0 (PURE AOSP Gsi, built from sources, just for testing purpose, no gapps support for this preview version).
- GSI & sGSI List page
Treble implementation and download:
JDCTeam is working from latest months of 2017 to implement on Gemini (un-supported from producer) the full support of Treble.
Thanks to @sir mordred, we reached on MI5 the full working status... from v5 we moved to full versioned vndk v28 (aka PIE support... and Q ready!).
NOTE: just to be clear, it's a work in progress development...
We tested with some available Gsi and we put over here some links to these images.
We are sharing a TWRP flashable zip that include vendor and boot images (flash only through TWRP 3.2.3-0 Official).
NOTE: ONLY with TWRP 3.2.3-0 version is possible to handle the treble flash!​
How to use:
Download the TREBLE zip provided here: Mediafire
Download a GSI image (Remember: ARM64 and A-ONLY version)
Reboot to recovery (TWRP 3.3.1-0 REQUIRED)
Clean the device (wipe Dalvik/Cache/System/Data partitions)
Flash Treble gemini zip
Flash the GSI system image you wish to use
Reboot
---> Video on How to install <---
Screenshots:
Youtube review: (To Be Updated when new links available)
- ANDROID Q Gsi on MI5 (How to Install) ---> Click here to play the video
- ANDROID Q Gsi on MI5 ---> Click here to play the video
- RR v7.0.0 Gsi on MI5 ---> Click here to play the video
- PHH AOSP 8.1 Gsi on MI5 ---> Click here to play the video
- AEX 8.1 Gsi on MI5 ---> Click here to play the video
What's working (... and not working):
The development is now @ an RC status (this is not a rom)... you have the possibility to have a look and test the phone with a GSI rom... let us know what does not work (not related to the GSI itself)!!
Issue reporting:
We already say that this is not the place to report issues or bugs ROM related... but in any case a bug encountered can be linked to the treble support not perfect or missing supported features... be free to post about issues you encountered, and please provide logs with the description of the issue. We will check the logs to understand the reason, and in case of fixes to be done, we will update on post#3 (MISCELLANEA) a kind of todo list for us and for users as a "bug list"... but the meaning is "what has to be checked/fixed to get a better treble support for future".
Any question?
If you have any question about, please check first on the post#2 (FAQ) to see if your question has already an answer... if not, post in the thread and we will give you informations.
Sources
GitHub
Social
YouTube: JDCTeam TV
XDA News: Read article
Credits
JDCTeam
LinageOS
Google
MI5Devs
Special thanks:
@sir mordred (developer)
@musabcel (for his test support)
Team Codefire - JDCTeam-Build03
XDA:DevDB Information
GEMINI Full Treble support project, ROM for the Xiaomi Mi 5
Contributors
smeroni68, sir mordred, mzo, ktulu84
Source Code: https://github.com/Project-Treble-Mi5
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest available
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v6
Stable Release Date: 2019-03-16
Created 2018-03-10
Last Updated 2019-06-27
FAQ Section...
This is the FAQ (Frequently Asked Questions).
Have a look here before asking in the thread... in the worst case you will not find the answer you are searching!
If this section is useful for most users needs, I'll be glad to continue investing time to update this Q/A list!!​​
Q1:Fingerprint wake/home button works?
A: Yes, now we have the complete support and this feature is available on standard GSI roms (treble support is ready for it)
Q2: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img,system and vendor partitions.
Q3: If I revert to a Custom rom, what I need to do to restore treble support?
A: Just flash the Treble zip through TWRP as the first time. Treble support need boot.img and vendor.img to be installed into the phone... nothing more... nothing less...
Q4: Phh GSI rom is quite poor in functionality. Why?
A: The purpose of Phh GSI AOSP rom is not to be a custom/featured rom. It is an experimental project that is born to have a common rom (better to say the same system.img) usable on many devices with treble support.
This support can be native, acquired after an Oreo original update or as we have done a custom integration on an "unsupported" device.
The meaning today of using a GSI rom is not to be a perfect rom for dayly use... or let's say, it can be a dayly rom only for users that like pure vanilla code.
In future we hope that many others custom roms will move to be a GSI (as JDC will try to do), so we will have the treble base to use these new project also on our devices.
Q5: If a new version of treble support is out, did I need to flash it or not?
A: Our project is on the way. This means that if is available a new update from us, it is for sure an enhancement with more support of feature or fixes.
In case you will need to install a GSI rom, check always here if there is any new version and get it.
In case you are running a custom rom without treble support, DO NOT update with treble flash, because most probably you will break your current installation.
Treble flash is 100% safe from the phone point of view... isn't safe for your current installation!! Why? Mainly because your current boot.img will be overwritten with treble support... 99% you will get a bootloop with a not treble rom!
Q6: How to get ROOT on phh gsi?
A: Firstly download the phh-gapps-su image. After installation, go to the market and install "phh superuser" app to manage the su access for the apps that need it. In the other cases, you can flash from TWRP the correct Magisk zip to gain root.
Q7: Where I can find the GSI images available?
A: Have a look in the OP post over here... there you can find the available ones. In any case here the LINK to the Treble Enabled Device Development section on XDA or here on GSI & sGSI List page
Q8: Everytime I entered the password, it says Decryption Unsuccessful!
A: You have internal SD encrypted. If after MIUI stock, you haven't FORMATTED the internal SD (FORMAT is not WIPE... Format will erase all data and files from the phone, so you must know what you are doing before formatting), the phone result as encrypted, so the rom is asking the password to decrypt the datas... Decryption Unsuccesful clearly states that the decryption procedure is not working. Post about the issue on the GSI rom you are using and provide logs to the developer to help digging the problem... if Developer will answer that encryption is not supported, you can only do one thing: backup all your data, files and pictures on an external storage (eg. a PC) and procede with a FORMAT DATA from TWRP to "destroy" the encryption and "free your phone from it"!
Q9: Is Google Camera working on Gsi?
A: Yes. But remember you need to install gapps package to let gcam works as it should.
We tested Gcam up to v6.1.021 on AOSiP Gsi. If you have greenish selfies pics, go in the Settings -> Fix ->and enable the fix for Front Camera and reboot. For SlowMotion, set 120fps.
Q10: Why can't flash a micro gapps and only pico is flashable?
A: If you get an error of Insufficent space on system partition, you need to resize the partition. Do in this way:
Flash the SYSTEM.IMG you wanna use (select a Vanilla based one)
Reboot to RECOVERY
MOUNT the SYSTEM partition
Go in WIPE menu -> ADVANCED WIPE -> select SYSTEM from the list and press the button REPAIR OR CHANGE FILE SYSTEM
select RESIZE FILE SYSTEM
than SWIPE to execute the command...
in case of error (you will see in red), repeat the RESIZE until it goes completed (Resizing... Done)
After this operation, the system partition will be resized to his maximum dimension (on Mi5 is around 2992MB)
before the installation of gapps package, do a REBOOT to recovery and after MOUNT the SYSTEM partition (check that it is really mounted)
Now you can flash the micro gapps without problem.
Q11: Is there any Magisk version working on Treble gsi?
A: Yes, you need to get v18.1 version or newer with treble support (check around).
Q12: VoLTE is working[/B]?
A: Yes. Install this ims.apk to use it!
Q13: ADB Logs are needed in case of Issue reporting...
A: In case you need help and want report an issue (eg. a boot problem), we need logcat of the phone. Just as sample, we report here what to do (but you must able to do by yourself... we are not giving help on how to do...)
prepare a PC (with adb package to support debug via usb connection)
flash on the phone our treble and the GSI image (just these 2 files, not any patch or other stuff)
reboot the phone
connect the usb cable
after the Mi logo screen, wait to hear from PC a sound that means the usb periferial has been recognised
go in a command window and type:
--> adb devices (if the phone is connected, you will see the code written after the command executed)
--> adb shell logcat > bootlog.txt (this will start real time recording of logs into the pc in the bootlog.txt file)
--> when the phone has completed boot/reboot (eg. a boot loop or fastboot), you need to press Ctrl+C from keyboard to stop log recording.
send attached to the issue description post the bootlog.txt
...let's dev check what's happening by reading the logcat.
... list will be updated...
Miscellanea...
Download (public versions history)
Here you can find the shared folder with all the version released of Treble support: GEMINI-TREBLE
Changelog's
v6 (20190316) - Release Candidate 2 full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- FIXED NFC support
- FIXED Ambient Display main icon size and settings menu icons style... Thanks to Subezhj for helping fixing.
- FIXED ConfigPanel - Fingerprint settings menu icons style
v5 (20190308) - Release Candidate full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- Mostly all library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated
- Updated kernel as per treble's kernel docs (enforced)
- Vendor image's version is now 28
- Misc updates and fixes
- GSI Pie roms support (check in OP for some links)
- JDC PIE GSI rom given just as a preview for testing (JDC PIE GSI is build from sources without ANY hack!!)... It's pure AOSP as Google bring to their devices... NOTE: No support for gapps... they do not complete setup... you are advised.
v4 (20180409) - Beta partially versioned_vndk with the following updates:
- VERSİONED_VNDK support is partially implemented
- Lots of library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated, only small number of lib dependencies which needs to be resolved are left
- Updated kernel as per treble's kernel docs
- Vendor image is now using google's stock vndk-sp, ll-ndk libs which are called as treble layer libs
- Vendor image's version is now 27.1.0
- Misc updates and fixes
v3 (20180329) - Beta status with the following updates:
- Updated camera Hal from latest qualcomm 8996 repo
- Hexedited more libs and removed more vendor system dependency (better treble and preparation for versioned vndk)
- Updated wifi configs from lates CAF
v2 (20180318) - Still alpha build with the following updates:
- Upstreamed kernel
- Hexedited blobs to correct path (for treble)
- Linker issues fixed
- Vendor overlays
- Latest device tree updates from CAF and miui oreo beta
- Disabled non-working apps (custom xiaomi doze package and configpanel app which were designed to work with LOS APIs)
- Disabled userspace thermal hal initialization which we dont have in cameraHal (faster cam launch)
- Increased jpeg quality parameters
- other misc. dev tree updates
v1 (20180310) - Initial release (Alpha)
Reported/Known Issues
- Camera works perfectly, but on some apk after a shot is taken with Flash active, the camera do not get more pictures... Close the app will clear the issue and you can get other pictures! Suggestion: do not use the flash with this camera apk if you have the issue! ... or use a working camera apk (is a better solution)!
to be updated...
Big thanx and credits also goes to @smeroni68
All of the story is started with the identifying unused CUST partition which xiaomi left on our device Mi5 https://forum.xda-developers.com/showpost.php?p=74702470&postcount=300
And after we determined that the /cust partiton is unused on AOSP roms, we used it as /vendor partition as per the requirement of Full-Treble https://github.com/sirmordred/android_device_xiaomi_gemini-twrp/commit/5faf9c4e162e8144b71f87d6d21c384931b1ac0c nearly 3 month ago
And that is also the reason of nearly all devices which get Full-Treble support via custom implementation, are Xiaomi devices (Redmi Note 4, Mi5S and our Mi5)
Thanx also to my teammates who contributed this project :good:
Our goal is now separating/isolating all vendor <=> system interactions (which will be enforced on future android releases for treble devices) and stabilizing vendor.img while getting closer to pure AOSP sources
Enjoy
...
...
Finally we are out for both MI5 and MI5S... yeah... now let's go ahead...
Thanks for all JDCTeam
Great Job dude! Finally we got treble. Downloading now. Can't wait flashing.
通过我的 MI 5 上的 Tapatalk发言
Thank you Sir, downloading now
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
kishan314 said:
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
Click to expand...
Click to collapse
Good question... I'll report also in post#2 in FAQ section.
Q: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img and the system partition... vendor partition will stay there waiting for your next test!
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
atembleque said:
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
Click to expand...
Click to collapse
This is something we can try to build... but only when sources of P will be released and will be good to build an AOSP based on them...
Very very thankful
Thanks for your hardwork, downloading now.
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
MichaelPan01 said:
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Here it is working.
Have you set the battery icon visibility status under the statusbar settings?
StealthHD said:
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
Click to expand...
Click to collapse
1) Phh rom support natively Phh superuser app (from market) with stock kernel and phh-gapps-su gsi image.
2) Gcam require API2/HAL3 support, and on phh gsi hasn't been implemented (as written is an experimental rom with the meaning to be compatible with stock Oreo treble devices). Instead, it has API1/HAL1 support for stock vanilla camera.
3) Stock kernel is HMP. We do not develop till now the EAS kernel on stock treble kernel (we will do for our JDC gsi).
4) Magisk is clearly reported into Phh thread to not be used. In custom development we have a plus, because we can change the kernel (as you have done)...
Thanks for this testing report.

[ROM][10.0.0]LineageOS-17.1[Joan][Unofficial]

{
"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 9.0 (Pie), 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.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working (LOS16.0):
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Flash
GPS
DAC
Vibration
Wifi Hotspot without password
[+] USB Tethering
What's not working (LOS16.0):
Hotspot with password/WPA2
Wifidisplay is borked
About LineageOS 17.0 and what you need to consider:
Read this post: https://forum.xda-developers.com/showpost.php?p=80271901&postcount=1580
Where are the features?
LineageOS is in development process so don't complain about xyz features missing.
Instructions:
Download the build
Reboot to recovery
Flash the latest build
Reboot
V30 Telegram group chat
Downloads:
17.1
H930: LineageOS 17.1
16.0:
LineageOS 16.0 AFH
H930 GDrive Mirror and H932 GDrive Mirror
15.1:
Here
H932 Release here, Mirror
Sources:
Device Tree: h930 + joan-common
Kernel: msm8998
Vendor: lge
lineage-16.0/17.0 branch
XDA:DevDB Information
LineageOS 16.0, ROM for the LG V30
Contributors
SGCMarkus, rashed97
Source Code: https://github.com/LineageOS/
ROM OS Version: 10.x Q
ROM Kernel: Linux 4.x
ROM Firmware Required: Pie firmware
Version Information
Status: Alpha
Current Beta Version: 1
Beta Release Date: 2018-05-13
Created 2018-05-13
Last Updated 2019-09-19
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 dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 13.05.2018
- Initial release
Release 16.05.2018
- Fixed boot (temporarily disabled sdcardfs)
Release 18.05.2018
-enabled sdcardfs again (fixed, took the OP5(T) driver, not the broken LG one)
-reduces system image size by around 10MB, so our friends who repartitioned have a bit more room for that
Release 21.05.2018
-updated to latest LineageOS sources
-enabled burnin protection in overlays
-re-enabled exfat driver in the kernel (may cause issues for some sdcards, may need to reformat them, as they could "load" forever and make the system crash eventually)
-cherry-picked https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/210106 (should fix acccess to wide angle camera on apps that support it)
Release 01.06.2018
- Updated Autobrightness from Taimen (Pixel 2 XL), as it has the same panel
- Enabled the AoD option (you might have to unlock the phone twice or so though, LOS source is currently broken, nothing i can do)
- Updated to latest LOS sources
- Nuked lge/common and moved gestures into our tree
Release 08.06.2018
- Source updates
- fixed AOD
- Added back sysnode (camera stuff)
- thermal/lights HAL are now bindarized
- setting right model name on boot (zip is still called h930 though)
Release 01.07.2018
- Source updates
Release 19.07.2018
- Source updated
- Fixed vibrator
- Updated vendor files to H930V20R
- Allowed access to Snap, SnapCam and Gcam Wide angle mod by default
Release 30.08.2018
- Updated sources
- Updated blobs to 21a
Release 27.09.2018
- Updated sources
- New init system for model detection (old one used ro.boot.suffix which not every V30 had for some reason)
- Some love for the H930DS, it finally works now
- Baseband is shown correctly now
- Includes a release for the H932, will be a seperate link, check download section (This build is done by @me2151 and will not be maintained, but is up-to-date with the H930 currently)
Release 06.12.2018
- Update to LineageOS 16 (synced on 6. december, still has november security patch)
- H930D/DS works
- H932 build is also there, seperate download
- Vibration uses our own service now (no LG dependency), can sometimes, for 1 certain type of vibration be a bit weird, but works fine otherwise
- QuadDAC can be turned on/off (Settings -> Sound -> Hi-Fi Quad DAC), also Volume Balance works, the filters/equalizers dont
- GCam records audio just fine
- Reworked some media profiles (higher bitrates, should be able to record 720p240 and 1080p120, the new gcams kinda override that though and end up recording stuttering 1080p240...)
- Cleanup of a few nonworking proprietary files
- Updated proprietary files to H930V21o (November security patch)
Release 08.12.2018
- Sources updated for december security patch
Release 09.01.2019
- Sources updated for january security patch
- Updated brightness scaling (rom side + kernel side patches)
- Raised default brightness of the AOD
- Enabled Pocketmode (disabled Fingerprint sensor when phone screen is turned off and the proximity sensor is covered)
- SELinux is enforcing (if you encounter any issues, let me know, WITH logs only though)
- I hope i didnt forget anything
Release 13.02.2019
- Updated Sources (Feb. security patch and more)
- FM Radio (may not work on all models, like V300)
- EAS Power HAL + Kernel
- DRM fixed with SELinux enforcing
- DP/HDMI out works now properly
- maybe other stuff i forgot
Release 08.04.2019
- Updated sources (april security patch, los changes)
- Updated vendor files (h930 21w)
- 24 bit audio support
- Lots of DAC stuff
- Back to HMP for better battery life
- Speaker is a bit louder
- Other things i forgot
Release 22.04.2019
- Updated sources
- Added more perf/iop blobs
- Added color service (Settings -> Display -> LiveDisplay -> Color calibration)
- You can use Wifi AND Hotspot now at the same time
- AOD has now a few more options and is now via a little hax more reliable
- Stuff i might have forgotten
Release 10.06.2019
- Updates LOS Sources (June Security Patch, and some other features)
- Volume Panel can now be moved (Settings -> System -> Buttons -> Show Panel on Left)
- Touchscreen Gestures: 4 Swipe directions while touchscreen is off (Settings -> System -> Gestures -> Touchscreen Gestures)
-- This is partly ROM and partly Kernel patch
- Reverted camera blobs to pre 21w patch for more functionality (ISO couldnt be raised as high anymore what ive been told)
- Few other things here and there i might have forgotten
Changelog 19.09.19
- Updated to LOS 17
- Used H930DS 30b blobs (september security patch)
- Kernel sources at 4.4.153 (H930DS 30e), and CAF at LA.UM.7.4.r1-5400
Changelog 05.02.20
- Updated to LOS 17.1
-- february security patch
- H930 v30q blobs
- Video playback issues should be resolved
- Added sdfat driver in the kernel for exfat support
- Hotspot works with no Password set (working on this...)
- Updated Graphics and Wifidisplay stack from LA.UM.8.2.r1-04300-sdm660.0 (same drivers as msm8998...)
-- Wifidisplay is still a bit ****ed though
- Encryption should work (but TWRP for pie encryption doesnt support it)
- Camera for december and later security patch has been fixed
- Added missing NFC configs thanks to @ShapeShifter499
- More i might have forgotten...
Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Which Models are supported?
A. So far it works well on the H930(G/D/DS), US998, VS996 and LS998. H932 works too, use the .zip for that model. Other devices may bootloop.
Q. Help, my H931/H933 is bootlooping!
A1. For H931 please go to https://forum.xda-developers.com/lg-v30/how-to/running-h930-aosp-rom-us998-converted-t3889320
A2. For H933 please go to https://forum.xda-developers.com/showpost.php?p=78183349&postcount=2
Q. USB Tethering isnt working!!!!
A. Make sure you have the correct drivers installed.
Try this: open device manager:
find the RNDIS (thats what it was called for me), or some other device similar to that name, with a probably yellow !
right click: uninstall drivers (and tick delete drivers)
restart usb tethering
then you have an "unknown device", right click
install driver
search on pc
select from list
search for LG Electronics as manufacturer
and then on right side select "LGE AndroidNet Remote NDIS Device"
My God, that was fast. It even looks to be usable daily, so long as you don't need an SD card (and keep the phone on).
Goodbye Axon 7; V30, here I come!
I didn't see this in the OP but WE install gapps yes?
foamerman said:
I didn't see this in the OP but WE install gapps yes?
Click to expand...
Click to collapse
Install gapps after you flash the rom, dont reboot inbetween
Finally.. my fav lineage os is here.. awesome.. hope it gets continuous support..
Thanks!
dadme said:
Finally.. my fav lineage os is here.. awesome.. hope it gets continuous support..
Thanks!
Click to expand...
Click to collapse
I plan to
(And I hope some more people/devs become interested in this device now.... fixing/trying to fix stuff nearly alone after rashed did the first device bringup.... And im no pro myself either, idk what causes the boot issues )
For exfat why don't try Samsung open source module https://github.com/bkuhn/exfat
Work on LG V20 D.O.T.S custom kernel, realy nice.
dadme said:
For exfat why don't try Samsung open source module https://github.com/bkuhn/exfat
Work on LG V20 D.O.T.S custom kernel, realy nice.
Click to expand...
Click to collapse
Thanks, will try that one. Already had it working once, then took it out again to just check if it was causing issues or not, and then imported it again, and suddenly its causing a weird behaviour
Setupwizard takes ages to load, its checking the sdcard forever, Launcher takes ages to load too, and after a few minutes the system crashes... Same happens with the sdfat driver lol
On stock and TWRP it works fine though (TWRP uses the same driver as i tried btw...).
Nice ! Good job as always
I will flash it next week as i still need my V30 urgently working for now... but anyways thanks in advance
Camera
Literally the 1 thing stopping me from installing this right now is the camera. Gcamera is great but doesn't support 4k video on this device nor does it support laser focus or duel lenses (although the ported version of gcamera have a separate app for each camera). Please can you port the LG Camera over. Also does the QuadDAC work on this?
You made my Monday great ?
Thank you
Klimos said:
Literally the 1 thing stopping me from installing this right now is the camera. Gcamera is great but doesn't support 4k video on this device nor does it support laser focus or duel lenses (although the ported version of gcamera have a separate app for each camera). Please can you port the LG Camera over. Also does the QuadDAC work on this?
Click to expand...
Click to collapse
That is the reason I never used other roms on my G5.
SGCMarkus said:
Install gapps after you flash the rom, dont reboot inbetween
Click to expand...
Click to collapse
No what I was saying was the rom doesn't have gapps with it so we've got install gapps with the rom. Sorry for the confusion.
foamerman said:
No what I was saying was the rom doesn't have gapps with it so we've got install gapps with the rom. Sorry for the confusion.
Click to expand...
Click to collapse
Yep, not shipped with gapps. From my last stand of knowledge (like years ago lol) its not even allowed to ship gapps with ROMs.
Hi, is fm radio working with this rom?
Hi Markus, Danke for your great work and astonishing results here!
Regarding the camera: I remember some guys where extracting the official LG Cam from the Korean Oreo update a few weeks ago...
Is there any chance we could get the LG camera working on LineageOS ?
kgian2007 said:
Hi, is fm radio working with this rom?
Click to expand...
Click to collapse
tbh, i think i havent tested this yet. I focused more on finding out what the **** causes the bootissues.... (trying to figure that out since easter...)
Thats like searching a needle in a haystack (as the logs dont contain anything helpfull when it happens... and no ramoops either ;-; )
FcBayernMinga said:
Hi Markus, Danke for your great work and astonishing results here!
Regarding the camera: I remember some guys where extracting the official LG Cam from the Korean Oreo update a few weeks ago...
Is there any chance we could get the LG camera working on LineageOS ?
Click to expand...
Click to collapse
Ehhm... Depends on how much the LG Cam depends of the LG Framework? But i suppose thats a lot, would be really really difficult (involving lots of reverse engineering then probably) and would take ages. Doubt LG wants to make our lives easy lol
So... Just got a report from my tester.
10 consecutive (re)boots without a problem. Will release a version soon with this fixed
Had to disable sdcardfs (ro.sys.sdcardfs=0). Maybe i can find a commit somewhere that fixes whatever LG ****ed up there (I suppose their stock framework/kernel source has a modified version, that doesnt work well with AOSP based ROMs...)
Edit: uploading non-treble build now
Thanks to @phhusson for leading me to the fix

[JDCTeam] 🥧 Pixel Experience Pie 🥧 Release 12 [26 Dec][9.0.0_r46][unofficial] [EOL]

[JDCTeam] 🥧 Pixel Experience Pie 🥧 Release 12 [26 Dec][9.0.0_r46][unofficial] [EOL]
{
"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"
}
Pixel Experience for Galaxy S4 (jflte)
What is this?
Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
DON'T FLASH GAPPS AS ALREADY INCLUDED
Download from AndroidFileHost
JDC Team Aroma addon - here
Translation
Help with project translation
Telegram channel
Stay tuned​
SUPPORTED DEVICES
All following Galaxy S4 variants with Qualcomm Snapdragon 600 are supported:
GT-i9505 - jfltexx
GT-i9507 - jtfddxx
GT-i9508 - jfltezm
SCH-i545 - jfltevzw
SCH-r970 - jflteusc
SGH-l337 - jflteatt
SGH-l337m - jfltecan
SGH-l337z - jfltecri
SGH-m919 - jfltetmo
SGH-s970g - TracFone / Straight talk
SM-s975l - TracFone / Straight talk
SPH-l720 - jfltespr
SPH-l720t -jflterefreshspr
jfltezm - China mobile
jfltecsp
jfltetfnatt
jfltetfntmo
All Variants with a locked bootloader are currently unavailable until the unified tree is further updated.
AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL bootloader.
VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK bootloader.​Do 'getprop ro.bootloader' in Terminal Emulator or through ADB shell to find out which bootloader you have.​
TWRP
You are REQUIRED to be using TWRP 3.2.3-0 or newer to be able to flash any Pie rom.
If your device does not have an updated relevant version then you can use the standard JFLTE version.
If you have a device with a locked but exploitable bootloader as above (AT&T + Verizon) then use the Loki-patched version.​
Latest recommended JDC TWRP Recovery v3.3.0-0 for JFLTE: HERE.
Official TWRP Recovery v3.2.3-0 for JFLTE Loki-patched by @mattgyver: HERE.
Other variants may require a different recovery. ​
UNSUPPORTED DEVICES
GT-I9515 is not / will never be supported (slightly different hardware)
GT-I9500 is not / will never be supported (completely different hardware)​
Thanks
Side
Arco
JDCTeam
jhenrique09 + Pixel Experience team
OpenGapps
SPECIAL THANKS
Donators
JDCTeam-pie test team / Slack testers
AndroidFileHost
All of you!
JDCTeam
Buff - @buff99
Chibbo - @chibbo
Creeper - @creeper36
Diego Monaco - @alucard_24
Dimitris Katikaridis - @side
Franck Rohée - @franzyroy
Ray Daley - @gadget!
Jim Silverlock - @Jimsilver73
Marco Zanin - @-+BB+-
Matthew Booth - @MattBooth
Mattia D'Alleva - @AntaresOne
Mike Atkins - @FernBch
Oliver - @angelcalibur
Paul Harris - @hawkerpaul
Paul Keith - @javelinanddart
SalimPS - @SalimPS
Simeon Ivanov - @smstiv
Stefano Meroni - @smeroni68
Yannis Menexes - @SkL*
Be sure to check out our official aroma addon installer by @salimPS HERE
You are welcome to join the official JDC Team chat / test group in Slack jdcteam-pie
XDA:DevDB Information
🥧 Pixel Experience Pie 🥧 for S4 unified, ROM for the Samsung Galaxy S4
Contributors
Buff99, side
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Lollipop compatible
Based On: AOSP
Version Information
Status: Stable
Created 2018-11-13
Last Updated 2020-05-17
Installation​Required for installation: Recovery - Latest version of TWRP - 3.2.3-0
If you require a LOKI-patched version of TWRP, try this version patched by @mattgyver.
Firmware - Lollipop supporting bootloader and modem / non-hlos. Look in _Bon_Bon's great MODEMS and BOOTLOADERS collection​The following are "best practice" recommendations for installation, you may be successful using your own routine.
1st install - " clean install "
Make a full nandroid backup <always backup!>.
** OPTIONAL Properly remove previous root solution (recommended - flash Magisk uninstaller and UnSU). **
Fully wipe device (At least system, cache, dalvik and data. Recommended - fully clean by wiping internal and external SD).
Make sure your partitions are formatted as EXT4. Do not use F2FS on pie.
Install Rom.
DO NOT Wipe cache and art / dalvik (rom is partially pre-deodexed).
Reboot.
Wait for 1st boot.
Run through Gapps setup.
** OPTIONAL Reboot back in to TWRP.
** OPTIONAL Install desired root solution (recommended - Magisk).
** OPTIONAL Do not clear caches, boot back into Android.
Enjoy.
2nd and subsequent installs - " dirty flash "
** OPTIONAL Uninstall all Substratum overlays **
Make a full nandroid backup <always backup!>.
Properly remove previous root solution (recommended - flash Magisk uninstaller and UnSU).
Wipe system, cache and art / dalvik (wiping system is ESSENTIAL for Magisk).
Install Rom.
Install desired root solution. (recommended - Magisk).
DO NOT wipe cache and art / dalvik (rom is partially pre-deodexed).
Reboot.
Wait for app optimisation.
Enjoy.
While dirty flashing may be possible for some updates, be prepared that progress means you will occasionally need to clean install updates (usually when settings files are changed)!
Nandroid backups are your friend!​
Latest changelist
Release 12- 26th December 2019
release_12-PixelExperience_jflte-9.0-20191224-0101-UNOFFICIAL.zip - 675.8MB
md5sum - 281d8447f69eff26b1fec744bab95efb​
Release 12
December 2019 security patches
Changed to different Arm-optimized repo and removed a couple of bionic tweaks
Snap camera - handle sdcard removed case and dont spam exceptions
BT fixes
Translations
Drop AmbientPlay
Remove weather client
CPU tuned and JIT profiles changed to speed
Buffcore Kernel 10.2 - removed autosleep & quickwakeup
See attached changelist file for specifics
Release 11
September 2019 security patches.
Longshot screenshots added
Recorder app added
Miracast / casting enabled
performance tuned - Interactive governor & AutoSMP
Buffcore kernel 10.0
Row IO scheduler set as default
See attached changelist file for specifics.
Release 10
August 2019 security patches.
Buffcore kernel 10.0
See attached changelist file for specifics.
Release 09
June 2019 security patches.
Buffcore kernel 6.5b - more tweaks, fixes and optimisations.
See attached changelist file for specifics.
Release 08
June security updates
Buffcore kernel 6.12b
See attached changelist file for specifics
Release 07
May 2019 security patches
Push libsec-ril libraries
Disable Vsync for cpu rendered apps
Load dummy initial BT MAC address
Dex optimizations
Bionic optimizations
Finalize the UI improvements ( Finally 60fps smoothness on UI)
Tune interactive governor
Tune PegasusQ governor
Fix the touch boost never been enabled
Stop BT location scannings
Add pseudo-bokeh on Snap camera (Its on ISO modes as PORTRAIT)
Clean up some logs and sources
Reduce camera to api1 for better response (api2 is not working good on custom jf roms anyways)
A better sleep drain
init: Set min freq to 216000
overlay: Let light sensor warm up before work
Clean out some double sounds
Bug fix "Wallpaper is half black after rotating quickly "
Fix some wifi issues ( i believe )
Relocate location QS icon to main icons
core: Zygote: Disable any DEBUG reference
Kernel changes:
Upgrade kernel to 6.1 version with the following changes
Zip it with GZIP
Enable ZRAM/Zcache/zsmalloc
Optimized LMK
Kill some debug spams
ARM optimization flags here and there
Fix memory leak on wifi and general clean up
Enable autodetection of OOM
Fix BT and wifi memory leaks
Compress ramdisk,kernel and zram with a faster compression type (faster boot and executions)
Increase swappiness to 60
Clean up CPU's behavior code
Release 06
April security patches
Enable full Dexpreopting . Faster boot and response
Enable call recording for the countries that legally support it
Camera improvements ( Greatly improve preview quality, faster focus, greater quality on images and videos)
Reduce kernel spam logs
Clean up the power services (Better balance between battery-performance)
Clean up graphics services and drivers.
Interactive and intelliplug changes
Reduce GPU's voltage by 25ma
kernel: New and updated governors:
ABYSSPLUG
ADAPTIVE
BADASS
CONSERVATIVE
DANCEDANCE
DARKNESS
INTERACTIVE
KTOONSERVATIVE
NIGHTMARE
ONDEMAND
PERFORMANCE
PEGASUSQ
POWERSAVE
SLP
WHEATLEY
BIOSHOCK
USERSPACE
Release 05
BT defaulted on
change graphic renderer
camera improvements
governor changes including on charger
call recording in supported countries
translation updates
Improve ambient play layout on keyguard
Introduce smart clock
Improvements for battery percent inside icon
Smart clock: Fix clock showing then device is on landscape and QS expanded
full dex pre-opt applied
launcher pinning removed
Kernel: Buffcore 4.3b.
March 2019 security updates applied for Pix, AOSP.
Pix and AOSP code grabbed 24th March 2019.
Release 04
Whitelist Whatsapp and other social media apps in order to use HAL1 camera
BlueTooth Changes
WiFi Changes
RIL Changes
Pin HOME app in order to go home faster
Add a missing RIL blob
Fix encryption (?)
Kernel edits about increasing performance and general CPU scaling
Graphics should be smoother now.
gps:Log only if error
kernel:Enable AddRandom and disable IOStats
Lots other stuff changed
Kernel: Buffcore 4.3b.
March 2019 security updates applied for Pix, AOSP.
Pix and AOSP code grabbed 16th March 2019.
Release 3
BT calling works
Lots other stuff changed
Kernel: Buffcore 4.3b.
February 2019 security updates applied for Pixel, AOSP.
Pixel and AOSP code grabbed 00:00 9th February 2019.
Release 2.93
Advanced reboot (from dev options);
Built in dark Pixel theme (basic but functional);
Launcher icon shape setting;
Translations updated;
AOSP camera shipped (may change back to snap though?)
Buffcore 3.1 app
Buffcore Kernel 4.3b
January 2019 security updates applied for PIX, AOSP.
PIX and AOSP code grabbed 07:00 19th January 2019.
Release 2.9
Wifi much better.
Hotspot / tethering fixed.
Some display changes.
LMK tweaked.
Kernel: Buffcore 3.04. Netfilter / wireless fixes.
December 2018 security updates applied for PIX, AOSP.
PIX and AOSP code grabbed 05:00 5th December 2018.
Release 02
Wifi stability improved;
OptLos "special sauce" added;
Buffcore app added (full JF optomised fork of Kernel Aduitor);
Default vibration reduced;
Some BT edits (Arco);
Toolchain changed to BB's JF optimised Linaro 7.1.1;
Kernel: Buffcore 3.01 (some Buffcore 2 tunings and optimisations added back in);
November 2018 security updates applied for PIX, AOSP.
PIX and AOSP code grabbed 02:00 22nd November 2018.
Thanks to JDCTeam chat / test group in Slack jdcteam-pie .
Current issues
Release 12​
This rom is as close as you will get to a stock Google Pixel style phone.
It is an unofficial version of Pixel Experience, so only report issues to this XDA thread, not Pixel Experience team.
Release 12 has even more @side OptLos super smooth speed optimisations applied…. - It's super smooth!.
Installs about 1.3 gb in system including gapps (** so WILL NOT WORK on i9505g / google version **)
System folder is re-sized to full 2.7gb.
Unified rom so should work on all S4 variants APART FROM i9505g DUE TO SIZE.
Remember this is an almost stock google pixel rom!
Gapps is already pre-installed and mandatory
DO NOT attempt to manually install any gapps package over the top, you will break it.
Don't work
MHL video (? we think ?)
Does work
Miracast / casting.
BT calling.
SE Linux is set as permissive.
Wifi is much improved.
Hotspot working.
GPS is great.
Make sure your partitions are formatted as EXT4. Do not use F2FS on pie.
CDMA phones work??
Magisk 19.3 works fine.
Magisk sound mods appear to work e.g. ViperFX.
Substratum works fine.
Sound changes may mean older sound mods no longer work.
The google sound app may crash, update to version 2.1.
This rom will not work / will never work on i9515, i9500 and i9506 variants of S4.
Reporting bugs​
Proper reporting of issues will help me spend time productively fixing bugs rather than tail chasing vague issues.
Please follow these guidelines.
Reporting bugs
If you wish to report an issue, then the onus is on you to prove the issue.
If you provide exact replication instructions, an idea of how often the issue occurs and logs that enable me to replicate the issue then a fix will be possible ("if you do action 1 then action 2 then action 3 you will find that bug X occurs 100% of the time").
If you give a vague complaint about an issue then I will not look at it without explicit replication instructions and preferably logs ("phone overheats when using game XYZ").
Issues about overheating, battery life or performance should be backed up with information from relevant monitoring apps.
One-off issues generally do not get investigated unless they are well documented and have provided logs.
Issues that are specific to one piece of software will generally not get investigated without logs. I am not very keen on installing software to investigate bugs, especially if I need to create user accounts. If you can replicate the issue on more than one piece of software it will increase the chance of being fixed.
Issues to do with speaker or microphone related issues need to be explicit about which speaker and mic is in use (internal, head phones, earphones, bluetooth headset, Bluetooth speakers), whether normal earpiece or hands free mode is in use, Audio mods that have been installed. Logs may be helpful too.
Issues with media / streaming / playback should be provided with examples.
A picture is worth a thousand words; a movie is thousands of pictures. If you cannot describe your problem in words, post pictures or movies to help show your issue. The rom has in-built screen capture and screen recording tools, so please use them.
It can often be difficult to tell what is going on with logs from a fully loaded system. It can help if you make a nandroid of your current system, format and then make a clean install, with gapps only if needed, and only the app that causes the issue - as minimal a system for replication as possible - then replicate the bug and capture logs. If I then have to replicate the issue I can easily replicate your system.
If you want to send logs for a bug, I would like you to use Syslog.
Perform some of the functionality that is bugged and then capture logs in the app.
If you have had a reboot then capture a set of logs immediately when the system reboots. If the last-kmsg file is empty then the logs are useless.
Type a brief description of the problem in the notes field and your XDA username .
Select to scrub personal information.
Upload it to a web based host (gdrive, dropbox, etc.) and PM the link to me.
And remember:The Drill ...​​
you stole my pie icon at the thread title
muehehehe <3 finally released .
loved it <3
side said:
you stole my pie icon at the thread title
muehehehe <3 finally released .
loved it <3
Click to expand...
Click to collapse
That Pie-con is JDC property.
I love that you love it.
:highfive:
Pies...Pies everywhere ?
@Buff99 @side ARTISTS !
Finally
Video by me
You killed it bro, amazing work & amazing team, love it <3
Dear Buff99,
Thank you for PE Pie ROM.
redacted
sghi747love said:
https://forum.xda-developers.com/re...-fix-signal-issues-fluctuations-t3811950/amp/
Click to expand...
Click to collapse
this guy removed his commit.
redacted
Beautiful ROM, great work! Definitely a daily driver for me if Bluetooth will be fixed!
I was looking for a lot this rom, thanks to the developers.
Inconveniences: at the first power-up, my device became excessively hot to the point of burning the screen, and turned off only.
Remove the battery, and let it cool for 10 minutes, now it seems to work normal.
Still this I am a user of this type of ROM (pixel experience) on all my devices with twrp installed.
thanks again
Release 02 is now available - see:
post #1 for download link
post #2 for installation instructions
post #3 for changelist
post #4 for updated current issues
post#5 for bug reporting instructions
Dirty flashing should work fine.
BT calling is still broken, but release 03 will see it fixed as good progress is being made.
Hotspot may be broken for this build, sorry.
This build is much faster and smoother than release 01.
[deleted]
Thanks. Waiting for stable rom.

EOL [ROM][Unofficial][9.0][signed][OTA] Lineage OS 16.0 for Xperia Z1 compact

This thread is discontinued - please visit the LineageOS 17.1 sucessor thread
This thread aims at providing LineageOS 16.0 builds for the Sony Xperia Z1 compact with current security patches.
You can consider this thread as a successor of our LineageOS 15.1 thread, where you may also find some useful information.
This is the joint effort of 115ek and MSe1969 (contributions welcome).
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
We offer two build variants:
A. Standard LineageOS 16.0 build
This build flavor aims at providing LineageOS 16.0 "as is" with most recent security patches.
If you want to install Google Apps (GApps) you have to use this build variant.
GApps are optional, of course. The smaller the GApps package, the better (pico). If you want "Okay google" support you need at least nano.
Just check the package comparison to see what fits your needs.
B. Pre-installed microG build variant with additional security patches
For the security/privacy focused (more details about below feature list, see here)
Pre-installed microG and F-Droid same as the LineageOS for microG project
Pre-installed AuroraStore
eSpeak TTS engine (FOSS TTS solution)
Additional security hardening features listed below
Access to /proc/net blocked for user apps
Bundled netmonitor app to allow network monitoring
Enhanced Privacy Guard: Switches for motion sensors and other sensors
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking
Optional disable captive portal detection
Increased max. password length of 64
No submission of IMSI/phone number to Google/Sony when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView
Additional restriction options for secondary users
Constified JNI method tables
Status
List template by AdrianDC
Code:
- Boot : Ok
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : only 2.4 GHz
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok (mono)
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: broken
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok
- SEPolicies : Enforcing
Limitations
Following limitations are known:
NFC-HCE does not work (needed for example for google pay)
FM does not work in stereo mode (mono works fine, though)
Problems with some 5 GHz Wifi channels (can be avoided by not using autochanneling) fixed with 20190408 build
MHL does not work
5 GHz hotspot does not work (2.4 GHz hotspot works fine)
ANT+ does not work fixed (see FAQ)
installing Magisk 19.1 prohibits entering recovery fixed with 20190521 build
GPS gets wrong time due to GPS week rollover since 3rd November 2019 (of importance when you record GPS tracks for example).
This also happens on stock and several other legacy devices. fixed with 20190611 build
Click to expand...
Click to collapse
Download
SourceForge
Click to expand...
Click to collapse
FAQ
What recovery system to use?
Please use this TWRP if you want to use OTA updates and/or encryption.
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 16.0 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Please note there is an issue starting with Magisk 19.1 which leads you to being unable to boot to recovery in any way. More info
Click to expand...
Click to collapse
ANT+ isn't working?
You need the 2 apps:
ANT Radio Service (Github) / (Google play)
ANT+ Plugin Service (Github) / (Google play)
afterwards setting proper permissions is essential!
Go to Apps & Notifications -> See All Apps
Select 'ANT Radio Service'
Select Permissions
Select Additional permissions
Slide switch to allow using of ANT hardware
This refers to those instructions which worked for me
Click to expand...
Click to collapse
I've got problems AND have magisk/exposed installed
I won't support anything related to magisk/exposed/other heavily system modifying things.
If you're encountering problems please make sure you're using a clean installation (at most gapps) to verify/reproduce the issue.
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/lin16-microg/android_kernel_sony_msm8974
Manifest: https://github.com/lin16-microg/local_manifests
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on Sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
Installation instructions
Please see the OP of our (deprecated) LineageOS 15.1 thread or also here
Click to expand...
Click to collapse
Changelog
13.12.2020
ASB Security string 2020-12-01 (this month, no kernel updates found)
Webview updates for both builds (microG build on M87)
microG build only: F-Droid updated to 1.10-alpha1-114
microG build only: microG updated from upstream to 0.2.14.204215-15 (picked until 720b089)
Expand for older changelogs:
10.11.2020
ASB Security string 2020-11-05
Fix for CVE-2020-15999
AOSP E-Mail widget fixed
Webviews upodated to/within M86
microG build only: microG - fixes in EN API and GCM
microG build only: Replaced weak F-Droid signatures with ROM's V2 signatures
13.10.2020
ASB Security string 2020-10-05
microG build only: Bromite Webview on M86
microG build only: microG 0.2.12.203315 - including "Exposure notification API" for use of Covid tracing apps
microG build only: Additional hardening: constified JNI method tables
13.09.2020
ASB Security string 2020-09-05
Webviews on M85
microG build only: Added eSpeak TTS engine (microG build variant)
09.08.2020
ASB Security string 2020-08-05
Webviews on M84
microG build only: Location of firewall UI now in Network => data usage (Settings menu)
12.07.2020
ASB Security string 2020-07-05
microG build only: updated prebuilt microG GmsCore fom /e/ project (fixed FCM registration issues)
microG build only: F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
microG build only: Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6
11.06.2020
Security string 2020-06-05
GPS improvements / modernisation
Enable MIDI support
microG build only: Bromite Webview on M83
microG build only: Netmonitor exception in SEPolicy f. "Tracker Control" app
09.05.2020
Security string 2020-05-05
Standard build only:System Webview on M81
microG build only: AuroraStore updated to 3.2.8
11.04.2020
Security string 2020-04-05
Fix for CVE-2020-8597 (external/ppp)
Kernel: CVE-2019-10638 siphash 128bit for IP generation
microG build only: AuroraStore updated to 3.2.4
microG build only: Bromite Webview on M81
07.03.2020
Security string 2020-03-05
System Webviews on M80
2nd build variant 'hardened microG build' (known from 15.1 thread) available
microG build only: AuroraStore updated to 3.2.0
19.02.2020
fixed DRM (we now have widevine Level 3, Netflix for example runs fine)
fixed TWRP time bug
added option to prevent USB gadgets working when screen locked (trust HAL)
enabled changelog (can be accessed under /settings/system/updater/changelog)
synced LineageOS sources (security patch level February 05, 2020)
16.01.2020
synced LineageOS sources (security patch level January 05, 2020)
13.12.2019
synced LineageOS sources (security patch level December 05, 2019)
13.11.2019
fixed unreliable SMS/MMS receiving (https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/262653)
synced LineageOS sources (security patch level November 05, 2019)
19.10.2019
synced LineageOS sources (security patch level October 05, 2019)
13.09.2019
bring back wifi display
three finger screenshot gesture
synced LineageOS sources (security patch level September 05, 2019)
12.08.2019
fixed manual mobile network selection (once again)
synced LineageOS sources (security patch level August 01, 2019)
07.07.2019
synced LineageOS sources (security patch level July 05, 2019)
fixed AudioFX effects completely (thanks @NeoArian)
03.07.2019
start signing builds (please check this if you want to update)
enable OTA updates (thanks @NeoArian)
10.06.2019
synced LineageOS sources (security patch level June 05, 2019)
21.05.2019
fixed recovery issue introduced by Magisk versions starting with 19.1 (thanks @Myself5)
11.05.2019
synced LineageOS sources (security patch level May 05, 2019)
08.04.2019
fixed manual mobile network selection (thanks @SpiritCroc)
fixed problems with 5 GHz Wifi channels
added aptX/aptXHD
synced LineageOS sources (security patch level April 05, 2019)
11.03.2019
fixed alarm delay (came with new lineage sources)
fixed some more offline / USB charging problems (thanks @SpiritCroc)
synced LineageOS sources (security patch level March 05, 2019)
17.02.2019
fixed occasional camera problems (thanks @SpiritCroc)
various kernel patches (thanks @SpiritCroc)
synced LineageOS sources (security patch level February 05, 2019)
15.01.2019
fixed video playback for some applications (thanks @SpiritCroc)
fixed offline charging (thanks @SpiritCroc)
fixed FM radio (thanks @SpiritCroc)
updated webview to version 71 (thanks @MSe1969)
synced LineageOS sources
04.01.2019
initial release
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 16.0 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, MSe1969, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/lin16-microg/local_manifests
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2020-11-10
Created 2019-01-04
Last Updated 2020-12-13
Changelog
The changelog was moved to the OP due to xda not allowing secondary thread owners to edit this post
Tips & Tricks
microG initial configuration after 1st install (microG build variant only)
After the first installation of this ROM, you need to setup microG.
Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"
OTA Updates on an encrypted device
In case your device in encrypted and you have flashed apps creating "survival scripts" in /system/addon.d (e.g. Magisk), there *may* be a dependency to files in the data partition.
An OTA update until current TWRP 3.3.1 does not decrypt the data partition, as this is usually not needed - under specific circumstances however, this may lead to unwanted effects (up to a non-booting device!) during an OTA update, if such scripts aim at modifying files located in the data partition. If unsure, rather perform the update manually as dirty-flash in TWRP or - which in general is a good practice - regularly perform backups in TWRP. If you haven't flashed anything on top of my build (except for the LineageOS root addon, which is no problem), there shouldn't be any issue.
(This commit in TWRP indicates, that this potential issue will be solved in future TWRP releases).
Ok ok .
new build
New build:
15.01.2019
fixed video playback for some applications (thanks @SpiritCroc)
fixed offline charging (thanks @SpiritCroc)
fixed FM radio (thanks @SpiritCroc)
updated webview to version 71 (thanks @MSe1969)
synced LineageOS sources
https://androidfilehost.com/?fid=11410963190603900297
Important announcement:
There were problems with FM radio in lineage-16.0-20190114 which was linked one post above.
Please use lineage-16.0-20190115 from here: https://www.androidfilehost.com/?fid=11410963190603901105
Took a while, but last night I flashed this. And it's fabulous! Some observations, regarding your list in the OP (couldn't test everything, though):
GPS: not just OK but I had the fasted 3D fix since I moved away from stock! Much faster than with signed LOS 15.1 or munjeni's LOS 7.1.2 (well below 10 seconds from my living room window, down from sometimes 90 - 120 seconds!)
WiFi Hotspot: working good and reliably
Compass: somewhat working but GPS Test says "unreliable", and indeed compared to my tablet directions are off by several degrees (pointing to NNW where the tablet says N); attempts to calibrate didn't have any effect
FM radio: working but mono (you wrote that already)
USB OTG: working good and at least reading is about as fast as with other ROMs (USB stick is formatted NTFS, btw)
===
I flashed together with Magisk 18 and openGapps 9 pico
During first boot phone froze completely during boot animatoin; had to hard reset, then it booted fine into system
Google initial setup was a bit weird, had a FC first, then a short loop through the initial three screens, but after a few attempts it finally ran through.
Didn't do much more now, as I need my phone for, well, what you usually need a phone for , so I'm going back to 15.1 now. But the first few steps were extremely promising. Probably will be testing a bit more over the weekend.
Can't wait to use this as a daily driver! :good::good::good:
Using 15/01/2019.
Dirty flashed over last 15.1 (wiped cache/dalvik/system but kept data).
Working really well so far.
One thing I've noticed is that the UI seems a bit slower/somewhat choppier than 15.1, very slightly though. Barely noticeable, but the UI does seem to be a bit slower.
Other than that it's really impressive and is going to be my daily driver until/if something goes bad.
Another thing is twrp 3.2.3 backup restore of this rom seems to result in bootloop, but that might as well be because of me keeping data from 15.1.
lingowistico said:
Using 15/01/2019.
Dirty flashed over last 15.1 (wiped cache/dalvik/system but kept data).
Working really well so far.
One thing I've noticed is that the UI seems a bit slower/somewhat choppier than 15.1, very slightly though. Barely noticeable, but the UI does seem to be a bit slower.
Other than that it's really impressive and is going to be my daily driver until/if something goes bad.
Another thing is twrp 3.2.3 backup restore of this rom seems to result in bootloop, but that might as well be because of me keeping data from 15.1.
Click to expand...
Click to collapse
It's just my impression, but I've seen that sometimes the sense of slow UI may be just due to the speed of animations. Try changing the 3 scale animations on developer settings from 1x to 0.5x as is a common value
Sorry if this is the wrong place to ask this but: when using Dir file manager (super clean and light weight) I can't add home screen shortcuts to files for some reason. This worked on stock lollipop but not on Lineage 15.1 or 16.
How do I make this work again?
lingowistico said:
Sorry if this is the wrong place to ask this but: when using Dir file manager (super clean and light weight) I can't add home screen shortcuts to files for some reason. This worked on stock lollipop but not on Lineage 15.1 or 16.
How do I make this work again?
Click to expand...
Click to collapse
It's definitely a problem with the app itself.
I just tested my preferred file manager - Total Commander - and it worked fine.
Also ES did the job.
Only your mentioned Dir file manager wasn't able to do it.
It seems there is a new api to access shortcuts? Maybe they don't support it? Did you tried on an other device with Android >=8 ?
I just made a screenshot how it should look like (the confirmation dialog).
EDIT:
Yes. Had the right suspicion: https://github.com/veniosg/Dir/issues/126
It's a known app problem.
115ek said:
It's definitely a problem with the app itself.
I just tested my preferred file manager - Total Commander - and it worked fine.
Also ES did the job.
Only your mentioned Dir file manager wasn't able to do it.
It seems there is a new api to access shortcuts? Maybe they don't support it? Did you tried on an other device with Android >=8 ?
I just made a screenshot how it should look like (the confirmation dialog).
EDIT:
Yes. Had the right suspicion: https://github.com/veniosg/Dir/issues/126
It's a known app problem.
Click to expand...
Click to collapse
Thanks a lot for replying. For some reason, I assumed that Total Commander for Android was shareware/adware.
Hopefully Dir will be updated soon enough, meanwhile I'll be using Total Commander.
Thanks again for looking this up for me and for suggesting alternatives. :highfive:
After 1 month using this version 15.1.2019 every day, i have found this critical problems:
- camera (force closing)
- audiofx (not good working)
- sms app (when i receive sms phone is still vibrating)
- sometimes graphic artefacts on navigation buttons
- sometimes freezing when i use more apps
This rom is pretty, clean, without unuseful functions and this is why i like LineageOS. :good:
Jerri7 said:
After 1 month using this version 15.1.2019 every day, i have found this critical problems:
- camera (force closing)
- audiofx (not good working)
- sms app (when i receive sms phone is still vibrating)
- sometimes graphic artefacts on navigation buttons
- sometimes freezing when i use more apps
This rom is pretty, clean, without unuseful functions and this is why i like LineageOS. :good:
Click to expand...
Click to collapse
Concerning camera: I have this problems too (unregular) although I can't reproduce them. A reboot should help. @SpiritCroc has merged a commit that may be connected to this http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/84248 though I'm not sure if it solves the problem. We'll see.
Concerning AudioFX: It's buggy in my opinion - independent of devices and android version. I also had issues with it on Oreo and on totally different devices. If someone has got a hint: feel free to share
Concerning SMS app: I also have issues here but I think it's related to the lineage code and nothing device specific. Keep in mind that Lineage 16 isn't officially released until now. If the next build is also buggy please provide a log.
Concerning the rest: Same as above --> LOS 16 isn't released and there are still issues left to fix.
I'll upload a new build soon. Let's see what it brings.
115ek said:
@SpiritCroc has merged a commit that may be connected to this http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/84248 though I'm not sure if it solves the problem. We'll see.
Click to expand...
Click to collapse
If you didn't have that before, it should help; AICP didn't need it at first in comparison to lineage, but we included it now for a cleaner approach, see discussion here http://gerrit.aicp-rom.com/c/AICP/frameworks_base/+/84029
SpiritCroc said:
If you didn't have that before, it should help; AICP didn't need it at first in comparison to lineage, but we included it now for a cleaner approach, see discussion here http://gerrit.aicp-rom.com/c/AICP/frameworks_base/+/84029
Click to expand...
Click to collapse
Great! Thanks again for finding that
The new build is now available:
17.02.2019
fixed occasional camera problems (thanks @SpiritCroc)
various kernel patches (thanks @SpiritCroc)
synced LineageOS sources (security patch level February 05, 2019)
Micro Gapps
First: Thanks for the Update.
My question:
Mostly the Rom-Providers not using MicroG recommend Pico-Gapps for their builds.
I am using them too for all LOS-related Roms without problems.
Is there a special reason/need for your Rom to recommend Micro-Gapps instead?
CyanoFriend said:
First: Thanks for the Update.
My question:
Mostly the Rom-Providers not using MicroG recommend Pico-Gapps for their builds.
I am using them too for all LOS-related Roms without problems.
Is there a special reason/need for your Rom to recommend Micro-Gapps instead?
Click to expand...
Click to collapse
Yes, you're right. Generally spoken the smallest gapps package (pico) is the best in terms of performance (apart from no gapps package ).
Additionally you can easily install missing google apps from playstore afterwards (e.g. maps, youtube...). But there are apps/functionalities you can't get from the playstore, for example "Okay Google".
I just checked the gapps comparison again https://github.com/opengapps/opengapps/wiki/Package-Comparison
It seems nano is sufficient to get these functionalities (so with pico you won't get them). Maybe that was micro earlier... I don't know
But thanks for your hint, I'll update the thread accordingly.
115ek said:
It seems nano is sufficient to get these functionalities (so with pico you won't get them). Maybe that was micro earlier... I don't know
But thanks for your hint, I'll update the thread accordingly.
Click to expand...
Click to collapse
Since I opened my Z1c some 18 months ago I'm running the nano packages and am very happy with that. Same applies to my recently opened tablet z.
Hello.
sorry to interrupt you for a reason not directly related to this topic...
Does anybody of you know AdrianDC (who was part of the team of this Z1 ROM version also) and the way how to reach him?
Maybe you, 115ek?
I have a Sony Ericsson mobile (SEMC 2011 devices) and he was the one having released the only Lineage 14.1 ROM Nougat version for those models (cm13 has been released by 'LegacyXperia' group on basketbuild.com before). It runs perfectly except two remaining issues of the camera's audio function which should be the very last bug fix at it.
Unfortunately my direct messages on XDA to him don't seem to reach him (no read status).
Does anybody can help me to reach him?
I don't even know if the LegacyXperia team is still existing or where those developers have been moved to.
Thank you so much for any hint you can give to me!

[ROM][Signature Spoofing]LineageOS 18.1 for S10E/S10/S10+ Exynos

{
"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 18.1 for Galaxy S10 Series​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Working:
- Wifi
- Sound
- mali drivers
- USB tethering
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- GPS
- Cameras (All of them)
- HWcomposer (HWC)
- Signal indicator
- Double tap to wake
- Wireless PowerShare
Not Working
- VoLTE and VoWiFi will not be implemented (for now) as they heavily depand on samsungs framework
To properly report a bug (Please dont report things already on the Not Working list)
a) Logcat
b) /proc/last_kmsg (or /proc/kmsg)
c) /data/tombstones
d) dmesg
Please do not report bugs if you have performed any system modifications excluding gapps installation
Installation instructions
Make sure you are on Q stock firmware (All of the Q firmwares are tested and confirmed to be working, This should be the case with new fws too as long as Samsung doesnt significantly change bootloader trustzone bits)
Download Q twrp from this thread
flash twrp as per given instructions
if you are coming from stock and have encryption enabled format data (Note i said format, Wiping it in twrp is not the same as formating it)
wipe cache, dalvik cache and system
flash LineageOS
If you want to have gapps flash them right after flashing the rom before first booting
Reboot the device
Downloads:
Google Drive
Mega.nz
(Select build coresponding to your devices codename, S10e = beyond0lte | s10 = beyond1lte | s10+ = beyond2lte)
sha256 checksums
Code:
c8b961734a7972e9db9110785ba622d48c65a3c8ada9c611165864b0411f6699 lineage-18.1-20211111-UNOFFICIAL-beyond2lte.zip
fea1d76cb049cf3d83b9863da19dd0c46b70f91cec7c2a820915adb8943a671c lineage-18.1-20211111-UNOFFICIAL-beyond1lte.zip
540c111583147e94076959fdf3ff51c3f8fc2f29ec98949c6a105d936882f8ce lineage-18.1-20211111-UNOFFICIAL-beyond0lte.zip
If you need general help or questions feel free to join Telegram group
READ BEFORE INSTALLING MAGISK
Gapps
I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler
Due to requests from some users I added signature spoofing support to the rom which allows usage of MicroG
you can simply install MinMicroG and grant it needed permissions for signature spoofing to make it work as intended
Based On Android R
Changelog
12.11.2021.
- Merged November 2021. security update
- Further Improved bluetooth in call handling
- Added more advanced burn in protection
- Misc performance and stability improvements
- Synced with LOS source
06.10.2021.
- Merged October 2021. security update
- Improved bluetooth in call handling
- Synced with LOS source
10.09.2021.
- Merged September 2021. Security update
- Synced with LOS source
06.08.2021.
- Merged August 2021. Security update
- Synced with LOS source
10.07.2021.
- Merged July 2021. Security update
- Performance and stability improvements
- Changed sensors handling in doze mode to prevent battery drain
- Synced with LOS source
10.06.2021.
- Merged June 2021. Security update
- Synced with LOS source
06.05.2021.
- Added wifi and portable hotspot overlays
- Merged May 2021. Security update
- Synced with LOS source
08.04.2021.
- Fixed USB C audio input/output
- Fixed charging with device powered off (It also has nice new animation now)
- Merged April 2021. Security update
- Misc performance and stability improvements
- Synced with LOS source
08.03.2021.
- Added signature spoofing support
- Synced with LOS source
05.03.2021.
- Merged March 2021. Security update
- Performance and stability improvements
- Synced with LOS source
06.02.2021.
- Merged February 2021. Security update
- Misc performance and stability improvements
- Modernized AdvancedDisplay app codebase
- Cleaned up the source
- Updated magisk boot images
- Synced with LOS source
06.01.2021.
- Merged January 2021. Security update
- Fixed OpenGapps installation from lineage recovery
- Fixed features that broke with initial 18.1 merge
- Misc performance and stability improvements
- Synced with LOS source
09.12.2020.
- Merged December 2020. security update
- Merged December 2020 feature drop
- Merged S9DTK9 vendor blobs
- Switched to full vndk30 vendor
- Fixed ADB inside of lineage recovery
- Improved brightness handling even more
- Performance and stability improvements
- Updated recovery images provided in 3rd post
- Synced with LOS source
10.11.2020.
- Further improved auto brightness handling
- Merged November 2020. security update
- Performance and stability improvements
- Updated recovery images provided in 3rd post
- Synced with LOS source
03.11.2020.
- Fixed issues with overlays and s10 camera cutout
- Enabled access to fingerprint for apps that were looking for secure biometics device (e.g. paypal)
- Improved automatic brightness handling (Switched to calibrated sensor virtual device which calculates brightness more precisely)
- Pinned SystsemUI and SurfaceFlinger to ram to imrpove responsivness
- Added blur to dropdrown notifications panel
- Enabled device controls from power menu
- Synced with LOS source
- Misc performance improvements
22.10.2020.
- Merged october security update
- Added back mDNIe display tuning options
- Added back a lot of previously non working los features
- Misc performance and stability improvements
- Synced with los source
07.10.2020.
- Initial public release
XDA:DevDB Information
[ROM] LineageOS 18.0 for S10E/S10/S10+ Exynos , ROM for the Samsung Galaxy S10
Contributors
Ivan_Meler
Source Code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-18.0
ROM OS Version: 11.0
Version Information
Status: Stable
Created 2020-10-07
Reserved
Magisk
Magisk boot images are provided in this google drive folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine, Source for given kernel is available at GitHub if you want to compile kernel yourself just run source build.sh devicename e.g. source build.sh beyond2lte, It will produce new boot image in build/ folder, To update magisk you can follow instructions given at this commit enjoy
Do note that you will have to reflash magisk boot image when updating rom
Wow ! Man, very nice job !
So, you stop release for Lineage 17 ?
troufiniou said:
Wow ! Man, very nice job !
So, you stop release for Lineage 17 ?
Click to expand...
Click to collapse
Nah will update that too, Just felt like releasing this because i had some time to sort out issues with it
The version of gapps doesnt matter even if this is android R right?
I can still flash android 10.0 gapps right?
Eidluci said:
The version of gapps doesnt matter even if this is android R right?
I can still flash android 10.0 gapps right?
Click to expand...
Click to collapse
there is link for android 11 gapps in first post under download section
Ivan_Meler said:
there is link for android 11 gapps in first post under download section
Click to expand...
Click to collapse
Oh thank you, my bad
Hi @Ivan_Meler i'm looking to change rom (i'm on hades rom but this one is not support anymore). And i just want to know if i need a custom kernel to improve battery life on LoS rom (this one or 17.1)?
Thanks for your precisions and your work to maintain on devices uptodate !
[Legenda] said:
Hi @Ivan_Meler i'm looking to change rom (i'm on hades rom but this one is not support anymore). And i just want to know if i need a custom kernel to improve battery life on LoS rom (this one or 17.1)?
Thanks for your precisions and your work to maintain on devices uptodate !
Click to expand...
Click to collapse
Battery life should be fine with stock kernel too as most of things are improved power hal side of things
Ivan_Meler said:
Battery life should be fine with stock kernel too as most of things are improved power hal side of things
Click to expand...
Click to collapse
Great. Thanks. I'll go on 17.1 LoS for awhile and will install this one when it will be more "polish".
Hi I don't know why but on previous lineage os ROMs, when I use TWRP and boot.img it would always boot back to recovery everytime I flashed a ROM.
Can you use lineage recovery to flash ROMs?
Ivan_Meler said:
If you want to root build you will have to use Magisk Canary from here, Once in app download Lineage Recovery for your device from Google Drive or Mega Patch image within manager and flash patched image to recovery partition, When booting hold recovery key combination till you get to first warning screen after that release keys and let system continue booting normally
Magisk curently has some issues properly detecting 2si devices so thats why we cant use boot.img without need for key combo for magisk right now, I will look into that in coming days but till then this is viable solution
Click to expand...
Click to collapse
Tried but says magisk still isn't installed please help.
Il be installing it soon to test it, very hype for android 11
FreeRunner2017 said:
Tried but says magisk still isn't installed please help.
Click to expand...
Click to collapse
make sure you followed instructions closely
1. Download recovery image
2. Download magisk canary app and patch recovery image
3. Flash magisk patched recovwry image (lineage recovery) to recovery partition
4. reboot and hold key combination for recovery until first warning screen shows up, after that release key combo
5. you should be in system with root
if you need further assistance im sure someone from telegram group can help you a bit more
Ivan_Meler said:
make sure you followed instructions closely
1. Download recovery image
2. Download magisk canary app and patch recovery image
3. Flash magisk patched recovwry image (lineage recovery) to recovery partition
4. reboot and hold key combination for recovery until first warning screen shows up, after that release key combo
5. you should be in system with root
if you need further assistance im sure someone from telegram group can help you a bit more
Click to expand...
Click to collapse
I did that but I still have no magisk
SD cards on the s10e just dont work, they keep saying its corrupted even after you format them in android itself ive also tried formatting in windows and twrp but same problem.
network traffic indicator can be turned on but never actualy shows up.
after installing magisk it takes apps 20 seconds to open.
if you need logs i will be happy to do so (if i can remember how to do so)
Wow, already an android 11 ROM ? Nice !
Is there the same issues as on L17 regarding bluetooth and front camera ?
Hi Ivan
Thanks for the great work! Awesome to have Android R available so early. Rom is solid.
On S10e i can confirm, it does not read MMC, i also tried formatting etc, not a biggy
On Bluetooth i can confirm that devices working, headphone sound, speakers etc. But on call when phoning, the sound does not come over to the headset.
HDMI Out is glitchy, creates flickering on secondary display, but is random....
Other than that, the rom is smooth and fast. Still checking battery...
Looking forward to developments...

Categories

Resources