yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] Pinktank:
whoah, is that v2 on kitkat? which rom?

---------- Post added at 02:04 PM ---------- Previous post was at 01:59 PM ----------

CM12 is not stable yet, have you all migrated already? It's like birds and global warming :silly:

Well if you do, I'll test it for you
[Moto G Original Android Development] twist3d0n3:
v3 beta on xperience rom (cm12 latest version).
[Moto G Original Android Development] kevin.26:
How have you configured Trickster Mod or similars?
[Moto G Original Android Development] twist3d0n3:
fauxclock:

interactive

fiops

readahead 2048

zram on (60% 85% 20% 5%)

intelli-ksm on
[Moto G Original Android Development] efeenes7474:
Battery drains much faster than expected

My device is running Anerik's CM12 03/12 build with Donkey Kang Kernel Beta and my battery's draining faster than I expected. Is this a known bug or am I doing something wrong?
[Moto G Original Android Development] fermasia:
Which version did you flash? Tweaked any settings? And most important... how fast do you expect battery to drain :p?
[Moto G Original Android Development] rogeriorp:
I have also noticed some faster drain than expected on N5X CM12 build with latest v3 beta. I might need a couple more charges to say for sure, but I love it for the performance it delivers and the riddance of the CPU frequency bug that most CM12 roms are with, maxing it's usage out all the time.

If there is something I can provide to further improve the future releases, let me know!
[Moto G Original Android Development] efeenes7474:
I flashed Donkey Kang Kernel v3 beta, the latest version. I didn't tweak any settings, that could be the reason why my battery life is like this. I'd be happy if you sent me a PM for the special tweaks (Still kinda new at this kernel tweaking stuff)

I didn't really expect battery life to be good. I mean, it's not bad, but it isn't good either. Could be better, and I'm sure you're going to make the battery life better in the next builds.

Overall, the kernel is great and made the first sim slot on my XT1033 to work again without problems.

Keep up the good work and thank you for the great support.
[Moto G Original Android Development] fermasia:
Ok guys, but I still can't guess all by myself what your expectations are. If we don't judge things by some specific parameter, it becomes a matter of personal appreciation.

To be honest, I'm not a battery freak at all. The goal is to optimize, but performance should not be compromised. Cause if not, I should grab the old siemens a56 I have in my bottom drawer... That lil guy could last days for each charge (lol).

I've read users that expected 7 hours SOT per charge... Well, I'd also like Jenniffer Lawrence to be my birthday gift, but reality sucks sometimes, doesn't it?
[Moto G Original Android Development] rogeriorp:
Indeed! Haha

Let me go further, well in the two first charges I lost about 35-50 minutes of screen time while manteining the same standby time. I usually reach 3 and a half to 4 hours in about 3 days (wifi only), yesterday went to charge with 2h50 minutes screentime, while nothing changed. My configs were mostly the way it came, then I saw your post yesterday and tweaked it on trickster, will report back later but tried a 10% run and got 37 minutes screentime, which is quite low for standards I was used to - obviously, not everything is kernel related and there is the factor that my rom still isn't on 5.0.1 and CM12 not yet fully optimized. It is unfair of me to say that your kernel is the culprit of it, I am just reporting!

Thank you!
[Moto G Original Android Development] fermasia:
Not arguiing at all, but I'm still not clear enough. And as you are reporting, we might mislead other forum readers. Not that I worry about them using or not my kernel, but we should keep expectations in it's place for other projects too. When you say you lost X minutes, are you comparing to CM12 stock kernel or to something else? And you get 3.5/4 hours SOT during 3 days running???

I'm very interested cause at the moment I'm comparing msm_hotplug, mpdecision and intelliplug performance on top of a same kernel base and equivalent usage (but it's taking time cause I don't have the resources or dedication needed to move forward rapidly).
[Moto G Original Android Development] Pinktank:
mpdecision is super crap with custom roms, losing 2% on standby per hour. I had much better lock with intelliplug, and have not tried msm_hotplug. I'll test v3 if you ever get to rebase it on cm11, or let me know if you want something tested with v2, just installing it from clean to test properly, I was having super lag in slim with it, somebody suggested another governor.
[Moto G Original Android Development] rogeriorp:
Yeah, it is compared to N5X's CM12 first build unmoded performance I had. I am back to the stock firmware now, so can't provide further info of how it went.

I might jump on your kernel in the future, I appreciate when devs try and gather information even from us not-so-much into development and details. Shows some good will! Good luck with the project, will keep an eye on it!
[Moto G Original Android Development] fermasia:
I'm beggining to think I 'might' be making a mistake exactly by doing that. Nevermind, good luck to you too
[Moto G Original Android Development] Flashhhh:
[MENTION=5190317]fermasia[/MENTION] the battery backup is really better than the msm hotlpug on the aero hotplug!!

Sent from my Moto G
[Moto G Original Android Development] Ganapatya:
Nice kernel.

Enviado desde mi Moto G usando Tapatalk 2
[Moto G Original Android Development] fermasia:
For starters, I'm working on cm11 V3 version... so hang on. ;) But I disagree about mpdecision. It's actually a good driver, one could solve the idle drain with any better suspend solution, but as it's closed source there's little one can do to develop around it. Yet, it's argueable, and I know that.
[Moto G Original Android Development] Pinktank:
I was actually going on someone elses suggestion on the mpdecision, and indeed once I replaced it with intelliplug, my deep sleep drain went from 2 to 0%, though admittedly, this is a limited sample, and it could be slim/cm roms not playing nice with mpdecision?
[Moto G Original Android Development] adinkwok:
There are other apps such as Trickster Mod that is very similar to faux clock.

You can find it on the Play Store here.
[Moto G Original Android Development] ncmz:
Still couldn't disable it. It turns on just after the toast "Changes has been successfully applied". Like a bug.
[Moto G Original Android Development] dimlay:
does the latest kernel compatible with the latest mokee 4.4.4? or should i flash the 1.1 version?
[Moto G Original Android Development] fermasia:
Will be taking care of that in next V3 release (coming soon). :good:
[Moto G Original Android Development] fermasia:
I haven't tested on Mokee KitKat, you can make a nandroid backup and test. If KitKat, you should try last V2 for now. A kitkat V3 is coming asap.
[Moto G Original Android Development] dimlay:
just test v3 to latest mokee 4.4.4 and cyanogen.overkill. phone just stay in booting

test the v1.1 on the same rom, systemui keep fc.

gonna try v2 now and yes please im waiting for V3 :D

thank you!
[Moto G Original Android Development] fermasia:
V3 on a kitkat rom will surely fail, that's why I suggested trying V2... Stay tuned, once it's tested and if I don't run into serious bugs, Kitkat-V3 will be coming soon.
[Moto G Original Android Development] dimlay:
haha i flashed it before read ur answer mate :p

oh and i just test the V2 too in latest Mokee 4.4.4, it same like v1.1 when the phone finish booting it keeps systemui FC. i do wipe cache and art/dalvik cache before flash.
[Moto G Original Android Development] fermasia:
Hi everybody.

I'm needing someone to test a new V3 KitKat version. Is anyone available to try it out and report back? If so, please PM me.

Thanks :good:

EDIT: We've begun testing it, so no more volunteers are needed. Thanks for answering the call, and if everything goes right, we'll have the KitKat version up pretty soon.
[Moto G Original Android Development] pattyboi:):
[MENTION=5190317]fermasia[/MENTION] bro just wanted to say this is the best kernel ive had on my device since i bought it,thank you for your work man :)
[Moto G Original Android Development] fermasia:
Version 3.1 - Released (both Cm11 and Cm12 support)

Versions 3.1 have been deleted due to some annoying bug that has come up. For the convenience of all users I'm putting links down and ask you to stay tuned for a next release that would eliminate problems and bring you what this project is supposed to, a solid experience. Sorry for the inconveniences and thanks for your support.
[Moto G Original Android Development] xxAirwickxx:
Awesome thanks !!
[Moto G Original Android Development] Membrillo007:
I flashed V3.1 for Lollipop,got 4 reboots in just 30 minutes...

Tap-a-talked from Moto G running CM12 Candy5 Rom / Donkeykang Kernel
[Moto G Original Android Development] ssalamon:
installed v3.1 on SlimKAT 8.18 (latest weekly), so far so good. tomorrow i'll report about battery life :)

btw: REALLY DAMN SMOOTH

300~1190mhz interactive

sio 256mb

fsync disabled
[Moto G Original Android Development] fermasia:
Must be the kernel don't liking Candy rom (or the other way round). I've had 0 reboots in 4 days with Anerik's build that's stock Cm12, Please provide Kmesg/Logcat if you want me to try to figure out anything.

Edit: were you using previous V3 with the same rom and build?
[Moto G Original Android Development] Flashhhh:
[MENTION=5190317]fermasia[/MENTION] i am getting severe battery drain on v3.1 with the validus rom!!

I don't know if it's the rom or kernel!!

Sent from my Moto G
[Moto G Original Android Development] deamonoid:
Okay one question [MENTION=5190317]fermasia[/MENTION]

Soak test is released for stock Brazilian Lollipop, cant we use that stock lollipop ROM kernel and improve this kernel. Just a suggestion. I know its based on CM but still we can take improvement from that stock lollipop kernel. Its just a thought
[Moto G Original Android Development] OldYellowBricks:
YYAAAASSSSSSS THE KK KERNAL HAS BEEN UPDATED THANKS [MENTION=5190317]fermasia[/MENTION]

---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------

He needs the sources. Not just the kernel
[Moto G Original Android Development] andogeek10:
I guess even I'm a silent downloader, this being my first post in this thread. The main reason is that I didn't have anything significant to contribute to the thread and that I have faced absolutely zero bugs. This would maybe be the reason most people don't post. Anyways, what you have got here is an amazing kernel which delivers on both the promises of good battery life and performance.

Thanks a lot for this kernel and hats off to you.
[Moto G Original Android Development] deamonoid:
I flashed anerik latest build and v3.1 donkey kang kernel. It was a clean flash. After flashing, my phone was randomly rebooting many times. But when I changed the governor and scheduler from ondemand to interactive and flops to cfq the random reboot stopped. Can anyone confirm?

This time I was not near my laptop but Next time I will take logcat and post.

Hope this helps
[Moto G Original Android Development] twist3d0n3:
running this on xperience rom atm with smartassfalcon, fiops, 2048 readahead. flawless so far, will report battery drain in the evening if it's useful to anyone.
[Moto G Original Android Development] Ganapatya:
i am having random rebooting also (ondemands, fiops). Maybe ondemands is the cause.

Enviado desde mi Moto G usando Tapatalk 2
[Moto G Original Android Development] Snowers96:
Hi! Are you planning to implement s2w or double touch to wake in your kernel? I really apreciate this!
[Moto G Original Android Development] OldYellowBricks:
OP has said that he will not implement screen gestures until a truly stable solution is found for it.
[Moto G Original Android Development] hekomat:
This is a really cool kernel:) Running MoKer OS with it and no problems so far. Running great!:)
[Moto G Original Android Development] fermasia:
Can you define "severe"? Are you using CM12 or CM11 kernel? In any case, can you switch to MpDecision and tell me if the drain is the same? Thanks.
[Moto G Original Android Development] fermasia:
Which kernel version and rom are you using?
[Moto G Original Android Development] fermasia:
No, not for now. Implementations I've seen so far don't give good results in deepsleep and the battery cost is not worth it.
[Moto G Original Android Development] fermasia:
A kmesg and logcat would be useful, still, I think I know what the problem is. I might have to make a patched version in a few days, but this week is hell complicated to work on this the way I'd want to.
[Moto G Original Android Development] fermasia:
No, until the source is released there's little to be done with stock. Some of the propietary blobs could have been useful, but on the kernel side, with all the phone features working fine (wifi/radio/camera/etc) there's little or none profit to be taken from the soak test. Yet, I'm not an engineer... maybe some dev around here finds something useful to be done with that.
[Moto G Original Android Development] Snowers96:
Thanks for your answer!
[Moto G Original Android Development] deamonoid:
Ok, next time I will post with logcat and kmesg for sure.

Yeah, I got it we need source of the stock lollipop kernel. [MENTION=4403780]TeamMex[/MENTION] asked for stock lollipop boot.img maybe he/she knows something. I mean collaboration. Just want to let you know to speed up our development. [emoji4]
[Moto G Original Android Development] syrkles:
I am on kk validus and I have no excessive battery drain. I enabled power suspend and battery backup is amazing
[Moto G Original Android Development] Flashhhh:
I was on validus lollipop and i can confirm that it was rom that was draining the battery!!

Now i am on anerik's build with v3.1 and its working quite good!!

Validus is a great rom and no offense!!

Sent from my Moto G
[Moto G Original Android Development] Ganapatya:
Donkey 3.1 and CM12 anerik. After change governor not more reboots for the moment.

Enviado desde mi Moto G usando Tapatalk 2
[Moto G Original Android Development] fermasia:
I'm 99% positive that Ondemand CpuGov is causing the random reboots. So please stay off that gov until I find a propper fix.

I'd also appreciate kmesg / logcats about those reboots, and if anybody has them with other governors. :good:
[Moto G Original Android Development] hekomat:
Using smartassfalcon nad no problema whatsoever
[Moto G Original Android Development] Ganapatya:
The frecuency tables has changed in last version. No more 192.000? Strange.

Edit. Kernel corrupted by bad flashing.

Enviado desde mi Moto G usando Tapatalk 2
[Moto G Original Android Development] andogeek10:
No, it's still there.
[Moto G Original Android Development] Ganapatya:
Edit. Don't flash it correctly.

Enviado desde mi Moto G usando Tapatalk 2
[Moto G Original Android Development] Cheddart:
May I flash it into stock 5.0?
[Moto G Original Android Development] SentinelGerrant:
Read the OP.

No, this is only for AOSP KitKat/Lollipop only.
[Moto G Original Android Development] jman1234:
Howcome no fast charge?
[Moto G Original Android Development] fermasia:
If you meant: "hey, it would be nice if you added fascharge support, can you try to include it in your next version?" the answer would be: "I'll try to, I believe it's safer for battery purposes to keep charging at it's regular pace, but I might add it as an option".

If you meant "How come no fast charge?" the answer is: "if it's so obvious why don't you download my source, find the right commits, add it yourself and recompile.

Cheers. :good:
[Moto G Original Android Development] attack11:
Hi [MENTION=5190317]fermasia[/MENTION] Yesterday i have a reboot with your latest kernel + anerik´s build , The errors i could see in last_kmsg are:

[ 3663.989718,0] Smartass: frequency change failed: 1094400 to 1094000 => 1094400

[ 3664.904001,0] init: Warning! Service mpdecision needs a SELinux domain defined; please fix!

Ive attached the file,it was the only thing i save sorry, hope it helps, I havent other reboots more than that

Ive also notice that there are always 2 cores working, in stock when i dont do anything it reduces to 1 dont know if its normal

Thanks For your Work :good:
[Moto G Original Android Development] jman1234:
Please don't act like a smart ass because I didn't sugarcoat my post with thank yous and smiley faces. I asked a simple question and all you had to do was keep your reply in line with the first paragraph.

Cheers :good:
[Moto G Original Android Development] twist3d0n3:
no, you asked it like a spoilt, demanding child.

show some respect or do one.
[Moto G Original Android Development] ncmz:
That form of question you made, sounds like you are DEMANDING an explanation to the dev about why his work doesn't have a feature. Not a proper way to ask to someone about his work. It's my opinion, though.

Cheers.
[Moto G Original Android Development] fermasia:
Thanks for the log. The issue you'll actually find it with the tag 'kernel panic', but the info is quite useful. :good:
[Moto G Original Android Development] xxAirwickxx:
Keep it up [MENTION=5190317]fermasia[/MENTION] ??
[Moto G Original Android Development] pattyboi:):
[MENTION=5190317]fermasia[/MENTION] , hey bro,for the next release can u look into bus overclock/ram overclock? of course if your comfortable with that :)
[Moto G Original Android Development] ncmz:
Random reboot

Here is my first logcat! TA-DA *angelical voices on the background*

To be honest, I don't even know if I took it right. Just when the phone was rebooting, I connected it to my PC while booting and just when PC recognized it, I ran "adb shell logcat > log.txt". Hope it helps and if it's wrong, I will appreciatte very much someone could give me a more efficient way to take one.

Device info.

ROM: anerik's latest build CM12.

Kernel: interactive, 512 read ahead, fiops I/O, multicore energy saver on 2, min GPU freq 320 and everything else stock configuration.

Edit: Btw, it rebooted just after I sent a reply to an XDA thread.

Edit2: Another random reboot and another logcat. I was on facebook app btw. Hope it helps.
[Moto G Original Android Development] twist3d0n3:
Why? It doesn't do anything!
[Moto G Original Android Development] justanicename:
I tried V3.1 for CM11. There is still the problem with makings backup using TiB. I would love to use this kernel ;) [MENTION=5190317]fermasia[/MENTION], do you think this will be fixed in the next version? Did you found out the problem with the logcat that i posted here?
[Moto G Original Android Development] kijp15:
I believe it says Donkey Kang Kernel v3.1 is available for CM11 & as well as AOSP KitKat. I can't seem to find the AOSP version.

Can someone point me to it? I checked the links in the OP but I can't seem to find it

Thanks
[Moto G Original Android Development] pattyboi:):
Can you actually prove that? && because higher bus/ram speed can = higher device memory bandwidth,which in turn equals out for better performance.
[Moto G Original Android Development] twist3d0n3:
You won't notice anything. It's a placebo...
[Moto G Original Android Development] pattyboi:):
Again,can you explicitly prove it does absolutely nothing? Have you done memcpy/ rambench tests with/without such modifications? Bandwidth testing? Because from my past expierences,the more bandwidth the better,and if higher ram/bus speeds allow for better bandwidth,why not take advantage of that?
[Moto G Original Android Development] twist3d0n3:
No because i've read what devs have said about it. You'll get a few more points in some benchmarks, that means **** all in the real world.

From usage, I can safely say I see no real advantage, aside from gpu overclock (i use force gpu rendering which gives a slight boost to how smooth usage feels at the small cost of battery drain being slightly higher)
[Moto G Original Android Development] fermasia:
Thanks for the info, I really, really appreciate. Are you using 3.1?
[Moto G Original Android Development] pattyboi:):
(Just so you know,don't take any of that as me being a smartass,they were legit questions) && then disregard my request :p
[Moto G Original Android Development] fermasia:
It's arguable. I can't prove you wrong, but even when it could boost benchmarks I'm not so sure the overall performance would be improved enough to compensate. After all it means using a component in a way it wasn't meant to, and I can't be sure what it means in terms of battery pays off the benefits. But it's an opinion, I'm not an engineer. What keeps me off it for now, is that it's not a toggleable option if I pick the commits to OC ram.
[Moto G Original Android Development] fermasia:
Actually, there are no Aosp roms around here that are not CM based. Even the guys that got to port OmniRom had to use CM kernel.

To honour the truth there had been some intents... but even dhacker dropped the codeaurora vanilla version back at the begginings of kitkat. And if he couldn't sort that out... or chose not to, there are very few devs thata could prove him wrong.

To sum up, CM version is good for any rom around here (regardless any compatibility issue you might find, meaning some rom could fail with my kernel, for now, I know Mokee is not working).
[Moto G Original Android Development] ncmz:
Yes, I am on 3.1 and I suffered another random reboot during this morning but didn't realise until now so I don't know how to take a logcat from that.
[Moto G Original Android Development] syrkles:
Titanium backup works fine with this kernel u just have to flash the supersu 2.37 update

I use titanium on a daily with mass effect infiltrator and works fine
[Moto G Original Android Development] fermasia:
Guys, I've come to the conclussion that I've rushed things and that resulted in a messy last release (hate reading about the random reboots in the last build). So I think the best solution to make things better for the future is to slow down things and be more solid. That's why I recommend going back to 3.0 for now, which was solid enough, and I'll bring 3.1 links off the download post to avoid further annoyances.

On the other hand, and as i try to learn from mistakes, I believe that for future releases I'll have to more testing before making releases, so I invite those who might be interested to join a small beta community I've set up in Google+ so I can make beta releases there and get propper feedback before releasing.

Those interested should:

- Know how to make and send logacts, kmesgs, etc. and them to pastebin if possible

- Be willing to keep the test builds in their phones for some days to evaluate propperly after a few battery cycles

- Just have a positive attitude to collaborate with info, do compatibility tests with different roms, etc.

- Have at least an intermediate knowledge about how to flash, configure, and tweak a kernel

Of course, I have no means to retribute this work, but to share with you openly my work. Whoever is interested can send me a PM and I'll let you know how to proceed further. Please don't be mad if I turn down somebody, the idea is to keep the community at a reasonable amount of people so we can work... a huge flush of feedback would just complicate things. Of course... I also consider the possibility that very few or none of you might be interested... who know. In any case, I thank you for your help.

Cheers. :good:
[Moto G Original Android Development] konikpk:
boot fail

I install on last cyanogen nigtly and after half hour stil booting ... fail
[Moto G Original Android Development] justanicename:
Ok, i was just hoping I could use the built-in supersu from Carbon Rom and that the dev could fix this problem. The less application on my phone the better ;) I like a lean and mean machine.

If in the next build this problem is still not fixed than I would try the workaround by installing supersu 2.37
[Moto G Original Android Development] fermasia:
What version? If you said nightly, must be KitKat. Hace you flashed the Cm12 versión by mistake?