yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Stuphologist:
That's why I asked bcvictory to please, please rerun the test with the A25 governor parameters. I'm very curious to see what the effect of the other changes are with the governor settings held constant.

The results so far are:

Originally Posted by bcvictory

“a26 got 5 hours 4 minutes on my battery test @1.3GHz which is close to the stock results of almost 5 hours. a25 got 6 hours 38 minutes on the same test @1.3GHz."

This post suggests that the governor parameters are pretty significant. We have an excellent chance to find out how much. Interesting, don't you think?

The OP of that post, droidphile, suggests:

-=-=-=-=-=-

For battery:-

To bias ondemand towards battery saving, set high up-thresholds and higher sampling-rate. This way, governor polls less often and scales up less often.

Up_threshold: 95

Sampling_rate: 120000

Sampling_down_factor: 1

Down_differential: 5

Freq_step: 10

ii) For performance:-

To bias ondemand towards performance, set low up-thresholds and lower sampling-rate. This way, governor polls more often and scales up quite often.

Up_threshold: 70

Sampling_rate: 50000

Sampling_down_factor: 2

Down_differential: 15

Freq_step: 50

-=-=-=-=-=-

I'm running A26 with:

Up_threshold: 90

Sampling_rate: 50000

Sampling_down_factor: 2

Down_differential: 10

Freq_step: (not an option?)

I've also set my min freq to 204 and the max to 1400. So far, after a typical day, I've still got 50% battery.

Dave

Edit: goodness that was a long past. I promise not to do that again this year!

Happy New Year to all here!!!
[Nexus 7 Android Development] bcvictory:
I used interactive for a26, ondemand for a25. I thought people wanted me to try the 'new' governor. It's kind of apples to oranges. These test is really just trying to make the kernels lose battery as quickly as possible. After a bit of maths and having my nexus 7 for a while I have realize that I normally get double my numbers of the test for normal use. So I got 5 hours for a26 on the test but I normally would get 10 hours of normal use.

---------- Post added at 10:22 AM ---------- Previous post was at 10:22 AM ----------

Run a25 with interactive?
[Nexus 7 Android Development] Stuphologist:
I meant run the test against A26 with the ondemand governor and A25 parameters. But drat that you did the A26 test with the interactive governor. Metallice doesn't recommend using interactive, he prefers (and I think optimizes for) ondemand. I understand why you did it that way, though. Makes sense.

Dave
[Nexus 7 Android Development] Metallice:
First off... just no. You don't purposefully change the conditions when running a comparison.

And they wanted a25 ondemand and a26 ondemand with a26 having the same up_threshold, sampling down factor etc.
[Nexus 7 Android Development] bcvictory:
Alright I'll go again. Well can you give me the numbers? Just so everything is clear.
[Nexus 7 Android Development] Metallice:
Not sure. I dont have a nexus 7 running a25. I believe 95 up threshold and sampling down factor of 1. Thanks. That would be really helpful.
[Nexus 7 Android Development] superbobup:
I think:

down_differential 3

Up_threshold 95

Sampling down factor 1

I/o is busy on

Ignore nice load off

Sampling rate 50k (not so sure about this one)

But in a26, down differential is fixed at 10. Tried changing it using Root Explorer and Trickster. Can anyone else change it? I feel like the changes metallice made to the hot plugging business (taking 4 seconds before hot plugging) will help the bounce between LP core and the other cores...so using a25 parameters on a26 would be nice.

On a26, I seem to be using 475mhz much more than I think I should, and I'm assuming it comes from down differential being at 10 so it takes longer to scale down to lower frequencies. No clue if this is true, though.

Sorry for my long post that is probably useless since I don't understand the down differential stuff very well.
[Nexus 7 Android Development] ezas:
Posting those ondemand settings was awesome. It was really helpful for me to have some ballpark numbers for battery & performance.

This kernel just keeps getting better and better.

<><><><><><><><><><><><><><><><><

Swyped from my N7

Current: PA 2.99 b9 & M-Kernel+ a26
[Nexus 7 Android Development] Metallice:
475 use increase is because it is the g core min and a26 is very hesitant to go to lp core compared to a25
[Nexus 7 Android Development] superbobup:
Thank you thank you thank you. I had no clue that was the min. Personally for my use, it seems much smoother without using the LP so much so it's quite nice. Thank you for all your work.

By the way, is there anywhere we can see the change log for a26? All I know is you kanged Franco's interactive stuff and did some other stuff with hot plugging. I tried looking at your github, but didn't see anything. Not that I really know how to read it anyway, but at least I can try.
[Nexus 7 Android Development] bcvictory:
Alright I'll do the tests as soon as I can. I'll redo the a25 one as well. I need my N7 for use most of today but I'll see what I can do!
[Nexus 7 Android Development] Metallice:
I haven't pushed the changes yet. Mostly because they are not final. I'm probably going to ease up a bit.

I increased the hotplugging down delays and decreased the hotplugging up delays. A lot.

I also decreased the core load balance target so more cores are used with less load.
[Nexus 7 Android Development] sert00:
on gnex kernels too,but there are some users that experience less prob than others and i'm one of them.i know of the problems you cited,read everyday of that,but a week ago i bought a new gnex and in that with 4.2.1 i don't have big problems..or a<t least no sod or random reboot,but you do right deleting it and reverting.not tried yet,flashed but haven't time to try it on grouper
[Nexus 7 Android Development] superbobup:
Thank you. I assumed it was something like that for the up/down delays as it made sense. No clue about the load balance target, I know nothing about that stuff haha

Hope you're on your way towards your new n7
[Nexus 7 Android Development] Stuphologist:
No, it's stuck at 10.

Dave

---------- Post added at 09:45 PM ---------- Previous post was at 09:34 PM ----------

Thank you! Just to be sure, and everyone please check me on this, the comparison is between:

A25 with its ondemand defaults

A26 with its ondemand defaults

A26 with the A25 ondemand settings

All with the same settings other than the ondemand settings.

That last one is my suggestion, the other two are the straight comparison tests. And really, you did the first one. I really do thank you for taking the time to do them.

Dave

---------- Post added at 10:19 PM ---------- Previous post was at 09:45 PM ----------

You're welcome. I copied that out of a much longer post here.

Dave
[Nexus 7 Android Development] benbailey84:
I noticed that core 0 is the main one that is used to the max the most, so that would be useful. Especially if you are trying to make sure all of your cores are activating.
[Nexus 7 Android Development] ace-user:
after the second cycle on a26, battery seems quite good..will experiment more and report to u guys soon..

Sent from both my sexy galaxy nexus and nexus 7 X)
[Nexus 7 Android Development] adstraylight:
I'm finding A26 great for battery, it uses next to nothing when sleeping, and not a lot when reading for extended periods. It's nice to have the raw horsepower available when needed to make load times and other operations seem much faster than before.

I think a soak test, while good for removing the subjectivity from the equation, bears no relation to anyone's real world usage, so is of little use as any kind of guide to user experience. This not to say it has no value at all, but must be taken in context, and not as an absolute guide as to which is 'better'.

Perhaps a comparison based on users' opinions via a few well chosen poll questions? As this is not about a purely mechanistic process because the users' subjective view is pretty integral to the success of any given modification. So some kind of statistical analysis of opinion could show trends of relative benefit.

^^^Sorry, that all sounds rather pompous, but I hope you take my point.

Anyway, on a specific note, what voltage are people using for 1.6ghz? I get SODs after long periods asleep with this maximum set. Sheer vanity of course, as it runs beautifully at 1.5.....:o
[Nexus 7 Android Development] R3dbeaver:
So in other words: just use whatever you feel like running smooth on your nexus.

Dude, you should totally help me on my English essays in college lol

Ps: my 1.6 runs on default voltage.
[Nexus 7 Android Development] adstraylight:
:D:o:D

LOL - yeah, sorry, I was just trying to get what I thought down in as few words as possible (and you did a much better job!). Don't know why when I'm trying not to be vague it comes out like a lecture....

With the 1.6 thing, I'm guessing my N7 simply can't handle it when waking from deep sleep, but it'd be interesting to know if anyone else has had a similar experience, and if they've solved it, how..I can run with 1.6, but it will SOD after being on standby for several hours.
[Nexus 7 Android Development] jamesst20:
Use my software 'JROMFlasher' to wipe properly your device and push back PA you will see your device much smoother whatever the kernel u use ;)
[Nexus 7 Android Development] Sveke:
And what does this jromflasher do that wipe cache, dalvik, system, factory reset doesn't do?

Sent from my Galaxy Nexus
[Nexus 7 Android Development] benbailey84:
Its made up of unicorns and puppies and ponies that talks your device into being smooth...
[Nexus 7 Android Development] sert00:
ahah good one.i doubt in magical performance by some tools...like the wipe scripts that does nothin more that what a users now can do with TWRP..
[Nexus 7 Android Development] Sveke:
OK, as long as it injects a healthy dose of glitter too, then I'll use it.

Reminds me of "aroma" installer.....haha....what a piece of sh*t that is. Cant believe some devs actually use it.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Stuphologist:
Better is subjective, true. Even the absolute values aren't a reliable guide, but the ratios between them are.

SOD: have you raised the minimum freq a step or two?

Dave
[Nexus 7 Android Development] adstraylight:
Interesting point, I agree that empirical testing has some merit in this context, in a very general sense, but to apply it to any depth when dealing with such relatively fine parameters to an individual user's experience becomes nigh on impossible imo.

The weird thing with my SOD is that it seems to only happen with the max set to1.6. I've now tried raising the voltage by 25 to see whether that makes a difference. If it does it again I'll try to get a last kmsg.
[Nexus 7 Android Development] Azurael:
A26 at 1.5GHz + CPU voltage at 1075mV, GPU at 520MHz undervolted by 100mV is giving me the best battery life and smoothest performance yet. I've switched back to interactive after a week or so of on demand though as I found battery life gains were far less noticeable than the lag it induced...
[Nexus 7 Android Development] Metallice:
Hmm. Interesting. I already have an a26/a25 hybrid built for a27, but i think I'll hold on to it until more users chime in on a26 battery life.
[Nexus 7 Android Development] zachf714:
For me I still get about 1.5 days with 4hrs of screen on time :) that's after only 1 cycle

Sent from my Nexus 7 using Xparent ICS Tapatalk 2
[Nexus 7 Android Development] thisguy23:
Were you able to change the low freq for G core from 550 to 551? Honestly I don't notice a change in battery life from a25. I undervolt everything so that could help too.
[Nexus 7 Android Development] Metallice:
The g min is 475 and will always be 475.

The 550 you see in the LP voltage table is a meaningless dummy frequency. Trickster auto merges frequencies in the voltage table. Otherwise you would see 4 entries for 666 in the LP table among other duplicates. That why 550 in the LP is showing up as the 550 MPU voltage. But it doesn't matter since the LP 550 is a dummy frequency anyway.

Yes I changed the LP 550 to 555 in a27. But as I said it really doesn't matter since it is a meaningless entry.

Voltage table frequencies do not correspond to the running frequencies. The running frequencies are seen when you change your CPU Max/min. Tegra just uses the closest value in the voltage table.
[Nexus 7 Android Development] Metallice:
Oh and hey I made some money selling some stuff for my parents on ebay. Took a percentage cut. Thanks to that and you wonderful people with your wonderful donations I'm now about $40 short of the 32GB. (If any of you actually care :) ) So almost there! Tempted to just get the 16GB now... but I know ill regret not spending that extra $50.
[Nexus 7 Android Development] zachf714:
Yeah 32gb is a better deal :)

Sent from my Nexus 7 using Xparent ICS Tapatalk 2
[Nexus 7 Android Development] Metallice:
But I can get a 16 GB nowwwwwwa!

Sent from my Future Nexus 7
[Nexus 7 Android Development] zachf714:
But 16gb isn't enoughhhhhhhhh ... Lol :)

Sent from my Nexus 7 using Xparent ICS Tapatalk 2
[Nexus 7 Android Development] superbobup:
20 mins of eBook reading, 20 mins of granny smith, rest on tapatalk and web. Not getting the flat line that I should be getting when idle, but battery life has been nice so I can assume it will only get better once I figure out what's draining it when idle.

Performance isn't up to what I want it to be, but I haven't messed with it enough yet. Sampling down factor of 2y sampling rate 10k, slight UV across the board.

BTW, Metallice, in Trickster Mod the voltage closest to the frequency is the value it uses, right? I.e. 475mhz on the G core uses the 550 MPU voltage slot while 860mhz G core uses the 910 MPU voltage slot
[Nexus 7 Android Development] Stuphologist:
True, of course. I work for a statistical research organization, I know you're right. The sample size is, well, one. The population size is very large. Statistically it's null. But as an engineering bench test it has merit.

This is fun, but I think we'll really bore the rest if we indulge in a statistical analysis. :)

Dave
[Nexus 7 Android Development] Tone_Capone:
Are you talking about a24 or a27?
[Nexus 7 Android Development] Metallice:
Umm. All of them. a1-27
[Nexus 7 Android Development] icytrey:
Running a26 with rasbean at 1.5 and 520 GPU with ondemand. No issues with battery life, but I've always been performance oriented and don't really care about battery life. Smooth as always. Thank you
[Nexus 7 Android Development] Stuphologist:
Metallice: A27? What are you planning? Going to split the difference between A25 and A26? Something else entirely? Should I stay up tonight?

Dave
[Nexus 7 Android Development] Metallice:
If you look back i posted that i had already built a27 but was holding off for now until i get more battery reports. Yes it splits the difference.
[Nexus 7 Android Development] knitler:
Could you split it more towards a25? ;)
[Nexus 7 Android Development] 93foxgt:
Ditto.
[Nexus 7 Android Development] aalupatti:
a26 :cowboy:
[Nexus 7 Android Development] ace-user:
idle on a26 aint that good...i left the tablet when i get to bed at 50% with wifi and sync on...woke up 9 hours later with 46%...i dont think that's normal..right?o.0

Sent from both my sexy galaxy nexus and nexus 7 X)
[Nexus 7 Android Development] Stuphologist:
Does anybody know what fraking process calls bugmailer.sh, and whether there's a setting to kill it altogether? The script tests to see if USB debugging is on, but the test apparently doesn't work because it runs even though I don't have USB debugging turned on. I added an exit 0 line, but I'd rather it wasn't called at all.

Thanks,

Dave
[Nexus 7 Android Development] Metallice:
I just delete bugmailer.sh or rename the extension. Why would I ever want to email Google about my custom ROM bugs?
[Nexus 7 Android Development] Stuphologist:
Is that bad? I'm doing this calculation in my head, but that's what... 220 hours to run down? From a full charge, that is, with WiFi and sync on. Plus, man, I have 2 kids and haven't slept 9 hours straight in maybe 4 years (sigh).

Dave

---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------

Well, this is subjective of course, but I've been running A26 with the A25 ondemand settings, heavier than normal day, and I've still got 54%. Ran great all day, too, no hitches or lag.

Dave
[Nexus 7 Android Development] Metallice:
Hmmmm. I dunno.
[Nexus 7 Android Development] NicoGa:
a26 is also very smooth here. After flashing the kernel a tweaked ondemand parameter (everything is still very smooth ... Notably more than with a25).

However, I disagree with all the post saying that a26 is good for the battery. Ok it is not that bad but I feel that loosing more than 1 hour of use is way too much!

Envoyé depuis mon Nexus 7
[Nexus 7 Android Development] xfrancis14:
just a suggestion.. but since some people like a25 and some a26 why dont you make like an a27 more for battery life but still decent performance and another for just performace
[Nexus 7 Android Development] 93foxgt:
Isnt that what a25 and a26 do already? Metallice can you make some brownies too while your at it? Lol I'm just messing btw xfrancis14. Maybe i shouldnt drink and post :)
[Nexus 7 Android Development] xfrancis14:
a26 was built more for performace and a25 has better battery life and some people want the perfomace from a26 and dont care about battery life and the people from a25 want a27 to be a bit more foucussed on battery then performace but still with decent performance
[Nexus 7 Android Development] _DrG_:
+1
[Nexus 7 Android Development] beobu:
Sorry if I ask a stupid question! Can I flash this Kernel for my LG F160L with CM10 rom? I really love USB Audio function and currently, our CM10 built for my phone not work. Both of USB audio and USB OTG.

If not, do you have any link or suggest for me?

Thank you very much!
[Nexus 7 Android Development] zPacKRat:
no
[Nexus 7 Android Development] ezas:
Split this, split that. Everything you need to know to 'split' it yourself is right here:

Short version: http://xdaforums.com/showpost.php?p=36121082&postcount=2190

Long version: http://xdaforums.com/showpost.php?p=19846297&postcount=2

Thanks goes to Stuphology for the original posts of this information.
[Nexus 7 Android Development] banny7000:
In trickstermod do I under volt with the mpu table?
[Nexus 7 Android Development] ezas:
a25 ondemand default settings:

down_differential 3

ignore_nice_load off

io_is_busy on

powersave_bias 0

sampling_down_factor 1

sampling_rate 50000

up_threshold 95

a26 default ondemand settings

down_differential 10

ignore_nice_load off

io_is_busy on

powersave_bias 0

sampling_down_factor 3

sampling_rate 50000

up_threshold 80

In case this helps anybody
[Nexus 7 Android Development] ace-user:
here's my battery life stats(comparing a25 and a26 usimg PA beta 9)

this is a25:

compared to a26:

as u can see, battery life is much better on a25...i can almost get a day more out of it..but performance wise, a26 is definitely faster and smoother...

hope this will help u guys decide between a25 and a26..looking forward for a27...

Sent from both my sexy galaxy nexus and nexus 7 X)
[Nexus 7 Android Development] Kearkan:
Without doing any exact tests, a26 does feel to be draining a hell of a lot more battery, i tweaked the governor settings to be more like a25 but its still noticeable.

Having said that everything also feels much more slick.

I think what im trying to say is yes, it uses more battery but you can see where it goes. So its not such a bad trade off.
[Nexus 7 Android Development] berkos:
i don't understand all this smoothness thing, in which elements of your device you guys seek smoothness? i mean, for apps and games you have a choice to overclock cpu/gpu, if im browsing the web, editing documents, i pop up trickster, set max freq to 1000mhz and i have same smoothness but excellent battery, for messing around in UI even on 1000mhz max on raspbeanjelly ROM i have maybe split second frameskip when sliding over second page in app drawer but that's it, it even feels smother than my friends S3 without powersaving setting on. i have tried a26 and it's marginally smoother but at a greater cost of the battery. for games and browsing i really don't see any difference between a25/a26. (i dont use benchmarks)

on a25 i undervolted a bit, i set max frequency to 1000 or 1300 depending what im doing on the device and im getting 2 and a half days of use with 4hours of screen time and being still at 55% battery, with stock governor settings, i could never get that result with any other kernel, stock or custom. If Mettallice somehow can in next revision keep the current performance of a25 and further extend battery life i will consider it magic :D . M-kernel a25 is perfect for the time being, rock solid, no SOD, force closes, or bugs, i was using it on PA beta 9, CM 10.1 nightlies and finally settling on raspbeanjelly rom.

if some of you are expecting smoothness of iOS devices i really dont see the point of achieving this using only raw horse power, it's just not practical IMHO. it think it more due the fact how physics in kinetic scrolling work on iOS compared to android than anything.
[Nexus 7 Android Development] sk3201:
Used to flash kernels on my gnex for smoothness and battery with success, but on my n4/n7 I have a diff feeling .... Tried already a couple of kernels and it wasn't as smooth as the stock one. I absolutely hate any! UI lag and in regards of this I am happy with stock. ROM is rasbean jelly btw and no lag at all. Of course, goal should be the ios smoothness, just my opinion.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 7 Android Development] d.kozzer:
I see where you're coming from, but I don't think trying to get to iOS levels of smoothness is impractical - my nexus is pretty much there with CM10.1 & a26 on performance/deadline. I suppose the things I really look at, in addition to launcher/scrolling smoothness, is how smooth panning, zooming and tilting is in Google Maps and Earth. I definitely noticed that both apps are significantly smoother with a26 at the settings I listed. I don't care much about battery life in general, because it's a wifi only tablet, and that means that when I'm using it I almost always have power available to plug in and/or recharge whenever I want. But it still gets me through a day of heavy use with juice to spare, so I'm more than happy.
[Nexus 7 Android Development] Keitaro:
I know I'm a few days late to the discussion but I too would like to keep these new lower minimum values for the brightness. It makes it much easier to be looking at light colored webpages (eg Xda) at night time.

As for battery life between A25 and A26: My usage of the N7 isn't particularly heavy. I mainly use it for around 1hr each side of sleep at night for browsing xda and rss feeds, and also few hours during the day. I'm getting the roughly the same 60mins screen-on time per 9% to 10% of battery between both versions.
[Nexus 7 Android Development] adstraylight:
There's also the thing of once having oc'ed and seen how much "better" it can be, it then feels somehow retrograde to go back to a lesser level of slick smooth butteryness even though the device is a long way from unusable. For me it is simply more satisfying to use at the higher performance level, and I'm never that far from the charger, so why not?

BTW, I had another SOD at 1.6, but the last_kmsg ends with the statement "no errors detected", could someone with a better trained eye have a look?

View attachment last_kmsg.zip

TIA