Related
Hi guys!
I haven't yet rooted my Desire(I would have but I was fool enough to install the 2.2 OTA).The main reason for me to root would be the ability to overclock my device.All this time that I have been around here on the Desire and Nexus One forums I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.However,to my great surprise,I noticed on OpenDesire ROM's thread that the Desire can be overclocked @1344MHz(which of course made me think a big HELL YEAH!).Is that number ok for all of us or for some select few?I remember from my Hero days that only some few,lucky guys like myself could overclock up to 768MHz,although there were cases of people,rare,yet not unheard of,that could overclock @844MHz.Is this the case here or are things different with the Snapdragon?
Many many thanks guys!
C'mon guys,no one?
tolis626 said:
I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.
Click to expand...
Click to collapse
I don't think overclocking to 1267MHz happens in rare cases. I had no problems oc-ing to 1267 and it seems that a lot of forum member were able to do this too.
Why don't you downgrade your HBoot to 0.80, root your phone and try it out?
Just make sure your phone does not become too hot if you try 1344MHz.
I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave
foxmeister said:
I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave
Click to expand...
Click to collapse
so this, its really not needed at all. a decent fast rom and 1ghz is more than enought for things to be super speedy. any decent kernal will provide more than enough speed.
overclocking(and lots of other things these days!) reminds me of that bit in jurassic park where they are all sat around the table and geoff goldblum says:
"Yeah, but your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should".
herein lies the lesson, just because you can do it doesnt mean you should do it.
Well,I have my reasons wanting to overclock...First off,I will check if I can see any difference in speed or smoothness.If there isn't,I will just revert the clock back to normal after some benchmarks.
I just am the kind of guy that wants to get the most out of his phone!
I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.
sbdags said:
I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.
Click to expand...
Click to collapse
That's what I'm talkin' about man!
And now that I think of it,it's not that much.I mean,the Hero could overclock @768,which is 45% overclocking.The Desire's 1267 is about 27% and 1344 is about 34,5%.Nothing too much!So why not?
Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.
Kinma said:
Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.
Click to expand...
Click to collapse
Well my man,in this case the MSM7200A is no beast but rather a pooch that barks to no avail!Good pet however!
Joking aside,the Snapdragon is a beast for a mobile phone,but even beasts get beaten.Now,if I can somehow reach or even get close to the performance of the Galaxy S or the Droid X I'll be happy.Software wise I believe that HTC is far superior ,but it's hardware is a little out of date.Let's see what their new devices will do for us!
Btw,does anyone know if the so anticipated HTC Ace will be anything better than what we already have or if it will be the Evo for GSM users?
Thanks!
The desire is plenty fast as it is and I don't see the point of overclocking it. I've had it to 1267 in the past and it made no difference at all for usability. I'm also the type that overclocks all his computers...
Sent from my HTC Desire using Tapatalk
Personal preferences dude...What everyone does with their phone is their own business.I wish I could resist overclocking too!
However,I was watching a thread over at the N1 forums in which a dude named Storm9999(genius dude,not just a random one) stated that an overclock @1,3GHz could fry our phones.Is that so?I mean,I know overclocking reduces the CPU's lifetime,but is it THAT MUCH dangerous?
I think overclocking can kill your phone.. I use to overclock my own o2 orbit and it died after a year..
Friend of mine just burned his old HTC by overclocking it and as a consequence is going to buy a desire.
I had my phone overclocked at 1345Mhz for a moment, just to test it, and it made no real difference to when it was overclocked at around 1.2Ghz, which in turn has very very little difference to stock 1Ghz.
I think the only case where you see some small impact is in games.
I've tested HD recording at 1.345 Ghz and stock speed and there was no difference.
If anything, it's going to kill your battery and shorten its life for sure, going so high. If ever I will OC again I won't go over 1.1 and only if I find some tangible improvements.
As said, this phone is always fast, there is no real need to OC, other than for 'fun'.
The fun is what I want...Well,most probably I will have my phone overclocked at the maximum speed it can get for about a week or two and then go back to 1 or 1,1GHz...
Btw,your signature kicks ass andycted!
I know a lot of chef around here eager to release ROMs with the ability to be overclocked. I for one also like to have a faster phone but there is always this question haunted me.
Do you always use your phone in overclock mode daily?
I use my MIUI'ed Desire at 998MHz (sometimes 1113MHz) but then afraid things might get wrong if I use it overclock too long.
Any expert that can confirm overclock will not harm the phone? I mean small overclock of course like from 998 to 1113. (or perhaps anyone want to explain what is the safe MHz for overclocking for daily use?)
Sorry if it has been asked before. Hope someone can shed some light here.
nyunyu said:
I know a lot of chef around here eager to release ROMs with the ability to be overclocked. I for one also like to have a faster phone but there is always this question haunted me.
Do you always use your phone in overclock mode daily?
I use my MIUI'ed Desire at 998MHz (sometimes 1113MHz) but then afraid things might get wrong if I use it overclock too long.
Any expert that can confirm overclock will not harm the phone? I mean small overclock of course like from 998 to 1113. (or perhaps anyone want to explain what is the safe MHz for overclocking for daily use?)
Sorry if it has been asked before. Hope someone can shed some light here.
Click to expand...
Click to collapse
i really depends on your cpu, all are diffrent, if you can run it at 1113mhz and its fine and stable, no random reboots ect, then its fine to run it like that on a daily basis, for example my cpu runs great up to 1150 but if i overclock it anymore my device becomes unstable and sometimes reboots, obviously this is bad for the cpu.
Well,I am one lucky fuc*er having a Desire that is all good and stable even at up to 1386MHz(only used that with an old version of OpenDesire though,spent some weeks with AuraxTSense @1300MHz too)!
However,overclocking is not harmful for your CPU as long as it doesn't "press" it too much as AndroHero pointed out.What does harm your CPU with time is overvolting in order to overclock.That's why I stopped overclocking too much.Now I use AuraxTSense 8 @1190MHz and am perfectly happy with it.It doesn't even get hotter than usual and battery seems to be unaffected(god bless undervolt! ).
I run my Desire with a 10% overclock (1113Mhz) all day long, and I am running my HD2 with a 20% overclock (1.2Ghz), I don't think twice about it. And tomorrow I will be getting a Desire HD and that's going to get a good thrashing as well!
So, Im sure this was answered somewhere, and I searched all over.
With that said, why cant the Evo be overclocked past the standard 1.19 or 1.2? I know stability is an issue, but there are other ARM processors that can OC almost double. Is the Evo ARM processor just not able to handle anything past that?
Does anyone know?
Thank you for the insite
You cannot compare the processor in teh Evo to other similar processors. Every single processor is different, and overclocking the evo past those speeds could brick it.
Why would you want to overclock that far? The Evo has no ventilation and crappy power management, even with an extended battery. You're taking an already unstable system and pushing it to the edge. Not only will your phone overheat and freeze, but you can permanently damage the hardware.
I know every processor is different and each one has their own limits.
There is always a risk of bricking and damaging the actual hardware, but what im asking is, in theory, and a practical test, can you push the evo processor past the 1.19 that seems to be the limit (im not talking about going huge, but is there a possibility of being able to hit the 1.5Ghz?). Because there are certain frequencies that are not stable, but ones slightly past that could be stable.
Just throwing it out there.
A car traveling at 120 MPH is not as easy to control as a car doing the speed limit.
try it out n see what happens n then report back ur findings for others that have the same question and cannot find an answer anywhere
Product F(RED) said:
A car traveling at 120 MPH is not as easy to control as a car doing the speed limit.
Click to expand...
Click to collapse
good analogy but that doesnt help anything.
{ParanoiA} said:
try it out n see what happens n then report back ur findings for others that have the same question and cannot find an answer anywhere
Click to expand...
Click to collapse
I would, but all the kernels that the Devs have developed have either a limit put on them, or they havent been able to allow it to OC that far
shagav said:
good analogy but that doesnt help anything.
I would, but all the kernels that the Devs have developed have either a limit put on them, or they havent been able to allow it to OC that far
Click to expand...
Click to collapse
I was wondering this too. It would be nice to have the option to push it over 1.19ghz, I'll be the test dummy.
My Evo can handle 1228 fairly well but can tell its not as stable as say 1190. 1190 MHz is no prob...1267 usually crashes after a run or 3 in quadrant. 1113 runs niiiice for me and my 0004 evo
stkiswr said:
My Evo can handle 1228 fairly well but can tell its not as stable as say 1190. 1190 MHz is no prob...1267 usually crashes after a run or 3 in quadrant. 1113 runs niiiice for me and my 0004 evo
Click to expand...
Click to collapse
I can run 1190 just fine. Can a Dev possibly create a kernel that allows us to go past 1.2whatever.
I can't go up to 1.19 stabley
Gimme a couple a days to come up with a new sig that is cool.
if I pass 1190 endless bootloop.... then ya gotta be fast and turn that damn thing down
I can go to 1228 MHz with Tiamat but it will crash and reboot once you do a couple of things.
shagav said:
So, Im sure this was answered somewhere, and I searched all over.
With that said, why cant the Evo be overclocked past the standard 1.19 or 1.2? I know stability is an issue, but there are other ARM processors that can OC almost double. Is the Evo ARM processor just not able to handle anything past that?
Does anyone know?
Thank you for the insite
Click to expand...
Click to collapse
despite the meriad of answers you have gotten, I have been running my Evo on Sprint lovers Rom, and KiNgxKernel-Evo-12-BFS357-2.6.32.25-Flashable.zip for kernal.
I have been overclocked at 1267 since the day the kernal came out. it is singularly the only kernal that has allowed me to do this without ever crashing. OH, and I'm using
SetCPU 1267 on both min and max and scaling set to performance.
shagav said:
I know every processor is different and each one has their own limits.
There is always a risk of bricking and damaging the actual hardware, but what im asking is, in theory, and a practical test, can you push the evo processor past the 1.19 that seems to be the limit (im not talking about going huge, but is there a possibility of being able to hit the 1.5Ghz?). Because there are certain frequencies that are not stable, but ones slightly past that could be stable.
Just throwing it out there.
Click to expand...
Click to collapse
Not going too big? Going from 1.0 ghz to 1.5ghz on a phone is like going from a civic to a v8. Alot of computer cpu's dont even overclock 500 mhz. I think you're expecting a little too much from a phone. If you want more, go buy a dual-core cpu atrix 4g or something. I'm a speed freak myself when it comes to cpu overclocking (mainly on computers) but 1.113 is plenty for a phone. It even runs fine at 600mhz. Dont get me wrong, it would be cool to get it that high, but your phone would hate you lol
Overclocking
Just flashed Netflix-AllianceROM-2.1-HybriD-3D-OTA-Themed-r7.3TCsigned.zip and was wondering if there is a safe compatible overclocking kernel. Anyone have an idea?
kdogg530 said:
Just flashed Netflix-AllianceROM-2.1-HybriD-3D-OTA-Themed-r7.3TCsigned.zip and was wondering if there is a safe compatible overclocking kernel. Anyone have an idea?
Click to expand...
Click to collapse
There are tons of kernals available in the Dev forum. I personally recommend Netarchy's kernals, but you are free to try any of them.
kdogg530 said:
Just flashed Netflix-AllianceROM-2.1-HybriD-3D-OTA-Themed-r7.3TCsigned.zip and was wondering if there is a safe compatible overclocking kernel. Anyone have an idea?
Click to expand...
Click to collapse
Until HTC drops source codes you will lose camera and other things.
How did you overclock the CPU? I have tried the setCPU and it does not work, I have my Phone rooted, installed the crazy UNleashed rom (since uninstalled) and could not get the setCPU to overclock. Even though UNleashed is made to do that, and I have read others getting over clocked. I am running Synergy now, which I do not think it can Overclock the EVO, but I would like to know how you fine folks are accomplishing this. I would love to go 1.1 right now.
AmericanAlien said:
How did you overclock the CPU? I have tried the setCPU and it does not work, I have my Phone rooted, installed the crazy UNleashed rom (since uninstalled) and could not get the setCPU to overclock. Even though UNleashed is made to do that, and I have read others getting over clocked. I am running Synergy now, which I do not think it can Overclock the EVO, but I would like to know how you fine folks are accomplishing this. I would love to go 1.1 right now.
Click to expand...
Click to collapse
If you're using a stock HTC kernel, hit menu inside SetCPU -> Perflock Disabler. Disable Perflock -> Set On Boot. Ta da.
What are your guys' opinions on the performance of these two kernels? From what I've gathered it seems like KToon's kernel is meant for overclocking, but then what would one use task's for?
Task's recent update to his kernel makes me want to try it because I've been using KToon's kernel with the ktoonservative governer and row scheduler UV'ed a little bit but unlocked to 2.1GHz and have been having some pretty bad battery life in mu opinion, do you think switching to task's kernel would be better on the battery?
Well what do you guys think?
Fun Fact for the day. Versus threads get shut down in no time here on XDA.
P.S- Why wouldn't you just try it first before making a thread about it? Kernels take about 3 seconds to flash. Also. No one can tell you that you will get better battery life on one or the other considering all of the variables. We are all in different locations, use different apps, have different settings, and we all use our devices differently. You need to try them both out and see which one works better for YOUR device.
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
berryman13 said:
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
Click to expand...
Click to collapse
I'm not giving you are hard time. I'm just telling you the facts here. If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Which no one can tell you one is better than the other for. Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
gilo123 said:
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
task650 said:
If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
Click to expand...
Click to collapse
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
gilo123 said:
Ithey're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
berryman13 said:
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Click to expand...
Click to collapse
He cannot answer this question honestly. He doesn't have your device. You're not understanding. He can have the best battery life possible on my kernel but if you use it, you could have the worst battery life possible. IT'S DEVICE DEPENDENT. Will you please just do yourself a favor and take 3 seconds, flash the kernel, and see. You say you've tried them both, but you are also asking about playing games and what not with them? You would know if you had tried them dude. Same goes for the governors & schedulers. You would also know that if you had actually tried them both. I need to ask you this. Why won't you just try them and see for yourself. Are you really the type of person to flash what people tell you to your expensive device?
Look dude. I'm only trying to help you here. I'm not quite sure why you wouldn't just take my advice here. I have quite a bit of experience with this stuff and I'm trying to help you get the best experience possible. But it seems as though you think that personal opinions of others are whats best for your device when in all reality they are not. Real life testing is what will prove to be best for your device. Trust me.
berryman13 said:
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
Click to expand...
Click to collapse
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Comprehensive list. I like it. Now I gotta figure out which gov I'm gonna use when I flash the underwear kernel.
Thanks everybody for their input, if anyone else has anything to say then please go for it!
Wiping cache + dalvik and flashing underwear kernel then fixing permissions and rebooting and gonna take a look around performance control to see whats up.
task650 said:
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
Click to expand...
Click to collapse
Ohh Thnx man. While you're here any suggestions as to how I go about fixing/finding out which apps are responsible? Also,any combinations/settings you might recommend trying with your kernel,despite the phone dependent variables and what not. Thnx )
Running the underwear kernel today, changes frequencies min and max to the farthest it can go. Will report back with my results.
Sent from my SGH-I747 using xda app-developers app
Sorry man, but no need to report back here as it has already been stated that each User's experience will differ upon usage, apps, personal habits, planet alignment,... Boils down to a flash and see type thing.
Thread Closed
Here is some info on Governor and I/O schedulers. Obviously it isn't going to include Ktoonservative or ROW but you get the idea.
I'm running SOA B2 with their kernel, in performance setting it allows me to go up to a maximum of 1836 MHz, is this safe?
Will battery life worsen?
Should I change the governor or I/O scheduler?
If you know what any of it means, it'd probably be best to stay away from it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have many app ideas, but don't have the skill or the time to learn how to make an app. if you would like to know an idea and attempt to make one, just message me.
Listen arianaLarge, don't bother replying if all you are gonna do is talk ****. Help the rookie out. This is a place for learning and contributing, its a community, it does not belong to you.
Having said that,.....you will lose stability and battery life if you go that high.
You will gain considerable performance but for what really?
Do you need it, probably not.
Personally I underclock to 1.18 for 80% of the day during the week, and run at 1.67ghz all day on the weekends. Its very easy to kick it up higher if you need the performance boost.
Also educate yourself on the various governors to better manage your CPU draw.
Google is your friend and the greatest tool you have for information.
Use tricksterMod or system tuner in the play store to manage CPU states and governors, both are free.
Both are great
there is no spoon.....
I never touch my CPU settings and use stock rom kernels....I've never seen a significant reason to bother with changing things. And I've never had hardly any of the problems I read in the rom dev threads.
Just my two cents.
Sent from my cell phone telephone....
Make sure you don't click the save on reboot button (or whatever it's called) because you may end up in a boot loop until you can flash some recovery to reset the setting. I don't think you're at too much of a risk, but the phone may not run stable and will likely shut down if it's pushed too hard. That's what I think.
Yes the battery life will be shorter. It may not be drastic unless you are constantly using it because the CPU speed will go back down when you idle.