yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] OldYellowBricks:
tbh, I think you shold remove dt2wake gestures for good; dont do two versions. I had zero dead screens on non 2tw versions of the kernel tbh. it'll save you headaches of d2tw users complaining imo. Thanks for the hardwork. Back when other kernels had d2tw it was the saaaaaaaame case with dead screens all over the place.
[Moto G Original Android Development] HobbitCy:
only reason i flash a kernel is to get dt2w option so would be really disappointed if it was not an option, waiting for he update to flash it with official nightly of cm12
[Moto G Original Android Development] OldYellowBricks:
I remembrr [MENTION=5190317]fermasia[/MENTION] saying the core of his kernel is stability. If d2tw stays then it beats the point. But then again its his kernel, not mine.

On another note, one workaround to those screen freezes is to have the gestures turned on at all times. The freezes occur when they are all (d2tw ans s2w) turned off.
[Moto G Original Android Development] antarix:
I get a good battery life and decent performance. I use custom kernels for dt2w and at times performance boost helping governors and frequency flexibility.

I don't think giving up on a feature because some people face no touch response would help the cause of a kernel.

I never had such problem with 3.8 version.

Using it since 3 days without dt2w/s2w just to see if I too face the problem being discussed here

The touch works pretty fine and the performance and battery managed itself to the best outcome.

I think may be it's just because I prefer only clean install or may be my screen and board hate rebooting frequently.

I agree with [MENTION=5190317]fermasia[/MENTION] decision to have 2 versions to satisfy all happy members of his kernel or may be only one version with all the features would do it but it's my story that I never face touch problems with or without dt2w/s2w.

Thanks a lot for the latest version.
[Moto G Original Android Development] Luucassrc:
No anda el wifi no hay caso :/

se queda en Activando wifi... y no pasa nada

tengo la ultima versión de cm 12 de hoy
[Moto G Original Android Development] Mchasard:
Wi-Fi doesn't work with last cm12 night fly official dd 10012015 with donkey .... With The 08012015 it worked...
[Moto G Original Android Development] :
About that Wifi Issues, it's Donkey Kang Kernel which needs to be updated

http://review.cyanogenmod.org/#/c/84431/
[Moto G Original Android Development] fermasia:
First of all... english only in this forum. Second of all... I've JUST commented about wifi issues a few posts before. Do you read what I write at all?
[Moto G Original Android Development] rp2615:
I really appreciate a your work but a warning about the non-functioning wifi would have been nice... It's kind of a deal breaker..
[Moto G Original Android Development] fermasia:
You are kidding me, right? I wouldn't build a kernel without wifi. Cyanogenmod changed wifi modules policy YESTERDAY, and I'm building a new version solving that at this very moment. Jeez...
[Moto G Original Android Development] methuselah:
hey

[MENTION=5190317]fermasia[/MENTION] i suggest you to stop commenting on the posts of people who don't even bother to read beforehand. This will keep everything okay.

all those people please remember that here The developer is building his kernel for his own hobby. Don't put burden on him like he goona get something out of it. It is his part time hobby.. Nobody like to again and again answers of Noobs questions. Well Wifi don't work read beforehand the thread and then come back with with logcats. It is best to have proper logs beforehand instead of pasting here DO NOT WORK, its like you are just announcing on a railway platform, it will be ignored. The same thing happen at jira. Most of people just post bugs without proof and developers don't quote them at all. So stop making others sick....
[Moto G Original Android Development] roxkiller:
which smartass difference for the smartassfalcon? and he is looking to have a better economy than interactive, or you have any better [MENTION=5190317]fermasia[/MENTION] economy?

App: Messenger (Facebook) causing many wakelocks draining the battery. I found what it was :)
[Moto G Original Android Development] Dr. Brawler:
The demeanor of this user base is very frustrating. Ppl wonder y all the good devs stop development. Can't even appreciate free things. If someone else's work isn't good enough for u then learn to do things urself. Shout out to all the users that appreciate n support this man's work. Reading is a beautiful thing
[Moto G Original Android Development] Shub77:
I find out that current 3.8 Donkey Kang kernel + cm-12-20150110-NIGHTLY-falcon (and many versions before) allows the Camera to work well, meanwhile the stock cm-12-20150110-NIGHTLY-falcon kernel does not.
[Moto G Original Android Development] santos_10:
Sorry, wasn't my intention to frustrate you. I only want to tell you the problem because before I install the Kernel I see problems with others users and this occurs in my case, now I read AGAIN new replies and I know that you're working in new releases, we're waiting for it and again sorry, and continue with your work, take your time.

Cheers. ;)

P.D. Sorry for my English :p
[Moto G Original Android Development] y@$h98:
There isn't a "problem" with the kernel which has to be solved. Due to new WiFi modules policy in the latest cm nightlies the WiFi isn't working with the kernel-not exactly the devs fault is it? Please read before commenting.

Sent from my Moto G
[Moto G Original Android Development] fermasia:
Version 3.9 (CM12 only) released

This was a tricky one, but it's finally working. You'll find the link on the second post as allways. For some reason UI will show as if it's not responding right after booting, but you MUST choose to wait when asked to kill the system process. After that, UI will lag for one or two minutes, but after that's done it seems like everything works as usual.

As I said, this one was a pain in the a**. I had to do this blindly, without the device, and that meant twice as work (thanks for the bunch that helped me testing, you were really helpful and I appreciate it). So I'm sorry to confirm that I won't continue supporting the kernel from now on. It's just too messy to be done now that I don't have the G anymore. I will split CM11 and CM12 into dt2w and no-dt2w as I announced, but that's it.
[Moto G Original Android Development] Volkan66:
Warning to all Moto G owners: Dont flash this kernel 3.9: I have softbricked my phone. Phone is unable to boot.
[Moto G Original Android Development] fermasia:
Gosh, I've had it flashed on at least three devices without problems. What device do you own? What recovery? Rom? Had you flashed stock Lollipop at some moment?

Please, I'd like to help if my kernel caused this, but I need some info and that announcement without more details is nasty.

P.D. I put down the link till this one is cleared up.
[Moto G Original Android Development] Volkan66:
Sorry i have to restore my phone through adb to stock motorola. I am using a XT1032 German Retail Version(only one sim card).

I am using the newest twrp 2.8.3.0 version. Before flashing your kernel, I was using the custom rom: Broken OS 01/10 Version (todays version).

Everything went fine in my case (restoring the whole phone to original stock motorola firmware), but during the flashing process of your kernel, i have only see an information on twrp saying that it has write something to init.d and then i got a blank screen, unable to go in twrp again. The phone doesn't start again.

Sorry i cant give you any logs because my phone is formated.
[Moto G Original Android Development] GæxD:
+1
[Moto G Original Android Development] fermasia:
Man, I'm sorry that happened, I wouldn't have let that version out if I didn't have positive feedback from testers. I can confirm it flashed fine onto today's cm official nightly, and I never had such problems with any of the releases, but I won't risk this happening to anybody, so the link's off and the release deferred till I find (if I find) the chance to test it thoroughly myself. Building something without the phone in my hand, was a bad, bad idea. Sorry for the inconveniences, my friend.

Ever heard of the thanks button? I already put the link down and made sure to contain every possible troubles to users, I surely don't need the red bold sofbrick warning replicated along the thread.
[Moto G Original Android Development] jonas210678:
[MENTION=5190317]fermasia[/MENTION] I deleted the ko. Modules in the 3.8 Kernel but WiFi don't work too. But what about when I flash only the kernel img should this work?
[Moto G Original Android Development] fermasia:
The new 3.9 version was the solution, but even when it was successfully tested in official Cm12, I had one user had a severe problem using Broken OS, and I can't risk anybody else get into a similar situation unless I can test the kernel myself in a couple of different roms. Sadly, not having the phone to do the tests or take some logs, it's a dead end and probably the end of developement for Moto G.
[Moto G Original Android Development] Kayant:
[MENTION=5190317]fermasia[/MENTION]

Could it be the zip causing issues? If am not wrong there shouldn't be another zip within the zip right?

Am crurrently porting your kernel to the peregrine so I can test it for you to see how it is from users that would be on versions with the modules not included in the kernel and users using the latest nightly with it included.

I will be using this zip layout - http://xdaforums.com/moto-g/4g-development/kernel-moggy-stock-aosp-peregrine-moto-t2991006
[Moto G Original Android Development] fermasia:
No, the zip inside the zip is me doing things manually to test and forgetting to wipe a previous zip in the anykernel folder. But that wouldn't cause such an issue. Anykernel basically splits and unpacks the current boot.img otg, takes the current ramdisk, applies some patches, and repacks everything again. And flashes some init.d scripts if needed, which I used to apply the custom settings of my kernel. For the moment, I'm puzzled and far from knowing what could have caused the issue.

The ugly thing now is that I can try a few things, but knowing the risks I could only test owning a phone. But well, if you are porting the kernel (it's a pleasant surprise to hear that) and get positive results, that would probably make it easy once there's a safe and tested version. So, thanks.
[Moto G Original Android Development] Kayant:
Oh never knew you could do that. I was thrown off by the files like init.tuna which are in the zip. I should say my kernel knowledge is basically zero :p I just know how to port roms and stuff for the most part ;)... No problem happy to assist and thanks for creating your awesome kernel :)
[Moto G Original Android Development] gigermunit:
My GPS is oddly not working anymore since I rebooted from initial flash.
[Moto G Original Android Development] fermasia:
Flashing what, on what rom, like what version, and over a dirty/clean rom-kernel install? And oddly not working means...? Two ways to go, you tell me or I try to guess. Or wait, we can play charades... would love to see your "cyanogenmod" face.
[Moto G Original Android Development] methuselah:
remember to give logs... give logcat... what i suggest you is to flash again your ROM
[Moto G Original Android Development] gigermunit:
haha I am sorry was in the middle of a league of legends match and didn't get to finish typing before my phone sent the message, I am running [ROM][Falcon/UNIFIED]XPerience-9.0.2_r1 NIGHTLY and I can post a logcat for you in one moment. I will edit the post.

Link to logcat
[Moto G Original Android Development] xxAirwickxx:
I like the name !! Haha ??

---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------

I didn't see Wheatley listed. Am I right or blind.... Blind is possible lmao
[Moto G Original Android Development] fermasia:
True, the ramdisk is incompatible. Hang on, I'm working on a non-anykernel version right now that might solve this issues :good:
[Moto G Original Android Development] Uz986:
Thats great.
[Moto G Original Android Development] RenderBroken:
Kernel looks promising! Keep it up!

As for Ramdisk, I prefer to use my own ramdisk to not have to deal with such issues. For me, it seems to be easier to maintain my own instead of adjusting scripts to adjust for all the changes in the other rom ramdisk out there. Just my 2 cents. I have been down the anykernel road. But the trick I use with my own ramdisk is to create a separate folder/repo outside the kernel source so if you ever have to reset your kernel's branch you wont inadvertently mess with your ramdisk. Also to build your own ramdisk you can extract the ramdisk from another rom's boot.img using a tool called:

Boot Recovery RePacker

It runs in windows. From here you will get everything you need for your own ramdisk. Hope this helps a little.
[Moto G Original Android Development] s.sawrav:
Thank you worked perfectly [MENTION=5190317]fermasia[/MENTION] this solves the problem of bootloop.I was on N5XPA rom with xperience 18 kernel when i flashed your kernel,it bootlooped but after i dirty flashed the rom and then flashed your kernel everything was awesome,Nice work man.

:good:
[Moto G Original Android Development] itslels:
Trickstermod reports that my phone isn't entering deep sleep state. Anyone else?
[Moto G Original Android Development] swarls:
Works fine for me.

Great kernel, running it on PA and the performance is amazing. Haven't had any issues, everything works fine.

Can't say much about the battery life for now, but seems fine from what I've seen so far.
[Moto G Original Android Development] fermasia:
[MENTION=4821745]OldYellowBricks[/MENTION]

[MENTION=3308423]Mchasard[/MENTION]

[MENTION=4739553]jaggu1989[/MENTION]

[MENTION=4336339]Uz986[/MENTION]

[MENTION=5857055]Flashhhh[/MENTION]

[MENTION=5542794]fabus[/MENTION]

and everyone else that might be interested, check the op for new version (v1.1). It's now built alltogether with it's own ramdisk and should solve most of the compatibility issues with other roms. Please report if you find any new problems.

Cheers
[Moto G Original Android Development] xxAirwickxx:
If first one is working should I do the new one ??
[Moto G Original Android Development] fermasia:
Check that your settings are as stated in "recommended settings". Specially CPU min_freq, should be 300000 and also check MpDecision is off (Intelliplug is recommended) or if you want to use it, disable Intelliplug. Trickster lets them be on at the same time, or at least it shows that.
[Moto G Original Android Development] fermasia:
There are no substantial changes in the kernel itself, just a few tweaks in the ramdisk, so probably you should keep the first one if everything goes fine. Maybe for future versions I'll build both (anykernel and standard boot.img) so you guys can choose what fits you best. The nice part of the anykernel version, depending on the rom that you are using, is that it will let you preserve the rom's own ramdisk tweaks. In any case, you can try both and see. :good:
[Moto G Original Android Development] fermasia:
Thanks for the kind words, man. Anykernel was actually a lazy option... but I've learnt my lesson - lol. I spent some time setting up and tuning some scripts to get things done, and we are now off anykernel, or maybe I'll make simultaneous builds so each one can choose what's best for them. About the tools to mess around with my ramdisk, my kitchen is ubuntu based, but it's ok, I got the necessary tools to do it. Actually, I've been trying to find a way to build my ramdisk from source (without building the entire rom, thought) but well, I've settled for extracting and tweaking one from latest CM build. And yeah, I'll take your advice and move the folder off my repo, I'd really wouldn't want to blow off my work accidentally!

Still, I might use your experience (you are the man, and you know it - lol), since I'm planning to mess up with stuff, so if you don't mind I'll PM you if I really need to about some details.
[Moto G Original Android Development] deeplyyoung:
Flashed V1 on N5XPA n see the battery… rest it's smooth..
[Moto G Original Android Development] RenderBroken:
Sounds great! Yea I use a Linux virtual machine to build with. Love it! Its easier building your own ramdisk than you think. Sure you can PM. Best of luck to you.
[Moto G Original Android Development] OldYellowBricks:
yyyaaaaaaasssss the newer kernel works with my CRDroid on philz recovery. Wifi camera BT all running fine yyyaaaassssssss
[Moto G Original Android Development] fermasia:
Check your settings. My first release had some default values messed up (depending on the rom it was flashed on), min cpu freq was defaulted to max, and both intelliplug and mpdecision were off. That's solved on 1.1, thought.

The way your charge drops non-stop, suggests that could be the problem.
[Moto G Original Android Development] deeplyyoung:
MY current setup is as follows:-

1- INTELLI-PLUG> ON
2- MP-DECISION >OFF
3- GPU MAX FREQ> 450
4- READ AHEAD BUFFER SZ>512
5-SCHEDULER> SIO
6-FREQUENCY LOCK>ON
7- FREQ PROFILE-MIN> 300000, MAX> 1190400
8- GOVERNOR> INTELLIACTIVE/INTERACTIVE.

Now what should i change to get max Juice:D:D
[Moto G Original Android Development] Stefano187:
Hello [MENTION=5190317]fermasia[/MENTION]

First of all: great job! Kernel is running perfectly on latest CM nightly, I'm using it since yesterday and it is really great! Intelliplug and Eco-mode are the best combo for a good combination of battery/performance! :highfive:

Your choice of building a non-anykernel version is very great on my opinion, it avoids you a lot of compatibility problems!

I've faced no issues with all features of my XT1032 (camera, Bluetooth, GPS, Radio), the only thing I found is not working is the simple_ondemand GPU governor. It is something that everybody can live with and something that is present on other custom and stock kernels, but if you want to achieve the perfection it is the only thing that need a fix.

Keep up the great work

Regards

Stefano
[Moto G Original Android Development] OldYellowBricks:
same here. changing the gpu gov to simple on demand causes a reboot. appart from that, its all A okay
[Moto G Original Android Development] Flashhhh:
[MENTION=5149175]deeplyyoung[/MENTION] Disable frequency lock option!

Whats the use of it when we have intelliplug!!

And one more thing frequency lock option sometimes prevents ur fone from going into deep sleep!!

Hit thanks if i helped!!
[Moto G Original Android Development] y@$h98:
Please don't post logcats directly (as in the text). It makes the thread too long. It'd be better to post them in notepad files as attachments....

Sent from my Moto G
[Moto G Original Android Development] gigermunit:
I apologize I remember reading to post them in code tagged somewhere.
[Moto G Original Android Development] Shub77:
It seems we have to collect some money to gift Fermasia a new Moto G, so that he can restart the development :)

Anyway it would be a great loss for Moto G community to have Donkey Kang no more, great kernel. I've been using it for a couple of weeks now, but I have already fallen in love with it. :)
[Moto G Original Android Development] abhi0502:
Delete
[Moto G Original Android Development] Adityadua:
Testing

PM me the zip, and I'll test it for you. :D
[Moto G Original Android Development] gharrrrrr:
Happy to be a tester as well [MENTION=5190317]fermasia[/MENTION]. I love this kernel on my Moto G and it isn't my main device so it can go through some bugs.
[Moto G Original Android Development] Kayant:
[MENTION=5190317]fermasia[/MENTION]

Some feedback -

I can confirm flashing your zip results in a softbrick in my experience which is easily fixed by re-flashing the rom. Removing the Update-Anykernel-zip within the zip results in a normal flash and rom booting.

I was wondering which toolchain you used specifically because the ones I have tried are making the rom run really slow and unstable. Thanks.

Also Wifi isn't working for me with your zip or the one I used based on bedalus's zip where I included the deletion of the modules folder. Not sure how to fix that. Reading http://review.cyanogenmod.org/#/c/84542/ apparently it is to do with the modem or ramdisk. Any ideas?
[Moto G Original Android Development] knizmi:
To make wifi work, you just need to merge those two commits:

https://github.com/CyanogenMod/andr...mmit/faa9160a64b27afdfd33790db53b767f432e8884

https://github.com/CyanogenMod/andr...mmit/2b1384c34c86c067c45605c547ca588b40d240df

The first one changes defconfig so that all modules are part of the kernel and the second one fixes iris module build and initialization. About one minute of work and recompile.

You seriously didn´t think that deleting wifi modules will make wifi work ;)

Moreover fermasia´s kernel will probably not work well if you use zip by bedalus. Bedalus repacks his kernel with whatever ramdisk is currently inside the phone, while fermasia uses his own ramdisk with several custom scripts.
[Moto G Original Android Development] Kayant:
Well the folder isn't being used so i thought so :p... Funny this is that I have those changes merged but it isn't working for me :( - This is flashing on a rom that has the modules already.

https://github.com/MotoG4G-AOSP/android_kernel_motorola_msm8226/commits/donkey-kernel

Edit -

Flashing a new CM12 nightly with the new kernel and changes. The modules are deleted :p
[Moto G Original Android Development] knizmi:
Well, with this config you can´t have any modules in the first place, so there should be nothing to delete.

What ROM exactly are you flashing this onto? Wifi will probably only work with latest CM builds. There are some changes needed inside the ROM and other ROMs most likely did not merge these changes yet.

In case it was any help to you, here is my CM12 kernel that I am using right now and here are the sources. It contains only a couple of patches, but works flawlessly.
[Moto G Original Android Development] Kayant:
I was testing flashing it on an older CM12 nightly which doesn't have the latest changes but that don't work :p but flashing the latest CM12 nightly with the latest changes works fine.
[Moto G Original Android Development] knizmi:
There you go :good:
[Moto G Original Android Development] Kayant:
Yh I guess the whole system needs to be deleted first :(
[Moto G Original Android Development] Kayant:
[MENTION=5190317]fermasia[/MENTION]

Just so you know your kernel is working perfectly fine. the softbrick issues were caused by a zip being within a zip ;)

Edit -

And as per above a separate version will be needed for users running older versions of roms with the modules not built in.
[Moto G Original Android Development] fermasia:
All right, with caution, whoever is able to please try this build: https://www.androidfilehost.com/?fid=95897840722640898

Thanks.
[Moto G Original Android Development] fermasia:
Kayant, I really appreciate you taking the time to look into this. If I can help you in any way, please let me know :good::good:
[Moto G Original Android Development] Kayant:
No problem. Just what toolchain you use as the ones I have tried have made the device really laggy and slow to boot with the system being unstable for several minutes.

I have tried -

https://github.com/Christopher83/linaro_toolchains_2014 - generic one

https://github.com/UBERUTILS/arm-eabi-4.8

Both result in poor performance :(
[Moto G Original Android Development] methuselah:
[MENTION=5190317]fermasia[/MENTION]

If you want a news on moto g xt1033 unofficial dual sim is working now...
[Moto G Original Android Development] fermasia:
I'm now using sabermod 4.8 from https://github.com/SaberMod/arm-androideabi-4.8

But I've tried Christopher's linaro builds and worked well too. If you like, I must have a bit older linaro armv7 optimized toolchain somewhere around here, so if you mean to try out things I could upload it and hand you the link too.
[Moto G Original Android Development] fermasia:
Meaning the last link I posted?