Database Info

overclock p3600

hi guys.
i'll want know a good program for overclock my trinity.
it's possiblehave 500mhz rock solid?
thanks

http://forum.xda-developers.com/showthread.php?t=324781&highlight=overclock

Some people report Pocket Hack Master worked for them.
Able to actually change the CPU speed, and noticed some obvious changes in their device behaviour.
It's worth a try

well i was experiencing very slow speeds and it seemed too sluggish for a 400mhz cpu. well i install xcpuscalar(3.03) and it was showing my cpu was set at 200mhz. this is a fresh flash of htc official wm5 rom so i found that odd. well i set it to 500mhz and ive been running it stable and smooth no problems. much faster, very obvious, will have to test more to see effect on battery but it does have settings to scale the cpu according to load. ymmv

cecrops said:
well i was experiencing very slow speeds and it seemed too sluggish for a 400mhz cpu. well i install xcpuscalar(3.03) and it was showing my cpu was set at 200mhz. this is a fresh flash of htc official wm5 rom so i found that odd. well i set it to 500mhz and ive been running it stable and smooth no problems. much faster, very obvious, will have to test more to see effect on battery but it does have settings to scale the cpu according to load. ymmv
Click to expand...
Click to collapse
That might be a new release of xcpuscalar that does support the samsung cpu effectively.
Some people has tested that soft one year ago, but it appeared to be, even once set to 500 mhz only placebo effect. When check with other softs, the cpu speed remained the same.
Nevertheless, it's very odd that on a fresh bought device, you have only a 200mhz speed, half the normal one...
The Trinity run very slow sometimes, but this is a matter of optimisation of the ROM you are using, not necessarilly a problem with the cpu speed itself.
Another good and simple way to check your cpu speed is TCPMP. In any case, it's always better to double-check with another soft, rather than believe everything your overclocking soft says.

riri22 said:
That might be a new release of xcpuscalar that does support the samsung cpu effectively.
Some people has tested that soft one year ago, but it appeared to be, even once set to 500 mhz only placebo effect. When check with other softs, the cpu speed remained the same.
Nevertheless, it's very odd that on a fresh bought device, you have only a 200mhz speed, half the normal one...
The Trinity run very slow sometimes, but this is a matter of optimisation of the ROM you are using, not necessarilly a problem with the cpu speed itself.
Another good and simple way to check your cpu speed is TCPMP. In any case, it's always better to double-check with another soft, rather than believe everything your overclocking soft says.
Click to expand...
Click to collapse
after more usage i uninstalled xcpu. when you first run the program it is set to default 200mhz which is why i thought thats what i was really at. TCPMP says im at 390-400 no matter what. better not to have too many programs running and loading at boot. also i tried pocket hack master but that didnt work either. ill stick to sktools and trinityhack, those registry tweaks are what i think i really needed.

Overclocking Qualcomm 7201 on Android OS

Hi there!!
Seems to me no one hasn't began this knd of theme. So. Off. info:
Qualcomm MSM7201a
Two cores
ARM11 + ARM9
528 Mhz (one stated speed for two cores...)
So what is G1's heart for real?
This is quotes from here
#1
Jean-Baptiste Queru 26 нояб 2008, 20:37
Indeed, the CPU in the G1 is clocked lower than its maximum rated
speed to conserve battery life. It's running somewhere between 300 and
400MHz if I remember correctly.
JBQ
Click to expand...
Click to collapse
#2
jdc4429 27 нояб 2008, 17:04
Hi Jean,
So your saying that the CPU speed is not controlled by the Android
software?
I was looking through the code and found this in the arch/arm/mach-msm/
clock.c file...
617 #define CPUFREQ_TABLE_MAX 4
618 static struct cpufreq_frequency_table cpufreq_table[] = {
619 { 0, 81920 },
620 { 1, 122880 },
621 { 2, 245760 },
622 { 3, 384000 },
623 { CPUFREQ_TABLE_MAX, CPUFREQ_TABLE_END },
624 };
It looks like the max speed is set to 384mhz and it seems it can be
easily changed.
It also seems that the phone already downshifts the CPU based on this
table and the
screen_open/closed speed setting...
702 if (screen_on) {
703 policy->user_policy.min = cpufreq_table
[2].frequency; // 245mhz
704 policy->user_policy.max = cpufreq_table
[3].frequency; // 384mhz
705 } else {
706 policy->user_policy.min = cpufreq_table
[0].frequency; // 82mhz
707 policy->user_policy.max = cpufreq_table
[2].frequency; // 245mhz
708 }
Sure looks controllable to me through Android. Is it really that hard
to add a setting to allow min/max settings
to be adjusted by the user?
Thanks
Jeff
Click to expand...
Click to collapse
#3
Romain Guy 26 нояб 2008, 20:39
> Can that
> be changed in software on the fly and was it set below maximum speed
> to help with the battery issue?
No and yes
> Also is anyone working on adding hardware acceleration so we can take
> full advantage of the processor?
We have a prototype of SGL running on top of OpenGL (it was actually
shown publicly in the SDK 0.9) but it's not the correct solution at
the moment.
Click to expand...
Click to collapse
Coclusion:
1) Google DevTeam does not know, or don' wanna tell, ca we\how to change CPU's speed or\when it would be possible to get the hardware accelariotion etc.
2) From stated 528Mhz we get 384Mhz maximum, as stated by Jean-Baptiste Queru and the code quote.
Both these I suppose seems not fare for us users)
So, can it be solved through the OS modifing??

Oh yeah that's another good point -- almost all of my experience on mobile
hardware has been that the memory bus speed was far more of a performance
bottleneck than the CPU was. It generally just wasn't useful to run the CPU
at its fastest speed and consume more power, because most of what it would
be doing was sitting there waiting on memory.
Click to expand...
Click to collapse
I don't know what is more important, the memory/cpu ratio working at its best or battery life. We'll have energy plans soon for android me thinks..

interesting... Anyone want to give it a try?

It's very worthwhile to read the entire thread:
http://tinyurl.com/9kme8v
Of particular note, the effect on battery life of clocking the CPU at full speed, and the apparently minimal performance boost.
Of real interest, and the very obvious bang for the buck, is the speed of Dalvik. Note that it's 7-8x slower than comparable JITs. About in line with what you'd expect, but it does imply that if we want to see some serious speed increases - and, I would think, battery life improvements - replacing Dalvik would be the obvious place to start. Or making it JIT, of course.

might be but lets say im at home plugged in or what not... then we could scale our CPU... like BatteryStatus or integrate it into an app somewhat like Locale or Power Manager...
End users look at the End result. my phone is rated at 528mhz and it is running slightly over half its rated operating speed. Battery life? Give me 528mhz and let HTC and Tmobile Recall there $h*tty batterys

The only advantage I can think of for this is for demanding games for instance but any other time its good to have it under clocked to save on battery juice. and the phone is fast enough running at half its rated speed!
Phil

philje123 said:
The only advantage I can think of for this is for demanding games for instance but any other time its good to have it under clocked to save on battery juice. and the phone is fast enough running at half its rated speed!
Phil
Click to expand...
Click to collapse
once you get demanding apps installed such as hello aim. phoneplus dgalerts etc there is constant hiccups and the phone becomes bogged down like i said give me 528mhz and let htc,tmo replace there $h**ty batteries didnt they hear over a year ago there was a huge advancement in nano tech for batteries

diabolical28 said:
once you get demanding apps installed such as hello aim. phoneplus dgalerts etc there is constant hiccups and the phone becomes bogged down like i said give me 528mhz and let htc,tmo replace there $h**ty batteries didnt they hear over a year ago there was a huge advancement in nano tech for batteries
Click to expand...
Click to collapse
True, but *if* it is the CPU which is bogging down (which I am not convinced is the case), the solution is as I stated - speed up Dalvik - not to put the CPU into a mode which drains the battery down even more quickly than it does today. If the fix is to clock the CPU at a higher rate (which again, seems not to be the case), that's only a stepping stone to the ultimate solution, which is going to be removing some apps, since the battery life is marginal right now anyway.

The reason why Android is underclocked is posted in the full thread. After a certain point, the increase in speed you get by bumping up the CPU slows down, because it's limited by FSB speed. An example of this (not real numbers), is that a CPU running at 50% speed could actually be closer to 75% speed.
Sure, the CPU CAN run at 100% speed, but after the FSB slows it down, it'll only be 75%. So after a point, increasing CPU speed isn't worth it.

hmm
i wonder if we would get an app too monitor it or
under and overclock by adjusting a slider
anywhere from 50% to 150% or whatever is possible
that is anywhere from 264Mhz to 798Mhz which would be amazingly fast

gary, might as well just save your breath.

I believe JF has already tested some code to do this, but mentioned that it is highly unstable.

dirr said:
I believe JF has already tested some code to do this, but mentioned that it is highly unstable.
Click to expand...
Click to collapse
Adjusting the speed breaks things, at least so far anyways. But like he said JF is playing with it.

djind said:
I don't know what is more important, the memory/cpu ratio working at its best or battery life. We'll have energy plans soon for android me thinks..
Click to expand...
Click to collapse
Sure, it might not be entirely "worth" it in terms of performance/battery ratio... but that doesn't mean it isn't worth a try. People keep saying "don't bother" but nobody has actually tried an overclocked G1. Maybe it's worth it for demanding gaming or apps while the phone is (gasp) plugged in.

back when i had my wing and so did ttran. Which uses the OMAP processor it was able to overclock over 100mhz faster than it was meant to go. Had real good luck overclocked to 288mhz. Which made the phone run at the speed that it SHOULD have ran at... including faster loading web pages, faster loading everything basically. Which hardly is an issue with the g1, but imagine how much more snappy it would be with an extra 100mhz also? People say its not worth it and it drains the battery more.... umm... if anyone here owns a g1 (surely hope so at least!) you probably know that the battery sucks anyways and needs charging all the time. Would love to see a good OC app made for the g1 =-) (with scaling like battery status was for the wing, which underclocked when screen was off, overclocked when screen was awakened which was amazing for battery life, as the phone doesnt need much power to accept a call, but when the screen is lit.... scaling occurs and it bumps it right up to 288mhz)

I think its well worth a go.
We could start with very small increments.

Gary13579 said:
The reason why Android is underclocked is posted in the full thread. After a certain point, the increase in speed you get by bumping up the CPU slows down, because it's limited by FSB speed. An example of this (not real numbers), is that a CPU running at 50% speed could actually be closer to 75% speed.
Sure, the CPU CAN run at 100% speed, but after the FSB slows it down, it'll only be 75%. So after a point, increasing CPU speed isn't worth it.
Click to expand...
Click to collapse
I think the question is... Are there any circumstances where this may help...
And either way how difficult is it to add a control under settings to allow you to modify the default method?
You could basically apply the same argument to anything... Until someone tries, we will not know for sure. What next? Don't bother trying to add a swap file cause it may not help? Don't bother trying to speed up Dalvik cause it will take too much memory?
That's the fun of open source...
jdc4429

FSB could really be the bottleneck here. From my experience overclocking mobile CPUs (PXA255, PXA263, PXA270, Samsung 300Mhz, TI OMAP 850) several percentage change on FSB speed or Memory speed could make significant performance changes.
The last WinMob device I had - Dell Axim x51v had a PXA270 [email protected] Pumping the bus from 208Mhz to 230Mhz and the CPU speed from 624 to about 700 did abput 50% improvement in several bencmarks (floating point, integer calculations, memory speed, graphics subsystem).
On the other hand pumping the CPU to 1014Mhz, (0.99GHz, the highest 24/7 stable for my device) while lowering the FSB to 185Mhz (23Mhz drop) led to about 10% lower result than at stock frequencies.
700Mhz CPU, 230Mhz FSB was totally 24/7 under stress tests with almost no extra heat, providing aboyt 50% extra performance, while battery life was about 30-40% shorter.
My experience with it showed that it could be worth for short speed bursts, while running many apps. When you are finished you return to normal frequencies.

Wow! Thanks for the info man!!
Thus we can see, that by increasing the CPU up to it's stock 528 Mhz would be perfect?

it will be perfect when the speed of the cpu uses 528Mhz and auto adjusts: high speed - mid speed - low speed - sleep, "ondemand"
android should use ondemand kernel module which does exactly that. (maybe this cpu cant do that?)

Overclocking: How does this make sense?!

I'm familiar with overclocking when it comes to my PC, so I'm not a complete noob.
With SetCPU, there's no real "slider", it just steps up by it self.
So starting from 1GHz, I did a 'rough' test, to see when it'll crash (slide it up by one, run full Quadrant Standard test, slide it up by one again, repeat until crash, go back to the second highest, do a "torture test" to see if stable).
It didn't crash at the highest setting allowed by the kernel of 1.9GHz...
I'm doing the "torture test" right now.
That's almost a 100% increase in performance...
How is this possible? Are phone CPUs this good overclockers?
FYI, Quadrant Standard at stock 1GHz was around 1400, at 1.9GHz was around 2000 (not that Quadrant Standard really matters).

2000 on quadrant overclocked at 1.9 ist high actually its kinda low compared to how it comes out of the box good luck with battery and replacing that cpu
Sent from my Desire HD using XDA Premium App

mohkg said:
2000 on quadrant overclocked at 1.9 ist high actually its kinda low compared to how it comes out of the box good luck with battery and replacing that cpu
Click to expand...
Click to collapse
This isn't for everyday use, obviously.
Trying to find the highest stable clock, and going to run some MKVs, and lower the clockspeed until the MKV doesn't stutter, and have that clockspeed set for whenever I watch videos on my phone (currently at stock 1.0GHz, MKV files stutter like mad, but at 1.9GHz, it doesn't stutter).
Going to leave it at stock 1.0GHz (maybe underclock it) for any other usage.

O_O what is the purpose in overclocking what does it do
Sent from my Desire HD using XDA App

Your CPU will be fine as long as its not constantly at 2.0. I left mine at 1.84 for 2 days for **** and giggles, phone didn't even get hot.. if you were to permanently leave it at 1.5 or so, you'd probably have a new phone before the CPU burns out. And not all phone cpus can overclock as high as our particular snapdragons, the 2nd gen snapdragon just happens to be an overclocking monster. The hummingbird in my captivate was kinda unstable at 1.4, the inspire takes 1.9 like a champ.

M.leonard2 said:
O_O what is the purpose in overclocking what does it do
Click to expand...
Click to collapse
Overclocking makes your CPU run faster than what it was originally designed, and usually it only increases by 10-30% (which is why I'm flabbergasted at the almost 100% increase in clock speed).
For me, I want it because, like stated previously, the phone lags quite heavily when playing HD 720p (MKV) videos. I don't want to re-encode to standard mp4 (since most of my library is MKV or DIVX/XVID) to watch movies flawlessly.
di11igaf said:
Your CPU will be fine as long as its not constantly at 2.0. I left mine at 1.84 for 2 days for **** and giggles, phone didn't even get hot.. if you were to permanently leave it at 1.5 or so, you'd probably have a new phone before the CPU burns out. And not all phone cpus can overclock as high as our particular snapdragons, the 2nd gen snapdragon just happens to be an overclocking monster. The hummingbird in my captivate was kinda unstable at 1.4, the inspire takes 1.9 like a champ.
Click to expand...
Click to collapse
Yea, this CPU is a champ at overclocking.
I'm done with the "torture" test, and am pretty confident in setting it as high as 1.9GHz if needed.
Currently, 1.7GHz would play my MKV files stutter-free (starts to stutter at 1.6 and below), so I have 3 profiles:
Underclocked (768MHz)- normal usage,
Stock (1GHz)- when things slow down during normal usage, say flash on websites or Android 3D games,
Overclocked (1.7GHz)- for HD (MKV) video playback
And of course, have a Temp > 50C at the top priority, where it goes down to the underclocked (768MHz) profile.
P.S. The under 720p videos encoded in divx/xvid play flawlessly even in underclocked mode. This whole ordeal is strictly for the HD videos I have. I don't have any <4GB 1080p to test 1080p videos with... heh (stupid FAT32 format).

How does one get this SetCPU program? A file you can flash? Or is it an app?

h-visual said:
How does one get this SetCPU program? A file you can flash? Or is it an app?
Click to expand...
Click to collapse
It is an app. I believe you can get it for free here on xda.

h-visual said:
How does one get this SetCPU program? A file you can flash? Or is it an app?
Click to expand...
Click to collapse
You can't just use the app to overclock though. The stock kernel is only capable of 1ghz. You need a custom kernel that's set up to overclock. There are plenty to choose from, simple to install.

[POLL] Tested Dual-core ( 972 mhz) vs Single-core ( 1.836 Ghz)

Hello guys,
Since i`ve seen so many debates about single vs dual-core, today i was bored and i tested with antutu and quadrant this thing.( I know that benchmarks isn`t a real proof in day-to-day performance )
WANT THE SCRIPTS FOR UNDERVOLTING AND FORCING CPU1 ONLINE OR OFFLINE ? See 2nd post
SO , what I actually did:
-flashed a freshly new rom ( using elegancia 3.1.0 for about 2 weeks and i found to be very stable and smooth with better battery life than any other rom i`ve tested)
-flashed latest bricked kernel min 192 mhz max 972 mhz with gpu oc @300mhz, lagfree governor, I/O deadline, both cores online via init.d script, booted and tested with antutu and quadrant and then i let the phone settle for a while to see what is the power consumption in stand-by with battery monitor widget.
-after that, i flashed bricked kernel with only max speed change to 1836 mhz, cpu1 offline via inid.d script and made those tests again
Here`s what I got:
Antutu: 4827 (both cores online, clocked @ 972 Mhz)
Quadrant: 2592
BMW: -19mA
Antutu: 4593 ( cpu1 offline, clocked @ 1.836 Ghz )
Quadrant: 3393 ( cpu1 offline, clocked @ 1.836 Ghz )
BMW: -28mA
Those numbers doesn`t reflect exactly the user experience. Some apps opened faster with 2 cores, some faster with only 1 core clecked at higher speed. The only major difference i noticed was in the browser( stock ICS browser) where the more fluid experience was with both cores on.
I`m gonna test those 2 configuration further to see which one has better battery and post some screenshots.
I will add a poll to see which configuration you think is the best.

Be aware that SoC are not created equaly, so the UV script or OC will NOT work with all devices.
Unrar the archive and choose what you want
This files needs to be copied in /system/etc/inid.d and then set the right permissions ( read: all 3 needs to be checked; write: owner checked; execute: same as read) . You need a file explorer that has access up to root ( i recommand Root exploer)

Benchmarks should always be done using Performance governor for consistency

Michealtbh said:
Benchmarks should always be done using Performance governor for consistency
Click to expand...
Click to collapse
I knew that, but i wanted a more real-life experience, and in my opinion there isn`t that much difference in lagfree vs performance. I ran benchmarks 2 times and the scores where almost identical

Please be aware that because of the instruction sets hard coded at low level into the cpu it doesn not mean that 2x 900mhz cpu cores is equal to 1x 1800mhz cpu core because of the way in which the second core is utilised. Its exactly the same with pc's hence why sometimes an AMD cpu with 2 cores can give a better real world performance benchmark than an intel cpu with 4 cores. the same applies vice versa, it just depends on what instruction sets were used and how the cpu is used. Benchmarking stuff like this is not a reliable way to test

Jonny said:
Please be aware that because of the instruction sets hard coded at low level into the cpu it doesn not mean that 2x 900mhz cpu cores is equal to 1x 1800mhz cpu core because of the way in which the second core is utilised. Its exactly the same with pc's hence why sometimes an AMD cpu with 2 cores can give a better real world performance benchmark than an intel cpu with 4 cores. the same applies vice versa, it just depends on what instruction sets were used and how the cpu is used. Benchmarking stuff like this is not a reliable way to test
Click to expand...
Click to collapse
Thanks (I'd use thanks button,but i'm limited to 8 oer day) for clarifying this for me and any other users, this post should be sticky because many members on xda think that way. I am aware that 2x900 doesn't equal 1x1800, but I didn't knew the exact explanation. The only reason that I did these tests was to see which configuration gives the best battery life. Their not equal, but acording to antutu, quadrant and end user experience they are comparable

Thanks for your time in doing these tests... It might not be reliable but it was interesting to know bout it... Im curious between the two tests though, which test puts the cpu under more stress? the first test shows awesome result on the battery so being single core might stress the cpu more, im guessing
Sent from my HTC Sensation using Tapatalk

AndroidNeophyte said:
Thanks for your time in doing these tests... It might not be reliable but it was interesting to know bout it... Im curious between the two tests though, which test puts the cpu under more stress? the first test shows awesome result on the battery so being single core might stress the cpu more, im guessing
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
33% left and it's running for15 hours with 2 cores

[Q] Overclocking but no Exploding

Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?

MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
Don't overclock that high. 2419MHz at most. Overclocking too high will cause more heat and throttle earlier, only useful for a short benchmark such as HWBot Prime or Quadrant (Antutu takes longer and will overheat by the time it finishes). Trinity also supports up to 3014MHz, OP hasn't been updated.

MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
You don't want to push the phone too much I think the Nexus 5 runs at 2.3 GHz. 2.7 MAY not be too bad but honestly, the phone runs pretty smooth as is. What benefits are you looking for from overclocking?

Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.

if you really wanted, the phone won't explode if you run it at 3015mhz either. the worst that will happen is that your phone won't be able to run that high, and will freeze and reboot.
and don't listen to all.. run your phone how YOU like. yes, it'll cause a little(not much) more heat, and will throttle a little earlier, but that's why people like me disable throttle, so that's a non issue. I run my phone at high CPU speeds all the time, and use 2880mhz high/300mhz low quite often. just because I feel like it, no other reason.
oh, I run trinity as well, and do all of Trinity's testing

MaLing15 said:
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
Click to expand...
Click to collapse
It's just what @jsgraphicart said. You're not really getting more out of your phone by overclocking. It's not going to run smoother, and most games don't lag anyway so they probably won't run better. I think most people just do it for benchmarks or just to check if it can run on a certain clockspeed.
Also what @simms22 said. You can do it if you want to, but simply because you want to because as far as I know there aren't really any benefits.

Back in my Palm Pre days, we used to overclock that thing to 1GHz. The default setting was 500MHz. I think it was even pushed to 1.2GHz. And it ran fine. But back then, you could tell the difference between a little lag at 500MHz and smoothness at 1GHz. With this phone and how Android has gotten smoother with every update, it's kind of hard to see any difference when overclocking. It will be smooth regardless.

oh, benefits, not really. a little more speed, yes. bit I would never call it a benefit, unless the speed difference was drastic, and its not.

As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.

bblzd said:
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
Click to expand...
Click to collapse
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol

Lethargy said:
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Click to expand...
Click to collapse
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.

simms22 said:
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
Click to expand...
Click to collapse
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices

Lethargy said:
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Click to expand...
Click to collapse
on some devices??? on most devices! anyways, stability is overrated

LOL...no explosions on XDA allowed!