Related
So Ive been playing around with doogees new firmware and I discovered
Warning : Never pay a cent for your stock firmware no matter how desperate you are there is a free solution somewhere on the internet
NOTE: I will not be held responsible for bricked devices, You flash mods as a choice and when modding values use google and learn how those values work before modifying if dont understand look at more webpages before your final decision.
1. The Doogee y9 plus and the Doogee N20 and Umidigi A5 pro(check commits) are the exact same phone but just with different features and settings
2.The doogee variants have been coded mishmashingly-some of the props are loaded from vendor and some from system and from both, then if a value is changed on one you have to change the other otherwise there will be boot fail/boot fail_critical (bootloop).
Both: Exact same hardware , the rooting and flashing method is exactly the same (umidigi just has different partition Tables/ PMT)
If you change a parameter you have to change it in vendor partion to make it stay forever or cause less system internal conflict
Dogge Y9 plus release: More polished and more locked down (boot, security, rooting etc)
Has 3 releases eea, user and Russia (user version worked best)
Doogee N20 release : the Development build : has missing features, some features which are enabled but don't work because of code and missing hardware (nfc - You can manually add one that is compatiable and edit vendor,system boot partions (theres maybe 4 which specify nfc app(disabled by vendor or system ) and hardware)... )
Has an unknown number release of versions (doogee moderators decided to remove links to some of the official copies on their forum in 2019-late 2019 (This was when they were changing their business model from you get to root and do what you want with your device without voiding warranty , then 2021 completely removed all traces of it but not the actual files (i dont know where these are the mod I was in touch with got removed and blocked - He "violated policy or knew too much , He communicated with developers))
I only know of 2 existing public releases early 2019 and late 2019 files
comparisons-
The doogee N20 firmware is more open and you can flash custom roms(gsi treble arm64 ab) with it, the y9 you can but you'll run into bootloops (a working on I found was the pixelexperience10 gsi arm64 ab
The doogee y9 release can block you from flashing the doogee n20 firmware, aaawthich is why so many of you found yourself with a bricked device but didnt know why it wasn't flashing the n20 stock rom (from need rom and other sites), The Y9 plus stock rom is found on halab tech website
(other notes) The doogee forum will run away from anything related to the doogee y9plus/ n20 because its an OP phone and it was easy for their developers to build on it to compete with the current medium-high to high end devices) and upgrade to perform better (but the comppany run by all money hungry dogs but hey they got to make a living too :/)
Others to be added later
To NEVER AGAIN BRICK THE DEVICE(except when OC / fall) :
TWRP
Stock firmware (N20 and Y9 plus, if one fails to flash the other one will flash no hassle)
SP Flash tools, when in bootloader mode(phone off) your phone will install the drivers you need
If you're rooting via magisk have a copy of the n20 and y9 plus boot images modded by magisk app (I no try SuperUser or it failed once or i intalled it incorrectlyand i said screw it)
To find the working doogee y9 plus doogee n20 stock firmware respectively in that order:
Halab tech support, anywhere on google just search doogee n20 firmware or stock rom
if anything happens with the halab tech support or youre asked to pay for the stock firmware, I have backed up copies of the releases and you can contact me(toggle signature or open my profile ) within 7 days I will give you link to download
else
search doogee y9 plus firmware in chinese (traditional) if remember correctly
Mods Updates(currently magisk independant ned twrp and pc, i dont know how to make twrp flashable zips )
THe seccond attached image is about the gpu used, it a bad gpu but in my mod I will underclock but run at higher minimum lock speeds
Trying to remove gaming fps cap, under my tests openl performed best with consistent 30fps but it was capped to 30 fps (thats why pubg and COD only offer 30 fps max the vulkan driver was just bad but had no fps cap or 60fps. weirdly the system ui and launcher had gone up to 77 fps consistently to 91 before capping dropped it back to 60fps but this was with forced unlocked fps, With a burst fps divisor it jumped to 101 fps at a point
Increased CPU clock speeds or I'll just make custom performance kernel parameter and make it the default setting, increase minimun clock speeds for both clusters to maybe 1000mhz and reduce maximum clock speeds for all clusters by maybe 100 to 300mhz
Enabling the root switch or possibly bypassing user limitations (engineer flavor, or Android Test mode(i can't find the ATM apps so far,unless the options will be in settings)
More coming soon
If it helped you in any way please consider liking post and donating ( www.paypal.me/xleage ). Donation link also in my profile
Happy Unbricking and modding . I've waited at least 2 years to say this lol
Here is one of the mods I'm working on so you can flash anything you want and modify your phone as you please (attached screenshot)
NOTE: modifying the wrong values, the wrong way will make you brick your device or break it
To restore default se linux values and just go to twrp, file manger ,rename buofrc, buof... files [remove "buof" in name and use that as overwrite]
Commits
You will have full control/access of your phone from recovery, the y9 is brother of umidigi a5 pro (second attatched screenshot)
adding more partions to be mounted (mntd at end) as storage for easier customizing security and other crap) mods
misc adds(using test display driver)
patched se linux contexts so all users are root perm enabled(from my research your phone will be easily hackable,(I will learn how to add my own custom parameters like the Superuser/ magisk (apps out of priv-app will use request requesting root permission)[kernel access added]
Updates ([Beta phase] images based on stock Doogee Y9 plus user files from halabtech)
I'll be fixing cpu and gpu clock speeds and removing the 30fps cap for rendering to possibly 40+ to 60 fps cap (don't wanna fry phones)
I'll be disabling some security features (faster boot and freeing up cpu,gpu and ram resources)
Releasing mods (images and magisk module) for your doogee y9 and n20 (will work for both) (just flash a modded (magisk patched boot.img from the ones I release. most likely all of them will be magisk patched as I figure out some things)
Inode values increased for larger files faster speeds(resource intensive games)
Ported values from the lagless Umidigi A5 pro big boi brother(like the zram swap fie size,made it smaller but it increases performance, tried disabled but the service to stop it fully was refusing to turn off and meant no visible performnce gain)(our firmware was the crappy mod version)
Releasing as twrp flash file
I don't know if I'll have permission to remove questions so Please remove when asked to do so
Just add this to watched threads so you don't miss updates and mods
I still am hoping Sptember 25 or 30 2021 intial releases (uploading working files)
Please Tell me if you'd like to help with testing, you will get the latest releases as soon as I finish testing them myself if they work, then you'll game and test for any other possible bugs
Tools needed TWRP , EXTERNAL Storage
Mods:Y9N20RAMDISK_Patched.img
Group 1
files:init and zygote
Info: Changed values for user enable root and r/w access for everything
Flash via SPflashtools
Group N20Y9Unlockpart2.zip
files:TWRPflashable zip
Info:fixing system stuff not to fight
flash via twrp
Thanks to:
topjohnwu
4.pda ru
Lineage OS devs
apb_axel and yarpiin (for UKM.zip)
List will updated soon as we go along
Information That may be hidden
Version for Marshmallow is available here: https://forum.xda-developers.com/t/...zation-for-old-touchwiz-mm-framework.3372401/
Version for Nougat is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-n-framework.3692391/
Version for Oreo is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-o-framework.3749479/
Version for Pie is available here: https://forum.xda-developers.com/t/...-14-customize-samsung-oneui-24-05-20.3908114/
Version for Q is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-2-0-30-12-20.4044757/
Version for R is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-3-x-14-03-21.4212051/
Firefds Kit [ S ]
Xposed module for Samsung S devices.
Known working devices:
Galaxy S20
Galaxy S20
Galaxy S10
Features
The module has the following features:
Fake system status to Official
Custom advanced power menu options:
Power off
Restart
Emergency mode
Recovery (with custom text)
Download
Data mode switch
Screenshot
Switch User (when multi user is enabled)
SystemUI restart
Flashlight
Screen Recorder (requires Samsung screen recorder app installed)
Disable restart confirmation
Enable performing power menu reboot / power off actions only after unlocking secure lock screen (stock behavior)
Disable display of power menu when secure lockscreen is locked
Change default behavior of reboot to reboot to recovery
Replace Reboot to Recovery icon with system default restart icon
Enable call recording and call recording settings
Replace add call button instead of call recording and adding record by menu option
Clock Size option
Enable Call ID and spam protection option
Enable Screen Record tile and Settings options
Enable screen record while in call
Enable additional advanced hotspot settings option
Hide VoLTE icon in status bar
Hide persistent USB connection notification
Hide persistent charging notification
Enable block phrases in messages app settings
Enable native blur on notification panel pull down
Enable multi user toggle
Set max user value selector
Show seconds in status bar clock toggle
Show AM/PM for seconds on clock toggle
Show clock date on right of clock toggle
Add date to status bar clock options
Enable fingerprint unlock on reboot toggle
Enable biometrics unlock on reboot toggle
Add network speed menu to show network speed in the status bar
Data icon symbol selection (4G, LTE, 4G+, 4.5G)
Show Data usage view in quick panel
Double tap for sleep
Hide NFC icon
Disable Bluetooth toggle popup
Disable sync toggle popup
Disable high level brightness popup
Hide carrier label
Carrier label size selection
Disable loud volume warning
Disable volume control sound
Disable low battery sound
Screen timeout settings
NFC behavior settings
Auto MTP
Disable camera temperature check
Enable camera shutter sound menu
Disable call number formatting
Disable SMS to MMS threshold
Force MMS connect
Bypass exchange security (currently not working)
Disable signature check
Disable secure flag
Attention
This version was tested by the community and not by me, as I don't have an Android 12 Samsung device.
THERE COULD BE BUGS/CRASHES/BOOTLOOPS, but it's pretty stable.
Please upload any xposed logs when you encounter any issue. I can't help you without the logs!
Installation
To install this module you need the following apps and modules installed on your device:
Magisk v24.0 and above - https://github.com/topjohnwu/Magisk/releases
Option 1 - Zygisk
LSPosed Magisk Zygisk Release module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Option 2 - Riru
LSPosed Magisk module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Riru Magisk module v25.0.0 and above - https://github.com/RikkaApps/Riru/releases
Download
Directly from LSPosed Manager or from Github : https://github.com/Xposed-Modules-Repo/sb.firefds.s.firefdskit/releases
Source Code
https://github.com/Firefds/FirefdsKit/tree/S
Known Issues
A lot has changed since Android 11. Since I don't have an Android 12 device all tests have been done with various testers. THERE MAY BE UNKNOWN ISSUES!!
Some features are removed on purpose. Since GravityBox has been working on Samsung Oreo devices without much issues, I only implemented features that need special Samsung coding.
Reporting Issues
When reporting an issue, please include Xposed logs and screenshots if any. Reporting should be done through Github - https://github.com/Firefds/FirefdsKit/issues
External Libraries
The project uses the following libraries:
https://github.com/rovo89/XposedBridge
https://github.com/rovo89/XposedMods/tree/master/XposedLibrary
Samsung framework libraries which are used for compile only
EdXposed Whitelisting
Users who want to use EdXposed's whitelist feature should whitelist the following apps:
Android System - android
Call - com.samsung.android.incallui
Call Settings - com.samsung.android.app.telephonyui
Camera - com.sec.android.app.camera
Contacts - com.samsung.android.contacts
Email - com.samsung.android.email.provider
Firefds Kit - sb.firefds.s.firefdskit
Messaging - com.samsung.android.messaging
MTP Application - com.samsung.android.MtpApplication
NFC - com.android.nfc
One UI Home - com.sec.android.app.launcher
Settings - com.android.settings
Smart Capture - com.samsung.android.app.smartcapture
Software Update - com.wssyncmldm
System UI - com.android.systemui
Credits
This module wouldn't have been here without the following people:
RikkaW - Creator of Riru Magisk module, which provides a way to inject codes into zygote process
@rovo89 - Creator of the original Xposed framework APIs
solohsu and MlgmXyysd - Creators of the EdXposed Magisk module and Installer that made all of this possible
@C3C076 - Creator of GravityBox Xposed modules, which I learnt a lot from
@wanam - Creator of the original XTouchWiz module, which this module is based on.
@topjohnwu - Creator of Magisk
@AbrahamGC - For the Extended Power Menu - Pie - Odex framework Smali guide
Big thank you to @m8980 and @ianmacd for testing countless versions and sending xposed logs
Telegram
Announcements and pre release versions - https://t.me/firefdskit
This is a moded version of Wanam's XTouchWiz:
https://github.com/wanam/XTouchWiz
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
okij said:
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
Click to expand...
Click to collapse
Thanks! This looks great! I'll add it to the next version
firefds said:
Thanks! This looks great! I'll add it to the next version
Click to expand...
Click to collapse
Thanks! I'm glad you like it and look forward to the next version.
IIRC Firefds Kit 11 uses the same icons (I have been using it until I switched to Android 12 two months ago), so you might use the new icons there too.
Thanks.
All my devices now bootloop with NoClassDefFoundError: com.android.systemui.BasicRune
Any chance we could add those whitelists to LSposed "Recommended"? Exactly the most important call recording check is missing.
Btw if LSposed 1.7.2 is installed, Riru can be uninstalled? -> looks like Sui uses Riru, so no switching.
In the end, I could leave Firefds enabled if I don't change anything, luckily call recording is on by default.
Thanks for the update for Android 12. Everything working good on my A52s 5g. Hope that one day you can add the ability to adjust the height of the navigation bar. That was available in the gravitybox app but there is no upgrade for 12 yet and not sure there will be which is why I've asked here... appreciate your efforts though.
Is there an easy way to fix bootloop in case something went wrong?
donkeyman1234 said:
Is there an easy way to fix bootloop in case something went wrong?
Click to expand...
Click to collapse
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me delete it worked and I didn't have to disable lsposed modules or the magisk
Kuba1996 said:
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me it worked and I didn't have to disable lsposed modules or the magisk
Click to expand...
Click to collapse
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
donkeyman1234 said:
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
Click to expand...
Click to collapse
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root without custom recovery?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
You can look at last post here and try do something like that. Mabye try in recovery choose "update from adb" and try erase with adb command (your directory: riru-core). Or try use this but I dont think it will work
[Tool][Aroma] Magisk Manager Recovery Tool V2.5
Warning: It's not a Magisk module! Description This is a Magisk module management tool that can be used in Recovery mode. It's based on Aroma Installer. You can manage almost everything in Magisk with this tool. You can manage installed modules...
forum.xda-developers.com
Kuba1996 said:
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root witchout custom recovery?
Click to expand...
Click to collapse
I used magisk patched AP file to root. There is no twrp for s22u.
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Also You can flash in odin patched ap and rest of file but with HOME_CSC not CSC
Check this:
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Had the same issue with my s22u. I reflashed through odin. Gonna try and flash this module again with magisk bootloop protector. fingers crossed.
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Hello,
Thank you for A12 update.
So nice to have your magic on this version.
I would also love to see the ability to adjust navbar, and the possibility to move cursor with buttons in navbar like in GravityBox.
For me, Force MMS to connect isn't working on BeyondRom 4.1.
Is it working for others ?
I am using LSPosed zygist latest version and safety net 2.2.1
nishantgupta107 said:
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Click to expand...
Click to collapse
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
doggydog2 said:
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
Click to expand...
Click to collapse
Yes, some os settings did get reset. Not sure why. But now I'll wait for a stable release (I have reflashed it now 5-6 times)
Arobase40 said:
You can install Magisk Bootloop Protector module...
It will disable Magisk modules when bootloop occurs.
Click to expand...
Click to collapse
Thanks. I did install, but it did not work, the phone kept rebooting, reflash was my last resort.
Bootloop
S10 plus UI 4.1 A12
LSPosed-v1.8.0-6482-zygisk
Anyone successfully installed viper4android on android 12. Please can you share the steps on how to do it. I've been digging the web on how to do it but failed.
Yep. theres a magisk zip for it. i don't use viper4 any more here it is
The step by step I used to get it working was as follows:
Flash a SELinux permissive magisk module - reboot
Install ainur narsil magisk module - reboot
Disable ainur narsil in magisk manager (not sure if this does anything but it works for me)
Install Audio Modification Library - reboot
Install Viper4Android magisk module AND open the app and install the driver (will reboot as a part of this)
Install Audio Compatibility Patch magisk module - reboot
Re-Enable ainur narsil module in magisk manager
Remove SELinux permissive
I've had success in this order. for the Audio Compatibility Patch I use vol up for the first two options and then vol down for the rest.
The app also seems to need to run in compatibility mode or legacy mode
Not sure if this will work for everyone but seems to be a bit hit or miss in general
Did not work for me . But after flashing the "Sound enchancement for Sony 10" viper4android legacy now worked.
Kirisakura-Kernel for the Sony Xperia 1 IV
Hello everyone,
To keep it short: Here is Kirisakura- GKI - Kernel for the Sony Xperia 1 IV aka Nagara. Nagara is the internal codename for this years development platform of Sony Mark IV devices.
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!
If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
There´s also a cpu-battery saver mode that cuts back the CPU max- freqs, but without the disadvantages like delayed notifications from built into the system user-space power-saving modes.
If that got your curious, I welcome you to continue reading if you´re still interested!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on kernel/common 5.10.149
- compiled with Clang 12.0.5
- CPU-Battery saver to be able to restrict max cpufreqs on the fly, without enabling powersaving modes that might cause missed notifications (see second post)
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- Power saving workingqueues enabled by default
- Change various drivers to use power efficient workingqueues. This compliments EAS in general
- implement LRNG (thanks @arter97, see arter kernel OP for more info )
- Enable support for TTL spoofing
- 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
- f2fs improvments for better efficiency
- scheduler improvements
- psi fixes
- Flashing the kernel will keep root!
- Flashable via EXKM, FKM or TWRP (if available) on a rooted system!
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of stock boot.img or your magisk patched boot.img in case you want to go back to stock.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Firmware (check the feature list for the current firmware the source is based on). When there´s an OTA update for the Sony Xperia 1 IV it takes Sony 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.
If you want to be sure there are no issues, always make sure to run the firmware the kernel is built for!
If you feel adventurous and try in advance, make sure you have a backup ready!
2. Flash the kernel.zip via latest TWRP (if available), EXKM or FKM app and do a full reboot.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder, or attached to the release posts in case AFH is wonky.
https://www.androidfilehost.com/?w=files&flid=335705
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 12
1.0.0 Initial Release
Android 13
1.0.0 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-87711541
1.0.1 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-87945391
1.0.3 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-88241223
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea
If you like my work: http://paypal.me/freak07
Credits:
Sony for the development device, giving me the opportunity to create this project!
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@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 and advices!
@topjohnwu for magisk!
Source Code: https://github.com/freak07/Kirisakura_GKI_Nagara
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: Safetynet does not pass on my phone since I unlocked the phone, why is this so?
Answer: Google introduced hardware backed attestation recently. Unfortunately the old kernel tricks to still get safetynet passing won´t work. Instead you will have to rely on some magisk modules. Short guide in post #4 below.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img from the matching firmware you are on (you can do so by using this tool or similar ones found on XDA and when googling around) and flash via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom and re-root.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: The kernel uses a ramdisk overlay to apply some settings after boot. If you are not rooted these settings will not get applied and you miss some of the optimizations.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , 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.
Feature Documentation:
Here´s a brief documentation about some of the features included in the kernel that can be changed as the user desires.
They can be accessed via either terminal, scripts or for example EXKM manager ( tools -> user settings).
CPU-Frequency Limiting:
Another option is CPU-Freq Limiting. You can now limit the CPU frequency to a few different levels with a sysfs interface. Original implementation is from @tbalden, I only changed it to be accessible via traditional root methods.
Main Switch:
sys/module/cpufreq/parameters/batterysaver
Set this option to "1" to enable the feature
Max-Frequency Selection (Input boosts, such as scrolling boost or app launching boosts will still apply, if touch boost restriction is not set to 1)
sys/module/cpufreq/parameters/batterysaver_level
Set this to "1" to restrict the max CPU-Freqs to 1,6GHZ/1,9GHZ/2,22GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "2" to restrict the max CPU-Freqs to 1,4GHZ/1,6GHZ/1,8GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "3" to restrict the max CPU-Freqs to 1,1GHZ/1,1GHZ/1,1GHZ (Little Cluster/Big Cluster/Prime Core)
Touch-Boost Restriction
sys/module/cpufreq/parameters/batterysaver_touch limiting
Set this to "1" to restrict the powerhal from boosting over the limit defined in batterysaver_level
Set this to "0" to allow the powerhal to boost above the values defined in batterysaver_level, but only during interaction with the Phone!
Screenshots:
View attachment 5309899View attachment 5309901View attachment 5309903
This is for example very useful during gaming to prevent additional heat, if not the highest performance from the CPU is required. Check if the game is running fine on level 1 or 2, and you´ll notice much less heat. Powerdraw will be reduced as well.
Another very useful trick while doing video calls or long extended navigation sessions with google maps to preserve battery or keep the phone from heating. Especially during summer if the ambient temperatures are high.
This is a very easy way to preserve battery or reduce heat without toggling the battery save mode in settings as that restricts background data usage, which can lead to delayed notifications.
How to pass Safetynet after unlocking the bootloader
With the introduction of hardware backed safetynet attestation, passing safetynet has become a lot more complicated.
Some probably remember a while ago, flashing a kernel that forced some flags was enough to pass it. However these days are gone.
Below is a short guide how to pass safetynet on phones that are flagged to use HW attestation (such as the ROG 5).
1. Make sure you´re running latest magisk canary.
2. In Magisk Manager enable both zygisk and deny list.
4. Download the latest Universal Safety Net Fix from @kdrag0n ´s github for zygisk cand flash it in Magisk Manager. Reboot.
5. Profit
Oh, my God! thank you so much for making the IV kernel
am I right to assume that CPU frequency limiting can help the phone not overheat when taking photos?
You are Awesome
tomatoketchup said:
am I right to assume that CPU frequency limiting can help the phone not overheat when taking photos?
Click to expand...
Click to collapse
yes. it should at least slow down the heat buildup. that´s the main goal behind it.
please note that 4k 120fps recording or other demanding tasks might not work without stutters if CPU gets restricted too much.
Apart from app loading times, if the usage is not super demanding level 3 works without major stutters in the UI on 120fps refresh rate.
htcmage said:
Oh, my God! thank you so much for making the IV kernel
Click to expand...
Click to collapse
Thaiban said:
You are Awesome
Click to expand...
Click to collapse
Freak07 said:
yes. it should at least slow down the heat buildup. that´s the main goal behind it.
please note that 4k 120fps recording or other demanding tasks might not work without stutters if CPU gets restricted too much.
Apart from app loading times, if the usage is not super demanding level 3 works without major stutters in the UI on 120fps refresh rate.
Click to expand...
Click to collapse
excellent <3, I don't need 4K 120fps recording I actually only do 1080p 24 because I like stabilization. so going to flash 64.0.A.8.25 and this kernel after that. million thanks!
It's a small amount, but I donated it, thank you always
htcmage said:
It's a small amount, but I donated it, thank you always
Click to expand...
Click to collapse
Thank you very much! I greatly appreciate it.
Hahaha... Hello my good friend @Freak07. Didn't know you were into Sony as well.
@Freak07 can you port it to xperia pro i ?
Developer, I have a question
If I use my work profile (shelter or island apk) I can't get into the settings menu I get a popup stating that the system UI is shutting down, maybe it's kernel related?
Should I uninstall Uperf before flashing?
Also thanks for this excellent work.
great work!Thx
to those who flashed, how is battery live ?
ist compüatible with latest sony update?
Would be interested to know, if it supports the old android kernels feature to emulate CD and DVD. Its a feature that DriveDroid needs to emulate a bootable DVD drive from an *.ISO hosted from an android device over USB. it was present in my older devices until XZ1 Compact and i was able to boot my pc off from a iso file hosted on my android device. It was much convinient than using silly PXE boot over eth0
No more update ?
Mrxyzl said:
No more update ?
Click to expand...
Click to collapse
OP will update when new Kernel sources are released and he has time. Mentioned in the first post.
I've just looked into the KNOXPatch project which is supposed to run with shizuku/lspatch(lposed) and it seems to set to properties (project tells it needs root but i'm not sure about that)
GitHub - BlackMesa123/KnoxPatch: LSPosed module to get Samsung apps/features working again in your rooted Galaxy device.
LSPosed module to get Samsung apps/features working again in your rooted Galaxy device. - GitHub - BlackMesa123/KnoxPatch: LSPosed module to get Samsung apps/features working again in your rooted G...
github.com
It is a root module but can anybody tell if we could unlock developer settings? tried some debugging myself but need to get into android development again. If we would be able to set ro properties we might be able to get root and unlock bootloaders on a lot of devices. People keep talking about the impossibility to unlock bootloaders but if you look at the source code of the Samsung SecSettings app there are two kind of logic's, one to enable the oem onlock option and one to actually use it. It checks a lot of ro properties. Also we might be able to disable platform verification and install a system app to just execute the oem unlock option.