yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] poondog:
Sorry I wasn't here, did you need tissues?

Smartmax is pretty good, on this device especially with mpdec because it will boost itself. But, mpdec will boost to one freq and smartmax will be ideal at another, so its not an ideal situation.. Since ondemand and mpdec were made for each other

We had a series of blind tests, which were makefile tests and I was testing flags. For then, benchmarks were a good way to see changes as there were no code changes otherwise, and the kernel was different with the tests. We tested battery, performance before settling for the flags we use now

You should be able to run att ruu, but I'm not 100% sure. The gpe firmware is not an issue. But, you will still have s off

Supercid can easily be removed with the fast boot OEM writecid command

Yep! Depends on what other devices you have around :D
[One (M7) Original Android Development] DanteGR:
There is a very detailed sticky on the general M7 forum concerning your topic if I remember correctly.

Might be worth a look if you haven't already done so :)

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] xero110:
Because not all ROMs/kernels are created equal. I use benchmarks for a base of how well they run. Iv'e installed kernels on the same ROM and get different results. So if I install a kernel and get 14-18k I move to the next kernel. I've installed ROMs that run like crap too. Yes, it's not real world usage, but it gives me an idea of what I'm in for.

I hear people say this a lot and think when it comes to custom ROMs and kernel benchmarks have a use to judge how well your new setup will run.

In AnTuTu if you get anything over 20k your fine. You will not see any difference if you get 24k or 31k in real life. Sure is all you do if web and E-mail there is no point.
[One (M7) Original Android Development] poondog:
Initially I had performance and efficiency tweaks, but the stuff in the kernel in the last ~4 versions will lower benchmarks, while retaining smoothness and adding battery life. I don't judge anything by benchmarks, except for the blind tests I did which the benchmarks were quite important. Even then, some smoother performers had low benchmarks. Obviously though if I change clocks we can break 30k but thats silly.

I could have gone a completely different direction and created a performance and benchmark monster, but its battery would be worse and wouldn't last a day..
[One (M7) Original Android Development] xero110:
All I'm saying is benchmarks are a good quick way to weed out the crap. I can benchmark higher with other kernels, but yours is working great.
[One (M7) Original Android Development] poondog:
yeah, but you can really only do a fair comparison with one variable. 033 vs 040 vs another kernel there are too many variables. I pushed like 90 commits to github for 040

I understand what you're saying though
[One (M7) Original Android Development] xero110:
I understand both sides of it, I'm just saying.

You'r kernel is running really good, so I'm going to try your AOSP kernel tomorrow.
[One (M7) Original Android Development] poondog:
ah okay

Thanks, hope you enjoy. If theres interest in AOSP (cause I am happy with it) I can easily do updates when kernel.org update, and when CM update their kernels. So with the current tweaks it can be up to date with CM and have the latest 3.4.y
[One (M7) Original Android Development] xero110:
That would be great. I spend most of my time with AOSP, so yeah please.
[One (M7) Original Android Development] poondog:
I spend most time on Sense. lol
[One (M7) Original Android Development] smoki3:
Did you have a battery comparison between aosp und sense? The most time I tried it sense was a lot of better

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Original Android Development] poondog:
okay heres the preview edition of the init.d script :)

#!/system/bin/sh
### KANGAROO KERNEL SCRIPT ###
### Headless_monkeyhunta96/Poondog ###

#Enable Force Fast Charge: 0=off, 1=on
echo 0 > /sys/kernel/fast_charge/force_fast_charge

#Enable Sweep2Wake: 0=none, 1=both, 2=s2s
echo 2 > /sys/android_touch/sweep2wake

#Enable Logo2Menu: 0=off, 1=on
echo 0 > /sys/android_touch/logo2menu

#Enable Double Tap To Wake: 0=off, 1=bottom only, 2=fullscreen
echo 2 > /sys/android_touch/doubletap2wake

#Enable Logo2Wake: 0=off, 1=on
echo 0 > /sys/android_touch/logo2wake

#Enable Pocket Detection: 0=off, 1=on
echo 1 > /sys/android_touch/pocket_detect

#IO Scheduler: in lower case
echo fiops > /sys/block/mmcblk0/queue/scheduler;

#IO Readahead:
echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb;

#Min and max CPUs online: not sure if this will stick
echo 1 > /sys/power/pnpmgr/hotplug/mp_min_cpus
echo 4 > /sys/power/pnpmgr/hotplug/mp_max_cpus

#Max GPU clock:
echo 400000000 > sys/power/pnpmgr/sysinfo/gpu_max_clk

#Powersaver:
echo 0 > sys/power/powersave

#Voltage control: not supported currently
#echo "800 800 800 825 875 900 960" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

Simply save this in a text file, put it in system/etc/init.d and give it permissions like everything else in that folder

Anything else I can add.. anyone know where pnpmgr switch is in sysfs or if it exists?
[One (M7) Original Android Development] poondog:
all I have is that Sense is a bit better :) for smoothness AND battery. Because on sense we have PNPMGR and PERFLOCK to boost CPU speeds on input. Its not as good on AOSP. If we had PNPMGR on AOSP it would be ideal lol but I don't have the time.. I'd rather spend time on the sense kernel
[One (M7) Original Android Development] hmillhouse:
Poondog, I'd love to try this kernel properly, seems like it's got some big love!

However, problem - on a clean Sense 6 (IC 2.5.0) install, the idle GPU freq is always stuck at 320mhz. Why is this? It's usually 200 or 128 depending on kernel.

Any ideas why? I guess it's going to affect heat and battery.

Thanks!
[One (M7) Original Android Development] poondog:
this kernel should be 128-400MHz. When the phone gets a bit hot (~50C iirc) it will throttle to 320MHz. A lot of the time though when the CPU is idle the GPU will be working.. due to GPU rendering on some ROMs. But, when its doing NOTHING it should sit at 128MHz :)
[One (M7) Original Android Development] jerrylzy:
[MENTION=4379011]poondog[/MENTION] [MENTION=4684315]flar2[/MENTION]

After fixing a couple of incompatibilities, I managed to compile the kernel and I do feel GCC 4.9.1 is faster. It's more noticeable compared to previous gcc updates.

EDIT:

O3 is smoother than Ofast
[One (M7) Original Android Development] Artc0re:
[MENTION=559267]poon[/MENTION] are you planning to add faux sound settings to your Kernel to adjust the gain?
[One (M7) Original Android Development] dsymbol:
Hi [MENTION=4379011]poondog[/MENTION] & kernel users,

I'm very new to custom kernel, & I'd like to try out this kernel to extend my battery life without sacrifice much performance.

I'm a minimalist & I do not ever need dt2w, l2m, ect...I do not ever care for benchmark.

I only care for battery life but not getting lags.

Regarding my usage, I use Lux to customize my screen brightness, & for apps, I only use web browsing, text, email, whatsapp, viber, making calls, & a tiny bit of facebook & youtube. No games whatsoever.

I'm at the moment running InsertCoin Sense 6 rom & could someone please give me some inputs on:

1. Should I stick with stock kernel, & turn on power saver mode (to reduce CPU speed?)

Or

2. use KKv040 with some recommend settings for my need please?

Between 1 & 2 with optimal settings, which 1 would give me the best of both worlds?

If #2 is recommended, Could you please show me optimal settings for my need please?

Thank you for your time.
[One (M7) Original Android Development] Thealshear:
All I have to say one of the best AOSP kernels I have tried low drain and smooth
[One (M7) Original Android Development] poondog:
What fixes did you need? I have -O2 in mine

We've found that -O2 is the best for a blend etc, with some -O3 and -Ofast flags. Call is -O2.5 :D you're using CR83 toolchain too?

Nah, probably not.. I use/recommend ZeroInfinity mod as it requires no apps or userspace control

Hi, I'd recommend to keep settings stock. They are my settings (although you might want to turn off 2w, you can use the script I just posted for that) and are a blend of smoothness and battery.

If you want to save more then use the power saver cpu :)
[One (M7) Original Android Development] smoki3:
Install this kernel an be happy. Don't care about kernel settings. Give it 2-3 full cycles of charging.

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Original Android Development] mitas35:
Battery life? Care to share?
[One (M7) Original Android Development] dsymbol:
Thank you for the quick reply.

I've just flashed your kernel in AROMA.

1. So without using trickster mode to edit anything, I'm keeping in stock per your recommendation correct?

2. So the Power Saver mode still works & reduces further CPU speed even though I use a custom kernel?

3. I have to give it at least 3 cycles to see any battery life improvement, correct?

Thank you for your time.
[One (M7) Original Android Development] hmillhouse:
I guess it's slightly unscientific, but with a clean install, temps around 35c, then stock or elementalx idle at 200MHz with screen on & GPU rendering on - Just sitting looking at faux tool or trickster mod. But with yours it's at 320MHz.

Is there any other info I can give you to help, or am I the only one with this issue?

Many thanks, Poondog!
[One (M7) Original Android Development] Headless96:
I can confirm this..

When the cpu ramps up, the gpu frequency scales down to 128 mhz but when cpu reaches the lower clocks (384mhz) the gpu jumps to 320 and stays there

Also [MENTION=4379011]poondog[/MENTION] for your question about the script, pnpmgr is located in /system/bin/pnpmgr
[One (M7) Original Android Development] DanteGR:
1. If you don't care about features like dt2w, s2s etc i would suggest using Trickstermod to turn them off and gain that little bit more battery life

2. In some roms power saver does not limit cpu frequency for some reason. Just try it on yours though and let us know how it goes

3. Most people say that at least 2-3 full charge cycles are necessary to witness optimal battery life but to tell you the truth for me it's the same from the 1st charge cycle

Hope that helps a bit :)

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] poondog:
Jerry won't share because theres a 4.9.1 test kernel in this thread and that will ruin the point of a blind test :P

1. only if you want to change stuff like 2w.. otherwise for a balance, keep things as they are

2. depending on your ROM, all sense 5.5 ROMs and some sense 6 ROMs (ViperOne, InsertCoin, I think Renovate too) will limit freq to 1134 max when you turn on power saver for CPU. It works as stock :P

3. Might be noticable in the first cycle, but generally after 3 or 4 it will be more apparent

Mine idles at 128 or 320MHz.. tbh it doesn't matter :D I didn't change much for GPU, if anything it should be better on battery because of the lower min freqs. Its normal behavior for the tweaks I have done
[One (M7) Original Android Development] poondog:
Cheers :)
[One (M7) Original Android Development] DanteGR:
[MENTION=4379011]poondog[/MENTION]

Power saver doesn't seem to limit cpu frequency on Renovate rom mate

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] poondog:
edited :P
[One (M7) Original Android Development] dsymbol:
*** EDIT: I do not need dt2w, s2w, l2m ect..

I guess I dont need trickster mode to turn them off because I think they're off as default. I try to swipe, double tab ect.. & the phone doesnt wake.

Am I right?

Thank you both !
[One (M7) Original Android Development] DanteGR:
S2s and dt2w as well as pocket detection are ON by default mate :)

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] dsymbol:
I've just downloaded trickster mod > Specific > Screen Wake Control. I see everything is off by default.

It's cool, that's what I need.

I'll give it a couple of cycles.

Thanks mate!
[One (M7) Original Android Development] DanteGR:
Hmm strange.. [MENTION=4379011]poondog[/MENTION]

Aren't the features i mentioned ON by default??

I could swear they are..

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] poondog:
Not really an issue but this is what comes default
[One (M7) Original Android Development] DanteGR:
Yup. Thought so. Thanks for confirming ;)

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] poondog:
No problem!

Hope everyone's enjoying the kernel
[One (M7) Original Android Development] DanteGR:
I certainly am!

Battery life seems better on 4.9.1 even from the first cycle (screenshot coming a bit later) although i still think it's just a taaad bit slower than 033 :p

Have a great Saturday everybody :)

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] txordi:
Of course. Trying the test Kernel. In smoothness all going great. In battery I even have no idea.

If you let me a little off-topic. Anyone of you knows what is fast-dormancy? And is better to have it on or off? Thanks.
[One (M7) Original Android Development] poondog:
I still don't think its any slower :) you too man, even though its nearly finished here!

http://xdaforums.com/galaxy-s2/help/fast-dormancy-quick-explanation-findings-t2241319

:)

In short: If your carrier supports Fast-Dormancy, better to keep it on. If its unsupported, turn it off :)
[One (M7) Original Android Development] jerrylzy:
It's too early to tell

Mainly a bunch of "uninitialized" warning. Very annoying because it happens whenever I upgrade GCC. Need to be fixed to make the kernel compiled.

I haven't tried O2 but O3 is smoother than Ofast according to my experience.

Yes I'm using his toolchain. He makes things a lot easier.
[One (M7) Original Android Development] poondog:
ah ok so the same stuff on -O3 :)

After I had fixed them for -Ofast and 4.8.3 I didn't have any new ones on 4.9.1... guess because I went through and fixed all the warnings on top of the errors.

You haven't tried -O2 lol you have not lived my friend.
[One (M7) Original Android Development] herwegan:
Your script? :D Where? :P
[One (M7) Original Android Development] poondog:
a page back :)
[One (M7) Original Android Development] poondog:
You beaut!

Put your name back there :P

A few things

Not sure if the min/max cores will work.. maybe if pnpmgr is disabled it will work cause it seems to reset :P

Does it mean the script will try to rename pnpmgr every time? Oh well :P

Thanks for your help and everything :)
[One (M7) Original Android Development] Headless96:
Haha nah if I put my name there, everyone will be asking for an official zip made just from you! :p

Yeah the min/max thing doesn't work when pnpmgr is enabled

And it'll only rename it once, since when it looks for it again it won't find it and it'll just move on to the next command

Edit: Just worked out how to make the min cores thing stick (I'll leave out max cores cos that's already 4, unless you wanna change it?)

Here's the code:

chmod 666 /sys/power/pnpmgr/hotplug/mp_min_cpus
echo 1 > /sys/power/pnpmgr/hotplug/mp_min_cpus
chmod 444 /sys/power/pnpmgr/hotplug/mp_min_cpus

Fixed my other post and updated zip, please download again if you already have for the updated files!
[One (M7) Original Android Development] poondog:
True! Just don't let anyone know you did it, I will take all the credit :D

Same thing works for max cpus too?

edit: can you please add in max cpus to your script too, then I can link it in the OP :D
[One (M7) Original Android Development] herwegan:
Haha thank you mate! You're now my officialy recognized poondog zip maker :P
[One (M7) Original Android Development] Headless96:
Done! :D

Guys anyone who's already downloaded it before this post, please download again.. Made some changes to updater-script and fixed the hotplugging command

Should be good to go now!
[One (M7) Original Android Development] poondog:
<3
[One (M7) Original Android Development] lerx:
Just one more feature and it would be perfect! The option to choose vibration for sweep wake controls :P
[One (M7) Original Android Development] Headless96:
No do it yourself!

... Just kidding, updated my other post, download again :p

The vibration for wake up controls command is disabled by default, delete the # before the command and choose the value you want :)
[One (M7) Original Android Development] poondog:
Max CPUs limit works :)

Magpir if you're still lurking, there's ha dual core kernel :D
[One (M7) Original Android Development] poondog:
Init.d script has made it to post #3. Thanks to Headless_monkeyhunta96 for your work :) Hit his thanks button!

edit: I just checked on my Nexus 7, the GPU sits at 320MHz there as well (stock behavior on that)
[One (M7) Original Android Development] Headless96:
Bro I just realized, the GPU command in the script doesn't work on it's own like that ... We have to do a similar permission lock like the min/max cores online

Anyways, I fixed the zip, reuploaded and edited my post

Would you mind re-quoting me in the OP to avoid confusion?

Also can you guys please download again (last time I promise :p)
[One (M7) Original Android Development] poondog:
yeah ok haha

edit: you might wanna take a look at the top 7 lines of the script too while you're at it ;)
[One (M7) Original Android Development] Headless96:
Lool, the zip is actually fine, it's just when I copied it over to post :p

Ah well, double the recognition ;)
[One (M7) Original Android Development] poondog:
haha okay fair enough understood :)
[One (M7) Original Android Development] herwegan:
zip works now perfectly on my phone. thank you both very much [MENTION=4379011]poondog[/MENTION] and [MENTION=4935526]Headless_monkeyhunta96[/MENTION] :)
[One (M7) Original Android Development] poondog:
yeah its really good here too, I am running dual core for the lolz
[One (M7) Original Android Development] DanteGR:
Pretty good I would say :D

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] poondog:
Yeah looking good! You going 2 days? I'm sitting at 60% on a mystery test kernel.. Thinking should I go day 2? I work till late on Sundays so idk :P
[One (M7) Original Android Development] poondog:
Just thought of a brilliant new name! Can you change the name in script in your post to Kangaroo Control script (in caps) in the top of the script? Thanks
[One (M7) Original Android Development] Headless96:
Yeah sure mate

Updater script, init.d file name and title all updated :)
[One (M7) Original Android Development] poondog:
Unless anyone has a better name? :)
[One (M7) Original Android Development] dsymbol:
this is by default on my phone. No issue though, this's what I want.
[One (M7) Original Android Development] txordi:
I think that's because you used another custom kernel before and you've some files remaining from those kernel
[One (M7) Original Android Development] kaleci07:
i just has random reboot on v40 test version , using viper and used it always whit your kernel is it someting or am i thinking about it too much :)
[One (M7) Original Android Development] daffie:
[KERNEL][LINARO4.8.3/4.9.1] ★☆ Kangaroo Kernel ☆★ | 4 MAY | v040 | SENSE4.4.2...

Another test, this time with latest kernel v40 and heavy usage during 8 hours.

Started at 85% and finished at approx 15% : 4 hours of screen time, over 20% app usage @70% battery usage.

Pretty damn good imo!

Thanks Poondog...kernel approved ;)
[One (M7) Original Android Development] DanteGR:
Have gone many times 2 days but only when being on wifi.

When on mobile data I'd always be lucky to go maximum 1 day.
[One (M7) Original Android Development] hamadazh:
hi first i like this kernel and this thread so much members so friendly specially you ( poondog )

1- i am sorry for my very bad Language

2- about INIT.D SCRIPT i am from those ( If you have no idea what is going on ) :)

3- i do not know about somethings in the INIT.D SCRIPT specially last 9 steps i know only some things like sweep2lock and those things

what can i do Exactly by this script? i have to flash it only without any change from me or this script for people who know what is going on?

for example i need this (Enable Force Fast Charge) this for fast charge right? i have to change 0 to 1 right? or your kernel have this step already

i am confusion tell me what can i do or i have to flash only your kernel and leave this script like If I had not see it before ?

Sorry to bother you and sorry for my languge
[One (M7) Original Android Development] neniick:
You can use the script to turn things like s2w and dt2w on or off. But you can also use apps like trickstermod to do this.

I myself prefer to use trickstermod to control those settings, so I can change them whenever I want.

Verstuurd vanaf mijn HTC One met Tapatalk
[One (M7) Original Android Development] hamadazh:
thanks for replay

can you give me advice for what i have to do for good results specially in last 9 steps in the script

thanks
[One (M7) Original Android Development] smoki3:
[MENTION=4379011]poondog[/MENTION] are you planing to add MLG?

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Original Android Development] CamoGeko:
I doubt it's one of his priorities.

Btw [MENTION=4379011]poondog[/MENTION], been running 040 today and I love how smooth it is. Thanks for all your work on this kernel so far, you're definitely heading in the right direction.

Kangaroo Kernel Kontrol :p

[MENTION=4935526]Headless_monkeyhunta96[/MENTION] would be nice to have undervolting options in the script too if possible but probably would be too much work. Something like flar has in his installation script.

Sent from my baked potato with blue cheese
[One (M7) Original Android Development] neniick:
You mean good battery and performance results? I would ignore the script.

Just follow these steps;

1 . flash the latest kernel

2. Use trickstermod to adjust your screen wake settings.

3. Ignore all other settings, they are just fine already.

4. Thank [MENTION=4379011]poondog[/MENTION] on your bare knees (most important step :D)

5. Profits!!1!

Verstuurd vanaf mijn HTC One met Tapatalk
[One (M7) Original Android Development] DanteGR:
Hey mate.

Have u been running the test version or the normal 040 one?

Thanks :)

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] CamoGeko:
Hi mate, not been aware of the test version so running the 040 release here.

Sent from my baked potato with blue cheese
[One (M7) Original Android Development] DanteGR:
Ok thanks matey.

Here's the test version. Could u please try it and get back to me?

Thanks ;)

https://www.dropbox.com/s/iwjbzdd3sx22vzx/kk040_4.9.1.zip

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] CamoGeko:
No worries mate downloading it now.

Where did you dig it up from? Little kernel compiler you :p

Sent from my baked potato with blue cheese
[One (M7) Original Android Development] DanteGR:
I wish :thumbup:

It's on some previous page in this thread mate. Just to bored to search for it so I uploaded it again.

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] hamadazh:
Thank you so much
[One (M7) Original Android Development] CamoGeko:
Hahaha, I read the last few pages.. must have missed it thought.

I'm flashing Renovate r84 tonight so will flash the test kernel straight after.

Thanks for the heads up mate! I have been on ElementalX since getting my HTC One so it will be nice to run another kernel for a while and see the difference.
[One (M7) Original Android Development] Headless96:
Undervolting options are in the script already mate, check the second last line ;)

But it's not currently supported yet, I'm guessing poondog's gonna add it in a later version so I left the option in there
[One (M7) Original Android Development] CamoGeko:
Ah I see it now mate, forgive my mistake. :(

I hope he adds it sooner rather than later, the UV and Thermal options are the ones that I really miss in this kernel.