-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [APP] QuickClock Overclock Assistant
- Thread starter Airmaxx23
- Start date
-
- Tags
- motorola droid x
Gotcha. No worries
Regarding your BMV, though, I'm wondering what the auto-finder spit back for it. Any luck with that?
Also, I'm in the midst of recoding the BMV auto-finder to be a bit more transparent in what it's doing. Should be a decent improvement.
Sa-weet. I may check that out nonetheless, since that would be great to just pick that off of each phone. Thanks for the info, FreeWELL!
pmforester
Newbie
So I've been playing around with this App and JRummy's OC. When I calculate my values with Quick Clock Advanced this is what I get.
BMF - 300
BMV - 16
SB - 13
24 - 400
38 - 700
48 - 900
60 - 1150
I apply these numbers in OC and run a game like Angry Birds my DX hangs and reboots. So I start tweaking my low end value up and I still get hangs. All the way to 27.
What should I be adjusting to get better stability? My OC speed or my vsels? Where do I go from here?
Thanks!
BMF - 300
BMV - 16
SB - 13
24 - 400
38 - 700
48 - 900
60 - 1150
I apply these numbers in OC and run a game like Angry Birds my DX hangs and reboots. So I start tweaking my low end value up and I still get hangs. All the way to 27.
What should I be adjusting to get better stability? My OC speed or my vsels? Where do I go from here?
Thanks!
Try increasing the stability buffer. Should be the quickest route to increasing all VSELs in the appropriate proportions.
***A note regarding the auto VSEL finder: I worked through the night on it, and I think it's significantly improved. Still a lot more I want in this next version, though, so no market update just yet.
Hey folks,
I just uploaded an update to the market, so make sure you check it out.
Two major updates:
1) You can now load the OC module from within the app. I was avoiding doing this so that full credit for the modle would be given to Tiago and the Milestone Overclock Project, but I've found it is simply too annoying having to switch between apps. I talked to Tiago about it and put in a statement about the module (per his suggestion) as a toast notification whenever it is loaded. I hope that people read it and understand that overclocking on the Droid X etc would be impossible without the work put in to the Milestone Overclock Project.
2) I rewrote the auto BMV finder from scratch. It is now cancelable and will display exactly what it's doing at any given moment. In my testing, there is an error range of 1 VSEL. For me, though, it always errs on the side of stability. i.e. If it is off by 1, it tells you the BMV is 1 higher than it actually is. It seems the reason this happens is due to how the system handles crashes. Though the lowest possible BMV does get set to the app's shared settings xml file, when the phone reboots it might load with a less recent BMV. I've tried desperately to improve upon this, but it seems impossible. It's still 100 times easier than doing it yourself, though, and I think it's fine as long as it errs on the side of stability.
Here are the the recent changes as well as upcoming changes copied from the market description:
Load module within QuickClock
- No need to switch apps!
Rewrote BMV-finder from scratch
- Cancelable
- Displays status throughout process
- Keeps screen alive while testing
*Working On*
Advanced Menu
- control every CPU parameter
- set on boot
- export profile to other OC apps
- write setscaling script
Top-End Finder
- assistant to help determine max speed
Better UI
- Display of current freq's & vsel's on main menu
- aesthetic improvements
As always, I am ever-grateful to all who use my app and even more grateful to those who provide feedback.
Peace,
Paul
I just uploaded an update to the market, so make sure you check it out.
Two major updates:
1) You can now load the OC module from within the app. I was avoiding doing this so that full credit for the modle would be given to Tiago and the Milestone Overclock Project, but I've found it is simply too annoying having to switch between apps. I talked to Tiago about it and put in a statement about the module (per his suggestion) as a toast notification whenever it is loaded. I hope that people read it and understand that overclocking on the Droid X etc would be impossible without the work put in to the Milestone Overclock Project.
2) I rewrote the auto BMV finder from scratch. It is now cancelable and will display exactly what it's doing at any given moment. In my testing, there is an error range of 1 VSEL. For me, though, it always errs on the side of stability. i.e. If it is off by 1, it tells you the BMV is 1 higher than it actually is. It seems the reason this happens is due to how the system handles crashes. Though the lowest possible BMV does get set to the app's shared settings xml file, when the phone reboots it might load with a less recent BMV. I've tried desperately to improve upon this, but it seems impossible. It's still 100 times easier than doing it yourself, though, and I think it's fine as long as it errs on the side of stability.
Here are the the recent changes as well as upcoming changes copied from the market description:
Load module within QuickClock
- No need to switch apps!
Rewrote BMV-finder from scratch
- Cancelable
- Displays status throughout process
- Keeps screen alive while testing
*Working On*
Advanced Menu
- control every CPU parameter
- set on boot
- export profile to other OC apps
- write setscaling script
Top-End Finder
- assistant to help determine max speed
Better UI
- Display of current freq's & vsel's on main menu
- aesthetic improvements
As always, I am ever-grateful to all who use my app and even more grateful to those who provide feedback.
Peace,
Paul
SlvrScoobie
Android Enthusiast
interesting, having used jrummys app since day 1 and spending hours working out my vsels by hand, ill tell you itll be interesting to see what this spits out.
I would ask - anyone using these numbers left a video or Nav (thats my overclock nemisis) run for an hour or so without reboots/kernel panics
I found I could OC/UV like Crazy on mine, until i did that. then ALL the nasty would come out. Used to run @ 1.35 @62 or something and be stable all day, until i ran NAV, then it would crap out after 45 min - so i started working on it, now im running :
350 - 31
750 - 56
1000 - 60
1250 - 74
Edit: that didnt take long:
played with 350 down to 18, which didnt reboot it. figured that was far enough, entered the data into the calculator, and got
350 - 19
750 - 38
1000 - 50
1250 - 62
took about 20 seconds before I went back to jrummy and it hung while opening the program and then kernel panic'ed
:/
I would ask - anyone using these numbers left a video or Nav (thats my overclock nemisis) run for an hour or so without reboots/kernel panics
I found I could OC/UV like Crazy on mine, until i did that. then ALL the nasty would come out. Used to run @ 1.35 @62 or something and be stable all day, until i ran NAV, then it would crap out after 45 min - so i started working on it, now im running :
350 - 31
750 - 56
1000 - 60
1250 - 74
Edit: that didnt take long:
played with 350 down to 18, which didnt reboot it. figured that was far enough, entered the data into the calculator, and got
350 - 19
750 - 38
1000 - 50
1250 - 62
took about 20 seconds before I went back to jrummy and it hung while opening the program and then kernel panic'ed
:/
Cool. Glad to have another seasoned OC'er testing it out. Let me know how it goes.
SlvrScoobie
Android Enthusiast
now - testing this out: Set the lower limit to give me a known working value - 1250 @ 74, which puts me @ 350 @ 25.
This nets me :
350 - 29
750 - 48
1000-60
1250-74
looks pretty good, im gonna try this...
This nets me :
350 - 29
750 - 48
1000-60
1250-74
looks pretty good, im gonna try this...
With a BMF of 350 and a BMV of 18, the calculator gives you this:
350 - 21
750 - 40
1000 - 52
1250 - 66
Unless you changed the stability buffer, that should be what you're seeing. Try those out and let me know how it goes.
colchiro
Extreme Android User
I thought I was doing well with 2 volts over the level that crashed during the manual method and spent about 30 seconds at each voltage to see if it was stable and it ran fine for a couple weeks until last night. My wife was playing Jewels and locked my X three times until I used jRummy OC to set my previous default of 1.25 @ ULV, after which it was stable the rest of the evening. I find that strange since I spent a couple hours trying new games with my nephews over Christmas without a problem.
So now I'm at crash voltage +3. I'll have to let my crash dummy try that setting.
BTW, I'm unable to "set to cpu" with QC, even after rebooting. It says no OC module detected, even after rebooting, which fixed it for me the last two times. I suspect it would be fixed by uninstalling one of the two apps. Also, even tho I had settings in it two weeks ago, today QC came up with all zero/empty values. Apparently there were updates that erased my previous settings.
So now I'm at crash voltage +3. I'll have to let my crash dummy try that setting.
BTW, I'm unable to "set to cpu" with QC, even after rebooting. It says no OC module detected, even after rebooting, which fixed it for me the last two times. I suspect it would be fixed by uninstalling one of the two apps. Also, even tho I had settings in it two weeks ago, today QC came up with all zero/empty values. Apparently there were updates that erased my previous settings.
SlvrScoobie
Android Enthusiast
yea i dunno where it got that from. I have to put in 16 to get those numbers
oh well - its been working well @ 25 bmv for 350 over night
could try to use lower voltages, but with my previous work, I suspect that Ill have to stay at 74 for 1250mhz, but 1000 could probably be lowered if the others are lower.
oh well - its been working well @ 25 bmv for 350 over night
could try to use lower voltages, but with my previous work, I suspect that Ill have to stay at 74 for 1250mhz, but 1000 could probably be lowered if the others are lower.
I thought I was doing well with 2 volts over the level that crashed during the manual method and spent about 30 seconds at each voltage to see if it was stable and it ran fine for a couple weeks until last night. My wife was playing Jewels and locked my X three times until I used jRummy OC to set my previous default of 1.25 @ ULV, after which it was stable the rest of the evening. I find that strange since I spent a couple hours trying new games with my nephews over Christmas without a problem.
So now I'm at crash voltage +3. I'll have to let my crash dummy try that setting.
BTW, I'm unable to "set to cpu" with QC, even after rebooting. It says no OC module detected, even after rebooting, which fixed it for me the last two times. I suspect it would be fixed by uninstalling one of the two apps. Also, even tho I had settings in it two weeks ago, today QC came up with all zero/empty values. Apparently there were updates that erased my previous settings.
Yeah it was necessary to wipe old settings with one of the more recent updates. Apologies for that, but try out the new auto-finder and see how that does for you. I think it's working much better.
***I'm probably going to change the default Stability Buffer to 14, though, so you may want to go ahead and set it that way.
Keep in mind that random reboots can still happen on stock, unrooted devices... so that reboot you got may have actually had nothing to do with the overclocking. Who knows!
We all just do our best to balance speed, stability, and battery life. I'mma just keep tryin to help us all do that with less time invested in testing and more time spent actually enjoying the benefits from overclocking and undervolting. Thanks for the update, Colchiro!Cool cool.
I'd be interested in seeing your results with an auto-found BMV + stability buffer of 14. Back on 2.2 I was able to run absolutely anything for any period of time using a stability buffer of 13, but now on 2.2.1 I get reboots when running a top end of 75 vsel @ 1400 Mhz. With just a slight bump to 76 vsel @ 1400 Mhz, however, all reboots cease. To account for this (and then some), I do think I'll be bumping the default stability buffer to 14. Thanks for the update to you as well, SlvrScoobie!
Really appreciate everyone's feedback on the app. If anyone has any feature requests, please feel free to let me know and I'll definitely oblige if at all possible.
Oh, Colchiro, if you have the latest update just use the Load Module button from the main menu. If that doesn't work for some reason, please let me know... that'd be a shocker though. Pretty simple little routine. Should pop up a toast notification to indicate the module has been loaded.
colchiro
Extreme Android User
Wow, fast comeback.
Tried clearing the cache in QC. When that didn't work, I uninstalled/reinstalled it and got the menu with 3 options (load, set, configure), all of which appeared to work until I tried to "set to cpu" and again same error.
Tried a reboot and that didn't help. It wasn't until I choose "load" and even tho the module was the same version, I let it reinstall and it worked after that.
Letting it redetect min VSEL right now. I like the status while detecting.... looks less like a hung apps now.
I'll try that.
That's what I thought, but when it happened 3 times, and increasing the voltage fixed it, I figured it was my voltage settings.
Wow, fast comeback.
Tried clearing the cache in QC. When that didn't work, I uninstalled/reinstalled it and got the menu with 3 options (load, set, configure), all of which appeared to work until I tried to "set to cpu" and again same error.
Tried a reboot and that didn't help. It wasn't until I choose "load" and even tho the module was the same version, I let it reinstall and it worked after that.
Oh ok. I'll fix that tonight. That's happening due to the way it detects the loaded module. I'll just change it so that it uses the same method as the load module button. Sorry for that frustration! Should be a simple change though.
Precisely my intention! Haha. I hated that it did that before, and think this way is much, much better.
Oh. Well in that case, I shall eat my words. *Om nom nom* Heheh. Oh lord, I need to start sleeping more.
colchiro
Extreme Android User
Ran the updated "get parms automatically" and it detected
min freq: 300,
min volt: 12
stability: 13.0
I originally crashed on 350 @ 12 volts so this is looking better until I set scaling and get lower voltages than what I found to be stable.
350 @16
600 @ 29
850 @ 41
1250 @ 62
As of this morning, I'm currently at:
350 @ 21
600 @ 33
850 @ 46
1250 @ 66
Each slot is 1 volt higher than what I used for the last 2 weeks.
I still need to get my crash dummy testing before I know this works.
min freq: 300,
min volt: 12
stability: 13.0
I originally crashed on 350 @ 12 volts so this is looking better until I set scaling and get lower voltages than what I found to be stable.
350 @16
600 @ 29
850 @ 41
1250 @ 62
As of this morning, I'm currently at:
350 @ 21
600 @ 33
850 @ 46
1250 @ 66
Each slot is 1 volt higher than what I used for the last 2 weeks.
I still need to get my crash dummy testing before I know this works.
Ran the updated "get parms automatically" and it detected
min freq: 300,
min volt: 12
stability: 13.0
I originally crashed on 350 @ 12 volts so this is looking better until I set scaling and get lower voltages than what I found to be stable.
350 @16
600 @ 29
850 @ 41
1250 @ 62
As of this morning, I'm currently at:
350 @ 21
600 @ 33
850 @ 46
1250 @ 66
Each slot is 1 volt higher than what I used for the last 2 weeks.
I still need to get my crash dummy testing before I know this works.
Yeah give those a shot, and if you see instability just up the stability buffer a bit. I'll be adding in a slider or text input on the CPU Config menu so that you can change the stability buffer there.
colchiro
Extreme Android User
I'm a web developer so understand how that works. You can think you've got the perfect interface/logic and within 2 minutes some dummy with 3 brain cells will crash it.
I'm avoiding doing actual work at work, so here's a mockup of the new main menu that I threw together in Paint. I always like the old-school 8-bit, terminal-looking graphics, so that's what I went for.
* 1000 Mhz / 56 VSEL would be the current frequency and vsel. And Mhz should be MHz. Derp.
* The min and max thingo would show all your current available scaling points and allow you to set the min and max a la SetCPU.
All criticisms welcome. Don't be shy.
* 1000 Mhz / 56 VSEL would be the current frequency and vsel. And Mhz should be MHz. Derp.
* The min and max thingo would show all your current available scaling points and allow you to set the min and max a la SetCPU.
All criticisms welcome. Don't be shy.
Why thank you, SoundQcar. I was hoping that a more transparent BMV finder would be more appealing
