Related
I really like specs of DHD it seems to be really great phone. Even if it lacks AMOLED display I still think that it would be phone arround. 4,3" display should be big enough to do light work on it which would include lots of browsing, emailing etc. I just wonder what do you expect from 1230 battery? I am still sticking to my very old but precious HTC Touch Diamond which is painfully slow and battery last only like 12 hours while I am using. So with all "improvments" (better cpu tech, older display and Android 2.2) battery life should be at least as good as EVO ? Thanks a lot for your opionions
PS I know that nobody will be sure until we get hands on DHD but at least we have something to chat about until we get final release date
The same DHD ROM on HD2 with base WM ROM optimizations gets me 1.5 day worth and its not running Android directly from the phone yet.
So I would guess it will be 1-2 days with medium-heavy use
x
Cool that would work for me Just wonder why EVO battery life is short? 4G drains more energy than 3G?
Not sure of 4G but rest is like this -
GSM : More Talk/Use time & Lower Standby Time
3G/HSDPA : Lesser Talk/Use time & Higher Standby Time
Hey guys, what do you think the battery life would be without 3g on? I dont have a data plan, and dont plan to get one (yet?), so i'll be using wifi for data. So with 3g off, and data roaming off, and even wifi off, what would u expect the battery life to be with moderate-heavy usage?
SupremeBeaver said:
Hey guys, what do you think the battery life would be without 3g on? I dont have a data plan, and dont plan to get one (yet?), so i'll be using wifi for data. So with 3g off, and data roaming off, and even wifi off, what would u expect the battery life to be with moderate-heavy usage?
Click to expand...
Click to collapse
I think HTC lowering the size of the battery is a big indicator that the battery will definitely last you 1 day of heavy usage... I think if they was worried about the battery life they would have stayed with the 1400..
JD
JupiterDroid said:
I think HTC lowering the size of the battery is a big indicator that the battery will definitely last you 1 day of heavy usage... I think if they was worried about the battery life they would have stayed with the 1400..
JD
Click to expand...
Click to collapse
They are using unibody design for DHD that could be also reason since EVO has classic design with removable back than I would think that physically bigger battery fits to it.
Appart from SE X10 I have never seen a smartphone of DHD, SGS, Desire etc. caliber to last more than 2 days max. Even the SGS (wich has 1500mAh) doesn`t last more than 3 days (that was the max I could get from it) although the battery is not the one that GsmArena guys used for testing, does who know about the controvers around the SGS battery know what I`m talking about. So, I don`t think it will do better than 2 days (max).
I wish at least as a marketing tactic, they should keep same size battery (1400 mAh) as Desire. It's really annoying to know you actually downsize in terms of battery while you are making a device upgrade.
eozen81 said:
I wish at least as a marketing tactic, they should keep same size battery (1400 mAh) as Desire. It's really annoying to know you actually downsize in terms of battery while you are making a device upgrade.
Click to expand...
Click to collapse
From my understanding the DHD consumes less than the Desire, so even a downgrade in battery total capacity does not mean you will have less autonomy.
I hope htc gets this right, i am really worried about battery life with heavy use.. It will be more power efficient compared to the evo 4g because the 4g uses a 65nm batt + likely the screen consumes more + the 4g is a battery eater.. but still i think the battery could have been a little bit bigger say 1320mah or even 1400mah, I hope mugen power or seidio come with a battery @ around 1600mah they can make that, the legend(Unibody) can have a 1800mah battery instead of the 1300mah that gives around 30 to 40% longer battery usage time in practice!
We don't know how efficient the new chip is yet. We will have to wait for reviews. But like all modern smartphones, expect it to charge it everyday. (if you are a heavy user)
Scotchy49 said:
From my understanding the DHD consumes less than the Desire, so even a downgrade in battery total capacity does not mean you will have less autonomy.
Click to expand...
Click to collapse
Maybe HTC is right about less consuming maybe not, we will see but at least there are many people who directly look up the battery capacity and it a downsized capacity may them prejudge and not to decide buy. I know this is not such a big probability but If I were CEo of HTC, I would definetely go with same size battery with Desire but declaration with "less consuming" compared to Desire.
eozen81 said:
Maybe HTC is right about less consuming maybe not, we will see but at least there are many people who directly look up the battery capacity and it a downsized capacity may them prejudge and not to decide buy. I know this is not such a big probability but If I were CEo of HTC, I would definetely go with same size battery with Desire but declaration with "less consuming" compared to Desire.
Click to expand...
Click to collapse
i think they were forced into using that size, otherwise they would have to make the DHD fatter to fit in a bigger battery.
dont think so,
Keep in mind that the DHD has a completely new processor in it with a new GPU aswell!
tests have shown that the DHD is 2x faster then a Nexus one with android 2.2! This new processor probably uses alot less power, and thus a smaller battery would be enough for atleast 1 day.
DHD sports a bigger screen than desire. when screen is on, I 'd bet DHD would drain more, whilst it could be less energy-consuming when screen is off.
To end this pointless thread in a whip:
1: 45nm VS 65nm - you can make the maths. This alone will yield a hefty decrease in power usage.
2 (a): the (only) potential power usage increase might come from the 4.3" screen, although that remains to be seen. WIFI/BT are standard.
2 (b): in order to decrease 2 (a), disable auto brightness and set a static, lower level.
3: Another contender for battery usage might be HTC's framework+apps+services. Once you get rid of the unnecessary, you'll save quite a bit of power. Once you get recovery and use an AOSP build (I HATE SenseUI), this will further decrease power usage.
4: In order to further tune the power scaling, use an UV/OC kernel + proper scheduler ammendments (once HTC posts the source on the dev site). You can tweak the latter with in the meantime with temp. root and a user script targetting /sys values.
I guess that should cover the basics.
adwinp said:
4: In order to further tune the power scaling, use an UV/OC kernel ....
Click to expand...
Click to collapse
hey man..there are rumors spred about new chips on board from sandisk with lock on nand. there's a chance that hd2 will be as u unbox, for a long time. just hope it could be possible to undervolt the same kernel provided from htc.
Or maybe not, everything has a weakness, even the lock on nand we will just have to wait...
Epic vs Evo battery differences
Something I noticed while having an Epic and Evo under one roof was that although they both last about the same length on a charge, the components using the juice vary greatly. Here’s is a breakdown of the most power hungry items arranged from most power usage to least:
Evo:
• Cell Standby (most power usage)
• Phone Idle
• WI-FI
• Android System
• Display
Epic:
• Display (most power usage)
• Cell standby
• Phone idle
• Android System
Initially I thought that the Epic’s AMOLED screen was WAY more power hungry than HTC’s LCD. But if that was the case I would expect the Evo to outlast the Epic on a charge which wasn't happening. Then it hit me. Samsung’s Hummingbird CPU/GPU is 45mn and is supposedly eating less power than the older 60mn Snapdragon processors. If true this could explain the reversal of the “Display” from being at the bottom to being at the top. I suspect the AMOLED does require more juice than HTC’s LCD but perhaps not as much more as I originally thought. What is likely going on is that the system components are less power hungry on the Epic but the screen is somewhat more power hungry. This could explain why Evo’s and their custom undervolted kernels see a big improvement in battery life, simply because the underlying cpu/gpu is using a larger percentage of the battery’s life.
The other noteworthy item, Wi-Fi was always in the middle of the list on the Evo but doesn’t even show up on the Epic even though Wi-Fi is always enabled. I have heard the Epic uses a newer low power Wi-Fi chip and if that’s the case it seems to have paid off.
My Conclusions:
1. If you want more battery life on the Epic, turn off auto brightness and set the brightness quite low. Set applications to “dark” theme’s when available because black pixels draw no power on the amoled screen.
2. If you want more battery life on the Evo, you’ll want to look into rooting & custom undervolting kernels (and you’re in the wrong forum…haha).
I welcome your comments and to know if you draw different conclusions. Thanks!
Well I've heard the samoled takes less power than the lcd but idk. Just putting some info down.
Sent from my SPH-D700 using XDA App
rocket321 said:
Epic vs Evo battery differences
My Conclusions:
1. If you want more battery life on the Epic, turn off auto brightness and set the brightness quite low. Set applications to “dark” theme’s when available because black pixels draw no power on the amoled screen.
2. If you want more battery life on the Evo, you’ll want to look into rooting & custom undervolting kernels (and you’re in the wrong forum…haha).
I welcome your comments and to know if you draw different conclusions. Thanks!
Click to expand...
Click to collapse
1. If you want more battery life on the EPIC, get a custom ROM (viperrom) running 2.2. Helped me get from 8-10h with low use to 16+h with moderate/heavy use.
Yeah stock epic battery is horrible.
However, on dk28 its much much better battery life
Anyone else notice that the screen always takes up about 90% of the power? Lol but that doesn't mean it won't last long
I just made a thread about how I watched two full length movies on the highest brightness and I'm at 13hrs right now still kickin lol
Sent from my SPH-D700 using XDA App
deano0714 said:
Well I've heard the samoled takes less power than the lcd but idk. Just putting some info down.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have said both of this things on other threads today, but they bear repeating here.
First of all, SAMOLED uses more power than LCD in most cases. It uses less power than regular AMOLED. If you go back and read Samsung's press releases, they say that fact. They don't claim better battery life than LCD, and you know they would be the first to say it if it were true.
narn17 said:
1. If you want more battery life on the EPIC, get a custom ROM (viperrom) running 2.2. Helped me get from 8-10h with low use to 16+h with moderate/heavy use.
Click to expand...
Click to collapse
The Galaxy S devices have software issues that cause some of them to use their antennas constantly. With this issue, the battery drains in 10 hours, at best. You should be getting at least 20 hours out of your battery with moderate use. If you are experiencing these issues, chances are it will happen on all ROMs (as it did with me). I know two other people who have Galaxy S devices and they both have this issue. Mine started getting 20 to 30 hours when I switch to DK28 (and my GPS broke, not to mention occasional FCs and a broken WiFi tether), so I am betting this will get fixed with the 2.2 update. The above quote further supports this theory.
BTW, the whole "recalibrating the battery" thing does not help and can be harmful to your battery. While I am dispelling myths, clearing a cache or resetting a partition more than once is a waste of time. If you ever hear someone say "clear system 3x", they are just being superstitious. Maybe they have accidentally hit "no" instead of "yes" when they cleared it in the past, and ever since then they decided to do it 3 times.
One more myth! Most benchmarking tools for Android are crap. Quadrant has been shown to give highly inaccurate and easily manipulated scores. I used to think Linpack was good, but I have heard of G2's getting like 33 MFlops, which is ridiculous and makes me think it is bad as well. Any benchmark that takes into account FPS is only accurate if you remove the FPS limiter on your phone. All phones that I know of are locked to a max of 55-60 FPS (Epic 4G is locked to 55.6). What that means, is if you put a 5ghz quad core CPU with a GTX 580 in your phone, you would still get 55.6 FPS with those benchmarks (such as Neocore).
BenchmarkPi seems to be pretty accurate for CPU. An3DBench seems to be OK for OpenGL and 3D benchmarks since they tend to tax the GPU so much that it doesnt ever hit its limiter.
just a question on overclocking, on a computer if you overclock it, it can cause cause a shorter life span on the processor because of the extra heat, is there any ill effects to the vega by overclocking it?
Overclocking always carries a risk (the manuafacturer wouldn't randomly underclock your CPU for no reason unless there called Apple ofc) the vega is very stable at the speeds it is so far possible to reach however when I ran mine at 1.4ghz I noticed a slight warmth from the device battery will be shorter lasting ofc as well running the vega up to 1.2 is very safe in my opinion 1.4 or 1.5 carries a very small risk
typed by using my vega as a tennis racquet
adding to bob's answer.
considering the current life span of mobile electronics I really wouldn't worry!
Yes, the processor on it, instead of lasting 25 years before burn n die will last only 23 years.. so don't worry!
Battery wise as well, instead of giving you 4 years of good life than an extra 2 of crappy life, it will be 3 years of good life!
remember.. ALL THOSE NUMBERS I said are purely guessing and have no scientific base!! They are for illustration purposes only.
fact is: in 3 years time you'll already have bought a n-videa core 8 based device that the screen is as thin as a piece of 300grm paper.
so conclusion: I wouldn't worry and enjoy the benefits of overclocking. But it's your decision!
thanks for the answers guys
n-videa core 8 based device that the screen is as thin as a piece of 300grm paper.
Click to expand...
Click to collapse
I so want one of those!
geekyhawkes said:
I so want one of those!
Click to expand...
Click to collapse
me too, I'm looking forward for the future to happen!
So since I had my nexus 4, I had to complain about its terrible battery life.
I would never get more than 3h of screen on time, despite my best efforts in conserving battery. Even with the phone in flight mode and on Wifi, I could not cross 3h give or take a few minutes. I even tried disabling location, google now, sync and everything else.
It was deep-sleeping nice, while the screen was off, standby time was awesome for me. If I turned it on though, it started to burn through battery insanely quick. So I started monitoring the frequency states with battery spy, and noticed that as if there was a little load, it spiked to 1026MHz and then stayed there for about three seconds every time before falling back to 386 MHz. So I tried setting the max cpufreq to 916Mhz with CPU tuner, and was astonished to find out, that immediately after the load was done, it went back to the lowest frequency. Like it should be, not hanging for multiple seconds on the high step.
Also, If I start CPU tuner, the min freq is always shown as 1026MHz. So I changed min to 386 and max to 916. Afterwards, this stays until I swipe cpu tuner away from the recent apps list. If I start it again, the settings revert. Strange...
With my cpu limited to 916MHz, I get about 5h and 50 min of screen on time without any other measures. Location on, Wifi on, Google now and sync all active. If I just go one step higher and set my max frequency to 1026, the old behavior starts again, and screen time drops to 3h because it seems to be stuck on that freq. Therefore I would like everybody who also has bad screen time to try that out and report back.
I don't really understand why it would take so long to drop back from the 1GHz step, and drop back immediately from the 0,9GHz step?
Of course, this is with normal surfing via chrome, or using normal apps that are not that much CPU intensive. Also, you hardly notice the performance limitation without playing games. There probably is an easy way to fix this?
Feedback would be appreciated. Maybe I see this wrong...
Thanks
tl;dr : if screen on, for me only 1026mhz is used, if max freq is set to anything lower, the phone spends most of the time at the lowest step 386mhz, greatly increasing screen time for me.
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
NoLunchBox_ said:
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Maybe, but I really first wanted to examine out of the box behavior
This is caused by qualcoms Mpdecision which ramps up the cpu to 1ghz on screen on and touches. All in the name of speed. It's basically a hot plugging technique such that smoothness is guaranteed under loaded gui transitions and scrolling. Before this you would have to wait for the cpu to be loaded for it to ramp up speed. Now the OS can demand speed.
You can see in Franco kernel he replaced Mpdecision with an open source alternative and swapped the lowest cpu speed to 368mhz. Then added a load step of 768mhz (for 60% loads). This actually added a bit of lag but should be better in the battery department. Some more tweaking to be done though.
Qualcoms thermald is what is causing thermal throttling.
Edit: this could be wrong. But I think I'm in the general area of what's going on...
Sent from my Nexus 4 using xda premium
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
ArRaY92 said:
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
Click to expand...
Click to collapse
You don't have to buy an app, everything can be set through scripts. The app just automates the process, allows you to back up kernels, download the latest nightly and milestone (when one becomes available). It's really worth the investment, plus you're helping out a great Dev who has shared his awesome work with us for a long time.
Sent from my Nexus 4 using Tapatalk 2
I like my phone to sleep. I bumped it down to 384!
No need to keep it @ the 1.026, it will pretty much kill battery! Makes no sense to me.
Sent from my Nexus 4 using Tapatalk 2
You can set the max to 384 mhz.. and still everything is smooth
Can I use SetCPU or is that app defunt now? And to change my CPU speeds can that be done on a phone that's simply rooted or do I need a custom kernel?
EDIT: I downloaded CPU tuner, but I'm not sure if it's working or not. Does it work w/ stock kernel or no?
Faux's Intellidemand fixes pretty much what you're describing. Since mpdecision is not used instead of fauxs alternative.
Sent from my Nexus 4
What is max frequency by default?
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
biffsmash said:
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
Click to expand...
Click to collapse
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
ksc6000 said:
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
Click to expand...
Click to collapse
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
[hfm] said:
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
Click to expand...
Click to collapse
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
ArRaY92 said:
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
Click to expand...
Click to collapse
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
[hfm] said:
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
Click to expand...
Click to collapse
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
My min CPU speed is 1 GHz and in still getting 4 hours on screen time though. I don't think setting my min at 384 MHz even made much difference in my battery, will try it again soon.
Sent from my Nexus 4 using xda premium
droyd4life said:
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
Click to expand...
Click to collapse
Stock never rooted bootloader still locked.
If you are getting bad battery... simply flash a custom kernel. You get to keep your stock ROM or whatever but you will get substantial benefits. I prefer Trinity Kernel. Only the second or third update on this kernel and now the phone has made huge gains in battery life. Like hfm, I good on screen time... usually 5-5.5. I have auto brightness on, mobile on 100% of the time, and all Google services synced including books, gmail, currents, google now, etc etc. I have locations on, gps on... everything. Sometimes I turn off NFC because I rarely am somewhere where I can use those cool RFID card scanners. What sucks battery is probably a problem in Android 4.2. The phone does not sleep as much as it should. Go ahead and turn all your sync stuff off and keep the screen on static and let the battery die at stock clock speeds. Probably will get at least 5 hours with auto-brightness on. My phone probably sleeps 60% of the time now according to CPU spy when it sits idle in my car for my 8-10 hour work day. I usually get to the car with a bunch of emails, a text or two waiting for me, and the phone has only been asleep the aforementioned 60% and around 90-91% battery life. On a new phone, starting from full charge, this should be at least 95%. My N10 that doesn't have mobile data, only loses about 1% overnight. Apples to oranges but still. I'm convinced that stock voltages on this device are too high, and that Qualcomm did not give Google the latest drivers... maybe because it's not releasable to AOSP as of yet. I really don't know, but it's gotta be something buggy. This SoC is capable of doing better... and it does in the Optimus G and even with sense, 1080p screen, and a 100mah smaller battery the HTC Droid DNA/Butterfly gets 3.5-4 hours stock screen time. None of the other phones using the S4 Pro are running 4.2. I'm hoping either Qualcomm pulls a Samsung and releases some updated drivers/firmware that Google can incorporate or that Google fixes whatever bugs they may have not worked out. In the next calendar year other phones will be out that use the S4 Pro and 4.2 and I doubt Qualcomm wants to lose the luster it earned with the regular S4 Kraits performance/efficiency. When 4.2 comes to other devices we will probably know whether or not Google is to blame for this or that the Nexus 4 is just a poor performer.
Am using a combination of Paranoidandroid and Franco kernel, and as widely discussed, the device gets hot at times very hot. So apologies if this has been discussed before, as I did a quick search but nothing came up, so what would be the gradual effect of the phone overheating, as clearly this must represent to some extent irregularities in the phone system DDoes it slowly cook up the internals of the phone, or maybe perhaps the phone is designed to withstand such heat, so just concerned because I use my phone at least 15hrs a day, so just concerned.?
I'm not a hardware pro so take this with a grain of salt. I think that long-term heating of the internals will have minimal harmful effects on your hardware. It'd take years and years for it to actually affect your device, long after you've upgraded. The CPU has undergone plenty of testing to make sure it lasts for a long time under self-inflicted environmental factors such as heat.
would also like to know. but not sure about what is considered hot/really hot.
the max CPU temperatures i reached were around 56°C (133°F), but thermal throttling on francos kernel is set to 70°C (158°C) by default (i lowered it to 65°C/149°C just to be safe).
if i remember correctly, i read somewhere that li-ion batteries dont really like being above 42°C (107°F), so when it reaches that temp, i immediately let it cool off.
so to sum up, thermal throttling is there to protect the soc and the hardware around it, so i would be concerned about the parts on the motherboard. i cant recall where i read that temp limit on the battery, so i cant state anything for sure about that.
marvi0 said:
Am using a combination of Paranoidandroid and Franco kernel, and as widely discussed, the device gets hot at times very hot. So apologies if this has been discussed before, as I did a quick search but nothing came up, so what would be the gradual effect of the phone overheating, as clearly this must represent to some extent irregularities in the phone system DDoes it slowly cook up the internals of the phone, or maybe perhaps the phone is designed to withstand such heat, so just concerned because I use my phone at least 15hrs a day, so just concerned.?
Click to expand...
Click to collapse
It won't affect phone's hardware afaik, the cpu itself has thermal guard and will automatically shutdown itself if the temp reach 110 or 120° (not sure between those two).
The one that may affected is battery, it may reduce your battery lifespan or even explode it if it's too hot, but it's hardly happens.
Sent from my Nexus 4 using Tapatalk 4 Beta