Is there a thread on over clocking the prophet ? tools? safely?
Battery Status! Nice tool and very stable!
http://forum.xda-developers.com/showthread.php?t=270751
BS rulez
I've set the CPU up to 273 mhz with BatteryStatus.
Absolutely stable.
Also the integrated tools in BS are verry comfortable.
Give it a try.
Greetings from Germany,
skylow
Sweet
Thanks Skylow
Ive over clocked it to 273mhz and wow is it fast& stable like you said ....thanks for the tip and greetz from Sweden
Hi !
I have also this speed for my S200, stable fast etc. no crash + I have dynamic overclocking "cpuscaler" settings.
min.:134 org.:195 max.:273
What do you think ? The oc is negative for battery uptime ?
Greatings from Hungary !
about 2 months ago, someone (I think it was Gullum) has noted that using cpuscaler has a negative effect on battery life as it prevents the device from going to sleep. I haven't used it ever since but also I haven't verified the effect. I always overclock my device to 273 and tap on the battery status today plug-in to set the speed back to 195 when oc is not needed (again, just as gullum suggested)
I have dynamic 123-175-208. Great for battery life for me.
amazing, after i overclock it to 273mhz im able to see the streaming video with no lags (live tv channels over wifi) !!!
im verry happy, watchin tvchannels on my prophet =)
I've heard that it has a bad effect on CPU and may cause CPU breakdown.
Is there anyone to verify that?
Bluetooth and overclocking
Hi!
Recently I discovered that if I overclock my devices (Prophet and Touch) I have a strange behavior using the bluetooth freehand environment integrated in my car. The WM Device connects and after a short time it disconnects suddenly. If I receive a call it takes a few seconds and it reconnects again - but you miss a few seconds of the phonecall!
With no overclocking everything works normal - bluetooth connect and disconnect if you leave the car.
(Btw my car is an Audi.)
Maybe somebody has the same problem.
Regards!
HAHA
skylow said:
I've set the CPU up to 273 mhz with BatteryStatus.
Absolutely stable.
Also the integrated tools in BS are verry comfortable.
Give it a try.
Greetings from Germany,
skylow
Click to expand...
Click to collapse
i use always at 286mh and till now i haven't problems with.
guys,do you use application based overclocking???
Baterystatus
tonydeli7 said:
guys,do you use application based overclocking???
Click to expand...
Click to collapse
Baterystatus for me
maxniper said:
Baterystatus for me
Click to expand...
Click to collapse
i know,i use it too but do you use the application based overclocking feature for phone&camera?? today i noticed some missed calls that showed up 3hrs later... I was using 2.20.21 Radio rom and CPU at 260MHz.Now i flashed 2.19.21 and CPU at 273MHz...and no problems so far..
Is that safe push it that way??
270 is not too much???
how about temps??
thks
CPU clock
I have a Jamin G4 and here is the overclocks that I tested:
I use Batt Status and Set CPUscaler.
Range from 99 to 286MHz is stable for Prophet (in my case)
- more than 286MHz which is 299 or higher PDA freezes.
- under 100MHz, 99MHz the screen has a light flick.
- I believe lower clock will save battery and higher clock may shorten CPU life.
- use Cpuscale to vary the cpu clock, especially when idle, it drops to lowest, hence save more battery and as active the cpu will step up to the max limit where you set your max
- Don't overclock unless you have to.
- My reference: CPUScaler from 99 to 260Mhz for normal use. And set to 286MHz unless you need to like games.
Eg: I have tested 286MHz and played Skyforce Reload for a few hours... beautifully... no problem
vnt said:
I have a Jamin G4 and here is the overclocks that I tested:
I use Batt Status and Set CPUscaler.
Range from 99 to 286MHz is stable for Prophet (in my case)
- more than 286MHz which is 299 or higher PDA freezes.
- under 100MHz, 99MHz the screen has a light flick.
- I believe lower clock will save battery and higher clock may shorten CPU life.
- use Cpuscale to vary the cpu clock, especially when idle, it drops to lowest, hence save more battery and as active the cpu will step up to the max limit where you set your max
- Don't overclock unless you have to.
- My reference: CPUScaler from 99 to 260Mhz for normal use. And set to 286MHz unless you need to like games.
Eg: I have tested 286MHz and played Skyforce Reload for a few hours... beautifully... no problem
Click to expand...
Click to collapse
Don't you have any problems with camera at this speed? Mine already at 221-247MHz has pure picture quality at highest resolution - some colors disapearing...
ZRimaZ said:
Don't you have any problems with camera at this speed? Mine already at 221-247MHz has pure picture quality at highest resolution - some colors disapearing...
Click to expand...
Click to collapse
The same happens on my NEO when I go beyond 221 MHz. My camera shows weired colors.
had a strange issue with batterystatus today... i tapped on 'minimize' and it appeared to minimize to the system tray... but i cannot get it to come back. tapping on the phone icon in the system tray shows a maximize option,,... but it does not bring the today screen plugin back... :/
anybody see this issue?
I was wondering what some SetCPU profile suggestions are for the Atrix? Right now all I have is a screen off profile. It has like 608 max and 216 min.
Ideally I would want to set the min a little lower, but it doesn't seem that I can?? It's also kind of annoying that each value can only be set to certain increments, like it jumps from 608 to 450 something or 760 something the other way.
Any thoughts on some other profiles I would maybe want to set?
thebeardedchild said:
I was wondering what some SetCPU profile suggestions are for the Atrix? Right now all I have is a screen off profile. It has like 608 max and 216 min.
Ideally I would want to set the min a little lower, but it doesn't seem that I can?? It's also kind of annoying that each value can only be set to certain increments, like it jumps from 608 to 450 something or 760 something the other way.
Any thoughts on some other profiles I would maybe want to set?
Click to expand...
Click to collapse
screen on 1000/216
screen off 216/216
stevendeb25 said:
screen on 1000/216
screen off 216/216
Click to expand...
Click to collapse
That screen off max seems sorta low. You haven't experienced any wake up lag or anything while using that?
out of all honesty i used setCPU for a while and didnt notice any difference other than wake lag on my LWP. The phone is already excellent at managing the processor loads on its own. To me it was Just another app using up my battery. I will def use it once OCing is possible. It didnt really seem to have any benefits IMO. I have great battery life without it and thats with chainfire, sdspeed increase, Titanium, and a few others running unrestricted by my task manager. Once again just my opinion.
thebeardedchild said:
That screen off max seems sorta low. You haven't experienced any wake up lag or anything while using that?
Click to expand...
Click to collapse
nope no lag here
I see, I could probably get away with setting it even lower.
Dirtburgler, yeah that's mostly why I've only set one profile so far because I haven't really noticed a super high need for anything else lol. I did notice that, in spare parts, my runtime greatly exceeded screen on time on average, so I wanted to make sure to limit the CPU while it was off and it actually has worked very well. I'm only about 1-3% higher with runtime now, even with heavy usage!
If been trying for a few weeks now various SetCPU clock speeds combined with UrukDroid but I have yet to see any sort of meaning full battery improvements, and what I mean by meaning full is 1+ hour.
Can anybody confirm that under clocking is just more of a gimmick idea then any real world use?
Servaas said:
If been trying for a few weeks now various SetCPU clock speeds combined with UrukDroid but I have yet to see any sort of meaning full battery improvements, and what I mean by meaning full is 1+ hour.
Can anybody confirm that under clocking is just more of a gimmick idea then any real world use?
Click to expand...
Click to collapse
Have to say it was the same for me, at that point i just went for full power and had it blasting at 1GHz permanently
It is more a problem of missunderstanding.
If you say you are using 1GHz, in 99% of the times this is only the maximum that will be used if demand is there.
Normally you have one of the lower speeds running most of the time ( see statistics in Info of SetCpu ).
And even if you completely run on 1.2GHz with the display on, the processor is not the one draining the batterie.
Has it ever been heard of that someone killed their gs2 from using 1600mhz in daily use?
My gs2 likes to have 1475 as a minimum voltage for 1600.
sent from I9100 using Omega
Ever rev an engine into the red? Did the engine blow up on the spot? unlikely. However if you constantly KEEP the engine in the red it will eventually break down.
Same thing for OC phones. The processor in the SGS was designed for somewhere around the 1ghz mark. Pushing it 110% likely wont kill it, they build allowances and tolerances into these things to help them last longer. Push that processor to 150% and you are risking serious damage.
Monitor the heat, if you notice its getting HOT then you should really pull the battery and let it sit for a while. Nobody here can say its safe to OC your phone like that, its a calculated risk you obviously didnt spend a lot of thought into.
TLDR: Just because you CAN doesn't mean you SHOULD.
Actually its my thought the reason I haven't been using it on 1.6 yet, and why I'm asking. Iv been ocing my pcs since the late 90s
Now the reason I'm asking here is because the cortex a9 was designed for up to 2gHz operation, but this phones design may or may not provide adequate cooling, that's why I'm asking if other people have any negative experiences with this.
Were not actually over reving the chip its more of a environment issue with cooling/ventilation.
sent from I9100 using Omega
Visentinel said:
Actually its my thought the reason I haven't been using it on 1.6 yet, and why I'm asking. Iv been ocing my pcs since the late 90s
Now the reason I'm asking here is because the cortex a9 was designed for up to 2gHz operation, but this phones design may or may not provide adequate cooling, that's why I'm asking if other people have any negative experiences with this.
Were not actually over reving the chip its more of a environment issue with cooling/ventilation.
sent from I9100 using Omega
Click to expand...
Click to collapse
You do have to have in mind that PCs are much safer to OC, so we shouldn't really compare brtween them.
Regarding the Phone OC, I haven't OC'd mine and probably never will because I have all the horsepower I need, but I think the "safest" OC is between 1.3 and 1.4GHz, since that's a range that all CPUs are designed to overtake (max 200MHz range ).
mine's been oc'ed, uv'ed pretty much within the week I bought the phone in june.
I've got it set to clock between 500-1600Mhz on demand and I've not had a problem yet. Mind you, not many tasks you do on the phone will actually require 1600Mhz and my phone's CPU clocks mostly between 500-800Mhz.
Playing some games or doing quick video conversion will push to 1600Mhz but I rarely play games on my phone and video conversion is short process - burst of 90 seconds to 120 seconds at most. So I think you should be alright so long as you don't leave your phone CPU at 1600Mhz at all times.
Like you said, it is the cooling and ventilation system on the phone, which you can't modify.. Unlike PCs, where you can install bigger fans or water cooling systems. So if the phone isn't constantly cooking itself inside, should be alright.
You should already know that OCing anything is dangerous since you overclock PCs,so I'll skip that part.
Well,if it's dangerous for the phone...It depends.Yes,the processor will die sooner.Yes,you risk frying your device.No,you don't have to push it to the limit(don't push it more that 1450μV,that's the general advice for 45nm chips).However,my thoughts are:
-I won't still have the device when it's time for its CPU to get fried,so I don't actually care.
-Something else,probably the Amoled screen,will make the phone useless by breaking sooner than the CPU will.
-This winter here is really cold(for our standards anyway),so heating has been taken care of.During hotter weather,I kept multiple temperature profiles in SetCPU,so that frequencies get lower as temperatures get higher.
In the end,what matters most to me is to have the experience I want.And with OCing my phone I get it.I'm happy with it,that's all I wanted.So,it's personal preference.Some feel they don't need it,others feel they do.Decide for yourself,that's the best advice.
PS:In case you are using Siyah kernel or CF-Root with Tegrak overclock,try lowering your clock by small steps(8Mhz is the smallest step) for a sane voltage,say 1400μV.Sometimes small increments make big differences.
Thanks for the advice guys. Appreciated.
sent from I9100 using Omega
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Buffalee said:
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Click to expand...
Click to collapse
how can you tell, that its dead because of the use and charging, if you didn't even OC'ed?
Buffalee said:
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Click to expand...
Click to collapse
I bet you didn't know there are faulty products out there that show their faults during intensive usage,eh?Mine's running at 1.6GHz(give or take a few MHz ) for months.I've played games while charging countless times.And my phone is still here,intact,so that I can write this here.
Sent from my GT-I9100 using xda premium
Of course my sgs mobo could have been faulty.
When the mobo fried it was hot, i mean hot.
I didn´t look temperatures.
It didn´t wake up even using jig.
I sended it to service.
If they had succesfully woke it up, they wouldn´t fix it on warranty (rooted).
Normally oc would be fine because it´s using powersave and underclock it.
But if you play like 2 hours on 1,6Ghz it can get too hot (over 60c on cpu).
I can´t recommend that kind of temperature.
And nobody here knows what kind of vrm´s phone has.
Also cooling plates are not designed for massive oc/voltage.
Of course temperature depends on voltage more than the clock speeds.
It´s up to user if he want to use it that kind of voltages/speeds.
I would´t use it 1600Mhz/24/7.
Generally i know what i´m talking about (using water on pc...)
Just look for temperatures and don´t give too much voltage (as low as possible).
Of course you don´t know safe voltage limits, but try and look what other have been using.
Don´t oc much if you don´t know what are you doing.
@tolis626 Hi, I have oc'd to 1.4ghz for the last few weeks, and I have under volted it to 12.75mV, the same as you, have you had any problems at that voltage? Also, is your 1200mhz voltage stable as it seems very low, to say that it was, at stock, 13mV. Furthermore, have you ever tried to under volt 1600mhz please?
Buffalee said:
Of course my sgs mobo could have been faulty.
When the mobo fried it was hot, i mean hot.
I didn´t look temperatures.
It didn´t wake up even using jig.
I sended it to service.
If they had succesfully woke it up, they wouldn´t fix it on warranty (rooted).
Normally oc would be fine because it´s using powersave and underclock it.
But if you play like 2 hours on 1,6Ghz it can get too hot (over 60c on cpu).
I can´t recommend that kind of temperature.
And nobody here knows what kind of vrm´s phone has.
Also cooling plates are not designed for massive oc/voltage.
Of course temperature depends on voltage more than the clock speeds.
It´s up to user if he want to use it that kind of voltages/speeds.
I would´t use it 1600Mhz/24/7.
Generally i know what i´m talking about (using water on pc...)
Just look for temperatures and don´t give too much voltage (as low as possible).
Of course you don´t know safe voltage limits, but try and look what other have been using.
Don´t oc much if you don´t know what are you doing.
Click to expand...
Click to collapse
I know what I'm doing.I know the risks,that's why I don't encourage anyone to overclock as much as I do.I carefully monitor temperatures and voltages over long time periods.Rest assured,I won't come back here crying.
danielsf said:
@tolis626 Hi, I have oc'd to 1.4ghz for the last few weeks, and I have under volted it to 12.75mV, the same as you, have you had any problems at that voltage? Also, is your 1200mhz voltage stable as it seems very low, to say that it was, at stock, 13mV. Furthermore, have you ever tried to under volt 1600mhz please?
Click to expand...
Click to collapse
Well,since 1400MHz and 1600MHz aren't stock clocks,you don't actually undervolt them.You rather choose a voltage for them as there isn't a standard one.
My phone is stable with the voltages in my sig(I've only changed 200Mhz and 500MHz voltages a little but too bored to update my sig ) for months,so yeah,I'd say I don't have any problems.This doesn't mean that no one will.Your phone might need 1325μV or 1225μV for 1400MHz.Every phone's CPU is unique in its own way.
@tolis626 Thanks very much, one more stupid question please, will under volting from stock Samsung voltages, even if it's stable, decrease performance compared to stock voltages on an average exynos processor please, aslo will undervolting from original kernel clock speed increase the processors life span? I have researching this and came up with nothing.
Will it break your phone? Not directly. It will shorten the lifetime.
Besides that the heat can indirectly kill your device.
I'm just curious:
Why overclocking the device? I have mine underclocked to 1 GHz max. It still has enough power to handle everything.
Sent from my GT-I9100 using XDA App
I have just been messing around. I can get 1.6ghz perfectly stable at 1350mv, I tried 1325mv and it hung up after about 2 min of use. I can also get my 1.4ghz down to 1225mv's and 1.2ghz to 1.200 it is rock stable and I haven't tried lower voltages on 1.4 & 1.2.
I am going to keep [email protected] & 1.4 @ 1250mv & [email protected]
danielsf said:
@tolis626 Thanks very much, one more stupid question please, will under volting from stock Samsung voltages, even if it's stable, decrease performance compared to stock voltages on an average exynos processor please, aslo will undervolting from original kernel clock speed increase the processors life span? I have researching this and came up with nothing.
Click to expand...
Click to collapse
No,undervolting will in fact prolong your processor's lifetime,albeit negligibly,because with less voltage less heat is generated.It's plain physics.
Overclocking on the other hand will reduce your CPU's lifetime.The damage(mostly electromigration) is dependent on the CPU and how much you overclock.Quite frankly again,you won't still have the phone when enough damage is done for it to break.If the slightly lower battery life doesn't bother you that much,I say go for it.
danielsf said:
I have just been messing around. I can get 1.6ghz perfectly stable at 1350mv, I tried 1325mv and it hung up after about 2 min of use. I can also get my 1.4ghz down to 1225mv's and 1.2ghz to 1.200 it is rock stable and I haven't tried lower voltages on 1.4 & 1.2.
I am going to keep [email protected] & 1.4 @ 1250mv & [email protected]
Click to expand...
Click to collapse
Dude,that's some nice UV!Mine instantly crashes when I set it to 1375μV at 1600MHz.You're lucky.
Oh and,most probably your phone can handle 1200MHz at 1150μV.
Sent from my GT-I9100 using xda premium
tolis626 said:
No,undervolting will in fact prolong your processor's lifetime,albeit negligibly,because with less voltage less heat is generated.It's plain physics.
Overclocking on the other hand will reduce your CPU's lifetime.The damage(mostly electromigration) is dependent on the CPU and how much you overclock.Quite frankly again,you won't still have the phone when enough damage is done for it to break.If the slightly lower battery life doesn't bother you that much,I say go for it.
Dude,that's some nice UV!Mine instantly crashes when I set it to 1375μV at 1600MHz.You're lucky.
Oh and,most probably your phone can handle 1200MHz at 1150μV.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you very much for all your help I tried undervolting 1200mhz more, I got to 1075mv and it was rock stable, I don't think I am going to try anything lower than that. Just for info, I'm on SiyahKernel v2.6.2 Thanks again
CPUs care a lot about voltage and don't give a rip about MHz except for the minor heat increase. The chip in my phone is a bad clocker though. If I could get 1400mhz to work at close to the stock 1200mhz voltage I would do it in a heartbeat. Sadly mine requires a healthy bump so I abstain. At least until I can afford to replace it
Number one rule of overclocking, don't push the voltage if you can't afford to replace it
I discussed the topic of overclocking processors with a friend of mine who design cellphone CPUs. He told me that over the lifetime of a CPU, the insulating oxide layers break down. This process is considerably faster at 40% extra power and frequency. So don't expect it to last as long as a normally clocked CPU. So the question is how long it would normally last.
Hi, I've got an annoying problem...
As far as i know the first thermal threshold for kicking down the CPU freq to 800MHz is set to somewhere around 80oC in SGS3. But in my case it kicks in after achieving just 51-54oC which makes some games unplayable after 5 mins
I've read somewhere that the battery temperature (45oC or so) is also considered when throttling down the CPU frequency, but my battery hits just 41oC when it happens...
Could it be a faulty temperature sensor(s) or just faulty almost 2 years old battery? I have no more clues, could anybody help?
Thanks a lot!
flither said:
Hi, I've got an annoying problem...
As far as i know the first thermal threshold for kicking down the CPU freq to 800MHz is set to somewhere around 80oC in SGS3. But in my case it kicks in after achieving just 51-54oC which makes some games unplayable after 5 mins
I've read somewhere that the battery temperature (45oC or so) is also considered when throttling down the CPU frequency, but my battery hits just 41oC when it happens...
Could it be a faulty temperature sensor(s) or just faulty almost 2 years old battery? I have no more clues, could anybody help?
Thanks a lot!
Click to expand...
Click to collapse
That's tricky... Afaik you CAN change some system files to avoid throttling but I don't believe that that would be healthy... Your temperature sensors could also be faulty... I don't know
Sent from my toaster
yeah, but is it possible that it's throttling down on such normal temperatures? Or maybe there's another safety mechanism involved (dunno, maybe GPU temp sensor)? But my GPU runs on stock freqs and voltage...also it doesn,t matter if i'm undervolted on CPU or not, still the same
flither said:
yeah, but is it possible that it's throttling down on such normal temperatures? Or maybe there's another safety mechanism involved (dunno, maybe GPU temp sensor)? But my GPU runs on stock freqs and voltage...also it doesn,t matter if i'm undervolted on CPU or not, still the same
Click to expand...
Click to collapse
I don't actually know... I've never faced throttling problems so i don't know what else can cause this.. Perhaps there is something else involved...
Sent from my toaster
SOLVED
After a really deep search I found out that Sammy based roms have a CPU throttle after battery reaches 41oC...now to change it