- Joined
- Nov 18, 2009
- Messages
- 11,104
- Reaction score
- 28
- Current Phone Model
- iPhone 7+ 256gb
Let's end the talk on Fraud...Please
I think I fried my droid
- Thread starter clwither
- Start date
SSHGuru
Silver Member
Wow this convinces me even more NOT to root my phone.
daftlush
Member
- Joined
- Dec 24, 2009
- Messages
- 53
- Reaction score
- 0
It's not charged enough. Happens to me all the time when running off comps usb.
- Thread Starter
- #19
NoKz
Member
Rooting is fine, there's nothing wrong with it. If you're still paranoid, just use the Roms in my signature. They're on the stock kernel and aren't overclocked. :icon_ banana:
Last edited:
- Thread Starter
- #21
Any problems with that 1.2ghz kernel?
SSHGuru
Silver Member
NoKz
Member
Nope! I've been at 1.2GHz for about....3 weeks now. I haven't had a single issue with that kernel and BB 0.7.6. It also works well on BB 1.0. :icon_ banana:
- Thread Starter
- #24
further customization of the phone for one, root only apps second, and last ... that's all i got lol
- Thread Starter
- #25
knotbeerdan
Member
I've been overclocked on my droid for a few weeks now also. So far I have seen that issue once or twice but once the phone sleeps for a minute its fine. I'm running 1GHz now and was at 1.2 before. I think the only rom I saw that on was a 2.1 rom come to think of it.
- Thread Starter
- #27
Yeah i started at 900mhz then went to 1ghz. I dont think im ever going to clock higher than that again. Its just not wroth it... Or at least until i can get a temperature application
knotbeerdan
Member
There is one available on the market. Just search for temp sensor. Mine runs constantly around 87F I've been as high as 114F with no issues. Our processors are rated for higher temps than that.
I had one crash and reboot in about a month being at 1GHz.
It was a sunny day... I wasn't doing anything in particular...then out of no where (!) some insane/crackly/crudy/digital/burpish noise came out of my droid!...a sound that should NEVER come from any machine ever...every thing stopped...the birds went quiet...the trees stopped swaying in the breeze...in the distance a dog barked...I stared down at the droid in my hand and the screen was frozen...then it flickered...YES the screen flickered! and then went blank..I began to wonder..."Am I the one!...will I be the first person on Droid Forums dot net to honestly say that I 'fried my droid'!?!"
Then it rebooted and we went on our merry way.
No issues since then
RW-1
Silver Member
The only real problem with OC'ing it is newb's dont set it to a lower setting at idle, or when charging. Leaving it at 1200Mhz all the time is asking for trouble.
Then you have the typical ones who push it a bit too far, but that just involves lowering it slightly.
I also really can't see the store figuring out what has happened, they are going to see if they can ressurect it, and when that fails, they'll give you a story like the display burnt out, not knowing that you may know more than they do on it.
Then you have the typical ones who push it a bit too far, but that just involves lowering it slightly.
I also really can't see the store figuring out what has happened, they are going to see if they can ressurect it, and when that fails, they'll give you a story like the display burnt out, not knowing that you may know more than they do on it.
