1.6 GHz Hummingbird OC (Vibrant), 3k+ Quadrant score


Last Updated:

  1. commenter01

    commenter01 Member This Topic's Starter

    Joined:
    Aug 31, 2010
    Messages:
    17
    Likes Received:
    6
    Check it out over at phandroid.


    Part of me is happy, the other part is still pissed off at the gps+froyo fiasco. Regardless... just wanted to share this little ray of sunshine.
     

    Advertisement
  2. sk8rboikelley

    sk8rboikelley Member

    Joined:
    Sep 23, 2010
    Messages:
    17
    Likes Received:
    0
    could you possibly give me a link/url to explain how to do this?
     
  3. commenter01

    commenter01 Member This Topic's Starter

    Joined:
    Aug 31, 2010
    Messages:
    17
    Likes Received:
    6
    I know about as much as you. Possibly, they're still cooking the ROM...
     
  4. sremick

    sremick Well-Known Member

    Joined:
    Jun 18, 2010
    Messages:
    2,521
    Likes Received:
    356
    Ah, more people who think overclocking is "safe". How amusing. And this is from someone (me) who's experimented with careful and methodical OCing for many years.

    (Cue the "LIES! I've overclocked for 3 months now and never had a problem!" clueless trolls.)

    1) Manufacturers don't clock a chip low just to piss you off. If it really COULD run safely higher, it'd make their product look better, more-competitive, and would sell more. There are reasons it's 1GHz and not 1+ GHz.

    2) Not all failures are "catastrophic". Meaning it doesn't just not work or work. Failures can creep in in subtle and delayed ways.

    3) Permanent damage can (and probably will) result. It's not all at once. It's gradually over time. Running beyond spec will reduce the useful life of your electronics. Only question is by how much.

    But hey, if you see your $400 electronics device as a disposable toy you don't mind burning through in 6 months, knock yourself out. You just forfeit your right to ever post anywhere again complaining "OMG my Captivate locked up! Samsung sucks! The Captivate is crap!"
     
  5. Thassodar

    Thassodar Well-Known Member

    Joined:
    Aug 4, 2010
    Messages:
    49
    Likes Received:
    14
    Are you always pessimistic? I have yet to see a non-sarcastic, snarky, or PARTIALLY helpful post by you in every post I've seen by you.

    That being said if they want to overclock, overclock. It's like slapping a turbo on a car that doesn't have a turbo without preparing other parts of the engine. FOR NOW, it'll be great and fun. In the long run you're putting more stress on the stock parts that weren't made to run that hard. The fun part is that it's the USER'S choice, and it's not someone else's place to reprimand them for doing something they themselves would not do.
     
  6. sremick

    sremick Well-Known Member

    Joined:
    Jun 18, 2010
    Messages:
    2,521
    Likes Received:
    356
    Haha, no... I'm realistic... and trying to bring some sanity to a board where everyone recommends dangerous hacks without passing along an education on the associated risks and repercussions at the same time. Those same people who OC because "everyone else seems to be doing it" then come back here to bitch when things die.

    If the phone-ricers are going to suggest to every grandma and soccer-mom that they have to hack the crap out of their phone just to be happy, then I'll be the sole voice tacking on the disclaimer and warning.

    And not a single even partially-helpful post, eh? Nice. :rolleyes: Baseless personal attacks like that don't really help add credibility to your side of the argument. Especially considering how many people disagree with that.

    Exactly. And would you slap on that turbo and increase the compression significantly without warning everyone about the dangers of doing so? But that's what happens here....

    "Hey everyone, new to the forum and just got my Captivate. What should I do first?"

    "dood... get urself the odin 1.2 OC rom and flash that baby, itll make it SCREAM and run sooo awesomez. DO IT!!!"
     
  7. commenter01

    commenter01 Member This Topic's Starter

    Joined:
    Aug 31, 2010
    Messages:
    17
    Likes Received:
    6
    First off, I didn't recommend anything. I posted the link to highlight the potential of our processor, especially in light of what has recently been done with the G2, et al.

    Secondly, can you really conclude that the phone will die prematurely if you overclock it? Define prematurely. A processor, running continuously within spec, will function for years without dying (e.g., my overclocked p4 has about 9 years on it, still going strong). Additionally, I think it is safe to say that the turnover for mobile phones is about once every 2-3 years. So probably, by the time the processor would have died given the overclock, the user has already replaced the phone.

    Regardless, it is not a matter of how much you overclock - it is a matter of whether you are exceeding the thermal design package (TDP) of the processor. Heat is what damages electronics. If you can keep it within it's TDP, you're fine. Keep in mind that most OC'ing software employs hardware monitoring to ensure that the temp doesn't spike, and if it does, it downclocks.

    Finally, it should be noted that companies underclock from the maximum potential of a processor for more than one reason. There is a requirement of uniformity of speed across processors when you are mass producing a unit - due to manufacturing differences, some units can be clocked higher than others, but they are all taken down to the same baseline. Additionally, since this is the mobile world, a premium is placed on battery life. It doesn't take a genius to know that an increased processor speed decreases battery life.

    TL;DR: There are compelling reasons to overclock, and do so safely. The reduction in processor life should be irrelevant to the end user.
     

Share This Page

Loading...