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!
Related
Just wondering if anybody has tried this kernel yet? Found it over on AndroidMobileJunkie.com (Followed a link in somebody's sig here n XDA that said 1.28Ghz so naturally I was curious lol) Anyways, here's the link for the post over on AMJ. http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-22-oct.11/
yea ziggy's kernel. It's been in discussion in both of the Desire rom port threads. 1.28 is very rough on the processor though, and mostly unstable for a lot of people's phones (mine included), even ziggy admits it's a risky business, but he has proven it is possible.
I am so tempted to try this, but I'm afraid to fry my phone. My go big or go home mentality may make me give in. Wish there was someone who posted on the thread link
I ran it. No problems a 1.28 but really didn't use it long. Here's my Quadrant post in the Desire Z port thread:
http://forum.xda-developers.com/showpost.php?p=8775977&postcount=168
X
I'd imagine that clocking the processor that high wouldn't make much difference than say, 1.19GHz.
In fact, in plenty of ROMs I've tried, anything clocking over 1152mhz actually gives me a decrease in my quadrant scores. Not to say its not a stability issue - I'd assume that most Snapdragons actually clock higher than 998mhz, but then are reduced because that's baseline performance, anything less than 998mhz would get kicked.
I've never had a ROM crash, even running at 1.19GHz, but didn't notice any performance gains, plus, unless you just happen to get a chip that is capable of 1.28GHz no problem, it's probably near bottle-neck anyway.
And Quadrant has several variables way outside of clock speed that can pull 1800's, including just your flavor ROM.
Bottom Line: It's not worth frying your phone just for a barely-existent performance gain. If you happen to have a processor that is incapable of stability at 1.28GHz, you might fry out some transistors, then get stuck with something that freezes if you clock it over 700, let alone the 998 stock.
For me personally 1.28 is no improvement over 1.152. In fact, it gives me worse benchmarks.
sorry for repost
I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.
I tried this kernal and my camera stopped working...
HeyItsLou said:
I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.
Click to expand...
Click to collapse
Lou hit the nail on the head. I love the .17 kernel. Im using the new guy with great performance, battery life, charging, and neat transitions. its like a new phone.
I'm using this with a vanilla froyo ROM and my battery life is amazing. Haven't noticed any freezing or any program not working.
Wow!
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol
dimebagdan65 said:
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol
Click to expand...
Click to collapse
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z
Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?
Nevermind...found it!
ziggy471 said:
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z
Click to expand...
Click to collapse
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy
hajabooja said:
Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?
Click to expand...
Click to collapse
What AOSP kernel??? I only see one kernel, and it references skyraider, which leads me to believe it is a sense kernel
edit: I am dumb. It is a different thread on the same site as listed above
http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-aosp-23-oct.24/
rmaccamr said:
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy
Click to expand...
Click to collapse
I didn't take it as such, and I agree with you fully. I prefer somewhere between 1.113 and 1.15. That's the reason I included the init script to set the max at 1.113, which I find very stable and fast, hell I'd say 1865 quad with ID's Z port isn't too shabby at 1.13.
I should be able to get 1.28 more stable with playing with the voltages, it's just that takes time, and I wasted too much this morning doing both AOSP INC and Evo kernels, so I'm worn out for awhile on kernels. I still need to fix the Evo for puertoblack, since it appears I left the debug port out, so no adb for it. lol
Z
I bet everyone has heard of the droid 2 and X being overclocked to crazy speeds right? Well... how come the Incredible hasn't reached those speeds?!?! Im sure some awesome dev could probably achieve this! There are many Inc owners who would like... scratch that... LOVE this speed increase, and im sure they wouldn't mind donating to the truly amazing dev who does this. Now the question is... whose willing to do it?
Sent from my ADR6300 using XDA App
The problem is that our phones can't handle those speeds mine cant handle anything over 1.113
Sent from my Incredible using XDA App
Gahh Its Lee said:
The problem is that our phones can't handle those speeds mine cant handle anything over 1.113
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That doesn't mean we can't try! Lol
Sent from my ADR6300 using XDA App
You could probably achieve this. Except you'd be buying another phone after your incredible spontaneously combusts from this kind of overclocking. Motorola phones use a different line of processors, OMAP from Texas Instruments rather than the Snapdragons.
then why with D2 or X's is that possible?
Because the Droid 2 and X use completely different processors made by completely different companies. We have a Qualcomm Snapdragon they have Texas Instruments OMAP.
No, see. Those speeds are fake. There's no way a mobile processor with today's technology could handle speeds of 2GHz or higher. 1.6Ghz is the highest I've seen on the X/2, and it wasn't very stable. That's why these "overclock apps" for the Droid X/2 only have options for 1.4GHz max.
Fake... plain and simple... you can't even overclock a PC processor 1.5ghz above its stock speed without some serious cooling. You really believe that a phone, with no fan/water/cooling of any kind can do it?
I am not a dev but my first degree was in engineering 20years ago. So when I say that its extremely unlikely that any of the massive OC stories are true I am talking from knowledge of engineering processes. 30-40% OC seems to be in the realm of reality. Beyond that, you enter the land of the bovine excrement.
First of all, as an engineer you simply do not design these chips with that much OC'ing being possible. Up to 40% OC seems possible - I would actually predict that some time in the near future we will be able to run the chips in the inc at 1.3 - stable. Expecting anything more is silly. If it was possible to run them at those speeds, guess what, they would have released them as 1.5 or 2 GHz chips.
Secondly, even if you were to temporarily be able to run them at substantially higher frequencies than what we can see them get to right now, they would be extremely unstable and would run hot very quickly. Thats too big a risk to take. In the best case scenario, you will just have a bricked device - replacing which will cost you $500-600. In the worst case, you will burn your hand and/or your face.
I would recommend that the OP volunteers his money, device(s), body and brains towards finding just how far we can OC an incredible. In the meantime I am happy to sit on the sidelines and implement solutions which are more logical and less quixotic.
wow LOL sounds cool to me just wondering, thank you!
IMO, Over clocking is over rated. You end up with reboots, crashes, and an unreliable phone.
I see a lot of people more concerned with quadrant scores than good battery life. Some of them expect both. I for one think the incredible is fast enough already, especially coming from a storm 1.
Sent from my ADR6300 running Virtuous 3.1.0, v4 kernel, using Tapatalk Pro.
To be honest i do notice a little bit of a speedup when I had mine overclocked to 1.15. But of course less battery life is a trade off with that. I am running the newest HTC stock kernel, no OC, and am very happy with battery life and speed. The phone would absolutely FLY with an OC of 1.5ghz or higher. But as someone said, if it was made to do that, they would have just put a 1.5ghz chip in there to begin with.
Hey all, I want to get some info on the limitations of our processor, mainly is their a ceiling on how high we can overclock our Evo's?
I am sure most of us here are familiar with the insanely fast 1.3ghz-1.8ghz(I think the top I read was 1.8ghz) speeds some newer phones are getting clocked to, the only thing that caught my eye about these speeds is that they are reported stable & usable. Coming from a Hero(a while ago) that I had to overclock to my Evo that is not really necessary to overclock was nice, BUT it would be awesome to have an Evo clocked at 1.5ghz-1.8ghz and stable as well as usable, is this even remotely doable? If not what is causing the limitation? Just curious
Edit: HAPPY THANKSGIVING, I am very thankful for my wife & kids as well as all you great guys and gals here at XDA!
Sent from my White Evo 4G
It all depends on your phone....what may run on yours may send mine into random reboot...I found mine is stable at 1.13
You may want to raise the bar a little at a time to see what you can handle....be sure not to have it set on boot till you are sure your phone can handle it....
Sent from my froyo using the xda app
matthewjulian said:
Hey all, I want to get some info on the limitations of our processor, mainly is their a ceiling on how high we can overclock our Evo's?
I am sure most of us here are familiar with the insanely fast 1.3ghz-1.8ghz(I think the top I read was 1.8ghz) speeds some newer phones are getting clocked to, the only thing that caught my eye about these speeds is that they are reported stable & usable. Coming from a Hero(a while ago) that I had to overclock to my Evo that is not really necessary to overclock was nice, BUT it would be awesome to have an Evo clocked at 1.5ghz-1.8ghz and stable as well as usable, is this even remotely doable? If not what is causing the limitation? Just curious
Edit: HAPPY THANKSGIVING, I am very thankful for my wife & kids as well as all you great guys and gals here at XDA!
Sent from my White Evo 4G
Click to expand...
Click to collapse
not exactly sure how it works on the phones but if its anything like a pc processor then it would take a kernel that can tweek voltages right like to get a 1.8 on our ever i would say it would need about a 3 step down uv but not sure if it would be stable heck at 3 step down uv it shouldn't boot unless its set oc'd on splash boot I'm pretty sure since our proc. are first gen snapdragons and the one's in the G2 and myTouch 4G are second with a smaller die ours won't be able to make it that far up with out major modification
Hmmm......so if I were to get off my ass and learn to compile a kernel I could at least attempt it, good info, thanks! At least now I have a place to start researching, I think I would be happy with a bump to an even 1.5ghz if it were stable, well if anyone else has more info I'm all ears!
Sent from my White Evo 4G
I got mine at 1.15 anything past that seems unstable 1.2/1.25 reboots automatically (cm7 nightly 88)
The FroYo kernels come unlocked to 1190 I believe. When I was running FroYo I ran 1152 all the time. You don't really need to compile your own kernel unless you really want to. All of the kernels available here are unlocked except for the stock kernels. Also 1190 was about the limit for most EVOs.
I don't have an evo, but I do have a snapdragon, use quadrant to check scores after an overclock. 1190 isn't so good. Makes lower scores than the stock 1ghz. Fsb bottlenecks at that speed, but gets a boost at 1530. I've had my snapdragon around 1600 stable all day. Low battery life though.
Sent from my HTC HD2 using XDA Premium App
Hello, after running all the kernels currently available for kindle fire, I cant help but noticing that none can clock up to more then 1200mhz. While this is an improvement, I would liek to see a kernel that could overclock all the way up to about 1400-1600mhz. I am sure that the kindle could handle it, It does fine with 1200mhz. Any thoughts, anyone think the kindle could handle this. If so, whats stopping all these great devs?
What a great thread to start. While we're at, here's what I'd "liek" to see: push the CPU to 3 cores. And can we get a higher pixel density, devs? I mean, come on!
My understanding is that no one will release a kernel OC'd to more than 1200 because it's dangerous. Even if some Kindle's can handle it, some can't even handle 1200, and it would cause too many problems with people breaking things. If you want it that bad you'll learn how to compile your own kernel.
This is the development section. Not the Q&A/General. If you would like something, please try it yourself. Remember, everyone does this for free and as a hobby.
What hasoon said...
What Jake said is correct also, it would take waay too much work to get an overclocked kernel stable enough for the masses. Lower frequencies are generally more easily overclocked to higher levels than already high frequencies are.
Plus, why would you even want to overclock, what app/game is it that needs more than our 1.2ghz can handle, especially since we have a dual core cpu? I can't think of any and I have over 900 apps/games.(Not all on my KF, of course)
All it would do is drain your battery faster. Even games like NOVA 2 & NOVA 3(Probably not the most resource intensive games, but you get the point) run fine on 600 and 800 mhz.
Tl;dr:
There would be little to no benefit in furthur overclocking our KF's.
I agree, I use the "Kindle" at a frequency of 800MHz, and I have enough speed for gaming and work)
But that should be added, so this optimization core to increase the autonomy of the "Kindl"
0xD34D had a 2.6x capable of 1.3ghz. Worked well, I had no issues.
If your still stock ROM look it up although some will say it's "dated".
Keep in mind just because it's clocked higher does'nt mean it's faster.
At 1.3ghz it felt OK but benchmarked well below 1.2ghz, something I've noticed on my G-Nex as well. Once over a certain speed performance drops.
Jr member. Hahaha
manchucka said:
What a great thread to start. While we're at, here's what I'd "liek" to see: push the CPU to 3 cores. And can we get a higher pixel density, devs? I mean, come on!
Click to expand...
Click to collapse
PowSniffer0110 said:
Jr member. Hahaha
Click to expand...
Click to collapse
What's the point in posting crap like this other than to be a troll?
Short answer is no, it's not going to happen.
All trolling aside half our devs didn't even want to go to 1.2
Do to differences in device state / hardware race (yes there are some differences in hardware albeit small and not expected by Amazon to be noticeable in stock, that obviously changes when you start changing the OS), there's no way to know who's kindle will support what clock speeds.
If that's not enough for you let's consider that TI clocked it at 1024M for a reason and that any manipulation beyond the MFG specs is going to run the risk of shortening the devices life. You'd get a similar response from me if you are talking real PCs as well. Quite frankly the risks of high OC are not worth the reward, for any device IMHO
Requests go in Q&A (moved)
Pax
FSM Amazon Kindle Fire
Sent from my R800x using Tapatalk 2
any one here can be a "dev" with learning and patience.
if we don't take it upon ourselves then we can't rightly complain with what's available.
with that said i will. i personally do't agree with the argument that it's not good for the device, some can't handle it, etc., so it's not done.
My gnex with the latest faux123 kernel can be set as high as 1.8ghz.
i cant get past 1.35 without a massive hit to performance, same with any other kernel that allow crazy high clock settings. there's a few.
At 1.56ghz it locks up. i don't blame faux123 for the instability at those speeds.
when battery life isn't a concern i'm clocked at 1.35ghz. i won't blame him if the phone stops working either.
I like that he put it there allowing me to try it. it's fun to push the limits. this is about fun.
There's a demand for oc'ing everything. I'd do the same with the KF, although from the 0xD4aD kernel i already know my KF was perfectly stable at 1.3ghz even with uv.
i wish i had the patience but sadly i don't so I wait.
fr4nk1yn said:
i wish i had the patience but sadly i don't so I wait.
Click to expand...
Click to collapse
Interesting irony here
PowSniffer0110 said:
Jr member. Hahaha
Click to expand...
Click to collapse
So many trolls, nothing better to do than stuff his face with donuts, play wow, and TROLL LOL
Sent from my Galaxy Nexus using Tapatalk 2
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.
thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.