1. Are you ready for the Galaxy S20? Here is everything we know so far!

Overclocking ?? Hmm.?

Discussion in 'Android Devices' started by pacedrum69, Jun 10, 2010.

  1. scary alien

    scary alien not really so scary
    VIP Member

    Guys, just a quick FYI: while charging my phone here at work, I decided to pull-up System Panel and watch the Temperatures gauge while it charged.

    The temp started at 32.4 C and quickly rose to 40.2 C within 15 minutes. I had my failsafe temp set to 41 C and realized that it wouldn't take very much to get it to climb past this limit.

    No big deal, I adjusted the limit to 43 C and took the silicone sleeve off of the phone and the temp has held steady at 40.2. Anyway, lesson here just reinforces namu1107's post that charging will easily bump the phone temp up by 8-plus degrees (and that's just while sitting, being charge--nothing else being done on the phone). Your mileage WILL vary. :D

    Cheers!

    edit: silicone sleeve being off allowed the temp to drop to 37.7 C while still charging...removal of sleeve seems to have made the biggest difference (i.e., not holding all that heat in)...charge is at 91% and temp is 35.4 C
     



    1. Download the Forums for Android™ app!


      Download

       
  2. Caddyman

    Caddyman Android Expert

    I have a little fan next to my charger plug i sit my phone on when charging, just in case...lol
     

    Attached Files:

  3. scary alien

    scary alien not really so scary
    VIP Member

    That's pretty sweet! Now you just need to make an Android-logo'd case/mod for it and root overclockers would be beating your door down to get one and you'd be filthy rich! :D

    I'm going to try to find a mini-fan like that...maybe a smaller, USB-powered one...Google, here I come!
     
  4. scary alien

    scary alien not really so scary
    VIP Member

    Okay, now I understand... I had erroneously thought and reported that Ivan's Eris Official 1.0 w/OC ROM started you out overclocked at 710 MHz.

    Well, this is obviously not the case (duh!).

    I swapped batteries just now and checked System Panel to view the CPU speed. Its all over the place...but is NOT going to 710 MHz like I saw before. The difference: simply running setCPU once must enable overclocking even if you don't change anything. I'm betting a lot of you guys already knew this, but I didn't :D.

    Anyway, I gleaned some of this from reading Ivan's thread over at xda last night and I thought I would double-check things before re-setting my setCPU settings after a reboot. Anyway, thanks again for everyone's help and feedback.

    P.S. Hey, and a bonus: I didn't have to re-enter my settings in setCPU, they were already there--all I had to do was launch it. I guess the "set on boot" just makes even having to remember to launch it after a reboot, unnecessary.
     
  5. Frisco

    Frisco =Luceat Lux Vestra=

    Good, some talk about over clocking. ;)

    I put mine at 710 and 445.. the first time I set it the thing froze up.. battery pull then plugged in the charger and rebooted one more time.

    Now all is well following about an hour of testing.. the thing was always pretty lag-free, as compared to reports I've seen posted around the forums.. but now it reminds me of my friend's Nexus One; it just snaps right to the app or settings page or whatever I'm going to.. no wait that I can perceive at all.

    Now that is one big proof of the pudding for me as far as rooting goes.

    Any of you doing this, using SetCPU, be conservative.. I took my time and started with low speeds and worked up to the maximum recommended by many who are in the know about the over clocking subject.
     
  6. hookem

    hookem Android Enthusiast

    Obviously I haven't been keeping up with things....

    FRISCO has gone ROOT!?!?! Were you trying to get back to 1.5? ;)

    But seriously... I've been pretty stable @ 768, only an occasional freeze. I'm gonna trim her down one slot to748 to see if it takes care of that.
     
  7. Frisco

    Frisco =Luceat Lux Vestra=

    Oh but 1.5 is sooooo THEN. Root is soooo NOW.

    ... and, hey, I'm (occasionally, when convenient) a NOW kind of guy.

    lol.. etc.

    ;)
     
  8. ACD168

    ACD168 Android Expert

    kept it on 710 when I first got comfortable, I've jumped it up to 768 and that seems to be my sweet spot. getting over 3.1 MFLOPS running ivans
     
  9. Frisco

    Frisco =Luceat Lux Vestra=

    In SetCPU the 710 is maxed out (green bar all the way to the right), although the low setting can still be changed.

    Is there a way to change that? I'm thinking it is inherent in the ROM design (Senseable 3.1).
     
  10. ttran97

    ttran97 Android Enthusiast

    You need to flash Zanfur's updated overclocking thing. It's over in the XDA forums here: Overclock Patch and update.zip - xda-developers

    Then you can go higher, but I wouldn't recommend going past 768...
     
  11. Frisco

    Frisco =Luceat Lux Vestra=

    Thank you.

    I just wanted to experiment a bit past 710.. likely working my way up to 768, as I've seen that figure as a max by most overclockers. I did see one saying he's had his at over 800 for a time with no ill effects.. but I'll stick with 768 as the max.
     
  12. ttran97

    ttran97 Android Enthusiast

    You're welcome! When you go over 768, it really depends on your individual Eris. Some phones can get up that high, but most don't. My phone locked up and I had to do battery pull and lots of "oh please I hope i can fix this". haha.

    Plus, I think someone posted that the increase isn't going to be that much more, but it will drain your battery a lot. I still think 710 is a good place to be at in terms of balance.

    Even if you leave the max at 710, the updated overclock patch is supposed to be more efficient at switching, so you're still better off upgrading. I think that with the next round of updates, the developers will integrate zanfur's patch built into the ROM.
     
  13. JrzDroid

    JrzDroid Android Expert

    just a heads up. I've been running 768 on different roms and it finally took its toll. The phone got really hot and just gave up. No recovery, barely hboot. Just dead

    So be warned those who are experimenting with OC. 710 is recoomended Eris oc for a reason
     
    Hagbard57 likes this.
  14. Frisco

    Frisco =Luceat Lux Vestra=

    Yeah, I'd think there would be a hardware limitation over time.

    The 768 does work very nicely on mine.. but I'm inclined to set it back to 710 which is smooth as snot on a doorknob anyway.
     
  15. bjanow

    bjanow Android Expert

    Shit, sorry dude. That sucks. What ya gonna do?
     
  16. JrzDroid

    JrzDroid Android Expert

    i got a new Eris, which is now rooted
     
  17. dirtmouth

    dirtmouth Android Enthusiast

    ok, whats the deal that 1.5.4 is old and when i get the newest it stil only gives me 528. that 1.5.4 doesnt seem to cooperate
     
  18. dirtmouth

    dirtmouth Android Enthusiast

    ya im stuck at 528, that link there is to an older setcpu app is it not?
    i have 2.0.1 and only see max at 528....
     
  19. Frisco

    Frisco =Luceat Lux Vestra=

    A couple of ROMs ago I decided to experiment with SetCPU because the "detect automatically" button caused 528 to be the maximum setting, as some are reporting now.

    I used the manual method and selected Nexus One (there were other devices listed along with the N1 on that setting). Ymmv!

    I quickly moved the slider to the left because it was momentarily maxed out.. it worked (about the third time and after a few battery pulls because of a frozen screen).

    Never have it set to oc at boot until you've found a safe setting. ;)

    If you fry your CPU or brick your phone trying what I tried, it is 100% your responsibility.
     
  20. NAA_Silent

    NAA_Silent Newbie

    I bought SetCPU, and now I've been stuck on the authorizing purchase screen for 15 minutes. Even canceled and restarted the download, and that didn't help.
     
  21. NAA_Silent

    NAA_Silent Newbie

    2.5 hours later, installed and running at 710 :)
     
  22. roscuthiii

    roscuthiii Well-Known Member

    I think I've killed my SetCPU...

    Long story... I had Ivan's 0.8t2 and when buying it in the market didn't realize I was in the negs. Since I was declined I got 2.0.1 for free from the XDA forum but was limited to only 528 max.
    I've upgraded to Ivan's 1.0 w/ OC. I didn't realize it had come with SetCPU 1.5.
    I restored the 2.0.1.apk from my Estrongs app back-ups. The market would say it was purchased but not installed.
    Now I have the greyed 1.5 icon in my app drawer. I have the colorful 2.0.1 icon when I go to manage apps. If I try to add SetCPU to my home screen is says the link to the app is no longer installed. And now that I was able to update my Google Checkout and actually purchase the app it says installed but I can only open 2.0.1 from the Market Downloads tab. If I want to open it from my phone I have to go to manage apps and uninstall updates but that's only v 1.5...
    WTF?!
     
  23. scary alien

    scary alien not really so scary
    VIP Member

    Bummer, dude! Well, I can't speak to the Google Checkout issues, but I'm not sure if a new/different setCPU would do you any good anyway on Ivan's 1.0. I read a quote from Ivan's thread that the kernal is clock-locked at 710MHz. So, I don't think you'd be able to o/c higher than that anyway on this ROM. Could be wrong, but...

    edit: perhaps the o/c kernal lock is the reason for the issues you are seeing...
     
  24. roscuthiii

    roscuthiii Well-Known Member

    I'm thinking that maybe a wipe/reset and a NAND restore back to Ivan's 0.8t2 might be a good starting place for getting SetCPU 2.0.1 working again. That seems to be the last time it worked.

    I guess it depends on whether the bug/glitch will continue because of some hidden file left behind in the system from the Android Market or Google Checkout...
     
  25. roscuthiii

    roscuthiii Well-Known Member

    Hold the phone! (Any way you like, right hand or left)

    Played with it and it seems I have 2.0.1 up and running as my default SetCPU instead of the older version. I have no idea what I did but with this mystery solved I can go look for something else to butcher now!

    Thank goodness for NAND back-ups. This should come standard.
     

HTC Droid Eris Forum

The HTC Droid Eris release date was November 2009. Features and Specs include a 3.2" inch screen, 5MP camera, 288GB RAM, MSM7600 processor, and 1300mAh battery.

November 2009
Release Date
0
Reviews
Loading...

Share This Page

Loading...