Database Info

graphics games on g2x -- unstoppable battery killer??

So, after incorporating ALL battery fixes for the g2x, I get great battery life -- easily more than a day with normal use (about 1.5 hrs of talk/day, about 1 hr of internet, lots of texts, etc)....
However, if I play 9 innings: pro baseball or NFS, after I finish playing, my battery life blows...it will go down by 1% every few minutes or so. Has anyone else had this issue, and does anyone know of any fixes??
I use ATK and Superpower, but they aren't doing much to save my battery from this problem.

Lucky you, my battery gets drained 1% every minute just from texting. Don't know what is wrong with it, calibrating it now

3D gaming will always be intensive on a phone/device. Especially if the game doesn't utilize the tegra 2 processor

Frank29 said:
3D gaming will always be intensive on a phone/device. Especially if the game doesn't utilize the tegra 2 processor
Click to expand...
Click to collapse
True, but what I'm getting at is that it continues to drain the battery at an increased rate after I've closed the game -- that seems really weird to me. It's like the game starts some hidden process that continues running in the background irrespective of whether the game is still going.

Erislover said:
True, but what I'm getting at is that it continues to drain the battery at an increased rate after I've closed the game -- that seems really weird to me. It's like the game starts some hidden process that continues running in the background irrespective of whether the game is still going.
Click to expand...
Click to collapse
Try using Watchdog or Wheres My Droid Power after playing the game to see if it is still eating up CPU in the background after closing.

my philosophy on overclocking

Seems like some recurring discussion in past threads:
1 - why should we even bother overclocking if we’re not a gamer.
2 - won’t we damage our device with overclocking.
I haven’t seen definitive answers posted anywhere, and I certainly don’t have one.
Maybe in that case (I have no definitive answer), I should probably just keep my mouth shut.
It may be the case, if so let me know.
For whatever reason, I have some strong opinions and I feel it would be useful to share my opinions and the reasons I have formed those opinions.
Take them or leave them or add to them... up to you.
Point out to me if you think I am grossly mistaken.
1 - why should we even bother overclocking if we’re not a gamer.
Click to expand...
Click to collapse
There is constant tradeoff between battery and performance.
Underclocking will help you save battery. How low you want to underclock depends on what you can tolerate.
But what you can tolerate depends on your user experience, which can be dramatically impacted by use of overclocking at other times.
The perfect example for me is a program which is slow to start up. In my case it is Memento database with 1000+ records, takes a long time to read in (I think the program does some sorting every time it opens). That is a minor annoyance. If I were to underclock it will start even slower, I’m going to get impatient and set my speed back up.
But think about this:
1 - Using Tasker you can apply cpu profiles upon application launch and remove them after a predetermined length of time. I can give the program a blast of 1600M-hz when it starts, then set it back where it was after predetermined period (for example 10 seconds).
2 – Setcpu is not quite as flexible as tasker in this regard. With setcpu we can create a profile to occur when we launch the program like Memento, but we just can’t incorproate a time delay into the logic (it will stay on the higher profile as long as the program runs in the foreground).
3 - There may be circumstances where this setcpu behavior is what you want... it will give you faster response whenever the program is in the foreground, and will yield to lower priority profiles whenever the program goes to the backghround.
(I haven’t investigated how to make make Tasker and setcpu play nicely together yet).
So, if you speed up the things that cause noticeable delay for only a short time, or particular applications which seem to run slow then you can probably be more satisfied with your underclock in the other times. In the overall picture, I think the overclock capability can ironically be used as part of a strategy to save battery (unless you just like overclocking just to see things zip accross your desktop and menu’s pop in and out faster than you can blink, I’m starting to get spoiled with that behavior on my phone in its new configuration, partially from overclock..I’m sure others get even better in their configuations..).
2 - won’t we damage our device with overclocking.
Click to expand...
Click to collapse
On this I would say no, as long as you are careful about not running it in conditions that create high temperature. .
(you may have stability problems as you guys know, an entirely different subject).
The physics of the damage are all related to temperature. There are many variables affecting temperature that the designer is unaware of and so he builds in margin for the worst cause unknown future occurence (he has to consider maybe phone will be in desert with 100F ambient, and on the charger, while the user tries some heavy surfing with gps, all at the same time, so he limits cpu to 1200Mhz).
We on the other hand know what are the conditions of our phone and what it’s likely to see and what it’s doing at any given time, and setcpu provides additional ability to monitor and adjust.
Here are example setcpu profiles I came up with to protect myself from damaging temperatures (Zen's kernel A/1600)
Priority 100: If batter temperature > 50C (122F),establish conservative governor 100-400Mhz
Priority 90: If batter temperature > 45C (113F),establish conservative governor 100-800Mhz
Priority 80: If battery temperature > 40C (104F), establish conservative governor 100-1200Mhz (in the event I was overclocking, this profile will stop it when battery temp exceeds 40C, all other profiles that may invoke overclocking are lower priority than 80).
This is just from judgement, knowing that I’m normally < 104F battery temp during light use and don’t want to overclock when I’m outside that normal light use zone. Some further curtailment of cpu max frequency occurs as battery temperature climbs above that. (which I would not have even had the benefit of if I were casual user with no overclocking and no setcpu).
As long as you’re limiting temperature, you should not be worried about damage imo. By the way, of course overclocking is not the only thing to affect temperature: things like phone case (thermal insulation), charging, gps, heavy use etc all have an effect. I'm not quite sure why sometime cpu overclocking gets singled out in a dangerous category all its own without any discussion of other things that affect tempertaure.
In fairness, you may point out that what we monitor is battery temperature and not the same thing as cpu temperature. It’s a good point. Increase in heat generated at the cpu causes more of an increase in temperature at the cpu then it does at the battery. But it's question of how much different. there's a matter of how much. Why do you think it is that Samsung didn’t give us cpu temperature indication? I think because they knew battery temperature is close enough. Even on newer flagship Behemoth Samsung Note, I’ve read you still only get battery temperature, no cpu temperature. If cpu temperature was that much different, they surely would have provided a separate indication of cpu temperature (cpu is after all a much more critical component than replaceable battery).
And why should we expect battery temperature to be representative of cpu temperature on our phone, when the same is not true on a pc? I think I can answer that:
* PC has things all spread out. There is air flowing through. The air picks up heat from each component from heat sinks by convection. The component temperatures are not tightly coupled together.
* Phone (in contrast to pc) has everything compact inside one itsy bitsy case. There is no air flowing through. That means heat transfer inside the phone is not by convection but by conduction. For most effective conduction, all components are attached with high thermal-conductivity path to the phone structure and the exterior surface of the phone. The heat transfer from phone to ambient is primarily convection. So we have effective heat transfer (conduction) among the components of the phone and less- effective heat transfer (from phone to environment). It tends to tell us that there will not be big difference in temperature among phone components. The big temperature difference that occurs is between the phone and the ambient air.
I don't have access to a phone which has both cpu and battery temperature indicators. If someone does, it would be interesting to hear how close those two temperatures follow each other.
===================================================================================
Edited to add: searching other threads suggests there can maybe be a substantial differencebetween cpu temperature and battery temperature. That makes me a little less certain. At least we can use battery temperature as a gross indicator that the cpu isn't seeing excessive extra heat from other non-cpu sources while we're overclocking it. Certainly having profiles in place to limit overclocking when battery temperature is high can only help protect us. But is it a false sense of security which can lead us astray? I dunno. I have already done a stability test at 1600 for quite awhile and there's no damage in sight, so if there is any damage potential, then it is only an accumulation over time. I don't plan on leaving Fmax at 1600 all the time anyway, since it would kill the battery. My planned strategy reserves the 1600 overclock for occasional playing around, and boosts when I need them like like my Memento database. My gut says that approach is just fine. Interested in hearing any other thoughts, experiences, links that may shed light.

N5 burning up with some games

I generally get great battery life using regular apps throughout the day. But many games seems to eat up battery life quicker than I would have thought. That coupled with how hot my phone gets, I'm a little worried there may be an issue with my phone.
The two games where my phone feels like it is burning up are Plants vs Zombies 2 and Anomaly 2. After playing a session, a quick look at the battery graph shows an extremely steep drop.
Is this normal? Maybe it is, but it doesn't feel or seem right.

flintdragon said:
I generally get great battery life using regular apps throughout the day. But many games seems to eat up battery life quicker than I would have thought. That coupled with how hot my phone gets, I'm a little worried there may be an issue with my phone.
The two games where my phone feels like it is burning up are Plants vs Zombies 2 and Anomaly 2. After playing a session, a quick look at the battery graph shows an extremely steep drop.
Is this normal? Maybe it is, but it doesn't feel or seem right.
Click to expand...
Click to collapse
its normal. cpu and gpu intensive games will warm up your device to a toasty level. but that why they make the phone have a thermal throttle. when it hits a certain temp, you phone will automatically reduce the cpu speed to cool down a little. but the heat from gpu/cpu intensive games is more than normal, its expected. btw, the safety shutdown temp for the n5 is 100C, which youll never reach because of the thermal throttle, only if you have root and disable thermal throttle, then it could hit the safety shutdown temp

I know about the problem with Plants vs Zombies 2, it eats through battery like crazy. I don't think that there is an issue with your phone, because your battery doesn't drop like that at any other intensive game, does it?
Sent from my Nexus 4 using XDA Premium 4 mobile app

I've noticed the exact same thing with PvZ 2. It's addictive as all hell, but chews through my battery.
I really wish they would release it on the Amazon Appstore so I could put it on my Kindle Fire. Unfortunately, because of the Google Play integration you can't even sideload it to a Kindle, you just get a black screen when you try to launch it.

Tudorrrr said:
I know about the problem with Plants vs Zombies 2, it eats through battery like crazy. I don't think that there is an issue with your phone, because your battery doesn't drop like that at any other intensive game, does it?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't play any intensive games actually and I wouldn't even catagorize PvZ2 as intensive. Maybe it is just suboptimally coded apps. Anomaly2 isn't even really that intensive. Not like a FPS/3D game anyway.

flintdragon said:
I generally get great battery life using regular apps throughout the day. But many games seems to eat up battery life quicker than I would have thought. That coupled with how hot my phone gets, I'm a little worried there may be an issue with my phone.
The two games where my phone feels like it is burning up are Plants vs Zombies 2 and Anomaly 2. After playing a session, a quick look at the battery graph shows an extremely steep drop.
Is this normal? Maybe it is, but it doesn't feel or seem right.
Click to expand...
Click to collapse
PvZ2 is terrible. Get Franco kernel + his updater app. Set the per app mode of PvZ @ 652MHz. Still runs fine. The only difference you will notice is when the last big wave hits, there can be a little slow down, but it goes away quickly. With all 4 cores running at 652MHz, there is virtually no heat. Will get you 1+ hour more game time. I'm experimenting with underclocking the GPU for it as well. I don't want to underclock the phone when I'm just using apps, but these games are using much more power than they need to be using. 4x, at least.
I think it's poor coding, as @flintdragon suggested.

Undervolting

Hello guys
I'm not a new user in kernels or ROMs .
I have a low-decent battery life ,and I'm sure there's a way to get a better battery life with undervolting .
I want to know
what is "undervolting" ?
What is the biggest damage it can cause?
What is PVS?
How do I know ,how much I can UV?
What are the steps to undervolt?
What I gain from UV (despite battery life)?
For your info ,I'm using AOSPAL ROM +FAUX's latest 16u kernel .
Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app

http://forum.xda-developers.com/showthread.php?t=2537000
Sent from my Nexus 5 using Tapatalk

Hi,
Most of your questions have a reply:
About undervolting: http://forum.xda-developers.com/google-nexus-5/general/nexus-5-undervolting-thread-t2537000.
CPU binning: http://forum.xda-developers.com/google-nexus-5/general/cpu-binning-nexus-5-t2515593.
The "risks" are instability like hard reboot, SOD, etc.... To find a "safe" value you will need to test by yourself to find what undervolting your CPU can handle, not all CPU's are equals.
Undervolt by steps like - 25mV, don't set your new values at boot unless your are sure it's stable (or you could encounter bootloop), test for a few days under different conditions (as your use).
The gain apart battery life (but you will not gain that much as people tend to think) is a little less heat, but again nothing huge..., better is to test by yourself and see what you will gain... or not.
Battery life depends mainly of your use, apps, signal quality and settings like, screen brightness, synchro, CPU governor, etc... In my opinion check first what could be the cause of your low battery life (and what is low battery life for you???) before play with undervolting.

As said above, undervolting will get you very minor battery life increases.
More than likely you have an issue, or its just your setup and usage giving you the battery life you are seeing.
Undervolting will not change any of this.... You'll gain only minutes of battery time.
Try some troubleshooting in the below thread to see if you have an issue, or how to setup for better battery life. Read through it a bit, from the last page and work back a bit. You can post meaningful screenshots there too. From gsam or BBS.... not the stock battery screen, it has no real useful info for finding issues. Good luck!!
http://forum.xda-developers.com/showthread.php?t=2509132
Nexus 5 Battery Results

I've been undervolting many systems for many years, primarily Linux desktops and some servers, and the primary benefit is that you get less heat output which means when running cpu-intensive tasks the temperature climbs slower so the throttling of the clockspeed kicks in later, so your phone will be faster in certain situations. If you take a phone which has been idle for a while and run a benchmark, and then immediately run that benchmark again, the 2nd time gets a lower result as the phone is still hot from the 1st. This makes drawing conclusions about settings really dificult but it illustrate that throttling from heat is affecting speed.
For most users their perception will be the phone runs cooler.
You do undervolt at each step in the processor's frequency, and each step is a trial+error activity, the throttling I mention means finding a stable under-volt at the higher frequency which is labour-intensive,i.e take the max clock, and undervolt it a little, run a benchmark which forces it to run at high clockspeed, and if it passes that test then run it again at the next step down in frequency. Once you've got the most stable top clockspeed, then do it progressively for all the other voltages on the way down.
In some platforms in Linux and Windoze, we wrote scripts which save the stable voltages and then undervolts a little and runs a stress-testing benchmark and if the system hung it wouldn't save the current voltages so the previous higher voltages were safer, stick that script in a startup script area and leave the compute to do many self resets, and you've calculated your device's voltage range. I wonder if someone has that done for Android??? For a laptop the FAN would run slower saving battery time and for laptops that would lead to say 20% better battery life but on a phone it won't make much saving as no fan.
Your phone will run most of its time (like 95%) at its lowest frequency, so for effort/benefit just focusing on dropping its voltage will gain the most in the phone running cooler.
Battery life improvement is marginal, if you look at your battery stats its down to your application settings and screen brightness, i.e. how you use and what you do with your phone. So if your battery life is bad, use your phone less!
I carry a slim USB battery, it is the $/effort/benefit the best thing you can do, $20 doubles your battery life, if you get one with a 1.5A-2A output in just a few minutes when the phone doesn't mind a battery attached, will dwarth every possible tweak and hack anyone can form in benefit.

Help with overheating problem

So I have an LG G4 running Octos-M with Xposed and a handful of modules. Recently my phone has been getting very hot doing mundane tasks. For example, while streaming YouTube videos at 480p it will sometimes, not all the time for some reason but usually, slowly get hotter and hotter. I don't know where it would cap out because I've never let it get past 53C, and usually stop using it at about 46.
It does it in Snapchat basically all the time and in games like Marvel Puzzle Quest a little less than half the time. It can't be good for the phone and it slows way down when it gets too hot.
Doing some looking into it I believe it is a GPU issue. When watching videos the GPU usage spikes to 70-100%. The high usage seems to cause the heat. The CPU usage rarely steps above 40-50% but I don't know of it's related or not. The GPU is just a hunch.
Does anyone have any suggestions? It's getting to the point where the phone is unusable due to heat so I'd like to resolve, or at least mitigate, the issue.

merger3 said:
So I have an LG G4 running Octos-M with Xposed and a handful of modules. Recently my phone has been getting very hot doing mundane tasks. For example, while streaming YouTube videos at 480p it will sometimes, not all the time for some reason but usually, slowly get hotter and hotter. I don't know where it would cap out because I've never let it get past 53C, and usually stop using it at about 46.
It does it in Snapchat basically all the time and in games like Marvel Puzzle Quest a little less than half the time. It can't be good for the phone and it slows way down when it gets too hot.
Doing some looking into it I believe it is a GPU issue. When watching videos the GPU usage spikes to 70-100%. The high usage seems to cause the heat. The CPU usage rarely steps above 40-50% but I don't know of it's related or not. The GPU is just a hunch.
Does anyone have any suggestions? It's getting to the point where the phone is unusable due to heat so I'd like to resolve, or at least mitigate, the issue.
Click to expand...
Click to collapse
Use the KA mod(Kernel Auditor) that is built into the Tentacles app in your app drawer, if you don't see the Tentacles app in app drawer then just go to system settings>about phone>Build date and tap the build date once and you'll have the Tentacles app. Use KA to lower the CPU/GPU settings to reduce the power consumption. If your OctOS doesn't come prepackaged with the Kraken kernel built in then consider configuring some KA settings on the stock OctOS kernel then try flashing the Kraken kernel if one exists for your device, then configure KA settings with that kernel and compare results, use the kernel and settings that give you the best results.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE