yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] hurtsky:
Add Simpler Version Kernel (more detail please click here)

Simpler Version

Introduction:

This kernel introduce for users that did not want to mess up with the kernel setting and more likely not really good in changing the value or tuneable kernel (hurtsky kernel) thus this version are created for those people. This kernel was tuned in balanced mode, with all default features been enabled and disabled.

Features of this kernel:-

- compiled with Achi Toolchain gcc 5.1

- -O3 and graphite optimization

- Used new hotplug infrastructure from kernel 3.10

- workqueue from kernel 3.10

- timer updates

- enabled Fsync from francisco

- updated Sched/fair structure

- remove alot of logging

- msm_limitter that limit freq at 600mhz during screen off

- complete patches of new louis cache maintenance api

- default governors is zmoove (highly tuned for balanced)

- disable cpu-boost complety (cause too much high frequency)

- tuned LOWMEMORYKILLER from neobuddy

- decrease the amount of time the device waits after entering low power mode to freeze processes by from 5ms to 2ms

- synced with google common update

- disabled alot of debug functioning kernel

- greately reduce overhead of the kernel

- filter WAKEUP that caused from disabling AMBIENT DISPLAY (reduce wakeup)

- and much more patches that i may left out

NOTE: - for those who comes from stable version / others kernel please do dirty flash of your rom before installing this kernel, because this kernel script runs many setting in default at first boot.. thank you

can be download at download tap
[Moto G Android Development] PeterImmel:
thanks a lot [MENTION=4723408]hurtsky[/MENTION]. sounds good.

I guess there wont be a simpler dt2w version? :p
[Moto G Android Development] hurtsky:
yea, no i think since if activated dt2w in default way could bring a problem the Simple user :p so better i make it more simpler without hassle :fingers-crossed:
[Moto G Android Development] OldYellowBricks:
Using this on latest cm nightly since this afternoon (its 2am now where I live) and everything seems to be fine. I have one question:

Is it possible to increase headphone volume by modding/compiling a kernel? Asking for info purposes hehe
[Moto G Android Development] riyosakura:
I got my first reboot using simpler version when using 9gag app on cm12.1 0519.

Here is my lastkmsg

Any suggestion what im doing wrong?

Sorry for my bad english.
[Moto G Android Development] hurtsky:
i feel the headphone volume already high @@ because i always let the volume in the middle. i will add high volume one later :p

nothing wrong, it just report from new hotplug.. its actually old bug that i thought already solved during test season.. btw i try to fix it.. thank you for the bug report
[Moto G Android Development] dark_knight_95:
https://docs.google.com/file/d/0B32CnXc53I8xVVVKR0t0eThjX1U/edit?usp=docslist_api
[Moto G Android Development] drsiddique5700:
was expecting intelliplug hotplug in simpler version but still simpler version is doing great
[Moto G Android Development] hurtsky:
thanks for the logs. i will look around this bug.. it same as simpler version.. hmmm

thanks.. it will be optimize one mpdecision.. i will try to improve more this version.
[Moto G Android Development] methuselah:
Can your grab some info for this thing

This is hotplug developed by nividia. http://xdaforums.com/showthread.php?p=52807169 . Here developer is talking about it. I think simpler version is deserving this if you can have a look... By the way MP decision in latest V1 is working great.
[Moto G Android Development] hurtsky:
i tried look into it, the patches that i could find is out-of-date one.. not really sure to implement that.
[Moto G Android Development] methuselah:
I see

Ok........
[Moto G Android Development] hurtsky:
maybe you can try find the updated one for me.. for now, the patches that i got is dated 2013.. about the stable version, maybe i will remove intelli_plug and change it with new one.. i found an interesting hotplug driver to test it out.. ;)
[Moto G Android Development] methuselah:
i will see what i can do

well i ill try to find whatever is in my ambit. And what is the new hotplug you are talking about btw ?? :silly:
[Moto G Android Development] mattheoh:
Can someone confirm that the last D2W version is the one of 7th may ?

I would like to try it on Euphoria ROM.

Thanks !
[Moto G Android Development] hurtsky:
let's it be a suprise :p i will rebuild stable version and adding new hotplug as experimental progress.. i will post up new build later

yup, that the latest one.. i still not update yet stable version because its already stable..
[Moto G Android Development] hurtsky:
Update Simpler version to V2

Changelogs:-

- rebase kernel based on [MENTION=4480917]Alberto97[/MENTION] kernel base (Audio, WiFi and merged MMI-LXB22.46-33 tag from Motorola) all credits goes to him.

- performance fixes ( use interactive as only governors )

- disable cpu-boost

- enabled simple_gpu in default (sorry, forgot to make it enable in V1 :p )

- enhanced lowmemorykiller from neobuddy - (greately try to avoid lowmemorykiller from killing systemui, contact, and process core)
[Moto G Android Development] hurtsky:
Sorry guys, in simpler V2 ,after 12 hours using it, i spotted some several bugs that effect battery usage.. i will add new sub version to fix this..
[Moto G Android Development] hurtsky:
as promise! update to V3

Changelogs:-

- fix bug in deep sleep

- timer, irq and topology updates

- some cpufreq updates

- more patches > click here
[Moto G Android Development] Niropa:
I was just working on a kernel identical to your simple version (based on Alberto's, only interactive etc) lol, its nice to have a minimal option :)
[Moto G Android Development] aouerfelli:
Trying out the simple one, so far pretty good. But would adding KCAL be okay? I would really like to use cfLumen's KCAL mode.
[Moto G Android Development] hurtsky:
it simple in config, but it not as simple for the sources, all the backport from 3.10 kernel i take long time to test it out before publish it to public ;)

yeah sure, i will add it in next version :D
[Moto G Android Development] OldYellowBricks:
Getting amazing standby battery life on this kernel
[Moto G Android Development] miguelAr52:
v15, or simpler3?
[Moto G Android Development] onlytanmoy:
@ hurtsky>> thanks a lot for this kernel...one request- please can you set SELinux as "Permissive" for the Simpler version. I am currently using Simpler V3 26/5/2015 on my Moto G running FlexOs (LP 5.1.1) and SELinux is being shown as "Enforcing".
[Moto G Android Development] hurtsky:
for security reason, i wont make it in default permissive during bootup the phone.... you can google how to set SELINUX as permissive, there are many way to do it.
[Moto G Android Development] onlytanmoy:
[MENTION=4723408]hurtsky[/MENTION]>> okay mate, can I also flash Kernel V15 7/5/2015 on Moto G XT1033 or I should stick to Simpler V3 26/5/2015?
[Moto G Android Development] hurtsky:
Depend on you, friend.. if you know how to tweak the value of the kernel, go for stable version... if not, more recommended to stay with simpler version
[Moto G Android Development] hurtsky:
Update Simpler Version to V4

Changelogs:-

- Enabled Neon mode

- Add KCAL support for post processing control [v2]

- fix potential memory corruption/leakage

- GPU governors, set conservative governor in balanced mode (more power saving)

- more details patches -> click here
[Moto G Android Development] onlytanmoy:
wow...a new update...going to flash Simpler V4 right away...thanks a lot bro.
[Moto G Android Development] BhavikRB:
master hurtsky, you forgot about Faux Sound ! How a Moto G User can live without Faux Sound !! :crying::crying::crying:

[IMG="Crying"]http://www.folksdaily.com/wp-content/uploads/2014/09/meme-faces-crying-3-288x300.png[/IMG]

--------------------------------------------------------------------------------------------------

kabhi kabhi aate hai

Par

Group

Hila jate hai... :cool::cool::cool:

[IMG="g"]http://media.giphy.com/media/gtoONZQegPnPy/giphy.gif[/IMG]
[Moto G Android Development] amit.lohar:
Please add faux sound if possible..
[Moto G Android Development] grosobart:
thanks

recently downloaded both versions, if I can tomorrow I try to see how they work, thank you very much for your work
[Moto G Android Development] vijayakumarpp:
Iam having a problem with V15 with dt2w feature enabled. Proximity sensor to automatically turn display on and off during calls not working. Only having the problem if the dt2w option is enabled. No problems with the simpler versions and if the dt2w feature is disabled. I checked with RR, Flexos, AICP, Euphoria, Blisspop roms.. So it may not be a rom related issue.
[Moto G Android Development] hurtsky:
are you sure, using faux sound in simpler version? the preset doesn't really work for me, i had problem using it last time..you need to adjust the setting manually and its not really suitable for Simpler policy which is "just flash it". :p

that's normally, i already stated that bugs in 4th post
[Moto G Android Development] plantator:
msms limiter don't work eg try set all cpus min 300 and

cpu0 1,2GHz

CPU1 1,1GHz

CPU2 1GHz

CPU3 600MHz

and max scaling is 600 for all ;)

other thing

set all max to 1GHz but in cpu stats shows that processor scaling up to 1,2GHz,

on optimus kernel there was msm limiter but removed due to problems with it.
[Moto G Android Development] hurtsky:
not really understand, yea i set it 600mhz default for all cpus (during suspend). and max in resume is 1190mhz.. for me, its work fine.

and also, what version did you use?
[Moto G Android Development] plantator:
simplier V4

mayby is there an app that I can check how my cores works? Then i can check is core3 scalling 300-600 that i set or no, but in other way great hob, have good battery life on it;)
[Moto G Android Development] hurtsky:
the easiest way i check up the freq is using freq table in kernel adiutor/3c toolbox(got percore freq), 600Mhz wont be use if msm_limiter is not enabled/not functioning, this is because the hispeed for interactive that i set up is 998Mhz so 600Mhz wont be select out during resume condition and by enabling msm_limiter you will see that there are some usage or % for 600Mhz because this freq only been selected during suspend... yeah sure :D its already tuned for speed and battery, no need to change any setting in simpler version :good: but you still can recommend out what setting good more battery and i will test it out first before publish it for user used.+

edit: okay i got what you means, actually it works but during hotplug the freq got reset. No worries, i already found the fix for this ;)
[Moto G Android Development] plantator:
will w8 for next version;)

on this what I mean: i have set this max cpus on synapse like on screenshot, restart, but in betterbatterystats it shows that proc scalling max to 600, restart againd and same, and i revert settings that cpu0 600, cpu1 787 cpu2 998 and cpu3 1094, restart and then bbs shows max scaling uo to 1094;)

but if you say that got fix will be great;)
[Moto G Android Development] hurtsky:
i see, im not really sure we can set each cpu with different limit freq. Our cpufreq.c not really updated, i did try to update it with some compatibility but some bugs have appears after update it.. but i still try another work around.. i let you test it later
[Moto G Android Development] hurtsky:
In order to differentiate simpler and stable version, i changed the name of stable version to EXTRA version (more features, more tuneable settings)

Changelogs V16

Changelogs:-

- rebase kernel based on [MENTION=4480917]Alberto97[/MENTION] kernel base (Audio, WiFi and merged MMI-LXB22.46-33 tag from Motorola) all credits goes to him

- remove all old hotplug

- use MAKO HOTPLUG as the only main hotplug

- tuned as default as balanced mode between battery and performance

- disable cpu-boost

- enhanced lowmemorykiller from neobuddy - (greately try to avoid lowmemorykiller from killing systemui, contact, and process core)

- use new hotplug infrastructure (3.10.x)

- complete patch of louis cache.

NOTE: PLEASE DIRTY FLASH ROM BEFORE FLASHING THIS KERNEL AS IT USE NEW KERNEL SCRIPT. THANK YOU ;)
[Moto G Android Development] onlytanmoy:
[MENTION=4723408]hurtsky[/MENTION]>> I am quite a n00b mate, please mind explaining how do i do the above step (dirty flash ROM)? I am using TWRP recovery on my Moto G.
[Moto G Android Development] twist3d0n3:
reflash everything you flashed when you originally installed your current rom (so rom, gapps, viper, etc, etc) then flash this kernel.
[Moto G Android Development] onlytanmoy:
@ twist3d0n3>> Do I need to wipe cache/ dalvik after flashing the kernel at the end or just reboot the system? Thanks.
[Moto G Android Development] twist3d0n3:
always do it if you're not sure, it's not going to hurt (just take a while to rebuild the art cache).
[Moto G Android Development] PeterImmel:
Thanks for your work.

Pocket guard doesn't work for me in V16.

(double takes wakes my screen although proximity sensor is covered)
[Moto G Android Development] hurtsky:
first screen off wont work, second screen off will work the pocket guard
[Moto G Android Development] hurtsky:
sorry guys, i need to remove latest version.. i had sudden reboot today after 24 hours using it..
[Moto G Android Development] hurtsky:
thanks to the bugs, because of that i can updates the kernel fully sync with CM latest kernel changes

Changelogs of EXTRA v17:-

- sync with CM latest changes - alot of changes CM already done for next nightlies

- dt2w : readd back suspend power button during screen off ( weird, adding this back make the dt2w more effective during pocket mode )

- revert some patches that bring trouble to me

.
[Moto G Android Development] josip-k:
[MENTION=4723408]hurtsky[/MENTION] do you think it would be possible to bump the kernel up to 3.10 version?
[Moto G Android Development] hurtsky:
possible, but it will really need hard work to do that.. btw, we not REALLY need to go for 3.10.x kernel because 3.10.x more optimize and built for 64bit infrastructure rather than our devices infrastructure which is 32bit.. ;)
[Moto G Android Development] antarix:
[MENTION=4723408]hurtsky[/MENTION] is it possible to remove faux sound?

It causes problems with different audio mods.
[Moto G Android Development] plantator:
In simpler version there isn't
[Moto G Android Development] antarix:
I'm looking for the extra versions. The tunable one's with dt2w.
[Moto G Android Development] hurtsky:
yup, im going to remove it anyway.. because im trying audio mod also.. so in next version im going to remove it.
[Moto G Android Development] antarix:
That's amazing. [emoji482]
[Moto G Android Development] josip-k:
Yeah, but wouldn't it increase compatibility with newer android versions? Like easier to port things and maybie a bit better performance? Did you even try to bump it, and do you think if it was ported, would it be accepted in offical cyanogenmod code?
[Moto G Android Development] hurtsky:
i don't think im had enough knowledge to bump from 3.4 to 3.10.. porting different level of kernel is really hard.. not really, the kernel still need to adjust accordingly to what ROM had and compatibility won't be an issues.. there are still had devices used 3.0.x kernel to running with lollipop.
[Moto G Android Development] josip-k:
Well you could at least try, there are many kernel devs in the Moto G section.. I'm not talking about Lollipop, i'm talking about android versions beyond android M, wich will be harder to port, since android M uses the same APi's and it really won't be a problem, but versions beyond, they will be a problem..
[Moto G Android Development] hurtsky:
i know that you're not talking about lollipop, i just give an example, because the old 3.0.x kernel still can running the latest android version. What we really needed is just a compatible drivers that suit with the android version rather than kernel version. Im not going to try it, because i already tried at another phone before going to this phone.. from 2.6.x kernel to 3.4.x kernel, escalating the kernel version will bring more bugs to drivers and more bugs hunting needs to do, it is really wasting time.
[Moto G Android Development] antarix:
[MENTION=4723408]hurtsky[/MENTION] i have a bug of proximity during call. It doesn't turn on the screen unless the call is ended though it detects touch.
[Moto G Android Development] drsiddique5700:
no such issue here on v17 just tested
[Moto G Android Development] antarix:
are you using dt2w version?

the screen stays black until i or the other party cuts the call.
[Moto G Android Development] hurtsky:
this maybe happen if you turn off the screen and covered the proximity sensor, and that time you cant wake up the phone using power button but you can wake up the phone using double tap (if you not covered the sensor). Do not forget to disable ambient display if youre using dt2w version ;)
[Moto G Android Development] antarix:
ambient display is turned off and even tried to double tap but the screen doesn't turn on unless the call is hung up.
[Moto G Android Development] hurtsky:
Update Simpler Version to V5

Changelogs:-

- rebase kernel base to latest CM kernel sources

- prevent mpdecision from changing the minimum freq

- some lmk updates from motorola

- improve msm limiter policy, note to [MENTION=5127197]plantator[/MENTION] can you test it out and let me know later? ;)

- update msm limiter
[Moto G Android Development] hurtsky:
i see, its not reboot right? give me some dmesg log (easy way to get it is from kernel adiutor at settings tap, make sure you copy it right after you having the bug), maybe i could try hunt it because during my test, i can turn on and off the screen during call..
[Moto G Android Development] antarix:
Dirty flashed gapps and rom.

May be something was wrong with flashing.

It's working now.

Will get dmesg as soon as it happens again.

Edit : it started to do the same again. Here is the log to dmesg.txt

https://drive.google.com/folder/d/0B-HfcNHadXOgdmQtaDNsUVJ4c1E/edit
[Moto G Android Development] plantator:
[MENTION=4723408]hurtsky[/MENTION] as You say I test it;) and:

starting from all cpus min 384 max 998 (synapse) and loking for cpu stats in betterbatterymonitor

first checked ddownscaling in min frequency core by core

when change cpu0 to 300 it shows in BBS that minimal scaling is to 300 so good

when cpu0 back to 384 and change cpu1 to 300 BBS shows that minimal scaling is still 384 so it don't aply

cpu1 back to 384 and try with cpu 2 and 3 same situation minimal scalling is still 384 so msm limiter only aplies to cpu0

and same with overclocking,

change cpu0 from 998 to 1094 it shows in BBS that max core go to 1094 so aplies

revert cpu0 to 998 and change one by one cpu1-3 to 1094 and no changes in BBS always show max 998

also trying checking BBS stats after restart when for eg cpu3 is raised to 1094 but it not scales more than 998

I think I describe it good, if not I will make video if you need it;)

Conclusion setting in msm limiter cpu0 is aplied to all cpus on processor

PS. all cpus set to 384, after restart BBS shows that minimal is 300, changed on cpu0 too 300, apply, next back to 384 appply and BBS shows it good 384

Cheers;)
[Moto G Android Development] hurtsky:
thanks, i will analyze the log... in one time reading, i see nothing wrong.. i will let you know if i saw something not good there..

i see, yeah.. because in my test also its only apply to cpu0, the others cpu getting reset after second suspend activity.. i tried updated cpufreq, but it wont work in our device and just getting sleep of death. Btw, thanks for your conclusion.. :fingers-crossed:
[Moto G Android Development] plantator:
On optimus dev also tries including msm limiter and fails, for me it will be great battery saver if it works
[Moto G Android Development] hurtsky:
i believed it not completely failed in my case/kernel, only we can use 50% of it real functionality.. lock maximum freq during screen off really save cpu usage and power.. the only function we cant use is, to set different minimum suspend freq to each core... i will try more way to do this, i believe we had another way to fix this ;)
[Moto G Android Development] Flashhhh:
On my kernel i also had the same problem. Can't set different frequencies for individual cores. Btw max screen off frequency worked in my kernel too. I removed it because users were clustering the thread with msm limiter bugs.
[Moto G Android Development] sunfire7:
After installing this kernel SELinux mode is still Enforcing :(

AICP ROM
[Moto G Android Development] twist3d0n3:
then change it in synapse to permissive.
[Moto G Android Development] hurtsky:
please use synapse to change it to permissive as recommended by [MENTION=4851254]twist3d0n3[/MENTION]. in next version i will try to set selinux as permissive after late boot.. it will bring some problem if force it in permissive directly during kernel boot up.

i see, i will put on infront post maybe it could avoid those reports ;)
[Moto G Android Development] Mchasard:
Stangely I had troubles with eos ROM ... Several time I encountered the non ability to wake up phone with the double tap.... And all is blocked I have to reboot the device.... I just change with the original kernel of eos ROM and it's OK ... Without double tap cause the kernel doesn't have this feature...

Envoyé de mon Moto G avec XDA Forums
[Moto G Android Development] twist3d0n3:
do you have ambient display wave/pocket mode enabled? if so, i think it's conflicting with custom kernels for some people (myself included).
[Moto G Android Development] hurtsky:
[MENTION=4644796]antarix[/MENTION] [MENTION=3308423]Mchasard[/MENTION] guys, please test out this test build, this dt2w version is completely different from official release.. i also had problem to wake up during call.. please let me know your feedback..
[Moto G Android Development] Mchasard:
Many thanks hursky I just install it and will report later in the day....

Envoyé de mon Moto G avec XDA Forums
[Moto G Android Development] hurtsky:
sure, let me know ya later. i already tested it and i had no more problem during call sesion. I satisfied with this new patch as no need to patch pause power key during screen off ,prox covered and without it, pocket mode nicely effective.
[Moto G Android Development] antarix:
It's working now. No bug of screen stuck during call. It goes off and turns on.
[Moto G Android Development] hurtsky:
good to hear that, and also new patch also fix accidentally touch activity during screen off (known as ghost touch).. no more accidentally/randomly open apps during screen off.. hope you guys like it for official release :D
[Moto G Android Development] antarix:
i think i'm loving it even before testing it because the main problem is gone and happy to know new security is in:)
[Moto G Android Development] hurtsky:
thanks for loving it.. if found any bug on that test build please let me know yea.. :)
[Moto G Android Development] antarix:
Sure i will inform you with logs. Cheers[emoji482]
[Moto G Android Development] Mchasard:
So after a day the new build is OK also for me ... Many thanks I goes on to use your kernel

Envoyé de mon Moto G avec XDA Forums
[Moto G Android Development] aouerfelli:
I know this is kind of a nuisance but before you compile v18, could you please re-add KCAL? It really helps me out.
[Moto G Android Development] hurtsky:
yeah, good to hear that :D

it is okay, i thought i already add it in extra version, but when you said about this i checked back and i just know i not yet implement it back.. thanks for point it out ;)
[Moto G Android Development] amit.lohar:
Can you please add westwood tcp congestion??
[Moto G Android Development] Siekil:
It already there, check out with adiutor ot synapse
[Moto G Android Development] amit.lohar:
I have checked bro. Its showing only reno and cubic. Using extra v17dtw
[Moto G Android Development] antarix:
Check post number 667 for the latest test which foxes a bug while in call.

[MENTION=4723408]hurtsky[/MENTION] are you facing touch detection while on call? Thought the screen is off but the device detects touch and opens notifications with v18test.