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.
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).
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.
could anyone suggest a safe clock speed for the play? i want to get a bit more power from the stock 1ghz processor but i don't really want to overdo it
Honestly, clock speeds are phone specific. For example, my phone might do just fine at 1.5, but your phone may not be able to go past 1.3, so you need to find your safe zone yourself.
Get an app that handles overclocking, SetCPU, AnTuTu CPU Master, etc. I use Rom Toolbox Pro. Move your CPU one step up, then play around for a while. If your phone doesn't bug out, go ahead and try the next one, until it won't go any higher without bugging out.
Make sure you don't lock your speeds at boot until you're sure it's safe.
I wouldn't recommend going above 1.6ghz even if your phone supports higher frequencies. It tends to get hot quite quickly at such high frequencies, and could be detrimental to the battery
thank you for the advice... ill try to see how my phone reacts to different clock speeds... and not go over 1.6
seagheart89 said:
could anyone suggest a safe clock speed for the play? i want to get a bit more power from the stock 1ghz processor but i don't really want to overdo it
Click to expand...
Click to collapse
i usually use 1.6 or 1.8 i feel that you should never oc it to the max it is allowed.
Depends entirely on the 'yield' of each individual processor, most can run over 1ghz but some can't, so to be safe all processors are set to the lowest safe speed.
My XP is stable at 1.8ghz. 1.9ghz causes occasional reboots, 2.0ghz is an instant crash.
Remember your unit will only get warm if the CPU is being worked hard, if it's idle then it will stay cool even at higher clock speeds. Using a more active CPU governer such as 'smartass' or 'interactive' will keep clock speed down when not required.
Also remember you can't overclock on the stock kernel.
Same here, I accidently overclocked to 2Ghz, instant crash. But 1.6Ghz is fine, yet eats battery like it's the cookie monster on crack.
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
There is definately some sort of bug in my note 2 or all note 2 cpus
Iv been trying to find out why nova3 and mc4 have random lag spikes and then smooth gameplay. At first like many people said
Gameloft games arent optimized well i belived that. While thats true to some extent heres what iv found
Using set cpu or tegrak to force the cpu at max clock fails after hitting 38c
Thus causeing lag in game
No matter what setting iv tried the moment my phone hits 38c the cpu
Locks back to 800mhz. My phone is rooted yet there is no way i can maintain the clock at 1.6ghz
Im now using androd revolution rom and that hasnt helped either. Does anyone else have this issue?
To test run nova3 or mc4 any level and stay in there moveing around after the phones warm enough(around 38c for me) youll notice
Stuttering. Check ur cpu and ull find its downocked to 800mhz
Dear nielo360,
Probably, you are reading the battery temp not the cpu temp since note2 cpu throttles at 80 c...
Try system tuner pro application to read real cpu temp...
If you are overclocking or wanna lock the cpu to max speed then you should do undervolting by installing custom kernels like perseus...
Try to undervolt both cpu and gpu...
Also try to lower your brightness to stay away from extra heat that screen makes...
Issue discussed before so you can refer to here :
http://forum.xda-developers.com/showthread.php?t=2058119
Hope all these helps...
Kind Regards..
Sent from my Amiga Note
Thanks for the reply, i did follow the thread and undervolted my cpu running at 1.3ghz 1025mv however my phone reaches 67c true temp and throttles very easily any idea if this normal i cant play any 3d games unless im sitting near a fan or ac. Every says they throttle at 80c
It is set to throttle for good reason. It may b irritating but I would let it be and not tamper with it.
Sent from my GT-N7100 using xda app-developers app
nielo360 said:
There is definately some sort of bug in my note 2 or all note 2 cpus
Iv been trying to find out why nova3 and mc4 have random lag spikes and then smooth gameplay. At first like many people said
Gameloft games arent optimized well i belived that. While thats true to some extent heres what iv found
Using set cpu or tegrak to force the cpu at max clock fails after hitting 38c
Thus causeing lag in game
No matter what setting iv tried the moment my phone hits 38c the cpu
Locks back to 800mhz. My phone is rooted yet there is no way i can maintain the clock at 1.6ghz
Im now using androd revolution rom and that hasnt helped either. Does anyone else have this issue?
To test run nova3 or mc4 any level and stay in there moveing around after the phones warm enough(around 38c for me) youll notice
Stuttering. Check ur cpu and ull find its downocked to 800mhz
Click to expand...
Click to collapse
The stuttering in mc4 has been driving me crazy.
I also used a tool to measure cpu and find that the game runs well for the first few matches and then it does tend to lock itself at 800mhz and the sideshow begins.
My phone doesn't get that hot, but something is definitely going on. I really hope that gameloft can optimize this game. These games running on ios are so much smoother that it's embarrassing for Android "super phone" users.
Sent from my Galaxy Note 2 using Tapatalk 2
The problem is not the cpu its the gpu throttleing as samsung has for some odd reason overclocked it. The fix for this is a bit tricky
If you use tegrak ultmate Do not force gpu lock at 533mhz this will underclock the cpu automaticly and make it unstable after a few mins instead
Set level 0 gpu 533mhz stock
Undervolt if your like
Set level 1 440mhz
1025
Seg level 2 440mhz
1025mv
.. leave the last level at stock 166mhz
Cpu you can scale it or leave it doesnt matter mine is locked at 1.3ghz
This works great for the most part and u wont notice the downclock as the clocks will move between 533 and 440 during heat.
nielo360 said:
The problem is not the cpu its the gpu throttleing as samsung has for some odd reason overclocked it. The fix for this is a bit tricky
If you use tegrak ultmate Do not force gpu lock at 533mhz this will underclock the cpu automaticly and make it unstable after a few mins instead
Set level 0 gpu 533mhz stock
Undervolt if your like
Set level 1 440mhz
1025
Seg level 2 440mhz
1025mv
.. leave the last level at stock 166mhz
Cpu you can scale it or leave it doesnt matter mine is locked at 1.3ghz
This works great for the most part and u wont notice the downclock as the clocks will move between 533 and 440 during heat.
Click to expand...
Click to collapse
i found that the real throttling problem is a security protocol that Samsung roms have. When the battery reach 41C the cpu throttles (no matter if its only at 60C cpu temp)
i dont know how to deactivate that protocol...but if you want, try CM10.1 or any other AOKP or AOSP roms and you´ll see that there is no cpu throttling unless the cpu reach 80C.
you´ll need "stability test" app (cpu stress testing, and you can watch battery temp), and "system tuner" app (to watch live cpu temp during the stress test)