Hey everyone,
I seem to be having an issue with the battery temperature sensor. It will always say 30 Celsius even if I can feel the heat of the battery through the case. Is this a known issue with the tabs? Using sensor test, I can see that a temperature sensor works and is constantly updating, showing temps from 30C to 40C. I'm running stock rooted EC02 with KhasMek Voodoo Plus OC 1.4Ghz.
Thanks for your help.
xz124 said:
Hey everyone,
I seem to be having an issue with the battery temperature sensor. It will always say 30 Celsius even if I can feel the heat of the battery through the case. Is this a known issue with the tabs? Using sensor test, I can see that a temperature sensor works and is constantly updating, showing temps from 30C to 40C. I'm running stock rooted EC02 with KhasMek Voodoo Plus OC 1.4Ghz.
Thanks for your help.
Click to expand...
Click to collapse
There are 2 main reasons for a constant temperature:
1- A third-party battery is used which have its temperature sensor removed, you will usually see 0.1 variations, like 30.0 and 30.1 at all times. or more often 25.0 and 25.1 (not sure why though).
2- the ROM or kernel is broken with regards to providing temperature to battery apps. Battery apps get temperature from Android OS using well documented API, which have not changed since the very beginning of Android. See here for more information about the API: http://developer.android.com/reference/android/os/BatteryManager.html
Unfortunately it seems to affect a few ROMs now-a-days.
EDIT: Are you using a S3 with CM-based or OMNI (AOSP-based) ROMs?
Related
I have been using setiron's reoriented kernel for awhile now with the Voltage control app set at -75mV for 100, 200, & 400mhz and -50mV for all other frequencies. I am not having any stability issues and the voltages are sticking after reboot. However, I was expecting a pretty significant increase in battery life due to the undervolting and I have seen next to nothing. Battery life is not bad by any means but in real world use is pretty comparable to what I was getting at stock voltage.
people seem to be reporting really big increases in battery life, so I'm a little confused. have I not UV'd by enough? if that were the case I would expect to see at least some battery improvement.
I wiped battery stats/recalibrated the battery when I flashed. I do have BLN enabled, but my understanding is that this causes a really small amount of battery drain. any thoughts?
How much % of battery you loose after night|?
while idle with the screen off (background data enabled) I lose about 1-2% per hour. I lost 10% overnight most recently and I was asleep for 7 hours. that is about the same that I was getting at stock voltage.
all i can sya, is thst you losing not many %
tehsam said:
while idle with the screen off (background data enabled) I lose about 1-2% per hour. I lost 10% overnight most recently and I was asleep for 7 hours. that is about the same that I was getting at stock voltage.
Click to expand...
Click to collapse
If you are in a weaker signal area, then the cell phone radio is going to work just as hard no matter what the CPU voltage.
tehsam said:
I have been using setiron's reoriented kernel for awhile now with the Voltage control app set at -75mV for 100, 200, & 400mhz and -50mV for all other frequencies. I am not having any stability issues and the voltages are sticking after reboot. However, I was expecting a pretty significant increase in battery life due to the undervolting and I have seen next to nothing. Battery life is not bad by any means but in real world use is pretty comparable to what I was getting at stock voltage.
people seem to be reporting really big increases in battery life, so I'm a little confused. have I not UV'd by enough? if that were the case I would expect to see at least some battery improvement.
I wiped battery stats/recalibrated the battery when I flashed. I do have BLN enabled, but my understanding is that this causes a really small amount of battery drain. any thoughts?
Click to expand...
Click to collapse
Battery drain can be a symptom of i9000 kernel and captivate modem.
Changing the modem and keeping 850mhz is a multi step process. I tried the kernel you are talking about but it's over rated.
if you want battery life flash a 2.1 rom and use unhelpful's kernel, 1.4.1 was the most stable on my phone but it doesn't have voodoo. 1.6 has voodoo and 1.7 has voodoo and clockwork recovery if I remember right. But I had random restarts, others did not report the same problems so who knows.
I would wait for captivate froyo source to drop. I'm getting decent life with cognition and no undervolting.
Edit after reading the whole thread your battery life seems normal, I don't see any problem, you can try more undervolt but test the phone completely. Make sure it doesn't freeze randomly, or on shutdown. Also test it with the charger plugged in, extra heat from the battery charging can affect stability.
Sent from my SAMSUNG-SGH-I897
Hi all,
I've recently installed Rocket ROM v13 along with AbbyssNote 2.6, but I'm experiencing frequent phone freezes and a abnormal warm device.
I've tried setting the voltages back to standard values, but that hasn't fixed the problem.
The freezing happens the most when launching the browser and less frequently when playing games.
Is there a way to test what frequencies work with what ideal voltages? And getting rid of the heat would be nice too Thanks in advance
The heat is probably mostly from the Wifi problem. You may also have trouble with CPU being overactive.
Leave the voltage alone as it will cause stability problems. Its just a bandaid and not the real solution to your heat issue.
What is the room temp and battery temp of your phone?
Sent from my GT-N7000 using xda premium
My battery ranges from 40-50C when on idle use. The room is around 20C.
The phone gets really hot on the top 20% whenever I use it for a decent amount of time.
I currently have the phone on default settings. From 200-1400 Mhz and the voltages found here.
This heat is something i am battling with also, tried many things even reducing volts does not seem to help.. i think it's just the way it behaves.
Some background on the Nexus 6 that I've owned for 5+ years. Battery life was fairly stable for ~3 years. There were occasions where I played Clash of Clans while quick charging that the phone got scorching hot. So hot that I couldn't hold it against my skin for more than a few seconds. After regularly doing that for a while, the battery degraded to less than half its original capacity.
I bit the bullet and bought a replacement battery. I made sure to get a good quality one, not a cheap Chinese knockoff. I tested the capacity of the new replacement battery and it was close to the original battery's new capacity. However after about a year of clashing and quick charging the phone to stove-top temperatures, the replacement's battery capacity degraded severely.
My friend's N6 suffered similar battery degradation during a road trip while he was charging it in the car, using map GPS, and playing music. The phone got so hot he had to hold it in front of the AC to keep it running.
I like the screen enough to where I'm considering replacing the battery again. However this time I want to prevent it from overheating. Is there a way to disable quick charging in the firmware? Which firmware aggressively throttles CPU to keep temperatures down?
chefp said:
Which firmware aggressively throttles CPU to keep temperatures down?
Click to expand...
Click to collapse
Not shure if this is what you want, but I implemented power profiles in LineageOS 15.1 and 16.0.
You could use the Effcient or Power Safe profile in situations like you mentioned.
Why not simply use a power adapter that cannot deliver much power?
And not wireless charging - that always creates more heat.
Elektroschmock said:
Not shure if this is what you want, but I implemented power profiles in LineageOS 15.1 and 16.0.
You could use the Effcient or Power Safe profile in situations like you mentioned.
Click to expand...
Click to collapse
That sounds great. My N6 is currently running Lineage 14 and I only see Power Save. Is the Efficient profile better? Power Save makes the phone run quite slow. It'd be nice to have a profile that adjusts performance based on temperature. When it's cool it runs faster, and as it heats up it slows down.
runekock said:
Why not simply use a power adapter that cannot deliver much power?
And not wireless charging - that always creates more heat.
Click to expand...
Click to collapse
I use a standard 10W charger at home (5v @ 2.x A). However when I'm on the road, visiting friends or traveling, I may have to borrow someone's charger, and it might be a fast charger. It would be better if the phone throttled its charge rate based on temperature.
chefp said:
That sounds great. My N6 is currently running Lineage 14 and I only see Power Save. Is the Efficient profile better? Power Save makes the phone run quite slow. It'd be nice to have a profile that adjusts performance based on temperature. When it's cool it runs faster, and as it heats up it slows down.
I use a standard 10W charger at home (5v @ 2.x A). However when I'm on the road, visiting friends or traveling, I may have to borrow someone's charger, and it might be a fast charger. It would be better if the phone throttled its charge rate based on temperature.
Click to expand...
Click to collapse
Oh I can't remenber what the Profiles where on 14.1. It's too long ago and 14.1 is far outdated. Profiles in 15.1 and 16.0 are totaly different to 14.1.
I guess a profile based on temperature wouldn't work properly, but we already have thermal limiting. That means the cpu / gpu is throtteld if a certain temperature is reached.
The charging rate is already based on temperature. But fastcharging is always generating more heat then normal charging. If you would limit it to the same temperature levels then standard charging it wouldn't be fast charging.
Elektroschmock said:
Oh I can't remenber what the Profiles where on 14.1. It's too long ago and 14.1 is far outdated. Profiles in 15.1 and 16.0 are totaly different to 14.1.
I guess a profile based on temperature wouldn't work properly, but we already have thermal limiting. That means the cpu / gpu is throtteld if a certain temperature is reached.
The charging rate is already based on temperature. But fastcharging is always generating more heat then normal charging. If you would limit it to the same temperature levels then standard charging it wouldn't be fast charging.
Click to expand...
Click to collapse
Thanks for the info. Is there any way to disable fast charging via firmware, or is that locked in by the hardware?
chefp said:
Thanks for the info. Is there any way to disable fast charging via firmware, or is that locked in by the hardware?
Click to expand...
Click to collapse
Could be limited in firmware but I guess you have to do it yourself.
Elektroschmock said:
Could be limited in firmware but I guess you have to do it yourself.
Click to expand...
Click to collapse
Would I need to build a custom kernel, or could I send commands to a device in /proc to disable fast charging? I do app development but not familiar with the inner workings of this in particular.
Thanks bud
chefp said:
Would I need to build a custom kernel, or could I send commands to a device in /proc to disable fast charging? I do app development but not familiar with the inner workings of this in particular.
Thanks bud
Click to expand...
Click to collapse
Kernel needs to be changed
This Nexus 6 has been running LineageOS 16 for the past 6 months and the power profile is vastly superior to both Lineage 14 and stock ROM. Great work @Elektroschmock on the improved power profiles.
I'm sure there's a custom kernel out there that will let you manually set the thermal throttle temperature. They really pushed the 28nm process to the limit on the Nexus 6 the clock speed of the CPU is 2.7ghz that probably explains why the phone gets so hot when you play Clash of Clans. I don't know what the Krait 450 cores equates to but most of Qualcomms quad core CPUs on 28nm are maxed at 1.4ghz. I'd set the CPU clock speed to 1.8ghz max and lower the graphical settings in the game that should help your heating issues.
Look guys just this year I realized what's causing the Nexus 6 to overheat soo bad look at these pictures in the link below it's because Google was Soo stupid enough to put the CPU right under the battery actually the battery is right on top of the CPU I'm like why the hell did they built the phone like this. If the CPU was far away from the battery the device would not get sooo hot and causing the battery degrade quickly because of all that heat.
https://www.ifixit.com/Teardown/Nexus+6+Teardown/32877
Hello, I have noticed that whenever I remove the charger from the phone after a full charge, the CPU stays idle at 1.04 and 1.06 for big cores instead of 576 and 710. It is fixed after a reboot.
Can anyone else confirm and report back the bug?
10.2.2.26 official global rom.
MysteriousStranger said:
Hello, I have noticed that whenever I remove the charger from the phone after a full charge, the CPU stays idle at 1.04 and 1.06 for big cores instead of 576 and 710. It is fixed after a reboot.
Can anyone else confirm and report back the bug?
10.2.2.26 official global rom.
Click to expand...
Click to collapse
I can confirm that the bug appears ONLY when I use fingerprints for unlock. When I delete all fingerprints, it is gone. (and in addition, still present in 10.2.28 EEA)
MysteriousStranger said:
I can confirm that the bug appears ONLY when I use fingerprints for unlock. When I delete all fingerprints, it is gone. (and in addition, still present in 10.2.28 EEA)
Click to expand...
Click to collapse
This explains why I got better battery hours after I deleted fingerprints! Not that it was bad before, but now it's ridiculously good!
I don’t think this a bug, it probably must be this way in order to wake up screen just by putting the finger on the scanner.
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
kingbasescu said:
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
Click to expand...
Click to collapse
This summer when I started to get the pocket photos, before the .27 was released (yes I was among the ones that got it before it was redrawn) I deleted the fingerprints to get rid of the pocket activity due to the non-existing pocket mode. As .27/.28 came with pocket mode I started to use fingerprint again but discovered that face unlock that I had been using was far more convenient and suited me better despite the somewhat lower security rating. I don’t use Gpay, and do not keep top secret stuff on my phone so I’m happy being rid of the fingerprint sensor. The sensitive economic things are protected by pin-code anyway.
So it was not battery time that drove me to ditch the fingerprint sensor, that extra battery time just came as added value for me!
kingbasescu said:
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
Click to expand...
Click to collapse
If you notice, the CPU frequency increase occurs randomly after a period of time, not as soon as you turn on the phone, which seems like a bug to me. In addition, the frequency does not settle down again, leading to less standby time available. So I don't really understand how an active fingerprint sensor affects the CPU frequency after a while, and not since the boot.
gerhard_wa said:
This explains why I got better battery hours after I deleted fingerprints! Not that it was bad before, but now it's ridiculously good!
I don’t think this a bug, it probably must be this way in order to wake up screen just by putting the finger on the scanner.
Click to expand...
Click to collapse
If that was the way to be, the frequency should be that high even right after booting.
MysteriousStranger said:
If that was the way to be, the frequency should be that high even right after booting.
Click to expand...
Click to collapse
No, that does not have to be true. I can think of some reasons why CPU speed can't slowdown in order to instantly start the scanner, like for example the more services and apps are started the more CPU power is needed to make the scanner snappy enough. So that may explain why right after boot the CPU may be able to enter a lower idle state. It is in fact true that if you turn off the fingerprint reader you will not have the higher speed at idle state at all, I tested this.
Perhaps there will be a new firmware with a somewhat slower response to the fingerprint scanner that allows the CPU to enter the lower idle state to save battery power. Who knows!
I noticed this as well right from the first firmware update I used (EEA). It's been fixed after upgrading to Android Q's beta modified by Xiaomi.eu, but I don't see much, if any, improvements in battery life, while also witnessing a giant storage performance regression. Hella disappointed.
gerhard_wa said:
No, that does not have to be true. I can think of some reasons why CPU speed can't slowdown in order to instantly start the scanner, like for example the more services and apps are started the more CPU power is needed to make the scanner snappy enough. So that may explain why right after boot the CPU may be able to enter a lower idle state. It is in fact true that if you turn off the fingerprint reader you will not have the higher speed at idle state at all, I tested this.
Perhaps there will be a new firmware with a somewhat slower response to the fingerprint scanner that allows the CPU to enter the lower idle state to save battery power. Who knows!
Click to expand...
Click to collapse
I get your point but the fact is that in never goes into these lower frequencies again, even after unlocking the phone and idling with screen on, which is strange. I don't get it, really. Plus, you are not able to see in real tilme what process is hooking up CPU resources, as you could normally do in older android versions by using an app.
Ok, if the frequency never locks in the high range again and the scanner starts just as snappy I guess you are right that it must be a bug.
Skickat från min MI 9 via Tapatalk
I disabled fingerprint auth, but I don't seen any improvements in battery life.
I notice it on mine as well right now, small cores sitting at 1036 MHz and big ones+super one at 1056 MHz. Can't really put my finger on what triggered it as I've been using the FP sensor all this time and I've checked many times and the cores were at normal clocks (576, 710 and 825). I killed all running apps but it still sat like that until I restarted... at least now I can understand why sometimes my overnight consumption goes from 1% up to 5% even though I always close/kill all apps.
kingbasescu said:
I notice it on mine as well right now, small cores sitting at 1036 MHz and big ones+super one at 1056 MHz. Can't really put my finger on what triggered it as I've been using the FP sensor all this time and I've checked many times and the cores were at normal clocks (576, 710 and 825). I killed all running apps but it still sat like that until I restarted... at least now I can understand why sometimes my overnight consumption goes from 1% up to 5% even though I always close/kill all apps.
Click to expand...
Click to collapse
Try rebooting your device and you will see what the actual idle frequencies should be, then monitor it for a day or two! Can't find what triggers it but It's bugged for sure.
apoklyps3 said:
I disabled fingerprint auth, but I don't seen any improvements in battery life.
Click to expand...
Click to collapse
Reboot your phone after disabling it, otherwise the frequencies stay the same
Is there anything I can do on a new galaxy note 4 to prevent the emmc issue happening in the first place?
There was some talk about preventing overheating?
ghostwheel said:
There was some talk about preventing overheating?
Click to expand...
Click to collapse
Do I need to lower the cpu ghz? Or run some kind of app or program?
Redrainz said:
Do I need to lower the cpu ghz? Or run some kind of app or program?
Click to expand...
Click to collapse
It might help to lower the CPU speed, but you need access to root and an app to tweak the values.
Avoid gaming which is very demanding on GPU and avoid gaming for long periods of time.
Search also in the Snapdragon forum a good kernel.
Also turn off the fast charging, this can heat too much the phone.
I created a script here. It works very good, it monitors the battery temperature AND all the CPU cores temperatures, and will automatically throttle the phone if temps are too high. You can even kill some apps if the temps are to high (not yet implemented).
The difference with Samsung DVFS or integrated temperature management of kernels is that this one monitors almost all CPU sensors and also the battery, all in complete combination, and it can be easily tweaked (rather than modding a kernel). No battery hog. You can enable USB fast charge, game, etc it will still prevent overheating.
Here is the solution to eMMC error
Hello everyone, I was pretty tired of the eMMC error, and I created a script that completely annihilate this error. This error is due to the phone heating up, and the fact that custom kernels (maybe even the original kernel) don't read the...
forum.xda-developers.com