yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] ser35:
Totally agree!!! But strange that HTC is using io_is_busy =1
[One (M7) Original Android Development] poondog:
Value of 0 will not take io request as input

Value of 1 will take this request as input

Therefore theoretically there will be more smoothness and higher performance with 1, but more battery saving with 0
[One (M7) Original Android Development] Rad ryan:
Basically everything poondog said. [emoji16]

Yeah there can be lags, and io_is_busy will smooth them out but I haven't really noticed much lagging. Also there are other tunables that can reduce lags such as Ramp_Up_Step, Up_rate, Touch_Boost_Freq, and even Down_Rate/step (by decreasing ramp down step and increasing down rate the cpu will stay at higher freqs for longer). Increase Up_rate and the cpu scales up faster, increase ramp up step and it will increase freq in bigger chunks leading to higher freqs. Touch boost freq and duration will probably make a huge difference in responsiveness by increasing but remember that if you are touching the screen alot it could use much battery if these are too high (personally I don't go above 1350000 for freq and 150000 for duration.

PS Max_CPU_Load will remove lags by lowering it. You can start with 80 and go down from there (below 70 will start to use a lot of battery). Also Min_CPU_Load can help some by lowering it. Remember that the range of loads between these 2 settings will be when the cpu is at the ideal_freq, loads below the Min_CPU_Load is when the cpu will scale down, either to ideal_freq if the current freq is above it or lower if current freq is at or lower than ideal_freq, loads above Max_CPU_Load is when the cpu starts scaling up (in the same way I just said above).

Cool, I didn't know why it did what it did but now it makes much more sense... Haha, ya get it... Sense. [emoji16]
[One (M7) Original Android Development] poondog:
Correct. Just think, its all about thresholds so if it scales with a lower threshold then it might be going too high too soon. If you see the tunables for other devices in the smartmax source, you can see that for older devices the thresholds are wayy lower
[One (M7) Original Android Development] fanbogo:
asphalt 8 works amazing, not even single lag, i thought this is battery friendly kernel :D ha good job man i love your job!
[One (M7) Original Android Development] poondog:
All in one ;D
[One (M7) Original Android Development] thaiboyger:
Wow what's up with today, no post at all

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Original Android Development] jukiewalsh:
Because nobody's having any issues [emoji12]
[One (M7) Original Android Development] Vaiet:
Well, I had issues with sound on Kangaroo v100 and Insert Coin (3.0.3 and 3.0.5). The sound was changing it's loudness on earphones and through speaker. After few minutes, usually, it was so quiet and distorted, that I barely could hear my wife like she was holding her cell few meters away from her, but after half a minute or so it all came back to normal, sometimes even it was louder than before. And so on. Experienced it many times throughout last few days but not even once after changing the kernel.
[One (M7) Original Android Development] dena994:
Anyone tried the aosp version on Paranoid?
[One (M7) Original Android Development] clockworkstop:
Yeah, works great. I have some apps force closing on ART that don't usually force close, but somehow I doubt that has anything to do with the kernel.
[One (M7) Original Android Development] jukiewalsh:
Yeah I also had a few fc's periodically and I wasn't even on art but I think that's a pa problem like you said because I tired cm for a day and it ran okay.
[One (M7) Original Android Development] Rad ryan:
Insert coin was one of the problem roms with sound bug on v85. Since v100 is based on v77 maybe it wasn't from all the changes from v77 to v85, or at least some of the changes. Maybe [MENTION=4379011]poondog[/MENTION] has an idea of what it could be.

Poondog, v100 seems to act similar to v77 as far as battery drain goes. I'm referring to my post from a few days ago that said

I, IMHO, still think some of the changes that were reverted from the v85 kernel had a noticeable impact on the performance and battery life in a positive way. Maybe you could put the Scheduler and memory optimizations from v85 back in v100 and see how it goes, or if you wanted to you could even rebase v85 to 5.11 like you did for v77 and apply the same patches you added to v77 and then do a blind test of the 2 versions which would be identical except for 1 was from the v77 and 1 from the v85. I'm not sure how much work this would be for you though so it's quite understandable if you don't want to do that. [emoji4]
[One (M7) Original Android Development] poondog:
So the sound issue is still there? Was it there at all on 077? I think I know what it may be but that will effect versions from like 40 something

Not related :)

I'll try some things but 085 is gone from my git lol
[One (M7) Original Android Development] jukiewalsh:
I

For the on call issues and sense, you guys should maybe give this or similar mods a shot http://xdaforums.com/showthread.php?t=2406524 and then see if the problem persists or if it is simply an issue with sound suppression. Then we can know for sure if it's something in the kernel.

Or provide a logcat of the sound issue for him to look at because by the looks of it nobody is really positive about what it is 100%... I've been running aospa for awhile but before that I didn't notice anything on kangaroo running viper
[One (M7) Original Android Development] poondog:
Not sure if this is the issue but yeah confirmation would be nice :)

The issue of the Mic though might be different

Anyone up for blind tests? I've got a few sleep/screen off stuff I'd like to test :P
[One (M7) Original Android Development] Asselalf:
Here I'am...
[One (M7) Original Android Development] mettleh3d:
I'll test :)

Sent from my HTC One
[One (M7) Original Android Development] Fuzi0719:
I'm using v100 on the stock T-Mobile US 5.14.531.1 ROM (rooted, unlocked, S-OFF) and I'm not having any issues. This is probably the most stable and solid kernel I've tried in a long while. After settling in, battery life is the best of any kernel, it is responsive, and great sound whether on-call or listening to music. I've kept the settings pretty much default but I only have s2w+s2s active.
[One (M7) Original Android Development] ser35:
I am willing to test

But I have no problem v100!

---------- Post added at 10:03 PM ---------- Previous post was at 09:23 PM ----------

I use smartmax for several days already. Excellent results! The kernel has improved efficiency and battery live. Interface has become even smoother and smoother.

I use these settings:

(These are my current settings that are more battery biased. Try em if you want and tweak how you like:)
[One (M7) Original Android Development] Undermyoath:
I'm available to test some of your builds, poon.

Just hit me up when needed with the thing you want to compare with the stable v100.

;)
[One (M7) Original Android Development] myrigon:
Sure. I'm having a little sit on viper one at the moment, so can test.
[One (M7) Original Android Development] jukiewalsh:
Just switched back to sense so I could too. One question though, adding qemu.hw.mainkeys=1 to my build.prop still doesn't stop the navbar from popping up in certain apps (8tracks for example), is there another way to disable it?
[One (M7) Original Android Development] Headless96:
Change the home button setting under Display to 'press and hold for menu'

Should get rid of the navbar
[One (M7) Original Android Development] jukiewalsh:
that's what it already was set for.
[One (M7) Original Android Development] poondog:
Thanks everyone

The test isn't for a fix, it is about battery. I might push out v108 first though :)
[One (M7) Original Android Development] poondog:
Blind tests v2

I rebased to v100 (my repo is on v107 atm) to make it a fair test. This weekend is the deadline. Sunday I hope to push the new kernel, or earlier

Changelog: v1xx TEST

.fixed thermal for some users, it was not applying

.mystery battery changes

Please test and report on the battery life, particularly with screen off/deep sleep. If the changes have an impact then there would be battery savings all over, not just in screen off. There are two test kernels, I am not saying which one has what in it. Thats for you to find. Please tell me which is better :)

ps if you know what the changes are, don't ruin the BLIND test :P

Added a poll too :)
[One (M7) Original Android Development] mettleh3d:
You're a very interesting dev poon

Sent from my HTC One
[One (M7) Original Android Development] poondog:
Interesting? That's good or bad haha
[One (M7) Original Android Development] ghostryder12:
??

HTC One M7_UL CyanogenMod 11 Snapshot Build
[One (M7) Original Android Development] poondog:
Gotta be good right?
[One (M7) Original Android Development] ghostryder12:
It's just got to... ?

HTC One M7_UL CyanogenMod 11 Snapshot Build
[One (M7) Original Android Development] supadupa111:
Soo... you're done with gpe (4.4.4)?
[One (M7) Original Android Development] Rad ryan:
[emoji43][emoji22] Ah well. Still best kernel around, I even would venture to say that (although I haven't used many other kernels for other devices) this could possibly be one of, if not, the best kernel in xda at the moment, as far as performance to power consumption/battery life goes. It may not have all the bells and whistles (which I don't even use), but it has what I need and want and most importantly it has swag. [emoji16]

Glad they worked out for ya. [emoji2] Did you put the settings in an init.d script? If so would ya mind sharing?

Try em with pnpmgr on and then with pnpmgr off. The difference is pretty noticeable. Let me know which you prefer if you don't mind. [emoji3]

Here is one more thing for ya to try if ya want. It's just a tweaked mpdecision to attempt to squeeze a little more battery out of the kernel, if that's possible. [emoji16]

It will be flashable but you can take it apart and do it manually if ya want. 2nd is a script to save any changes you make, if you do at least, into a ready to go file. If you do make changes I'd like to try em. [emoji16] You will need to change the path in the script unless you create the folder I have it being saved to in the script.

TO ALL:

Please don't download and flash this unless you know what you are doing and I'm not responsible for anything that may happen to your phone. 99.999999% chance nothing bad will happen, basically as close to 100%as possible. I don't say 100% bc rarely things can happen during the flashing process of anything. To remove the mod go to "/system/ect/init.d " and delete the file called "21mpds" and reboot. Simple as that. If you do try please report if any battery savings, etc. [emoji2]

PS if you are doing the blind test for poondog it's best to not try this bc it will affect the results of the test. When doing a blind test it is best to keep everything as close as humanly possible to the same except for the thing being tested. So wait until after the test.

21mpds = https://www.dropbox.com/s/w043a4dqsftpbmq/mpds.zip

My to script = https://www.dropbox.com/s/5q4lgsju9uxzk3x/mpd_settings_to_script

Yeah, blind test. I love em [emoji16]

It's like playing hide and seek and cracking open a pinyata at the same time [emoji16]
[One (M7) Original Android Development] myrigon:
Testing test p at the moment. Haven't noticed anything yet, but will report more in a couple of days.

Also, have you given any more consideration to making something compatible with 4.4.3/4? Really missing kangaroo goodness on the up to date ROMs. When gaming with another kernel I'm usually 6 degrees hotter, with comparable front end settings! :eek:
[One (M7) Original Android Development] poondog:
Thanks again for your very kind words, I highly doubt it though :)

Its nothing like pinyata and hide and seek, because there is only one variable :D Thats how experiments work, there can't be more than one variable otherwise we can't have accurate results :D :D :D

btw your settings are about to become default for the kernel smartmax (ondemand will remain default gov)

Cheers. You'll notice the difference in battery in standby, not as much in use. I have considered this, rebasing to gpe 4.4.4 source but I don't think its worth it, waste of time imo when I am not going to use it yet (until reno/viper are updated anyway, which I doubt they will move officially to this base)

PRETTY COOL AYE :D
[One (M7) Original Android Development] ser35:
smartmax/fiops/illinois

pnpmgr -on

cpu 384-1728

gpu 400

is my script

http://xdaforums.com/showpost.php?p=53743804&postcount=4052
[One (M7) Original Android Development] poondog:
Ok what are the winning Smartmax tunables?
[One (M7) Original Android Development] ser35:
I use these settings by Rad ryan

( Rad ryan- These are my current settings that are more battery biased. Try em if you want and tweak how you like)

## Cpu governor settings

echo 150000 > /sys/devices/system/cpu/cpufreq/smartmax/input_boost_duration;

echo 0 > /sys/devices/system/cpu/cpufreq/smartmax/io_is_busy;

echo 95 > /sys/devices/system/cpu/cpufreq/smartmax/max_cpu_load;

echo 45 > /sys/devices/system/cpu/cpufreq/smartmax/min_cpu_load;

echo 10000 > /sys/devices/system/cpu/cpufreq/smartmax/min_sampling_rate;

echo 162000 > /sys/devices/system/cpu/cpufreq/smartmax/ramp_down_step;

echo 1 > /sys/devices/system/cpu/cpufreq/smartmax/ramp_up_during_boost;

echo 162000 > /sys/devices/system/cpu/cpufreq/smartmax/ramp_up_step;

echo 30000 > /sys/devices/system/cpu/cpufreq/smartmax/sampling_rate;

echo 594000 > /sys/devices/system/cpu/cpufreq/smartmax/suspend_ideal_freq;

echo 918000 > /sys/devices/system/cpu/cpufreq/smartmax/touch_poke_freq;

echo 60000 > /sys/devices/system/cpu/cpufreq/smartmax/up_rate;

echo 918000 > /sys/devices/system/cpu/cpufreq/smartmax/awake_ideal_freq;

echo 1 > /sys/devices/system/cpu/cpufreq/smartmax/boost_duration;

echo 1026000 > /sys/devices/system/cpu/cpufreq/smartmax/boost_freq;

echo 0 > /sys/devices/system/cpu/cpufreq/smartmax/debug_mask;

echo 15000 > /sys/devices/system/cpu/cpufreq/smartmax/down_rate;

echo 0 > /sys/devices/system/cpu/cpufreq/smartmax/ignore_nice;

## undervolt

echo "775 775 800 825 850 875 900 925 925 950 975 1000 1025 1085" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table;
[One (M7) Original Android Development] poondog:
They were the battery biased or the balanced ones? I think its better to have battery biased for smartmax, since ondemand will always kick a** in performance
[One (M7) Original Android Development] ser35:
Yes, the settings is battery biased

I too believe that smartmax must be economical. And for antutu and heavy gaming let remains fast ondemand
[One (M7) Original Android Development] poondog:
Well new version is basically ready :) just waiting on those test results
[One (M7) Original Android Development] bikkits:
du wunt puundug
[One (M7) Original Android Development] poondog:
Took some decoding but I know what you said now :)

Eta this weekend, I wanna include the tweaks from the tests
[One (M7) Original Android Development] ser35:
test

It seems to me that kk100_p has a smooth and responsive interface. kk100_с-desktops button with jerks.
[One (M7) Original Android Development] poondog:
Thx for reporting :) I don't notice much difference here
[One (M7) Original Android Development] xavierf:
Hello,

Is it possible to have a mirror for JOEY kernel I have some issues with androidfilehost :confused:

Thx :good:
[One (M7) Original Android Development] Rad ryan:
I mean like hide and seek bc there is a surprise waiting for you to find it, and a pinyata( a pinyata with only a single piece of candy, but damn is it good) bc once you crack it open (poondog tells us) it's like getting the candy ? [emoji16]

Yes, that was possibly the worst metaphor in the history of the universe. [emoji16]

Cool, I'll let you know if I come up with any better smartmax settings but I doubt that they would be that different bc I'm pretty happy with them as is. [emoji2]

100% agreed. Ondemand is great on your kernel and I use both it and smartmax, depending on what I'm doing. Surprisingly, I use smartmax for games bc I get better battery life with it on games and don't really notice much difference in Smoothness of the game, except for the heaviest of heavy games.

They seem pretty close to me, but I haven't really spent more than an hour on each version so far. I'm gonna use the .c version for rest of day and .p version all tomorrow.

In the short time I used them each I had the opposite experience as ser35. It felt as if .p version was a little bit more sluggish than .c. .c felt real smooth, in fact it felt very similar to v100. The .p version was still smooth but it seemed to be just moving a little slower, but battery seemed to be a little better but really its way to soon to tell.
[One (M7) Original Android Development] ser35:
No!

I think version C more slowly, with delays in the interface. Version of the P runs better and more smoothly.

UPDATE

Again, carefully tested both variants (c & p), the difference in the smoothness and responsiveness of interface not!

All equally
[One (M7) Original Android Development] herwegan:
I'm testing version c right now, seems really smooth. Will report back about battery life soon.
[One (M7) Original Android Development] h4waii:
Any chance of getting DT2W on Joey / CM11 kernel releases?
[One (M7) Original Android Development] Rad ryan:
[MENTION=5428870]ser35[/MENTION] here is your script with the other 3 cores (123) governors set to smartmax also, the rest is untouched. Thanks for scripting out the gov settings, I copied and pasted em in my script. On v100 the sysfs is there for all 4 gov.
[One (M7) Original Android Development] ser35:
You can publish your script?

And coming back to the 21mpds. What can you tell me about this:

echo "0 2.0 3.1 4.5" > /sys/power/pnpmgr/hotplug/mp_nw;

echo "0 1.1 2.1 3.5" > /sys/power/pnpmgr/hotplug/mp_ns;

echo "0 150 150 150" > /sys/power/pnpmgr/hotplug/mp_tw;
[One (M7) Original Android Development] supadupa111:
Haven't used .c but .p is great for screen off
[One (M7) Original Android Development] poondog:
Thx for the input :)

This is what I expected, same in smoothness but slightly different in suspend battery

Cheers

Nah probably not, its causing way too many issues

Thanks for the feedback
[One (M7) Original Android Development] xavierf:
Please
[One (M7) Original Android Development] poondog:
Will do when I am at my pc, sorry :)
[One (M7) Original Android Development] xavierf:
No problem Thx
[One (M7) Original Android Development] poondog:
I think this was the latest :D
[One (M7) Original Android Development] dani_nec:
I used yesterday's version p. I've been feeling that everything worked very smooth, but I think the battery in general has been a little worse.

I'll try the C version now.
[One (M7) Original Android Development] poondog:
Thanks for the feedback again, I am keen to know what you guys think of v100 vs v100_p vs v100_c
[One (M7) Original Android Development] myrigon:
P seemed to run a little less cool imho. The standby battery did seem to be better like you said.
[One (M7) Original Android Development] poondog:
So to confirm.. you say P is hotter but better battery? They're usually opposites :D
[One (M7) Original Android Development] myrigon:
Lol, I know, but that's what I saw. Maybe a background app, or something?
[One (M7) Original Android Development] poondog:
Well the test goes for a few more days :)
[One (M7) Original Android Development] herwegan:
Version c: runs smooth, runs cool, but no impact on battery life for me, maybe even a little little worse than stock v100.
[One (M7) Original Android Development] donibrasco:
I'm using version "c" and have worse battery in sleeping mode than v100, runnnig smooth as usual, can't say cooler feels the same.Going to run another cycle with "c", and switch to "p".
[One (M7) Original Android Development] poondog:
Doing a bit of a light orange theme while waiting on the results :) [MENTION=4380624]Raymond Ebertt[/MENTION] when can I get my RT?
[One (M7) Original Android Development] ser35:
In Australia so cold? Just 8 degrees? I thought you had heat.
[One (M7) Original Android Development] poondog:
Its winter :)
[One (M7) Original Android Development] randykzc:
Erm.. Just my opinion.. I think p standby is much better but temperature is about the same as v100.. C standby is not good but not sure why feels temperature a little cooler.. Anyway I kinda think p is better for battery.. I go for P as of now
[One (M7) Original Android Development] poondog:
Thanks for the feedback

I wonder what you guys will think when the changes go public :)
[One (M7) Original Android Development] thatnitai:
I wonder if temps are something we should really worry about? I doubt even the hottest Kangaroo kernel was even half dangerous to our phones, and the battery drain resulting from the heat is probably also very minimal. Perhaps temps should matter less to us, its nice to have a cool phone in your hand, yes, but its probably less important than battery life + performance i'd wager
[One (M7) Original Android Development] drsamratroy:
[MENTION=4379011]poondog[/MENTION] please try to implement the motion launch gestures in your kernel...i so miss using ur kernel & its awesome battery & coolness...have been using the MLG in Elemental with the new xposed module 'Wake Gestures' & i now cant live without it...it is very nicely implemented & using MLG to unlock screen or launching any app or changing music is a breeze...i know you have reservations about using a 3rd party module for the MLG with ur kernel but afaik i dont think it cannot be incorporated with the kernel & we have to always use a xposed module in M7...so please if possible look into it... :good:
[One (M7) Original Android Development] dani_nec:
I have worse battery life with c variant..
[One (M7) Original Android Development] YudmudTR:
DELETE
[One (M7) Original Android Development] randykzc:
I have the same thought..
[One (M7) Original Android Development] poondog:
I'm not worried, its already cooler than stock and we have thermal customizable to make it even cooler by throttling earlier

I'll consider soon
[One (M7) Original Android Development] randykzc:
hah..seems like 50/50 in the poll
[One (M7) Original Android Development] ser35:
In December, 2014 for m7 will be the official android L (the ART instead of the dalvik runtime) and the xposed module stops working altogether and gestures too.
[One (M7) Original Android Development] dani_nec:
Definitive, version p have more battery live
[One (M7) Original Android Development] shiningarmor:
been bothering me for a while now,

max cpu freq kept dropping to 1.2ghz when i open up next browser and some other small apps like keep n stuff.

set cpu freq lock to on in trickster mod but doesnt seem to help

arhd sense 6/ kk4.4 here (forgot arhd version)

using ondemand governor and v100
[One (M7) Original Android Development] ser35:
1. Power save mode off (in settings)? It limits the frequency of.

2. If the processor temperature is greater than 46 degrees then trigger thermal limiting and rate falls to 1242mz.

Raise the threshold limits are higher.

You are now on the street (or air) what temperature?
[One (M7) Original Android Development] fastcx:
1st, did u load init script for this kernel? If you haven't, do it so the top speed is fixed during boot. Once you allow that script to run, shouldn't have such issue, unless u run extreme power saving mode, which I can't seem to make it back to full speed after exiting that mode
[One (M7) Original Android Development] poondog:
Still a few days :)

I doubt xposed will go extinct, they'll work around it

Poll is pretty close :D

Did you have anything setting cpu? It should behave normally. It will boost itself though to 1.1ghz or similar on input

Cpu lock or anything won't do anything good :)

And hi incredible s user :D
[One (M7) Original Android Development] zoological:
Sorry guys, i must be blind: i can't find the link to download the latest joey kernel for cm11 :confused:
[One (M7) Original Android Development] poondog:
You must be

Thats what search is for

You can find on page 1