Develop Bugs

Is this dangerous...

Just installed netarchy 4.1.9 over BS 1.8, and it could be under clocked o 125Mhz. Is it safe to have the Processor work at that speed when screen is off and the min value in setCPU.
Don't want to mess the love of my life.

Thread moved to Q&A.

first this is definatly the wrong forum for this. it should be in the Q&A area.
Development is a forum where developers can post there works and isnt intended for people to ask general questions. If you have a question on something someone developed and posted in the development forum it should be in that "projects" thread.
second. If you use the search you can find a TON of information on SetCPU profiles and what is ok and not and normally it is expected that you search some yourself before posting not only to help keep the forum clean but also its hard to expect others to keep answering the same questions for people who cant even be bothered to try and help themselves first. (think of XDA as a library of information)
Now to answer your questin.
yes it is safe, i will say however that the performance is very poor and most do nto like having it clocked that low because of this. most stick to 256 or above while the screen is off so that start up doesnt lag as baddly.

You can try, my phone doesn't like to be clocked that low and reboots, mine also doesn't like 1.267 and reboots. I usually don't overclock and I only underclock to 245.

My phone also dislikes being clocked that low and will lag considerably bad when trying to wake up, sometimes only recovering after changing the clock up to 256 and rebooting. Also I clock at 1.19 as my phone reboots itself above 1.2. Seems to be a common pattern if you look around I would follow that.

I remember reading somewhere that the voltage for 128 and 256 is the same, so there is really no point in clocking it that low. Basically, it takes the same battery to run at 128 as 256, and 128 seems to cause problems anyways.

128MHz is fine on my phone with the screen off, with absolutely no lag turning it on.

2.0 Ghz kernel

Hai Guise!
Back a little while ago the G2/Vision thread (before Desire Z was merged) had a thread about overclocking made by a user named Flippy. I followed it for a while because it was getting insanely out of control and awesome. I had used 1.9Ghz as my max oc for a while and It was great. Now I'm on 1.8Ghz again because the 1.9Ghz kernel was removed later on and replaced with the 1.8Ghz update zip. (For some reason doesn't work for me so I had to fastboot it)
So the reason I made this thread is because I would like to have the 2.0Ghz kernel. I know it's possible and has been done already. I've looked into compiling my own but apparently I need linux to compile it and I'm not fond of installing VM's on my old computer that will barely run as it is.
Now I ask of you, if anyone who is kind enough to possibly please compile a 2.0Ghz zimage for me, I would be greatly in your debt and appreciate it much so! I understand that it is my fault if I mess up my device and only I am held responsible.
Thank you in advanced to anyone kind enough to offer their services.

dietotherhythm said:
Hai Guise!
Back a little while ago the G2/Vision thread (before Desire Z was merged) had a thread about overclocking made by a user named Flippy. I followed it for a while because it was getting insanely out of control and awesome. I had used 1.9Ghz as my max oc for a while and It was great. Now I'm on 1.8Ghz again because the 1.9Ghz kernel was removed later on and replaced with the 1.8Ghz update zip. (For some reason doesn't work for me so I had to fastboot it)
So the reason I made this thread is because I would like to have the 2.0Ghz kernel. I know it's possible and has been done already. I've looked into compiling my own but apparently I need linux to compile it and I'm not fond of installing VM's on my old computer that will barely run as it is.
Now I ask of you, if anyone who is kind enough to possibly please compile a 2.0Ghz zimage for me, I would be greatly in your debt and appreciate it much so! I understand that it is my fault if I mess up my device and only I am held responsible.
Thank you in advanced to anyone kind enough to offer their services.
Click to expand...
Click to collapse
Why do you need to overclock that high? I've used the 1.8Ghz and found that to.be overkill. I'm running at about 1ghz at that seems ample.
Sent from my CM7 powered Desire Z

cjward23 said:
Why do you need to overclock that high? I've used the 1.8Ghz and found that to.be overkill. I'm running at about 1ghz at that seems ample.
Sent from my CM7 powered Desire Z
Click to expand...
Click to collapse
+1
Wouldn't that fry your phone without any active cooling system or something? Sounds unnecessarily risky..

dietotherhythm said:
Hai Guise!
Back a little while ago the G2/Vision thread (before Desire Z was merged) had a thread about overclocking made by a user named Flippy. I followed it for a while because it was getting insanely out of control and awesome. I had used 1.9Ghz as my max oc for a while and It was great. Now I'm on 1.8Ghz again because the 1.9Ghz kernel was removed later on and replaced with the 1.8Ghz update zip. (For some reason doesn't work for me so I had to fastboot it)
So the reason I made this thread is because I would like to have the 2.0Ghz kernel. I know it's possible and has been done already. I've looked into compiling my own but apparently I need linux to compile it and I'm not fond of installing VM's on my old computer that will barely run as it is.
Now I ask of you, if anyone who is kind enough to possibly please compile a 2.0Ghz zimage for me, I would be greatly in your debt and appreciate it much so! I understand that it is my fault if I mess up my device and only I am held responsible.
Thank you in advanced to anyone kind enough to offer their services.
Click to expand...
Click to collapse
You don't need a VM. You need to wipe the garbage off and install linux on the "bare metal".

While it would be *neat* to oc this phone to 2GHz - just because. It would be beyond useless and I can just see some noob burning down their parents house or possibly starting a nuclear war with Russia by accident. Lets not forget your carrier reporting you to the CIA for having a nuclear reactor in your phone.
Look, with no active cooling it's just downright stupid to go that high. However being the genius' that we are I'm sure somebody could devise a method to install a mini fan or some liquid cooling on this phone. But then you may need that nuclear reactor to power all that stuff. Haven't we already set a guiness world record at 1.8GHz on a production phone anyway? Maybe we need to tell them so we can make it in the book

My phone froze at 2Ghz... I went in for 2.2Ghz at first but it froze after a couple seconds

MacaronyMax said:
My phone froze at 2Ghz... I went in for 2.2Ghz at first but it froze after a couple seconds
Click to expand...
Click to collapse
LOL, it didn't make you go back in time or some ****?

The 1.9Ghz kernel caused my phone to crash. 2.0 would burn your phone's processor out. Just use the 1.8Ghz kernel and have the profiles on SetCPU set to the lowest speeds when the display's off.

Your phone may not actually run stable at 2GHz. Mine doesn't run stable past 1.6GHz, and that runs psx4droid *perfectly*, especially with the optimization they've done in the app recently.
Also, even with setCPU profiles, battery drain when you ARE running that high is a beeeotch.

Honestly, it's not really for OCing that high, but rather the look at what I can do I had a friend just ask be how high I can OC my phone and at 1.5GHz he's like woah :O His face at 2GHz would have been like

I previously used Flippy's kernel on my G2 and did OC it to 1.8 GHz, and got a Quadrant score of 3037. It was cool to see how fast my phone could actually get, but I'm more than comfortable with OC'ing it to 1.4 GHz. Anything more than that seems to be unnecessary to me, but that's just my opinion. Last thing I want is to have my G2 melt while it's in the pocket of my pants.

Try the .ko module and overclock that way
Sent from my HTC Vision using XDA App

mejorguille said:
Try the .ko module and overclock that way
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Oh yeah totally forgot that existed. Thank you for the useful response.

tried the module but the phone freezes after doing anything above 1.4ghz
I believe it needs voltage tweaking which I don't know how to go about sooo... yeah

MacaronyMax said:
My phone froze at 2Ghz... I went in for 2.2Ghz at first but it froze after a couple seconds
Click to expand...
Click to collapse
LOL!! Froze? Or more like "fried"!! Hehe
Doesn't it happen to you guys that when running @1.5Ghz u get many FC from some games? Running excessive OC might stop your phone from working.
Why do you need 2Ghz?!

EdWRX said:
LOL!! Froze? Or more like "fried"!! Hehe
Doesn't it happen to you guys that when running @1.5Ghz u get many FC from some games? Running excessive OC might stop your phone from working.
Why do you need 2Ghz?!
Click to expand...
Click to collapse
Nope, not for me anyway. I know different HW revisions and such have an effect on how high you can oc but my phone doesn't skip a beat at 1.8GHZ. I'm sure I could go to 2GHZ or a bit higher but unless I'm trying to emulate a PS3, I don't see the purpose - aside from maybe setting a record.

KCRic said:
Nope, not for me anyway. I know different HW revisions and such have an effect on how high you can oc but my phone doesn't skip a beat at 1.8GHZ. I'm sure I could go to 2GHZ or a bit higher but unless I'm trying to emulate a PS3, I don't see the purpose - aside from maybe setting a record.
Click to expand...
Click to collapse
Same. I can do 1.8 all day if I keep near a charger. Anything over 1.3 will drain my battery like a monster though.
I keep at 1.2 regularly and only go higher for games.
Sent from my HTC Vision using XDA App

EdWRX said:
LOL!! Froze? Or more like "fried"!! Hehe
Doesn't it happen to you guys that when running @1.5Ghz u get many FC from some games? Running excessive OC might stop your phone from working.
Why do you need 2Ghz?!
Click to expand...
Click to collapse
I can jog 1.8 and 1.9Ghz for a day without even reaching a dangerous temperature.
Can I get some supportive ideas and less herp derp personal opinions?

Highest Ive pushed mine is 1.5ghz. No need to go any further, Im satisfied with the performance. I get a full days battery life and the temperatures never get critical (my setcpu profile is set to underclock at 38.2 degrees Celcius but my G2 hasn't gotten close to that). Im curious at what stage my G2 would score 3000+ in Quadrant.

You might PM flippy and see if he will customize a kernel for you that goes that high. Let him know you will send a certified letter signed in blood and a video of you stating you release him of all liability for what ever town you destroy when your phone goes nuclear.
Seriously though, I'm willing to be he'll make it for kicks if you ask nicely - btw, call guiness so you can make it into the record books. Also, I'm not sure but if you flash a 'blank' kernel couldn't you just echo the speed and voltage in the 00banner file or whichever one it is?

Feelings about undervolting.

How does everyone feel? I've always assumed that it forces better battery life but I've noticed a lot of people do. I've done it till now just because I figured it has to help since every kernel I've used on any phone is under volted. Do you think it helps? Any kind of proof is welcome but so are opinions.
Sent from my Galaxy Nexus using XDA App

I'm on board with a modest under volt, but when you drop the voltages to the point that the phone is no longer 100% stable any minuscule battery savings would be undone by the forced reboot.

GN's cpu uses a power management technology called smartreflex which dynamically changes voltages used by different frequencies. The values that are set with setcpu and similiar apps are only the maximum voltages that smartreflex is allowed to use. The actual voltages may be well below the nominal ones.
Personally I never noticed any significant improvements. It's hard to tell how much but it is definitely not worth going really low. Right now I am using leankernel which is undervolted slightly by default.

codesplice said:
I'm on board with a modest under volt, but when you drop the voltages to the point that the phone is no longer 100% stable any minuscule battery savings would be undone by the forced reboot.
Click to expand...
Click to collapse
This.
Apps may stop working randomly or the phone may have random reboots if you mess with the wrong speed.
Honestly speaking, just go to setting...
1. then data and limit background data of certain unimportant apps
2. developer options > background process limit. Set it to like at most 3.
These ways are much safer and will boost your battery life.

Thanks. Right now I have a decently aggressive but stable UV but I'm gonna up them another 50mv just to be safe and do that. Thanks for the suggestion I didn't know I could do that. I'd hit thanks if I wasn't on a phone...
MilkPudding said:
This.
Apps may stop working randomly or the phone may have random reboots if you mess with the wrong speed.
Honestly speaking, just go to setting...
1. then data and limit background data of certain unimportant apps
2. developer options > background process limit. Set it to like at most 3.
These ways are much safer and will boost your battery life.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using XDA App

How much is safe for overclocking?

I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.

ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
Any overclocking can be unsafe as it can shorten the lifespan of your memory and CPU. But with that said I run mine at 1200 with no issues. Most people don't go higher than 1600 but anything 1400 or lower is not going to burn it up too quick IMO. Everyones hardware will react differently though.
Sent from my Inspire 4G using xda app-developers app

They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G

ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
I run IceColdSandwich and have found 1459MHz to be the best combo of performance and stability on my phone. Every phone handles OCing a little differently, some can reportedly take over 1600 without a flinch and others will lock regularly with even a slight OC. Just experiment with the "set at boot" option turned off until you find something that works reliably on your phone.

Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2

asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2
Click to expand...
Click to collapse
I think OC can affect battery drain only if you use an application which utilizes a full cpu load. But, if you're using this app in normal mode, economy will not be great also. So, when you using your phone for calling or general usage you will not see any problems with battery discharge.
I'm using DHD with Blackout v3.0 and I set 1200Mhz for maximum cpu value. I have no problems, phone is stable. Some time ago I used Leedroid ROM and set also 1200Mhz, but phone was rebooted by itself very often. More than twice a day.
You should try to use OC, as someone said above, without "set on boot" option. I think there is no danger for hardware up to 1600Mhz.

asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Click to expand...
Click to collapse
Not under normal use. There's a school of thought that says even though the increased speed requires more power, it can also finish tasks and go back to sleep faster, so it ends up being a wash. I've overclocked all three smartphones I've owned to date and haven't experienced any significant difference in battery life.

ai6908 said:
They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G
Click to expand...
Click to collapse
They say that as a precautionary measure just as they say flashing a custom ROM can be dangerous. For people who don't know what they're doing. But precaution aside, just like you said you can go up to 1600 MHz safely on this phone. I know every phone behaves differently but on average no one has issues upto that frequency. But above that frequency the phone might be unstable. The CPU will be drawing much more power at high frequencies and will heat up more. The CPU heating up too much and too frequently reduces the life of the CPU. So it's not a myth.
Sent from my Desire HD using xda premium

2ghz.... the phone is old now. Make it bleed.
Sent from my Desire HD

Don't try to Cross above 1600.

Undervolting For Dummies

Ok I would really like to learn how to undervolt my phone the proper way I have read through maybe what feels like 1000 undervolting guides and I either one song understand half of what I reading or I never successfully do it right looking for much very appreciated help here (a guide, some tips, ect)
Sent from my SPH-L900 using Tapatalk 2

Kelsey Jones said:
Ok I would really like to learn how to undervolt my phone the proper way I have read through maybe what feels like 1000 undervolting guides and I either one song understand half of what I reading or I never successfully do it right looking for much very appreciated help here (a guide, some tips, ect)
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
It's actually pretty simple. First off you need a kernel that allows undervolting. Secondly you need an application like an NSTools or STweaks however with STweaks the kernel has to support that application. Once you get in there and it shows your frequencies its going to show your millivolts as in mV. Take for example let's just say that you're 1.6GHz frequency is @1100mV you can take it down to 1075mV. And after make sure its stable if so continue to undervolt and so on and so forth. Now again those aren't real numbers. There just an example for you. Now there is a thing called overvolting which is essentially only used when you have a frequency that is unstable.
Sent from my SPH-L900 using xda app-developers app

XxLostSoulxX said:
It's actually pretty simple. First off you need a kernel that allows undervolting. Secondly you need an application like an NSTools or STweaks however with STweaks the kernel has to support that application. Once you get in there and it shows your frequencies its going to show your millivolts as in mV. Take for example let's just say that you're 1.6GHz frequency is @1100mV you can take it down to 1075mV. And after make sure its stable if so continue to undervolt and so on and so forth. Now again those aren't real numbers. There just an example for you. Now there is a thing called overvolting which is essentially only used when you have a frequency that is unstable.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much I will definitely try this tomorrow at work thanks!
Samsung ??? Note 2 = A ?Best Friend ❤

Some tips:
Don't make any changes to roms, mods, kernels, etc while testing undervolting. You don't want to introduce other variables during this phase.
Go by steps of -25mV to be conservative. Do -50mV if you want to be aggressive in your testing.
You know if you've undervolted too much if you start noticing laggyness, UI studdering, random reboots, and other unexplained problems. This is why you shouldn't make other changes during the evaluation, since you wouldn't know what caused the problem.
You will need more voltage at higher MHz. It's not uncommon to undervolt more at the lower frequencies.
Once you find a safe undervolt settings, it can be a baseline for other kernels/roms. You'll still need to verify it's stable.
Sent from my SPH-L900

coiledwire said:
Some tips:
Don't make any changes to roms, mods, kernels, etc while testing undervolting. You don't want to introduce other variables during this phase.
Go by steps of -25mV to be conservative. Do -50mV if you want to be aggressive in your testing.
You know if you've undervolted too much if you start noticing laggyness, UI studdering, random reboots, and other unexplained problems. This is why you shouldn't make other changes during the evaluation, since you wouldn't know what caused the problem.
You will need more voltage at higher MHz. It's not uncommon to undervolt more at the lower frequencies.
Once you find a safe undervolt settings, it can be a baseline for other kernels/roms. You'll still need to verify it's stable.
Sent from my SPH-L900
Click to expand...
Click to collapse
Thank you for the tips in going to spend my whole day off tomorrow seeing what works with my phone and what doesn't
Samsung Galaxy Note 2 = A ? Best Friend ❤??