yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] SeannyM:
When I use the 0219 kernel build the issue dissapears.

Sent from my Moto G

---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------

That's when it happens the most, had it once or twice in other places.

Sent from my Moto G

Edit: It seems a reflash fixed it for now.

I had two small lockups after the reflash.
[Moto G Android Development] shure2:
I got lag with the old kernel too, still it's the only alternative kernel for cm11 so please carry on supporting it
[Moto G Android Development] xheon:
I had lag too, fixed it by putting CPU max freq to highest, CPU governor to intelliactive and scheduler to deadline. Now it's smooth as butter.
[Moto G Android Development] pinkflozd:
I will make the kernel more performance friendly by default on the next release
[Moto G Android Development] cortex69:
guys, could you be that kind and help me with adjusting settings of the kernel ? I've got a weird feeling that everytime I install faux tuning apk through play store and disable s2w and dt2w things just get bit ugly. phone doesn't work as smooth as it before the install of the app. Does this app push faux's settings to kernel and override yours, [MENTION=3545900]pinkflozd[/MENTION] ? Is there any other way for tweaking the kernel without using this ? Plus apart of that I noticed the battery drain while having the app (~1.5 % / hour) and no at all while don't (~0.2% / hour)
[Moto G Android Development] justjr:
I used with faux recommended settings, intelliactive and fiops. Worked flawlessly and no lags.
[Moto G Android Development] Haggster66:
fsync?

I'm really happy with how this kernel is developing!

One question: Does the kernel currently switch off fsync during boot? I know that a lot of other kernels do this with great success to minimize startup and reboot times. A good while ago with another device I was experimenting with switching off fsync completely, but despite a lot of people saying that it never caused them any problems, I constantly lost data when one of my games crashed (i.e. it seems the data which was recording my progress in the game was corrupted, effectively erasing all my achievements). Therefore I'm not a big fan of switching off fsync completely, but it seems switching it off during boot is a perfectly good idea.

Looking forward to the next kernel releases! This will be amazing once CM11 is stable and bug free.

EDIT: Since the Moto G's flash storage is quite fast I think the speed gains would be questionable though... also depends on how many write operations there are during boot. In any case, it'd always be necessary to manually switch fsync back on after boot, correct? Anyway, would be interesting to know how this kernel handles it
[Moto G Android Development] SeannyM:
Does this commit help overclock any? I'm going to compile with the latest sources to test.
[Moto G Android Development] SeannyM:
After messing around with my build of this kernel's latest commits, I've noticed a few things:

-the commit mentioned in the above post did not help with overclock

-the freezing issue that it seems only I experienced is fixed

-the system is slightly snappier

I think a new build should be released, mainly because of the last two things. I would use my build however I could not get it to boot unless it was temporary. :eek: Also, there must be something with the way this kernel is compiled, because on my build there is 883MB of RAM like there should be however on all of the builds posted here there is 880MB. I compiled with the Linaro 4.8.3 toolchain just like these builds, so I don't see what the problem is.
[Moto G Android Development] diego88it:
Guys i have a problem: i try to flash it on my moto g with official cm11, but when the phone is rebooting it blocks itself on the cyanogenmod logo...why this happens?
[Moto G Android Development] pinkflozd:
get me a logcat and dmesg

i saw dhacker implemented gpe support so perhaps thats the problem, as its not yet i this kernel but i dont think so

p.s. i will release a new build tomorrow, was a bit busy IRL
[Moto G Android Development] SeannyM:
Does FauxSound work? I won't need it because my headphones sound great without any DSP, but in my build of the kernel it seems that it doesn't work. Unless you need to set it in the config? It seems it is "default y", so IDK if it's my build or the kernel in general. Maybe I just can't find it in the FauxClock app :p

Edit: also, those lockups that I've been having are present again, but the logcat shows nothing wrong. (at least from what I can find) I may try a factory reset but if that doesn't fix it than maybe I'll try to look around the code and fix it myself.

Edit: lol, I need the FauxSound app. My bad.
[Moto G Android Development] MrKra:
My Antutu Scores:

1) Stock: ~17000

2) LiquidSmooth ROM (+buildin Kernel) (http://xdaforums.com/showthread.php?t=2648886):

16300-16500

3) LiquidSmooth ROM and pinkKernel

a) [MENTION=1823332]119[/MENTION]0, ondemand, row: 16500-16700

b) [MENTION=425767]130[/MENTION]5, ondemand, row: 16700-17000

c) [MENTION=1421704]159[/MENTION]3, ondemand, row: 16800-17050

=> Ram overclock doesnt change anything for Antutu.

The best Antutu Scores i got with the stock Rom and stock Kernel
[Moto G Android Development] Haggster66:
LiquidSmooth is AOSP based and contains less optimizations than stock or CM; both, CM and stock contain optimized libraries and algorithms (at least more so than almost all pure AOSP based ROMs). Furthermore the Ondemand governor doesn't give good performance and in case of Pink kernel, Intelliactive should be used which is not available on stock. ROW gives bad results for write performance since it's not a fair scheduler, therefore if you want a flash memory optimized io scheduler and get even read/write results, use FIOPS instead. Also the benchmark doesn't test multitasking performance, which is heavily optimized in Pink kernel through various modifications in e.g. areas of RAM handling among others like entropy generation.

The stock kernel and ROM are indeed quite good. I assume you tested Moto stock instead of GPE stock, correct? I found GPE to be even faster, also on GPE there's more free RAM available per default. I think Moto stock gains most points compared to the other ROMs due to the fact that it's using F2FS instead of ext4, which is however not faster in every single use case and unfortunately brings data consistency problems since ext4 has proven to be more reliable.
[Moto G Android Development] Pinktank:
Does this kernel include the updates dished out with the Februrary OTA (I am not sure what google did with source disclosure, hence the question)
[Moto G Android Development] SeannyM:
[MENTION=3545900]pinkflozd[/MENTION] there are some new changes to the original CyanogenMod kernel which apparently cause the kernel to be incompatible. These commits should be added to the kernel soon so when the next nightly comes out the kernel will still be compatible.
[Moto G Android Development] pinkflozd:
yes dhacker added GPE support, the kernel should still work without it...

i wont be able to roll out a update today, just came from work, but tomorrow certainly
[Moto G Android Development] SeannyM:
The GPE is a separate kernel, the thing that people are reporting is causing problems are some changes to the display. I haven't tested myself, I just saw that on the CyanogenMod thread.

I'm fine with not having an update today, I fixed my builds so now I can compile myself "nightlies" of this kernel. I also might overclock my GPU a tad more, and maybe I'll try to fix up the overclock (which of course I will make a pull request for, I wouldn't keep it to myself, or would I? :p) No guarantees there though, I might not even try :)
[Moto G Android Development] pinkflozd:
i see the display commits now, thx mate, commited them and testing the new feutures that i added,

yes mate make a pull request if u get the best values for any overclock, i'll leave overclock aside for now

an update is due soon that will work on the latest CM builds...

edit: i will upload it when the next CM ota rolls out
[Moto G Android Development] mccbrandon:
I can't wait for that update!
[Moto G Android Development] SeannyM:
I'm compiling soon, I might look into the CPU voltages after.

Edit: new build working great with 0226 CyanogenMod, now I will work on overclock for a bit.
[Moto G Android Development] SeannyM:
After a couple of failed attempts, some logcats, one bootloop and about an hour of time, I have established one thing: the overclock's problem is not the voltages. The problem is the frequencies themselves. From what the logcats showed, even though you can select the "overclocked" frequencies, the kernel just doesn't recognize them and therefore caps the clock limit at 1190MHz. Here is a snippet from one of the logcats I took:

I/ThermalEngine( 405): Threshold 0 Action Info[0] : 1190400
I/ThermalEngine( 405): Threshold 1 Action Info[0] : 1094400
I/ThermalEngine( 405): Threshold 2 Action Info[0] : 998400
I/ThermalEngine( 405): Threshold 3 Action Info[0] : 787200
I/ThermalEngine( 405): Threshold 4 Action Info[0] : 600000
I/ThermalEngine( 405): Threshold 5 Action Info[0] : 384000

These are the frequencies recognized by the system. As you can see, it does not see the higher frequencies. What I think is the problem (and this is a guess at best) is that something is not linking up correctly. Somewhere in the code, the frequencies are being linked to non-overclocked values for something, whether it be the speed bin, the voltages, etc. something's not matching up. All the necessary values are there for a functional overclock, they're just not matching up. Now, whether this is true or not true, it's the best lead we've got, so if I have some spare time, I will look through the code a little more and try to find the "missing link". I might not have much time to do this for a few days, so maybe [MENTION=3545900]pinkflozd[/MENTION] can snoop around a bit if there is ever time for them. Anyways, just thought I'd report on my findings.
[Moto G Android Development] adinkwok:
OTA has rolled out! I'm waiting for the release of the more performance kernel (no pressure) :fingers-crossed:
[Moto G Android Development] MrKra:
Which Moto G CM rom can you recommend
[Moto G Android Development] Haggster66:
At the moment there's only pre-releases. So if you're not afraid of bugs it'd make sense to use the official CM11 pre-release ROM since it's updated via OTAs regularly and gradually improving. If you're seriously depending on actually using your phone I'd however wait until it's stable (which should be the case soon)
[Moto G Android Development] pinkflozd:
new version released

The 20140227 version is compatible only with roms released after February 25

GPE Compatible

Sound Control 3.2 thx to faux123

FIOPS Default Scheduler

Intelliactive Default CPU governor

3.4.82 CAF patches

BFQ, CFQ tweaks

linaro patches

more memory, cpu optimizations

some more patches
[Moto G Android Development] daniel910821:
Edit: Nevermind, i already understood.
[Moto G Android Development] herbesi01:
mmm I can´t find the link of dowload in to folder...

Thanks is a great kernel...
[Moto G Android Development] Slothboy:
Me neither, love the kernel too, but no download link
[Moto G Android Development] justjr:
Thank you. Download link please?
[Moto G Android Development] pinkflozd:
fixed, seems a glitch in meadiafire deleted the file
[Moto G Android Development] Tenroc:
Working awesomely with latest CM nightly.

But could you add support for faux sound in your next kernel?
[Moto G Android Development] SeannyM:
FauxSound is supported, did you not see the changelog?
[Moto G Android Development] justjr:
Awesome new version. All working as intended.

You tweaked the intelliactive governor? Looks nice.

edit: ops, important think it, it breaks the radio signal in xt1033 build of cm11, 26022014
[Moto G Android Development] SeannyM:
It seems I have a bit of spare time today, so I will try two ideas that I have on how to fix the overclock. I have some faith in the second one, not sure about the first one though... oh well, I have to try everything until it is fixed!
[Moto G Android Development] pinkflozd:
yes tweaked a bit intelliactive to be more responsive

great mate ;) hopefully you'll be lucky to get it working
[Moto G Android Development] SeannyM:
If I do, I'll make a pull request ASAP :fingers-crossed:
[Moto G Android Development] xheon:
Working great on latest cm11, the fluidity really feels on nova launcher after flashing pink kernel, great work.
[Moto G Android Development] justjr:
Quoting myself, but, yes. :3

I was able to make calls, but like as if I had flashed official cm11 in my xt1033, I could not hang up calls. It stuck there.

Have to go back to stock unofficial cm for xt1033 by doublepranks. =/
[Moto G Android Development] pinkflozd:
could you get me a logcat and dmesg?
[Moto G Android Development] justjr:
Yes, here it is: http://pastebin.com/PRqAWYUq, take a look and tell me if it have everything you need.

Remember, it's flashed over Doublepranks unofficial version of CM11 made for XT1033 (only one sim working).

Much love!
[Moto G Android Development] Tenroc:
Oh, sorry, really, I was in a bit of a hurry when I posted and it wasn't listed in the features list. Should have checked the changelog though. My apologies.
[Moto G Android Development] Jdgp42:
1rst post says no stock rom, but latest version says GPE compatible.... So, can I install this on GPE rom?
[Moto G Android Development] pinkflozd:
no you cant use it with GPE stock rom, it's only compatible with Cyanogen based roms
[Moto G Android Development] marc_miranda:
Could anybody upload the previous version? Flashed it on a pre-25th Feb ROM and now stuck on bootloop :/

EDIT: Found it in the downloads, ignore my stupid question
[Moto G Android Development] SeannyM:
I have pinpointed the overclock issue. In the logcat that I posted previously I overlooked something big time. Whoops :p

I/ThermalEngine( 399): Threshold 0 Action[0] : cpu
I/ThermalEngine( 399): Threshold 1 Action[0] : cpu
I/ThermalEngine( 399): Threshold 2 Action[0] : cpu
I/ThermalEngine( 399): Threshold 3 Action[0] : cpu
I/ThermalEngine( 399): Threshold 4 Action[0] : cpu
I/ThermalEngine( 399): Threshold 5 Action[0] : cpu
I/ThermalEngine( 399): Threshold 0 Action Info[0] : 1190400
I/ThermalEngine( 399): Threshold 1 Action Info[0] : 1094400
I/ThermalEngine( 399): Threshold 2 Action Info[0] : 998400
I/ThermalEngine( 399): Threshold 3 Action Info[0] : 787200
I/ThermalEngine( 399): Threshold 4 Action Info[0] : 600000
I/ThermalEngine( 399): Threshold 5 Action Info[0] : 384000

and farther down...

I/ThermalEngine( 399): thresholds 37000 45000 48000 52000 57000 62000
I/ThermalEngine( 399): thresholds_clr 35000 42000 46000 49000 54000 59000
I/ThermalEngine( 399): actions cpu cpu cpu cpu cpu cpu
I/ThermalEngine( 399): action_info 1190400 1094400 998400 787200 600000 384000

The issue is that the thermal engine is only allowing 6 different frequencies to be used. It excludes the overclocked frequencies and even excludes the 300MHz frequency. (meaning 300MHz is actually running at 384MHz, tested and confirmed) To get a working overclock, we either need to make the thermal engine select different usable frequencies or the more suitable option, force the thermal engine to select more than just six frequencies. I might not be able to work on this for a few days, but now that the exact problem has been uncovered it should be a lot easier to fix.
[Moto G Android Development] pinkflozd:
nice find mate, i'm looking around at the thermal engine atm
[Moto G Android Development] pinkflozd:
new version released

Fixed ThermalEngine frequencies

Algorithm improvements

Performance improvements

some more patches

[MENTION=4888452]SeannyM[/MENTION] ThermalEngine didnt fixed the overclock but better have a working thermal engine when we get the overclock finished
[Moto G Android Development] Marco_nx:
Tittle says [KERNEL][CM][SLIM][AOSPA][CARBON][AOSB], but right under says it´s only compatible with CM based ROMs. S can I flash this kernel on PA?
[Moto G Android Development] SWTR:
[AOSPA]Is PA:)

So, yes:)
[Moto G Android Development] adinkwok:
All the ROMs listed in the title are CM based
[Moto G Android Development] TheeuS:
Do you guys recommend this kernel instead of the CM one that comes with the zip?

And when an OTA update arrives, I will have to flash it again?
[Moto G Android Development] Feyerabend:
Yes x2
[Moto G Android Development] SeannyM:
Have the changes been pushed to GitHub? Nothing seems to have changed since yesterday in the kk/kk-exp branches.
[Moto G Android Development] pinkflozd:
the thermal changes are in /system/etc/thermal-engine-8226.conf in the update.zip
[Moto G Android Development] SeannyM:
Okay, thanks. I completely forgot that there were other files in the .zip besides modules and the kernel :p

---------- Post added at 03:03 PM ---------- Previous post was at 02:54 PM ----------

I/ThermalEngine( 389): Threshold 0 Action[0] : cpu
I/ThermalEngine( 389): Threshold 1 Action[0] : cpu
I/ThermalEngine( 389): Threshold 2 Action[0] : cpu
I/ThermalEngine( 389): Threshold 3 Action[0] : cpu
I/ThermalEngine( 389): Threshold 4 Action[0] : cpu
I/ThermalEngine( 389): Threshold 5 Action[0] : cpu
I/ThermalEngine( 389): Threshold 6 Action[0] : cpu
I/ThermalEngine( 389): Threshold 7 Action[0] : cpu
I/ThermalEngine( 389): Threshold 0 Action Info[0] : 1593600
I/ThermalEngine( 389): Threshold 1 Action Info[0] : 1497600
I/ThermalEngine( 389): Threshold 2 Action Info[0] : 1401600
I/ThermalEngine( 389): Threshold 3 Action Info[0] : 1344000
I/ThermalEngine( 389): Threshold 4 Action Info[0] : 1305600
I/ThermalEngine( 389): Threshold 5 Action Info[0] : 1190400
I/ThermalEngine( 389): Threshold 6 Action Info[0] : 1094400
I/ThermalEngine( 389): Threshold 7 Action Info[0] : 998400

It seems the frequencies are cut off at 998MHz now...

Nvm, the frequencies still work.
[Moto G Android Development] obvious:
On top of latest cm, had to reboot for changes to take effect then got 16496 in Antutu fwiw. :)
[Moto G Android Development] xheon:
Im feeling my phone a bit more warmer after installing latest build 02/28 not sure if its just me :/
[Moto G Android Development] ares93:
Any chance you could implement som sort of gpu clock adjustment? My phone seems to lock up on occation and I'm 90% sure its the gpu overclock. It doesnt happen with stock kernel and didnt show up until you turned it up to 487. 450 was rock solid.
[Moto G Android Development] SeannyM:
I have actually been having lockups since feb 21's kernel, but the latest changes to the kernel (a lot of reverts) actually fixed it for me. Are you on the latest version? I think the revert commits are in the 0228 build.
[Moto G Android Development] SeannyM:
I just overclocked my GPU to 520Mhz, and the performance is great! Haven't tested battery life yet, but I'm afraid to see how much it will drain :eek: I've decided to take a break from CPU overclocking, but at least we're closer with the thermal engine. Anyways, I am going to be playing around with the GPU overclock, if anyone wants to try it out, I will happily upload my build. Beware if I do upload though, all phones are slightly different and an overclock that works on one phone may not work on another. (meaning your phone may not boot if it can't handle the overclock)
[Moto G Android Development] obvious:
Please do :)
[Moto G Android Development] SeannyM:
How high do you want it? I'm at 550MHz right now, GTA San Andreas finally has zero lag (at least with resolution set to 0). Maybe I can get to 600? I'm sure the battery will be terrible ;) I've only tested while charging currently.
[Moto G Android Development] obvious:
550 to be on the safer side I guess. Cheers.
[Moto G Android Development] SeannyM:
Okay, I'll upload in a bit. I'm just going to mess around a little more first.
[Moto G Android Development] obvious:
A 22% gpu overclock should certainly be noticeable...
[Moto G Android Development] SeannyM:
It is, but it would probably be better if I did it better, right now I just did a quick value change of the highest frequency. I might integrate it better later.
[Moto G Android Development] adinkwok:
link please :D
[Moto G Android Development] SeannyM:
Here is the link for the 550MHz overclock. Please be aware of the following things before using:

This is for testing purposes ONLY. It may not even boot on your phone! If it boots, don't expect amazing results, as it is "messily" implemented. Most of the values are not optimized for this overclock, almost all of them are from the 487MHz overclock. If I took the time to implement the overclock correctly, it would likely have a lot better results. This is mainly to see if your device can handle 550MHz. This is a TEMPORARY kernel, as it will be reverted once you reboot. If it does not boot for you, you can easily fix it by rebooting. Wifi may or may not work, the modules are not included, I have not tested with the 0228 modules.

Anyways, after reading all that boring stuff, go ahead and download the kernel. Do not be surprised when it is not a boot.img. To use it, place it in a directory with adb/fastboot access and boot into the bootloader on your phone. Make sure your phone is plugged in and type:

fastboot boot zImage

Your phone will boot with the 550MHz kernel. When you are done testing, simply reboot your phone to revert back to the normal pink kernel.
[Moto G Android Development] obvious:
Most modules increased in Antutu notably:-

2D 932 -> 948 1.7%

3D 5104 -> 5328 4.4%

Overall score 16496 -> 16845 2.1%
[Moto G Android Development] SeannyM:
How's the battery life? If it's only a bit worse than normal I may make a flashable permanent version and tweak the values to make it work better.
[Moto G Android Development] obvious:
Haven't tested. I'm not much of a gamer. Interested from a technical and "that looks cool" perspective.

The GFXBench T-Rex test is great btw ;)
[Moto G Android Development] SeannyM:
I'm not really a gamer either, I do play games occasionally when I have nothing better to do, and when I'm testing performance. I just want to see for normal usage if it is an issue or if it only decreases slightly faster.
[Moto G Android Development] obvious:
I'll run with it until I next have to reboot. Btw, can confirm Wi-Fi isn't hooked up
[Moto G Android Development] ron580:
It be nice to have another kernel for the moto g to choose from.
[Moto G Android Development] adinkwok:
Okay here's my review. Obvious performance boost in all aspects and overall usage. Battery drains faster even when doing things like surfing the net. When I play Shadowgun Deadzone, it decreases battery a bit faster (10% : 20-30 minutes while running ART is what I had before flashing this kernel) but is not very noticeable. I would like to test a 600 MHz one if you can compile one.
[Moto G Android Development] SeannyM:
It's not another kernel, it's simply the pink kernel with a more overclocked GPU.

---------- Post added at 10:28 PM ---------- Previous post was at 10:25 PM ----------

Good to know battery doesn't take a big hit. I will optimize the values a bit and release a full flashable zip tomorrow with wifi and FM radio modules. I already tried 600MHz, but it started to slow down because I think it was more than the GPU could handle.
[Moto G Android Development] SeannyM:
Here's a full build with 550MHz GPU, I optimized it slightly and included everything to use daily. Flash with CWM like any other release. Tell me how it is, and [MENTION=3545900]pinkflozd[/MENTION] if people find it suitable for daily use, I will make a pull request.
[Moto G Android Development] adinkwok:
It's perfect, I don't really notice any battery drain but my gut is telling me that there is (I honestly don't know anymore). I think that there should be two versions of Pink Kernel released: Performance and Battery. Each with what the title says it has (hence the names).
[Moto G Android Development] myabc:
please, is there a pink kernel flashable from trwp recovery and working for 4.4 kitkat without overclock, optimized for battery life? thanks
[Moto G Android Development] bogante:
Obviosly this is for CM11, right?

Enviado desde mi XT1032 mediante Tapatalk
[Moto G Android Development] adinkwok:
Any ROM in the title