Well sure, your phone may not be able to HANDLE an OC, but generally, in both the PC and Android worlds alike, it's seen that overclocking can't destroy a phone because it will generally become unstable and shut down before the heat can cause any damage, unlike an overvolt where you can just instantly fry the transistors on the chip.
While that is true, you have to factor in the added concept of user proficiency with troubleshooting skills as well. Otherwise you get all those posts like I mentioned above.
It's not
just whether the phone can handle the OC, or the rooting process, or whatnot, It's the
totality of everything,
including user experience, that makes the warnings still justified.
I have stated in the past that I have never personally heard of an instance where a OG Droid could not be OC'd to AT LEAST 800MHz. I would expand that and venture to say that almost all D1's (if not 100%) can handle 1.0GHz. Above that...it's on a phone-by-phone basis.
1.1GHz was the max I could go with 100% functionality (no reboots, etc.).
I have seen a pair of DROIDs that acted stupidly on 800 MHz - granted, they were both refurbs owned by different people, both of whom had had their original DROID replaced, and only one of whom had been rooted previously.
I realize the extenuating circumstances (refurbs) probably had a lot ot do with it - but if your phone cannot handle it, regardless of the circumstances, your phone cannot handle it.
i too think that all og droids are capable of over clocking safely. most can handle 1gb easy enough.
the problems come from the operators end not the phone. mostly either by trying to go high or being uninformed about the process.
over clocking your phone will not harm your phone as long as you read up and
slowly work your way up to faster kernals (imo)
Agreed - as I said above, the problem comes from the
totality of the situation - not
just the phone, not
just the user, not
just the instructions -
ALL of it put
together
.
I would have to generally agree with the comments made here. OCing your OG Droid is definitely possible; however, the max OC is completely dependent on your actual device. Some can handle 1.25, while others can barely handle 800.
I have been able to OC mine to 1.1 without any issue, but haven't really attempted to OC it any higher. I tried a couple Chevy kernels that were above 1.1 and my phone hated them. So, I have stuck with my trusty 1.1 Chevy LV #2 kernel. That said, I don't notice enough of a speed boost to warrant running my OG Droid at 1.1 all the time compared to 1.0 with "decent" battery life. What I mean is that I run at 1.1 while plugged in and charging, but not on battery. I get about 20-28 hours of battery with normal use (medium texting, occasional phone call, light to moderate data use) while running at 1.0 and about 10-11 hours with the same usage while running at 1.1.
As for rooting, there are so many methods available that if one doesn't work, another surely will. The main ill effect that comes from rooting is the user. If someone roots and doesn't know what the hell they are doing, they could potentially delete or change files that should not be touched. Luckily, we do have ways of reverting to stock (to try again) and backing up our entire system.
I completely agree that the warnings are all the same no matter what. Just because there have not been any (or at least any I know of) reports of a fried Droid from OCing doesn't mean that it cannot happen. I know of a couple people who have OCd their computers and ended up frying their processors, motherboards, etc. Since the general task of OCing does the same thing to a processor on a computer as it does on a mobile phone, I would say that it is completely possible to over work your phones processor.
With all of that said, I don't think that we can completely lay to rest the rumor of ill effects of OCing and rooting. However, we do know that, for the most part, they are not as bad as the Manufacturers would have us to believe.
Kratos
Undoubtedly - for 99% of issues (specifically those not hardware related) we can fix the problem. Hardware issues are, for the most part, out of our control.
With computer CPUs, though, the majority of OCing is performed by folks who do not understand that finer points of OCing in the first place - "Let's increase our clock multiplier and see what happens!" Well, if you pay attention to your voltage, it
also increases to match the desired output - so you either have to a) manually lower the voltage, or b) stick with it and monitor it to make sure it is not going too far up, especially based upon your hardware capabilities. So many tiny things, like with my Core1Quad CPU and eVGA mobo - adjust the
millivoltage of the GTRLEF Lanes to execute timings and speed much better than before are beyond even me - I pick a stable OC and let it go, making sure the voltages stick close to where the hardware specs allow them to be. If I understood what those GTRLEF lanes actually did, and how better to manipulate them , I should be able to take my Core2Quad 6600 from 2.4 GHz to 3.6 GHz, achieving a 50% OC - as it is I settle for a 33% OC to 3.2 b/c that is where it stays stable without really fine tuning those Lanes.
With our phones, it is a little bit different. In the beginning, I tried pushing my phone past hte 100 Mhz barrier - it refused to budge. Back then, there were no
low voltage / ultra low voltage kernels available. Low and Behold, (I don't remember who did the first LV - Taz? Chevy? just don't remember, sorry) someone came out with the LV kernel - after 3 more devs started using the LV moniker for their kernels, I tried one - Chevy's 1.2 GHz kernel - and it worked. Perfectly.
Since then I have played with quite a few ROMs, and some liked Chevy's kernel and some didn't - now, on LFY, I leave the stock 1.0 GHz kernel - I've learned that I want ultra stability with a performance boost, but IDGAF about bragging rights regarding what my Quadrant scores anymore - I want to be able to use my phone with my 130+ apps all the time, with no issues like reboots, overheating, etc.
With regards to the OP, though, the warnings, as I and others have said, are just that - warnings. Since these outcomes are theoretically possible, they must still be maintained.
