when overclocking which one is best for beast mode?
LV or SV?
LBOG_Kush said:
when overclocking which one is best for beast mode?
LV or SV?
Click to expand...
Click to collapse
LV or SV? I am taking it you are using Faux's kernel in that case LV means low voltage and SV means stock voltage. Which has more to do with power efficacy as lower voltage will be more battery consumption friendly. Far as the OC thing goes they are both sharing same enchantment as they don't differentiate. So try LV first and if it does not bootup as not all chips are same then try SV.
thanks for the info and yes they both load up fine
but in LV my phone isnt that hot as it is in SV
weird? because u say LV eats up more battery so its working more right?
idk but thx good info nice benchmark score
what would be the best scaling for overclock
i run performance at 1.84 the whole day seems to be working fine
but like to here info from anybody
LBOG_Kush said:
thanks for the info and yes they both load up fine
but in LV my phone isnt that hot as it is in SV
weird? because u say LV eats up more battery so its working more right?
idk but thx good info nice benchmark score
what would be the best scaling for overclock
i run performance at 1.84 the whole day seems to be working fine
but like to here info from anybody
Click to expand...
Click to collapse
I know i'm going to stand alone on this one.
Unless you are trying to prove something to someone or get stupid high Quadrant scores there is no real reason for overclocking your phone.
I'd recommend backing down from 1.84 and using something less than 1.5.
LBOG_Kush said:
thanks for the info and yes they both load up fine
but in LV my phone isnt that hot as it is in SV
weird? because u say LV eats up more battery so its working more right?
idk but thx good info nice benchmark score
what would be the best scaling for overclock
i run performance at 1.84 the whole day seems to be working fine
but like to here info from anybody
Click to expand...
Click to collapse
No I said LV uses less power where SV is using little higher voltage. If you want balanced device I would recommend you use LV. Far as scaling to max @1843mhz all the time goes it will have adverse effect in long run. BTW only reason your phone is running hot is because you have it scaled at max frequency.
HKM said:
Well yes if you OC you are in danger of frying the SoC due to heat as you might know from middle school when thinks are hot they expend and when its cool they contract. So this consent extend/contract cycle has impact and can fry or crack the circuit in long run thus limiting the life expectancy.
Now that being said OC does have its power more for us its the control so we can manually increase the power when needed like I do to conserve battery power and underclock it when power is not needed as it will waste battery. Based on how you have setup you can setup mCPU profiles but make sure when its idle (screen off) you have the lowest min frequency selected.
Click to expand...
Click to collapse
neidlinger said:
I know i'm going to stand alone on this one.
Unless you are trying to prove something to someone or get stupid high Quadrant scores there is no real reason for overclocking your phone.
I'd recommend backing down from 1.84 and using something less than 1.5.
Click to expand...
Click to collapse
No we all share that as no need to scale to max when not needed that way you only kill more battery and slowly wear out the SoC. lol but ya if you are showing off your phone to your friend then scale it other than that I don't see what anyone need to run at MAX scale for 24/7. I personally have my setup underclocked.
wow thx for clearing it up
yes max is on 24/7 for couple more days
just testing how well it can work
so ill guess ill stick with LV for now
since ill be out IT'S FRIDAY
THX blackshelf and others
again if u have info on scaling blackshelf you'll make me smile again LOL
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 guys, just want to check it out what is going wrong with my HD2. From the start, using mattc 1.5 wit zImage 384mb ram was able to hit at least a 1350 easily. Yesterday I switched the zImage to the fullram settings with the graphical fix, i had a quadrant of about 1392. However, since today morning, my quadrant hit super low of 900+, and now I keep getting values about 1000+. How come?
LittleMerc said:
Hey guys, just want to check it out what is going wrong with my HD2. From the start, using mattc 1.5 wit zImage 384mb ram was able to hit at least a 1350 easily. Yesterday I switched the zImage to the fullram settings with the graphical fix, i had a quadrant of about 1392. However, since today morning, my quadrant hit super low of 900+, and now I keep getting values about 1000+. How come?
Click to expand...
Click to collapse
it cold be any of these things:
if youre using set cpu it may have enabled a profile with lower cpu speed
you could have something running in the background hogging up recousces
you may have just brought youre phone out of sleep so the cpu may not have scaled up completely yet
or it could be something that has nothing to do with any of these, ust throwing some ideas out there
what he^^^ said.
try disabling profiles, and setting 'main' governor to 'performance, in setcpu
this should illiminate low-speed setcpu profiles and prevent the need to run multiple tests to 'rev-up' the cpu.
if you still get low scores you can illiminate setcpu from the equation at look at background apps etc.
(re-enable profiles etc after testing)
LittleMerc said:
Hey guys, just want to check it out what is going wrong with my HD2. From the start, using mattc 1.5 wit zImage 384mb ram was able to hit at least a 1350 easily. Yesterday I switched the zImage to the fullram settings with the graphical fix, i had a quadrant of about 1392. However, since today morning, my quadrant hit super low of 900+, and now I keep getting values about 1000+. How come?
Click to expand...
Click to collapse
WOO HOO! Yea, u guyz rock... After disabling the profiles and enable performance in setcpu, i scored 1436! But somehow its weird, cause before this I used to run the quadrant without disabling those settings...
* I just set it to performance mode, I noticed my device heat up very fast... 43.1 C...
LittleMerc said:
WOO HOO! Yea, u guyz rock... After disabling the profiles and enable performance in setcpu, i scored 1436! But somehow its weird, cause before this I used to run the quadrant without disabling those settings...
* I just set it to performance mode, I noticed my device heat up very fast... 43.1 C...
Click to expand...
Click to collapse
Yeah probably best not to leave it on performance (constant 998Mhz) all the time.
Although Last night I ran quadrant on 'performance' for half an hour and topped out at 39 C
plus it seemed as if battery life was as good if not better than with 'on demand' setting.
Is it possible that the throttling and switching speeds actually uses more power than leaving a constant speed???
might be something to test long term but while keeping an eye on temperatures.
As for why you got low scores today:
JJbdoggg must have been correct when he said the profiles could be the cause (evidenced by the result you just got).
Now the question is... which profile was activated to give you the low scores? is your battery level below your set threshold?
Im getting kinda fustrated here... i tried CM7 and currently on Ice Glacier and im having a problem where when i try to overclock my phone (even if its not so high) it gets frozen and needs a battery pull... i know that some cpu's cant handle frequencies like 1.8ghz, but even at 1.2 / 1.3 / 1.4 etc. i still get it. I switched from smartass, ondemand, and other governers and still freezes... any advice? Or am i stuck with the weakest link??
mike21pr said:
Im getting kinda fustrated here... i tried CM7 and currently on Ice Glacier and im having a problem where when i try to overclock my phone (even if its not so high) it gets frozen and needs a battery pull... i know that some cpu's cant handle frequencies like 1.8ghz, but even at 1.2 / 1.3 / 1.4 etc. i still get it. I switched from smartass, ondemand, and other governers and still freezes... any advice? Or am i stuck with the weakest link??
Click to expand...
Click to collapse
have you tried flashing another kernel?...maybe another Faux kernel on low voltage or maybe try Grankin v.05 kernel
Freek91 said:
have you tried flashing another kernel?...maybe another Faux kernel on low voltage or maybe try Grankin v.05 kernel
Click to expand...
Click to collapse
im using faux right now. ill see if i can find another one thats good to try out
thnx
i always thought that stock voltage was the more stable of the two since thats why i flashed it first when i had this issue... Anyways, tried faux low voltage and cranked it up to 1.8ghz to see how it goes. PLayed around with it so see no freezing yet. but performance was pretty much the same so i tried quadrant and see... i get an average of 1600 so thats pretty low IMO. As soon as i change to ondemand governor... it froze
back to the drawing board
mike21pr said:
i always thought that stock voltage was the more stable of the two since thats why i flashed it first when i had this issue... Anyways, tried faux low voltage and cranked it up to 1.8ghz to see how it goes. PLayed around with it so see no freezing yet. but performance was pretty much the same so i tried quadrant and see... i get an average of 1600 so thats pretty low IMO. As soon as i change to ondemand governor... it froze
back to the drawing board
Click to expand...
Click to collapse
well like im sure you've seen or heard...all hardware is different
so while 1.8ghz maybe slow...going down to 1.5 maybe quick and the opposite maybe true for someone elses phone...they may just totally fly at 1.8 while they grind to a halt at 1.5
so keep messing with it and see what happens...change clock speeds...change up the governors...just dont OC it to 1.8 and think the phone will magicly hit a 4100 quadrant and not have any issues
worse case...flash a different kernel and see how it acts
also on that topic...you said you were running IG...did you run the stock kernel for any length of time? did you try and OC that one?
I am going to be getting an Atrix in the next few days and will install the Aura ROM right off the bat, but im wandering, since it appears to use an OC'ing kernal, what effect will this have on heat and battery life? presumably negative, but how much so? i dont want another phone which heats up like mad, but i do like the look of the ROM. please help out an Android n00b
thanks
Just because it can overclock doesn't mean you have to. I use set cpu and keep mine undervolted and set to 1.1ghz. Idle around 30 celsius and when I game it gets up to 50 degrees.
Sent from my MB860 using xda premium
the atrix on stock 1.0 ghz gets REALLY hot so yea i would assume it would just get hotter MUCH hotter but you can get a setcpu and just set your processor down when you dont use it much or make profiles to automatically do it
great, so the rom just allows OCing, not forces it? thats good to know, thanks
ishamm said:
great, so the rom just allows OCing, not forces it? thats good to know, thanks
Click to expand...
Click to collapse
it will automatically clock itself to 1.3ghz, you'll need a program like SetCPU or PimpMyCPU to set it to not OC itself.
i suggest SetCPU myself, it can be found on the market. i prefer buying it over getting it for free here on XDA, we gotta support our devs right?
i want to know if its safe to overclock my samsung vibrant to 1200 mhz. will doing that shorten the life of my phone in any way.
tinye99 said:
i want to know if its safe to overclock my samsung vibrant to 1200 mhz. will doing that shorten the life of my phone in any way.
Click to expand...
Click to collapse
It will definitely shorten the life of the battery. As for the phone itself I can't really say. I used to use my vibrant @ 1200mhz daily while running bionix 1.3.1. I never really noticed any wear and tear from the overclocking. If your phone runs warm while overclocking you should really consider running the stock voltages. Your phone may overheat and fry your cpu gpu with the high temperatures. So be careful when overclocking.
Meh i dont completely agree...
It will only shorter the life of your battery because the processor will draw about 20% more power which is very small compared to the like 20x more power the lcd takes up.. i dont think youll feel the difference.
The heating up i disagree with too since ive seen processors reach boiling point of water and continue to work.. thats not to say they all will but ive oced my phone to 1.6ghz to benchmark for several minutes and it never got above 41*... the battery heats up alot more when its charging than the processor does most of the time so i wouldnt worry tooo much about that.
Now as to whether the phones llife will lower... yes probably.. youre putting more stress on the processor than if you dont oc.. honestly tho, processors dont die very often so i oc all day as my daily runner, usually to 1.4ghz if my kernel will do it..
Up to you and honestly all of this is my opinion based on my available info etc.. hope this helps
sent from the xda app on my android smartphone.
I have mine Oc to 1.5 and no issues. 1.5 is the Max I would go.
Sent from my SGH-T959 using xda premium
Everything I have read says 1200 is completely safe. I run mine at 1460 with no issues. It obviously draws more battery but using Voltage control app you can adjust the level of battery.
Sent from my SGH-T959 using xda premium
You would be fine with 1.2Ghz, but look into a kernel that supports some slick CPU scalers (smartass is a good, easy choice). You can set that (1.2Ghz) as a max clock and you can let the scaler determine how it gets there (if need be). Running only 2 clocks (OC and deep sleep) seems a bit overkill to me, but to each their own.
Like everyone else said, you ought to be perfectly fine with that value.
The highest I would go is 1500 though
kaiser_bun said:
You would be fine with 1.2Ghz, but look into a kernel that supports some slick CPU scalers (smartass is a good, easy choice). You can set that (1.2Ghz) as a max clock and you can let the scaler determine how it gets there (if need be). Running only 2 clocks (OC and deep sleep) seems a bit overkill to me, but to each their own.
Click to expand...
Click to collapse
Lol, running an overclock on a phone seems a bit overkill to me...
Think about this.. How much copper is strapped up to your phones cpu?
Would you overclock your desktop on a stock cooler?
I feel sorry for the saps who buy phones second hand(especially after reading this thread). (hey wait a minute, that's me too.. Lol)
I never overclock anything.
Ever.
(learned my lesson with an amd Duron 733 back in the day)
Sent from my SGH-T959 using XDA