yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] slickie88:
Agree. To be honest I'm not that concerned with it unless it starts happening a lot more frequently than it has been.
[Nexus 6  Original Android Development] old_fart:
I was remembering a few pages back where [MENTION=3357040]Imoseyon[/MENTION] was talking about advanced wipe and the clobbering of : cache and dalvik cache . . . One kernel ( or maybe even 'custom rom ) can mess with the stable running of a later one. . . . I saw this when I ( weeks ago . . . ) installed a new lk and then the antutu dropped ( consistently ) from 52k down to 44k. . . . I had to do a 'clean' to make it all back to normal .

.

Ah, a couple daze ago when I updated euphoria from 0118 to 0124, I noticed in 3C tools that core one with staying ( stuck ? ) at 1.7 megga jiggles . . . . And I wiped cache and dalvik cache and reloaded lk1.9 and "TAA DAA" - the core one was normal again . . .

hth.
[Nexus 6  Original Android Development] dsmitty166:
hey guys,

look at this :) https://github.com/imoseyon/leanKernel-shamu/pull/2
[Nexus 6  Original Android Development] tysonwald:
I had the same issue. Pish the power button and nothing. Push it three or four times and the screen would finally come on. It happened enough that I switched to Franco kernel to see if it was my phone, ROM , or kernel. It was kernel as I don't ever have that issue since switching.
[Nexus 6  Original Android Development] Franzie3:
Stalker....lol ;)
[Nexus 6  Original Android Development] Imoseyon:
Hmmm... those of you with screen wake (power button) issues, can you post some data please?

1) Which governor do you use?

2) If you're running interactiveX, what is your screen off frequency set to?

3) Have you undervolted?

4) Any other kernel customizations you made?

I have a few guesses as to what it could be, but since I can't reproduce let's see if we can find a pattern. Also try v1.10 which should be released today as well.

thanks!

[MENTION=4983347]beyeond[/MENTION] & [MENTION=5907697]tysonwald[/MENTION] & [MENTION=811336]slickie88[/MENTION]
[Nexus 6  Original Android Development] Franzie3:
this is for the smb135x_wake right? if so i have weird stats.

lkconfig shows it as my number 1 but when i open up Wake Lock detector and look for it under kernel wakelocks it only shows it at 1 second and x74. WLD shows msm_hsic_host as my #1 kernel wakelock which lkconfig shows as my #2. Kinda weird.

My settings are as follows

interactiveX

screen off max frequency 2265600

not undervolted, never have

only customization is the d2tw set to 1.
[Nexus 6  Original Android Development] magnum870:
I have seen this a few times myself. I'm basically stock beside wake gestures, but I'll answer the questions specifcally

1) Default governor (I don't even remember what it is right now, I uninstalled all kernel tweakers cuz it just runs smoother with defaults for me)

3)No Undervolting

4) Wake gestures enabled.

As a side note, I think I first saw this issue after enabling the wake gestures, but I'm not positive on that (but I was using the power button to try to wake in all incidents where I considered it an "issue"). So maybe others can shed light on the possibility of the gestures bit causing trouble. The issue has happened probably 4 times over the last month, and the phone always ends up waking, its just after 10-15 seconds.
[Nexus 6  Original Android Development] Imoseyon:
Nah it's for some folks who have occasional issues in waking up the phone via the power button.

If the issue is wake gestures, it could explain why I never see the bad behavior. Let's gather some more data from other folks who are seeing the same bad behavior.
[Nexus 6  Original Android Development] natezire71:
I DO NOT have the issue, but also have wake gestures enabled.

1) Default

2) Default

3) Default

4) Have a script setup to enable the dt2w gestures alongside lkconfig
[Nexus 6  Original Android Development] b.huss2:
Happens to me as well:

Clean SlimROM + PA gapps + Supersu + Franco kernel (straight up default kernel settings)

Never really thought it to be a major issue but thought I'd chime in because others are seeing it. It's not just leankernel.

Edit: DT2W is enabled.
[Nexus 6  Original Android Development] Imoseyon:
Interesting... If I can reproduce it on my phone I can fix it. :)
[Nexus 6  Original Android Development] Smallsmx3:
Everything is default on the kernel side. I have power save on. Gesture is on 4. LED light on.
[Nexus 6  Original Android Development] Cy_n_ic:
Wake gestures. I use sweep2wake. Powersave mode. All else is default from install other than color calibrations. I would definitely suggest enabling the gestures to see if you can reproduce the sleepy screen. Bear in mind it is quite infrequent for me. Maybe only 2-3 times a week i notice it.
[Nexus 6  Original Android Development] tysonwald:
I don't remember my settings as this was last week. But here's what I do remember

1) stock

2) stock

3)no undervolt

4)no

Running slimLP alpha the whole time. I will try v1.10 and see with my setup if I get that issue again.
[Nexus 6  Original Android Development] resynx:
I've had the wake problem on Franco kernel too, so it's not just a lean kernel thing.
[Nexus 6  Original Android Development] zephiK:
It would appear that video has brought a lot of confusion. I honestly don't even know why that app is even brought up into the Lean Kernel thread as it has nothing to do with the Lean Kernel.

Vomertweaks is just a alternative pre-configured setup (min/max freq, governor settings, cpu boost settings, hotplug, etc) designed for Franco Kernel, [MENTION=1363323]vomer[/MENTION] was creating a app and I decided to fork a Franco Kernel with flar2's dt2w/s2w/s2s commit. So since vomer was already creating a app, I asked for him to include flar2's dt2w/s2s/s2w tuneables in the app so users using the modified kernel can enable/disable settings.

And indeed, Imoseyon already has flar2's gesture controls already enabled and thats accessible via "lk" or "lkconfig" in Terminal Emulator. Although, users of my ROM has stated that having the gesture controls enabled makes the screen to not be turned off during calls so should be noted.
[Nexus 6  Original Android Development] vomer:
THanks :)

now if only I could get some noob named [MENTION=3357040]Imoseyon[/MENTION] to get on board and get his kernel supported too :p :cool:
[Nexus 6  Original Android Development] Imoseyon:
hmmm do I need to do anything on my end? Is there a special club i need to join or something? :p
[Nexus 6  Original Android Development] Imoseyon:
v1.10 is up: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

Notable changes are:

1) the cpu error due to cores in low power mode getting unclocked is fixed (v1.9.4)

2) smb135x wakelock can now be disabled by user via sysfs node (use lkconfig). If you're getting unusually high wake lock count from smb135x even while not charging, i'd give this option a try.

3) merged pull request from Euphoria to include faux sound.

For full change log click on the link above. Enjoy...

Edit: i will continue to try to reproduce the screen not waking up issue. Fingers crossed...
[Nexus 6  Original Android Development] fitz420:
Thanks for adding fauxsound!!!!!!!
[Nexus 6  Original Android Development] franciscofranco:
Yes, you need to wire me 5k.
[Nexus 6  Original Android Development] Imoseyon:
Didn't I buy beers last time we met? yes you owe me drinks
[Nexus 6  Original Android Development] inzaghi75:
Which gov do you recommend Imoseyon?
[Nexus 6  Original Android Development] frenchy714:
I know this wasn't directed to me but you should be golden with stock settings.

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] Imoseyon:
Yup stick to default. Interactivex
[Nexus 6  Original Android Development] inzaghi75:
First reboot I had theme chooser fc. Now it works.
[Nexus 6  Original Android Development] Imoseyon:
Try to grab logcat when theme chooser fc's?
[Nexus 6  Original Android Development] Imoseyon:
Try to look at the whole logcat file and look for "denied" messages? If not, just attach the whole file here.
[Nexus 6  Original Android Development] old_fart:
Have a thousand line long log ( lazily languishing at large ) in the notepad++ and searched for denied and got naadaa . . . sorry !

... i'm pretty sure if i try a cm11/12 theme . . . it'll freeze . . . but that was last week and I only got ( high quality ) cm12 themes now . . .
[Nexus 6  Original Android Development] beyeond:
[MENTION=3357040]Imoseyon[/MENTION]

I'm on all default kernel settings and no wake gestures, unless they're enabled by default
[Nexus 6  Original Android Development] Mervingio:
THANK YOU!!
[Nexus 6  Original Android Development] zephiK:
Nothing at all, vomer just has to make a pre-defined configuration set up on your kernel. Quit slacking vomer! :D
[Nexus 6  Original Android Development] Imoseyon:
I'll tell you what. I've been putting the phone to sleep and hitting the power button all day to replicate the issue. :D No luck so far though.
[Nexus 6  Original Android Development] beyeond:
Thanks for taking the time to try. It's by no means a major issue. About to flash the new release..
[Nexus 6  Original Android Development] natezire71:
So, what kinda stuff can you do with fauxSound? I've never used a kernel with it.
[Nexus 6  Original Android Development] PeenX2:
Running V1.10 now, I did a fresh clean install of Pure Shamu 3.98 with LK v1.10ocuc. Initially I had the sensor wake lock running havoc even with no Hangouts, adaptive and ambient off. Went away though after 32m of being on. I am a bit curious since I am a hard core PC over clocker, how are you keeping 2.88ghz stable on this? I can run the same voltage and clock on other kernels and they crash benching. Turn the clocks down on the other kernels and it's fine then.
[Nexus 6  Original Android Development] inffy:
What is needed to make a kernel not to force encryption? What needs to be modified on the kernel level?

I want my CM kernel not to force encryption
[Nexus 6  Original Android Development] spinkick:
So i downloaded fauxsound app from the play store and it says that you cant modify anything for the speaker because its using a seperate DSP. fauxsound does not affect bluetooth audio so basically this is for tuning headphones on the nexus 6? I cant see any other reason for it. Anyone?
[Nexus 6  Original Android Development] Cy_n_ic:
Its for headphones and the built in speakers. Another DSP would be like viper or whatever other dsp manager things these crazy kids do now days.

---------- Post added at 11:00 PM ---------- Previous post was at 10:58 PM ----------

http://xdaforums.com/showthread.php?t=2946715
[Nexus 6  Original Android Development] spinkick:
Yeah but it says that the speakers are ran through another DSP so faux cant control them.
[Nexus 6  Original Android Development] Cy_n_ic:
So turn the other off?
[Nexus 6  Original Android Development] inffy:
Thanks but I have my own built CM rom for Nexus 6 and I just want the stock CM kernel not to force encryption.
[Nexus 6  Original Android Development] Cy_n_ic:
My bad. I thought there were instructions. Sorry
[Nexus 6  Original Android Development] Imoseyon:
The change is in the ramdisk: https://github.com/imoseyon/leanKernel-shamu/commit/58ac4f97d882414bdea35d0d1ef0cd6f9027a3bb
[Nexus 6  Original Android Development] spinkick:
Its a digital sound processing chip, not an app like viper
[Nexus 6  Original Android Development] vomer:
lol I will pm you soon :) just need some details from ur end re: kernel setup/structure

---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------

Can confirm :crying: :p

---------- Post added at 12:20 AM ---------- Previous post was at 12:19 AM ----------

Dammit.. you caught on my slacking :( :angel:
[Nexus 6  Original Android Development] tom.lockhart:
Fine to flash newest version right over the top if 1.9?
[Nexus 6  Original Android Development] Mocheen:
Yes, you shouldn't have any problems.
[Nexus 6  Original Android Development] adrman:
[MENTION=3357040]Imoseyon[/MENTION] Disabling the smb135x wakelock causes the charging led to behave erratically when the device is on my qi charger. If it would have pulsed with any regularity, I'd have said you solved the always on led issue. Placing the device on the factory charger cable returned the led to normal, always on. I don't think the disabled wakelock interfered with charging, just the led, as the charge indicator on the qi pad was solid. Re-enabling the wakelock returns the charging led to always on.
[Nexus 6  Original Android Development] magnum870:
Mine says the same. Definitely no apps like Viper installed. I should've taken a screenshot, but I've already refunded the app.....
[Nexus 6  Original Android Development] rignfool:
FauxSound is not a DSP like the CM one...

Its an amplification gain tweak...

It will turn up the output of your speakers...

Even in call volume...

Sent from my Nexus 6
[Nexus 6  Original Android Development] blinde:
Does lightflow work with 1.10? Apparently it didn't work with 1.9.
[Nexus 6  Original Android Development] old_fart:
After 1.9 to 1.10, I noticed my gmail notification is not going "brang-alang-alang-alang" for twelve hours . . . So a couple hours ago, I went into gmail and sure enough, there was 'good ol' spam in there waiting for me to nuke. Now that I'm sitting at my desk at work and I woke the phone up and then . . . it does this "brang-alang-alang-alang" in my face and the notification tells me that the 'windoze secrets' - monthly email has arrived ! ! !

.

And I haven't seen a LED light for almost a week now . . .

.

thinking . . . probably, for me, the multiple switching in and out of 'themes' glitched it . . .
[Nexus 6  Original Android Development] PeenX2:
Lightflow has worked for every Kernel I've tried including LK1.9 and 1.10.
[Nexus 6  Original Android Development] spinkick:
but it says it cant for the nexus 6 speakers..
[Nexus 6  Original Android Development] Smallsmx3:
I've tried your slim and cm builds.. No new slim for awhile?
[Nexus 6  Original Android Development] natezire71:
Yeah, I know its not a DSP; however, I didn't know you can adjust the in-call volume, so that's helpful.

Is there any way to change this stuff without buying Faux's app? I'd rather do stuff with scripts.
[Nexus 6  Original Android Development] Imoseyon:
I don't use this feature so I haven't really looked into its controls but look for a sys directory called "sound_control_3", and mess around with it.
[Nexus 6  Original Android Development] flying_pigs:
Thanks so much for the updated kernel. Been using it since the beginning and it's been flawless.

However, FauxSound significantly degrades the speaker audio quality. Any way to get rid of it? I tried adjusting the settings in FauxSound but it still sounds like the volume has been boosted waay too much and causes it to crackle and distort.
[Nexus 6  Original Android Development] old_fart:
I updated again to the newest Euphoria rom and 3C Tools again shows that my core1 is not budging at all . . . If I now wash out [MENTION=2906672]dsmitty166[/MENTION] version of lk1.10 and go to the one here . . . will it again go back to bouncing up and down ?

.

here I go.

.

Nope, core1 is not budging from the 1.49 gigga-wiggles oscillatory state.

.

going to try next the 1.10ocuc one . . .

Good golly miss molly . . . ran into a snag. tried to use 'terminal emulator' and it insisted on google VOICE as the input and in setup it would NOT let me toggle that one away to a normal keyboard. Went to play store and downloaded 'google keyboard' and yeah ! am able to use the 'terminal emulator' and wow, surprise . . . all of my old setting were still in there and in effect as I set them two days ago. ie. boost off, vibe at 55, etc . . .

.

And ( the most important thing ! ! ! ) the 3C tools /cpu manager shows the core1 bopping on and off as ( i believe ) it should . . .
[Nexus 6  Original Android Development] Imoseyon:
This happens even when you don't have it enabled using the faux sound app? If so, this is disturbing and I will revert ASAP - similar stuff happened on the note 3 kernel and i had to revert all the faux commits to fix it. Let me test a bit as well.

What app are you using to check core1 (second core) speed? What happens you turn off screen for a while, turn it back on and check again?
[Nexus 6  Original Android Development] old_fart:
It is '3C Toolbox Pro' ( got it several years ago when I had a job paying 'good' money ) Is a very nice one, and the dev has updated to accommodate lollipop.

I have gone power 'off and on' many times in my checks and validations. The stick ( for me ) was solid !

---------- Post added at 10:59 AM ---------- Previous post was at 10:50 AM ----------

I have a ( china special ) sound pressure meter. When I get off work, I can crank up the sound ( oscillation ) app and take some DBa readings.

( disclosure ) And I have a BAD case of tinnitus and wear hearing aids . . .
[Nexus 6  Original Android Development] Cy_n_ic:
I do not have the fauxsound app and have not messed with sys/kernel/sound_control_3 at all.

Speaker audio sounds fine for me. No popping or cracking at all. I see no need to revert the commit unless its just not working right once user begins to adjust it. I planned on trying to boost in call volume if i can figure that out without the app (no im not cheap, it just seems like more fun that way).
[Nexus 6  Original Android Development] Imoseyon:
I just put up a bug fix release v1.10.1. This version does not fix a bug in v1.10, rather it fixes a bug I introduced in beta3 (!!). I reverted one commit from android that apparently causes occasional stutter - I'm sure this is in most custom kernels out there as well.

Thanks to [MENTION=710997]funcrusher[/MENTION] for testing all leankernel versions starting from beta0.

https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

edit: lol, and i accidentally threw in a change that was going to go in v1.11. This change made the kernel a bit leaner by removing a couple of big debug functionality.
[Nexus 6  Original Android Development] funcrusher:
No problem, [MENTION=3357040]Imoseyon[/MENTION]. Thank you.

[MENTION=4770693]Krunk83[/MENTION]

[MENTION=2781818]sn0warmy[/MENTION]

I know you guys were experiencing the same occasional stutter on custom kernels - specifically the unlock stutter. Give v1.10.1 a whirl.
[Nexus 6  Original Android Development] smclaughlin3:
good looking kernel so far it seems to be the only one letting the minimum frequency of 300 stick. going to try the latest one props to the dev because

i ran this on my previous phone the note 3 tmobile and now the nexus 6 tmobile. btw using trickster.

Thanks.
[Nexus 6  Original Android Development] old_fart:
Should I try the 1.10.1 to see if it has a "core1 doesn't move" condition ? ? ?
[Nexus 6  Original Android Development] Imoseyon:
yes it won't hurt but i believe your problem is elsewhere. Can you try using a different app like kernel tweaker and trickster mode and see if they show the same behavior?
[Nexus 6  Original Android Development] Damon13:
Sorry for this question, do I need to tweak this kernel at all? I prefer to just flash and let it do its job. I am coming from FK R10. I prefer not to messed around with LKconfig or MPdecision. Thanks
[Nexus 6  Original Android Development] PeenX2:
Trying 1.10.1ocuc, I didn't even notice the unlock stutter until it was just mentioned. It's a pretty minor stutter, but the new Kernel seems to make it go away in my 10min of testing :)

---------- Post added at 09:27 PM ---------- Previous post was at 09:22 PM ----------

Although I can't seem to make the msm_hsic_host wakelock go away. Seems to be a problem with all kernels and rom's on my phone though.
[Nexus 6  Original Android Development] old_fart:
Ya, I too was thinking that this is part of ( 1 ) boost off, or ( 2 ) no_freq. affects . . trying now.

.

So, the lk1.10.1 also says ( for me ) that core1 is stuck on 1.5 GHz. Trickster and 'System Monitor' also showing the same.
[Nexus 6  Original Android Development] oak:
I don't tweak it at all. Works great as is for me.
[Nexus 6  Original Android Development] Smallsmx3:
Lkconfig is actually really nice. All your doing is running terminal commands. I'm the same and never cared for kernel apps. I feel sometimes they cause more harm then good. I just like to flash a kernel and be done with it. But there are some basic options that are useful like turning on power save or the led
[Nexus 6  Original Android Development] Imoseyon:
That wakelock is actually necessary. If you use cellular data network a lot, you will see high count of that wakelock.

Hmm try turning cpu-boost back on and restore stock mpdecision. Let me know if that helps.
[Nexus 6  Original Android Development] Damon13:
Thanks, I will tried LKconfig for the power save mode. Do I need terminal emulator in order to access lkconfig. Have you seen any improvement in battery with power save?
[Nexus 6  Original Android Development] old_fart:
That was it ! . . With lk1.10.1 and then only changing the "cpu boost" back "on", the core_1 is flipping like core_0 . . .

( i had already restored the stock mp_decision, always do, with the normal lk )
[Nexus 6  Original Android Development] sn0warmy:
Thanks for the heads up. Giving it a try right now.
[Nexus 6  Original Android Development] blinde:
Lightflow doesn't work with 1.10 & slim. With 1.8 it works just fine.
[Nexus 6  Original Android Development] Imoseyon:
Ok i'll take a look at cpu boost and see if I can replicate your condition.

Try re-installing lightflow?
[Nexus 6  Original Android Development] spinkick:
Thanks for the update

Lightflow seems like a nightmare lol
[Nexus 6  Original Android Development] PeenX2:
Works for me, but I'm using a different ROM.
[Nexus 6  Original Android Development] jackpollard:
Powersave works great. I have cpu boost off and powersave and get great battery life. Yes you need terminal emulator, fire it up, enter "SU", then either lk or lkconfig. Try out the advanced rgb also, someone calibrated the colors and I find 248, 246, 255 really good.
[Nexus 6  Original Android Development] Cy_n_ic:
+1 i use the same values and white no longer has that yellow tint to it. Also lkconfig is awesome. I would opt for it over any tweaker app any day! It seems we are configured quite the same with powersave and no cpu boost. No complaints here what so ever.

Downloading latest update right meow and keep up the great work [MENTION=3357040]Imoseyon[/MENTION]
[Nexus 6  Original Android Development] smclaughlin3:
Would flashing the no/disable mpdecision keep the min freq at 300 more stable also disabling mp decision enables what substitutes it? Thanks
[Nexus 6  Original Android Development] Imoseyon:
Interesting I can reproduce this when cpu-boost is disabled.
[Nexus 6  Original Android Development] tom.lockhart:
What exactly does powersave do?

Also - by default is cpu-boost on within the kernel.

I will add that I also LOVE the lkconfig, easy to use, and the changes stick! Thats the best part, with other kernel apps I had trouble getting the changes to stick.