Daemon Controller on Sense ROMs - Nexus One Q&A, Help & Troubleshooting

Hi All,
- I am seeing an issue with Daemon Controller used in almost all of the latest Sense ROMs for Nexus One.
- I kind of know that my Nexus One becomes sluggish on over clocking. I have seen that it works fine when min = 245 MHz and max = 998 MHz.
- So when I set these values in Daemon controller, it accepts these values. But when I restart the phone these values are reset to default ones of min = 125 MHz and max = 1113.6 MHz.
- I then installed an application called CPUSpy from market. This shows the time spend by CPU in all the possible frequency states. It always shows that my maximum frequency is 1113.6 MHz when I know I have set it to 998 MHz in Daemon controller.
- I have seen this issue on Hypersense, Runneymede etc. I do not see such a thing happening on eVil's Desire HD port. The difference between these ROMs is eVil's ROM does not have Daemon Controller.
- One more thing common to all the latest Sense ROMs is, they use dbasabe's Sense kernel. So I am not sure if this issue is caused due to kernel or the Daemon Controller application is to be blamed here.
Can experienced folks please shed some light on this issue?

I would like to know how to set the a lower clock speed too, as it is a little bit hot.......

chota_shivaji said:
Hi All,
- I am seeing an issue with Daemon Controller used in almost all of the latest Sense ROMs for Nexus One.
- I kind of know that my Nexus One becomes sluggish on over clocking. I have seen that it works fine when min = 245 MHz and max = 998 MHz.
- So when I set these values in Daemon controller, it accepts these values. But when I restart the phone these values are reset to default ones of min = 125 MHz and max = 1113.6 MHz.
- I then installed an application called CPUSpy from market. This shows the time spend by CPU in all the possible frequency states. It always shows that my maximum frequency is 1113.6 MHz when I know I have set it to 998 MHz in Daemon controller.
- I have seen this issue on Hypersense, Runneymede etc. I do not see such a thing happening on eVil's Desire HD port. The difference between these ROMs is eVil's ROM does not have Daemon Controller.
- One more thing common to all the latest Sense ROMs is, they use dbasabe's Sense kernel. So I am not sure if this issue is caused due to kernel or the Daemon Controller application is to be blamed here.
Can experienced folks please shed some light on this issue?
Click to expand...
Click to collapse
Hi All,
This thread had almost ~200 views but only 1 reply. I sincerely request to all the knowledgeable folks here to shed some light on the query in this thread. Its because of my phone getting sluggish on over clocking, I cannot use latest sense ROMs for longer times. Hope to get some positive output out of this thread.
Thanks in advance for your time and comments.

Finally I found the solution in a reply inside hypersense 3.0.
I use the app "setcpu", in the first page of the app activate settings and choose preflock disabler, after that the clock can be down back to 1GHz.
Hopes it helps.

Related

New(Free) Overclocking App(works for Haykuro)

I wrote an overclocking app today that will become opensource as soon as I put the source online(lol). This is confirmed to work on at least Haykuro's 5.0.1G ROM. Allows setting custom min and max cpu frequency. Enjoy . (Thanks buttkicker for this idea)
And the source code is now live on googlecode.
site is: http://code.google.com/p/openoverclocker/
UPDATE: New version up. Everything is now working and tested on both JF and Haykuro. Will continue to set clock even after reboot, so enjoy!
[email protected] said:
I wrote an overclocking app today that will become opensource as soon as I put the source online(lol). This is confirmed to work on at least Haykuro's 5.0.1G ROM. Allows setting custom min and max cpu frequency. Currently gets reset on restart but will fix that soon as well. Enjoy . (Thanks buttkicker for this idea)
Click to expand...
Click to collapse
Nice Marcus! Just downloaded it from the marketplace, and it works! I don't mind the reset after restart because honestly, how often do we restart our phones? Confirmed working on 5.0G (apps to sd) as well. go poly! =]
Question: would it harm the phone to set min and max to 528?
wow, it works fine. thank you. its pretty fast
it doesn't seem to work in the H version
Hmm darn no go on H eh? Lol I'll have to wait till someone figures out how to overclock that one and then incorperate it.
Perrosky said:
it doesn't seem to work in the H version
Click to expand...
Click to collapse
I am running 5.0.2H, and it should work.
[email protected], are you doing anything different in the app?
Hmm no, not really. Except that I'm saving the values in files and then cat-ing them out to the frequency files. Perrosky, did you set a different minimum? It will scale between them so it might not run at max when you look at /proc/cpuinfo
seems to work fine with my G1. is this actually overclocking or just clocking the processor to its max.
jaboswell said:
seems to work fine with my G1. is this actually overclocking or just clocking the processor to its max.
Click to expand...
Click to collapse
As I understand it, the G1 has a scalable 512 MHz processor, so this is clocking it to it's max specs.
testing567 said:
As I understand it, the G1 has a scalable 512 MHz processor, so this is clocking it to it's max specs.
Click to expand...
Click to collapse
Thats what I thought, was reading it somewhere but couldnt remember so I just asked..
well some programs seem to run faster, but that could just be me.. i ran cat /proc/cpuinfo and got a speed of 383.38...i have it set to min 384 max 524 even tried 512 as max..when i run some programs it seems faster than before..but when i run term. emu to get speed it resets the app to 384 max. 248 min.
I got the 5.0.1H...
and I don't think it works for me too...
how to check ? If I set Max to 528 MIN 248 and click "apply" nothing happen
if I set MAX/MIN both 528.. phone hang/crash
victortung said:
I got the 5.0.1H...
and I don't think it works for me too...
how to check ? If I set Max to 528 MIN 248 and click "apply" nothing happen
if I set MAX/MIN both 528.. phone hang/crash
Click to expand...
Click to collapse
Hmm interesting on the phone hanging. For the 528 max and 248 min the phone will run faster when taxed but will run the same at low points. Maybe try 528 max and 400 min and then see what "cat /proc/cpuinfo" says? If it says anything over 348 then you're already over what the normal maximum is
jaboswell said:
Thats what I thought, was reading it somewhere but couldnt remember so I just asked..
well some programs seem to run faster, but that could just be me.. i ran cat /proc/cpuinfo and got a speed of 383.38...i have it set to min 384 max 524 even tried 512 as max..when i run some programs it seems faster than before..but when i run term. emu to get speed it resets the app to 384 max. 248 min.
Click to expand...
Click to collapse
App always resets to 384 max and 248 min, I hardcoded those in. Next revision should support loading the actual speed and remembering what you put last.
After reboot, sometimes it hangs while requesting superuser access, then crashes.
Doesn't seem very different thus far. Any way to benchmark it?
I guess we'll find out if our battery life shortens.
Edit: Nevermind... I found my answer in this thread.
Saw this last night during my nightly before-I-sleep market app search.
Thanks!
[email protected] said:
Hmm no, not really. Except that I'm saving the values in files and then cat-ing them out to the frequency files. Perrosky, did you set a different minimum? It will scale between them so it might not run at max when you look at /proc/cpuinfo
Click to expand...
Click to collapse
sorry for my late post, I set the min at 328 and max at 500 I hit apply and the overclock apk just stay still, then when I use the Terminal to see the speed I show 258
Perrosky said:
sorry for my late post, I set the min at 328 and max at 500 I hit apply and the overclock apk just stay still, then when I use the Terminal to see the speed I show 258
Click to expand...
Click to collapse
Do you have the superuser whitelist app installed.
You will need that.
Not sure, but since the cpu is scaling, the terminal or other program would show the current cpu usage when it reads and display it.
So, if you're not doing anything in the OS, the readout would be near the low-end, when you check the freq.
I tried the software, but I wish it had a button to monitor or show the cpu mhz somewhere.
clspdhax1 said:
Not sure, but since the cpu is scaling, the terminal or other program would show the current cpu usage when it reads and display it.
So, if you're not doing anything in the OS, the readout would be near the low-end, when you check the freq.
I tried the software, but I wish it had a button to monitor or show the cpu mhz somewhere.
Click to expand...
Click to collapse
That will be in the next version. That's why it says MHz at the top, planning on putting the number there but gonna have to do some parsing of /proc/cpuinfo... somehow...

overclock widget

worked great for a while then kept force closeing anyone haveing problems??
It seems to be working fine for me. One thing is that when I set the clock to 128 or something, the status displayed on the widget still shows 527. The performance is significantly slowed so I assume it's doing it's job.
Overall I think it's a nice little widget. Great for maxing out performance, and maxing battery life by limiting performance.
Phone:
Black G1
JF 1.51
Yup...me too
I will make the change but it sometimes does not refresh the gui. It will also not work if you reboot. (if i remember correctly) also tons of force closes. I am on 6.01 and have tried JF1.5 and am curently on HERO but have not had success with the widgets on the build yet so I dont have a confirmation.
Could someone post the previous version of this app please? The updated version on the market shows "problem loading gadget" on the Hero rom when you add it to the screen..previous versions worked without any problems. Thanks in advance.
edit: nm..fixed it..just had to run the odex optimization script and all is good again
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
what is a good configeration for over clock..i dotn want to mess up my phone??
I was thinking the same and should I have it on always max. Or what?
I've got mine set to 128Mhz min and 527Mhz max, it has drastically increased my battery life. Batter life barely drops 1% overnight.
Anyone have the Version before the 1.7 update. The new update doesnt seem to work on hero w/ Rosie.
You can grab the 1.6 apk from the Dev's Google Site (check the Files section).
1.7 doesn't work with Ion for me either
zgmf-x322a said:
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
Click to expand...
Click to collapse
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
IronCross1788 said:
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
Click to expand...
Click to collapse
The creator of the original Overclock app hasn't updated his application for even Cupcake build support yet. I thought he removed it from the market.
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yeah NeoBlade (thanks!) gave me the tip on that one yesterday. Seems to be helping a ton.
Min384Max527
Screen off Min128Max245
I can't find Overclock Widget in Market, was it removed?
I have the Overclock Widget and my question is, is it bad for my phone that while my screen is on i have it a min 527 max 527 then while screen off min 128 max 245... I've noticed that phone charges last longer but the useage of going back and forth determental to the phone? Thanks
coolbho3000 said:
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
Click to expand...
Click to collapse
Thanks, that would be of great help. Specially the battery profile settings. If you could also put a monitor, be it a widget or something on the notification bar it would be beyond awesome, or maybe a just notification of when the speed is changed and to what it was changed to.
Does anyobdy know if this SETCPU works on Hero ?
And must the app be on after i set the clock or can i close the app after ?
*bump* need to know

[Q] TriNiTy SensationXL V 5.0 Final - Random FC/Reboot?

I've just updated to Trinity v 5.0, but my phone keeps rebooting itself after scrolling the homescreens. I flashed the 1 GHz script and changed the Kernel to Unity v10, now it's back to normal again without reboots.
Does anyone know why this is happening? No one else on Trinity's thread seems to have this problem...
Your CPU cannot handle anything more than 1GHz. That's probably the thing that caused the reboot.
Not all CPU can handle >1GHz due to the nature of the manufacturing process of the CPU, so you are a bit unlucky to get the CPU that can only run 1 GHz max, still its still satisfy what it says on the spec..
wpra3 said:
Your CPU cannot handle anything more than 1GHz. That's probably the thing that caused the reboot.
Not all CPU can handle >1GHz due to the nature of the manufacturing process of the CPU, so you are a bit unlucky to get the CPU that can only run 1 GHz max, still its still satisfy what it says on the spec..
Click to expand...
Click to collapse
Thanks, that's what I thought. But it's only after I flashed the Unity v10 kernel then it would stop rebooting. Is it because the Ruslik kernel that comes with it is custom made for OC? Should I go to Tweaks now and remove OC Daemon then?
I think the Ruslik kernel comes with OC, therefore it reboots every time, just try to make it to 1GHz it should work, if not its probably kernel bug. And you don't have to remove the OC daemon after, just set it to 1GHz and you are good to go.
In TriNiTy SensationXL 4.5 i have a reboot bug in FBReader. If i won't touch the screen for some time the phone will reboot. And in 5.0 final version i have force close in FIFA 12. Anyone else has this problem?

CM10 underclocking with Stock kernel broken?

Hello XDA-Members
I wanna ask around if someone of you is experiencing the same bug when trying to underclock the SGS on CM10-Nightlies...
The first time i experienced this bug was on 20120820 - I tried to set the max freq to 800 Mhz and saw instantly the bootanimation.
The second time was today with 20120826 - when i choose max freq 800 mhz in the system settings, the hole SGS freezes. only the backlight of hardware keys shows response.
The Nightlies in between i couldn't test.
Everything is stock. Checked the md5 of the downloaded zips. No apps installed. All okay. This bug is annoying Even if nearly nobody would underclock this phone because of the "butter" in CM10...
Cheers

[Q]the cpu ignores max/min values

Hello all,
so in the effort to make my O4X last like a normal smartphone when not in use iv'e rooted it,unlocked the b/l and flashed custom kerenal.
i did managed to go from an avg. -10%/hr battery drain to 5%/hr but still even if i dont use the phone it will go down alot.
i've tried setcpu,trickster,no frills cpu and none of them could really keep the cpu in the freq. i want. it shos sucess in appling the values but then it jumps below and above the value's iv'e set.
what can be done?
thank you
Have you tried no-frills cpu setting to prevent system for making changes to the cpu frequences?
Yes.. Still not sticking and ignore the freq. I set
@genia.m which kernel are you using ?
Currently I'm on the latest Werewolfjb.
It happened with stock kerenal too..
Might be the rom's fault?
Well it can be, I believe it is the kernel but still, try to change your rom to one which has been reported to not having the baseband wakelock and similar wakelocks . It is the Nvidia Tegra 3 which overrides the definitions and sets them to default. It used to happen with me in stock and on cm too, but I changed to another stock rom , a modified one, and is working like a charm, no stupid wakes.
Try and post the result if you want !

Categories

Resources