*WARning* O/C @1000Mhz+

[BayouFlyFisher]

I think we have a Breakfast/Lunch Logic going on here. My Grand Dad had a saying, "Just because Lunch comes after Breakfast everyday, does not mean Breakfast is caused by Lunch".

I think you are linking two events that may not have anything in common. There have been several phones fail with exactly the same symptoms as yours while charging and they were stock phones. The failure is related to a charging event and not to an overclock event.

 

[r-dubya]

I have read about that as well. The difference seems to be that the majority of those phones had temp problems from the beginning, with owners saying their phones felt hotter then they thought they should.

I got my phone the second day it was out, and NEVER had a heat issue. I have been O/Ced since almost the first kernels that supported it were released. And it was only AFTER clocking to speeds of 1000+ that i noticed ANY issues...

I do like your quote though, i something similar to it all through out my undergrad program.. I had a professor who was very fond of that logic of thought.

 

[Hugh Jass]

It really sounds like this was something not up to par with your hardware to be honest, way too many people are running at absurd speed, the fact your phone was the first to fail out of all of these tells me your hardware had to have a defect. I've pushed my phone to the limit with my own stress test, as soon as the chip reached 145-150F the phone simply shut down, and went into a boot loop a few times until it cooled. I don't think software could cause this to happen really.

 

[BayouFlyFisher]

I have read about that as well. The difference seems to be that the majority of those phones had temp problems from the beginning, with owners saying their phones felt hotter then they thought they should.

I got my phone the second day it was out, and NEVER had a heat issue. I have been O/Ced since almost the first kernels that supported it were released. And it was only AFTER clocking to speeds of 1000+ that i noticed ANY issues...

I do like your quote though, i something similar to it all through out my undergrad program.. I had a professor who was very fond of that logic of thought.

Grand Dad was a smart old coot.

 

[JhankG]

I think we have a Breakfast/Lunch Logic going on here. My Grand Dad had a saying, "Just because Lunch comes after Breakfast everyday, does not mean Breakfast is caused by Lunch".

I think you are linking two events that may not have anything in common. There have been several phones fail with exactly the same symptoms as yours while charging and they were stock phones. The failure is related to a charging event and not to an overclock event.

Exactly. I've been overclocked since the day it became possible and am now running at 1.2ghz. There would have been other cases of this happening if it was related to overclocking.

 

[r-dubya]

I was thinking the same, but the phone was hung. the alarm clock blaring and it was completely unresponsive. I have had it to some pretty high temps before myself, but never felt what it was i felt this time...

Did you do your tests with your phone charging on your AC adapter? I think it was just a strange occurrence with a few freak anomalies mixed together. I DONT think it was my hardware, as i have had any hardware issues to speak of...

 

[r-dubya]

I think we have a Breakfast/Lunch Logic going on here. My Grand Dad had a saying, "Just because Lunch comes after Breakfast everyday, does not mean Breakfast is caused by Lunch".

I think you are linking two events that may not have anything in common. There have been several phones fail with exactly the same symptoms as yours while charging and they were stock phones. The failure is related to a charging event and not to an overclock event.

Exactly. I've been overclocked since the day it became possible and am now running at 1.2ghz. There would have been other cases of this happening if it was related to overclocking.

Not entirely true. Look guys, I'm not saying unroot and head for the hills, I'm only stating what happened to me, with the facts i know, take it as you will. I was only attempting to warm you guys, thats all....

 

[mikes]

Don't say i didn't warn you though. $89 for a replacement isn't a lot of money, but that's $89 i could have used on something else...

So, instead of taking responsibilities for your actions, you ripped off the insurance company. Nice.:dry:

 

[BayouFlyFisher]

I think we have a Breakfast/Lunch Logic going on here. My Grand Dad had a saying, "Just because Lunch comes after Breakfast everyday, does not mean Breakfast is caused by Lunch".

I think you are linking two events that may not have anything in common. There have been several phones fail with exactly the same symptoms as yours while charging and they were stock phones. The failure is related to a charging event and not to an overclock event.

Exactly. I've been overclocked since the day it became possible and am now running at 1.2ghz. There would have been other cases of this happening if it was related to overclocking.

Not entirely true. Look guys, I'm not saying unroot and head for the hills, I'm only stating what happened to me, with the facts i know, take it as you will. I was only attempting to warm you guys, thats all....

Absolutely not questioning your intentions or actions. Just an honest disagreement as to cause and effect.

Hope you get your new phone soon.

 

[hookbill]

Funny when mine got to 118 on the battery temperature it was under my pillow just like the OP. I was charging at the time and it was hooked up to the charger all night and only charged to 50%.

 

[mikes]

"Just because Lunch comes after Breakfast everyday, does not mean Breakfast is caused by Lunch".

Post hoc, ergo propter hoc.

Being paranoid doesn't mean someone isn't out to get you.

 

[gentlefury]

mine is oc to 800Mhz and downclocked to 250 when sleeping...it actually gets cooler than it did before I set it to underclock....operating temps seem the same, get hot while plugged in or dling....9 out of 10 times heat is caused by something pulling data....not the CPU...are you sure you didn't add an app that constantly pushes or pulls data...that would be a much more logical answer than OC.

I have had my phone go down to 68º while sleeping.

 

[BayouFlyFisher]

Don't say i didn't warn you though. $89 for a replacement isn't a lot of money, but that's $89 i could have used on something else...

So, instead of taking responsibilities for your actions, you ripped off the insurance company. Nice.:dry:

Absolutely don't agree with this. His insurance is basically a "no assigned fault" policy as it will cover even loss and mysterious disappearance. They don't care what happened to it, they just replace it. I'm pretty sure their policy is so lenient because they collect 6.99 per month and then charge you $89 for a refurbished phone. And I bet their cost for the replacement phone is probably, oh say about, <$89!!

Anyway we have no proof that anything he did to his phone caused it. I've done the same or worse to mine and it still functions and even functions at very close to stock temperatures. Mine's never seen anything over 107.

 

[BayouFlyFisher]

"Just because Lunch comes after Breakfast everyday, does not mean Breakfast is caused by Lunch".

Post hoc, ergo propter hoc.

Being paranoid doesn't mean someone isn't out to get you.

Good point but remember, "A wet bird can't fly at night".

Also, the early bird catches the worm. But you're still eating worms!

 

[Hugh Jass]

Did you do your tests with your phone charging on your AC adapter?

I sure didn't, but my only point was that with just the processor alone with no extreme heat from the battery, the system simply failed before damage was done. If this was by design or not I wouldn't know, but it happened below the rated heat for the chip. It seems across the board our phones are unique to to even very similar situations which makes cross examination nearly impossible at any accuracy.

The hottest my phone has ever been by feel was when I had it plugged in charging while playing Pandora and running navigation at the same time. It was damn hot no lie, but nothing that seriously concerned me and that is a brutal combination to say the least.

There was some special scenario going on for you to burn up your board, I think we can agree on that.