Develop Bugs

[Q] Why is the newest Netarchy Kernel making my Stock Root Rom's FPS WORSE?!

Can anyone help me out?
I'm running stock rooted 2.2 (deodexed) and flahsed over the 4.0 zip... and the scrolling is choppier than all hell. I re flashed the stock kernel, and it was back to being fine again. So, I tried again, with wiping the caches first, and still choppier than all get out when I flashed the kernel.
It's definitely the right kernel, but what the hell am I doing wrong here? Any help would be appreciated.

And, I'll even throw in 5-10 dollrs for someone who can give me an answer that works.

This could be because of the new settings he just changed. Try the download that is 4.0.2 and not 4.0.3, or try overclocking your processor to 1.2GHZ with OC widget or SetCPU.

What kind of screen do you have? If you have a Nova panel, you may need to adjust T2 values to get the best performance. Just my 2 cents.

Ok, so I installed 4.0.2, and it seems to be running better, but still some choppiness on the menu up and down scrolling when "all apps" is opened.
I have no idea how to use SetCPU (noob yep... graphics guy... not a tech guy_, so I took a screen:
{
"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"
}
Wpould you mind just telling me where the sliders should be?

nukedukem said:
What kind of screen do you have? If you have a Nova panel, you may need to adjust T2 values to get the best performance. Just my 2 cents.
Click to expand...
Click to collapse
I have a Nova, but, I have no idea what T2 panels are and how to adjust them. If you could point me to the right app or direction, that'd be awesome. I'll donate to you as well if it helps.

There's an app floating around here called NovaFreq formerly evoswitch. It allows you to change the panel frequency to improve fps. Everyone gets different results. 450ish was usually the best for me. Basically trial and error. Most haven't needed it with recent kernels though. As for setcpu, the higher the max frequency the better fps performance, but overclocking comes with some risks. Im usually underclocked at 576max / 245min. You can also set profiles to run certain speeds when screen off, charging, etc. Helps a lot with battery life. I would move your max down to 998 or 1113 and min to 245. Ondemand is usually a good scaling setting. Hope this helps.
Sent from my FROYO'D EVO using xda app

dglowe343 said:
There's an app floating around here called NovaFreq formerly evoswitch. It allows you to change the panel frequency to improve fps. Everyone gets different results. 450ish was usually the best for me. Basically trial and error. Most haven't needed it with recent kernels though. As for setcpu, the higher the max frequency the better fps performance, but overclocking comes with some risks. Im usually underclocked at 576max / 245min. You can also set profiles to run certain speeds when screen off, charging, etc. Helps a lot with battery life. I would move your max down to 998 or 1113 and min to 245. Ondemand is usually a good scaling setting. Hope this helps.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
Wow thanks. I downloaded nova frequency, but just left it at default, and changed the setcpu, bc I was getting random reboots with the overclock. I also set profiles to way lower when the screen is off and the phone is at lower battery percents.
This phone officially runs like it's on crack now. Good stuff.
Guys, PM me ur paypals, and I dont' mind donating a few bucks tomorrow.

Glad to help. Feel free to send my donation to one of the developers on this forum. Without them I wouldn't have known any of that.
Sent from my FROYO'D EVO using xda app

dglowe343 said:
Glad to help. Feel free to send my donation to one of the developers on this forum. Without them I wouldn't have known any of that.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
Good ****
Sent from my PC36100 using XDA App

TJDuckett said:
Wow thanks. I downloaded nova frequency, but just left it at default, and changed the setcpu, bc I was getting random reboots with the overclock. I also set profiles to way lower when the screen is off and the phone is at lower battery percents.
This phone officially runs like it's on crack now. Good stuff.
Guys, PM me ur paypals, and I dont' mind donating a few bucks tomorrow.
Click to expand...
Click to collapse
LOL bro. Not only did I tell you to use NovaFreq, but I also told you not to use SetCPU. You were getting reboots b/c it was set too high and you don't want to set it below 245 when screen is off. I don't think SetCPU is so great for *most* people. I could have helped you on GTalk and taken your money...gladly would have

Update! [Kernel] [2.6.29] [Updated: 22/12/2010] RaKern-113 for GSM Hero

Please take the time to read all the description. It is important!
What's new in RaKern-113?
I tweaked things here and there. It is now better to work with and much more stable. I've also discovered what was causing wlan not to work, and it is fixed. To be more specific:
- I've gone again a little bit into the scheduler and made some changes
- tweaked lowmemorykiller
- reduced the maximum frequency to 652MHz(from 691MHz), hopefully this will make the kernel compatible with more Heros
- patched smd_rpcrouter(see here why: http://forum.xda-developers.com/showthread.php?t=878268 )
- created update.zip for any rom available
Why should you choose RaKern?(long story, good to read)
After some debates about the perfect cpu frequency governor for a battery powered device like ours(thank erasmux for that), I've decided to tune what I already have and go for the elegant way. That means using a tuned version of the ondemand governor while the screen is on, and then use the conservative governor when the screen is off. Here's the story:
The only major difference between the conservative and ondemand governor is that the ondemand governor switches to the highest frequency available when the cpu load is higher than the threshold set. Same thing when the load is lower than the min_threshold. The conservative governor takes all the available frequencies in the table and switches between them until the load is lower than the threshold. I've been thinking about it for quite a while and on our CPU I don't think this behavior is the best we can get.
Why? Well let's say we have 650MHz in our table as the maximum frequency. Staying on the same PLL, we would get something like: 176->352->518->537->556->576->595->614->633->652. Let's consider that the phone, while the screen is off, stays at 176 because there is no process that could put load on the cpu, which usually is true, depending on the user setup. When you unlock the screen, you might need a bit of power if you have an animated widget on the main screen. Let's consider that it also uses the internet to update its data and the cpu would be loaded under 80% only @576. In this case, the conservative governor will go from 176 to 576 like: 176-352-518-537-556-576. Remember that on each frequency the kernel will wait for a few us to check the load and then decide whether it needs to raise the frequency again or not, so it would take some time until the CPU can provide the power necessary to have a responsive phone. On the other hand, the ondemand governor would go straight to 652MHz(I forgot to mention that from 518MHz, all frequencies use the same voltage). But here comes the nice part(quote taken from the Ondemand governor data sheet):
the ondemand algorithm frequency down-scaling was changed to jump directly to the lowest frequency that can keep the CPU ~80% busy. This saves more power and enables the algorithm to go to right frequency in one hop
Click to expand...
Click to collapse
So after jumping straight to 652MHz, it will go directly to 576. So instead of 5 steps, the ondemand governor only does two. Of course, in theory, the ondemand governor would be inferior in battery consumption, but in real life it is not so bad, and from my calculations it can even be better. Keep in mind that the latencies are pretty much the same on both governors. The conservative governor is just a modified ondemand.
The conservative governor would be excellent on a Snapdragon device(or any other cpu >1GHz), which can provide good performance at lower speeds, so you'd not have to jump to the highest frequency available. But on our Hero, the difference between 514 and 534 for example is unsignificant if the load is intense, so this basically causes latency.
On small loads, the power consumption with the conservative governor is much better than using the ondemand governor.
How is the governor changing done?
SetCPU. You need to create a SCREEN OFF PROFILE - 19MHz-352MHz with the CONSERVATIVE Governor. Here's how it should look like:
{
"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"
}
Here is the frequency table the kernel is using in its default setting:
{ 0, 19200 },
{ 1, 176000 },
{ 2, 352000 },
{ 3, 518400 },
{ 4, 556000 },
{ 5, 576000 },
{ 6, 614400 },
{ 7, 652800 },
{ 8, CPUFREQ_TABLE_END },
Click to expand...
Click to collapse
As you have probably figured out, in screen-off mode the cpu can only go between 19-176-352. With the screen on, it has a wider choice, 352-518-556-576-614-652. I added more entries to the table(even though I always said this is not good) because I'm not using the default ondemand governor anymore. Now, if the load is >60%, it goes up. If the load is <70%, it goes down. IF the load is >90%, it goes to MAX and if the load is <20% it goes to MIN. This is very efficient and battery-friendly. It also changes very fast between steps, as I've done some other tweaks to improve latency.
Instructions:
Download the ZIP and flash it. Then, install SetCPU(if you don't have it already) and configure a profile as you've seen in the screenshot above. After that, you're good to go .
The most important features are:
- Ondemand CPU governor improved for efficient frequency jumps and usage optimization
- dual-CPU governor based on screen state
- kernel level touch input filtering(Ninpo)
- EXT2/3/4 and FAT support
- IPv6 support, including GRE and IP multicasting(see more info below)... Mobile IPv6 should also work in a proper enviroment not anymore in 109 and 113, I will bring it back in the next version
- dalvik and swap optimizations
- battery life enhancements
- Fair scheduler tweaked for better performance
Message for users: RaKern-113 works brilliantly with ChocolateEclair 2.0.
IPv6 info(good to read, but not available in the current version):
I do not own an IPv6 capable router, so I can not say exactly how it works, but I can tell you how it should behave. From what I could see, in this configuration, the IPv6 implementation is similar to the one in Windows Vista/7. IPv4 and IPv6 work together, but IPv6 is preferred. If it can obtain a global unicast address, it will attept to communicate via IPv6. Also, support for IPSec and 6-to-4 tunneling is enabled.
Until a get a dual-stack router, I can only help you with theoretical information. Maybe fellows in Japan can give me a bit of help with this?
Filesystem info:
I've added support for EXT3/4 because I know some people might find using those FSs useful. But for the avreage user, I suggest sticking with EXT2 as its successors use more cpu juice.
Feel free to include this kernel in your ROM. All that I require is that you do not change the kernel name/version, and post a link to this thread in your ROM description. Other than that, it would also be good for the community if you'd share your changes here. Whichever leads to improvement is appreciated.
So... To the important part:
RaKern-113 for ALL ROMS
MD5 sum: 3a1d07e6a2bcbdcb39330477e877ac81
SOURCES
If you appreciate my work, please consider helping Santa buy some presents
​

Reserved for future use.

Thanks RaduG,
Will definitely try this out on ChocolateEclair 2.0; you've done some amazing work on that ROM as it is.

Thanks. Please let me know how it works.

Any chance of you sharing the tweaks you found usefull?
github is the ideal platform for this, but you need to use it properly. If you just push "first commit" then it really does not help the development community....
In any case, good luck with your kernel, and hopefully soon, your ROM.

Well, it is the first commit, what should I say other than first commit... I will mark the further updates. Also, the main changes have been mentioned in the first post.
Thanks, good luck to you too

It is now hard to view the changes you made, and now we will have to diff it manually
Just for the next time, maybe you should first upload where you got it from (or fork?) then commit the changes.
Anyway.... good to have another kernel for the hero. Variation is good for the quality
ps. care to look at the .34 port of Elemag and see what is wrong?

It does not work on my Hero with Froyo (Elelinux - http://forum.xda-developers.com/showthread.php?t=767886) - force closes... well, everything on boot and reboots itself (boot-loop).

I don't know where I got it from, because I applied changes to the sources that I already had been working on before I left. I will have a look at Elemag's port after I finnish my next ROM.
@pushaty
Try to wipe dalvik-cache/cache, as I said in the first post.

RaduG said:
Try to wipe dalvik-cache/cache, as I said in the first post.
Click to expand...
Click to collapse
That's what I did, just after flashing Your ROM (before first boot). I've even wiped it again after first fail but 'no go'.
Edit
FYI (maybe this will be helpful), Flykernel is 'doing it's job' for me. Even 12pre2 (experimental) is running just fine.

Same here. Everything force closes on boot after a full wipe and a clean install of ChocolateEclair + this kernel.

I've flashed the exact same package and it works just fine. :-?

It does not work on my Hero with : CyanogenMod-6.1 for HTC Hero V6.1.0 .
I wiped dalvik-cache/cache, but not boot.

Just reinstalled everything without the kernel and going to see what happens when I flash it past the 'android.setup' process which is what prevented the phone from functioning last time.

RaduG said:
I've flashed the exact same package and it works just fine. :-?
Click to expand...
Click to collapse
Are You running Froyo or Eclair?

RaduG said:
Well, it is the first commit, what should I say other than first commit... I will mark the further updates. Also, the main changes have been mentioned in the first post.
Thanks, good luck to you too
Click to expand...
Click to collapse
Lets pretend, that I am a kernel developer and I want to learn/check/admire/criticize/improve/port/etc. your tweaks and developments. How am suppose to do this? The normal way is to check the commits in the github and their diffs, unfortunately in this kernels case, there are no commits for the tweaks. Look at almost any other kernel on github to see what I mean (mine, ninpo's, cyanogen's, Decad3nce's, etc.).
For example, in the case of this kernel and version, I would be very interested to know what are the code changes you did for these two items:
RaduG said:
- dalvik and swap optimizations
- battery life enhancements
Click to expand...
Click to collapse
Especially in the case of these two, having only the "first commit" in your github doesn't really tell me anything. I can download all your sources and do a full diff against mine, but I hope its clear why thats just crazy....
If you prefer to share your changes in some other way it will be very welcome. Of course if you choose to keep it only in this inconvenient way (which at least satisfies GPL I believe) its your right.
This will be my last post on the subject. I am sure that if you choose to share your knowledge, by github or otherwise, it will be beneficial to the entire community.

Doesn't work here either, running Cronos ROM Froyo.
logcat: http://pastebin.com/ag96BF2W
There is really something going on when Dexopting apps.apks.

I've got it to work now, but you have to boot at least once before flashing the kernel as it causes the 'android.setup' process to crash (at least with ChocolateEclair).

beachdemon said:
I've got it to work now, but you have to boot at least once before flashing the kernel as it causes the 'android.setup' process to crash (at least with ChocolateEclair).
Click to expand...
Click to collapse
IMO, that means something is wrong and it should be fixed asap.

I'll have a look at it. Thanks for reporting.

[Q] Check CPU speeds

I'm kinda new at the whole flashing kernel thing. i just downloaded and flashed the Tiamat_Evo (v4.0.6) on my GB 2.3.3 with CyanogenMad-7.0.3.1.
What are the ways to check the max/min speeds now and what are recommend ranges for long battery life and or fast performance on the EVO
+1 in advance

There's an app called CPU Spy Beta out...I couldn't find it in the market. Try Google...they seem to have everything. I'm underclocked with interactiveX 128/768. Runs great on battery with freedom kernal
HTC EVO 4G running MIKG 2.45

slimno19 said:
There's an app called CPU Spy Beta out...I couldn't find it in the market. Try Google...they seem to have everything. I'm underclocked with interactiveX 128/768. Runs great on battery with freedom kernal
HTC EVO 4G running MIKG 2.45
Click to expand...
Click to collapse
is this it?
https://market.android.com/details?id=com.bvalosek.cpuspy

If you use Setcpu to set frequencies it also has a feature that does the same thing. Go to the info tab then select time in state. Tells you everything that app does and more.
Sent from my PC36100 using Tapatalk

Cm7 has a built in CPU setting.
Settings - cyanogenmod settings - performance - CPU settings
I run min 128 Max 614, still speedy no reboots (unless I undervolt too much)
Also check out vipermod, it was designed around the tiamat kernel to allow you to change the voltages to your CPU. This also helps battery life!
Sent by Supersonic!

imheroldman said:
Cm7 has a built in CPU setting.
Settings - cyanogenmod settings - performance - CPU settings
I run min 128 Max 614, still speedy no reboots (unless I undervolt too much)
Also check out vipermod, it was designed around the tiamat kernel to allow you to change the voltages to your CPU. This also helps battery life!
Sent by Supersonic!
Click to expand...
Click to collapse
I'm undervolted by 100 and I get get more and more battery life the longer I condition my battery. I'm also set at min 691 and max 921
The more that your phone spends time that it's switching clock speeds (drastic changes) seems like a waste of power.

imheroldman said:
Cm7 has a built in CPU setting.
Settings - cyanogenmod settings - performance - CPU settings
I run min 128 Max 614, still speedy no reboots (unless I undervolt too much)
Also check out vipermod, it was designed around the tiamat kernel to allow you to change the voltages to your CPU. This also helps battery life!
Sent by Supersonic!
Click to expand...
Click to collapse
Awesome, ill try that. is it best to reboot after applying the new settings?

If you just changed clock frequencies then no need to reboot as It's done on the fly. If you change voltages then you need to reboot. Vipermod is an excellent script. I have used it on sense kernels even though it wasn't made for them.
After looking closer at the vipermod script it doesn't say a reboot is required unless going back to factory defaults.
Sent from my PC36100 using Tapatalk

@civicboy, no real need to reboot, make sure the settings don't cause your phone to reboot on its own before checking set at boot. Same goes for undervolting, and, you are more likely to get reboots with undervolting. I have seen peoples phones that wont accept any undervolting... be cautious... do it in 25mv increments to find what your phone can handle... have the reset file on your sdcard at all times. Sounds scary but its really not that bad once you figure it out.
Check back with your results or if you need more info.
Sent by Supersonic!

imheroldman said:
@civicboy, no real need to reboot, make sure the settings don't cause your phone to reboot on its own before checking set at boot. Same goes for undervolting, and, you are more likely to get reboots with undervolting. I have seen peoples phones that wont accept any undervolting... be cautious... do it in 25mv increments to find what your phone can handle... have the reset file on your sdcard at all times. Sounds scary but its really not that bad once you figure it out.
Check back with your results or if you need more info.
Sent by Supersonic!
Click to expand...
Click to collapse
here are my values. i went down to 100, however, i dont know what the factory values are so I cant confirm that it worked, or that the values stuck after reboot
Can anyone confirm by looking at these numbers?
{
"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"
}

those numbers look too high. after you changed the value, did you enter "10" to save the changes and re-write to the init.d file?

alaman68 said:
those numbers look too high. after you changed the value, did you enter "10" to save the changes and re-write to the init.d file?
Click to expand...
Click to collapse
probably not, since i cant say yes right away lol
EDIT: I am just going to reset to factory, do the reboot, and start over.... making sure i save changes

Why am I getting this error at the bottom of the screen?
[/IMG]

Are you typing SU before you start vipermod? You have to give TU root for vipermod to work.

I think i got it figured out. i reflashed and restarted process and works great now, keeping all values. i went down -50. dont want to push my luck. Thanks for all the help!

Be sure to get vipers zip for reseting to default. This allows you to push the voltages and if you get boot looping you can just flash the reset from recovery.
And I gave you a "thanks" for actually thanking those that help out.

BuddaBelly said:
Be sure to get vipers zip for reseting to default. This allows you to push the voltages and if you get boot looping you can just flash the reset from recovery.
And I gave you a "thanks" for actually thanking those that help out.
Click to expand...
Click to collapse
lol awesome. thanks man.
You are talking about the original zip file right? can i just creat a folder called vipermod and store it in that incase of emergency?

ha, i was going to pop his "thanks" cherry too.
there is restore defaults .zip you can flash. Put it on your sd for safe keeping wherever you like and remember.
Terminal emulator is fun to learn too

alaman68 said:
ha, i was going to pop his "thanks" cherry too.
there is restore defaults .zip you can flash. Put it on your sd for safe keeping wherever you like and remember.
Terminal emulator is fun to learn too
Click to expand...
Click to collapse
Where can i get that?

http://bit.ly/nNN1P6
That's the file you need. Just put it on the root of the sdcard or wherever you know it's at and if you get into trouble going to crazy on voltages just flash it from recovery. It will reset your voltages back to defaults.

Performance governor

Anyone run this?

The only real reason to run performance governor is for benchmark testing. I wouldn't run it any more than that.
Sent from my SPH-D710 using XDA

g_ding84 said:
The only real reason to run performance governor is for benchmark testing. I wouldn't run it any more than that.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Most use it that way, as for me i use to keep the high end freq set and to keep the cpu from cycling and wasting battery
Example.... i like to run at 800, i set to preformance so the phone will not cycle lower then 800 no matter what.

Unknown Zone said:
Most use it that way, as for me i use to keep the high end freq set and to keep the cpu from cycling and wasting battery
Example.... i like to run at 800, i set to preformance so the phone will not cycle lower then 800 no matter what.
Click to expand...
Click to collapse
Battery life difference?

donsh00tmesanta said:
Battery life difference?
Click to expand...
Click to collapse
it might be small but little things add up ........instead of bouncing/cycling up and down from low to high freqs cause it is monitoring the processes/work load even when the phone is not in use. Performance takes the cycling/monitoring of the processes out of the equation and just sets the cpu at the high end.

its weird in set CPU it shows it going to 800mhz instead of staying at 1200mhz
Bug? Glitch?

donsh00tmesanta said:
its weird in set CPU it shows it going to 800mhz instead of staying at 1200mhz
Bug? Glitch?
Click to expand...
Click to collapse
It could be, I use "System Tuner Pro" and when I select "Performance" it stays at 800, since 800 is what I have my high end set at.
Btw I am running EL29 GB with Gunslinger so that is also something to consider.
Edit: I tried different high end freq on performance 1k/1.2k/1.4k and they all were setting and not fluxing to other fregs.

{
"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"
}

I running rh13

interesting try the free version of system tuner and see if it will stick

Done I'll check in a bit

Same thing

weird, r u running stock? since i only saw 1200 on your high end. btw i am waiting for work that is why I am up.... lol
---------- Post added at 05:55 AM ---------- Previous post was at 05:49 AM ----------
i was going to say try a ics overclock kernel but is there any? maybe the stock kernel does not have a performance governor built in
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
maybe the stock kernel does not have a performance governor built in

Try agats 4.5 or the kuban kernel. They have the over clocking steps built in.
Sent from my SPH-D710 using XDA

I'm stock but tried others

donsh00tmesanta said:
I'm stock but tried others
Click to expand...
Click to collapse
Try wiping the cache and dalvik before you try the kernels that g_ding stated.
agats or kuban should stick on performance if they still dont....I really dont know what to tell you any more to help.....
g_ding84 said:
Try agats 4.5 or the kuban kernel. They have the over clocking steps built in.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Thanks I knew there were some ICS overclock kernels , I am on GB so I dont look/have ICS stuff.

Unknown Zone said:
Try wiping the cache and dalvik before you try the kernels that g_ding stated.
agats or kuban should stick on performance if they still dont....I really dont know what to tell you any more to help.....
Thanks I knew there were some ICS overclock kernels , I am on GB so I dont look/have ICS stuff.
Click to expand...
Click to collapse
I always wipe twice
They stick to performance but they down clock to 800mhz not stay at 1200

donsh00tmesanta said:
I always wipe twice
They stick to performance but they down clock to 800mhz not stay at 1200
Click to expand...
Click to collapse
I'm on voltage control. And both kernels show proper scaling and on performance I have it stick to 1200mhz. Do you have CPU spy?
Sent from my SPH-D710 using XDA

donsh00tmesanta said:
I always wipe twice
They stick to performance but they down clock to 800mhz not stay at 1200
Click to expand...
Click to collapse
You've been using SetCPU and now apparently System Tuner Pro. It's possible you may have EX Tweaks installed as well, ROM Toolbox Pro, or Tegrak.
The thing you want to remember, is that any and all of these utilities can set CPU performance and governors, so you want to be sure that if you are testing with any of them, that ALL of the others are disabled (at least the functions that would control CPU).
That said, I wouldn't be surprised if it's not a kernel issue. You might have Stock, but it may have been modified or not compatible w/OC/UC. Try one of Agat's kernels with confirmed working overclock/underclock (0.4.4) http://forum.xda-developers.com/showthread.php?t=1767421
I've been using that with SetCPU and it works well.
Oh - one last point -- do you have any Profiles set up in SetCPU? Because if you do, one of them might be overriding your Performance governor setting on the Main SetCPU screen.

Capp5050 said:
You've been using SetCPU and now apparently System Tuner Pro. It's possible you may have EX Tweaks installed as well, ROM Toolbox Pro, or Tegrak.
The thing you want to remember, is that any and all of these utilities can set CPU performance and governors, so you want to be sure that if you are testing with any of them, that ALL of the others are disabled (at least the functions that would control CPU).
That said, I wouldn't be surprised if it's not a kernel issue. You might have Stock, but it may have been modified or not compatible w/OC/UC. Try one of Agat's kernels with confirmed working overclock/underclock (0.4.4) http://forum.xda-developers.com/showthread.php?t=1767421
I've been using that with SetCPU and it works well.
Oh - one last point -- do you have any Profiles set up in SetCPU? Because if you do, one of them might be overriding your Performance governor setting on the Main SetCPU screen.
Click to expand...
Click to collapse
i uninstalled set cpu before using system tuner
i have been using stock, kuban kernel and 4.0 to 4.4 of agats kernels all same issue
zero profiles

cpu cores does not go offline, never satys at low frequencie

Hi.
i'm on stock 4.4.3, s-off+root and stock kernel+recovery.
i want it to scale the cpu from 300 to 1900 of even 1700 to save battery and to keep it cooler.i dont like the power saver option of htc because its to slow for daily use.
no matter what app i try use to control the cpu, i can see it will not stick to low cpu frequencies.its always jumping around the 900+ ghz ,sometimes it will go to 300 mhz, but will go higher again afetr few seconds and the cpus never goes offline.i have tried SETCPU, TRICKSTER,CPU CONTROL, KERNEL TUNER.
i have read that HTC uses PERFLOCK.could it be responsible for that? anyway to bypass it if so?
setcpu has a trick to bypass this, but its not working under the htc one m8.
any way to change the frequencies of the htc's built in power saver?
thanks.

Perhaps the stock kernel can't be adjusted?
Have you tried a custom kernel?

I don't want to switch kernel for now. I prefer to have complete stock.

Then as I said, it may not be possible. On most other devices I've used, altering frequencies on stock kernel is a no go.

It can be adjusted on the higher end, it won't pass the frequency I have set as max. And it does go sometimes to the 300*i have set as min. The only thing annoying is that bouncing around 1000ghz allot.
The device is way too active on idle use. I came from Galaxy s2 and the cpu over stick to lowest possible frequency when the device is idle.
So something is wrong here and I can't pinpoint it.
All the bloatware is disabled, I use manual sync, no Google location and history reporting, no wifi scanning in the background . I have no strage wakelocks and alarms in bed. I even made a factory reset.
So what could lead to this strange behavior?

K-a-M-u-Z-u said:
It can be adjusted on the higher end, it won't pass the frequency I have set as max. And it does go sometimes to the 300*i have set as min. The only thing annoying is that bouncing around 1000ghz allot.
The device is way too active on idle use. I came from Galaxy s2 and the cpu over stick to lowest possible frequency when the device is idle.
So something is wrong here and I can't pinpoint it.
All the bloatware is disabled, I use manual sync, no Google location and history reporting, no wifi scanning in the background . I have no strage wakelocks and alarms in bed. I even made a factory reset.
So what could lead to this strange behavior?
Click to expand...
Click to collapse
What governor is set?
If you take the powersave governor (which is most likely not included in the stock kernel), your cpu clock won't scale up that often.
If you want decent battery life, you'd go with ondemand or interactive. I suppose that those are included in the stock kernel.
Kernels like lionhearth scale a lot more often, which gives better performance when needed at the cost of a little battery power.
I would check it myself, to be sure, but I'll only have my device next Tuesday. So I have no idea about what governors are included in the stock kernel.

Yeah, all your issues would be solved with a custom kernel.
The stock one basically is what it is. No one will be able to give you much more help than that I doubt.
But, maybe I'm wrong. ?

Warhoax said:
What governor is set?
If you take the powersave governor (which is most likely not included in the stock kernel), your cpu clock won't scale up that often.
If you want decent battery life, you'd go with ondemand or interactive. I suppose that those are included in the stock kernel.
Kernels like lionhearth scale a lot more often, which gives better performance when needed at the cost of a little battery power.
I would check it myself, to be sure, but I'll only have my device next Tuesday. So I have no idea about what governors are included in the stock kernel.
Click to expand...
Click to collapse
Powersave governor will not help. This governor will only set the device to the lower frequency. The exact opposite of performance governor.
I'm using ondemand. The rest are :
{
"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"
}
I know that interactive allows the spend more time on higher frequencies than ondemand.
Conservative also show erratic behavior.
You meantuned lionheart kernel. I know only one custom kernel for htc one you, Elementalx.

Same issue here.
I think stock kernel can switch cores offline; I think I did it once; but that day, I did several mistakes, and in the end the phone was unusable.
---------- Post added at 03:03 AM ---------- Previous post was at 02:46 AM ----------
Can do it for sure: installed
https://play.google.com/store/apps/details?id=com.mugich.cpumulticorecontrol
and after playing a bit, I now got core 3 always disabled. I was in OnDemand, and Interactive seems better for me for now. Cores more often at 300MHz, and phone remains fluent. I had tried Powersave this morning, and I could not even write an SMS; tapping each letter was taking more than 1s, and entering numbers was taking 5s.