<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_06_30_2356228</id>
	<title>Some Overheating 3GS iPhones Glow Pink</title>
	<author>kdawson</author>
	<datestamp>1246351860000</datestamp>
	<htmltext><a href="http://hughpickens.com/slashdot/" rel="nofollow">Hugh Pickens</a> writes <i>"The Telegraph reports that dozens of users of the recently released iPhone 3GS have reported overheating issues, with <a href="http://www.telegraph.co.uk/scienceandtechnology/technology/apple/5699853/Overheating-iPhone-3GS-handsets-worry-users.html">some iPhone owners unable to pick up the device</a> because the handset gets so hot to the touch, while others say <a href="http://iphone.tmcnet.com/topics/iphone/articles/58935-iphone-3g-s-overheating-issue-raises-recall-flag.htm">the casing turns pink with the heat</a>. 'I am definitely experiencing issues with the iPhone running warm and quick battery life lost,' writes Tom Goldstein on one discussion board. 'The phone seems to warm up almost immediately if I am doing anything that pulls data over the network.' Some users have said the device has been too hot to put to their ear while making a phone call, and others say the overheating seems to occur when owners are using the iPhone's mapping software, which uses the handset's built-in GPS technology. Melissa J. Perenson writes at PC World: 'I became aware the handset had become very hot. Very, very hot &mdash; not just on the back, but <a href="http://www.pcworld.com/article/167495/apple\_iphone\_3gs\_overheating\_reports.html">the entire length of the front face</a>, too.' Some gadget experts believe faulty batteries could be the cause of overheating and poor battery life. 'My guess is there's going to be a whole lot of batteries affected because these [iPhones] are from very large production runs,' said Aaron Vronko, who fixes iPods and iPhones. 'If you have a problem in the design of a series of batteries, it's probably going to be spread to tens of thousands [of device], if not hundreds of thousands, and maybe more.'"</i></htmltext>
<tokenext>Hugh Pickens writes " The Telegraph reports that dozens of users of the recently released iPhone 3GS have reported overheating issues , with some iPhone owners unable to pick up the device because the handset gets so hot to the touch , while others say the casing turns pink with the heat .
'I am definitely experiencing issues with the iPhone running warm and quick battery life lost, ' writes Tom Goldstein on one discussion board .
'The phone seems to warm up almost immediately if I am doing anything that pulls data over the network .
' Some users have said the device has been too hot to put to their ear while making a phone call , and others say the overheating seems to occur when owners are using the iPhone 's mapping software , which uses the handset 's built-in GPS technology .
Melissa J. Perenson writes at PC World : 'I became aware the handset had become very hot .
Very , very hot    not just on the back , but the entire length of the front face , too .
' Some gadget experts believe faulty batteries could be the cause of overheating and poor battery life .
'My guess is there 's going to be a whole lot of batteries affected because these [ iPhones ] are from very large production runs, ' said Aaron Vronko , who fixes iPods and iPhones .
'If you have a problem in the design of a series of batteries , it 's probably going to be spread to tens of thousands [ of device ] , if not hundreds of thousands , and maybe more .
' "</tokentext>
<sentencetext>Hugh Pickens writes "The Telegraph reports that dozens of users of the recently released iPhone 3GS have reported overheating issues, with some iPhone owners unable to pick up the device because the handset gets so hot to the touch, while others say the casing turns pink with the heat.
'I am definitely experiencing issues with the iPhone running warm and quick battery life lost,' writes Tom Goldstein on one discussion board.
'The phone seems to warm up almost immediately if I am doing anything that pulls data over the network.
' Some users have said the device has been too hot to put to their ear while making a phone call, and others say the overheating seems to occur when owners are using the iPhone's mapping software, which uses the handset's built-in GPS technology.
Melissa J. Perenson writes at PC World: 'I became aware the handset had become very hot.
Very, very hot — not just on the back, but the entire length of the front face, too.
' Some gadget experts believe faulty batteries could be the cause of overheating and poor battery life.
'My guess is there's going to be a whole lot of batteries affected because these [iPhones] are from very large production runs,' said Aaron Vronko, who fixes iPods and iPhones.
'If you have a problem in the design of a series of batteries, it's probably going to be spread to tens of thousands [of device], if not hundreds of thousands, and maybe more.
'"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540927</id>
	<title>Why not read the logs?</title>
	<author>Anonymous</author>
	<datestamp>1246455660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Download the iPhone Configuration Utility, connect the iPhone and read the log.</p><p>My wife's 3GS was constantly running some process in the background and added 3 log entries every second.  The battery drained quickly.  We did an OS restore without restoring the backup and it gets great battery life now.</p><p>A little troubleshooting goes a long way.</p></htmltext>
<tokenext>Download the iPhone Configuration Utility , connect the iPhone and read the log.My wife 's 3GS was constantly running some process in the background and added 3 log entries every second .
The battery drained quickly .
We did an OS restore without restoring the backup and it gets great battery life now.A little troubleshooting goes a long way .</tokentext>
<sentencetext>Download the iPhone Configuration Utility, connect the iPhone and read the log.My wife's 3GS was constantly running some process in the background and added 3 log entries every second.
The battery drained quickly.
We did an OS restore without restoring the backup and it gets great battery life now.A little troubleshooting goes a long way.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540007</id>
	<title>Obviously the user's fault</title>
	<author>Opportunist</author>
	<datestamp>1246444380000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>The iPhone was supposed to be used by cool people who can easily take the heat.</p></htmltext>
<tokenext>The iPhone was supposed to be used by cool people who can easily take the heat .</tokentext>
<sentencetext>The iPhone was supposed to be used by cool people who can easily take the heat.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541747</id>
	<title>Re:should have released it in winter</title>
	<author>Sockatume</author>
	<datestamp>1246460580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually, a lot of people have their phone out in direct sunlight, especially in the summer. When I use my black Nokia on the bus, it heats up like crazy as long as the sun's out. The iPhone has one of the best transflective displays on the market, it'd seem a bit of a shame to hide it away from actual sunlight.</p></htmltext>
<tokenext>Actually , a lot of people have their phone out in direct sunlight , especially in the summer .
When I use my black Nokia on the bus , it heats up like crazy as long as the sun 's out .
The iPhone has one of the best transflective displays on the market , it 'd seem a bit of a shame to hide it away from actual sunlight .</tokentext>
<sentencetext>Actually, a lot of people have their phone out in direct sunlight, especially in the summer.
When I use my black Nokia on the bus, it heats up like crazy as long as the sun's out.
The iPhone has one of the best transflective displays on the market, it'd seem a bit of a shame to hide it away from actual sunlight.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540199</id>
	<title>Re:Oh hey no problem</title>
	<author>Anonymous</author>
	<datestamp>1246447320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Why would someone with a discoloured case just want a new battery? They'd go for a new device entirely.</p><p>Hence your post is pointless.</p></htmltext>
<tokenext>Why would someone with a discoloured case just want a new battery ?
They 'd go for a new device entirely.Hence your post is pointless .</tokentext>
<sentencetext>Why would someone with a discoloured case just want a new battery?
They'd go for a new device entirely.Hence your post is pointless.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542635</id>
	<title>Re:I'm dubious</title>
	<author>yabos</author>
	<datestamp>1246464480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The iPhone shuts the GPS off when it's not needed which is most of the time.</htmltext>
<tokenext>The iPhone shuts the GPS off when it 's not needed which is most of the time .</tokentext>
<sentencetext>The iPhone shuts the GPS off when it's not needed which is most of the time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540839</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171</id>
	<title>should have released it in winter</title>
	<author>cheekyboy</author>
	<datestamp>1246446780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Then they can claim it has a built in heater.</p><p>Test your products both in cold climates and 40c+ climates. btw apple, black sucks, it absorbes heat in the sun shine.</p></htmltext>
<tokenext>Then they can claim it has a built in heater.Test your products both in cold climates and 40c + climates .
btw apple , black sucks , it absorbes heat in the sun shine .</tokentext>
<sentencetext>Then they can claim it has a built in heater.Test your products both in cold climates and 40c+ climates.
btw apple, black sucks, it absorbes heat in the sun shine.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540027</id>
	<title>gayPhone</title>
	<author>Anonymous</author>
	<datestamp>1246444680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>iKnew that there iS someTiNg gay iN iPhone!</p></htmltext>
<tokenext>iKnew that there iS someTiNg gay iN iPhone !</tokentext>
<sentencetext>iKnew that there iS someTiNg gay iN iPhone!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541417</id>
	<title>Awsome, pink Iphone</title>
	<author>anexkahn</author>
	<datestamp>1246458720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Sounds like a feature to me, save me  $200 for getting it painted: <a href="http://www.colorwarepc.com/p-182-iphone-3gs.aspx" title="colorwarepc.com" rel="nofollow">http://www.colorwarepc.com/p-182-iphone-3gs.aspx</a> [colorwarepc.com]</htmltext>
<tokenext>Sounds like a feature to me , save me $ 200 for getting it painted : http : //www.colorwarepc.com/p-182-iphone-3gs.aspx [ colorwarepc.com ]</tokentext>
<sentencetext>Sounds like a feature to me, save me  $200 for getting it painted: http://www.colorwarepc.com/p-182-iphone-3gs.aspx [colorwarepc.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542659</id>
	<title>Re:should have released it in winter</title>
	<author>Sandbags</author>
	<datestamp>1246464540000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>My new 3G S gets pleanty of sunshine, sitting in a dock on my black dashboard in full direct sinlight...</p><p>I have run it for 4+ hours straight, in SC sunlight, in a car with poorly performaing Air Conditioning, (about 80 in the car) running iPod in the background, full volume output, WiFi and BlueTooth on, and with Google Maps on, in hybrid mode, screen set to not sleep, with GPS real time tracking and the compass enabled, while and charging the battery.</p><p>It was 102 degrees on Saturday.  After that much time under that heavy load, the device was warm, but placing it in my shirt pocket was not uncomfortable.  I even made a phone call within a minute or two of getting out of the car and placed it on my ear and was not at all concerned about the temp of the device.</p><p>I also played an immersive 3D game the other night from full charge until the battery died (about 4.5 hours) with the iPod running in the background.  My bluetooth headset was on in my pocket, and wifi was enabled.  The device again got warm, but not even as warm as it did in the car.  Far from uncomfortable.  My (now my wife's) 2G gets hotter under those loads.</p><p>Reports I've heard from people with "pink" phones are people who left it running like this under a pillow, in a bag, outside in the hot summer sun for hours, and other extreme conditions.</p><p>Quite possibly there's a battery issue and some bad one's floating around.  There's over a million of them out there already.  An issue rate of a few dozen phones per milion is a SMALL issue.  Also, being a LiPo, not a LiIon, though it may get hot, it;s not likely to explode or burn as cascade failure is fare more difficult to achive in LiPo.</p></htmltext>
<tokenext>My new 3G S gets pleanty of sunshine , sitting in a dock on my black dashboard in full direct sinlight...I have run it for 4 + hours straight , in SC sunlight , in a car with poorly performaing Air Conditioning , ( about 80 in the car ) running iPod in the background , full volume output , WiFi and BlueTooth on , and with Google Maps on , in hybrid mode , screen set to not sleep , with GPS real time tracking and the compass enabled , while and charging the battery.It was 102 degrees on Saturday .
After that much time under that heavy load , the device was warm , but placing it in my shirt pocket was not uncomfortable .
I even made a phone call within a minute or two of getting out of the car and placed it on my ear and was not at all concerned about the temp of the device.I also played an immersive 3D game the other night from full charge until the battery died ( about 4.5 hours ) with the iPod running in the background .
My bluetooth headset was on in my pocket , and wifi was enabled .
The device again got warm , but not even as warm as it did in the car .
Far from uncomfortable .
My ( now my wife 's ) 2G gets hotter under those loads.Reports I 've heard from people with " pink " phones are people who left it running like this under a pillow , in a bag , outside in the hot summer sun for hours , and other extreme conditions.Quite possibly there 's a battery issue and some bad one 's floating around .
There 's over a million of them out there already .
An issue rate of a few dozen phones per milion is a SMALL issue .
Also , being a LiPo , not a LiIon , though it may get hot , it ; s not likely to explode or burn as cascade failure is fare more difficult to achive in LiPo .</tokentext>
<sentencetext>My new 3G S gets pleanty of sunshine, sitting in a dock on my black dashboard in full direct sinlight...I have run it for 4+ hours straight, in SC sunlight, in a car with poorly performaing Air Conditioning, (about 80 in the car) running iPod in the background, full volume output, WiFi and BlueTooth on, and with Google Maps on, in hybrid mode, screen set to not sleep, with GPS real time tracking and the compass enabled, while and charging the battery.It was 102 degrees on Saturday.
After that much time under that heavy load, the device was warm, but placing it in my shirt pocket was not uncomfortable.
I even made a phone call within a minute or two of getting out of the car and placed it on my ear and was not at all concerned about the temp of the device.I also played an immersive 3D game the other night from full charge until the battery died (about 4.5 hours) with the iPod running in the background.
My bluetooth headset was on in my pocket, and wifi was enabled.
The device again got warm, but not even as warm as it did in the car.
Far from uncomfortable.
My (now my wife's) 2G gets hotter under those loads.Reports I've heard from people with "pink" phones are people who left it running like this under a pillow, in a bag, outside in the hot summer sun for hours, and other extreme conditions.Quite possibly there's a battery issue and some bad one's floating around.
There's over a million of them out there already.
An issue rate of a few dozen phones per milion is a SMALL issue.
Also, being a LiPo, not a LiIon, though it may get hot, it;s not likely to explode or burn as cascade failure is fare more difficult to achive in LiPo.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095</id>
	<title>Re:Provably False</title>
	<author>Anonymous</author>
	<datestamp>1246445400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>3. Apple cant do no wrong</p></htmltext>
<tokenext>3 .
Apple cant do no wrong</tokentext>
<sentencetext>3.
Apple cant do no wrong</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540025</id>
	<title>A Boon for Paris Hilton</title>
	<author>eBayDoug</author>
	<datestamp>1246444680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>She can have a pink iPhone and say "That's Hot" and not look like a douchebag.</htmltext>
<tokenext>She can have a pink iPhone and say " That 's Hot " and not look like a douchebag .</tokentext>
<sentencetext>She can have a pink iPhone and say "That's Hot" and not look like a douchebag.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28554873</id>
	<title>Re:should have released it in winter</title>
	<author>EricTheO</author>
	<datestamp>1246567500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p><div class="quote"><p>btw apple, black sucks, it absorbes heat in the sun shine.</p></div><p>How often do you leave your phone out in direct sunlight?
And black radiates heat better, so in the shade it will cool down faster.</p></div><p>Black absorbs infared heat better, not radiate it. The radiating material, not it's color, is what makes the difference when you want to cool something. Ever paint your CPU cooler contact plate black before putting ArticSilver on it?</p></div>
	</htmltext>
<tokenext>btw apple , black sucks , it absorbes heat in the sun shine.How often do you leave your phone out in direct sunlight ?
And black radiates heat better , so in the shade it will cool down faster.Black absorbs infared heat better , not radiate it .
The radiating material , not it 's color , is what makes the difference when you want to cool something .
Ever paint your CPU cooler contact plate black before putting ArticSilver on it ?</tokentext>
<sentencetext>btw apple, black sucks, it absorbes heat in the sun shine.How often do you leave your phone out in direct sunlight?
And black radiates heat better, so in the shade it will cool down faster.Black absorbs infared heat better, not radiate it.
The radiating material, not it's color, is what makes the difference when you want to cool something.
Ever paint your CPU cooler contact plate black before putting ArticSilver on it?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541165</id>
	<title>Not just the 3Gs</title>
	<author>Anonymous</author>
	<datestamp>1246457280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I have an iphone 3G and the thing gets incredibly warm if I am using 3G for more than a few minutes.  I've got one of those Agent 18 plastic cases on it and it gets so hot through the case that it makes my hand sweaty.  And no, its not all that pr0n making it so hot, it even does it when I'm on your mom's facebook site =oP</p></htmltext>
<tokenext>I have an iphone 3G and the thing gets incredibly warm if I am using 3G for more than a few minutes .
I 've got one of those Agent 18 plastic cases on it and it gets so hot through the case that it makes my hand sweaty .
And no , its not all that pr0n making it so hot , it even does it when I 'm on your mom 's facebook site = oP</tokentext>
<sentencetext>I have an iphone 3G and the thing gets incredibly warm if I am using 3G for more than a few minutes.
I've got one of those Agent 18 plastic cases on it and it gets so hot through the case that it makes my hand sweaty.
And no, its not all that pr0n making it so hot, it even does it when I'm on your mom's facebook site =oP</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540695</id>
	<title>Re:Provably False</title>
	<author>kannibal\_klown</author>
	<datestamp>1246453620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Eh, no matter what electronic product you have there are going to be batches of bad products.  This batch got a lousy battery, this a bad speaker, another went through a flawed machine for sealing, etc.  They sold a million within the first day or weekend, and how many people are complaining?</p><p>I picked one up (my first iPhone) the other day and haven't had a problem with it.  While I notice the temp increase while playing a game, it's "just" noticable.  Not uncomfortable, not obvious, not "too warm" etc.  I also know a number of people that picked one up and haven't had any problems with them.</p></htmltext>
<tokenext>Eh , no matter what electronic product you have there are going to be batches of bad products .
This batch got a lousy battery , this a bad speaker , another went through a flawed machine for sealing , etc .
They sold a million within the first day or weekend , and how many people are complaining ? I picked one up ( my first iPhone ) the other day and have n't had a problem with it .
While I notice the temp increase while playing a game , it 's " just " noticable .
Not uncomfortable , not obvious , not " too warm " etc .
I also know a number of people that picked one up and have n't had any problems with them .</tokentext>
<sentencetext>Eh, no matter what electronic product you have there are going to be batches of bad products.
This batch got a lousy battery, this a bad speaker, another went through a flawed machine for sealing, etc.
They sold a million within the first day or weekend, and how many people are complaining?I picked one up (my first iPhone) the other day and haven't had a problem with it.
While I notice the temp increase while playing a game, it's "just" noticable.
Not uncomfortable, not obvious, not "too warm" etc.
I also know a number of people that picked one up and haven't had any problems with them.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540931</id>
	<title>Will the next "feature" be removable battery?</title>
	<author>erroneus</author>
	<datestamp>1246455660000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>I sit in awe seeing commercials advertising "Copy and Paste" as if it were some ground breaking new technology wonder if the less educated users have any clue at all.</p><p>I think it has become accepted that it doesn't seem to matter what 3rd world country they buy from, these hungry, over-worked, under-paid people can't seem to build a battery that doesn't eventually turn into an explosive.  So with that in mind, being able to change the battery in the event of need should be fundamental especially in the most expensive of devices.  It has made sense for users to be able to change their batteries, but now is it starting to make sense for Apple?  How many of their phones need this kind of problem before it makes more sense to simply hand the user a new battery to change rather than trading iPhones while repairs are made.</p><p>I've got to say, that portable Apple gear, as cool as it may be, cannot be used in places where it is mission critical.  They don't have the kind of warranty service and support that I have come to expect from technology vendors and frankly, I was shocked when I learned this of Apple the hard way in a world where everyone else offers better service and support.</p></htmltext>
<tokenext>I sit in awe seeing commercials advertising " Copy and Paste " as if it were some ground breaking new technology wonder if the less educated users have any clue at all.I think it has become accepted that it does n't seem to matter what 3rd world country they buy from , these hungry , over-worked , under-paid people ca n't seem to build a battery that does n't eventually turn into an explosive .
So with that in mind , being able to change the battery in the event of need should be fundamental especially in the most expensive of devices .
It has made sense for users to be able to change their batteries , but now is it starting to make sense for Apple ?
How many of their phones need this kind of problem before it makes more sense to simply hand the user a new battery to change rather than trading iPhones while repairs are made.I 've got to say , that portable Apple gear , as cool as it may be , can not be used in places where it is mission critical .
They do n't have the kind of warranty service and support that I have come to expect from technology vendors and frankly , I was shocked when I learned this of Apple the hard way in a world where everyone else offers better service and support .</tokentext>
<sentencetext>I sit in awe seeing commercials advertising "Copy and Paste" as if it were some ground breaking new technology wonder if the less educated users have any clue at all.I think it has become accepted that it doesn't seem to matter what 3rd world country they buy from, these hungry, over-worked, under-paid people can't seem to build a battery that doesn't eventually turn into an explosive.
So with that in mind, being able to change the battery in the event of need should be fundamental especially in the most expensive of devices.
It has made sense for users to be able to change their batteries, but now is it starting to make sense for Apple?
How many of their phones need this kind of problem before it makes more sense to simply hand the user a new battery to change rather than trading iPhones while repairs are made.I've got to say, that portable Apple gear, as cool as it may be, cannot be used in places where it is mission critical.
They don't have the kind of warranty service and support that I have come to expect from technology vendors and frankly, I was shocked when I learned this of Apple the hard way in a world where everyone else offers better service and support.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541513</id>
	<title>New accessory</title>
	<author>FishTankX</author>
	<datestamp>1246459320000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>iFan: Keeping the blistering speed of the 3GS from giving you blisters! Also provides emergency cooling in those tough Iraqi deserts where iPhones are being deployed. Comes with free 'Fanspeed control app'</htmltext>
<tokenext>iFan : Keeping the blistering speed of the 3GS from giving you blisters !
Also provides emergency cooling in those tough Iraqi deserts where iPhones are being deployed .
Comes with free 'Fanspeed control app'</tokentext>
<sentencetext>iFan: Keeping the blistering speed of the 3GS from giving you blisters!
Also provides emergency cooling in those tough Iraqi deserts where iPhones are being deployed.
Comes with free 'Fanspeed control app'</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540035</id>
	<title>Re:Provably False</title>
	<author>Anonymous</author>
	<datestamp>1246444800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Odd. You forgot axiom 3: "teh iPhone overheats and/or discolours"</p><p>Theorem 4, which is a synthesis of axioms 2 and 3, states "teh iPhone is clearly not teh Best Thing Ever".</p><p>Thus postulate 1 is proven false as it contradicts theorem 4.</p><p>HTH<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>Odd .
You forgot axiom 3 : " teh iPhone overheats and/or discolours " Theorem 4 , which is a synthesis of axioms 2 and 3 , states " teh iPhone is clearly not teh Best Thing Ever " .Thus postulate 1 is proven false as it contradicts theorem 4.HTH : )</tokentext>
<sentencetext>Odd.
You forgot axiom 3: "teh iPhone overheats and/or discolours"Theorem 4, which is a synthesis of axioms 2 and 3, states "teh iPhone is clearly not teh Best Thing Ever".Thus postulate 1 is proven false as it contradicts theorem 4.HTH :)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540147</id>
	<title>Re:Obviously</title>
	<author>ascendant</author>
	<datestamp>1246446420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Apologize.</p></htmltext>
<tokenext>Apologize .</tokentext>
<sentencetext>Apologize.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539953</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540211</id>
	<title>Re:Obviously</title>
	<author>Hurricane78</author>
	<datestamp>1246447500000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><a href="http://thebestpageintheuniverse.net/c.cgi?u=iphone" title="thebestpag...iverse.net">Actually, it never was.</a> [thebestpag...iverse.net]</p><p>It's one of those things that are like the hairstyles and clothes of the 80s. We will some day wonder, why people bought them.<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>Actually , it never was .
[ thebestpag...iverse.net ] It 's one of those things that are like the hairstyles and clothes of the 80s .
We will some day wonder , why people bought them .
: )</tokentext>
<sentencetext>Actually, it never was.
[thebestpag...iverse.net]It's one of those things that are like the hairstyles and clothes of the 80s.
We will some day wonder, why people bought them.
:)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539953</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28554611</id>
	<title>Software vs environment</title>
	<author>Anonymous</author>
	<datestamp>1246477980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>My old iPhone started heating a few days ago, when two events took place<br>- summer began<br>- I switched from 2.0 to 3.0<br>So it's a software and/or environment problem. Let's wait for winter to be sure.</p></htmltext>
<tokenext>My old iPhone started heating a few days ago , when two events took place- summer began- I switched from 2.0 to 3.0So it 's a software and/or environment problem .
Let 's wait for winter to be sure .</tokentext>
<sentencetext>My old iPhone started heating a few days ago, when two events took place- summer began- I switched from 2.0 to 3.0So it's a software and/or environment problem.
Let's wait for winter to be sure.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540979</id>
	<title>Re:Obviously</title>
	<author>Anonymous</author>
	<datestamp>1246456020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>We will some day wonder, why that comma is there.<nobr> <wbr></nobr>:)</htmltext>
<tokenext>We will some day wonder , why that comma is there .
: )</tokentext>
<sentencetext>We will some day wonder, why that comma is there.
:)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540211</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543389</id>
	<title>Re:Hmmmm ...</title>
	<author>Tony Hoyle</author>
	<datestamp>1246467120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Indeed. my wife has a unibody macbook pro.  Looks nice, until you remember that as it's one piece of metal it's effectively *all* heatsink.. once it's been on for an hour you can't touch the area around the keyboard without serious risk of burning yourself.  It overheats randomly as well (as do, from a very unscientific straw poll of friends, all the unibody macs).</p></htmltext>
<tokenext>Indeed .
my wife has a unibody macbook pro .
Looks nice , until you remember that as it 's one piece of metal it 's effectively * all * heatsink.. once it 's been on for an hour you ca n't touch the area around the keyboard without serious risk of burning yourself .
It overheats randomly as well ( as do , from a very unscientific straw poll of friends , all the unibody macs ) .</tokentext>
<sentencetext>Indeed.
my wife has a unibody macbook pro.
Looks nice, until you remember that as it's one piece of metal it's effectively *all* heatsink.. once it's been on for an hour you can't touch the area around the keyboard without serious risk of burning yourself.
It overheats randomly as well (as do, from a very unscientific straw poll of friends, all the unibody macs).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540781</id>
	<title>What about the ponies???</title>
	<author>ToreTS</author>
	<datestamp>1246454520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Does it display ponies as well when it glows pink?</htmltext>
<tokenext>Does it display ponies as well when it glows pink ?</tokentext>
<sentencetext>Does it display ponies as well when it glows pink?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541457</id>
	<title>Re:There's definately an issue of some sort</title>
	<author>MrCrassic</author>
	<datestamp>1246458960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That's usually happened to me because a background task would burn up CPU resources. I would get a Task Manager for your iPhone, but you might have to jailbreak it to get it working.</htmltext>
<tokenext>That 's usually happened to me because a background task would burn up CPU resources .
I would get a Task Manager for your iPhone , but you might have to jailbreak it to get it working .</tokentext>
<sentencetext>That's usually happened to me because a background task would burn up CPU resources.
I would get a Task Manager for your iPhone, but you might have to jailbreak it to get it working.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541081</id>
	<title>I don't think that word means what you pink it mns</title>
	<author>Anonymous</author>
	<datestamp>1246456740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Nice headline Eds.  Did you read TFA?  (Sorry, that was a rhetorical question.)</p><p>Or did you bother to consider how hot the casing would have to be to GLOW pink?  (Around 538C, if the case was steel.)</p><p>"Later, the owner discovered that the white backing on the device had turned pink-toned near the spot where the battery is stored, the report said."</p></htmltext>
<tokenext>Nice headline Eds .
Did you read TFA ?
( Sorry , that was a rhetorical question .
) Or did you bother to consider how hot the casing would have to be to GLOW pink ?
( Around 538C , if the case was steel .
) " Later , the owner discovered that the white backing on the device had turned pink-toned near the spot where the battery is stored , the report said .
"</tokentext>
<sentencetext>Nice headline Eds.
Did you read TFA?
(Sorry, that was a rhetorical question.
)Or did you bother to consider how hot the casing would have to be to GLOW pink?
(Around 538C, if the case was steel.
)"Later, the owner discovered that the white backing on the device had turned pink-toned near the spot where the battery is stored, the report said.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28546659</id>
	<title>iPhone Commercial</title>
	<author>atramentum</author>
	<datestamp>1246476660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>(British Accent narrating)
 - Right.  Ok.  Today we'll be testing the new iPhone's durability.
 -<nobr> <wbr></nobr>...In Fire!  (Pulls out flamethrower, iPhone obviously melting, then it explodes)

(British guy drops iPhone into a concrete enclosure)
 - Grenades! (Drops a grenade in with it)

(Scenes begin to switch faster, showing the iPhone blowing up over and over in each scenario)
 - Lasers!
 - Sharks!
 - Sports!
 - Cars!
 - Molten Lava!
 - (Then cuts to a scene where someone is just talking on the phone or using an app - a boring 5 seconds)  Consumers!

 - Judges show their ratings:  10, 8, 9, 8, 1.2 (Germany)</htmltext>
<tokenext>( British Accent narrating ) - Right .
Ok. Today we 'll be testing the new iPhone 's durability .
- ...In Fire !
( Pulls out flamethrower , iPhone obviously melting , then it explodes ) ( British guy drops iPhone into a concrete enclosure ) - Grenades !
( Drops a grenade in with it ) ( Scenes begin to switch faster , showing the iPhone blowing up over and over in each scenario ) - Lasers !
- Sharks !
- Sports !
- Cars !
- Molten Lava !
- ( Then cuts to a scene where someone is just talking on the phone or using an app - a boring 5 seconds ) Consumers !
- Judges show their ratings : 10 , 8 , 9 , 8 , 1.2 ( Germany )</tokentext>
<sentencetext>(British Accent narrating)
 - Right.
Ok.  Today we'll be testing the new iPhone's durability.
- ...In Fire!
(Pulls out flamethrower, iPhone obviously melting, then it explodes)

(British guy drops iPhone into a concrete enclosure)
 - Grenades!
(Drops a grenade in with it)

(Scenes begin to switch faster, showing the iPhone blowing up over and over in each scenario)
 - Lasers!
- Sharks!
- Sports!
- Cars!
- Molten Lava!
- (Then cuts to a scene where someone is just talking on the phone or using an app - a boring 5 seconds)  Consumers!
- Judges show their ratings:  10, 8, 9, 8, 1.2 (Germany)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540631</id>
	<title>Re:Hmmmm ...</title>
	<author>MemoryDragon</author>
	<datestamp>1246452780000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>... testing anyone?</p><p>It seems Apple has a hard time learning that electronics cause heat and that this heat needs to be led away from the device.</p><p>I can remember several cases ( MacBooks, iMacs, what have you) where they've had overheating issues<nobr> <wbr></nobr>... pretty sloppy engineering if you ask me.</p></div><p>Well the first batch of Macbook Airs also had severe overheating issues, mostly crawling up in summer, Apple never fixed it, well they did, the fix was to sell a second generation after a few months where the heating issues occur less frequently!<br>So the list of Apples thermal design failures is pretty long starting btw. with the famous Apple 3 whichs thermal problems back then was Steve Jobs personal fault, because he refused to listen to his engineers and demanded a fanless machine!</p></div>
	</htmltext>
<tokenext>... testing anyone ? It seems Apple has a hard time learning that electronics cause heat and that this heat needs to be led away from the device.I can remember several cases ( MacBooks , iMacs , what have you ) where they 've had overheating issues ... pretty sloppy engineering if you ask me.Well the first batch of Macbook Airs also had severe overheating issues , mostly crawling up in summer , Apple never fixed it , well they did , the fix was to sell a second generation after a few months where the heating issues occur less frequently ! So the list of Apples thermal design failures is pretty long starting btw .
with the famous Apple 3 whichs thermal problems back then was Steve Jobs personal fault , because he refused to listen to his engineers and demanded a fanless machine !</tokentext>
<sentencetext>... testing anyone?It seems Apple has a hard time learning that electronics cause heat and that this heat needs to be led away from the device.I can remember several cases ( MacBooks, iMacs, what have you) where they've had overheating issues ... pretty sloppy engineering if you ask me.Well the first batch of Macbook Airs also had severe overheating issues, mostly crawling up in summer, Apple never fixed it, well they did, the fix was to sell a second generation after a few months where the heating issues occur less frequently!So the list of Apples thermal design failures is pretty long starting btw.
with the famous Apple 3 whichs thermal problems back then was Steve Jobs personal fault, because he refused to listen to his engineers and demanded a fanless machine!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540153</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>patch0</author>
	<datestamp>1246446420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>My iPhone 3GS definitely heats up when using GPS, noticed it this weekend while lost on the way to a wedding...</htmltext>
<tokenext>My iPhone 3GS definitely heats up when using GPS , noticed it this weekend while lost on the way to a wedding.. .</tokentext>
<sentencetext>My iPhone 3GS definitely heats up when using GPS, noticed it this weekend while lost on the way to a wedding...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542035</id>
	<title>Poor Battery Life for 3G S</title>
	<author>forrie</author>
	<datestamp>1246461960000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>The battery life on my new 3G S has been terrible--worse than my experience with the first generation device, where I had to replace the phone three times before I got one that worked properly.</p><p>I recently went into the Apple Store at the Burlington Mall, Burlington, MA, to see the Genius Bar about this battery problem.   I was (and wasn't) surprised to have them offload the problem to me, how I was pushing/pulling data.  They made a quick adjustment and told me to "come back if you have more problems".  Though, intuitively, I wonder if this is what they're instructed to do.</p><p>The FAQ on apple.com even suggests that you just turn off 3G and this-and-that.  What would be the point of having the phone if you have to turn off all the useful features?</p><p>I say that because I already experimented with different settings and did not see any improved battery life.  I explained this very clearly.</p><p>What's even more concerning is when I made the initial call to Apple Support about the issue, the representative said that the battery performance was not covered under any warranty and that, even though I just bought the darned thing, I'd have to pay 79.00 to have it sent in and repaired, during which time I would be without a phone.</p><p>Ummm.... NO.</p><p>I made it very clear I would get an attorney and make them replace it.   I was then placed on hold 2 different times, after which I was passed to a different representative who was more friendly and scheduled a Genius Bar appointment (per the above).</p><p>In summary:  be prepared to invest extra time with this device if you're having any issues with the iPhone.</p><p>Caveat Emptor.</p></htmltext>
<tokenext>The battery life on my new 3G S has been terrible--worse than my experience with the first generation device , where I had to replace the phone three times before I got one that worked properly.I recently went into the Apple Store at the Burlington Mall , Burlington , MA , to see the Genius Bar about this battery problem .
I was ( and was n't ) surprised to have them offload the problem to me , how I was pushing/pulling data .
They made a quick adjustment and told me to " come back if you have more problems " .
Though , intuitively , I wonder if this is what they 're instructed to do.The FAQ on apple.com even suggests that you just turn off 3G and this-and-that .
What would be the point of having the phone if you have to turn off all the useful features ? I say that because I already experimented with different settings and did not see any improved battery life .
I explained this very clearly.What 's even more concerning is when I made the initial call to Apple Support about the issue , the representative said that the battery performance was not covered under any warranty and that , even though I just bought the darned thing , I 'd have to pay 79.00 to have it sent in and repaired , during which time I would be without a phone.Ummm.... NO.I made it very clear I would get an attorney and make them replace it .
I was then placed on hold 2 different times , after which I was passed to a different representative who was more friendly and scheduled a Genius Bar appointment ( per the above ) .In summary : be prepared to invest extra time with this device if you 're having any issues with the iPhone.Caveat Emptor .</tokentext>
<sentencetext>The battery life on my new 3G S has been terrible--worse than my experience with the first generation device, where I had to replace the phone three times before I got one that worked properly.I recently went into the Apple Store at the Burlington Mall, Burlington, MA, to see the Genius Bar about this battery problem.
I was (and wasn't) surprised to have them offload the problem to me, how I was pushing/pulling data.
They made a quick adjustment and told me to "come back if you have more problems".
Though, intuitively, I wonder if this is what they're instructed to do.The FAQ on apple.com even suggests that you just turn off 3G and this-and-that.
What would be the point of having the phone if you have to turn off all the useful features?I say that because I already experimented with different settings and did not see any improved battery life.
I explained this very clearly.What's even more concerning is when I made the initial call to Apple Support about the issue, the representative said that the battery performance was not covered under any warranty and that, even though I just bought the darned thing, I'd have to pay 79.00 to have it sent in and repaired, during which time I would be without a phone.Ummm.... NO.I made it very clear I would get an attorney and make them replace it.
I was then placed on hold 2 different times, after which I was passed to a different representative who was more friendly and scheduled a Genius Bar appointment (per the above).In summary:  be prepared to invest extra time with this device if you're having any issues with the iPhone.Caveat Emptor.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540971</id>
	<title>Unfortunately not uncommon</title>
	<author>Thumper\_SVX</author>
	<datestamp>1246455960000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>A lot of modern smartphones suffer these exact problems because of the push for more and more features. Basically, a feature add will add power draw, and will also tend to add CPU usage as the applications to run these new features crank up the utilization.</p><p>I don't have an iPhone... I have too much invested in the Windows Mobile platform dating back almost a decade to really migrate at this point (plus, I write some of my own little applets and upload to my phone all the time... can't do that with the iPhone without jailbreaking). However, I DO currently have an HTC Touch Pro, my previous device being an HTC Tilt. The majority of the time, the phone is excellent; it runs cool, it does exactly what I want when I want and doesn't have too many horribly nefarious bugs, though much of that probably has to do with the custom ROM I flashed to it. But if I start activating devices such as GPS, WiFi and other features like that it sometimes shocks me how hot the phone will get. Particularly if I'm using, say Google Maps as a GPS application.</p><p>Google Maps will turn on my GPS antenna, and then will start pulling data using my 3G connection (I have traffic turned on, too). Both of these add significant power draw and heat generation, and the GM app itself will tend to crank up the CPU. Because of the draw, and because most of the time I only use these functions together in the car I plug my phone into my car charger. But you know what? Then the screen stays on... more heat. Literally, my phone can get to the point where I'd be really uncomfortable holding that thing up to my ear... thank  for Bluetooth headsets! Even if I skip Google Maps and use TomTom Mobile, it forces the screen to stay on so again the battery life goes into the toilet and I end up with a rather nice hand warmer on cold days.</p><p>Does it concern me? A little. I get concerned that this heat is going to shorten the life of my device significantly, but on the flip side I'm enough of a phone geek I tend to trade out my phones every couple of years anyway to get the "latest and greatest". Also, the Touch Pro has not shown any significant signs of being a problem child... it all works.</p><p>The Touch Pro has been pretty well engineered by HTC; they design a LOT of handsets for a lot of different markets. As a result, their experience in engineering these kind of form factors is really good. Their smartphone devices will dissipate heat quite well, and be none the worse for wear. My old Tilt still works as well as the day I bought it ~3 or 4 years ago, except that it's been dropped quite a number of times. Apple's problem is that they really don't have that experience, and as such they DO make mistakes with heat dissipation and things like that in a small form factor like the iPhone. They've done it before; their focus on aesthetics often takes over from the engineering portion... and while I know Apple has some phenomenal engineers, there's no replacement for experience. I think the engineering margins they built into the 3GS were just too tight for such a large CPU bump and general hardware bump. Everyone loves the fact that Apple used the same case (almost) for the 3GS... which is great for all those dock-equipped things that were designed for the 3G... but when you make such a significant jump from the old architecture to the new, something has to give if the margins for error were not factored correctly.</p><p>I suspect that Apple will provide a fix soon that will underclock the Cortex A8 core in the 3GS to eliminate some of that heat. Thankfully that's an easy solution until the hardware is reengineered a little. It should be possible to do that by maybe 10\% and the average user will never notice the difference. If they're truly running it at 600Mhz, then the A8 provides a nice little mechanism to drop back to 500Mhz, or further. If they just provide a software limit so that the CPU doesn't crank up to a higher rate during high utilization, then it should take care of the problem. Yes, I have a Beagleboard which runs almost the same hardware (thou</p></htmltext>
<tokenext>A lot of modern smartphones suffer these exact problems because of the push for more and more features .
Basically , a feature add will add power draw , and will also tend to add CPU usage as the applications to run these new features crank up the utilization.I do n't have an iPhone... I have too much invested in the Windows Mobile platform dating back almost a decade to really migrate at this point ( plus , I write some of my own little applets and upload to my phone all the time... ca n't do that with the iPhone without jailbreaking ) .
However , I DO currently have an HTC Touch Pro , my previous device being an HTC Tilt .
The majority of the time , the phone is excellent ; it runs cool , it does exactly what I want when I want and does n't have too many horribly nefarious bugs , though much of that probably has to do with the custom ROM I flashed to it .
But if I start activating devices such as GPS , WiFi and other features like that it sometimes shocks me how hot the phone will get .
Particularly if I 'm using , say Google Maps as a GPS application.Google Maps will turn on my GPS antenna , and then will start pulling data using my 3G connection ( I have traffic turned on , too ) .
Both of these add significant power draw and heat generation , and the GM app itself will tend to crank up the CPU .
Because of the draw , and because most of the time I only use these functions together in the car I plug my phone into my car charger .
But you know what ?
Then the screen stays on... more heat .
Literally , my phone can get to the point where I 'd be really uncomfortable holding that thing up to my ear... thank for Bluetooth headsets !
Even if I skip Google Maps and use TomTom Mobile , it forces the screen to stay on so again the battery life goes into the toilet and I end up with a rather nice hand warmer on cold days.Does it concern me ?
A little .
I get concerned that this heat is going to shorten the life of my device significantly , but on the flip side I 'm enough of a phone geek I tend to trade out my phones every couple of years anyway to get the " latest and greatest " .
Also , the Touch Pro has not shown any significant signs of being a problem child... it all works.The Touch Pro has been pretty well engineered by HTC ; they design a LOT of handsets for a lot of different markets .
As a result , their experience in engineering these kind of form factors is really good .
Their smartphone devices will dissipate heat quite well , and be none the worse for wear .
My old Tilt still works as well as the day I bought it ~ 3 or 4 years ago , except that it 's been dropped quite a number of times .
Apple 's problem is that they really do n't have that experience , and as such they DO make mistakes with heat dissipation and things like that in a small form factor like the iPhone .
They 've done it before ; their focus on aesthetics often takes over from the engineering portion... and while I know Apple has some phenomenal engineers , there 's no replacement for experience .
I think the engineering margins they built into the 3GS were just too tight for such a large CPU bump and general hardware bump .
Everyone loves the fact that Apple used the same case ( almost ) for the 3GS... which is great for all those dock-equipped things that were designed for the 3G... but when you make such a significant jump from the old architecture to the new , something has to give if the margins for error were not factored correctly.I suspect that Apple will provide a fix soon that will underclock the Cortex A8 core in the 3GS to eliminate some of that heat .
Thankfully that 's an easy solution until the hardware is reengineered a little .
It should be possible to do that by maybe 10 \ % and the average user will never notice the difference .
If they 're truly running it at 600Mhz , then the A8 provides a nice little mechanism to drop back to 500Mhz , or further .
If they just provide a software limit so that the CPU does n't crank up to a higher rate during high utilization , then it should take care of the problem .
Yes , I have a Beagleboard which runs almost the same hardware ( thou</tokentext>
<sentencetext>A lot of modern smartphones suffer these exact problems because of the push for more and more features.
Basically, a feature add will add power draw, and will also tend to add CPU usage as the applications to run these new features crank up the utilization.I don't have an iPhone... I have too much invested in the Windows Mobile platform dating back almost a decade to really migrate at this point (plus, I write some of my own little applets and upload to my phone all the time... can't do that with the iPhone without jailbreaking).
However, I DO currently have an HTC Touch Pro, my previous device being an HTC Tilt.
The majority of the time, the phone is excellent; it runs cool, it does exactly what I want when I want and doesn't have too many horribly nefarious bugs, though much of that probably has to do with the custom ROM I flashed to it.
But if I start activating devices such as GPS, WiFi and other features like that it sometimes shocks me how hot the phone will get.
Particularly if I'm using, say Google Maps as a GPS application.Google Maps will turn on my GPS antenna, and then will start pulling data using my 3G connection (I have traffic turned on, too).
Both of these add significant power draw and heat generation, and the GM app itself will tend to crank up the CPU.
Because of the draw, and because most of the time I only use these functions together in the car I plug my phone into my car charger.
But you know what?
Then the screen stays on... more heat.
Literally, my phone can get to the point where I'd be really uncomfortable holding that thing up to my ear... thank  for Bluetooth headsets!
Even if I skip Google Maps and use TomTom Mobile, it forces the screen to stay on so again the battery life goes into the toilet and I end up with a rather nice hand warmer on cold days.Does it concern me?
A little.
I get concerned that this heat is going to shorten the life of my device significantly, but on the flip side I'm enough of a phone geek I tend to trade out my phones every couple of years anyway to get the "latest and greatest".
Also, the Touch Pro has not shown any significant signs of being a problem child... it all works.The Touch Pro has been pretty well engineered by HTC; they design a LOT of handsets for a lot of different markets.
As a result, their experience in engineering these kind of form factors is really good.
Their smartphone devices will dissipate heat quite well, and be none the worse for wear.
My old Tilt still works as well as the day I bought it ~3 or 4 years ago, except that it's been dropped quite a number of times.
Apple's problem is that they really don't have that experience, and as such they DO make mistakes with heat dissipation and things like that in a small form factor like the iPhone.
They've done it before; their focus on aesthetics often takes over from the engineering portion... and while I know Apple has some phenomenal engineers, there's no replacement for experience.
I think the engineering margins they built into the 3GS were just too tight for such a large CPU bump and general hardware bump.
Everyone loves the fact that Apple used the same case (almost) for the 3GS... which is great for all those dock-equipped things that were designed for the 3G... but when you make such a significant jump from the old architecture to the new, something has to give if the margins for error were not factored correctly.I suspect that Apple will provide a fix soon that will underclock the Cortex A8 core in the 3GS to eliminate some of that heat.
Thankfully that's an easy solution until the hardware is reengineered a little.
It should be possible to do that by maybe 10\% and the average user will never notice the difference.
If they're truly running it at 600Mhz, then the A8 provides a nice little mechanism to drop back to 500Mhz, or further.
If they just provide a software limit so that the CPU doesn't crank up to a higher rate during high utilization, then it should take care of the problem.
Yes, I have a Beagleboard which runs almost the same hardware (thou</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543419</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>IorDMUX</author>
	<datestamp>1246467240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I work for the company (Qualcomm) that made *most* of the chips for the G1.  I say "most" because HTC decided to go with their own homegrown power management solution, rather than the one we had prepared for them.  The result?  Exactly what you've been talking about.<br> <br>With any luck, they'll come back to us (I'm on the power management team) for the<nobr> <wbr></nobr>... uh... G2?<nobr> <wbr></nobr>... and there will be an Android phone that is fast *and* efficient.</htmltext>
<tokenext>I work for the company ( Qualcomm ) that made * most * of the chips for the G1 .
I say " most " because HTC decided to go with their own homegrown power management solution , rather than the one we had prepared for them .
The result ?
Exactly what you 've been talking about .
With any luck , they 'll come back to us ( I 'm on the power management team ) for the ... uh... G2 ?
... and there will be an Android phone that is fast * and * efficient .</tokentext>
<sentencetext>I work for the company (Qualcomm) that made *most* of the chips for the G1.
I say "most" because HTC decided to go with their own homegrown power management solution, rather than the one we had prepared for them.
The result?
Exactly what you've been talking about.
With any luck, they'll come back to us (I'm on the power management team) for the ... uh... G2?
... and there will be an Android phone that is fast *and* efficient.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540141</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541041</id>
	<title>Early adopters..</title>
	<author>asdf7890</author>
	<datestamp>1246456440000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Just goes to show you shouldn't be the first to buy any new gadget.</p><p>Early adopters always get burnt in some way. It is just more literal in this case.</p></htmltext>
<tokenext>Just goes to show you should n't be the first to buy any new gadget.Early adopters always get burnt in some way .
It is just more literal in this case .</tokentext>
<sentencetext>Just goes to show you shouldn't be the first to buy any new gadget.Early adopters always get burnt in some way.
It is just more literal in this case.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541147</id>
	<title>It warms my hearth ...</title>
	<author>Anonymous</author>
	<datestamp>1246457100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Nothing warms the hearth of true Apple fanboy, as does new [overheating] iPhone.</p></htmltext>
<tokenext>Nothing warms the hearth of true Apple fanboy , as does new [ overheating ] iPhone .</tokentext>
<sentencetext>Nothing warms the hearth of true Apple fanboy, as does new [overheating] iPhone.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539871</id>
	<title>Does this prove it ?</title>
	<author>Anonymous</author>
	<datestamp>1246442640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>An iPhone is heat is gay ?</p></htmltext>
<tokenext>An iPhone is heat is gay ?</tokentext>
<sentencetext>An iPhone is heat is gay ?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28555715</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>superposed</author>
	<datestamp>1246536060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>My Motorola krzr k1m (verizon) used to have great battery life, except when running GPS with turn-by-turn navigation (i.e., continuous update of my GPS position). Then a new, fully-charged battery would run down within an hour, and the phone would get noticeably warm. Eventually I started using the navigator function to plan out the next few steps of my trip, then turned it off for a while, then repeated once I got closer to my destination. <br>
<br>
Even with such efforts, GPS seemed to kill batteries quickly -- i.e., the battery physically expanded, and its recharge capacity dropped precipitously after a few months. Lithium-ion batteries <a href="http://www.batteryuniversity.com/parttwo-34.htm" title="batteryuniversity.com">don't like to run hot</a> [batteryuniversity.com], so maybe that was a factor.<br>
<br>
I was hoping that the 3G S had avoided these problems, but maybe they haven't...</htmltext>
<tokenext>My Motorola krzr k1m ( verizon ) used to have great battery life , except when running GPS with turn-by-turn navigation ( i.e. , continuous update of my GPS position ) .
Then a new , fully-charged battery would run down within an hour , and the phone would get noticeably warm .
Eventually I started using the navigator function to plan out the next few steps of my trip , then turned it off for a while , then repeated once I got closer to my destination .
Even with such efforts , GPS seemed to kill batteries quickly -- i.e. , the battery physically expanded , and its recharge capacity dropped precipitously after a few months .
Lithium-ion batteries do n't like to run hot [ batteryuniversity.com ] , so maybe that was a factor .
I was hoping that the 3G S had avoided these problems , but maybe they have n't.. .</tokentext>
<sentencetext>My Motorola krzr k1m (verizon) used to have great battery life, except when running GPS with turn-by-turn navigation (i.e., continuous update of my GPS position).
Then a new, fully-charged battery would run down within an hour, and the phone would get noticeably warm.
Eventually I started using the navigator function to plan out the next few steps of my trip, then turned it off for a while, then repeated once I got closer to my destination.
Even with such efforts, GPS seemed to kill batteries quickly -- i.e., the battery physically expanded, and its recharge capacity dropped precipitously after a few months.
Lithium-ion batteries don't like to run hot [batteryuniversity.com], so maybe that was a factor.
I was hoping that the 3G S had avoided these problems, but maybe they haven't...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541509</id>
	<title>It's not a bug, it's a feature</title>
	<author>elrous0</author>
	<datestamp>1246459320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's just a test run of their soon-to-be-released iSpaceheater app.</htmltext>
<tokenext>It 's just a test run of their soon-to-be-released iSpaceheater app .</tokentext>
<sentencetext>It's just a test run of their soon-to-be-released iSpaceheater app.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543247</id>
	<title>Re:Hmmmm ...</title>
	<author>leptons</author>
	<datestamp>1246466820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>No, it is not all hardware manufacturers. It is specifically Apple that has chosen form over function, again and again and again.  Apple and their fanboys are addicted to aesthetics, they are like the poodle of the electronics industry - bred to look nice but under the hood they are sickly animals.

  If they had made the iPhone a few millimeters larger to allow for proper cooling, would it really be that much worse for their users? No.  But they chose to shave every last bit off the case to make it as thin as possible and in the process they sacrifice the ability to correctly cool the parts they crammed into the case.  Apple is likely to get burned by their design fetish again, but they don't care as long as it doesn't bring them into the red.</htmltext>
<tokenext>No , it is not all hardware manufacturers .
It is specifically Apple that has chosen form over function , again and again and again .
Apple and their fanboys are addicted to aesthetics , they are like the poodle of the electronics industry - bred to look nice but under the hood they are sickly animals .
If they had made the iPhone a few millimeters larger to allow for proper cooling , would it really be that much worse for their users ?
No. But they chose to shave every last bit off the case to make it as thin as possible and in the process they sacrifice the ability to correctly cool the parts they crammed into the case .
Apple is likely to get burned by their design fetish again , but they do n't care as long as it does n't bring them into the red .</tokentext>
<sentencetext>No, it is not all hardware manufacturers.
It is specifically Apple that has chosen form over function, again and again and again.
Apple and their fanboys are addicted to aesthetics, they are like the poodle of the electronics industry - bred to look nice but under the hood they are sickly animals.
If they had made the iPhone a few millimeters larger to allow for proper cooling, would it really be that much worse for their users?
No.  But they chose to shave every last bit off the case to make it as thin as possible and in the process they sacrifice the ability to correctly cool the parts they crammed into the case.
Apple is likely to get burned by their design fetish again, but they don't care as long as it doesn't bring them into the red.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545445</id>
	<title>Re:Hmmmm ...</title>
	<author>prockcore</author>
	<datestamp>1246473120000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>Yeah, especially since Apple has been making the same mistake for almost 30 years now.</p><blockquote><div><p>Steve Jobs' insistence that the Apple III be fanless, coupled with the cramped aluminum chassis designed to reduce radio-frequency emissions without regard to the demands of the electrical circuitry was a recipe for disaster. As the computer was used, its chips got hot, expanded slightly, and slowly worked their way out of their sockets, at which point the computer simply died. Apple's solution was to recommend lifting the front of the computer six inches off the desktop, then letting it drop with the hope that the chips would reseat themselves.</p></div></blockquote><p><a href="http://www.vectronicsappleworld.com/appleii/appleiii.html" title="vectronicsappleworld.com">http://www.vectronicsappleworld.com/appleii/appleiii.html</a> [vectronicsappleworld.com]</p></div>
	</htmltext>
<tokenext>Yeah , especially since Apple has been making the same mistake for almost 30 years now.Steve Jobs ' insistence that the Apple III be fanless , coupled with the cramped aluminum chassis designed to reduce radio-frequency emissions without regard to the demands of the electrical circuitry was a recipe for disaster .
As the computer was used , its chips got hot , expanded slightly , and slowly worked their way out of their sockets , at which point the computer simply died .
Apple 's solution was to recommend lifting the front of the computer six inches off the desktop , then letting it drop with the hope that the chips would reseat themselves.http : //www.vectronicsappleworld.com/appleii/appleiii.html [ vectronicsappleworld.com ]</tokentext>
<sentencetext>Yeah, especially since Apple has been making the same mistake for almost 30 years now.Steve Jobs' insistence that the Apple III be fanless, coupled with the cramped aluminum chassis designed to reduce radio-frequency emissions without regard to the demands of the electrical circuitry was a recipe for disaster.
As the computer was used, its chips got hot, expanded slightly, and slowly worked their way out of their sockets, at which point the computer simply died.
Apple's solution was to recommend lifting the front of the computer six inches off the desktop, then letting it drop with the hope that the chips would reseat themselves.http://www.vectronicsappleworld.com/appleii/appleiii.html [vectronicsappleworld.com]
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541519</id>
	<title>Re:saw this on El Reg yesterday</title>
	<author>Colonel Korn</author>
	<datestamp>1246459380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Sounds like a fairly straight forward case of there being a few dodgy units out there to me</p></div><p>It's not just faulty new hardware - all versions of iphone and touches updated to the new OS version are suffering from the problem.  It may be that certain applications or combinations of factors cause the CPU to get into an infinite loop in the new OS.  It's probably fixable in software once they find the problem.  I'm surprised that they haven't found it yet, though, considering the commonality of this problem.</p></div>
	</htmltext>
<tokenext>Sounds like a fairly straight forward case of there being a few dodgy units out there to meIt 's not just faulty new hardware - all versions of iphone and touches updated to the new OS version are suffering from the problem .
It may be that certain applications or combinations of factors cause the CPU to get into an infinite loop in the new OS .
It 's probably fixable in software once they find the problem .
I 'm surprised that they have n't found it yet , though , considering the commonality of this problem .</tokentext>
<sentencetext>Sounds like a fairly straight forward case of there being a few dodgy units out there to meIt's not just faulty new hardware - all versions of iphone and touches updated to the new OS version are suffering from the problem.
It may be that certain applications or combinations of factors cause the CPU to get into an infinite loop in the new OS.
It's probably fixable in software once they find the problem.
I'm surprised that they haven't found it yet, though, considering the commonality of this problem.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540033</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540831</id>
	<title>pink belly!</title>
	<author>yaksha</author>
	<datestamp>1246454880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Now bullies can play pink belly with other's iPhones!</htmltext>
<tokenext>Now bullies can play pink belly with other 's iPhones !</tokentext>
<sentencetext>Now bullies can play pink belly with other's iPhones!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542235</id>
	<title>Re:Unfortunately not uncommon</title>
	<author>dunkelfalke</author>
	<datestamp>1246462680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You should try IGO for turn to turn navigation. It has got backlight profiles like backlight always on, same settings as standard windows mobile and battery saving mode (backlight goes on for a couple of seconds the same time the next announcement comes).</p></htmltext>
<tokenext>You should try IGO for turn to turn navigation .
It has got backlight profiles like backlight always on , same settings as standard windows mobile and battery saving mode ( backlight goes on for a couple of seconds the same time the next announcement comes ) .</tokentext>
<sentencetext>You should try IGO for turn to turn navigation.
It has got backlight profiles like backlight always on, same settings as standard windows mobile and battery saving mode (backlight goes on for a couple of seconds the same time the next announcement comes).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540971</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543931</id>
	<title>Re:Battery Concerns</title>
	<author>slyn</author>
	<datestamp>1246468740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you upgraded from the first iPhone to the 3GS you are going to see a battery life loss because of the 3G.</p><p>See: <a href="http://www.anandtech.com/gadgets/showdoc.aspx?i=3353" title="anandtech.com">http://www.anandtech.com/gadgets/showdoc.aspx?i=3353</a> [anandtech.com]</p><p>Those results are from nearly a year ago so battery life will have likely improved some from the 2.0 -&gt; 2.1 -&gt; 2.2 -&gt; 2.3 -&gt; 3.0 OS updates, but it gives you an approximation for the difference between the edge vs 3g power consumption.</p></htmltext>
<tokenext>If you upgraded from the first iPhone to the 3GS you are going to see a battery life loss because of the 3G.See : http : //www.anandtech.com/gadgets/showdoc.aspx ? i = 3353 [ anandtech.com ] Those results are from nearly a year ago so battery life will have likely improved some from the 2.0 - &gt; 2.1 - &gt; 2.2 - &gt; 2.3 - &gt; 3.0 OS updates , but it gives you an approximation for the difference between the edge vs 3g power consumption .</tokentext>
<sentencetext>If you upgraded from the first iPhone to the 3GS you are going to see a battery life loss because of the 3G.See: http://www.anandtech.com/gadgets/showdoc.aspx?i=3353 [anandtech.com]Those results are from nearly a year ago so battery life will have likely improved some from the 2.0 -&gt; 2.1 -&gt; 2.2 -&gt; 2.3 -&gt; 3.0 OS updates, but it gives you an approximation for the difference between the edge vs 3g power consumption.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580509</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>Swift2001</author>
	<datestamp>1246726080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>About three months after I got my iPhone 3G, I started having overheating problems and the battery was giving out after five or six hours. The software update took part of it. The other part was that I stupidly named my ad hoc wifi network at home the same as my network at work. Duh. The name was recognized, but the MAC address was different, so the phone had kept on hammering on that address over and over without success. I turned off wifi, temporarily, and my battery life was back to normal. Then I figured out my stupid mistake with the wifi, wiped out and redid the network connections, and then I had network access AND normal battery life.</p><p>As far as I can tell from my friends, the overheating may be a flaw in some units, or the product of silly mistakes like mine. Of course, the unquestionably ethical, non-tabloid Fleet Street bull**** Telegraph wouldn't sensationalize anything. Would they?</p></htmltext>
<tokenext>About three months after I got my iPhone 3G , I started having overheating problems and the battery was giving out after five or six hours .
The software update took part of it .
The other part was that I stupidly named my ad hoc wifi network at home the same as my network at work .
Duh. The name was recognized , but the MAC address was different , so the phone had kept on hammering on that address over and over without success .
I turned off wifi , temporarily , and my battery life was back to normal .
Then I figured out my stupid mistake with the wifi , wiped out and redid the network connections , and then I had network access AND normal battery life.As far as I can tell from my friends , the overheating may be a flaw in some units , or the product of silly mistakes like mine .
Of course , the unquestionably ethical , non-tabloid Fleet Street bull * * * * Telegraph would n't sensationalize anything .
Would they ?</tokentext>
<sentencetext>About three months after I got my iPhone 3G, I started having overheating problems and the battery was giving out after five or six hours.
The software update took part of it.
The other part was that I stupidly named my ad hoc wifi network at home the same as my network at work.
Duh. The name was recognized, but the MAC address was different, so the phone had kept on hammering on that address over and over without success.
I turned off wifi, temporarily, and my battery life was back to normal.
Then I figured out my stupid mistake with the wifi, wiped out and redid the network connections, and then I had network access AND normal battery life.As far as I can tell from my friends, the overheating may be a flaw in some units, or the product of silly mistakes like mine.
Of course, the unquestionably ethical, non-tabloid Fleet Street bull**** Telegraph wouldn't sensationalize anything.
Would they?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541321</id>
	<title>What can I say?</title>
	<author>dasunst3r</author>
	<datestamp>1246458240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well, what can I say?  The iPhone is one smokin' hot gadget out there!</p></htmltext>
<tokenext>Well , what can I say ?
The iPhone is one smokin ' hot gadget out there !</tokentext>
<sentencetext>Well, what can I say?
The iPhone is one smokin' hot gadget out there!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28547383</id>
	<title>Re:should have released it in winter</title>
	<author>Anonymous</author>
	<datestamp>1246479120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Black only radiates better in optical wavebands.  There are other things that matter more in the IR wavebands the phone uses to cool down</p></htmltext>
<tokenext>Black only radiates better in optical wavebands .
There are other things that matter more in the IR wavebands the phone uses to cool down</tokentext>
<sentencetext>Black only radiates better in optical wavebands.
There are other things that matter more in the IR wavebands the phone uses to cool down</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913</id>
	<title>Battery Concerns</title>
	<author>alistair</author>
	<datestamp>1246443120000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Having just upgraded from the first iPhone to the 3GS I have to say I am disappointed with the battery life on the new handset, it's certainly not the improvement I was expecting from reviews. With Wi-Fi and location services turned off and very light usage I can get just about 2 days out of it, normal use sees it being recharged every night which is inferior to the old model. I was contemplating returning it to O2 but before I did that I wanted to know if there are any standard tests to see if my battery is that much worse than normal, e.g. the phone plays a movie for 5.5 hours at 75\% brightness or play music through headphones for 9 hours from full charge etc. Any thoughts? Reviews also seemed to suggest there was a better battery meter in this model but I haven't seen it, 20\% charge remaining still seems to mean run for a recarger, not you have 20\% of the usage time you would get from a full charge left.</p></htmltext>
<tokenext>Having just upgraded from the first iPhone to the 3GS I have to say I am disappointed with the battery life on the new handset , it 's certainly not the improvement I was expecting from reviews .
With Wi-Fi and location services turned off and very light usage I can get just about 2 days out of it , normal use sees it being recharged every night which is inferior to the old model .
I was contemplating returning it to O2 but before I did that I wanted to know if there are any standard tests to see if my battery is that much worse than normal , e.g .
the phone plays a movie for 5.5 hours at 75 \ % brightness or play music through headphones for 9 hours from full charge etc .
Any thoughts ?
Reviews also seemed to suggest there was a better battery meter in this model but I have n't seen it , 20 \ % charge remaining still seems to mean run for a recarger , not you have 20 \ % of the usage time you would get from a full charge left .</tokentext>
<sentencetext>Having just upgraded from the first iPhone to the 3GS I have to say I am disappointed with the battery life on the new handset, it's certainly not the improvement I was expecting from reviews.
With Wi-Fi and location services turned off and very light usage I can get just about 2 days out of it, normal use sees it being recharged every night which is inferior to the old model.
I was contemplating returning it to O2 but before I did that I wanted to know if there are any standard tests to see if my battery is that much worse than normal, e.g.
the phone plays a movie for 5.5 hours at 75\% brightness or play music through headphones for 9 hours from full charge etc.
Any thoughts?
Reviews also seemed to suggest there was a better battery meter in this model but I haven't seen it, 20\% charge remaining still seems to mean run for a recarger, not you have 20\% of the usage time you would get from a full charge left.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28546705</id>
	<title>My bet</title>
	<author>Ingcuervo</author>
	<datestamp>1246476780000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext>this is just a commercial strategy from apple, just hear it:

my new IPHONE is so damn hot!!!!

my iphone is on fire should be the next step!</htmltext>
<tokenext>this is just a commercial strategy from apple , just hear it : my new IPHONE is so damn hot ! ! ! !
my iphone is on fire should be the next step !</tokentext>
<sentencetext>this is just a commercial strategy from apple, just hear it:

my new IPHONE is so damn hot!!!!
my iphone is on fire should be the next step!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821</id>
	<title>Provably False</title>
	<author>Anonymous</author>
	<datestamp>1246442220000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Simple logic shows these claims to be provably false:</p><p>1. 'teh iPhone' is 'teh Best Thing Ever'</p><p>2. 'teh Best Thing Ever' obviously doesn't overheat and discolour</p><p>Therefore</p><p>'teh iPhone' doesn't overheat and discolour.</p><p>QED</p></htmltext>
<tokenext>Simple logic shows these claims to be provably false : 1 .
'teh iPhone ' is 'teh Best Thing Ever'2 .
'teh Best Thing Ever ' obviously does n't overheat and discolourTherefore'teh iPhone ' does n't overheat and discolour.QED</tokentext>
<sentencetext>Simple logic shows these claims to be provably false:1.
'teh iPhone' is 'teh Best Thing Ever'2.
'teh Best Thing Ever' obviously doesn't overheat and discolourTherefore'teh iPhone' doesn't overheat and discolour.QED</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540637</id>
	<title>Re:Hmmmm ...</title>
	<author>samirbenabid</author>
	<datestamp>1246452840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You forgot Apple III...</htmltext>
<tokenext>You forgot Apple III.. .</tokentext>
<sentencetext>You forgot Apple III...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542435</id>
	<title>Re:Hmmmm ...</title>
	<author>AncientPC</author>
	<datestamp>1246463580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's because all 3 laptops you linked to used Sony cells which were the root cause of the problem (dated 2006 - 2007).  In this case, the engineering issue is still localized to a single manufacturer.</p></htmltext>
<tokenext>That 's because all 3 laptops you linked to used Sony cells which were the root cause of the problem ( dated 2006 - 2007 ) .
In this case , the engineering issue is still localized to a single manufacturer .</tokentext>
<sentencetext>That's because all 3 laptops you linked to used Sony cells which were the root cause of the problem (dated 2006 - 2007).
In this case, the engineering issue is still localized to a single manufacturer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540475</id>
	<title>Re:Provably False</title>
	<author>rinoid</author>
	<datestamp>1246450920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually with the built in iPhone word predictor you don't really get that kind of misspelling.</p><p>#justsaying</p></htmltext>
<tokenext>Actually with the built in iPhone word predictor you do n't really get that kind of misspelling. # justsaying</tokentext>
<sentencetext>Actually with the built in iPhone word predictor you don't really get that kind of misspelling.#justsaying</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28553891</id>
	<title>Watercooled</title>
	<author>Anonymous</author>
	<datestamp>1246469280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It is designed to be watercooled(Drop it in a bucket of water)</p></htmltext>
<tokenext>It is designed to be watercooled ( Drop it in a bucket of water )</tokentext>
<sentencetext>It is designed to be watercooled(Drop it in a bucket of water)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831</id>
	<title>Oh hey no problem</title>
	<author>Anonymous</author>
	<datestamp>1246442280000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Apple can just deal with this like everyone else, right? You know, send a whole bunch of batteries to the retail stores, and those affected can come in, pop off the back of the phone, replace the battery, and drop off the old one. No need to send the phone back or anything.</p></htmltext>
<tokenext>Apple can just deal with this like everyone else , right ?
You know , send a whole bunch of batteries to the retail stores , and those affected can come in , pop off the back of the phone , replace the battery , and drop off the old one .
No need to send the phone back or anything .</tokentext>
<sentencetext>Apple can just deal with this like everyone else, right?
You know, send a whole bunch of batteries to the retail stores, and those affected can come in, pop off the back of the phone, replace the battery, and drop off the old one.
No need to send the phone back or anything.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541023</id>
	<title>Motorola</title>
	<author>Thyamine</author>
	<datestamp>1246456380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I haven't had a chance to try the new iPhones, but I remember my black Motorola flip phone from about 8 or so years ago doing exactly that.  Calling from the car and thinking it was almost too hot to hold to my head.  Now, that was also 8 years ago, so you'd think they'd be better, but it's not like it's the first phone to scald your face off.</htmltext>
<tokenext>I have n't had a chance to try the new iPhones , but I remember my black Motorola flip phone from about 8 or so years ago doing exactly that .
Calling from the car and thinking it was almost too hot to hold to my head .
Now , that was also 8 years ago , so you 'd think they 'd be better , but it 's not like it 's the first phone to scald your face off .</tokentext>
<sentencetext>I haven't had a chance to try the new iPhones, but I remember my black Motorola flip phone from about 8 or so years ago doing exactly that.
Calling from the car and thinking it was almost too hot to hold to my head.
Now, that was also 8 years ago, so you'd think they'd be better, but it's not like it's the first phone to scald your face off.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28555629</id>
	<title>The NEW iPhone!</title>
	<author>Asylumkeeper</author>
	<datestamp>1246534740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Don't worry everyone, they will design and bring a new one out by christmas so everyone can bin their current iPhone and rush out to buy the new one! I wonder what wonderful features will be on the next one? Tea making facilities maybe?</htmltext>
<tokenext>Do n't worry everyone , they will design and bring a new one out by christmas so everyone can bin their current iPhone and rush out to buy the new one !
I wonder what wonderful features will be on the next one ?
Tea making facilities maybe ?</tokentext>
<sentencetext>Don't worry everyone, they will design and bring a new one out by christmas so everyone can bin their current iPhone and rush out to buy the new one!
I wonder what wonderful features will be on the next one?
Tea making facilities maybe?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539855</id>
	<title>Bug or Feature?</title>
	<author>Anonymous</author>
	<datestamp>1246442460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Glowing pink.... is that a bug or a feature?</htmltext>
<tokenext>Glowing pink.... is that a bug or a feature ?</tokentext>
<sentencetext>Glowing pink.... is that a bug or a feature?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542219</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>nametaken</author>
	<datestamp>1246462620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>PS. No idea why you've been modded off topic, since a comparison of similar issues with other phones seems highly relevant to me. Had I mod points I'd have corrected that.</i></p><p>That would be the hypersensitive Google fans countering the hypersensitive Apple fans.  Out of my way, I'm getting out of here!</p></htmltext>
<tokenext>PS .
No idea why you 've been modded off topic , since a comparison of similar issues with other phones seems highly relevant to me .
Had I mod points I 'd have corrected that.That would be the hypersensitive Google fans countering the hypersensitive Apple fans .
Out of my way , I 'm getting out of here !</tokentext>
<sentencetext>PS.
No idea why you've been modded off topic, since a comparison of similar issues with other phones seems highly relevant to me.
Had I mod points I'd have corrected that.That would be the hypersensitive Google fans countering the hypersensitive Apple fans.
Out of my way, I'm getting out of here!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540141</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543573</id>
	<title>Re:Hmmmm ...</title>
	<author>nine-times</author>
	<datestamp>1246467660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I can remember several cases ( MacBooks, iMacs, what have you) where they've had overheating issues<nobr> <wbr></nobr>... pretty sloppy engineering if you ask me.</p></div><p>Citation needed?  How many different models have had overheating issues, and what was the failure rate?
</p><p>I know some of their laptops would become noticeably warm, but some of that is specifically because they're leading heat away from the device by using parts of the case as a heat sink.  I remember reading that some people had problems where the MacBook Air would run slowly at times because, when it started running too hot, it would go into some kind of "reduced power mode".  Neither of those things are really sloppy engineering, but only design choices.</p></div>
	</htmltext>
<tokenext>I can remember several cases ( MacBooks , iMacs , what have you ) where they 've had overheating issues ... pretty sloppy engineering if you ask me.Citation needed ?
How many different models have had overheating issues , and what was the failure rate ?
I know some of their laptops would become noticeably warm , but some of that is specifically because they 're leading heat away from the device by using parts of the case as a heat sink .
I remember reading that some people had problems where the MacBook Air would run slowly at times because , when it started running too hot , it would go into some kind of " reduced power mode " .
Neither of those things are really sloppy engineering , but only design choices .</tokentext>
<sentencetext>I can remember several cases ( MacBooks, iMacs, what have you) where they've had overheating issues ... pretty sloppy engineering if you ask me.Citation needed?
How many different models have had overheating issues, and what was the failure rate?
I know some of their laptops would become noticeably warm, but some of that is specifically because they're leading heat away from the device by using parts of the case as a heat sink.
I remember reading that some people had problems where the MacBook Air would run slowly at times because, when it started running too hot, it would go into some kind of "reduced power mode".
Neither of those things are really sloppy engineering, but only design choices.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28544607</id>
	<title>3G</title>
	<author>CSFFlame</author>
	<datestamp>1246470660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>My normal 3G gets quite hot (not unhandlably, but enough to be uncomfortable) when using GPS.

If the 3GS is worse, it could easily be to hot to hold.</htmltext>
<tokenext>My normal 3G gets quite hot ( not unhandlably , but enough to be uncomfortable ) when using GPS .
If the 3GS is worse , it could easily be to hot to hold .</tokentext>
<sentencetext>My normal 3G gets quite hot (not unhandlably, but enough to be uncomfortable) when using GPS.
If the 3GS is worse, it could easily be to hot to hold.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540429</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>jellomizer</author>
	<datestamp>1246450440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have a Generation 1 iPhone when I am doing a lot of browsing over edge or WiFi it gets noticeably warm too. Not Hot just warm. It is probably just the CPU heating up from the extra work. the 3G S cpu probably had some variation in its manufacture or during the iphone manufacture process a step was missed or the wrong quantity was used, or just replaced with a different part that seemed equal but had issues.  Perhaps the overheating iPhones actually go faster then the non-overheating ones.</p></htmltext>
<tokenext>I have a Generation 1 iPhone when I am doing a lot of browsing over edge or WiFi it gets noticeably warm too .
Not Hot just warm .
It is probably just the CPU heating up from the extra work .
the 3G S cpu probably had some variation in its manufacture or during the iphone manufacture process a step was missed or the wrong quantity was used , or just replaced with a different part that seemed equal but had issues .
Perhaps the overheating iPhones actually go faster then the non-overheating ones .</tokentext>
<sentencetext>I have a Generation 1 iPhone when I am doing a lot of browsing over edge or WiFi it gets noticeably warm too.
Not Hot just warm.
It is probably just the CPU heating up from the extra work.
the 3G S cpu probably had some variation in its manufacture or during the iphone manufacture process a step was missed or the wrong quantity was used, or just replaced with a different part that seemed equal but had issues.
Perhaps the overheating iPhones actually go faster then the non-overheating ones.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540055</id>
	<title>Re:Provably False</title>
	<author>Anonymous</author>
	<datestamp>1246444920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Actually it's an indicator light that tells the processor is working hard. Only Steve could come up with something as ingenious as this.</p></htmltext>
<tokenext>Actually it 's an indicator light that tells the processor is working hard .
Only Steve could come up with something as ingenious as this .</tokentext>
<sentencetext>Actually it's an indicator light that tells the processor is working hard.
Only Steve could come up with something as ingenious as this.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580443</id>
	<title>Re:should have released it in winter</title>
	<author>Swift2001</author>
	<datestamp>1246725660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>But, if you set it on fire, it will melt! How about that, Apple???? What a worthless piece of... What's that? Any heat that destroys an iPhone will also destroy any other electronic device? Oh, come on, you Apple fanboys! Linux devices are free, and not subject to the 2nd law of thermodynamics! Get with it!</p></htmltext>
<tokenext>But , if you set it on fire , it will melt !
How about that , Apple ? ? ? ?
What a worthless piece of... What 's that ?
Any heat that destroys an iPhone will also destroy any other electronic device ?
Oh , come on , you Apple fanboys !
Linux devices are free , and not subject to the 2nd law of thermodynamics !
Get with it !</tokentext>
<sentencetext>But, if you set it on fire, it will melt!
How about that, Apple????
What a worthless piece of... What's that?
Any heat that destroys an iPhone will also destroy any other electronic device?
Oh, come on, you Apple fanboys!
Linux devices are free, and not subject to the 2nd law of thermodynamics!
Get with it!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28546917</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>GooberToo</author>
	<datestamp>1246477560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Much of the heat is generated by the battery. As the load increases so does the heat. Any application which constantly updates the screen, uses your GPS, and networking via WIFI is going to generate a lot more heat than simply using your phone. In part its because of additional electronics are running. The other part is the battery load is way up.</p></htmltext>
<tokenext>Much of the heat is generated by the battery .
As the load increases so does the heat .
Any application which constantly updates the screen , uses your GPS , and networking via WIFI is going to generate a lot more heat than simply using your phone .
In part its because of additional electronics are running .
The other part is the battery load is way up .</tokentext>
<sentencetext>Much of the heat is generated by the battery.
As the load increases so does the heat.
Any application which constantly updates the screen, uses your GPS, and networking via WIFI is going to generate a lot more heat than simply using your phone.
In part its because of additional electronics are running.
The other part is the battery load is way up.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540439</id>
	<title>Haven't seen anything like that so far</title>
	<author>jht</author>
	<datestamp>1246450440000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>I've got a white 32GB iPhone 3GS, and no problems that severe.  If I'm in extended use of the GPS/compass it does get warmer to the touch, as it will also do on lengthy phone calls (15 minutes plus or so).  It also gets warmer when (surprise) playing games for an extended period.  It hasn't gotten uncomfortably hot, nor has there been any discoloration so far.</p><p>As far as software issues, the only major one I've seen so far is that the Jawbone Prime headset I'd been using as my main headset has been having trouble with this phone - it disassociates sometimes and the button sequence to turn off the headset LED doesn't work anymore.  My other headset (a Jabra 530) works fine so I've been using it.</p><p>Battery life has been pretty good so far - from my unscientific study it seems a little better than the 3G I had before that my wife now uses.  Game playing drops it faster than voice or data, and web surfing does use more juice on 3G than on wifi.</p><p>There were a lot of BT and power management issues in the initial release of 2.0 last year.  It took Apple a couple of releases over the first month or two to get things all the way right, and I suspect we'll have a couple of fast releases now as well.</p><p>The Apple trend with every new OS release (Mac or iPhone) is basically this:</p><p>- Limited public testing if any.  Code freeze about a month before shipping.</p><p>- Initial bugfix release (.01) 2-4 weeks after the product shipped, with all the glaring bugs that they found after freeze addressed.  This rarely has any problems found in initial public release addressed unless they're super-critical.</p><p>- About 2 months after release we get a<nobr> <wbr></nobr>.02 version that covers the main issues found after they got the product into public release.  By this time the software is pretty solid - subsequent point releases during the product lifetime will add occasional minor features but mainly fix performance issues and/or security holes.  Almost all the releases afterwards will be in the first 6-8 months when it's an iPhone OS - roughly 4 months before the next year's new OS version Apple will abandon the current one and concentrate on the announcements for the coming year.</p><p>So next February or so Apple will stop fixing 3.0 in preparation for 4.0 which will be announced around March and ship around June.</p><p>They basically do the same thing with the desktop OS - just the overall life cycle is longer.  but the initial freeze/release/patch1/patch2 cycle applies there as well and on roughly the same timing.</p><p>So basically what I'm saying is that the problems that some 3GS users are having (but not me) are assuredly legit, and will likely be addressed in one of the first two bug-fix software releases for the phone.  The first release will probably come in the next week or two and may address it - and within 1-2 months it will almost certainly be taken care of through power management.  Not to mention that I'm sure my Bluetooth issue will be fixed as well.  You get used to this.  At least modern phones (iPhone, Android, Palm Pre) can and do now regularly get software updates to address issues.</p><p>I remember an era BI (before iPhone) where the carriers controlled software tightly, and the cell companies rarely or never released patches.  There's no real good reason why Windows Mobile phones virtually never get OS updates for the installed base, or why the PalmOS Treos would take over a year to fix minor issues.  Now that's properly in the hands of the vendors, where it belongs.</p></htmltext>
<tokenext>I 've got a white 32GB iPhone 3GS , and no problems that severe .
If I 'm in extended use of the GPS/compass it does get warmer to the touch , as it will also do on lengthy phone calls ( 15 minutes plus or so ) .
It also gets warmer when ( surprise ) playing games for an extended period .
It has n't gotten uncomfortably hot , nor has there been any discoloration so far.As far as software issues , the only major one I 've seen so far is that the Jawbone Prime headset I 'd been using as my main headset has been having trouble with this phone - it disassociates sometimes and the button sequence to turn off the headset LED does n't work anymore .
My other headset ( a Jabra 530 ) works fine so I 've been using it.Battery life has been pretty good so far - from my unscientific study it seems a little better than the 3G I had before that my wife now uses .
Game playing drops it faster than voice or data , and web surfing does use more juice on 3G than on wifi.There were a lot of BT and power management issues in the initial release of 2.0 last year .
It took Apple a couple of releases over the first month or two to get things all the way right , and I suspect we 'll have a couple of fast releases now as well.The Apple trend with every new OS release ( Mac or iPhone ) is basically this : - Limited public testing if any .
Code freeze about a month before shipping.- Initial bugfix release ( .01 ) 2-4 weeks after the product shipped , with all the glaring bugs that they found after freeze addressed .
This rarely has any problems found in initial public release addressed unless they 're super-critical.- About 2 months after release we get a .02 version that covers the main issues found after they got the product into public release .
By this time the software is pretty solid - subsequent point releases during the product lifetime will add occasional minor features but mainly fix performance issues and/or security holes .
Almost all the releases afterwards will be in the first 6-8 months when it 's an iPhone OS - roughly 4 months before the next year 's new OS version Apple will abandon the current one and concentrate on the announcements for the coming year.So next February or so Apple will stop fixing 3.0 in preparation for 4.0 which will be announced around March and ship around June.They basically do the same thing with the desktop OS - just the overall life cycle is longer .
but the initial freeze/release/patch1/patch2 cycle applies there as well and on roughly the same timing.So basically what I 'm saying is that the problems that some 3GS users are having ( but not me ) are assuredly legit , and will likely be addressed in one of the first two bug-fix software releases for the phone .
The first release will probably come in the next week or two and may address it - and within 1-2 months it will almost certainly be taken care of through power management .
Not to mention that I 'm sure my Bluetooth issue will be fixed as well .
You get used to this .
At least modern phones ( iPhone , Android , Palm Pre ) can and do now regularly get software updates to address issues.I remember an era BI ( before iPhone ) where the carriers controlled software tightly , and the cell companies rarely or never released patches .
There 's no real good reason why Windows Mobile phones virtually never get OS updates for the installed base , or why the PalmOS Treos would take over a year to fix minor issues .
Now that 's properly in the hands of the vendors , where it belongs .</tokentext>
<sentencetext>I've got a white 32GB iPhone 3GS, and no problems that severe.
If I'm in extended use of the GPS/compass it does get warmer to the touch, as it will also do on lengthy phone calls (15 minutes plus or so).
It also gets warmer when (surprise) playing games for an extended period.
It hasn't gotten uncomfortably hot, nor has there been any discoloration so far.As far as software issues, the only major one I've seen so far is that the Jawbone Prime headset I'd been using as my main headset has been having trouble with this phone - it disassociates sometimes and the button sequence to turn off the headset LED doesn't work anymore.
My other headset (a Jabra 530) works fine so I've been using it.Battery life has been pretty good so far - from my unscientific study it seems a little better than the 3G I had before that my wife now uses.
Game playing drops it faster than voice or data, and web surfing does use more juice on 3G than on wifi.There were a lot of BT and power management issues in the initial release of 2.0 last year.
It took Apple a couple of releases over the first month or two to get things all the way right, and I suspect we'll have a couple of fast releases now as well.The Apple trend with every new OS release (Mac or iPhone) is basically this:- Limited public testing if any.
Code freeze about a month before shipping.- Initial bugfix release (.01) 2-4 weeks after the product shipped, with all the glaring bugs that they found after freeze addressed.
This rarely has any problems found in initial public release addressed unless they're super-critical.- About 2 months after release we get a .02 version that covers the main issues found after they got the product into public release.
By this time the software is pretty solid - subsequent point releases during the product lifetime will add occasional minor features but mainly fix performance issues and/or security holes.
Almost all the releases afterwards will be in the first 6-8 months when it's an iPhone OS - roughly 4 months before the next year's new OS version Apple will abandon the current one and concentrate on the announcements for the coming year.So next February or so Apple will stop fixing 3.0 in preparation for 4.0 which will be announced around March and ship around June.They basically do the same thing with the desktop OS - just the overall life cycle is longer.
but the initial freeze/release/patch1/patch2 cycle applies there as well and on roughly the same timing.So basically what I'm saying is that the problems that some 3GS users are having (but not me) are assuredly legit, and will likely be addressed in one of the first two bug-fix software releases for the phone.
The first release will probably come in the next week or two and may address it - and within 1-2 months it will almost certainly be taken care of through power management.
Not to mention that I'm sure my Bluetooth issue will be fixed as well.
You get used to this.
At least modern phones (iPhone, Android, Palm Pre) can and do now regularly get software updates to address issues.I remember an era BI (before iPhone) where the carriers controlled software tightly, and the cell companies rarely or never released patches.
There's no real good reason why Windows Mobile phones virtually never get OS updates for the installed base, or why the PalmOS Treos would take over a year to fix minor issues.
Now that's properly in the hands of the vendors, where it belongs.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541917</id>
	<title>Re:Hmmmm ...</title>
	<author>Nemyst</author>
	<datestamp>1246461480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>At least the other manufacturers you are listing here have removeable batteries...</htmltext>
<tokenext>At least the other manufacturers you are listing here have removeable batteries.. .</tokentext>
<sentencetext>At least the other manufacturers you are listing here have removeable batteries...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540575</id>
	<title>Re:They DO test it you insensitive clod...</title>
	<author>Anonymous</author>
	<datestamp>1246452120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>iPhone iMplicated iN iNcinerated iGloo iNferno iNdigenous iNuit iNsist.</p></htmltext>
<tokenext>iPhone iMplicated iN iNcinerated iGloo iNferno iNdigenous iNuit iNsist .</tokentext>
<sentencetext>iPhone iMplicated iN iNcinerated iGloo iNferno iNdigenous iNuit iNsist.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539985</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542637</id>
	<title>My 3GS had a different issue...</title>
	<author>UttBuggly</author>
	<datestamp>1246464480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I started a story about my iPhone 3GS experience Monday night after experiencing what I termed the "3GS Sleep (switch) Disorder".</p><p>The short version is that I purchased my first iPhone...a black 16GB 3GS last Saturday...from the local Apple Store. By Sunday, I was convinced I had a problem and opened a case with Apple on Monday. The AppleCare tech scheduled a Genius appointment at the local store for Thursday, 7/2. The phone could still make and receive calls at that point.</p><p>Yesterday morning (Tuesday, 6/30) the phone was toast...the screen was strobing between the Lock screen and the Power Off screen. The sleep switch no longer worked at all.</p><p>I called the local Apple store, explained the situation, cited the case number, was told to come in and get on STANDBY for a Genius. It took a little over an hour...mostly wait time...and I ended up with a new iPhone from the 5 they had in stock. Neither the original unit nor the new one have exhibited any heating issues, and I pretty much leave everything on as it's new and I can't put the damn thing down!</p><p>So, I may be OK. I will mention that several folks on the Apple Forums described the same issue I had. The AppleCare tech made a mention of "cracked circuit boards" but did not elaborate. The local Genius took the unit apart to check the ribbon cable to the sleep switch and found no visible cracks or damage to the phone. The phone would NOT complete a Restore,,,it hung during the Firmware install/verify. That's when the Genius said "I've lost faith in this phone...let's get you a new one."</p><p>Overall, I love the phone and the software. And, I can't be unhappy with Apple's response; I have a functioning unit that so far, seems trouble free.</p><p>My 2 cents, plus tip.</p></htmltext>
<tokenext>I started a story about my iPhone 3GS experience Monday night after experiencing what I termed the " 3GS Sleep ( switch ) Disorder " .The short version is that I purchased my first iPhone...a black 16GB 3GS last Saturday...from the local Apple Store .
By Sunday , I was convinced I had a problem and opened a case with Apple on Monday .
The AppleCare tech scheduled a Genius appointment at the local store for Thursday , 7/2 .
The phone could still make and receive calls at that point.Yesterday morning ( Tuesday , 6/30 ) the phone was toast...the screen was strobing between the Lock screen and the Power Off screen .
The sleep switch no longer worked at all.I called the local Apple store , explained the situation , cited the case number , was told to come in and get on STANDBY for a Genius .
It took a little over an hour...mostly wait time...and I ended up with a new iPhone from the 5 they had in stock .
Neither the original unit nor the new one have exhibited any heating issues , and I pretty much leave everything on as it 's new and I ca n't put the damn thing down ! So , I may be OK. I will mention that several folks on the Apple Forums described the same issue I had .
The AppleCare tech made a mention of " cracked circuit boards " but did not elaborate .
The local Genius took the unit apart to check the ribbon cable to the sleep switch and found no visible cracks or damage to the phone .
The phone would NOT complete a Restore,,,it hung during the Firmware install/verify .
That 's when the Genius said " I 've lost faith in this phone...let 's get you a new one .
" Overall , I love the phone and the software .
And , I ca n't be unhappy with Apple 's response ; I have a functioning unit that so far , seems trouble free.My 2 cents , plus tip .</tokentext>
<sentencetext>I started a story about my iPhone 3GS experience Monday night after experiencing what I termed the "3GS Sleep (switch) Disorder".The short version is that I purchased my first iPhone...a black 16GB 3GS last Saturday...from the local Apple Store.
By Sunday, I was convinced I had a problem and opened a case with Apple on Monday.
The AppleCare tech scheduled a Genius appointment at the local store for Thursday, 7/2.
The phone could still make and receive calls at that point.Yesterday morning (Tuesday, 6/30) the phone was toast...the screen was strobing between the Lock screen and the Power Off screen.
The sleep switch no longer worked at all.I called the local Apple store, explained the situation, cited the case number, was told to come in and get on STANDBY for a Genius.
It took a little over an hour...mostly wait time...and I ended up with a new iPhone from the 5 they had in stock.
Neither the original unit nor the new one have exhibited any heating issues, and I pretty much leave everything on as it's new and I can't put the damn thing down!So, I may be OK. I will mention that several folks on the Apple Forums described the same issue I had.
The AppleCare tech made a mention of "cracked circuit boards" but did not elaborate.
The local Genius took the unit apart to check the ribbon cable to the sleep switch and found no visible cracks or damage to the phone.
The phone would NOT complete a Restore,,,it hung during the Firmware install/verify.
That's when the Genius said "I've lost faith in this phone...let's get you a new one.
"Overall, I love the phone and the software.
And, I can't be unhappy with Apple's response; I have a functioning unit that so far, seems trouble free.My 2 cents, plus tip.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540209</id>
	<title>Re:They DO test it you insensitive clod...</title>
	<author>wtfamidoinghere</author>
	<datestamp>1246447440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Oh man wish I had mod points right now!<br>iNuit ftw!</p></htmltext>
<tokenext>Oh man wish I had mod points right now ! iNuit ftw !</tokentext>
<sentencetext>Oh man wish I had mod points right now!iNuit ftw!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539985</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540619</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>indre1</author>
	<datestamp>1246452540000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>The heating may be caused by the <strong>increased power consumption - all Li-Po batteries have a certain constant discharge rate</strong>. If the battery gets close to that discharge rate, it starts heating up. Add to this the heat that the telephone's chips create and you get a phone that's burning your hands! This would explain why even some normal phones heat up while talking (W610i for example). <br> <br>
<strong>Why won't manufacturers use batteries with greater discharge rate?</strong> <br>
Simple: the batteries would be larger for the same capacity (mAh).</htmltext>
<tokenext>The heating may be caused by the increased power consumption - all Li-Po batteries have a certain constant discharge rate .
If the battery gets close to that discharge rate , it starts heating up .
Add to this the heat that the telephone 's chips create and you get a phone that 's burning your hands !
This would explain why even some normal phones heat up while talking ( W610i for example ) .
Why wo n't manufacturers use batteries with greater discharge rate ?
Simple : the batteries would be larger for the same capacity ( mAh ) .</tokentext>
<sentencetext>The heating may be caused by the increased power consumption - all Li-Po batteries have a certain constant discharge rate.
If the battery gets close to that discharge rate, it starts heating up.
Add to this the heat that the telephone's chips create and you get a phone that's burning your hands!
This would explain why even some normal phones heat up while talking (W610i for example).
Why won't manufacturers use batteries with greater discharge rate?
Simple: the batteries would be larger for the same capacity (mAh).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542069</id>
	<title>Re:I'm dubious</title>
	<author>hey!</author>
	<datestamp>1246462080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Again, how do you know it is the GPS chip itself?</p><p>It seems to me that this is the kind of thing you can tell from specs.  Entire OEM modules use less than one watt in continuous operation.  GPS ICs according to the spec sheets I've seen use less than 1/10 of a watt (e.g. less than 10mw when run from a 3.6v li-ion battery).</p><p>I'm not saying that GPS use doesn't trigger this.  I'm not saying it <em>can't</em> be the chip.  But if it is, this is something they surely should have known about just by reading the specs.  I can't believe that they don't watch the power consumption figures for each component they put in a device like this.</p></htmltext>
<tokenext>Again , how do you know it is the GPS chip itself ? It seems to me that this is the kind of thing you can tell from specs .
Entire OEM modules use less than one watt in continuous operation .
GPS ICs according to the spec sheets I 've seen use less than 1/10 of a watt ( e.g .
less than 10mw when run from a 3.6v li-ion battery ) .I 'm not saying that GPS use does n't trigger this .
I 'm not saying it ca n't be the chip .
But if it is , this is something they surely should have known about just by reading the specs .
I ca n't believe that they do n't watch the power consumption figures for each component they put in a device like this .</tokentext>
<sentencetext>Again, how do you know it is the GPS chip itself?It seems to me that this is the kind of thing you can tell from specs.
Entire OEM modules use less than one watt in continuous operation.
GPS ICs according to the spec sheets I've seen use less than 1/10 of a watt (e.g.
less than 10mw when run from a 3.6v li-ion battery).I'm not saying that GPS use doesn't trigger this.
I'm not saying it can't be the chip.
But if it is, this is something they surely should have known about just by reading the specs.
I can't believe that they don't watch the power consumption figures for each component they put in a device like this.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541659</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540073</id>
	<title>Re:unable to pick up the device</title>
	<author>Carewolf</author>
	<datestamp>1246445160000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>Well, you \_can\_ pick it up.</p><p>It just burns stuck in your hand so you can't let go of it. Definitely a feature!</p><p>Plus, you smell like bacon!</p></htmltext>
<tokenext>Well , you \ _can \ _ pick it up.It just burns stuck in your hand so you ca n't let go of it .
Definitely a feature ! Plus , you smell like bacon !</tokentext>
<sentencetext>Well, you \_can\_ pick it up.It just burns stuck in your hand so you can't let go of it.
Definitely a feature!Plus, you smell like bacon!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539823</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</id>
	<title>Android G1 also heats when using GPS</title>
	<author>Simon Brooke</author>
	<datestamp>1246442220000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>My Android G1 - normally cool (in the thermal sense) heats quickly when using GPS for sustained periods. It doesn't become uncomfortable to hold or to use but it's definitely noticable. My bet is that the iPhone problem is also GPS related.</p></htmltext>
<tokenext>My Android G1 - normally cool ( in the thermal sense ) heats quickly when using GPS for sustained periods .
It does n't become uncomfortable to hold or to use but it 's definitely noticable .
My bet is that the iPhone problem is also GPS related .</tokentext>
<sentencetext>My Android G1 - normally cool (in the thermal sense) heats quickly when using GPS for sustained periods.
It doesn't become uncomfortable to hold or to use but it's definitely noticable.
My bet is that the iPhone problem is also GPS related.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540581</id>
	<title>How appropriately gay is that!</title>
	<author>Anonymous</author>
	<datestamp>1246452180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>One for the fanbois!</p></htmltext>
<tokenext>One for the fanbois !</tokentext>
<sentencetext>One for the fanbois!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28544829</id>
	<title>Key word "some" iPhones overheating.</title>
	<author>aristotle-dude</author>
	<datestamp>1246471320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What is with the jumping to conclusions? Just because some units are overheating, it does not mean that the entire production run that they are part of is also flawed. With any product, there will be lemon units.
<p>
My advice would be to turn off the battery percentage as I would not be surprised if it is buggy somehow and causing a battery drain by running in the background. Not only that, but turning it off would relieve all of you OCD types from obsessing over the numbers rather than looking at actual use of the device.
</p><p>
I think that the number of unit is relatively low but my fellow apple aficionados tend to be a bunch of whiny cry babies so you end up seeing the same damn people complaining all over the internet causing it to seem more widespread than it actually is.
</p><p>
I submit for your perusal the Apple product cycle: <a href="http://www.misterbg.org/AppleProductCycle/" title="misterbg.org">http://www.misterbg.org/AppleProductCycle/</a> [misterbg.org]
</p><p>
I kind of feel left out of all this fun give than I have yet to have a problem with my iPhone but I did notice that turning on the battery percentage does tend to drain my battery faster so I'm going to turn it off for now until 3.1 comes out. Hopefully, bugs related to battery consumption will be fixed with a new release.</p></htmltext>
<tokenext>What is with the jumping to conclusions ?
Just because some units are overheating , it does not mean that the entire production run that they are part of is also flawed .
With any product , there will be lemon units .
My advice would be to turn off the battery percentage as I would not be surprised if it is buggy somehow and causing a battery drain by running in the background .
Not only that , but turning it off would relieve all of you OCD types from obsessing over the numbers rather than looking at actual use of the device .
I think that the number of unit is relatively low but my fellow apple aficionados tend to be a bunch of whiny cry babies so you end up seeing the same damn people complaining all over the internet causing it to seem more widespread than it actually is .
I submit for your perusal the Apple product cycle : http : //www.misterbg.org/AppleProductCycle/ [ misterbg.org ] I kind of feel left out of all this fun give than I have yet to have a problem with my iPhone but I did notice that turning on the battery percentage does tend to drain my battery faster so I 'm going to turn it off for now until 3.1 comes out .
Hopefully , bugs related to battery consumption will be fixed with a new release .</tokentext>
<sentencetext>What is with the jumping to conclusions?
Just because some units are overheating, it does not mean that the entire production run that they are part of is also flawed.
With any product, there will be lemon units.
My advice would be to turn off the battery percentage as I would not be surprised if it is buggy somehow and causing a battery drain by running in the background.
Not only that, but turning it off would relieve all of you OCD types from obsessing over the numbers rather than looking at actual use of the device.
I think that the number of unit is relatively low but my fellow apple aficionados tend to be a bunch of whiny cry babies so you end up seeing the same damn people complaining all over the internet causing it to seem more widespread than it actually is.
I submit for your perusal the Apple product cycle: http://www.misterbg.org/AppleProductCycle/ [misterbg.org]

I kind of feel left out of all this fun give than I have yet to have a problem with my iPhone but I did notice that turning on the battery percentage does tend to drain my battery faster so I'm going to turn it off for now until 3.1 comes out.
Hopefully, bugs related to battery consumption will be fixed with a new release.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541167</id>
	<title>Re:OMG!!!!111!</title>
	<author>Anonymous</author>
	<datestamp>1246457280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>It's a pony-phone!</p></div><p>More like a "p(h)ony-phone"</p></div>
	</htmltext>
<tokenext>It 's a pony-phone ! More like a " p ( h ) ony-phone "</tokentext>
<sentencetext>It's a pony-phone!More like a "p(h)ony-phone"
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539841</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540513</id>
	<title>Re:Hmmmm ...</title>
	<author>samkass</author>
	<datestamp>1246451580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Considering that Apple has sold millions of these things already and a relatively few are having problems, I don't think testing would likely have caught this issue.  Besides, it sounds like a software problem not a hardware problem.  Almost no embedded device is designed to be run with everything pegged at 100\% for extended periods... obviously some bug in the OS is doing so.</p></htmltext>
<tokenext>Considering that Apple has sold millions of these things already and a relatively few are having problems , I do n't think testing would likely have caught this issue .
Besides , it sounds like a software problem not a hardware problem .
Almost no embedded device is designed to be run with everything pegged at 100 \ % for extended periods... obviously some bug in the OS is doing so .</tokentext>
<sentencetext>Considering that Apple has sold millions of these things already and a relatively few are having problems, I don't think testing would likely have caught this issue.
Besides, it sounds like a software problem not a hardware problem.
Almost no embedded device is designed to be run with everything pegged at 100\% for extended periods... obviously some bug in the OS is doing so.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540841</id>
	<title>Re:Hmmmm ...</title>
	<author>Anonymous</author>
	<datestamp>1246454940000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>Eh its Apple. I mean look at how much time was spent on the Pre falling apart. Some people on Palm boards or literally on their THIRD PRE because its so poorly constructed, yet a handful of iPhones get hot and Apple is this awful company.</htmltext>
<tokenext>Eh its Apple .
I mean look at how much time was spent on the Pre falling apart .
Some people on Palm boards or literally on their THIRD PRE because its so poorly constructed , yet a handful of iPhones get hot and Apple is this awful company .</tokentext>
<sentencetext>Eh its Apple.
I mean look at how much time was spent on the Pre falling apart.
Some people on Palm boards or literally on their THIRD PRE because its so poorly constructed, yet a handful of iPhones get hot and Apple is this awful company.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539985</id>
	<title>They DO test it you insensitive clod...</title>
	<author>denzacar</author>
	<datestamp>1246444080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>It is just that all testing is done by a team of Eskimos. iNuit to be precise.</p></htmltext>
<tokenext>It is just that all testing is done by a team of Eskimos .
iNuit to be precise .</tokentext>
<sentencetext>It is just that all testing is done by a team of Eskimos.
iNuit to be precise.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542231</id>
	<title>Re:Hmmmm ...</title>
	<author>StayFrosty</author>
	<datestamp>1246462680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'd like to point out a few flaws in this argument:<br> <br>

1.  These "hardware manufacturers"  do not build their own laptops.  They are built by OEM's like Compal, AlphaTop, Asus, and Quanta.  <a href="http://tuxmobil.org/laptop\_oem.html" title="tuxmobil.org" rel="nofollow">Here</a> [tuxmobil.org] is a nice chart that can give you an idea of who really made your laptop.<br> <br>

2.  In the cases of the laptop batteries catching fire, the problem was not with the design of the laptop.  The heat produced by the electronics did not cause the battery to catch fire.  The problem is that Sony, who is the OEM of the batteries used in all of these cases, used substandard materials in the battery pack.  Check the headline on your second link if you need evidence the problem is with Sony batteries.</htmltext>
<tokenext>I 'd like to point out a few flaws in this argument : 1 .
These " hardware manufacturers " do not build their own laptops .
They are built by OEM 's like Compal , AlphaTop , Asus , and Quanta .
Here [ tuxmobil.org ] is a nice chart that can give you an idea of who really made your laptop .
2. In the cases of the laptop batteries catching fire , the problem was not with the design of the laptop .
The heat produced by the electronics did not cause the battery to catch fire .
The problem is that Sony , who is the OEM of the batteries used in all of these cases , used substandard materials in the battery pack .
Check the headline on your second link if you need evidence the problem is with Sony batteries .</tokentext>
<sentencetext>I'd like to point out a few flaws in this argument: 

1.
These "hardware manufacturers"  do not build their own laptops.
They are built by OEM's like Compal, AlphaTop, Asus, and Quanta.
Here [tuxmobil.org] is a nice chart that can give you an idea of who really made your laptop.
2.  In the cases of the laptop batteries catching fire, the problem was not with the design of the laptop.
The heat produced by the electronics did not cause the battery to catch fire.
The problem is that Sony, who is the OEM of the batteries used in all of these cases, used substandard materials in the battery pack.
Check the headline on your second link if you need evidence the problem is with Sony batteries.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543013</id>
	<title>So *that's* what the S stands for</title>
	<author>laoudji</author>
	<datestamp>1246465980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>...as in the sound it makes when it sears to your earlobe<nobr> <wbr></nobr>;)</htmltext>
<tokenext>...as in the sound it makes when it sears to your earlobe ; )</tokentext>
<sentencetext>...as in the sound it makes when it sears to your earlobe ;)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540633</id>
	<title>Re:Oh hey no problem</title>
	<author>Anonymous</author>
	<datestamp>1246452780000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>They'll just hand you a replacement and restore your data in store. I've seen it done more than once</p></htmltext>
<tokenext>They 'll just hand you a replacement and restore your data in store .
I 've seen it done more than once</tokentext>
<sentencetext>They'll just hand you a replacement and restore your data in store.
I've seen it done more than once</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485</id>
	<title>Re:Hmmmm ...</title>
	<author>Anonymous</author>
	<datestamp>1246451040000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>It seems <b>hardware manufacturers</b> have a hard time learning that electronics cause heat and that this heat needs to be led away from the device.</p></div><p>
Fixed that for you. <br> <br>
It has nothing to do with Apple - all hardware manufacturers seem to have problems. A quick look at google for "laptop battery catches fire" turns up <a href="http://consumerist.com/190546/another-dell-laptop-ablaze" title="consumerist.com" rel="nofollow">this</a> [consumerist.com] story about a Dell battery catching fire, <a href="http://gizmodo.com/gadgets/laptops/gizmodo-reader-witnesses-ibm-laptop-catch-fire-at-lax-201115.php" title="gizmodo.com" rel="nofollow">this</a> [gizmodo.com] story about an IBM catching fire, and <a href="http://www.v3.co.uk/vnunet/news/2192359/tosh-laptop-fire-reignites-sony" title="v3.co.uk" rel="nofollow">this</a> [v3.co.uk] story about a Toshiba catching fire. And we know those three stories aren't rare - those were just quick search results to prove a point.<br> <br>
If you're going to pick on a manufacturer for a faulty battery issue, make sure you don't portray it to be something unique to that manufacturer when it's actually something that occurs pretty much across the board.</p></div>
	</htmltext>
<tokenext>It seems hardware manufacturers have a hard time learning that electronics cause heat and that this heat needs to be led away from the device .
Fixed that for you .
It has nothing to do with Apple - all hardware manufacturers seem to have problems .
A quick look at google for " laptop battery catches fire " turns up this [ consumerist.com ] story about a Dell battery catching fire , this [ gizmodo.com ] story about an IBM catching fire , and this [ v3.co.uk ] story about a Toshiba catching fire .
And we know those three stories are n't rare - those were just quick search results to prove a point .
If you 're going to pick on a manufacturer for a faulty battery issue , make sure you do n't portray it to be something unique to that manufacturer when it 's actually something that occurs pretty much across the board .</tokentext>
<sentencetext>It seems hardware manufacturers have a hard time learning that electronics cause heat and that this heat needs to be led away from the device.
Fixed that for you.
It has nothing to do with Apple - all hardware manufacturers seem to have problems.
A quick look at google for "laptop battery catches fire" turns up this [consumerist.com] story about a Dell battery catching fire, this [gizmodo.com] story about an IBM catching fire, and this [v3.co.uk] story about a Toshiba catching fire.
And we know those three stories aren't rare - those were just quick search results to prove a point.
If you're going to pick on a manufacturer for a faulty battery issue, make sure you don't portray it to be something unique to that manufacturer when it's actually something that occurs pretty much across the board.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539841</id>
	<title>OMG!!!!111!</title>
	<author>adavies42</author>
	<datestamp>1246442340000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext>It's a pony-phone!</htmltext>
<tokenext>It 's a pony-phone !</tokentext>
<sentencetext>It's a pony-phone!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540141</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>ct1972</author>
	<datestamp>1246446240000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>When I truck a lot of traffic over 3G to the G1 I also seem to have some overheating problems, albeit not as severe as those being discussed above. Notably trying to watch TV in beebplayer seems to cause overheating which may or may not be why the video often halts for me in that application. That might tally with those proclaiming general traffic as being a problem too.

PS. No idea why you've been modded off topic, since a comparison of similar issues with other phones seems highly relevant to me. Had I mod points I'd have corrected that.</htmltext>
<tokenext>When I truck a lot of traffic over 3G to the G1 I also seem to have some overheating problems , albeit not as severe as those being discussed above .
Notably trying to watch TV in beebplayer seems to cause overheating which may or may not be why the video often halts for me in that application .
That might tally with those proclaiming general traffic as being a problem too .
PS. No idea why you 've been modded off topic , since a comparison of similar issues with other phones seems highly relevant to me .
Had I mod points I 'd have corrected that .</tokentext>
<sentencetext>When I truck a lot of traffic over 3G to the G1 I also seem to have some overheating problems, albeit not as severe as those being discussed above.
Notably trying to watch TV in beebplayer seems to cause overheating which may or may not be why the video often halts for me in that application.
That might tally with those proclaiming general traffic as being a problem too.
PS. No idea why you've been modded off topic, since a comparison of similar issues with other phones seems highly relevant to me.
Had I mod points I'd have corrected that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28558571</id>
	<title>I know what is causing this. It is not a bug.</title>
	<author>aristotle-dude</author>
	<datestamp>1246553400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>People are using power intensive applications which are drawing more power than what the USB interface can draw in peaks and valleys of usage. What you end up with is a situation where the device is getting hot because the battery is constantly draining and charging since the device has to supplement from the battery.
<p>
Many people experienced similar issues when they were using Netshare many months ago on iPhone OS 2.0 while plugged in. They noticed that the iphone 3G would get really hot and the battery would still drain even if it was plugged into a power source.
</p><p>
To prevent overheating, unplug the device when you are using it and stop using it when you have to recharge the device again. Not only will it not overheat but the battery life will not deteriorate as quickly.</p></htmltext>
<tokenext>People are using power intensive applications which are drawing more power than what the USB interface can draw in peaks and valleys of usage .
What you end up with is a situation where the device is getting hot because the battery is constantly draining and charging since the device has to supplement from the battery .
Many people experienced similar issues when they were using Netshare many months ago on iPhone OS 2.0 while plugged in .
They noticed that the iphone 3G would get really hot and the battery would still drain even if it was plugged into a power source .
To prevent overheating , unplug the device when you are using it and stop using it when you have to recharge the device again .
Not only will it not overheat but the battery life will not deteriorate as quickly .</tokentext>
<sentencetext>People are using power intensive applications which are drawing more power than what the USB interface can draw in peaks and valleys of usage.
What you end up with is a situation where the device is getting hot because the battery is constantly draining and charging since the device has to supplement from the battery.
Many people experienced similar issues when they were using Netshare many months ago on iPhone OS 2.0 while plugged in.
They noticed that the iphone 3G would get really hot and the battery would still drain even if it was plugged into a power source.
To prevent overheating, unplug the device when you are using it and stop using it when you have to recharge the device again.
Not only will it not overheat but the battery life will not deteriorate as quickly.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539957</id>
	<title>It's Real Name</title>
	<author>timothyb89</author>
	<datestamp>1246443660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I guess the added "S" is for "Scorching".

<p>Still, I've yet to find a phone that doesn't do this. My Palm Centro gets quite hot when using the antenna for any extended period of time (streaming a video or something). Every now and then it gets so hot I have to pull the battery out to wait for it to cool down. </p><p>Maybe the pink glow is a creative way to make the best out of an unavoidable problem?<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>I guess the added " S " is for " Scorching " .
Still , I 've yet to find a phone that does n't do this .
My Palm Centro gets quite hot when using the antenna for any extended period of time ( streaming a video or something ) .
Every now and then it gets so hot I have to pull the battery out to wait for it to cool down .
Maybe the pink glow is a creative way to make the best out of an unavoidable problem ?
: )</tokentext>
<sentencetext>I guess the added "S" is for "Scorching".
Still, I've yet to find a phone that doesn't do this.
My Palm Centro gets quite hot when using the antenna for any extended period of time (streaming a video or something).
Every now and then it gets so hot I have to pull the battery out to wait for it to cool down.
Maybe the pink glow is a creative way to make the best out of an unavoidable problem?
:)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540079</id>
	<title>Re:There's definately an issue of some sort</title>
	<author>ocularDeathRay</author>
	<datestamp>1246445220000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext>I had an issue like that with my old blackberry pearl. I was beta testing some software from my broker and after you loaded the quotes page once, it would continue to download data until you pulled the battery. It would get extremely hot, I didn't notice the problem for a couple hours the first time it happened. I could smell electronics starting to burn and checked over all the computers around my desk before I realized it was my phone. I think you are on to something, could easily be a buggy app causing this.</htmltext>
<tokenext>I had an issue like that with my old blackberry pearl .
I was beta testing some software from my broker and after you loaded the quotes page once , it would continue to download data until you pulled the battery .
It would get extremely hot , I did n't notice the problem for a couple hours the first time it happened .
I could smell electronics starting to burn and checked over all the computers around my desk before I realized it was my phone .
I think you are on to something , could easily be a buggy app causing this .</tokentext>
<sentencetext>I had an issue like that with my old blackberry pearl.
I was beta testing some software from my broker and after you loaded the quotes page once, it would continue to download data until you pulled the battery.
It would get extremely hot, I didn't notice the problem for a couple hours the first time it happened.
I could smell electronics starting to burn and checked over all the computers around my desk before I realized it was my phone.
I think you are on to something, could easily be a buggy app causing this.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</id>
	<title>Hmmmm ...</title>
	<author>Anonymous</author>
	<datestamp>1246442400000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>... testing anyone?</p><p>It seems Apple has a hard time learning that electronics cause heat and that this heat needs to be led away from the device.</p><p>I can remember several cases ( MacBooks, iMacs, what have you) where they've had overheating issues<nobr> <wbr></nobr>... pretty sloppy engineering if you ask me.</p></htmltext>
<tokenext>... testing anyone ? It seems Apple has a hard time learning that electronics cause heat and that this heat needs to be led away from the device.I can remember several cases ( MacBooks , iMacs , what have you ) where they 've had overheating issues ... pretty sloppy engineering if you ask me .</tokentext>
<sentencetext>... testing anyone?It seems Apple has a hard time learning that electronics cause heat and that this heat needs to be led away from the device.I can remember several cases ( MacBooks, iMacs, what have you) where they've had overheating issues ... pretty sloppy engineering if you ask me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545527</id>
	<title>Re:Battery Concerns</title>
	<author>Anonymous</author>
	<datestamp>1246473300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>the 3G plaid a big part in battery life reduction going from 1st to second gen. I live in an Edge zone on weekends and work out of town in a 3G zone during the week. I can go the whole weekend without a recharge, I have trouble going more than a day during the week without recharging.</p><p>Also, turn of wifi when you aren't actively using it - you will save many a milliwatt.</p></htmltext>
<tokenext>the 3G plaid a big part in battery life reduction going from 1st to second gen. I live in an Edge zone on weekends and work out of town in a 3G zone during the week .
I can go the whole weekend without a recharge , I have trouble going more than a day during the week without recharging.Also , turn of wifi when you are n't actively using it - you will save many a milliwatt .</tokentext>
<sentencetext>the 3G plaid a big part in battery life reduction going from 1st to second gen. I live in an Edge zone on weekends and work out of town in a 3G zone during the week.
I can go the whole weekend without a recharge, I have trouble going more than a day during the week without recharging.Also, turn of wifi when you aren't actively using it - you will save many a milliwatt.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28558623</id>
	<title>Just like the Macbook Pro!</title>
	<author>HockeyPuck</author>
	<datestamp>1246553700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>A few years back when the macbook pro (core duo) came out, people complained that the bottom got (and still does) get too hot to use it when it's on your lap.  We complained "it's a laptop, you should be able to use it on your lap!" And Apple's response was along the lines of, "you should be using it on a desk or table..."</p><p>I'm waiting for apple to come back to this and say, "Yeah it's a phone, but you shouldn't be holding it up to your head, you should be using a bluetooth headset or speakerphone."</p></htmltext>
<tokenext>A few years back when the macbook pro ( core duo ) came out , people complained that the bottom got ( and still does ) get too hot to use it when it 's on your lap .
We complained " it 's a laptop , you should be able to use it on your lap !
" And Apple 's response was along the lines of , " you should be using it on a desk or table... " I 'm waiting for apple to come back to this and say , " Yeah it 's a phone , but you should n't be holding it up to your head , you should be using a bluetooth headset or speakerphone .
"</tokentext>
<sentencetext>A few years back when the macbook pro (core duo) came out, people complained that the bottom got (and still does) get too hot to use it when it's on your lap.
We complained "it's a laptop, you should be able to use it on your lap!
" And Apple's response was along the lines of, "you should be using it on a desk or table..."I'm waiting for apple to come back to this and say, "Yeah it's a phone, but you shouldn't be holding it up to your head, you should be using a bluetooth headset or speakerphone.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542111</id>
	<title>iDAM / iPhwned</title>
	<author>Anonymous</author>
	<datestamp>1246462200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>iPhone = Made in China = BSD port of Green Dam = hot handset = iPhwned</p></htmltext>
<tokenext>iPhone = Made in China = BSD port of Green Dam = hot handset = iPhwned</tokentext>
<sentencetext>iPhone = Made in China = BSD port of Green Dam = hot handset = iPhwned</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540189</id>
	<title>Re:Hmmmm ...</title>
	<author>Anonymous</author>
	<datestamp>1246447200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's not just overheating, look at the rediculously easily scratch nanos, the fire hazard magsafe power adapters and the discolouration of MacBooks.</p><p>I wish Apple fans would let us drop the myth that Apple products are well engineered, the fact is they're not, they're shoddy as hell. People suggest the price you pay for Apple kit is for quality but that's just bollocks, it's low quality kit made in Asian sweatshops and poorly engineered without proper testing.</p><p>The fact is, all you pay for with Apple is the prestige factor, they're seen as high end devices that all the cool people have and nothing more. Apple does not produce quality products.</p></htmltext>
<tokenext>It 's not just overheating , look at the rediculously easily scratch nanos , the fire hazard magsafe power adapters and the discolouration of MacBooks.I wish Apple fans would let us drop the myth that Apple products are well engineered , the fact is they 're not , they 're shoddy as hell .
People suggest the price you pay for Apple kit is for quality but that 's just bollocks , it 's low quality kit made in Asian sweatshops and poorly engineered without proper testing.The fact is , all you pay for with Apple is the prestige factor , they 're seen as high end devices that all the cool people have and nothing more .
Apple does not produce quality products .</tokentext>
<sentencetext>It's not just overheating, look at the rediculously easily scratch nanos, the fire hazard magsafe power adapters and the discolouration of MacBooks.I wish Apple fans would let us drop the myth that Apple products are well engineered, the fact is they're not, they're shoddy as hell.
People suggest the price you pay for Apple kit is for quality but that's just bollocks, it's low quality kit made in Asian sweatshops and poorly engineered without proper testing.The fact is, all you pay for with Apple is the prestige factor, they're seen as high end devices that all the cool people have and nothing more.
Apple does not produce quality products.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411</id>
	<title>Re:should have released it in winter</title>
	<author>emlyncorrin</author>
	<datestamp>1246450080000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p><div class="quote"><p>btw apple, black sucks, it absorbes heat in the sun shine.</p></div><p>How often do you leave your phone out in direct sunlight?
And black radiates heat better, so in the shade it will cool down faster.</p></div>
	</htmltext>
<tokenext>btw apple , black sucks , it absorbes heat in the sun shine.How often do you leave your phone out in direct sunlight ?
And black radiates heat better , so in the shade it will cool down faster .</tokentext>
<sentencetext>btw apple, black sucks, it absorbes heat in the sun shine.How often do you leave your phone out in direct sunlight?
And black radiates heat better, so in the shade it will cool down faster.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539967</id>
	<title>There's an app for that</title>
	<author>Anonymous</author>
	<datestamp>1246443840000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>If you need to cook your food in the wilderness or light a campfire, there's an app for that...</htmltext>
<tokenext>If you need to cook your food in the wilderness or light a campfire , there 's an app for that.. .</tokentext>
<sentencetext>If you need to cook your food in the wilderness or light a campfire, there's an app for that...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540901</id>
	<title>Just the normal....</title>
	<author>rec9140</author>
	<datestamp>1246455420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>ripening process for a CRapple<nobr> <wbr></nobr>..... its not ripe till its red....</p><p>Just let them run till they turn red... Then they will be good to go.....</p><p>cue crapple fanbois....4...3...2....1.</p></htmltext>
<tokenext>ripening process for a CRapple ..... its not ripe till its red....Just let them run till they turn red... Then they will be good to go.....cue crapple fanbois....4...3...2....1 .</tokentext>
<sentencetext>ripening process for a CRapple ..... its not ripe till its red....Just let them run till they turn red... Then they will be good to go.....cue crapple fanbois....4...3...2....1.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540589</id>
	<title>Apple -- Microsoft</title>
	<author>Anonymous</author>
	<datestamp>1246452300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Apple is following Microsoft.  Release without testing!</p></htmltext>
<tokenext>Apple is following Microsoft .
Release without testing !</tokentext>
<sentencetext>Apple is following Microsoft.
Release without testing!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541121</id>
	<title>Re:Provably False</title>
	<author>Anonymous</author>
	<datestamp>1246456980000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Double negatives. So apple can do wrong.  (not cancells no)</p></htmltext>
<tokenext>Double negatives .
So apple can do wrong .
( not cancells no )</tokentext>
<sentencetext>Double negatives.
So apple can do wrong.
(not cancells no)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542213</id>
	<title>Re:Oh hey no problem</title>
	<author>Anonymous</author>
	<datestamp>1246462620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yeh<nobr> <wbr></nobr>:-) <br>It's not easy to implement planned obsolescence with user-replaceable parts.<br>
&nbsp; <br>A cynic might suggest that you don't buy portable Apple gear... you rent it.<br>Steve reserves the right to put his hand in your pocket every 24 months.<br>
&nbsp; <br>I seemed to be starting a collection of battery-dead iPods, so I just pick mp3-enabled cellphones these days.</p></htmltext>
<tokenext>Yeh : - ) It 's not easy to implement planned obsolescence with user-replaceable parts .
  A cynic might suggest that you do n't buy portable Apple gear... you rent it.Steve reserves the right to put his hand in your pocket every 24 months .
  I seemed to be starting a collection of battery-dead iPods , so I just pick mp3-enabled cellphones these days .</tokentext>
<sentencetext>Yeh :-) It's not easy to implement planned obsolescence with user-replaceable parts.
  A cynic might suggest that you don't buy portable Apple gear... you rent it.Steve reserves the right to put his hand in your pocket every 24 months.
  I seemed to be starting a collection of battery-dead iPods, so I just pick mp3-enabled cellphones these days.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28554921</id>
	<title>Re:Hmmmm ...</title>
	<author>MemoryDragon</author>
	<datestamp>1246567980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually apple has done a lot of machines with thermal problems in the last 20 years, the most recent examples are the macbook airs and iphones!<br>but if you read it up the first one was the famous apple 3, one of the biggest factors why ibm won over apple in those days and one of the biggest failures where jobs personal ego went against the law of physics and physics won, as always!</p></htmltext>
<tokenext>Actually apple has done a lot of machines with thermal problems in the last 20 years , the most recent examples are the macbook airs and iphones ! but if you read it up the first one was the famous apple 3 , one of the biggest factors why ibm won over apple in those days and one of the biggest failures where jobs personal ego went against the law of physics and physics won , as always !</tokentext>
<sentencetext>Actually apple has done a lot of machines with thermal problems in the last 20 years, the most recent examples are the macbook airs and iphones!but if you read it up the first one was the famous apple 3, one of the biggest factors why ibm won over apple in those days and one of the biggest failures where jobs personal ego went against the law of physics and physics won, as always!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540841</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545773</id>
	<title>Re:Inaccurate</title>
	<author>IamTheRealMike</author>
	<datestamp>1246474140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You've never seen an infinite loop inside malloc? I guess I have been unlucky enough to debug more memory corruptions than you then. They're not as common as crashes but they do happen on every platform I've worked with.</p><p>Nothing I said is false. Objective C requires you to manually manage memory. Yes, the Cocoa libraries provide some (weak) abstractions to help you with that, not that auto-release pools are very helpful for managing non-event scoped state. Yet it is based on C and does not bounds check, it does not prevent memory errors and it uses a standard malloc implementation. Having some abstraction over malloc doesn't suddenly make your program managed.</p></htmltext>
<tokenext>You 've never seen an infinite loop inside malloc ?
I guess I have been unlucky enough to debug more memory corruptions than you then .
They 're not as common as crashes but they do happen on every platform I 've worked with.Nothing I said is false .
Objective C requires you to manually manage memory .
Yes , the Cocoa libraries provide some ( weak ) abstractions to help you with that , not that auto-release pools are very helpful for managing non-event scoped state .
Yet it is based on C and does not bounds check , it does not prevent memory errors and it uses a standard malloc implementation .
Having some abstraction over malloc does n't suddenly make your program managed .</tokentext>
<sentencetext>You've never seen an infinite loop inside malloc?
I guess I have been unlucky enough to debug more memory corruptions than you then.
They're not as common as crashes but they do happen on every platform I've worked with.Nothing I said is false.
Objective C requires you to manually manage memory.
Yes, the Cocoa libraries provide some (weak) abstractions to help you with that, not that auto-release pools are very helpful for managing non-event scoped state.
Yet it is based on C and does not bounds check, it does not prevent memory errors and it uses a standard malloc implementation.
Having some abstraction over malloc doesn't suddenly make your program managed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542725</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541745</id>
	<title>Re:unable to pick up the device</title>
	<author>syousef</author>
	<datestamp>1246460580000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p><i>Well, you \_can\_ pick it up. It just burns stuck in your hand so you can't let go of it. Definitely a feature!</i></p><p>I was wondering when Apple would get around to branding it's users.</p></htmltext>
<tokenext>Well , you \ _can \ _ pick it up .
It just burns stuck in your hand so you ca n't let go of it .
Definitely a feature ! I was wondering when Apple would get around to branding it 's users .</tokentext>
<sentencetext>Well, you \_can\_ pick it up.
It just burns stuck in your hand so you can't let go of it.
Definitely a feature!I was wondering when Apple would get around to branding it's users.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540073</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28555393</id>
	<title>Not just iPhones - Apple laptops overheat too....</title>
	<author>PensivePeter</author>
	<datestamp>1246531140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>...just that when any user complains about their batteries overheating or exploding, they are quickly and quietly replaced (the batteries, not the users).<p> Apple remains the master of news management for different vital organ transplants, but this time it seems that there are simply too many stories out there for even Apple to shut them all down in their customary, efficient, and 1984-style manner.</p></htmltext>
<tokenext>...just that when any user complains about their batteries overheating or exploding , they are quickly and quietly replaced ( the batteries , not the users ) .
Apple remains the master of news management for different vital organ transplants , but this time it seems that there are simply too many stories out there for even Apple to shut them all down in their customary , efficient , and 1984-style manner .</tokentext>
<sentencetext>...just that when any user complains about their batteries overheating or exploding, they are quickly and quietly replaced (the batteries, not the users).
Apple remains the master of news management for different vital organ transplants, but this time it seems that there are simply too many stories out there for even Apple to shut them all down in their customary, efficient, and 1984-style manner.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540615</id>
	<title>Re:unable to pick up the device</title>
	<author>Idbar</author>
	<datestamp>1246452540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>it isn't a bug, it's a feature</p></div><p>It's alive! The iPhone has the feature of killing bugs by means of fever. Probably people with the reported devices had signs of swine flu, or... Were the iPhones just trying to kill their owners already? That's some impressive AI!</p></div>
	</htmltext>
<tokenext>it is n't a bug , it 's a featureIt 's alive !
The iPhone has the feature of killing bugs by means of fever .
Probably people with the reported devices had signs of swine flu , or... Were the iPhones just trying to kill their owners already ?
That 's some impressive AI !</tokentext>
<sentencetext>it isn't a bug, it's a featureIt's alive!
The iPhone has the feature of killing bugs by means of fever.
Probably people with the reported devices had signs of swine flu, or... Were the iPhones just trying to kill their owners already?
That's some impressive AI!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539823</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539823</id>
	<title>unable to pick up the device</title>
	<author>Anonymous</author>
	<datestamp>1246442220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>it isn't a bug, it's a feature</p></htmltext>
<tokenext>it is n't a bug , it 's a feature</tokentext>
<sentencetext>it isn't a bug, it's a feature</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539927</id>
	<title>New App perhaps ?</title>
	<author>BeANeR\_UK</author>
	<datestamp>1246443360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>
Perhaps the heat thing is a new app, for use in colder climates,...

 - ihotwaterbottle ?</htmltext>
<tokenext>Perhaps the heat thing is a new app , for use in colder climates,.. . - ihotwaterbottle ?</tokentext>
<sentencetext>
Perhaps the heat thing is a new app, for use in colder climates,...

 - ihotwaterbottle ?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541027</id>
	<title>And that...</title>
	<author>Anonymous</author>
	<datestamp>1246456380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>is why I am a PC.<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>is why I am a PC .
: )</tokentext>
<sentencetext>is why I am a PC.
:)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545621</id>
	<title>Welcome our IPhone overlords</title>
	<author>SpoodyGoon</author>
	<datestamp>1246473600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I for one welcome our IPhone overlords, it's obvious the IPhones are becoming self aware.</htmltext>
<tokenext>I for one welcome our IPhone overlords , it 's obvious the IPhones are becoming self aware .</tokentext>
<sentencetext>I for one welcome our IPhone overlords, it's obvious the IPhones are becoming self aware.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540683</id>
	<title>Re:There's definately an issue of some sort</title>
	<author>pringlis</author>
	<datestamp>1246453500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>I've had this problem too.  Those I've spoken to about it attribute it to either the GPS chip or the WiFi chip not powering down properly.</htmltext>
<tokenext>I 've had this problem too .
Those I 've spoken to about it attribute it to either the GPS chip or the WiFi chip not powering down properly .</tokentext>
<sentencetext>I've had this problem too.
Those I've spoken to about it attribute it to either the GPS chip or the WiFi chip not powering down properly.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915</id>
	<title>There's definately an issue of some sort</title>
	<author>Anonymous</author>
	<datestamp>1246443120000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>I think there is a software issue that causes something to start draining power at a crazy rate non-stop.  I turned on the percentage battery indicator on my 3gs and one day I noticed it was running kind of hot and I looked at the indicator and saw the battery \% had gotten crazy low really fast so I just set the phone down and watched.</p><p>I was losing like 1\% every minute while running nothing other than the OS itself.  WTF?  That's like under 2 hour battery life while doing NOTHING but staring at the home screen -- you're supposed to be able to watch video for 6-7 hours, right?</p><p>So I powered my phone off completely, then let it reboot.  Whatever it was, it went away.  After that it ran smooth, no extra heat, battery indicator stayed at the same percent as I stared at homescreen for 5+ minutes and it was perfectly fine for the rest of the day.   No clue what happened there, but something was draining power non-stop until I rebooted the thing.  I assume it wasn't the processor, because it wasn't locked up -- so perhaps it was a modem issue.</p><p>It's quite possible that had I not noticed this issue and rebooted my phone I might have ended up with a pink one as well.</p></htmltext>
<tokenext>I think there is a software issue that causes something to start draining power at a crazy rate non-stop .
I turned on the percentage battery indicator on my 3gs and one day I noticed it was running kind of hot and I looked at the indicator and saw the battery \ % had gotten crazy low really fast so I just set the phone down and watched.I was losing like 1 \ % every minute while running nothing other than the OS itself .
WTF ? That 's like under 2 hour battery life while doing NOTHING but staring at the home screen -- you 're supposed to be able to watch video for 6-7 hours , right ? So I powered my phone off completely , then let it reboot .
Whatever it was , it went away .
After that it ran smooth , no extra heat , battery indicator stayed at the same percent as I stared at homescreen for 5 + minutes and it was perfectly fine for the rest of the day .
No clue what happened there , but something was draining power non-stop until I rebooted the thing .
I assume it was n't the processor , because it was n't locked up -- so perhaps it was a modem issue.It 's quite possible that had I not noticed this issue and rebooted my phone I might have ended up with a pink one as well .</tokentext>
<sentencetext>I think there is a software issue that causes something to start draining power at a crazy rate non-stop.
I turned on the percentage battery indicator on my 3gs and one day I noticed it was running kind of hot and I looked at the indicator and saw the battery \% had gotten crazy low really fast so I just set the phone down and watched.I was losing like 1\% every minute while running nothing other than the OS itself.
WTF?  That's like under 2 hour battery life while doing NOTHING but staring at the home screen -- you're supposed to be able to watch video for 6-7 hours, right?So I powered my phone off completely, then let it reboot.
Whatever it was, it went away.
After that it ran smooth, no extra heat, battery indicator stayed at the same percent as I stared at homescreen for 5+ minutes and it was perfectly fine for the rest of the day.
No clue what happened there, but something was draining power non-stop until I rebooted the thing.
I assume it wasn't the processor, because it wasn't locked up -- so perhaps it was a modem issue.It's quite possible that had I not noticed this issue and rebooted my phone I might have ended up with a pink one as well.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540639</id>
	<title>Running in the background</title>
	<author>imakemusic</author>
	<datestamp>1246452840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Someone clearly left their iBacon app running the background.</htmltext>
<tokenext>Someone clearly left their iBacon app running the background .</tokentext>
<sentencetext>Someone clearly left their iBacon app running the background.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539925</id>
	<title>Ouch</title>
	<author>sonicmerlin</author>
	<datestamp>1246443300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>If this is what happens when Steve Jobs is absent from Apple for 6 months, I shudder to think what will happen when he's permanently gone.

As arrogant and bone-headed as Apple can seem sometimes, there's no doubt it's lead extremely well.</htmltext>
<tokenext>If this is what happens when Steve Jobs is absent from Apple for 6 months , I shudder to think what will happen when he 's permanently gone .
As arrogant and bone-headed as Apple can seem sometimes , there 's no doubt it 's lead extremely well .</tokentext>
<sentencetext>If this is what happens when Steve Jobs is absent from Apple for 6 months, I shudder to think what will happen when he's permanently gone.
As arrogant and bone-headed as Apple can seem sometimes, there's no doubt it's lead extremely well.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541525</id>
	<title>Re:Battery Concerns</title>
	<author>Bertie</author>
	<datestamp>1246459380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I just took an iPhone 3G to Glastonbury.  I turned off WiFi and 3G, and switched it off at night, and it made it from Wednesday to Sunday morning before dying, despite me making probably hundreds of calls (most of them didn't connect).  So you can get decent milage out of them if you strip back most of the functaionality.  Obviously this rather defeats the purpose of having such a sophisticated device, but really, WiFi's not a lot of good to you in a field.</p></htmltext>
<tokenext>I just took an iPhone 3G to Glastonbury .
I turned off WiFi and 3G , and switched it off at night , and it made it from Wednesday to Sunday morning before dying , despite me making probably hundreds of calls ( most of them did n't connect ) .
So you can get decent milage out of them if you strip back most of the functaionality .
Obviously this rather defeats the purpose of having such a sophisticated device , but really , WiFi 's not a lot of good to you in a field .</tokentext>
<sentencetext>I just took an iPhone 3G to Glastonbury.
I turned off WiFi and 3G, and switched it off at night, and it made it from Wednesday to Sunday morning before dying, despite me making probably hundreds of calls (most of them didn't connect).
So you can get decent milage out of them if you strip back most of the functaionality.
Obviously this rather defeats the purpose of having such a sophisticated device, but really, WiFi's not a lot of good to you in a field.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540547</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>vlm</author>
	<datestamp>1246452000000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>My bet is that the iPhone problem is also GPS related.</p></div><p>My somewhat ancient Garmin GPS runs for somewhat over a day continuous on two AA batteries.  It has a nice full color screen about the size of a iphone although much lower resolution.  It is an inch or two larger than an iphone in all dimensions but that's mostly empty space... its engineered to be less dense than water, so as to float.</p><p>So, thats about 3 volts at about 1.5 amp-hours equals about 4.5 watt-hours.</p><p>Dividing 4.5 watthours by a pessimistic 24 hours, gives 188 milliwatts.</p><p>I'm sure a decade or so newer engineering results in much lower power consumption.  Checking out the technical specifications PDF for the first google I found:</p><p><a href="http://www.latitudetechnology.com/gps\_module.html" title="latitudetechnology.com">http://www.latitudetechnology.com/gps\_module.html</a> [latitudetechnology.com]</p><p>You're looking at about 23 mA at about 3 volts, for a whopping 70 milliwatts, almost a third less for an "april of 2009" GPS module.  Technology marches onward I guess.</p><p>1) A quarter watt dumped in a case that large is not going to be detectably warmer, but it'll probably be almost enough to stop dew from condensing on the surface, most of the time.  Dew will condense on the surface of my powered up GPS in extreme weather conditions.  To get "warm" with a quarter watt, compare the tiny volume and tiny surface area of a typical quarter-watt power resistor to an iphone.</p><p>2) Considering handheld cellphones are allowed to transmit 600 mW and I suspect the overall RF section is less than 50\% efficient, the phone probably dumps at least 3 times the heat from its RF section than its GPS section.  Then probably about half the emitted RF gets adsorbed by the users hands, figure about a watt of total heat in the hands just from the transmitter.  GPS or no, will not be noticeable.</p><p>The problem is not the GPS module.  Now a GPS application could "require" a multi-core GHZ class pentium processor at full blast, but thats a software engineering problem not a "GPS" problem, since obviously a "real handheld GPS" does the same task without turning into a handwarmer.  A bad enough programmer could make a tetris that would burn your hands, but that doesn't mean tetris is the problem.</p></div>
	</htmltext>
<tokenext>My bet is that the iPhone problem is also GPS related.My somewhat ancient Garmin GPS runs for somewhat over a day continuous on two AA batteries .
It has a nice full color screen about the size of a iphone although much lower resolution .
It is an inch or two larger than an iphone in all dimensions but that 's mostly empty space... its engineered to be less dense than water , so as to float.So , thats about 3 volts at about 1.5 amp-hours equals about 4.5 watt-hours.Dividing 4.5 watthours by a pessimistic 24 hours , gives 188 milliwatts.I 'm sure a decade or so newer engineering results in much lower power consumption .
Checking out the technical specifications PDF for the first google I found : http : //www.latitudetechnology.com/gps \ _module.html [ latitudetechnology.com ] You 're looking at about 23 mA at about 3 volts , for a whopping 70 milliwatts , almost a third less for an " april of 2009 " GPS module .
Technology marches onward I guess.1 ) A quarter watt dumped in a case that large is not going to be detectably warmer , but it 'll probably be almost enough to stop dew from condensing on the surface , most of the time .
Dew will condense on the surface of my powered up GPS in extreme weather conditions .
To get " warm " with a quarter watt , compare the tiny volume and tiny surface area of a typical quarter-watt power resistor to an iphone.2 ) Considering handheld cellphones are allowed to transmit 600 mW and I suspect the overall RF section is less than 50 \ % efficient , the phone probably dumps at least 3 times the heat from its RF section than its GPS section .
Then probably about half the emitted RF gets adsorbed by the users hands , figure about a watt of total heat in the hands just from the transmitter .
GPS or no , will not be noticeable.The problem is not the GPS module .
Now a GPS application could " require " a multi-core GHZ class pentium processor at full blast , but thats a software engineering problem not a " GPS " problem , since obviously a " real handheld GPS " does the same task without turning into a handwarmer .
A bad enough programmer could make a tetris that would burn your hands , but that does n't mean tetris is the problem .</tokentext>
<sentencetext>My bet is that the iPhone problem is also GPS related.My somewhat ancient Garmin GPS runs for somewhat over a day continuous on two AA batteries.
It has a nice full color screen about the size of a iphone although much lower resolution.
It is an inch or two larger than an iphone in all dimensions but that's mostly empty space... its engineered to be less dense than water, so as to float.So, thats about 3 volts at about 1.5 amp-hours equals about 4.5 watt-hours.Dividing 4.5 watthours by a pessimistic 24 hours, gives 188 milliwatts.I'm sure a decade or so newer engineering results in much lower power consumption.
Checking out the technical specifications PDF for the first google I found:http://www.latitudetechnology.com/gps\_module.html [latitudetechnology.com]You're looking at about 23 mA at about 3 volts, for a whopping 70 milliwatts, almost a third less for an "april of 2009" GPS module.
Technology marches onward I guess.1) A quarter watt dumped in a case that large is not going to be detectably warmer, but it'll probably be almost enough to stop dew from condensing on the surface, most of the time.
Dew will condense on the surface of my powered up GPS in extreme weather conditions.
To get "warm" with a quarter watt, compare the tiny volume and tiny surface area of a typical quarter-watt power resistor to an iphone.2) Considering handheld cellphones are allowed to transmit 600 mW and I suspect the overall RF section is less than 50\% efficient, the phone probably dumps at least 3 times the heat from its RF section than its GPS section.
Then probably about half the emitted RF gets adsorbed by the users hands, figure about a watt of total heat in the hands just from the transmitter.
GPS or no, will not be noticeable.The problem is not the GPS module.
Now a GPS application could "require" a multi-core GHZ class pentium processor at full blast, but thats a software engineering problem not a "GPS" problem, since obviously a "real handheld GPS" does the same task without turning into a handwarmer.
A bad enough programmer could make a tetris that would burn your hands, but that doesn't mean tetris is the problem.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540033</id>
	<title>saw this on El Reg yesterday</title>
	<author>tiggertaebo</author>
	<datestamp>1246444800000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Sounds like a fairly straight forward case of there being a few dodgy units out there to me - not exactly the biggest surprise when you consider the number of units produced and the short development/testing cycles people have to get new gadgets out these days. Apple aren't the only ones this sort of thing has happened to and they certainly won't be the last.</p><p>Watching all the fanbois go up in flames (bah-dum-tish) was however pure internet entertainment!</p><p>"nuh-huh didn't happen!"</p><p>"they are using it wrong"</p><p>"its normal!! laptops can browse the internet and gets hot - the iphone can browse the internet and gets hot. Same thing innit?"</p><p>"it's cos of the mega-fast hardware - it just shows how awesome it is"</p><p>"YOU'RE ALL JEALOUS!!"</p><p>As I expect there will be some of the same along here shortly I'll grab some popcorn<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>Sounds like a fairly straight forward case of there being a few dodgy units out there to me - not exactly the biggest surprise when you consider the number of units produced and the short development/testing cycles people have to get new gadgets out these days .
Apple are n't the only ones this sort of thing has happened to and they certainly wo n't be the last.Watching all the fanbois go up in flames ( bah-dum-tish ) was however pure internet entertainment !
" nuh-huh did n't happen !
" " they are using it wrong " " its normal ! !
laptops can browse the internet and gets hot - the iphone can browse the internet and gets hot .
Same thing innit ?
" " it 's cos of the mega-fast hardware - it just shows how awesome it is " " YOU 'RE ALL JEALOUS ! !
" As I expect there will be some of the same along here shortly I 'll grab some popcorn : )</tokentext>
<sentencetext>Sounds like a fairly straight forward case of there being a few dodgy units out there to me - not exactly the biggest surprise when you consider the number of units produced and the short development/testing cycles people have to get new gadgets out these days.
Apple aren't the only ones this sort of thing has happened to and they certainly won't be the last.Watching all the fanbois go up in flames (bah-dum-tish) was however pure internet entertainment!
"nuh-huh didn't happen!
""they are using it wrong""its normal!!
laptops can browse the internet and gets hot - the iphone can browse the internet and gets hot.
Same thing innit?
""it's cos of the mega-fast hardware - it just shows how awesome it is""YOU'RE ALL JEALOUS!!
"As I expect there will be some of the same along here shortly I'll grab some popcorn :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542161</id>
	<title>Water Cooled</title>
	<author>Anonymous</author>
	<datestamp>1246462380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The Iphones are meant to be water cooled. You are supposed use them underwater only.</p></htmltext>
<tokenext>The Iphones are meant to be water cooled .
You are supposed use them underwater only .</tokentext>
<sentencetext>The Iphones are meant to be water cooled.
You are supposed use them underwater only.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541173</id>
	<title>Re:There's definately an issue of some sort</title>
	<author>Anonymous</author>
	<datestamp>1246457340000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>It seems to be pretty common after the 3.0 OS upgrade and not limited to the 3GS.:</p><p>

<a href="http://discussions.apple.com/thread.jspa?threadID=2045240&amp;tstart=0" title="apple.com">http://discussions.apple.com/thread.jspa?threadID=2045240&amp;tstart=0</a> [apple.com] <br>
<a href="http://forums.macnn.com/103/ipod-iphone-and-apple-tv/394175/battery-life-sucks-iphone-3-0-a/" title="macnn.com">http://forums.macnn.com/103/ipod-iphone-and-apple-tv/394175/battery-life-sucks-iphone-3-0-a/</a> [macnn.com]</p></htmltext>
<tokenext>It seems to be pretty common after the 3.0 OS upgrade and not limited to the 3GS .
: http : //discussions.apple.com/thread.jspa ? threadID = 2045240&amp;tstart = 0 [ apple.com ] http : //forums.macnn.com/103/ipod-iphone-and-apple-tv/394175/battery-life-sucks-iphone-3-0-a/ [ macnn.com ]</tokentext>
<sentencetext>It seems to be pretty common after the 3.0 OS upgrade and not limited to the 3GS.
:

http://discussions.apple.com/thread.jspa?threadID=2045240&amp;tstart=0 [apple.com] 
http://forums.macnn.com/103/ipod-iphone-and-apple-tv/394175/battery-life-sucks-iphone-3-0-a/ [macnn.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540127</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541611</id>
	<title>Re:Hmmmm ...</title>
	<author>BobMcD</author>
	<datestamp>1246459740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>When I googled "laptop battery catches fire" I didn't see any that weren't able to be replaced by the end user.  In fact, there are many stories of battery recalls and replacement programs.</p><p>And for the iPhone?</p><p>My point - If you're going to make the battery a permanent fixture, you need to vet it first.  Particularly in a world where we know laptops catch fire due to battery heat.</p></htmltext>
<tokenext>When I googled " laptop battery catches fire " I did n't see any that were n't able to be replaced by the end user .
In fact , there are many stories of battery recalls and replacement programs.And for the iPhone ? My point - If you 're going to make the battery a permanent fixture , you need to vet it first .
Particularly in a world where we know laptops catch fire due to battery heat .</tokentext>
<sentencetext>When I googled "laptop battery catches fire" I didn't see any that weren't able to be replaced by the end user.
In fact, there are many stories of battery recalls and replacement programs.And for the iPhone?My point - If you're going to make the battery a permanent fixture, you need to vet it first.
Particularly in a world where we know laptops catch fire due to battery heat.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542185</id>
	<title>Re:Hmmmm ...</title>
	<author>craagz</author>
	<datestamp>1246462500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>the cooler new iPhone 3GS F

now with a fan!</htmltext>
<tokenext>the cooler new iPhone 3GS F now with a fan !</tokentext>
<sentencetext>the cooler new iPhone 3GS F

now with a fan!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28547771</id>
	<title>That's Secret Apple Technology!</title>
	<author>Anonymous</author>
	<datestamp>1246480380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Even the Powerbook G4 back then used their casings to dissipate heat, so what's the news?</p></htmltext>
<tokenext>Even the Powerbook G4 back then used their casings to dissipate heat , so what 's the news ?</tokentext>
<sentencetext>Even the Powerbook G4 back then used their casings to dissipate heat, so what's the news?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540793</id>
	<title>Boiling eggs....</title>
	<author>bagsta</author>
	<datestamp>1246454640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>See the bright side of overheated iPhone, if you are hungry you can boil an <a href="http://en.wikipedia.org/wiki/Egg\_(food)" title="wikipedia.org" rel="nofollow">egg</a> [wikipedia.org] and eat it<nobr> <wbr></nobr>:)</htmltext>
<tokenext>See the bright side of overheated iPhone , if you are hungry you can boil an egg [ wikipedia.org ] and eat it : )</tokentext>
<sentencetext>See the bright side of overheated iPhone, if you are hungry you can boil an egg [wikipedia.org] and eat it :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540839</id>
	<title>I'm dubious</title>
	<author>hey!</author>
	<datestamp>1246454940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I mean, isn't the GPS chip running all the time to give you cellular 9-1-1 and location based services?</p><p>It's not like OEM GPS units are an exotic technology either.  You determine the thermal dissipation of the unit on the test bench just by firing it up.  This is some kind of system behavior phenomenon.</p><p>If I had to pull an answer out of my donkey I'd guess that the initial cause of the overheating is plain old CPU wattage. Normally the CPU would run throttled down, but then when you do mapping and processing GPS data it's chugging away all the time doing trigonometry -- and mobile CPUs are probably not power optimized for continual floating point operations.  And <em>then</em> some kind of thermal runaway gets triggered in some component -- possibly the backliight or battery.</p></htmltext>
<tokenext>I mean , is n't the GPS chip running all the time to give you cellular 9-1-1 and location based services ? It 's not like OEM GPS units are an exotic technology either .
You determine the thermal dissipation of the unit on the test bench just by firing it up .
This is some kind of system behavior phenomenon.If I had to pull an answer out of my donkey I 'd guess that the initial cause of the overheating is plain old CPU wattage .
Normally the CPU would run throttled down , but then when you do mapping and processing GPS data it 's chugging away all the time doing trigonometry -- and mobile CPUs are probably not power optimized for continual floating point operations .
And then some kind of thermal runaway gets triggered in some component -- possibly the backliight or battery .</tokentext>
<sentencetext>I mean, isn't the GPS chip running all the time to give you cellular 9-1-1 and location based services?It's not like OEM GPS units are an exotic technology either.
You determine the thermal dissipation of the unit on the test bench just by firing it up.
This is some kind of system behavior phenomenon.If I had to pull an answer out of my donkey I'd guess that the initial cause of the overheating is plain old CPU wattage.
Normally the CPU would run throttled down, but then when you do mapping and processing GPS data it's chugging away all the time doing trigonometry -- and mobile CPUs are probably not power optimized for continual floating point operations.
And then some kind of thermal runaway gets triggered in some component -- possibly the backliight or battery.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541659</id>
	<title>Re:I'm dubious</title>
	<author>digitalchinky</author>
	<datestamp>1246460100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The 911 GPS thing is filled with a lot of assumptions and misinformation. How 911 gets the lat and long is entirely up to the carrier. Some do it using tower triangulation, some get it from the phone itself, but the GPS chip (if the phone even has one, and not all of them do) is only activated when 911 (or 117) is dialled. GPS chips still draw too much power to have them turned on all the time. My N95 lasts about 2 to 3 hours with GPS on, about 24 hours with it off.</p></htmltext>
<tokenext>The 911 GPS thing is filled with a lot of assumptions and misinformation .
How 911 gets the lat and long is entirely up to the carrier .
Some do it using tower triangulation , some get it from the phone itself , but the GPS chip ( if the phone even has one , and not all of them do ) is only activated when 911 ( or 117 ) is dialled .
GPS chips still draw too much power to have them turned on all the time .
My N95 lasts about 2 to 3 hours with GPS on , about 24 hours with it off .</tokentext>
<sentencetext>The 911 GPS thing is filled with a lot of assumptions and misinformation.
How 911 gets the lat and long is entirely up to the carrier.
Some do it using tower triangulation, some get it from the phone itself, but the GPS chip (if the phone even has one, and not all of them do) is only activated when 911 (or 117) is dialled.
GPS chips still draw too much power to have them turned on all the time.
My N95 lasts about 2 to 3 hours with GPS on, about 24 hours with it off.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540839</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580521</id>
	<title>Re:Oh hey no problem</title>
	<author>Swift2001</author>
	<datestamp>1246726260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In fact, they're allowing you to switch the phones affected. Go to the Genius Bar. There's a reason why Apple has such high positives for customer support.</p></htmltext>
<tokenext>In fact , they 're allowing you to switch the phones affected .
Go to the Genius Bar .
There 's a reason why Apple has such high positives for customer support .</tokentext>
<sentencetext>In fact, they're allowing you to switch the phones affected.
Go to the Genius Bar.
There's a reason why Apple has such high positives for customer support.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542785</id>
	<title>Re:Hmmmm ...</title>
	<author>Sandbags</author>
	<datestamp>1246465140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And Sony, Dell, HP, Compaq, Gateway have all been immune????</p><p>No quite the opposite.</p><p>Nokia, RIM, motorolla, have also all had MASSIVE recalls.  Nearly every cell manufacturer has.  This is their 3rd device, and the first "potential" (unconfirmed) issue.</p><p>Apple's heat issues have largely been limited events, and when they have been confirmed (which does take some time and a moderate sample size), they have been completely forthcoming, and have issues easy to deal with voluntary recall programs.  In the case of my Mother's macBook Pro, they actually sent her a letter, and told her to come in as they were actually concerned it might be an issue.  For my older MacBook, I brought it in for a CD drive issue, and they replaced the motherboard, and it was OUT OF WARANTY at the time.  They even threw in the CD replacement free for my "trouble" which i fully expected to pay for even with the motherboard being replaced under a voluntary recall.</p><p>So far, i have not seen a report of an overheating phone that was not in my opinion abused.  They are not designed to run under pillows and inside insulated bags, nor are they designed to run in 100 degree summer weather in direct sunlight on a hot wooden table.  Heck, my Sprint phone actually WARPED in the heat just sitting on my dashboard.  My iPhone runs quite nice for hours there, playing music and running GPS concurrently.</p><p>If you have an issue, tell Apple.</p></htmltext>
<tokenext>And Sony , Dell , HP , Compaq , Gateway have all been immune ? ? ?
? No quite the opposite.Nokia , RIM , motorolla , have also all had MASSIVE recalls .
Nearly every cell manufacturer has .
This is their 3rd device , and the first " potential " ( unconfirmed ) issue.Apple 's heat issues have largely been limited events , and when they have been confirmed ( which does take some time and a moderate sample size ) , they have been completely forthcoming , and have issues easy to deal with voluntary recall programs .
In the case of my Mother 's macBook Pro , they actually sent her a letter , and told her to come in as they were actually concerned it might be an issue .
For my older MacBook , I brought it in for a CD drive issue , and they replaced the motherboard , and it was OUT OF WARANTY at the time .
They even threw in the CD replacement free for my " trouble " which i fully expected to pay for even with the motherboard being replaced under a voluntary recall.So far , i have not seen a report of an overheating phone that was not in my opinion abused .
They are not designed to run under pillows and inside insulated bags , nor are they designed to run in 100 degree summer weather in direct sunlight on a hot wooden table .
Heck , my Sprint phone actually WARPED in the heat just sitting on my dashboard .
My iPhone runs quite nice for hours there , playing music and running GPS concurrently.If you have an issue , tell Apple .</tokentext>
<sentencetext>And Sony, Dell, HP, Compaq, Gateway have all been immune???
?No quite the opposite.Nokia, RIM, motorolla, have also all had MASSIVE recalls.
Nearly every cell manufacturer has.
This is their 3rd device, and the first "potential" (unconfirmed) issue.Apple's heat issues have largely been limited events, and when they have been confirmed (which does take some time and a moderate sample size), they have been completely forthcoming, and have issues easy to deal with voluntary recall programs.
In the case of my Mother's macBook Pro, they actually sent her a letter, and told her to come in as they were actually concerned it might be an issue.
For my older MacBook, I brought it in for a CD drive issue, and they replaced the motherboard, and it was OUT OF WARANTY at the time.
They even threw in the CD replacement free for my "trouble" which i fully expected to pay for even with the motherboard being replaced under a voluntary recall.So far, i have not seen a report of an overheating phone that was not in my opinion abused.
They are not designed to run under pillows and inside insulated bags, nor are they designed to run in 100 degree summer weather in direct sunlight on a hot wooden table.
Heck, my Sprint phone actually WARPED in the heat just sitting on my dashboard.
My iPhone runs quite nice for hours there, playing music and running GPS concurrently.If you have an issue, tell Apple.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545085</id>
	<title>Re:should have released it in winter</title>
	<author>sexconker</author>
	<datestamp>1246472040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>But white reflects light, DOUBLING the radiation pressure!</p></htmltext>
<tokenext>But white reflects light , DOUBLING the radiation pressure !</tokentext>
<sentencetext>But white reflects light, DOUBLING the radiation pressure!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539953</id>
	<title>Obviously</title>
	<author>Rhaban</author>
	<datestamp>1246443600000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>The iphone just isn't cool anymore.</p></htmltext>
<tokenext>The iphone just is n't cool anymore .</tokentext>
<sentencetext>The iphone just isn't cool anymore.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540253</id>
	<title>Re:unable to pick up the device</title>
	<author>zeromorph</author>
	<datestamp>1246447980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Indeed it is! It changes colour - neet - and - of all colours - it turns pink, OMG! Additionally it functions as a pocket heater, who on earth could think it is a bug.</p></htmltext>
<tokenext>Indeed it is !
It changes colour - neet - and - of all colours - it turns pink , OMG !
Additionally it functions as a pocket heater , who on earth could think it is a bug .</tokentext>
<sentencetext>Indeed it is!
It changes colour - neet - and - of all colours - it turns pink, OMG!
Additionally it functions as a pocket heater, who on earth could think it is a bug.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539823</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542861</id>
	<title>"black radiates heat better"?</title>
	<author>SuperKendall</author>
	<datestamp>1246465380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So if you turn out the lights, all devices will radiate heat equally well?</p></htmltext>
<tokenext>So if you turn out the lights , all devices will radiate heat equally well ?</tokentext>
<sentencetext>So if you turn out the lights, all devices will radiate heat equally well?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28547475</id>
	<title>Anonymous Coward</title>
	<author>Anonymous</author>
	<datestamp>1246479480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>From the iPhone owners manual: "The pink color is normal. Pink indicates iPhone is done cooking. Allow iPhone to cool, then apply cocktail sauce and enjoy."</p></htmltext>
<tokenext>From the iPhone owners manual : " The pink color is normal .
Pink indicates iPhone is done cooking .
Allow iPhone to cool , then apply cocktail sauce and enjoy .
"</tokentext>
<sentencetext>From the iPhone owners manual: "The pink color is normal.
Pink indicates iPhone is done cooking.
Allow iPhone to cool, then apply cocktail sauce and enjoy.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28546401</id>
	<title>This is why I love slashdot</title>
	<author>Red Flayer</author>
	<datestamp>1246475880000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>To get "warm" with a quarter watt, <i>compare the tiny volume and tiny surface area of a typical quarter-watt power resistor</i> to an iphone</p></div></blockquote><p>The poster assumes that the reader is familiar with the size of a typical<nobr> <wbr></nobr>.25 watt resistor... and for the people who will actually read his (somewhat technical) post, he's probably right.<br> <br>Nowhere else is technical knowledge brought together with goatse and GNAA trolls so seamlessly.<br> <br>Love it!</p></div>
	</htmltext>
<tokenext>To get " warm " with a quarter watt , compare the tiny volume and tiny surface area of a typical quarter-watt power resistor to an iphoneThe poster assumes that the reader is familiar with the size of a typical .25 watt resistor... and for the people who will actually read his ( somewhat technical ) post , he 's probably right .
Nowhere else is technical knowledge brought together with goatse and GNAA trolls so seamlessly .
Love it !</tokentext>
<sentencetext>To get "warm" with a quarter watt, compare the tiny volume and tiny surface area of a typical quarter-watt power resistor to an iphoneThe poster assumes that the reader is familiar with the size of a typical .25 watt resistor... and for the people who will actually read his (somewhat technical) post, he's probably right.
Nowhere else is technical knowledge brought together with goatse and GNAA trolls so seamlessly.
Love it!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540547</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542281</id>
	<title>iPhone 3G does it too</title>
	<author>Anonymous</author>
	<datestamp>1246462860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>My iPhone 3G recently started overheating and causes the screen to go white.  It's happened twice now and just after I upgraded to 3.0.</p><p>Always when I'm using GPS.  Sounds like a more general problem then just on the new 3GS.</p></htmltext>
<tokenext>My iPhone 3G recently started overheating and causes the screen to go white .
It 's happened twice now and just after I upgraded to 3.0.Always when I 'm using GPS .
Sounds like a more general problem then just on the new 3GS .</tokentext>
<sentencetext>My iPhone 3G recently started overheating and causes the screen to go white.
It's happened twice now and just after I upgraded to 3.0.Always when I'm using GPS.
Sounds like a more general problem then just on the new 3GS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542701</id>
	<title>Re:Battery Concerns</title>
	<author>imgod2u</author>
	<datestamp>1246464720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've noticed this too. Particularly when using 3G or WiFi the battery life seems to be much worse than my older iTouch (1st gen) on WiFi. Even given the additional features and beefed up processor, the newer battery should more than compensate.</p></htmltext>
<tokenext>I 've noticed this too .
Particularly when using 3G or WiFi the battery life seems to be much worse than my older iTouch ( 1st gen ) on WiFi .
Even given the additional features and beefed up processor , the newer battery should more than compensate .</tokentext>
<sentencetext>I've noticed this too.
Particularly when using 3G or WiFi the battery life seems to be much worse than my older iTouch (1st gen) on WiFi.
Even given the additional features and beefed up processor, the newer battery should more than compensate.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540127</id>
	<title>Re:There's definately an issue of some sort</title>
	<author>Anonymous</author>
	<datestamp>1246445940000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>I had the same experience with a iPhone 3G (not 3GS) after upgrading to OS 3.0 Some stuck process drained my battery to zero in a very short period of time. I wasn't near my charger, and initially I thought that the unit had died. I've never drained the battery before, and trying to power it up in that state didn't give a response of any kind. Once I got home I was relieved when it woke up after docking it.</p><p>This is an OS issue I think, not the battery. The side effect is heat and reduced life though. I'd imagine that the thermal monitoring isn't able to shutdown the unit when it gets into that state. I wasn't handling my unit at the time so I don't know if there was heat related to the event.</p></htmltext>
<tokenext>I had the same experience with a iPhone 3G ( not 3GS ) after upgrading to OS 3.0 Some stuck process drained my battery to zero in a very short period of time .
I was n't near my charger , and initially I thought that the unit had died .
I 've never drained the battery before , and trying to power it up in that state did n't give a response of any kind .
Once I got home I was relieved when it woke up after docking it.This is an OS issue I think , not the battery .
The side effect is heat and reduced life though .
I 'd imagine that the thermal monitoring is n't able to shutdown the unit when it gets into that state .
I was n't handling my unit at the time so I do n't know if there was heat related to the event .</tokentext>
<sentencetext>I had the same experience with a iPhone 3G (not 3GS) after upgrading to OS 3.0 Some stuck process drained my battery to zero in a very short period of time.
I wasn't near my charger, and initially I thought that the unit had died.
I've never drained the battery before, and trying to power it up in that state didn't give a response of any kind.
Once I got home I was relieved when it woke up after docking it.This is an OS issue I think, not the battery.
The side effect is heat and reduced life though.
I'd imagine that the thermal monitoring isn't able to shutdown the unit when it gets into that state.
I wasn't handling my unit at the time so I don't know if there was heat related to the event.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542725</id>
	<title>Inaccurate</title>
	<author>Anonymous</author>
	<datestamp>1246464840000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>The iPhone is (rather questionably imho) written in Objective-C, which uses manual memory management and thus lets you do double frees, buffer overruns</i></p><p>If you actually knew much about objective-C you'd know that's false.</p><p>Memory management is based an retain/release model, which removes you from most of the dangers of C memory management because you are working with a higher level abstraction.</p><p>The equivalent of a "double free" is over releasing an object, which means you send a message to a dead object and the program simply crashes.  There's basically no way to corrupt the heap in Objective-C programming, because you are never doing the kinds of things that lead to that.  Even in normal C code what you postulate is insanely unlikely, as heap corruption leads to core dumps, not infinite loops.  I've done a lot of Java work too and basically the memory management dangers are very similar, the biggest problem you will have is creating a situation where you are not allowing memory to free properly when you think it shoud (which again simply does not lead to infinite loops).</p><p><i>What I suspect happens is that there's a subtle memory error in a part of iPhone 3.0 which causes some background process to start spinning inside malloc.</i></p><p>Far more likely is that some interaction with some of the new chips (say a new GPS chip with compass) that leads to it constantly consuming power when the phone thinks it's powered down.  I have not seen this issue myself with a heavy day using maps recently, but it could be in combination with something else.</p></htmltext>
<tokenext>The iPhone is ( rather questionably imho ) written in Objective-C , which uses manual memory management and thus lets you do double frees , buffer overrunsIf you actually knew much about objective-C you 'd know that 's false.Memory management is based an retain/release model , which removes you from most of the dangers of C memory management because you are working with a higher level abstraction.The equivalent of a " double free " is over releasing an object , which means you send a message to a dead object and the program simply crashes .
There 's basically no way to corrupt the heap in Objective-C programming , because you are never doing the kinds of things that lead to that .
Even in normal C code what you postulate is insanely unlikely , as heap corruption leads to core dumps , not infinite loops .
I 've done a lot of Java work too and basically the memory management dangers are very similar , the biggest problem you will have is creating a situation where you are not allowing memory to free properly when you think it shoud ( which again simply does not lead to infinite loops ) .What I suspect happens is that there 's a subtle memory error in a part of iPhone 3.0 which causes some background process to start spinning inside malloc.Far more likely is that some interaction with some of the new chips ( say a new GPS chip with compass ) that leads to it constantly consuming power when the phone thinks it 's powered down .
I have not seen this issue myself with a heavy day using maps recently , but it could be in combination with something else .</tokentext>
<sentencetext>The iPhone is (rather questionably imho) written in Objective-C, which uses manual memory management and thus lets you do double frees, buffer overrunsIf you actually knew much about objective-C you'd know that's false.Memory management is based an retain/release model, which removes you from most of the dangers of C memory management because you are working with a higher level abstraction.The equivalent of a "double free" is over releasing an object, which means you send a message to a dead object and the program simply crashes.
There's basically no way to corrupt the heap in Objective-C programming, because you are never doing the kinds of things that lead to that.
Even in normal C code what you postulate is insanely unlikely, as heap corruption leads to core dumps, not infinite loops.
I've done a lot of Java work too and basically the memory management dangers are very similar, the biggest problem you will have is creating a situation where you are not allowing memory to free properly when you think it shoud (which again simply does not lead to infinite loops).What I suspect happens is that there's a subtle memory error in a part of iPhone 3.0 which causes some background process to start spinning inside malloc.Far more likely is that some interaction with some of the new chips (say a new GPS chip with compass) that leads to it constantly consuming power when the phone thinks it's powered down.
I have not seen this issue myself with a heavy day using maps recently, but it could be in combination with something else.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540391</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540463</id>
	<title>iPhone Porn is the reason</title>
	<author>Anonymous</author>
	<datestamp>1246450740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Too Hot to handle!.</p></htmltext>
<tokenext>Too Hot to handle ! .</tokentext>
<sentencetext>Too Hot to handle!.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542491</id>
	<title>Similar on the iPhone v1</title>
	<author>lymond01</author>
	<datestamp>1246463820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I had the first iPhone and it would overheat on occasion, but I couldn't make it do it consistently.  I could be on the phone walking the dog for 15 minutes and it would be fine.  But then I could be on the phone with a friend for 5 minutes and it would be too hot to hold against my ear.  Data never seemed to make it heat up much, though playing music in my car would warm it up, but only sometimes.</p><p>The new 3G S hasn't had any heating issues, but I'm not sure I've spent enough time talking on it to say mine doesn't have a problem.</p></htmltext>
<tokenext>I had the first iPhone and it would overheat on occasion , but I could n't make it do it consistently .
I could be on the phone walking the dog for 15 minutes and it would be fine .
But then I could be on the phone with a friend for 5 minutes and it would be too hot to hold against my ear .
Data never seemed to make it heat up much , though playing music in my car would warm it up , but only sometimes.The new 3G S has n't had any heating issues , but I 'm not sure I 've spent enough time talking on it to say mine does n't have a problem .</tokentext>
<sentencetext>I had the first iPhone and it would overheat on occasion, but I couldn't make it do it consistently.
I could be on the phone walking the dog for 15 minutes and it would be fine.
But then I could be on the phone with a friend for 5 minutes and it would be too hot to hold against my ear.
Data never seemed to make it heat up much, though playing music in my car would warm it up, but only sometimes.The new 3G S hasn't had any heating issues, but I'm not sure I've spent enough time talking on it to say mine doesn't have a problem.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540143</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>El\_Muerte\_TDS</author>
	<datestamp>1246446360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My Android G1 also gets warm when using 3G or Wifi. It's warm, not hot. And it's always in the lower part of the phone (the part with the scroll wheel).</p></htmltext>
<tokenext>My Android G1 also gets warm when using 3G or Wifi .
It 's warm , not hot .
And it 's always in the lower part of the phone ( the part with the scroll wheel ) .</tokentext>
<sentencetext>My Android G1 also gets warm when using 3G or Wifi.
It's warm, not hot.
And it's always in the lower part of the phone (the part with the scroll wheel).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542171</id>
	<title>According to "experts"?</title>
	<author>Guysmiley777</author>
	<datestamp>1246462380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>The early blame seems to fall on games and GPS, resource-intensive applications that are pumping up the battery until it gets too hot to handle and eventually overheats. </i> <br> <br>What a horrible choice of words. "Pumping up" the battery? That would seem to indicate charging the battery. "Large battery drain" or "heavy power consumption", something that indicates battery use instead of charging would have made a lot more sense. Since when does "some random blogger" become an expert?<br> <br>Another gem: <i>One commenter shared this tale: "I had my iPhone under my pillow playing music through the head phones for a nap; I awoke with a sharp pain on my left arm under the pillow. I had been burned decently from the iPhone getting so hot. The phone seems to function fine though." </i> <br> <br>Try sticking a running notebook PC under your pillow and laying on it. It'll probably melt.</htmltext>
<tokenext>The early blame seems to fall on games and GPS , resource-intensive applications that are pumping up the battery until it gets too hot to handle and eventually overheats .
What a horrible choice of words .
" Pumping up " the battery ?
That would seem to indicate charging the battery .
" Large battery drain " or " heavy power consumption " , something that indicates battery use instead of charging would have made a lot more sense .
Since when does " some random blogger " become an expert ?
Another gem : One commenter shared this tale : " I had my iPhone under my pillow playing music through the head phones for a nap ; I awoke with a sharp pain on my left arm under the pillow .
I had been burned decently from the iPhone getting so hot .
The phone seems to function fine though .
" Try sticking a running notebook PC under your pillow and laying on it .
It 'll probably melt .</tokentext>
<sentencetext>The early blame seems to fall on games and GPS, resource-intensive applications that are pumping up the battery until it gets too hot to handle and eventually overheats.
What a horrible choice of words.
"Pumping up" the battery?
That would seem to indicate charging the battery.
"Large battery drain" or "heavy power consumption", something that indicates battery use instead of charging would have made a lot more sense.
Since when does "some random blogger" become an expert?
Another gem: One commenter shared this tale: "I had my iPhone under my pillow playing music through the head phones for a nap; I awoke with a sharp pain on my left arm under the pillow.
I had been burned decently from the iPhone getting so hot.
The phone seems to function fine though.
"   Try sticking a running notebook PC under your pillow and laying on it.
It'll probably melt.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28597757</id>
	<title>Re:Hmmmm ...</title>
	<author>bill\_mcgonigle</author>
	<datestamp>1246909320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>... testing anyone?</i></p><p>If reports are to be believed, probably only a dozen people inside Apple ever saw a finished part before it went public.</p><p>How much testing can really be done under such a veil of secrecy?</p></htmltext>
<tokenext>... testing anyone ? If reports are to be believed , probably only a dozen people inside Apple ever saw a finished part before it went public.How much testing can really be done under such a veil of secrecy ?</tokentext>
<sentencetext>... testing anyone?If reports are to be believed, probably only a dozen people inside Apple ever saw a finished part before it went public.How much testing can really be done under such a veil of secrecy?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28548949</id>
	<title>Re:Android G1 also heats when using GPS</title>
	<author>Anonymous</author>
	<datestamp>1246440660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>When I <b>truck</b> a lot of traffic over 3G to the G1</p></div><p>Got a great big <i>data</i> convoy? CONVOY!!</p><p>(Sorry, after that part I read the entire rest of the post in the voice and melody of the song.)</p></div>
	</htmltext>
<tokenext>When I truck a lot of traffic over 3G to the G1Got a great big data convoy ?
CONVOY ! ! ( Sorry , after that part I read the entire rest of the post in the voice and melody of the song .
)</tokentext>
<sentencetext>When I truck a lot of traffic over 3G to the G1Got a great big data convoy?
CONVOY!!(Sorry, after that part I read the entire rest of the post in the voice and melody of the song.
)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540141</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543767</id>
	<title>Re:Unfortunately not uncommon</title>
	<author>Anonymous</author>
	<datestamp>1246468260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Just so you know you can load your own software that you make onto your iPhone without Jailbraking. They allow up to a certain number of ad hoc installs (I think 200 or something like that) on any program. They do this so if you are a company and you want to make an app for internal use you don't have to post it to the app store and get approval.</p></htmltext>
<tokenext>Just so you know you can load your own software that you make onto your iPhone without Jailbraking .
They allow up to a certain number of ad hoc installs ( I think 200 or something like that ) on any program .
They do this so if you are a company and you want to make an app for internal use you do n't have to post it to the app store and get approval .</tokentext>
<sentencetext>Just so you know you can load your own software that you make onto your iPhone without Jailbraking.
They allow up to a certain number of ad hoc installs (I think 200 or something like that) on any program.
They do this so if you are a company and you want to make an app for internal use you don't have to post it to the app store and get approval.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540971</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540391</id>
	<title>Re:There's definately an issue of some sort</title>
	<author>IamTheRealMike</author>
	<datestamp>1246449780000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><blockquote><div><p>I assume it wasn't the processor, because it wasn't locked up -- so perhaps it was a modem issue.</p></div></blockquote><p>Although Apple don't want you to know it, the iPhone OS is actually a multi-tasking OS at heart, so a spinning process won't lock up the processor. It'll just keep the CPU pegged at 100\% and flatten the battery. What might cause such a thing? On Android, most of the software is written in Java so the only way to make it spin like that is to actually enter a real infinite loop. The iPhone is (rather questionably imho) written in Objective-C, which uses manual memory management and thus lets you do double frees, buffer overruns etc. A classic cause of infinite loops in C based apps is heap arena corruption - you smash the heap control structures in some way, and then malloc or free go into an infinite loop trying to find a free block. Most mallocs don't do much error checking for performance reasons. </p><p>What I suspect happens is that there's a subtle memory error in a part of iPhone 3.0 which causes some background process to start spinning inside malloc. The iPhone 3GS has a more powerful processor than its predecessor and it's possible that Apple decided (riskily imho) that it was OK if they couldn't dissipate the heat from a pegged CPU because they would try and ensure the CPU never pegged in software. For instance they might be throttling user applications (I have no evidence of that, it's just a theory). However that overlooks the possibility that their own software would accidentally peg the CPU for some time<nobr> <wbr></nobr>.... leading to the result we have here.</p></div>
	</htmltext>
<tokenext>I assume it was n't the processor , because it was n't locked up -- so perhaps it was a modem issue.Although Apple do n't want you to know it , the iPhone OS is actually a multi-tasking OS at heart , so a spinning process wo n't lock up the processor .
It 'll just keep the CPU pegged at 100 \ % and flatten the battery .
What might cause such a thing ?
On Android , most of the software is written in Java so the only way to make it spin like that is to actually enter a real infinite loop .
The iPhone is ( rather questionably imho ) written in Objective-C , which uses manual memory management and thus lets you do double frees , buffer overruns etc .
A classic cause of infinite loops in C based apps is heap arena corruption - you smash the heap control structures in some way , and then malloc or free go into an infinite loop trying to find a free block .
Most mallocs do n't do much error checking for performance reasons .
What I suspect happens is that there 's a subtle memory error in a part of iPhone 3.0 which causes some background process to start spinning inside malloc .
The iPhone 3GS has a more powerful processor than its predecessor and it 's possible that Apple decided ( riskily imho ) that it was OK if they could n't dissipate the heat from a pegged CPU because they would try and ensure the CPU never pegged in software .
For instance they might be throttling user applications ( I have no evidence of that , it 's just a theory ) .
However that overlooks the possibility that their own software would accidentally peg the CPU for some time .... leading to the result we have here .</tokentext>
<sentencetext>I assume it wasn't the processor, because it wasn't locked up -- so perhaps it was a modem issue.Although Apple don't want you to know it, the iPhone OS is actually a multi-tasking OS at heart, so a spinning process won't lock up the processor.
It'll just keep the CPU pegged at 100\% and flatten the battery.
What might cause such a thing?
On Android, most of the software is written in Java so the only way to make it spin like that is to actually enter a real infinite loop.
The iPhone is (rather questionably imho) written in Objective-C, which uses manual memory management and thus lets you do double frees, buffer overruns etc.
A classic cause of infinite loops in C based apps is heap arena corruption - you smash the heap control structures in some way, and then malloc or free go into an infinite loop trying to find a free block.
Most mallocs don't do much error checking for performance reasons.
What I suspect happens is that there's a subtle memory error in a part of iPhone 3.0 which causes some background process to start spinning inside malloc.
The iPhone 3GS has a more powerful processor than its predecessor and it's possible that Apple decided (riskily imho) that it was OK if they couldn't dissipate the heat from a pegged CPU because they would try and ensure the CPU never pegged in software.
For instance they might be throttling user applications (I have no evidence of that, it's just a theory).
However that overlooks the possibility that their own software would accidentally peg the CPU for some time .... leading to the result we have here.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541193</id>
	<title>Been there, done that.</title>
	<author>PeterChenoweth</author>
	<datestamp>1246457460000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext>How short our collective geek memories are.  This same phenomenon occurred last year when Apple released 2.0.  <br> <br>

Around August of '08 there was an outcry of users complaining about diminished battery life + hot iPhones.  Both on the then-new 3G, and on the original.  I had this problem with my iPhone 2G (the original) after installing iPhone 2.0.  My battery life went from lasting several days to barely making it through one, with the phone getting quite warm if I used it for more than a few minutes straight.  It would even stay warmer than ambient when I wasn't using it.  A sure sign that *something* was awry.  In September of '08, Apple released 2.1 and that completely solved the problem for me and many other users.  Battery life + heat levels returned to pre-2.0 levels.  Problem solved. <br> <br>

So it's entirely possible that this is some sort of software/power management issue.  And if that's the case, Apple will (ok, should) be able to fix it.  And if that *is* the case, then Apple really needs to take another look at their iPhone power management coding/testing procedures.<nobr> <wbr></nobr>;-)</htmltext>
<tokenext>How short our collective geek memories are .
This same phenomenon occurred last year when Apple released 2.0 .
Around August of '08 there was an outcry of users complaining about diminished battery life + hot iPhones .
Both on the then-new 3G , and on the original .
I had this problem with my iPhone 2G ( the original ) after installing iPhone 2.0 .
My battery life went from lasting several days to barely making it through one , with the phone getting quite warm if I used it for more than a few minutes straight .
It would even stay warmer than ambient when I was n't using it .
A sure sign that * something * was awry .
In September of '08 , Apple released 2.1 and that completely solved the problem for me and many other users .
Battery life + heat levels returned to pre-2.0 levels .
Problem solved .
So it 's entirely possible that this is some sort of software/power management issue .
And if that 's the case , Apple will ( ok , should ) be able to fix it .
And if that * is * the case , then Apple really needs to take another look at their iPhone power management coding/testing procedures .
; - )</tokentext>
<sentencetext>How short our collective geek memories are.
This same phenomenon occurred last year when Apple released 2.0.
Around August of '08 there was an outcry of users complaining about diminished battery life + hot iPhones.
Both on the then-new 3G, and on the original.
I had this problem with my iPhone 2G (the original) after installing iPhone 2.0.
My battery life went from lasting several days to barely making it through one, with the phone getting quite warm if I used it for more than a few minutes straight.
It would even stay warmer than ambient when I wasn't using it.
A sure sign that *something* was awry.
In September of '08, Apple released 2.1 and that completely solved the problem for me and many other users.
Battery life + heat levels returned to pre-2.0 levels.
Problem solved.
So it's entirely possible that this is some sort of software/power management issue.
And if that's the case, Apple will (ok, should) be able to fix it.
And if that *is* the case, then Apple really needs to take another look at their iPhone power management coding/testing procedures.
;-)</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539841
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541167
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543931
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542213
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540429
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540683
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540841
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28554921
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540141
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542219
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541525
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580509
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539823
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540615
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580443
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541121
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539823
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540073
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541745
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540695
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541611
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540619
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540513
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545527
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540637
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540141
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28548949
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539985
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540575
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580521
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541747
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540547
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28546401
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543247
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540971
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543767
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542861
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542435
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540839
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541659
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542069
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539985
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540209
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540391
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542725
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545773
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541457
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540839
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542635
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540035
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543573
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28597757
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540199
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539953
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540147
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541509
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542659
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542701
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28554873
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542185
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540033
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541519
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545085
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545445
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543389
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_65</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540631
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540633
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540127
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541173
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542785
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540143
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28555715
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540971
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542235
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539953
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540211
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540979
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28546917
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_64</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540079
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542231
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540141
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543419
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539823
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540253
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541917
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540189
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540055
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_2356228_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28547383
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539841
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541167
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539913
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543931
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545527
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542701
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541525
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539823
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540073
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541745
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540253
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540615
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539957
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540931
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540033
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541519
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539927
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539953
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540211
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540979
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540147
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539821
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540095
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541121
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540171
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540411
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542861
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28547383
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541747
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28554873
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542659
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580443
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545085
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540035
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540055
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540695
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540475
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542035
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539915
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540127
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541173
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541457
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540079
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540391
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542725
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545773
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540683
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540439
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542171
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539831
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540199
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580521
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540633
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542213
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541509
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542491
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539851
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540513
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542185
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28545445
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540485
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542435
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541611
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540841
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28554921
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543247
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541917
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542231
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28597757
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543389
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540631
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543573
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539985
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540209
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540575
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540189
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540637
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542785
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540971
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543767
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542235
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28558623
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539827
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28546917
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28555715
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540619
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540141
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542219
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28543419
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28548949
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540839
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542635
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28541659
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28542069
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540143
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540153
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28580509
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540429
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540547
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28546401
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540589
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540007
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539967
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28540793
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539855
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_2356228.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_2356228.28539925
</commentlist>
</conversation>
