yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] methuselah:
[MENTION=5190317]fermasia[/MENTION]

As know you already took a vacation from development, I have a suggestion for you in case when you come back. I don't know whether this is already suggested or this is already came into your mind , may be you are going to implement it. Anyhow coming on main topic. I am using your kitkat latest kernel with "cr droid 24-12-014 built" kernel is working fine I don't know about the hotspot. Well when I use faux kernel on official Rom , the next core come online when one core reach a limit . I mean when it gains maximum frequency then gently the next core start working. This is what I noticed. But while I used your kernel cores come online very fast. I dont know whether this is what i am looking or what's going on inside the coding. But I think something could be tuned with this thing if I am right....
[Moto G Original Android Development] fermasia:
Core handling is different depending on what hotplug driver you are using. Faux's intelliplug goes core by core, some other prefer to keep at least two online trying to balance de battery cost of waking a new core. Each implementation is built around a different logic and one might tweak it a bit, yet won't change it's logic completely. Otherwise it would mean developing a whole new hotplug driver, what's actually quite difficult to do (even those naming hotplug drivers after themselves, are usually just modding a previous one).

For now I'm sticking to Aero -which is also a modification of a previous implementation, and blah blah- (trying to tweak it a bit more) and Intelliplug alltogether, i think it's the safest and giving users the chance to pick whatever they like better.
[Moto G Original Android Development] methuselah:
Well nicely explained... Well I just noticed this..and seriously this allow to give a huge effect on battery life....
[Moto G Original Android Development] fermasia:
3.6 Test

If someone's up to try a new test version, here's the link: https://www.androidfilehost.com/?fid=95864024717070323

Interactive should be fixed, AeroHotplug and IntelliMM tunables are re-tweaked, and some battery saving patches (that might make things unstable, that's why it's a test version) have been applied.

If anyone tries it, I'd appreciate the feedback.
[Moto G Original Android Development] Dr. Brawler:
Ill test. I dont have experience on producing logcat/kmsg though. Any noob friendly apps or guides you might recommend? \=
[Moto G Original Android Development] attack11:
Tried the test kernel wiping cache and dalvik, get stuck on motorola logo, reflashing v 3.5 make it boot again, :eek:

Ill try a clean flash when i have time, Thanks for keep working in this great kernel!
[Moto G Original Android Development] Dr. Brawler:
Its booting for me. Im using TWRP 2.8.2 from http://xdaforums.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

I mounted my system. Then advance wipe "dalvik cache" and "cache." Then flashed kernel. Im on Broken OS rom if that matters \=
[Moto G Original Android Development] xxAirwickxx:
So far so good. Using a few hrs & no issues. Don't use for mobile data just WiFi. ?? Thanks
[Moto G Original Android Development] fermasia:
Try AndyLog from the store, it's as simple as it gets :good:
[Moto G Original Android Development] Dr. Brawler:
Thanx boss
[Moto G Original Android Development] fermasia:
Strange, it's booted fine for me both in Anerik's CM and SlimLP. I'd have expected other problems, but not having trouble to boot.
[Moto G Original Android Development] Rocketval:
Flashed 3,5 version. About 8:40 hours in deep sleep with 2tap2wake activated and just 5% of battery drained. Really good work! :good:
[Moto G Original Android Development] fermasia:
Fellows, may I get some more feedback about the test version?

I'm concerned about stability, then we can talk about performance, etc... but I'd like to know if anybody experienced reboots/freezes or any problem at all, and also if there were any compatibility issues with roms.

Thanks.
[Moto G Original Android Development] Flashhhh:
[MENTION=5190317]fermasia[/MENTION] I have been getting lockscreen freeze issues!!

I know it's just bcoz of dt2w feature!!

So u might wanna think on dt2w feature again!!
[Moto G Original Android Development] fermasia:
Thanks for the feedback. Was this happening too in v3.5?
[Moto G Original Android Development] Flashhhh:
[MENTION=5190317]fermasia[/MENTION] Yup!!
[Moto G Original Android Development] fermasia:
Regretably... this is the most stable dt2w implementation I've found. Yet I'll have a look.

Anyone else? C'mon guys, I've peeked 20 downloads of the test version, there should be more than 2 guys giving feedback...!!
[Moto G Original Android Development] xxAirwickxx:
Still testing lol. Booted on Candyrom, Broken OS & TeamUB ROM. Running on Broken ROM right now & will b my test ROM.

Using Fiops 1024 with Smartassfalcon & On demand GPU. So far OK ?

---------- Post added at 10:27 AM ---------- Previous post was at 10:24 AM ----------

Loading XDA app pages seems to take a bit longer to load now. Use only wifi
[Moto G Original Android Development] fermasia:
Big thanks for taking so much trouble. Good to hear it's booting fine on all those roms.

I'll probably release it later today, if I don't get any critical feedback before that.
[Moto G Original Android Development] xxAirwickxx:
No problem. Ya only problem is WiFi seems to b slow. I only use WiFi. Tried other governors so far. Cannot enable Mp decision either but can intelliplug

---------- Post added at 11:35 AM ---------- Previous post was at 10:58 AM ----------

Row & interactive seems OK with WiFi.
[Moto G Original Android Development] fermasia:
You got Intelliplug and AeroHotplug (if you disable them all in Trickster or in Userspace if using Faux's app). MpDecision should be there too, perhaps you'd need to reflash to get it. :good:

Thanks for reporting, dude.
[Moto G Original Android Development] sajty:
No freezes or slowdowns for me so far. Using test version.
[Moto G Original Android Development] fermasia:
Version 3.6 - Release

Guys, here it comes V3.6.... probably a final version.

I'll be soon off Moto G developement, simply cause I'm switching my device for a new one, and I find it complicated to dev for a phone I won't own. Yet I might still try to do some fixes if needed, but besides that, this should be the last release. It's become quite solid in my opinion (considering it's based on still unofficial CM12 sources) with features and core options (two strong and tested hotplug drivers) beyond what I had in mind initially. I hope this one can last for some time until something better comes out (there are really great devs in this community, much better ones that I could ever be!). For sure, anyone can take whatever they like from my source, or even, if someone owning a G is interested, continue developing from my source (I could help, I guess).

But it's been a really fun ride. Even when I've sometimes got a lil frustrated, the balance is very positive. So I thank all of you guys that have been riding with me during these weeks. We'll probably be seeing each other somewhere else in this big Xda country.

Well, now to what's really important. This release fixes Interactive Gov and adds some tweaking to AeroHotplug, IntelliMM governor and adds some battery saving patches. Plus being built with Sabermod 4.8.4 (I've dropped 03 flags cause even when they boost performance, that's not required right now and makes battery eating a big problem). And I'll be still around to get your feedback, answer questions, and so on (I'm not moving to the north pole, lol).

Have fun and enjoy guys, and make sure your 2015 really rocks :good::good::good:

P.D. Right, link's on the second post as usual!!
[Moto G Original Android Development] kijp15:
:( We'll miss YOU & your HARD WORK ferm. Thanks for building great kernels for us Moto G users. Later boss.
[Moto G Original Android Development] xxAirwickxx:
Thank you, good luck & hopefully i helped lol
[Moto G Original Android Development] ncmz:
[MENTION=5190317]fermasia[/MENTION] thanks again for your work.

This is my last logcat (I guess). I took it a bit after second reboot because I didn't have Andy Log app on my phone so I installed it after reboot and took the logcar, hope it helps. Had 2 random reboot in about 2 hours after I flashed the kernel zip. I'm on crDroid 5.0.2, latest build.
[Moto G Original Android Development] twist3d0n3:
Thanks fermasia, you're going to be missed!
[Moto G Original Android Development] fermasia:
Uhm... let's wait a bit and see if this is replicated in other roms. If so, I have to revert those power saving patches. I just got cocky thinking random reboots were on cm12 side, and those patches do help squeezing some important juice... but if they keep things too unstable, they'll have to go.

Please guys, keep reporting, so I know wether to revert those changes or not. Thanks!!
[Moto G Original Android Development] ldiomedi:
Hi, Fer. I'm using xperience rom. 7 hours uptime. No random reboot, freeze or any trouble. Everything is smooth and fast. May be a little hard freeing memory. Most of the time the app I left for one minute gets killed. And the dt2w it's the best implemented till now on LL, but sometime when I took the phone from the pocket, it's not responding to the touch. Intelliplug and intelliactive governor. Much better release than 3.5. We'll miss our Argentinian dev.. Thanks for what you do here..

Enviado desde mi Moto G 5.0
[Moto G Original Android Development] methuselah:
Another great dev about to leave. Sad to see you leaving.....thanks for your greatest support....
[Moto G Original Android Development] Dr. Brawler:
Everything solid on 3.6 + Broken OS
[Moto G Original Android Development] fermasia:
Thanks for reporting. Memory issues are part of how Cm12 is handling low-memory-killing... and for now there's no propper solution for that. I've even tweaked the tunable trying to make it less agressive, but it seems to be more complicated than that. Eventually, the Cm team will find a solution for that (I hope).

About dt2w... yup, the one you described is the worst problem. Doesn't happen every time, but if the phone goes into propper deepsleep, that might happen. For the sake of testing, try setting a higher screen-off frequency, or try with aero and power-suspend off.
[Moto G Original Android Development] ncmz:
Another random reboot while using Facebook app. Not using any weird app or something. http://pastebin.com/t4pGg62V

And I noticed that touch issue Idiomedi said, but also with 3.5 version. Had to reboot every time to get touch working again but I was not using dt2w. Weird thing is that it only happened when I had the phone in my pocket.

PS: still on crDroid.
[Moto G Original Android Development] Rumpel78:
Also got two random reboots, but never had any touchscreen issues. Anyway, great Kernel!
[Moto G Original Android Development] methuselah:
[MENTION=5190317]fermasia[/MENTION] will there be addition of new features in kitkat version ?? Just to know...you now work mostly on lollipop version. ... Still people out here use kitkat..
[Moto G Original Android Development] sajty:
Still no reboots for me.
[Moto G Original Android Development] fermasia:
I tried a rebase some days ago and it was unsuccessful. I will try again in a couple of days, and in case I'm successful, I'll surely let you know. :good:
[Moto G Original Android Development] fermasia:
Curious about the reboots... some reporting none at all, other's pulling logcats cpu crashes... I might end it with a salomonic solution, making a second 3.6 version without those battery patches. About dt2w... I can't do much, but pull it completely off as some user reported screen trouble even when dt2w was disabled.
[Moto G Original Android Development] attack11:
Ive been using the latest release with latest cm 12 anerik's build and i doesnt experience any reboot , its super stable !
[Moto G Original Android Development] methuselah:
I will keep on checking op.... Thanks bro
[Moto G Original Android Development] ncmz:
Here I am again, with a new log! Hahaha this time I'm on 28th december CM12 build from anerik. Again, using facebook app.

Hope this helps in some way. Cheers.
[Moto G Original Android Development] Edgarngg:
This last release is just perfect, no random reboot of any kind for me, dt2w is one of the main reasons I'm using this kernel. Please don't remove it :D speed and memory management are amazing.
[Moto G Original Android Development] argo7:
Camera doesnt work for me. Lastest versión of kernel and Candy rom
[Moto G Original Android Development] robt77:
What Camera you using, Google Camera should work fine, AOSP camera is a bit temperamental on all lollipop builds but google camera should work fine

[MENTION=5190317]fermasia[/MENTION] latest build is solid, have had no issues with dt2w or anything
[Moto G Original Android Development] PeterImmel:
Camera doesn't work for me, too. I'm on latest crDroid.

Any camera I tried. I press on taking Photo and the current picture stay(and is not taken).

(back on xPerience 22)
[Moto G Original Android Development] ncmz:
Happened the same to me on crDroid but I think it's an AOSP ROM problem. Now the have marged some codes releted to camera and it works just fine in CM12 at least with Donkey Kernel.

Does Xperience 22 work fine on latest crDroid? (I'm a crDroid user too)
[Moto G Original Android Development] PeterImmel:
Ok, thanks for information.

For me XPerience has the best multitasking experience :laugh: .

But I'm not really satisfied with its battery usage. Between 3 and 4 hours SOT for me...
[Moto G Original Android Development] CsR0501:
Sorry for the noob question but what version is for SlimKK 4.4.4 (v 9.0)? [emoji53]

Enviado desde mi XT1058 mediante Tapatalk
[Moto G Original Android Development] fermasia:
For now, KK is supported up to V2. Every version has a KK or CM12/lollipop tag in the filename, you can't get mixed up :good:
[Moto G Original Android Development] fermasia:
These camera issues are not kernel related, but ROM related. Cyanogenmod hasn't modified anything in their kernel source, neither have I in my sources. You are talking about customized roms (CrDroid, for instance) with unofficial Cm12 under the hood... problems should be expected. If camera is working fine in pure cm12, then it's not kernel related.
[Moto G Original Android Development] fermasia:
I respect every personal opinion, but how do you measure a multitasking experience?
[Moto G Original Android Development] :
I know I know I should post this with logcat but as this phone is my primary device I had to quickly revert to stable state.

Issue - I was having random reboot issues with some apps, namely google plus.

Config - Everything was default. DT2W was on.

Otherwise kernel is doing the good job, battery consumption seemed good in that period.
[Moto G Original Android Development] fermasia:
Rom you are using? Kernel version? Have you clean flashed (or flashed on top of another custom kernel?) :D:D

Down through the guessing path, I'll assume you are using V3.6... if that's so, try with 3.5 an see if you still have any SODs.
[Moto G Original Android Development] :
Exodus_Vanir, v3.6 yes. Clean install (of course after Flashing rom (and rom has its own kernel, duh) then gapps then this kernel zip)

Quick testing with v3.5, no issues of reboots so far. will stay and report if anything comes up! Thanks [MENTION=5190317]fermasia[/MENTION].
[Moto G Original Android Development] PeterImmel:
On how I can change between different apps without that they were killed in backround. But all in all this is the biggest problem of lollipop on moto g, also with experience not as good as it was on kitkat...
[Moto G Original Android Development] Dr. Brawler:
had a random reboot yesterday on 3.6 final version. Here is log
[Moto G Original Android Development] fermasia:
I'll make a fixed version without the patches I suspect are boosting SODs, prolly tomorrow.
[Moto G Original Android Development] y@$h98:
double tap 2 wake not working

Sorry for the noob question but I just flashed donkey kang kernel v1.1 on paranoid android 4.6 beta 5 on my moto g xt1033 (Clean flash). It's working very well and is very smooth but dt2w or s2w is not working. I installed TricksterMOD and in the settings double tap to wake is not there at all? Is this feature available on v1.1 or not? Did I do something wrong? Thank you in advance.
[Moto G Original Android Development] fermasia:
No, dt2w was introduced with v3.5 (which is for Cm12) ; you'll need to hang on till I finally succeed in porting the cm12 version to kitkat (which I hope I get time to achieve soon). :good:
[Moto G Original Android Development] y@$h98:
Thanks a lot for clearing that up. Simply love your kernel, its amazing!! Thanks a lot and keep up the great work!:)
[Moto G Original Android Development] xxAirwickxx:
So again generally runs good for me. no random reboots. Don't use that dw2ts oor whatever its called Lol Only use phone for Wi-Fi connection. Can get a bit laggy with smartassfalcon & intellimm. I'm unable to turn on Mp decision in TricksterMOD. Can enabled/disable intelliplug. Keep the goods rolling ?? Only in time comes perfection ;)

Thanks for your work !!
[Moto G Original Android Development] Rocketval:
There's no 3.7 version download link in description :confused:
[Moto G Original Android Development] fermasia:
Version 3.7 - fixed

As promised, here I bring you a new version without the SODs causing patches. Everything else stays just as 3.6.

Link on the second post (as allways).

Cheers and happy new year to you all!!
[Moto G Original Android Development] PeterImmel:
Thank you very much for your work.

Could the latest change solve the rom-related camera problems? Don't know nothing.....
[Moto G Original Android Development] xxAirwickxx:
Thanks and Happy New Year as well
[Moto G Original Android Development] fermasia:
Have you tried with a different rom? Since Cm sorted out camera problems, I didn't have any issues with it. I'd say it's something that CrDroid has changed, but I think other users reported everything was Ok with 3.6 and CrDroid. Can anyone confirm this?
[Moto G Original Android Development] PeterImmel:
I'll test tomorrow. Need my phone, when I'm drunk.

Happy new year
[Moto G Original Android Development] reversegear:
I'm drunk too but I flashed the kernel [emoji13]
[Moto G Original Android Development] sub77:
Nice kernel. Can u make it kexec patched?
[Moto G Original Android Development] methuselah:
[MENTION=5190317]fermasia[/MENTION].. Well bumping your thread for a technical question. Today I was using my official ROM4.4.4 with faux kernel. Well I noticed something. While I am in official ROM with faux the cores behave very gently. Just let me quote a example, while you are in faux app then if I am not matter in which ROM on which kernel ,official kernel or other, the way cores behave is very strange. In all other kernels or Roms when you are in faux app the cores follow pattern to come online. What I mean firstly the first core will come online (though it always stay online) , then when it reaches maximum frequency only then the next core goes online. Well you will say this should have happen Im every kernel which uses faux modules. But in official ROM with faux it is different. The third core stays offline till max frequency came only then the 3 core go then online till that time they remain offline. I will later attach a video for what i mean.

But in all other roms and kernels cores behave very aggressively... Now this thing will definitely goona help in saving battery in long run.

Can you look at this thing while developing a rebase. .. I know I am asking too much but its worth a look what I mean....
[Moto G Original Android Development] fermasia:
Honestly, I'm not sure if I missed something of what you wanted to tell me, it's not very clear :p Still I think I get the idea. The way cores are hotplugged is defined by the hotplug driver you use, there's no easy way to implement a waking core logic. Governors have a lot to do, but within what the hotplug driver logic admits. Considering we are in CM (stock roms allways drain less battery throughout the whole system), the way cores are handled in my kernel is reasonable enough, otherwise it would mean a whole new hotplug driver implementation, which is far beyond my reach and I truly think it's not worth it.

Happy new year my friend :good:
[Moto G Original Android Development] methuselah:
well this what i mean

well see this video. this is what i mean here see when i am at home screen of faux app the phone is on 300mhz, second core is shutoff, then when i touch the screen only then first core reach 1.19ghz and then next core come online at 300..under this process the 3rd core never come online. Well when this situation is compared with other kernels then something happens. i mean when you touch the screen all cores come sometime online aggressively. well this is not the case with any single kernel but with all most of them... :confused: ...here what makes me curious whats that special in official faux kernel that makes this pattern so systematic that the cores come online step by step . they don't shoot at once.

happy new year from my side too brother.....
[Moto G Original Android Development] Sik-1:
The only thing I can say honestly, is that to get as close as possible to faux performance since he hasn't updated in awhile was using experience kernel, he has if notost of faux's implements and I get close to stock battery

---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------

Most kernel devs I see here use the aero implement, but that's based off of Franco's hotplug driver, which keeps the first 2cores on all the time, then throttles the others

I too much prefer the faux way, more battery by at least half hour for my use and I never lost any performance
[Moto G Original Android Development] fermasia:
People, I don't think this is the place to have this discussion. Faux and Xperience... stock? Cm11? Cm12? What are we talking about? I don't see the point, if any could benefit of such discussion here, is if you can provide some feedback about performance to this kernel (Donkey). Everything else is for some thread about battery performance in general, and there is a thread for that already. Battery is absolutely subjective, if you use wifi mostly, if it's on radio most of the time, how healthy the signal is, if you give the phone intervals to let deepsleep preserve batter or if you wake it every 10 minutes, blah, blah, it's a neverending discussion.
[Moto G Original Android Development] Sik-1:
Whoa whoa whoa, we are simply only talking about the hotplug driver used in your kernel vs others, sheesh, this is about your kernel, I was just explaining to him the one your using compared to the way others have there's implemented

But its your thread so I'll back out. Smfh
[Moto G Original Android Development] PeterImmel:
Donkey Kang Kernel - V3.7

in combination with

crDroid

is running great (for 6 hours now / no fc/reboots/etc.). Thanks a lot!

(Camera also works)