Using Droid with Droidmod 1.0. I just updated to the newest version and for some reason when i have my profiles on.It sets it to max of 384 and min of 250. The lowest max i have set in my profiles is 600 so how can it show max is 384.
I know this is something real easy.
Of course using auto-detect set on boot checked on-demand (main screen) on-demand (profiles) max on all profiles is set to 600 min 250.
I am using Nexbeast 1.0 and I have installed setcpu and advanced task manager. I hear that it messes up somehow but I haven't noticed any problems. In fact before I installed setcpu my phone kept on restarting due to overheating. Am i messing my phone up in a way I can't detect? Any clarification on this issue would be great.
I just rooted my droid to Liquid froyo 1.6. Everything is smooth except for SetCPU, it doesn't want to do anything for me. I made a widget, and whenever I try to change my speed, overclock or underclock it force closes, it won't let me do anything.
I downloaded and installed Bekit's 1GHz kernel and by default on SetCPU it shows it running at 1000MHz and such.But when I open SetCPU, it shows the bar maxed out at 528MHz with the Min at 245Mhz. And if I try and change it, it reverts the cpu back to 528MHz.I'm going to try another kernel (I checked to make sure I was in fact running Bekit's 1GHz kernel in the about phone), but can anyone explain this?long bench was 762ms, so I'm apt to think it's something with the display and that I am in fact overclocking correctly, yes? UPDATE: Sorry all I just uninstalled and reinstalled SetCPU and this corrected the discrepancy.
I finally rooted my phone, and put froyo on with flash. works great. Now i want to overclock as well. What do you use for overclocking the cpu speed?? I've seen setcpu referenced...are there any alternatives??? Thanks!
New to rooting and just got myself setCPU. I was wondering what some standard profiles that people use to maximize performance and battery life. So far I have it set to underclock when the screen is off and when less than a certain battery percentage. What temperature should I be looking at as "dangerous" to set my cpu to underclock then as well? Any other recommended profiles?
What is your guy's sampling rate on setcpu? It comes standard as 46875.. This is what it means if you don't know what it means.Sampling Rate is defined in microseconds. The lower this value, the more responsive the CPU will be in scaling its speed up or down. However, a lower sampling rate will also negatively impact overall performance.
The Sampling Rate, Threshold, etc. What do they mean and what are some optimal settings? I have mine untouched from whatever was stock with the app. Just curious if these settings were worth messing with unless you were advanced user, much like the settings themselves.
Alright, so I've rooted using DroidMod (right, I know, easy way out, I was too afraid of bricking it doing it the hard way) and I've installed SetCPU, but for some reason, it will only let me clock up to 600mHz.Any ideas?
Any D1 using this app? Seems like you can set the speed anywhere from 250Mhz to 1Ghz and you can also tell it have different range when screen is off. Is this accurate and how does this compare to SetCPU? OverclockWidget (Need Root)
Anyone using SetCPU to enforce underclocking profiles with their X? I'm concerned about how hot the X gets when it's charging in the car dock and using Navigation. Would downclocking the cpu to 800MHz or 600MHz when the battery is above a certain temp (45C or so) make a difference? Has anyone noticed any battery gains from using other profiles?
I just bought SetCPU last night, and ever since installing it, I've had issues with sending and recieving txt messages, for example, I'll have 3-4 bars of 3G and the txt will either not send out, or if someone sends me a txt, I'll get about 3 all at once from them. Maybe its just how I have setcpu setup, I let the app decide best speed for my phone 900max 250 min, and I set it on interactive at first, then changed it to performance to see if that made a difference with txts.
I just rooted today and downloaded Bugless Beast V1.0 ROM as well as the kernel that allows for overclocking up to 1Ghz. I'm playing around with SetCPU and wondering if anyone has any suggestions for the min/max settings within the profile. I don't want to fry my phone, so if there's someone with experience with a kernel with similar capabilities who would be so kind as to share his profile settings.
Now I have Juice Defender on my phone. It's running with the battery lasting 2x as much. Now, I have finally rooted my phone and now I use setCPU and AutoKiller on Optimized. Is it worth it to have Juice Defender?
The SetCpu suddenly stop working with my Droid X 2.2 OTA. So I decided to troubleshooting by clearing the data, clearing the cache, uninstalling, reinstalling, un-rooting the device and re-rooting the device. I'm able to get other "Rooted Apps" to recognize permission ,but SetCpu wont even ask for permission during the installation process after picking "Auto Recommend". After "Auto Recommend" it just goes into the app and all I can see is a blank black screen. I'm able to launch the widget app once in a while but it seems like the program is working in the background. I have emailed the dev about this rare problem and sent him some logcat one being the installation process and the other one is adding the widget to the home-screen and then launching the app through the widget. I'll be including those attachment if someone with android code skills willing to help me solve this problem. Edit: I did a titanium backup of SetCpu when it was working fine 10/6/10. I did both the app +data restoration and on restart of the device it is able to ask for root permision and it shows the SetCpu bar notification icon. This tells me that the app is working in the background but when I launch it up all I'm able to see is a black screen.
Anyone else download the new setcpu and when you charge your phone and then remove it, it stays stuck in the charge profile? I upgraded to the newest version tonight and I'm running on the new smoked glass 5.0.1 rom (I was using setcpu 1.4.6 and just did a market upgrade).