yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] ryanbg:
I love this kernel. Fresh commits and he's actively working on lots of bug fixes.
[Nexus 6  Original Android Development] wrongway213:
You missed the joke bro. There's been a lot of tweaks added to LK in recent days and thus people (myself included) are coming to Franco's thread to ask him to implement Imoseyon's patches on his kernel.. so he came over and made a joke about it.
[Nexus 6  Original Android Development] Bataga:
He's an ass and always has been.
[Nexus 6  Original Android Development] flyinj54:
Quite sure this wasn't a literal statement. These two at friends. Let's not start any trouble in here. Two great kernels from two great developers.
[Nexus 6  Original Android Development] franciscofranco:
I'm joking with imoseyon you dickwads.
[Nexus 6  Original Android Development] ryanbg:
Cherry picker.
[Nexus 6  Original Android Development] Bataga:
Sorry, Lord Franco
[Nexus 6  Original Android Development] franciscofranco:
Look dude, I don't know who you are, but let's get some **** straight. I know imoseyon in person, I had dinner with him once, we exchange e-mails in a regular basis, I'm entitled to come here and make a joke on him. If you can't take a joke that it's not even directed to you, you can **** yourself.

And yes, everyone is a cherry-picker, there's tons of good code that we can use. But before ****ting on me or ****ing with me on imoseyon's thread you should first to go my repo and read some code, you know, original code, that I wrote.

And this is my last reply, I already apologized to imoseyon for this, clearly it's not possible to make a joke to a friend, in public.
[Nexus 6  Original Android Development] wrongway213:
Kinda baffled at the blatant disrespect for Franco in any kernel thread - is this real life?
[Nexus 6  Original Android Development] DatDude123:
I knew some cherry pickers in high school.

D
[Nexus 6  Original Android Development] ryanbg:
Relax. I was being facetious. Cherry-picking is obviously essential and time-saving. No disrespect intended.
[Nexus 6  Original Android Development] flyinj54:
Bunch of childish bulls***. Can't have enough respect to let people joke with each other? Man the disrespect is absolutely ridiculous at times on here. Don't like someone (that your don't even know on a forum on the damn internet) keep your mouth fingers from typing so we can all enjoy peoples free work on our devices. No one comes on here to read this crap. Im here to read and learn about making my device better not whether sometimes panties are bunched up.
[Nexus 6  Original Android Development] Imoseyon:
Hey guys, it's all good. Let's take the hostility out of this thread.

Franco and I go way back and we joke all the time. We are working on fixing some gpu bugs offline together.

Now back to our regular programming...
[Nexus 6  Original Android Development] wrongway213:
We just don't know what to do with all this extra time we have not dealing with wonky sensor_ind wakelock reboots and so we are lashing out. :p

Seriously though, 1.13 is awesome work, snappy and the changes you made with SEPolicy are very cool and functional.
[Nexus 6  Original Android Development] flyinj54:
Thank God. For some reason my device was tuned to lifetime all the sudden for no reason. Glad im back to ESPN lol.
[Nexus 6  Original Android Development] bikeryder007:
Sally Struthers and Judith Light up in my phone!
[Nexus 6  Original Android Development] wrongway213:
What is it about the air in Ohio? We just don't have time to deal with people's BS, sometimes I wake up and think I'm in NYC for a second until I look around again and realize there isn't a thing to do.
[Nexus 6  Original Android Development] Mervingio:
Not Sound Faux right? [emoji20]
[Nexus 6  Original Android Development] wrongway213:
Faux sound has been included, option 9 in lkconfig
[Nexus 6  Original Android Development] Imoseyon:
Yup, faux sound is disabled by default so you need to enable it (via lkconfig or init.d/sysfs).
[Nexus 6  Original Android Development] Mervingio:
Thank You I will try today!
[Nexus 6  Original Android Development] arcanexvi:
Hey Imo. Where did you hide the Sunshine, Rainbows and Unicorn setting?
[Nexus 6  Original Android Development] nextelbuddy:
sorry for the slightly OT question but what is the best kernel app to use?

i use Trickster with the donation purchased and man it never really remembers certain things. like MIN CPU keeps changing to some other random number... i change it to 233 and hit the check mark and bam it changes to another random number. I understand that some times this screen may update and display the CURRENT freq at the time and some people say to ignore it its only an eye sore but when I DO that and use CPU SPY, it shows that my min freq is that random number that last displayed in trickster.

Plus I really loved how beautiful the FKU app and Elemental X apps are, but they dont have this wonderful sensor_ind wakelock fix yet so im back to lean kernel for now.
[Nexus 6  Original Android Development] Smallsmx3:
Lkconfig.... Simple and no mess
[Nexus 6  Original Android Development] biggiestuff:
R15 has it. Testing it right now. He posted the boot.img in the thread
[Nexus 6  Original Android Development] GPS3:
The best part about this kernel is not needing an app to use it. IMO.

Kernel apps not specifically designed for the kernel in use always seemed to be more of a hassle than they were beneficial: settings wouldn't stick, etc. At least in my experience as a novice user.
[Nexus 6  Original Android Development] mugendon:
And if you dont like typing in the terminal emulator with the touchkeyboard you can also use adb on your pc and type with your keyboard ("adb shell" from there just type "lkconfig" and so on).
[Nexus 6  Original Android Development] wrongway213:
I thought lkconfig couldn't set min frequency? If I missed that please do let me know so I can dump Trickster, no need for anything else I haven't found in lkconfig... that's not what option 1 set interactivex max screenoff freq is, is it? I'm gonna feel like a fool if it is lol

Edit: When you disable mpdecision via LK core control is min freq set to 300 by default? I've always just used Trickster but looking through lkconfig I see no options to configure min freq, but all the users saying they use lkconfig with no kernel tweaker app makes me wonder if I am missing something or if it just defaults to 300 and no one wants to raise it from that? I can't imagine everyone is fine with 1.4 ghz but I thought that was default until switching in Trickster.
[Nexus 6  Original Android Development] franciscofranco:
???????????????????
[Nexus 6  Original Android Development] GPS3:
I didn't phrase my post well.

I edited it to the following: "Kernel apps not specifically designed for the kernel in use always seemed to be more of a hassle than they were beneficial: settings wouldn't stick, etc. At least in my experience as a novice user."
[Nexus 6  Original Android Development] Imoseyon:
One difference between lkconfig and other kernel control apps is that lkconfig is tightly coupled with leankernel/ramdisk. I control (almost) everything and don't need to rely on ROM, the OS, etc. So the experience should be more seamless and trouble free.

Having said that, there are a million of these kernel apps out there and some of those are going to cause issues, and some won't. :)
[Nexus 6  Original Android Development] datajosh:
Wow, my phone is sleeping like a f***ing baby on 1.13 with both wakelocks disabled. I didn't think I was having an issue with them but my battery is doing noticeably better.
[Nexus 6  Original Android Development] Imoseyon:
More wakelock tweaks are coming in the future... :)
[Nexus 6  Original Android Development] wrongway213:
So the last few pages are making me wonder if I have any need for Trickster anymore at all. I searched but just getting info on mp-decision and touch boost and the faq. Will the kernel default to 300mhz min freq if I set option 1 in core control to disable mp-decision? I'd test for myself but have already set values in Trickster, unsure on if uninstalling would make them go away. If all can be done from lkconfig I'm all for that. Looking forward to wakelock options in the future, sensor_ind disabled is making an immense difference for me. Franco just released a test disabling msm_hsic_host (as I am sure you know) that I'm curious about as to how it works as I thought that wakelock was required for data or signal.. very curious how all this is gonna play out with wakelock blocking, it's pretty sweet since Xposed is still not here and that was huge back on Kitkat. Sorry for hybrid question/comment, quite a lot going on in LK recently
[Nexus 6  Original Android Development] Imoseyon:
I haven't added max/min frequency options to lkconfig because I haven't felt the need (yet). Franco talked to me about adding his performance profiles into leankernel so I may look into that as well. I may still add min/max freq option to lkconfig - i feel like a lot of people are still using apps like trickster just for that option now.

As for other wakelocks, I'm definitely doing my own thing (which is what I normally do). I'm thinking about making some of these wake sources user configurable, similar to what I did with smb135x and sensor_ind.
[Nexus 6  Original Android Development] flyinj54:
My CPU min freq always stays at 300mhz by default. Looking in trickster it shows my minimum at 1728000 but I know this isn't the case after looking at CPU stats. 300mhz min is working fine according to CPU stats.
[Nexus 6  Original Android Development] wrongway213:
That's great news - I think letting users configure the wakelocks is a great idea, no one will complain about what isn't forced on them as many people are not yet convinced blocking stuff is safe, but the rest of us sick of wakelocks can have what we need - for me I have never seen smb135x issues so I leave that be and kill sensor_ind, perfect. Also, in my opinion, performance profiles would be awesome - they were great in FKU and anytime you and Franco work together it seems to just make everything even better. As for the min freq, I didn't think Lean Kernel set a min freq different than stoc.. I'm now looking over the last few pages of people not needing a kernel tweaker app like :confused:. Excited to see what you choose to implement, so far doing your own thing has lead to some pretty awesome and surprising results.
[Nexus 6  Original Android Development] smclaughlin3:
i feel like adding the option to set max and min frequencies on lk config would render any trickster app useless it becomes sort of an ocd thing for me constantly checking and rechecking trickster to make sure my preferred min and max frequencies are sticking. many times i have experienced these kernel showing me different frequencies even with at boot options it drives me crazy sometimes.

on another im about to dirty flash 1.13 now wondering if the previous lk config settings i set with 1.12.7 will stick to 1.13 or if for new kernel versions or do i have to go back into lk config to set same settings....

Thanks
[Nexus 6  Original Android Development] wrongway213:
And you don't use any kernel tweaking apps, just lkconfig? If that's the case, bye bye Trickster as I think I'll be sticking with Lean for the near future
[Nexus 6  Original Android Development] Zer0_Cool:
I've been flashing roms/kernels since the droid eris days, but since I've had the n6 I haven't felt the need to flash anything until today. Flashed 1.13, I love the philosophy behind the kernel. lkconfig is also great to use, excellent work!
[Nexus 6  Original Android Development] Nalix:
Hey guys,

I've been running leanKernel since early versions and I've always had a slight problem with random "locks" of the SIM card, i.e. sometimes I have to re-enter my SIM PIN code. This can happen 5 times in 10 minutes or once per week. I believe I've had this problem a long time but today it has been worse than in a while so I thought I post here to see if someone knows what's going on. I haven't found any pattern on when this happens, it MAY be when the cell network coverage is low but I don't think so. It usually happens at home where I have pretty good reception and it only happens once per day, in average.

I'm using the OC/UC kernel (1.12, patching to 1.13 now) and I have the CPU scheduler in powersave mode. I did however have the same problems with a non OC/UC kernel and no powersaver mode with the 1.3 and 1.4 versions of leanKernel. Probably 1.0 aswell but I can't really remember.

So a couple of questions:

1) Do you have any ideas on what the problem can be?

2) Is it possible to activate some kind of logging, probably in some general Android kind of way (not leanKernel specific)?
[Nexus 6  Original Android Development] cam30era:
For those of us who flash lean kernel, but do not make any of the modifications via lkconfig, is there any reason to flash 1.13? I'm currently running 1.12.
[Nexus 6  Original Android Development] wrongway213:
Sensor_ind wakelock is disabled by default, Viper4Android now works with SELinux in enforcing mode instead of having to switch it to permissive.
[Nexus 6  Original Android Development] cam30era:
Thank you. I don't use V4A, but Sensor_ind wakelock disabled should be a benefit.
[Nexus 6  Original Android Development] mugendon:
Also voting for msm_hsic_host wakelock as the next one you should tackle :) Just as a quick fix in a testbuild before you make a more complex approach to the wakelock topic (sounds like you are planning a more generic approach for wakelocks).
[Nexus 6  Original Android Development] cam30era:
This is absolutely remarkable, how much snappier my N6 feels with 1.13 vs 1.12. And how much faster it opens apps and web pages. No lkconfig mods.
[Nexus 6  Original Android Development] simms22:
you are actually right, i just noticed that the op is missing it.
[Nexus 6  Original Android Development] cdub50:
What score are people getting for their CPU? I only scored a 3 contemplating returning, but wondering what others are seeing.
[Nexus 6  Original Android Development] akellar:
There's about 5 pages of this already but don't return your device no matter the number, it's not that significant
[Nexus 6  Original Android Development] seniorstew:
Min CPU doesn't seem to me sticking.. Both trickster and kernel
[Nexus 6  Original Android Development] estallings15:
He's absolutely right. If this were a device with severe heat and throttling issues, MAYBE. It'd still be a big maybe.

That's not the case here. Just be happy you have one in your hand.
[Nexus 6  Original Android Development] eep2378:
You need to turn off mpdecision in order for min to stick. With mpdecision (default kernel behavior) cpu will ramp up on touch.
[Nexus 6  Original Android Development] simms22:
disable mpdecision as usual, or itll never stick. in a terminal emulator..

su(press enter)

stop mpdecision(press enter)
[Nexus 6  Original Android Development] rockky:
Wiped Dalvik and cache from recovery and have bootloop...

Factory reset only way out?
[Nexus 6  Original Android Development] BDR456:
Stock kernel ^^^

Or try flashing stock kernel.
[Nexus 6  Original Android Development] Xileforce:
Try boosting the voltage of 2.88 to 1157 mv
[Nexus 6  Original Android Development] EniGmA1987:
Leankernel??? heck ya. Glad to see you here Imo.
[Nexus 6  Original Android Development] Imoseyon:
That's a tower defense game! I love those - downloading... (expect kernel development to slow down a tad bit now). :)

Try the new "beta3ocuc" build.

I know you.. I think. :) It's coming soon! I'm working on a dozen different branches simultaneously currently and my code base is a huge mess. Will clean it up and put it up in the next few days.

I tend to agree. The only exception (and this is purely IMHO) might be if you ended up with a pvs 0. Personally, it would just bother me too much and I might end up blaming CPU binning for a lot of my future issues. ;)
[Nexus 6  Original Android Development] Imoseyon:
Beta3 is up. More significant changes are in the "ocuc" build - I tweaked voltages a bit to make 2.9ghz more stable and also added a 223mhz slot for folks who want the extra battery life.
[Nexus 6  Original Android Development] simms22:
on my way..

edit.. i see voltages are raised a tiny bit.

---------- Post added at 06:00 PM ---------- Previous post was at 05:54 PM ----------

any chances of an fsync off option? or at least exposing them so we could disable it manually :)
[Nexus 6  Original Android Development] Imoseyon:
You know I've resisted considering fsync off for years due to its potential for data loss. But I will probably change my mind for shamu mostly due to there being so much sensitivity around the whole write I/O speed issue.
[Nexus 6  Original Android Development] simms22:
potential is always there. unfortunately(fortunately) its actually hard to do. on the n4, it was easy to reach that point, crash and lose data. on the n5, it was harder, but still possible. it only happened to me at 3014mhz(3014 low and high), and the temp was hanging around 85C, when i finally got it to crash. it wouldnt boot after, until i restored a nandroid.

---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------

btw, beta 3ocuc is running well.
[Nexus 6  Original Android Development] digweed4me:
Latest beta 3 oc/uc
[Nexus 6  Original Android Development] BDR456:
Can't get max/min frequencies to stick. Mpdecision is off...

On latest ocuc
[Nexus 6  Original Android Development] simms22:
they both stick fine for me. what cpu control app are you using? and you are sure mpdecision is disabled?
[Nexus 6  Original Android Development] eep2378:
Sticking here too. I'm using trickster.
[Nexus 6  Original Android Development] wrongway213:
Told ya it was worth the flash :p
[Nexus 6  Original Android Development] beyeond:
Why not? It only takes a minute or two.

I can tell you one thing for sure; flashing 1.13 definitely isn't gonna have a negative impact on you in any way.

Edit: didn't see that you already flashed.

---------- Post added at 06:18 PM ---------- Previous post was at 06:15 PM ----------

yeah msm_hsic_whatever has been a pain in my ass the last two days.
[Nexus 6  Original Android Development] Cy_n_ic:
Thats your mobile data! You dont want to block that. Just use airplane mode
[Nexus 6  Original Android Development] helaklatka:
What Governer for good performance and battery?
[Nexus 6  Original Android Development] Imoseyon:
That is correct. There may still be something I can do...
[Nexus 6  Original Android Development] wrongway213:
So I would have to assume the FK test kernel blocking msm_hsic_host would kill mobile data then? I'm confused as to what the difference between simply turning mobile data off and blocking that wakelock would be, haven't flashed myself, don't understand the reason for disabling the wakelock fully. Not asking you to explain Franco's work or anything, just curious as to the discussion of the wakelock going on here as I saw in his thread it's been blocked.
[Nexus 6  Original Android Development] Imoseyon:
It wouldn't kill mobile data but I'd be surprised disabling the wake source completely does not degrade some aspect of mobile data.
[Nexus 6  Original Android Development] Cy_n_ic:
Most complaints i have seen on that wake lock is either those in a bad signal area and/or handing off from 3g to Lte or vice versa a lot
[Nexus 6  Original Android Development] PeenX2:
FYI,

I have perfect LTE connection and still get that msm wake lock on the top of my list. Turn off 4G, still there. Go into airplane mode and it doesn't change. But I will say, it doesn't seem to affect battery life in any way. Still had 5hrs SOT with almost 2 days between charge. I did disable the sensor and 135 wakelock, though.
[Nexus 6  Original Android Development] bigant262:
Are all 4 cores supposed to remain online if you pick option 3 in lkconfig? Trying to figure out why 2 aren't online in the latest Eurphia build.
[Nexus 6  Original Android Development] bradld:
logic check

Just a clarification: Does wakelock disabled mean " stop wakelock from occurring"

I.e. wakelock status "N" means the wakelock shouldn't appear?

Thanks.
[Nexus 6  Original Android Development] wrongway213:
Right.
[Nexus 6  Original Android Development] Gnex1:
This may have already been answered in the past 240 pages of this thread.. but is it possible to enable double tap to wake from lkconfig? I just switched from Franco's kernel to LeanKernel two days ago.
[Nexus 6  Original Android Development] wrongway213:
Yes it is
[Nexus 6  Original Android Development] Gnex1:
stock dt2w vs haptic dt2w, which would you recommend?
[Nexus 6  Original Android Development] wrongway213:
Haptic is way more responsive, so haptic. Stock is Google's implementation, haptic is flar2's from ElementalX.
[Nexus 6  Original Android Development] Gnex1:
Enabled haptic dt2w now, thanks for your help!
[Nexus 6  Original Android Development] smclaughlin3:
The msm wakelock along with a couple more im not sure of
[Nexus 6  Original Android Development] supercluver:
[MENTION=3357040]Imoseyon[/MENTION] is it a feature of leanKernel that USB access is disabled? I have been running francoKernel, but gave your version 1.12.1 and then 1.13 a try, and have noticed with both that when I plug my N6 into my laptop, it is not recognized. It charges, but the debugging icon doesn't pop up on the N6 and I can't transfer files, etc... This happens with both 1.12.1 and 1.13. I'm on stock rom, not rooted. If I flash back to a francoKernel (even his test one with sensor_ind wakelock disabled) then USB works again. Any help?
[Nexus 6  Original Android Development] NikWillOrStuff:
It works flawlessly for me :/
[Nexus 6  Original Android Development] supercluver:
Strange, but I can do it repeatedly. Flash 1.12.1 or 1.13 and laptop & other computers don't see the phone any more. Flash back to any francoKernel and they do see the phone... I've done it several times just to be sure, on two different computers...
[Nexus 6  Original Android Development] Imoseyon:
another experimental build!

Here's an interesting test version (v1.13.2): https://onedrive.live.com/?cid=F1ED4BADFEE3FC02&id=F1ED4BADFEE3FC02!440

In this version, I attempted to drastically reduce wakelock time for wlan_rx and msm_hsic_host wake sources. I need some testers to confirm whether I did it right or barking up the wrong tree. :) Thanks guys.

[MENTION=265835]supercluver[/MENTION], how are you communicating via USB? IIRC, I disabled ethernet over USB but everything else should work.
[Nexus 6  Original Android Development] supercluver:
I'm talking about just plugging my N6 into my laptop or desktop via USB cable. On LK 1.12.1 or 1.13 the computer doesn't recognize the device. In a terminal window if I type adb devices, it lists nothing. In a file explorer, I can't see the N6 file system. It isn't listed in the device manager. Then I can reboot into bootloader, and fastboot flash a francoKernel and upon rebooting into android I can type adb devices and my N6 is listed, I can use a file explorer to browse the N6 file system and transfer files, and it is listed in the device manager on the computer. I can do this repeatedly, over and over again. I only figured it out when I went to send a file over to the N6 and plugging it in did nothing, and through several trouble shooting steps arrived at the kernel being the culprit (or something with the kernel and my phone/ROM/whatever).
[Nexus 6  Original Android Development] Imoseyon:
So you're running adb. Which ROM are you on? And which OS on laptop/desktop? I remember hearing something about issues with adb on CM12 with leankernel a while back, but I can't think of a reason why the computer wouldn't recognize the phone at all. If that didn't work I'd be hearing a lot of complaints...
[Nexus 6  Original Android Development] smclaughlin3:
Gonna test now i with betterbattstats like i been doing and compare prolly rough comparison but it will give me good idea to see if this wakwlock goes down for me. I think it cause of my apt brick walls prolly causing screwy data signal......