yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] dictionary:
So, I was having the boot issue. Then flashed elemental 14.0. It booted no problem. I then flashed 009, to reintroduce the boot loop, so that I could test 005 and 0061. 009 booted up just fine, and I've been using it for hours now. No idea what that's about. Will reflash ROM again and try to replicate bootloop so that I can test new kernels
[One (M7) Original Android Development] Rad ryan:
That's why I had said maybe it was a ramdisk issue occurring bc poondog's kernel uses current ramdisk and packages his zimage in with it. Mine was fixed by flashing the stock kernel/ramdisk and then reflashing poondog's kernel after reboot. Your situation fits also, but poondog said that he smelled something fishy and worked on it for like 2 hours, so I'm guessing whatever it was that he got it figured out. To reproduce the bootloop you will probably have to do what you said and then flash another 009 version after, xg version did it for me only that once but it hasn't happened since. I have had phone hang on boot 2 or 3 times out of about 6 to 7 boots but a hard reboot and it would boot fine.
[One (M7) Original Android Development] dictionary:
Yeah, I had kind if narrowed it down to the ramdisk after it worked with Elemental.
[One (M7) Original Android Development] Rad ryan:
I don't know if it's the ramdisk or not. poondog said that it probably something else and he was debugging it. So I'm not sure what the deal was, I had just initially thought it was ramdisk. Did you manage to reproduce the bootloop and flash his fix test version/s?
[One (M7) Original Android Development] poondog:
0061 (as numbers suggest) is not version 61, it's version 006 test 1 (maybe 6.1)

Thanks, I'll have a look

Problem was in two commits. The ones to do with sync

There was an incompatibly somewhere, or maybe it's unstable

0061 should work regardless?
[One (M7) Original Android Development] dictionary:
Tested with fresh flash stock. Boots. Flashed 009. Bootloop. Flashed 005. Boots. Flashed 0061. Boots. IC SVN80.
[One (M7) Original Android Development] poondog:
Thanks

#win

015 should be good to go :D
[One (M7) Original Android Development] Mikey:
Here are the rest of the Kernels :) https://drive.google.com/folderview?id=0B2TainPw3RB2S1BwbUVOdlNZQUU&usp=sharing

LK

SM

ST

CF
[One (M7) Original Android Development] RUUMan:
I am on 0061 battery isn't so good as 00041
[One (M7) Original Android Development] Ktan188:
Dude, you're not helping here.
[One (M7) Original Android Development] RUUMan:
Well it's a test right
[One (M7) Original Android Development] poondog:
Thanks, you higher ups need to look at letting us humble non-mods have more thanks to give out during the day :) On desktop view

seems you got highest on ST, which seems to be the most consistently good at the moment. Did you find it the smoothest too? Thanks for your help :)

was only a 'is it booting' test for the people with boot issues. It hasn't even been like 24 hours anyway :/
[One (M7) Original Android Development] dictionary:
[MENTION=4379011]poondog[/MENTION] yeah I agree. 004 battery was far superior, especially with the device off. Very minimal battery drain. Please revert to 004 immediately so I can haz extreme off mode battery life again.

In all seriousness, 004 DID have better battery, but I know that's not the nature of these new tests. I'm just glad I'm getting the new ones to boot, so that's sorted. I'm sure you'll work your skills and get us another great kernel, so take your time. ;)
[One (M7) Original Android Development] poondog:
yeah I know what the issue is. My 014 is great on battery, seems 015 (which will have the changes from the tests) will be out soon. Some of the tests have better/worse battery because of the changes
[One (M7) Original Android Development] RUUMan:
Hmm 014 ,015? Are these new
[One (M7) Original Android Development] poondog:
014--> testing (no you can't have it only some people have it)

015--> release in a few days which will be 014 with the blind test stuff added in

[YOUTUBE]JYRAOR1tPVY[/YOUTUBE]

[MENTION=1102297]Sneakyghost[/MENTION]
[One (M7) Original Android Development] myrigon:
Creasing myself here! "This one must be potato?"
[One (M7) Original Android Development] poondog:
What is this?
[One (M7) Original Android Development] Mikey:
As for smoothness, i thought ST was smooth but i dont know if it was caused i didnt have any apps or nothing installed on this phone?

I am willing to see what you have in store for next :)
[One (M7) Original Android Development] poondog:
they all seem pretty smooth to me. I just switched ROMs and it still flies so this is good :)

I can tell you whats next but it will ruin the surprise
[One (M7) Original Android Development] Mikey:
I dont like surprises :P
[One (M7) Original Android Development] poondog:
Cool then I will not tell you :)
[One (M7) Original Android Development] itzsnookums:
ok, then tell me, its his fault he read the spoilers.......LOL
[One (M7) Original Android Development] Large Hadron:
Well given them all a few hours now. Restricting comments to the "candidates" listed a page or two earlier:

No stability problems with any.

Antutu:

SM, LK ~27k.

BR, ST ~26.6k

CF: 2 runs > 27k plus 1 run scoring 19k!

Battery (short test, few hours standby):

SM dropped ~1-2% in 3 hours

CF dropped 2-3% in 3.5 hours

ST dropped 3% in 3.5 hours

BR, LK dropped 3-4% in 4.5 hours

(i.e. all pretty similar. Would need repeat/longer tests to determine whether any differences are significant).

Impressions:

No real response problems with any. SM, ST and BR felt "snappy",

LK and CF marginally less so.

Subjectively I probably found SM the smoothest (have just flashed it again after

ST, to check my memory), but there's very little between any of these.
[One (M7) Original Android Development] Rad ryan:
Version 009lk test was inconclusive due to issues. I don't want to post results bc it was not very controlled, to many variables. But general impression was smooth with a few lags during game play. Battery was not as good as 009br but on par with 009cf. Testing 009st now.

So far CF smoothest, br is best battery, lk in between, testing st now.
[One (M7) Original Android Development] RUUMan:
Just my suggestion , why not make the 0041 with more governors like preservative ect,?
[One (M7) Original Android Development] Asselalf:
Wait a few days. More governors will come later. Let him test some things and then we will have the best kernel for the One

Gesendet von meinem HTC One
[One (M7) Original Android Development] Rad ryan:
[MENTION=4379011]poondog[/MENTION] I just finished 009st test. I cut it short at 12 hrs bc it was killing my battery and it's cold outside today, the rest of my test were done on hot days and I'm outside most of day. Subjectively, this was the smoothest version I tried, but at a serious cost of battery and that's just not my cup of tea. I would consider doing a 24 hr test on this bf choosing it as the best to really check battery usage. I do the same exact thing for about the same time for each test. I keep rom same, no new apps and only update essential apps. I cut test short so that's why I suggest doing a good battery test yourself if this ends up being your choice. I am on 009 SM right now and nothing has changed but the kernel and I'm getting much better battery life out of it and no lags at all. Here are 009st benches and battery:

I'm going to try to do 2 more short retest of 009cf & 009BR(my favourite so far, I think)
[One (M7) Original Android Development] poondog:
Ok so you liked SM :) thanks

Did you test SM too, I'm thinking SM or ST

I might push out one more, which is in between :D

You can always download sources yourself. Governors will come soon, I'm going in stages
[One (M7) Original Android Development] poondog:
ok basically, next release candidate is up. It contains changes that sit in between ST and SM.

Called kk009_SE

If people could test to see if its the best of both worlds that would be great :)
[One (M7) Original Android Development] myrigon:
Bench is good for me,

3d test was pretty much 39~45fps solid. Among the best I've noticed from the tests.
[One (M7) Original Android Development] poondog:
This is SE? I just compiled it this morning, on 009 and 014 (I am using 014) but for fairness in testing I uploaded 009 here :)

lets see how it goes, if its good I might upload 015 (which will be 014+ this test so basically what I am using now) tonight or tomorrow :)
[One (M7) Original Android Development] Ktan188:
SE is looking good on the first flash. Here is the antutu benchmark:
[One (M7) Original Android Development] poondog:
^^we have a record!!!
[One (M7) Original Android Development] miten_sheth:
I have a suggestion..

You should post the highest Antutu score and the max battery life got in the op.. So that people who tell they are not getting proper performance/battery.. Will come to know that it's their phone and settings..

Just a suggestion.. :)
[One (M7) Original Android Development] poondog:
Nah cause of different factors.. it's not 100% because of me so it's not really fair

I see no point in it, cause then someone might be on a different Rom and get 25k, then ask why haha

Proper performance and battery in the current kernel= better than stock :)
[One (M7) Original Android Development] FanDroid09:
Probablly not a good idea. I won't speak for [MENTION=4379011]poondog[/MENTION] but kernel is still in testing and probably gonna be changing quite a bit, would make more sense when kernel is more complete.
[One (M7) Original Android Development] poondog:
True it changes like every second day haha

Im working on f2fs and kexec for next version (after 015)
[One (M7) Original Android Development] Large Hadron:
SE working well so far. Nice & smooth. Accidentally left WiFi on during my standby test, but dropped 3% in 4 hours. Antutu averaged 27.2k.
[One (M7) Original Android Development] dictionary:
Pretty decent battery on svn80 with 0061 methinks

All default settings.
[One (M7) Original Android Development] poondog:
oops haha looks like the kangaroo saved ya ;P

Cheers

this is amazing

If all is good I will release 015 in an hour.. if you have problem on any test then SPEAK UP pls :P
[One (M7) Original Android Development] seandk:
Hi, is there anyone using this kernel with lastest ViperOne ? I have bootloops when I try this kernel ( Even after a fresh install with a full wipe before flashing Rom ).

Envoyé de mon HTC One en utilisant Tapatalk
[One (M7) Original Android Development] TRSolebum:
I'm using Kangaroo 009 with ViperOne 5.8.0 and it works very good.
[One (M7) Original Android Development] poondog:
Working here. 009 may have bootloop problems on SOME devices (maybe 5%)

015 is compiled and works :)
[One (M7) Original Android Development] poondog:
Kangaroo Kernel v015 sense 4.4.2 (tested mine on 2 different sense 6 roms)

.msm: dma: upstreamed to CAF

.kernel random gen driver updated to Linux 3.14+ (faux123)

.ext4: upstreamed to latest CAF (mrg666/CAF)

.ASoC: increase buffer sizes for low latency audio playback

.block/partitions: optimize memory allocation in check_partition()

.mm: optimized KSM

.upstreamed random32 drivers to latest CAF to work with ext4 updates

.kernel mode NEON

.Enable NEON optimized crypto routines

.2w options (s2w, dt2w, l2m etc: flar2, default s2s/dt2w bottom of screen)

.build: add build flags simplified version with -O2 optimization (used to be -Os) as per testing.

.fixed boot issues for the people who had problems

What were we testing for the past week? Build flags in makefile. The code was 100% identical except for the build flags to make the kernel. Resulted sometimes in ~2mb bigger kernel. Basically, the names were due to flags being based on particular kernels:

1. BR: Bricked kernel

2. CF: CodefireXperiment

3. FA: Stock with -Ofast

4. JO: Joey kernel

5. LK: Lean kernel

6. SM: SaberMod

7. ST: STOCK control test.. no additional flags

8. XG: AK XGenesis

What we settled with is in between SM and ST

kk015.zip - 7.46 MB

Enjoy! Thanks a lot to those who helped test these kernels :)

016 will start... now :D
[One (M7) Original Android Development] superleeds27:
I finally got round to trying AOKP ith your kernel.

Only issue ive found so far is that Titanium backup tends to hang on restoring apps :/
[One (M7) Original Android Development] ZeroInfinity:
.ASoC: increase buffer sizes for low latency playback

ehhhhhh, doesn't increasing buffer size result in HIGHER latency? :p
[One (M7) Original Android Development] poondog:
ah who cares :D I don't see why there would be an issue though

ahhhhhhhh what do you know about audio anyway

https://github.com/poondog/kangaroo-m7-mkIII/commit/c7b9fb6c02d1496f6d125db5f92f777981846780

Maybe my changelog is not clear, I mean its for low latency playback not make it lower. Mainly for scheduling improvements, as the commit suggests :D
[One (M7) Original Android Development] ZeroInfinity:
Ah I get it now :p you only increased the buffer size on low latency playback mode to stop shuttering! :p

I thought you said you lowered the audio latency by increasing the buffer size (Which made me go WTF) xD
[One (M7) Original Android Development] edgarf28:
Just flashed 015, verrrrry smooth!!! :good:

also good Antutu score on ARHD 62:
[One (M7) Original Android Development] poondog:
Yes now if anyone complains off stuttering audio I will flip

I'm working on your extra bits too I haven't forgotten btw

Yay :) hope you enjoy
[One (M7) Original Android Development] herwegan:
How many test stations do you expect until it's time for the official perfect kernel? ;) trying v15 now :)
[One (M7) Original Android Development] poondog:
How many versions you mean? Well, I seem to upload every 5th after testing. The "Official perfect kernel" does not exist imo

the closest we will get will be like v200+ with everything in it :D

I am working on schedulers next, kexec, f2fs and upstreaming slowwwwly to 3.4.86 (which was released today)

Up to 3.4.25 now cause it takes forever to manually patch :D
[One (M7) Original Android Development] FanDroid09:
0015 is running great. Nice and smooth, ran a couple antutu tests, all at or just above 28k.

Keep it up man :) :thumbup:
[One (M7) Original Android Development] poondog:
Awesome. I thought some of the changes, for battery would drag the scores a bit down haha
[One (M7) Original Android Development] FanDroid09:
Ya they did a little for me... But I was seeing a decent bit over 28k on the tests. Now it's between like 27950 and 28150. So not a big difference, still damn good. :thumbup:
[One (M7) Original Android Development] Rad ryan:
I did test SM and was going to post results this morning but slept in. SM was good. Would it have been possible to mix build flags of SM, ST, and BR? I really liked the battery life of BR :) I had no idea build flags could make such a difference! :eek: I'm hyped for upcoming versions :D I talked to dragonesdenano and he said he would make rom with f2fs. He's waiting for dev to get back with him. Doesn't it need rom support?
[One (M7) Original Android Development] Ktan188:
kk015 is working great after flashing it this morning.
[One (M7) Original Android Development] One Hype:
How do I enable logo 2 menu with kk015 on sense 4.4.2? I can't do so with trickstermod
[One (M7) Original Android Development] myrigon:
You should be able to. I have it.
[One (M7) Original Android Development] poondog:
I think its ramdisk only but maybe something else.

Mixing build flags are a bit funny sometimes, because you he some that really just don't go together. ST haD no build flags, SM was extreme so the release is in the middle

Yep now ya know what they can do :) I'll start testing memory optimizations too

You might need rom side support for this to map the menu button in the first place. I'm against swapping parts of the rom in my kernel zips, they're designed as a simple drop in replacement to stock :)
[One (M7) Original Android Development] Rad ryan:
[MENTION=4379011]poondog[/MENTION] Would you mind building a version/s for me to test with build flags from versions CF + BR and/or BR + SM and/or BR + LK and, if you could combine 3 versions, I would love to try BR + CF + SM?

I'm not sure if it would be a lot of extra work or time, I'm just thinking that if build flags can make such a difference and since you are putting so much time into this kernel (it's like your baby) to make it your Mona Lisa that rushing into next phase of development bc everyone is so anxious for your completed kernel that it would not be a bad idea for one more small/short test on this step just to make sure you have the best setup going into the next step.

I personally love how you are going about the development of this kernel. So I would like to run a few more test as I stated above. I'm on v0015 now and it's performing nicely but my battery has been better. Here are some screen shots of current battery life. Let me know if you would be willing to give this idea a try and you could continue to develop your kernel as planned why I, and any others willing, test out the build flag combos I mentioned in beginning of this post.

Edit: just read your post about mixing build flags. But I think you could make it work and I would be willing to test if your willing to build. If nothing else maybe mix BR(battery) + ST(performance) = Balance?
[One (M7) Original Android Development] poondog:
BR+SM+CF would not produce good results, because there will be too many conflicting build flags. CF and SM use quite a few build flags as well as -O3 already, so they will produce very similar results.

BR and ST (simple+nothing) would be just BR because ST has no extra flags :)

I'll do a quick BR+015 and a 015+memory opt now :)

And I'll reset it to the code in 009 for fairness
[One (M7) Original Android Development] poondog:
ok two new tests are up in my dropbox as per request:

kk009_SEBR (SE+BR flags, all of them none conflicted)

kk009_SEMEM (SE+memory optimizations which are present in SM, so could be SE+ 0.5SM)

https://www.dropbox.com/sh/y46ps2d8t0xgb36/V5owYtMOH0

Thanks
[One (M7) Original Android Development] ghostENVY:
Thx for the update :D

Updating now! Do you need anymore testers? :o
[One (M7) Original Android Development] poondog:
if you'd like to test the above :)
[One (M7) Original Android Development] txordi:
009_SEMEM have not booted for me. I've tried erasing cache, dalvik and with fastboot erase cache and no success. I had to dirty flash viperOne again.
[One (M7) Original Android Development] poondog:
Yeah because it has the same code as 009tests the bootloop fix is not there. Sorry, I don't think you can test these

015 should be fine its not a test :)
[One (M7) Original Android Development] txordi:
Okay! I'll give it a try! Thanks

---------- Post added at 01:57 PM ---------- Previous post was at 01:49 PM ----------

Okay 015 working fine. Thanks poondog, soon I'll give feedback ;) I like your kernels

---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------

26441 in antutu:

But the most important, I'm feeling perfectly smooth and fast. I'll keep on this kernel to see battery results :D
[One (M7) Original Android Development] poondog:
Thanks mate for the kindness! Benchmark scores don't matter for full releases, I just wanted to see difference between build flags :)
[One (M7) Original Android Development] poondog:
What's coming

I wonder if I can make hashtags by editing the version number in the kernel :)
[One (M7) Original Android Development] Rad ryan:
Thanks :)
[One (M7) Original Android Development] Rad ryan:
[MENTION=4379011]poondog[/MENTION] I'm currently sloowwwlllyyy TRYING to learn kernel development. So I decided to do some searching on build flags and found it tough, but I did find this ( http://www.linaro.org/blog/android...ro-android-2011-10-and-future-optimizations/ and didn't know if it would be helpful or if you already knew about all of that. I'm also in the process of reading these 3 books ( https://www.dropbox.com/s/cf2zk4n1yd6b750/UnderStandingTheLinuxKernel3rdEdition.pdf & https://www.dropbox.com/s/utp0wgb0zdr3egj/linux_device_drivers_third_edition.pdf & https://www.dropbox.com/s/kbrcmnxnhv0496m/Linux Kernel Development, 3rd Edition.pdf ). Are these a good place to start?

PS you are welcome to download them for yourself if you want or anyone interested, that's why I posted links instead of just typing names.
[One (M7) Original Android Development] txordi:
I always wanted to start learning this things. This books are not in my language but you've motivated me to start learning! :D
[One (M7) Original Android Development] dena994:
I flashed aokp v10 but it's writhe that is v08..normal?
[One (M7) Original Android Development] Rad ryan:
I got 009SEBR to boot but I then tried SEMEM and it will not boot at all and in addition I'm having trouble getting any version to boot. I know it's not very accurate if you were to add in your fix for booting issues to these versions but I can't test them at all at the moment.Do you think you could add in the fix?
[One (M7) Original Android Development] poondog:
I never read any books? Lol

Thanks mate for these links maybe I'll learn something

Don't know don't remember :D
[One (M7) Original Android Development] poondog:
These don't have the booting fix in 015

Reflash the rom and then the kernel :)
[One (M7) Original Android Development] Rad ryan:
I didn't know where to start bc I know very little about Linux, hence why I got the books :)

I gotta say that you did a good job of learning without books judging by your kernels :)

Yeah, I know they don't have boot fix in them, I just haven't been able to get them to boot, I think it may be the rom bc one of them booted on a different rom. I did try what you said many times and it's still a no go. I even tried doing a fresh install of rom then kernel and it still didn't work. I'm going to try another clean slate install and then flash kernel again.
[One (M7) Original Android Development] poondog:
Haha just don't judge me now that you know stuff

Yeah for some reason my device started being plagued by the non booting issue that's how I fixed it lels
[One (M7) Original Android Development] Rad ryan:
The Dreaded Non-booting Plague :eek: still haunts me at this very moment. . . ooooooooo :eek: haha :D

Gonna try SEBR on Nocturnal LE 7.1.1 tomorrow morning
[One (M7) Original Android Development] poondog:
But I know what it is so why are you haunted, don't be scared I'll protect you from it
[One (M7) Original Android Development] poondog:
Just wanted to shout out to these people..

[MENTION=4388232]ZeroInfinity[/MENTION] [MENTION=2846080]Large Hadron[/MENTION] [MENTION=4412307]neniick[/MENTION] [MENTION=5288647]myrigon[/MENTION]

[MENTION=3540818]Rad ryan[/MENTION] [MENTION=4139905]FanDroid09[/MENTION] [MENTION=5264389]drsamratroy[/MENTION] [MENTION=641753]Mikey[/MENTION] [MENTION=2190489]dictionary[/MENTION]

who helped with the tests last week, providing solid results. Didn't have time to check back to get the names until now. If I have missed anyone lemme know. Couldn't have done it without ya

020 is in testing now :)

And to [MENTION=4647967]Guich[/MENTION] [MENTION=670396]smw6180[/MENTION] [MENTION=2133457]janarp[/MENTION] [MENTION=4380624]Raymond Ebertt[/MENTION] [MENTION=4637027]Black-FR[/MENTION] [MENTION=5628924]Skulldiver[/MENTION] for their support :)

Thank you all for your time and support, it helps me and keeps the development of this kernel going. For reasons some of you know I have been considering stopping public releases.. thanks for keeping it going :)
[One (M7) Original Android Development] s33d1ing:
Now that Sense 6 is out, I've been using it and I'm back on your kernel. Its been running great, especially v015! :good:

I am having one issue though, I mostly charge my phone on a cable that is only power and not data because it's the longest one I have, but Sense doesn't like it and puts it into slow charge mode. Do you think we'll see fast charge anywhere in the future?
[One (M7) Original Android Development] poondog:
Welcome back!

Fast charge.. yes after the next release. I'm working on a few things for next

Don't really want to be testing too many things at once :) thanks