Anyone running the droid at 1.3Ghz?

[Bear in NM]

Here is the link to alldroid, the temp monitor program and the oc kernels.

http://http://www.alldroid.org/viewt...p?f=312&t=2115

I would highly suggest reading through, and checking all of the temp threads here and there. I am really only running it to contribute to the developer and to Taz, and do not place a lot of stock in fretting over it.

Craig

[Hugh Jass]

I just pushed my Droid to the max. At 1.1ghz, I simultaneously was navigating with google maps to the other side of the country, and had pandora and robo-defense blasting away. Finally it started crashing programs, pandora failed and robo-defese started to glitch slightly. I saw it at 140F just before it gave after 3 minutes of torture. Frankly I am impressed with what this little chip can do! I never ever thought it could handle anything like that.

Based on this I've set my fail-safe at 48c for now at 800mhz.

Droid DOES.

[Bear in NM]

Hugh,

Most excellent reply. What I found intersting is that the system iteslf, whether through intentional design or by product of abuse, starting shutting down, or at least becoming unstable enough that anyone paying attention might notice. I have not been able to get my system unstable with the things I do, and your testing might help folks get beyond "I was doing some stuff on the phone, saw the temp go to 105F and now I am gonna unroot and go back to stock".

And, get your butt of the road, driving cross country while playing a game, at the wheel, you should be ashamed of yourself I think some folks loose track of this oc'ing to the extent that a maximum scenario may in no way shape or form relate to their partular use of the phone. In your testing, "stuff" stopped working. This is what I might call a "clue" that you are taxing the system, so back off. Most interesting.

Perhaps you can give me a tutorial on Robo Defense. I tried it, and was hopelessly lost..........

Craig

[Benny]

I'm running 1ghz, with BB7.4.
1.1ghz and 1.3ghz are completely unstable for me.

[Hugh Jass]

Hugh,

Most excellent reply. What I found intersting is that the system iteslf, whether through intentional design or by product of abuse, starting shutting down, or at least becoming unstable enough that anyone paying attention might notice. I have not been able to get my system unstable with the things I do, and your testing might help folks get beyond "I was doing some stuff on the phone, saw the temp go to 105F and now I am gonna unroot and go back to stock".

And, get your butt of the road, driving cross country while playing a game, at the wheel, you should be ashamed of yourself I think some folks loose track of this oc'ing to the extent that a maximum scenario may in no way shape or form relate to their partular use of the phone. In your testing, "stuff" stopped working. This is what I might call a "clue" that you are taxing the system, so back off. Most interesting.

Perhaps you can give me a tutorial on Robo Defense. I tried it, and was hopelessly lost..........

Craig

HAHA, no I wasn't actually driving my friend, but Google Maps didn't know that. I was doing this from my hotel bed.

I also found it interesting that the system was hinting toward failure. With my experience overclocking PC's they run geat and BOOM, instantaneously crash without warning. I expected the same from the Droid but it certainly let me know before it gave up.

Based on what I saw personally I don't think temp wise 1.3ghz is feasible on the Droid. Perhaps it might be stable for a period of time with focused intentions (one app or two at a time) but it is just too damn hot when multitasking on intensive programs such as Robo Defense.

As for me giving you a tutorial on Robo, I'd suck at that so I found this for you.

Lupis Labs: Robo Defense Instructions!

Read comments as well, some info there too.

[roberj13]

I am on Sholes 2.0.3. Currently running at 1GHz. I used the 1.3 kernel last night for about thirty minutes. Randomly rebooted when I was responding to a post here. Temps got to 119 before I rebooted. Then I read a post from Taz on alldroid.org mentioning that he DID NOT recommend to run his kernels on Sholes as the sholes team had rewritten some init scripts causing his kernal to not run properly. I thought I might just see how long I could keep it running and just decided I shouldn't go against the actual developers advice...

Completely stable and fast on 1GHz though, always get distracted by shiny things passing by though...lol

[Hugh Jass]

1.1 works great for me on Sholes so far.

[Bear in NM]

Hugh,

I understood you were "driving" only on paper. Couldn't resist though. I agree with your thoughts on the oc, and use. As I posted, 1.3 is working for me, likley as I have not found a way to tax mine with what I do.

I was half kidding on the rob defense, as I did go through all the destructions on it's use. Now that I know it was processor and temp taxing on your phone at 1.1, I may reinstall (rd) on my 1.3 and see how it does. I'm just not a big game player, across the boards. I did see the 50 game thread, and really want to try one that uses the accelerometer, but 4 or 5 bucks for a game, not being a big game person...........

I do hope we get more reports like yours with actual use and results with the higer oc's. We definately need more of that.

Craig