Related
With Linpack I see people getting to 848mhz and even 1ghz.
I lose stability at 787mhz and I'm ok at 768. I know that different chips vary... but 1ghz difference?
Is there a way to overvolt on the Eris I don't know of?
The eris OC at 1ghz....thats a lie and some one is pulling your leg lol. The eris is not built handle that and if it did reach 1ghz the motherboard would burn up.
Yeah but 848mhz isn't so farfetched. I can do 787 for a while without any freezes. The freezes do happen though.
If you overvolt it shouldn't be impossible to get up to 848mhz.
As for the 1ghz + entries on linpack's site I think it must be another phone running Eris ROM's/ basebands.
Hungry Man said:
With Linpack I see people getting to 848mhz and even 1ghz.
I lose stability at 787mhz and I'm ok at 768. I know that different chips vary... but 1ghz difference?
Is there a way to overvolt on the Eris I don't know of?
Click to expand...
Click to collapse
I can do 806 all day with Aloysius but my buddy with the same exact setup (i setup it up, so I nkow its exactly the same) can only get stable at 768.
I have not seen anyone with proof or that is respectable, show that they can keep their phone over 806.
"Begin envy now "
I do lol
So there are NO overvolt kernels/ methods?
I can run 806 stable with evil Eris 3, most of the other roms crash when I clock them at 806.
Lucky lol my processor seems to be stuck at 768. 787 doesn't last too long and it's not worth the random FC'ing. I'm sure it would be stable with more voltage and heat hasn't been an issue for me at all at 768 even with Pandora/ Zenonia running for quite a while I haven't gotten even lose 50C.
The question is why would one want to OC that high. I see absolutely no difference in performance at 710 vs anything higher. Probably even lower than that. I just don't see why you would want to run any higher and eat up your battery as well as tax the processor and board more when there isnt a noticeable difference other than linpack scores. Just my opinion but I think all new to OC'ing should be aware that faster isnt always better.
I know that lol I mean... a lot of people who overclock computers don't do it for a performance boost, they do it because they want to see if they can. They won't get better gaming performance they just get a slightly better benchmark.
I want to do it just to do it.
Ok rock on speed demon On that note, I wonder if it could be clocked to the max in a freezer room. If the low temp would help or if it is just hardware limited.
The MAIN problem with overclocking with voltage modification would be heat/ ****ty PSU. I'm sure the Eris battery can get up pretty high, it's a matter of staying cool. I would like to see how high I can get with cooling but I don't even know if overvolting exists for the Eris lol
Dont know about over but I know you can undervolt on it.
If there's undervolting there should be overvolting... someone has to know lol I've tried searching XDA and google but I can't find anything specific.
n2imagination said:
The question is why would one want to OC that high. I see absolutely no difference in performance at 710 vs anything higher. Probably even lower than that. I just don't see why you would want to run any higher and eat up your battery as well as tax the processor and board more when there isnt a noticeable difference other than linpack scores. Just my opinion but I think all new to OC'ing should be aware that faster isnt always better.
Click to expand...
Click to collapse
I tested 710, 768 and 806. I didnt just test with linpack either. I just used apps I normally would run, running for a few days and what not and noticed a difference from 710 to 768 but not really a noticeable diff from 768 to 806. I still keep it at 806 for reasons that my battery life is better. Dont ask me how or why but it just is. I have mine set at 806/480 and for sleep, 480/240. Now most of the day my phone is just in my desk drawer so that could be the reason but i still go a full day with heavy use at the end of the day (bt, wifi, internet radio, run keeper) and still have about 30%+ left when I go to sleep at 10
I have never had a problem with battery lol since overclocking my phone I've only increased battery life. Significantly so.
There has got to be some sweet spot there for OC'ing that gives best perform with least batt consumption. Just wish I knew what it was.
People are getting high because all processors aren't the same. So some can handle, some can't. As for the 1ghz it's a big lie. According to several people including jcase linpack scores can be easily edited and faked. I wouldn't believe anything on linpack that's outrageous.
I sorta figured they wre faking somehow. And I know some processors can handle higher speeds, that's the basis of overclocking. I want to know if I can overvolt my processor.
Can't help you there. Maybe go ask in the IRC? I'm curious if you can as well.
I can hit 787 and run stable... linkpack scores around 5.3-5.4. Oddly enough, my fone refuses to run at 768. I actually have to use a txt file for setcpu to remove 768 from the equation with profiles and the setcpu "trick" my battery life is GREAT. Much better than "stock" even.
-------------------------------------
Sent via the XDA Tapatalk App
Hey,
So I'm on the fence about perma rooting and over clocking my G2, but i have a few questions:
1) Will my battery life suffer greatly due to over clocking say to 1Ghz or 1.4Ghz?
2) Are there any real world noticeable real world performance gains besides benchmark scores?
3) Will perma-Rooting it decrease performance? (Back when i had the mytouch 3g, the phone never felt as snappy after i rooted and installed custom roms, as compared to stock).
Thanks
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
thedarkpassenger said:
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Launcher42? that's a heck lot of upgrade from Launcher2 I'd like to check it out
but he's right overclocking is not going to eat up your battery much. Heavy graphic ROMs do however suck up battery and performance. I personally like to stick to rooted stock roms and tune up here and there to fit my personal needs.
You should however read carefully and make sure to understand every steps you're doing if you want to root your phone.
androidtoy09 said:
Launcher42? that's a heck lot of upgrade from Launcher2 I'd like to check it out
but he's right overclocking is not going to eat up your battery much. Heavy graphic ROMs do however suck up battery and performance. I personally like to stick to rooted stock roms and tune up here and there to fit my personal needs.
You should however read carefully and make sure to understand every steps you're doing if you want to root your phone.
Click to expand...
Click to collapse
thedarkpassenger said:
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Alright I'm going to give it a shot later tonight probably, i forgot about the SETCPU profiles where you can have the phone under clocked while the screen is off. That should definitely give me better battery life. Ill be back to post results
kcm117 said:
Alright I'm going to give it a shot later tonight probably, i forgot about the SETCPU profiles where you can have the phone under clocked while the screen is off. That should definitely give me better battery life. Ill be back to post results
Click to expand...
Click to collapse
Good luck and I'm sure you will enjoy your G2.
Oh, and don't forget to show it off to your friends. Let them see how this thing "Fly"
I oc to 1.4+ with setcpu and a few profiles set up i get much better bat life then stock. Im also running a sense rom which feels sluggish until you oc. At 1.4 it runs smooth as can be with live wallpapers plus all the pretty sense animations. The only problem i have is i hate the sense dialer and msg system also i want to change the "personalise" tab....do people really change theyre settings everyday that they need a dedicated button for it? Anyway i digress
Sent from my HTC Vision using XDA App
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
convolution said:
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
Click to expand...
Click to collapse
No, that's not entirely true BUT with SetCPU you can profile it with different mode which can benefit the battery life.
kcm117 said:
Hey,
So I'm on the fence about perma rooting and over clocking my G2, but i have a few questions:
1) Will my battery life suffer greatly due to over clocking say to 1Ghz or 1.4Ghz?
2) Are there any real world noticeable real world performance gains besides benchmark scores?
3) Will perma-Rooting it decrease performance? (Back when i had the mytouch 3g, the phone never felt as snappy after i rooted and installed custom roms, as compared to stock).
Thanks
Click to expand...
Click to collapse
I don't notice any difference in battery and I have the 1.9ghz kernel. I normally keep it at 1ghz though. I enjoy it overclocked. My games run incredibly smooth, when navigating my phone it literally almost feels like it knows what i'm pressing a split second before i do and benchmarks rape the face off anyone else I know with an android phone. It's just sooo smooth. It really boils down to being the kind of person who likes to hold a powerhouse of a phone in the palm of their hand. (Literally) with even just the 1.4ghz OC you'll never have to ask yourself "can my phone run this without being sluggish?" because the answer is yes, it can probably even run two or three instances of whatever made you question yourself in the first place without being sluggish. Any if you're worried about custom roms from the past, just remember how outdated your old android is compared to this one. No offense because I can relate, I used to have a G1 that is now a hand-me-down to my brother and whenever he asks me to mod something on it, I'm just amazed at how slow it is and really don't know how I tolerated it for the last 2 years. I mean I'd score a 150 quadrant on the G1 (on a good day) but with my full OC on, the G2 scores 3000~3100. That's roughly 20 times faster...
Bottom line is that you won't need to worry about "will this make my device sluggish?" for quite some time.
Hey
Alright guys i got the phone perma rooted now, but i havent installed an OC kernel yet, two questions.
-Which kernal should i install if i want 1.4Ghz? there seems to be two threads with 1.4ghz kernels
-Do i need to install Bacon Bits for the kernel?
kcm117 said:
Alright guys i got the phone perma rooted now, but i havent installed an OC kernel yet, two questions.
-Which kernal should i install if i want 1.4Ghz? there seems to be two threads with 1.4ghz kernels
-Do i need to install Bacon Bits for the kernel?
Click to expand...
Click to collapse
just install cm6.1 and setCPU and you will be fine, then you can tweak it up to 1.42 if you like or whatever you want it at
Any heat related issues? Let's say I get into a zone and play some graphics intensive game 6 hours straight on USB power at 1.4Ghz? Wouldn't that put out more heat then the G2 was design to handle possibly shortening its life span?
convolution said:
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
Click to expand...
Click to collapse
It doesn't. However, overclocking is misnomer. What we really mean is over and UNDER clocking. For example with SetCPU is can create a profile that greatly slows down my CPU when the screen is off. This saves the battery a lot, since my screen is nearly always off.
Also, I can create profiles that slow down the CPU as the battery lowers in order to offset the fact that I overclock the CPU when the battery is fuller.
manvstech said:
Wouldn't that put out more heat then the G2 was design to handle possibly shortening its life span?
Click to expand...
Click to collapse
Probably could shorten the life span. I keep phones for a year or two, though, and shortened life span for me isn't an issue. The phone becomes outdated before the CPU gives up.
cparekh said:
It doesn't. However, overclocking is misnomer. What we really mean is over and UNDER clocking. For example with SetCPU is can create a profile that greatly slows down my CPU when the screen is off. This saves the battery a lot, since my screen is nearly always off.
Also, I can create profiles that slow down the CPU as the battery lowers in order to offset the fact that I overclock the CPU when the battery is fuller.
Click to expand...
Click to collapse
^This.
I've gone a full 10 hours with my battery still reporting 100%.
Sent from my HTC Vision using XDA App
my default sense rom does not feel sluggish at all.
this oc is not really required from my point of view. and it also does not increase battery. the thing what increased is the underclocking when screen is off.
and this you can do even without overclocking. and THEN it brings even more gain.
an example of "real world" for me is how well my g2 plays PSX games on the emulator. I have it overclocked at 1.5 on setcpu and it runs chrono cross pretty much flawlessly with no noticeable slow down.
i use setcpu for underclocking since i don't do enough just yet to overclock, i haven't noticed any battery increase just yet and i've been using it for a few days now. i almost questioned my self if i was losing battery life due to my system mhz always fluctuating? is this a possibility? i just added a profile for screen off 245/245 but i still had to choose on demand? what should i put there. thanks for ur help everyone
I installed the bacon bits 1.4ghz kernel and setup some setcpu profiles.....battery life is much better now.
Sent from my T-Mobile G2 using XDA App
screen off profile doesn't work with G2
noone has any proof it does change anything.
with or without widget running
How far have people got with over clocking their Visions?
Mines over clocked at 1GHz, i don't think id be increasing it any time soon think it would ruin my battery life
How far have all you all got to? Stable of course
That I know, we're at 1.8ghz so far. I keep mine at 806mhz all day since I barely use it throughout the day. Once I get home, I clock it up to 1.5ghz when I'm using it.
I've ran it once at 1.8ghz running a couple of benchmarks (linpack, neocore, quadrant)
It did very well, but, ran very hot (could be due to the fact I had it connected to the charger at the same time)
Either case, how much you get out of your battery depends on how you use it, how you set up your cpu profiles (dependant on which you use. I.e. cpu tuner, setcpu), and what frequency you're constantly letting your phone run on.
I run mine at 1.5ghz, see no need to push it further. Im getting all the performance I need at 1.5ghz. I use setcpu profiles, one to severely underclock when it reaches a certain temp and a charging profile that runs at stock clock to reduce heat when charging.
1.3ghz. Not like i feel it however. But 1.4ghz one they have posted wasnt 100% stable for me.
hi guys!!
i'm just curious.. has anyone tried this mod?? it's not for defy.. but maybe someone manaeged to make it work properly on it
thanks!!
byebye
what mod there is no link or description?? best you can do is decrease your vsel and use juicedefender on extreme.
Apart from that I doubt you will make a difference. Lowing the voltage of the CPU and juicedefender will stop all activities apart from cell service that drain the power. Dunno what more you could do without turning the phone off.
ahahaha sorry i forgot the link i'm a "lerdo" ahaahha
http://forum.xda-developers.com/showthread.php?t=1621808
this is the link!
i'm already using juice defender and i'm pretty satisfied about my defy battery life.. but i've found this thread intresting!
thanks again!
yeah could be interesting but what will it sacrifice. You get these builds by builders and if this is really the be all end all wouldnt they use it??
Like vsel you decrease the vsel you get better battery life but you sacrifice the speed of the CPU. Your CPU is faster running at a higher volt but it is using more power. So if you can run the same speed at lower volts it will use less battery.
Now this is a catch 22 as some times overclocking the cpu and undervolting it will be slower then the stock setting but you may gain more battery life.
I jus t wondering does undervolt really affect our battery life? How does it work?
When choose to undervolt it affect on performance, isn't it? Slower or stuttering when switch apps? With less energy less performance, does it wrong?
If it is, then how underbolt can improve peeformance better? :confuse
Sent from my Nexus 4 using xda app-developers app
Judging from my experience UV experimentation doesn't affect battery life, and if it does it's definitely by an inappreciable margin. It does substantially reduce heating issues though especially during high-intensity usage (Spotify, GNow, gaming etc). Just don't overdo it or you wind up rebooting repeatedly--"safe" threshold varies by kernel
It also has no effect on performance, it's completely separate from clock speed.
I UV to lower temperature The N4 is very heat sensitive so you'd be wise to UV if possible, the throttle can kick in very quickly on stock, because of the default CPU behavior(mpdecision+ondemand seem to ramp in a ridiculous manner). I am seeing temps in the mid-low 30s thanks to UV and I'm running turbo mode on Faux's kernel.