Has anyone seen an issue with the hardware temperature sensor reading being incorrect? Mine shows about 8c when sitting idle for a while with room temperature at 22-23c. It seems about 14c too low. Possible software issue??
Related
hello i got an optimus one...
ok ther is not a cpu temperature sensor.
but my battery report 2.3 °C .... is strange
ther is some app that correct read battery temperature on p500?
tnx
try Elixir
i have try
elixir report battery 2.5 °C
i have trai stock 2.2 , void and devoid rom and i have the same error...
is my battery fault?
Why do you want to know the battery's temperature ?
why not? are your battery temperature sensor working?
Not working here either
From what I've seen in the past month since I have this phone, nobody is able to get a correct reading of their battery temperature, no matter what application they used. The LG Optimus One always reports the temperature in the range of 2.x - 3.x degrees Celsius.
So, scoppyxda, your phone and battery are actually fine, don't worry. I hope this issue is fixed with the next Android version (2.3).
everythin reports it wrong except batteryminder..search for it in the market
I guess that the real temp is divided by a factor of 10. I say "i guess" because when i do something power hungry (like listening to streaming radio) the temp raises to 3.8 and the phone bak is quite hot.
I think it shows temp in deg. Fahrenhiet by default and app has to change it to deg. celcius.
Mik can fix this 5 mins if he spends time
I played with this a while today - I tried to multiply temp by 10 and voltage by 1000 in battery driver.
For voltage, it worked (see screenshot). When I tried to multiply temp by 10, apps showed it correctly, but android yelled that battery is overheated. So, android API gives wrong values to applications?
Make the api assume that it's normal ;p
Maybe the fahrenheit temp is actually the celsius temp.
And the celsius temp is the wrong temp.
I think it's...
Correct Values
While using myPhoneExplorer (usb connection) i get more realistic values. The monitor gives me figures in the range of 23-28 deg Celsius.
moses1202 said:
Maybe the fahrenheit temp is actually the celsius temp.
And the celsius temp is the wrong temp.
I think it's...
Click to expand...
Click to collapse
It isnt, battery driver returns value in celsius, fahrenheits are calculated from it by android.
I've posted the same question in the void forum (which is the ROM i'm currently using) it seems to be a problem with the model of the phone itself. So everyone will have the same results. I was told to just multiple the value by 10 to get the accurate degree.
All application show wrong reading in temp it show abot 3.5 degree Celciuss and it's just not real..
Why >? how to fix that ?
The phone does not have a thermometer (Would be cool though) so you just need to specify the correct location but turning on GPS and Wireless network locations. If the correct location is set, there is nothing to do except for obtaining the temperatures from the server you determine your temperatures.
He is talking about CPU and battery temperature sensors. Mine doesn't work neither. Seems that only works in Fahrenheit.
I don't know how to fix.
Senate from my LG-P500h using XDA App
The fault is with the phone. When using certain battery apps, you're supposed to multiply the degrees by 10 to get the actual figure. So 3.5C = 35C
you do the same with 'v' except use 1000 so it'l be 4.000
and why exactly do it do that?, from what i've expirienced i figured it's a hardware problem, cuz i tried a lot of software modifications and got the same temperature readings.
Hello,
I got an s4 that got water damage, I only knew after buying it. Now, I have a "charging paused battery temperature too high" message. I have tried changing the flex cable, it doesn't work nor changing the battery. The phone battery sensor show temperatures ranging from 70 to 80 which is exaggerated. I looked for an app that would allow me to offset the temperature by -30 degrees Celsius, with no luck.
Looking at the Android SDK I realized that the battery info could only be extracted as a constant. I'm guessing it is controlled by the kernel. However I came across an interesting document on how to configure the battery service for Android X-86.
on /sys/class/power_supply/ there are files that are used by the SDK in order to provide information (the constants mentioned above). That is if I understood everything correctly.
Anybody knows how I could modify file systems to offset the temperature? the problem might be on the motherboard, I don't want to change it.
thank you.
Hi,
since I updated my Z2 (D6503) to LP 5.0 my phone is heating pretty much. After 10 min. of using (doesn't matter how) temp. foes up to 38-39 degrees of celsius, and after using for a while like an half hour, it goes even up to 41-42 degrees (but it is also very very hot in room in which I use it).
So, I just wanted to hear your opinions about this, is it normal, do you have the same issue and can it be corrected somehow?
That's all, thanks in advance to all.
Mine's CPU almost hits 70 degrees celsius. Your temps must be battery temps, cause mine are the same.
38-42° Celsius? You mean Battery temperature right? My phones CPU was about 58-66°C after installing 5.1
Is there any possibility of a DC dimming implementation for the Pixel series? My PWM sensitivity has gotten so severe I’m basically limited to IPS screens or AMOLED screens with DC dimming.
I would happily pay for a solution, I just wonder if it’s at all possible on Pixel 5/6/6 Pro with a new ROM maybe?
Not for Pixels apparently.
However quit a few do have it.
edit:
Lol, scrap Samsung as it's modulating at 256hz apparently.
I don't notice it but you very well might.
I would like to see some solution for Pixel's 6 PWM as well.
I have also tried multiple apps. They help a little, but the issue with Pixel 6 is that it flickers even on 100% brightness.
I do wonder if it it even remotely possible to force the device to DC dimming or there are HW barriers.
DC dimming is really not DC dimming -- its not technically feasible. Its just cranking up the PWM frequency past some threshold where the circuit capacitance is high enough to filter out the flickering.
If you want DC dimming, you need a linear regulator on every sub-pixel.
96carboard said:
DC dimming is really not DC dimming -- its not technically feasible. Its just cranking up the PWM frequency past some threshold where the circuit capacitance is high enough to filter out the flickering.
If you want DC dimming, you need a linear regulator on every sub-pixel.
Click to expand...
Click to collapse
That appears to be true. Some were showing scope traces of DC back in 2019 for AMOLED display phones but have since discretely removed those images
A big obstacle to implementing is it would skew the color accuracy badly. The OLED pixels are calibrated at a fixed current and to regulated their intensity level their duty cycle is varied. With DC the calibration is lost because their light output is different at every voltage level, it's not linear. That destroys color and especially gamma calibration/accuracy. Variable refresh rate displays are already horrors to calibrate. DC dimming would add another variable. The QC of the pixels would need to be tighter leading to more rejected displays during manufacturing and increase the cost as well potential returns.
One thing that might help is to turn off animations which I never use. I never have noticed flickering even when I look for it at 60hz. Operate at a comfortable brightness level (I never use the lowest setting, it's simply too low except when I'm doing prolonged downloads, etc and need to monitor it). Use manual brightness control to decrease eye fatigue and strain.
Increasing refresh rate may also help.
Avoid using under pulse modulated LED lighting, try a incandescent light source.