Sorry i had to post this here, i couldn't reply on viperboys thread. Ive been able to keep 1600 mhz running after reboot by opening cpu5.sh with script manager and selecting execute.Hope i could help. Sorry if i couldnt.
Thanks but this is known though. U can use script manager or gscript to do this. I use to have it like that but changed it back. I'd rather overclock on demand. I can use my Prime in balanced mode with no overclock n still be fast as a mofo in everything. Amazing how powerful device already is stock. But evertime I see someone mention overclock, it usually makes me go apply mines..lol. I love it but not the shortened battery life. Plus I have a method to take regular overclocking a step further than vipercontrol or ATP tweaks. I can make it so that all 4 cores run @ 1.6Ghz at the saw time, all the time. Regular overclocking doesn't do this. But battery drains even faster. Sometimes we take stock speedsfor granted on prime. Amazing how powerful it is stock and the great battery life it gets. Usuallyif I overclock, ill make sure I'm near a power source.
Dang, now u made me wanna overclock...SMH....
What are you using to overclock?
Related
Hey all,
I come from an extensive background in OC'ing my own systems, pushing them to the extreme for noticeable performance increases. The one thing I know though, is that it does add wear and tear on the components, and shortens their lifespan. Is overclocking the Vibrant really worth it? I'm not sure if, with a ROM like Axura 2.2.5.7 which is blazing fast already, an extra 100 or 200 mHz is really worth the risk/performance.
What do you all say?
howetechnical said:
Hey all,
I come from an extensive background in OC'ing my own systems, pushing them to the extreme for noticeable performance increases. The one thing I know though, is that it does add wear and tear on the components, and shortens their lifespan. Is overclocking the Vibrant really worth it? I'm not sure if, with a ROM like Axura 2.2.5.7 which is blazing fast already, an extra 100 or 200 mHz is really worth the risk/performance.
What do you all say?
Click to expand...
Click to collapse
the only reason i OC is basically just so i can tell myself that i am OCing. If that makes ANY sense. its basically just my phone OCD.
to answer your question, even though you kind of already answered it yourself: the only reason you would actually NEED to OC is if you game a lot on your phone, if you do a lot of multitasking, or if you have a lot of data transfering going on (which i do). other than that, our processor is pretty powerful, and can handle 95% of what is thrown at it.
With that said, since youve indicated that you are satisifed with your phones performance, i would say the only thing you should definately do is install a lagfix (if you havnt already). if you dont need to OC, do your battery/hardware a favor, and dont.....unless you have phone OCD like myself.
PS - not to ramble on, but there was actually a 2-day period where i actually wasnt OCed and i didnt know it (i guess my app reset itself or something). i remember saying to myself during that time that my phone phone seemed a little laggy and much slower than usual....then once i discovered that my OC wasnt applied, it made sense. but keep in mind, i have my phone doing a lotttttt of things constantly, so OCing may not have the effect on lighter users that it does on myself. pretty crazy what a .2 ghz difference makes
Like above stated, OC is only needed if you do some intensive task on your phone. In addition, most of the Overclocking Kernels are targeted at a broad audience, what I meant by that is the developer bumps up the voltage enough so that only a small amount of people experience crashes. However, user generally have no control over the voltage themselves and any increase in voltage is bad for electronic components. (exception being some of Eugene's kernels which allows UV by user).
I don't, its not needed. I like my battery life.
Sent from my SGH-T959 using XDA App
I dont usually oc unless I am near a power source. last night i tried the Dow kernals and wow my phone was dead within ours even while in standby. Imo thats just nuts. Even while Oc'd it shouldnt die that way.
What I am looking for is a kernal thats compatible with nero v3 that will maintain battery life aslong as I dont oc.
I have seen this post http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28&page=1 on Eugenes forum but non of the info makes sense. The one that does make sense has a older modem than the one I am using.
I guess I am use to the hd2 in which I would underclock to maintain decent battery life and use profiles. It doesnt seem like this cpu likes the profiles. amirite?
I would OC no question if we could get a UV kernel with good battery life like we did with Eclair. I won't do it with Froyo because of the terrible battery on i9000 kernels.
Sent from my SGH-T959 using XDA App
What TopShelf10 said is correct. Basically the trade off is this.... faster kernel.......quicker battery drain. That is the trade off. I have used oc kernels ...I do not use the phone for games, so EVERY thing I do on the phone the oc is not necessary. That statement is true for 95% of us.
BUT, that said, there is some cool macho feeling you get when your phone is in overdrive, just like my car, 350 hp but I live on an island that only allows 25mph speed limit...still, it doesn't change that feeling of awesomeness I get when I start the engine
I had nothing but issues with each and every OC ROM I tried. App alarm, pandora, slacker, ect. It was always something. My phone would actually get random freezes so it made the phone feel slower. Voodoo or OCLF on the other hand work wonders.
is it worth it?
well, here were the trades i had with dow14:
going from 13-14mflops to 18-19mflops in linpack (yeah, it's a benchmark, but it's hard to otherwise convey how the oc directly translated to the phone being extremely fast otherwise).
battery life went from easily going 22+ hours between charges to going 6-8 hours between charges.
however, with the core 1.2 oc i had great battery life and performance. so i assume (and have gathered from reading people more knowledgeable than me) the battery downside is due to it being a i9000 kernel. so hopefully/eventually we will get source for the vibrant 2.2 kernel and get an oc kernel with similar performance but much better battery life.
and until i flashed nero v3 and using voodoo, i kept super io and dow14 kernels on my phone so i could flash the oc if i wanted the performance or flash super io for battery life/day to day.
Just curious is most people who root/use custom ROMs overclock, and if so, what settings do you typically use in SetCPU?
I'm using a S2, rooted with latest Unnamed ROM and find myself contemplating if I should make any changes with SetCPU. Lots of options, and Unnamed has all the different governor options, etc. just really looking for some best practices that people who overclock often.
Would appreciate seeing what you consider to be stable overclock options that give a good boost without causing excessive heat/stability issues.
I'm coming at SetCPU with limited experience so I do appreciate any tips that might see rudimentary, or if there are better resources that teach about this I'd appreciate any links as would like to get a better technical understanding of all this. Thanks in advance.
I use No Frills CPU, and I just set it to 1.6 max/ondemand. Absolutely no heat issues or stability issues, so I just stuck with it. Battery life is good.
most maybe but only by a little bit. a good number of people underclock and undervolt their devices to try and get better battery life. to be honest, the newer phones dont need overclocking to handle the current apps and stuff. the older phones like the nexus one and older need overclocking tho. i leave my gs2 stock. what we really need is dual core support before OC becomes worth it on my phone. ymmv
I have never overclocked mine, phone runs smooth as butter at 1.2 so I don't see the need to go farther. Plus I like my battery lasting more than 24 hours...
I overclock my s2. im running unamed 1.3.0. I like run different speeds at different at different battery percents. 1.6 till 75% 1.4 till 50% 1.2 till 25% 1000 till 15% 800mhz till dead. i had some problems with 1.4 ghz but i tweeked the voltage and that did solved my problem. I'm at 50% battery with normal usage. display 1hr 25mn phone calls for 47min and android os for 56min. my phone doesn't get any hotter then it did before i overclocked. I just did it to say i did. It will prolly help a little unless you like emulators then it will help alot. i have to overclock my iconia a500 to 1.6 if i want to play n64 games.
I'm on UnNamed 1.3.1 with the latest entropy dd kernel and am very happy with the stock CPU speed
Sent from my Samsung GT-I9100
Just wondering if anyone has done this with success. I have heard of speeds as high as 2GHz and was skeptical of this being safe. I figured it would cause some overheating issues. Also what is the best app for this? If this is done is there any noticeable differences in performance(most likely as this doubles the CPU power)? How much battery life lost? Is it worth it?
Thanks
Seriously, use the search or take a peek in the dev section. 1.6 GHz is no problem at the moment. Oh, and for me, it is worth it.
Check out vipercontrol mod in dev. Section. Allows overclock to either 1.5 or 1.6ghz. PRIME CAN EASILY HANDLE this as it was tested by Asus themselves on those speeds. It was seen in the source at first but we couldn't use it. NOW Viperboy made it possible to use those higher speeds. Its more of a mild to normal overclock. Its very easy to do. You will need to install vipercontrol mod to your prime and also terminal emulator. INSTRUCTIONS are in that thread.
WE have even found another method to run parallel to vipercontrol mod to allow overclocking of all 4 cores to 1.6Ghz. Vipercontrol, St the moment, doesn't do that by itself. JUST ALLOWS normal overclocking as Asus had it.
Seems kind of odd that ASUS backed off on the performance by 30% don't you think? Maybe they just wanted to do more testing, or maybe it was a last minute change based on their first prototypes.
Mine seems OK at 1.6, but I don't feel the need to overclock it in general use - unlike my phone which I think will have a shorter life as a device anyway.
tshoulihane said:
Seems kind of odd that ASUS backed off on the performance by 30% don't you think? Maybe they just wanted to do more testing, or maybe it was a last minute change based on their first prototypes.
Mine seems OK at 1.6, but I don't feel the need to overclock it in general use - unlike my phone which I think will have a shorter life as a device anyway.
Click to expand...
Click to collapse
I think it was more about more money down the road. AS I'm sure you've heard of Lenovo tablet coming out months down the road. Its gonna use exact same tegra3 chip except with the 1.6ghz enabled on it.
THINK of it this way, why would Asus/Nvidia release its first quad core device already at 1.6ghz? Its already the most powerful tablet at its current state. They did this so down the line when newer tablets come out, it'll be more incentive to like the device or think it's more powerful if its clocked higher. If prime came out with 1.6ghz enabled already, then how would that look to consumers who buy tablets months later that have exact same speeds. PRIME would be the better value and those newer tablets wouldn't be all that appealing, As far as power goes. SO the newer manufacturers can have something to boast about. Like hey look at our device its clocked higher therefore more powerful. Another reason also they didn't enable it on the Prime was for battery life. At its current state, stock, prime gets excellent battery life no matter what mode you in really. HAVING 1.6ghz enabled, as I do now, drains the battery at least at the same rate as performance mode or more. PLusbif you add the extra boost to vipercontrol overclock using system tuner, then battery really drains alot faster. Because then I have all 4 cores running Max 1.6ghz at the same time. Viper control doesn't go that extreme, yet.
YOU ALSO have to remember Asus and Nvidia designed the Prime together. SO prime n tegra3 speeds are really a testing ground for future setups in future tablets. That's how we were already able to see the higher speeds a couple updates back but couldn't use them till vioerboy made it possible or you figured out how to do it with root and going into /system/etc and executing the cpu5.sh script.
I LOVE the overclock but find myself now going to stock speeds to see how they compare. STOCK speeds are really good, especially with ICS. EVERYthing is smooth n superfast.. Overclocking does make it even faster but the tradeoff is slightly faster battery drain. PLUS there's nothing out now that stock prime really can't handle. SO no real use for needing to overclock, yet. UNLESS you just want your device to be the fastest it can be. I keep switching now. Lol. Ill have it on stock speeds n as soon as I see a mention of overclock. It compels me to do it. N vs. Versa. ACTUALLY. Even with vioerboy overclock, battery life is still good. Just not as good as it would be on stock configuration. Now once bootloader unlocked, we will see overclocking paired with undervolting. So we can get Max speed and Max battery life. Or at least get the overclock to get same battery life or better as stock configuration. DONT be surprised if you see us hitting 2Ghz overclock soon. Its coming. Then if paired with system tuner, we could have all 4 cores running @ 2Ghz a piece all at the same time. unbelievable!
Hello! i am in the process of overclocking my thunderbolt in order to get better performance with the eternity rom, and i was wondering what you guys oc your phones to? and if you do, what program/setting do you use to do so? (i plan to use a script in init after have found suitable settings)
I, personally, find it pointless to OC the Thunderbolt. The phone is fast and smooth enough for me on the stock speed, plus the battery life is bad enough without adding more strain to it.
However, if you insist on OC'ing, 1.2GHz is a safe bet. Some people can get to 1.4GHz, but then you run into freezing and random reboots. Also remember that individual phones handle overclocking differently. Where one phone can run perfect at 1.4GHz, another might freeze instantly when going that high.
Good OC'ing programs include SetCPU, No Frills CPU, and ROM Toolbox.
I don't overclock. That being said i have OC'd my phone b4 i have had it up to 1.8 Ghz stable, but it doesnt seem to make anything run faster. I use the Thundershed version of CM7 and its super fast. I dont think it could get much faster. and without overclocking i get better battery life.
thanks for the info actually ended up going with the lean kernel which is oc'd on the kernel level, works fairly well
lacrosse1991 said:
thanks for the info actually ended up going with the lean kernel which is oc'd on the kernel level, works fairly well
Click to expand...
Click to collapse
Leankernel is tops. I use battsaver mode which is stock speed and undervolted. Smooth as butter on my phone.
Sent from my ADR6400L using xda premium
Little by little I'm learning. I install no frills cpu overclock and did NOTHING with it so far.
It does, however, appear that this phone with jmz kernel is capable of oc.
I'd like to try this responsibly unless someone has good reason to avoid it.
So it's sort of an open topic...
Have you tried oc the desire 610?
What do you set it to?
Do you apply it automatically on boot?
What are the potential dangers of this?
I overclock my rpi openelec with pretty amazing results and it's worked fine for a long time. But this will be the first android device I've attempted it on. If in fact I do...
No frills works well. I tested it on my kfhd7 running cm11 and wow!! What a difference!!!
Our phone obviously has better hardware but after trying it ion fire I bit the bullet and tried it on desire. The results might've been placebic but it feels smoother to me. Of course I use modest settings. But did some reading beforehand, this app has safeguards built in. Been running it awhile. Battery drains a little faster so I switch to conservative when I'm not home.