• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root EVO V CPU Frequency Inconsistent...

E

EvoVAlpha

Member
Okay folks, I'm currently on Negalite BluRom and really can't complain. I have it overclocked to 1620 with the base as 384. I use Kernel Tuner to tweak it but noticed a problem that happens a lot... For some reason out of nowhere, my CPU frequency goes right down to rock bottom to 384, single core.

Meaning I go from using both cores at 1620 to one at 384, for no reason. I even had a profile set way back when to keep them both linked and at 1620 through KT, but still have the same problem.

So first, is this a result of the tuner program? Second, I guess I wouldn't be surprised if you told me that it fluctuates downward when not in use, but it still does it when the screen is on, and even if it's idle, I'll begin to use it and everything moves at a snails pace.

Any help would be great!
 
I would get rid of that Kernel Tuner app right now. You are not tuning anything but making it worse with that app. CPU is supposed to decrease the frequency and disable idle cores (other than cpu0) when there is no demand.
 
I know that some of us, me included, use Kernel Tuner to change a lot of different things. What would you recommend as an alternative to Kernel Tuner?
 
Chingling said:
I know that some of us, me included, use Kernel Tuner to change a lot of different things. What would you recommend as an alternative to Kernel Tuner?
Click to expand...

I don't believe a kernel should need any user tuning. User's interface to the device is .... GUI. I would recommend keeping the changes only for GUI to a user. GUI interfaces with OS and OS interfaces with kernel. User shouldn't bypass the interface layers and access the kernel since this disturbs the computing hierarchy and decreases the efficiency of the kernel. How you might ask. Here is an example: Each kernel tuning parameter added to sysfs is a file for the kernel to periodically monitor and that comes with its CPU and RAM overhead. Plus each file system access actually adds load to io scheduler, workqueue, and uses the entropy pool. Just giving the user a tuning parameter actually decreases the efficiency of kernel to begin with.

Do you remember why user-space mpdecision was so bad? Because the hierarchy was disturbed and the kernel was trying to feed the user-space daemon via sysfs interface which is not an efficient data transfer protocol.

Anyway, I have strong feelings about feature pollution of Android kernels. Maybe you asked the wrong person. I will stop here.
 
mrg666 said:
I don't believe a kernel should need any user tuning. User's interface to the device is .... GUI. I would recommend keeping the changes only for GUI to a user. GUI interfaces with OS and OS interfaces with kernel. User shouldn't bypass the interface layers and access the kernel since this disturbs the computing hierarchy and decreases the efficiency of the kernel. How you might ask. Here is an example: Each kernel tuning parameter added to sysfs is a file for the kernel to periodically monitor and that comes with its CPU and RAM overhead. Plus each file system access actually adds load to io scheduler, workqueue, and uses the entropy pool. Just giving the user a tuning parameter actually decreases the efficiency of kernel to begin with.

Do you remember why user-space mpdecision was so bad? Because the hierarchy was disturbed and the kernel was trying to feed the user-space daemon via sysfs interface which is not an efficient data transfer protocol.

Anyway, I have strong feelings about feature pollution of Android kernels. Maybe you asked the wrong person. I will stop here.
Click to expand...

Actually, I think I couldn't have asked a better person :P What you said made a lot of sense. I never thought of it in that way. So the best thing to do would probably be to just leave the kernel alone. Does that mean that things like choosing what governor you're using or setting parameters for these governors can decrease efficiency?
 
Does it get stuck at that frequency? I had the same problem when using blurom. I did not have the issue with other roms. I have been using unlocked potential HD for a while with kernel tuner with no such issue.
 
Chingling said:
Actually, I think I couldn't have asked a better person :P What you said made a lot of sense. I never thought of it in that way. So the best thing to do would probably be to just leave the kernel alone. Does that mean that things like choosing what governor you're using or setting parameters for these governors can decrease efficiency?
Click to expand...

You can change governor with a simple app like No-frills that doesn't disturb the kernel too much. Changing the governor parameters should not be necessary. If the governor is not working well I would just replace the kernel with another that works better. A good kernel works well out of the box, under every possible situation, without any tuning.
 
mrg666 said:
You can change governor with a simple app like No-frills that doesn't disturb the kernel too much. Changing the governor parameters should not be necessary. If the governor is not working well I would just replace the kernel with another that works better. A good kernel works well out of the box, under every possible situation, without any tuning.
Click to expand...

Thanks! Your advice has been very helpful.
 
Yes MRG, very much appreciate your words. I won't lie, a good bit where above my 'pay grade,' but the gist is that KT's mess with aspects of the kernel that just shouldn't be touched. And doing so causes more issues then not. I've often thought about just uninstalling it and not messing with the kernel, but tell me this... Because I have it overclocked to 1620, if I get rid of the KT, will it still utilize the max rate and second core?

If I'm even asking the question properly!!!
 
In general (including my kernel), both cores will be reaching the maximum frequency independently when there is demand and both of them will be at minimum frequency when they are idle. Additionally, the idle cores (except core 0) will be shutdown to save battery. The frequency is controlled by the cpu governor independently for each core. You don't need to and shouldn't lock the cores at the same frequency. You can monitor the cpu frequencies as shown in the picture below. Both System Monitor and Nofrills are available free in the Play Store. It is hard to see the CPU's at their maximum frequency and all cores online since when you are visualizing them they will be mostly idle.
oh9j.png
 
Okay, again thanks for the info... I installed no frills, but tell me this... Where do you set yours? If you set it at all. My max was 1674 and min is 864 with performance as the governor. I know you're saying leave well enough alone but want to make sure to just leave it as it is with NF.
 
Yep, still having the same issues. I even uninstalled nofrills and still have the same problems. Is this a kernel issue now?
 
Well, I tried something else with so so results... I reinstalled the ROM and went with the recommended clock speed at 1.5. Haven't had it as much but sometimes I'll still unlock it and both cores and the max and min are stuck at 384:|
 
You must log in or register to reply here.
Back
Top Bottom