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

My Droid is running at 1GHZ

Fabolous said:
To fix your SetCPU problem, don't select 'Droid' as your device, just choose auto detect. That will let you adjust the sliders without screwing it up.

As for running at a higher frequency, you need to download either the boot image or a nandroid backup of the boot image that allows you to run at the higher speeds. Then SetCPU will detect these new frequencies and allow you to use them.

You can find those images at the same place you found the bugless beast ROM.
Click to expand...

Ok thanks! Do you know if there is a bugless beast cloaked to 1.1?
 
Kirch21 said:
Ok thanks! Do you know if there is a bugless beast cloaked to 1.1?
Click to expand...

No, and I don't see one being made. These public releases will be conservative on the overclock, because not everyone's devices can handle 1+ GHz speeds.

Still, it's a 2 minute ordeal to flash the new boot image, so yeah...
 
Fabolous said:
No, and I don't see one being made. These public releases will be conservative on the overclock, because not everyone's devices can handle 1+ GHz speeds.

Still, it's a 2 minute ordeal to flash the new boot image, so yeah...
Click to expand...

will it be an update.zip? sorry i am a noob at overclocking
 
No. It is a nandroid backup, with only the /boot partition.

You download the backup, choose advanced restore in your recovery image.

select the overclock backup, make sure only 'BOOT' has a star by it, and recover.

That's all.
 
So I'm running 1.1 and decided to test mine against the youtube video posted in this thread. BOTH of those droids were already booted while mine was still sitting at the M screen.

Also I noticed that if I reboot my phone, it will drop back down to 550. It's set to autodetect in SetCPU. I have to go into the profile section and check/uncheck then hit refresh and it jumps to 1100. All the while SetCPU slider is saying 1100. Just not in the top left corner or the widget.
 
Fabolous said:
No. It is a nandroid backup, with only the /boot partition.

You download the backup, choose advanced restore in your recovery image.

select the overclock backup, make sure only 'BOOT' has a star by it, and recover.

That's all.
Click to expand...

Thanks for the help! Sorry for bugging you with my noobyness haha but i swear im better at this phone at other things just not over clocking yet!
 
Hey all!
So I overclocked my phone to 800Mhz and no it seems that I can't adjust the phone's brightness. Does anyone else have this problem and is there anyway to fix it? Or is it just something that is inherent with overclocking? Thanks!
 
I made the jump to bugless beauty and did the 1ghz boot img. Been running normally all day, txting, web, movie, only had one reboot and that was right after I had first started at 1ghz. Batt temp was over 100 f. BUT everything has been silky smooth since.
 
Icedemon said:
So I'm running 1.1 and decided to test mine against the youtube video posted in this thread. BOTH of those droids were already booted while mine was still sitting at the M screen.

Also I noticed that if I reboot my phone, it will drop back down to 550. It's set to autodetect in SetCPU. I have to go into the profile section and check/uncheck then hit refresh and it jumps to 1100. All the while SetCPU slider is saying 1100. Just not in the top left corner or the widget.
Click to expand...

have you tried checking "set on boot" ??
 
dispatch1054 said:
Hey all!
So I overclocked my phone to 800Mhz and no it seems that I can't adjust the phone's brightness. Does anyone else have this problem and is there anyway to fix it? Or is it just something that is inherent with overclocking? Thanks!
Click to expand...

Yeah...I'm seeing this as well, using the 900mhz Tas boot image, I'm assuming you're using auto-brightness?

Manual brightness works fine, but auto-brightness will intermittently go to laser bright for me...have to reboot to fix it.

Not willing to give up the extra speed/smoothness from OC yet, but it's annoying. Didn't happen the first time until I'd been running the OC boot image for hours, happened the second time just a hour or so later.

I've asked both Tas and Pete if they are aware of any fix...
 
Awesome thanks redflea!

Actually both manual brightness and auto wouldn't work for me. It was
Just constantly really bright. I was running humancyborgs 2.1 rom
And didn't wanna give up overclock either. I ended up switching to the
Bugless Beauty and the problem thankfully went away .
 
Thanks for all the help. Finally got Bugless .7.1 installed lastnight and everything is working great! Using Evilboot8.img with no crashes and really fast.

Only thing, like post above is the brightness issue, but I'll live with that.

Thanks again guys
S
 
scott5626 said:
It's no different from overclocking a computer's chip, excessive heat will burn up that chip, there's a reason Motorola ,Apple, and Palm stopped at 550 MHz. They all run on this processor.

I have burnt up video cards by doing the same thing...it may take a while it may not but eventually....
Click to expand...

Not trying to take sides or anything but one reason why phone companies decide a lower clock speed before releasing is to get a better battery life to make it more appealing to the consumer. (The average consumer who does not know about clockspeed and tends to be interested in the more superficial aspects of phones)
 
Having read through the entire thread (again, as 2 pages were added since I last posted) I have to say this:

1) I need to peruse the other links provided....

2) I used Pede7's (?) thread in the help and support pages to root my DROID _ only it never fully got done, meaning that the step where I boot into the alternate mode and then mount 4 then 3 never works - it locks up on the first mount step and nothing ever happened after that until I force rebooted.

So, that being said....will these steps attempt to fix my previous attempts at rooting, or should I start from scratch as if I never rooted my phone?

For the record, it was a long tie before I even attempted OCing my CPUs - now it is a matter of principle. In fact, I bought a Core i7 965 EE last month, and am about to buy my eVGA Classified X58 mobo and some RAM to rebuild my beast and help achieve its place of honor in my house....

But, my phone, well, never have done that, so I am a true phone OC n00b.

At this time f night, there may not be a lot of folks on, but I'll try the chat room anyway to see if anyone can help me live.
 
Quick Question... What are the best frequencies to set for when your droid is charging and when the screen is off... mine are set to 250 min and 550 max (which i guess is default) for both of those, and it jumps to 900 when the screen is turned on. Is this what you guys have it set to?
 
BigMace23 said:
Quick Question... What are the best frequencies to set for when your droid is charging and when the screen is off... mine are set to 250 min and 550 max (which i guess is default) for both of those, and it jumps to 900 when the screen is turned on. Is this what you guys have it set to?
Click to expand...

I've set mine to:

charging-max 550, min 250
sleeping-max 250, min 125
 
Hey guys, I got my Droid rooted and OC'ed to 900 MHz with the Nandroid IMG found here. So I wanted to get my OC profiles set up with SetCPU. I went to the Market, purchased and started to download it, but every time I hit "Install", it says "authorizing purchase, then flashes to "downloaded" for a split sec, then goes back to the installed apps menu where it just says "purchased" beside the app, not "installed". So basically it won't install. Wtf could be causing this? I've tried restarting the phone, but still a no-go.

Thanks for the help and all the great info so far!

Edit: Nm, seems I typo'd my CVC code on the back of my CC, D'oh! I'm good now, hah.
 
I said...
psychokitty said:
will there be any progress on an under-volting front, emphasis being on complete customizable cpu speed & voltage that works for the individuals' needs?
i use rmclock for my old dothan to regulate stepping and voltage. My behemoth 17" laptop gets over 50% more battery life than it did new, with no underclocking, all just voltage regulation. You just decrease voltage, run a series of endurance runs to see where your blow-chunx @ low voltage threshold is, and back her off a bit. So just because i get 50% more mpg outta my lappie means nothing for the droid, but i figure if the droids cpu can be oced 66%, it might have significant capability in this other department, as well.
Click to expand...
 
deeznuts2 said:
so when can we expect people to be blowing their nads off due to excessive heat resulting in exploding batteries?
Click to expand...

Umm ... yea, that's an intelligent question. :rolleyes:
Been playing with the DROID for an hour now, at 1.1 GHz. ;) Just checked the "BatteryLife" widget, my current battery temp is a SMOLDERING 82.4 degrees. Crazy, right? *yawn*

Next question! :p
 
messenger13 said:
Umm ... yea, that's an intelligent question. :rolleyes:
Been playing with the DROID for an hour now, at 1.1 GHz. ;) Just checked the "BatteryLife" widget, my current battery temp is a SMOLDERING 82.4 degrees. Crazy, right? *yawn*

Next question! :p
Click to expand...

Not likely, considering the ambient temp of the device is around 75*F. If you believe that overclocking the processor to 1.1Ghz only results in a 7*F increase you must be out of your mind.

But then again, widgets are never wrong
tirehead.gif
 
Would you like to see some screenshots of my Droid running at 550mhz and the temp, then at 1.1ghz and the temp? It is a 2 C difference. Both after a hour of browsing, GPS nav, and some video playback.
 
You must log in or register to reply here.
Back
Top Bottom