yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Imoseyon:
Folks,

I need to work on my Note 3 leankernel for a couple of days so v2.2 probably won't show up until the weekend or next week. I think v2.1 is pretty solid. :)

Interesting... I haven't seen sensor_ind in my top 10 since I enabled it. And what's even weirder is that *disabling it via lkconfig should have an immediate effect. I'll keep an eye on this.

EDIT: ah that's not true actually. If the wakelock was already held, disabling it via lkconfig won't kill it. It needs to be freed on its own first then the kernel will prevent it from being held again.

Yup actually that's the expected behavior for v2.1. I reverted my audio driver based call detection code in favor of [MENTION=4684315]flar2[/MENTION]'s x-coord tweak. Which behavior do you prefer? Which one is the lesser of two evils? :p
[Nexus 6  Original Android Development] wrongway213:
To note: the ROM I am on (Benzo) comes with DT2W enabled by default and must be turned off via built-in kernel app - I checked lkconfig and stock DT2W is set to auto, haptic is set to 1 as I turned it on that way. Could this be the "culprit"? If not, confirmed case of sensor_ind on 5.1 right here - you know how I watch for that wakelock and seem to have a knack for inducing it, lol.
[Nexus 6  Original Android Development] Imoseyon:
Ah I should have known you'd be responding so quickly! :) I corrected my response above to this:

Doesn't answer your question entirely though. I'll keep an eye on it for sure.
[Nexus 6  Original Android Development] rauschkugl:
Well I think that it's not good at the Moment. Double tap can happen really easy. I think disabling gestures completely while in call would be the better option. They are not needed anyway during that time. In my opinion the current behaviour makes gestures still not usable and I'll rather disable them completely for now.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] Smallsmx3:
I'm assuming that the 47E kernel is the same as the 47D?
[Nexus 6  Original Android Development] Jaspah:
Agreed.
[Nexus 6  Original Android Development] shawnten:
What is everyone's favorite color control numbers

Does gamma or hue make the screen brighter. I am clueless
[Nexus 6  Original Android Development] Imoseyon:
Yup. Pretty sure.

I'm going to revert back to my implementation in v2.2.
[Nexus 6  Original Android Development] jeromechrome1:
This.

+1
[Nexus 6  Original Android Development] SilkyJohnson:
[MENTION=3357040]Imoseyon[/MENTION]

This makes me smile. Performed wonderfully today. Thank you!
[Nexus 6  Original Android Development] semdoc:
Agreed. Your solution seems to be better...

[MENTION=3357040]Imoseyon[/MENTION], one side note... I'm still on old implementation (I have in my source this commit only

wake_gestures: disable during phone calls via ASoC/qdsp6v2

)"

While I make call via my BT headset... It disables wake gestures as expected... But doesn't activate them after call... No matter If I press power key, or end the call manually or wake screen after call etc... The only working solution is to re-enable them from settings...
[Nexus 6  Original Android Development] michmeister:
I know it's awesome kernel that's why it's the only one I use.
[Nexus 6  Original Android Development] Imoseyon:
Yup that's the drawback of my implementation. There are still a few edge cases I need to catch. I got a BT device at home somewhere so let me play around with that a bit.
[Nexus 6  Original Android Development] old_fart:
There is a thread where they are talking about a new rom. "M" for motorola ?

http://xdaforums.com/showpost.php?p=59549724&postcount=31
[Nexus 6  Original Android Development] Franzie3:
I think each build thats getting pushed is having VoLTE specifics in it per carrier. I think the E version was Verizon, and now M might be from T-Mo. That seems to be what all the chirping is about
[Nexus 6  Original Android Development] smclaughlin3:
thought 5.1 already came with volte? thanks
[Nexus 6  Original Android Development] Franzie3:
it does, getting it working though is the second part of it. Apparently OTA's to devices are working fine but AOSP built ROMs are having trouble. it'll all get figured out
[Nexus 6  Original Android Development] lainemac:
Interesting. D build had VoLTE for me(T-Mobile) and so did the E build. I flashed the factory images for both. I assumed they pushed the E build out quickly to ACTUALLY fix that memory leak.
[Nexus 6  Original Android Development] shawnten:
so what is the trick to getting this thing to deep sleep. I have 77% and 300 but no deep sleep
[Nexus 6  Original Android Development] old_fart:
I believe Imo stated ( yesterday ? ) its a rom issue. More specifically the roms based on aosp and NOT the ones based off an image . . . There are "missing" stuff in the distribution ! . . And going even more specific, it has to do with google play services, update service.

Kernel 2.1 is working great ! Thank you Imoseyon for all of your expertise and hard work !
[Nexus 6  Original Android Development] Franzie3:
Do you have BBS or some kind of wake lock detector installed. It might be the play services causing the device not to go night night....
[Nexus 6  Original Android Development] joeyddr:
Google play services I bet
[Nexus 6  Original Android Development] jkc120:
I have the smb135x_wake wakelock turned off according to lk, but it's by far my top wakelock as shown with the top 10 wakelock? Any ideas why? This is on v2.1 and I'm on stock 5.1 (LMY47D). Battery life seems ok, with 5% awake time. But I definitely had better battery life on 5.0.1 with lk 1.x.
[Nexus 6  Original Android Development] wrongway213:
You charging your phone? It disables it when not charging - literally cannot disable the wakelock when charging or your phone will die and, well, stay dead forever given we don't have a removable battery I guess.
[Nexus 6  Original Android Development] jkc120:
Nope, I typically charge once a night and leave it plugged in over night. Though perhaps the counter is being incremented then and that's why it shows up? Only way to tell I guess would be to reboot when not plugged in and wait to see if it increments?
[Nexus 6  Original Android Development] wrongway213:
That's what I would do yeah.
[Nexus 6  Original Android Development] Cheater912:
Just wanted to report that my battery went down to 2%, and Android shut it down gracefully :)
[Nexus 6  Original Android Development] WhoNeedszzz:
Having trouble with Deep Sleep on MeanPop 2.0.2. Is this a problem with the ROM or the kernel? Running 2.1 ocuc.
[Nexus 6  Original Android Development] mhseraph:
I think mean pop is set up to not go into deep sleep. Mike covers it in his thread.
[Nexus 6  Original Android Development] funcrusher:
Yes, unless you disable the blinking led in the build.prop.
[Nexus 6  Original Android Development] mrgwap:
Does this kernel have am app? How do we go about using faux sound
[Nexus 6  Original Android Development] WhoNeedszzz:
Oh ok I missed that. Good to know. I don't actually need the blinking led. Thanks.
[Nexus 6  Original Android Development] old_fart:
You use 'terminal emulator' and type 'su' and then 'lk'. Its covered in the OP or the page below the OP. . So you can toggle ( on/off )support for it.

---------- Post added at 01:14 PM ---------- Previous post was at 01:10 PM ----------

And then on an entirely different note . . .

David Ruddock is talking about "trusting your butt" ! . . . Er, ah, don't let it get in the way ! Is in an article in Android Police about a new 'feature' coming.

http://www.androidpolice.com/2015/0...-in-android-seems-to-be-hitting-some-devices/

.

We all need a little more 'trust' around here.

hth.
[Nexus 6  Original Android Development] flyinj54:
I wonder why Google implemented the change in 5.1 to the CPU slowing down to 2.2 gigahertz at 40% battery. Seems way premature to me. Hopefully this is something we can disable at the kernel level. It really drives me nuts and there's nothing you can do about it lol. I can understand it in battery saving mode but 40 percent is just ridiculous
[Nexus 6  Original Android Development] TMYINC:
Man this kernel + LightRom = wicked fast and smooth!!! Gonna try Cleanrom again since he just updated it but man does this kernel make any ROM faster then hell!!!
[Nexus 6  Original Android Development] __NBH__:
I totally agree, Google have a battery saving mode in the ROM so just let us pick the battery percentage it kicks in at and above that just let it run at maximum speed. Making all 4 cores online but under clocking the CPU is kind of cheating a bit, I've never known such an aggressive under clocking which comes as standard on a phone.
[Nexus 6  Original Android Development] bradputt:
[MENTION=3357040]Imoseyon[/MENTION]

Just wanna ask, is kexec support still in the pipeline ?

You said after v2.1 right?

I hate using stock kernel, it makes my screen very yellow.
[Nexus 6  Original Android Development] wrongway213:
I believe he's gonna wait for Tasssadar to release the full patch as its still not out - the only kernel with Tasssadar's kexec hardboot support implementation are the multirom test kernels, according to him they missed something trying to patch it on Vindicator before he released the patch, haven't tried it myself to confirm
[Nexus 6  Original Android Development] smclaughlin3:
What's the change in 2.1.1? Thanks
[Nexus 6  Original Android Development] bradputt:
Awwwww, guess it will be a long wait. Tassadar bricked his phone, development will halt for awhile. Didn't know they had problems releasing the patch.

Thanks for the info anyway.
[Nexus 6  Original Android Development] wrongway213:
Check his G+. In the N6 post comments section he gives his thoughts on it.
[Nexus 6  Original Android Development] Imoseyon:
Ok i'll make this happen for v2.2. :) Just gotta get my phone down to 40% battery....

Yeah I tried a while back using my old kexec patch but I don't think I got a low level hardware stuff quite right. And I've been pretty busy with Note 3 in the past week or so. At this point I'd rather wait for a working patch that I can apply cleanly.
[Nexus 6  Original Android Development] halfez:
not sure if this has been ask, but will there still be support for 5.0?
[Nexus 6  Original Android Development] wrongway213:
There still is. All versions 1.x are 5.0, 2.x = 5.1. Located in the same place in OP.
[Nexus 6  Original Android Development] halfez:
I meant future development
[Nexus 6  Original Android Development] Imoseyon:
Ok I have prevention code working for this. Hope to release 2.2 tonight.

Any reason why you didn't upgrade to 5.1?
[Nexus 6  Original Android Development] halfez:
Only still on 5.0.1 because of xposed framework. Probably won't upgrade until xposed is available.

Further lean kernel improvements would be great till then.
[Nexus 6  Original Android Development] wera750:
Soon.... Mine is in route. Will be awesome being back on leankernel. Still available to test like the good ole days. How you been Imoseyon?
[Nexus 6  Original Android Development] Imoseyon:
Gotcha. I will probably do one more v1.x release and that's probably going to be it.

Hey I think I remember you!
[Nexus 6  Original Android Development] 808phoneaddict:
Hey imoseyon, I been having the issue where my screen turns off when I'm on a phone call and won't turn back on unless I'm done with the call. I've been told this is a 5.1 issue, it's found on different roms and most people solve it by removing their screen protector because the proximity sensor is very sensitive in 5.1. Is there a way the kernel could have an option to adjust the sensor? Or maybe return the setting for the proximity sensor back to what it was on 5.0?
[Nexus 6  Original Android Development] Yank555:
I'm still on 5.0.2, haven't had tine to look at 5.1 yet. Where's this UC coming from, ROM, mpdecision or in kernel ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.8 kernel.
[Nexus 6  Original Android Development] old_fart:
I am running MeanPop, version 2.03 - is a solid, nice rom, stock based . . ( I wish it had the google bloat removed, so I didn't have to. . . I like lean things ) . . . I had the blinking LED all working nice the way I like it, woke up the following day and the blink was gone. Sob.

Put back in the stock kernel and it was still missing.

Dirty flashed the rom back in there and the blink came back.

Dirty flashed lk2.1 back in there and the blink is still okay.

Changed option3 in lkconfig to block all wake locks and the blink is still okay.

Powered it off and turbo charged it back up from being low . . . and the blink is still okay.

.

I wish to discover what clobbered the wakelock that MikeyXDA uses, but I am at a loss as to how to go about that. I recovered dirty so all the messing I did in settings and with freezing in TiB is still there and in play . . .

.

Well, MeanPop knows that leankernel is the goto kernel ( that plays nice ) . . .
[Nexus 6  Original Android Development] wera750:
I haven't got to run leankernel since the S3 days. I still remember testing your original workaround for the S3's locked bootloader! Lol
[Nexus 6  Original Android Development] jkc120:
Hey imo, open to a patch for the lk script that provides a backup/restore option? Thought it would be handy when switching ROMs for people.
[Nexus 6  Original Android Development] Imoseyon:
Hmmm I think that's more of a ROM thing than a kernel thing.

Backup/restore for the kernel? Interesting, I'll think about adding this to to TODO list.

All ROM. mpdecision and msm_thermal, but the prevention code is all in the kernel space - this way I don't really have to touch anything outside the kernel.
[Nexus 6  Original Android Development] Imoseyon:
v2.2 is up.

One notable change is kernel code to prevent /system components like mpdecision and msm_thermal from raising minfreq and lowering maxfreq via lkconfig (sysfs nodes). I no longer need to work in userspace (ie. disable mpdecision, change sysfs file permissions, etc.) to achieve this which is how I preferred to do things anyway.

Note this is *disabled* by default - you must enable it via lkconfig if you want this feature. Just to be clear, this is for those of you who 1) want to prevent unwanted minfreq changes, and/or 2) want to keep maxfreq from changing say when battery drops to 40%, etc. Hope it works. :p

Full changelog: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog
[Nexus 6  Original Android Development] nextelbuddy:
I'm on 5.1 with 2.1 uc/oc. I was on 2.0 and had no issues. Using lkconfig to adjust items.

Now that I'm on 2.1 changing nothing else, I frequently get FC and app not responding in all apps at random times...

I could click a YouTube link and instead of YouTube app opening, I get a fc... If I click the link again it opens fine.. Same with dialer app, I'll click phone button app and instead get fc not responding... Click phone app again and it works... I've got it in virtually every app.. Never happened with 2.0 and a week worth of usage out of it.
[Nexus 6  Original Android Development] flyinj54:
Almost at 40% see how it goes. Awesome work thanks

Working well below 40% life.
[Nexus 6  Original Android Development] franciscofranco:
Clever patch.

Did you test it for thermal throttle cases? Or that msm_thermal:fre is specific for this maxfreq lowering scheme when hitting 40% or 20% (1.7GHz)?
[Nexus 6  Original Android Development] old_fart:
Option 11, enter a 3 to get 'no' throttling . . . Ah, on the wake gestures, option 2, haptic dt2w = 1 ? ? ?
[Nexus 6  Original Android Development] Imoseyon:
What happens if you go back to 2.0? Do the FCs stop? What ROM are you on?

Is it me or is it pretty hard to trigger a true thermal throttling on our phone? I played Darkness Reborn for two straight hours to trigger it but was not successful. There are three msm_thermal processes: msm_thermal:hot, msm_thermal:fre, and msm_thermal:the. I'm hoping it's one of the other two that handles that, or maybe someone can go through the AOSP source to check. :)

Sorry... is there a question in there?
[Nexus 6  Original Android Development] franciscofranco:
It's not particularly easy to heat up this device (it's a good change, all the other Nexus were a disgrace on this matter, **** LG). Try this app: https://play.google.com/store/apps/details?id=com.into.stability&hl=en
[Nexus 6  Original Android Development] gnubian:
Awesome! Thanks [MENTION=3357040]Imoseyon[/MENTION] . Downloading now. Always loved your kernel on gnex.
[Nexus 6  Original Android Development] spinkick:
Thanks again!
[Nexus 6  Original Android Development] old_fart:
delete
[Nexus 6  Original Android Development] Franzie3:
[MENTION=3357040]Imoseyon[/MENTION] I have had the same similar problems to. Running 2.1 (about to flash 2.2) stable build on Chorma. Randomly in apps they force close, particularly Instagram. I have also seen some sporadic reboots occasionally. Not sure if its ROM or kernel related as volte things were being ironed out.
[Nexus 6  Original Android Development] Yank555:
I'll be good then as well, I don't use either of them anyway ... seems like too much hassle, they seem to come up with weirder stuff on each iteration ;)

Thanx for saving me time :D

JP.

---------- Post added at 02:12 PM ---------- Previous post was at 02:03 PM ----------

I have had something similar to this in my CPU hardlimit driver for quite a bit, I called it userspace DVFS control, it allowed to accept, ignore or refuse changes via scaling min/max sysfs interface (ignore would accept the value but not apply it, refuse would return EINVAL).

Though I'd not have done it without in-kernel thermal control tbh, this would be my only concern as well going this way...

JP.

PS: Stability test is indeed an excellent tool to trigger thermal control ;)
[Nexus 6  Original Android Development] Imoseyon:
I haven't seen any FCs myself. When this happens try to grab logcat - it's most likely not a kernel issue but logcat will usually tell you the culprit. Reboots could be a kernel problem, when this happens grab all files in /sys/fs/pstore/ and send them to me.

One thing I've noticed since going to 5.1 is the occasional failure for device to wake. It doesn't happen often enough to even be annoying but I haven't seen that behavior in 5.0. Hopefully this is not a kernel issue.
[Nexus 6  Original Android Development] dabadoo:
This is probably a noob question, but what does smb135x, sensor_ind, wlan_rx, and msm_hsic in the wakelock settings do? Is it safe to disable all/some of them?
[Nexus 6  Original Android Development] Damon13:
They are wakeloks which back in 5.01 used to keep the phone from deep sleeping. I am not sure if they are needed since 5.1 has corrected some of the issues.

---------- Post added at 05:27 PM ---------- Previous post was at 05:14 PM ----------

Yes, I noticed the failure for device to wake in a few occasions with stock kernel. In regards to V2.2 and option 11 to prevent unwanted minfreq, does it need to be disable in conjunction with keep maxfreq from changing in order for the phone not to throttle down in freq after reaching 40%? thanks in advanced
[Nexus 6  Original Android Development] franciscofranco:
No. If you only want to prevent these userspace daemons to mess with your maxfreq obviously just toggle the maxfreq thing on lkconfig. The other one is just to prevent them to mess with minfreq as well. It's self explanatory :p
[Nexus 6  Original Android Development] amelo28:
Can anyone offer any insight regarding this?

After not being able to find the cause or a solution for this wakelock, I did a clean install of 5.1 and it has been fine for the past few days.. after installing v2.2 last night (maybe coincidental?), the wakelock has reappeared and is preventing my phone from sleeping and the wakelock is even running when the screen is on. Once this wakelock starts, it doesn't stop until I reboot my phone. The reboot seems to temporarily fix the problem, but the wakelock seems to reappear intermittently. I saw someone else posting that they also had a problem with this, so any help would be appreciated. This is frustrating because it's really taking a toll on otherwise good battery life.
[Nexus 6  Original Android Development] Stigga:
Do these settings apply to the Franco Kernel Color Control? When I use these the colors are black and hard to read.
[Nexus 6  Original Android Development] mugendon:
This is just a wild guess, but I had something similiar with an audio wakelock, which was triggered, because I had NuPlayer enabled in developer settings. Switched it off and the wakelock was gone. With 5.1 the NuPlayer is the new default player, but you can still switch back to the old "awesome player" in developer settings.

Maybe you should give that a try. Hope this helps :)
[Nexus 6  Original Android Development] Imoseyon:
I see video2 in my wake source list, but not video3. Neither is in the kernel though. I can probably disable it (similar to what I did for sensor_ind) but I'd like to understand what it does first.

[MENTION=2687578]wrinklefree[/MENTION] was using savoca's app which uses numbers with an offset. You're probably better off using lkconfig, which has wrinklefree's reference settings in the simple config option.
[Nexus 6  Original Android Development] Stigga:
Ah that makes sense, thanks!
[Nexus 6  Original Android Development] Imoseyon:
[MENTION=2033478]Yank555[/MENTION], [MENTION=3292224]franciscofranco[/MENTION] and [MENTION=3795148]neobuddy89[/MENTION],

I've been looking through the thermal code a little bit and it does look like msm_thermal:freq_mitig task is responsible for all thermal related frequency changes. Although I don't think disabling this is terribly dangerous, especially since msm_thermal:hotplug is still active, I think there may be a better way to do this. I'll investigate this a bit more when I get a chance.

EDIT: Ah never mind! We're good! Frequency mitigation due to temp threshold crossing is handled internally, and outside of userspace msm_thermal:freq-mitig task!
[Nexus 6  Original Android Development] dabadoo:
Can you explain to me how "sensor_ind", or "msm_hspic" is "self-explanatory?

---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------
[Nexus 6  Original Android Development] PhilDX:
you kids notice that the screen seems to respond to touches while it's off when sleep2wake is enabled (v2.2)? I never noticed this with v1.x.

seems ok when only haptic DTW is enabled. sweep2sleep is working well too.

EDIT: I'm running the stock 5.1 LMY47E factory image
[Nexus 6  Original Android Development] seh6183:
Hello sir, sorry to bother you. I was wondering if you had any ideas about this wakelock problem im having. They changed something in 5.1 and now even with location services disabled I am still getting RILJ and NLP wakelocks. I didn't think this would be possible when I have shut down all location tracking on my phone. Any ideas?
[Nexus 6  Original Android Development] old_fart:
You did not say which rom you are using. . . The reason I am bringing that up is . . .

I am currently running MeanPop and it works really "great" ! . . Love the blinky winky function. . . Last night I tried lk2.2 haptic dt2w and it produced a hard lockup. . . I thought and then double thought about asking Imo to look at it . . . But it is a rom issue, the way I see it . . . I'll give up tapping for blinking. That's an easy decision.
[Nexus 6  Original Android Development] Chad_Petree:
I read that google now changed the way the cpu works and now all 4 cores are working at the same time and that's why 5.1 feels so smooth for nexus 6 users, is leankernel using the same configuration or is it like before that only the 4 cores would be used when doing extensive tasks? :confused:
[Nexus 6  Original Android Development] neobuddy89:
Only if you disable thermal-engine service (which I believe you haven't), msm_thermal of kernel will be activated.

So, I think you are safe :)

Yes, mitigation changes max freq of kernel when board reaches mitigation-temp. This temp is usually board limit to sustain highest temp.