Related
Hi, first to defend myself, I did search and found that everybody says good things for every kernel. So every kernel is best for Stock ICS?
I got confused. Yes I'am total noob and recently learned how to root and flash custom rom's.
I just want to hear your opinion for best kernel running on Stock ICS.
I need kernel that is good for the battery but also snappy for the system. I don't play games and I use my phone for calls, reading news, working on excel files, google maps, mail and taking pictures.
My phone is Nexus S GT-I9020T on Wind network.
IMO ezekeel kernels
Has lats of featured including voodoo color
http://forum.xda-developers.com/showthread.php?p=20520270
Sent from my Nexus S using xda premium
Thank you. Is this kernel stable?
Im just trying to set it up as we speak, will let you know how stable it appears once I figure it out
Stuck on trying to flash an unsecure boot image at the moment.
*shrugs* The stock kernel?
Unless you want the functions third party kernels bring to the table, I don't see a good enough reason to swap the stock kernel for another.
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Just managed to get ezekeels CFS on there and I get the reboot bug after going to standby.
Looking for updates but the thread is huge. Yet to try BFS.
darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Click to expand...
Click to collapse
You can try and turn off deep idle for your reboots.
Solves the problem 99% of the time (totally made up stat that could actually be true)
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
darko.baruh said:
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Deep idle gives more battery time under certain conditions (screen off but not completely idle, playing music for instance). It won't really give you more battery time if your phone is actually idle with the screen off.
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel.
Click to expand...
Click to collapse
Same here but not bad at least for me just one reboot since i installed yesterday when he posted. 2.1 kernel I never got any reboots
Sent from my Nexus S using xda premium
darko.baruh said:
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
Click to expand...
Click to collapse
The first post that you linked actually just confirms what I said.
Ezekeel said:
Since this is just theory and Morfic noted that his experience seems to indicate otherwise and that limiting the CPU frequency does actually decrease the battery drain, I put this theory to the test and logged the battery charge over 10h of FLAC playback in Airplane mode with the screen switched off.
Click to expand...
Click to collapse
1) Playing FLAC (not idle)
2) Screen off
Pre-requisites are met.
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
darko.baruh said:
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
Click to expand...
Click to collapse
Deep idle only shows savings if there is tasks running while the screen is off VS the same situation without deep idle.
So for someone doing commuting (like simms22 for example) and listening to music for around an hour, they'll lose less battery with deep idle than without.
You won't actually save battery if your phone is actually idle with deep idle enabled.
It's not some kind of magical function that makes your phone use less battery doing tasks with the screen on, deep idle disables certain components of the phone while executing tasks with the screen off, instead of having it "at full speed" as if the screen was on.
Now I understood. Thank you very much.
darko.baruh said:
Now I understood. Thank you very much.
Click to expand...
Click to collapse
No problem. I think Deep Idle is probably the mod by Ezekeel surrounded by the most misconceptions.
Most new users want it absolutely but don't seem to know why.
On His Glados kernel I noticed that Android OS was using 20%-21% of the battery and on the stock kernel 30%-31%.
Android System was using around 14% and on the stock around 19%.
Ok, have you decided to give the Glados 2.2 another go? I believe I have finally tweaked it so that it is stable for me.
Before I was getting restarts within 30 seconds of the screen turning off. I have cornered this (on my phone at least) to a problem with NSTools auto-setting the lower frequency to 100mhz. Changing it back to 200mhz and I have yet to see the system restart itself. Im not overclocked, because I dont see the point as everything is fairly snappy with this new kernel. I dont really play games on it so Im not fussed.
I did used NSTools and the frequency was set to 200mhz and I had system restarting on screen off. Using stock ICS with Glados 2.2
Also I had green annoying flickr on locking and unlocking the screen.
MIT student proves by A + B that T-Mobile G2x has hardware issues related to overheating / shutdown / battery
http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
Let's share this and be social.
Here are some other references for this same post.
#OccupyLg
LG: http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
XDA-Developers: http://forum.xda-developers.com/showthread.php?t=1433445
T-Mobile: http://support.t-mobile.com/thread/16431
I would assume a hot reboot would work as well if you don't want to install an app killer
Sent from my LG-P999 using xda premium
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
jcbofkc said:
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
Click to expand...
Click to collapse
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
psychoace said:
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
Click to expand...
Click to collapse
If (big if) the overheating observed is due to heat from the battery charging leaching into the phone, wouldn't a quick and easy fix/test be a piece of aluminum foil between the battery and the phone?
Sent from my LG-P999 using Tapatalk
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Prod1702 said:
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Click to expand...
Click to collapse
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
FYI if it does it on all roms then its a hardware issue and software change wont fix it...
Sent from my LG-P999 using xda premium
I also had the dreaded sod at least once every couple of days.
However, after I installed eb kang with faux oc/uv profile with set cpu, I have had no problems since.
I guess its ymmv...
Sent from my LG-P999 using XDA App
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
gggirlgeek said:
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
Click to expand...
Click to collapse
I don't think anyone is saying this problem effects everyone. It's just with all the bad units out there with this problem, this is probably why it's happening. Right now I'm trying to run some profiles in setcpu to see if it improves my phones sleep. It's only been one day so I will see by the end of the week how this fares
Sent from my LG-P999 using xda premium
Cm7, morfic Trinity kernel, go launcher ex oc'ed to 1.4 ghz. Perfect! No issues!
Sent from my LG-P999 using xda premium
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
Posts like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Prod1702 said:
Things like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Click to expand...
Click to collapse
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
mt3g said:
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I think the term overheating is thrown around too loosely here without more of a description. There's the type of overheating that causes our phones to shut off and stay off until the battery is pulled. There is also the type of overheating that occurs when you plug in an HDMI cable, which may or may not cause your device to die.
I'd assume those two types of overheating are the same, as they result in the same thing: dead device that won't turn on without a battery pull. And the phone gets hot as fsck. Hot as in you'd be scared to keep it in your pocket because (1) it'll burn your leg and (2) you are scared the battery will explode.
Those two types are overheating are different from your phone merely heating up upon use. I'm talking about charging the phone while navigating via GPS at full brightness or playing a graphically intense gaming. That magnitude of that heat is normal. And I'm guessing that's what all your devices have experienced.
And as all the devices get thinner, that battery's going to sit closer and closer to your hand, which equals more heat. And as the glass technology gets thinner (gorilla glass 2.0), your face will probably feel the heat to a greater degree as well.
---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
It's true, it's not android, it's LG.
And to all the people thinking that undervolting and underclocking your phone will fix everything, it won't. Android already underclocks the CPU when it's not in use. SetCPU does nothing in this instance. The only instance they'll see a difference is if they have some sort of rogue app that's maintaining a wake lock. You just can't beat terrible design (referring to the MIT guy's findings). Sometimes it'll work, sometimes you just lose.
LG majorly screwed up with this and I hope that their mobile efforts in the future fail for their lack of follow through.
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Just wanted to say that this thread has been really helpful to me. Every time I've flashed a custom kernel, my phone has always, within the first 2 nights of installation, turned off in the middle of the night while on the charger. So I've always been stuck with the stock kernel. But then the suggestion to use SetCPU to lower the speed while the screen is turned off worked for me. So far no SOD and my phone has survived Faux's kernel and charging overnight without a battery pull and without overheating.
Now I can try out custom kernels and find all new ways to destroy my battery by doing things I'm not knowledgable enough to be doing!
lotherius said:
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Click to expand...
Click to collapse
hmm.. I dont doubt you, but I think doing that would not be any different.
BECAUSE, the charger is not constantly charging at 1A rate. If you notice, the phones ramps down the input current after a certain percentage ~90%, and trickles it up to 100. Once at 100, the charging is supposed to be stopped. I've charged mine with my bluetooth 500ma charger, and I didnt see a difference in heat temps; only charging time took longer.
As far as heat, Lion batteries should be able to handle 1C charge (1 x charge capacity) with no problems in heat. That means even at 1.5A charge, it should be OK.
Regarding overclocking, undervolting and overheating. There is a variation of parameters across every silicon wafer; among the 25 or so wafers in a wafer lot; and from wafer lot to wafer lot. This is referred to as the "spread" and parts at the extremes are called "corner parts". Most parts should be in the middle of things, not all. With newer parts and small silicon process geometries, the margins are typically smaller - hopefully improving as the fab gets experience with the new process.
A hardware developer should get corner parts to check their PCBA layout and FW, to see if they have design margin. In the case of DDR (RAM), the voltage, circuit layout and DDR interface timing (from Tegra, in this case) should be checked across some tolerance and with the corner parts. "Fast" parts can draw more current during operation that nominal parts, possible heating up the voltage regulators nearby.
In a good hardware design, everything should work across part variation and the specified operating temperature for the system. When we start playing with the clocking frequency and voltages, there is the risk of FW crashing and HW flipping out. The symptoms can include system shut down (lost), resets, heating, bad effects on other systems (battery, voltage regulator circuits, etc.).
This is why some of us (like me) have little luck Set CPU and others can change it to extreme. What none of us know is how close to the design limits the G2X is - the system and the components like Tegra, the FW control. If due design diligence was not done, the sensitivity to part variation and our hacking is greater than normal.
When I play graphic intensive games like Where's My Water or Cut The Rope, my battery temperature goes up rapidly. Within 4 or 5 levels it's in the mid 40s C. (The first time it went all the way up to 53 C before I looked at it.)
Is this normal?
If not, would you suspect a bad battery? (I got the phone used.)
FWIW, I'm running ARHD 6.6.3. Behavior is the same under the stock kernel and under SebastianFM's kernel.
Thanks in advance for any help.
Same problem.
I'm having the same problem too. Would appreciate it if someone could post a solution here!
iscarechyu said:
I'm having the same problem too. Would appreciate it if someone could post a solution here!
Click to expand...
Click to collapse
Well the battery doesn't CAUSE overheating, the processors do. Always. ICS roms, the newer ones anyway don't overheat the phone as much, turn of your syncs, mobile network and decrease the brightness of the phone. Your phone will always overheat pretty much no matter what you are doing on it if it is charging.
benjdm said:
When I play graphic intensive games like Where's My Water or Cut The Rope, my battery temperature goes up rapidly. Within 4 or 5 levels it's in the mid 40s C. (The first time it went all the way up to 53 C before I looked at it.)
Is this normal?
If not, would you suspect a bad battery? (I got the phone used.)
FWIW, I'm running ARHD 6.6.3. Behavior is the same under the stock kernel and under SebastianFM's kernel.
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to change the governer...and don't over clock the processors..actually 1.2ghz would do....so try changing the governer...or try faux kernel (keep the governer to intellidemand) ...I use faux kernel and also I play a lot...phone heats up but not that much...it reached max of 40 C
sent from my blazing fast pyramid through sonic waves
ganeshp said:
Try to change the governer...and don't over clock the processors..actually 1.2ghz would do....so try changing the governer...or try faux kernel (keep the governer to intellidemand) ...I use faux kernel and also I play a lot...phone heats up but not that much...it reached max of 40 C
sent from my blazing fast pyramid through sonic waves
Click to expand...
Click to collapse
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)
benjdm said:
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)
Click to expand...
Click to collapse
The governor sort of controls how the CPU speed will run on your kernel. You can change the governor using an app like SetCPU or System Tuner. BTW faux does tend to run a bit warmer, in my experience, but it's nothing to worry about if you know that you're running apps that are a bit heavy on the CPU.
benjdm said:
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)
Click to expand...
Click to collapse
I had the same problem , and im now currently running ARHD.
First time i try stock kernel and everything was burning, tryed to change with sebastian kernel with stock cpu speed and nothing change (and so a hard battery drain), they suggest me re-flashing Sebastian kernel and now everything is ok, temperature is not going up..
im currently running Faux kernel, all stock, and everything is awsome, try it.
see ya
Lollaz
Read this form and flash the 3.12 firmware
any help send feed back
http://forum.xda-developers.com/showthread.php?t=1610232
it manager musa91
I Super-wiped, formatted dalvik cache (I didn't see it in the Superwipe messages), re-installed ARD 6.6.3 with SebastianFM kernel, re-installed the radio, and put in the Anker battery. With System Tuner limiting the CPU max to 1.148 MHz and Governor set to Powersave, my battery hardly heated up at all while playing a game. The game's graphics did stutter though.
Now trying the on-demand governor to see if I can play without stuttering and without overheating the battery. My suspicion is that the improvement is due to re-doing the flashes or replacing a damaged battery.
musa91 said:
Read this form and flash the 3.12 firmware
any help send feed back
http://forum.xda-developers.com/showthread.php?t=1610232
it manager musa91
Click to expand...
Click to collapse
DO NOT DO THIS!!!!!!!
This fix only works for Ondroid rom. And then it has mixed results as to effectiveness.
But ARHD requires firmware 3.32 to work. If you try 3.12 you are likely to get bootlooping.
Musa, you know this only works on Ondroid. You should not be recomending firmware twaeks for other roms you havent tested it on.
benjdm said:
I Super-wiped, formatted dalvik cache (I didn't see it in the Superwipe messages), re-installed ARD 6.6.3 with SebastianFM kernel, re-installed the radio, and put in the Anker battery. With System Tuner limiting the CPU max to 1.148 MHz and Governor set to Powersave, my battery hardly heated up at all while playing a game. The game's graphics did stutter though.
Now trying the on-demand governor to see if I can play without stuttering and without overheating the battery. My suspicion is that the improvement is due to re-doing the flashes or replacing a damaged battery.
Click to expand...
Click to collapse
For future refference you dont have to reflash your rom to switch kernels.
Just wipe dalvik and cache and flash the new kernel. The first boot after than will take a few minutes but then it will be fine.
Its MUCH easier tgan redoing the whole rom.
Skipjacks said:
For future refference you dont have to reflash your rom to switch kernels.
Just wipe dalvik and cache and flash the new kernel. The first boot after than will take a few minutes but then it will be fine.
Its MUCH easier tgan redoing the whole rom.
Click to expand...
Click to collapse
I was trying to re-do everything because I didn't know what the problem was.
benjdm said:
I was trying to re-do everything because I didn't know what the problem was.
Click to expand...
Click to collapse
That plan certainly has its place too! Ive relied on numerous times in various subjects.
I like to call it the Noahs Ark fix. When everything else fails, destroy the world and start over!
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
More testing: I tried putting the old battery back in. Within 3 levels of gameplay the battery heated up to 40C. The new battery hasn't hit 30C no matter what I do. I think it's fairly conclusive the used battery that came with the phone is defective (whether from use, mis-use, or original defect, I have no idea.)
benjdm said:
More testing: I tried putting the old battery back in. Within 3 levels of gameplay the battery heated up to 40C. The new battery hasn't hit 30C no matter what I do. I think it's fairly conclusive the used battery that came with the phone is defective (whether from use, mis-use, or original defect, I have no idea.)
Click to expand...
Click to collapse
Nope incorrect my friend. Any batteries that ate not from HTC themselves won't tell the correct temperature because they do not have full battery calibration like it is with the stock ones.
Sent from my HTC Sensation Z710e using XDA
sensation lover said:
Nope incorrect my friend. Any batteries that ate not from HTC themselves won't tell the correct temperature because they do not have full battery calibration like it is with the stock ones.
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
Well, darn it
benjdm said:
Well, darn it
Click to expand...
Click to collapse
dont hold me to this but you could try getting the htc evo 3d battery or the sensation xe which I think are 1720mah, their callibration should work.
I contacted Anker to see if they had any software or anything for reading temperature. They said they did not and offered to take the battery back (kudos.) I'm keeping the battery.
Underclocking the CPU to 1 GHz seems to be helping quite a bit. Also, something changed with the battery sensing. The Anker battery went from indicating 25C all the time to indicating 11.5-12C all the time. When I put the stock battery back in, it's reading 17C while charging and somewhat above that while playing games, but nowhere near as high as before.
I wonder what's going on...
Hey guys,
I am calibrating my battery atm and as you may know you have to discharge your device fully to calibrate the battery properly. To speed up the process I decided to install a stresstest app to my phone and guess what: the phone gets insanely hot, I can't even hold it in my hand longer then 5-10 seconds. Kernel tuner displays me temperatures between 78 and 82°C.
But this overheating problem not only happens with the stresstest. When I start watching videos on youtube or start using my phone for maps it gets hot too (about 60-70°C). It starts to bug me.
What do you guys think I should do to fix this? I already thought about applying some thermal compound between the CPU and the metal shield around it. But I'm not quite sure if it's a good idea. I already have a new phone but I still need two phones because I have to travel between Germany and Switzerland all the time. And this issue starts to make my Sensation unusable.
Send from my flying Note 2
I would suggest an anker battery. It has a greater capacity and it keeps the battery very cool.
Sent from my Ouya
did you try different kernels?
AndroidSupporter318 said:
I would suggest an anker battery. It has a greater capacity and it keeps the battery very cool.
Sent from my Ouya
Click to expand...
Click to collapse
Already using it and I'm talking about the CPU temperatures and not the battery's temperature.
And sure I did try different kernels. Even at stock kernel setting this thing gets hot as f***!
Send from my hovering Note 2
So I just decided to disassemble my Sensation and put some thermal compound on the processor chip. Now I'm not getting over 70°C at full load, 1,56GHz. Pretty good outcome. And under normal use it doesn't heat up over 45°C.
I really have to recommend you this method!
OK, I ran into this issue about 5 days ago. No matter what ROM I install, my phone constantly heats up within 15-20 mins of casual usage. I don't even play games on my phone. I tried N ROMs and MM ROMs too, no matter what ROM I install, phone just heats up. I'm attaching a screenshot from CPU-Z app (which I used to monitor the temperature). Are those readings OK, or is there something wrong with my phone?
My phone's temperatures are usually similar to yours and I thought this was normal. In case it's not I'd like to see a solution to this as well.
Btw, do you have any custom kernels? Agni made my phone way too hot..
mike.... said:
My phone's temperatures are usually similar to yours and I thought this was normal. In case it's not I'd like to see a solution to this as well.
Btw, do you have any custom kernels? Agni made my phone way too hot..
Click to expand...
Click to collapse
I don't really go for custom kernels unless I'm testing one. I stick to the kernel that comes with the ROM.
Check kernel adiutor if your frequenties are peaking constantly
HelpMeruth said:
Check kernel adiutor if your frequenties are peaking constantly
Click to expand...
Click to collapse
I have checked. They are mostly around 800 MHz mark. And 45% of the time in deep sleep or 400 MHz.
Also I want to whether surrounding temperature can affect the values? Right now the temperature at my home city is averaging around 34-35°C. Would that be the cause?
HelpMeruth said:
Check kernel adiutor if your frequenties are peaking constantly
Click to expand...
Click to collapse
Not to hijack the thread but I have experienced all the cores being on max. frequency. I noticed this when my phone started warming up even being idle.
I saw this behavior for a few times in RR with both Optimus and Firekernel (Optimus had optimus set as its governor and Firekernel had darkness), however never encountered it in Ultradevs (with both chill and darkness).
This was a couple of months ago, and it hasn't happened again yet. However I am not sure if this was related to kernel because sometimes force stopping random applications such as greenify or nova launcher made the frequency scale down back to 400 (efficiency profile). Unfortunately I didn't get a hold on what was causing this, but I suspect some background user application was the culprit.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Not to hijack the thread but I have experienced all the cores being on max. frequency. I noticed this when my phone started warming up even being idle.
I saw this behavior for a few times in RR with both Optimus and Firekernel (Optimus had optimus set as its governor and Firekernel had darkness), however never encountered it in Ultradevs (with both chill and darkness).
This was a couple of months ago, and it hasn't happened again yet. However I am not sure if this was related to kernel because sometimes force stopping random applications such as greenify or nova launcher made the frequency scale down back to 400 (efficiency profile). Unfortunately I didn't get a hold on what was causing this, but I suspect some background user application was the culprit.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I also faced this issue first time when I flashed RR 5.8.2, no custom kernel used. And now its following on every ROM I install. I even tried custom kernels, different gapps packages but none seem to work. The phone heats up while charging and while doing simple things like using WhatsApp, sending emails, browsing through XDA. Also kernel adiutor is showing that GPU temperature is always above 43°C.
adityak1303 said:
I also faced this issue first time when I flashed RR 5.8.2, no custom kernel used. And now its following on every ROM I install. I even tried custom kernels, different gapps packages but none seem to work. The phone heats up while charging and while doing simple things like using WhatsApp, sending emails, browsing through XDA. Also kernel adiutor is showing that GPU temperature is always above 43°C.
Click to expand...
Click to collapse
Did you restore apps through some backup program such as Titanium backup? In my case, I used to use it and it might be the reason the problem was popping up everywhere.
If not, and if the phone still heats up even in clean state (after a fresh custom/stock rom install), then maybe some hardware issue could be the reason.
My Cpu-z reports battery being at 37° discharging and the sensor0 to sensor5 show 45-51°c although the phone feels way cooler than that.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Did you restore apps through some backup program such as Titanium backup? In my case, I used to use it and it might be the reason the problem was popping up everywhere.
If not, and if the phone still heats up even in clean state (after a fresh custom/stock rom install), then maybe some hardware issue could be the reason.
My Cpu-z reports battery being at 37° discharging and the sensor0 to sensor5 show 45-51°c although the phone feels way cooler than that.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I clean installed all the ROMs. Still the issue persists. I haven't tried stock ROM yet. I'll try that and report back.
adityak1303 said:
I clean installed all the ROMs. Still the issue persists. I haven't tried stock ROM yet. I'll try that and report back.
Click to expand...
Click to collapse
yeah, thinking you may have to flash stock, not restore it via twrp. I know it's a pain but it would give you a good reference point.
Well I can't flash stock ROM for the next 2 days. So let me ask this : Is a temperature of 37-42°C for battery and CPU harmful for the phone? Or I shouldn't worry about it?
107F? I shouldn't think so...
"Right now the temperature at my home city is averaging around 34-35°C. Would that be the cause? " It wouldn't help...
I am 26 ambient and my phone temps run 36-36 or so.
Ambient temp does play a factor. If the phone is Almost as hot as the ambient it's hard to transfer the phone heat to the ambient surrounding.
My freqs and temps in attachment. I use aosp-caf with prepackaged kernel(ud i think) with some custom settings.
Ambient temp is around 20 C inside and 10 C outside
HelpMeruth said:
Ambient temp does play a factor. If the phone is Almost as hot as the ambient it's hard to transfer the phone heat to the ambient surrounding.
My freqs and temps in attachment. I use aosp-caf with prepackaged kernel(ud i think) with some custom settings.
Ambient temp is around 20 C inside and 10 C outside
Click to expand...
Click to collapse
Thanks a lot. Even when my phone was not heating up, the CPU and battery never got cooler 31°C. And GPU was around 38°C. And even after intensive use, CPU never got hotter than 37°C.
Now my phone's CPU and battery are around 35°C mark and GPU around 43°C. And during use CPU reaches 43°C mark and GPU about 52°C. Can these temperatures cause any harm to the device?
adityak1303 said:
Thanks a lot. Even when my phone was not heating up, the CPU and battery never got cooler 31°C. And GPU was around 38°C. And even after intensive use, CPU never got hotter than 37°C.
Now my phone's CPU and battery are around 35°C mark and GPU around 43°C. And during use CPU reaches 43°C mark and GPU about 52°C. Can these temperatures cause any harm to the device?
Click to expand...
Click to collapse
Don't quote me but I think it's okay. Motorola should have tested it on much higher temps. So just go with it if it dies you maybe have warranty.
adityak1303 said:
I clean installed all the ROMs. Still the issue persists. I haven't tried stock ROM yet. I'll try that and report back.
Click to expand...
Click to collapse
I had the same issue . with few ROMS . My device temperature went around 70C on oen ROM. I am usimng Osprey 1GB RAM
I have not faced any issues since I am using Nano Gapps. Previousely I used Mini gapps and that was causing the issue . Depend whar Mobile you use 1GB RAM or 2GB RAM. Also it is better to clear cache after every install
Also I use following settings to make suer it doe snot get hot.
-Ambient Display Off
-Adaptive Display Off
-Try not to block any apps from sending notoification as I had issues where battery draining and mobiel heating up by doing so
-Keep brightness to minimum
and since I am using this I had not any issues with heating
chungomungo1 said:
I had the same issue . with few ROMS . My device temperature went around 70C on oen ROM. I am usimng Osprey 1GB RAM
I have not faced any issues since I am using Nano Gapps. Previousely I used Mini gapps and that was causing the issue . Depend whar Mobile you use 1GB RAM or 2GB RAM. Also it is better to clear cache after every install
Also I use following settings to make suer it doe snot get hot.
-Ambient Display Off
-Adaptive Display Off
-Try not to block any apps from sending notoification as I had issues where battery draining and mobiel heating up by doing so
-Keep brightness to minimum
and since I am using this I had not any issues with heating
Click to expand...
Click to collapse
Thanks for replying but its not the issue of any ROM. I flashed stock and the issue still persisted. So I literally contacted everyone I know of who owns an unrooted osprey in my city and asked them about this.
Turns out everyone's phone is getting hotter a lot faster than before. Even went into a Moto Service Centre, they said its fine for the phone to heat up in such temperatures.
The issue is ambient heat. As you might have seen in my previous post, I mentioned that the temperature in my city is averaging around 35-36°C (Today it reached 40°C), the phone just doesn't cool down enough after using it. So when I started to use it again, it heated up.
Thanks everyone for replying.
adityak1303 said:
Thanks for replying but its not the issue of any ROM. I flashed stock and the issue still persisted. So I literally contacted everyone I know of who owns an unrooted osprey in my city and asked them about this.
Turns out everyone's phone is getting hotter a lot faster than before. Even went into a Moto Service Centre, they said its fine for the phone to heat up in such temperatures.
The issue is ambient heat. As you might have seen in my previous post, I mentioned that the temperature in my city is averaging around 35-36°C (Today it reached 40°C), the phone just doesn't cool down enough after using it. So when I started to use it again, it heated up.
Thanks everyone for replying.
Click to expand...
Click to collapse
It might be issue with India summers :laugh: mine is also getting hot from past few days.
libert19 said:
It might be issue with India summers :laugh: mine is also getting hot from past few days.
Click to expand...
Click to collapse
That's what I figured. Thanks.