Okay, so my question is basically how stable is overclocking your g2? I typically keep it at 800 when I use my phone normally, than 1.5ghz for games. I wante d to keep my g2 at 1.5ghz forever.. is that bad?
My battery obviously increases in temp..
I just use 1GH. It's enough for all game now. and didn't see any bad to battery or phone
I've had my DZ for about three weeks now and all this time I've had it consistently overclocked to 1843MHz. At that high of a speed, I had to let the phone cool down after 20 minutes of use.
Just today I flashed pershoot's 1516MHz kernel and noticed no heat issues after ~45 minutes of consistent use (temps < 40C).
I have had my g2 for.... However long they been out. I have always been overclock to at least 1.5 with zero heat issues. I ran 1.8 and even 1.9 for a good long time as well. Those speeds have heat issues ones that required a battery pull a few times because it started heating up faster then i could shut down the phone. If your going to OC at those speeds makes sure you set temp profiles with alarms.
Sent from my HTC Vision using XDA App
ARM processors, like our snapdragons, are a lot more forgiving on the overclocking front than what you might find in your desktop, for instance.
I still treat overclocking on my phone like I do my computers, though... setcpu has a stress test built in that you can use if you're curious how "stable" your overclock is. but in my experience, I've found that you can get away with just playing around with it and using the phone normally and seeing how it reacts to different clockspeeds.
right now, I run it at 1.1ghz (24/7). I have run it at 1.5ghz (24/7) in the past for PSX/N64 emulators, but I've found with my new setup (pretty light; no widgets, very few things going on in the background, stripped as many unnecessary apps as possible, and not using any animations or fancy bits) that 1.1ghz is more than enough to be able to play the games I play on any emulator smoothly.
you should be fine at any speed that is currently available in the overclocking kernels we have with the exception of flippy's 1.9ghz kernel, which does require some monitoring to keep things cool and stable. but it still does vary from phone to phone. if you're running at 1.5ghz and the phone isn't doing anything wonky, then you shouldn't worry about it. if you're running it at 1.5ghz and you're experiencing stability issues, random force closes that aren't fixable through conventional methods, or heat issues, you should probably back off a bit.
some people have problems at 1.2ghz, some people are running at 1.9ghz all the time and never have problems... just find what works best for normal usage with your device and go with it.. it's not like we keep these things for more than a couple of years anyway, and the processor will be capable of handling the [stable] overclock for that period of time.
im always at 1.2ghz. 768 as min, interactive gov (when i use CM7) and battery has been fine, havent noticed any major issues. hard to tell if it was the rom bugs or OC being the issue but from what i read all my issues others have at various speeds so im guessing it was rom related
i think it depends on the rom.
when i use the Pyromod rom i dont need overclock but for other roms like sense roms those I require OC. I always keep it at 1400 when needed.
Related
Sent from my PC36100 using XDA App
http://forum.xda-developers.com/forumdisplay.php?f=652
I've had my phone overclocked 15% for months now...I pre-ordered and picked it up on June 4th (the day they were released to the public) and it's never been replaced. I rooted it right away using the engineering hboot method, and I immediately went to a rooted stock rom with a kernel that'd allow overclocking the very first time I saw one posted on this forum. I've never been able to run it at anything higher than 1152 mhz, but I've also never had any stability issues at 1152 mhz. I also allow it to go as low as 128 mhz all the time.
Since then I've played with various roms, and various kernels, but the first thing I've done when changing any rom or kernel, is always set the min and max CPU speeds again, and decide which governor to use. I've also always played with the undervolting strategies, from static to HAVS, and I've always been able to get away with the most agressive stuff posted without any stability issues.
Your mileage may vary, but thats been my experience with an overclocked Evo. I will admit I can barely notice the performance difference from 998 mhz to 1152 mhz, but I actually notice a battery life improvement...get it done faster so the CPU can go back to idling at a low frequency as soon as possible mentality I guess.
please watch what you say here. its not going to get you any help to curse and swear at other members. last warning
@MikeOD, which governor and what governor parameters have you found to work best for you?
I think the whole overclock boils down to what you do with your phone. If nothing overly cpu intensive, then there's likely to be little gain in the amount of saved time.
I actually have mine under clocked at 921 Mhz (came that way in the rom initially). UI was fluid enough and everything still seemed to work well/responsive. I get slightly better battery life too. Noticeable in the rate the batt % declines during active tasks (web browsing).
I heard there was a problem with stability issues before. Has it been fixed?
Also, do any of you guys feel the need to OC in the first place?
iArtisan said:
I heard there was a problem with stability issues before. Has it been fixed?
Also, do any of you guys feel the need to OC in the first place?
Click to expand...
Click to collapse
I tried OC'ing to 1,4 for a short time, didnt get any instabilities.
Which leads me to question two. No I don't feel the need to OC this phone, it is still good enough to cope with everything i throw at it.
The worst that will happen is that it will run a little hotter than normal. I was running Trinity Kernel on RasCream ROM clocked at 1.5GHz and it was fine, nothing crashed, no reboots, all was well.
Besides; It's a Nexus, it was built for this!
This varies for everyone
Sent from my GT-I9300 using Tapatalk 2
Meh. It all varies. No 2 chipsets are the same. What may work for someone else may not work for you. Trial and error is the only surefire way to find out.
Hi,
I agree with what has been said above, all the CPU's are not equal but actually the progress made by the kernel devs allows all (or almost) phones to run at 1.3* Ghz (1.34/1.35 Ghz, it depends of the kernel) without any issues.I think it's for all, actually I don't remember a user with issues at 1.3* Ghz...
And for most phones 1.5 Ghz is fine.For some others, above 1.5 Ghz is problematic but it depends also of too many factors.
Now it's not like it when the Genx came out, where 1.3 Ghz was the limit of CPU overclock for all the phones.
And many people can run stable at 1.65 Ghz, also it depends of the kernel.
For me for example my max CPU freq usable each day, so stable is 1.72 Ghz with Glados kernel, above (like 1.8 Ghz) it runs fine for 30 mins, sometimes 1 hour, but after always freeze/reboot... maybe my CPU can't reach this CPU freq or maybe my settings are wrong (voltage) ...
I agree, an extreme overclock like 1.72 Ghz is not really necessary for all day (heat, battery life, etc...) but a little overclock like 1.5/1.53 Ghz and you a difference in certain case (openning some apps, general UI, browsing, etc...).
But if we have the ability to test and play...why not... ,in any case for me it's yes, I like overclock and test the possibilities/limits of my phone, different settings...
Everyone does as he wants and it depends on what you want (battery life,a little more power in some situation like playing or a higher bench score ).
Well considering Texas instruments recommended highest clock speed for this processor is 1.5 ghz I'd say your fine. Anything above that is dependent on how well your chip set will handle it. Besides who honestly has needed to OC for anything other than benchmarks?
Sent From My Sprint Galaxy Nexus
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.
thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.
ok guys I downloaded cpu spy and after using the phone for 10min my phone never hit above 1.5 ghz ... I thought this phone was at 1.9 ,I did a lot of testing and still couldn't get the phone past 1.5 , no wonder things are not as smooth as they should be. I also upgraded to the new firmware it is a bit faster but I see the phone cpu is always around 1.5-1.1 ghz not good to run as smooth , also if cpu the low I'm sure gpu as low why all the animations run slow.
Edit : was playing angry birds star wars check back cpu ran at 1.1ghz -950mhz ...
Edit2: so i ran a anTuTu test and finally it hit at 1.9ghz and it drop down to 1.6ghz and 1.7 ghz for a few seconds. I really feel if this phone ran past the 1.5 it be a lottttt smoother i mean a lot.. just my 2cents trying to help out.
Sent from my SGH-M919 using xda premium
CPU factors
Listed CPU speeds are a maximum, a lot of factors play into that actually CPU speed you will see when running various apps.
Also, the CPU monitor reporting may not be 100% accurate, again due to several factors.
Also for reasons spread around this forum (all the battery threads popping up after the 1st week with the devices in hand)
The default cpu speed governors are likely set to preserve battery and only kick into high gear when the need REALLY presents itself.
Ie to samsung a little stuttering is fine if it means the battery lasts an extra hour in most cases
Most custom roms have different cpu governors in place - designed in part to respond more quickly to system load and increase performance.
Curious if overclocking the CPU and GPU is really worth it looking at performance vs battery life. My device seems zippy already, but I'm just wondering if overclocking would improve anything seeing as some other tablets are moving onto 2.0+GHz.
If so, what kernel would you recommend me to use?
I would not overclock it, if you think it is very fast already. Overclocking from 1.5GHz to 2+GHz is probably mostly used for people trying to get the highest benchmark score.
i used to test roms and over clock the kernels while testing now iam back to basics
as i noticed even with a small overclock the system got hot around camera area on most kernels
that was enough for me to stop oclocking