yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Imoseyon:
Not really, except a crap ton of these:

W/main (31551): type=1400 audit(0.0:774): avc: denied { chown } for capability=4 scontext=u:r:zygote:s0 tcontext=u:r:zygote:s0 tclass=capability permissive=0

Yikes, that's no good. Let me see if I can merge in their selinux changes without breaking compatibility with stock. This could get messy.

Oh you know what would help a lot, [MENTION=251020]inffy[/MENTION]? Can you post the logcat or dmesg output after the FC hits? I'm specifically looking for "denied" messages.
[Nexus 6  Original Android Development] inffy:
Will try to get you some logs. Just need to restore my CM backup first
[Nexus 6  Original Android Development] sykopompos:
Isn't that just the SuperSU permissive spam?
[Nexus 6  Original Android Development] Imoseyon:
I think so? I modified the kernel to log *everything* denied, and unfortunately these are the only ones I see, other than the usual.
[Nexus 6  Original Android Development] sykopompos:
Anytime you run something with su, you will see a ton of denial messages from SuperSU because chains just patches them in as permissive instead of allow. I guess at some point, I'm gonna just make them allow so I stop seeing the spam
[Nexus 6  Original Android Development] inffy:
[MENTION=3357040]Imoseyon[/MENTION]

https://drive.google.com/file/d/0By5TAx9BhakReERNeFAxaWsyZTQ/view?usp=sharing

log
[Nexus 6  Original Android Development] andyx1985:
Hi,

Got the logcat. It does show more info. I'm nor sure what it means though.

Thanks for looking into this.
[Nexus 6  Original Android Development] wrongway213:
[MENTION=3357040]Imoseyon[/MENTION] CPA Poke from LiquidSmooth shared the fix to make kernels play nice with the new CM theme engine. Add this to your ramdisk and it will work. http://gerrit.liquidsmooth.net/#/c/5348/
[Nexus 6  Original Android Development] Imoseyon:
Thanks for that. Those of you having issues with CM theme engine, try v1.7.7 in the testbuild directory? https://onedrive.live.com/?cid=F1ED4BADFEE3FC02&id=F1ED4BADFEE3FC02!440
[Nexus 6  Original Android Development] old_fart:
Question on lkconfig. going into option two, configure wake jester ( gesture ) control. choosing both ( option four ) to allow tapping and sweeping . . . and then do an option zero to see where its all at. surprise ! ! ! gestures says its "OFF - 1 15"

And then trickster also agrees that sweep is "OFF" . . . huh? . and so what is happening when you choose both ?

.

went to the OP to read the description / doc on lkconfig . . . and option 2 says : "set mmc crc". . . Hmm.
[Nexus 6  Original Android Development] micr0g:
Thanks for the test build but I still have Theme engine fc. https://www.dropbox.com/s/0fbms9dsowodhe3/Th.txt?dl=0
[Nexus 6  Original Android Development] CPA Poke:
FYI

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

In case you don't want to compile inline just for one binary :)
[Nexus 6  Original Android Development] whalechan:
Hi Imoseyon!

First of all a big thanks for your work. After two soft-bricks (that's the best way of learning Android isn't it?) and a ton of reading and re-reading I am now running your kernel. A friend suggested me so I believe him and You.

My only question is, when I got the phone and transferred all my contacts (from my 6yo nokia e51 through blutooth) I could add any contact to my favourites no problem. Then later I jumped into unlocking, rooting, installing your kernel and made a backup of my contacts through export in the Contacts app; at the end I restored them all from the file and then favourites didn't work.

Apparently if the number starts with the international version (+36.....) the fav does add but if it's the national one (06.......) it doesn't. If I edit the original number(06...) and add the edited one(+36) then reedit back to the original (06...) I can easily remove/add the contact to favs. My question is can it be something in your kernel (although as much as I understand this is a ROM thing?) or it's something else in which case can you or someone bump me to the correct path of finding my answer?

Thanks again!
[Nexus 6  Original Android Development] Imoseyon:
Hmmm.. that 15 means that s2w is definitely enabled. I wonder if Trickster looks at a different s2w implementation then. If I get a chance I'll take a look. Ignore the "screenshot" on OP - I will update that. :)

I've actually been trying to keep my sepolicy file stock by patching policies live. Let me take a deeper look this weekend to see what else i'm missing. I may even flash CM to troubleshoot although that will be my last resort.

Sorry I'm pretty sure that's not a kernel issue...
[Nexus 6  Original Android Development] CPA Poke:
Ah, nice! Do you maybe need to modify file_contexts?
[Nexus 6  Original Android Development] Imoseyon:
There where I was gonna look next. :)
[Nexus 6  Original Android Development] Imoseyon:
How about v1.7.8 in the same directory? Theme engine work? I made some changes to *_contexts files this time.
[Nexus 6  Original Android Development] inffy:
[MENTION=3357040]Imoseyon[/MENTION] the newest 1.7.8 testkernel seems to fix the Theme manager FC.
[Nexus 6  Original Android Development] old_fart:
It seems that [MENTION=5169465]RIPng[/MENTION] was poke'ing and digging with the 'theme engine' stuff and stumbled across getting the PIE control working . . . They're pretty jazzed . . . http://xdaforums.com/showpost.php?p=58228727&postcount=461
[Nexus 6  Original Android Development] micr0g:
No fc's or anything else with 1.7.8

Everything is back to normal.
[Nexus 6  Original Android Development] mclisme:
When coming from stock kernel do we have to wipe anything before/after flashing LK?
[Nexus 6  Original Android Development] rstar2015:
I have a question which is a little bit off topic..

Does a custom Kernel interferes with google software updates? also, what would happen if

I have a custom Kernel installed and google decides to update their stock kernel?
[Nexus 6  Original Android Development] inffy:
No
[Nexus 6  Original Android Development] panooos:
I believe you mean the OTA update. Root phones that have even the slightest thing changed/added/installed don't get OTA.
[Nexus 6  Original Android Development] CPA Poke:
So I guess that was the ticket? :)
[Nexus 6  Original Android Development] Imoseyon:
Yeah file, seapp and service. I'll upload my source in a bit along with the v1.8 release.

edit: https://github.com/imoseyon/leanKernel-shamu/commit/0ccf74715777c14c823a6c581219522b6465ee4a (not all changes in there are theme engine related though)
[Nexus 6  Original Android Development] Imoseyon:
v1.8 is up: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

Aside from the usual stability/performance/power improvements, a couple of notable changes:

1) a bunch of selinux related fixes, including a new sysfs node (/sys/module/selinux/parameters/force_audit) to enable force auditing of all/hidden deny messages. Mostly for kernel/ROM devs to troubleshoot.

2) leankernel should now slightly favor giving free RAM to apps rather than file/dir caches, than before. This should discourage lowmem killer from being trigger happy all the time, theoretically.

Enjoy!
[Nexus 6  Original Android Development] franciscofranco:
Take a look into my git, I merged a couple SELinux fixes from upstream. Good job with sepolicy :)
[Nexus 6  Original Android Development] 12MaNy:
Thank man! :D

No OC/UC build?
[Nexus 6  Original Android Development] Imoseyon:
Hah, I knew you were going to make me look at your git repo sooner or later! :p

Ah completely slipped my mind. It should be up now. thanks.
[Nexus 6  Original Android Development] strikerdj2011:
is there and oc/uc 1.8 cant seem to find it cheers
[Nexus 6  Original Android Development] Pilz:
Look up one post
[Nexus 6  Original Android Development] strikerdj2011:
i did and looked in where its meant to be and its not there was just double checking lol
[Nexus 6  Original Android Development] Pilz:
Yes you are correct it's not there. I wasn't sure of you saw his post above.
[Nexus 6  Original Android Development] Imoseyon:
Darn give me 15 minutes I think I forgot to upload

Edit: Ok, it's up there now. Sorry about that. Hopefully that's my last fail of the day.
[Nexus 6  Original Android Development] strikerdj2011:
sorry if i sounded demanding was just eager to flash it :)
[Nexus 6  Original Android Development] natezire71:
Does lkconfig allow modifying the vibe strength now?
[Nexus 6  Original Android Development] Imoseyon:
Ah.. that's coming soon. Didn't make 1.8 but should make 1.9. In the meantime use Trickster...
[Nexus 6  Original Android Development] 12MaNy:
Dude, you're the man. Donation sent...
[Nexus 6  Original Android Development] old_fart:
I noticed your lkconfig has a 'new' option... Is option 8, drop cache ! ! ! ( but, I love johnny ! )

.

Can you do any thing like '3C Toolbox Pro' does with its : system manager / fstrimmer ? ? ?

After I did your 'option 8', i then clicked on its trim and was expecting cache NOT to trim . . . but, it sez

system gets back 901 MB / data gets back 1.19 GB / and ( lastly ) cache gets back 248 MB

hmmm . . .

.

And then also . . .if I set my logcat filer at error ( instead of fatal ) . . . well I immediately get a screen full of sickly pink notices about : wfstatemachine and then mp-decision ! ! ! those two guys look 'pissed off' ! . . . the list grows and grows . . .
[Nexus 6  Original Android Development] Mervingio:
Any plans to add FauxSound?
[Nexus 6  Original Android Development] poczynek:
Just with themes they are only working on the stock kernel. Any fix to make them work here? Thanks
[Nexus 6  Original Android Development] TetsuNoKobushi:
The 1.78 test build had themes working. I assume 1.8 incorporated those upgrades as well. As for themes however, no CM11 themes are compatible, you'd need CM12 themes, which aren't out yet it seems.
[Nexus 6  Original Android Development] wrongway213:
Yeah this is the case. No themes yet to use but no FCs like other kernels on systemui
[Nexus 6  Original Android Development] poczynek:
Yes the blue fire cm 11 theme works on stock but not custom kernel.
[Nexus 6  Original Android Development] Imoseyon:
Anyone want to try a test build? Try v1.8.3 in the testbuild folder. There's some massive changes in there that will go into v1.9, especially with the cpu scheduler. I'm mostly interested in any regressions in performance or stability.

hmmm if I understand you correctly... Dropping file/dir cache is not the same thing as TRIM. It will temporarily purge the caches to immediately free up RAM for Android and apps, but the caches will fill up again as the kernel reclaims it eventually. It's all normal.

Depends. I've included fauxsound in leankernels in the past, so maybe... All depends on how it's implemented.
[Nexus 6  Original Android Development] Imoseyon:
Hey guys!

Just put up a 2.9ghz version in the beta folder. I tried to go higher but my phone (pvs6) started getting too hot and became unstable. And I probably won't spend too much time on overclocking since snapdragon 805 is already fast enough.

I've been on the 2.9ghz version for a couple of hours now and so far it's been stable.
[Nexus 6  Original Android Development] Blaze420916:
Lmfao what a dummy <--------
[Nexus 6  Original Android Development] simms22:
lol, it benches nearly identically to stock(2649mhz) :)
[Nexus 6  Original Android Development] Imoseyon:
doh that's no good - you're probably getting throttled. On my Antutu tests it scored consistently better. I may need to mess with the bus bandwidth a bit when i get a chance.
[Nexus 6  Original Android Development] Xileforce:
Pvs5 here, and I can't seem to get the oc kernel to run properly. I attempted to run antutu with it oc,d set to performance governor and it crashed. So I decided to try underclocling it to stock 2.7ghz and Performance governor and still crash...not really sure what's up because that should work...
[Nexus 6  Original Android Development] simms22:
thermal throttle is off, benched at 2880 low/2880 high(mpdecision off), ondemand/deadline. was seeing 21000+ at 2649/2649. this time benched at 2880/2880, and i saw 22000. yes, there's a slight difference. but thats all it is, very minimal, almost identical.
[Nexus 6  Original Android Development] Imoseyon:
BTW, i cannot reproduce this.

I first stopped mpdecision. And then changed governor multiple times as well as io-scheduler. No reboots or SODs yet - how long does it take for you?

---

For 2.9ghz benchmarks, I was getting around 6500 on the single thread cpu test on 2.7ghz and around 7000 on 2.9ghz. Not sure how much time I want to spend on overclocking though - probably not worth the effort. :)
[Nexus 6  Original Android Development] simms22:
anywhere from 5 minutes to 2 hours. if its a reboot, its usually while in the browser. and sod, when the screen is off for longer than several minutes. its an odd behavior for sure, possibly its just my phone. but that's an odd behavior.

about the overclocking.. the small percent of the cpu raised is only like 7%, so i shouldnt expect that much if a difference. i just thought about that :)
[Nexus 6  Original Android Development] brizey:
I think we will be waiting for the next generation of SOCs before OCing does much. There is always a cycle. By the end of the series the manufacturers have effectively already OCed the snot out of the architecture. And every once and a while you have a hero chip like the snapdragon S2 in the Thunderbolt that can run at a 60% overclock for years on end, lol. I think the bigger difference between this SOC and say an 800 is the move from Adreno 3xx to 4xx. Supposed to be something like 40% more processing power. There may be more headroom for tweaking there vs finding gains on the Krait side.
[Nexus 6  Original Android Development] k2buckley:
I'm not rooted yet, it worked for me. Mines a 6.
[Nexus 6  Original Android Development] BDR456:
Just switched from Note 3 and had just updated leankernel on it a day or so before my N6 came in. Glad to see you over here bro, hope to be a tester on this device for you as well. :thumbup::thumbup:
[Nexus 6  Original Android Development] StickyEyez:
Download site not working for me..webpage can't open

Sent from ChameleonOS

---------- Post added at 02:30 PM ---------- Previous post was at 02:27 PM ----------

Nvm downloaded on PC

Sent from ChameleonOS
[Nexus 6  Original Android Development] pathtologos:
Guys, can u help me interpret this:
[Nexus 6  Original Android Development] jarjar124:
I believe yours is 4.
[Nexus 6  Original Android Development] pathtologos:
Dam. Not good, am I right? Its weird. I see a 3 on there, a 4, a 13, and one more. Which is it?
[Nexus 6  Original Android Development] jarjar124:
Higher is suggested. It's just that you'll need more voltage than usual.
[Nexus 6  Original Android Development] BeansTown106:
Glad to see you here [MENTION=3357040]Imoseyon[/MENTION] always nice to have the same device as you
[Nexus 6  Original Android Development] Imoseyon:
beta1 is up. Added interactiveX.

screen_off_maxfreq is set to 2.2Ghz by default. Use an app like Trickster or Kernel Tweaker to modify for now.
[Nexus 6  Original Android Development] Imoseyon:
Agreed - it certainly seems that way so far for apq8084. I will take a look at the GPU soon...
[Nexus 6  Original Android Development] __NBH__:
V1.8 is amazing so far. Got 3 hrs screen on time watching downloaded programs on iPlayer and had 71% battery left then left it overnight and lost 3% in 8 hours :thumbup:
[Nexus 6  Original Android Development] TetsuNoKobushi:
I'm very tempted. But I need to cycle 1.8 first to be able to compare.
[Nexus 6  Original Android Development] Smallsmx3:
So far so good, no Performance lost from what I've noticed
[Nexus 6  Original Android Development] nowise:
No performance hiccups or instability so far on 1.8.3. Been running it all day.
[Nexus 6  Original Android Development] inffy:
Same here. And the battery life seems better than with other kernels. Been running this today but not much use for the phone so it has been idling almost all day.
[Nexus 6  Original Android Development] TetsuNoKobushi:
Going to flash 1.83. For some reason my cores are always active at 1.5 -2.6 for 2-3 cores on 1.8. Did a clean flash. Must have gone wrong somewhere.

Edit: 1.8.3 allows the cores to stay idle at 300/300/0/0 again. Phew.
[Nexus 6  Original Android Development] Cheater912:
I haven't charged my battery since I flashed v1.0. 3 weeks of SOT. Crazy...

I'm going to donate once vibration settings are added to lkconfig!
[Nexus 6  Original Android Development] old_fart:
So, i'm listening to twit and 'leo laporte' and the pod cast - 'this week in google' . . . and i'm going down through a dozen odd benchmarks ( oooh, pretty ! ) - running 18 and then 18.3 . . and i do not see any difference . . . you're doing massive additions / alterations ? what are you cooking ?

.

all that ( grunt ) testing and my battery is down to 35%, that be a GOOD thing.

example : vellamo metal - 1986 versus 1990

antutu - 52445 versus 52738

geekbench3 - 1108/3266 versus 1113/3389

gfxbench - 786 versus

Some of the testing comparisons sites say we're higher than the average N6 community . . . So that would be a MAJOR testament to leankernel ( and maybe then turning off encryption too ). . . And honestly, we're only talking about five to ten percent better.
[Nexus 6  Original Android Development] Imoseyon:
Good question. The CPU scheduler change in v1.8.3 is not supposed to perform better than v1.8, although there may be other changes in v1.8.3 that could affect it positively. I just wanted to make sure that there is no *regression* in performance.

I don't want to go into too much detail in what the scheduler change is since I may decide to pull it before v1.9 is released, but here's a small taste. Somewhere between Linux 3.8 and 3.10, the mainline contributors decided to pull the power saving features of the scheduler because they couldn't agree on the implementation so what we ended up is sort of a vanila dumb implementation. I'm working on changing that.
[Nexus 6  Original Android Development] arcanexvi:
I'd leave it in as it seems to be helping my end. I don't think I've ever gone through the first half of a work day (yes I work in Sundays bleh) and only been down 20%.
[Nexus 6  Original Android Development] old_fart:
I agree. . Keep and then if possible - add in more 'power saving' constructs. . The N6 is over powerful enough as it is. In six months, the sixty four bit stuff will be out to be king of the hill.
[Nexus 6  Original Android Development] Imoseyon:
Funny you should ask. Do this for additional power efficiency (v1.8.3 only):

echo powersaving > /sys/devices/system/cpu/sched_balance_policy/current_sched_balance_policy

I hope that improves things a bit. The problem with doing kernel development on a single device is that it's really hard to test on my own what the battery life is like, as I'm flashing and rebooting the phone with test versions several times a day.
[Nexus 6  Original Android Development] eggydrums:
Gonna try that now. What if I want to disable that?
[Nexus 6  Original Android Development] thederekjay:
echo performance > /sys/devices/system/cpu/sched_balance_policy/current_sched_balance_policy
[Nexus 6  Original Android Development] Imoseyon:
Yep or just reboot
[Nexus 6  Original Android Development] eggydrums:
So I just execute it again? Also, it doesn't persist after boot then?

Also just thought you should know, 1.8.3 is running great! Thanks

Edit: my bad, I saw you enter "performance" rather than "powersaving"
[Nexus 6  Original Android Development] old_fart:
Please 'consider' adding in a link/hook to allow faux sound. Did you know ? ( what am I saying, ha ha ha, you're mr. mega brains, you know this already ! ) that the clever chaps over at the euphoria rom take your kernel and extend it in a couple ways. . . One of which is 'faux sound'. So, their auto system checker notified me there's a new January 18th rom. It dnlds the delta ( ten times smaller ) and its got lk1.8 ( plus ) resident within it. I have tinnitus.
[Nexus 6  Original Android Development] jaflrf15:
Been running 1.8.3 all day and haven't seen any issues with stability or performance. Battery life has been great as well.
[Nexus 6  Original Android Development] arcanexvi:
Same here
[Nexus 6  Original Android Development] Pilz:
I'm running 1.8ocuc but with stock frequencies with the ondemand CPU gov and I have had 4-5 reboots today. Is there a reason for this, or is it something I'm doing wrong? I haven't touched the frequencies/voltages and this didn't happen with Franco or ElemnetalX so far with the same set up.

I'm just finding it odd because this kernel has always been very stable even if I run it at 2.9gHz as I have done with earlier builds. I'm thinking that it's something that trickster is doing by default such as setting the voltage but I haven't played with the 1.8 build that much today. I might try the 1.8.3 and see if the issue persists.
[Nexus 6  Original Android Development] mkcbbusiness:
I heard that lmoseyen had an undervolting guide can someone help me find it or point me in the direction of another?
[Nexus 6  Original Android Development] lainemac:
Believe imo said that this is cause by a conflict between cpu boost and ondemand governor. Try disabling cpu boost with lkconfig.
[Nexus 6  Original Android Development] Pilz:
CPU boost is always turned off. I check and turn it off when I flash any kernels.
[Nexus 6  Original Android Development] oak:
1.83 seems fine to me. No regressions that I can discern.
[Nexus 6  Original Android Development] Imoseyon:
Hmmm, you had no reboots on v1.7ocuc with default frequencies and ondemand? And the reboots happen often on 1.8ocuc? Can you PM or email me at imoseyon@gmail.com? Thanks
[Nexus 6  Original Android Development] franciscofranco:
Do you think that cfs being power aware will conflict with this device's own cpu power states? I can see it working on a desktop, where cpus have standard interfaces for power states... I read the docs, and it's a good approach, I was actually planning on trying to code something like this on my own for a while.
[Nexus 6  Original Android Development] Imoseyon:
Well, there are like half a dozen RFCs out there already - some are ARM aware (including core power gating) and some aren't. I'm playing with a few of them at the moment. The one in v1.8.3 is the most generic one (not ARM aware) and also carries the least risk - all it does is to try to pack tasks into the smallest number of CPU cores to maximize the core idle time.

Some point in the future mainline folks will take one of those implementations and include it but I fear that we'll never see it for Linux 3.10.

I put up v1.8.5 in the testbuild folder which uses an entirely different implementation which is ARM aware. Testers, go for it! Please check for any performance regressions.
[Nexus 6  Original Android Development] franciscofranco:
Can you push those patches? I would love to take a look.
[Nexus 6  Original Android Development] nobnut:
I've been using 1.8.3 with no issues and flashed 1.8.5 just now. I then saw a CM12 theme and tried to install it but it failed. I then tried 1.8.3 again, it failed also. I then used the 'stock' Euphoria kernel (based on your 1.8.0) and it installed just fine.

Just reporting for info.

The theme link is http://xdaforums.com/android/themes...gn=Feed:+xda-developers/ShsH+(xda-developers)
[Nexus 6  Original Android Development] Imoseyon:
Hmm I will take a look. It's likely a ramdisk change which gets compiled separately inline for Euphoria.

EDIT: can you send me a logcat output when it fails please?

Check your email.