Develop Bugs

Strange UnderClocking Discovery !! ;)

I am on WIUI 1.12.16 ICS build.
Yesterday, dont know what struck my mind, and i just happend to UnderClock my defy. I underclocked it to 600 Mhz, and to my surprise, i didnt find any lag.
The phone is running smooth as earlier (as at 1.1 Ghz).
Profit : Am saving considerable Juice
No effect on homescreen scrolling, multitasking, opening of app drawer, etc.
Infact all my games (Adrenaline HD, GTA III, BattleHomerun 3D, etc) are running the same way they did when phone was OverClocked
Am using the following Clock Frequencies & find it stable. Will test it even furthur
300-16
450- 28
600-38
Am pretty happy with the present speed as there is hardly and sluggishness or lag in my phone.
Give it a try and Share your experience here.
Trust me its worth giving a shot

Nobody tried it yet ??
Sent from my MB525 using XDA App

Have you doubled checked the settings in bootmenu?
Or just the app setvels?
I find at 800 its slower to open apps.
Sent from my Xoom using xda premium

Hell, I find 1000MHz too laggy nowadays, i keep it at 1100-62. Increasing vsel3 also helped maintain stability under heavier loads.

my vsel
im on CM7 RC
300 / 20
500 / 38
800 / 45
im running normally no lag prety god battery life.
just start to undervolt and im on those values for now
but wanna try lower values
just wanna know if lower values may do something to the phone.

Yea keep on going lower...
There is hardly any lag in my ROM and its pretty stable.
For those who find 1Ghz slow, blame ur build
At the end of the day, juice really does matters

question
Sidz4u said:
I am on WIUI 1.12.16 ICS build.
Yesterday, dont know what struck my mind, and i just happend to UnderClock my defy. I underclocked it to 600 Mhz, and to my surprise, i didnt find any lag.
The phone is running smooth as earlier (as at 1.1 Ghz).
Profit : Am saving considerable Juice
No effect on homescreen scrolling, multitasking, opening of app drawer, etc.
Infact all my games (Adrenaline HD, GTA III, BattleHomerun 3D, etc) are running the same way they did when phone was OverClocked
Am using the following Clock Frequencies & find it stable. Will test it even furthur
300-16
450- 28
600-38
Am pretty happy with the present speed as there is hardly and sluggishness or lag in my phone.
Give it a try and Share your experience here.
Trust me its worth giving a shot
Click to expand...
Click to collapse
how much juice u think u save?
how much your battery last with cpu oveclocked and how much now ?

Im on CM7.2 12.01.02 with these settings
300/20
800/45
1250/65
ondemand gov
up load 85
Stepping 50000
and i get 2 days of usage with wireless always connected and synk on and twitdeck updates set at 1 hour, and i think you cant downclock under 800 if u set vsel3 like that it doesent consider it and it loads the default ( on CM is1000,i dont know on miui wich is it)
Sent from my MoTo.MB525 with XDApp.

saneToMore said:
how much juice u think u save?
how much your battery last with cpu oveclocked and how much now ?
Click to expand...
Click to collapse
I unplugged my charger today morning with battery full.
>Played Videos for about an hour with full brightness (Moboplayer)
>Listened Music for more than two hours via earphones.
>Browsed the net for about half an hour. (2G)
>My GPRS was connected all the time and Nimbuzz was running in background.
After all this i have 68% battery left
I think thats some performance

kHron0S said:
Im on CM7.2 12.01.02 with these settings
300/20
800/45
1250/65
ondemand gov
up load 85
Stepping 50000
and i get 2 days of usage with wireless always connected and synk on and twitdeck updates set at 1 hour.
Click to expand...
Click to collapse
Dude, u got to be kidding,
firstly at 1.25Ghz, setting vsel to 65 wont be stable and woulld give you hotboots
Next at that vsel, there is no way that you get 2 days usage that too with wireless "always" connected, Unless you have an Extended battery.(more than 1540mAh)
, and i think you cant downclock under 800 if u set vsel3 like that it doesent consider it and it loads the default ( on CM is1000,i dont know on miui wich is it)
Click to expand...
Click to collapse
I feel i can actually set my vsel3 below the default cause when i check the CPU through other apps (Elixer or others) and also the System info shows the Processor speed as 600 Mhz.
{
"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"
}

could anyone please tell me ... how did you get that 'WajkIUI' logo there in system details !?? ... i always get 'MIUI' logo there ..

yamandude said:
could anyone please tell me ... how did you get that 'WajkIUI' logo there in system details !?? ... i always get 'MIUI' logo there ..
Click to expand...
Click to collapse
Just flash the latest build of WajkIUI from the WajkIUI thread and u'll get the new logo
The latest one is WajkIUI 2.1.6

Sidz4u said:
I am on WIUI 1.12.16 ICS build.
Yesterday, dont know what struck my mind, and i just happend to UnderClock my defy. I underclocked it to 600 Mhz, and to my surprise, i didnt find any lag.
The phone is running smooth as earlier (as at 1.1 Ghz).
Profit : Am saving considerable Juice
No effect on homescreen scrolling, multitasking, opening of app drawer, etc.
Infact all my games (Adrenaline HD, GTA III, BattleHomerun 3D, etc) are running the same way they did when phone was OverClocked
Am using the following Clock Frequencies & find it stable. Will test it even furthur
300-16
450- 28
600-38
Am pretty happy with the present speed as there is hardly and sluggishness or lag in my phone.
Give it a try and Share your experience here.
Trust me its worth giving a shot
Click to expand...
Click to collapse
All games use the gpu for rendering and dont completely use the cpu, the homescreen scrolling, effects are also mostly done the gpu (yes, even without full harware accelerated UI). So underclocking wouldnt have affected that much.
I know this because ive tried a series of vsel - clock combos from 800-38 to 1200-64 and noticed slight inc/dec in performance for games and homescreen scrolling.
But, it obviously affects processes that require the use of cpu. The one that i could notice right away was in the browser. It was noticeably slower in loading pages.
So basically its a matter of choosing b/w power vs battery and finding the right balance.
I use 900-40 600-28 300-16 and if i need more power i use 1200-62(ms2ginger)

I've done that ! .... again ! .... still miui logo comes. ... ... done both ICS version and the normal one ..... any ideas ?
---------- Post added at 02:52 AM ---------- Previous post was at 02:48 AM ----------
And Yea @pravarth. .. ure right man. ... on these super low settings browsing and many other CPU intensive activities do take a hit. ..
And yes .... that wajkiui logo thing was somewhat related to the themes .... got it now )

another question
also wanna know what scaling governor are you using
is ondemand or are you using a custon governor ?
thanks

Sidz4u said:
Dude, u got to be kidding,
firstly at 1.25Ghz, setting vsel to 65 wont be stable and woulld give you hotboots
Next at that vsel, there is no way that you get 2 days usage that too with wireless "always" connected, Unless you have an Extended battery.(more than 1540mAh)
I feel i can actually set my vsel3 below the default cause when i check the CPU through other apps (Elixer or others) and also the System info shows the Processor speed as 600 Mhz.
Click to expand...
Click to collapse
Im to lazy to make a battery spy stat to show it to you and second my first max vsel was 1270/66 but i had problems with the wireles not startin from the start and i downclocked to 1250/65 and for me its perfectly stable.
Sent from my MoTo.MB525 with XDApp.

pravarth said:
All games use the gpu for rendering and dont completely use the cpu, the homescreen scrolling, effects are also mostly done the gpu (yes, even without full harware accelerated UI). So underclocking wouldnt have affected that much.
I know this because ive tried a series of vsel - clock combos from 800-38 to 1200-64 and noticed slight inc/dec in performance for games and homescreen scrolling.
But, it obviously affects processes that require the use of cpu. The one that i could notice right away was in the browser. It was noticeably slower in loading pages.
So basically its a matter of choosing b/w power vs battery and finding the right balance.
I use 900-40 600-28 300-16 and if i need more power i use 1200-62(ms2ginger)
Click to expand...
Click to collapse
the rom you use?? I nerver get lower than 900/46, or the phone will restart.

He mentioned ms2ginger . ...

vinhomn said:
the rom you use?? I nerver get lower than 900/46, or the phone will restart.
Click to expand...
Click to collapse
Yeah it varies from phone to phone. I can even do 1000-46 and it is pretty stable. Rarely freezes.

I can't even accept the speed of a 800mhz defy
600 mhz...

Perseus Kernel

ok. Figured out why perseus kernel ran like poo on my device. I noticed on all my 3d games and sometimes on my browser, there would be be occasional stutter or a slighr but noticeable fps drop leading to a jerky stutter performance. even on the tw launcher I would see it here and there. luckily this awesome device has split screen. So I was able to observe the cpu LIVE as it scales. I ran tons of benchmarks and observed the culprit. While the phone is pushing polygons the cpu down scales to fast and way to much. it would bounce from 1.8ghz to 600mhz constantly. When this aggressive down scale happens then you see the stutter. At least I do. So... Here's the fix. Open Stweaks and on CPU SCALING scroll down to FREQUENCY FOR RESPONSIVENESS. Set that to 1.2ghz or above. Done. enjoy your stuttering free performance. Will this impact your battery? Not much. It just keeps the cpu fast when it needs the power. Once you let go of touching the screen then it scale down to below 1.4ghz.

I think your "fix" may work but I don't think it is optimal. See Andrielux's original N7100 thread and you will see that he recommends keeping this parameter no higher than 600mhz because it causes issues above that. I think there are more direct parameters that can be changed regarding down scaling to fix your issue. You should post this on his thread to get his input as he is quite wise.
Sent from my SPH-L900 using xda app-developers app

yup. I kept an eye on it all day yesterday and with cpuspy I noticed my device was hanging allot of time at 1.2. makes sense. I'll play with it more today.

found a better setting change on stweak! You can leave everything on stweak at default and may change........
under CPU SCALING go to UP THRESHOLD AT FAST-DOWN and set that to 25%. Default is 95. Now using cpuspy I see all the clocks being used healthier compared to before where 1.2ghz was hogging up more. And the studder is gone. This makes the cpu hold 1.8. steady and not down scale when using 3d . try it and you will thank me.

Okay I can confirm it now. This is a good fix for the stuttering. my battery has not taken a hit at all. And it runs smooth. And to boot I'm getting a quadrant score on the 7600. this is the change.
under cpu scaling I changed UP THRESHOLD to 70%. UP THRESHOLD AT FAST DOWN to 20%. Under GPU I changed GPU MAX FREQUENCY to 800mhz. And it's UP THRESHOLD to 80%. Everything else is at stock. Now play with the voltage of the cpu to the lowest possible voltages. And you will be thankful.

Spherekat 5.4 N5110 Slowdown/lag

Not sure if this is the right thread to talk about it, but recently I flashed the 5.4 version of this kernel http://forum.xda-developers.com/showthread.php?t=2775998 and so far so good, it fixed the 4.4.2 S Pen problem. However, I've noticed that, when I use multitask mode (2 apps open at the same time stacked on top of each other), there is some light stuttering(?). Not laggy, but when I scroll it kinda stutters a bit. Strangely enough, this only happens during multitask mode, not if I have a lot of apps open in the background. This isn't the real problem though, the real problem is that the kernel seems to cause the S Note app to lag so much that it's almost unusable. Another problem i've found was that SOMETIMES when listening to music when the screen is off, the music lags so much that it's inaudible. Not often, though, and I dorn know what specifically causes it, other than the low GPU speed. The kernel specifically states this:
"GPU settings are:
Step0 54MHz = new Idle step = when in browser mode and no gaming this low GPU speed will help save power
Step1 266MHz
Step2 350MHz
Step3 533MHz = new speed foe step3 for better performance in drawing
Step4 700MHz = New OC speed for the better gaming performance
GPU settings are not editable and hard set in the kernel"
I'm taking a guess here but I think that the low, non editable GPU settings are causing the slowdowns.
Is there any way to somehow increase the GPU, even though it says that it's uneditable? Has anyone used this kernel before and found out how to fix it? Would downgrading to a lower version of the kernel fix the slowdowns? This is the only kernel I found that fixed the slowdown for my device, I can't really install a different one, but I can downgrade this specific kernel, which I think could fix it but I'm not sure. Are there any other fixes?

Red Magic 5G MOD Kernel GPUOC 900/940mhz +battery 1.4 STABLE!

{
"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"
}
*** NOTE THAT 3.16 NA OR 4.13 Red Magic 5G SPECIFIC ROMS SHOULD BE USED WITH THIS KERNEL! THE COMBINED ROM (WITH RM5S) HAS UPDATED KERNEL CODE THAT IS NOT FULLY COMPATIBLE AND NUBIA HAS NOT UPDATED THEIR SOURCE CODE ***
*** Please click Thanks (Thumbs up icon) on my post here if you like my kernel and rate the thread 5 stars, then just use it and enjoy - if you want to send me a beer or two feel free - you don't have to use PayPal - Revolut and Amazon.com (USA) gift cards avoid fees. I like to hear from happy users I hope you are glad that you have the fastest phone in the world currently. The active cooling in this device is utilized to the extreme with MOD kernel, meanwhile your battery usage will be much improved at the same time. How? Well, that's all in the source code, free for all to fork it on GitHub and modify to your liking. Just don't forget to credit me and the many great devs that made the improvements possible... without them, there would be no MOD kernel. This is just a hobby of mine and I like to produce a nice product that all can enjoy. I'm also quite friendly and although I may tell you no I won't add that feature (such as network hacking tools), I won't hold anything against you for asking. I have not been compensated other than by some generous folks on my Telegram channel, so this whole project is basically self funded. Red Magic will not support it, unfortunately, but you can if you feel the improvements are worth it. I believe they are, but I come from a biased point of view as the sole developer for RM5G ***
********************************************************************************************************************************************************************************************************************************
NOTICE: YOU ASSUME FULL LIABILITY FOR ANYTHING THAT MAY HAPPEN TO YOUR PHONE USING THIS KERNEL. ALTHOUGH IT WORKS 100% ON MY PHONE, IT MAY NOT WORK THE SAME ON YOURS. THE PROCESS OF ROOTING A PHONE AND INSTALLING A CUSTOM KERNEL ALWAYS HAS RISKS, SO IF YOU ARE NOT COMFORTABLE ASSUMING THOSE RISKS, DON'T INSTALL THE KERNEL! THIS IS A TYPICAL DISCLAIMER FOR CUSTOM KERNELS I HAVE FOUND NO BUGS WITH IT AT ALL. USERS ON CN, GLOBAL, AND NA ALSO HAVE NOT FOUND ANY PERFORMANCE ISSUES OR BUGS (DO NOT USE V7.14 or V8.11) IF YOU DON'T KNOW WHAT YOU ARE DOING, IT'S BEST TO REMAIN STOCK. OR JOIN THE TELEGRAM GROUP, AND GET SOME REAL HELP.
********************************************************************************************************************************************************************************************************************************
Easy root method: https://forum.xda-developers.com/nu...nner-tutorial-unlock-bootloader-t4131585/amp/ although I suggest still using Magisk 20.4 for root.
Note: if you've already rooted and want to upgrade, people have had success saving the kernel as boot.img and TWRP as recovery.img in SmartPack, vbmeta skip as vbmeta.img and placing into the ROM update.zip using MT Manager (a root browser) and saving the updated file. Then do a Settings / System Update / click the 3 dots / local update and select your modified file. In fact I upgraded from 3.13 to 3.16 NA ROM without losing anything this way. Now for normal installation:
Custom kernels require root and Magisk to be installed. This is due to the signature not being signed by Red Magic (the company) itself. Following the above method you will still pass SafetyNet and most apps will work without trouble. If you have a specific app that detects root, well, Magisk Hide the app from Magisk Manager and see if that fixes it. You should also Hide Magisk Manager from various forms of detection (under Settings). Last case is to move the installation of Magisk under a random directory (which I have not had to do and all my banking apps still work), only if the root detection methods used by your app providers are more picky.
MOD KERNEL 1.4 STABLE:
RELEASE NOTES:
Block mode I/O has been changed to Multi-Queue from Single-Queue so your default scheduler is now MQ-deadline (credits to PappaSmurf, excellent kernel dev). You can choose between mq-deadline, kyber, and none in a kernel manager under I/O scheduler. From my benching with Androbench, it doesn't make much difference which one you use. Some have parameters you can tweak. None literally means no scheduler which is fine on an SSD, and has no overhead if you want to select it in a kernel manager. I always recommend SmartPack. To get settings to stick you Toggle "Apply on Boot" and it will go to what you've selected after 5-10 seconds on the next boot.
All debugging has been turned off completely on BBRv2 - thanks to PappaSmurf (I missed a few spots), and debug can't be turned back on from the userspace now. BBRv2 is selected as the default TCP algorithm which users have explained as a "no-lag" algorithm while gaming. It's just generally a fast algorithm all around. For me it works great, but you can still choose from many different algorithms in a kernel manager if you want to.
In SmartPack / Misc / TCP Congestion Algorithm, you have many choices: reno / bbr / bbr2 / bic / cdg / cubic / dctcp / westwood / highspeed / hybla / htcp / vegas / veno / scalable / lp / yeah / illinois. A SmartPack script is included below you can add in SmartPack to show the true TCP algorithm as it will always show Reno (a bug also shared by FK kernel manager). Below it's called Check_TCP.sh just go to SmartPack / Script Manager / Import / Check_TCP.sh. Afterwards, click Execute to see the active algorithm. If you set it on boot, this is the algorithm that will run, despite what the field says in Misc.
Battery is running very well on normal usage I'm getting around 7.5% active screen on drain over 7 hours and <0.7% screen off drain over 13 hours at 90hz screen setting. This is with actively using the phone for multiple "normal" purposes, reading emails, browsing websites with Chrome, reading news, streaming videos, etc. various shopping (Amazon/eBay) and tracking, Reddit feeds and live video, and other random "daily" tasks, up to 10 apps open at a time. Gaming of course will drain more, as will 144hz. I also have dark mode enabled in Settings. To get idle drain down I disabled 3 additional wakelocks that were causing high screen off drain, and so far I haven't seen an issue with blocking them. I also removed wakelocks that no longer exist since the Boeffla WL Blocker default list was created (it was quite old) so it now should be relevant for this device, with no interaction on the users part to disable anything via a kernel manager. Still, in SmartPack you will see a Wakelocks menu in case you install an app that causes idle drain to rise, this can be used to find and block wakelocks causing the problems. It can sort by wakeups and also by time. As it states though, you should be very careful what you disable. There can be unintended consequences and most wakelocks are not well documented as to what they actually control.
Dynamic Stune Boost is entirely removed from the kernel code now, as I didn't see any benefit from using it with this kernel.
Don't forget Dynamic Fsync is hidden under Misc in SmartPack which if you turn on will speed up your SQLite speeds. AnTuTu will penalize you for this, ignore it, your phone will be faster - but I leave it off by default. Androbench will show the true memory benefit. It is significant if an app does a lot of operations on databases. Journaling for the database is held in memory until the screen is off, then it is written. Although there is a chance of a data loss or corruption with this on if the device were to crash, it is safer than just turning off fsync. If you have any unstable apps, just leave it off - better to be safe. On a solid system though, you may notice better performance.
Also remember under SmartPack / GPU there is AdrenoBoost - it is set to low. You can alter to medium or high to get faster transfer between GPU frequencies, although it has worked great for me the way I use the phone. For you another setting may suit you better. Recall RedMagic OS only allows several frequencies which I spaced out as well as possible at 305mhz, 400mhz, 525mhz, 670mhz, 800mhz, and either 900 or 940mhz depending on the version you installed.
Overall I'm very satisfied with this kernel build and don't plan on adding or subtracting anything from it for the time being. It does what it should do, gives solid performance, and good battery life. My last score on AnTuTu setup with defaults 12GB/256GB was 682K which currently is still the top performing phone out there - running at 940mhz GPU. Not all phones can handle 940mhz so use 900mhz if yours cannot. If there are enough requests for an intermediate build (say 925mhz) I can add one later off the same code base. Also note in releases there are "gaming" builds that don't keep track of CPU times at each frequency, which was a request by users to remove any potential lag while gaming. I run the non gaming version, useful if you want to tweak battery usage, but nonetheless, both versions are there for you to use.
I'm on Telegram t.me/NubiaRedMagic5G_Mods as long as I have the phone. Which will be quite a while if Red Magic / Nubia decides to fix N41 5G in the USA.
Also note that all the features of this kernel (besides ones specifically added by me) are the creation of other developers whose contributions are all notated in the kernel source code. Some of the developers that have contributions here or helped me in some fashion: Resurrect88, DD3Boh, PappaSmurf, kdrag0n, Ayrton990, Flar2, Lord Boeffla, plus many more across the globe. Without them, I wouldn't be making any kernels! And I'm sure there are many other devs I've forgotten to mention, I thank all you guys for your help and support.
MOD 1.4 Download Link:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.4
PRIOR RELEASES BELOW:
8th Release:
MOD KERNEL 1.35-BBRv2 STABLE:
RELEASE NOTES:
This is an intermediate release - I realized that the prior release was draining far more battery than it should, and I found the source was debug related code in BBRv2 from Google. So this is the updated kernel that gives you battery life like before this TCP algorithm was added.
CONFIG_CPU_FREQ_TIMES=y has also been added so you can see in a kernel manager how much time is spent in each mhz block for each set of processors. This can be useful if you set in a kernel manager (like SmartPack) a minimum CPU mhz to see how much time is actually spent at each level.
The code base also has Dynamic Stune Boost, but I haven't had time to optimize it for the device, so it's just on default settings. So there are 2 versions of this 1.35-bbr2 release. At some point it will be enabled as part of a regular release (some 17 commits squashed together into 1, Stune Assist was causing issues so I turned it off). The main idea of that set of code additions is to run the device at lower frequencies, saving battery, while still achieving the same performance level to the user of the phone. If you want to try different options for it in SmartPack or FK Kernel Manager you can.
Downloads:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.35-bbr2
7th Release:
MOD KERNEL 1.3-BBRv2 STABLE:
RELEASE NOTES:
Added the 31+ commits for BBRv2 from Google. Squashed the commits down to 6 by author from Google (for easy code maintenance). It's said to be the best TCP (internet congestion) algorithm so this sets it by default. You can still select from the others added in 1.3, as mentioned only EX Kernel manager properly shows them. But SmartPack if you choose the one you want under Misc, then click Apply on Boot, it actually will load the TCP algo you selected. It's just a visual defect. I also made a script for SmartPack uploaded to show you the TCP algo that's selected in my repo you can install so you can verify for yourself. Give it 10 seconds (default on boot setting) before you check.
Downloads:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.3-bbr2
6th Release:
MOD KERNEL 1.3 STABLE
RELEASE NOTES:
All this release adds is TCP congestion algorithms. The only kernel manager which correctly shows the algo set correctly is EX Kernel Manager. Using SmartPack or FK Kernel Manager will tell you that you're always on Reno, when in fact, you aren't. I'm not quite sure if this is bug related to 865 kernels as a fellow dev had the same experience (on an Op8 Pro). Now the default is set to BBR. Why? No reason specifically, although it is one of the better algorithms for internet usage. You can easily change in any kernel manager and set on boot which one you'd like to use (see above RELEASE NOTES if using SmartPack). But this gives you plenty of options:
BBR, BIC, CDG, CUBIC, DCTCP, WESTWOOD, HSTCP, HYBLA, HTCP, VEGAS, RENO, VENO, SCALABLE, LP, YEAH, ILLINOIS
You can Google the benefits of each and pick what you like. Or just leave it alone. The prime idea of MOD kernel is that you don't need to adjust anything it just works optimally without any intervention. Read the release notes for prior features that have been added. There are many just not summarized in a single place at the moment. All the optimization has been done for Red Magic OS.
Downloads:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.3
5th Release:
MOD KERNEL 1.25BETA
RELEASE NOTES:
This release is mostly about battery savings. I'm averaging around 6.5% active drain on normal tasks with this version (90hz setting), and around 0.5% screen off drain. A big improvement over the stock kernel. So I ended up with about 13 hours SOT + 24 hours screen off on 1 charge! See the picture, I stopped at 11% left. Now I didn't say anything about gaming. If you want to game and have power saving benefits, don't enable any of the built in boosting modes in the game launcher - the Red Magic OS will override everything. Let the kernel do the work for you. And if you're seeing any graphics lag, go into SmartPack kernel manager (free) and go under GPU, Adreno Boost is enabled on low, you can set it to medium or high. That will increase the speed at which the GPU throttles up and down.
1) Switch to the Energy Model for CPUs: Several subsystems (thermal and/or the task scheduler for example) can leverage information about the energy consumed by CPUs to make smarter decisions. This config option enables the framework from which subsystems can access the energy models.
2) Added CPUMASKS for the Little, Big, and Prime cores from Sultan Alsawaf Sultan: SultanXDA, prime added by Danny Lin: kdrag0n.
3) Added kernel control of the minimum frequencies for the little and big clusters by Danny Lin kdrag0n. They are set to run at their minimum running frequencies when idle 691mhz (little) and 710mhz (big) which results in nice power savings when web browsing or just under low load in general. Prime cluster min is not set as it makes the CPU scheduler function poorly.
4) Added AdrenoBoost by Aaron Segaert: Flar2, with all its changes squashed into 1 commit. Defaults to low setting. As mentioned before, you can change in SmartPack, and set on boot if you need a higher value than low: https://github.com/SmartPack/SmartPack-Kernel-Manager/releases
5) Uploaded the various GPU OC files to the repo, It still will just build off the default one, but they are here to be complete. 940mhz version again is posted, Building direct from the repo will give you 900mhz max GPU.
Downloads:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.25BETA
4th Release:
MOD KERNEL 1.2 BETA
RELEASE NOTES: (Note a 940mhz GPU clock edition is available, if you want to try it, a few of us have had good results on it. Likely the max an 865 GPU can run. You'll sacrifice the power savings, however):
1) Enable Power-efficient workqueues by default, add a toggle that can turn this off via a kernel manager (under CPU in SmartPack). Enabling this makes the per-cpu workqueues which were observed to contribute significantly to power consumption unbound, leading to measurably lower power usage at the cost of small performance overhead. Have also added many other power saving features to the defconfig. The phone is a beast, power savings is a good thing to implement.
2) Update the LZ4 decompressor algorithm with a much faster variant for the ZRAM swap, now version 1.8.3-9 credits Gao Xiang [email protected] and many others (check commits). Speed improvement below (should help on 8GB devices):
Compressor name Compress. Decompress. Compr. size Ratio Filename
lz4hc 1.7.3 -9 12 MB/s 653 MB/s 42203253 42.20 enwik8
lz4hc 1.8.3 -9 11 MB/s 965 MB/s 42203094 42.20 enwik8
3) Default scheduler is set to SQ deadline. Should see minimal improvements in speed until I get a MQ variant working. On the task list ahead.
Download Link:
1.2BETA: https://github.com/mrslezak/NX659J_Q_kernel/releases/download/1.2BETA/MOD-RM5G-GPUOC-Beta1.2.zip
940mhz GPU release here, it's still 1.2BETA, just with the max clock a few of us have been able to use. That doesn't mean your device can for sure handle it, but give it a try if you'd like! Note the power savings will likely not be there vs the other release at 900mhz:
https://github.com/mrslezak/NX659J_...oad/1.2BETA/MOD-RM5G-GPUOC-940mhz-Beta1.2.zip
3rd Release:
1.15BETA: https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.15BETA
This is a HEAVILY updated release of the MOD kernel 1.10BETA - I realized the phone's software will allow 6 frequency clocks, although 1 did not have a regulator defined (now patched). NOW I VERY HIGHLY suggest installing SmartPack Kernel manager. It will give you insights into the kernel and how it's performing and it's free. It also will let you adjust added options now in the kernel. Just root your phone and flash from TWRP. If you haven't already installed Magisk, then install that too. There's a guide I posted on XDA about that. Use the experimental method there is no reason to unlock your bootloader. https://forum.xda-developers.com/nu...how-to-unlock-bootloader-redmagic-5g-t4081743
RELEASE NOTES:
1) Bugfix: there was 1 missing 800mhz GPU frequency regulator clock on the prior version. This has been set to TURBO, 1 level under the 900mhz regulator of TURBO_L1.
2) Boeffla WakeLock blocker (v1.10 + tweaks) has been added to reduce battery drain when the phone is not being used, using the latest version and all patches. A default block list is included. You can access in SmartPack Kernel Manager under the new menu that will appear "Wakelocks" - especially investigate if your phone has high idle drain, you can experiment with blocking other wakelocks (which don't allow your phone to sleep). Or you can leave as is. I get just under 1% drain (screen off) and the phone sleeps quite often with this version. Take a look at the screen shot! That's just normal phone usage, not gaming.
3) All debug entries (except those required) have been stripped completely out of the kernel. This results in less wasteful debug information being generated.
4) The default algorithm for ZRAM has been changed from LZO (high compression, but slow) to LZ4 (slightly less compression, but fast). LZ4 algo was added. It still defaults to 4GB.
5) Dynamic Fsync has been added to the kernel as well. This patch allows journal entries to be written only when the screen is off. I.e. they are cached and written afterwards. This increases database performance. It is disabled by default so in SmartPack Kernel manager, if you'd like to turn it on, go under Misc, select Dynamic Fysnc, and select apply on boot. There is always a risk of data loss when delaying writes, although I've personally never have had issues - it only happens if the phone crashes, and mine has never crashed on this kernel. This won't normally increase your benchmark scores (except AndroBench), it increases SQLite database access speed. Up to you to use or not, works fine on my device.
6) Here are the updated frequencies (note there is 1 more). Will have to wait for AOSP before I can add back more. Note the 670MHz is likely the 865+ max frequency per the release notes today on the device (which I assumed by the source code anyhow pre-announcement): 900MHz / 800MHz / 670MHz / 525MHz / 400MHz / 305MHz
AS ALWAYS, USE AT YOUR OWN RISK!!!
Github Source:
https://github.com/mrslezak/NX659J_Q_kernel
Initial Release:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.0.BETA
Second release - gets over the "reset to 490mhz" bug caused by the system software, at the expense of reducing frequencies to 6 total:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.10BETA
Newest release -> will be posted on the top from now on.
Telegram:
https://t.me/NubiaRedMagic5G_Mods
And note the AnTuTu benchmark is just a first run after installing. 670K is likely a record on any 865 phone. The last bench turning off 4GB ZRAM (12gb/256gb device) I got 673K. AnTuTu doesn't equal performance, but if you've benched you'll see this is an insane improvement over the stock kernel. Only when the demand is there will it scale up to 900mhz. I've been using for a while now and notice no difference in battery life. The Adreno driver is very good at handling extra clock frequencies efficiently without modification (despite an "Adreno Boost" that is often added to kernels). The gamers using the kernel are making statements that they couldn't imagine the game play any better than it already was, but now it's even smoother.
Unfortunately the way the Nubia software behaves, it auto-resets to power level 5 (which was 490mhz) on the 1.0BETA on boot and also after boosting the frequencies up. I tried every possible way to bypass this but eventually just gave in and removed frequencies. So the BETA1.10 and above have less frequencies but will always revert to 305mhz, the base minimum frequency of the device. Hopefully once we have AOSP ready I can add more.
MattoftheDead
I.e. M.O.D. Kernel Developer
The first Red Magic 5G OC kernel.
Xiaomi Mi9 / Mi9T Pro Pie V2 and Q V1.5 Kernel Dev

Nice work. Do you notice any benefits to OCing the GPU like that? I don't think there are many games that would benefit atm.

This is amazing !!! :laugh:

Is this going to work on all roms like CN, NA or EU Roms? Im currently running NA 3.11 flash from CN rom with root and twrp

We have people using it on CN Global and NA versions no problem at all. Works fine on every model.

Kernel is fully functional no issues at all.
CN Rom to NA Rom v3.11
305mhz min to 900mhz max confirmed and using smart pack to control the frequency
Thank you for this hopefully there is more development i really appreciate ur effort

Kernel building is just a hobby of mine, I was posting a minimal kernel to get some more kernel developers on board to hopefully add more features. I usually add Boeffla Wakelock Blocker and Dynamic Fsync and call it a basic kernel. The last super kernel I made took way too long, and I don't have that kind of time anymore - boost functions and underclocking to balance out the battery life and such. Development work doesn't pay anything, I didn't get the phone free, all my donations go to other developers. And I have a full time job and family. But if anyone wants to port over my MOD Kernel Q 1.5 Mi9 features, well that would be a super kernel. It's just really, really time consuming, time I don't have at the moment. And the merging of source has to be EXACT or you end up with a really slow phone rather one that balances underclocking, boost, and overclocking.

MishaalRahman said:
Nice work. Do you notice any benefits to OCing the GPU like that? I don't think there are many games that would benefit atm.
Click to expand...
Click to collapse
All the gamers using the kernel are reporting that the games run smoother than before, which no one thought was possible. It is already a flagship device. But the GPU OC with the Adreno driver scales when needed up to the frequencies that it has in the table and has no issue on 670, 800, and 900mhz reported so far. There are gamers on NA, Global, and CN ROMs, with no bugs reported. No issues and everything works properly. I have tested myself and although I'm not a gamer, all the functions work as they should. It still connects via Bluetooth, it still takes photos and videos, etc. There is no lag whatsoever. Overall I think the frequencies are ideal for this device with it's advanced active cooling system. Other devices however, with passive cooling, are unlikely to handle the increased GPU clocks.

I found an unusual bug where the GPU Minimum Frequency will reset on its own to 490mhz even if i set the minimum frequency to 305mhz im using smart pack kernel manager that you provided and cool tool btw to monitor the gpu frequency.
I also set the battery optimization to off on smart pack so it wont turn off itself.
This also happens when i played games that actually boost to 800 to 900mhz then after i close the game it sets back the minimum frequency to 490mhz so i have to set it again to 305mhz on the kernel manager to save more battery and lower the temps.
I also notice it sets back to 490mhz minimum frequency by just watching youtube videos so i have to set it back to 305mhz again. I tried different kernel manager too like Franco Kernel Manager and Kernel Audiator and still doesnt fix the issue
I think this was a minor bug for sure
I never touch the GPU governor btw
Performance was super nice thou i scored 645k on antutu on my first run but for now im going back to stock and gonna wait for your next update

What to do to root the phone without breaking the fingerprint please. I read the article publish nothing understood someone can explain to me step by step. I am an amateur I never root a phone. I have cn 2.55 16gb.

I don't have the same issue - I just tried to recreate it by watching a YouTube video and I went back to SmartPack and it still shows 305MHz GPU frequency. Although I'm using the debloated / optimized ROM I created Black Magic 5G which has everything setup properly, Nubia apps frozen, everything moved to 3rd party apps. NETFLIX patched to 4K HDR10, YouTube Vanced, a ton of root utilities, AdAway ad blocker, etc. You can find it on the Telegram channel (I'm using the NA/Global version of Black Magic 5G). Then I watched Netflix, still at 305mhz. As I have no idea how you've setup your phone, I just can't recreate it.
shaifabra5 said:
I found an unusual bug where the GPU Minimum Frequency will reset on its own to 490mhz even if i set the minimum frequency to 305mhz im using smart pack kernel manager that you provided and cool tool btw to monitor the gpu frequency.
I also set the battery optimization to off on smart pack so it wont turn off itself.
This also happens when i played games that actually boost to 800 to 900mhz then after i close the game it sets back the minimum frequency to 490mhz so i have to set it again to 305mhz on the kernel manager to save more battery and lower the temps.
I also notice it sets back to 490mhz minimum frequency by just watching youtube videos so i have to set it back to 305mhz again. I tried different kernel manager too like Franco Kernel Manager and Kernel Audiator and still doesnt fix the issue
I think this was a minor bug for sure
I never touch the GPU governor btw
Performance was super nice thou i scored 645k on antutu on my first run but for now im going back to stock and gonna wait for your next update
Click to expand...
Click to collapse

Yeah maybe because you modified the rom.
Im currently running Flash Global V3.11 when i tested your kernel no modification made im just rooted with TWRP Installed and i posted this kernel on red magic 5g group on facebook and 3 of us having the same issues as well.
Im gonna try it again on V3.13
UPDATE:
still returning to 490mhz as minimum frequency after gaming and after watching one youtube clip
kinda sad hopefully you can fix this bug on the global rom that nubia provided if you have the time, great kernel for gaming because of the 900mhz boost and the phone can sustain this boost because of the active fan

Why don't I have a roughly similar score?

Is it possible to overclock the CPU as well? They officially release the specs sheet of ROG Phone 3 it has overclocked CPU (3.091ghz) and an overclocked GPU. I know this phone can keep up with those clocks because of the cooling system but the problem is the battery life. But still, its worth it.

Blink003 said:
Is it possible to overclock the CPU as well? They officially release the specs sheet of ROG Phone 3 it has overclocked CPU (3.091ghz) and an overclocked GPU. I know this phone can keep up with those clocks because of the cooling system but the problem is the battery life. But still, its worth it.
Click to expand...
Click to collapse
I believe Qualcomm blocked overclocking of CPUs quite a while ago from SD845. Only GPUs can be overclocked.
Though I don't know if devs have gotten tools to get around it.

The 490 bug looks like it's related to the gaming mode APK resetting the min frequency. I can't decompile or recompile APKs so I don't have a way to get around the system reverting to 490 without removing 3 other frequencies. It seems hard-coded in the app that it only expects to see 5 frequencies so to have all working properly, 3 need to be removed. This is in contrast to what my buddy dev on the Op8 Pro can do, but this device is designed differently in how it boots and custom apps that increase frequency clocks. If any devs are good with APKs it's a very simple function call that sets the minimum GPU frequency. The only odd thing I see is that the minimum power level stays at 8 (minimum) which corresponds to the lowest clock speed. That number doesn't change in a kernel manager when the min GPU clock reverts to 490.
I'm off on vacation not near a PC but will try to come up with a stock # of clock frequencies that still scrolls smoothly between them and the Adreno GPU driver. May take a few tries but it's quite easy to modify. I already think 180mhz is too low from using it, it's more of a sleep frequency some suggested going this low but I think the phone design is for 300+. I prefer to use more clocks for better throttling but have to work with what we are given and do the best inside those boundaries.
No you can't raise CPU clocks on 865 devices that ROG device is supposedly using the 865+ or whatever the mid device is named between the 865 and 875. They have blocked CPU OC hardware wise for some time now.

mslezak said:
No you can't raise CPU clocks on 865 devices that ROG device is supposedly using the 865+ or whatever the mid device is named between the 865 and 875. They have blocked CPU OC hardware wise for some time now.
Click to expand...
Click to collapse
Qualcomm's Meizu’s CMO Wan Zhiqiang recently commented on Weibo saying that there won’t be a Snapdragon 865 Plus this year.
We will see!

No 865+ this year..
Trust me whatever they call it it's already defined in the source code as a second GPU bin clock for another device ID. So maybe it won't be called an 865+ but there is some device between the 865 and 875 coming out. I have OEM confirmation as well this device exists the name isn't important. I can tell you the top GPU frequency is 670mhz that's it, vs. the 587mhz default on the 865. Still the 865 handles 900mhz GPU no problem the only benefit would be higher CPU clocks. And an extra GPU clock. Which I'll attempt to spoof next time I get near a PC.

mslezak said:
Trust me whatever they call it it's already defined in the source code as a second GPU bin clock for another device ID. So maybe it won't be called an 865+ but there is some device between the 865 and 875 coming out. I have OEM confirmation as well this device exists the name isn't important. I can tell you the top GPU frequency is 670mhz that's it, vs. the 587mhz default on the 865. Still the 865 handles 900mhz GPU no problem the only benefit would be higher CPU clocks. And an extra GPU clock. Which I'll attempt to spoof next time I get near a PC.
Click to expand...
Click to collapse
Is it possible to overclock the memory clock too? I assumed that 900mhz is the core clock.

mslezak said:
Trust me whatever they call it it's already defined in the source code as a second GPU bin clock for another device ID. So maybe it won't be called an 865+ but there is some device between the 865 and 875 coming out. I have OEM confirmation as well this device exists the name isn't important. I can tell you the top GPU frequency is 670mhz that's it, vs. the 587mhz default on the 865. Still the 865 handles 900mhz GPU no problem the only benefit would be higher CPU clocks. And an extra GPU clock. Which I'll attempt to spoof next time I get near a PC.
Click to expand...
Click to collapse
You're right, that makes sense.
I'm glad they are making a refreshed chip.
On another note, do you think we will see an overclocking tool in the future?
Possibly with a custom ROM?

Touch screen randomly stops functioning

I've been facing non responsive screen with my OnePlus 5T. The screen touch stops responding and only volume keys and power button are responsive.
Sometimes a reboot fixes the trouble but other times I have to dirty flash the stock Oxygen OS 10.0.0 zip file in TWRP recovery using OTG and mouse, to bring back the touch function to normal.
What should I do to permanently solve this trouble?
This has been a frequent problem as posted by many users here.
https://forum.xda-developers.com/oneplus-5t/help/touch-screen-5t-randomly-stops-t3888017

Well, this problem is 100% a hardware one and it is caused by the fluid of the screen digitizer. One possible cause (apart from manufacturing flaw) is the prolonged heat that is encapsulated inside the phone. That's why most people with thick protective cases and protective plastic screen film had the issue appear as soon as 4 months of usage.
You can easily prove my theory: the next time it happens again leave the phone in the fridge (not freezer) for around 10 minutes, without restarting or doing anything to it. Then see by yourself if your touchscreen has come back to normal.
The most permanent solution is to replace the AMOLED screen and use a case that is as thin as possible. Other people had success by flashing a different custom kernel (probably one that lowered the Snapdragon's power consumption) but even then some reported that it reappeared after a few months. But I think that the screen's digitzer fluid has been permanently damaged by the heat over the years of use.
So to sum up:
1. Change screen for a new one
2. Use the thinnest possible case for the phone
3. (my recommendation) Flash a slightly underclocked/undervolted kernel alongside a stock-android based custom ROM
The third step is just a precaution to prevent it from happening again.
Hope I helped to clarify the issue

BlackRazor97 said:
Well, this problem is 100% a hardware one and it is caused by the fluid of the screen digitizer. One possible cause (apart from manufacturing flaw) is the prolonged heat that is encapsulated inside the phone. That's why most people with thick protective cases and protective plastic screen film had the issue appear as soon as 4 months of usage.
You can easily prove my theory: the next time it happens again leave the phone in the fridge (not freezer) for around 10 minutes, without restarting or doing anything to it. Then see by yourself if your touchscreen has come back to normal.
The most permanent solution is to replace the AMOLED screen and use a case that is as thin as possible. Other people had success by flashing a different custom kernel (probably one that lowered the Snapdragon's power consumption) but even then some reported that it reappeared after a few months. But I think that the screen's digitzer fluid has been permanently damaged by the heat over the years of use.
So to sum up:
1. Change screen for a new one
2. Use the thinnest possible case for the phone
Click to expand...
Click to collapse
Thanks for replying @BlackRazor97. Few minutes ago, I faced this trouble again.
My screen froze and I rebooted once. The screen wasn't responding. I gave a second reboot. It started functioning again. While it was booting, I came here and went through your post. I just went through your post. Getting the screen replaced is probably going to be an expensive affair. I would rather buy a new phone but still want to continue with this one without getting any hardware replaced.
I'll surely try the fridge trick the next time it happens.
BlackRazor97 said:
3. (my recommendation) Flash a slightly underclocked/undervolted kernel alongside a stock-android based custom ROM
The third step is just a precaution to prevent it from happening again.
Hope I helped to clarify the issue
Click to expand...
Click to collapse
I have never done underclocking/undervolting before. Wouldn't it make the phone slow? Can you please suggest any reliable slightly underclocked/undervolted kernel for stock oxygen os 10.0.0 as that's the one I'm currently on. Flashing a new ROM, restoring my apps will take a long time.

archz2 said:
I have never done underclocking/undervolting before. Wouldn't it make the phone slow? Can you please suggest any reliable slightly underclocked/undervolted kernel for stock oxygen os 10.0.0 as that's the one I'm currently on. Flashing a new ROM, restoring my apps will take a long time.
Click to expand...
Click to collapse
I have only used FrancoKernel myself but since it's not available for Android 10, I recommend you to flash blu_spark r209 stable kernel for Android 10. It should work fine for stock Android 10 OOS.
https://forum.xda-developers.com/oneplus-5/oneplus-5--5t-cross-device-development/kernel-t3651933
And then by using the FKM (Franko Kernel Manager) under "battery tips" you can underclock the CPU. You don't need to underclock it too much; set it to 2Ghz (instead of 2.45Ghz) for the big cluster and 1.2Ghz for the little cluster. You will see no big difference in performance and your battery life will improve too !
Always do a backup of your stock kernel, just in case something happens.
Please let me know if it helped resolve your issue.

BlackRazor97 said:
I have only used FrancoKernel myself but since it's not available for Android 10, I recommend you to flash blu_spark r209 stable kernel for Android 10. It should work fine for stock Android 10 OOS.
https://forum.xda-developers.com/oneplus-5/oneplus-5--5t-cross-device-development/kernel-t3651933
And then by using the FKM (Franko Kernel Manager) under "battery tips" you can underclock the CPU. You don't need to underclock it too much; set it to 2Ghz (instead of 2.45Ghz) for the big cluster and 1.2Ghz for the little cluster. You will see no big difference in performance and your battery life will improve too !
Always do a backup of your stock kernel, just in case something happens.
Please let me know if it helped resolve your issue.
Click to expand...
Click to collapse
I'm quite frustrated now. I'll try flashing the blu spark and do settings with Franco Kernel Manager.
Anyway, my experience with the refrigerator trick today.
First time it worked. The other time when screen issue came up, I rebooted my phone twice, hoping to solve the problem, but it didn't happen. Then I put it in the fridge. After ten minutes, I took it out the screen wasn't responding. I rebooted it. The screen started working.
Sent from my ONEPLUS A5010 using Tapatalk

@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?
{
"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"
}
Sent from my ONEPLUS A5010 using Tapatalk

archz2 said:
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?View attachment 5128013
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Yes exactly. Let the minimums as it is and lower the maximum frequencies. FKM received a big overhaul update in version 4.0, which apparently I haven't used. The menus are different but the functionality must be the same. Also don't forget to enable blu_spark blu_active governor.
Let me know if the fix is a permanent solution for you.

BlackRazor97 said:
Yes exactly. Let the minimums as it is and lower the maximum frequencies. FKM received a big overhaul update in version 4.0, which apparently I haven't used. The menus are different but the functionality must be the same. Also don't forget to enable blu_spark blu_active governor.
Let me know if the fix is a permanent solution for you.
Click to expand...
Click to collapse
Okay. Thanks. I've done it. So far so good. I have set frequencies to 1248MHz, 2112MHz. These I selected from the options pop-up. There's no way to type frequencies manually. One small query. When I do any changes in franco kernel, I don't have to reboot to apply those changes. Or should I ?

archz2 said:
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?
Click to expand...
Click to collapse
Actually there is a battery tips tab.
And if you are interested, you can check the Lazy kernel
They say it's good.

archz2 said:
Okay. Thanks. I've done it. So far so good. I have set frequencies to 1248MHz, 2112MHz. These I selected from the options pop-up. There's no way to type frequencies manually. One small query. When I do any changes in franco kernel, I don't have to reboot to apply those changes. Or should I ?
Click to expand...
Click to collapse
Nice! Yes, I think you don't need to reboot for the settings to apply. You can check with another app like CPUZ to check if clocks go above 2112MHz. But I think you should be fine.
As for the Lazy Kernel, I don't know if it's compatible with stock Android 10 OOS. But here we don't go for the performance but we target stability and low thermals to resolve the screen issue.

BlackRazor97 said:
Nice! Yes, I think you don't need to reboot for the settings to apply. You can check with another app like CPUZ to check if clocks go above 2112MHz. But I think you should be fine.
As for the Lazy Kernel, I don't know if it's compatible with stock Android 10 OOS. But here we don't go for the performance but we target stability and low thermals to resolve the screen issue.
Click to expand...
Click to collapse
Yah there is lazy kernel for stock OOS .
Those who flashed it has high recommendations and showed low ram usage .
Before flashing lazy kernel it was 700 mb free ram usage .
After flashing lazy kernel , attached screenshot.
Rom- derpfest
I haven't flashed it yet , I will when I get time

...........

@BlackRazor97
Okay. Almost a week went by. I faced non-responsive screens in last 3-4 days but the issue got resolved by tapping mindlessly on the screen when it was locked and frequent screen unlocks. Yesterday came the issue where I rebooted the phone multiple times to make the screen respond. Today the issue also came, half an hour ago and frequent reboots didn't solve the issue. I rebooted in recovery and wiped the cache and dalvic. Then I started my phone. It responded fine. I went to Franco Kernel Manager. To my surprise, the frequencies were switched back to 2361 MHz for Big Cluster and 1824 or 1900 MHz (can't remember which one) for the Little Cluster. Now I've changed them back to 2112 MHz and 1248 MHz
How did these frequencies got back to higher number without me every touching the Kernel Manager? I didn't install any app, nothing in these days.

archz2 said:
@BlackRazor97
Okay. Almost a week went by. I faced non-responsive screens in last 3-4 days but the issue got resolved by tapping mindlessly on the screen when it was locked and frequent screen unlocks. Yesterday came the issue where I rebooted the phone multiple times to make the screen respond. Today the issue also came, half an hour ago and frequent reboots didn't solve the issue. I rebooted in recovery and wiped the cache and dalvic. Then I started my phone. It responded fine. I went to Franco Kernel Manager. To my surprise, the frequencies were switched back to 2361 MHz for Big Cluster and 1824 or 1900 MHz (can't remember which one) for the Little Cluster. Now I've changed them back to 2112 MHz and 1248 MHz
How did these frequencies got back to higher number without me every touching the Kernel Manager? I didn't install any app, nothing in these days.
Click to expand...
Click to collapse
Did you set it to set on boot my friend?

When I enable the CPU governor blu_active, I get the notification "set on boot:true", that's it. I didn't toggle any other setting. I just restarted, the frequencies are back to 2361 MHz. Is there some other place where I should set on boot ?
View attachment 5132257

archz2 said:
When I enable the CPU governor blu_active, I get the notification "set on boot:true", that's it. I didn't toggle any other setting. I just restarted, the frequencies are back to 2361 MHz. Is there some other place where I should set on boot ?
Click to expand...
Click to collapse
Do one thing this time.
Under clock both your CPU AND GPU.
Under battery life tips, check under clock both.
And click on the settings icon just near to it and set it on boot.
Check this for some days and tell me

This

rohithksaj said:
Do one thing this time.
Under clock both your CPU AND GPU.
Under battery life tips, check under clock both.
And click on the settings icon just near to it and set it on boot.
Check this for some days and tell me
Click to expand...
Click to collapse
Thanks. I've done it. I'll keep you posted.

The situation became worse after underclocking. Had to reboot twice to get the screen working. I went back to the old settings.

archz2 said:
The situation became worse after underclocking. Had to reboot twice to get the screen working. I went back to the old settings.
Click to expand...
Click to collapse
DO NOT use the automatic underclock button. This also lowers the voltage to the point it becomes unstable and we don't want this to happen. Use the typical 2112 MHz and 1248 MHz (big and little cluster accordingly).
Unfortunately, it seems that the "set on boot:true" flag is bugged. So every time you shutdown your phone, you have to re-configure to the frequencies. Let me know if you have found any better solution to keep the settings.