yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] thracemerin:
I just realized I made a stupid error, I didn't activate init.d support, so having these interfaces is great but you must use trickster or similar kernel control app for the settings to actually be applied on reboot, I will solve this problem and re-upload test2 momentarily.

Edit: situation resolved, if you downloaded test2 in the brief period between when I uploaded it initially and deleted it (you can check if it matches the new MD5 or not), I would recommend downloading it again.

Edit2: in order to get init.d support you must have busybox installed to /system/xbin and create a directory in /system/etc named 'init.d'. all init.d scripts must have permissions (rwxr-xr-x or 755)
[Nexus 4 Android Development] nibla101:
Faux sound with power amp is a nice addition since the stock volume is so painfully low, its currently a must have for me with this device when im traveling :fingers-crossed:
[Nexus 4 Android Development] thracemerin:
Already in the pipe, I'm just of the belief that it's easier to debug things if I push out smaller incremental changes than one huge merge of everything.
[Nexus 4 Android Development] Sierra35:
Tested your kernel for 2 days, phone did not go into deepsleep. Had installed in stock Rom, wiped cache and dalvik. So moved to hellscore kk

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Android Development] SkyBeam2048:
Right now there seem to be some issues with Google services preventing deep sleep. Check Settings => Battery. You might see "Google Services" on top of the list an details showing high "Keep awake" time. This is not kernel related but rather an issue with Google services at the moment.

Actually I had the same issue and it stopped automagically somewhen mid of the day yesterday. So you might re-try m+ kernel as the cause for your deepsleep issue might not be the kernel.
[Nexus 4 Android Development] thracemerin:
http://www.androidpolice.com/2013/1...lay-services-seems-to-be-a-battery-hog-today/

Doesn't seem to be happening to me, but lots of people are reporting this problem on multiple platforms, so it's not kernel related, if it's fixed by switching kernels that's likely a coincidence.
[Nexus 4 Android Development] thracemerin:
Test 3 is now available!

See post 1 for info.

Happy Flashing! :victory:

Note: Faux Sound was supposed to make this version but somehow I screwed it up, so I will get that sorted and probably push that tomorrow.
[Nexus 4 Android Development] apatal:
Test 3 working great, bud. Looking forward to faux sound control and more optimizations. Thanks for sharing your work! :)
[Nexus 4 Android Development] thracemerin:
Getting closer to Beta, Test 4 is now available.

Changes

Dynamic fsync

Faux Sound including PowerAmp

Happy Flashing! :victory:

Note: I don't own the Faux Sound app, it appears it's working to me but if someone with the app could confirm for me that would be excellent.
[Nexus 4 Android Development] apatal:
Volume boost! Yesss! :D
[Nexus 4 Android Development] iPwn_:
Test 4 working like a charm :).

One question...Is the Simple governor enabled by default?

I'm not having any issues with deep sleep.
[Nexus 4 Android Development] thracemerin:
Yes, simple governor is the default.

If you want to switch it back to ondemand, do the following:

echo 'ondemand' > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/pwrscale/trustzone/governor
[Nexus 4 Android Development] nibla101:
I can't get the faux sound to work, no change in volume even when maxed out, I'm on raskat rom with poweramp as player. Is it just me?
[Nexus 4 Android Development] thracemerin:
I never notice a big difference even on Faux kernel, so I'm not the best person to judge whether or not it's working, if someone else can confirm that it is or is not working that'd be great.
[Nexus 4 Android Development] tlf55:
Hi i've a question, why when i put 1350mhz for max cpu speed in trickster mod , it only lock the first core ? Core 2-3-4 still goes up to 1500mhz ..

Maybe i did something wrong ? Can someone help me ?
[Nexus 4 Android Development] hamedunix:
I am on stock 4.4 with everything stock except rooted and unlocked bootloader. Can I flash your kernel via booting into custom recovery?
[Nexus 4 Android Development] thracemerin:
This kernel still uses mpdecision which overrides the CPU settings in trickster, I'm working on adding hotplug for the next test version.

At the moment, just fastboot, flashable zips coming soon.
[Nexus 4 Android Development] tlf55:
Please just leave mpdecision it's very fine ! Or if you add a hot plug put it as optional ..

By the way I have successfully put the limit to 1350mhz you have to put it on trickster and enable the set on boot then reboot your phone :) it makes your limit frequency and doesn't go over it ! Even with mpdecision as I said !

Mpdecision is a really great hot plug ! The stock kernel is very fine but just needed to have some tweak as your test kernel does (undervolting, GPU governor, ..) I thing the only thing missing is the C state tweaking as faux has in his kernel (c0,c1,c2,c3)

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] pincakez:
maybe i am dreaming but the battery life is getting better after flashing test 4 !

good work
[Nexus 4 Android Development] thracemerin:
Test 5 Posted (boot6.img)

Changes

Updated Faux Sound to v3 (Thanks faux123)

Hopefully this will fix some of the issues people were having with Faux Sound support, please let me know.

Assuming this goes well, the next release will be 0.1.0 :D

Happy Flashing :victory:
[Nexus 4 Android Development] nibla101:
Sound control is now working as expected :)
[Nexus 4 Android Development] thracemerin:
Good to hear.

On a completely separate topic, I know there are those out there who want auto hotplug back because of the tuning options and potentially slightly better battery life, and there are those who want to keep mpdecision because it's smoother and just works, so unofficial poll, mpdecision or auto hotplug? (no, I will not entertain requests for franco hotplug, intelliplug, stratosk's dynamic hotplug, etc... this is a one or the other type question)
[Nexus 4 Android Development] apatal:
My vote: mpdecision
[Nexus 4 Android Development] azrash:
If the potential battery saving of the hot plug is negligible or very minimal, I am all in for mp decision. I think last time, during 4.2, I ran the hot plug at 1.4 Ghz max and 0.9 Ghz as the touchboost. Didn't do any testing on the battery usage but I doubt it'll be significant at that setup.
[Nexus 4 Android Development] Kocai:
mpdecision.
[Nexus 4 Android Development] snak3ater:
How about including mpdecision & auto hotplug both at the same time?

People would be having a choice there.Selecting their preferred option :)

If this thing is not possible,then it's okay
[Nexus 4 Android Development] thracemerin:
I suppose it might be possible to have both, co-existence of multiple hotplug routines sometimes proves problematic, but I'll think about it at least :highfive:
[Nexus 4 Android Development] snak3ater:
So far i've seen this thing in Faux kernel only..Having mpdecision & intelliplug :)

Most kernel devs try to get rid of mpdecision & implement their own hotplug..I guess it's because of the same reason that you just said..If it's problematic,then it's okay..Do what is easy for you to implement..I would prefer auto hotplug :)
[Nexus 4 Android Development] ak:
Mpd and others hotplug drivers can coexist ...

there could be problems when you go to overclock the kernel as with the original drivers is not possible to limit the maximum frequency of the CPU.
[Nexus 4 Android Development] tlf55:
For me its mpdecision that would stay the best ! It work very good and with the capacity of UV it's still very battery friendly :)

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] farhanito:
CIFS support (that works).
[Nexus 4 Android Development] Ace42:
Auto plug, and the one faux uses on nexus 5.

Sent with Virtue
[Nexus 4 Android Development] iPwn_:
Are there any changes to the kernel in KOT49E or can I safely flash one of the tests to 4.4.1?
[Nexus 4 Android Development] thracemerin:
It seems to be working fine on 4.4.1 for me, but sources haven't been released so I can't say there aren't changes, nothing that breaks anything obvious though.
[Nexus 4 Android Development] tlf55:
Does this kernel fit with lastest CM11 nightly ?
[Nexus 4 Android Development] thracemerin:
Unlikely, they use a completely different kernel branch.
[Nexus 4 Android Development] tlf55:
So is it possible to you to make a second version of the test 5 for CM ? I like your kernel the way it is ! For me it doesn't need any change ! it would be great to make it available for CM too .. :angel:
[Nexus 4 Android Development] thracemerin:
I'll think about it.
[Nexus 4 Android Development] thracemerin:
Sources for 4.4.1 were released: https://android.googlesource.com/kernel/msm/+/android-msm-mako-3.4-kitkat-mr1

I'm building a new version now, will release it shortly if it boots when I'm done.
[Nexus 4 Android Development] thracemerin:
m_plus version 0.1.0 released! We're now in Beta!

Changes

Enabled Krait Retention for Mako (thanks faux123)

Updated to Google's 4.4.1 sources (thanks Google)

Going forward I will be releasing flashable zips. Zips with names ending in _any are any kernel versions should should work on any ROM even those with modified ramdisks, zips with names ending in _rd will be packed with the stock ramdisk and are for those running pure stock who want to be able to have init.d support and insecure ramdisk.

Note: If you were already on the test builds beyond test2, you can flash the anykernel version since you already have the modified ramdisk installed.

Happy Flashing :victory:

Edit: something strange is going on with the uploader for XDA right now, here is a temporary mirror: Removed, use download tab version

Edit 2: I have only tested this on stock KOT49E, it should work on all KOT49E based builds, it may not work on older KRT builds I'm not sure.

Edit 3: If you are on pure stock and want the insecure ramdisk/init.d support, flash test 5 in fastboot first, I will release an _rd version once the new factory images are posted.

Edit 4: Thanks to bitpushr the uploader is working again so the file is attached to the download tab, temporary mirror removed.
[Nexus 4 Android Development] tlf55:
Thanks ! :)

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] thracemerin:
Still won't work on CM, just to warn you.
[Nexus 4 Android Development] tlf55:
Yeah i know ! I won't go to CM until you merge your kernel for CM :D Love your kernel so much haha :)
[Nexus 4 Android Development] arief347:
New kernel is awesome with latest slimbean 4.4.1 .. Thank you dev..
[Nexus 4 Android Development] iPwn_:
Since I installed 0.1 on stock 4.4.1, I've had some rare, randomly occurring graphical glitches. I can't say for sure that the kernel is even the cause, but I don't think I saw them before the flash.

The glitches usually involve the screen briefly flashing with a garbled frame of whatever I was viewing. It happens once every few hours.
[Nexus 4 Android Development] thracemerin:
Hmm...did you have test5 installed on 4.4.1? if so did you have the same issues? I don't seem to be able to reproduce it.
[Nexus 4 Android Development] iPwn_:
No. I had test 5 installed on 4.4 and then restored to the stock kernel to sideload the OTA. I waited for 0.1 before flashing anything on 4.4.1.
[Nexus 4 Android Development] thracemerin:
I'm running an app that redraws my screen over and over with different patterns and I'm not seeing it. If it happens again see if you can grab me a logcat and dmesg.

Edit: not entirely sure this would matter, but I went to stock, sideloaded the ota, flashed test5 in fastboot (to get init.d support), then flashed 0.1.0 in recovery, I'll keep looking into it. I didn't release an _rd version because I was waiting for the factory images to be released so I could pull the new boot.img.
[Nexus 4 Android Development] apatal:
Flashed the latest one from stock as well. No issues here. I came from a clean install. As in really clean as I accidentally wiped the whole sdcard. :)
[Nexus 4 Android Development] iPwn_:
I just got it to show up repeatedly when playing a YouTube video. The screen actually goes black in the middle of playback after flickering for a few seconda and returns once I try to play/pause.
[Nexus 4 Android Development] thracemerin:
Strange, I'm still not seeing this, tried it with a bunch of youtube videos.
[Nexus 4 Android Development] apatal:
Same here. I suggest users who is reporting this submit logs. Use an app like catlog to record it.
[Nexus 4 Android Development] iPwn_:
http://pastebin.com/RGwQw5Bx

Oddly, when I first tried to log it through my PC, the flicker disappeared, so this is from CatLog.

Also, as you might expect, disabling HW overlays gets rid of the issue.
[Nexus 4 Android Development] thracemerin:
This is on pure stock? I don't think this is the issue but it's certainly weird (mismatched dexopt binary):

12-08 01:03:49.023 D/dalvikvm(12568): DexOpt: VM build version mismatch (27 vs 28)
[Nexus 4 Android Development] tvisforme:
I'm scanning through the previous posts but wil also ask here - does this work on the Cyanogenmod ROMs or is it only for non-CAF builds?
[Nexus 4 Android Development] thracemerin:
I haven't tested it myself, but I can pretty much guarantee that it doesn't work on CM.
[Nexus 4 Android Development] farhanito:
Tested on CM11 non-CAF build

http://xdaforums.com/showthread.php?p=47388258

Works great.

Edit.

And CIFS works fine as well. Thanks
[Nexus 4 Android Development] iPwn_:
Well when I first flashed the kernel I was using ART, so I don't think that's the issue. My log is from Dalvik because I wanted to see if going back would fix the issue.

But no it's not pure stock. I flashed the "qualcomm optimized" Moto X Dalvik and Bionic binaries. However, I had them installed before I flashed m+ and I had no issues.

I suppose bionic could be causing problems, so I'll restore the stock binaries to see if it resolves the issue.
[Nexus 4 Android Development] thracemerin:
The logcat you sent me looks like the one I get on my device when I play youtube, except for that dexopt error I don't see that at all.
[Nexus 4 Android Development] iPwn_:
Just reverted. Nothing changed.

Eh, whatever. It's not really that big of a deal anyway.
[Nexus 4 Android Development] thracemerin:
Hmmm....well, I'll keep looking into it, puzzles like this peak my curiosity.
[Nexus 4 Android Development] apatal:
Just curious: have you been using one of them dalvik and bionic patches that have been floating around?
[Nexus 4 Android Development] iPwn_:
I was and had no issues with the stock kernel. I just reverted back to the stock dalvik/bionic and the issue is still there with m+.
[Nexus 4 Android Development] y3mita:
Battery life pretty good with kernel
[Nexus 4 Android Development] apatal:
Hmmm. That's really weird. I've been running latest m+ with stock, with rastakat, etc and have no issues. Oh well, let's see. 4.4.2 might have fixed some things regarding that.
[Nexus 4 Android Development] thracemerin:
There doesn't seem to be a new kernel for 4.4.2, so I'm not sure what if anything changed.
[Nexus 4 Android Development] iPwn_:
I reflashed stock 4.4.1. No flicker. Installed m+ with fresh zip. Flicker. Restored stock kernel...and no flicker.

You're saying there were no changes at all in the 4.4.1 kernel? Maybe there was a graphics change that's conflicting with gamma control or something.

Are any of you using FauxDisplay?
[Nexus 4 Android Development] thracemerin:
There were changes in the kernel between 4.4 and 4.4.1 including some tweaks to the graphics drivers, but those should be in the stock kernel as well, the only difference between m+ and stock when it comes to graphics is the simple GPU governor, I wonder if that's the problem.
[Nexus 4 Android Development] apatal:
Hmm. Maybe he can test it. I've always changed the GPU governor to ondemand (personal preference) so that could be the reason I'm not experiencing this flicker.
[Nexus 4 Android Development] thracemerin:
Could be, but I was using simple and not seeing it, if that's the case it could just be that the simple governor isn't ramping up quick enough to handle the additional load when playing videos, that's probably fixable with the tunables.
[Nexus 4 Android Development] y3mita:
Simple governor here and no flickering at all
[Nexus 4 Android Development] seangeezy12:
Does this fix the colors?
[Nexus 4 Android Development] thracemerin:
Colors are tunable with Trickster/FauxClock or by using init.d scripts. Init.d instructions are in post 2. The default kernel colors are stock.
[Nexus 4 Android Development] iPwn_:
I wandered into the thread for the AK kernel and noticed that there were quite a few posts about flickering.

The only listed solution was to just disable overlays, which isn't ideal for performance reasons.

Faux's thread has several mentions of flicker too, and his newest beta may or may not fix it (it says "Please test for flickers").

Franco's thread has no mention of flicker at all.

I suppose this may narrow your search.
[Nexus 4 Android Development] thracemerin:
There is nothing in Faux's git that I don't have in terms of graphics related stuff, hmm....possible he didn't push commits for his beta, I'll keep an eye on it.
[Nexus 4 Android Development] thracemerin:
I looked into it further, and apparently Google/Qualcomm added something that causes graphics flickering on some devices (not all devices obviously, since not everyone is seeing this), faux fixed this by reverting every graphics commit between JB and KK which apparently fixes the problem, but that isn't a particularly good solution because while it does fix the problem it also removes a lot of things which probably enhance the GPU performance overall, ultimately the correct solution is to find which commit is the problem and remove/fix that single commit, the problem is that we're looking at 50+ commits and it could be as simple as a 1 instead of 0 so this could be a long and troublesome process unless Google or Qualcomm identifies it and fixes it.
[Nexus 4 Android Development] ciprianruse88:
[MENTION=4303511]thracemerin[/MENTION]

Hey mate,

Any plans to update to latest fauxsound(v3.2) ?
[Nexus 4 Android Development] thracemerin:
Commits are in my repo, I'm working on a few other things before I push a new version, probably early this week :D
[Nexus 4 Android Development] ciprianruse88:
Nice !! Gonna flash it when posted :thumbup::D
[Nexus 4 Android Development] mnajem:
i use CM patch as being shared by Jolie's kernel.. to your kernel so I can use m_plus into my Beanstalk ROM (CM 11 based)...

nicely done.

recompiled with Linaro 4.7 ;) from your git
[Nexus 4 Android Development] :
Do you have a link for this cm patch? I haven't found it ?

Thx

Gesendet von meinem Nexus 10 mit Tapatalk 4
[Nexus 4 Android Development] thracemerin:
It needs to be built into the kernel, it's not flashable separately. I'll consider making a CM compatible version for the next release.
[Nexus 4 Android Development] mnajem:
on phone now. it's in cyanogen github.

i created a flashable kernel for myself.. but since OP plan for next release that will be better source. I'm not a developer so any hiccups happened; i can't respond to it
[Nexus 4 Android Development] thracemerin:
Version 0.1.1 is now Available!

What's Changed:

Faux Sound v3.2

TCP Congestion Control (added veno (default), reno, bic, westwood, vegas, yeah, illinois)

Cubic was previously the default and only tcp congestion control algorithm, it remains available.

Happy Flashing :victory:
[Nexus 4 Android Development] thracemerin:
There is now a CM11 compatible version attached in downloads as well.

Please read the note in post 1 regarding CM compatible kernels, also note that since I don't run CM currently I am unable to test this version though I have no reason to believe it doesn't work, if someone would be so kind as to test it I would be extremely appreciative.

Happy Flashing :victory:
[Nexus 4 Android Development] ciprianruse88:
Thanks a lot for the update ! :thumbup::thumbup:
[Nexus 4 Android Development] thracemerin:
It was supposed to be a bigger update but I messed something up with my wip branch and had to revert a bunch of stuff, so expect another update in a couple of days when I get that sorted :D
[Nexus 4 Android Development] mnajem:
i just realized the download section isn't appear in Tapatalk. on WiFi now so no worry about data drained out
[Nexus 4 Android Development] thracemerin:
There's a link in the OP that should send you to the right spot if you open it in a browser.
[Nexus 4 Android Development] ciprianruse88:
Take your time mate . Better to do things slow and perfect rather than fast and buggy:cool:
[Nexus 4 Android Development] pixiebob:
installed and approved.

i can offline 3 core like stock kernel(mpdecision off), better for battery life.

edit: screen flickering
[Nexus 4 Android Development] thracemerin:
Yeah, the screen flicker is a bug in the graphics drivers in KitKat, the only fix right now seems to be to revert all the graphics commits back to JB, and that seems to be a slight overreaction to the problem, I'm trying to figure out what specifically causes the problem but it's not a simple or quick fix, I understand that it's annoying for some but for the moment I prefer to live with it over reverting the commits.
[Nexus 4 Android Development] flash5000:
[MENTION=4303511]thracemerin[/MENTION]:

Does your kernel implement Tasssadars kexec-hardboot patches, i.e. does it support MultiROM?

If not, would you consider merging this?
[Nexus 4 Android Development] thracemerin:
It doesn't right at the moment.

I guess that's a good question to ask, are there people out there who would like to see the ability to use MultiROM with this kernel? if so I will put it in.
[Nexus 4 Android Development] flash5000:
Now that's a fast answer ;)

I would very much appreciate it, as there are only few kernels out there that do support it, and they are all more or less heavily modified.

I'm looking for a kernel like yours - only useful stuff added/changed. However, I rely on MultiROM for testing new ROMs without losing my stable daily driver.

TL;DR:

Please merge it if there's nothing negative about it :)
[Nexus 4 Android Development] ciprianruse88:
This is the second time when I'm trying m plus and I am very pleasantly impressed.The kernel is lean,fast and with fauxsound it's perfect.Now I need to see battery life. [MENTION=4303511]thracemerin[/MENTION] happy holidays and please keep maintaining the kernel !! :thumbup:
[Nexus 4 Android Development] thracemerin:
Quick update regarding development, I had another update ready to push but there was a huge ice storm here Saturday evening/Sunday morning and I lost power, sadly it hasn't come back yet and I'm not exactly sure when it will be back. Also I'm going on holidays on the 26th and won't be back until January 6th so if the power doesn't come back tonight the update may be delayed until then, sadly there is nothing I can do about situations beyond my control but I do plan to continue work when I can.

Happy holidays to everyone, I will do my best to answer questions and assist if I can while on vacation but I likely won't be around like I normally am.
[Nexus 4 Android Development] ryan92084:
Enjoy your holidays. We can wait "patiently."
[Nexus 4 Android Development] ciprianruse88:
0.1.1 is a rockstar ! Have a great time and see you after 6th next year :beer:
[Nexus 4 Android Development] thracemerin:
Power back after roughly 72 hours, unfortunately with holiday stuff today and leaving tomorrow I haven't had time to restart my build boxes, so 0.1.1 will have to suffice until I'm back.

I hope everyone has a safe and happy holidays! :good:
[Nexus 4 Android Development] thegtfusion:
[MENTION=4303511]thracemerin[/MENTION] this is exactly the kernel i am looking for but only for nexus 5....

http://xdaforums.com/showthread.php?p=48926153#post48926153

i made a thread about it.

can you also build for n5?
[Nexus 4 Android Development] thracemerin:
Not gonna guarantee anything, but I have been considering doing so.