yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] michal89chz:
so it is working or not? CPU OC?

Someone know something about GPU freq in this kernel?
[Moto G Android Development] pinkflozd:
new version released

Removed OTA Survive script for now *

Synched with dhackers kernel

CPU Bus Overclock 566mhz

AIO Filesystem Optimizations

some more patches

* Need to rewrite the script so we always have a fresh ramdisk when ota flashes
[Moto G Android Development] wijiji:
No need to reflash the entire rom before right? (I using the 20140317)
[Moto G Android Development] pinkflozd:
no need to reflash the rom, but it will work on bulds released from the 18th onward
[Moto G Android Development] mccbrandon:
No WiFi on pac rom latest with pink kernel latest...

However phone feels a lot quicker, don't know if that's the updated pac or the kernel but I can definitely feel a difference
[Moto G Android Development] SeannyM:
There is no need to have a fresh ramdisk for OTA, the script backs up kernel and ramdisk as is and puts them back without modifying. Nevermind, I think I see what you are saying, how when you flash an update with new ramdisk changes you need a fresh ramdisk. Maybe we could modify the install script to back up the stock ramdisk somewhere (/data/pink would be a good spot) and then it could use that ramdisk for every new installation. If there was already a ramdisk saved, it would not overwrite it. Maybe I'll work on that today.
[Moto G Android Development] pinkflozd:
PAC probably didnt yet merged the latest cyanogen commit

yea or we could try to use the post restore part of addon.d and copy in it mkbootimg.sh & repack-ramdisk.sh from the anykernel so its like a anykernel reflash
[Moto G Android Development] SeannyM:
I am working on the scripts now, I'll shoot you a PM with the finished product.

Edit: won't be done today
[Moto G Android Development] wijiji:
So I cant use the Last update, Im on Liquidsmooth
[Moto G Android Development] bogante:
Can i use the kernel in last CM11? (20140319)
[Moto G Android Development] syrkles:
Running good on mokee nightly 32014 build
[Moto G Android Development] mccbrandon:
Is there a thread for mokee?
[Moto G Android Development] okaryn:
No problem with latest PAC source (this morning). Wifi is working.
[Moto G Android Development] rr46000:
No

just google mokee opensource and download the rom from downloads section

or just click the link

http://download.mfunz.com/?device=falcon
[Moto G Android Development] sniper.12:
Works perfect on the Ehndroix Rom. Thank you!

Sry fo the question but... what is the best governor for smoothness and good battery life? Also the IO Sheduler?

thanks :D
[Moto G Android Development] okaryn:
I'm using the combination of WestWood / Fiops / IntelliActive and it's very smooth with no battery draining (on PAC-Man ROM)
[Moto G Android Development] syrkles:
Y does antutu force close on latest kernel??
[Moto G Android Development] SeannyM:
[MENTION=3545900]pinkflozd[/MENTION] about the anykernel restore script, we will have to have mkbootimg and other commands stored on the phone somewhere. I was thinking either /system/addon.d or /data/pink. Which one do you want me to use? I can probably set this up pretty easily, just not in the next few days because I am likely going to be busy.
[Moto G Android Development] pinkflozd:
Best would be to use /data/pink

Btw no hurry mate
[Moto G Android Development] twist3d0n3:
since you seem to know something about tcp congestion etc, is there any real difference between say, cubic, westwood etc? i haven't noticed anything

/sorry for slight OT
[Moto G Android Development] Haggster66:
Cubic is a general TCP congestion algorithm that gives an ok performance in most situations. Westwood and Veno are the two only algorithms that are optimized for wireless networks since they differentiate between packet loss caused due to delay and packet loss caused by connection interference (or just poor connection quality). Westwood is a year older than Vegas, but the algorithm used nowadays is actually Westwood+, which is a kind of a bug fix since the original algorithm was flawed. I did a couple of tests with bandwith test apps and Veno gave a slightly better performance than Westwood. 99.9% of all custom kernels use Westwood as a default though and that's why it's great that Pink is not sheepishly following that pattern, making it stand out from the mass since it's using Veno as default.

However the differences between Cubic, Veno and Westwood are not big, performance wise... however all if them should give better performance than either older, obsolete algorithms or highly specialized ones for high delay networks or high speed wired networks. So since you're using a phone you should also use an algorithm that's adjusted to wireless networks, simple logic really.
[Moto G Android Development] MrKra:
There is something with the GPU which forces Antutu to close.

I experienced this weeks ago on all kernels and all Roms.

But it happens after a few hours runtime !?
[Moto G Android Development] wijiji:
Same problem with AnTuTu
[Moto G Android Development] SeannyM:
Bump!
[Moto G Android Development] SWTR:
In next release, maybe you can implent the ram bug fix from this thread?

http://xdaforums.com/showthread.php?t=2685338
[Moto G Android Development] MrKra:
Does ZRAM work on newest kernel?

The app "Zram Status" exits and i am confused.

"/sys/block/zram0/disksize: open failed

ENOENT (no such file or directory)

(using PACRom)
[Moto G Android Development] Geordie Boyo:
This is the 2nd time in a few days when dirty flashing the latest nightly builds of CM11, then flashing the kernel 20140319 release on top, when phone has rebooted, there is no Wifi connection at all. Fortunately i had a nandroid backup.

Anyone else had this issue ?
[Moto G Android Development] SeannyM:
Works fine for me.

Sent from my Moto G
[Moto G Android Development] xtugap:
I had The same with liquid_smoth 3.0. I delete the ota survive file and flash the ROM and wi-fi start working (with stock kernel).
[Moto G Android Development] Geordie Boyo:
The OTA survive file?
[Moto G Android Development] matmutant:
read pink kernel FAQ ;)
[Moto G Android Development] SeannyM:
I feel like a new release should come out since there are new CM kernel changes. I haven't flashed the newest build yet but it would probably be best.

Sent from my Moto G
[Moto G Android Development] vasili_defy:
[MENTION=3545900]pinkflozd[/MENTION] In ops you have stated cortex a7 optimized linaro , since desire also has a7 can this be also used in desire?

Sent from ISS
[Moto G Android Development] SeannyM:
[MENTION=3545900]pinkflozd[/MENTION] the github hasnt been updated for some time, not even for the new CM patches!? Its completely understandable to have a break, but it's always nice when we know about it ;) I may merge the latest commits myself and make a new build if I hear nothing back soon.

Sent from my Moto G
[Moto G Android Development] pinkflozd:
yes if its a CortexA7 the optimizations could be used, both Makefile optimization and the custom toolchain

i'll update it today, was a bit busy with my boat, and since there were no big changes i didnt updated the kernel
[Moto G Android Development] adizz4:
I get random reboots on wake. Using Cm11 nightly on xt1033
[Moto G Android Development] OurJerry:
Great kernel. Can I undervolt the 1,4 ghz with stock values?
[Moto G Android Development] pinkflozd:
i left the stock values stock for now, will be adding 192mhz if i notice any improvement while testing, the freq's are funky on this device

next releases will target to save some battery
[Moto G Android Development] ricola1989:
Compatible with boost/CDMA, xt1031?
[Moto G Android Development] mattrb:
Moto G radio Is independent to kernel. Yea
[Moto G Android Development] SeannyM:
The overclock to 1.4GHz does not give any boost, tested with apps that show FPS and they showed no sign of change. From my overclocking experience, it is not enough to have the kernel point to the new frequencies you must also usually set the maximum frequency somewhere. My previous 1GHz device which I overclocked to 1.2GHz had to have the added frequencies along with

[B]arch/arm/mach-msm/Kconfig[/B]

config MSM_CPU_FREQ_MAX
int "Max CPU Frequency"
depends on MSM_CPU_FREQ_SET_MIN_MAX
-	default 1008000
+	default 1228800

and

[B]include/linux/cpufreq.h[/B]

-#define MAX_FREQ_LIMIT	1008000
+#define MAX_FREQ_LIMIT	1228800

however it is more than likely that this must be set in a different place/manner for Moto G since it is an entirely different CPU. I do know however that when I did not make these changes the overclock also had no effect. When these changes were committed, the overclock improved performance.
[Moto G Android Development] pinkflozd:
yes overclock is not working :S

but a new version is aviabile

IF YOU INSTALLED THE 20140210 VERSION PLEASE UPDATE, THAT VERSION HAS A INTELLIPLUG BUG

Linaro GCC 4.8.3 O3 Compiled

Intelliplug Bootup FIX

Battery life tweaks

PowerSuspend lots of new features to improve battery (enabled by default)

Adreno Governor fixes (aviable governors: ondemand, powersave, performance, simple_ondemand, adreno-tz - default)

Anyone has any info on GPU governors?

some more patches
[Moto G Android Development] BachuArg:
I´ve just flashed it on PA. Works perfectly!

Do I need Faux App to be able to use swipe or tap to wake?

Thanks
[Moto G Android Development] kellerman40:
Can you change the frequencies using CM performance settings? Or you have to use faux app or some other tool? Changing the kernel affects the bootloader or not?
[Moto G Android Development] OurJerry:
Ok I installed it, I hope the battery tweaks help a little cuz it was a little less then default CM kernel yesterday.
[Moto G Android Development] anerik:
Built it from source with ls and works like a charm. linaro and o3. Just a question, how did you enable intellidemand? Did you use all faux commits for it or added it manually??
[Moto G Android Development] k-kuchen:
What about free apps like TricksterMOD and Kernel Tuner?
[Moto G Android Development] SeannyM:
I have come across a problem in this kernel. By default, the available system RAM is 882MB. This kernel reduces this to 879MB. I took a look at the code and found the problem. The way logging RAM is implemented now is the size of the logcat multiplied by four since the size of the entire logcat is given to each separate logging device.

DEFINE_LOGGER_DEVICE(log_main, LOGGER_LOG_MAIN, [B]CONFIG_LOGCAT_SIZE[/B]*1024)
DEFINE_LOGGER_DEVICE(log_events, LOGGER_LOG_EVENTS, [B]CONFIG_LOGCAT_SIZE[/B]*1024)
DEFINE_LOGGER_DEVICE(log_radio, LOGGER_LOG_RADIO, [B]CONFIG_LOGCAT_SIZE[/B]*1024)
DEFINE_LOGGER_DEVICE(log_system, LOGGER_LOG_SYSTEM, [B]CONFIG_LOGCAT_SIZE[/B]*1024)
DEFINE_LOGGER_DEVICE(log_kernel, LOGGER_LOG_KERNEL, 256*1024)
DEFINE_LOGGER_DEVICE(log_kernel_bottom, LOGGER_LOG_KERNEL_BOT, 64*1024)

Each time CONFIG_LOGCAT_SIZE is used the entire size of the logcat is removed from the available RAM and assigned to logging. To fix this, I have made up a little patch.

[B]drivers/staging/android/logger.c[/B]

[COLOR="red"]-DEFINE_LOGGER_DEVICE(log_main, LOGGER_LOG_MAIN, CONFIG_LOGCAT_SIZE*1024)
-DEFINE_LOGGER_DEVICE(log_events, LOGGER_LOG_EVENTS, CONFIG_LOGCAT_SIZE*1024)
-DEFINE_LOGGER_DEVICE(log_radio, LOGGER_LOG_RADIO, CONFIG_LOGCAT_SIZE*1024)
-DEFINE_LOGGER_DEVICE(log_system, LOGGER_LOG_SYSTEM, CONFIG_LOGCAT_SIZE*1024)[/COLOR]
[COLOR="lime"]+DEFINE_LOGGER_DEVICE(log_main, LOGGER_LOG_MAIN, 64*1024)
+DEFINE_LOGGER_DEVICE(log_events, LOGGER_LOG_EVENTS, 32*1024)
+DEFINE_LOGGER_DEVICE(log_radio, LOGGER_LOG_RADIO, 32*1024)
+DEFINE_LOGGER_DEVICE(log_system, LOGGER_LOG_SYSTEM, 64*1024)[/COLOR]
DEFINE_LOGGER_DEVICE(log_kernel, LOGGER_LOG_KERNEL, 256*1024)
DEFINE_LOGGER_DEVICE(log_kernel_bottom, LOGGER_LOG_KERNEL_BOT, 64*1024)

Aside from restoring the default 882MB, my patch will also add an extra ~1MB making the total available system RAM 883MB. I have used these values on a few previous kernels I have compiled with no ill effects. The logcats will still work as expected and we will gain some RAM! I hope my patch will be committed to the kernel, right now logcat is getting too much RAM.
[Moto G Android Development] anerik:
That's awesome! Not too much gain but still. On a commiting side, the kernel still lacks some of the official dhacker commits:

https://github.com/razrqcom-dev-tea...mmit/a1a84092c2abbb6a81f47c1999e8d94af09a9f33

https://github.com/razrqcom-dev-tea...mmit/6f3f7a23ee682a87b4382f9e74328caccde35848

https://github.com/razrqcom-dev-tea...mmit/37bcf16f0077399c1bebc90a1976455f7ce41d8d

Cherry picked these three and built with no issues
[Moto G Android Development] Cameron581:
overclock doesnt work cause you still have values set at no....
[Moto G Android Development] SickBeast:
Will this kernel work on the GPE roms? Do we have to manually overclock it using trickster? Will it hit 1.6ghz like the faux kernel does?
[Moto G Android Development] denzel09:
This is not for stock man ;)
[Moto G Android Development] Alchedin:
Reply on the red text

Some tablets run on an so called 'fantasy' governor which in my opinion was both speedy and battery friendly altogether. Not much info about it though, but then again maybe I'm not looking at the right places. :o

I can perhaps extract it from my tablet if it has the governor and perhaps you (guys) can take a look? It might have some positive effect on phones as well :fingers-crossed:
[Moto G Android Development] pinkflozd:
thx mate. i usualy reclaim ram from loggers but forgot this time ... commited your change

we dont need the defconfig cherry picks as i use a different defconfig

cherr-picked the vibrator commit though

if you have any ideas be try to get it working a and make a pull request if you get it working, i will leave overclock resting for now as i dont get it
[Moto G Android Development] SeannyM:
dhacker has released a new build with some new kernel commits. I think it would be best if these commits were cherry picked and a new release made.

Sent from my Moto G
[Moto G Android Development] pinkflozd:
Yes already working on it, have to test a few more fixes...
[Moto G Android Development] pinkflozd:
Can you try to get a bug report? Look in the second post
[Moto G Android Development] pinkflozd:
new version released

Linux 3.4.84

synced with dhackers kernel

Ram Bug fix

Dynamic management of timer slack

Use the power efficient workqueue for delayed powerdown

AbyssplugV2 CPU governor (needs tuning)

some more patches
[Moto G Android Development] diego88it:
Will it survive at OTA updates?
[Moto G Android Development] pinkflozd:
no, i removed the OTA survival for now, need to rewrite the script, you will need to reflash the kernel after OTA's

p.s. i'm tryng to get Kernel 3.10.x working, keep the fingers crossed guys :P
[Moto G Android Development] MaLiXs:
I think i'm gonna try this one thank !!!

think i'll wait a update of slim ... strange video glitch instead of beautiful slim bootscreen :P
[Moto G Android Development] adizz4:
Here's the report, don't know if its of any use as its from the previous version.
[Moto G Android Development] Pir4t3:
does it support voodoo sound ?

i hope so :)

thanks
[Moto G Android Development] MaLiXs:
Everytime I reboot my device the cpu reset to Oc freq .... There a way to let it run at only 1.2 ?

Envoyé de mon Moto G en utilisant Tapatalk
[Moto G Android Development] SeannyM:
In performance settings check set on boot...?

Sent from my Moto G
[Moto G Android Development] MaLiXs:
All case set on boot are checked

Edut : it seem to work with Trickster

Envoyé de mon Moto G en utilisant Tapatalk
[Moto G Android Development] raulillo88:
Same thing happens to me, but not neccesary with a reboot. I don't know what is the problem because set on boot is on and performance setting of CM menu off

BTW I notice that intelliplug drain much more battery than mpdecision
[Moto G Android Development] the_hustler:
I am on GPE Moto G running stock/rooted. Will it be safe to flash this kernel?
[Moto G Android Development] bogante:
This kernel is not for Stock
[Moto G Android Development] MaLiXs:
Yeah there have something very strange with the max and min freq that will not stay at selected value...

Envoyé de mon falcon en utilisant Tapatalk
[Moto G Android Development] Kai Disobey:
Yesterday my Battery had 75%, I installed the new Official SlimKat after that, I made a backup and installed Rom again with the pink kernel,

and did a backup again.

Now I have 8% Battery and over 5h Screen on time. Thats awesome, really great Kernel.

Thank you [MENTION=3545900]pinkflozd[/MENTION], dobro rad :good:
[Moto G Android Development] MrKra:
I had this problem too.

there were two background tasks which set the frequency to different values ;)
[Moto G Android Development] pinkflozd:
I will take a look at the frequency persistance after rebooting , I'm currently reinstalling the system with a new hardware raid so I'll need a few days.

It's happening only on CM?
[Moto G Android Development] Kai Disobey:
Is this Kernel Stock overlocked to 1593mhz ??? I set it now on Boot to1190mhz.
[Moto G Android Development] SickBeast:
Can someone please run geekbench 3 at 1.6ghz and let me know the single threaded score? I get about 350 points at 1.2ghz. I'm trying to see if the overclock works. With the faux kernel my scores are the same as stock.
[Moto G Android Development] MrKra:
On every Kernel and every freq above 1190 the scores are around 350/1190.

Overclocking doesnt work right now on Moto G
[Moto G Android Development] :
what option there is to enable a smooth functioning of the double tap to wake?

after 1 minute, which stands off no longer responds to any commands
[Moto G Android Development] SickBeast:
I wonder if we ask Motorola if they would tell us what is going on. This is not normal. Guys like faux have made overclocking kernels for many other devices and they do not exhibit this behavior. I have a feeling that Motorola has locked things down at the hardware level.
[Moto G Android Development] MaLiXs:
Cm and slim i have tested som kernel tweak app too

I would also like to say that for me it impossible to listen music with this kernel. When screen goes off my music will start skippigng randomly. This issue is not on slim stock Kernel and stock with faux

Envoyé de mon falcon en utilisant Tapatalk
[Moto G Android Development] twist3d0n3:
which music player are you using?

i use poweramp on pacrom with pink kernel and don't have this issue.
[Moto G Android Development] MaLiXs:
I also use poweramp ... Perhap it can be caysed by Bluetooth (im using track air by sol Republic)

Envoyé de mon falcon en utilisant Tapatalk
[Moto G Android Development] twist3d0n3:
i use wired headphones so it's entirely possible.

have you tried upping the poweramp audio thread priority and buffer size? might help
[Moto G Android Development] MaLiXs:
i dont think it related to poweramp config since I use the same in stock, stock + faux and slim stock kernel
[Moto G Android Development] SWTR:
Thank you for this great Kernel!:)
[Moto G Android Development] rr46000:
Wifi

wifi not working on crom

everything else fine

c-rom(flashed over retail gb)

XT1033

just trying
[Moto G Android Development] SWTR:
Do we need to implent this new Ram bug fix into the kernel?

http://review.cyanogenmod.org/#/c/62091/
[Moto G Android Development] robt77:
Looking at it, that fix is in the frameworks/base not in the kernel, so if it works it would need to be implemented at ROM level not in the kernel. But it looks promising.

Edit clearly it will be in the next CM nightly, so time will tell if it has worked
[Moto G Android Development] SeannyM:
Im juat wondering why you call it stock GB, gb is gingerbread. Stock Moto G is jb (jelly bean) or kk (kitkat).

Sent from my Moto G
[Moto G Android Development] mccbrandon:
Great Britain ROM I think
[Moto G Android Development] MaLiXs:
Yes you are right

Envoyé de mon falcon en utilisant Tapatalk
[Moto G Android Development] Geordie Boyo:
Quick question, does this kernel cause the rom leak bug on CM11 rom?

Reason I ask is that I've had this issue when using the build or thereafter where the leak was "fixed" having flashed the pink kernel.

After flashing CM11 again, but sticking to the built-in kernel from CM11, it may appear the leak has gone, after not using the pink kernel for 3-4 days.
[Moto G Android Development] adizz4:
The ram leak is a ROM issue and not kernel related akaik
[Moto G Android Development] chetanya95:
Does minimum frequency goes to 192mhz for everybody.. Because previously it used to be just 300mhz.. Please confirm
[Moto G Android Development] chetanya95:
Using PacMan Rom
[Moto G Android Development] akiaki1:
192 is also for me on cm11, on another note, I dont think usb fast charge is working, I can still connect to the phone and charging is slow, can anyone confirm if it works? I am using cm11 nightly
[Moto G Android Development] deej_roamer:
GB is Global

I have a friend in moto Service Center to confirm that GB is Global no GingerBread, no Great Britain!
[Moto G Android Development] SeannyM:
Its supposed to go to 192mhz. It's underclocked to save battery in standby.

Sent from my Moto G
[Moto G Android Development] mccbrandon:
Look at the system version, retail GB , retail great Britain
[Moto G Android Development] deej_roamer:
I think you are right, when I installed retail.gb default language of English UK and moreover my friend said gb is gingerbread today so his words not to be considered
[Moto G Android Development] SeannyM:
There are some new CM kernel updates related to media-caf-new.

Sent from my Moto G
[Moto G Android Development] pinkflozd:
i'll get them in, will probably release a new version today, with a big f2fs update
[Moto G Android Development] pinkflozd:
sorry guys for no release yesterday, i'm trying to get the RealTime kernel patches in, i'm half way done (all together more than 400 patches)

hopefully i'll finish it today
[Moto G Android Development] akiaki1:
Can anyone verify that usb fast charge is working with cm11 rom and this kernel? It isn't working for me
[Moto G Android Development] Kai Disobey:
It works in SlimKat .

Gesendet von meinem falcon mit Tapatalk
[Moto G Android Development] myctek:
Thanks for the great work!

LCD calibration would also be a welcome feature! I've noticed whiter whites by tweaking some values in Faux's kernel. Hope to see this feature in future builds! Cheers, mate! :highfive:
[Moto G Android Development] SeannyM:
[MENTION=3545900]pinkflozd[/MENTION] the kk-rt branch, it's stable, right? I haven't made a new build for a while, but I feel like now is a good time because without those CM kernel patches the camcorder is broken and it's bugging me because if I ever need it, maybe it should work ;)
[Moto G Android Development] pinkflozd:
use the f2fs branch, the RT didnt worked out
[Moto G Android Development] pinkflozd:
btw new version aviabile

huge f2fs update from linux 3.15

Color Calibration

Removed jRCU

Compiled with O2 to save 2MB of memory

Linux 3.4.85

ZSWAP optimizations

some more patches
[Moto G Android Development] raulillo88:
Any software to calibrate color or is calibrated without doing anything?

Enviado desde mi Moto G mediante Tapatalk
[Moto G Android Development] pinkflozd:
you can use trickster to calibrate the colors, haven't calibrated them myself (using stock), just tested if its working
[Moto G Android Development] -NickHalden-:
Sir, Does it work on cm11 dual sim with both SIMs working?
[Moto G Android Development] killerBRs:
This Kernel WORKS With "Tweaky ROM"? ( http://xdaforums.com/showthread.php?t=2702540 ) ?
[Moto G Android Development] SeannyM:
No, Tweaky is stock-based. This is for AOSP-based (open sourced) ROMs.

Sent from my Moto G
[Moto G Android Development] killerBRs:
Carbon ROM And EHNDROIX V Are Supported?
[Moto G Android Development] SeannyM:
Is AOSP-based. This kernel will work.

Sent from my Moto G
[Moto G Android Development] killerBRs:
Ok.... thanks....;)
[Moto G Android Development] killerBRs:
Carbom ROM Doesn´t WOrk..

"Telephone Stopped, ??-Aplication Stopped"..

I Install Kernel First, or ROM?

Carbon

IS BASED on AOSP!
[Moto G Android Development] SeannyM:
Ive never used that rom, I cant help.

Sent from my Moto G