FEATURES:
Flicker-free display in sRGB/DCI-P3 mode
NOTICE:
Due to the compatible issue with OnePlus original design,
the Night mode will not work,
and the brightness will flash for a instant after fingerprint unlock.
DOWNLOAD:
Google Drive
XDA:DevDB Information
ImageBreaker Kernel, Kernel for the OnePlus 6T
Contributors
Devries, osm0sis, Sultan, flar2
Source Code: https://github.com/DevriesL/Fajita_ImageBreaker
Kernel Special Features: Flicker-free
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-01-01
Created 2019-01-01
Last Updated 2019-01-09
Reserved
First..
Thanks for the kernel..
And happy New year..
But what is flicker free??...
Is this kernel, mod or what ? Please more info, thanks
marko94 said:
Is this kernel, mod or what ? Please more info, thanks
Click to expand...
Click to collapse
It's a kernel
Sent from my OnePlus 6T using XDA Labs
cultofluna said:
First..
Thanks for the kernel..
And happy New year..
But what is flicker free??...
Click to expand...
Click to collapse
You can refer to this post: https://forum.xda-developers.com/s7-edge/development/amoled-pwm-s7-edge-t3517739
dange niubi。
Devries said:
You can refer to this post: https://forum.xda-developers.com/s7-edge/development/amoled-pwm-s7-edge-t3517739
Click to expand...
Click to collapse
So you've increased the screen refresh rate?
Causical said:
So you've increased the screen refresh rate?
Click to expand...
Click to collapse
No, this is not related to refresh rate, it's chaning the metohd of adjust brightness from PWM duty ratio to direct current.
Is there a way to use this with a other kernel? Kernel-addon or so (Im not a expert - thats why im asking)?
Because OP of blue_spark Kernel , eng.stk, will not implement this in his kernel...
I went ahead and tested on my device. For those interested Night mode does turn on when you activate it manually, however it does not stay on once the screen is turned off. Not sure if this messes with the kernel but I'm leaving it off just in case. Also, this will overwrite Magisk so flash this then Magisk to maintain root.
No issues otherwise, thank you for letting us know about the PWM curve, I hadn't seen the information in post #6 before. Maybe you could throw that link in the OP for others to see? I'm testing it with cf.lumen and magisk at the moment to substitute for night mode and I'll let you all know if it is a suitable substitute. Thank you for sharing the kernel with us!
AlkaliV2 said:
I went ahead and tested on my device. For those interested Night mode does turn on when you activate it manually, however it does not stay on once the screen is turned off. Not sure if this messes with the kernel but I'm leaving it off just in case. Also, this will overwrite Magisk so flash this then Magisk to maintain root.
No issues otherwise, thank you for letting us know about the PWM curve, I hadn't seen the information in post #6 before. Maybe you could throw that link in the OP for others to see? I'm testing it with cf.lumen and magisk at the moment to substitute for night mode and I'll let you all know if it is a suitable substitute. Thank you for sharing the kernel with us!
Click to expand...
Click to collapse
Hello, thanks for your reply, because night mode uses same interface with my driver, so it will be overridden. The purpose for me to released this kernel is to share my flicker-free design, I hope it can be ported to other kernels and devices.
Devries said:
Hello, thanks for your reply, because night mode uses same interface with my driver, so it will be overridden. The purpose for me to released this kernel is to share my flicker-free design, I hope it can be ported to other kernels and devices.
Click to expand...
Click to collapse
Its already implemented on other kernels
cultofluna said:
Its already implemented on other kernels
Click to expand...
Click to collapse
Yes, it's already implemented on galaxy S7/S8, but the method on the S7/S8 is changing the display register, which is hard to port.
Devries said:
Yes, it's already implemented on galaxy S7/S8, but the method on the S7/S8 is changing the display register, which is hard to port.
Click to expand...
Click to collapse
Im not asking ...i Just confirm that the developer from smurf kernel has this implemented in his kernel (OP6/6T)
cultofluna said:
Im not asking ...i Just confirm that the developer from smurf kernel has this implemented in his kernel (OP6/6T)
Click to expand...
Click to collapse
Okay, I got it.
Devries said:
Okay, I got it.
Click to expand...
Click to collapse
pappschlumpf has implemented that when night mode is turned on flickerfree mods are disabled and viceversa.
This is not 100% working because under some color profiles it doesn't work because oos is not updating the night mode status.
I don't know if this helps you but this the commit:
https://github.com/pappschlumpf/op6/commit/cc523af123600d8bc0e0ae0449d42af8c3b0f955
Thanks for your work and thanks to pappschlumpf.
still cant support night mode ...
cantsupport
MarcoCount said:
pappschlumpf has implemented that when night mode is turned on flickerfree mods are disabled and viceversa.
This is not 100% working because under some color profiles it doesn't work because oos is not updating the night mode status.
I don't know if this helps you but this the commit:
https://github.com/pappschlumpf/op6/commit/cc523af123600d8bc0e0ae0449d42af8c3b0f955
Thanks for your work and thanks to pappschlumpf.
Click to expand...
Click to collapse
Well I wanna know, the flicker free kernel is the sole option for us not to use Low frequency PWM dimming in the low brightness.. A kernel may tweak the system and trick it with DC dimming instead of low Frequency PWM when brightness is low, but one thing emerges.. is this kernel is unofficial, it seems to discontinue at any time
So there is another solution out there, the OLED Saver in Play store... it prevents your phone reaches relatively low brightness which may trigger the Flicker caused by low frequency PWM dimming, but you sacrifice you eye exposing a brighter display in a relatively dark environment at night which is no good.
Finally,
Xiaomi Mi 9 and Meizu is said to work on this, very possibly, they will tweak their kernel, add a flipper switch in the ROM interface to always running DC dimming...
I guess only when the official kernel defaultly support always on DC dimming, then the custom ROMs of that model will truly have the same Feature
If the official kernel does support that always DC dimming options.. then the massive adoption of flickerfree AMOLED display can truly begin
By then, rest in piece, our old phones which can't receive an official flickerfree kernel (DC dimming kernel or high frequency PWM kernel)
For those old ones, we use the OLED Saver APP to prevent flicker and tolerate a brighter display at night
For those new phones..Pray that this flickerfree display official kernel will be happening this time and later on forever..
Then
There will be no more eye strain and fatigue due to the flicker???
Would love to see more development of this feature! I'm a medical technician in Ophthalmology, so I really want to protect my eyes after seeing what I've seen for so long.
Related
Q&A for [KERNEL]Forest-CM11 (V5 with OC CPU-GPU)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Any updates?
hello i am using your kernel now for some month and it was really nice. but since some months there is no progress here. are you working on it anymore? an update would be nice after over 3 months now. I would have really some "good" additions und suggestions for the kernel. Furthermore, philz touch has a new version out. would be really nice if you could update it to the latest version. the cwm integrated to the cm11 stock kernel now is newer as the base of your last released forest kernel. Also some here have deep sleep problems. Also it would be nice if you could look for sabermod/Linaro und archi optimizations or -03 optimization of the kernel in general. thanks for your great kernel!
would be nice if you could comment short here so that your fans know that you are working on this anymore or not
That's gotta get funny... Getting my popcorn ready! ?
Gesendet von meinem GT-N7000 mit Tapatalk
Noteguy said:
hello i am using your kernel now for some month and it was really nice. but since some months there is no progress here. are you working on it anymore? an update would be nice after over 3 months now. I would have really some "good" additions und suggestions for the kernel. Furthermore, philz touch has a new version out. would be really nice if you could update it to the latest version. the cwm integrated to the cm11 stock kernel now is newer as the base of your last released forest kernel. Also some here have deep sleep problems. Also it would be nice if you could look for sabermod/Linaro und archi optimizations or -03 optimization of the kernel in general. thanks for your great kernel!
would be nice if you could comment short here so that your fans know that you are working on this anymore or not
Click to expand...
Click to collapse
Too busy at work so not working on it for now. Maybe when there is CM stable or CM Lilopop....
For those who has deep sleep prob, should try disabling the sync. Use synker app to manually turn sync on/off.
Sent from my GT-N7000 using Tapatalk 2
i had a problem wiz cm11
Guys my battery drains very fast and i change it but the problem still happening
And after install this kernal v5 it better than the stock kernal but it use more than 25% of battery wthin less than on hour if i use wifi and just open whatsapp and browser .
If anyone had a solve for this problem ?
alimohammad412 said:
Guys my battery drains very fast and i change it but the problem still happening
And after install this kernal v5 it better than the stock kernal but it use more than 25% of battery wthin less than on hour if i use wifi and just open whatsapp and browser .
If anyone had a solve for this problem ?
Click to expand...
Click to collapse
Have u turned off autosync? It consumes much battery.
Sent from my GT-N7000 using Tapatalk 2
the drain of battery still
forest1971 said:
Have u turned off autosync? It consumes much battery.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
yes i turned it off and from setting/privacy/ i disabled Google play services and almost the app. from- wake up & Location & keep awake.
and i used the lowest Brightness
What exactly is the difference between the one with trim support and the one without . how do i choose which one to flash?
Thomas k philip said:
What exactly is the difference between the one with trim support and the one without . how do i choose which one to flash?
Click to expand...
Click to collapse
The one that has TRIM has TRIM. The one that doesn't have TRIM doesn't have TRIM. You can choose which one to flash by searching and reading what TRIM is, understanding the risks, and then deciding whether you're willing to take on the risk or not. Simple as that.
Am using v3 kernal for nightowl ..phones heating..but v1 is stable for me no heating and very snappy .thankyou for the kernal
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
alimohammad412 said:
Guys my battery drains very fast and i change it but the problem still happening
And after install this kernal v5 it better than the stock kernal but it use more than 25% of battery wthin less than on hour if i use wifi and just open whatsapp and browser .
If anyone had a solve for this problem ?
Click to expand...
Click to collapse
Use no frills, underclock to 1.2 GHz.. Then use ondemand Governor... Problem solved..
Dear Forest, am I correct that the forest kernel beta4 in comparison to r9 is missing lcd oc?
Is there now any advantages left over r9 since cpu oc got removed?
phoenX80 said:
Dear Forest, am I correct that the forest kernel beta4 in comparison to r9 is missing lcd oc?
Is there now any advantages left over r9 since cpu oc got removed?
Click to expand...
Click to collapse
If u cant read properly the op and cant flash and try for your self then dont go to xda asking nonsense questions.
Sent from my GT-N7000 using Tapatalk 2
Whats ur problem? This q+a or not?
I used v3ts until now on rr528. Since theres no b4 i switched to nightowl b4. And now Raw4 ist out that offers trim, gpu driver upd, oled oc and fpbug. I used to use forest because of cpu oc. Now that it is gone i wonder if there still is any supremacy of ur kernel that i dont see.
So what is ur problem with this question?
Why don't you just use whatever kernel you like and stop trolling?
Gesendet von meinem GT-N7000 mit Tapatalk
English is not my first language so i might not see the intentions of ur answers. I dont mean to troll. I want to continue using forests kernel and was wondering what the current state in comparison to raw it is in as these are the only custom kernels available. Since this is somehow an offence to someone dont mind anserwing this anymore. Its not an issue.
The link
The link for the downloading the kernel Forest-LP-Kernel_V4 from dropbox doesn't work. It suggests me to register on the dropbox.
I've downloaded it.
A Little Request and Questions
Greetings Forest! I am a new user of XDA, so forgive me if I made mistakes in presentation or in technical accuracy.
I am currently using your Kernel with CM11, and as far as stability goes, everything is working fine, although I find myself facing instabilities using the PegasusQ governor. Looking at the governer closely through ROM toolbox lead me to realise that there a hotplug settings existent for 4 core devices, while the Galaxy Note only has 2. Is this an issue? As far as it goes, I find myself waking up to a device showing the bootanimation continuously, but very slowly and choppy, forcing me to restart the phone. Luckily I wake up on time for work via instinct. Apart from that, the phone crashes except when using ondemand. Is there any explanation for these crashes?
Now for the requests. Since ondemand is not really the best, as I have seen more responsive and effective governors like SmartAssV2, which is personally my favourite. I've also read up on Interactive being a more responsive version of ondemand, I was wondering if you could include more governors for the kernel. Unless of course, governors are limited to CPU types which I hope not, then probably this post would've been written for nothing.
Thank you for taking the time to read this. Do understand that I am not in the field of programming, and I apologise if I made any mistakes. I look forward to your reply.
Zarhymn said:
Greetings Forest! I am a new user of XDA, so forgive me if I made mistakes in presentation or in technical accuracy.
I am currently using your Kernel with CM11, and as far as stability goes, everything is working fine, although I find myself facing instabilities using the PegasusQ governor. Looking at the governer closely through ROM toolbox lead me to realise that there a hotplug settings existent for 4 core devices, while the Galaxy Note only has 2. Is this an issue? As far as it goes, I find myself waking up to a device showing the bootanimation continuously, but very slowly and choppy, forcing me to restart the phone. Luckily I wake up on time for work via instinct. Apart from that, the phone crashes except when using ondemand. Is there any explanation for these crashes?
Now for the requests. Since ondemand is not really the best, as I have seen more responsive and effective governors like SmartAssV2, which is personally my favourite. I've also read up on Interactive being a more responsive version of ondemand, I was wondering if you could include more governors for the kernel. Unless of course, governors are limited to CPU types which I hope not, then probably this post would've been written for nothing.
Thank you for taking the time to read this. Do understand that I am not in the field of programming, and I apologise if I made any mistakes. I look forward to your reply.
Click to expand...
Click to collapse
Thank u for investigating the bug and helpful report:good:. I am also testing with stock cm kernel using pegasusq and also got a freeze. Now i can recalled similar problem faced by Slimsaber. On the other hand, my kernel run well on omni and omni based. So there seems to be some issues with some governors but only happen in CM and CM based rom. I will try to fix or remove/add some new governors when I can.
For now should use Ondemand!
Update
forest1971 said:
Thank u for investigating the bug and helpful report:good:. I am also testing with stock cm kernel using pegasusq and also got a freeze. Now i can recalled similar problem faced by Slimsaber. On the other hand, my kernel run well on omni and omni based. So there seems to be some issues with some governors but only happen in CM and CM based rom. I will try to fix or remove/add some new governors when I can.
For now should use Ondemand!
Click to expand...
Click to collapse
Well, today I woke up to a frozen boot animation screen, even on ondemand. Although ondemand lasted longer before crashing.
There might be much more issues with CM.
I will test out OmniRom later this afternoon.
Zarhymn said:
Well, today I woke up to a frozen boot animation screen, even on ondemand. Although ondemand lasted longer before crashing.
There might be much more issues with CM.
I will test out OmniRom later this afternoon.[/QUOTE
Hm. That present some new challenge. I am back to cm now to test it more. will also update the kernel soon to apply some changes in governors and other changes to improve stability.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
USE THE BETA FROM A RECENT POST IF YOU ARE USING CM13!
This is a kernel for Cyanogen Mod 13 and 12.1, which was originally based on the EvoMix kernel by Alx31, olivieer and SuperHanss. Due to Alx31's lack of time and in order to archive maximum compatibility and to benefit from latest updates, I decided to recreate a new kernel, forked from CM's very latest official one (thanks to qsnc). It has a focus on stability, performance, endurance and overclock-ability (roughly in that order).
It uses the original ramdisk of the installed kernel (thanks to osm0sis), for maximum compatibly in the long run and instant adaptability to most source changes. It should also work with other CM13/12.1 based ROMs, like crDroid and PAC.. Please don't report bugs to qsnc, if you are using this kernel!
Features (compared to CyanogenMod's official kernel):
build using the original Linaro 4.8.5 toolchain
CPU: over/under-clock 1728MHz-192 MHz possible
additional governors: abyssplugv2, alucard, dancedance, darkness, lionheart, nightmare, pegasusq, wheatley
Voltage Control (under-/over voltage)
GPU: over/under-clock 487MHz-27MHz + simple governor
additional file-systems: exFAT, NTFS
intelli-plug hot-plugger and power saver
restrict maximum screen off frequency
Sound Control 3.x (poweramp controls, loudness enhancements)
kernel mode NEON optimizations
optimized AES and SHA1 routines (faster encryption)
compressed by using LZ4 (faster boot)
fsync on/off support (turn of for higher disk performance, but increased risk of data-loss)
KSM support (Kernel Samepage Merging)
multirom compatibility (kexec-hardboot)
fast-charge support (not recommended and only works with dock, not with USB-charger!)
numerous small performance improvements
...
Performance: about 10% faster than original CM12.1-kernel with same settings, and some additional 20% speed by using maximum over-clocked frequencies (use at your own risk, every device is different!)
Configuration: Kernel Adiutor (https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor) or PerformanceControl 2.2.6 (http://forum.xda-developers.com/devdb/project/?id=600#downloads)
Install: just flash the attached zip with TWRP (http://forum.xda-developers.com/xpe...very-twrp-2-8-7-0-pollux-polluxwindy-t3187811) or CWM
Uninstall: re-flash the complete ROM (just re-flashing the original kernel is not enough!)
Changelog:
2016-04-08:
removed MSM GPU powerscale (more stable and governor selectable)
removed intelli-plug (outdated and obsolete)
fsync no longer enabled by default
synced with latest official CM13 source (many fixes)
2015-12-21:
fast-charge support (not recommended and only works with dock, not with USB-charger!)
synced with latest official CM13 source
2015-11-28:
initial release
IF INSTALLATION FAILS: If the kernel installation is not working (i.e. installation takes less than 5 seconds and you don't see the new boot-logo), re-flash latest ROM, reboot into recovery and try to install the kernel again!
Install a custom recovery first! The simple CyanogenMod Recovery, which comes with most ROMs, is pretty useless anyway..
XDA:DevDB Information
Black Kernel for CyanogenMod-based ROMs, Kernel for the Sony Xperia Tablet Z
Contributors
BlackAfghan, qsnc, Alx31, olivieer and SuperHanss
Source Code: https://github.com/Gabriel85/android_kernel_sony_apq8064
USE THE BETA FROM A RECENT POST IF YOU ARE USING CM13!
Downloaded, installed, checked.
Screen rotation is working again.
Thanks a lot for maintaining.
Thx for the update. One question; couldn't see fast charge option - available?
Sent from my Xperia Tablet Z Wi-Fi using Tapatalk
Awesome, thanks man for the update! This tablet is still chugging away very strong for its age and thanks to you for adding some more stream to it!
Great scott!
Essentrix said:
Thx for the update. One question; couldn't see fast charge option - available?
Click to expand...
Click to collapse
I don't think that fast-charge ever worked on the Tablet.. or did it?
cantenna said:
Awesome, thanks man for the update! This tablet is still chugging away very strong for its age and thanks to you for adding some more stream to it!
Click to expand...
Click to collapse
You’re welcome! :good:
BlackAfghan said:
I don't think that fast-charge ever worked on the Tablet.. or did it?
Hi mate yes evomix kernel has the fast charge. Gone back to it for the time being - it's one feature that makes a huge difference to charging time. Look forward to seeing you add the feature when you get the chance. Cheers
Sent from my Xperia Tablet Z Wi-Fi using Tapatalk
Click to expand...
Click to collapse
Essentrix said:
BlackAfghan said:
I don't think that fast-charge ever worked on the Tablet.. or did it?
Hi mate yes evomix kernel has the fast charge. Gone back to it for the time being - it's one feature that makes a huge difference to charging time. Look forward to seeing you add the feature when you get the chance. Cheers
Sent from my Xperia Tablet Z Wi-Fi using Tapatalk
Click to expand...
Click to collapse
Are you really sure that it actually charges faster? I think the maximum it uses are 1500mA, and that is not even enough for the tablet to run with maximum brightness without discharging the battery! I doubt fast-charging makes any difference..
Click to expand...
Click to collapse
BlackAfghan said:
Essentrix said:
Are you really sure that it actually charges faster? I think the maximum it uses are 1500mA, and that is not even enough for the tablet to run with maximum brightness without discharging the battery! I doubt fast-charging makes any difference..
Click to expand...
Click to collapse
Seems to make a decent difference with mine. Previously the charge took forever - using crdroid ROM - now quite fast. Might time the next charge.
Sent from my Xperia Tablet Z Wi-Fi using Tapatalk
Click to expand...
Click to collapse
Tablet Z doesn't have the fast charge function, so I suppose it's just your feelings or the tablet not fully discharged. To me no difference at all.
BlackAfghan said:
Are you really sure that it actually charges faster? I think the maximum it uses are 1500mA, and that is not even enough for the tablet to run with maximum brightness without discharging the battery! I doubt fast-charging makes any difference..
Click to expand...
Click to collapse
Under normal charge via microusb port, maximum current is 1,5A, even using 2A charger. But when using dock contacts and ipad 2,4A adapter, it easily exceeds 2A, which significantly reduces charging time.
Essentrix said:
BlackAfghan said:
Seems to make a decent difference with mine. Previously the charge took forever - using crdroid ROM - now quite fast. Might time the next charge.
Sent from my Xperia Tablet Z Wi-Fi using Tapatalk
Click to expand...
Click to collapse
Tested charging and both this and evo about the same. Both are faster than stock kernel. I did change the charger and could also be to do with flashing non stock kernels?
Sent from my Xperia Tablet Z Wi-Fi using Tapatalk
Click to expand...
Click to collapse
BlackAfghan Thanks for listening to my post and adding up 400MHz in GPU. But I can't set the GPU governor now, I don't see that option. I was running CM 12.1 latest nightly on my Pollux.
IlD4nX said:
Tablet Z doesn't have the fast charge function, so I suppose it's just your feelings or the tablet not fully discharged. To me no difference at all.
Click to expand...
Click to collapse
I agree..
Rootk1t said:
Under normal charge via microusb port, maximum current is 1,5A, even using 2A charger. But when using dock contacts and ipad 2,4A adapter, it easily exceeds 2A, which significantly reduces charging time.
Click to expand...
Click to collapse
Makes also sense..
Essentrix said:
Essentrix said:
Tested charging and both this and evo about the same. Both are faster than stock kernel. I did change the charger and could also be to do with flashing non stock kernels?
Sent from my Xperia Tablet Z Wi-Fi using Tapatalk
Click to expand...
Click to collapse
Absolutely..
I'll add fast-charge to the next release!
Alok Bajaj said:
BlackAfghan Thanks for listening to my post and adding up 400MHz in GPU. But I can't set the GPU governor now, I don't see that option. I was running CM 12.1 latest nightly on my Pollux.
Click to expand...
Click to collapse
I thought that is related to KernelAdiutor? Nevertheless, it uses the effective simple govenor by default! Also I reduced to minimum frequency significantly, in order to save power.
Click to expand...
Click to collapse
Hello, I have just flashed this kernel on my Z Tablet with crDroid rom, and tried it with Antutu.
I am getting a 30k score with this, and 32k with crDroid rom's kernel. Can i do something to improve it?
Marco Odradek said:
Hello, I have just flashed this kernel on my Z Tablet with crDroid rom, and tried it with Antutu.
I am getting a 30k score with this, and 32k with crDroid rom's kernel. Can i do something to improve it?
Click to expand...
Click to collapse
Repeat it at least 5 times! But I never got more than 27k..
crDroid allows over-clocking, too?
BlackAfghan said:
Repeat it at least 5 times! But I never got more than 27k..
crDroid allows over-clocking, too?
Click to expand...
Click to collapse
I did it 3 times.
I didn't check if crDroid overclock by default.
Just tried with 1.7 ghz and got 33k
New version is out... Happy holidays! :angel:
fast-charge support (not recommended and only works with dock, not with USB-charger!)
synced with latest official CM13 source
Click to expand...
Click to collapse
BlackAfghan said:
New version is out... Happy holidays! :angel:
Click to expand...
Click to collapse
Still working with CM12.1 ROMS?
There is no newer Rom since 12.1 ?
So i think answer must be: yes
>>>>>> Kernel for > CM-14.0 < (NOUGAT) <<<<<<
THIS IS MY KERNEL FOR DAILY USE
I AM NOT RESPONSIBLE FOR DEFECTS IN YOUR CELLPHONE
Changelog:
VERSION 1.4 (03/11/2016)
- CLEAN, BYE DEAD CODE
- MORE GOVERNORS AND ONE PRESIDENT )
- ZZMOVE RESUMED, DARKNESS, BIOSHOCK, ELEMENTALX, IMPULSE, INTELLIACTIVE, IRONACTIVE AND ALUCARD (OUR GRANDFATHER CONSERVATIVE DEFAULT)
- MORE FIXES FOR CORTEX-A53
- ZSWAP 50% NOW
VERSION 1.3 (31/10/2016)
- BYE BOOT "BLUE BUG" AND LIVE DISPLAY REMAINS INTACT.
VERSION 1.2 (30/10/2016)
- BIG.LITTLE IMPROVEMENTS
- CP64
- TCP: BIC,CUBIC,WESTWOOD,HTCP,HSTCP,HYBLA,VEGAS,SCALABLE,LP,VENO,YEAH,ILLINOIS
- CORRECTIONS
ATUNTU: CONSEVATIVE, DEFAULT SETTINGS, NO OVERCLOCK OR HACK (CM14)
VERSION 1.1
- INTERACTIVE GOV CORRECT NOW AND DEFAULT
- OPENMP
- HOTPLUG QUALCOMM ADDED
- FINE ADJUSTMENTS IN PERFORMANCE
- SWEEP2WAKE and DOUBLETAP2WAKE
- ZSWAP 30% POOL DEFAULT
VERSION 1.0
- BASED IN CYANOGENMOD KENZO SOURCE KERNEL
- ZSWAP LZ4
- LINUX 3.10.104
- BETTER BALANCE BETWEEN PERFORMANCE AND BATTERY SAVING
- CONSERVATIVE GOV DEFAULT
- KERNEL EXTREMELY CUT FOR DAILY USE
- CAM ADJUSTS
- NO OVERCLOCK OR SCRIPTS
- MORE ADJUSTS IN SCREEN, SOUND...
- THERMAL OPTIONS
- HIGH COMPATIBILITY WITH KERNEL ADIUTOR
- 512KB READAHEAD
- FIOPS SCHEDULER DEFAULT
- COMPILED WITH NONO GCC 64 EX 6 . 2 . 0 (MINE PURE AARCH64 GCC)
DOWNLOAD (INSTALL SIMPLE IN TWRP OR CWM):
Mod edit: Links removed
If you like my work, donate to me :fingers-crossed:
THANKS FOR:
ALL DEVS :good:
ALL XDA MEMBERS AND ADMINS
CYANOGENMOD TEAM (FOREVER)
IS MY FIRST TOPIC IN XDA, THANK YOU FOR PATIENCE :fingers-crossed:
SOURCE
Nice...
Y u posted here
It's not a right place
Post in Development section...
People get to know less here
Sent from my Redmi Note 3 using XDA-Developers mobile app
Moved from Themes/Apps
Mike
Cool . Trying asap
Sent from my Redmi Note 3 using Tapatalk
Does it support goodix and latest camera sensors?
update your source link with all changes commited.(ever heard of gpl?)
Ello, nice kernel name.
Support for wake gestures?
zilan said:
Support for wake gestures?
Click to expand...
Click to collapse
Hello bro, Sweep2Wake and DoubleTap2Wake is supported
neonkat said:
update your source link with all changes commited.(ever heard of gpl?)
Click to expand...
Click to collapse
Hi my smart friend, I'm the developer more than 20 years, do not know what is GPL, it was good you comment on that now met the first time the GPL. I'll do it later, calm. Do not get so flustered with this, you will be able to analyze it later.
Thanks!
More kernel for kenzo, more option for us...glad to see this...will try it asap..
Anyway, thanks for this kernel
prmonteiro said:
Hi my smart friend, I'm the developer more than 20 years, do not know what is GPL, it was good you comment on that now met the first time the GPL. I'll do it later, calm. Do not get so flustered with this, you will be able to analyze it later.
Thanks!
Click to expand...
Click to collapse
meh,i ain't a smart kid,just tried to clear up some things(sarcasm ftw?).
well sorry if that hurts your feelings.
Does goodix fp works on this?
Testing :
Quite smooth , no hotplugging and no real gain compared to AGNi 2.5
Fp working great (FPC)
ROM: Tesla 3.0
Battery life: wait & see
rhyme4u12 said:
Does goodix fp works on this?
Click to expand...
Click to collapse
It is to work perfectly with goodix.
aaz03 said:
Testing :
Quite smooth , no hotplugging and no real gain compared to AGNi 2.5
Fp working great (FPC)
ROM: Tesla 3.0
Battery life: wait & see
Click to expand...
Click to collapse
Thanks for the feedback!
Just flashed this kernel, looks pretty smooth.
cam works, videos don't work with Google cam.
Got no deep sleep. Same problem as with agni.
I'm thinking that it might be caused by the cam.
I'm on aicp 12,with stock kernel my cam doesn't work but I have perfect deep sleep. On kernels where my cam works I don't get any deep sleep anymore. Other assumption would be wifi, even tho it works perfect.
Please let me know what infos you need?
tschulieh said:
Just flashed this kernel, looks pretty smooth.
cam works, videos don't work with Google cam.
Got no deep sleep. Same problem as with agni.
I'm thinking that it might be caused by the cam.
I'm on aicp 12,with stock kernel my cam doesn't work but I have perfect deep sleep. On kernels where my cam works I don't get any deep sleep anymore. Other assumption would be wifi, even tho it works perfect.
Please let me know what infos you need?
Click to expand...
Click to collapse
Nice! Thanks for the feedback!
Also i'm pretty curious about this NONO GCC as i never heard of it before , any optimisations proper to this toolchain made into the kernel?
looks good
cant wait to try it!!
im so excited about N!!!
thanks @prmonteiro for developing this
Keep up the good work!!
MoKee Open Source is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Forum:http://bbs.mfunz.com
Guide:http://bbs.mfunz.com/thread-754544-1-1.html
Statistics:http://stats.mokeedev.com
Review:http://review.mfunz.com
Download:http://download.mokeedev.com
Github:https://github.com/MoKee
Bug Tracker:http://issues.mokeedev.com/
Credits:
Google, Qualcomm, Linux Kernel Organization, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,
CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser, lineageOS, TeamWin,
Smartisan Digital Co, Substratum Development Team, The Open GApps Team.
OFFICIAL WEBSITE
I'm not the Maintainer for this ROM. I do just provide the Thread for XDA. Sharing is caring!
DOWNLOAD: AXON 7
Oh goodness, I knew my Flashaholic sense's were tingling.
On a whim, I decided to install this on my U. The progress bar in TWRP isn't indicating an install, so don't panic. The install will eventually complete. It does seem to take a bit longer than usual. This appears to be a Lineage base and not AOSP. Magisk 14.0 does not pass the SafetyNet check for some reason. No big deal for me. I just thought I'd mention it. Aegis looks interesting. It seems to be a Greenify on Steroids app exclusive to Mokee. It is Substratum capable.
Much of it is standard fare with a few annoyances. I couldn't find a way to disable the network speed indicator in the status bar. Freezing the Mokee Center app disables settings altogether. I thought I'd at least disable wifi and data but like a few other apps, the switches are replaced with the colorservice switches. I don't like this and decide to ditch the rom.
It ran well and seemed stable. There were no hiccups during install and setup. Not much else I can say as it was a short lived install.
Cablespider said:
On a whim, I decided to install this on my U. The progress bar in TWRP isn't indicating an install, so don't panic. The install will eventually complete. It does seem to take a bit longer than usual. This appears to be a Lineage base and not AOSP. Magisk 14.0 does not pass the SafetyNet check for some reason. No big deal for me. I just thought I'd mention it. Aegis looks interesting. It seems to be a Greenify on Steroids app exclusive to Mokee. It is Substratum capable.
Much of it is standard fare with a few annoyances. I couldn't find a way to disable the network speed indicator in the status bar. Freezing the Mokee Center app disables settings altogether. I thought I'd at least disable wifi and data but like a few other apps, the switches are replaced with the colorservice switches. I don't like this and decide to ditch the rom.
It ran well and seemed stable. There were no hiccups during install and setup. Not much else I can say as it was a short lived install.
Click to expand...
Click to collapse
I disabled the ongoing and incoming network indicator in status bar in settings
Is there a guide to flashing this or prerequisites?
emilio242 said:
Is there a guide to flashing this or prerequisites?
Click to expand...
Click to collapse
It's a fairly basic LOS-based ROM. No particular requirements needed as far as I know. Should be an easy flash.
Haven't used MoKee regularly since Lollipop (it was great on my G3) so not much experience with it since.
Maybe the slow/metered downloads kept me away. ?
ZTE Axon 7 A2017U, VertexOS Carbide-v3.6 ROM, Tapatalk 4.9.5
marcdw said:
Maybe the slow/metered downloads kept me away.
Click to expand...
Click to collapse
I ran Mokee on my previous phone (ZUK Z2 Plus) as a daily driver for about a month and liked it, but the restrictions on download speeds for ROM updates and 60-second waiting time from their website really pissed me off and prompted me to switch to another ROM. I know they're trying to get people to donate but c'mon, we don't need our download speeds crippled just to encourage us into making a donation.
A few months back I actually heard from someone on the ZUKFans.eu forum who made a donation towards the project, but didn't get his download speeds derestricted and attempts to contact the team were completely ignored.
P650SE said:
I ran Mokee on my previous phone (ZUK Z2 Plus) as a daily driver for about a month and liked it, but the restrictions on download speeds for ROM updates and 60-second waiting time from their website really pissed me off and prompted me to switch to another ROM. I know they're trying to get people to donate but c'mon, we don't need our download speeds crippled just to encourage us into making a donation.
A few months back I actually heard from someone on the ZUKFans.eu forum who made a donation towards the project, but didn't get his download speeds derestricted and attempts to contact the team were completely ignored.
Click to expand...
Click to collapse
Wait a minute, if that why my downloads aren't as fast as they were before, then i'm jumping to a new ROM immediately. That does sound quite ridiculous.
After reading all this... Is MoKee still the better LinageOS lol
I'm over feeded from Linage/CM based ROMs and MoKee is the only ROM i would use again from this Edge (Was running last Night). The best is still AOSP based! AOSPA, AOSP Extended and so so... Clean, no Lags, and Features placed in without screwing up the Settings Order... But anyways, i like to share MoKee since it's almost unknown (Still) and always delivering Nightlies (There aren't that much ROMs here which are providing such a Support). So, love it or hate it
Cablespider said:
On a whim, I decided to install this on my U. The progress bar in TWRP isn't indicating an install, so don't panic. The install will eventually complete. It does seem to take a bit longer than usual. This appears to be a Lineage base and not AOSP. Magisk 14.0 does not pass the SafetyNet check for some reason. No big deal for me. I just thought I'd mention it. Aegis looks interesting. It seems to be a Greenify on Steroids app exclusive to Mokee. It is Substratum capable.
Much of it is standard fare with a few annoyances. I couldn't find a way to disable the network speed indicator in the status bar. Freezing the Mokee Center app disables settings altogether. I thought I'd at least disable wifi and data but like a few other apps, the switches are replaced with the colorservice switches. I don't like this and decide to ditch the rom.
It ran well and seemed stable. There were no hiccups during install and setup. Not much else I can say as it was a short lived install.
Click to expand...
Click to collapse
I have the same problems. I think that the safetynet problem is for xposed. I uninstall xposed but the problem still there are. I think that xposed should not be preinstalled. Other problem that the audio on calls is too high....I'm still trying
Regards
Enviado desde mi ZTE A2017U mediante Tapatalk
I must say, this ROM with the Hellsgate kernel is pretty damn impressive.
SOT: 6hrs, 34m and 24s
Computed power use: 814 mAh
Time off charger: 16hrs(changed at the last moment before dying)
Kernel Config: Alucard gov. With maple as I/o Scheduler, Intellthermal, CPU Boost enabled with 652 mhz of touch-input on cores #1 and 3.
Battery Profile: Balanced
Not too bad at all.
troy5890 said:
I must say, this ROM with the Hellsgate kernel is pretty damn impressive.
SOT: 6hrs, 34m and 24s
Computed power use: 814 mAh
Time off charger: 16hrs(changed at the last moment before dying)
Kernel Config: Alucard gov. With maple as I/o Scheduler, Intellthermal, CPU Boost enabled with 652 mhz of touch-input on cores #1 and 3.
Battery Profile: Balanced
Not too bad at all.
Click to expand...
Click to collapse
Tried it like that and it's amazing
emilio242 said:
Tried it like that and it's amazing
Click to expand...
Click to collapse
I'm very glad, tomorrow I'm going to try with the Lionfish give and see what type of battery life I get.
Miustone said:
MoKee Open Source is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
Click to expand...
Click to collapse
Thanks for this.
I'm willing to give it a shot.
Gonna report here for anything!
Need to flash stock modem or universal bootloader?
Reiyer said:
Need to flash stock modem or universal bootloader?
Click to expand...
Click to collapse
On the U model I flashed without anything else. I do believe I'm on b19 (don't remember ever flashing universal bootloader).
ZTE Axon 7 A2017U, MoKee Open Source ROM, Light Patch v1.5, Tapatalk 4.9.5
troy5890 said:
I must say, this ROM with the Hellsgate kernel is pretty damn impressive.
SOT: 6hrs, 34m and 24s
Computed power use: 814 mAh
Time off charger: 16hrs(changed at the last moment before dying)
Kernel Config: Alucard gov. With maple as I/o Scheduler, Intellthermal, CPU Boost enabled with 652 mhz of touch-input on cores #1 and 3.
Battery Profile: Balanced
Not too bad at all.
Click to expand...
Click to collapse
I've just charged my device up to 90% and switched to these settings, so it'll be interesting to see what the battery life and performance is like in comparison with stock. :fingers-crossed: My millage might be slightly less because I have the 3,140mAh version of the Axon 7 rather than the 3,250mAh variant.
P650SE said:
I've just charged my device up to 90% and switched to these settings, so it'll be interesting to see what the battery life and performance is like in comparison with stock. :fingers-crossed: My millage might be slightly less because I have the 3,140mAh version of the Axon 7 rather than the 3,250mAh variant.
Click to expand...
Click to collapse
Great! Let us know how your battery life turns out. Also, don't worry, I have the 3140 mah capacity as well, but a little tweaking can get you up to that 3250 mah battery status.
troy5890 said:
Great! Let us know how your battery life turns out. Also, don't worry, I have the 3140 mah capacity as well, but a little tweaking can get you up to that 3250 mah battery status.
Click to expand...
Click to collapse
Oh, well that's great to hear you also have the 3,140mAh capacity and are getting such decent battery life! I was slightly disappointed when I received my Axon 7 because it quite clearly said 3,250mAh on the website listing, but in all the battery apps i've used it states 3,100mAh which presumably means it's the 3,140mAh one. It came from AliExpress in China. I also thought I was getting UFS storage but it turned out to be eMMC, although to be fair it didn't mention this in the listing unlike the battery capacity. How did you find the Lionfish governor?
P650SE said:
Oh, well that's great to hear you also have the 3,140mAh capacity and are getting such decent battery life! I was slightly disappointed when I received my Axon 7 because it quite clearly said 3,250mAh on the website listing, but in all the battery apps i've used it states 3,100mAh which presumably means it's the 3,140mAh one. It came from AliExpress in China. I also thought I was getting UFS storage but it turned out to be eMMC, although to be fair it didn't mention this in the listing unlike the battery capacity. How did you find the Lionfish governor?
Click to expand...
Click to collapse
Yeah wish ZTE did something about that. I forgot to tell you that i flashed Hellsgate kernel with the ROM to get more govenors and tweaking. The kernel that came with it is pretty battery friendly as well. Every 5 to 6 minutes with the included kernel dropped to 1%.
This is a home of White Wolf Kernel for OneUI and Los/AOSP based roms.
Would like to thank to all devs that work has been used to create this kernel.
Al Credits belong to devs listed below
@farovitus - ELS
@AndreiLux
@Lord Boeffla
@franciscofranco
@ Despair Factor
@ak
@flar2
@arter97
@TheCrazyLex
@Sultanxda
@eng.stk
@osm0sis
@neobuddy89
@Tkkg1994
@frap129
@jcadduono
@yank-lu.555
@dorimanx
@acuicultor
@Alucard24
@ZeroInfinity
@morogoku
@nathanchance
@mostafaz
@joshuous
@faux123
@djb77
@Eamo5
@remilia15
@jesec
@synt4x93
@DEVILOPS 007
@abtekk
@osm0sis - AnyKernel
and all others devs that make our lives easier.
Special thanx for @urgali , @Sungfive and @Duncan1982 .
@Cybertron™ for thread and signature images.
@Saber for his superb thread with all detailed kernel stuff.
Short Feature list:
Always based on latest Linux Stable
Governors:
Schedutil, ShedutiliX
Custom Frequencies:
Gpu - 598MHz
Additional drivers:
- Power Efficient Workqueues
- apk launch and touch boost - from Sultanxda
- Wake Gestures from flar2
Flashing instructions
1. Flash in recovery no black magic
WARNING
Always flash on stock kernel.
Compatibility list:
Kernels have been tested with ROMs below:
- official Ultimate Pie ROM all credits to @rifek4
- official TeamExyKings LightROM all credits to @yash92duster.
- LOS Kernel have been tested with unofficial LOS 17
Telegram Support Group
https://t.me/joinchat/DNkhGFMc-o5FP9qSwz-4og
Downloads:
https://mega.nz/folder/IkdUVQ5D#9mgIsnTS6GnBEAHZSx7QAA
TWRP With f2fs support
https://www.androidfilehost.com/?w=files&flid=294117
Kernel Source
https://github.com/yarpiin/White-Wolf-Uni-LOS
https://github.com/yarpiin/White-Wolf-Uni-OneUI
Twrp Source
https://github.com/yarpiin/android_device_samsung
https://github.com/yarpiin/android_kernel_samsung_universal9810
If You like my work - hit thanx button or buy me a beer
https://www.paypal.me/yarpiin
XDA:DevDB Information
White Wolf Kernel, Kernel for the Samsung Galaxy S9
Contributors
yarpiin
Source Code: https://github.com/yarpiin/White-Wolf-SGS9-TW
Kernel Special Features:
Version Information
Status: Testing
Created 2018-11-13
Last Updated 2020-11-11
Changelog:
OneUI Based kernels
https://github.com/yarpiin/White-Wolf-Uni-OneUI/blob/master/changelog.txt
LOS 17
https://github.com/yarpiin/White-Wolf-Uni-LOS/blob/master/changelog.txt
Set of rules for flashaholics by @flar2 .
Great guide how to avoid problems when flashing .
https://elementalx.org/ten-rules-for-flashaholics/
Please read and follow.
TWRP Usage Guide
Make sure your kernel support f2fs file system
1.Flash patched TWRP by yarpiin
2.MAKE BACKUP( Problems with restoring backups are solved now, but just in case)
3.Go to Wipe > Advanced wipe select Data and Change File System to F2FS, you can do the same to Cache ( Not recommended )
4.Restore backup of your data
5.Reboot & enjoy
Troubleshoot
It might happen that package extract error will occure when flashing the rom (or any updater-script based zip) . In this case just restart instalator and all should be fine.
Follow these steps or you will loose your data.
reserved
Glad to see you here!
ExtentedByte said:
Glad to see you here!
Click to expand...
Click to collapse
Had massive problems with rhread opening . Xda became so slow and tricky.
Sent from my Galaxy S9+ using XDA Labs
yarpiin said:
Had massive problems with rhread opening . Xda became so slow and tricky.
Sent from my Galaxy S9+ using XDA Labs
Click to expand...
Click to collapse
Been there lol. Great to see more development for the device. Welcome and congratulations on release
rifek4 said:
Wow, great to see new kernel! Keep it up, gonna follow you and try it!
Clean duplicaded threads in S9+ Review and S9+ ROMs&kernels section. Just keep one thread here so in S9 / S9+ Cross section where are all kernels and ROMs
Yeah, it's since years like that... You must be used to that Now you will be know Always after click "send thread" go to check section where you opening thread because your page seems to be stuck while adding but in real the thread is opened there and added correctly...
P.S.
Polacy przejmują S9 sekcje xD
Click to expand...
Click to collapse
Duplicated threads are @Xda Fault . Didnt had a clue that they have been created as I had bad gateway and xda server couldnt phrase request messages qhen created . It has been reported to xda .
I will get them removed
Btw im not newbie at xda
Sent from my Galaxy S9+ using XDA Labs
wow didnt had idea that so many multiple threads has been created have requested removal
Sent from my Galaxy S9+ using XDA Labs
Deleted
Great performance!
rifek4 said:
I didn't tell that you're newbie I'm just letting you know that adding threads working like that since 1 year or something... I released S7 ROM then and was same like is now, nothing changed since then
Click to expand...
Click to collapse
no offence m8 :laugh: never had any problems with any of my 4 threads
Sent from my Galaxy S9+ using XDA Labs
Thanks! Using it right now, keep it up.
rifek4 said:
So you're really lucky bcz 99% users has it... And you also had it if you made XXX dupliaced themes
Click to expand...
Click to collapse
Looks like last of my threads been started 2 years ago , but never faced any issue with it.
Ohh well **** happens
Sent from my Galaxy S9+ using XDA Labs
Better battery life with this kernel. Standby drain is much better, even with gaming with pubg with high fps
Hi there, just had an opportunity to delve through the source. Very impressive work and well done, without a doubt this will influence future releases of Endurance! Would also like to quickly address something I noted, as my kernel was heavily influenced by Andrei's work.
Your commit utilising Andrei's EAS values are outdated and following the BRE5 source drop have since been updated in the exynos9810.dtsi.
Have a good day, and thanks for giving me some more stuff to play with for future releases!
Eamo5 said:
Hi there, just had an opportunity to delve through the source. Very impressive work and well done, without a doubt this will influence future releases of Endurance! Would also like to quickly address something I noted, as my kernel was heavily influenced by Andrei's work.
Your commit utilising Andrei's EAS values are outdated and following the BRE5 source drop have since been updated in the exynos9810.dtsi.
Have a good day, and thanks for giving me some more stuff to play with for future releases!
Click to expand...
Click to collapse
Thank you for that . Will revert it then. Yea shame that Andrei stop working on it . Have read his article. This is my first exynos device so it was a nice point of start.
One thing that i noticed withs flars OC that frequencies are going to max value 2.7MHz just at ceratin ocxasions and i think that not all cores at the same time . I decided to use that commit to find out how it does work. When disable Exynos hotplug and OC big xluster to anything above 2324MHz device crashes under the load . So to make it bir snappier i jave kept Andreis max frequencies but also raise min as 850Mhz is the highest one with same voltage as the stock lowest.
Sent from my Galaxy S9+ using XDA Labs
yarpiin said:
Thank you for that . Will revert it then. Yea shame that Andrei stop working on it . Have read his article. This is my first exynos device so it was a nice point of start.
One thing that i noticed withs flars OC that frequencies are going to max value 2.7MHz just at ceratin ocxasions and i think that not all cores at the same time . I decided to use that commit to find out how it does work. When disable Exynos hotplug and OC big xluster to anything above 2324MHz device crashes under the load . So to make it bir snappier i jave kept Andreis max frequencies but also raise min as 850Mhz is the highest one with same voltage as the stock lowest.
Click to expand...
Click to collapse
I agree, truly great work accomplished by Andrei. it is a shame, albeit his merging in of the 16ms PELT was IMO the best thing to happen to this device yet.
Yep that's the nature of hotplugging. I eventually decided to maintain hotplugging and the max quad freq of 1794MHz to conserve battery. I've found hotplugging just to give insanely good Geekbench scores and not much more, likely due to the very very rare usage of those frequencies in realistic workloads. No noticeable regression in performance using 1794MHz quad in regards to user experience when using 16ms PELT.
I use 2002MHz on my OC build as I find it the best balance of performance and battery for the device. 2314 is too much of a battery regression with quad frequencies for me to justify the performance boost.
Eamo5 said:
I agree, truly great work accomplished by Andrei. it is a shame, albeit his merging in of the 16ms PELT was IMO the best thing to happen to this device yet.
Yep that's the nature of hotplugging. I eventually decided to maintain hotplugging and the max quad freq of 1794MHz to conserve battery. I've found hotplugging just to give insanely good Geekbench scores and not much more, likely due to the very very rare usage of those frequencies in realistic workloads. No noticeable regression in performance using 1794MHz quad in regards to user experience when using 16ms PELT.
I use 2002MHz on my OC build as I find it the best balance of performance and battery for the device. 2314 is too much of a battery regression with quad frequencies for me to justify the performance boost.
Click to expand...
Click to collapse
I will agree but after weeks of testing I havent found 2314MHz has a massive impact in the battery
Nature of hotplug in exynos is totaly different than snapdragon and one that I jsed to . Trus hotplugging is actualy offlining not needed cpus in my meaning.
Sent from my Galaxy S9+ using XDA Labs