Database Users

ICS Tweaked..

ICS would kill my battery in mere hours... so I stuck with BlackICS lastest nightly.
I am sorta new when it comes down to andriod... I was IOS fan... after getting my inspire which has more speed, ram, customization. Well $#@* apple. Jailbreaking was easier, but your device always looked like the person next to you, I like uniqueness, and the ability to tell my phone what to do when to do it, and how to do it.
So waiting 3 long hours in the doctor's office I thought of several different ways to tweak ICS to my standards. alais this is my first step in tweaking.
16 Hrs from 46% (Orginal stock battery)
I have a few other tweaks working.
Kudos to Lord for his Kernel and Rom line-up

I too am a huge fan of LoRd and his ICS builds! What exactly did you tweak to achieve this low battery usage?

Pongt09 said:
ICS would kill my battery in mere hours... so I stuck with BlackICS lastest nightly.
I am sorta new when it comes down to andriod... I was IOS fan... after getting my inspire which has more speed, ram, customization. Well $#@* apple. Jailbreaking was easier, but your device always looked like the person next to you, I like uniqueness, and the ability to tell my phone what to do when to do it, and how to do it.
So waiting 3 long hours in the doctor's office I thought of several different ways to tweak ICS to my standards. alais this is my first step in tweaking.
16 Hrs from 46% (Orginal stock battery)
I have a few other tweaks working.
Kudos to Lord for his Kernel and Rom line-up
Click to expand...
Click to collapse
His tweak was using it as a paper weight...in the screen shot directly under the graph toy see dark blue bars...those are indicating the screen is on...his screen was on for maybe 14% of the time...however he still got decent battery life.
Sent from my Desire HD using XDA

trh1341 said:
His tweak was using it as a paper weight...in the screen shot directly under the graph toy see dark blue bars...those are indicating the screen is on...his screen was on for maybe 14% of the time...however he still got decent battery life.
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
I'll put it a different way.
No matter what the screen state was I would only usually get a max of 5-7 hours before i would have to charge it.
Seems like deep sleep never kicked on...
What ever the reason for the loss, I did some research on everything from his ICS all the way down to the battery... which is the same one that came with the phone I wanna say 2010.
1) Used System tuner pro...
1.1) Removed unwanted processes from running. (I had mine almost bare)
1.2) Removed unwanted apps.
1.3) Auto kill was set to Very aggressive
1.4) Used conservative Gov. with tweaked thresholds
1.5) Screen-off behavior set to powersave with max 800mhz
1.6) Set deadline SIO
1.7) Auto kill was set to kill at screen-off
1.8) Boot settings enabled all tweaks on boot complete
2.0) Used lux auto brightness to set custom brightness.
( I actually found one of his newer kernels would only read like 4 lux states)
( his lastest one seemed to be alot better, he also added custom brightness in the settings)
3.0) Used build.prop and edited different values.
3.1) Used 3g/2g inside buildings via tasker or you could use a toggle
4.0) Killed the battery to 0% then charged it overnight
5.0) Sync was forced every 8 hours via 3g or wifi
5.1) Wifi disabled radio.
5.2) Radio limited to power output
I believe that was pretty much all I did.
Thank you for your time.

Reason for bad Battery life, sticky 1026MHz?!

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.

Flash Kernel, leave Screen on until battery dead -> find out which ROM/Kernel wins?

Flash Kernel, leave Screen on until battery dead -> find out which ROM/Kernel wins?
Hey there, I thought I would charge my N4 with franco Kernel & Stock ROM too 100% and then leave the screen on until e.g. 5%.. then I will do the same with other Kernels to figure out which one gives me the best on-screen time.
Is this a reliable test to find out which Kernel gives best battery life for me?
Thanks

Re: Flash Kernel, leave Screen on until battery dead -> find out which ROM/Kernel win
zakazak said:
Hey there, I thought I would charge my N4 with franco Kernel & Stock ROM too 100% and then leave the screen on until e.g. 5%.. then I will do the same with other Kernels to figure out which one gives me the best on-screen time.
Is this a reliable test to find out which Kernel gives best battery life for me?
Thanks
Click to expand...
Click to collapse
This belongs in the Q & A section. Definitely not development
Sent from my Nexus 4 using xda premium

Moved to Q&A

Well one thing is on screen time could also be subjective.
I can have the screen on and do nothing but idle for hours vs. playing a game or browsing the web that will eat up more power.
If doing it idle then kernel comparison would be who is using a governor that uses less cores on idle or uses the most UV, so pretty much the results will depend on the behavior.
Different kernels feature different things such as, one could be more power saving but less ramp up or performance for gaming while another can be super smooth for gaming and multitasking transitions but consumes a little more power, so pretty much if you're going to be comparing kernels it would be the specific features they present and everyone has to be on the same level as not every version release will have the same setting as previous.
So your best bet for power saving would be one that gives good UV for your specific binning (unless you test your own settings) and maybe underclock if you're not a heavy multitasker/user/gamer etc...

Thanks for moving !
Well I could also make a test with 30minutes gaming, 30 minutes music, 10 minutes video recording, rest on idle with display on?
That would cover pretty much the "whole" package.
I am not gaming much (and I haven't seen a game yet which wouldn't run on N4 anyway). About Multitasking:
1x gmail (calender,contacts + k9mail)
1x gmail (k9mail)
1x facebook
1x friendcaster for contacts sync
1x WhatsApp
1x Skype
maybe 1x AndroIRC with 2 servers connected
But besides that I do the general stuff... listening music, sometimes browsing, checking mails/chatting/texting/writing, Alarmdroid to wake up, sometimes Navigation ;P

Re: Flash Kernel, leave Screen on until battery dead -> find out which ROM/Kernel win
zakazak said:
Thanks for moving !
Well I could also make a test with 30minutes gaming, 30 minutes music, 10 minutes video recording, rest on idle with display on?
That would cover pretty much the "whole" package.
I am not gaming much (and I haven't seen a game yet which wouldn't run on N4 anyway). About Multitasking:
1x gmail (calender,contacts + k9mail)
1x gmail (k9mail)
1x facebook
1x friendcaster for contacts sync
1x WhatsApp
1x Skype
maybe 1x AndroIRC with 2 servers connected
But besides that I do the general stuff... listening music, sometimes browsing, checking mails/chatting/texting/writing, Alarmdroid to wake up, sometimes Navigation ;P
Click to expand...
Click to collapse
As long as you keep the usage consistent, and do equal amounts of time on WiFI and data, that kind of test is fine. You don't need to make sure you test the whole world. Just keep your tests as consistent as possible. What will really burn you up, though, is how fast kernel builds are released. Good luck keeping up.

Well I am only concerned about franco vs faux kernel. Those are the two I can't decide between.
Also I would do the same test again after installing avast.. just to find out if it causes more batter drain or if the gaming performance goes down.

zakazak said:
Well I am only concerned about franco vs faux kernel. Those are the two I can't decide between.
Also I would do the same test again after installing avast.. just to find out if it causes more batter drain or if the gaming performance goes down.
Click to expand...
Click to collapse
if you care about my opinion in more real world usage under similar conditions, i prefer faux b/c faster and more features. franco is kind of performance limited and it slows down multitasking a lot. battery life is similar maybe a tiny bit better on franco but not worth the performance sacrifice

mbucks911 said:
if you care about my opinion in more real world usage under similar conditions, i prefer faux b/c faster and more features. franco is kind of performance limited and it slows down multitasking a lot. battery life is similar maybe a tiny bit better on franco but not worth the performance sacrifice
Click to expand...
Click to collapse
Well that is one users opinion ;P
I would like to make my own with some test.. also including benchmark test I guess.
Will do that this weekend and let u know the results. Generally it seems to be useless anyway.. since one update could change everything :/

Nexus 4 battery the first week

Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.

Beerad875 said:
Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.
Click to expand...
Click to collapse
Are you taking any measures to save battery life, like certain screen brightness, disabling of certain features or radios, undervolting or CPU/Governor changes, etc?
First thing I installed on mine ( haven't had mine a week yet ) was Battery Monitor Widger Pro, since I've used that on my past devices when I was testing out generic batteries (speaking of which the 8$ ebay 3800mAh on my Desire-Z is still kicking strong after a year).
Problem with estimates, is that they are basically just that, and the difference between browsing on mobile vs browsing on wifi or mix, and your reception quality can also have an impact on your battery. (in the end, your screen is the biggest impact).
Mine lately, say if I had it charged at 100% , it'll take about 2 hours on mobile to get to 91%, with the screen being on about 25%-35% of that time (auto-brightness), receive/send text, take out of pocket to check email or facebook notifications, and so forth. Which would normally show as screen 30%, Google services 13%, Wifi 9% (when I had it on between house and destination). Phone idle 8%, Android OS 7% etc.
The widget I mentioned earlier can basically monitor your draw from time to time and if the screen was off or on and such during those times (default interval on it if using a widget is around 10 minutes on the logging, shorter may actually impact the battery it's monitoring oddly enough)
PS: The other day when I actually drained it down to 0% it took about 5-6 hours

Beerad875 said:
Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.
Click to expand...
Click to collapse
I had about 3-4.5 hours of screen time other moderate to heavy usage on my first week as I was testing it's battery life. As that I just used my phone under light to moderate usage. My brightness level is always at it's lowest but when I'm outside I turn it up to about 50%. I rarely play games on my device. I read a lot on my phone. I use my phone to record lectures in class and do a bit of homework on it. 7 months later and I'm pretty much doing the same. I have a custom kernel installed and I'm really confidence about it. I carry a external battery pack with me all the time but I hardly use. After having a custom kernel for the past 7 months I can say battery life has been relativity the same screen time wise. I learned how to manage my apps so they won't prevent my phone from sleeping to save power. Your mileage will vary depending on what you're doing on your phone and how you manage your device. Cell service is crucial to the phone. If you're in area with little to no service your device will use up more power to stay connected. This is when "Airplane mode" comes in handy.

kbeezie said:
Are you taking any measures to save battery life, like certain screen brightness, disabling of certain features or radios, undervolting or CPU/Governor changes, etc?
First thing I installed on mine ( haven't had mine a week yet ) was Battery Monitor Widger Pro, since I've used that on my past devices when I was testing out generic batteries (speaking of which the 8$ ebay 3800mAh on my Desire-Z is still kicking strong after a year).
Problem with estimates, is that they are basically just that, and the difference between browsing on mobile vs browsing on wifi or mix, and your reception quality can also have an impact on your battery. (in the end, your screen is the biggest impact).
Mine lately, say if I had it charged at 100% , it'll take about 2 hours on mobile to get to 91%, with the screen being on about 25%-35% of that time (auto-brightness), receive/send text, take out of pocket to check email or facebook notifications, and so forth. Which would normally show as screen 30%, Google services 13%, Wifi 9% (when I had it on between house and destination). Phone idle 8%, Android OS 7% etc.
The widget I mentioned earlier can basically monitor your draw from time to time and if the screen was off or on and such during those times (default interval on it if using a widget is around 10 minutes on the logging, shorter may actually impact the battery it's monitoring oddly enough)
PS: The other day when I actually drained it down to 0% it took about 5-6 hours
Click to expand...
Click to collapse
Nah. All stock, not rooted yet, auto-brightness, No auto sync. I don't get very good service at my work and I was about 28% without service during the time I was there. I would get on facebook and message people on facebook and text, surf the internet etc because it was slow. I had maybe 2 hours screen time and 8% battery life when I left work. It was probably 9 hours off the charger. Here. I'll post a screen shot after this post (On my computer right now)

Sent from my Nexus 4 using xda premium

Beerad875 said:
Nah. All stock, not rooted yet, auto-brightness, No auto sync. I don't get very good service at my work and I was about 28% without service during the time I was there. I would get on facebook and message people on facebook and text, surf the internet etc because it was slow. I had maybe 2 hours screen time and 8% battery life when I left work. It was probably 9 hours off the charger. Here. I'll post a screen shot after this post (On my computer right now)
Click to expand...
Click to collapse
One of the benefits to custom roms (though 'stock' on a nexus is well AOSP so...) is the ability to tweak that stuff to finer details, top it off with a custom kernel and can optimize even further. Just a matter of how far you want to take it.
I have a history of immediately rooting anything I get my hands on, so I tend to have very little experience with stock. But the Nexus devices are probably the only ones I could survive having stock (but rooted) as opposed to say touchWhiz on samsung.

I can say that this phone charges FAAAAAAST.

kbeezie said:
One of the benefits to custom roms (though 'stock' on a nexus is well AOSP so...) is the ability to tweak that stuff to finer details, top it off with a custom kernel and can optimize even further. Just a matter of how far you want to take it.
I have a history of immediately rooting anything I get my hands on, so I tend to have very little experience with stock. But the Nexus devices are probably the only ones I could survive having stock (but rooted) as opposed to say touchWhiz on samsung.
Click to expand...
Click to collapse
Coming from the the backflip's motoblur to the Captivate's touchwiz then onto One X's sense to AOSP.. I'm going to stay android purist from now on. I'm in love with AOSP

Beerad875 said:
Coming from the the backflip's motoblur to the Captivate's touchwiz then onto One X's sense to AOSP.. I'm going to stay android purist from now on. I'm in love with AOSP
Click to expand...
Click to collapse
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).

kbeezie said:
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).
Click to expand...
Click to collapse
Why do you prefer them?
So with battery monitor widget pro do I just let it run and collect data?

kbeezie said:
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).
Click to expand...
Click to collapse
Guess tonight I'm going to work on getting it drained down to 0% just remembered it was my N7 that I did a full cycle on with monitoring, I haven't done so yet to the N4.
PS: I usually do a dual-graph (mV and mA), but in this screenshot you can see generally speaking with my current configuration, I tend to drain around 200-300 mA screen on, and around -20-50 with it off.
PS#2 : It only went up to the -400 or so mA on the top right because I had changed my screen brightness to about half instead of autobrightness.

Beerad875 said:
Why do you prefer them?
Click to expand...
Click to collapse
Additional options. Take for example the Bricked kernel for the N4 in my signature. This is it's feature list, it's not aimed for hardcore overclockers or such but gives you some options (The one for the Nexus 7 is a bit more configurable during the installation).
* Based upon Googles msm 3.4 source
* Various other fixes (look @ github)
* Compiled with gcc4.7.2 toolchain (linaro 09.12)
* -O3 optimized
* Snapdragon S4 & CortexA15 optimizations
* Sweep2wake
* 192Mhz min clock
* replaced qcoms hotplug binary with msm_mpdecision (IN-KERNEL, better battery life + performance)
* Extensive sysfs interface for mpdecision with all the tuneables you want (/sys/kernel/msm_mpdecision/)
* replaced the thermald binary with my IN-KERNEL solution. (/sys/kernel/msm_thermal/)
* export krait version to: /sys/kernel/debug/krait_variant
* modified ondemand governor
* Allow OC up to 1,83Ghz, faux123 (from a thermal point of view that is now SAFE)
* Fixed min cpufreq resets
* Undervolting (faux123)
* Default clocks: 384min & 1512max
Click to expand...
Click to collapse
Sweep2Wake is kind of nice too, you just slide accross the screen to turn it on without having to touch the power button (And yes your phone is still asleep doing this, it just works off interupts.)
other kernels can be a bit more involved, such as being aimed towards overclocking the CPU or GPU, or adding in extra features not normally found in stock, and so forth. I've had the best luck with Bricked and Francos'
Beerad875 said:
So with battery monitor widget pro do I just let it run and collect data?
Click to expand...
Click to collapse
Yep, if you have a widget on the home screen (I usually do 2x1 size) it'll collect every 10 mins by default. If you don't use a widget you'd have to check a box in preference to monitor without widget or it won't log times (note for example the missing 'blocks' from my history log).
---------- Post added at 11:29 PM ---------- Previous post was at 11:22 PM ----------
Speaking of battery, anyone ever gotten more than say 800mA charge on their N4? Cuz even on my old Desire-Z if I plugged it into a 2.1A charger it would actually charge up around 1300-1500mA, but with the Nexus 4 seems that even on a 2.1A port it rarely charges more than 500-600mA.
It'll probably become more accurate once I actually drain it down to 0% and have the widget record it's history from 0% to 100% since it bases a lot of it's mA estimates off that (ie: off the rate of decrease of the battery's mv since batteries typically have a certain voltage once they hit near 0% and when they're at 100%, comebine that with what it knows the battery's mA to be it can determine the charge/discharge based off that).

kbeezie said:
[/COLOR]Speaking of battery, anyone ever gotten more than say 800mA charge on their N4? Cuz even on my old Desire-Z if I plugged it into a 2.1A charger it would actually charge up around 1300-1500mA, but with the Nexus 4 seems that even on a 2.1A port it rarely charges more than 500-600mA.
It'll probably become more accurate once I actually drain it down to 0% and have the widget record it's history from 0% to 100% since it bases a lot of it's mA estimates off that (ie: off the rate of decrease of the battery's mv since batteries typically have a certain voltage once they hit near 0% and when they're at 100%, comebine that with what it knows the battery's mA to be it can determine the charge/discharge based off that).
Click to expand...
Click to collapse
I can get back to you when I figure this app out more and start using it.
What'd you say your screen on time usually was?

Beerad875 said:
I can get back to you when I figure this app out more and start using it.
What'd you say your screen on time usually was?
Click to expand...
Click to collapse
Just in the last 2 hours or so, probably 30-45 minutes. I was in the car so it wasn't coming on all that often. Since I actually have the widget on my home screen now, I'll just post an update again probably in the morning as I play with the phone some more, maybe play a game or two (I'll set a Market in the battery history before I start and after I end it).
Far as figuring it out, it's pretty easy since most of it is already set up by default once you open it. You can basically just pop a 2x1 widget on the home screen and just leave it.

My battery life has improved drastically by just sticking with one setup and letting the phone get used to it. That means keep the same rom and kernel so the phone settles in and gets used to it. After a few cycles your usage should increase.
I recommend straight CM 10.1 with Franco kernel.
Also use 2g instead of HSPA+ when you're not using data to save power.
If you're using touch control, don't, it drains more power for sure.
Undervolting helps too.
Sent from my Nexus 4 using xda app-developers app

nyyankees1237 said:
If you're using touch control, don't, it drains more power for sure.
Click to expand...
Click to collapse
Can you clarify on this, other than the power/volume there's not much else to actually control the phone with.

kbeezie said:
Can you clarify on this, other than the power/volume there's not much else to actually control the phone with.
Click to expand...
Click to collapse
The app 'touch control' , many nexus 4 owners use it to wake and lock the phone using touch gestures in place of the traditional power button. In my usage it definitely drains the battery quicker.
Sent from my GT-N5110 using xda app-developers app

nyyankees1237 said:
The app 'touch control' , many nexus 4 owners use it to wake and lock the phone using touch gestures in place of the traditional power button. In my usage it definitely drains the battery quicker.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Oh you mean like Sweep2Wake in the Bricked Kernel I'm using, except that doesn't use any battery cuz that's in the kernel using interrupts rather than an app that would keep the phone awake. (course that's all it does too, wake, nothing more sophisticated than that).
But yea I didn't know about that app.

kbeezie said:
Just in the last 2 hours or so, probably 30-45 minutes. I was in the car so it wasn't coming on all that often. Since I actually have the widget on my home screen now, I'll just post an update again probably in the morning as I play with the phone some more, maybe play a game or two (I'll set a Market in the battery history before I start and after I end it).
Far as figuring it out, it's pretty easy since most of it is already set up by default once you open it. You can basically just pop a 2x1 widget on the home screen and just leave it.
Click to expand...
Click to collapse
So yeah. You should drain it then report with some screenshots.

It's at 44% right now
Sent from my Nexus 4 using XDA Premium HD app

Tweaking governor for better battery while typing?

One thing that has always bothered me is how quickly (relatively) the battery drains on any android phone i've had in the past 6 years when typing. I can read articles, scroll webpages and whatnot for hours...but if I'm having a heavy day of instant messaging, my battery drains much faster. This makes sense due to way that this phone and most android phones ship with the ondemand governor. Just to test, and you can try this too, in better battery stats or some other app that can monitor CPU speeds, set a custom reference and then type for one minute in a note keeping app or an instant messaging app. Then go back and check. What you'll find is that the CPU frequency stays at max 80% of the time or more, because the screen is being touched the entire time. So to me, that is horribly inefficient.
I went ahead and bought an iPhone 6s to try to see if iOS handles typing better, and it does. I can get about 6-7 minutes of nonstop typing before the battery drops 1%, whereas on mine it can be anywhere from a minute and half to 3 minutes tops.
I want to see if I can clamp down on this so I found this post but it's very specific to the Nexus 5x: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/page51
What do you guys think? I'm not nearly well versed in this kind of stuff so I need some help. Let me know!

I agree, it's a very crude and inefficient way of doing it. Android is designed for maximum fluidity so they assume that every time you touch the screen the cpu will be put under load, thus the cpu ramps of the frequency - this is commonly known as touchboost. If you have a custom kernel like dorimanx you can modify it to lower the touchboost frequency and various settings so it could potentially lower battery usage during input. Although I don't know if it's worth it considering all of the various potential problems that go along with such a kernel..
iOS and android are so fundamentally different that I doubt you can (easily)modify it to perform like ios in a given workload. However, each manufacturer has their own flavor of android so they may be optimized differently. Either try several different models or just go with an iphone since you've tried it and seemed to like it - or you could always wait for android n which will hopefully be more clever and efficient..

you could try intellimn this stays at lower freq, when more power its needed it boots to higher frequencies. that along with allucard hotplug. should save battery this is with dorimanx kernel.
with ondemand its the same. or if you want more lower use smartassv2

I returned the iPhone. The fact that it doesn't repeat notifications for missed calls is abhorrent to me. I need to be able to glance at my phone and know that I've missed a call with the screen lighting up every few seconds or a LED light.
So I'm definitely sticking with the G2 for now.
If I install another kernel to give me more governor options, how difficult is it to put back the stock AT&T lollipop kernel? Can I back it up first in any way?

ksc6000 said:
I returned the iPhone. The fact that it doesn't repeat notifications for missed calls is abhorrent to me. I need to be able to glance at my phone and know that I've missed a call with the screen lighting up every few seconds or a LED light.
So I'm definitely sticking with the G2 for now.
If I install another kernel to give me more governor options, how difficult is it to put back the stock AT&T lollipop kernel? Can I back it up first in any way?
Click to expand...
Click to collapse
Yes you could either use twrp and back up boot. or use flashify from playstore to back up stock kernel.

ksc6000 said:
One thing that has always bothered me is how quickly (relatively) the battery drains on any android phone i've had in the past 6 years when typing. I can read articles, scroll webpages and whatnot for hours...but if I'm having a heavy day of instant messaging, my battery drains much faster. This makes sense due to way that this phone and most android phones ship with the ondemand governor. Just to test, and you can try this too, in better battery stats or some other app that can monitor CPU speeds, set a custom reference and then type for one minute in a note keeping app or an instant messaging app. Then go back and check. What you'll find is that the CPU frequency stays at max 80% of the time or more, because the screen is being touched the entire time. So to me, that is horribly inefficient.
I went ahead and bought an iPhone 6s to try to see if iOS handles typing better, and it does. I can get about 6-7 minutes of nonstop typing before the battery drops 1%, whereas on mine it can be anywhere from a minute and half to 3 minutes tops.
I want to see if I can clamp down on this so I found this post but it's very specific to the Nexus 5x: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/page51
What do you guys think? I'm not nearly well versed in this kind of stuff so I need some help. Let me know!
Click to expand...
Click to collapse
So this is not a scientific test at all, but I usually will use whatsapp for messaging nonstop during my 1 hour lunch at work. No browsing or anything else is usually included in that. I have a few conversations going so I'm typing and getting messages non stop. Previously that would decrease the battery by 22% or so. Now by switching my governor to interactive and making tweaks to it using EX Kernel Manager, with this it's down to 14%. I will admit there is some minor stutter when first turning on the screen with the settings I'm using so I'm sure I need to keep tweaking but my main concern is the battery life while typing.
Previously as I mentioned if I'm typing, the CPU speed would go up to max and stay there until I'm done typing for a few seconds. Now with these tweaks my CPU speed barely goes up above 960 MHz...most of the time it's between 640 or 883. I think that's the reason I'm getting 4 to 4.3 minutes of screen time now while typing instead of getting anywhere between 1 and 1/2 minute or 3 at best while typing.

ksc6000 said:
So this is not a scientific test at all, but I usually will use whatsapp for messaging nonstop during my 1 hour lunch at work. No browsing or anything else is usually included in that. I have a few conversations going so I'm typing and getting messages non stop. Previously that would decrease the battery by 22% or so. Now by switching my governor to interactive and making tweaks to it using EX Kernel Manager, with this it's down to 14%. I will admit there is some minor stutter when first turning on the screen with the settings I'm using so I'm sure I need to keep tweaking but my main concern is the battery life while typing.
Previously as I mentioned if I'm typing, the CPU speed would go up to max and stay there until I'm done typing for a few seconds. Now with these tweaks my CPU speed barely goes up above 960 MHz...most of the time it's between 640 or 883. I think that's the reason I'm getting 4 to 4.3 minutes of screen time now while typing instead of getting anywhere between 1 and 1/2 minute or 3 at best while typing.
Click to expand...
Click to collapse
if you use smartassv2 its lower.