Last updated 05/02/12
I am not responsible for anything you do to your phone. If the phone dies or bricks, I blame you, it will not be my fault.
It can be different on every phone. These are what I found and tried.
Everything below was tested on i777 running Task650 AKOP(Build 4.28.12 (2nd Release) running the N.E.A.K Kernel(N.E.A.K-2.0.3xb-I777-AOSP). (Thank you guys for an awesome Kernel and Rom )
This was my first time undervolting and wanted to share sense not many people(that I know of) undervolt.
Clocking are set at ondemand between (Min)200 - (Max)1200
I started off with the stock and lowered each one by -25 till it froze. If it froze I went back up 25 and made sure it was fine. Then did the next clock.
Lets say it froze at 1000 then I changed it too 1025.
UnderVolting can give your phone longer battery life.
Also lower the heat produced by the phone.
To undervolt, you can use SetCPU or Voltage Control.
Tomorrow I will start posting battery life with everything(Screen on time, data, ect). I will have sync and everything on for the testing.
It can be different on every phone. These work fine with mine.
------------------
Later today, I will post screen shots of what undervolting can do for battery with the correct frequency's you find on your phone. Everything is on, just took of the charger at 100%.
Enjoy,
Jake
Those values may work for you, but may not work at all for others
I do wonder one thing though. If one lowers voltage, does current increase in turn to compensate for the lower voltage?
twiggums said:
Those values may work for you, but may not work at all for others
I do wonder one thing though. If one lowers voltage, does current increase in turn to compensate for the lower voltage?
Click to expand...
Click to collapse
From basic physics, voltage and current are proportional, so if one decreases (holding resistance constant) the other will also decrease; Ohm's Law, V = iR. Of course, that's for ideal and very simple circuits, so I have no idea if that law actually holds in such complex things as phones, but I don't immediately see why it wouldn't.
Sorry, I'm currently taking a basic college physics course on electromagnetism XD.
karate104 said:
From basic physics, voltage and current are proportional, so if one decreases (holding resistance constant) the other will also decrease; Ohm's Law, V = iR. Of course, that's for ideal and very simple circuits, so I have no idea if that law actually holds in such complex things as phones, but I don't immediately see why it wouldn't.
Sorry, I'm currently taking a basic college physics course on electromagnetism XD.
Click to expand...
Click to collapse
Your completely correct assuming load remains constant . However if something operates on varying voltage it'll often adjust the current to meet power req for operation I believe .. Hehe and if that's the case then UV becomes pointless :what:
Not sure how the CPUs in or phones work, but I'm sure it'd be considered "complex circuitry" vs a "simple circuit". I've asked this in a different thread before but never really got a firm answer.
karate104 said:
From basic physics, voltage and current are proportional, so if one decreases (holding resistance constant) the other will also decrease; Ohm's Law, V = iR. Of course, that's for ideal and very simple circuits, so I have no idea if that law actually holds in such complex things as phones, but I don't immediately see why it wouldn't.
Sorry, I'm currently taking a basic college physics course on electromagnetism XD.
Click to expand...
Click to collapse
I'm taking physics in hs this year lol I hate it I sucked the first half of the year and I'm only doing okay this quarter
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Thanks for posting this man. Good read. Keep us updated.
Sent from my SGH-I777 using xda premium
One thing seems evident to me. I could run my device -100mv at all steppings on GB, but ICS is so much more sensitive to UVing.
Sent from my SGH-I777 using xda premium
This thread is compeletly pointless and should be deleted. No one should try and take someone elses settings for OC/UV. been this way for all of time. and if you'd have done any research, you'd probably have found this out.
No the CPU will not increase current to compensate for reduced voltage.
The transistors create most heat during switching when their conductivity isn't ideal. The resistance along the conducting path increases during on/off cycles and the voltage across this path with determine the Watts consumed by the device.
So lowering the voltage or frequency will reduce the wasted energy.
Sent from my SAMSUNG-SGH-I777 using xda premium
MotoMudder77 said:
This thread is compeletly pointless and should be deleted. No one should try and take someone elses settings for OC/UV. been this way for all of time. and if you'd have done any research, you'd probably have found this out.
Click to expand...
Click to collapse
I state that it won't work for everyone, that these work on my phone.
This helps give people a clue in how to undervolt. Once I get home I plan to make this more guide like. I don't see many detailed threads on undervolting and not many people know about it.
Sent from my SGH-I777 using xda premium
ACCUSED24 said:
I state that it won't work for everyone, that these work on my phone.
This helps give people a clue in how to undervolt. Once I get home I plan to make this more guide like. I don't see many detailed threads on undervolting and not many people know about it.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
theres a reason that not many people know about it. noobs dont know what they're doing, and those that do, know not share setttings. not hard to UV, and those that find it hard, are probably best of not messing with it
I can make a guide on how to turn a vaccume into a sort of gun, but sharing it publicly is not recomended
I understand your want to help the community, and thats good.
MotoMudder77 said:
theres a reason that not many people know about it. noobs dont know what they're doing, and those that do, know not share setttings. not hard to UV, and those that find it hard, are probably best of not messing with it
I can make a guide on how to turn a vaccume into a sort of gun, but sharing it publicly is not recomended
I understand your want to help the community, and thats good.
Click to expand...
Click to collapse
Is this better? I removed my frequency's but explained myself. Think of this as a test to see results now. It also has a simple guide that isn't beating anyone with a bat.
karate104 said:
From basic physics, voltage and current are proportional, so if one decreases (holding resistance constant) the other will also decrease; Ohm's Law, V = iR. Of course, that's for ideal and very simple circuits, so I have no idea if that law actually holds in such complex things as phones, but I don't immediately see why it wouldn't.
Sorry, I'm currently taking a basic college physics course on electromagnetism XD.
Click to expand...
Click to collapse
Well as you start to involve capacitors and inductors the law becomes slightly more complex, involving real and imaginary components . the reason why the phone at lock up may be due to the capacitors and inductors. These values are very sensitive to the current in the circuit! Changing it slightly may give undesirable results. Long story short. Undervolting by small amounts will have a negligible difference in battery life. Undervolting by large amounts will screw with how the circuit was designed. So be careful!
Sources - me being an electrical engineer!
EDIT: One last thing karate made me realize, decreasing the voltage would require increase current. (Since the values of L, R, and C cannot be changed! if you guys really want to save battery just stick to underclocking, you don't know the circuit configuration and specs of the phone.
Sent from my SGH-I777 using xda premium
So does undervolting really offer no battery life savings? I've read an article on laptop undervolting offering significant battery life improvements, especially because the CPUs run at lower temps thus saving life by requiring less fan cooling. I guess that doesn't apply to phones because we don't have cooling fans, but is there really no reason to undervolt?
Also, why would underclocking offer more battery life?
Sent from my SGH-I777 using XDA
karate104 said:
So does undervolting really offer no battery life savings? I've read an article on laptop undervolting offering significant battery life improvements, especially because the CPUs run at lower temps thus saving life by requiring less fan cooling. I guess that doesn't apply to phones because we don't have cooling fans, but is there really no reason to undervolt?
Also, why would underclocking offer more battery life?
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Lower CPU usage= less power consumed
Sent from my SGH-I777 using xda premium
jthatch12 said:
Lower CPU usage= less power consumed
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
+1
I generally uc to 800mhz, and see a noticeable difference.
I've tried UV as well, but never really noticed anything significant.
Related
http://m.androidcentral.com/wiping-battery-stats-doesnt-improve-battery-life-says-google-engineer
Sent from my PG86100 using Tapatalk
bloodrain954 said:
http://m.androidcentral.com/wiping-battery-stats-doesnt-improve-battery-life-says-google-engineer
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Haven't read it yet.
But its 'myth'.
posting part of the article here would help you know
Dude, not to be a **** and rain on your free will for posting info, but this is old news. Battery stats are known to be used to measure how much juice your battery can hold, in otherwords the stats are their to learn your battery. Wiping battery stats should be used only when your on an alpha Rom with broken battery reporting moving to a more stable version. Or when your battery needs calibrating.
"DU4L C0R3 SH00T3R"┌П┐[◣_◢]┌П┐
http://goo.gl/v6NqW iTz_r0cky!
r0cky0790 said:
Dude, not to be a **** and rain on your free will for posting info, but this is old news. Battery stats are known to be used to measure how much juice your battery can hold, in otherwords the stats are their to learn your battery. Wiping battery stats should be used only when your on an alpha Rom with broken battery reporting moving to a more stable version. Or when your battery needs calibrating.
"DU4L C0R3 SH00T3R"┌П┐[◣_◢]┌П┐
http://goo.gl/v6NqW iTz_r0cky!
Click to expand...
Click to collapse
this is the point....
your battery does not need calibrating. that is the myth.
tailsthecat3 said:
Havent read it yet.
But its 'myth'.
Click to expand...
Click to collapse
Thanks for the help, also it's "haven't."
Sent from my PG86100 using Tapatalk
Alright, alright.
bloodrain954 said:
Thanks for the help, also it's "haven't."
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Grammar police.. *siren noise*
lol... nice thread. it still has potential
Well when phones start shutting off at 14%, we will see who stays committed to this thread. Like i said no disrespect but nice talking to you guys.
"DU4L C0R3 SH00T3R"┌П┐[◣_◢]┌П┐
http://goo.gl/v6NqW iTz_r0cky!
i saw this and posted about it but didnt get any responses. was wondering if any devs or people in the know could explain it a little more.
r0cky0790 said:
Well when phones start shutting off at 14%, we will see who stays committed to this thread. Like i said no disrespect but nice talking to you guys.
"DU4L C0R3 SH00T3R"┌П┐[◣_◢]┌П┐
http://goo.gl/v6NqW iTz_r0cky!
Click to expand...
Click to collapse
explain this to me then... how, logically this idea about wiping battery stats makes sense. think about this.
you flash a new rom, wiping system completely, fresh start right? ok. so a small crash course in Linux... the Linux kernel is the power management system for android. this means voltage, charge capacity, and discharge cycles. the Linux kernel determines at what voltage to power down your phone, and at what voltage is full charge. is it not? it is. right.
ok so the next question I ask... is why is this a dispute? you just read a quote from an engineer that told you exactly what the function of the battery stats file is... and it is simply system analysis. it logs readings on what is consuming battery, for how long... charge and discharge cycles. it does NOT control or maintain the phone's power management. this is a Linux kernel function. just like your CPU voltages are maintained and operated by your Linux kernel, so is everything else (your entire phone for that matter) in the android world.
I used to wipe battery stats alllll the time. did the whole charge to full capacity, delete battery stats, yadda yadda yadda... does nothing.
let me ask you this as well, and this logic should by itself debunk anything you have ever been told about the batterystats.bin file... HOW does it make any sense, that your phone would know when it is fully charged after flashing a rom if your system was dependent upon the batterystats info to know when it is fully charged? because remember that information is lost when reflashing a rom, because it is stored in the /data/system/ directory. so after flashing a rom shouldnt your phone have ABSOLUTELY no idea what to display????? but instead you boot it up, and what do you see? the difference is nothing, you see a small difference in percentage that was spent while flashing your rom. and why is that? because the new kernel you flashed is now taking the voltage readings... not the batterystats file.
batterystats.bin "calibration" is indeed a myth. and you are not calibrating it, or anything, by deleting it. you are simply deleting a system log of what has been using your battery.
Lol I only wiped my stats when I had a new battery when I swapped em out or a bigger battery.
reaper24 said:
Lol I only wiped my stats when I had a new battery when I swapped em out or a bigger battery.
Click to expand...
Click to collapse
still isn't needed. lol. your charge capacity could be a bajillion mAh and as long as your voltage ranges for the battery are within the spec of the OS.. it will run perfectly.
have to understand that mAh and voltage are two completely different things. a simple way to put it is mAh is simply a measurement of theoretical sustained power output, and voltage is the actual power output.
voltage ranges are the same for a 4000 mAh battery for this phone, or a stock one. the difference (the mAh) is the amount of power it has stored for use.
think of it like.... gasoline... the gas tank is the mAh, and the MPG is the voltage. one has an effect on the other, but only in regards to sustained travel time.
cobraboy85 said:
still isn't needed. lol. your charge capacity could be a bajillion mAh and as long as your voltage ranges for the battery are within the spec of the OS.. it will run perfectly.
have to understand that mAh and voltage are two completely different things. a simple way to put it is mAh is simply a measurement of theoretical sustained power output, and voltage is the actual power output.
voltage ranges are the same for a 4000 mAh battery for this phone, or a stock one. the difference (the mAh) is the amount of power it has stored for use.
think of it like.... gasoline... the gas tank is the mAh, and the MPG is the voltage. one has an effect on the other, but only in regards to sustained travel time.
Click to expand...
Click to collapse
Lol im a mechanic I know all about gas and volts
How big of a gas tank does your phone have? I've put a half gallon in my phone but it still won't start/power up...
I was happy to learn that wiping battery stats isn't neccessary because it's now one less thing I need to go through when changing things up.
I will say I was wiping stats when changing roms because I simply didn't know any better.
I'm no guru with programing or engineering so I was part of the masses doing this. Lol enjoyed the placebo effect of thinking I was doing something essential to improve battery though.
Sent from my PG86100 using xda premium
aerajan said:
I was happy to learn that wiping battery stats isn't neccessary because it's now one less thing I need to go through when changing things up.
I will say I was wiping stats when changing roms because I simply didn't know any better.
I'm no guru with programing or engineering so I was part of the masses doing this. Lol enjoyed the placebo effect of thinking I was doing something essential to improve battery though.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Its technically not a placebo effect that battery life improved while "calibrating your battery"...but its not related to the wiping of stats.
During the calibration process, it takes time to cycle (fully charge and discharge) your battery...while this itself didn't affect battery life...it allotted time for the ROM and kernel combo to "settle in", and run more efficiently, which in turn, made people think that the positive effects of the "calibrating process" were due to the wiping an arbitrary stats file
Vinchenzop said:
Its technically not a placebo effect that battery life improved while "calibrating your battery"...but its not related to the wiping of stats.
During the calibration process, it takes time to cycle (fully charge and discharge) your battery...while this itself didn't affect battery life...it allotted time for the ROM and kernel combo to "settle in", which in turn, made people think that the positive effects of the "calibrating process" were due to the wiping an arbitrary stats file
Click to expand...
Click to collapse
Cool, thanks for the simple explanation. So is it still a good idea to calibrate the battery by fully charging then discharging it when switching roms?
aerajan said:
Cool, thanks for the simple explanation. So is it still a good idea to calibrate the battery by fully charging then discharging it when switching roms?
Click to expand...
Click to collapse
No, not necessarily....just wait a day or two after installing a new ROM and/or kernel before judging how it will run on your specific phone...
Basically, after flashing a ROM or kernel, just use your phone. If the battery is low, charge it, if its not low, don't charge it...don't stress about battery life for a day or two until everything sets in
So many people wait only an hour after flashing and scream "horrible battery life on this ROM/kernel!"....people need to learn patience
OK here is the official SGS2 I777 Battery saving thread. I don't mean to be a culprit and post "another battery saving thread", but I am. So get over it. This thread is meant to maintain the battery savings threads, all in one place. INCLUDING: Battery savings tips, philosophies, and other methods of efficiently managing the charge that your battery witholds. Since I searched through basically all of the 17 pages in both the I777 and regular SG2 to collect all this. NOTE: THIS THREAD IS NOT MEANT TO ADDRESS BATTERY DRAIN PROBLEMS OR ANYTHING OF THE LIKE. DO NOT POST YOUR PROBLEMS HERE. This is simply a collection of what I found to be the most essential threads and information regarding efficient use of battery charge and battery savings. I'll update this every few months, or as I see fit. I don't see things changing much since the way a battery works, and our android os will be relatively similar over the years.
I realize that people looking for this information could just go through all the threads like any other xda troll would be the first to point out, but I also recognize the noob community for this phone (I was once there myself) and would like to be helpful in providing it all in one place to prevent others from wasting their time, whether deserving or not
BATTERY SAVING THREADS:
*Basically what I did here is I just weeded out all the crap and gave you the threads that are actually of use*
Here is your basic, comprehensive Battery Saving thread:
http://forum.xda-developers.com/showthread.php?t=1234264
(It contains many simple changes that are obvious to some, including lower brightness, turning off animations, and then more complex changes such as under volting and fast dormancy)
More general tips plus freezing apps and undervolting:
http://forum.xda-developers.com/showthread.php?t=1335864&highlight=battery
More general tips: http://forum.xda-developers.com/showthread.php?t=1443603&highlight=battery+life
THE TWO THINGS THAT KILL YOUR BATTERY THE MOST:
Super AMOLED Screen: Now it's all apparent to us at this point that android screens (S-amoled's) kill very large amounts of battery. You will save copious amounts of battery if you do not use your screen as much, hence why half of the people posting their battery stats have screen on like once an hour for half a second. They basically don't use their phones.
Data/Radio: Ever notice that when you put your phone on airplane mode before you go to bed, when you wake up it's only gone down by about 1%? That's because you're not getting any service, and have no data coming in. Believe it or not, the phones hardware is pretty efficient. CPU's don't use very much idle power at all, and I expect that to stay the same, even with quad-core processors coming out. It's mostly the over air things (and screen ) that kill our battery. Data itself uses a **** ton of battery. On a daily basis (And I've tried just about all the roms; CM7,CM9, MIUI (GB and ICS), SammyTW ones, etc.) I use a considerable amount of data. I try to have my data on most of the day since I get facebook notifiations and send/receive MMS's, but on the days where I have it off for a couple hours I start to notice, damn, my battery is still pretty high
EDIT: Using Edge/2G saves a lot of battery if you're someone who needs data on most of the day. I recently switched to instead of intermitedly turning data on and off, just having Edge on all day (for notifications) and then switching to 3G when I needed to browse or use maps, etc. Idle usage of Edge vs. 3G is probably around 40% less battery consumption (my opinion), it works really well for me.
PHILOSOPHIES:
If you want to compare your own battery life with others to get a better idea about things, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1498303&highlight=undervolt
Juice Defender + others: I am a fan of this application. I used to use it for the first couple months I had the phone and it made a significant difference (mostly because of data deactivation). It makes 20-35% difference in savings from having not micro-managed anything yourself to then using the app. There are other variations of JD, GreenPower, Battery Booster, etc.
If you want more information about Undervolting, or the process, please check out:
http://checkrom.com/threads/more-ba...ry-before-posting-about-bad-battery-life.542/
Fast Dormancy effects the trafficway in which your data makes it to your phone, both effecting the speed at which is arrives, and the battery it consumes while doing so. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1111581&highlight=fast+dormancy
Underclocking and Overclocking: These are ways of tweaking your CPU usage. Underclocking is known for when you limit the maximum frequency, your CPU can clock to. So in laymans terms, what that transaltes to is your 1.2 GHz (1200 MHz) processor, can be changed to a 0.8 GHz (800 MHz) processor, if you were to underclock it to 800 Mhz. This is helpful to some almost completely dependant on your usage.
More elaborate, drawn out explanation: While your phone is idling, or sitting with the screen off, it is sitting at 200 MHz (lowest default - if you go lower than that your phone can become unstable [screen not turn on, etc.]), so underclocking won't help you improve battery usage much if you just keep your phone off most of the day. Undervolting would help more with that. if you however, find that you play lots of games, or mindless swipe across homescreens all day confused, or perhaps photo editing apps, or other things that use the maximum cpu frequency; then you will find that having your phone underclocked to 800 MHz, forces your cpu to work less during those heavy maintence situations, but in turn, prevents heavy battery drain. What this translates to in daily use: If you play angry birds, your phone's cpu might be jumping up to 1200 MHz (depends on your kernel settings - usually it's set to ondemand, in which case it will do so) during those swipes when the bird flys across the screen. However, that is not a very cpu intensive action, so if you were underclocked to 800 MHz, you probably wouldn't see any difference (lag, stutters) in your game play. However, if you were playing a 3D defense game, or esentially any other 3D game which requires you to scroll around the map, or has many many things on the screen at once (beyond fruit ninja and angry birds), then you would notice a difference in performance due to underclocking. I mention all of this because underclocking will be most effective during those situations, but it can also be the most hindering, in those same situations. All depends on how you're using your phone and what you're trying to achieve, while maintaining a certain level of quality.
Overclocking works the opposite, if you are trying to reach a certain level of performance (you just downloaded a new 3D MMO dungeon defense game and your phone is jittering and laggy during gameplay), beyond your default 200-1200 MHz clocked cpu, you may overclock up to 1600 MHz (some devs don't like you doing it - because it is essentially quite harmful for your cpu if used for a longer period of time), also depending on the kernel (again, devs created them) you may not be able to overclock, but on the majority you can.
To Underclock you will need an app called SetCpu (or equivalent) in order to change your over-underclock rate, as well as the scaling of your kernel (ondemand, performance [max frequency, all the time], conservative, etc.), also some roms have clocking options built in (such as AOKP).
For information regarding Underclocking check out: http://forum.xda-developers.com/showthread.php?t=1238580&highlight=underclock
If you're just straight up looking for a better battery saving rom, look here:
http://forum.xda-developers.com/showthread.php?t=1439179&highlight=battery
If you want to know more about Android OS, and how it goes about consuming battery, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1290020
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Last but not least, if you do most or all of these methods but you're still not happy? You can always turn your phone off, I heard that saves a lot of battery
If you care, leave thanks at the bottom. If not that's cool. I'm not into the whole publicity thing, I just like helping.
First, juice defender does not help at all and btw s amoleds save battery vs lcds
Sent from my SGH-I777 using Tapatalk 2
Very useful compilation of battery related threads. Good job VanillaCracker <claps>
Super AMOLED Screen: Now it's all apparent to us at this point that android screens (S-amoled's) kill very large amounts of battery. You will save copious amounts of battery if you do not use your screen as much, hence why half of the people posting their battery stats have screen on like once an hour for half a second. They basically don't use their phones.
Click to expand...
Click to collapse
AMOLEDs are supposed to be more energy efficient than LCDs I thought. That being said, I think one problem might be that many users of the former tend to keep their screens very bright because they are such a beauty to look at. I get what I think is good battery life by adjusting the brightness of my screen down when on battery only and by fine-tuning auto brightness settings.
One of the nice things about the S-AMOLED screen is that when it shows blacks, it's not using pixels. Pixels are actually turned off for the blacks. You can get further battery saving by using darker themes and inverted apps. Of course, that's not to everyone's liking. Me, I tend to like darker, tending towards minimalist screens as opposed to bright, busy ones, so it's a win for me.
Nick281051 said:
First, juice defender does not help at all and btw s amoleds save battery vs lcds
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
First, in reading my paragraph I was speaking of JD's helpfulness in relation to not micro-managing (turning off data, etc.) anything yourself. In this case JD helps a lot....
Second, I didn't bash any part of our AMOLED screens, but they use a lot of battery...idk anything about how they compare to other screens, and idc...that has nothing to do with my post. We all have I777's, and that's the way it is, so I'm not too concerned of other screens.
I will say, that in light of reading most of your comments (which are found everywhere) , evidently, that you do at least make a good point, most of the time.
Sent from my SGH-I777 using XDA
Yes data drains battery. If you are rooted (I hope you are since you are reading this on xda), you should get Droidwall. It's a firewall for your phone which limits certain apps to use network data, wifi data, or neither. Useful if you are also a little bit paranoid :silly:.
Another amazing app I also use is called llama. It is similar to tasker but it's free. This app allows me to set profiles and actions based on location (antenna mast instead of GPS to save battery) and other triggers. Not sure how ICS manages BT and Wifi scanning but those things use to drain my battery under GB so I got into a habit of toggling them on/off. Llama can do it automatically for me because I am lazy or sometimes I forget to.
I think any phone screen can be a big battery drainer if left on long and are set really bright. I have a habit of hitting the power button after I am done using it as opposed to just letting it shut off by itself.
xhepera said:
AMOLEDs are supposed to be more energy efficient than LCDs I thought. That being said, I think one problem might be that many users of the former tend to keep their screens very bright because they are such a beauty to look at. I get what I think is good battery life by adjusting the brightness of my screen down when on battery only and by fine-tuning auto brightness settings.
One of the nice things about the S-AMOLED screen is that when it shows blacks, it's not using pixels. Pixels are actually turned off for the blacks. You can get further battery saving by using darker themes and inverted apps. Of course, that's not to everyone's liking. Me, I tend to like darker, tending towards minimalist screens as opposed to bright, busy ones, so it's a win for me.
Click to expand...
Click to collapse
They are more efficient than LCD's, and I made no notion to say they weren't. I simply said that they were one of the two main culprits of battery drain. I'm not saying our phones suck cus they have AMOLED screens, it's actually awesome. I'm just saying, like any other phone, having the screen on lot is going to kill your battery.
Yeah on stock (rooted after a month) I used to use auto-brightness most of the time, and sammy's auto seems a little brighter than necessary by default (so I'd keep it on 40% some days). But after switching around to different rooms (before I started tweaking auto-brightness) having brightness at what I'd actually consider an adequate level, versus a little bit brighter makes a huge difference. When the screen looks just a little too dull in all situations it really takes away from the experience hah
Also, I know black pixels are technically off on AMOLEDS, but I've noticed on many occasion when using in a room with no light on at night (pitch black, essentially) that when rebooting and hitting the yellow triangle screen (mostly black) you can see the black area of the screen. It's not completely black. It's definitely a very real looking black, but it still looks like there's a backlight behind the screen. Is that the case? Can anyone confirm?
Sent from my SGH-I777 using XDA
. . .idk anything about how they compare to other screens, and idc...that has nothing to do with my post.
Click to expand...
Click to collapse
While it may not have anything to do with your post, per se, I think it's a good idea for people to be educated about our screens since many *are* coming from the LCD world and some of the rules they're used to don't apply. And some of those rules very definitely have an effect on battery life, like the rendering of blacks that I mentioned above.
VanillaCracker said:
They are more efficient than LCD's, and I made no notion to say they weren't. I simply said that they were one of the two main culprits of battery drain. I'm not saying our phones suck cus they have AMOLED screens, it's actually awesome. I'm just saying, like any other phone, having the screen on lot is going to kill your battery.
Yeah on stock (rooted after a month) I used to use auto-brightness most of the time, and sammy's auto seems a little brighter than necessary by default (so I'd keep it on 40% some days). But after switching around to different rooms (before I started tweaking auto-brightness) having brightness at what I'd actually consider an adequate level, versus a little bit brighter makes a huge difference. When the screen looks just a little too dull in all situations it really takes away from the experience hah
Also, I know black pixels are technically off on AMOLEDS, but I've noticed on many occasion when using in a room with no light on at night (pitch black, essentially) that when rebooting and hitting the yellow triangle screen (mostly black) you can see the black area of the screen. It's not completely black. It's definitely a very real looking black, but it still looks like there's a backlight behind the screen. Is that the case? Can anyone confirm?
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
That is the case with LED screens. In a mostly black scene, the individual pixels for the black area are not lit, however there is still a backlight lighting the screen itself which you may see bleed through. This is of course assuming the phone LED works at least somewhat similarly to a TV.
xhepera said:
While it may not have anything to do with your post, per se, I think it's a good idea for people to be educated about our screens since many *are* coming from the LCD world and some of the rules they're used to don't apply. And some of those rules very definitely have an effect on battery life, like the rendering of blacks that I mentioned above.
Click to expand...
Click to collapse
Yes I agree with you on that. It is more the manner of criticism which he spoke it that I am not favorable of, not necessarily the information which he shared. Which is why I wrote what I did at the end of my comment.
Sent from my SGH-I777 using XDA
Ahem....let me try to get his thread back on track.
I agree wih your comments vanillacracker. On a gb rom if I disable auto sync it helps me a lot wih battery life because he signal is really awful at my work. So I guess if the signal is bad it tries to sync amd keeps doing it for a long time whih really drains the battery. Disabling background data helps even more but I like to get my emails so I do not.
Sammy based roms are the best wih auto brightness quickness. Aosp roms are always slow to react. I hate when I step outside and the screen takes for ever to adjust. But the sammy based roms also have high default brightness as you mentioned.
Ps: do not feed the trolls. Just report them.
Sent from my SGH-I777 using xda app-developers app
Tophaholic said:
Ahem....let me try to get his thread back on track.
I agree wih your comments vanillacracker. On a gb rom if I disable auto sync it helps me a lot wih battery life because he signal is really awful at my work. So I guess if the signal is bad it tries to sync amd keeps doing it for a long time whih really drains the battery. Disabling background data helps even more but I like to get my emails so I do not.
Sammy based roms are the best wih auto brightness quickness. Aosp roms are always slow to react. I hate when I step outside and the screen takes for ever to adjust. But the sammy based roms also have high default brightness as you mentioned.
Ps: do not feed the trolls. Just report them.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
I will agree with you on most of your points and yes you are correct about the signal, the worse your signal is the more it affects the battery. Also, tasks aokp has the option now to change the reaction speed so if you like aosp but hate the reaction speed that is an option.
How exactly was I trolling? I know you're referring to me, I made a criticism of two points out of the entire thing and he tells me I'm a troll and that I need to take an anti depressant. What exactly did I do wrong?
Sent from my SGH-I777 using Tapatalk 2
Amobius said:
That is the case with LED screens. In a mostly black scene, the individual pixels for the black area are not lit, however there is still a backlight lighting the screen itself which you may see bleed through. This is of course assuming the phone LED works at least somewhat similarly to a TV.
Click to expand...
Click to collapse
Ohh alright that makes a lot of sense then. Thanks a lot, that was really helpful for me! Yeah cus in the completely black screen sometimes I can see the little splotches that look like it's where the backlight is squished against the screen or something. I noticed the marks are in a different spot on my current I777 than they were on my old one (replaced cus power button stopped working). Yeah it would make sense that AMOLED's came around the same time LED's started getting more popular in TVs too (few years ago), pretty baller technology for a phone! I'm loving it haha
Nick281051 said:
Way to come back with a personal attack, it's been proven in many cases that JD does not help and if anything hurts battery life. I used to use it and now I don't with no hit on battery. I'm not depressed thank you very much. I reported you for that one. I wasn't saying anything bad or personal but you had to go ahead and do it.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I disagree with you that Juice defender does not improve battery life. I am aware that obviously running an app in the background (Juice defender in this case) uses battery. But if the app is disabling your data (data uses battery..more than the juice defender app uses) then it's not possible for it to not increase battery.....just logic there. Anyway I'm sure there's been reports that say it does and does not increase battery, it's been obvious to me that it does, and it's logical to assume it does (if you know what I'm addressing) too. So I'll say to each their own. I do not wish to argue about things anymore, I will not edit my thread to your liking, you may simply dismiss that tip if you'd like.
I do not care about a report, I'm sure most people see the way I act and understand my reasoning. I probably overreacted a bit to your initial response , I've edited my accords. :cyclops:
BTW, VC, thanks for the compilation. Hopefully it will prove useful to folks!
VanillaCracker said:
I disagree with you that Juice defender does not improve battery life. I am aware that obviously running an app in the background (Juice defender in this case) uses battery. But if the app is disabling your data (data uses battery..more than the juice defender app uses) then it's not possible for it to not increase battery.....just logic there. Anyway I'm sure there's been reports that say it does and does not increase battery, it's been obvious to me that it does, and it's logical to assume it does (if you know what I'm addressing) too. So I'll say to each their own. I do not wish to argue about things anymore, I will not edit my thread to your liking, you may simply dismiss that tip if you'd like.
I do not care about a report, I'm sure most people see the way I act and understand my reasoning. I probably overreacted a bit to your initial response , I've edited my accords. :cyclops:
Click to expand...
Click to collapse
Thank you for being mature about it, that makes me infinitely less mad And i respect you for thay, ill edit mine as well
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
I will agree with you on most of your points and yes you are correct about the signal, the worse your signal is the more it affects the battery. Also, tasks aokp has the option now to change the reaction speed so if you like aosp but hate the reaction speed that is an option.
How exactly was I trolling? I know you're referring to me, I made a criticism of two points out of the entire thing and he tells me I'm a troll and that I need to take an anti depressant. What exactly did I do wrong?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Dude.....no offense but your first post was pretty disrespectful....hence my comment. However your quoted post was very useful. I believe in one thing...you give respect you get respect.
Now...getting back to the topic....good point about tasks rom....I did try it out but frankly speaking it is still not at par with sammy base roms wih regards to auto brightness. It does rock otherwise.
I am currently on ktoonsezs MIUI port (love that guy. No homo)....and m pretty happy with the auto brightness
Sent from my SGH-I777 using xda app-developers app
Tophaholic said:
Dude.....no offense but your first post was pretty disrespectful....hence my comment. However your quoted post was very useful. I believe in one thing...you give respect you get respect.
Now...getting back to the topic....good point about tasks rom....I did try it out but frankly speaking it is still not at par with sammy base roms wih regards to auto brightness. It does rock otherwise.
I am currently on ktoonsezs MIUI port (love that guy. No homo)....and m pretty happy with the auto brightness
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Yes now that I think about it I did come off douchey, and I apologize to the op for that
Sent from my SGH-I777 using Tapatalk 2
Tophaholic said:
Dude.....no offense but your first post was pretty disrespectful....hence my comment. However your quoted post was very useful. I believe in one thing...you give respect you get respect.
Now...getting back to the topic....good point about tasks rom....I did try it out but frankly speaking it is still not at par with sammy base roms wih regards to auto brightness. It does rock otherwise.
I am currently on ktoonsezs MIUI port (love that guy. No homo)....and m pretty happy with the auto brightness
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
If the only thing which is holding you from using aokp is the auto brightness, there is a flashable zip in the fluxxi thread which gives great settings.
Sent from my SGH-I777 using xda app-developers app
Amobius said:
That is the case with LED screens. In a mostly black scene, the individual pixels for the black area are not lit, however there is still a backlight lighting the screen itself which you may see bleed through. This is of course assuming the phone LED works at least somewhat similarly to a TV.
Click to expand...
Click to collapse
OLED screens do not have a backlight. That is one of the things that make them much more power efficient than LCD. The pixels themselves in an OLED display generate light.
I am running on a kernel and am getting reboots when the device gets too hot. Any scripts for me to run?
Sent from my GT-I9300 using xda premium
Someone?
Sent from my GT-I9300 using xda premium
disabling thermal throttle will permanently damage your processor, its specifically meant to safeguard the processor from higher temperature that it cant handle. u have to change it at the time of kernel compilation if you still need a fried cpu
xukaisheng said:
I am running on a kernel and am getting reboots when the device gets too hot. Any scripts for me to run?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
There is absolutely no way you are getting reboots because your device is too hot.
It gets throttled at 80c first, then at 90 or 100 and doesn't switch off til 120c.
There's no way you are hitting 120c.
Your reboots are due to something else.
"It's all in the game yo, all in the game..." - Omar Little
Hold a cell phone - anything, actually - that is at 120ºC is pretty much a lot worse than sticking your hand into boiling water: you'd have terrible burns.
Are you using the phone on a very humid, wet environment?
Simonetti2011 said:
Hold a cell phone - anything, actually - that is at 120ºC is pretty much a lot worse than sticking your hand into boiling water: you'd have terrible burns.
Are you using the phone on a very humid, wet environment?
Click to expand...
Click to collapse
That doesn't apply, it isn't the phone that is 120c, its the CPU.
I held my galaxy nexus as it shut down because it hit 110c, I didn't get burnt.
"It's all in the game yo, all in the game..." - Omar Little
bala_gamer said:
disabling thermal throttle will permanently damage your processor, its specifically meant to safeguard the processor from higher temperature that it cant handle.
Click to expand...
Click to collapse
you are wrong
TTC does not read temps its guessing the temp and it guessing it so wrong.
try to cool down your S3 and run a stability test then run the same test without cooling.
check the CPU speed with CPUspy.
TTC kicks in at the same time even if you cool your device down or not.
TTC has nothing to do with real world temps!
i have a Nexus 10 and i must take this ugly bug out of the tablet.
it stinks!
anyone knows how to disable Thermal Throttling Control or higher the limit?
it must be the same settings for every samsung device.
pg_ice said:
you are wrong
TTC does not read temps its guessing the temp and it guessing it so wrong.
try to cool down your S3 and run a stability test then run the same test without cooling.
check the CPU speed with CPUspy.
TTC kicks in at the same time even if you cool your device down or not.
TTC has nothing to do with real world temps!
i have a Nexus 10 and i must take this ugly bug out of the tablet.
it stinks!
anyone knows how to disable Thermal Throttling Control or higher the limit?
it must be the same settings for every samsung device.
Click to expand...
Click to collapse
Is it supposed to work the same way for both of them? As far as I know nexus 10 doesn't have a temperature sensor, is that the same case with, S3?
Hello!
I have some concerns about the heat of my phone. I've read some threads, but everybody has different opinions and readings.
Basically, with room temperature at around 27-28, during browsing (especially with lots of scrolling through images) the phone will heat up to 40-41C (even to 42 with some encouraging) within 5 minutes, so the bottom front and back are very hot.
During other use, like writing a few messages in Whatsapp, going though settings in programs, menus etc it will, slowly, but will go up to ~36-37C.
Is it normal, or should I prepare for war with the shop I bought it from?
are you rinning a custom rom/kernel or stock? if so which?
I've found that different roms heat up more than others.
I'm using anaraxia rom 10.3 build and have no heat problems and the battery life is amazing!
squ89r97 said:
are you rinning a custom rom/kernel or stock? if so which?
I've found that different roms heat up more than others.
I'm using anaraxia rom 10.3 build and have no heat problems and the battery life is amazing!
Click to expand...
Click to collapse
Using a stock rom. I'm not experienced enough to flash custom roms yet, and I would also prefer to not void the warranty, at least since I'm not yet certain that my phone is not damaged in some way
I'm not that bothered by the heat, my only concern is whether this behavior is normal or not, and whether I should start the whole warranty war sooner.
Well I wouldn't be bothered tbh.. I've had 42°c while heavy usage and charging. If your phone overheats and burns out send it in then.. No point doing it now unless your warranty is out soon?
I tried to attach a screen shot for your peace of mind - Edit: Post below
Sent from my GT-I9300 using xda premium
Edit- From previous post
NatTheCat said:
Edit- From previous post
Click to expand...
Click to collapse
41.5, but how much did you strain the device? Today in a room where the temp was +-30-31C, while browsing XDA (which seemed to strain the device a bit) I got up to 44...
Also checked the idle tempretures, it's usually the same as the room temp at the moment, so it's not that it's always hot, just when used.
R: [Q] Regarding heat
Its weird that it should heat up while doing normal stuff...im on international version and last time it heated up was while i was playing modern combat 4 online after 2 hourse while connected to charger....so maybe youve got prpblems if it heats up like that only by viewing messages. I watch videos and browse the internet everyday, it never heats up. Im using stock rom and syiah ketnel...
Sent from my GT-I9300 using xda app-developers app
While doing regular stuff like messages etc it doesn't heat up much. The first test was done while browsing, but I kept it at 40% load and 1400mhz, so it can't not heat up. I think that room temperature matters, I live in a hot area, today was 31C.
s it normal, or should I prepare for war with the shop I bought it from?
Click to expand...
Click to collapse
I don't know where you live but in most civlized countries you can go in all guns blazing and they have to prove you wrong within the first year or so =) They will, of course, try to tell you sth different...
but will go up to ~36-37C.
Click to expand...
Click to collapse
I've had that "problem" (well it's not really a problem, only a minor annoyance during warm seasons) with stock rom too.
Didn't have that much experience with other roms and kernels (I'm very picky with features) but I never noticed it on Siyah with Wanamlite.
Stock kernel is far too happy to ramp up clock speeds to slightly improve response time (or so is the theory... practice is not noticeable) so it will heat up your device. More heat of course also means higher battery drain .
Note that a protection around your device usually keeps you from noticing this fact (while the phone gets even warmer due to worse cooling)
R: [Q] Regarding heat
d4fseeker said:
I don't know where you live but in most civlized countries you can go in all guns blazing and they have to prove you wrong within the first year or so =) They will, of course, try to tell you sth different...
Click to expand...
Click to collapse
I dont know where you live in but in italy you have first to prove them you bought the phone. Then prove you bought it from them. Then youre f**ked anyways cause youll never get a refund, ever...
Sent from my GT-I9300 using xda app-developers app
d4fseeker said:
I don't know where you live but in most civlized countries you can go in all guns blazing and they have to prove you wrong within the first year or so =) They will, of course, try to tell you sth different...
I've had that "problem" (well it's not really a problem, only a minor annoyance during warm seasons) with stock rom too.
Didn't have that much experience with other roms and kernels (I'm very picky with features) but I never noticed it on Siyah with Wanamlite.
Stock kernel is far too happy to ramp up clock speeds to slightly improve response time (or so is the theory... practice is not noticeable) so it will heat up your device. More heat of course also means higher battery drain .
Note that a protection around your device usually keeps you from noticing this fact (while the phone gets even warmer due to worse cooling)
Click to expand...
Click to collapse
I've also noticed this heat problem, I'm also on a stock rom.
Using the "CPU power saving" in the Power Saving setting has helped, so I figured it was the kernel ramping itself up.
It's not that noticeable to run at a lower cpu frequency except that some games are sometimes choppy now
The fact that stock rom likes to ramp up the clock speeds is correct. Just by simply fast scrolling back and forth through pages on forums etc makes it go up to 1400mhz and keep it at 40% load, that's why I get the higher temps.
STANDARD DISCLAIMER: I am not responsible for any damage caused to your phone or loved ones.
MUST HAVE ROOT.
The PROBLEM:
This mod is for phones that throttle heavily and lag during charging / heavy use/ gaming. Seems like it affects people on stock-based roms rather than AOSP/lineage based roms since the thermal file is deleted/edited already. Switching kernels does not help the throttling at all. Using any kernel or cpu app (EX kernel, kernel aduitor), you should see that the cpu freqs throttle down to 652mhz on the small cluster and 1036mhz on the big cluster when charging or after heavy use. The throttling isn't caused by thermals since the CPU temps and battery temps are well within acceptable levels (below 50 degrees cpu and below 25 degrees battery).
Seems like the only reason LG does this is to prolong battery life rather than keeping performance at acceptable levels.
The second issue is the SLOW charging when your screen is on. Ampere reports a maximum charging rate of ~300mah when charging (qc3 or regular) before the mod. This mod will increase it to ~1000mah when screen on (I'm unsure how to increase it further). Screen off charging is unaffected and is still Quick Charge.
THE FIX:
Download my "thermal-engine-8996.conf" file here: https://drive.google.com/file/d/0B0W3xXHgfOxvLUpKNWhrWDE0TDg/view?usp=sharing
Use a root explorer.
Backup your old one in root/system/etc (or just rename it to thermal-engine-8996.conf.bak).
Put the new one in root/system/etc
Edit: apparently it downloads as a .txt file so change it back to .conf
Change permissions to rw-r--r--
Restart and enjoy lag free charging + increased charging speed!
This will make your device slightly hotter and possibly less battery life during heavy use but that's a given.
Thermal throttling is NOT affected (CPU speeds still throttle after 80 degrees with my testing)
Flashing rom updates WILL overwrite the file so you will need to replace it again.
Different versions:
Reduced charging speed (to 600mah) when screen on (To reduce heat): https://drive.google.com/file/d/0B7VVzSKFTGVkNHBnWXNYY2JJdEU/view?usp=sharing
Reduced max speed (to 1824mhz) but kept 1000mah charging when screen on (should reduce heat when doing intensive tasks): https://drive.google.com/open?id=0B7VVzSKFTGVkWjlnUF84SDc0N0k
Reduced charging speed (600mah) + max speed (1824mhz) to reduce heat even more and will still help reduce lag:https://drive.google.com/file/d/0B7VVzSKFTGVkV2ZoTU1sS2YtOUk/view?usp=sharing
What I did:
Under [KRYO_SS] in the conf file, I edited the "device_perf_floor" value to 2150000 instead of the stock 1036800. This will cause the phone to never throttle below 2150mhz big cluster and 1593mhz small cluster when charging/heavy use. If you are using an kernel that supports overclocking, this value can be set higher (to your max big cluster mhz). The small cluster mhz will automatically scale up since there's no value for it anyways. I think this entire section is just to save battery life as I see no other benefit from throttling when you're charging (when temps are low). Honestly, you can probably delete the whole section under [KRYO_SS] and it'll keep it at max mhz but I rather have some control over it.
For increased charging speed when screen on, I edited the values under [CHG_MONITOR]. I also deleted the entire [PA_MONITOR] and [LCD_ON_MONITOR] section. This increases the charging speed to ~1000mah from ~300mah but I can't seem to increase it further when screen on. Might be due to another setting I haven't found yet.
I also increased the GPU clocks to decrease throttling but I haven't found GPU throttling to be a problem at all before the mod so this probably won't affect performance.
The only other phone I have found that has the same thermal conf file is the LG G5 thread here: https://forum.xda-developers.com/lg-g5/help/reduce-gpu-thermal-throttling-help-t3471510
Seems like they were doing it for the GPU throttling however.
Let me know if anyone is having issues with this mod or wants to implement it in their rom
wow awesome. seems easy enough. I'm gonna try!
Sent from my LG-US996 using Tapatalk
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
wonder if you could figure out a way to stop the screen on service from being dozed so hard that it lags to turn the screen on when it's sitting for like 30 seconds. so slow to turn on, can't stand it.
Sent from my LG-US996 using Tapatalk
Got it loaded. Works like a charm. A huge thank you! ???
Don't forget
Don't forget to rename the file from .txt to .conf after pasting. THANK YOU!!!!
jreed3786 said:
Don't forget to rename the file from .txt to .conf after pasting. THANK YOU!!!!
Click to expand...
Click to collapse
Good point. I noticed that also. Took care of it. With a little common sense. But yes glad your telling the thread this. For many it would of caused problems.
storm68 said:
Good point. I noticed that also. Took care of it. With a little common sense. But yes glad your telling the thread this. For many it would of caused problems.
Click to expand...
Click to collapse
Anytime, buddy! Thank you for your work!
i love you
dude i made an account for the first time ever just to come here to comment and tell you that you are awesome and i love you and i just applied the fix and i'm so happy!
jayochs said:
wow awesome. seems easy enough. I'm gonna try!
Sent from my LG-US996 using Tapatalk
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
wonder if you could figure out a way to stop the screen on service from being dozed so hard that it lags to turn the screen on when it's sitting for like 30 seconds. so slow to turn on, can't stand it.
Sent from my LG-US996 using Tapatalk
Click to expand...
Click to collapse
Haven't had that issue so not sure how to fix it. I'm using a custom rom (WETA) so I probably can't replicate it. Maybe try a different kernel?
eh I did. the one custom kernel for us996, the guy said it had faster wake but it actually didn't. lol. stupid v20.
Sent from my LG-US996 using Tapatalk
is there a way to verify these changes are in effect? I'm planning to put this into Magisk as a module, but not sure how to verify...
dimm0k said:
is there a way to verify these changes are in effect? I'm planning to put this into Magisk as a module, but not sure how to verify...
Click to expand...
Click to collapse
If you use a cpu monitoring app (cpu-z or kernel aduiter), you will see the cores don't throttle when you have the phone plugged in after applying the mod. Ampere will also report a maximum charge rate of about 1000mah when screen on.
Holyman007 said:
Let me know if anyone is having issues with this mod or wants to implement it in their rom
Click to expand...
Click to collapse
Freakin sweet! ? Came here to fix the stupid throttling but you also improved the charging speed when screen is on too. Mucho thanks!
Congrats on the XDA portal. ???
storm68 said:
Congrats on the XDA portal.
Click to expand...
Click to collapse
Haha thanks! I just read it. Surprised that our forum gets any love.
KUSOsan said:
Freakin sweet! Came here to fix the stupid throttling but you also improved the charging speed when screen is on too. Mucho thanks!
Click to expand...
Click to collapse
Glad it worked for you
Holyman007 said:
Haha thanks! I just read it. Surprised that our forum gets any love.
Click to expand...
Click to collapse
This Doug Lynch guy really likes to share projects.
As for this mod, I'm kind of scared at how quickly my phone is charging now...
EDIT: Lynch, not Lunch lol. Autocorrect...
Zacharee1 said:
This Doug Lunch guy really likes to share projects.
As for this mod, I'm kind of scared at how quickly my phone is charging now...
Click to expand...
Click to collapse
Lol! I call it "my charger on steroids" mod.... Good job! ?
I just want to make a point that if you are doing this mod it is highly advisable to switch to a QC 3.0 charger for your battery to maintain its lifetime. One of the reasons that this was put into place is because QC 2.0 pushes a LOT of voltage to the device to quick charge it when the screen is off and the phone is idle because there will be less overall heat generated in the device (which LG wants to avoid after the bootloop situation it can't seem to get out of). QC 3.0, which the v20 is capable of using, charges faster and cooler than its 2.0 counterpart and will be easier on your battery lifespan. A QC 3.0 charger is more efficient overall and should be going on sale soon because QC 4.0 is on the way/out now with the new Samsung devices.
And yes, you can swap this battery out if the first one won't hold a charge anymore, but the longer you keep the first one the later you have to pay for the second one (assuming you keep the phone that long). Also, you do not want the components to bake in case the v20 uses the same manufacturing technique as the 5x did.
AlkaliV2 said:
I just want to make a point that if you are doing this mod it is highly advisable to switch to a QC 3.0 charger for your battery to maintain its lifetime. One of the reasons that this was put into place is because QC 2.0 pushes a LOT of voltage to the device to quick charge it when the screen is off and the phone is idle because there will be less overall heat generated in the device (which LG wants to avoid after the bootloop situation it can't seem to get out of). QC 3.0, which the v20 is capable of using, charges faster and cooler than its 2.0 counterpart and will be easier on your battery lifespan. A QC 3.0 charger is more efficient overall and should be going on sale soon because QC 4.0 is on the way/out now with the new Samsung devices.
And yes, you can swap this battery out if the first one won't hold a charge anymore, but the longer you keep the first one the later you have to pay for the second one (assuming you keep the phone that long). Also, you do not want the components to bake in case the v20 uses the same manufacturing technique as the 5x did.
Click to expand...
Click to collapse
Hmm interesting. Yeah the thought of restricting the voltage to prevent any heat build up at all came to mind. I still think they overdid it with the throttling to the point where it is unusable when charging.
The thermal file can be edited so it throttles a bit or halfway which I explained in the op if anyway is worried about the heat.
Holyman007 said:
Haha thanks! I just read it. Surprised that our forum gets any love.
Click to expand...
Click to collapse
It gets some love.