Related
[Closing message]
Hi,
I am discontinuing the work on the Android Permission Spoofing Framework as I am not using Android anymore.
If anybody is interested in taking over the development I would be very happy to help her or him getting started as much as possible.
Feel free to contact me if you would like to work on it.
Sorry and have fun - Guhl
[End closing message]
This ROM is based on AOSP KitKat 4.4.2_r1. Besides the deep integration of the permission spoofing functionality the ROM is completely stock - it's not even rooted!
In addition to the original AOSP rom it includes the permission spoofing framework enhancement that was originally developed by Plamen K. Kosseff for Android 2.3. The functionality has been rebased to Android 4.4 and enhanced (a lot) by me and is now available.
My work was/is originally done for the HTC vision (G2/DZ) for which i provide ROMs based on ASOP and CM10.1 (see posting in the vision forum) but since i do also own a N4 i will provide ROMs for it also. There is also a CM version for the Nexus 4 here.
If you as a developer want to add the permission spoofing framework to your ROM please go ahead it should be portable easily. I will keep the commit list updated. If you need help don't hesitate to ask!
Actually the main motivation to publish this is to inspire other developers to integrate this with their work.
The source of the enhancement can be found on github in the repositories:
platform_frameworks_base
platform_frameworks_opt_telephony
platform_packages_apps_settings
The current work is done in the 4.4.2_r1 branch and the relevant commits are:
framework initial commit
framework bug fix 1
framework bug fix 2
frameworks telephony initial commit
app settings initial commit
framework permission spoofing - location
framework pff: infrastructure code cleanup
framework pff: permission spoofing - contacts and phone log
framework pff: permission spoofing - calendar (Instances)
framework pff: permission spoofing - calendar (Instances - cleanup)
framework pff: permission revoking - initial commit
framework pff: add PFFInfoDatabase to make spoofed informations persistant and changeable
framework pff: bug fix for permission revoking
What is permission spoofing
Permission spoofing means that the framework will return spoofed information to Apps instead of the original information based on permissions that the App requested during installation. The main motivation for the development of this functionality is the protection of the privacy of the phones owner.
Examples for spoofed information are:
Empty contact list instead of real contacts - READ_CONTACTS
False location instead of real location - ACCESS_COARSE_LOCATION / ACCESS_FINE_LOCATION
False Information for phone id and phone number - READ_PHONE_STATE
Empty log instead of real phone call log - READ_CALL_LOG
Empty calendar list instead of real calendar entries - READ_CALENDAR
....
Current implementation
Currently the following permissions are available:
READ_PHONE_STATE
While this permission allows the App to read the state of the phone (in call, ...) it also allows the App to read information like the phone number or the IMEI of the phone. Instead of revoking the permission that has to be granted to an App, permission spoofing provides spoofed information for this sensitive data.
ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION
Instead of the real location a location that can be set using the PFF-GPSPath will be reporte (the default spoofed location is the top of Mt. Everest). The implementation is not perfect yet (Google maps and Latitude still seem to know the coarse location - working on that)
READ_CONTACTS and READ_CALL_LOG
Instead of the contacts and the call log an empty list will be reported. The implementation sets the limit parameter of the query to 0 if the permission is spoofed.
READ_CALENDAR
The implementation changes the date for which the items will returned to the first week of 1970.
More permissions might be added in the future.
Usage
Spoofing can be enabled on a per App basis. To enable spoofing go to Settings - Apps, choose the App for which you want to spoof the permission. Below the spoofable permission will be a switch that can be set to On to enable spoofing or Off to disable spoofing for this App.
Optional Apps
The source of these apps is also available at https://github.com/guhl
PFF-GPSPath
The PFF-GPSPath App can be used to set the spoofed location and in addition it can also be used to define a path the can then be simulated in the App (by effectively moveing the spoofed location)!
HowTo for PFF-GPSPath HowTo
PFF-Settings
The PFF-Settings app provides the same functionality as App - Settings but in a more comprehensive way.
It provides a list of all Apps (including system Apps) that have a spoofable permission and allows you to set spoofing On/Off for them
PFF-Test
If you spoof a spoofable permission for the app PFF-Test you can check the info that the framework provides to PFF-Test
Downloads
ROM aosp_mako-ota-eng.4.4.2.pff.20131216.zip
Gapps are not included in the rom - they can be found at pa_gapps-stock-4.4.2-20131215-signed.zip
PFF-GPSPath_1_3.apk
PFF-AppSettings_1_1.apk
PFF-Test
Communication
I do not want to start a flame war on spoofing on XDA. Whiile spoofing is important for me I do understand people opposing it.
If you want to talk to me, the best way to do this is to look for me (Guhl) at #nexus4, #G2ROOT or #andromadus on freenode IRC.
Changelog
2013-12-16
Rebased from AOSP 4.3 to 4.4.2
Credits
Plamen K. Kosseff for the original framework changes
Flinny for his huge work on the Andromadus roms and supporting me with my original development for the vision
pierre_ja, Nipqer, Hymie and all the others at #G2ROOT for their endless help and entertainment
XDA:DevDB Information
Permission spoofing framwork - Nexus 4 - AOSP 4.4, ROM for the Google Nexus 4
Contributors
guhl99
ROM OS Version: 4.4.x KitKat
Based On: AOSP
Version Information
Status: Stable
Created 2013-12-16
Last Updated 2014-07-06
PFF-GPSPath Version 1.3
Hi,
In my constant struggle to remove everything that involves the use of the closed source Google Play-Services from my devices I rewrote the PFF-GPSPath App.
Version 1.3:
- Switched to OpenStreetMap data using the MapQuest Android API
- Completely removed dependencies on Google play-services
Known-Issues:
- Draging Markers is not implemented yet
There is no functional improvement between version 1.2 and version 1.3 but it is all free!
Have fun - Guhl
*******
{
"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"
}
Energized Protection - Magisk
Version: Ă©clairs | Updated: Oct 13, 2019 | Status: Stable
ad.porn.malware blocking.
This repository consolidates several reputable filters, and merges them into couple of protection packs with duplicates and dead/inactive domains removed. A variety of tailored packs are provided.
Cloud Codenvy | License CC BY-NC-SA 4.0
Website | Energized Repo | Check Energized | Telegram
A Trio Project with ❤︎ from Bangladesh, India & Zanzibar.​
M A I N T H R E A D
XDA Thread - Get to know more about Energized!
F E A T U R E S
Ďź hosts based: based on Hosts file, all the bad stuffs blocked with 0.0.0.0
Ďź any device: compatible with all devices, regardless of OS.
Ďź blockings: strictly blocks advertisements, malwares, spams, statistics & trackers on both web browsing and applications.
Ďź multiple formats: different variants for different devices.
Ďź speed you need: reduces page loading time upto half of its actual time!
Ďź privacy: with all these annoyances blocking, it also increases privacy.
Ďź saves expense: greatly decreases data consumption saving expense.
Ďź clean: no extra abracadabra!
W H A T I S T H I S F O R ?
This Energized System is designed for Unix-like systems, gets a list of domains that serve ads, tracking scripts and malware from multiple reputable sources and creates a hosts file that prevents your system from connecting to them.
I know, there are couple of great sources to use, but this project is one of my hobby projects, and I'm still learning how to do these things properly. There will be mistakes and bugs, hope to fix them with all of your help! So, let's make an annoyance free better open internet, altogether!
I N S T R U C T I O N S
• GUIDE: 2ND POST for usage instructions.
D O W N L O A D
• DOWNLOADoad: Energized Protection > Magisk Manager - Single Module to get the job done!
• CHANGELOG: READ HERE - All the changes of Energized Protection Module.
P A C K A G E D E T A I L S
• DETAILS: Check our GITHUB README for better viewing experience.
S U B M I T I S S U E
Got any issue? or any query? Need to report broken app/site issue? Found a legit site blocked? or any annoyance that bothering you, and you want to block?
• ENERGIZED BOX: Intorducing Energized Web App - ENERGIZED BOX- More Info.
L I C E N S E
CC BY-NC-SA 4.0
D I S C L A I M E R
Energized Hosts are basically hosts files to block access to domains. If you don't know how it works, then please try this at your own risk. I won't be responsible for any damage or loss. Never forget to make backups.
T H A N K S
For their great scripts.
Code:
♡ LarappsOfDongle - RP's Script
♡ QwertySDuos2 - Base Script
♡ topjohnwu - Magisk
♡ Zackptg5 - UHA Script
Let's make an annoyance free better open internet, altogether!
A project by Ador with ♡ from Bangladesh.
Say Thanks!​
XDA:DevDB Information
Energized ⚡ Protection, Tool/Utility for all devices (see above for details)
Contributors
AdroitAdorKhan, badmojr
Source Code: https://github.com/Magisk-Modules-Repo/Energized-Protection
Version Information
Status: Stable
Current Stable Version: Ă©clairs
Stable Release Date: 2019-10-13
Created 2018-06-20
Last Updated 2019-10-13
Instructions
Requirements:
- Install the Busybox For Android NDK Busybox Module from Magisk Manager.
- Install any Terminal App from Google Play Store. Recommended Termux
Run:
- First Enable Systemless Hosts in Magisk Manager; or the script won't run.
- Open terminal then type:
Code:
su
energized
- Then follow the prompts to install host file of choice
Whitelist Instructions:
- Find text file on sdcard called whitelist in sdcard/EnergizedProtection/
- Add the domain with redirecting IP, domain name or regex to whitelist the exact domain.
Code:
Example -
redirecting IP - 0.0.0.0 abcd.com
domain name - abcd.com
regex - .*abcd.*
- Run hosts script and choose whitelist w option.
Instant Whitelist:
- To instantly whitelist a domain, select iw and then type your domain.
- Type Y and press enter.
Blacklist Instructions:
- Find text file on sdcard called blacklist in sdcard/EnergizedProtection/
- Add exact lines you want to remove it (do not include the 0.0.0.0 -> so for example: abcd.com)
- Run hosts script and choose blacklist b option.
Instant Blacklist:
- To instantly blacklist a domain, select ib and then type your domain.
- Type Y and press enter.
Remove Whitelist/Blacklist:
- Just run hosts script and reinstall host file of choice without selecting whitelist/blacklist.
More Instructions - GIT INSTRUCTIONS
*If you find any issue while using this, feel free to report the issue here, on Telegram or in Github!
Whenever you are facing issue, help us with the log.​NON-ROOT -
- Download this DNSfilter Energized Fork App.
- Install and Apply the filter.
- Open the app you are having issues, and re-check the dns log in DNSfilter app.
- RED Marked ones are Blocked and GREEN Marked ones are open.
- Now send us the Screenshot or log.
ROOT -
- Download AdAway App.
- Remove any applied hosts and reboot.
- Install AdAway and open the app.
- Go to Options > Log DNS Requests and toggle TCP DUMP on.
- Now go back to your app, open and run the app till you get your issue fixed.
- Open Adaway > Log DNS Requests > Open Log File.
- Now send us the Screenshot or log.
WINDOWS -
- Download DNS Query Sniffer Software.
- Install and follow the detailed instructions here.
First of all, heartfelt gratitude towards all the amazing human beings who have been loving our work and supporting us since the very beginning. We are really glad to have you by our side.
But maintaining a quality blocking project takes a lot of time. Energized Protection is completely independently funded. We fight for our users. This does mean however that we also have to spend our owns to pay the bills. This is where you can help: by chipping in you can ensure more time is spent improving Energized rather than dealing with distractions.
Support Us -
PayPal - [email protected]
Will this work with adaway if it is used to block some specific sites (Spotify ads).
Also, how to uninstall?
Sent from my LEX727 using XDA Labs
Redhawk2000 said:
Will this work with adaway if it is used to block some specific sites (Spotify ads).
Also, how to uninstall?
Click to expand...
Click to collapse
Yea. It can be used with Adaway. As Spotify's Video Ads sources are generated dynamically like the Google Video! So it will be impossible with hosts to block all of'em!
Else, it removes all other ads.
To uninstall Magisk Module, just remove the module from Magisk Manager and reboot!
Do u need systemless hosts enabled in magisk settings for this?
yung40oz84 said:
Do u need systemless hosts enabled in magisk settings for this?
Click to expand...
Click to collapse
well, for All-In-One Module yes!
but, for standalone packs, no! (As it just simply replaces system/etc/hosts via Standalone Module!)
Stay Energized!
Hi! Just dropping in to say that the opening post is absolutely beautiful! Well-designed, clear, detailed and pleasing to the eyes. Good work!
shadowstep said:
Hi! Just dropping in to say that the opening post is absolutely beautiful! Well-designed, clear, detailed and pleasing to the eyes. Good work!
Click to expand...
Click to collapse
Wow! That's so kind of you bhai!
AdroitAdorKhan said:
Yea. It can be used with Adaway. As Spotify's Video Ads sources are generated dynamically like the Google Video! So it will be impossible with hosts to block all of'em!
Else, it removes all other ads.
To uninstall Magisk Module, just remove the module from Magisk Manager and reboot!
Click to expand...
Click to collapse
how it can be used with adaway? afaik it both changes the host file right? and adaway will refresh and replace the host with its version only
Why is the all in one module of such small size compared to the others?
raxijuciro said:
how it can be used with adaway? afaik it both changes the host file right? and adaway will refresh and replace the host with its version only
Click to expand...
Click to collapse
Check this main thread - https://elbo.in/energizedxda ... You will find mirror link to use with Adaway! :fingers-crossed:
Redhawk2000 said:
Why is the all in one module of such small size compared to the others?
Click to expand...
Click to collapse
Because, All-In-One let's you choose the pack you want to use. It also comes up with whitelisting and blacklisting with extensions support on the go! It's all about script!
When you choose a pack, it downloads and applies the pack.
Otherside, standalone packs contain the hosts in it and just need to flash, to work!
raxijuciro said:
how it can be used with adaway? afaik it both changes the host file right? and adaway will refresh and replace the host with its version only
Click to expand...
Click to collapse
Get the MIRROR link of the PACKAGE from the main thread you want, and add it to Adaway > Hosts Sources. Then simply apply.
Yea, it will replace the hosts or systemless hosts of your device.
Feel free to ask, if you need any help!
Does it work just like adaway or it also block Facebook ads and YouTube ads ? Or does it hide the ads white space ? (Like adguard)
So just quickly trying it, I disabled adaway and flashed the 12kb all in one zip via magisk manager. It hung on reboot for several minutes so I forced a reboot again and it booted normally. Magisk manager showed the module as installed but I see ads as if no effect.
I removed that module and flashed a stand alone module via M manager and rebooted fine but still no effect. When I reenable adaway ads are blocked.
Am I missing something?
LeEco Pro3 with AICP Oreo 8.1
Sent from my LEX727 using XDA Labs
Redhawk2000 said:
So just quickly trying it, I disabled adaway and flashed the 12kb all in one zip via magisk manager. It hung on reboot for several minutes so I forced a reboot again and it booted normally. Magisk manager showed the module as installed but I see ads as if no effect.
I removed that module and flashed a stand alone module via M manager and rebooted fine but still no effect. When I reenable adaway ads are blocked.
Am I missing something?
Click to expand...
Click to collapse
Have you tried anabling (or disabling) the systemless hosts option in Magisk Manager settings?
abacate123 said:
Have you tried anabling (or disabling) the systemless hosts option in Magisk Manager settings?
Click to expand...
Click to collapse
It's enabled. I didn't try disabling it though as I thought it had to be enabled.
Sent from my LEX727 using XDA Labs
Redhawk2000 said:
So just quickly trying it, I disabled adaway and flashed the 12kb all in one zip via magisk manager. It hung on reboot for several minutes so I forced a reboot again and it booted normally. Magisk manager showed the module as installed but I see ads as if no effect.
I removed that module and flashed a stand alone module via M manager and rebooted fine but still no effect. When I reenable adaway ads are blocked.
Am I missing something?
LeEco Pro3 with AICP Oreo 8.1
Click to expand...
Click to collapse
After enabling module have u downloaded hosts packs?
Just installing module doesn't block ads
You have to download hosts
In terminal
su
energized
Then select a pack of your wish.
tlf55 said:
Does it work just like adaway or it also block Facebook ads and YouTube ads ? Or does it hide the ads white space ? (Like adguard)
Click to expand...
Click to collapse
Yea. It's kinda like Adaway, but with more hosts, from reputable sources baked in!
You know, Facebook Ads are from graph.facebook.com, You can block it personally. It causes few issues with Facebook Apps if we block it.
Moreover, you can't use cosmetic filters with hosts. So it won't be able to hide all the ads. One of the few limitations of hosts.
Stay Energized Mate!
Kirisakura-Kernel for the Asus Zenfone 6
Hello everyone,
After rising to the most popular Kernel on Pixel 3/XL, here it is for the Asus Zenfone 6!
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this, alongside Kirisakura-Kernel for the OnePlus 8 Pro, may be (and probably is) the first 4.19 msm kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3, 4 and 5 devices.
The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
Another security feature is Shadow Call Stack (SCS). Similar to CFI, only the Pixel 3, 4 and 5 kernels use this security feature.
SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
If you´re interested here are a few good links:
Google Security Blog explaining SCS.
LLVM doc about SCS
Android DOCs documenting SCS
If reading about upstream in the paragraph above got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 855/+ that´s built into the different SKUs of the Zenfone 6.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
Many of the improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 11
- Upstreamed against latest CAF
- Linux-Stable-Upstream included to latest 4.14.220
- compiled with Clang 11.0.1 prebuilt from Google
- Link-Time-Optimization (LTO)
- Kernel Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO for full program visibility (needed by CFI)
- fix CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Anykernel zip is based on the all new Anykernel3 release from @osm0sis
- include vDSO 32 patches to improve 32-bit performance
- disable various debugging configs, that are not needed in a perf build kernel according to google.
- disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
EAS related features:
- backported scheduler from sd865
- disable autogroups and use cgroups for more efficient task placement!
- disable core_ctl for improved task placement and load balancing
- updates from kernel/common
- scheduler updates from Googles Pixel kernel
CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers ( MM, audio) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
- vdso32 patches as found on Google Pixel devices (brief documentation here)
File System related features:
- Set the bio REQ_NOENCRYPT flag (When lower layers such as dm-crypt observe the REQ_NOENCRYPT flag, it helps the I/O stack avoid redundant encryption, improving performance and power utilization. ) (CAF default)
- improve memory allocations in sdcardfs
- improve eventpoll logging to stop indicting timerfd (improves kernel wakelock readability)
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
- ufs improvements from pixel 4/ pixel 5 kernel
GPU related features:
- KCAL to control the display
- KLAPSE integrated
- KCAL/KLAPSE: changes safety measures -> allow completely disabling two RGB values (this was requested to, for example, only have red values on night dimming)
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbrv2
Memory related features:
- Memory Management patches from mainline kernel
- Speculative Page Faults (1. 2)
- Fix various memory leaks in different subsystems
- Reap memory of a task that receives sigkill
- enabled per process reclaim
- allow ZRAM to use higher swappiness values than 100
- possibility to use lzo-rle as default ZRAM compression algorithm (more information here and there )
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- Shadow Call Stack (SCS) Security-Feature
- fix various CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
WLAN Driver
- use CAF wlan driver and compile it inline, the only way to ensure working wlan with this kernel
- the kernel cannot even force load prebuild WLAN module as the kernel base is way to far from stock!
- do no longer rely on the pre compiled wlan driver module
- completely removed qcom_rx wakelock in the wlan driver
- removed debugging from wlan driver
- removed logging from wlan driver
Magisk Companion Module
- set kernel settings like I intend them to be
Misc Features:
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!
Other features:
- disable logging to make the kernel more lightweight in various places
- fix several coding issues detected by newer Clang-Toolchains
- add support for steam controller
- add support for nintendo switch controller
- ufs improvements from pixel 4/ pixel 5 kernel
- gpu/kgsl improvements from pixel 4/pixel 5 kernel
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
How to flash the Kernel:
1. Download the latest kernel.zip
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk stable. (not the latest canary!)
3. Flash the kernel.zip via latest EXKM or FKM app. Alternatively via TWRP.
4. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9/Pie
1.0.0 Initial Release
1.3.0 https://forum.xda-developers.com/showpost.php?p=79852192&postcount=21
1.5.0 https://forum.xda-developers.com/showpost.php?p=79948337&postcount=36
1.6.0 https://forum.xda-developers.com/showpost.php?p=80037776&postcount=46
1.8.1 https://forum.xda-developers.com/showpost.php?p=80275065&postcount=58
3.0.0 https://forum.xda-developers.com/showpost.php?p=80712703&postcount=66
Android 10/Q
1.0.0_Q https://forum.xda-developers.com/showpost.php?p=81368413&postcount=73
1.0.3_Q https://forum.xda-developers.com/showpost.php?p=82387237&postcount=86
1.2.0_Q https://forum.xda-developers.com/showpost.php?p=83920653&postcount=92
Android 11/R
1.0.1_R https://forum.xda-developers.com/t/...sus-zenfone-6-aka-kirin.3940178/post-84526765
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
Asus for the Zenfone 6!
@osm0sis for all his work, including the ak2 installer!
@tbalden for being the best HTC wingman!
@LeeDroid for his awesome roms!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@topjohnwu for magisk!
@osm0sis for anykernel!
XDA:DevDB Information
Kirisakura-Kernel, Kernel for the ASUS ZenFone 6 (2019)
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_Kirin
Version Information
Status: Stable
Mine for FAQ
Too
And too
Flashed it today and no problems so far.
Everything seems to work as intended
Freak07 said:
Mine for FAQ
Click to expand...
Click to collapse
Which RAM version do you have please?
Is the kernel for both?
EMJI79 said:
Which RAM version do you have please?
Is the kernel for both?
Click to expand...
Click to collapse
The 8GB version. RAM variant shouldn´t matter.
1. Does it have to be magisk stable or is canary (dev version) ok? I am asking because i need to use canary so my stupid pay app will not detect root.
2. This might sound stupid but what is magisk companion and where do i get it? I can not find it in the magisk modules repository or on xda and neither google.
2. This might sound stupid but what is magisk companion and where do i get it? I can not find it in the magisk modules repository or on xda and neither google.[/QUOTE]
It's in the downloads folder at the end of the afh link in the OP
isthisadagger said:
1. Does it have to be magisk stable or is canary (dev version) ok? I am asking because i need to use canary so my stupid pay app will not detect root.
2. This might sound stupid but what is magisk companion and where do i get it? I can not find it in the magisk modules repository or on xda and neither google.
Click to expand...
Click to collapse
jeremyet said:
2. This might sound stupid but what is magisk companion and where do i get it? I can not find it in the magisk modules repository or on xda and neither google.
Click to expand...
Click to collapse
It's in the downloads folder at the end of the afh link in the OP[/QUOTE]
1. you can probably use the canaries of magisk too. But keep in mind, they’re canary builds for a reason. If you’re having issues, flash to magisk stable and see if you can reproduce them.
2. Like @jeremyet said, it’s in the download folder in the OP
good job man
@Freak07: Cool, the first costom kernel for the Zenfone 6, thanks
I am still thinking of switching to the Zenfone 6, one feature I currently use a lot, is the "USB fast charge" : it makes a big difference, if I have my Smartphone for file transfer on my Laptop or PC, whether it charges in the background only with 500 mAh or with a little over 900 mAh on my USB 3 ports.
Does your kernel support USB fast charge / if not: will it be supported? (some custom kernels devs don't want to implement it, bacause it is not an official feature and "might" not work perfectly)
Coming from stock kernel, I got stuck at the Zenfone logo during reboot after the first flash with exkm. Volume down+power fixed that and after flashing a second time all seems to be working ? zram is at 684mb for my 6Gb variant.
Thank you a lot.
A quick question about the kernel source: Is there an API/kernel endpoint that can be used to query and manipulate the flip camera's motor? If so, is it something than can be accessed from userland? I was wondering if one might be able to write a shell script that can be used to send commands to it.
Does camera has OIS? I've seen OIS code in DTS
dmd79 said:
Does camera has OIS? I've seen OIS code in DTS
Click to expand...
Click to collapse
It's not the object of this thread.
There's a "ask me anything thread" in the discussions forum.
Flashing via EXKM will NOT work, if you’re on the latest magisk canary! (currently 19305!)
19302 is still working fine with EXKM, as is stable 19.3. Big changes in magisk are coming. we will have to wait for flar2 to find a new way of flashing zips.
Can this be flashed on the latest update or does it require an update from you? If not are there any downsides to it not being based on the most current kernel source code then?
Kind regards
regenwurm16 said:
Can this be flashed on the latest update or does it require an update from you? If not are there any downsides to it not being based on the most current kernel source code then?
Kind regards
Click to expand...
Click to collapse
Wait a bit. I’ll release an update soon. (hopefully later today) This will have latest asus sources merged.
I currently see 2 downloads for my kernel :cyclops: so I thought I can take it slow.
Testing was good so it should be ready for prime time stay tuned!
Thanks for your effort.
If think the two downloads are because of the scarce availability of the phone. I ordered mine on 5th of June on Amazon Germany the 6GB RAM 128GB ROM variant (only model they sell) and it took until 1st of July to get to me
I would have ordered on the Asus eShop but they don't ship to my country/don't have a shop for my country
Just take a look in the UK availability thread it's even worse there
# NO LIMITS INFECTED
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!​
## Introduction
No Limits Infected V3, is the fusion between the No Limits and Infected modules, improved in terms of ram, added entropy of core automation, shedulers, battery and dooze, fast loading, excellent improvement in gaming, reduction of lag, liquid UI , multitask, new ios fonts, One Ui and Miui sounds, improvisations for a unique user experience, adapting to any version of rom and kernel automatically.
## Description
Shadow project firm that increases the GPU power of the phone by up to 75%, but at the same time puts the performance and stability of the battery in equivalent.
## Functions
This module uses the tools to modify the default values found here to improve gpu and accelerate the performance of your device to the highest level.
## Requirements
* Magisk v15.0 or higher
## Download
[MOD EDIT: URL removed]
## Change Log
* v1.0 - Initial Release
* v2.0 - Various fixes, Unused codes were removed, GPU specific functionalities were added, Load execution failure was fixed
* v3.0 - Added fast charging support, improvements in GPU, CPU, better ram improvisation, runtimes
## Credits
@Dariel Salinas
Testers
This thing is going to likely destroy someones device. A lot of things in it don't have any logic at all. Things you replace from the system can easily brick a device.
- First, there is only one busybox, according to a directory it's only ARM related module, you should mention that or use the set of commands provided by the device.
- Then let's check common directory, there is another busybox file which is not needed and also common/unityfiles/tools have busybox files for ARM and x86. So you have 4 busybox files inside a zip.
data.sh - File which assume to start random entropy generator and thermal-engine. Again those things are not necessary on nowadays devices.
enableinit.sh - A init.d enabler which is not necessary as Magisk module, since we already have a boot triggered service, you can maybe provide a feature by your module to run other scripts trough it. Since i think that 3% of android users don't use init.d
opt.sh - Change Boeffla wakelock blocker and disable Find device feature
Code:
# Disable Find My Device (in order to have optimized GMS for Android 7 or later);
pm disable com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver
well it's not so safety in order to achieve some battery saving which are so minimal, also killing GMS will cause issues with receiving notifications for other apps. And the last part of the code seems like a old fix for a wakelock issue caused by SystemUpdateService.
post-fs-data.sh - Contains fast charging tweaking, keep on mind that not all devices are the same and that shouldn't be touched without a knowledge.
service.sh - Well, this file looks like some older version of NFS module by @k1ks as we can see here:
Code:
# NO LIMITS (SHADOW)
# Codename : Powerfire
# Version : 6.0
# Developer : @Ingen
If this is a first version of your module there should be v1.0? Right?
Now let's take a look in /common/system/bin:
shadowtuner - That's a Governor tuner by:
Code:
# Copyright (C) 2016 Debuffer @ XDA-Developers
# With help from Paget96 and F4uzan
It's okay to use it, but seems like a lot of stuff from it is missing so I can say it wont work at all.
tune.sh - This file makes no sense at all. It assume to start a governor tuner profiles which actually doesn't exists.
Uh!!
/common/system/etc/ShadowGpu - This contains Governor tuner stuff and it seems like it's from few versions which makes no sense.
And /system dir in zip have a lot of file what shouldn't be changed at all, including app permissions, fonts, thermal profiles, notification sounds and everything else.
Sorry for your time spent out here for making something but it cannot be done like this.
Check out basic scripting tutorial:
https://forum.xda-developers.com/android/general/guide-tut-learn-basic-scripting-busybox-t3209180
Learn something and try to make own stuff.
Cheers
What ??!!!!! two words :
Dangerous / Crazy
I'm sorry, I had no idea
Paget96 said:
This thing is going to likely destroy someones device. A lot of things in it don't have any logic at all. Things you replace from the system can easily brick a device.
- First, there is only one busybox, according to a directory it's only ARM related module, you should mention that or use the set of commands provided by the device.
- Then let's check common directory, there is another busybox file which is not needed and also common/unityfiles/tools have busybox files for ARM and x86. So you have 4 busybox files inside a zip.
data.sh - File which assume to start random entropy generator and thermal-engine. Again those things are not necessary on nowadays devices.
enableinit.sh - A init.d enabler which is not necessary as Magisk module, since we already have a boot triggered service, you can maybe provide a feature by your module to run other scripts trough it. Since i think that 3% of android users don't use init.d
opt.sh - Change Boeffla wakelock blocker and disable Find device feature
Code:
# Disable Find My Device (in order to have optimized GMS for Android 7 or later);
pm disable com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver
well it's not so safety in order to achieve some battery saving which are so minimal, also killing GMS will cause issues with receiving notifications for other apps. And the last part of the code seems like a old fix for a wakelock issue caused by SystemUpdateService.
post-fs-data.sh - Contains fast charging tweaking, keep on mind that not all devices are the same and that shouldn't be touched without a knowledge.
service.sh - Well, this file looks like some older version of NFS module by @k1ks as we can see here:
Code:
# NO LIMITS (SHADOW)
# Codename : Powerfire
# Version : 6.0
# Developer : @Ingen
If this is a first version of your module there should be v1.0? Right?
Now let's take a look in /common/system/bin:
shadowtuner - That's a Governor tuner by:
Code:
# Copyright (C) 2016 Debuffer @ XDA-Developers
# With help from Paget96 and F4uzan
It's okay to use it, but seems like a lot of stuff from it is missing so I can say it wont work at all.
tune.sh - This file makes no sense at all. It assume to start a governor tuner profiles which actually doesn't exists.
Uh!!
/common/system/etc/ShadowGpu - This contains Governor tuner stuff and it seems like it's from few versions which makes no sense.
And /system dir in zip have a lot of file what shouldn't be changed at all, including app permissions, fonts, thermal profiles, notification sounds and everything else.
Sorry for your time spent out here for making something but it cannot be done like this.
Check out basic scripting tutorial:
https://forum.xda-developers.com/android/general/guide-tut-learn-basic-scripting-busybox-t3209180
Learn something and try to make own stuff.
Cheers
Click to expand...
Click to collapse
Sorry, I had no idea how dangerous it could be. Could you review this other module that I planned to upload before making any changes? If it also turns out to be dangerous, I delete the post to avoid problems ...
Module Link: https://drive.google.com/file/d/10FMH4meNwi-H_qrGfyugGd3LqTI-_gbg/view?usp=drivesdk
Thread closed. If you're going to use parts from other developers work, get their permission first. It avoids problems, and you may be able to get insight from them before something could cause catastrophic daily if a device.
When you're ready to re-release, PM me, and I'll reopen the thread.
Kirisakura-Kernel for the OnePlus 8 Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the OnePlus 8 Pro aka InstantNoodle.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this may be (and probably is) the first 4.19 msm kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If that got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 865 that´s built into the OP8 Pro.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst others to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
I´d like to mention @tbalden ´s excellent CleanSlate features at this place. They improve usability by a big margin for me personally. The highly customizable sweep to sleep implementation (adjustable to different navigation settings), long tap to bring down status bar (very useful on a big device), backlight dimmer and notification reminder are very useful features that I use personally every day, which can be enabled rootless if one desires to run without root.
Another big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from OnePlus for Android 10 and intended for use on OOS-Stable releases
- compiled with Clang 11.0.3 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.19.146
- CAF base for the Snapdragon 865 (SD865) updated to CAF-Tag LA.UM.8.12.r1-12500-sm8250.0
- Kernel Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO
- fix various CFI-Violations found in various subsystems like OnePlus drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Cleanslate Features included! See @tbaldens´s CleanSlate Thread for more information
- Flashable via EXKM and FKM on a rooted system!
- Anykernel zip is based on the Anykernel3 release from @osm0sis
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- Dynamic Stune Boost to inflate task utilization and not overload cores on interaction (thanks to @RenderBroken, @joshuous and @tbalden for the rootless implementation )
- updates from kernel/common
CPU related features:
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This compliments EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
GPU related features:
- GPU driver updated to latest CAF-State
- remove POPP functionality from GPU driver to avoid constant fight about downscaling with msm-adreno-tz
- don´t wake the gpu on touch input, instead wake when receiving an ioctl
- don´t copy fence names by default to save a bit of cpu-time (explanation)
- msm: kgsl: Stop slab shrinker when no more pages can be reclaimed
File System related features:
- improve memory allocations in sdcardfs
- improve eventpoll logging to stop indicting timerfd (improves kernel wakelock readability)
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Flashlight Notification/Call blinking
- Vibrating Notification Reminder
- Sweep to Sleep touchscreen gesture - highly customizable
- DoubleTap on Sweep2Sleep's area gestures - new way to pull down android Notification Area
- Face down screen off - new gesture
- Backlight Dimmer - possibility to use lower panel brightness (switch DC dimming off in Lab settings!)
- KCAL Color Control (credit to @savoca)
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF default)
- various fixes for PSI-Monitor, which is used by the userspace lowmemorykiller-daemon
- Fix various memory leaks in different subsystems
- improved mm with patches from mainline
- various other changes from mainline
- included zstd as an option for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- improve memory allocations in various subsystems
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- fix various CFI-Violations found in various subsystems like OnePlus drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled, enable them with your favorite kernel manager
- includes new bbr2
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!
Other features:
- disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
- fix several coding issues detected by newer Clang-Toolchains
- add support for steam controller
- add support for nintendo switch controller
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching OnePlus firmware. When OOS receives an update it takes OnePlus a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk-stable, if you choose to use Magisk.
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP (haven´t tested TWRP myself as I don´t need it) and do a full reboot.
4. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=313864
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 10
1.0.0 Initial Release
1.2.0 https://forum.xda-developers.com/showpost.php?p=83260487&postcount=67
1.2.2 https://forum.xda-developers.com/showpost.php?p=83521551&postcount=119
1.2.4 https://forum.xda-developers.com/showpost.php?p=83539543&postcount=125
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid and @mwilky for their awesome roms and work!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help too
@topjohnwu for magisk!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the OnePlus 8 Pro
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_OP8PRO_InstantNoodle
Kernel Special Features:
Version Information
Status: Stable
Created 2020-06-19
Last Updated 2020-09-20
FAQ
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img from matching firmware you are on and flash the extracted boot.img via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom.
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
Please also take a log at the FAQ one post above. It covers some procedural steps as well and serves as a guideline too!
https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt
Hello everyone
I want to lose a few words about this kernel.
Before anybody asks, it´s made for the OP8 Pro only!
As you may or may not have noticed by reading the OP this kernel is very far from the stock base.
Adding linux-stable upstream and CAF-Upstream causes the commit-count to increase from 805000 to about 840000.
A "higher" commit count does not automatically translater to a better kernel. However upstreaming linux-stable and the CAF-Base to the latest code is an important aspect, that´s often cast aside. (after all the android kernel is based on the linux-kernel and the CAF-Base is the kernel base OnePlus bases the kernel for the OP8 Pro on) . Many developers work constantly on improving the linux-stable branches with commits that are tested, same goes for the qualcomm developers over at the CAF-Forums.
The main goals of this kernel are summarized in the OP. I encourage everyone to at least read once through it.
Here´s a short summary of what I think are the most characteristic and important aspects (also an excerpt from the first post of this thread ):
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this may be (and probably is) the first 4.19 kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If some of that got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 865 that´s built into the OP8 Pro.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst others to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
I invite everybody to try the kernel
If you face any bugs, I´d appreciate if bug reports are done in the proper way, like it is asked for and explained in the 2nd and 3rd post.
If you read the OP you probably noticed I´m not talking about any improvments (some call it even magic) to performance or battery life. This is not one of the direct goals of this kernel.
If the modifications present in the kernel make you feel a noticable difference in either of these I´m very happy for you. I know that artifical benchmarks are improved and some other things I tested.
If this kernel is not for you you can very easy return to the stock kernel, like it´s described in the FAQ as well!
There might not be updates of this kernel for every single linux-stable upstream revision that is released at kernel.org or every single new commit added to the tree, but rather less updates but bigger ones.
I guess that gives everybody a rough idea of where this project might be going.
I wish everybody a nice day
Loved this for the 7 pro. Welcome ?
Woohoo, welcome!
Congrats on this truly great achievement.
Keep it up.
[emoji106][emoji106][emoji122][emoji122]
Sent from my Pixel 4 XL using Tapatalk
Excellent, welcome!
Hey buddy! Nice to see you here! ?
possible to add option to disable touchboost?
tbalden said:
Woohoo, welcome!
Congrats on this truly great achievement.
Keep it up.
[emoji106][emoji106][emoji122][emoji122]
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Thank you! Glad to have you as a wingman for a very long time across different devices now!
Keep on rocking with all the CleanSlate goodies!
Reuben_skelz92 said:
Loved this for the 7 pro. Welcome
Click to expand...
Click to collapse
kristofpetho said:
Excellent, welcome!
Click to expand...
Click to collapse
TheKnux said:
Hey buddy! Nice to see you here!
Click to expand...
Click to collapse
Thank you
Nekromantik said:
possible to add option to disable touchboost?
Click to expand...
Click to collapse
Yes, since all Cleanslate features are included it´s accessible via CleanSlate config app.
https://forum.xda-developers.com/showpost.php?p=82598221&postcount=192
Gestures and Extras Section - Stock touchboost.
nice to see ya here
Doing a sexy dance right this minute! :victory: Dam glad your covering this device now also buddy Always a great solid kernel that runs smooth and fluid without issue! :good:
Omg the kernel was amazing on the OP7P, can't wait to use this one again on my 8!
Running smooth as butter for me ?
Thank you sir, donation sent.
Nice to see this Kernel here for the 8pro
Gesendet von meinem IN2023 mit Tapatalk
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Lxeon said:
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Click to expand...
Click to collapse
The lowmemorykiller daemon is no longer in the kernel. it’s handled from userspace on the op8 pro on android 10 OOS.
Unfortunately nothing I can do in the kernel to change this.
If apps are getting killed say thank you to OnePlus and OOS. Not related to the kernel.
Lxeon said:
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Click to expand...
Click to collapse
Try to disable zram/swap
cultofluna said:
Try to disable zram/swap
Click to expand...
Click to collapse
still around 65%
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
Freak07 said:
The lowmemorykiller daemon is no longer in the kernel. it’s handled from userspace on the op8 pro on android 10 OOS.
Unfortunately nothing I can do in the kernel to change this.
If apps are getting killed say thank you to OnePlus and OOS. Not related to the kernel.
Click to expand...
Click to collapse
good hardware, suck software