Either i'm not looking hard enough, or i'm just not finding any decent guides on in-depth tweaking in kernels, what does what (with examples, because a lot of the time, only certain types of people can grasp what an explanation of a setting or value does), whether certain groups of values are synergetic (changing one value can have an effect on another value, good or bad; not using 1 setting when another setting is active), stuff like that. I took screenshots of everything in EXKM, except for the governor parameters, i didn't change what the kernel has for defaults with the Wheatley governor.
GWARslave119 said:
Either i'm not looking hard enough, or i'm just not finding any decent guides on in-depth tweaking in kernels, what does what (with examples, because a lot of the time, only certain types of people can grasp what an explanation of a setting or value does), whether certain groups of values are synergetic (changing one value can have an effect on another value, good or bad; not using 1 setting when another setting is active), stuff like that. I took screenshots of everything in EXKM, except for the governor parameters, i didn't change what the kernel has for defaults with the Wheatley governor.
Click to expand...
Click to collapse
Well, you definitely have the right program, I used to think Kernel Adiutor was the best kernel tweaker of all times, so I bought it, with no additional benefit
Not long ago or yesterday, ( Lol ) I finally decided to spend a few dollars and buy Ex Kernel Manager, its very satisfying to use with its beautiful design and extensive features. One awesome feature of EXKM is the ability to save your profile to widgets so you can quickly change to a saved profile for balance, battery or speed.
Because my original X727 suffered from chip death early last month, I am hesitant to use overclocking and probably never will again. Honestly, the phone is still extremely fast when underclocking and the battery life is amazing.
Below are a couple of screenshots. Maybe later, when I have time I will make an extensive post with all of the small details or better yet someone else does it.
tsongming said:
Well, you definitely have the right program, I used to think Kernel Adiutor was the best kernel tweaker of all times, so I bought it, with no additional benefit
Not long ago or yesterday, ( Lol ) I finally decided to spend a few dollars and buy Ex Kernel Manager, its very satisfying to use with its beautiful design and extensive features. One awesome feature of EXKM is the ability to save your profile to widgets so you can quickly change to a saved profile for balance, battery or speed.
Because my original X727 suffered from chip death early last month, I am hesitant to use overclocking and probably never will again. Honestly, the phone is still extremely fast when underclocking and the battery life is amazing.
Below are a couple of screenshots. Maybe later, when I have time I will make an extensive post with all of the small details or better yet someone else does it.
Click to expand...
Click to collapse
lol my battery life is half of yours ;p And how exactly where u overclocking it, by changing the voltages? And yeah it's a fast phone for the money, I haven't found a game yet that it doesn't run smoothly on..
A couple things I've been noticing lately, one is fast charge hasn't been working lately even when selected. Not sure if it's the cable or the rom or what. And also I've noticed the charge times change when I flip over the usb-c connector when plugging it in..again i dunno if thats cause of the cable or if usb-c is meant to be that way
GWARslave119 said:
lol my battery life is half of yours ;p And how exactly where u overclocking it, by changing the voltages? And yeah it's a fast phone for the money, I haven't found a game yet that it doesn't run smoothly on..
A couple things I've been noticing lately, one is fast charge hasn't been working lately even when selected. Not sure if it's the cable or the rom or what. And also I've noticed the charge times change when I flip over the usb-c connector when plugging it in..again i dunno if thats cause of the cable or if usb-c is meant to be that way
Click to expand...
Click to collapse
The charge speed is not static, it fluctuates otherwise it will shorten the life of the battery. The speed can be improved upon by switching the kernel. For example, Black Screen 5.4 uses the higher rate charging, it also allows you to change voltage frequencies, which I don't recommend. I fried my old X727 early last month, by simply restoring Google settings..
If you are using the stock Leeco cable, get rid of it and but an Anker cable instead. Some of the stock cables were really bad quality and quite a few people burned their ports due to faulty cables.
Concerning battery life, Right now AICP 14 has the best battery life.
It also has the new perf profiles extracted from EUI. It is my understanding (?) that this was extracted and made compatible by Max 2 developer : shivatejapeddi.
He made a comment on telegram stating that he may build a flashable zip for Zl1 that could be flashed on any rom to improve the battery life.
Lets hope, that would be awesome.
tsongming said:
The charge speed is not static, it fluctuates otherwise it will shorten the life of the battery. The speed can be improved upon by switching the kernel. For example, Black Screen 5.4 uses the higher rate charging, it also allows you to change voltage frequencies, which I don't recommend. I fried my old X727 early last month, by simply restoring Google settings..
If you are using the stock Leeco cable, get rid of it and but an Anker cable instead. Some of the stock cables were really bad quality and quite a few people burned their ports due to faulty cables.
Concerning battery life, Right now AICP 14 has the best battery life.
It also has the new perf profiles extracted from EUI. It is my understanding (?) that this was extracted and made compatible by Max 2 developer : shivatejapeddi.
He made a comment on telegram stating that he may build a flashable zip for Zl1 that could be flashed on any rom to improve the battery life.
Lets hope, that would be awesome.
Click to expand...
Click to collapse
Sorry, been too distracted to reply ha. Yeah I don't mess with the voltage frequencies, just try different governors and whatnot...I don't mess with the governor settings much since somet imes it's hard for me to notice any difference , unless it's a huge one. Basically it's jsut me trying to put aside time to focus and I haven't made time, it's all jumbled with other things i do ;p
Actually I lie, I did notice what seemed to me as odd on a few things... i'll toss screenshots. What I dont get is the first boost duration under the CPU Boost at 0... also, the boost frequency, is the mhz it boosts to, or an addon amount.. and just the boost in general, input boost vs touchboost...? next there's the online core count.., max cores online for litl and big make sense, 2 each. Min core online 1, max cores online...2? with an up and down threshold of 0...how does 0 work in this case? NExt is arch_power and wq_power_saving, i've tried looking them up and couldn't find much, so not sure what they doe xactly and what it would hurt/hinder...
Zram, does it hurt to have it on and at full, 2096mb? Just as an extra ceiling, in case I do use all my 6gb, or does having it on but not using it constantly affect anything.. the TCP algorithm i've scoured and couldn't find anything about which ones are good for what types of networks, maybe only a couple of them, so i usually don't play with that since to me it'd be hard to test because of the fluxuation.
Ok that was more than I thought I'd throw out, sorry ;p There's lots more probably, but I don't need to overload mine or yours' head right now ;p
oh.. i was wondering if i posted this or not lol... wasnt sure if the draft had gotten lost or what.. anyways, i was just now going to take screenshots when i rememebred, you can just use the ones from my origianl post ha
GWARslave119 said:
oh.. i was wondering if i posted this or not lol... wasnt sure if the draft had gotten lost or what.. anyways, i was just now going to take screenshots when i rememebred, you can just use the ones from my origianl post ha
Click to expand...
Click to collapse
Just now seeing this and no time to respond at the moment. I will answer later.
Related
Iv always considered battery life a very important factor in my purchasing of a phone and was one of the big reasons i moved from my Desire HD to the Nexus S (amongst many others). However having been on the android scene for a while im used to tinkering with kernels and roms etc and due to the new battery graph in gingerbread im now able to make direct comparisons rom by rom and kernel by kernel to see how they all differ. This is all shown + explained below.
First id like to explain my method;
I install the rom and kernel with the same apps I always use and charge the phone fully until i am about to go to sleep. I then unplug the phone and leave it in the exactly the same place on my desk with exactly the same settings (sync intervals etc) and i kill all apps before i leave it just to make sure the test is fair.
In the morning i then take a screen shot of the battery life over the period of usually 8 hours and will upload this for you to see. I then look at the over-night battery drain as a comparison on how good battery life is on specific roms and kernels.
Justification - Many of you may be thinking who cares about standby battery life? I care about the battery when im using it!?
Well although that's valid there are many reasons i have taken this approach;
1. It is completely fair i.e. no individual differences such as 'im a heavy user' but we all have different definitions of a 'heavy user'. This is eliminated by the fact the phone is not used and thus the same every time (no individual differences)
2. If a phone has severe battery drain during sleep general knowledge should dictate that battery drain should increase when the screen is on, cpu is working and your syncing your facebook wall, thus a direct correlation with sleep battery drain and usage drain should be apparent.
Therefore i have decided over the next few days/weeks etc i will upload on a regular basis a screenshot of the battery drain over night, along with the battery use details and screen on time etc etc. In addition to the rom and kernel info and i hope that over time this proves to be a very useful thread.
I have been doing this over the last few days on a less strict system and there have been some VERY interesting results which i will upload over the next few days.
(Just a final note iv never really done anything like this on xda before so if its a stupid idea then please tell me now so i dont waste my time doing it, however if people are really interested please let me know and il make sure i do my best!!)
Thanks for reading my extremely long post!
Bratfink
SCREENSHOT 1: This was using modacos custom rom r10 and the kernel that comes with it, i had quite a short sleep (about 6 hours) but the curve pretty much shows what the point im trying to make is. The battery life is great!!
SCREENSHOT 2: This is CM7 Nightly build 27# with Netarchy's latest 1.2.1 kernel and although i didnt use the screen once of charge for a few minutes as you can see once the screen was off battery life barely decreased and was over a long period of time.
If anyone wants me to test specific combos please let me know.
I'm actually looking forward to reading your results.
Sent from my Nexus S using XDA App
Yep, this would actually be pretty useful. Good luck and good work!
i'm a sucker for these types of tests, always love doing them and seeing the results. post soon!
I like others will be keeping an interested eye on your findings.
Uploading pictures of modaco r10 with it's own original kernel today. Its an interesting result!
Sent from my Nexus S using XDA App
Uploaded to OP
I'm interested too.
Can u try modaco r10 with Netarchy 1.2.1 kernel.
bratfink said:
Iv always considered battery life a very important factor in my purchasing of a phone and was one of the big reasons i moved from my Desire HD to the Nexus S (amongst many others). However having been on the android scene for a while im used to tinkering with kernels and roms etc and due to the new battery graph in gingerbread im now able to make direct comparisons rom by rom and kernel by kernel to see how they all differ. This is all shown + explained below.
First id like to explain my method;
I install the rom and kernel with the same apps I always use and charge the phone fully until i am about to go to sleep. I then unplug the phone and leave it in the exactly the same place on my desk with exactly the same settings (sync intervals etc) and i kill all apps before i leave it just to make sure the test is fair.
In the morning i then take a screen shot of the battery life over the period of usually 8 hours and will upload this for you to see. I then look at the over-night battery drain as a comparison on how good battery life is on specific roms and kernels.
Justification - Many of you may be thinking who cares about standby battery life? I care about the battery when im using it!?
Well although that's valid there are many reasons i have taken this approach;
1. It is completely fair i.e. no individual differences such as 'im a heavy user' but we all have different definitions of a 'heavy user'. This is eliminated by the fact the phone is not used and thus the same every time (no individual differences)
2. If a phone has severe battery drain during sleep general knowledge should dictate that battery drain should increase when the screen is on, cpu is working and your syncing your facebook wall, thus a direct correlation with sleep battery drain and usage drain should be apparent.
Therefore i have decided over the next few days/weeks etc i will upload on a regular basis a screenshot of the battery drain over night, along with the battery use details and screen on time etc etc. In addition to the rom and kernel info and i hope that over time this proves to be a very useful thread.
I have been doing this over the last few days on a less strict system and there have been some VERY interesting results which i will upload over the next few days.
(Just a final note iv never really done anything like this on xda before so if its a stupid idea then please tell me now so i dont waste my time doing it, however if people are really interested please let me know and il make sure i do my best!!)
Thanks for reading my extremely long post!
Bratfink
SCREENSHOT 1: This was using modacos custom rom r10 and the kernel that comes with it, i had quite a short sleep (about 6 hours) but the curve pretty much shows what the point im trying to make is. The battery life is great!!
If anyone wants me to test specific combos please let me know.
Click to expand...
Click to collapse
Sent from my Dell Streak using XDA App
I'd be interested in seeing CM7, just whatever nightly build you manage to catch.
I don't think that result will give you precise result.
I found that statistic is wrong sometimes.
It is better to measure using "play video loop".
So, find a movie, set to the same brightness and play in loop?
gogol said:
I don't think that result will give you precise result.
I found that statistic is wrong sometimes.
It is better to measure using "play video loop".
So, find a movie, set to the same brightness and play in loop?
Click to expand...
Click to collapse
Unfortunately that will not give you how well the rom does while it is idle.
I'm really looking forward to your results. My only issue with this phone is the battery life is terrible. I ordered an extended battery off Ebay 3 weeks ago and have yet to receive it. Never ordering anything from Hong Kong again!
Fuse8499 said:
I'm really looking forward to your results. My only issue with this phone is the battery life is terrible. I ordered an extended battery off Ebay 3 weeks ago and have yet to receive it. Never ordering anything from Hong Kong again!
Click to expand...
Click to collapse
What were you using before that you consider this phone to have bad battery life? By far this phone has the best battery life of any Android device I've owned. If you want bad battery life, get an Evo. That is horrific battery life.
bratfink said:
Uploading pictures of modaco r10 with it's own original kernel today. Its an interesting result!
Sent from my Nexus S using XDA App
Uploaded to OP
Click to expand...
Click to collapse
I am looking forward to the rest of these, however just a quick question. What was your battery use like in that situation with the stock ROM? Just for reference, because I'm thinking I might switch to modaco soon. Thanks!
More soon
Iv got a few more screenies but it seems i may have to end this thread prematurely. Its the SNS or 2.3 but idle battery usage for me is pretty much identical no matter what the kernel or rom (il upload a CM7 + Netarchy 1.2.1 shot top op). This was unexpected on my behalf because with my DHD kernels and roms had a big impact on idle battery consumption. I have noticed however that without a full wipe when changing some kernels such as with M r10 idle battery life can increase drastically. I will continue for the next few days and if i dont see any big changes i may move method to a video loop or something of the sort.
Interesting find
I found out something today that may interest may of you. I was messing around with the sleep profiles on SetCpu with netarchys kernel and i found that its better to leave the range from 100-800 than 100-400 or less. This i believe is because when the phone is asleep and carries out a process it will be forced to clock to the maximum of 400mhz and then stay at that speed for 10 seconds, instead of say going up to 800mhz for 1-2 seconds to complete the same process. So a tip to you would be set your profile to 100-800mhz conservative and see what you get!
bratfink said:
I found out something today that may interest may of you. I was messing around with the sleep profiles on SetCpu with netarchys kernel and i found that its better to leave the range from 100-800 than 100-400 or less. This i believe is because when the phone is asleep and carries out a process it will be forced to clock to the maximum of 400mhz and then stay at that speed for 10 seconds, instead of say going up to 800mhz for 1-2 seconds to complete the same process. So a tip to you would be set your profile to 100-800mhz conservative and see what you get!
Click to expand...
Click to collapse
This kinda enforces the point that SetCPU is useless for the NS unless you really want to overclock...
Any battery saving tactics used buy lowering screen off profiles are counteracted by the system process;( So i think in the context of battery life you are probably better to not use SetCPU
JD
bratfink said:
Iv got a few more screenies but it seems i may have to end this thread prematurely. Its the SNS or 2.3 but idle battery usage for me is pretty much identical no matter what the kernel or rom (il upload a CM7 + Netarchy 1.2.1 shot top op). This was unexpected on my behalf because with my DHD kernels and roms had a big impact on idle battery consumption. I have noticed however that without a full wipe when changing some kernels such as with M r10 idle battery life can increase drastically. I will continue for the next few days and if i dont see any big changes i may move method to a video loop or something of the sort.
Click to expand...
Click to collapse
I would definitely move to a video loop or some other 'heavy use' task because when you think about it, not too much can really be changed when almost no power is being used in the first place.
You could also just mention your general feeling for the battery life of each rom, because quite often that is what I go by as my usage varies depending on a range of things (school day or weekend etc) .
Sent from my Nexus S using XDA App
Could you please test modaco r10 with Netarchy's latest 1.2.1 kernel ?
I would love to see the difference between modaco's default kernel vs netarchy's kernel.
On CM nightly 13, I just went 11 hours and I'm at 90%. That's 1/2% an hour. Not bad. That is with stock kernel.
Sent from my Nexus S using Tapatalk
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.
Wanted to give the Moto X a little love for AOSP folks, particularly to include Sprint users -- they seem to get so little (and my kids love their Moto X / Sprint).
[KERNEL][AOSP 4.4.4|CAF][UNIFIED moto_msm8960dt][TDHK 07/16/2014]
Enjoy
Finally!
Omg! I remember some days ago thinking why not somebody make a AOSP Kernel... Well here it is, thanks so much i will give it a try.
Awaiting for DT2W
Franxx said:
Omg! I remember some days ago thinking why not somebody make a AOSP Kernel... Well here it is, thanks so much i will give it a try.
Awaiting for DT2W
Click to expand...
Click to collapse
Why would you need dt2w with active display as an option....and it doesn't hurt battery life. Dt2w takes a big toll on battery life as it won't run on the low voltage core.
KJ said:
Why would you need dt2w with active display as an option....and it doesn't hurt battery life. Dt2w takes a big toll on battery life as it won't run on the low voltage core.
Click to expand...
Click to collapse
DTw2 is cheap. Dunno where you got that. That's the point of specialized governors.
As for active display -- hopefully one day we'll get that working in AOSP/CAF kernels, but MOTO is not exactly forthcoming in their tricks.
tdhite said:
DTw2 is cheap. Dunno where you got that. That's the point of specialized governors.
As for active display -- hopefully one day we'll get that working in AOSP/CAF kernels, but MOTO is not exactly forthcoming in their tricks.
Click to expand...
Click to collapse
Dt2w is "cheap" on the G2....why? Low voltage core.
Go read how it is on the N5. 2 to 3 percent battery drain on standby. And if the huge development community of the N5 can't crack the low voltage core to use for apps....I very much doubt the Moto kernels will figure it out. Its probably not possible.
Unless it runs on a low voltage core, it is terrible on the battery. You don't have to take my word for it..... You will see if/when its an option for the X.
KJ said:
Dt2w is "cheap" on the G2....why? Low voltage core.
Go read how it is on the N5. 2 to 3 percent battery drain on standby. And if the huge development community of the N5 can't crack the low voltage core to use for apps....I very much doubt the Moto kernels will figure it out. Its probably not possible.
Unless it runs on a low voltage core, it is terrible on the battery. You don't have to take my word for it..... You will see if/when its an option for the X.
Click to expand...
Click to collapse
Already read the N5 games and sources. The drain here in moto x land won't be so much about cores (imho), it'll be about keeping the touch panel alive to detect touches. Cores are easy. TPs are always another story (they take power).
Hang in brother, -- I've heard this on other devices, we've always solved it. The key is the 'it' that runs on 'a core'. Low voltage core is interesting only to the extent it would solve a particular problem. We won't have that problem because we will remove the cycles of interest by low frequency testing for touch. Still working on it, but it'll work. There's no magic in kernels, just crap-work and testing.
As for sticking the TP up for touches, surely will have work to do.
LOL -- building test #5 now, and it's still borked . Just crap-work, I'll get it working and we'll get it. Never seen something unsolvable with kernels today. Just time to figure it up.
tdhite said:
Already read the N5 games and sources. The drain here in moto x land won't be so much about cores (imho), it'll be about keeping the touch panel alive to detect touches. Cores are easy. TPs are always another story (they take power).
Hang in brother, -- I've heard this on other devices, we've always solved it. The key is the 'it' that runs on 'a core'. Low voltage core is interesting only to the extent it would solve a particular problem. We won't have that problem because we will remove the cycles of interest by low frequency testing for touch. Still working on it, but it'll work. There's no magic in kernels, just crap-work and testing.
As for sticking the TP up for touches, surely will have work to do.
LOL -- building test #5 now, and it's still borked . Just crap-work, I'll get it working and we'll get it. Never seen something unsolvable with kernels today. Just time to figure it up.
Click to expand...
Click to collapse
Well, I hope you can make it not pummel the battery. But I still don't see how you'll do what oh so many N5 devs haven't been able to.
For the N5 especially, since there's no active display (for same reason....battery destroyer), dt2w is a nice feature, but only usable by those who are willing to charge twice as much as usual. So its very unpopular at this point.
Good luck tho! Maybe you can let the N5 devs know your secret if you succeed. ?
KJ said:
Why would you need dt2w with active display as an option....and it doesn't hurt battery life. Dt2w takes a big toll on battery life as it won't run on the low voltage core.
Click to expand...
Click to collapse
I don't wanna sound rude or anything but it's probably because AOSP rom doesn't have Active Display. Have you considered that? Otherwise i'll stick with stock rom.
But to be honest i always come back to stock. I'm a noobie with all of roms, kernels and scripts. This is my third android phone and obviously this is the most exciting.
Franxx said:
I don't wanna sound rude or anything but it's probably because AOSP rom doesn't have Active Display. Have you considered that? Otherwise i'll stick with stock rom.
But to be honest i always come back to stock. I'm a noobie with all of roms, kernels and scripts. This is my third android phone and obviously this is the most exciting.
Click to expand...
Click to collapse
I know why.....its how I am questioning.... Without the same battery drain the N5 gets with dt2w. The N5 has a low voltage core as well, with a pedometer... Lol....and its pretty much been found to be inaccessible for any other apps. And I imagine the same will be true of the X.
---------- Post added at 10:59 PM ---------- Previous post was at 10:52 PM ----------
Let me explain a bit....
The X has active display and touch less control...
The N5 has an extremely useful (sarcasm) pedometer.....
The LG G2 has double tap to wake and?????....
All of these features run on a sort of low voltage core, that's why battery drain is minimal with those features on their devices. And no one yet has accessed those cores to put them to other uses. Even in the massive N5 development community. Yes, the N5 has dt2w as a feature on some custom kernels, and they've put timeouts on it now, but still its a battery hog....and less useful, since after the timeout period....you need to press power to wake dt2w again.
I was just asking the OP how he intends to solve this, or is he not worrying about the battery drain and trying to bring the feature to the X anyway, regardless of the bad battery drain.
KJ said:
or is he not worrying about the battery drain and trying to bring the feature to the X anyway
Click to expand...
Click to collapse
LOL -- seriously? Of course I worry about battery -- that's the whole point. But I want performance too. We'll get 'em both. I probably won't comment much more -- have plenty to do. Hang in, it's easy to doubt as progress goes.
Hang in -- it's not an overnight game. Test #6 about done, it'll be #20 before it gets good and releasable -- at least that's my bet at the moment.
Updated 08/31/2014
Important updated kernel. See this post.
Have fun!
Hey guys! This is my first topic on XDA, so I apologize in advance if I do something wrong.
I love my 6P and since it's a Nexus, there's always some tinkering so I can make it even better and suitable for my needs. I pretty much like stock-ish ROMs with that touch of Pixel phones and I find that original Google kernel serves me well in terms of battery life and overall performance (I'm probably one of the rare dudes to state something like this). But original kernel is very limited in terms of other options custom kernels offer, like gestures, screen color control, audio boost, etc. Regarding custom kernels, I never had any good experience with battery life, even when setting the governors on powersave/noop/cfq or any other I tried.
So, I guess what I'm asking is - can you recommend me a kernel that's exactly like the Google's out-of-the-box, but with those added options I mentioned above? Or is there some way to restore settings on custom kernels to default Google's settings?
Cheers!
I keep falling back on ElementalX, it offers enough customization, and still has decent battery depending on your settings. There's a million and 1 ways to configure it. I tried other very popular, more feature rich (they have everything, plus the kitchen sink, and sometimes cupboards too), but the battery drain is just too high for my liking. Not even using the phone, and every time I wake it with one of those kernels, it's dropped another 8-10%, without being used.
I haven't tried them all though. Many of the slimmer kernels don't offer a way to disable touchboost, so I rule those out as soon as I see that.
HikingMoose said:
I keep falling back on ElementalX, it offers enough customization, and still has decent battery depending on your settings. There's a million and 1 ways to configure it. I tried other very popular, more feature rich (they have everything, plus the kitchen sink, and sometimes cupboards too), but the battery drain is just too high for my liking. Not even using the phone, and every time I wake it with one of those kernels, it's dropped another 8-10%, without being used.
I haven't tried them all though. Many of the slimmer kernels don't offer a way to disable touchboost, so I rule those out as soon as I see that.
Click to expand...
Click to collapse
Oh, ElementalX was my first choice too, but suddenly that too started to drain my battery quickly after a while. At first I thought it happened because of some app, but when I flashed default kernel everything got back to normal. That's why I wonder is there a way to copy those default settings and apply them to some custom kernel.
You think disabling touchboost is a big deal? Cause of battery life or something else?
inspire4gfreak said:
Oh, ElementalX was my first choice too, but suddenly that too started to drain my battery quickly after a while. At first I thought it happened because of some app, but when I flashed default kernel everything got back to normal. That's why I wonder is there a way to copy those default settings and apply them to some custom kernel.
You think disabling touchboost is a big deal? Cause of battery life or something else?
Click to expand...
Click to collapse
You may check this thread regarding kernel governor profile customisation:
https://forum.xda-developers.com/ne...dvanced-interactive-governor-t3290605/page471
A lot of options to choose from. EX Kernel, Flash Kernel, (I guess other kernels) support this mod using a kernel manager app.
I'm currently using EX Kernel + EX Kernel Manager + Ghost Pepper profile.
Fast enough for me. Plus it helped me saving some juice.
Depending on your usage, it takes trials and errors until you find the good kernel/config that suits your needs.
Happy reading...
5.1 said:
You may check this thread regarding kernel governor profile customisation:
https://forum.xda-developers.com/ne...dvanced-interactive-governor-t3290605/page471
A lot of options to choose from. EX Kernel, Flash Kernel, (I guess other kernels) support this mod using a kernel manager app.
I'm currently using EX Kernel + EX Kernel Manager + Ghost Pepper profile.
Fast enough for me. Plus it helped me saving some juice.
Depending on your usage, it takes trials and errors until you find the good kernel/config that suits your needs.
Happy reading...
Click to expand...
Click to collapse
Wow, I stumbled upon some other loooooong post about governors, but this one is amazing! I didn't know touchboost has that much influence on battery. I will try this out, thanks mate!
I get better battery life on ElementalEx over stock kernel without a doubt. I am running interactive with Ghost Pepper profile and touch boost disabled. If battery life is your main consideration you could try Franco's Kernel but you are sacrificing some phone performance to get the better battery life. I found the drop off in performance very noticeable but his kernel has its fans. I think ElementalEx has a better balance between performance and battery life.
inspire4gfreak said:
Oh, ElementalX was my first choice too, but suddenly that too started to drain my battery quickly after a while. At first I thought it happened because of some app, but when I flashed default kernel everything got back to normal. That's why I wonder is there a way to copy those default settings and apply them to some custom kernel.
You think disabling touchboost is a big deal? Cause of battery life or something else?
Click to expand...
Click to collapse
Touchboost wastes battery because it boosts you to 1248000 every single time you touch the screen, and it holds it for like a second or two. It does make your phone faster, and responsive though.
Sent from my Nexus 6P using Tapatalk
I got my nexus 6p and it was pretty fast with no mods or custom roms, just had a weak battery. I ordered the battery on ebay (aftermarket THQL 3600mah) Now the battery is fine but ive heared theres no thermal contact or something like that. After installing a new kernel, the phone was sluggish... Installed root and Kernel Auditor and saw my for BIG cores were offline... This was NOT a problem earlier! Turning off Thermal VDD fixes this and turns the BIG ores on (Phew)! But am i missing something? I heard somewhere the Big cores were shut off to save battery or something. Any help and info would be awesome!
Kernels probably turning big cores off until there is demand. I've seen it happen many of times nothing to worry about. I have also battery from eBay works great just no temp sensor. Kernels are fine and all but sometimes can sacrifice performance. If you need your fix I found just changing the governor's on the stock kernel with elemantal app is all you need. Google search the article Flar posted about kernels. It really puts things into perspective. I'm no expert on the subject just from my personal experience.