[Q] Shouldn't we just shift the base clock speed to 1.5GHz? - TouchPad Q&A, Help & Troubleshooting

Technically speaking all TouchPads, black or white ones have the same SoCs, the APQ8060. It's factory clock should be 1.5GHz, which the white TouchPads are set on, but the black ones are all clocked at 1.2GHz.
So if we treat it as a 1.5GHz base shouldn't we 'technically' have more overclock head room, ignoring the fact that we don't have proper kernels for that anyways?
I'm just curious on why the CM7 builds didn't use the SoC factory clock and instead followed the HP settings. Because with the kernel as it is, we can get to a maximum of about 1.8GHz using any basic overclocking program which is only about 20% over the factory speed.

they might have lowered the voltage in addition to running it at 1.2 as opposed to 1.5G. that means even if you want to set it back to 1.5G, settings still need to be looked at closely. running it at default 1.5G does not give you more overclock head room either, as the final speed that your particular touchpad cpu can run does not depend on that.

iamsamsamiam said:
Technically speaking all TouchPads, black or white ones have the same SoCs, the APQ8060. It's factory clock should be 1.5GHz, which the white TouchPads are set on, but the black ones are all clocked at 1.2GHz.
So if we treat it as a 1.5GHz base shouldn't we 'technically' have more overclock head room, ignoring the fact that we don't have proper kernels for that anyways?
I'm just curious on why the CM7 builds didn't use the SoC factory clock and instead followed the HP settings. Because with the kernel as it is, we can get to a maximum of about 1.8GHz using any basic overclocking program which is only about 20% over the factory speed.
Click to expand...
Click to collapse
HP most likely turned them down for battery life concerns (a rather common practice, Apple used to do this on the iPhone before they started making their own chips) and then undid it to justify a higher price on the white models. CM most likely is keeping it so that battery life will be comparable once its issues are worked out.

For now 1.2ghz is fast enough for me, i would rather have the better battery life.

Well, if i remember correctly, in WebOS there was no battery or heat issues changing the clock speed to 1.5GHz. Basically, the battery life was the same and the system temperature was about 2 degrees higher, and was well within the safe range. It just seemed like there was no benefit in clocking it down.
Maybe there are a battery benefits in Android, but as it stands the battery expectancy in Android is about 30-40% less than the WebOS usage range.
Moving the clock speed to over 1.5 might raise the temperature a bit, but even in WebOS people didn't see that much of a usage change (but that could be because there's nothing really to run on WebOS).

There is another thing to consider, all chips are not born equal, every fabricator of chips does what they call binning and I'll quote an article that can describe it better than I can
from - http://www.edn.com/blog/Between_The_Lines/35926-Karma_for_MPUs_is_chip_binning_burning_up_.php
"Chip binning has always been fascinating to me on many levels. What is it? It’s essentially a practice in which chip manufacturers design a chip to hit a targeted speed grade, say for example 2GHz, but after the chips are manufactured and tested, manufactures find some of the chips perform at the targeted speed grade of 2GHz, some perform at higher than 2GHz, and even more perform at lower speeds than that targeted specification number (some of those lower performing chips may perform at 1.8 GHz, others at 1.5 GHz and some at 1 GHz…and lower). But instead of throwing out the chips that didn’t hit the targeted performance specification, some semiconductor vendors, especially microprocessor vendors, sell most of them to us, the consumer. They simply put them in bins according to speed grade and price them accordingly."
Click to expand...
Click to collapse
So the 1.5GHz units may very well be of greater quality than the chips that ended up in our 1.2GHz units and by raising the base to 1.5GHz many people could end up with unstable Touchpads.

Related

Risks for overclocking your G1

There's some apps on the market that can makes phone CPU goes faster and push it to its limit, and mine is called overclock widget.
One quick question here, does this app shorten G1 CPUs life? will it harm the CPU in the long run? If so, how much the damage it could cause??
My G1 is a little bit lag, i consider to use this app, but if it shortens the CPU life, than it's not worth it and im okay with the lag.
You can't OVERclock your G1. You can only clock it to its rated frequency. The processor is rated at 528Mhz, but when it's distributed, it's set to run between 245-384. So it's UNDERclocked when you buy it.
The process is made to run at 528Mhz, so you can safely do it. It will decrease your battery life, but won't hard your processor.
tehseano said:
You can't OVERclock your G1. You can only clock it to its rated frequency. The processor is rated at 528Mhz, but when it's distributed, it's set to run between 245-384. So it's UNDERclocked when you buy it.
The process is made to run at 528Mhz, so you can safely do it. It will decrease your battery life, but won't hard your processor.
Click to expand...
Click to collapse
lol then I feel dumb now that I used "overclock" word without knowing what it means. Haha
Thank's for the confirmation.
So even if I clock it to min = 528, max = 528, it will not harm the CPU at all?
Will it makes the CPU Hot for always clocking the rate to the max??
Yes, it will increase in temperature.
Typically, you don't want to run it at its maximum speed continually. Just for short bursts as needed. That's what automatic clock scaling is for.
riki28 said:
lol then I feel dumb now that I used "overclock" word without knowing what it means. Haha
Thank's for the confirmation.
So even if I clock it to min = 528, max = 528, it will not harm the CPU at all?
Will it makes the CPU Hot for always clocking the rate to the max??
Click to expand...
Click to collapse
lbcoder said:
Yes, it will increase in temperature.
Typically, you don't want to run it at its maximum speed continually. Just for short bursts as needed. That's what automatic clock scaling is for.
Click to expand...
Click to collapse
I see, Okaay, I will use it when I need it then, if 128-384 mb is the default rate by HTC, then I think it's the best freq rate for the phone...
Thanks for the info guys =)
For the record, you are "overclocking" it. It's clocked at a specific speed in stock format and you're OC'ing it from that.
TheSamurai said:
For the record, you are "overclocking" it. It's clocked at a specific speed in stock format and you're OC'ing it from that.
Click to expand...
Click to collapse
Wrong...
As quoted from http://en.wikipedia.org/wiki/Overclock - "Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer." Maybe as specified by HTC, but on actual terms, no, it's not overclocked.
r3s-rt said:
Wrong...
As quoted from wiki/Overclock - "Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer." Maybe as specified by HTC, but on actual terms, no, it's not overclocked.
Click to expand...
Click to collapse
lol @ proving yourself wrong.
I preordered my G1 and rooted it as soon as possible, fully charge it atleast once a day and keep my overclock widget set to 528 min - 528 max.. My phone holds good charge and works fine more than a year later
r3s-rt said:
Wrong...
As quoted from http://en.wikipedia.org/wiki/Overclock - "Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer." Maybe as specified by HTC, but on actual terms, no, it's not overclocked.
Click to expand...
Click to collapse
Quite a FAIL
Aznneedlovetoo said:
Quite a FAIL
Click to expand...
Click to collapse
HTC made the phone, but not all of the components. Qualcomm made the MSM7200A processor, and they set the recomended frequency at 528 Mhz. Anything lower then 528 should therefore be considered an underclock, and anyhting over should be considered an overclock.
OT, overclock is completely safe until a point. A company will test its products way harder then what consumer use for it would be. For example, if you were building a house in which the roof weighted a ton, you would use wooden walls that was designed for a ton. But, say that the roof is a little more then a ton, 1.001 tons, would the walls break? No, they would not. Qualcomm probably tested the processor much higher then the recomended values and set the maximum low enough so that they would not have issues about consumers with bricked hardware. My phone runs perfectly stable at 652 Mhz, but I cannot comment on battery life as my phone has always sucked way too much more then normal, even when I was still on stock. Setting it to say 160000 max and 528 min would be perfect for your phone without any risks.
http://pdadb.net/index.php?m=cpu&id=a7200a&c=qualcomm_msm7200a
For the most part, unless you are planning on using your phone for a decade or so, you should not worry too much about the effects of increasing your processor clock speed.
You will notice an increase in temperature, in fact it is actually quite significant and a bit scary. If I recall though, seeing performance charts, increasing the clock speed on the Qualcomm processor does increase performance, but really not by a significant or (correct me if I am wrong) discernible amount.
I know this contradicts a bit with what I said earlier, but its more of just my own theory and that is I believe the heat from the processor probably would be fine for the processor itself, but I don't know about the other components. The temperature actually does get so hot to the point where it would be uncomfortable to have the phone on your lap. I have a hybrid silicone/plastic case on my phone and it expands by ALOT when the processor is clocked to 528Mhz from the heat.
So what's the best solution?
I just bought an HTC Dream on Ebay. As soon as I get it I plan to unlock and flash CM6. Will it come with overclocking software? If so, what's the best way to get the performance when it's needed and otherwise let it underclock?
onecallednick said:
I just bought an HTC Dream on Ebay. As soon as I get it I plan to unlock and flash CM6. Will it come with overclocking software? If so, what's the best way to get the performance when it's needed and otherwise let it underclock?
Click to expand...
Click to collapse
you best bet is to use setcpu 2.0.2 and it wont come with it
I would just like to put a little clarification note in here about the definition of overclocking....
Fact is that the rated maximum clock speed is/may_be based on certain IDEAL conditions and that a particular APPLICATION of that component may have a lower rating as a result of its characteristics. Specifically, knowing that speed makes HEAT, one could rate a CPU at LOWER than its manufacturer's spec in order to keep it within the heat envelope.
I am not saying that that is what is happening in this case, but it could, along with battery life, be part of the equation that led to them setting the clock below the chip's maximum rated speed.
So from this perspective, bringing the clocks up to 528 COULD IN FACT be considered OVERCLOCKING.
Further perspective, the processor if considered as a stand alone device is rated at 528MHz, so those terms the processor is underclocked when running at a lower frequency
However if you look at the processor as a component part of a larger assembly, then the manufacturers defined speed is set by other concerns than merely that of the processor's designed rating, and in this context running it at higher speeds than the device's rated speeds would be considered overclocking.
It all depends on perspective, from Qualcomm's perspective, HTC underclock the processor, from HTC's perspective, we overclock if we raise the clock frequency above that which they rate the assembly at.
And as we are talking of a multilayer PCB with components on both sides, what is the heat rating of the components on the opposite side of the PCB to the processor? I don't know, but I bet HTC does, and that may be a factor to consider, the processor may not fail, but what of the surrounding components?
And for the record, I use setcpu, and have it scaled for 160-528, it does heat up under heavy use, but not so much that I worry unduly, as has been said, HTC probably do take the heat envelope into account, as most manufacturers do, and most take the safe approach, and prefer to stay away from the edges of the envelope.
So unless you plan to peg your cpu clock at 528 or nothing, it should be safe enough, and will not reduce the life of the device significantly.

Droid Gone Wonky After 1.1ghz overclock

I just overclocked my droid using the tazkern 1.1 Besides being miserably slower than before when I boot up, It doesn't even give me the option to go up to 1.1 ghz. Any suggestions?
suggestion:
and don't take this wrongly in any way..
Stop overclocking so much!! It's a damn phone, not a gaming rig. That and also you really risk of damaging of your CPU and other internals...
My Milestone is running stock. It stays cool and is fast enough. This is after i tried some weeks running it on 800 Mhz. It gets too hot and that also during conversations.
I get where you're coming from but still, I was just getting a lil tired of the the thing lagging every time i opened the app drawer or market. I actually fiddled with it a little after I posted that and got it to run perfectly. And I think Im fixing to try out a 1.2ghz kernel just to see what happens. So far there's been no overheating or crashing.
ECC is kicking in and making your phone slower. Use a lower clock, your phone doesn't support it.
Actually its running quite smoothly so far. Ive been running it for around 30 mins now and its super fats, smooth, and appears stable. Ive tested it on youtube tho and its getting pretty warm.
Mines runs all day, every day at 1.2ghz. The quirks are not from the overclock. Thbey were always there.
Thats what Im on now. I think Im using the slayher 1.2ghz kernel.
Droid or Milestone?
If Droid, you're in the wrong forum. This is the Milestone one.
I have mine at 720mhz overclocked and it works fine,i dont have any heat problems,i always check the battery tempeture via SETCPU app,always is at 30C to 32C,not more than 32C!!!
I love it more tha my iphone
I think people need to learn the risks of overclocking.
You may say its stable and running fine and "just a little warm" but you are infact destroying your CPU.
If you touched your computer case and "it was a little warm" you would be worried.
Consistently hot systems aren't expected to last anywhere near as long a cooler systems. Thermal fatigue in silicon results in cracks in transistors, and transistor mounting failures, in particular. Of course, just one transistor failure on a complex system such as a motherboard or graphics card can result in the entire system failing. And a replacement board being an appropriate fix.
Source: http://ezinearticles.com/?The-Effect-of-Heat-on-CPUs-and-Computer-Systems&id=2310508
For computer CPUs, but you get the idea.
Oh dont worry. I turn my phone by the time it burstsinto flames. And btw i apologize but i did post this in the wrong forum. Oops.
droid doesnt equal milestone. development is different due to locked kernel / bootloader..
but saying that. i use 1.2ghz with 70 vsel, or 1ghz with 60 vsel.
its a little lower voltage, but i assume it saves battery.
might not be stable for you, but i've been running it for 8 days straight now..
i dont use a lower voltage cuz i heard it damages the cpu. i stay within safe tested voltages
Link to german oc voltage testing
milestone users have to rely on a kernel module to overclock.
DannyDroid said:
words
Click to expand...
Click to collapse
overclocking damaging the phone? please.. the omap 3430 has the same CPU as the 3630
3630 is upclocked to 1.2ghz and is in the droid 2. i suggest you checking out T.I.'s website. our cpu is clearly capable of reaching these speeds without damage.
Besides. i've had my milestone ever since it came out. I've been overclocking it since it became an option and my phone has never died.
but saying all that. an inexperienced user playing with voltages can seriously damage their phones if they dont know what they're doing. too high or low of voltage or speed can result in a brick.
EDIT: sry for bringing up the droid/milestone thing again, i didnt read the post above me lol
1xinfusion said:
droid doesnt equal milestone. development is different due to locked kernel / bootloader..
but saying that. i use 1.2ghz with 70 vsel, or 1ghz with 60 vsel.
its a little lower voltage, but i assume it saves battery.
might not be stable for you, but i've been running it for 8 days straight now..
i dont use a lower voltage cuz i heard it damages the cpu. i stay within safe tested voltages
Link to german oc voltage testing
milestone users have to rely on a kernel module to overclock.
overclocking damaging the phone? please.. the omap 3430 has the same CPU as the 3630
3630 is upclocked to 1.2ghz and is in the droid 2. i suggest you checking out T.I.'s website. our cpu is clearly capable of reaching these speeds without damage.
Besides. i've had my milestone ever since it came out. I've been overclocking it since it became an option and my phone has never died.
but saying all that. an inexperienced user playing with voltages can seriously damage their phones if they dont know what they're doing. too high or low of voltage or speed can result in a brick.
EDIT: sry for bringing up the droid/milestone thing again, i didnt read the post above me lol
Click to expand...
Click to collapse
The OMAP 3430 is a 65nm chip while the 3630 is a 45nm chip. Newer smaller manufacturing processes = cooler chips. They are NOT the same chips by far.
Furthermore, you realize that many memory chips are made equally. Then the memory manufacturers go and test out different batches. The ones that clock higher can be stamped as higher clocking or faster timing memory. They may be made the same, but usually the better made batches go to the higher end parts. The same goes when Intel makes CPUs. The crappy CPUs with some problems become Celerons. It might've been a Core 2 Duo or i7 or whatever, but Intel goes and disables cores/cuts off memory if it was not a good batch.
You can't look at models and go "well that CPU can do it, why can't mine."
If people have knowledge of CPU overclocking here where you understand that people look for certain serials/batches of Core i7s for best overclockability. Even though to Intel they all meet i7 930 specifications, there's still separation within the i7 930 crowd. Certain batches are better. Maybe not good enough to be an i7 950, but still better than the worst i7 930.
The other question is: What is stability? How do YOU determine what is stable? apps not crashing? In the overclocking world we run Linpack tests for like 24 hours before calling computers stable. Just because you can boot into Windows or Android or play Angry Birds for 3 hours doesn't mean much. It doesn't mean you don't suffer from bugs from overclocking. It's hard to say unless you do a full stress test on your CPU.
The 3600 OMAP is clearly superior to the 3400 series, but I do think that the latter is more overclockable.
I've had no overheating issues at 900MHz, 56 vsel, don't feel the need for higher frequency.
Will, this is all starting to go over my head. I'll just sit in the corner n twiddle my thumbs.
Just think of the 3600 as a 2010 Intel i7 chip and the 3400 as last year's i7 CPU...same platform and architecture but smaller manufacturing process and (probably) a bit faster at the same clock speeds, with the same features.
applebook said:
Just think of the 3600 as a 2010 Intel i7 chip and the 3400 as last year's i7 CPU...same platform and architecture but smaller manufacturing process and (probably) a bit faster at the same clock speeds, with the same features.
Click to expand...
Click to collapse
I was just trying to get at the same idea
I might have been too exact in my words but this is what i meant
and something fyi is that the OC capability of both chips are "capped" at 1.2ghz ... its just dangerous and unstable after that.
heat wise ? I'm inclined to believe that heavy wifi / 3g usage provides a higher source of heat than our petty oc-ing. Our cpus are clearly capable of this. true you make a good point. smaller architecture = cooler and less power. but the heat is probably out of the question. i use setcpu to display my temp. it never goes past the rated temperature. in fact it always stays at around 35c
when using wifi/3g on the other hand.. no need to say. the fact that these chips have no thermal barrier between them and the fact that the heat is able to be felt on the surface on your phone... in such close proximity to the radio chips, the cpu is not going to be heated by oc but by these other factors.
its safe to say you should lower your 3g / wifi usage to reduce thermal stress on your phone
stability wise... I'm not the one to stress test or w.e for long periods of time, but the link i've attached to my previous post shows a lot of people who have.
maybe you should check that out. I'm just here to relay information.
I have mine overclocked to 800 and it stable and quicker than stock its not all cpu its the amount of free memory you have at any given time
here is another very interesting page. this time regarding the droid
http://www.droidforums.net/forum/droid-hacks/20406-max-temp-while-overclocking-12.html
be aware that a lot of the temperatures are in fahrenheit.
highest temps of these guys average around 40-50 Celsius, way below the rated temp
Actually, mine has been running smooth this past week or so with no abnormal heat or crashes.
Sent from my Droid using Tapatalk

Questions...

I've seen some people that have OC'd their CPU.
I know OC'ing a computer's cpu eventually takes it's toll on the processor, and you get less life out of it. Not to mention the extra heat from oc'in it. Does the same apply to these phones?
Do you get a lot more heat from the cpu?
You can monitor your CPU temperature using free apps and judge for yourself, since every phone may differ in optimal oc/uv settings. However, I personally haven't heard of anyone burning out their phone CPU through an overclocked kernel, since they're generally limited to 'tested' oc ranges.
There is actually a lot of code written into the Galaxy S by Samsung for 1.2 Ghz, but it was taken out due to charging instability. The temp on mine has never gotten too high at 1.2, especially since it doesn't spend a lot of time there unless you are playing 3D intensive games.

will OC to 1.4 hurt my phone ?

so, i am using the Fear Rom and with the OC karnel. i played around the max sittings to 1.4 and tried quadarant. amazing score of 4150. nice... but what will happen if i keep it at 1.4 ?
will it over heat the phone / burn the GPU/CPU when playing games for example ?
i understand the battery life will be shorter. but what other disdvantages ?
ll_l_x_l_ll said:
so, i am using the Fear Rom and with the OC karnel. i played around the max sittings to 1.4 and tried quadarant. amazing score of 4150. nice... but what will happen if i keep it at 1.4 ?
will it over heat the phone / burn the GPU/CPU when playing games for example ?
i understand the battery life will be shorter. but what other disdvantages ?
Click to expand...
Click to collapse
You could dmg ur cpu. But Tegra is known to run 1.8Ghz stable. So with 1.4 you should be good.
Sent from my LG-P990 using XDA App
Oh!! Great 1.8Ghz but only 1.4Ghz is very drain my battery to much.
In the long run, your cpu might get affected but its shouldn't happen so soon.
That said, in my honest opinion, don't need to OC the chip.
The same OCing rules apply from the PC World. The same batch of chips have varying maximum OCing capabilities and thus different stabilities. Although you can stably run a chip at a higher clock, it will definitely shorten its life (Sometimes it could kill it in a year, sometimes beyond what we can measure.). Chip makers purposefully OC chips during tests to simulate the stress effects of using the chip over a long period of time (OCing that makes it seem like the chip is being used for months or years.). Nvidia sticks the Tegra at 1 GHz half because it's cheaper to do so (don't need to ensure higher clock rates which would mean a larger percentage of their chips won't last doing it.) and half because of marketing (At the time, no one has 1.2 GHz like we do now. From what I've seen, Tegra 2 can do 1.2 GHz easy.).
So what it comes down to is how long you plan on keeping the phone and how lucky you are. =)
Imo, in the interest of power savings (P = (V^2)/R), the gains of OCing having an exponentially worse effect on battery life.
imho theres currently no point in oc'ing the Tegra2 in Optimus at all.
Theres no real life benefit, only theoretical benefit when running benchmark apps for show off.
Theres not a single application or game out there today that require more processing power than what the Tegra delivers at 1ghz - and not a single one out there that will run any better or faster by oc'ing because the demand for processing power to run the application or game at its maximum capacity are allready met at 1ghz
Basically there are only negatives in terms of decreased battery and cpu life for nothing but a screenshot of a higher quadrant (or whatever) score
If at some time in the future you should run into a game that would not run smoothly unless the cpu are oc'ed then it would make sence to do so - but for now not.
The games available today either do run perfectly smooth at 1ghz or if they dont, then they dont because of poor programming or other factors and they would still run poorly even if the cpu are oc'ed
Actually there are real life benefits until you find a game which really lags when you run it. Meaning, you should leave it as it is until next year.
It may damage the CPU like what others say but since lower clocks are undervolt it might last as long as a non OC (Stock).
But it will kill the battery faster as you will have to charge more often due to the higher power draws.

[Q] Overclocking my SGS to 1.2GHz

Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Shadow Life said:
Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Click to expand...
Click to collapse
Yes you can, depending on the kernel you use, oc your phone even up to 1.5 ghz.
Flash Glitch, MNICS, Devil or Semaphore Kernel for ICS roms
Do so with care as OCing WILL degrade your processor faster.
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Oc SGS 1.2Ghz
nwsk said:
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Click to expand...
Click to collapse
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Shadow Life said:
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Click to expand...
Click to collapse
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
upichie said:
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
Click to expand...
Click to collapse
+1

Categories

Resources