So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.
Nerz said:
So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.
Click to expand...
Click to collapse
i have never seen the cpu get hot in my phone. it gets unstable before any heat is detected, but my phone is not very overclockable, i can get 1.3 with much care to the uv settings. i wouldnt worry about heat until the 1.4 mark, even then you are probably fine. the newer qualcom chips have been set to run at 1.9ghz and dont burn up they are on the same size architecture as ours. these arm chips run at such low voltages that heat is not really a big problem. i dont think anyone on the board has killed a hummingbird from overclocking it.
I think your speaking pre-emptively about not burning up.
Just because the chip doesn't instantly melt doesn't mean your not risking electro migration.
Nerz said:
So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.
Click to expand...
Click to collapse
this chip has a built in fail safe and can run as long as it can handle it automatically freezes or reboot your phone above its capable limit. If you want real time monitoring of your cpu clock speed/usage, ram usage and battery temp download Temp+CPU V2 widget from the market pretty good app. enjoy
Related
Any ideas on how to improve 3D performance on the G1? I am talking about changing things in the kernel/firmware to make 3D games run a little smoother. My favorite game on android is raging thunder 2, and it runs fine for the most part until more then one car gets on the screen. At that point it starts to lag alot. I know it was designed for faster hardware but with some mods we can make it better.
My setup:
CM based 2.6.34 kernel with BFS
Cyanogen 5.0.8 test4
No sound
All tasks killed before the game starts.
Overclocked at 691 min/max (Universal overclock, and always plugged in)
Any ideas?
One, stop killing tasks.
I'm curious if there's a way to assign more RAM to 3d. Hence a... reverse RAM hack?
r3s-rt said:
One, stop killing tasks.
I'm curious if there's a way to assign more RAM to 3d. Hence a... reverse RAM hack?
Click to expand...
Click to collapse
I use the running services section under settings to kill tasks. I haven't used a separate app taskiller since my donut days. Now the reverse RAM hack seems like a good idea, but wouldn't general phone performance suffer because of that?
Ah. Smart man on the killing tasks then.
Hmm... Probably? I usually go with about 18 free... never under 10... But that's ME. Maybe giving it 5mb more? That's a ~50% increase of the original 10.7MB reserved for it. The question here is how? I'm sure it can't be too hard.
the funny thing is dude, you dont mean to boost ur GPU as everything is integrated. when it comes to lag u'd usually resort to OCing the processor. i normally stick to RT1. RT2's requirements are 700Mhz and I dont know if i wanna put ma poor G1 through that - i have a hard enough time trying to get speedforge to work propperly
Vylle said:
the funny thing is dude, you dont mean to boost ur GPU as everything is integrated. when it comes to lag u'd usually resort to OCing the processor. i normally stick to RT1. RT2's requirements are 700Mhz and I dont know if i wanna put ma poor G1 through that - i have a hard enough time trying to get speedforge to work propperly
Click to expand...
Click to collapse
How could I have forgotten about overclock?!?! I'm one of the lucky ones my phone will boot at up to 710 Mhz for a good 30 seconds and I'm perfectly stable at around 652 Mhz. RT1 runs a lot smoother but it has a lot worse graphics. RT2 actually runs fairly well most of the time with the sound off when clocked at 528 so I dunno.
Yeah so I played with overclock some and I'm getting amazing results. When playing 3D games I've got my cpu clocked at 710 max/min and I am getting absolutely no slowdowns. My neocore benchmark is at 30.2 fps now, way higher then stock cyanogen's 22.5 ish scores. I haven't played with overclock since the universal overclock first came out and now my phone seems to be a lot more stable at higher frequencies then it was before. It's gonna kill my battery, but I'll just play with the phone plugged in lol. Problem is solved, but I'm still open to any 3D improving suggestions.
EDIT:I still get a few random reboots, specially if the phone has been idle, but performance is amazing.
EDIT2: I'm gonna have to eat my words....710max/min might have been too aggressive. Sometimes it reboots completely, sometimes it just exits out of the game. Until I posted on here I was having amazing results but a slower clock is more reasonable...I'll go with 691 max/min=p
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
Hi guys. I looking forward to ROM with can work at 1.2GHz. I think most of XDA users have modified ROM working at 1.2GHz, so everything fine? It's save to run Galxy Tab at 1.2GHz?
1.2 has been stable for me for well over a month now. I run 1.4 from time to time when I want to play games or just show off. Some tabs report overheating, but use setCPU profiles to alert you if that happens and you wont run into any problems. I have setCPU to warn me at 40 degrees and at 41 it goes down to 800mhz. Just keep your eyes on the temperature to be safe.
Its a popular misconception that the tab runs at overclock frequency ALL THE time. Unless the kernel (which I seriously doubt coz that would be stupid) is programmed to run at maximum clock frequency or you have set it up yourself (with setCPU or voltage control or w/e overclocking utility you use) which is basically an explosion waiting to happen (or at least crash). The tab runs at a RANGE of frequencies it runs at max frequency (1.2 or 1.4) on demand like playing a game or an HD movie or anything stressful.
DarkPal said:
Its a popular misconception that the tab runs at overclock frequency ALL THE time. Unless the kernel (which I seriously doubt coz that would be stupid) is programmed to run at maximum clock frequency or you have set it up yourself (with setCPU or voltage control or w/e overclocking utility you use) which is basically an explosion waiting to happen (or at least crash). The tab runs at a RANGE of frequencies it runs at max frequency (1.2 or 1.4) on demand like playing a game or an HD movie or anything stressful.
Click to expand...
Click to collapse
You want to say, like PC CPU, that Tab ARM Cortex A8 chip working on range of frequencies? It's possible because of battery save, but I think Tab's Cortex A8 is designed to work at 1GHz all the time without any problems.
Winudert said:
You want to say, like PC CPU, that Tab ARM Cortex A8 chip working on range of frequencies? It's possible because of battery save, but I think Tab's Cortex A8 is designed to work at 1GHz all the time without any problems.
Click to expand...
Click to collapse
DarkPal is right.
While you're theoretically correct too, in the sense that the Tab's Hummingbird is designed to be able to work at 1Ghz all the time, by why would you want to do that? It'll kill your battery if you set it to run at 1Ghz all the time, much less at the higher frequencies that these CPU were not rated to run. Not to mention the heat issues.
There's a reason these ARM-based chips scale up and down the frequency scale according to the CPU governors' settings and load demand, and that's why ARM-based chips are known for their battery savings.
galaxy tab 4G Lte runs at 1.2Ghz
http://www.gsmarena.com/samsung_galaxy_tab_4g_lte-3769.php
I've been running mine at 1.4 for about a month now but undervolted too. Perfectly stable. If you are using SetCPU app you'll be able to see how much time your tab spends at each level.
Sent from my GT-P1000 using XDA Premium App
Bit of a noob question but apart from games in what other areas does overclocking help?
I notice the difference with video. Crisper and smoother. It's not a big thing, but why not do it if you can?
purline said:
I notice the difference with video. Crisper and smoother. It's not a big thing, but why not do it if you can?
Click to expand...
Click to collapse
Because it does run your battery faster and hotter, as well as the processor itself...
Force a sprinter to run 5 miles, they can do it, but I bet they tear something along the way...
Oh yeah, thanks to the illustrious Rotohammer that's not a problem...
Ever since I upgraded to Roto's JMI ROM and a few other tweaks [ see my post: http://forum.xda-developers.com/showthread.php?p=12786456*** Galaxy Tab Master Tweak Thread*** ] the battery life on the galaxy tab has been absolutely insane. Even though the phone is overclocked to 1.4 Mhz.
I used to come home at the end of the day (before overclocking) and my battery would be approximately 15 percent, now it's always over 50 percent. I don't know what the black magic is, but it is good...
Sent from my GT-P1000 using XDA Premium App
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.
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