Database Develop

KERNEL ❯ PIXEL 3 XL ❯❯ Proton Kernel • v19 • September 8 - Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth

KERNEL ❯ PIXEL 3 XL ❯❯ Proton Kernel • v19 • September 8
Proton Kernel • Pixel 3/XL
by kdrag0n​
This kernel has been discontinued as I no longer own my Pixel 3 XL and have moved on. The original post has been retained below for transparency, but I would strongly recommend using another kernel.
I am not liable if your phone explodes, stops functioning, or turns into scrap metal. I have no obligation to publish this kernel. However, if you provide an accurate description of your issue accompanied with logs, it is likely that I will at least look into your issue. By flashing this kernel, you acknowledge the potential risks it brings.
Introduction
Proton Kernel strives to provide the perfect balance of performance and battery life in order to create the best possible experience for your phone. Features are welcome if they are useful, within reason. The kernel has been debloated to reduce size and improve performance.
Compatibility
Stock and custom Pie ROMs are supported. Both the Pixel 3 and Pixel 3 XL are supported in the same package. Wiping cache isn't necessary. Magisk is retained, so there is no need to reflash it afterwards. The kernel may be flashed from TWRP or your app of choice.
Android Q is NOT supported, nor will it ever be.
Features
​ ​ ​ ​ • Latest upstream Linux 4.9.191
​ ​ ​ ​ • Latest Google August updates
​ ​ ​ ​ • Compiled with bare-metal GCC 9.1.0
​ ​ ​ ​ • Heavily tuned Spectrum and FKM performance profiles
​ ​ ​ ​ • Numerous configuration changes for performance, size, and battery
​ ​ ​ ​ • Heavily debloated for faster boot, enhanced security, and smaller download
​ ​ ​ ​ • Fast and versatile installer (modified version of @osm0sis' AnyKernel2)
​ ​ ​ ​ • Sound control (microphone and speakers only; @flar2)
​ ​ ​ ​ • Latest WireGuard VPN snapshot
​ ​ ​ ​ • KCAL advanced color control
​ ​ ​ ​ • A wide variety of battery and performance improvements from the Qualcomm, Pixel 3a, Snapdragon 855, and more kernels
​ ​ ​ ​ • CPU governors: performance, powersave, schedutil, userspace, ondemand, conservative
​ ​ ​ ​ • I/O schedulers: noop, deadline, cfq, anxiety, bfq
​ ​ ​ ​ • Various improvements from @Sultanxda, @arter97, @ab123321, @Freak07, etc
​ ​ ​ ​ • Vibration control (@flar2)
​ ​ ​ ​ • TCP congestion control algorithms: westwood, reno, bbr, bic, cdg, cubic, dctcp, highspeed, hybla, htcp, vegas, nv, veno, scalable, lp, yeah, illinois
​ ​ ​ ​ • Xbox and DualShock USB controller support
​ ​ ​ ​ • Simple LMK for improved memory management and reduced camera opening lag (@Sultanxda)
​ ​ ​ ​ • Assorted scheduler patches to improve battery and performance
​ ​ ​ ​ • Speculative page fault for faster app opening
​ ​ ​ ​ • Support for forcing fast charging (500 mA limit bumped to 900 mA for USB, 5V limit bumped to 9V for wireless)
​ ​ ​ ​ • Simple GPU Algorithm
​ ​ ​ ​ • AVB 2.0 and dm-verity fully disabled (allows custom boot animation on stock ROM)
​ ​ ​ ​ • Display tweaks
​ ​ ​ ​ • Speaker gain control and backlight dimmer
​ ​ ​ ​ • Efficient in-kernel CPU and memory boosting solution (modified version of @Sultanxda's work)
​ ​ ​ ​ • Improved overall performance and battery life compared to stock
​ ​ ​ ​ • Faster lock implementations backported from mainline
​ ​ ​ ​ • Lots of backports from the mainline kernel
​ ​ ​ ​ • Scheduler improvements and fixes from Qualcomm's Snapdragon 855 kernel
​ ​ ​ ​ • Support for common Realtek RTL815x USB Ethernet adapters
​ ​ ​ ​ • A few F2FS tweaks (namely Rapid GC) by @arter97
​ ​ ​ ​ • I/O prioritization by app groups (background, foreground, etc) when using CFQ (ported from Pixel 3a) for better UX during background app updates and other I/O-heavy scenarios
​ ​ ​ ​ • Countless other features and optimizations to enhance the overall experience
Click to expand...
Click to collapse
Think twice before enabling fast wireless charging because cheap chargers can cause your phone to heat up significantly more than usual, which damages the battery permanently. They may also cause temporary issues with your phone (such as ticking sounds) or irreversible damage to internal circuits. However, if used properly with a high-quality charger, there should not be any issues. Enable at your own risk. I am not responsible for any damage to you or your phone caused by this feature.
Downloads
Downloads and changelogs can be found here on GitHub. The topmost release is the latest. Alternatively, you can simply download the latest version here.
Join the Telegram group for beta builds and support
Donate to support development
XDA:DevDB Information
Proton Kernel, Kernel for the Google Pixel 3 XL
Contributors
kdrag0n
Source Code: https://github.com/kdrag0n/proton_bluecross
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v19
Stable Release Date: 2019-09-08
Created 2018-11-19
Last Updated 2019-09-09

FAQ
Q: Is my phone not secure anymore? You said you disabled security features for performance.
A: Not really. Kernel features such as CFI, stack protector, etc protect against potential attacks in a way where if an attack is detected, the phone will forcibly reboot. It doesn't prevent the attack in the first place. This kernel simply disables such features because they have a performance impact. Preventative security features such as SELinux are not disabled, nor will they ever be.
Some speculative execution mitigations such as SSBD have also been disabled. That's because these have quite an impact on performance. How many times have you heard of L1TF, Spectre, Meltdown, or anything of the like exploited in the wild?
Q: Why GCC instead of Clang? Isn't Clang better? Google switched to it.
A: No. I benchmarked Clang 8 with LTO, Clang 8, and GCC 8. Here are the full results.
Q: Do I need to flash Magisk after the kernel?
A: No. The kernel will keep Magisk if it's already installed.
Q: My phone randomly rebooted or locked up. / Apps are crashing.
A: Describe your issue accurately with detail and provide logs. It's easy to do with apps like Syslog or MatLog. If it's an unexpected reboot, grab all the files from /sys/fs/pstore for the log. For reboots the current logs (dmesg, logcat, etc) are useless - I need the logs from the previous boot, which are in pstore.
Q: How do I see what version I'm running?
A: Settings → System → About → Android version → Kernel version

Wonderful!

Welcome @kdrag0n let the fun begin!

Flashed using Exkm like I've done with all the other kernels. Lost Magisk FYI

drdrewdown said:
Flashed using Exkm like I've done with all the other kernels. Lost Magisk FYI
Click to expand...
Click to collapse
Sup Drew.
Are you using the canary build? That one has been giving some of us fits. I just flash both then reboot.
Sent from my crosshatch using XDA Labs

ridobe said:
Sup Drew.
Are you using the canary build? That one has been giving some of us fits. I just flash both then reboot.
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Nah just on Beta

drdrewdown said:
Flashed using Exkm like I've done with all the other kernels. Lost Magisk FYI
Click to expand...
Click to collapse
Hmm, I'll look into that. Using 17.3 myself.

kdrag0n said:
Hmm, I'll look into that. Using 17.3 myself.
Click to expand...
Click to collapse
Pretty sure it removed TWRP too, in case you run across something in testing

drdrewdown said:
Pretty sure it removed TWRP too, in case you run across something in testing
Click to expand...
Click to collapse
Looks like it corrupts the ramdisk so TWRP and Magisk won't work. Flash the kernel in TWRP until this is fixed. Hopefully I'll have an update out in a few hours to fix flashing in EXKM/FKM/other apps.
To recover from your current situation:
• Fastboot TWRP
• Flash TWRP installer
• Flash Magisk
• Flash Proton Kernel
You do not need to reboot recovery after flashing TWRP.

kdrag0n said:
Looks like it corrupts the ramdisk so TWRP and Magisk won't work. Flash the kernel in TWRP until this is fixed. Hopefully I'll have an update out in a few hours to fix flashing in EXKM/FKM/other apps.
To recover from your current situation:
• Fastboot TWRP
• Flash TWRP installer
• Flash Magisk
• Flash Proton Kernel
You do not need to reboot recovery after flashing TWRP.
Click to expand...
Click to collapse
Right on. Thanks for confirming

I'm showing lz4 zram compression enable by default, not ztsd fwiw

drdrewdown said:
I'm showing lz4 zram compression enable by default, not ztsd fwiw
Click to expand...
Click to collapse
That's caused by the lack of Magisk. It also won't work if Magisk is flashed after the kernel.

Version v2 has just been released to fix flashing in Android (via apps such as EXKM, FKM, etc), especially the loss of TWRP and Magisk afterwards. Along with that are some CFQ I/O scheduler and battery improvements, along with the removal of Adrenoboost as the code is extremely dirty and is not necessary for our device. In my testing, it didn't work at all. Get it here on GitHub.
Full changelog:
​ ​ ​ ​ • Fixed flashing in Android (EXKM, FKM, etc), especially preservation of TWRP and Magisk
​ ​ ​ ​ • Removed Adrenoboost
​ ​ ​ ​ • Backported some CFQ I/O scheduler patches from upstream
​ ​ ​ ​ • Added Sony scheduler patches for better battery (@_LLJY, @ab123321)
​ ​ ​ ​ • Removed blu_schedutil governor (almost identical to Pixel schedutil)
Click to expand...
Click to collapse
Direct download link
Enjoy!

kdrag0n said:
Version v2 has just been released to fix flashing in Android (via apps such as EXKM, FKM, etc), especially the loss of TWRP and Magisk afterwards. Along with that are some CFQ I/O scheduler and battery improvements, along with the removal of Adrenoboost as the code is extremely dirty and is not necessary for our device. In my testing, it didn't work at all. Get it here on GitHub.
Full changelog:
Direct download link
Enjoy!
Click to expand...
Click to collapse
Nailed it. Thanks
Removed the blusched it seems as well

Flashed v2 over frankenkernel with exkm. All good. Kept root and twrp.
Thanks

Proton Kernel v3 has been released to fix battery life. Get it here on GitHub.
Full changelog:
​ ​ ​ ​ • Fixed battery life by reverting major debloat
​ ​ ​ ​ • Increased entropy pool read/write thresholds
Click to expand...
Click to collapse
Direct download link
Enjoy!

Just flashed v3 with exkm no issues still have root.

Is there good battery improvement compared to stock? Standby on stock is terrible.

kdrag0n said:
Proton Kernel v3 has been released to fix battery life. Get it here on GitHub.
Full changelog:
Direct download link
Enjoy!
Click to expand...
Click to collapse
I don't know what magic you worked, but my idle drain went from ~4%/hr to 1.8/hr. Keep up the good work!

Related

KERNEL ❯ MI A1 ❯❯❯ Velocity Kernel • r9 • August 15
Velocity Kernel • Mi A1
by kdragon and tytydraco​
Flash at your own risk.
This kernel is abandoned. I suggest using other kernels such as Canting. Sorry for the inconvenience.
The original post follows.
Introduction
Velocity Kernel was made to provide the best possible experience on all devices. We strive to provide the perfect balance of performance and battery life. Features are also plentiful, but features that nobody uses will not be included. We also completely debloat all our kernels and aim for small sizes relative to other kernels. Due to the small size and careful debloating, boot time is also improved.
Compatibility
This single kernel ZIP supports both custom ROMs and Treble custom ROMs (GSIs). Simply flash the kernel after flashing your ROM of and it should work. Pie is fully supported.
The stock ROM is not supported.
Features
​ ​ ​ ​ • Latest upstream Linux LTS 3.18.118
​ ​ ​ ​ • CPU overclock to 2208 MHz for a good performance + battery balance
​ ​ ​ ​ • GPU overclock to 700 MHz
​ ​ ​ ​ • Undervolted CPU by 150 mV
​ ​ ​ ​ • Improved 3.5mm jack output
​ ​ ​ ​ • Energy Aware Scheduling
​ ​ ​ ​ • CPU governors: elementalx, zzmoove, yankactive, relaxed, alucard, nightmare, chill, blu_active, darkness, intelliactive, bioshock, impulse, ironactive, ondemandplus
​ ​ ​ ​ • EAS CPU governors: electroutil, schedutil, pwrutilx, sched, helix_schedutil, energy-dcfc, alucardsched, darknesssched
​ ​ ​ ​ • IO schedulers: fiops, zen, sioplus, row, tripndroid, maple, cfq, noop, deadline, bfq, fifo
​ ​ ​ ​ • Updated ExFAT drivers that support TRIM (faster long-term performance)
​ ​ ​ ​ • Compiled with latest Clang 8 revision 339049
​ ​ ​ ​ • Small size
​ ​ ​ ​ • Faster boot
​ ​ ​ ​ • Fast wakeup
​ ​ ​ ​ • Low latency
​ ​ ​ ​ • 500 Hz for maximum performance-latency-battery balance
​ ​ ​ ​ • ZRAM compressors: lzo, lz4, lz4hc, zstd (higher compressing)
​ ​ ​ ​ • Reduced pop when plugging headphones in
​ ​ ​ ​ • KCAL advanced color control
​ ​ ​ ​ • Wakelock blocker
​ ​ ​ ​ • Customizable CRC check and Fsync
​ ​ ​ ​ • Adreno Idler
​ ​ ​ ​ • Backlight dimmer (extremely low brightness)
​ ​ ​ ​ • Adreno Boost
​ ​ ​ ​ • Sound output control
​ ​ ​ ​ • Forced USB fast charge
​ ​ ​ ​ • Westwood TCP congestion control
​ ​ ​ ​ • Improved output on 3.5mm jack
​ ​ ​ ​ • Improved scrolling performance
​ ​ ​ ​ • Various optimizations from Google Pixel kernels
​ ​ ​ ​ • Faster NEON accelerated random data generator
​ ​ ​ ​ • Good battery life
​ ​ ​ ​ • Vibration intensity control
​ ​ ​ ​ • Double tap to wake
​ ​ ​ ​ • Latest WireGuard VPN snapshot
​ ​ ​ ​ • Removed legacy drivers
​ ​ ​ ​ • Sweep2wake, sweep2sleep, and doubletap2wake gestures
​ ​ ​ ​ • Updated Wi-Fi drivers
​ ​ ​ ​ • Optimized memory page copying
​ ​ ​ ​ • TCP ECN for faster internet on busy networks
​ ​ ​ ​ • DTS-Eagle support
​ ​ ​ ​ • Improved security
​ ​ ​ ​ • Full Kali NetHunter support (Bluetooth & Wi-Fi dongles)
​ ​ ​ ​ • Countless other improvements and optimizations
​ ​ ​ ​ • Flash and forget
Downloads
Downloads can be found here on GitHub.
The first release listed is the latest version.
Credits
Without the help and contributions of these people, this kernel would not exist:
​ ​ ​ ​ • nathanchance: upstreaming, kbuild commits, Flash kernel, many other commits
​ ​ ​ ​ • ghpranav: MetaPhoenix kernel, wake gestures on kernel_tissot (savoca, showp1984, ryan-andri), EAS, help, and more
​ ​ ​ ​ • franciscofranco: config options, fsync control, many other commits
​ ​ ​ ​ • Flex1911: Void kernel, base commits
​ ​ ​ ​ • flar2: old wake gestures, many other commits that shaped the kernel
​ ​ ​ ​ • frap129: Maple I/O scheduler (base for Marrow), Electron kernel, many other commits
​ ​ ​ ​ • Alek Dev: overclocking values for CPU and GPU, undervolting and overvolting values
​ ​ ​ ​ • nine7nine: EAS governors, EAS commits, optimized ext4 fsync, many other commits
​ ​ ​ ​ • gougous3: help with tuning Spectrum profiles, helix_schedutil tunables, ideas
​ ​ ​ ​ • Everyone else mentioned in Git history
Join our Telegram group here for betas
Enjoy!
Donate to support future development
XDA:DevDB Information
Velocity Kernel, Kernel for the Xiaomi Mi A1
Contributors
kdragon, tytydraco
Source Code: https://github.com/kdrag0n/velocity_tissot
Kernel Special Features:
Version Information
Status: Abandoned
Current Stable Version: r9
Stable Release Date: 2018-08-15
Created 2018-05-25
Last Updated 2019-01-23

Changelogs
r9 • August 15, 2018
​ ​ ​ ​ • Linux 3.18.118
​ ​ ​ ​ • CAF LA.UM.6.6.r1-09200-89xx.0
​ ​ ​ ​ • Updated Wi-Fi drivers
​ ​ ​ ​ • Compiled with Clang 8 revision 339049
​ ​ ​ ​ • Significant increases in security
​ ​ ​ ​ • Faster app opening
​ ​ ​ ​ • Smoother UI
​ ​ ​ ​ • Faster wakeup (power + fingerprint)
​ ​ ​ ​ • Lower latency
​ ​ ​ ​ • Balanced custom 500 Hz timer
​ ​ ​ ​ • Improved battery life
​ ​ ​ ​ • Optimized low memory killer
​ ​ ​ ​ • Disabled unnecessary CPU bug workarounds (overhead)
​ ​ ​ ​ • Disabled useless drivers
​ ​ ​ ​ • Fixed USB OTG (flash drivers, etc)
​ ​ ​ ​ • Optimized default settings
​ ​ ​ ​ • Improved reliability of default settings
​ ​ ​ ​ • Removed 307 MHz CPU underclock (detrimental to battery due to no undervolt)
​ ​ ​ ​ • Turned CPU overclock down to 2208 MHz for stability and battery
​ ​ ​ ​ • Turned GPU overclock down to 700 MHz for stability and battery
​ ​ ​ ​ • Enabled TCP ECN for slightly faster speeds on congested networks
​ ​ ​ ​ • Reduced chance of videos not playing
​ ​ ​ ​ • Added sdFAT driver for SD cards on some ROMs
​ ​ ​ ​ • Undervolted CPU by 150 mV
​ ​ ​ ​ • Added Kali NetHunter support (IPC, Bluetooth, Wi-Fi)
​ ​ ​ ​ • Improved audio jack quality
​ ​ ​ ​ • Added DTS-Eagle (DTS Headphone-X) support
​ ​ ​ ​ • Improved overall smoothness
​ ​ ​ ​ • Removed UKSM (additional overhead even when not in use)
​ ​ ​ ​ • Enabled fully multi-threaded IO
​ ​ ​ ​ • Improved boot speed
​ ​ ​ ​ • Removed hotplugs (this has been proven to actually be detrimental to battery, as well as performance)
​ ​ ​ ​ • Added ironactive and ondemandplus CPU governors
​ ​ ​ ​ • Fixed simple_ondemand GPU governor
​ ​ ​ ​ • Tuned Spectrum GPU settings
​ ​ ​ ​ • Fixed "There's an internal problem with your device" message on Treble ROMs
​ ​ ​ ​ • Fixed many more bugs
​ ​ ​ ​ • Removed non-functional Intellithermal
​ ​ ​ ​ • Fixed Bluetooth Low Energy + Wi-Fi co-existence on Pie
Click to expand...
Click to collapse
Older versions:
r8 • June 19, 2018
​ ​ ​ ​ • ​Linux 3.18.113
​ ​ ​ ​ • Updated Qualcomm code to latest CAF LA.UM.6.6.r1-08900-899xx.0
​ ​ ​ ​ • Enabled Large Receive Offload
​ ​ ​ ​ • Improved idle battery life
​ ​ ​ ​ • Fixed lazyplug
​ ​ ​ ​ • New hotplugging settings using msm_hotplug
​ ​ ​ ​ • Added fingerprint boost
​ ​ ​ ​ • Improved wakeup times
​ ​ ​ ​ • Improved CFQ and BFQ performance
​ ​ ​ ​ • Added dynamic schedtune input boost
​ ​ ​ ​ • Disabled unnecessary CPU bug workarounds (not applicable to Snapdragon 625)
​ ​ ​ ​ • Switched to AOSP clang 7.0.2
​ ​ ​ ​ • Reduced 3.5mm jack background noise
Click to expand...
Click to collapse
r7 • June 6, 2018
​ ​ ​ ​ • Updated to Linux 3.18.112
​ ​ ​ ​ • Disabled ZRAM (negative impact on 4 GB RAM devices)
​ ​ ​ ​ • Disabled wake gestures by default
​ ​ ​ ​ • Added CPU governors: elementalx, zzmoove, yankactive, relaxed, alucard, nightmare, chill
​ ​ ​ ​ • Increased default I/O performance
​ ​ ​ ​ • Removed custom marrow and microfreq governors
​ ​ ​ ​ • Fixed random reboots
​ ​ ​ ​ • Reverted to default 84% vibration strength
​ ​ ​ ​ • Improved performance on default profile
​ ​ ​ ​ • Enabled Adreno Idler
​ ​ ​ ​ • Improved idle battery life (fixed heavy drain)
​ ​ ​ ​ • Enabled idle IO scheduler switcher
​ ​ ​ ​ • Decreased entropy pool thresholds
​ ​ ​ ​ • Improved wakeup time
​ ​ ​ ​ • Fixed flashing on latest Resurrection Remix
​ ​ ​ ​ • Likely fixed video playback
​ ​ ​ ​ • Disabled compressed disk cache
Click to expand...
Click to collapse
r6 • May 29, 2018
​ ​ ​ ​ • Reverted to 100 Hz for maximum performance
​ ​ ​ ​ • Removed unused module support (0.2 MB smaller)
​ ​ ​ ​ • Microfreq GPU governor made more aggressive
​ ​ ​ ​ • Aggessively tuned helix_schedutil and autosmp on Balanced profile
​ ​ ​ ​ • Fixed almost all random reboots (hopefully)
​ ​ ​ ​ • Extra compiler optimizations
​ ​ ​ ​ • Switched back to clang as it seems to be smoother
​ ​ ​ ​ • Other Spectrum profiles tuned
​ ​ ​ ​ • Completely fixed Wi-Fi MAC address
Click to expand...
Click to collapse
r5 • May 28, 2018
​ ​ ​ ​ • Fixed all performance issues
​ ​ ​ ​ • Geekbench: 928 single-core, 4433 multi-core
​ ​ ​ ​ • Antutu: 81868
​ ​ ​ ​ • Fixed Spectrum profiles not setting on boot
​ ​ ​ ​ • Heavily tuned Spectrum profiles
​ ​ ​ ​ • Revamped Balanced profile to maximize performance and battery
Click to expand...
Click to collapse
r4 • May 27, 2018
​ ​ ​ ​ • Switched to GCC 8.1
​ ​ ​ ​ • Added sweep2sleep, sweep2wake, doubletap2wake gestures
​ ​ ​ ​ • Tweaked Spectrum profiles for much better performance and battery where applicable
​ ​ ​ ​ • Fixed broken Wi-Fi MAC address
​ ​ ​ ​ • Output version and build date when flashing
​ ​ ​ ​ • Fixed double tap to wake
Click to expand...
Click to collapse
r3 • May 26, 2018
​ ​ ​ ​ • Fixed data corruption when encrypted
​ ​ ​ ​ • Upstreamed to 3.18.110
​ ​ ​ ​ • Optimized memory page copying
​ ​ ​ ​ • Switched to Linaro GCC 7 compiler for fluidity
​ ​ ​ ​ • Added stock ROM support framework (disabled at the moment)
Click to expand...
Click to collapse
r2 • May 25, 2018
​ ​ ​ ​ • Enabled Integrity subsystem
Click to expand...
Click to collapse
r1 • May 24, 2018
​ ​ ​ ​ • Initial release
​ ​ ​ ​ • Linux 3.18.109
Click to expand...
Click to collapse

FAQ
Q: What ROMs are supported?
A: Treble GSIs and custom ROMs.
Q: What is the difference between all the EAS governors?
A: In terms of aggression, alucardsched > electroutil > (pwrutilx / schedutil) > darknessched. For more information, consult this post:
Freak07 said:
So this post will be dedicated to information about EAS in general.
Another amazing write up about alucardsched by a talented new dev @joshuous:
This is what I understand from tracing the Alucardsched code. I apologise if my understanding is incorrect.
Firstly, next frequency selection with Schedutil (very simple):
Code:
next_freq = 1.25 * Max_freq * current_util / max_util;
Now, here's a quick overview of one cycle of frequency selection in Alucardsched:
1. You have two key extra tunables: PUMP_INC_STEP and PUMP_DEC_STEP
2. Current utilisation here refers to the system's current demand. It is calculated using:
Code:
curr_util = (util * (100 + tunables->boost_perc)) / max_utilisation
The "util" is a value determined by the EAS scheduler.
3. Target load here refers to what processor is currently supplying. It is calculated using:
Code:
target_load = (current_freq * 100) / max_freq;
4. The key idea is to ensure that supply satisfies demand. That is, target load ≈ current load.
5. If target_load <= current_load (too little supply), then we want to increase frequencies to match the system’s load. For Alucardsched, frequency is increased by jumping up PUMP_INC_STEP number of steps in the OPP table. (By OPP table, I refer to the available frequencies that you can switch to)
6. If target_load > current_load (too much supply), then we want to decrease frequencies to match the system’s load. For Alucardsched, frequency is decreased by jumping down PUMP_DEC_STEP number of steps in the OPP table.
7. Do note that Alucardsched jumps several frequency steps, compared to Schedutil and Interactive which try to jump immediately to a calculated next frequency. In this way, Alucardsched doesn't care about the specific value of the next speed. It's like driving a car, and deciding to increase gears by several steps instead of deciding to jump immediately to a specific gear.
Extra Tunables
FREQ_RESPONSIVENESS
PUMP_INC_STEP_AT_MIN_FREQ
PUMP_DEC_STEP_AT_MIN_FREQ
Sometimes you want the "pumping" behaviour to behave differently at lower and higher frequencies. FREQ_RESPONSIVENESS can be seen as the mark that divides the low and high frequencies. If the current frequency is less than FREQ_RESPONSIVENESS, the number of frequency skips will be PUMP_INC_STEP_AT_MIN_FREQ and PUMP_DEC_STEP_AT_MIN_FREQ instead of the usual PUMP_INC_STEP and PUMP_DEC_STEP.
How is it used? If your frequency is low (lower than FREQ_RESPONSIVENESS) and your system demand is high, you ideally want to boost frequency speeds quickly. This is when PUMP_INC_STEP_AT_MIN_FREQ kicks in. PUMP_INC_STEP_AT_MIN_FREQ is usually (and should be) a larger value than PUMP_INC_STEP. When your frequency is high (higher than FREQ_RESPONSIVENESS) and your system demand is high, you don't want to be jumping so many steps up otherwise you will hit max frequencies too quickly (overkill). I'm pretty sure you can figure out how PUMP_DEC_STEP and PUMP_DEC_STEP_AT_MIN_FREQ works after having read this paragraph
Tldr;
Schedutil: simpler
Alucardsched: more tunable
Code:
IF CURRENT_FREQ < FREQ_RESPONSIVENESS:
PUMP_INC_STEP_AT_MIN_FREQ and PUMP_DEC_STEP_AT_MIN_FREQ are used
ELSE:
PUMP_INC_STEP and PUMP_DEC_STEP are used
PUMP_INC_STEP_AT_MIN_FREQ should be larger than PUMP_INC_STEP.
Note: There is however a potential problem (if you may call it one) with Alucardsched: just like Interactive you rely almost entirely on heuristics (trial and error) to control your frequency jumps instead of letting the system choose it for you, like in Schedutil. In that way, Alucardsched detracts from the goal of Schedutil to provide a simple frequency choosing mechanism. Without the proper tuning to meet your specific usage, it is likely that your frequencies will overshoot or undershoot past the needed load on Alucardsched (just like in Interactive). I would recommend that you play with the tunables to see what works best for you.
Here is information about energy-dcfc (Dynamic Capacity and Frequency Capping):
This new governor is based on schedutil. It uses target_load variables as thresholds to let the governor decide when to cap the frequencies for both clusters. These variables are called "load1_cap" and "load2_cap". Load1_cap corresponds to target_load1 meaning anything that is below target_load1, it caps using load1_cap. Anything above target_load1 and below target_load2, use load2_cap. Anything above target_load 2 and the maximum frequency will be used.
As a result of this behaviour, bit shift value must be set to 1. Anything higher than 1 and frequency scaling will be extremely slow. This is because the lower the maximum frequency, the lower the next frequency target is because the frequency range is being limited.
AS OF V009: The governor has now incorporated @Kyuubi10 's schedutil dynamic formula change. When load is below target_load1 it will use add bitshift in the formula. If load is above target_load1 but below target_load2, it won't use any bit shifting at all. If load is more than target_load2, it will subtract bitshift in the formula. This has proven to be very efficient with a touchboost-like behaviour when scrolling (Up to the capped frequency of this governor), then steady performance in between, and on heavy workloads it will not just stay on maximum frequency, in fact it will hover around 1.3-1.9GHz to ensure thermals are good as well as battery endurance.
This governor is aimed with maximum efficiency in mind. Do not expect outstanding performance with this governor.
helix_schedutil explained by @Kyuubi10
To understand Helix_schedutil you must first understand the original schedutil algorithm.
Here it is:
next_freq = maxfreq + (maxfreq >> bitshift) * util/maxcapacity
Explanation:
The most obvious difference of this algorithm is that it moves away from the idea of scaling frequencies up or down which were used in previous generations of governors.
Instead the aim of the above algorithm is to calculate the most appropriate frequency for the TOTAL CPU load.
NOTE: This is TOTAL load on CPU, not just load for the current frequency step as Interactive used to calculate with.
Now, for you numberphiles like myself that like understanding algorithms... Let's break it down:
"util/maxcapacity = Load."
The above creates a percentage value in decimal format (80% = 0.8) which represents the TOTAL load on CPU.
the algorithm now reads the following way:
next_freq = maxfreq + (maxfreq >> bitshift) * load
"maxfreq + (maxfreq >> bitshift)"
Essentially the aim of the above is to ensure that next_freq is always a little higher than the exact value needed to cover the load.
Bitshift: (paraphrasing @ZeroInfinity) in programming the ">>" mathematical function allows for shifting the binary values towards the direction of the arrows by "N" times.
In this case it is towards the right.
The relationship between "N" and the calculation in the "()" is as follows:
Bitshift = 1 = maxfreq/2
Bitshift = 2 = maxfreq/4
Bitshift = 3 = maxfreq/8
If the "+()" didn't exist in the algorithm, the chosen frequency would be exactly enough to cover the load.
If load is 0.6, aka 60%, all you need is a frequency = 60% of max frequency.
This would be bad since it doesn't leave any capacity/bandwidth leftover for inevitable bumps in load, nor space for EAS itself to run. Thus inevitably creating lags.
To keep a bit of free bandwidth you add "(maxfreq >> bitshift)".
Finally the problem I encountered, if bitshift = 2, then the result of the algorithm is that any load above 0.8 will result in a next_freq HIGHER than maxfreq. - This is your tipping point. As any load higher than 80% will wake up a new CPU.
Which means you have still about 20% of the CPU's max capacity being unused. Such a CPU is only 80% efficient.
Therefore by increasing bitshift to 3, the algorithm reads:
"maxfreq+(maxfreq/8)*load = next_freq"
This way you can use 89% of capacity before reaching max frequency of the CPU.
With bitshift=4 it reads:
"maxfreq+(maxfreq/16)*load = next_freq"
This allows you to use up to 94% total CPU load before reaching max frequency.
While this is great for improving efficiency at the higher frequencies, it doesn't leave enough bandwidth when calculating lower frequencies, and creates lag when load spikes at lower frequencies.
Update to the explanation:
After being inspired by the concept of @ZeroInfinity's new governor - Energy-DCFC, I decided to carry out a couple of tests on HTC 10 using variations of Helix_Schedutil.
The focus was stress-testing by increasing the current frequency load above 100%. (AKA Use up all of the bandwidth of the current frequency step.)
After the testing me and Zero worked on this new version of Helix_Schedutil.
The current behaviour of the governor is the following:
- Boost frequencies when load is below Target_Load1. (Boost can be increased by DECREASING bit_shift1 value.)
- Between Target_Loads there is no bit_shift at all. The governor just uses the following algorithm instead - (max_freq*util/max = next_freq)
- Loads higher than Target_Load2 will be THROTTLED. Bit_Shift2 here is subtracted rather than added. (Throttle effect can be increased by DECREASING bit_shift2 value.)
The result is that low freqs have spare bandwidth to avoid lags, middle frequencies leave no extra bandwidth at all, while higher frequencies are throttled to save battery.
Another focus of the governor update is to reduce overhead as much as possible. This results in a very responsive governor which isn't overly demanding on battery life.
Schedtune.boost values recommended for use with this governor:
Top_App: 5
Foreground: -50
Background: -50
Global: -50
Energy-DCFC is still recommended for those who prefer battery life over performance, but if you prefer greater performance then this governor can be used without making you feel guilty about wasting battery.
correction a misconception:
Some people describe tipping point as the load threshold which the governor uses to decide whether to ramp up or down.
While if you look into the behaviour of the governor it may appear that it behaves in such a way, it is technically incorrect.
As I mentioned previously this new algorithm moves away from the behaviour of legacy governor algorithms which focus on the current frequency load.
This governor does no ramping up or down.
It isn't even aware of the current frequency load, as it only knows the load relative to max capacity.
The misconception appears based on a property of the algorithm that results in a consistent load at any chosen frequency. This is a coincidental result of the algorithm, even though the algorithm is completely unaware of it.
Tipping point is in fact the load percentage at which the CPU reaches max frequency and any increase in load forces it to wake up a new core
here is some Information about pwrutil governor:
This new governor is based on schedutil.
A much simpler yet very effective governor based on schedutil. All this changes is the calculation to get the next frequency. Rather than using bit shift to calculate tipping point and what not, we don't use it at all. This is much much more efficient if you use my program called "schedutilCalculator" to calculate what the next frequency is. For example, a load of 25% with a max freq of 2150400 will get 500MHz as next frequency. A load of 50% will get 1GHz as next frequency. A load of 75% will get 1.5-1.6GHz as next frequency. A load of 100% will get 2.15GHz as next frequency. You can see the lower the load, the much lower the frequency selection will be, but the higher the load and the higher the frequency selection is. So it can go from a very low powered state with 50% load and under, to a high performance state from 75% load and above.
Includes a tunable called "utilboost" which is basically a load multiplier - it makes load higher than it is perceived by the governor, thus making next frequency selection higher. Remember utilisation does not equal load. The equation of calculating load is util / max capacity of a CPU (which should be 1024). So 512 / 1024 = 0.5 (50% load).
UTIL BOOST IS NOT MEANT TO BE USED WITH SCHEDTUNE.BOOST AT THE SAME TIME! EITHER USE ONE OR THE OTHER OR ELSE PERFORMANCE WILL BE OVERKILL AND BATTERY LIFE WILL DRAIN MUCH FASTER!!!
Util boost is supposed to be a replacement of schedtune.boost. schedtune.boost applies boosting to both clusters, whereas util boost allows boosting per-cluster so users can have much more control.
Click to expand...
Click to collapse

Cool ! New kernel, will test now. Thanks dev

Nice to see EAS for our device, performance should overtake battery I assume.

Awesome, good job op!

kdragon said:
Velocity Kernel • Mi A1
Introduction
Velocity Kernel was made to provide the best possible experience on all devices. We strive to provide the perfect balance of performance and battery life. Features are also plentiful, but features that nobody will use are outdated. We also completely debloat all our kernels and aim for small sizes relative to other kernels. Due to the small size and careful debloating, boot time is also improved.
Compatibility
At the moment only custom ROMs are supported. If there is enough demand, support for stock may be added.
Unofficial Project Treble devices are supported. Treble support is dynamically enabled if a Treble ROM is installed and your device has Treble. No special ZIP is necessary.
Click to expand...
Click to collapse
Where to flash in boot.img?

I'm one of the devs for this kernel.
Here's some things we'd like to hear back about from this kernel:
- Any random reboots / kernel panics?
- Does YouTube ever black out?
- Is your idle battery good?
- Do you get scroll lag?
- Does DT2W work properly?
These were all things we were experimenting with, so let us know if things are broken. Thanks and enjoy!

Ayush061 said:
Where to flash in boot.img?
Click to expand...
Click to collapse
It's a zip to flash in TWRP, not boot.img.

kdragon said:
It's a zip to flash in TWRP, not boot.img.
Click to expand...
Click to collapse
Okay got yah

After flashing the Kernel, data got corrupted with display unable to decrypt message. Even the correct password didn't work in recovery. Fortunately able to recover phone by flashing stock ROM.

Dasseem said:
Phone got corrupted, not accepting my password in recovery too.
Click to expand...
Click to collapse
That should never happen. Does booting TWRP from fastboot work? Does tAndroid not boot anymore?

Dasseem said:
Phone got corrupted, not accepting my password in recovery too.
Click to expand...
Click to collapse
me too, I had to delete my data

kdragon said:
That should never happen. Does booting TWRP from fastboot work? Does tAndroid not boot anymore?
Click to expand...
Click to collapse
Thankfully fastboot was working, flashed stock ROM.
Booting TWRP from fastboot didn't help since the it didn't accept my password. Had to flash stock.

Flashed this kernel on top of Mint, so far no issue. Watched YouTube for 20 minutes, taking photos, everything seems fine.

Any tried to flash this on AEX? without bootloop?
Sent from my [device_name] using XDA-Developers Legacy app

TatsuyaKaneki2015 said:
Any tried to flash this on AEX? without bootloop?
Click to expand...
Click to collapse
I'm using aex latest build. No bootloop.

TatsuyaKaneki2015 said:
Any tried to flash this on AEX? without bootloop?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was able to use it just fine on the latest AEX 5.5. Which kernel did you switch from?

kdragon said:
I was able to use it just fine on the latest AEX 5.5. Which kernel did you switch from?
Click to expand...
Click to collapse
Franco planning to flash it but little hesitant . I dont wanna get bootloop. But anyways it should work fine right im going to clean flash anyway installing latest AEX rom and installing this?
Sent from my [device_name] using XDA-Developers Legacy app

TatsuyaKaneki2015 said:
Franco planning to flash it but little hesitant . I dont wanna get bootloop. But anyways it should work fine right im going to clean flash anyway installing latest AEX rom and installing this?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, that should work fine.

INTRODUCTION​Canting is a kernel based on Google Common 3.18 merged over CAF-kernel.lnx.3.18.r34-rel. Built to provide security and stability improvement​
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
FEATURES​----------------------------------------------
• Only for Custom ROM 8.1.0 & 9.0.0
• Treble/Non-Treble Support
• Linux version 3.18.137
• CAF Tag LA.UM.7.6.r1-04300-89xx.0
• Build with CLANG 9.x optimized for arm64 compiled with build-tools-clang
• Kernel Hardening from Copperhead OS
• CPU Governors: interactive, conservative, ondemand, powersave, performance, userspace
• I/O Schedulers: noop, deadline, cfq, bfq
• Live Display Driver
• Compat vDSO from Pixel kernel
• Native DT2W support
• WireGuard VPN support (Current version: 0.0.20190227)
• KCAL colour control
• Sound Control
• Vibration Intensity Control
• Boeffla wakelock blocker
• sdFAT, exFAT and NTFS Support
• Better performance
• CRC & SHA256 crypto algorithms
• Blocked many wakelocks
• Removed safetynet flags (no need of magisk to bypass safteynet)
• Improved zRAM with lz4 compression
• Tweaked Westwood TCP Congestion set as default
• CPU Boost
• Adreno idler
• Spectrum Kernel Manager
• for more info check my commits
INSTALLATION INSTRUCTIONS​
Download latest kernel version
Boot to recovery
Flash Magisk (skip this if already installed)
Flash kernel.zip
reboot to system
DOWNLOAD LINK​GDrive​ - Github​
CREDITS​• nathanchance
• abhishek987
• fransiscofranco
• flex1911
• All of contributors from my git history ​
XDA:DevDB Information
Canting, Kernel for the Xiaomi Mi A1
Contributors
khusika
Source Code: https://github.com/khusika/canting_kernel_xiaomi_msm8953/
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2019-03-24
Created 2018-11-11
Last Updated 2019-03-23

Reserved

Reserved

name Canting is the tool to draw Batik ? ?

Can I direct update from project-k?

kickadnan said:
name Canting is the tool to draw Batik ? ?
Click to expand...
Click to collapse
Absolutely right
Awawa29 said:
Can I direct update from project-k?
Click to expand...
Click to collapse
Yes you can

i am getting bootloop using LR rom .... it is booting back to twrp ....

Hi, thanks for the new project,I use Project k r24 + Los 15.1, I use custom governor. Do you add gov in future??

Wow, new project. ?

Indo pride??

I know that is a different project, but what are the major differences between this and projectK?

hope to see kernel 4.9 soon... :laugh:
**sorry..just notice another post for 4.9 kernel

Jess182 said:
I know that is a different project, but what are the major differences between this and projectK?
Click to expand...
Click to collapse
1. Inline with Google Common & CAF
2. Ton of dummy commits was removed

Long life to canting!!!

ill try!! thanks for the hard work khusika!!

khusika said:
1. Inline with Google Common & CAF
2. Ton of dummy commits was removed
Click to expand...
Click to collapse
Alright thanks for info, could we say that is same base as projectK?

Jess182 said:
Alright thanks for info, could we say that is same base as projectK?
Click to expand...
Click to collapse
Differents, simply check the source codes.

It does not work well in sGSI port. Although this is descrypted, a "unsuccessful unencryption" screen appears

khusika said:
Differents, simply check the source codes.
Click to expand...
Click to collapse
Thanks for reply, last question...
I have searched OP for something about fast charge, but I have not seen anything, this new kernel also has high amperage after 90% ?, because although on projectK fast charge was disabled, after 90% the amperage was high and charged very fast.
(I was referring to that with the "same base", but I think the correct way is "same features?"

what about fast charging. still like projectk?
---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------
please made a telegram group for questions

Kintsugi
Kintsugi is the first custom kernel project I've worked on and I am proud to finally release it. Its name comes from the Japanese art of repairing broken pottery using powdered gold or silver, and I would say that it fitted the philosophy of my work. It wouldn't have come to life without my use of several developers' contributions. Finally, I aimed for a balance between performance and battery life in order to offer a stable user experience.
Features:
- Built with the latest Linaro prebuilt toolchain and compiled with -O2 and GCC Graphite optimizations
- Upstreamed to the latest linux-stable kernel version
- Updated the kernel source code to BTF6 from Samsung.
- Upstreamed CFQ I/O scheduler
- Disabled several Samsung security and debugging related configs
- All the CPU clusters' are undervolted (by -75mV) and have their minimum frequencies underclocked
(343Mhz for the little clusters and 520Mhz for the big clusters)
- Implented CPUfreq backports by celtare21 @KuranKaname)
- Increased the timer frequency to 300Hz for fewer jitters
- Enabled power-efficient workqueue mode by default for improved power consumption
- Disabled Kernel Samepage Merging by default for less CPU usage
- Implented different memory and filesystem related changes by @Sultanxda and @arter97
- Westwood is set as the default TCP Congestion algorithm
- Built-in SafetyNet patches by @Sultanxda are included (with @tbalden rootless approach)
- Built-in Boeffla Wakelock Blocker by @andip71 with pre-configured wakelock blocklist
@evdenis and @diepquynh)
- Built-in State Notifier driver by @neobuddy89
- exFAT and vFAT support
- Implented sdFAT mount options by cocafe
- Numerous other fixes, tweaks and under-the-hood optimizations
Installation:
The boot image can either be flashed via Odin or TWRP. I can add instructions if that would be necessary.
Download:
GSI
OneUI
Credits:
I thank the following persons for their respective contributions. If I forgot someone, their name is properly credited on GitHub.
@arter97
@cocafe
@evdenis
@farovitus
@Freak07
@ianmacd
@idkwhoiam322
@kdrag0n
@KuranKaname (celtare21)
@nathanchance
@neobuddy89
@nr7777
@osm0sis
@pascua28
@pkgnex
@Sultanxda
@tbalden
@tytydraco
@wrongway213
XDA:DevDB Information
Kintsugi, Kernel for the Samsung Galaxy A30
Contributors
BlackGunZ
Source Code: https://github.com/BlackGunZ/Kintsugi
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.1.6
Stable Release Date: 2020-09-06
Created 2020-08-01
Last Updated 2020-09-06

Really nice!

nice job!

Support Treble?

hacker812c said:
Support Treble?
Click to expand...
Click to collapse
The first users from Telegram reported that the kernel worked on HavocOS. You could give it a try.

New update is up!
Changelog:
- Increased the timer frequency to 300Hz for fewer jitters

Kintsugi #1.0.2
Second update of the day! Thanks to the contributors on Github.
Changelog:
- staging: samsung: argos: remove hmp boost
- mm: page-writeback: Subtract min_free_kbytes from dirtyable memory
- PM / Wakeup: Use rcu callbacks for better performance
- Revert "CHROMIUM: cpufreq: interactive: calculate load before freq change"
- include: asm-generic: do not hard code HZ to 100
- sched: use custom LOAD_FREQ for each HZ
- mm: Increase vmstat interval
- fbdev: decon: Disable logging

Kintsugi #1.0.3
New update! Thanks to the contributors on Github.
Changelog:
- Disable dm-verity and avb
- MTP bug fix for GSI ROMs

Kintsugi #1.0.4
New update! Thanks to the contributors on Github.
Changelog:
- Upstreamed to the 4.4.210 kernel version
- arm64: dts: Remove the reserved block of memory for CONFIG_TIMA (the driver was already disabled, so it makes sense)
- exynos-dm: Wrap exynos-ss debugging parts
- defconfig: Disable exynos-dm debugging for exynos-ss
- workqueue: Add system wide power_efficient workqueues
- Changes and updates to some other kernel parts (lib: sort and int_sqrt; rcu)

for setting the kernel, what must i can use the app name?

ican2703 said:
for setting the kernel, what must i can use the app name?
Click to expand...
Click to collapse
Use the app you prefer!

Can you make the kernel support permissive too? I tried to make it permissive with hktweaks but it won't work it only work in enforcing mode

Jake4lvas said:
Can you make the kernel support permissive too? I tried to make it permissive with hktweaks but it won't work it only work in enforcing mode
Click to expand...
Click to collapse
No, I kept the kernel's SElinux mode in enforcing state by default for security reasons.

Kintsugi #1.0.5
New update! Thanks to the contributors on Github, and to my testers (ilina-tatyana, RiccoS and Moneer).
Changelog:
- Upstreamed to the latest linux-stable kernel version (4.4.232)
- Fixed fast charge support for GSI ROMs
- boeffla_wl_blocker: Add more wakelocks (14860000.decon_f, umts_ipc0 and umts_ipc1) to the blacklist (thanks to ilina-tatyana for the logs)
- arm64: dts: Properly disable the reserved block of memory for CONFIG_TIMA
- Reverted "workqueue: Add system wide power_efficient workqueues"
- Reverted the changes and updates to some other kernel parts (lib: sort and int_sqrt; rcu)
- kernel: add a few patches for avoiding unnecessary skb reallocations - significantly improves ethernet<->wireless performance
- Other under-the-hood changes (that are available on Github).

Kintsugi #1.1.0
New update! Thanks to the contributors on Github and to my testers on Telegram.
Speaking of Telegram, I had to factory reset my phone and I lost most of my data. Reach out to me on XDA.
Changelog:
- Updated the kernel source code to BTE3 from Samsung.
- ZSWAP uses now ZSTD as its compression algorithm (instead of LZ4).
- Enabled Mass Storage USB file transfer mode for GSI ROMs.

Can it necessary to install Disable dm-verity and avb.

Tayyab Sohail said:
Can it necessary to install Disable dm-verity and avb.
Click to expand...
Click to collapse
Hello,
No, you don't have to. You can install the custom kernel without it.

What about a version for the A40? They even have the same SoC

Can you add instructions for how can the .img be flashed with Odin?

ponces said:
What about a version for the A40? They even have the same SoC
Click to expand...
Click to collapse
Indeed. I want to do make that in the future!
spicy_fox said:
Can you add instructions for how can the .img be flashed with Odin?
Click to expand...
Click to collapse
Have you found them or do you still need those instructions?

​
{
"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"
}
Afterlife Kernel for the Galaxy A70
Hey there choombas!
Afterlife kernel is designed to optimize your device, get some performance, save juice and be updated to latest version of the Linux Kernel. The aim is to give you a smooth experience and that you enjoy your device more!
Be warned I'm not responsible for bricked devices, dead SD cards, flash at your own risk.
​AfterlifeKernel v1 features:
- Based on latest Android R source A705FNXXU5DUC6
- Upstreamed to latest 4.14.233
- All TCP Congestion algorithms available (BBR set as default)
- Added Boeffla_Wakelock driver
- Added vDSO32
- Added latest Wireguard (1.0.20210424)
- Added Maple, ZEN, SIO and FIOPS I/O schedulers (cfq set as default)
- Added blu_schedutil governor
- Added sched tweaks for smoother experience
- Added spin lock function family
- Added some CPU optimizations
- Added some tweaks on GPU
- Added some tweaks to TCP
- Disabled avb 2.0 and DM-verity checks
- Enabled lz4 and updated decompressor module
- Patched some Safetynet flags
- Removed Samsung security features
- Removed VLA
- Built using Proton-clang 13 and -O3 optimizations
Drive:
https://drive.google.com/file/d/1ZK4MffVWjEiH0NcdiDVq3Y-E-0habB1L/view
Installation steps:
- Reboot to custom recovery (TWRP/OFOX/PBRP/SHRP)
- Flash the zip file & wipe cache
- (Optional) Flash magisk if you need root
- Reboot and enjoy choomba!
I would like to thank all these amazing people for their work, time and tips:
@Chatur27 - For taking the time to explain stuff to me, and for being a real pruh
@Panchajanya1999 - For letting me use some of his work from his Xiaomi Redmi Note 7 Pro kernel
@atndko - For helping me with some debugging
@osm0sis - For all his work, including AK3 and AIK
@kdrag0n - For all his work, including Proton Clang
@nathanchance - For all his work, including the telegram community and kernel upstreaming
@kirbyNx - For her support, and testing the kernel <3
@ all the choombas from the spanish A series group for the support, big thanks to @Gollo99 @Nico04
@ all the choombas from A70 Official and testers group
If I forgot someone let me know!
Source code: https://github.com/phennaux/AfterlifeKernel_sm6150_samsung
Telegram Channel: https://t.me/afterlife_kernel
Status: Stable

Reserved

Very good work!

Nice work bro!

Nice Work
Hats off to you

itz_rogue_77 said:
​View attachment 5316915
Afterlife Kernel for the Galaxy A70
Hey there choombas!
Afterlife kernel is designed to optimize your device, get some performance, save juice and be updated to latest version of the Linux Kernel. The aim is to give you a smooth experience and that you enjoy your device more!
Be warned I'm not responsible for bricked devices, dead SD cards, flash at your own risk.
View attachment 5316917​AfterlifeKernel v1 features:
- Based on latest Android R source A705FNXXU5DUC6
- Upstreamed to latest 4.14.233
- All TCP Congestion algorithms available (BBR set as default)
- Added Boeffla_Wakelock driver
- Added vDSO32
- Added latest Wireguard (1.0.20210424)
- Added Maple, ZEN, SIO and FIOPS I/O schedulers (cfq set as default)
- Added blu_schedutil governor
- Added sched tweaks for smoother experience
- Added spin lock function family
- Added some CPU optimizations
- Added some tweaks on GPU
- Added some tweaks to TCP
- Disabled avb 2.0 and DM-verity checks
- Enabled lz4 and updated decompressor module
- Patched some Safetynet flags
- Removed Samsung security features
- Removed VLA
- Built using Proton-clang 13 and -O3 optimizations
View attachment 5316929
Drive:
https://drive.google.com/file/d/1ZK4MffVWjEiH0NcdiDVq3Y-E-0habB1L/view
View attachment 5316949
Installation steps:
- Reboot to custom recovery (TWRP/OFOX/PBRP/SHRP)
- Flash the zip file & wipe cache
- (Optional) Flash magisk if you need root
- Reboot and enjoy choomba!
View attachment 5316921
I would like to thank all these amazing people for their work, time and tips:
@Chatur27 - For taking the time to explain stuff to me, and for being a real pruh
@Panchajanya1999 - For letting me use some of his work from his Xiaomi Redmi Note 7 Pro kernel
@atndko - For helping me with some debugging
@osm0sis - For all his work, including AK3 and AIK
@kdrag0n - For all his work, including Proton Clang
@nathanchance - For all his work, including the telegram community and kernel upstreaming
@kirbyNx - For her support, and testing the kernel <3
@ all the choombas from the spanish A series group for the support, big thanks to @Gollo99 @Nico04
@ all the choombas from A70 Official and testers group
If I forgot someone let me know!
Source code: https://github.com/phennaux/AfterlifeKernel_sm6150_samsung
Telegram Channel: https://t.me/afterlife_kernel
Status: Stable
Click to expand...
Click to collapse
nice job bro

Would this custom kernel only work for Android 11? i have CAOS GSI 11 with one UI 2.0 vendor. Thank you!

william3378801 said:
Would this custom kernel only work for Android 11? i have CAOS GSI 11 with one UI 2.0 vendor. Thank you!
Click to expand...
Click to collapse
I've tested my kernel on Haky's latest LOS 17.1 under the OneUI 2.5 (CTK4) vendor and it works fine, so it should work with OneUI 2.0 vendor I think not sure.

this will work on A705FNXXU5DUE2?

oli231 said:
this will work on A705FNXXU5DUE2?
Click to expand...
Click to collapse
yes

kirbyNx said:
yes
Click to expand...
Click to collapse
thank you i,m ready to install kernel afterlife from cyberpunk

Is there a version for the A705MN model by any chance? My phone was in bootloop after flashing the kernel. And I have the MN variant of the phone. Thank you!

william3378801 said:
Is there a version for the A705MN model by any chance? My phone was in bootloop after flashing the kernel. And I have the MN variant of the phone. Thank you!
Click to expand...
Click to collapse
Idk, my device is also A705MN and it works fine.

Is the kernel compatible with one UI 2.0 firmware tho? I have one UI 2.0 firmware with CAOS 11 gsi . Thanks!

itz_rogue_77 said:
​View attachment 5316915
Afterlife Kernel for the Galaxy A70
Hey there choombas!
Afterlife kernel is designed to optimize your device, get some performance, save juice and be updated to latest version of the Linux Kernel. The aim is to give you a smooth experience and that you enjoy your device more!
Be warned I'm not responsible for bricked devices, dead SD cards, flash at your own risk.
View attachment 5316917​AfterlifeKernel v1 features:
- Based on latest Android R source A705FNXXU5DUC6
- Upstreamed to latest 4.14.233
- All TCP Congestion algorithms available (BBR set as default)
- Added Boeffla_Wakelock driver
- Added vDSO32
- Added latest Wireguard (1.0.20210424)
- Added Maple, ZEN, SIO and FIOPS I/O schedulers (cfq set as default)
- Added blu_schedutil governor
- Added sched tweaks for smoother experience
- Added spin lock function family
- Added some CPU optimizations
- Added some tweaks on GPU
- Added some tweaks to TCP
- Disabled avb 2.0 and DM-verity checks
- Enabled lz4 and updated decompressor module
- Patched some Safetynet flags
- Removed Samsung security features
- Removed VLA
- Built using Proton-clang 13 and -O3 optimizations
View attachment 5316929
Drive:
https://drive.google.com/file/d/1ZK4MffVWjEiH0NcdiDVq3Y-E-0habB1L/view
View attachment 5316949
Installation steps:
- Reboot to custom recovery (TWRP/OFOX/PBRP/SHRP)
- Flash the zip file & wipe cache
- (Optional) Flash magisk if you need root
- Reboot and enjoy choomba!
View attachment 5316921
I would like to thank all these amazing people for their work, time and tips:
@Chatur27 - For taking the time to explain stuff to me, and for being a real pruh
@Panchajanya1999 - For letting me use some of his work from his Xiaomi Redmi Note 7 Pro kernel
@atndko - For helping me with some debugging
@osm0sis - For all his work, including AK3 and AIK
@kdrag0n - For all his work, including Proton Clang
@nathanchance - For all his work, including the telegram community and kernel upstreaming
@kirbyNx - For her support, and testing the kernel <3
@ all the choombas from the spanish A series group for the support, big thanks to @Gollo99 @Nico04
@ all the choombas from A70 Official and testers group
If I forgot someone let me know!
Source code: https://github.com/phennaux/AfterlifeKernel_sm6150_samsung
Telegram Channel: https://t.me/afterlife_kernel
Status: Stable
Click to expand...
Click to collapse
nice work choomba give this man a beer or something for his work

you ca
william3378801 said:
Is the kernel compatible with one UI 2.0 firmware tho? I have one UI 2.0 firmware with CAOS 11 gsi . Thanks!ytest it but it is built for one ui 3.1 just do a backup first
Click to expand...
Click to collapse
william3378801 said:
Is the kernel compatible with one UI 2.0 firmware tho? I have one UI 2.0 firmware with CAOS 11 gsi . Thanks!
Click to expand...
Click to collapse
well it is built for one ui 3.1 ! test it but do a backup first

william3378801 said:
Is there a version for the A705MN model by any chance? My phone was in bootloop after flashing the kernel. And I have the MN variant of the phone. are you running one ui and which version or los ?
Click to expand...
Click to collapse

william3378801 said:
Is the kernel compatible with one UI 2.0 firmware tho? I have one UI 2.0 firmware with CAOS 11 gsi . Thanks!
Click to expand...
Click to collapse
It should work, I can't confirm yet for GSIs but all phh based ones should work.

william3378801 said:
Is there a version for the A705MN model by any chance? My phone was in bootloop after flashing the kernel. And I have the MN variant of the phone. Thank you!
Click to expand...
Click to collapse
Hmm weird, I've had a couple of A705MN testers, it worked fine for them. Could you elaborate please on what ROM are you and what you've done? Thanks

oli231 said:
this will work on A705FNXXU5DUE2?
Click to expand...
Click to collapse
Yup it will work, it's been tested and it works fine on latest DUE2 firmware

{
"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"
}
VoltageOS 12.1 for Redmi 7/Y3​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
Github: https://github.com/VoltageOS
Website: https://voltage-os.sourceforge.io
Telegram: Group
Donate: UPI: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Encryption
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Installation Guide
Clean flash recommended
Always make a nandroid backup, be safe.
ROM uses lineage based kernel
NikGapps Basic recommended for better experience.
NOTE: DFE.zip is not needed anymore as encryption is removed temporarily till the recovery gets fixed.
- Clean flash recommended
- Use the latest official orange fox recovery.
- Format Data type Yes
- Reboot to recovery
- Wipe
* Dalvik / ART Cache
* Cache
* System
* Vendor
* Data
- Flash VoltageOS+Gapps
- Format Data type yes
- Reboot
ROM Source: https://github.com/VoltageOS
Device Source: Github
Kernel Source: Github
Special thanks to testers especially @officialtechrom & @insect_cs
If you liked my work don't forget to give thanks, hit like, buy me a coffee UPI: [email protected]
ROM OS Version: Android 12.1
ROM Kernel: Linux 4.9.x
Based On: AOSP
Release Type: Stable

Awesome, first Android 12 ROM

aravindCV said:
Awesome, first Android 12 ROM
Click to expand...
Click to collapse
Thanks BRO

Changelogs 1.8-EOL
Build Date : 12/09/2022
- Update dirac blobs
- Update GPS config from stock
- Updated build fingerprint
- Overlay: Allowed all apps to use smart replies
- Overlay: added support for smart pixels
- Audio: extend buffer size to 256kb for offload playback
- Set cutoff voltage to 3400
- Set speaker and microphone volume to 90
- Added Battery statistics overlay
- Fixed sepolicy denial for radio.te
- Kernel Changes
-Increase silver cluster boost freq to 1800 MHz
-Configure max-boost frequencies for cpu_input_boost
-Introduce Simple Low Memory Killer for 2GB RAM devices means better RAM Management
-Increase Max Charging speed to 2500MAH
Changelogs 1.7
Build Date : 11/07/2022
- Switched Pixel Power HALS and thermals.
- Added thermals profiles in device settings.
- Set audio to fluence to fix voice recorder & mic buzz.
- Fixed screen record lag.
- Improved sinsperf.
- Introduced Libperfmgr improves performance and reduces lag.
Changelogs 1.6
Build Date : 18/06/2022
- June Security Patch
- June Build Fingerprint
- Import some permissions from stock
- Add few performance props
- Overlay : Show display color modes
Changelogs 1.5​- May Security Patch
- May Build Fingerprint
- Dropped Xiaomi Parts
- Introduced DeviceSettings
- Fix Lockscreen Wakeup Delay
- Enable Performance Profiles
- Enable ViLTE overlay
- Speed dexpreopt Pixel Launcher
- Explicitly Enable IORap & OFR
- Enable Seamless Transfer Support
- Set Max WFD Resolution to 1080p
- Disable Wallpaper Zooming
- Enable Stereo Channel Support for Voip over audio path
- Enable 24-bit audio for Wired Headphones and Headsets
Changelogs 1.4​- Merged February Security Patch
- Build based on r29
- Switched Raven(Pixel 6 Pro) February Fingerprint
- Switch to AOSP WFD or Screencast
- Adapt to Android Go Guidelines for 2GB RAM Devices
- Disable UI Touch sounds by default
- Fixed Battery Drain Issue
- Ship with Pulse Music player by default
- Added Ambient Display missing string
- Fixed sepolicy denials
Changelogs 1.3​
Merged January Security Patch
Add More Battery Saving Props.
[Temp] Disable Encryption for now.
Switch to Vulkan UI Renderer.
WiFi: Disable Packet Logging.
Add Nodes to Hide Magisk in Banking apps.
Import Hotword Enrollment from Oneplus 8 Pro.
Show 4G icon for all carriers.
Allow display to be rotated in all 4 directions.
Audio: Enable 24-bit audio for primary output.
Improve Scrolling Responsiveness.
Enable AlwaysOnDisplay(AOD).
Enable Adaptive Sleep.
Dropped Board Uses Adreno to true.
CHANGELOGS 1.2
Fixed Boot Animation Resolution
Update Maintainer Name
Fix Screen Record Lag
Set Board Uses Adreno to True
Enable Call Recording
Enable WiFi Battery Saving
Fix Recovery Stuck Issue
Make UI Smoother
Update SOC Name
Enable MIUI Notch Overlay
Update Device Name
Switched to Redfin December Build Fingerprint
CHANGELOGS 1.1
-Initial Official Build
-Safetynet Passed
-November Security Patch
-Add Pixel.xml 2016 for unlimited GPhotos Storage
-Raven November Build Fingerprint.

adi123.pratap said:
VoltageOS 12.0 for Redmi 7/Y3​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
Github: https://github.com/VoltageOS
Website: https://voltage-os.sourceforge.io
Telegram: Group
Donate: UPI: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Encryption
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Installation Guide
Clean flash recommended
Always make a nandroid backup, be safe.
ROM uses lineage based kernel
NikGapps Basic recommended for better experience.
- Clean flash recommended
- Use the latest official orange fox recovery.
- Format Data type Yes
- Reboot to recovery
- Wipe
* Dalvik / ART Cache
* Cache
* System
* Vendor
* Data
- Flash VoltageOS+Gapps+DFE.zip
- Format Data type yes
- Reboot
ROM Source: https://github.com/VoltageOS
Device Source: Github
Kernel Source: Github
Special thanks to testers especially @officialtechrom & @insect_cs
If you liked my work don't forget to give thanks, hit like, buy me a coffee UPI: [email protected]
ROM OS Version: Android 12
ROM Kernel: Linux 4.9.x
Based On: AOSP
Release Type: Stable
Click to expand...
Click to collapse
Thanks buddy for android version 12.0 rom we really appreciate your hard work

adi123.pratap said:
VoltageOS 12.0 for Redmi 7/Y3​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
Github: https://github.com/VoltageOS
Website: https://voltage-os.sourceforge.io
Telegram: Group
Donate: UPI: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Encryption
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Installation Guide
Clean flash recommended
Always make a nandroid backup, be safe.
ROM uses lineage based kernel
NikGapps Basic recommended for better experience.
- Clean flash recommended
- Use the latest official orange fox recovery.
- Format Data type Yes
- Reboot to recovery
- Wipe
* Dalvik / ART Cache
* Cache
* System
* Vendor
* Data
- Flash VoltageOS+Gapps+DFE.zip
- Format Data type yes
- Reboot
ROM Source: https://github.com/VoltageOS
Device Source: Github
Kernel Source: Github
Special thanks to testers especially @officialtechrom & @insect_cs
If you liked my work don't forget to give thanks, hit like, buy me a coffee UPI: [email protected]
ROM OS Version: Android 12
ROM Kernel: Linux 4.9.x
Based On: AOSP
Re
Click to expand...
Click to collapse
adi123.pratap said:
VoltageOS 12.0 for Redmi 7/Y3​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
Github: https://github.com/VoltageOS
Website: https://voltage-os.sourceforge.io
Telegram: Group
Donate: UPI: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Encryption
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Installation Guide
Clean flash recommended
Always make a nandroid backup, be safe.
ROM uses lineage based kernel
NikGapps Basic recommended for better experience.
- Clean flash recommended
- Use the latest official orange fox recovery.
- Format Data type Yes
- Reboot to recovery
- Wipe
* Dalvik / ART Cache
* Cache
* System
* Vendor
* Data
- Flash VoltageOS+Gapps+DFE.zip
- Format Data type yes
- Reboot
ROM Source: https://github.com/VoltageOS
Device Source: Github
Kernel Source: Github
Special thanks to testers especially @officialtechrom & @insect_cs
If you liked my work don't forget to give thanks, hit like, buy me a coffee UPI: [email protected]
ROM OS Version: Android 12
ROM Kernel: Linux 4.9.x
Based On: AOSP
Release Type: Stable
Click to expand...
Click to collapse
Bro can you help us with kali nethunter kerel for redmi note 7 onclight ?

adi123.pratap said:
VoltageOS 12.0 for Redmi 7/Y3​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
Github: https://github.com/VoltageOS
Website: https://voltage-os.sourceforge.io
Telegram: Group
Donate: UPI: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Encryption
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Installation Guide
Clean flash recommended
Always make a nandroid backup, be safe.
ROM uses lineage based kernel
NikGapps Basic recommended for better experience.
- Clean flash recommended
- Use the latest official orange fox recovery.
- Format Data type Yes
- Reboot to recovery
- Wipe
* Dalvik / ART Cache
* Cache
* System
* Vendor
* Data
- Flash VoltageOS+Gapps+DFE.zip
- Format Data type yes
- Reboot
ROM Source: https://github.com/VoltageOS
Device Source: Github
Kernel Source: Github
Special thanks to testers especially @officialtechrom & @insect_cs
If you liked my work don't forget to give thanks, hit like, buy me a coffee UPI: [email protected]
ROM OS Version: Android 12
ROM Kernel: Linux 4.9.x
Based On: AOSP
Release Type: Stable
Click to expand...
Click to collapse
Bro why your ROM say workings SD card corrupted and its need to be formated ?

I have tried this rom, there is a wasteful battery bug when using a data connection, and it's also blank without a display charging when it's turned off, can fix that bug, tanks before, the rom smooth, i like your job sir

Rashik lama said:
Bro why your ROM say workings SD card corrupted and its need to be formated ?
Click to expand...
Click to collapse
Format once to fix the issue

draycomputer said:
I have tried this rom, there is a wasteful battery bug when using a data connection, and it's also blank without a display charging when it's turned off, can fix that bug, tanks before, the rom smooth, i like your job sir
Click to expand...
Click to collapse
Please explain properly i couldn't get it?

Rashik lama said:
Thanks buddy for android version 12.0 rom we really appreciate your hard work
Click to expand...
Click to collapse
Thanks sir

adi123.pratap said:
Please explain properly i couldn't get it?
Click to expand...
Click to collapse
simply:
1, the battery is wasteful if used data connection
2 ,no display of the battery charging when the device is in a state of power off (Just dark blank ni indicator charging)

draycomputer said:
simply:
1, the battery is wasteful if used data connection
2 ,no display of the battery charging when the device is in a state of power off (Just dark blank ni indicator charging)
Click to expand...
Click to collapse
u mean charging animation that's not a bug well it's not added right now from the source side

adi123.pratap said:
VoltageOS 12.0 for Redmi 7/Y3​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
Github: https://github.com/VoltageOS
Website: https://voltage-os.sourceforge.io
Telegram: Group
Donate: UPI: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Encryption
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Installation Guide
Clean flash recommended
Always make a nandroid backup, be safe.
ROM uses lineage based kernel
NikGapps Basic recommended for better experience.
- Clean flash recommended
- Use the latest official orange fox recovery.
- Format Data type Yes
- Reboot to recovery
- Wipe
* Dalvik / ART Cache
* Cache
* System
* Vendor
* Data
- Flash VoltageOS+Gapps+DFE.zip
- Format Data type yes
- Reboot
ROM Source: https://github.com/VoltageOS
Device Source: Github
Kernel Source: Github
Special thanks to testers especially @officialtechrom & @insect_cs
If you liked my work don't forget to give thanks, hit like, buy me a coffee UPI: [email protected]
ROM OS Version: Android 12
ROM Kernel: Linux 4.9.x
Based On: AOSP
Release Type: Stable
Click to expand...
Click to collapse
Thanks developers for such smooth and stable rom.
Now we can safely avoid upgrading smartphone until developer community with us.

Anonmityslayer said:
Thanks developers for such smooth and stable rom.
Now we can safely avoid upgrading smartphone until developer community with us.
Click to expand...
Click to collapse
Thank

Is it available on this ROM to download App's at External SD card?

dody1000 said:
Is it available on this ROM to download App's at External SD card?
Click to expand...
Click to collapse
TRY and report me sir

where could I find DFE.zip for redmi 7

kareemmohamed1223 said:
where could I find DFE.zip for r
Click to expand...
Click to collapse
kareemmohamed1223 said:
In redmi 7 official telegram group join there
Click to expand...
Click to collapse

Good work, please add an option to turn off the battery light, when the battery is low or while charging