Database Info

[Kernel]ICS,CM9/CM7(v004b1/v029)OC~1.73GHz/UV/True Dual Core/Power Savings[Apr-14]

NOTICE: This is COMPATIBLE with ALL AOSP/CM7/CM9/OpenSense Based ROMs
(Thanks to Albinoman887, scorp2kk, intervigilium and vorbeth for pull requests and contributions.)
For frequency control use fauxclock from Google Play
Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to hack this kernel. If you use my modified kernel source in parts or in its entirety, I kindly ask you mention its origins and to send me a github pull request or PM whenever you find bugs or think you can help improve my kernel hack further. This way the entire community will truly benefit from the spirit of open source. Thank you
​
Hi XDA members and fellow Sensation users:
This is my eleventh kernel hack. I want to thank Cyanogen, CyanogenMod members, Erasmux, and several others I cannot recall for inspiring me to venture into this unfamiliar territory for me.
What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.
​
THIS KERNEL is BASED ON CM7 Source Code. So it is COMPATIBLE ONLY WITH CM7/AOSP Sensation Builds.
Please DO NOT use any task killers, they DO NOT improve performance nor battery life. They INTERFERE with your phone's stability (more crashes) and App compatibilities (Forced Close).
Joe's RCU (Optimized for Small SMP systems)
Joe Korty has created an RCU for small SMP systems (> 32 cores). His approach is to isolate all the Garbage Collection (GC, a slow time consuming but necessary processing) to a single core, thus allowing other cores to ONLY work on real required processing. This will allow the additional cores to complete their assigned tasks as fast as possible (not bogged down by GC) then immediately go back to a suspended state (saving battery).
Fast No Hz RCU (Optimized for SMP operations)
Fast NoHz is an optimized version of the traditional Tree RCU. Many new kernels are using the Tickless NoHz design. This RCU is tailored and designed to work with the new NoHz kernel system.
SmartAssV2 Governor (Balanced)
This governor has a built-in "profile" similar to SetCPU, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).
Interactive Governor (Performance)
This governor is designed to put more priority to User Interface (UI aka Apps) tasks, therefore appears more responsive then the traditional OnDemand governor. So if you want the smoothest UI interaction, this governor is for you...
Brain F*ck Scheduler - (BFS)
This scheduler is designed to be simple and speedy tailor specifically for user interface type systems such as desktop/smart phone devices where user interaction is MORE important than serving 1 million web requests (CFS, the default scheduler) at the same time (think of nimble desktop workstations vs large corporate servers).
SLQB - (SLAB allocator with Queue)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate). Not all kernels are using SLQB including CM7 main line...
Fair Budget Queue (BFQ I/O scheduler)
This I/O scheduler is an improvement on top of Completely Fair Queue (CFQ). CFQ is fair in terms of time but not in terms of throughput / bandwidth, so BFQ make sure that both time and throughput / bandwidth are balanced across all requests.
Installation Instructions:
Here's a step by step instruction to install this kernel:
*************** ICE CREAM SANDWICH (Android 4.0.x) ***************
<< Fast NoHz >>
[ CFS-OnDemand ] (Mainline Edition)
The File ==> Latest AOSP Sensation Kernel (1.73 GHz) <==
*************** GINGERBREAD (Android 2.3.x) ***************
<< Fast NoHz >>
[ CFS-OnDemand ] (Mainline Edition)
The File ==> Sensation Kernel 029 (1.73 GHz) <==
[ CFS-OnDemand ] (Extreme Edition -- Should work with most phones but NOT GUARANTEED!)
The File ==> Sensation Kernel 029 (1.73 GHz, ZCACHE, GPU @ 320 MHz) <==
[ Optional: ]
The File ==> Modified Sensation Thermal Throttler Configuration <==
Optional Under voltage: Version 0.1.4+ ONLY
Code:
[ to over volt ALL frequencies by 25000 uv (microvolts) ]
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to under volt ALL frequencies by 25000 uv (microvolts) ]
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to set a specific frequency (ie 1.18 GHz)
with a specific voltage (ie 1.0875 volts) ]
echo "1188000 1087500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
CPU Frequency Voltage Table
Code:
192000: 812500
310500: 812500
384000: 812500
432000: 812500
486000: 837500
540000: 850000
594000: 862500
648000: 875000
702000: 900000
756000: 925000
810000: 937500
864000: 962500
918000: 962500
972000: 962500
1026000: 975000
1080000: 987500
1134000: 1000000
1188000: 1012500
1242000: 1025000
1296000: 1050000
1350000: 1075000
1404000: 1100000
1458000: 1112500
1512000: 1125000
1566000: 1150000
Low Voltage - Under Volt the processor, therefore uses Less Battery, but NOT ALL CHIPS can handle Under Volt.. If you experience instability, try the Stock Voltage Version.
Stock Voltage - Uses the voltage values from ORIGINAL HTC Kernel Source.
There are NO PERFORMANCE DIFFERENCE between the Under Volted and Stock Voltage versions!
1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. Open ROM Manager and select "Reboot into Recovery" and select "OK"
4. Once in recovery, select "wipe cache partition", select "Yes", then select "advanced", then select "Wipe Dalvik Cache", then select "Yes" again. Once finished, click the back button to go back to the main recovery menu. On that menu, select "Install Zip From SDCad", then select "Choose zip from SDCard", then go to /sdcard/download and select the downloaded zip file and let it run its script.
5. Once the script is done, select "reboot system now"
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
NEWS BULLETIN:
Version 001 for AOSP/CM9/OpenSense is out! Major thanks to all those who worked on OpenSense device tree! Version 029 is OUT for GB!
Please don't hesitate to talk among yourselves and help each other out... The XDA community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...
BUGS:
Not All CHIPS ARE CREATED EQUAL
TO DO:
version 1.x.x -- Haven't thought about it yet...
History:
See Post below...
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My Github Complying with GPL
Follow me on
:
If you find this Kernel useful, feel free to hit the [Thanks] button below

Version History
Version 012 (deprecated)
- EXT 4 Support, CIFS + UTF-8 (NLS Support)
- Kineto_gan Support (WiFi Calling)
- BFQ I/O Scheduler default
- TUN VPN support added
- SLQB memory allocator added and made default
- BFQ I/O scheduler added and made default
- Added NEON and other Snapdragon Compiler optimizations
- Patched kernel to version 2.6.35.14
- Tweaked Voltage Table for more stability
- Allowed unaligned memory access
- Reverted CPU Clock Table back to CAF version
- OC up to 1.512 GHz CAF Fast Version
- Added CAF Patches to msm/cpufreq
- OC CPU up to 1.782 GHz, L2 Cache up to 1.512 GHz
- Added CAF Patch to force max frequency for all cores via sysfs mfreq
- Added Bluetooth BNEP support
- Introducing Synchronous L2 Cache (1.56 GHz version ONLY)
- Introducing L2 Cache Bandwidth Boost (from max 310MHz to 360MHz)
- CAF Patch msm: acpuclock: Subscribe to _FROZEN CPU notifiers
- CAF Patch msm: pm-8x60: Remove redundant code for restoring ACPU Clock Rate
- CAF Patch msm: acpuclock-8x60: Use hotplug notifications for CPU, L2, BUS, voltage
- Added back Scaling_Available_Frequecies sysfs entries (For Mike1986 and other ROM devs)
- Introducing GPU 2D/3D Overclocking <img src="http://rootzwiki.com/public/style_emoticons/default/biggrin.png" class="bbc_emoticon" alt="">
- 3D Engine from 266.6 MHz to 320 MHz (both versions will benefit from this boost)
- Fast NoHz RCU (An RCU designed for Tickless kernel, which is our kernel)
- CAF msm: clock-8x60: Refresh PDM and TSSC halt bits at boot (Bug Fix)
- CAF msm: 8660: Add barriers to SMP boot code (Stability patch)
- CAF msm: clock-local: Add memory barriers for later move to _relaxed accessors (Stability patch)
- CAF ARM: SMP: Make resched-ipi-while-offline warning less verbose (Slight performance tweak)
- CAF msm: clock-8x60: Vote for mmfpb_a_clk at 64MHz (Bug fix)
- CAF mmc: core: put eMMC in sleep (cmd5) mode before suspend (Power Saving)
- CAF msm: clock-8x60: Don't disable clocks in reg_init (Bug fix)
Version 014 (deprecated, CM7 Alpha1 ONLY)
-Introducing Global CPU Voltage Table (Under volt capability via sysfs interface, inspired by snq adapted for Snapdragon Dual-Core by me )
Version 019 (deprecated, CM7 Alpha2+)
Applied many FrameBuffer patches from CAF
Applied couple more KGSL patches from CAF
Revenge of CFS, CFS Enhancement (Interactive latency greatly reduced, make it BFS like)
Applied many FrameBuffer patches from CAF yet again
Added New Early suspend drivers for 2D and 3D GPU engines
Re-Enabled KGSL Ringbuffer Power Management Overrides
Updated to JHash3
Updated Cpufreq to copy policy from siblings
Fixed memory leak in cpufreq stats
Removed CPU from NoHz Idle fair cgroup
Shorten 1080P start up latency
Fixed USB Gadget Serial Crash
Applied more MSM FrameBuffer updates from CAF
Fixed random SPI Operational State Invalid error
Added histogram capability for MSM video
Added lock/unlock for KGSL Early Suspend Drivers
Updated KGSL power level change
Revert Reg Init Patch from earlier (cause of instability)
Optimized memcpy and memmove for string library calls (real working version )
fixed audio unmapped memory crash
fixed inaccurate D-Cache size Macro
Version 020 (deprecated, CM7 Alpha2+)
CFS Autogroup Version 2.0 (Super Charged CFS)
Fixed Kernel/Timekeeping issue
Fixed Full / Stretched Screen issue for Video Player
Patched FB and KGSL
Fixed Random Reboot issue (took me a week to verify this fix)
Revenge of JRCU (JRCU tweaked for better performance and battery savings)
Removed ALWAYS ON ADM Clock to save battery
Moved Data Mover to early suspend for cleaner exit
Version 023 (deprecated, CM7 Alpha2+)
Added XZ Compression support to 2.6.35 kernel
Added XZ Compression support for kernel image
Added XZ Compression RAMDisk support (boot time)
Used the git implementation of SHA-1 to reduce boot time by 11%
Updated qdsp6v2 to block write until buffer is full
Updated trivial bug fix for SMP macro
Added newly optimized CRC32 Improves EVERYTHING that uses it including TCP/IP, File Systems etc...
Added newly optimized CRC32c improves EXT4 metadata performance and anything else which uses CRC32c
Patched msm_serial_hs_lite (better battery life)
Patched qdsp6v2 to fix unexpected power consumption (better battery life)
Patched mdp4_overlay to flush RGB pipe when solid fill mode is used (better battery life)
Patched clock-8x60 to add a lower gsbi_uart_clk entry to save power (better battery life)
Lowered Camera Flash limit from 30% to 10%
Tweaked conservative governor for better interactive performance
Enabled Deep Power Management Options (better battery life)
Lowered CPU Minimum Voltage (better battery life)
Gate smi_2x_axi_clk off when smi_clk is disabled (better battery life)
Fixed performance level computation for VCD (better performance)
Added local control of vpe_axi_clk and rot_axi_clk (better battery life)
Removed unnecessary checks from DMA engine (more efficient DMA Engine == performance)
ARM Patch: Use CTR for the I-cache line size on ARMv7 (better performance)
Enabled inline locks for ARM (performance)
CPU workqueue optimization (limit some workqueues to single thread)
patched qdsp6v2 to Set tx and rx flags based on current device
patched display to avoid staging up two pipes at same mixer_stage
Added GPU slumber (whenever screen is off, GPU is set to sleep)
Added idle wait support for SMP
Fixed AXI clock bug in GPU
Fixed L2 Cache Synchro bug (better performance)
Updated spin lock code (better performance)
Reduced WiFi voltage to min recommended by datasheet (better battery)
Reduced other sub-system voltages by 5~10% (better battery)
Eliminated unnecessary macro from decompressors (code clean up)
Wind down GPU turbo mode if idling (better battery)
compiled with latest code sourcery (better performance)
Fixed Power Management memory leak
Added 2 way call record capability (thanks to mdeejay!)
Patched wakelock to latest AOSP
Patched audio DSPs
Patched Ondemand Governor for better power savings.
Version 024 (deprecated, CM7 Alpha2+)
NoHz RCU set as default
Disable BCM4329 wake irq when stopped (battery saving fix)
Re-order PPP packets in PPPoLAC and PPPoPNS (VPN bug fix)
PLL clock training with higher frequencies for better stability (stability enhancements)
mfd - Fix memory leak in debug probe
Introducing GPU 2D scaling governor (Enabled, completely original coding from me)
-- now it will scale from 145.455MHz~200 MHz depending on usage (this should save additional battery while screen is on).
Introducing IntelliDemand CPU governor
-- Built-in Screen Off profile (like SmartAss)
-- Built-in Browsing detection (enabled, completely original coding from me)
(this will limit cpu clock to max 1.0 GHz while browsing web, book, email etc)
Adjusted 3D and 2D GPU scaling and initial states for better compatibility with Rosie
Version 025 (deprecated, CM7 Alpha2+)
msm72k_udc: Replace dma_coherent_pre/post_ops with mb/rmb
nfs: writeback pages wait queue
block: limit default readahead size for small devices
make default readahead size a kernel parameter
smd_pkt: Extend read operation to receive data larger than SMD FIFO
pet watchdog from console driver
Correct the number of slave ports in the system
watchdog: increase pet time to ten seconds
led: enable dynamic LED brightness
mm/vmalloc.c: eliminate extra loop in pcpu_get_vm_areas error path
Revert "qup_i2c: Calculate combined write length for multiple write transactions" (broke Sensors )
restart: call secure code to disable arbiter
restart: Handle reset interrupt from pmic
pmic8058-xoadc: request's done late into suspend
pmic8058-xoadc: Add mpp_config call on configure
Remove pm_runtime_suspended() from __pm_generic_call
HDMI: Support for 480p 16:9 in HDMI Driver
qdsp6v2: Reduce the pcm write timeout value
enable ldo's in PHY resume path (usb)
Add suspend/resume for TSENS (thermal sensor)
While powering down flush all the rpcrouter workqueues (rpc)
Reader thread to allocate memory without holding a spinlock (rpc)
Reorganize the usage of spinlocks in RPC Router reader thread
Update RPC client's cb_list_lock to use spinlocks
Retry callback registration on timeout (rpc)
Add smd_tiocmset api without spinlocks
Close smd ports upon failure to open.
print lock name for lockdep_init_error
execute lockdep_init as early as possible
board:clocks: add comments to make trouble shooting easier
smd_tty: restrict DS port platform driver
smd: add closing state to subsystem restart
smd_pkt: add subsystem restart loopback server reinit
smd_tty: add subsystem restart loopback server reinit
smd: add check for LOOPBACK_TTY platform device
Add 10 microsec delay before fetching setup_data (usb)
Simplify ACA state machine to support standard ACA (usb)
Recovery point SEI support for ISDB-Tmm (vidc)
Copy the End of Sequence flag (vidc)
Fix H.263 30fps standard resolution encoding.
Override SP profile to ASP for MPEG4 decoding.
Remove check for allocation of sequence buffer size. (vidc)
Update firmware memory size. (vidc)
Fix GOB Header for H.263 encoding.
Increase the decoder input buffer size.
Return the correct error code for IOCTL. (vidc)
Set correct divx codec type.
Handle b-frame not supported error.
Increase the kernel SMI memory size. (vidc)
Report bitstream errors to driver client.
add change to print MFC firmware version
Removed check for comparing DPB Size
add Check for infinite intraperiod configuration.
Fix to handle non-fatal sequence header errors. (vidc)
Fix not coded vop handling in decode order.
add mdp revision number
increase mdp max burst size
Calculate combined write length for multiple write transactions (i2c)
Fix input handler crash (ondemand, intellidemenad)
Add htc off-alarm support from XE source
updated sii9234 tpi driver from XE source code
USB misc code updates from XE source
enable android USB gadget projector support
Added thermal trip critical retry from XE source
updated DMA engine from XE source
fixed minor HTC battery driver coding derp
Added HTC Beats headset support from XE source
kernel:sched: avoids loadavg Moire
don't call task_group() many times in set_task_rq()
block level disk cache target for device mapper
Do not destroy old sched domain on cpu_up
Do not block when waiting to free old root domain
Check for extended quiescent state at start of gp (rcu)
Don't allow cpu to get console lock during hotplugging (printk)
Add the function 'cpu_hotplug_inprogress'
Remove extraneous boot_secondary delay
Version 026 (deprecated)
PM / Sleep: fixed coding derp from "Drop pm_op() and pm_noirq_op()"
mfd: timpani-codec: Handle register write for numbers more than cached one
mfd: timpani-codec: Write register defaults when disabling devices
msm_fb: Remove Audio Packet Control Register setup
mfd: timpani: Retry upon I2C failure.
msm_fb: Check for ACP and ACFG register before reset core.
msm_serial: add PM_RUNTIME code from CAF
mm: retry page fault when blocking on disk transfer
msm: kgsl: Do not allow SLUMBER from INIT
PM / Sleep: Drop pm_op() and pm_noirq_op()
PM / Sleep: Unify diagnostic messages from device suspend/resume
sched/rt: code cleanup, remove a redundant function call
ARM: Add optimised swahb32() byteswap helper for v6 and above
hugetlb: Replace BUG() with BUILD_BUG() for dummy definitions.
kernel.h: Add BUILD_BUG() macro.
msm: kgsl: New low power level
msm: vidc: print message as kernel info instead of error
camera:gemini: update gemini engine from hTc Ruby
battery: battery driver and charging driver update
mm: Android Ashmem update from hTc Ruby
misc: android pmem update from hTc Ruby source code
mfd: marimba core update from hTc Ruby
board: ARM kernel update from Ruby source code
cpufreq: add two-phase to ondemand and intellidemand
Version 027 (deprecated)
input/misc/gpio: update input GPIO driver from PyramidLE source
vidc: 1080p: Override profile to ASP for XVid/Divx456
Re-enabled ZRAM
Version 028 (deprecated)
Updated Zcache and ZRAM to latest Linux-next patches
Added Google's Snappy Compression for ZRAM
Version 029 (Current, CM7 Alpha2+)
Init: Multithread initcalls to auto-resolve ordering issues.*
memcg: let css_get_next() rely upon rcu_read_lock()*
idr: make idr_get_next() good for rcu_read_lock()*
mm: implement WasActive page flag (for improving cleancache)*
zcache: fix deadlock condition*
Revert "msm: kgsl: Clocks should be set to the active level during NAP"*
Revert "partition_sched_domains: Do not destroy old sched domain on c…*
mmc: core: Prevent too long response times for suspend*

Reserved 2... just in case!

Faux123 you're my favorite recognized developer hero

Why do you make your font size so large? Hurts to read.

WOW! CM kernel is out!

I have tested this kernel and it runs very smooth, most things so far work. There are a few hiccups but they could also be due to not having kernel source for the cm7 rom yet.
Im not posting screenshots since it scores about the same as sense based roms. Linpack is a bit low but that could be a number of factors. Overall importance is that the rom is smooth and very agile

Wow, you're quick!

persiansown said:
Why do you make your font size so large? Hurts to read.
Click to expand...
Click to collapse
For those people who fail @ reading

Thank you!
Thanks a ton for all the work you do. At first I was afraid this phone wasn't going to have much love (I came from Mytouch slide), but I have been overwhelmed by the amount of people that are putting out quality work for it
Prepare to have your thanks button massaged a few times.

I knew you were up to something. Flashing now.
Remember to give THANKS were THANKS is due.

Where is the download link?

Idk? Faux were is the download link?
Remember to give THANKS were THANKS is due.

Martovitz said:
Idk? Faux were is the download link?
Remember to give THANKS were THANKS is due.
Click to expand...
Click to collapse
I totally support your message, but, it's "where" thanks is due, dude, not "were."

CM7 Kernel is OUT! Version 012 is the baseline version.
Current CM7 is based on 2.3.3 Binary Blobs, so only up to my version 012 is compatible with it. Once CM7 decides to move to 2.3.4 binary blobs, then I will apply my 013 and 014 patches to the kernel.
Enjoy and have fun.. Now let's post some amazing benchmarks!

Wiped cache, dalvik, flashed 1.78 then thermal patch. Rebooted. Getting constant reboots shortly after ADW EX finishes loading. Won't stop.

man, tonight just keeps on getting better and better lol first we get cm7, then xboarder fixes his AOSP rom due to cm7 , then faux comes out with a cm7/AOSP OC kernel... this phone just became the best out , easily.

Part Four said:
Wiped cache, dalvik, flashed 1.78 then thermal patch. Rebooted. Getting constant reboots shortly after ADW EX finishes loading. Won't stop.
Click to expand...
Click to collapse
hm... my beta tester has tested with 1.78 GHz version and verified that essential capabilities were working correctly.

Part Four said:
Wiped cache, dalvik, flashed 1.78 then thermal patch. Rebooted. Getting constant reboots shortly after ADW EX finishes loading. Won't stop.
Click to expand...
Click to collapse
I tried the 1.78 and worked but bootlooped during cf bench, odd because I have been able to run the 1.78 kernels before but we shall see. I'll be testing heavily tonight.
Edit: Okay she's running just fine on 1.5 so maybe my phone cant handle 1.78.......anymore ....??

faux123 said:
hm... my beta tester has tested with 1.78 GHz version and verified that essential capabilities were working correctly.
Click to expand...
Click to collapse
I don't doubt it. All phones are different. With this 1.78, my phone would freeze and reboot after ADW finished loading, but all of your 1.78 versions worked perfectly for me on Melvin's Beast ROM. Trying 1.56 now.

[KERNEL][EAS][8.0/8.1/9.0][GPUSC] Proto8 Kernel [Ofast]

{
"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"
}
Proto Kernel
Huawei Honor 9, P10 and P10+​
This kernel is aimed for optimal relation between Performance and Battery on the Honor 9 and the P10 family.
It's built with Function and Optimization in mind, no mile-long list of Features and unnecessary Bloat.
P10/P10+ users should download appropriate version.
Users with CN versions (AL-00's, TL-00's, C636 Region and alike) must also download appropriate version (CN) or it will cause a major bootloop.
As of August 23rd, following recent Huawei decisions and intentional provocation of issues with custom firmware, EMUI 8 is only Officially supported up to B369. It will work with more recent versions up to September Patch but WE WON'T TAKE ANY BUG REPORTS FROM THEM.
OpenKirin 8.1 Roms and HavocOS-hi3660 are Officially supported, Compatible with other Treble 8.1 and 9.0 Projects BUT WE ADVISE STRONGLY TO BASE YOUR TREBLE ROMS ON B368 OR B369 AT THE MOST.
DISCLAIMER
I'm not responsible for bricked devices and nuked SD Cards or the inability of reading instructions. Unlocking bootloader, flashing kernels and such, voids your warranty. If you have any doubts or don't know what you're doing, SEARCH, READ and then ASK. And i can't and therefore won't respond to issues without logs.
FEATURES
- Compiled with Linaro AArch64 GCC 5.5 2017.10 and GCC 4.9 2017.01 (CN Versions) (ARMv8,A53 Optimized)
- Native ARM big.LITTLE CPU Driver while keeping Huawei's specific SMP Flow for Kirin SoC
- HiSi GPUFreq driver and Frequency Hopping Spread Spectrum feature
- UV (UnderVolt) on both CPU Clusters and GPU for better efficiency (All thanks to @nutcasev1.5)
- Energy Aware Scheduling (EAS) with "Schedutil" CPU Governor
- blu_active and blu_schedutil CPU Governors
- CAF CPU Boost driver and SchedTune Boost v3
- GPU Scene Aware (set as default)
- Maple, SIOPlus and Zen additional I/O Schedulers
- Aggressive GPU Suspend on Low Frequencies
- Swap and zRam disabled
- NTFS R/W Support
- Reduced Kernel Wakelock Sources by 90% in relation to Stock
- Advanced TCP Algorithms with "Westwood" Default
- Reactivation of the "setenforce" command
- Huawei's Analytics Engine disabled
- Capacitive Button Fix by @zxz0O0
- Wireguard VPN Support
REQUIREMENTS
- Unlocked Bootloader
For EMUI 8:
- TWRP Recovery - @zxz0O0 TWRP Mandatory for the H9
- EMUI 8 Stock Firmware up to B369 Officially Supported. Others may work.
For Treble 8.1 and 9.0:
- TWRP for 8.1 - Get it here -> Link
- You will have to place Zips on external SD because this TWRP can't decrypt internal storage.
- OpenKirin Projects and HavocOS-hi3660 Officially supported. Other projects should work as well.
ACKNOWLEDGEMENTS
- Huawei/Honor for the source code
- @osm0sis for the AnyKernel2 and AIK tools
- @zx2c4 for Wireguard
- @eng.stk for his awesome blu_active and blu_schedutil CPU Govs
- @franciscofranco for the small bits and pieces that just make things work
- @zxz0O0 for initial tips on EMUI8 boot structure and the Capacitive Button Fix
EAS DISCLAIMER
- It is possible, as reported on other device threads, that EAS may increase your active battery drain during the first 2 or 3 cycles of usage. This is normal. Just continue to use the device normally and it will tune itself to your use and battery life will stabilize afterwards.
DOWNLOAD H9
AFH
DOWNLOAD H9 CN
AFH
DOWNLOAD FOR P10/P10+
AFH
DOWNLOAD FOR P10/P10+ CN
AFH​
XDA:DevDB Information
Proto8, Kernel for the Honor 9
Contributors
JBolho, nutcasev1.5
Source Code: https://github.com/JBolho/Proto
Kernel Special Features: EAS, UnderVolt, GPU Optimization, Persistent Spectrum Support, Wireguard
Version Information
Status: Stable - Final
Current Stable Version: 5.1F
Stable Release Date: 2018-10-24
Created 2018-04-21
Last Updated 2018-10-24

ProtoSSC, Changelog, Init.d Script and EMUI8 Theme
Q&A, Proto-Spectrum System Control, Proto init.d Script and Proto EMUI8 Theme
Proto-Spectrum System Control (ProtoSSC)
- Spectrum App - Google Play Link
- Spectrum System Control - AFH Download
"What is Spectrum and ProtoSSC?"
Spectrum, to put it simply, it's a quick and easy way of changing between Kernel settings oriented for 4 different scenarios, using pre-programmed profiles. More info? Check out the XDA link:
Spectrum App XDA Thread
Huge thanks to @frap129 for this work (and for Maple I/O too by the way)
ProtoSSC is a set of intructions that will give you full power over your system, completely eliminating Huawei's Management and Override Framework, replacing it with Spectrum-based Management, without having to mess around with files on internal storage.
Profiles are now built-in and are persistent after reboots (read notes)
ProtoSSC Instructions
First download the SSC flashable zip for your device file from the link above and place it on external SD card
Go to <root>/vendor/etc and delete the "perfgenius_boost_policy" and "perfgenius_config" XML files.
Go to <root>/vendor/bin/hw and rename (do not delete) "[email protected]" and "[email protected]" (just add ".bak" in the end)
Go to <root>product/etc/xml and delete the "uniperf_config_cust" XML file.
Go back to <root>/vendor and open the build.prop, find the lines "ro.config.hw_perfgenius" and "persist.sys.iaware.cpuenable" and change them from 'true' to 'false'.
If you were already using Spectrum, on your Internal Storage, delete the Spectrum folder, along with the profiles. Leave the Spectrum app installed.
Reboot to TWRP and flash the SSC file and reboot. (If you do not have Spectrum app installed, install it - Play Store link is above). Just give root permissions to the app and set whatever profile you want to use.
Every SSC Profile is now EAS based and separated by device family and was designed and tested for each purpose.
Every single profile has also some degree of underclocking, according to its design and purpose.
Therefore, we don't want to hear any noobs ranting about Antutu points.​
Balance - Designed for normal everyday use. Best balance between performance and SOT.
Performance - Designed for more demanding use, heavy multi-tasking and heavy Camera usage.
Battery - Designed for the best Battery life while maintaining minimal settings to avoid lags. GPU and Big cluster capped to minimum frequencies.
Gaming - Specifically designed and tested for sustained performance with heavy 3D gaming.
IMPORTANT NOTES:
After a lot of headaches and trying to figure all this Huawei system out, with the precious help of people at fRom Future Roms TG Group, and of course the ProtoKernel Testing Team, we finally made the profiles 100% persistent, and CPU/GPU freqs will no longer be overriden by the system.
There is only one logic exception to this, and that is of course, the Thermal Engine. Suffice to say, we will never mess with this.
These devices are not gaming consoles, i've heard the complaints, and i adjusted Boost settings on Gaming profile to be less agressive and underclocked the Little Cluster as well. With highly demanding games it will heat anyway, but should be better now. I take no complaints regarding PUBG or hour-long gaming sessions.
What is the Proto init.d Script and how do i use it?
- The Proto init.d Script tweaks the TCP buffers to optimize Mobile Data performance and enables the USB Fast Charging by default.
The script is best used with Magisk and you have to place it under <root>/magisk/.core/post-fs-data.d or <root>/sbin/.core/img/.core/post-fs-data.d depending on Magisk version.
Download is attached to this post as a zip file.
There's a Proto EMUI8 Theme? Where do i get it?
Right this way! --> Download Proto Kernel EMUI 8 Theme
Put it on Themes folder on Internal Storage and it will show up on your Themes app.
"My device started to lag a bit, what's happening?"
- If this occasionally happens, you really should know that rebooting your device every other day is a good thing. Swap and ZRam are dead for good and i'm not bringing them back.
Enjoy!
Version 5.1F - 10.24.18 [Final Feature-Development Release]
- Upstreamed to Linux 4.4.159
- Disable Huawei's D.U.B.A.I. functionality (No More Analytics for the H Company)
- Optimize build for big.LITTLE (GCC 5.5 based version only)
- Full Rebase of EAS to AOSP
- Implement Schedutil Governor
- Port Blu_Schedutil from OP6 Blu_Spark Kernel
- Deprecate Sched Governor
- Fix and Implement WALT (Window-Based Load Tracking)
- Add Tuned Zen I/O Scheduler (Now part of SSC Balance Profile)
- Separate SSC Profiles between Honor9 and P10 family (avoids error spamming on init logs and tailored freqs)
- Update Wireguard
- It's recommended you use the Kernel along with SSC and the init.d Script
Older Versions:
Version 3.0R - 09.19.18
- Upgrade to Linaro GCC 5.5-2017.10 (Keep Linaro GCC 4.9 for CN versions)
- Upstreamed to 4.4.103 - Kernel now on par with stock K970
- Increased Buffer on GPUFreq driver
- Port HiSi JPEG Processing Engine
- Update Wireguard to 0.0.20180910
- Update on SSC - All profiles are now based on EAS with heavy frequency customization
- Revert Proto init.d Script back to v1 due to Huawei's poor implementation of Skia
Version 2.5R - 08.20.18 [GPU Supercharger Edition]
- GPU - Reduce TLB Pressure and Prevent Memory Fragmentation
- GPU - Port and Optimize HiSilicon GPUFreq Driver and FHSS GPU Feature
- GPU - Re-Tune Scene Aware and Disable D.U.B.A.I. Analytics on GPU Govs
- Update Wireguard to 0.0.20180809
- Optimize Async I/O for SSD Storage
- Disable HiSi PerfHub
- Minor FS Optimization
- Initramfs Optimizations
- Minor Memory Fragmentation Optimization
- Updated Proto init.d Script to v2
Version 2.0R - 06.29.18 - Major Milestone Update
- Upstreamed to 4.4.73
- New Optimal Timer Frequency - 156HZ Set as Default
- Go Tickless - Enable Full Dynticks System
- Power Efficient Workqueues can now be toggled
- Revert CPU DDR Link Enabling and other HiSi CPU Functions
- Keep Kirin Specific SMP Flow but move to ARM big.LITTLE CPUFreq Driver
- Reduce Kernel Max Wakelocks down by 90% relative to Stock
- Minor RAM and DevFreq Tweaks
- GPU Scene_Aware Tuned for Power Efficiency
- Minor Log Spam on CPU's Silenced
- Reduce Timeout to Stop Processes and Enter Sleep
- Optimized Sound Output Gains and Eliminate Rates below 16Khz
- Implement UKSM 0.1.2.6
- Upgrade SchedTune Boost to v3
- Major Update to Spectrum Profiles to accomodate new features as well
- Update Wireguard to 0.0.20180620
Version 1.7.1R - 06.02.18 - Minor Fix Version
- @zxz0O0 Capacitive Button Fix now included
- Update Wireguard to 0.0.20180531
Version 1.7R - 05.28.18
- Upstream to 4.4.63
- Implement USB Fast Charging Capability
- Minor Efficiency Tweaks to Sched, SchedTune CPU Boost and LMK
- Removed Sociopath TCP Algorithm (Not needed, performance similar to Westwood)
- Update Wireguard to 0.0.20180524 and make it built-in instead of module
- Updated Spectrum Profiles
- Introduction of Proto init.d script - Tweaks TCP and Enables the USB Fast Charging by Default
Version 1.6R - 05.19.18
- Upstream to 4.4.52
- Add FRandom RNG Driver
- Add Dynamic SchedTune Boost
- Update Westwood TCP Algorithm
- Add Boeffla Wakelock Blocker
- Fix for possible Entropy depletion
- Update Wireguard to 0.0.20180519
Version 1.5R - 05.10.18
- Add blu_active CPU Governor and CAF Boost driver for non-EAS users
- Enable CPUFreq DDR Link
- Enable HiSilicon Low Temp CPU Frequency Set
- Timer Frequency set to 300HZ
- Powersave, Userspace and Conservative CPU Govs no longer available
- Automatic Process Group Scheduling Support
- SMT Scheduler Support for Multi-Threading Optimization
- Disable Scheduler Logging to reduce Overhead
- GPU Scene Aware - Battery friendly balanced GPU management. OpenGL may suffer, Vulkan is favored.
- Add Powersave GPU Gov for users that really don't need any GPU performance
- Maple I/O Scheduler tuned and set to default
- ZRam Disabled
- Entropy Tuned for improved performance
- Add FSync Toggle capability
- Disable CRC checks
- NTFS File System R/W Support
- Enable CleanCache Driver
- Skip Kernel Sync on Suspend
- Disabled Huawei Root Scanner
- Add Sociopath TCP Algorithm
- Update Wireguard to version 0.0.20180420
Version 1.2R - 05.04.18
- Add Maple and Tuned SIOPlus I/O Schedulers (SIOPlus now default)
- Tuned CFQ and Deadline I/O Schedulers
- Updated Sched Governor to Kirin970 .103 Source
- Updated CPUFreq Drivers and Governors to Kirin970 .103 Source
Version 1.1R - 04.26.18
- [FIX] Knuckle Gestures now work
- Reverted Huawei Max Freq. Detection for Increased Granularity on "big" Cluster
- Sched Governor now tuned for faster Freq Ramp-Down - [This may affect Benchmark Performance but not device overall performance and/or behaviour]
Version 1.0R - First Official Release 04.21.18
- Linaro AArch64 GCC 4.9 2017.01 (ARMv8,A53 Optimized)
- UnderVolt CPU/GPU by @nutcasev1.5
- Activate built-in EAS and set "Sched" Governor as default
- Enable Kirin Hotplug Flow for big.LITTLE
- Enable Aggressive GPU Suspend on Low Frequencies
- Deactivated Swap
- Reduced Kernel Wakelocks by 50%
- Set CFQ as Default I/O Scheduler
- Renamed Interactive Gov to bypass EMUI Governor Overrides
- Set Westwood as Default TCP Algorithm
- Reactivated "setenforce" command
- Added Wireguard VPN Capability

YES! a custom kernel, will take a look at this with AOSP oreo.
You say it under volts the CPU, is it possible to allow CPU OC'ing, since the A73 cores can hit 2.6GHz according to ARM, but we get stuck with 2.4GHz?

ambitiousButRubbish said:
YES! a custom kernel, will take a look at this with AOSP oreo.
You say it under volts the CPU, is it possible to allow CPU OC'ing, since the A73 cores can hit 2.6GHz according to ARM, but we get stuck with 2.4GHz?
Click to expand...
Click to collapse
The frequency is there on the kernel CPU files but it's not being considered, and plus, the max frequency is locked by Huawei on a hardware config file on vendor partition that sets all kinds of parameters. So far, fortunately, we managed to get around the override on that file that forced "interactive" to be default governor, no matter what was set on kernel, or else, EAS with its Gov as default wouldn't be possible.
But tampering with the file itself is not an option at this point in time.

JBolho said:
The frequency is there on the kernel CPU files but it's not being considered, and plus, the max frequency is locked by Huawei on a hardware config file on vendor partition that sets all kinds of parameters. So far, fortunately, we managed to get around the override on that file that forced "interactive" to be default governor, no matter what was set on kernel, or else, EAS with its Gov as default wouldn't be possible.
But tampering with the file itself is not an option at this point in time.
Click to expand...
Click to collapse
Ah, ok, still nice anyway, maybe someone will find a way to get around this lock.

ambitiousButRubbish said:
Ah, ok, still nice anyway, maybe someone will find a way to get around this lock.
Click to expand...
Click to collapse
Time will tell. Huawei's manner of doing things is a bit tricky. They set one thing on the kernel but then override it on the rom, or on Vendor (because of Treble compatibility)
I'm still pissed at them for switching to 64bit audio drivers exclusively, which nukes the ability to use currently available audio mods.

so , hang on, on the AOSP rom, i am able to change the CPU governor, and it DOES have an effect (bench on interactive gave ~180000 antutu v7, on performance gave ~200000) so, is it a setting in vendor, if its in the ROM itself, then a custom ROM might allow modifications from the kernel to take an effect, though the ROM may have to exclusively support the feature.

ambitiousButRubbish said:
so , hang on, on the AOSP rom, i am able to change the CPU governor, and it DOES have an effect (bench on interactive gave ~180000 antutu v7, on performance gave ~200000) so, is it a setting in vendor, if its in the ROM itself, then a custom ROM might allow modifications from the kernel to take an effect, though the ROM may have to exclusively support the feature.
Click to expand...
Click to collapse
You misunderstood me. You can change the governor after boot with any kernel management app, that's not the question. (I use KA for example)
But if you do not use one of those apps, the governor by default is interactive, even if you go into the kernel code and change it to something else. (that's why we had to find a way to override that)
Also, that vendor file sets Performance as governor during boot, and sets different governors also when the device is charging.

oh, ok, yes, that makes sense

Use su.d or service.d for change govs or sched like you wish with time wait until process found.
I use this way for my mod .
My H9 have no values stock , cpu at Lmk and no kernel app

k1ks said:
Use su.d or service.d for change govs or sched like you wish with time wait until process found.
I use this way for my mod .
My H9 have no values stock , cpu at Lmk and no kernel app
Click to expand...
Click to collapse
That's not a user-friendly solution. It's not even a solution in itself when it comes to developing...
If I want my kernel to be set a certain way, I have the obligation to make it so, without telling users to follow extra steps... Furthermore, no user should be forced to root in order to have a kernel work as it is intended. This is flash-and-forget, no extra steps needed.
If a certain user doesn't want to use it as-is, then of course, they can install a kernel app or use your method to set things their way, but that's out of my control or responsibility.

JBolho said:
That's not a user-friendly solution. It's not even a solution in itself when it comes to developing...
If I want my kernel to be set a certain way, I have the obligation to make it so, without telling users to follow extra steps... Furthermore, no user should be forced to root in order to have a kernel work as it is intended. This is flash-and-forget, no extra steps needed.
If a certain user doesn't want to use it as-is, then of course, they can install a kernel app or use your method to set things their way, but that's out of my control or responsibility.
Click to expand...
Click to collapse
It's a solution anyway.
By the way, great to see a custom kernel here.
Good initiative.

k1ks said:
It's a solution anyway.
By the way, great to see a custom kernel here.
Good initiative.
Click to expand...
Click to collapse
Thank you!
In the meantime i've been looking through some files and there are things that may be possible to improve but require root access and "manual labor" since TWRP still can't flash stuff on certain partitions.
If i can validate them with my testing, they may end up as some form of "Optional Root-Only Additional Optimizations" but the goal should be to provide something that performs without extra work.
Anyway, any and all feedback is appreciated, this device has great potential.

Nice work bro.. Will definitely give it a try.. :good:

JBolho said:
Thank you!
In the meantime i've been looking through some files and there are things that may be possible to improve but require root access and "manual labor" since TWRP still can't flash stuff on certain partitions.
If i can validate them with my testing, they may end up as some form of "Optional Root-Only Additional Optimizations" but the goal should be to provide something that performs without extra work.
Anyway, any and all feedback is appreciated, this device has great potential.
Click to expand...
Click to collapse
What do you mean " TWRP still can't flash stuff on certain partitions " ??
Twrp flash well .
If you want some support for the optionnal root add.
Yes great potential , sadly Huawei does not do like the others.

k1ks said:
What do you mean " TWRP still can't flash stuff on certain partitions " ??
Twrp flash well .
If you want some support for the optionnal root add.
Yes great potential , sadly Huawei does not do like the others.
Click to expand...
Click to collapse
Last time I checked, it still couldn't mount system... But thanks for the suggestion, this is still a work in progress, Huawei's methods are a bit mind bending and we're still figuring out what works and what doesn't. But there's still much room for improvement, I'm sure.

JBolho said:
Last time I checked, it still couldn't mount system... But thanks for the suggestion, this is still a work in progress, Huawei's methods are a bit mind bending and we're still figuring out what works and what doesn't. But there's still much room for improvement, I'm sure.
Click to expand...
Click to collapse
Of course , for sure . Stille much.
About mount system , i can help.
My mod that I develop on G+ need to mount system and mount root img too and works perfectly.
Works on most Huawei devices , H9 , P9 , P10...
Twrp Oreo manage successfully this step.
New Magisk use another way to mount because .img is in /data/adb/**.

@JBolho your kernel is working on my P10 (VTR-L29c432 Oreo b365), it's pretty fast I'm impressed with it, great work!
Update: Wifi and Bluetooth not working.

Working great on latest 362 ROM with KangVIP341. Safetynet passed, setenforce supported. But I still can not make VIPER4ANDROIDFX work in any way. Also nandroid backup is impossible from latest TWRP 3.2.1-0 v3. Error 255.

This kernel work on honor 8 pro.

[EXYNOS][GalaxyNote4][N910C/U/H/S/L/K][UNOFFICIAL] LineageOS 18.1 12/31/2022

{
"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 the Samsung Galaxy Note 4 (N910C/H/U/S/L/K | N915S/L/K | N916S/L/K) ​
--> Personal Notes <--
20221231 Release notes :
Happy to be able to still work on this device whenever the time allows, Lineage 18.1 Android 11 is here, comes with a good number of bug fixes and optimizations. and fixes some old issues we struggled with in past versions, Audio is still sadly a big downside of lineage roms however it is good enough for every day use and media consumption.
I have updated all the wikis on SourceForge, and ROM is mirrored to AFH.
Further more, i will be compiling PixelExperience 11 and releasing it soon, since sadly there is no RR-OS with android 11.
Android 11 itself is moving to EOL, so sooner or later i will have to start working on 12, so that is in the pipeline, other things such as TWRP will also get an update next year.
There isnt much traction to the note 4 anymore, but im happy some people still find it usable to this day
universal543
Happy new year everyone!
SourceForge mirrors, Wiki and TWRP/Bootloader is all found here Head over to WiKi for instructions.
The main device repo contains bug reporting and tracking found here it is the most updated bug list page and you are able to provide your own bug reports there following the steps below.
Submitting new issues/Requests
First read existing issues and the F.A.Q Below to ensure its not a duplicate/workaround
Head over to universal5433 for logging and issue reporting guide
provide as much info as possible and upload your logs on the forum
old release notes
20220430
This is more or less a minor release, You can dirty flash it, Main key points is fixing encryption and few other minor things.
Ive also included VR Support which enables Gyro sensor in VR, however it is VERY funky and you need to force enable the Gyro service in Google VR Services
RR builds are compiled and will be released along side this, with the same changelog as 17.1 however ive also compiled FaceUnlock packages and enabled SystemInfo overlay
20220421:
Hey everyone! Glad to be back again for another release, This one has been in development for couple months now, and comes with massive upgrades and improvements, the most major is a full transition into Exynos7420 Oreo graphics drivers, which modernizes our device graphics stack significantly, and finally allows us to use proper OMX media codecs which solves many issues including the dreaded low quality playback! (You no longer need to flash FakeDeviceInfo)
Further more the new GPU driver significantly boosts performance in games and UI which is always a welcome (including fixing graphical glitches in games)
Other major fixes include full encryption support, Please refer to Updated TWRP to perform first time encryption setup, i must warn however, Encryption might interfere with future rom flashes, so only use it if you can keep your data backed up, as it will fully deny you access to it from TWRP.
This release also includes fixes for the random reboots, and Audio leakage, sadly this does not address the tiny microphone quality, so that remains an issue, Please refer to bugs for an uptodate bug list and instructions on how to easily report new issues
Big thanks to @Fuadmoin , @ISoreo and @TrisTanster for a ton of help with testing
20210630:
Builds for all variants have been updated, this release has been a WIP since April, ive done quite alot of changes for memory management, and added zRAM with LZ4 compression, to significantly improve our RAM situation.
Ive also fixed a broken sdfat driver that caused random reboots, and over all did a clean up of the kernel, removed old commits, updated some drivers, and more importantly, ive removed "ALL" custom GPU modifications, as they cause graphical issues in most games, and overheating, this means there no longer is an option to overclock/undervolt GPU. for now atleast.
finally, ive added a binary to help with N910H devices, which now allows them the option to go to settings > mobile networks > and pick 3G (full guide in F.A.Q) to fix SIM issues
Change-log wise this is a "small" update, but it hopefully addresses various stability problems, i have not done much work in audio tho, nothing ready for release, but i will be looking into that moving further.
03/08/2021
Update : I have released N910U builds with full sim support, they are available in the download section Sim calls / Data and SMS were all tested. it should be at the same level of bugs as other models now
03/05/2021
Alright i finally have time to release the next set of builds, i have done alot of work again on Audio to make it more stable.
and other fixes overall for modem / sim. i have used it for the past 3 days with my sim in it, and its alright.
i have also made a magisk module which you need to flash if you want high quality instagram (and other apps) video playback. all info in F.A.Q
I still have no idea how N910H will perform, so let me know if it works or not. if sim is buggy, try to manually force 3G APNs
N910U Now can show baseband info but still will not load or detect simcards. so no progress there.
We are down to few bugs, i am going to try to tackle some boring tasks in the next releases, like selinux and encryption, i am hoping to get us enforced soon, and maybe encrypted. after that i will probably re-do all our device trees. in case we ever get all the bugs resolved, we might apply to lineage official
2/17/2021
This batch of releases should hopefully address the random reboots and sim issues faced by many, i have also did entire audio from scratch, which would be fun to experiment on, i could not test it fully so i am going to expect that some calling scenarios might not work, would love to know about them.
i would like to also mention that the power management in this build has been re-done and settings > battery > profiles actually do use custom tunable similar to stock ROM, you may override the frequency i set for CPUs via HKTweaks but i personally think its better for over all stability and battery life
i should also mention that performance in general is miles better than both 16 and 17.1 builds of the past, as i found a big flaw in the kernel
over-all these set of builds carry a ton of improvements and fixes, and many missing commits that we should have had ages ago.
Enjoy and do let me know how it goes, to report any issues, follow the guide below on how to capture useful logs
2020 NOV
Alright everyone, so i have taken the stable state of our lineage 16.0 trees and decided to just go for 17.1, i have basically observed the same bugs (wifi thing on idle, no video recording in default cam app and encryption) so figured it was worth it to just spend the extra time to upbring 17.1, i have noticed a ton of improvements myself, i dropped certain hacks, and repaired a bunch of stuff in the tree, and fixed some critical 16.0 bugs related to GPS, Wifi and a ton others. I hope you enjoy this release, and please let me know how it goes, i am basically down to 2 or 3 testers at this point as everyone i knew already left this device, and i personally suck at testing, i loaded my phone with gapps micro, nova prime launcher and my general social apps / debugging tools. and so far its solid, There are some additional notes make sure to read below regarding registering fingerprint, as it gets stuck but actually takes in the FP information.
regarding continuing 16 builds, i dont know honestly, the build server i use is already crowded and building for 5 devices is too much to handle, last 16 build might be the last for a while.
Hope you enjoy this release!
Also BIG WARNING : Dualbootpatcher is no longer a thing with 17.1, it wont work ,dont ask me for support. the tool is deprecated
Lineage 16 release notes :-
Alright, it took a lot of work and effort, but finally our device is running Android Pie in a state that is considered "usable" by myself and the testers. There is still a lot of room for improvement but for now the current C/H build is good enough. S/L/K and U builds will follow later after the C/H one is tested, and while i get myself a server.
This project is only possible due to the awesome people who helped me get my foot into AOSP development, which is very different from what I'm used to. In no particular order, our thanks to @Lunarixus , @ripee , @Stricted (especially for commits that fixed RIL) @tripLr , @bonuzzz and many others from various communities who helped indirectly by sharing their device trees on GitHub.
I will continue to work on Lineage 16.0 and hopefully Lineage 17.0 in the future. I am enjoying AOSP more than TW at the moment.
Expect other flavors of AOSP Pie to come out. I was going to release Havoc but it seems to have a problem with incall UI when you install gapps, so I'm skipping it for now.
If you appreciate the effort behind this, don't hesitate to leave a thanks, provide constructive criticism and maybe consider donating some "totally not illegal stuff" over at my paypal
Documentation
- Our project is also at SourceForge
TWRP
- My builds (3.5.9) WIth encryption support - XDA
ROOT Method
Magisk
- Simple follow Install instructions , Make sure to enable Magisk Hide to restore SafetyNet functionality
- i recommend Magisk V23 + Magisk hide for most usage
Google Apps
Open GApps
- Pick ARM > Android 10. No MicroG support currently
or
BiTGApps
- Pick ARM Package
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
Bootloader/Modem
- Latest Packages here
Hope you enjoy this ROM!
--> Quick Notes about this project <--
ROM is stable for daily-usage.
Only the N910C version is tested by me.
All Exynos models support full functionality (Sim , calls etc)
For Stable Camera (Photo/Video) Use this GoogleCamera or XDA Thanks @Kaper_20 and enable camera2Api
Lineage 17.1/18.1 DOES NOT support dualboot patcher!
The kernel is fully customizable using HKTweaks by corsicanu: Github
--> Known Bugs <--
Footej and This GoogleCamera or Custom Opencamera XDA can record videos only
Kernel is Permissive
Microphone quality outside of calls is weak
Issues Page
--> Credits <--
Special and massive thanks to retiredtab for his contributions to the Exynos5433 project on the Galaxy Tablets!
@bonuzzz for his work in los-15.1 and exynos5433 Tablets and @dl12345 for his los-14.1 contributions
@stricted for help throughout this project, and porting modern BSP for exynos5xxx
@Alastor89 for help with custom powerHAL and contributions from Galaxy S7
@ripee & @tripLr for contributions to maintain the trees and build server
[*][user=8096767]@lukasb06 for contributions in exynos7420
@RaymanFx & @erickwill for their work in maintaining this device on CyanogenMod 13.0, which helped both directly and indirectly with this project.
@lineage project and all team members.
If you helped with this project and I forgot to add you, please PM or mention below.
Thanks for the best testers you could wish for :
@Fuadmoin for extensive N910S/L/K Testing
@ISoreo for extensive N910C Testing
ck on telegram for N910U testing
@Voytec83 @claude96 @Enginyaman @MrNova @podiwadda @muddii_yasser @Mohelsayedplus @SypeR_ @exalented @Seemanthinis @clewisit
Downloads, Change-logs and F.A.Q Below
Source Code: github
ROM OS Version: 11.x
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Bootloader/Modem and TWRP 3.5.9 Encryption
Based On: Lineage OS 17.1
Version Information
Status: stable
Stable Release Date: 2022-12-31
Created 2019-06-09

Downloads and changelogs
Track changes on RefinedChannel : Telegram
Come hang with us on our chat : Telegram
My TWRP (3.5.9) For all Galaxy Note 4 Exynos Variants With Encryption : XDA
This project is also hosted on SourceForge with links to ROM,s Recovery and Bootloader Packages.
--> Downloads <--
Lineage 18.1 (12/31/2022 - STABLE)
N910C/H (treltexx) MD5 : f04e4d721f00944fb69d1e722a596d1b
N910S/L/K (trelteskt) MD5 afd9a56cbbf149b95caafba69565efa4
N915SLK (tbelteskt) MD5 : 8b1313779913f456cb2aaf446d545f6c
N916SLK (tre3calteskt) MD5 : cb852552c3d0295e7afc9251d97d446d
N910U (trhpltexx) MD5 : 636b8a2f0305ef5cbb2c377fdf463ff5
SourceForge : Download
AFH : Download
Note : Build 12/31 Is compiled on 12/29 and 12/30
Old Builds (Only on AFH and SourceForge)
Lineage 17.1 (04/30/2022 - STABLE)
N910C/H (treltexx) MD5 : 510fbbada80fb21eccacb22cdd8b9943
N910S/L/K (trelteskt) MD5 93f6b140d3af105d93718264db5ad9cb
N915SLK (tbelteskt) MD5 : 724e3ad16b217a0ccd53d4ca08a5ea3c
N916SLK (tre3calteskt) MD5 : c21c8c014d1dab3174fe783dd9451094
N910U (trhpltexx) MD5 : 7e5944265b2980d9eb33eff8b2875f95
SourceForge : Download
Lineage 17.1 (04/21/2022 - STABLE)
N910C/H (treltexx) MD5 : 5d3006cec330316f5187aab14c8ec3c7
N910S/L/K (trelteskt) MD5 12fa00de2dfa0affcaab2bd590b72454
N915SLK (tbelteskt) MD5 : 70754e3490c9576899db1e7632e555d8
N916SLK (tre3calteskt) MD5 : cc01e77e0b5e26e122427ddaa41d790f
N910U (trhpltexx) MD5 : 4ee91c68117f2ef77a960dbf1eb771c4
Google Drive : Download
SourceForge : Download
Lineage 17.1 (6/30/2021 - STABLE)
N910C/H (treltexx) : AFH | MD5 : ac96cb3104b2e2b7a85fab8b6ce8ac06
N910S/L/K (trelteskt) : AFH | MD5 : ff84c1b4d4f4fdef8b0382efd1fe8fdc
N915SLK (tbelteskt) : AFH | MD5 : 79e104f0984b0cfa2f9ae88cdf42a42d
N916SLK (tre3calteskt) : AFH | MD5 : 6f1c70a84b40131281d519d659723625
N910U (trhpltexx) : AFH | MD5 : 31e4ef4ec43af360ecaac704f37ff6bb
Google Drive mirror : Download
FakeDeviceInfo v2 : GDrive | AFH (Read more about it in F.A.Q)
Lineage 17.1 N910U Update (3/08/2021 - STABLE)
N910U (trhpltexx) : AFH | MD5 : 331659c66e1dcd82ec0be81de7899bd6
Google Drive : Mirror
Lineage 17.1 (3/05/2021 - STABLE)
N910C/H (treltexx) : AFH | MD5 : a2da420d64b450988f5b23c61120bf07
N910S/L/K (trelteskt) : AFH | MD5 : 762cef4d9353bfc9a0eed7e7b139db9e
N915SLK (tbelteskt) : AFH | MD5 : da3924b4ceff4793bb5a7f9d10e3fca5
N916SLK (tre3calteskt) : AFH | MD5 : ab09e57d034dc3dd5f94dd7b45d96f8d
N910U ALPHA (trhpltexx) : AFH | MD5 : 8d610b1f348990850e527ba544d3d1f6
Google Drive mirror : Download
FakeDeviceInfo : AFH (Read more about it in F.A.Q)
Lineage 17.1 (2/17/2021)
N910C/H (treltexx) : AFH | MD5 : a04e33f9b9143a5e1bddf84b02da2425
N910S/L/K (trelteskt) : AFH | MD5 : ce1a4711a2f9da5801c0a6ef6a2472e8
N915SLK (tbelteskt) : AFH | MD5 : 09826bb4adba8e472f2d77dc337493eb
N916SLK (tre3calteskt) : AFH | MD5 : 8c511737528abf6fdbf6576b77fed985
N910U ALPHA (trhpltexx) : AFH | MD5 : 0694c9a1d3bc9da0c2037ce82b263244
GoogleDrive Mirror : Download
Calls patch : Download
Lineage 17.1 (11/23/2020)
N910C/H (treltexx) : AFH | MD5 : e8de4fa2e53d21ab59c9524c2c09fec9
N910S/L/K (trelteskt) : AFH | MD5 : d2b38f59afc461035f6723551d1716bd
N915SLK (tbelteskt) : AFH | MD5 : b4cbf809ebdd176cb74bdd4294cbc79c
N916SLK (tre3calteskt) : AFH | MD5 : 87da8b64428d52215149efdc0a4c06c9
N910U ALPHA (trhpltexx) : AFH | MD5 : 030c8cfeb8412fb1ed594e3bc946445b
GoogleDrive Mirror : Download
Lineage 16.0 (11/01/2020)
N910C/H (treltexx) : AFH | MD5 : a09788f0384b7d10924acb1467603f48
N910S/L/K (trelteskt) : AFH | MD5 : 48950d5032f0721d1e2bd892a61baf1f
N915SLK (tbelteskt) : AFH | MD5 : 082461f5c5099aac5a200cb2100f48c9
N916SLK (tre3calteskt) : AFH | MD5 : a61060895aae647b42b0107d1e50bc69
N910U ALPHA (trhpltexx) : AFH | MD5 : 6221a2d991083778c502dd5764d6ebe9
GoogleDrive Mirror : Download
->> Lineage 16.0 builds (10/19/2019)
N910C/H (treltexx) : AFH | MD5 : 488840aca19725b0003f5d262da95b2f
N910S/L/K (trelteskt) : AFH | MD5 : 04681665fa88a1c4eacd56e42067bd09
N915SLK (tbelteskt) : AFH | MD5 : c7c975bd401f1e5a5a1ea3c7f8486631
N916SLK (tre3calteskt) : AFH | MD5 : c72ec56a7f67d6d57ab78759f9375718
->> Lineage 16.0 builds (10/10/2019)
N910C/H (treltexx) : AFH | MD5 : c26c8cedf315398c002c4c7629eb2b56
N910S/L/K (trelteskt) : AFH | MD5 : 0b7cf4305d160f7a42c5d5342c1a74cb
N915SLK (tbelteskt) : AFH | MD5 : 0a302764053ce8e1ef666a3f34e97698
N916SLK (tre3calteskt) : AFH | MD5 : a91239b9335bc79231a1ec2bc8e5572c
--> Changelog <--
Lineage 18.1 Update (12/31/2022 - STABLE)
Update and fix trees for Android 11
Update various Packages and drivers/hidls
Cleanup the device trees (leftovers/unused)
Update LPM (offline charging) to Samsung Android 11
Fix Fingerprint first enrollment lag/animation
Place volume on left
ZRAM update (75% Size, Priority, Apply early on init, discard flag)
Update WiFi packages/overlays
Enable WiFi Display (Miracast)
Update NFC Package
Add Custom LiveDisplay (Supports all MDNIE modes)
Switch to 2GB Dalvik VM Config (instead of 4GB)
Enable AAudio MMAP Support (Route through ALSA MMAP/NOIRQ Mode)
Remove broken HEVC Decoder (Causes hangs in streaming)
Fix Notification LED patterns
Enable Haptic on Select text
Cleanup and update overlays
Disable MAC Randomization
Update Memory Pinner list
Adjust default lineage settings (Disable lock/unlock sound, Vibate while ringing)
Other minor/misc optimizations
Fix R22P0 GPU Temp code
Fix Slow Audio in calls
Adjust Power Profiles to have extra performance from big cores
Disable Problematic Hotplug on big and small cores to fix lag / BT playback etc
Sync source to latest lineage Dec patch
Adjust performance overall
Kernel Changes​
Revert higher min clocks
Revert overclocking support
Revert Undervolting
Revert custom HMP Mods
Restore Stock CPUFREQ/HMP For now
Set Audio Sample rate to 48khz by default
Fix R22P0 GPU TMU
Lineage 17.1 Minor Update (04/30/2022 - STABLE)
- Include VR Support Pacakges
- Fix bootloop caused by encryption
- Resync latest LOS Source
Lineage 17.1 Update (04/21/2022 - STABLE)
* This is a cumulative release of the past couple months
- Fix interactive governor performance issues
- build missing OMX hidl
- update media configs to fix some playback issues
- Switch to N935FXXS7CTJ2 OMX to fix video recording (screen record/footej)
- Increase min cpu clock to 700mhz
- restore stock little cpu boosting frequency
- Revert Agressive hotplug power saving mods
- Fix bluetooth audio suttering when screen is off
- Switch to Exynos7420 Oreo R22P0 GPU
- Update Gralloc to oreo buffer
- Patch camera to work with new gralloc
- Fix AdaptivePlayback low quality issues
- add 4K camera recording profile (ofc wont work)
- re-do media configs and bunch of other **** for oreo graphics
- update power_profiles to use proper power values
- Fix Power management in PowerProfile switcher (Balanced / Powersaving and performance now properly apply)
- Add custom audioroute which fixes various Audio issues (leakout in headphone jack, some echo, other audio route issues)
- Enable AOSP dynamic audio processing
- Reserve 128MB of internal storage for critical system operations (to avoid losing data when internal is full)
- Fix parse errors in media configs
- Fix MFC dec/enc permissions
- Improve RIL mobile data stability / latching onto network
- Remove unused things such as DRK, F2FS and deprecated camera configs
- Add Encryption support (Follow F.A.Q For how to get encrypted)
- Add 2017 August Vendor patch level
- Fix USB MIDI mode crash
- Remove unsupported audio sampling rates to avoid extra processing
- Fix WiFI Direct / P2P
- Significantly reduce Drain caused by broken P2P
- Add back GPS NTP server configs
- Fix-up and update XTRA configs for GPS
- Remove unsupported software decoders
- Revert broken audio processing in the lineage audio HAL
- Fix random reboots caused by invalid GNSS/GPS config
- Disable legacy hardware keystore
- Switch from proprietary keystore/tee to OSS for future support
- Various fixes to USB / MTP
- Add a fix for WiFi turning off after doze
- And a bunch of other minor things here and there in the device trees
Kernel :-
- Fully re-do USB upstream to fix weird issues with MTP
- Fix FBE Encryption
- Switch to OSS Mobicore driver
- Remove default Boeffla block list as it broke WiFi and other parts
- Update interactive governor
- Disable broken/unused governors
Lineage 17.1 Update (6/30/2021 - STABLE)
- Sync GPS headers with exynos5420
- add patch for our old gps hal
- remove custom LMK stuff
- add ZRAM configs
- cleanup LMK
- add binary to detect device and set 3g/4g and proper codename/fingerprint
- support devices with engineering bootloader
- Remove problematic old commits from kernel
- re-do memfd and sdcardfs updates for Q
- backport zpool/zbud/zsmalloc and zRAM drivers
- Disable ZSWAP, and samsung swap (vnswap)
- Enable 1.5GB LZ4 ZRAM
- add proper LMK driver
- improve powerHAL frequency changing
- Downgrade sdfat driver to 2.0.6 to fix random reboots
- Add FreeForm multiwindow lineage patches
Lineage 17.1 N910U Update (3/08/2021 - STABLE)
- Fix simcard recognition
- Fix mobile data
- Fix voice call verbs and scenarios
- Now fully functional Sim calls, 3rd party calls, SMS and mobile data
Lineage 17.1 (3/04/2021 - STABLE)
- Fix modem startup on N910C/H/U that caused random reboots and sim issues overtime
- improve modem stability and fix a bug that caused the phone to panic if you unlock it fast after boot
- Enable Full screen gestures (See F.A.Q for how to enable)
- Replace custom fingerprint service with stock AOSP one
- Disable camera debugging and custom params that cause issues
- Rework media profiles to improve camera video quality in gcam
- Fix media performance issues to fix playback issues (Read F.A.Q for quality fix for instagram)
- Remove buggy AptXHD bluetooth codec and keep Aptx only
- Rework DRM service for full L1 support (No secure L1 playback yet)
- Disable absolute volume to fix bluetooth audio issues
- Add Wifi/Gps wakelock group to prevent issues on long uptimes
- More fixes to disable buggy P2P/WiFi Direct spam
- use low-end video profiles for smoother playback in some apps
- Add back and fix missing NFC
- Massive Audio rework to fix issues listed below :-
- Fix calls on earpiece, speaker, bluetooth and headphones for C/H/S/L/K
- Fix microphone issues on speaker calls
- Fix microphone issues on video calls
- Fix bluetooth call issues on all models
- Fix an issue that caused headphone volume to leak from speaker
- Fix an issue that caused earpiece to work when doing bluetooth calls
- Add custom workaround to fix no incall volume and other audio routing when you boot muted
Old releases changelogs
Lineage 17.1 (2/17/2021)
- set default gpu clock to 600mhz to fix instability
- add FB notifier for power hal
- reduce mobicore logging
- fix HMP up/down tune to fix performance issues
- disable P2P Spam
- add support for lineage/twrp recoveries in the device tree
- add odex optimizations
- let aosp only compile the needed resources for our DPI
- add RAM pinner and pin SystemUI, graphics and runtime to RAM
- organize ramdisk into vendor
- add FastCharging hidl to turn on / off fast charging in settings
- add improved SQLITE overlays for app database optimization
- add custom max_volume warning for headphones
- remove guard that made flipflap (sview) not compile on korean variants
- build custom powerHAL
- add stock interactive profiles in powerHAL (balanced, performance and power saving)
- let the powerHAL manage CPU FREQ for all 3 modes and use stock powersaving freqs for max clocks
- overall powerHAL now has real management now and multiple tunable presets
- remove camera param debugging that clutter logs
- rebrand our custom hardware HALs into universal5433
- enable vibration intensity control in settings for some options
- update calling overlays and signal overlays
- organize app overlays in device tree
- add some props for HWC
- add mali gpu props
- fix-up core services startup in ramdisk
- let zram go across all 1.5GB of swap
- add AOSP RCS packages
- disable NFC debugging
- properly override AOSP APNS
- remove outdated configs and features from tree
- add fixes for random reboots
- update and improve audio hal / policy
- add basic support for audio cancelation (not fully working yet)
- re-organize stock aosp audio effect support
- fully reworked audio mixers
- redo mic quality / gains for all mics including headphone mic
- redo verbs and channels for audio recording
- reduce and remove clutter from mixers and update the used paths for speaker/earpiece and heaphones
- let camera use both left and right microphones when recording
- remove useless BT code and try to improve stability in media (untested in calls)
- commonize mixers_path for all variants
NOV 24 limited Test build changelog
- Fix OpenCL and Vulkan devices
- Improve UI performance and scrolling
- Disable loggy script to not fill /cache and cause issues. use adb for debugging
- Add fixes for bluetooth SCO (calls)
- Switch to better dalvik-heap config
- expose our opencl and vulkan devices to apps
- properly set max surface buffers to avoid lag over time
- Fix APN issues that broke LTE , 3G on some phones
- Fix Bluetooth stability issues / stuttering
- Increase proximity detection range to match stock
- overall graphics and UI improvements
Lineage 17.1 (11/23/2020
- Rebased trees and update to lineage 17.1 running android ten
- resolved an issue that broke GPS + RIL Connection and affected GNSS Locking
- Updated widevine and implemented clearkey to match modern devices with netflix playback support (requires magisk hide + reboot and some time to show up on the store)
- Updated kernel net driver significantly to resolve connectivity issues
- Remove broken/unsupported WiFi display that caused severe draining
- Fixed Fingerprint for android Q (read F.A.Q For more details)
- Allow direct booting from offline charging mode
- Added logging service to help with user debugging (When facing issues zip me /cache) read F.A.Q if you want to disable it
- Improve network scanning for RIL
- Improve graphics performance
- Early boot system for faster booting speeds
- Include official lineage power HAL which works better on our phones
- Apply fixes for media playback that required hacks previously
- and everything else Android ten brings!
Lineage 16.0 (11/01/2020).
ROM :-
- Updated to latest lineage sources with October 2020 Patch
- Switched to new BSP to compile most blobs (including video , display etc) big thanks @Stricted
- build and update OMX from BSP to resolve many codec issues
- Fix graphical glitches / issues during games (pink stuff)
- remove unused shims from the trees and do general cleanup
- update GPS shim and and improve its stability
- implement MultiHAL Sensors wrapper to resolve rotation and other sensor issues
- Disable broken CPUSETS
- update WiFi Configs and disable broken wifi features
- update TCP and other throughput configs
- Fix spammy P2P wifi logging
- bring back argosd service to fix slow WiFi / lag when downloading (tested upto 260mbps)
- Fixes to Wifi during Doze
- build open source bluetooth blobs with some call fixes
- update and adjust SWAP rates and switch to ZRAM
- disable nearby service by default which makes wifi unstable when bluetooth is active
- use second mic when using speaker calls to avoid echos
- other misc mixer and audio changes
- Disable GPU errors caused by unsupported screen fade effect
- Fix Front camera in stock/3rd party
- fixed video recording in footej camera and its quality to 1080p
- Fix headphone mic one more time
- Add workaround for muted incall audio
Kernel :-
- Remove broken wakelock controls
- implement devfreq boost driver by @Lunarixus
- update LMK driver to resolve issues with memory leaks
- properly kill GPU DVFS control from the driver
- adjust GPU interactive governor
- Fix an issue that made the GPU stuck at 100% utilization with min frequencies (this also resolved serious lag issues)
- bring back stock input booster settings (to maintain decent performance).
Lineage 16.0 (10/19/2019)
1- Fixed low quality video in instagram/twitter and so on by fixing AVC decoder (And encoder was improved)
2- Fixed offline charging animation
3- inline encryption with stock (untested)
4- Tons of fixes to WiFi, will remain working when screen is off, and more stable in games (and enabled background scan/batched scan)
5- Generally improved the quality of video playback / recording (to inline with stock)
6- LowMemoryKiller tweaks added that should help with the memory leak issue
7- Enabled burn-in protection
8- Added some fixes for mediaserver and made it more stable (It will crash less often now, but it will if you try hard enough)
9- Many changes to ramdisk to fix missing nodes (NFC, DVFS, GPS And sensors)
10- Adjust LowBattery warns (to inline with stock)
11- fix some errors in miracast so it works more often
12- Entire rework to the GPU to fix Graphical glitches, crashes and many more to heavy games (PUBG, CSR, COD etc)
13- Removed 100mhz GPU clock, set default min 266, max 600 as stock, removed 800mhz overclock option (Max is 730)
14- Sync with latest lineageOS source
15- And other misc changes to fix performance and battery in general
Lineage 16.0 (10/10/2019)
Cumulative changes from all the previous test versions
1- Re-work Audio fully with a new mixer_path based on stock tinyucm conf
2- Fix call echo in all scenarios (3rd party calls not tested)
3- restore stock gains (the ones we had were all over the place)
4- fix headphone mic in 3rdpaty apps and in calls
5- add missing wideband/narrowband scenarios
6- update the lineage audio hardware hal
7- restore mic level to stock without hurting voice recorders
8- Fix memory issues (with improved LowMemoryKiller and swap)
9- fix random shutdowns due to low memory after long useage
10- Set the minimum GPU frequency to 160
11- Set the GPU to be always online (due to lack of HWC, this fixes performance issues)
12- reduce the effect of touch booster to save battery
13- Disable swipe-up gestures
14- Massive liveDisplay fixing (ColorProfile , Displaymode (Night/day) , Color temperature , Outdoor mode And color calibration support)
15- Other performance improvments
16- Improvments to calls by reverting some broken changes
17- removed AudioFX (Qcom only)
18- added lineage vibration hal
19- removed custom gnss hal that wasnt needed
20- more fixes to GPS
21- slight changes to sensors
22- built healthd hal (still no offline charging)
23- enabled and fixed HWC
24- added a prop that helps with performance
25- Fixed NFC so it no longer ****s everything up when its turned off (and now can be turned on without also ****ing said things up)
26- other misc changes you can see in git
27- Fixed all HWC leaks (therefore you shouldnt have random reboots anymore)
28- Disabled always_on GPU for better battery saving
29- Animations and layers will have improved performance
30- removed a workaround that delayed boots
31- critical kernel changes to remove many workarounds we had by :
32- updated sdcardfs driver to remove legacy stuff
33- updated sdfat driver and enabling it for exFAT
34- updated EXT4 driver and using it for EXT2/3 instead of dedicated drivers for both
35- updated USB and ADB so we dont need legacy stuff anymore
36- updated and enabled F2FS Driver (support not tested)
37- patch a ion leak
38- updated wireless/wifi driver to remove the need for workarounds
39- Added back AudioFX as it works
40- DRM changes
41- default hotspot name
42- fixes to rotation sensor (it works fine with/without location enabled here, but if it as slow, enable location)
43- remove duplicated tether config
44- fix nfc config
45- Updated powerprofiles
46- slight changes to meda and camera set for the future
47- synced with latest lineage sources
TLDR : tons of fixes, better performance and having an actual usable phone.
Lineage 16.0 (9/21/2019)
1- Full hardware video playback (no lag even on 1080p60 playback)
2- LiveDisplay enabled (color mode changing) with more features to be added later
3- updated and enabled back ambient and aod (not fully tested yet)
4- added and updated APN and SPN configs
5- improvments to camera and include camera2 instead of snap
6- fix a mic bug that introduces artifacts in audio recording
7- OMX and media fully redone based on herolte
8- Rotation sensor should be more robust now
9- few changes to spen
10- Bluetooth range and issues fixed
11- improve RIL for SLK variants
12- Fix NFC issues on N916 variants
13- improvments to NFC on intl variants
14- set default color mode to cinema for vivid colors
15- Removed a binary that caused SLK variants to over-heat
16- latest lineageOS sources
17- compiled stable builds for N910SLK|N915SLK|N916SLK
18- overall the build is more responsive and stable due to MFC/OMX fixes
Lineage 16.0 build (9/16/2019)
1- Fixed Video playback for 3rd party apps
2- Youtube and other social media apps will no longer freeze randomly
3- fixed an issue that took a toll on performance
4- over all the rom will be noticeably smoother
Lineage 16.0 initial build (9/14/2019)
1- Updated and reworked the tree all together
2- A decent powerHAL modded to N4
3- Bluetooth APTX errors resolved
4- Fully fixed RIL (no workarounds needed)
5- Entire Kernel has been built from scratch
6- New binder, sdcardfs, and WiFi drivers
7- all the features of HeliosKernel built it and customizable
8- Updated brightness tables to conform with stock
9- removed ugly workarounds and hacks
10- Audio much more stable
11- stock APN , TCP configs and much more
12- Added more LED modes
13- Added AOD and ambient display support that kinda works
14- updated most libs and shims
15- built lineage trust and touch HALs
16- enabled gesture support
17- enabled smart pixels for ROMs that support it
18- And tons of other changes covered in the github source

F.A.Q And Notes
Q : How to use Encryption ?
A : First, head over to TWRP Thread And follow the notes for First time encryption setup (this involves formatting internal storage while using that twrp, This is mandatory as previous twrps did not create proper partition state for encryption), Then head over to settings > security > encryption > Encrypt Phone, the phone will reboot once or twice
Warning : Encryption will prevent TWRP from reading your internal storage at all, And encryption is very sensitive, any untested customization or mods might brick the ROM, and putting your data at risk, only use if required
UPDATE : You will bootloop if you did not set PIN/lockscreen in setup wizard before encrypting
Q : WiFi Wont Turn on
A : This is a bug in lineage-18.1 when you leave NearbyShare enabled and reboot, Turn it off or follow workaround in github
Q : How to Tune for Performance or battery life ?
A : Latest release offers proper Power profiles which can be adjusted in Settings > Battery > EnergySaver and Performance. The slider will adjust MAX CPU frequency as follows,
Power saving Big: 1.4GHz Little: 1.0GHz
Balanced: Big: 1.7GHz Little: 1.3GHz
Performance: Big: 1.9GHz Little: 1.4GHz
Q: N910H wont detect SIM / network
A: This is due to it trying to force LTE, Go to settings > network > mobile networks And change preferred network type to 3G, then enable and disable Airplane Mode. Here is a Video by @mvrul2k20 to explain the procedure
Q : Korean variants (S/L/K) have tube / robotic audio in calls
A : this bug is unfixable for now as those models rely on stock audio hardware effects to fix this issue, but we cant use that and open source H/W does not support them
Q : How to enable android 11 gestures
A : First you need to enable navigation bar (this will disable touchkeys) then go to gesture settings and enable full screen gestures
Q : Recommended camera app to use ?
A : This Google Camera : Download or Footej2 from the play store
Q: Whenever I try flashing any lineage- build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: Update your TWRP to 3.2.3 or higher available Here or newer
Q : Device is too warm
A : After first boot that is common, let the phone finish setting up and cool down
Q : How to get google apps ?
A : Go to Opengapps.org . Select ARM > 11 > [your choice] and flash opengapps*.zip after the ROM.zip
Q : How to get Root ?
A : Flash Magisk Root From Here (Recommended version 23.0 for better MagiskHide)
Q : How to tune the kernel ?
A : use HKTweaks app from @corsicanu : Github

Additional
Reserved

Reserved

Congrulations mate, keep it up. :good: After the Refined Nougat, you will be became an AOSP dev

Thank you very much for this build.
Thank you very much for this build.
I have flashed initial builds whenever they become available. Flashed build 9 2 hours ago on top of build 8, and I am testing it without a simcard at the moment.
Really appreciate your efforts in getting Android 8.1 to work on N910CQ.

Congrats!

Greatt

thank you very much brother, your the best and proud to be in your testing Team ♥

Cant thank you enough for your immense work on this abandoned but powerful device.. to others, it was totally unexpected that we would get this rom working in this condition for note 4. The development has been really positive and the rom is in a very usable daily state.
Glad to be part of the family and seeing this rom from its inception to its release is heart warming.
Cheers to all..

Finally...
Thanks boss, been waiting for this release since developing stage.
Im on 7th built, flashing 9th soon.

Anyone have a voice in WhatsApp very low??
I have this in my phone n910h

Zeus of Android has arrived...AGAIN!??
Thanks for Your amazing work for old-s(coolest) device Samsung ever made.
Exy5433 is like a phoenix - resurrects from ashes every year?

You again achieved an awesome work ! Keep it up

Well, true passionate work has paid off once more. Words are useless, but satisfaction is immense. In your face samsung, there is someone who deserves much more love and respect. Thank you again Anan

Only i can say is "THANK YOU VERY MUCH" GOD bless mate..

910cq , twrp 3.2.3
thanks you

Deleted

We'll lose the s-pen function with this rom tho, correct?

remove

about Deluxe Kernel
This kernel is born as an option. It is not necessary to look for a low latency experience and additives.
because this brings it to Moto G6 plus evert a low latency performance optimized throughout all the parts build
the balance of the governor add-ons and the latest stable caf patches for our android based on sdm630 good dexk support on android pie+ arrives
the next betas published in the evert test group. Good luck to all of us.
great job @ seba_3567
FEATURES
- add ASB-2019-07-05_4.4-p-release
- add ASB-2019-07-05_4.4-p
- add LA.UM.7.4.r1-05400-8x98.0
- add LA.UM.7.2.r2-01300-8x98.0
- Align file struct to 8 bytes (old 4)
- 53 warning fixed
- all commit old build
- TTL fixup & misc.
- all changes old build
and commit beta 1-5 (sorry file changes to trash)
- remove blu gov cpu
- f2fs update support
- Update GPU governor with adrenoboost support
-remove vendor verify
- set kernel ANXIETY (I O FILES ) for default
- optimize anxiety (L1 procesador cache)
- cache l1 improve and reduce latency
- proc: Remove verifiedbootstate flag from /proc/cmdline 2/2 (thank to @fjsanti and @SyberHexen )
-proc: Remove SafetyNet flags from /proc/cmdline 1/2
- Tune VM params
- evert_defconfig cleaner
- uv gpu (80mv)
- uv display
add LA.UM.7.2.r1-07200-sdm660.0 into on dexk
- add LA.UM.6.2.r1-12700-sdm660.0 into on dexk
- update v4.4.184 to v4.4.185 into on dexk (74 commits)
- camera driver update
- sound driver update
- soc update
- display driver update
- wireless driver update
v8.0 final
- fixed derps battery drein and latency error on last 7.3
- DSBOOST update
- sched: import schedutil from pixel 3a (add no active)
- blu gov problem (get no active)
- reduce latency all kernel
- Dexk get support boot GSI permisive
- update 4.4.181 to 4.4.182 (6 commit)
- update 4.4.180 to 4.4.181 (268 commit)
- add Alucard Hotplug
- msm: mdss: Boost cpubw devfreq device when a new frame is ready
- kernel: Boost whenever a zygote-forked process becomes a top app
- upstream-f2fs-stable-linux-4.4.y' (285 commits)
- power: boeffla: Block some wakelocks
- boeffla_wl_blocker: update to wakelock blocker driver v1.1.0
- boeffla_wl_blocker: update to wakelock blocker driver v1.0.1
- boeffla_wl_blocker: add generic wakelock blocker driver v1.0.0
-kernel: Don't allow IRQ affinity masks to have more than one CPU
- defconfig: Enable RCU boost
- Wait 1 second to turn off a cpu
- init: mark dm_setup as __maybe_unused
- LA.UM.7.2.r1-07000-sdm660.0
- mmc: queue: Do not attempt request merging
- block: Force requests onto their origin CPU
-init: bypass dm-verity and mount system directly
Mount system_a/system_b directly by reading androidboot.slot_suffix=
v7.0 final release
- add dts_eagle sound support
- wcd9335: enable interrupt requests for huwifi mode;
-Have Adreno Idler ramp down frequency quicker but increase idlewait t…
-PM / devfreq: Add an interface to boost devices when the screen is woken
-cpufreq: Introduce CPU wake boost driver
-disable crc check
- cpu oc tester
- it accelerates the CPU but it does not show the apparent
- increased speed apart from what the latency gains but it is bearable
- ARM: dts: Reduce the maximum voltage allowed for the panel
- ARM: dts: sdm660-pm: set LPM parameters from SDM845
- ARM: dts: sdm630-pm: set LPM parameters from SDM845
- add support cryto SHA512
- update bsboost set
- ram optimize
- mm: Bump dirty ratios
- fs: Reduce cache pressure
- mm: Do not reserve memory for admins
- mm: Keep dirty pages in ram for at least 80 seconds
- mm: Do not periodically writeback data
- Compact memory mostly when fragmentation occurs
- mm: Increase vmstat interval
- block: Reduce queue depth
- update 4.4.179 to 4.4.180: (267 commits)
- add LA.UM.7.2.r1-06900-sdm660.0 into pie (12 commit)
- set Always overcommit memory by default
- mm: Allow memory to overcommit to 80% ratio
- sched/fair: Tune the scheduler using Google's presets
- Improve headset detection to 1sec..
- increase ROOT_FREQ to 24600000
- DTS: Decrease BCL low battery threshold to 5%
- zram: set lz4 by default
- cpu uc (add new 300MHZ on 8cores)
- cpu more frequency
- ARM: dts: Reduce the maximum voltage allowed for the panel
- ARM: dts: sdm660-pm: set LPM parameters from SDM845
- ARM: dts: sdm630-pm: set LPM parameters from SDM845
- add support cryto SHA512
- update bsboost set
- ram optimize
- mm: Bump dirty ratios
- fs: Reduce cache pressure
- mm: Do not reserve memory for admins
- mm: Keep dirty pages in ram for at least 80 seconds
- mm: Do not periodically writeback data
- Compact memory mostly when fragmentation occurs
- mm: Increase vmstat interval
- block: Reduce queue depth
v5.0 :
https://www.androidfilehost.com/?fid=1395089523397957276
cpu: optimize
add more apis [12]
add more cpu gov (7)
add support for Dynamic SchedTune Boost
cpu: optimize driver
other changes
I deleted the other file
in which it contained changes}:
and more........
final pie release deluxe kernel
Download
https://t.me/evert_roms
check telegram group :good:
you like my job give me a cup of coffee:highfive: https://www.paypal.me/sebastian3567
XDA:DevDB Information
remove, Kernel for the Moto G6 Plus
Contributors
sebastian3567HD
Source Code: https://github.com/TeamDeluxe/android_kernel_motorola_msm8998
Kernel Special Features:
Version Information
Status: Testing
Created 2019-07-27
Last Updated 2020-04-08

Reserved
at the moment he cannot do the ZIP since I have social life c: put to that I invite the developers / cooks that includes the tree in his environment and someone wants to help with the zip can contact me a telegram @ seba_3567 and I give him permissions to the tree

Reserved
dexk get support for android 10 ! update soon

Thank you very much for posting this. I am eager to try this on my device, which has Havoc on it.
Just to confirm the installtion process. I assume that I would install the kernel, then flash Magisk.
Is there any need to reload TWRP (I noticed that you posted an updated flashable twrp on Telegram as well which I am eager to try).

Perfect
Great combination, Havoc and KernelDeluxe. Thank you

I have tested this on my phone using the latest version of Havoc.
Unfortunately, I experienced a couple of instances where the phone totally froze then restarted. I was in the middle of using firefox for android both of those times. Since the phone was non responsive, I was not able to get a logcat.
I am not sure if that behavior would be limited to firefox, at each of those restarts I had to set up my home screen widgets again and didn't want this to happen again so I reverted to the standard Havoc kernel.
If there are any tests or diagnostic information I can provide, I will be happy to do so. I can flash the kernel again and do that. I am just a bit wary of using it as a daily driver. Please let me know how I can help troubleshoot or if there is any information I can provide. Note, I didn't do any kernel tuning.
I am wondering what others may have experienced....

ew said:
I have tested this on my phone using the latest version of Havoc.
Unfortunately, I experienced a couple of instances where the phone totally froze then restarted. I was in the middle of using firefox for android both of those times. Since the phone was non responsive, I was not able to get a logcat.
I am not sure if that behavior would be limited to firefox, at each of those restarts I had to set up my home screen widgets again and didn't want this to happen again so I reverted to the standard Havoc kernel.
If there are any tests or diagnostic information I can provide, I will be happy to do so. I can flash the kernel again and do that. I am just a bit wary of using it as a daily driver. Please let me know how I can help troubleshoot or if there is any information I can provide. Note, I didn't do any kernel tuning.
I am wondering what others may have experienced....
Click to expand...
Click to collapse
it is normal if that compilation has a non-stable preliminary version

sebastian3567HD said:
it is normal if that compilation has a non-stable preliminary version
Click to expand...
Click to collapse
I totally understand and just wanted to report my experience.
I will try the next version whenever it comes out.
If I am not mistake, the "stock" kernel that comes with Havoc is an earlier version of this (If I am correct).

- proc: Remove verifiedbootstate flag from /proc/cmdline 2/2 (thank to @FJSanti and @SyberHexen )
-proc: Remove SafetyNet flags from /proc/cmdline 1/2
Hi, does this 2 thing mean i can use gpay and other safetynet sh.. without root, magis and bla bla with this kernel without a problem? Or it no longer works for gpay?

lsander said:
- proc: Remove verifiedbootstate flag from /proc/cmdline 2/2 (thank to @FJSanti and @SyberHexen )
-proc: Remove SafetyNet flags from /proc/cmdline 1/2
Hi, does this 2 thing mean i can use gpay and other safetynet sh.. without root, magis and bla bla with this kernel without a problem? Or it no longer works for gpay?
Click to expand...
Click to collapse
in theory yes

sebastian3567HD said:
in theory yes
Click to expand...
Click to collapse
Yup in theory but before i will unlock ky hootloader would be nice to know if somebody use it that way. I use a lot gpay for now that is why asking. Anyway thanks maybe i will unlock anyway. I hate stock roms

Hey, does this work on stock?

Would this make my phone faster game wise?

This will overclock my gpu or not..?
---------- Post added at 08:00 AM ---------- Previous post was at 07:54 AM ----------
This will overclock my gpu or not..?

Suport Android 11?

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer
Code:
/*
* 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
- EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.
- IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required). This will be fixed in a later update.
Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- When reporting bugs please post a logcat and/or dmesg where possible
Lastest TWRP version
- 3.6.1-9.2
Downloads
- Google Drive
Source Code
GitHub - lineage16-suez/kernel_amazon_suez
Contribute to lineage16-suez/kernel_amazon_suez development by creating an account on GitHub.
github.com
GitHub - lineage16-suez/device_amazon_suez
Contribute to lineage16-suez/device_amazon_suez development by creating an account on GitHub.
github.com
GitHub - android-extra/twrp_device_amazon_suez: TWRP device tree for Amazon Fire HD10 (2017)
TWRP device tree for Amazon Fire HD10 (2017). Contribute to android-extra/twrp_device_amazon_suez development by creating an account on GitHub.
github.com
Thanks
- @k4y0z and @xyz` for the bootloader hack
- @k4y0z for the initial kernel
- LineageOS

⏱ Change log / Release Notes
05 July 2022
- [fixed] Backlight HAL Errors
- [fixed] LiveDisplay not working
06 May 2022
- [fixed] Voice assist MIC not working
- [fixed] USB-OTG Ethernet
- [fixed] TWRP: MTP access
- [fixed] TWRP: Fixed USB-OTG
- [info] Added android.hardware.opengles.aep.xml permissions
13 April 2022
- [fixed] Terminal input via apps and adb shell
12 April 2022
- [kernel] Up-streamed to 3.18.140
- [kernel] Enable per user storage quota
- [kernel] Optimized build flags for Cortex-a53
- [kernel] Boeffla Wakelock Blocker Driver v1.1.0
- [kernel] Enable some TCP congestion algorithms
- [kernel] Westwood Default TCP congestion algorithm
- [kernel] Sdcardfs v2.0
- [info] Remove aptX bluetooth libraries for now
- [info] Mount /system partition early-mount style
- [info] Add vendor security patch
06 April 2022
- [fixed] Fix KernelUidCpuTimeReader errors
- [info] Revert audio HIDL from 2.0 to 4.0 back to 2.0 - our drivers aren't ready for this
- [info] Put storage permissions force close on the todo list
- [info] Chrome browser works
- [info] Jelly browser works
- [info] WeDo lego app works
Show Further History
03 April 2022
- [fixed] Magisk update by app
- [fixed] Storage permission issues (cause of some apps crashing)
- [fixed] Lego app not working (more info here)
- [fixed] Cannot switch wifi on after storage encryption enabled
- [info] Update suez defconfig in kernel to be more inline with aosp
- [info] TWRP 3.6.1-9.0 available from Google Drive (no encryption support)
- [info] Up-rev audio HIDL from 2.0 to 4.0
- [info] Disabled amazon logging functions in kernel
- [info] Disabled unused squashfs in kernel
- [info] Conditionally compile MTK_M4U in the ion kernel driver as our device doesn't use it
27 March 2022
- [reverted] WiFi changes from previous build
- [removed] 26 March Build
26 March 2022
- [fixed] Speakers continuing to play while headphones are plugged in
- [fixed] Disney+ crashing
- [didn't work for everyone] Slow WiFi throughtput
- [didn't work for everyone] 5GHz connectivity to AX-88U router and in general
- [didn't work for everyone] 5GHz connectivity to across all channels
- [info] Include Bromite Webview
- [request] WiFi: Can someone test connecting to hidden SSID's and report back?
- [request] Magisk: Can someone test whether updating through the application works and report back?
16 March 2022
- [fixed] MtkOmxCore crash
- [fixed] Better auto adjust on backlight
- [fixed] SIM card prompt
- [fixed] Changed battery capacity to 6300mAh
- [fixed] sdcard access for chrome and other apps
- [fixed] "There's an internal problem with your device." dialog
- [info] Explicitly enable sdcardfs
- [info] Refactor root init scripts
- [info] Remove deprecated storage_list.xml
- [info] Clean-up build.prop
01 March 2022
- [info] Re-build of 28 February version
28 February 2022
- [fixed] DRM Widevine L3 support
- [new] Signature spoofing (enable and disable via developer options)
- [fixed] Wired headphones not working
- [fixed] Backlight HAL crashing
- [fixed] Hardware OMX (MTK codecs now been used)
- [info] Disable camera completely until fully investigated to stop logcat spam
- [info] Enable OTG for ethernet in kernel
07 February 2022
- [fixed] OMX regression was breaking NewPipe and local video file playback
- [info] Clean-up amazon binaries - media playback should be better - config file mess
05 February 2022
- [fixed] Navbar icon corruption
- [fixed] Wallpaper corruption
- [fixed] Laggy graphics
- [fixed] High idle cpu usage
- [info] Updated amazon binaries to fireos 5.6.9.0
12 February 2021
- Initial Release

🛠 Worklist / Tasks
- [fixed] Bluetooth works
- [fixed] Audio works
- [fixed] Internal storage isn't accessible from any app
- [done] Sensors working
- [fixed] Touch sounds are working
- [done] Test audio format playback - mp3 working
- [done] Tested video playback with NewPipe which is working
- [fixed] WiFi signal strength not working
- [done] Support aptX-HD encoder for bluetooth
- [fixed] No adb during boot
- [fixed] WiFi working
- [fixed] Navbar icon corruption
- [fixed] Wallpaper corruption
- [fixed] Laggy graphics
- [fixed] High cpu usage
- [fixed] DRM not working
- [fixed] Hardware OMX (for the most part)
- [fixed] Wired headphones not working
- [done] Enable OTG USB for ethernet
- [fixed] Youtube black screen with audio
- [fixed] MtkOmxCore crash
- [fixed] Battery showing wrong capacity - reported here
- [fixed] "There's an internal problem with your device." dialog
- [fixed] SIM card prompt
- [fixed] Chrome cannot access internal storage
- [fixed] Poor WiFi throughput (potential cause of choppy video playback)
- [fixed] Disney app crashing (more info here)
- [fixed] Speakers continuing to play while headphones are plugged in
- [fixed] Cannot switch wifi on after storage encryption enabled
- [hold] Bluetooth not working properly - can't see issue here
- [fixed] Magisk update by app
- [fixed] Storage permission issues (cause of some apps crashing)
- [done] Upstreamed kernel
- [todo] TWRP: USB-OTG not working
- [fixed] USB-OTG Ethernet
- [fixed] TWRP: MTP access
- [todo] Voice assist MIC not working
- [done] Added android.hardware.opengles.aep.xml permissions
- [fixed] LiveDisplay not working
- [fixed] Backlight HAL Errors
- [todo] Shutdown after entering sleep mode (suspect cpu/gpu coming up in the wrong state -> overheating)
- [todo] Gapps > pico causing not enough space error
- [todo] Youtube black screen with audio
- [todo] Mirrorcast not working
- [todo] Multi-user not working
- [todo] Navbar problem when keyboard is in horizontal mode
- [todo] Playing videos over SMB failure after 30 min (more info here)
- [todo] Can't connect to hidden WiFi networks
- [todo] Lego app not working (more info here)
- [todo] Cameras not working (more info here)
- [todo] SELinux
- [todo] Intermittent high idle cpu usage
- [todo] Investigate L1 widevine support (L3 currently)
- [todo] Pass safetynet
- [todo] Device build fingerprinting
- [todo] Enable zram?
- [todo] Device encryption (TWRP)
- [todo] Battery idle mode
- [todo] Offline charging mode
- [todo] Low speaker volume
- [todo] Thermal Shutoff, overheating
- [todo] System partition needs to be increased in size to accomodate gapps

New Build is up
12 February 2021
- Initial Release
- Post #2 contains change log
- Post #3 contains task list
- Clean installation is required

Thank you for your great work! Can´t wait to try the new rom!
Just a few questions on build 12.february.2021:
DRM not working -> So netflix, amazon prime etc. isn´t working yet?
clean install required -> coming from lineage 12, factory reset and flashing afterwards will work? Or do i have to wipe anything specific?
Cameras not working -> both of them ? Or maybe just camcorder like in the early versions of your Los12?
Wired headphones not working -> i guess the headphone fix from previous versions (Los-12,Los-14) does +not+ work on Lineage 16?

cochonez1312 said:
Thank you for your great work! Can´t wait to try the new rom!
Just a few questions on build 12.february.2021:
DRM not working -> So netflix, amazon prime etc. isn´t working yet?
clean install required -> coming from lineage 12, factory reset and flashing afterwards will work? Or do i have to wipe anything specific?
Cameras not working -> both of them ? Or maybe just camcorder like in the early versions of your Los12?
Wired headphones not working -> i guess the headphone fix from previous versions (Los-12,Los-14) does +not+ work on Lineage 16?
Click to expand...
Click to collapse
Try netflix and amazon and let me know if anything needs looking into, I have started a tasklist so we can add items there.
Factory reset should suffice for clean installation.
Cameras not working at all, more to come on this. I understand why they are not working and it's not great news I know. I'll do a more detailed post on this.
The headphone fix from cm-14.1 might work or be adaptable to work on this rom. I am looking into a permanent solution for this.

I have faced these issues so far
1) Directly after first boot, i get the error message "Your device encountered a problem. Please contact the manufacturer". Anyways, I can proceed after tapping on OK.
2) I can only flash pico Gapps, any package larger than that throw error 70 (Insufficient system space). In older builds, i was able to flash the nano package. The system partition (1.5 GB) should be large enough to fit Gapps packages larger than pico.
3) The start assistant prompts me to insert a SIM card, although this device does not have a SIM card slot.
4) The three softbuttons are broken, as shown in the picture

BeniS98 said:
I have faced these issues so far
1) Directly after first boot, i get the error message "Your device encountered a problem. Please contact the manufacturer". Anyways, I can proceed after tapping on OK.
2) I can only flash pico Gapps, any package larger than that throw error 70 (Insufficient system space). In older builds, i was able to flash the nano package. The system partition (1.5 GB) should be large enough to fit Gapps packages larger than pico.
3) The start assistant prompts me to insert a SIM card, although this device does not have a SIM card slot.
4) The three softbuttons are broken, as shown in the picture
Click to expand...
Click to collapse
Point 1: I forgot to mention this initial message after boot. This is due to fixing the persistent and repeated camera hal crash and the way in which I had to stop that from happening, hopefully as a temporary measure. I'll add this to the OP so everyone is aware.
Point 2 and 3: I'll add to the list
Point 4: already on the list todo

A few more issues:
1) HD videos in Youtube app are not working. The video either stops or i'm just getting a blackscreen. 480p works.
2) The graphics is not very fluent and a bit laggy, especially when opening apps and scrolling within them. It seems that there's no graphics acceleration.

@ggow is playready crashing (DRM)? If so try to debug the crash with https://github.com/douglas-developm...987d31da8cda42c03b53fb988c18d77f3e297fffd16c4
As for the graphic glitches try adding:
Code:
PRODUCT_PROPERTY_OVERRIDES += \
debug.hwui.renderer=opengl \
debug.hwui.use_partial_updates=false \
debug.sf.disable_backpressure=1 \
debug.sf.latch_unsignaled=1 \
persist.sys.display.clearMotion=1
That fixed Graphic Glitches in 16.0 for my MT8163 tablet.

*****in danks ggow

Lineage 16 = Android 9 !!
OMG, never ever expected to see this on a 7th Gen HD10
Big thanks to ggow for bringing new life to our old "crap". The tablet isn't bad at all, so definitely worth to receive an update. Have to have a drink first to celebrate this, maybe will try the update next week. (I'm still on Amazon stock version, so I'll have to unlock first)

@ggow I may have found some useful information regarding the camera. While exploring why SuperSU wasn't working, I unexpectedly came across some logs. I did not save them, but I'm still trying to fix supersu and will grab them the next time I'm attempting a fix. It might be the smoking gun I'm not sure though.
In regards to supersu, I have figured out why it will not hold root access. For some reason it fails to obtain a root user account.
Code:
Error stderr: null, stdout: null, exit_value: 1
according to root checker, that is the only issue now. I have managed, I think, to rewrite or remove the scripts or lines of script in the files that lineage superuser uses. I'm not sure why it's doing this though. Flashing in twrp just causes a neverending boot animation. @ggow that's where I came across the camera logs, because after rebooting from flashing, I still get an adb connection so I ran a logcat, but aside from the camera, I didn't find anything useful. I made sure the files have owner root:root. I do know KingoRoot doesn't have an issue rooting. So the investigation continues.

Why are we pushing SuperSU? That's been deprecated and I've used Magisk on 12.1 and 14.1 successfully.

for the 11 thousandth time dragon supersu is DEAD stop using it use magisk in core only mode if you need minimal root handling stop pinging ggow because you refuse to join us in the year 2021 and use magisk like everybody else on xda

DragonFire1024 said:
I think the lack of space for gapps has to do with mounts. It sems things are confused to an extent because technically nothing is where it should be. For example, on the lin14 rom, SuperSU won't work and that's because it can't find the boot.img (it's looking in the spot where the img was prior to the unlock hack). I don't know why it won't work as a system install though.
I got init.d to finally work (lineage uses their own so you have to write a script in /system/etc/init and modify a line in init.cm.rc (in root directory) because lineage disables androids init.d I think that's where some of the issues are and part of why SuperSU doesn't work (superuser.rc).
Click to expand...
Click to collapse
the issue for gapps is the system partition size after installing los 16, is set incorrectly, not a mounting issue. supersu dont work because its not compatible and wont be, use magisk. the camera dont work due to a lack of proper drivers not to mention the coding is completly missing from 14.1 and 16 so dont bother trying to fix it yourself unless your compiling a new rom. this is just the first release and will get better in time. it boots and thats a start.

Understanding the Camera Issue:
@daniel_hk made a good post on understanding this:
REF: https://forum.xda-developers.com/t/rom-7-1-2_r36-27jan2018-lineageos-14-1-custom-roms.3513466/
Relevant Extract of the information
III. The Camera
After my first ROM was out, the most eye catching in the log would be the stack corruption in libcam.halsensor.so.
Code:
11-24 21:53:55.967 490 490 F DEBUG : #08 pc 00017459 /system/lib/libcam.halsensor.so (_ZN12ImgSensorDrv13getResolutionEPP34ACDK_SENSOR_RESOLUTION_INFO_STRUCT+60)
After study the source for mt6735, I found it was called within the blob libcam.halsensor.so. In the function ImgSensorDrv::getResolution(), an ioctl() call was passed to the kernel. I was thinking it was caused by user space data handling in the kernel. After a series of trials and dumping, I remarked that part of code from the kernel. The crash persisted. That means it was from the blob itself. I tried a shim library to replace the function ImgSensorDrv::getResolution() but the result is the same. That means the callee was responsible.
After some digging, I was pretty sure it was caused by the alignment (address sanitize) of struct addresses. The latest blob from Lenovo dev.1631 (also the latest for mt6752 devices) were built with gcc 4.9 Clang 3.6. Nougat now use Clang 3.8 by default. Those blob already have alignment support in Clang 3.6 might have issues with the new Clang 3.8.
What is address alignment? In short, a 32 bit processor can handle 32 bit at a time. It would be a easier for the register to locate memories in 32 bits (4 bytes) cells (aligned). If the head or tail for a block of memory is not aligned, extra code would required to separately handle those loose ends. The new clang compiler would fill leading bytes with its own algorithm to make the pointer or variable aligned. Why is ImgSensorDrv::getResolution() being "affected"? The argument of it is a pointer to ACDK_SENSOR_RESOLUTION_INFO_STRUCT. Its definition can be found in the kernel. It is a struct of an array of pointers to another struct. The source from Mediatek use direct reference to the address of struct variables all the time. This is inappropriate in sense of address alignment. Early compilers didn't handle alignments and won't have problem with that. Newer compiler would use its own algorithm to align the structs and pointers. I guess Clang 3.6 didn't handle the above complex struct as argument well. Nougat linker and loader are all built with Clang 3.8. Local variables are allocated at load time which might be handled differently. Thus a call to ImgSensorDrv::getResolution() would cause the stack corruption.
** Those interested may read this article for detail. **
1. Work around
Using older blobs built by gcc 4.8 or earlier might work. Jiayu S3's AOSP were using those old blobs. I'm new to K3-note. I don't think I have the patience and experience to test all the existing blobs. That's the main reason I uploaded the last two test ROM. Trying blobs and hoping some combination would work is passive. Stlport is also obsolete for some time now. I rather deal with the problem directly.
2. The solution
Without the source, building the whole blob is impossible. Even if we have the source from other devices, those custom parameters are unique to each image sensor. It's impossible to guess or back engineer...
If we can change the way ImgSensorDrv::getResolution() is being called or didn't touch the argument within the function. It would avoid the crash. Unfortunately, the function need to fill a local struct within the ImgSensorDrv class. That means it is not seen outside ImgSensorDrv. The only way is to replace the whole ImgSensorDrv class. Fortunately, it is self contained. We can write a wrapper to replace the ImgSensorDrv class only. The source from mt6735 or mt6595 are a bit different and obviously can't be used directly. Most of the struct can be cross referenced to the kernel source. There are two local sturct left unknown. One is for the commands sent to the kernel. The other is some info. collected from the kernel.
With the wrapper, the crash was gone but still no preview. I wrote a test HAL to dump the values in stock ROM. Guessing the values against the names was not a decent job. Fortunately, there were only a few differences. After nights of trial and error, I finally pulled everything together. Camera is working now! Video recording is still not working. Seems codec related. Some say it's not a problem "again". Hoping there will be some real solutions and helps soon...

ggow said:
Understanding the Camera Issue:
@daniel_hk made a good post on understanding this:
REF: https://forum.xda-developers.com/t/rom-7-1-2_r36-27jan2018-lineageos-14-1-custom-roms.3513466/
Relevant Extract of the information
III. The Camera
After my first ROM was out, the most eye catching in the log would be the stack corruption in libcam.halsensor.so.
Code:
11-24 21:53:55.967 490 490 F DEBUG : #08 pc 00017459 /system/lib/libcam.halsensor.so (_ZN12ImgSensorDrv13getResolutionEPP34ACDK_SENSOR_RESOLUTION_INFO_STRUCT+60)
After study the source for mt6735, I found it was called within the blob libcam.halsensor.so. In the function ImgSensorDrv::getResolution(), an ioctl() call was passed to the kernel. I was thinking it was caused by user space data handling in the kernel. After a series of trials and dumping, I remarked that part of code from the kernel. The crash persisted. That means it was from the blob itself. I tried a shim library to replace the function ImgSensorDrv::getResolution() but the result is the same. That means the callee was responsible.
After some digging, I was pretty sure it was caused by the alignment (address sanitize) of struct addresses. The latest blob from Lenovo dev.1631 (also the latest for mt6752 devices) were built with gcc 4.9 Clang 3.6. Nougat now use Clang 3.8 by default. Those blob already have alignment support in Clang 3.6 might have issues with the new Clang 3.8.
What is address alignment? In short, a 32 bit processor can handle 32 bit at a time. It would be a easier for the register to locate memories in 32 bits (4 bytes) cells (aligned). If the head or tail for a block of memory is not aligned, extra code would required to separately handle those loose ends. The new clang compiler would fill leading bytes with its own algorithm to make the pointer or variable aligned. Why is ImgSensorDrv::getResolution() being "affected"? The argument of it is a pointer to ACDK_SENSOR_RESOLUTION_INFO_STRUCT. Its definition can be found in the kernel. It is a struct of an array of pointers to another struct. The source from Mediatek use direct reference to the address of struct variables all the time. This is inappropriate in sense of address alignment. Early compilers didn't handle alignments and won't have problem with that. Newer compiler would use its own algorithm to align the structs and pointers. I guess Clang 3.6 didn't handle the above complex struct as argument well. Nougat linker and loader are all built with Clang 3.8. Local variables are allocated at load time which might be handled differently. Thus a call to ImgSensorDrv::getResolution() would cause the stack corruption.
** Those interested may read this article for detail. **
1. Work around
Using older blobs built by gcc 4.8 or earlier might work. Jiayu S3's AOSP were using those old blobs. I'm new to K3-note. I don't think I have the patience and experience to test all the existing blobs. That's the main reason I uploaded the last two test ROM. Trying blobs and hoping some combination would work is passive. Stlport is also obsolete for some time now. I rather deal with the problem directly.
2. The solution
Without the source, building the whole blob is impossible. Even if we have the source from other devices, those custom parameters are unique to each image sensor. It's impossible to guess or back engineer...
If we can change the way ImgSensorDrv::getResolution() is being called or didn't touch the argument within the function. It would avoid the crash. Unfortunately, the function need to fill a local struct within the ImgSensorDrv class. That means it is not seen outside ImgSensorDrv. The only way is to replace the whole ImgSensorDrv class. Fortunately, it is self contained. We can write a wrapper to replace the ImgSensorDrv class only. The source from mt6735 or mt6595 are a bit different and obviously can't be used directly. Most of the struct can be cross referenced to the kernel source. There are two local sturct left unknown. One is for the commands sent to the kernel. The other is some info. collected from the kernel.
With the wrapper, the crash was gone but still no preview. I wrote a test HAL to dump the values in stock ROM. Guessing the values against the names was not a decent job. Fortunately, there were only a few differences. After nights of trial and error, I finally pulled everything together. Camera is working now! Video recording is still not working. Seems codec related. Some say it's not a problem "again". Hoping there will be some real solutions and helps soon...
Click to expand...
Click to collapse
Yeah after you fix that you'll get mediaserver libc fatal crashes as I do in douglas.

MOD ACTION:
Thread cleaned.
Friends, please do not lose the focus of the thread. Discussions about other issues and multiple persons posting multiple ways of solving such issues etc make the thread cluttered.
The OP is there and answering queries.
Thank you for understanding!

ggow said:
🛠 Worklist / Tasks
...
- [todo] Wired headphones not working
Click to expand...
Click to collapse
thank you, @ggow, for coming back to Fire HD 10!!! ur recent works on HDX makes me thinking about it but its still >5yo tab.
for the wired headset, there is a fix available already: https://forum.xda-developers.com/t/...4-1-26-sep-2019.3973703/page-29#post-81763775
i have used it on both HD8 and HD10. hope it saves u some work!