Wrong/impossible temperature reported

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Having the app installed and running

What is the expected outcome? What happens instead?
I expect a temperature higher than ambient room temperature. I get one close to 
freezing (right now, 2.8 degrees Celcius)

What version of the app are you using?
4.0.3

Which device are you using?
LG Optimus T (P509)

Which carrier are you using?
Tmobile

Which version of Android are you using?
2.2 (stock) 

Please provide any additional information here:
Others have reported similar problems @
http://forum.xda-developers.com/archive/index.php/t-937683.html

Original issue reported on code.google.com by alexst...@gmail.com on 5 Sep 2011 at 10:01

[GoogleCodeExporter]

This is almost certainly caused by your device reporting the temperature as the 
integer number of degrees Celsius rather than as the integer number of tenths 
of degree Celsius as it should.

I'll work around this by having the app assume that if the temperature reported 
is less than [something around 70] it is meant to be whole degrees rather than 
tenths of degree.  This will fix the temperature reporting in both Celsius and 
Fahrenheit, but you'll have a larger step size of 1°C (1.8°F) until such a 
time as your device gets a ROM update to fix the issue.

In the mean time, just view that 2.8 as a 28 until I get the fix out.

Original comment by andr...@darshancomputing.com on 5 Sep 2011 at 10:35

• Changed state: Accepted

[GoogleCodeExporter]

Sounds like a smart workaround. Thanks for your fast response!

Original comment by alexst...@gmail.com on 6 Sep 2011 at 1:29

[GoogleCodeExporter]

Having given this more thought, I've changed my mind about the workaround.

I really didn't want to clutter the UI with an option that would only be useful 
to a very small percentage of users, which is why I was trying to come up with 
an automatic workaround.  Just a small internal change, and having the app 
automatically detect when it needs to interpret the number differently was very 
appealing.  It's summer here, so I thought, "When is the last time my battery 
was below 7°C?  Never."  But in reality it isn't that unusual.  It looks like 
most phones have operating temperature lows of 0°C or lower, and I'm sure many 
phones do get that cold in the winter.

My idea would have been a nice easy workaround if it were literally never going 
to happen that a device gets below 7°C, but that's just not the case.  The 
result would be my app incorrectly reporting temperatures on correctly 
functioning devices when they were cold, and that's worse than the current 
situation.

So I guess I'll have to add an option to multiply the Celsius temperature by 
10, but that's frankly a low priority right now.

Original comment by andr...@darshancomputing.com on 9 Sep 2011 at 8:35

• Added labels: Priority-Low
• Removed labels: Priority-Medium