yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] wrongway213:
I have always simply used Catlog to catch in the act because I don't need to be plugged in so for me it's much simpler - are dmesg logs provided within? If not, are logcats still useful without dmesgs, or for this would it just be a waste of time to provide you a simple logcat from Catlog? I will likely be able to catch the error a lot easier on my device than via ADB, at least with my schedule today anyway, so I just don't wanna waste my time creating errors or yours posting useless logs. If I need to use ADB for dmesg I could still try to recreate errors, just not until quite a bit later in the evening.
[Nexus 6  Original Android Development] colinmcg71:
I have S2S working fine here. I'm using flar's ElementalX app to set it on boot. I swipe from right to left on the navigation bar, works every time. You can also set it manually by editing the file named sweep2sleep located in /sys/android_touch. 0 is disabled, 1 is left to right, 2 is right to left and 3 is both ways. Doing it this way doesn't persist through a reboot though.
[Nexus 6  Original Android Development] tatoniss:
I still need to test more to be sure but last night while tethering I was having some issues. My computer kept disconnecting for small amounts of time. This is running the latest test kernel. Of course it could be something else so I want to test more first. Besides that this thing is sleeping so well now.
[Nexus 6  Original Android Development] wrongway213:
I wonder if there are echo commands that could make it persist on boot - I'm not sure there are but it may be worth investigating if anyone knows where to look.
[Nexus 6  Original Android Development] spinkick:
Another option for those that enjoy slide to sleep is to install greenify, then when you do the thumb slide up from the bottom of the device (used to enable google search by default I believe, you can select sleep via greenify as an option.)
[Nexus 6  Original Android Development] Mistertac:
By lurking around and making witty comments obviously [emoji6]
[Nexus 6  Original Android Development] lifeisfun:
And I thought you are Irish :p
[Nexus 6  Original Android Development] Imoseyon:
for selinux logs, either logcat or dmesg will be fine. So pull as much logcat (using Catlog) as possible and send to me? Thanks
[Nexus 6  Original Android Development] PeenX2:
If toning down the msm wakelock seems to effect wireless tethering, why not just disable it to see if it completely breaks something? Maybe easier to tell what effects it has if disabled? I would be happy to try it for you, if you disabled it completely.
[Nexus 6  Original Android Development] Imoseyon:
Attached! msm_hsic wake source is completely disabled - it's not even registered. :cool:
[Nexus 6  Original Android Development] tysonwald:
Awesome testing now!! been wanting this

seeing no ill effect, hotspot works, sms and mms. I will continue to test, thank you
[Nexus 6  Original Android Development] PeenX2:
Just quick test...everything still works, calling, texting, internet, and hotspot. msm is completely gone from BBS. Did speedtest on tethered laptop, and got 30Mbps down and up.
[Nexus 6  Original Android Development] smclaughlin3:
Anyone experiencing a wakelock called video2? Thanks
[Nexus 6  Original Android Development] Gnex1:
I'm seeing a video3 wakelock but it's only been on for 30 seconds (1% on BBS) so I'm not concerned about it at all. Currently getting 5-6 hrs SOT
[Nexus 6  Original Android Development] grayskul:
Settings please[emoji3]
[Nexus 6  Original Android Development] Jdban:
I just tried the one you linked there, and it seems to be starting in enforcing mode still.

---------- Post added at 01:53 AM ---------- Previous post was at 01:45 AM ----------

Or maybe I'm wrong...
[Nexus 6  Original Android Development] smclaughlin3:
What the difference between 13.2 and 13.3no_hsic i believe 13.2 gives you ability to disable that wake lock? Thanks
[Nexus 6  Original Android Development] smclaughlin3:
Permissive must be working because xposed installer working just activate module soft reboot this is how its working for now....

Thanks imoseyon.. the peoples dev
[Nexus 6  Original Android Development] italia0101:
No, 13.2 had some fixes to reduce that msm_hsic Wakelock, but it was still there.

13.3 it's completely removed.
[Nexus 6  Original Android Development] beyeond:
This kernel has gotten so good that the idea of even opening another kernel thread is laughable to me.
[Nexus 6  Original Android Development] DanRyb:
Just wanted to make sure I'm not missing anything. I was using your kernel 1.13 on AICP. Last night I took the plunge and wiped everything so I can run f2fs. I saw your kernel has f2fs support but couldn't get phone to boot past the Google screen after flashing this. I'm not wrong, it should work right?
[Nexus 6  Original Android Development] Gnex1:
Adaptive brightness ON @ 40%, ambient display OFF, leankernel v1.13.2 test build. Also make sure scanning for wi-fi is disabled.

For the record, your wakelocks don't look too bad. How much SOT are you getting?
[Nexus 6  Original Android Development] GregNexus:
[MENTION=3357040]Imoseyon[/MENTION]

[MENTION=3292224]franciscofranco[/MENTION]

Dont know whats happening... Since r7 or r8 from Francos kernel (not 100% sure if r6,r7 or r8) the performance from my phone ( animations, scrolling in the options, scrolling in chrome) is quite worse.. Because there are everytime stutters etc.(small ones most of the time). I used Francos kernel all the time, now i flashed your wakelock testkernel and i noticed how much smoother your kernel is, 100% stutterfree against Francos... On both kernels i use the stock settings.

I dont know what i can do against this. I dont even know if there is a useful information about this in the catlog (i can provide them)

This is not the : "maybe its just a placebo" or a "everyone has another interpretation for stutters"

100% visible stutters on Francos:-/

Both are 2 great kernels from 2 great developers. Love it when i read that you are both exchanging information in the threads for a even better kernel on both sides
[Nexus 6  Original Android Development] Imoseyon:
Attached is another version of test build with kernel put in permissive mode in a slightly different way. I'm not sure if you guys can ever run Xposed in Enforcing mode - I can imagine that being a nightmare. All these modules out there requiring access to all kinds of resources.

Also, I've been running all day with msm_hsic wake source disabled. No negative effects I can tell. Quite strange. Still, 1.14 will be released with the wake source enabled - you will need to use lkconfig to disable or dial it down.

Yeah unfortunately my ramdisk requires SuperSu for selinux live policy fixes. If SuperSu doesn't exist you may run into some selinux related issues.
[Nexus 6  Original Android Development] wrongway213:
Put in permissive a different way - does this aim to kill the need for a script? Curious as to what's different. Thanks for helping walk us through yet another major change like children lol
[Nexus 6  Original Android Development] Imoseyon:
Yeah I'm not sure exactly what issues you guys are running into, and not sure if I can help you since I've never run Xposed before. ;) The new build puts the kernel in permissive mode a tad bit earlier in init process than the previous. Not likely going to make a huge difference.
[Nexus 6  Original Android Development] akellar:
This in relation to all partitions or just system? Does lean support f2fs in cache and data?
[Nexus 6  Original Android Development] wrongway213:
This kernel makes Xposed work perfectly through any reboots - whatever you did here, oh man the people would appreciate oh so much if you could release these version of your kernels from time to time when you update kernel... this is exactly what we needed, no scripts at all required, no problems. Awesome work as always!
[Nexus 6  Original Android Development] Imoseyon:
Awesome. Spread the word!

only cache partition for now which is kinda useless. Lol
[Nexus 6  Original Android Development] akellar:
No idea how f2fs support works but if it helps at all it appears (havent tried it myself) that CM's kernel supports both data and cache if that points you in the right direction. If not, oh well, this works great anyway. :good:
[Nexus 6  Original Android Development] poczynek:
I've been on xda for over 2 years and read so many threads and so many developers but I have never met a more obliging and kind guy than lmoseyon. Always helpful, never patronising and delivers a friggin top kernel.

Not trying to suck up but you are the standard bearer for all developers.
[Nexus 6  Original Android Development] DespairFactor:
We have it working on a few kernels, it's pretty much just adding userdata mount point with F2FS in addition to the EXT4, just like with cache.
[Nexus 6  Original Android Development] Imoseyon:
You mean outside of fstab in an init file right? I'm the one who came up with that method on note 3 a while back. The problem is that that breaks encryption, unless you guys came up with another method to do this.
[Nexus 6  Original Android Development] DespairFactor:
No, I believe it's just in the fstab, I use your base and add stuff I like to it since your base has optimizations and is so lean;) I use the same implementation as CM and LiquidSmooth for it.

I have a question, could we not use lkconfig to set selinux to permissive? or does xposed load prior to us importing the init file for lk-post-boot?
[Nexus 6  Original Android Development] Imoseyon:
Adding f2fs mount points along with ext4 in fstab works on shamu??? Wow let me take a look at the CM ramdisk to check this out. Thanks for the info.

This is possible - I've been thinking about adding this option. It will have to be done as a separate service outside of lk-post-boot. It's a bit trickier though but I believe I can get it to work.
[Nexus 6  Original Android Development] DespairFactor:
No worries:) I am always up for a brainstorming session if you need ideas or weird ideas you wish to explore, you are doing a great job here! I wish I one day could be as good as you at what you do:)

---------- Post added at 11:58 PM ---------- Previous post was at 11:42 PM ----------

If you need help exploring it, you can always hit me up to get my thoughts or to even mess around with a few things, I like to take risks in messing with new concepts and ideas, I never worry about bootlooping my device when testing code or anything:P
[Nexus 6  Original Android Development] daleski75:
Flashed 1.13.3no_hsic and still get the same issue with no usb access and zero root.

Will try flashing CM12 to see if it's a Euphoria issue.

Tried CM12 and same issue.
[Nexus 6  Original Android Development] SilkyJohnson:
Seriously, about the most refreshing and humble Dev on here. Good vibes.
[Nexus 6  Original Android Development] Imoseyon:
[MENTION=5964313]wrongway213[/MENTION] & [MENTION=5169465]DespairFactor[/MENTION], I've attached v1.13.4 which changes selinux mode via lkconfig. Would be great if you (or others) can verify that changing to permissive mode via lkconfig will also work with Xposed.

I believe my ramdisk does not play nicely with ROMs that don't use SuperSU. I need to look into this some more. What about any of the permissive versions i've been attaching (or even 1.13.4 here)?
[Nexus 6  Original Android Development] daleski75:
Will give them a go and will let you know how I get on.
[Nexus 6  Original Android Development] DespairFactor:
I have tried to add some permissions to my version of you lk-post-boot for superuser and shipped the init.superuser.rc, but I am unsure if anyone has tested this for me. I was attempting to add superuser support. I can link you my file if you want to take a look. I don't use xposed myself, but I can test if it sets to permissive, but my concern was more, is where we are setting permissive early enough for xposed to work.

---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------

There is a line you can add to build.prop which make fix your USB issue, I just can't recall the line it has something like ro.securestorage.
[Nexus 6  Original Android Development] Imoseyon:
Ah take a look at my init.lk.rc which is where most of the magic happens. Yes I'd love to take a look at init.superuser.rc. I haven't had a chance to look at CM12 ramdisk yet - I'm out of town this weekend and working on kernels whenever I get a break here and there. ;)
[Nexus 6  Original Android Development] daleski75:
No dice still get nothing when doing adb devices from my laptop with adb debugging turned on with 1.13.4
[Nexus 6  Original Android Development] wrongway213:
Will test and see if it works, appreciated. I'll be using the default permissive 1.13.3 myself as it'll automatically work when I flash a ROM/update, but will test this out for you shortly and report back if no one beats me to it lol

Figured someone would beat me to it lol. How about allowing Xposed to boot? Does it apply permissive early enough or do we need to stay on 1.13.3?
[Nexus 6  Original Android Development] DespairFactor:
Well the init.superuser.rc is just a stock one from Koush, I'm more concerned about allowing all the permissions it needs, I will give you a link to the post boot script I have modified to take a look, unless the supolicy younuse is only for SuperSU, then I may be at a loss for full compatibility, but at least the permissions are outlined there for you to see.

I want to avoid us releasing two builds because of xposed and let users choose what they want, if your source is pushed I will look at the stuff you've done for permissive and take a look in my own time as well if you haven't been able to fix it and mess around with some things.

Sorry in advance for the novel.
[Nexus 6  Original Android Development] wrongway213:
Double post
[Nexus 6  Original Android Development] daleski75:
Fingers crossed I got it working.

1) Flash supersu 2.45 on twrp

2) disabled adb debugging

3) rebooted

4) enabled adb debuggin

5) adb devices now see's my nexus
[Nexus 6  Original Android Development] DespairFactor:
Have you test the permissive/xposed?

If we can't beat this xposed/permissive race on boot from setting in lkconfig, we may have to try doing a permissive by default with lk-post-boot throwing it into enforcing by default after, then letting users disable the option of enforcing after boot.
[Nexus 6  Original Android Development] Imoseyon:
PM me or email me (@gmail.com) if you want to test some builds? I want to see if I can make my ramdisk compatible with both CM's superuser and SuperSU.

1.13.4 should work just as well as 1.13.3permissive2 on Xposed. The only difference would be that on first boot it's set to Enforced so you'd have to launch lkconfig to change that and reboot. (You'd only have to do this once)

So this test build includes supolicy in /sbin now. I get the feeling though supolicy may not work at all unless SuperSU is present. Maybe or maybe not. As far as setting permissive is concerned, I now set it in post-fs-data rather than waiting until boot is completely finished.
[Nexus 6  Original Android Development] daleski75:
Not yet will do a full nandroid backup before messing around any further specially with xposed.

---------- Post added at 04:34 PM ---------- Previous post was at 04:30 PM ----------

Sure no worries will be more than happy to test some builds and will PM you my email address if that's ok?
[Nexus 6  Original Android Development] DespairFactor:
Here if you want to take a look at my lk-post-boot where I put the permissions in the supolicy for superuser.

https://github.com/RIPng/Despair/blob/despair/lk.ramdisk/boot.img-ramdisk/sbin/lk-post-boot.sh
[Nexus 6  Original Android Development] Imoseyon:
Holy crap that's a lot of policies needed for superuser. Does it work?
[Nexus 6  Original Android Development] DespairFactor:
I don't have a rom with superuser to test, I can test later today, I am just about to head out to do some stuff, and yeah, I looked at how they added support on the ROM side, and these were all required. It took me a while to type them out properly. If you want to you can use it in a test build, I don't mind. Feel free to use anything I have done, as my stuff wouldn't exist without yours:)
[Nexus 6  Original Android Development] Imoseyon:
Sounds good will do. Feel free to send me a pull request anytime as well. Thanks.
[Nexus 6  Original Android Development] DespairFactor:
Will do, if you ever want any assistance from me or anything you can either hangouts me(easiest way to get a hold of me) or you can just mention me or PM me. Mind you, I will be keeping a close eye on if this stuff works for us and if not I always have a knack for trying weird things that may or may not brick my device.
[Nexus 6  Original Android Development] linuxares:
Trying your special "xposed?" kernel now. My N6 has been a really bugger about allowing Xposed to function.

EDIT: and Xposed works! Thank you and accept my tiny donation!
[Nexus 6  Original Android Development] old_fart:
ditto . . . ( Trying your special "xposed?" kernel )

Okay, did not do quick reboot on replacing kernel plus framework. . counted up thru app apps like i wiped cache ( and i wiped nothing and am doing this dirty. . btw, i am running latest euphoria rom ! . . wakelocks has not changed, 'powermanagerservice.display' is still the 'numero uno' bad boy . . . . . .

.

and it does not work, am getting ( in the app ), "Installation is only possible manually via recovery for now."

.

tried again, and again . . . no go . . .

.

read that i had to have debugging off, so tried that and still no go . . .
[Nexus 6  Original Android Development] wrongway213:
1.13.3 or 1.13.4? 1.13.3 works, I haven't got to test 1.13.4 myself though.
[Nexus 6  Original Android Development] Damon13:
Yes I do agree with you Powermanagerservice.display wasn't a number one in my list of wake locks but since being in V1.13.3 it seems to have taken the #1 spot. The phone sleeps well, Wakelock detector has my phone at 4% awake despite Powermanagerservice.display at 2 hours and 19 min with 68% battery life still remaining.
[Nexus 6  Original Android Development] DespairFactor:
Set permissive via lkconfig and reboot to try xposed please, that is all we really need tested right kpw to confirm that soft reboot isn't required. We are trying to make it so you guys can boot permissive after changing in lkconfig.
[Nexus 6  Original Android Development] old_fart:
went into wugfresh's NRT, oh - look - need to update the twrp to newest 2.8.5.0 . . . hmmm ?

now finishing up a complete nandroid as insurance ( 838 MB ), and then was poking in the setting and in supersu and am giving it more privileges - 'trust system user', and then 'enable su during boot' was already set. . . . here i try once more !

.

no go, no joy . . . yet !
[Nexus 6  Original Android Development] supernexus:
Installed lk_shamu_lp-v1.13.4.zip, set permissive mode through lkconfig, rebooted and it worked!! it stayed in permissive mode and xposed was working.

For those complaining the xposed app says "no app_process active", you should try installing a module. Mine displays no active app_process but it works, well some modules work anyway. Xposed framework for lollipop is still in alpha so expect bugs.

Thanx Imoseyon for this awesome kernel and for being so quick for these changes!!
[Nexus 6  Original Android Development] DespairFactor:
Confirm USB storage as well please.

[MENTION=3357040]Imoseyon[/MENTION] it looks like you've done it:) now get that source up so I can have the fix;):P
[Nexus 6  Original Android Development] Imoseyon:
Or

If you don't want to boot into enforcing kernel to run lkconfig, you can just create a file called /data/data/leankernel/selinux_permissive (contents of the file doesn't matter).

Then flash 1.13.4. You'll be booting into a permissive kernel.
[Nexus 6  Original Android Development] smclaughlin3:
Hey Imoseyon i have been trying to keep up with your beautiful work. i have the 13.3permissive was wondering if i should flash the 13.4 since i imagine everything just is accumulating across kernels as far as wakelock disabling and features. 13.4 is different in the sense that the option is given to set it to permissive in lk config instead of it being set to permissive by default. As for me if the only changed is that permissive is configurable then ill just stick with 13.3permissive since viper4android is working great with it, as far as xposed i found that my phone will lock up... and i dont know why since i followed their instructions to the T...... so im waiting till xposed is more stable for our n6...thanks dont want to miss your enhancements...Thanks!
[Nexus 6  Original Android Development] supernexus:
Don't know if it will help but I'm using Kubuntu 14.04.1 with 3.16.0-30-generic kernel.

Got adb and fastboot tools installed and working through "ppa:nilarimogard/webupd8" repository.

adb via cable and wireless is working.

USB Storage activates when I plug in the phone and kdeconnect app in kubuntu also works perfectly when laptop/pc and smartphone are in the same net.

Hope this helps

---------- Post added at 08:58 PM ---------- Previous post was at 08:31 PM ----------

Forgot to say one more thing:

[root] StickMount works and my device is a

Nexus 6

Stock Android 5.0.1 LRX22C

Rooted with SuperSu

Decrypted data partition

lk_shamu_lp-v1.13.4 kernel of course :D
[Nexus 6  Original Android Development] oak:
Sorry I'm off topic but thanks for mentioning KDE Connect. I did not know about that. Looks cool and seems to work well.
[Nexus 6  Original Android Development] linuxares:
I already change to permessive before Leankernel with that script in the other thread.

I used "Amplify" for test Module since it really showed if it worked or not. It always test if Xposed is working before running, so it was a great test module, and it's also very useful. Just a tip from me :)
[Nexus 6  Original Android Development] Amaze209:
Can confirm too that after setting permissive via lkconfig it sticks on multiple reboots and USB works
[Nexus 6  Original Android Development] smclaughlin3:
incredible just gave the phone a regular reboot tried xposed module and it worked....lets see if the freezing is gone, pretty sure not kernel related this was happening to me in the soft reboot era lol
[Nexus 6  Original Android Development] old_fart:
Hmmm . . . well this one says "YES" ! ! ! it's all installed and working even though the Xposed framework install says 'nope - try again'. . . . So, isn't that a big kick in the a$$ !

Is it that the rom ( euphoria ) is so well fleshed out with custom tweaks . . . . none of the exposed stuff shows itself ? makes a dent ? is hiding ?

If I had a stock rom then it would be more needed / evident .

.

Thinking smarter instead of harder . . . I did a total wipe ( second today ) and rm'd the Xposed right out of there ! . . . ( themes is already a pain, don't need a bigger one. )
[Nexus 6  Original Android Development] Smallsmx3:
I wish xposed wasn't supported.... So many problems.... It's going to take over the thread. But not going to stop me from using lk
[Nexus 6  Original Android Development] linuxares:
If it blocks Wakelocks etc. Then your Xposed works.
[Nexus 6  Original Android Development] Gungrave223:
Dude have I told you lately how awesome you were? If not...you're awesome....
[Nexus 6  Original Android Development] bradputt:
hi Imoseyon, does this 1.13.4 disable the wakelock msm_hsic_host?

just checking as i see mine came back after flashing this.
[Nexus 6  Original Android Development] Krunk83:
Getting random reboots when making phone calls when the other person picks up. Not sure if ROM or kernel related. Not sure how to get a log. Running 1.13.4

Edit: I think it's the smb_135 wake lock being disabled. I enabled.

Nexus 6
[Nexus 6  Original Android Development] daleski75:
I don't think it does however 1.13.3no_hsic does which is posted a few pages back and I am running it with zero issues.