yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Tree of Knowledge:
I've gotten the best battery life on 13.1 by far. I never changed voltages or anything, all I did was enable hotplug along with mess around with some of the AOKP rom settings and was easily able to achieve 2+ hours of screen on time daily with fairly heavy usage and LTE on most of the day. If I was trying to conserve battery however, I could get upwards of 3 hours screen time and around 20 hours total and that's still with moderate usage.
[Samsung Galaxy Nexus] Wicked4u2c:
Decided to go back to 13.1 too, it was by far the most stable release with awesome battery life. I think some of the issues are how the CPU doesn't scale anymore. If you have 700/1350 its either at 700 or 1350 nothing in between. Personally I think that's what screwed everything up after 13.1. But what do I know, I'm no kernel developer it just seems that was the biggest change.
[Samsung Galaxy Nexus] franciscofranco:
#15.2's been the best so far in my opinion, everyone at the GSM side seem to be having great results with it. Be aware that I don't give any type of support for older releases, you're on your own ;)
[Samsung Galaxy Nexus] Gahh Its Lee:
I absolutely love 15.2 its running great for me. A little warm but that's it.
[Samsung Galaxy Nexus] Tsoflyyup:
Yea this is what im afraid to jump back to 13.1 franco, wha was in 13.1 that made it so great? Lol
[Samsung Galaxy Nexus] mike216:
Franco look at these numbers!I love 15.2 its actually the best kernel I've ever ran up to data and I'm no fan boy but a very pleased fellow member who will give credit when credits due

What rom are you guys getting SOD on? Please indicate that because I'm on gummy and battery life along with performance are crazy

This is moderate use. Phone was off the charger all night and had heavy use when I woke up and then again was on idle for 8 hours at work with occasional use at work followed with moderate use at home. Still have another day if I push it but tomorrow is Friday and ill bull**** all day at work tomorrow so back on the charger! Lol.....

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] Tree of Knowledge:
That's my major concern. I'm back to 13.1 at the moment but I do like being up to date with what is being supported. I have noticed that the conservative governer runs smoother on my phone on 13.1 than francoturtle on 15.2, transitions are a lot smoother. I would try to mess with voltages but I really know nothing about them. Any suggestions Franco?
[Samsung Galaxy Nexus] mike216:
Thanks once again franco I just donated. Its not much but I don't have much and always find a way to donate at least 1 a month

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] Wicked4u2c:
Wow Mike, thanks for sharing your screenshot. I have to give 15.2 a shot now.
[Samsung Galaxy Nexus] mike216:
I didn't touch the default settings until a few hours ago but I ended up putting my minimum back on 700. I thought who knows better me or franco? Ahh probably franco ill put it back on 700. :-)

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] Wicked4u2c:
This may sound crazy but on 13.1 I can run 350/700 and its fast as hell. I'm actually going to record a video this weekend to show how ridiculous fast it is. The best part is that it never exceeds over 34c in temp even at peak performance. The phone is cold, and battery life is phenomenal.

FWIW here is a screenshot of my best on 13.1 the first part is 8 hours of idle the rest is just moderate use throughout the day
[Samsung Galaxy Nexus] dincfool:
I've had a few random roommates on 15 so just for kicks im going back to 13.1. Im also on aokp m3. Those that comment should write up what rom your running and what your kernel settings are.
[Samsung Galaxy Nexus] sway40:
Random roommates??? I know you meant reboots it was funny though.

~ Sent from my Galaxy Nexus running Cm9~
[Samsung Galaxy Nexus] mark manning:
Well its pretty simple, 350 use less energy than 700 so it will last longer. The only reason Franco likes 700 is because the phone wakes up faster therefore his kernel feels smoother.

Franco correct me if I am wrong!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] azndan2:
I don't remember running 13.1 for that long, but I can definitely say that idle on 15.2 is not going well for me, I was getting better battery life on 14.x at least.
[Samsung Galaxy Nexus] mark manning:
Aokp is sucking battery from users at the moment. Due to the popularity of Franco's kernel I think he might be taking the brunt of an issue that isn't his.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
Maybe so mark? I also think Franco likes the minimum at 700 because the phone can finish task and enter a deep sleep state quicker and prevent less wake ups from a deep sleep status. I read this on his thread when using his kernel on my nexus S. This was highly debated and proven to be the case when franco, and ezekeel did a series of tests.

Maybe I misunderstood what I read but roughly a year ago I remember reading this much disgusted topic on the (at the time) 400 minimum? Please set the record straight franco. I know the question will be asked a million more times

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] mark manning:
Thank you mike your adding an exclamation point, in a way, to my comment.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
Mark I'm not questioning you! I'm saying there could be more to it and to be honest I'm trying to remember the other reason on the minimum so I don't want to sound like an idiot if I'm totally wrong

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] mark manning:
I know, I could be wrong too but I would bet against it!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
You'll bet against you being wrong. Your definitely not wrong about the phone having a better chance of responding quicker on a 700 minimum wake up but is that it? Is that the reason for the 700 min?

I hope franco doesn't miss this when reading through these when he wakes up in the morning

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] mild7intl:
Franco. I never ever pay for apps. I paid for yours and its the only one that I plan on paying for. I will say to all the haters out there that any issues you may be experiencing are non kernel related. This is, out of glados faux IMO and stock cna/@0kp best performance and battery life by far. The app is worth more than 2 bucks it makes life sure lot easier if you're a crack flasher and tbh since 15.2 I am no longer a crack flasher

Aokpm3 and Franco 15.2 is the best combo (top 3) for sure as I can't speak for trinity and jdkernel but if you're lucky enough to read this.. listen to me and I promise you will be amazed.

Not trying to kiss ass. I work in the business. And these are my objective conclusions after two months of constant testing.

Thank you Franco. You really redeemed the capabilities of this phone and continue your work so others can realize this as well.

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk
[Samsung Galaxy Nexus] Janzomaster:
Hi there,

I've got one question: my wifi keeps activating on it's own, some time after I switched it off. Is this a problem that derives from the kernel (it did say something about wifi drivers in the changelog) or might it come from some other source?
[Samsung Galaxy Nexus] mark manning:
glados faux??? What is that supposed to mean?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mirwolf:
Those are names of the other kernels.
[Samsung Galaxy Nexus] BankZZ:
Anyone else having problems with 5.x and nova launcher? After every reboot I have to restart nova. The screen isn't readable. The text is garbled. Went back to 3.1.
[Samsung Galaxy Nexus] Milyenair:
I've been running AOKP-M3 and everything was smooth. I finally flashed franco 15.2 and almost immediately my phone won't charge. It shows it's charging but the Percentage remains or even drops and the battery on time is frozen. I restored to before I flashed the kernel and now the problem still remains. What has happened?
[Samsung Galaxy Nexus] Kidd_Funkadelic:
Damn Franco, you keep one upping yourself. My overnight drain last night was 0% (~6hours). - FrancoGazelle/hotplug/350/1.35...

That's the best I've ever seen on any kernel.

Thanks!
[Samsung Galaxy Nexus] hajabooja:
This kernel is running great and I'm really liking francogazelle. I'm just wondering, is anyone else getting really high RAM usage? I'm hovering around 500mb used with nothing besides Google stuff running.
[Samsung Galaxy Nexus] TEK112:
That is ROM related.
[Samsung Galaxy Nexus] Pupalei:
I got zero battery loss overnight, like every night, because night is the logical time to charge :-D
[Samsung Galaxy Nexus] Smabbage:
Franco 15.2: Went to bed at 10:00 P.M. with 80% battery. Checked it at 8:30 A.M. and had 66% battery. Hotplug enabled. Impressive to say the least. :)
[Samsung Galaxy Nexus] hajabooja:
Generally I would I agree with you. However, I've tried different kernels and it seems that the RAM usage goes down to normal (around 300mb).
[Samsung Galaxy Nexus] TEK112:
Are those kernels changing the heap size that much? Usually the swings I see are from ROMs limiting/expanding the number of concurrent processes. I could very well be wrong about the kernel. Please let me know what you find.
[Samsung Galaxy Nexus] Wicked4u2c:
I'm no expert, but I think its funny that 700 is recommended because it wakes up "faster". It doesn't matter what my min is set too even 350 I click on turn on and my phone wakes up instantly. What, 700 will wake it up 0005ms faster? Were not talking about minutes or even seconds. Is it really worth having the CPU draw more battery for a savings of a fraction of a second?

Same thing goes for apps, usually when I click on an app it boots immediately, were not dealing with long load times. Even certain games I've set my min and Max to 350/350 and ran a few apps, then I set my min max to 700/700 and you couldn't tell the difference. I think on certain games like Angry Birds, cut the rope which take a few seconds more there was at most a half a second difference.

Same thing goes with how he changed the CPU to work after 13.1. It doesn't scale anymore, its either at min or max and nothing in between. Again, I'm no expert but just using my common sense. I look at like a car (I know this is not a car) if I was driving and I could only use 25% of the throttle or 100% and nothing in between I think a lot of gas will be wasted. I believe the same would apply to this, setting your phone to 700min then having it scale to 1200 without ever seeing anything in between seems pretty aggressive.

BTW I'm not complaining, I'm just providing feedback. I'm not saying his newest kernels are not good. I had great results on 14.1 and I think was 15. But something is always missing, its not as good or as balanced as 13.1 and I think most will agree.
[Samsung Galaxy Nexus] franciscofranco:
I'll explain again. 700mhz as minimum is to minimize the wakeups-from-idle per second and to boost race-to-idle effect. I've seen voltage tests in this forum comparing my kernel with 700mhz and other kernels with 350mhz, say for example listening to music, and my 700mhz shows less power used. I already said this 18048394059435823 times =(
[Samsung Galaxy Nexus] danman7:
I'm running AOKP M3, along with the 15.2 kernel (using francoTurtle). I have only one complaint, but it's a substantial one. I am finding that if I have it charging (via USB port or AC charger) and I'm using the phone, the temperature really spikes. It also does not actually charge. The battery level continues to drop.

For example, I was uploading some files to Dropbox over 4G, had it plugged into my charger and the temp (per BadAss Battery Monitor) went from 85F to 110F in less than 10 minutes. Battery level during the same period DROPPED from 84% to 78%. Dropbox then force closed.

Other than this, I'm really happy with performance and don't want to change. However, I'm concerned with the long-term effects and don't want to kill the hardware.
[Samsung Galaxy Nexus] franciscofranco:
Were you undervolting? I'm a lot of time with the device plugged into USB doing stuff with wifi always enabled and never experienced any kind of overheat.

Ok so let's do a bit of testing:

http://androtransfer.com/franciscofranco/Galaxy Nexus/test_kernel/

That test kernel has the dynamic hotplug coded into francoTurtle governor, which means that everytime that the device is at the minimum frequency cpu1 is down. When it's > min frequency cpu1 is up again. Since with turtle governor the device spends around 90% of the time at minimum frequency its going to be interesting to see if shuting down cpu1 will be beneficial or not.

The only intruction is that you have to disable hotplug mod to prevent conflicts.
[Samsung Galaxy Nexus] aznxk3vi17:
So even with simple, low-demand tasks such as browsing, music, Gmail, etc., it's still less of a power drain to use 700? Why does every other kernel default to 350 as MinCPU then? Is it just a case of you knowing something they don't, differences in the way the kernels are made, or just your personal experiences/preferences?
[Samsung Galaxy Nexus] franciscofranco:
I'm not saying others are worse than mine, I just read the numbers from the experience. The power usage between 350mhz and 700mhz is minimal, so minimal that its not seen, in my opinion, in real world tasks. It's just my personal experience/preferences. I've been doing this in all the phones I worked on, and I've had awesome results.
[Samsung Galaxy Nexus] aznxk3vi17:
Fair enough - I too haven't noticed much change in drain between 350/700. I'll do test runs on both and just make decisions based on my own experiences (thanks to Android/devs for that possibility at all!). I did see that thread about the actual power drain too, so that's something to chew on.
[Samsung Galaxy Nexus] mike216:
I hope my buddy mark Manning could see this and me quoting at the same time! Thanks for clearing this up franco I was close when explaining this a couple pages back!

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] Wicked4u2c:
Thanks for explaining again, I will do a test by turning everything off (airplane mode) and let it idle for 8-10 hours on 350 then try on 700. I get what your saying, but even if the phone is idling isnt it technically drawing more energy since the clock speed is at 700 (higher voltage) vs 350 (lower voltage). I can't imagine the phone needing to process heavy intensive tasks while idling. Again, I'm no expert just using logic.
[Samsung Galaxy Nexus] mike216:
This is what I asked to clear up franco that's how this 700 minimum popped back up but ill be sure to try and put the fire out before it starts by quoting you, thanks

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] TEK112:
Clock speed is frequency and voltage is voltage. A higher clock speed does not necessarily indicate a higher voltage.

For this example of 350 vs 700, look at it like heating a home. If you turned the heat off everytime you didn't need and turned it on when you got cold you would use more energy in the long run even though during times when you have it off you are using no power. Same thing here.
[Samsung Galaxy Nexus] franciscofranco:
No, idle is idle, it's power collapsed, doesn't use a **** of power.
[Samsung Galaxy Nexus] dwallersv:
Indeed.

Batteries are more complex than most people understand. For example, something most people are not familiar with is internal or intrinsic resistance -- a fact of batteries of any type that results in load dependent output voltage regardless of the stored energy state.

Put differently, a battery that has 50% of it's storage capacity will present a lower voltage under an instantaneous load of 1A than a load of 500mA (0.5A). Yet, if output voltage is being used as a proxy for capacity, the battery will be interpreted as having less remaining stored capacity under the 1A load than the 500mA load, even though the remaining stored energy is the same.

When the heavier load is reduced -- not uncommon when going from, say, playing an FPS game to surfing the net in a browser, the output voltage of the battery will be seen to increase -- even though there is no increase in stored energy.

Again, if voltage is being used as a proxy for remaining energy storage, this will give a false indication that the battery has magically found some phantom energy somewhere.

Now, all that said, voltage is generally the means by which remaining energy is determined in devices like cell phones. It is generally a pretty decent metric, and is more than sufficient for this purpose, which doesn't require high precision.

A far more precise calculation measures both instantaneous voltage and load current at the same time, then essentially take these values and finds remaining capacity based on a set of discharge curves for the battery chemistry in use (programatically it's a table lookup with extrapolation between values). Where knowing capacity with precision is critical, like in a nuclear power plant control circuit, the extra cost is justified.

Even voltage/current is still less than optimal from an accuracy standpoint -- discharge curves are also temperature dependent, and change as a battery ages and is used. To get really precise, voltage, current, temperature need to to all be factored in, and the discharge curves used to look up remaining capacity need to be adjusted periodically to match the actual capability of the battery as it ages.

In applications where such precision is necessary sophisticated battery control circuits periodically drive a fixed charge/discharge cycle with the battery "offline", based on a count of charge/discharge cycles (a measurement of aging), and recalibrate the discharge curves.

Doing all of this can make a "battery meter" very, very precise. And while it is easily possible to engineer this into a smartphone, the added accuracy isn't anywhere near worth the expense for the all but those 4 OCD users that just have to have accuracy perfection.

Sadly for that gang, they're not enough to add another $50 to the cost of the phone.

---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------

Um actually it's 18048394059435827 times.

You missed a few.

:D
[Samsung Galaxy Nexus] kjwalker:
Flashed and charging. We will see!
[Samsung Galaxy Nexus] dwallersv:
I may have misunderstood what you were saying, so apologies in advance if I am correcting something that I read wrong.

Both voltage and clock frequency impact power (rate of energy consumption). In CMOS technology, this is especially so -- power is consumed chiefly during state transition -- that's when electrons flow through CMOS digital circuits.

The more transitions per second -- i.e. clock rate -- the more power is present, more energy consumed.

This is vastly oversimplified, but gets the basic concept across. So, running an identical load on the CPU for 1 minute @ 700MHz will, with certainty, run at higher power and consume more energy than @ 350Mhz. For example, running a prime number generator (classic load in geekdom for measuring these sorts of things).

Of course, @700 more will get done. Not precisely 2x as much, but in the gross argument, a reasonable estimate.

The issue here is not the instantaneous rate at which energy is being (power) consumed, but rather the total energy consumed to perform the task (power * time). And this is where it gets tricky, because power and time do not scale linearly, and inversely, under identical circumstances.

So, for example, if 700 uses roughly 1.5x the power, but finishes the task in half the time than @350, then @700 will consume 1.5*0.5 = 75% of the total energy performing the same task @350, saving battery.

Why would this be? I.e., why would things scale in this non-linear fashion? If we were talking a simple resistor network, they wouldn't -- the scaling would be precisely linear. But we're talking active circuits and complex systems with all sorts of interlocks, timing situations, latencies for things like RAM and IO components, and on and on and on. As such, as Franco has been pounding into us all here, @700 Mhz the phone might wake up and complete a task faster than at 350, such that the power consumed over the short time completing the task simply comes out more favorably in terms of total energy used than at 350.

There isn't a simple explanation than this. The only way to nail it is to do some real-world testing, and see what happens. Sounds like enough of that's been done, by Franco and others, to convince Franco.

Based on the quality of his kernels and the technical expertise he's demonstrated, he's no piker. From my perspective, if he's convinced, based on his cred that's good enough for me. I'm certainly technically capable enough as an engineer myself to put together a testing protocol and gather my own data, but why bother? I trust Franco.

Hope this mini-novella helps someone here understand this better :)
[Samsung Galaxy Nexus] crupp:
yea, I'm sticking with 700. Phone just over all feels snappier...Battery, whatver :cool:
[Samsung Galaxy Nexus] wallendiaz:
I can use this kernel on my gsm galaxy nexus or only is for cdma???
[Samsung Galaxy Nexus] Elganja:
either... if it makes you feel better, here is the GSM thread: http://xdaforums.com/showthread.php?t=1367341&page=59
[Samsung Galaxy Nexus] djh816:
Still getting problems with hotplug in 11. I can click power 20 times back to back and most likely it locks up. Coservative governor.
[Samsung Galaxy Nexus] fiveoh:
AudioOut_1

Yes but it is directly related to my battery life.
[Samsung Galaxy Nexus] GirLuvsDroid:
The #11 kernel is fantastic! Thank you for your work.
[Samsung Galaxy Nexus] littleguevara:
+1

10 chars
[Samsung Galaxy Nexus] zman6900:
Hey man, I'm running your latest kernel with Gummy 0.4.7 and when I'm playing GTA, it's really choppy in the graphics. I noticed it in Shadow Gun also. Can you let me know if there is a fix for this or if it's a ROM or Kernel issue? Thanks in advance.
[Samsung Galaxy Nexus] DirtySimpleClean:
First off, thank you for developing a great kernel franco. took my phone off the charger last night after wiping battery stats and i got 21 hours of battery with 8% remainin (waiting til the phone dies to run another full cycle :cool:)

i noticed when i ran this kernel on gummy rom, my quadrant scores were 2600ish and didnt feel as snappy. when i run this kernel with axiom rom, i get around 3100 and **** is smooth as butter!
[Samsung Galaxy Nexus] reverepats:
Hey guys. In the past few years I've had a few android. Well maybe more than a fee, but here's something I've never seen. I'm running AOKP 15 w/ Franco's #15. A few hours ago I was messing around with a few things and did a full restore. I booted up and had 59% Batt life remaining. In the past 4 hours my battery hasn't drained at all, but rose 2%. Personally I've seen this happen before, but not over a 4hr period. I think it pretty funny, and I am i n no way complaning. Just curious if its normal LOL. Any input would be great. Thanks guys.

Ohh and frequencies are 1.3mHz-Max...350Mhz-min
[Samsung Galaxy Nexus] Tsoflyyup:
i want to try #11 im currently on gummynex with franco 10. Is anyone having issues with rom manager? it just did an update and now i cannot flash recovery img. I click on flash recovery and it proceeds then at the end it just freezes..then the app becomes unresponsive.......any ideas?

---------- Post added at 10:19 PM ---------- Previous post was at 10:08 PM ----------

nevermind i just reinstalled a later version of rom manager
[Samsung Galaxy Nexus] TEK112:
Why not just make it permanent so you don't have to keep reflashing it?
[Samsung Galaxy Nexus] Xezuka:
Really interesting. I was going to say I've experienced seeing 88%, turning the screen off, looking again 10 minutes later and its at 89%, but nothing like this.

EDIT: Second thought -- don't you mean AOKP #14 + franco #11?
[Samsung Galaxy Nexus] sinik420:
Quit using rom manager