yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Damon13:
Hello Imoseyon, loving your kernel. You mentioned before that you could possibly disable the sensor_ind wakelock, will that be implemented in a future release? The wakelock keeps my phone on for hours. I tried a few options but it still persists. Thanks for all your hard work.
[Nexus 6  Original Android Development] thejron:
Of course, be patient
[Nexus 6  Original Android Development] zephiK:
Huh? ... I'm using the notification LED on this kernel and it works fine. Its independent of the kernel. Simply using light flow and setting it up right will light up the LED.
[Nexus 6  Original Android Development] Circaflex:
is the paid version of lightflow still needed or can you now do it with the free version?
[Nexus 6  Original Android Development] BDR456:
Don't want to use another app to do it. Would rather it's native.
[Nexus 6  Original Android Development] wytecaztle:
Anyone have a link to the stock kernel?
[Nexus 6  Original Android Development] eep2378:
Here:)
[Nexus 6  Original Android Development] zephiK:
Yes paid version only as the free version hasn't been updated.
[Nexus 6  Original Android Development] jjhiza:
So happy to see Imoseyon back in action. I missed this kernel on the N5, so I'm excited to see what's in store for Shamu. I get mine on Monday, and I'll be rooting and loading this up ASAP. ?
[Nexus 6  Original Android Development] Imoseyon:
LED driver is enabled in leanKernel (as well as stock). I was actually thinking about disabling that driver since I thought with ambient display we wouldn't want it anyway, but I will leave it alone for now. :)

I think I may have done Captivate briefly...

beta2-2.9ghz build is up now. I will look into GPU OC soon.
[Nexus 6  Original Android Development] Xileforce:
GPU OC on the 420..can't wait to try it! The 420 is already an absolute beast!

---------- Post added 28th November 2014 at 12:04 AM ---------- Previous post was 27th November 2014 at 11:31 PM ----------

Quick suggestion. My processor is a 5, and in order to get through the antutu benchmark without the benchmark crashing while running at 2.9 I had to set my voltage for 2.9ghz to 1157mVolts in fauxclock. Maybe its just my phone but perhaps if other people notice the same it could be a good default voltage.
[Nexus 6  Original Android Development] rebretz000:
I was thinking I may have something up with my phone.

I ran it on AT&T for a few days before going back to Verizon.

Sent from my Nexus 7
[Nexus 6  Original Android Development] MrDSL:
thanks for the kernel!! seems to work good...

didnt fix my stutter issue in some of my games sadly but seems pretty smooth other than that.
[Nexus 6  Original Android Development] old_fart:
You did not state if you're running 'encrypted' or 'unencrypted'. Um, personally I would be curious if so and then which game too.
[Nexus 6  Original Android Development] cheami:
Kingdom Rush Origins as unencrypted and tried on beta0,1,2. I'm sure it's the game and not the kernel.
[Nexus 6  Original Android Development] old_fart:
Sadly, I just tried going from the beta2 ( two point seven gigahertz ) to the 'two niner' and no joy . . . . antutu v5.3 reboot every try . . . .
[Nexus 6  Original Android Development] simms22:
im a 5 as well, and have no issue running antutu at 2880mhz with the default voltage of 1145mV.
[Nexus 6  Original Android Development] seniorstew:
Stupid question.. If I flash it on my encrypted system will it wipe everything?
[Nexus 6  Original Android Development] simms22:
no. you can flash it being encrypted or not, without issue. if you want to decrypt, wipe your data first..
[Nexus 6  Original Android Development] MrDSL:
im unencrypted and the game is Castle Clash..

I am on a hardware 10 from which i read is pretty good. Both my chipset memory is Samsung.
[Nexus 6  Original Android Development] garyd9:
source?

thanks

Gary
[Nexus 6  Original Android Development] mugendon:
Only Fat32 is supported for writing (atleast from the Windows world. I guess every native linux filesystem should also work, but never tried it). NTFS for example won't work. Microsoft licensing issues ^^
[Nexus 6  Original Android Development] old_fart:
I have been using sdformatter

https://www.sdcard.org/downloads/formatter_4/

for quite a while to prep the sd card.

Micro sd hc are evil little things. It turns out that if you get a card for hi speed sequential, it is really bad in random access. In the past, I needed 'great' random access when I was popping and swapping the 'internal' sd on my sony experia. I passed that phone down to my youngest son. He wants to keep using the sony . . . even when I offered him my 'nexus 5' . . .
[Nexus 6  Original Android Development] Imoseyon:
Yup will look into that - no promises though...
[Nexus 6  Original Android Development] BubooBear:
I don't know if this has been asked before but I'm trying to undervolt. On on lk v. 1.12 and every time I try to undervolt with trickster mod it doesn't stick when I reboot. Also, mpdecision is off on both the trickstermod app and the the lkconfig. Can someone help me please?
[Nexus 6  Original Android Development] rignfool:
Thank you Beavis... ;)
[Nexus 6  Original Android Development] mugendon:
Silly question, but have you activated under "SET ON BOOT" the "Kernel Settings" in Trickster Mod?
[Nexus 6  Original Android Development] Imoseyon:
Hmmm I just ran into a semi sod and the phone went into safe mode. I've never had this happened to me. It may be lollipop or may be this test kernel version I'm on. Let me know if this happens to anyone else though.
[Nexus 6  Original Android Development] old_fart:
I was at the marketing kick-off last night ( old campaign slogan - "in it to win it" <<>> new campaign slogan - "we're here to 'pump you up !' " ) and was "trying", unsuccessfully to use google camera. It was bombing on me. The apple person sitting next to me was snickering up a storm ! I don't know why the camera app would be dorking ? ? ? . It did it again this morning, I r&r'ed it, and then it's not doing it any more . . .

. . . . That was my 'only' recent troubles . . .

.

Oh, I then too put in your new kernel version this morning.
[Nexus 6  Original Android Development] akellar:
Logs or it didn't happen ;)
[Nexus 6  Original Android Development] Imoseyon:
ah yeah v1.12 should fix the camera issues i think.
[Nexus 6  Original Android Development] mugendon:
I miss the vibration very often in my pocket. Is it somehow possible to enhance the vibration? The max value 127 is already stock and I wan't more :)
[Nexus 6  Original Android Development] magnum870:
I have this with every phone.....thats one of the reasons I got a LG G Watch (wish the 360 had been out when I was in the market...) :)
[Nexus 6  Original Android Development] Imoseyon:
Lol first request for this. I'll look at the code later to see if it's possible.
[Nexus 6  Original Android Development] mugendon:
Had the galaxy nexus before and didn't miss the vibration. Seems strange since I read from many people complaining about the n6 vibrates to strong :) But somehow it is to weak for me.

So thanks [MENTION=786144]imo[/MENTION] for looking into that :)
[Nexus 6  Original Android Development] Imoseyon:
sensor_ind

Who wants to try a fun experiment?

In v1.12.1, I disabled the sensor_ind wakelock from within the kernel (even though the wakelock itself gets created from the ROM) here: https://onedrive.live.com/?cid=F1ED4BADFEE3FC02&id=F1ED4BADFEE3FC02!440

I'm curious to see what this breaks - it's not obvious to me after an hour of using this version.
[Nexus 6  Original Android Development] magnum870:
I actually think its a bit weak too, but I figured its a design flaw (or just a different type of motor than I'm used to?). Its quite noisy, but doesn't feel very strong. Just thought I'd put in my 2 cents earlier about how much I love Android Wear. Its fantastic :)
[Nexus 6  Original Android Development] mugendon:
I think the problem is, I use vibrate only in my pocket. When the phone lies on my desk I use priority (aka silent) mode. Guess if others use it on the desk it might me quite loud as you said :)

@ android wear: Had a moto 360, but couldn't handle the difference in display density from n6 to the moto360. Felt like using a htc wildfire on my wrist ;)
[Nexus 6  Original Android Development] suku_patel_22:
Have flashed it. Let's see if I run into any problems.

Sent from my Nexus 6
[Nexus 6  Original Android Development] wrongway213:
Will be curious to hear... cannot get this wakelock to tame no matter what I try, if it doesn't cause issues this needs to be spread to stop everyone's headaches.

Obviously curious to see if it breaks ambient display, adaptive brightness, auto-rotation or even Hangouts, primarily, but I imagine Imoseyon tested all those already lol
[Nexus 6  Original Android Development] beyeond:
Yeah my line of work involves walking around a lot so unless I'm standing still, I don't feel the vibration. But this isn't unique to shamu for me though. Had the same issue with my s3 and my epic. Would be interesting to see if you can make it stronger.

On the other hand I do like to use it as an excuse to avoid talking to certain people..
[Nexus 6  Original Android Development] suku_patel_22:
Been 5 hours on this kernel. No issues whatsoever.

Ambient display, Adaptive brightness, all sensors, auto rotate, GPS every ****ing thing works.

In these 5 hours I used every app that had caused me sensor_ind wakelock in the past. G+, Hangouts, Riptide GP, Androsensor.

And ofcourse there is no sensor_ind **** in BBS anymore. I would say we should make this final!!

Sent from my Nexus 6
[Nexus 6  Original Android Development] tysonwald:
totally AGREE. I have been running it for a few hours now and the battery standby has increased noticeably. Ca't wait to keep experimenting and seeing where these things go
[Nexus 6  Original Android Development] Damon13:
Hey

Thanks for the feedback, do you have adaptive and ambient on? Thanks in advanced
[Nexus 6  Original Android Development] suku_patel_22:
I have adaptive brightness on and I hate ambient display.

Sent from my Nexus 6
[Nexus 6  Original Android Development] old_fart:
The first thing that popped up on the screen after load was "Unfortunately, launcher2 has stopped" . . . Probably a rom thing.

In lk settings, in option #12, I could not see / tell what I had set the cores to.

.

Question : is the GPU 'really' always chugging away at 300 mega hertz ? . . even when the phone is resting and relaxing ?

.

At home, I get POOR radio reception. The one testing app I tried went "bonk, bonk, bonk" and then said I lived in a bat cave . . . . Honest. Can you turn "OFF" the wake lock(s) tied to the crumby cell radio reception ? . . That would be nice !
[Nexus 6  Original Android Development] Imoseyon:
Well, this begs the question why is the ROM holding these wakelocks when it has no business holding them, at least most of the time? And are there other wakelocks like this?

Either way, it looks like I will make this a user configurable option in the next leankernel version, enabled by default but can be disabled via sysfs/lkconfig.

What exactly happens? Screenshot? If you're on euphoria or other roms with leankernel integrated it's possible they haven't include lkcc script yet.

I can disable any wakelock in the kernel but then we'd all end up with semi functional phones. :p
[Nexus 6  Original Android Development] wrongway213:
This is exciting... sensor_ind is a huge problem for me. As I see wakelock block requests coming, I figure I may as well ask: is this something that had to be done to the kernel itself, or is there an echo command/sys path etc. that can be user to turn this (or possibly other) wakelocks off? I'm quite curious about how this particular process works as killing wake locks was so simple at the user end on KK.
[Nexus 6  Original Android Development] Imoseyon:
Well disabling wakelocks and creating/exposing a userspace control via sysfs isn't that hard, and this is exactly what I did for the smb135x wakelock, and what I'm going to do for sensor_ind. One big difference is that smb135x wakelock is created within the kernel, whereas the sensor_ind one is created from the ROM, which makes the latter method a bit of a hack/workaround (I pretty much tell kernel to ignore a wake source named "sensor_ind").

This is doable whether you're on KK or LP - you just need a kernel dev who's willing to do the implementation (they can look at my source once i'm done with it).
[Nexus 6  Original Android Development] dsmitty166:
Everything works in euphoria now

?
[Nexus 6  Original Android Development] wrongway213:
Awesome, thanks so much. Am I to assume disabling a wakelock via sysfs is not possible on the user end without dev intervention such as this, then? Or is it possible if you know what you are doing for a user to disable via sysfs? Sorry for all the questions, this has been the single biggest problem on the N6 for me by far... I need closure :-p i appreciate you dumbing it down for me as much as you can as always.
[Nexus 6  Original Android Development] Imoseyon:
That's correct. Sysfs nodes for wake sources are not in kernel by default and must be created by the dev. In fact, I might have created this whole sysfs control for wakelocks concept. ;)
[Nexus 6  Original Android Development] slekkas:
Do we know what is the sensor_ind used for?
[Nexus 6  Original Android Development] wrongway213:
You, sir, are truly an awesome developer. I greatly appreciate your effort to make a process far beyond my comprehension user friendly like you just have, and moreover your general attitude of willingness to debug and fix issues that will help EVERYONE on the N6, regardless of if they use your kernel or not. Sensor_ind isn't an LK issue for certain, and as it turned out it's not even a kernel issue, but it's a huge problem for the community and so you just step up, fix it, and move on with your day.. know that those of us who don't have the power to influence the experience of other users like you do greatly appreciate all you do to make sure everyone on this device has an awesome experience.
[Nexus 6  Original Android Development] suku_patel_22:
It finally is a relief to be able to use g+ and hangouts without the worry of sensor_ind. No need to greenify anymore!!

Sent from my Nexus 6
[Nexus 6  Original Android Development] old_fart:
Within option 12, which is like a nested, sub function, you press option 0 to see where the core control setting is currently at. . I give it a zero and then I don't see that it's telling me the setting. . It just seems to be repeating the options.

okay . . . . . . I'll run the android app "Timed Toggles (Auto Airplane)", seven days a week and turn off the cell radio all the time that I'm at the house . . .
[Nexus 6  Original Android Development] Imoseyon:
Can you do a screenshot? It should look something like this:

leanKernel core control
---
WARNING: Using this script may change things outside the kernel (ie. mpdecision)
and may interfere with other apps like Trickstermod. Use at your own risk!

0) display current setting

1) prevent mpdecision from scaling cpu - 2 cores online (cpu-boost off)
2) prevent mpdecision from scaling cpu - 4 cores online (cpu-boost on)
3) prevent mpdecision from scaling cpu - 4 cores online (cpu-boost off)
4) back to stock/default - reenable mpdecision

please enter a number (or press enter to exit): 0

Setting 2: Mpdecision disabled. Cpu-boost on. 4 cores online
[Nexus 6  Original Android Development] old_fart:
Argh ! . . ah, for me there is no 'shot' but rather a 'record' ! ? ! ? Hmmm, something high jacked the shot . . . . where can I find that ? how can I un-do that ( simply ) and get back to shot ? . Hmmm . . .

.

In a nutshell, i'll choose 4 and then look by pressing 0 and i'll tell me it's on default . . . for me . . .
[Nexus 6  Original Android Development] wrongway213:
Power buton and volume down to screenshot whether enabled in menus or not.
[Nexus 6  Original Android Development] old_fart:
chuckle, chuckle, wish it was... for me its a record and 6 megabyte versus 6 kilobytes . . . hmmm, well many YEARS ago, i purchased a copy of a screen shot . . . let me find it and load it . . . .
[Nexus 6  Original Android Development] old_fart:
A shot attached.

.

So, it is working fine and I am just confused. ( where's the coffee pot ? )
[Nexus 6  Original Android Development] spyder52:
The version numbers for this kernel do not make sense...

v1.12 is the latest (2/5/15) but v1.2 was released on (12/19/14)

Should be revised..
[Nexus 6  Original Android Development] DatDude123:
It increments by .1 each build.

D
[Nexus 6  Original Android Development] wrongway213:
Oh, I just assumed you were asking how to screenshot if it was missing from your power menu... I've never seen screenshot re-mapped to screen record in a ROM or anything like that before I don't believe... learn something new everyday on XDA
[Nexus 6  Original Android Development] spyder52:
Well for the first several versions it incremented by .1 and now it is .01

Hard to tell in the download folder which Kernel is the most recent
[Nexus 6  Original Android Development] NikWillOrStuff:
just use "Sort By: Date Modified", probably the easiest way
[Nexus 6  Original Android Development] nobnut:
I'm lolling at you right now. I'll show your post to some folk later. They'll be lolling at you also.
[Nexus 6  Original Android Development] Remoteconcern:
They're numbers. One point one, one point two etc. Now we are on one point twelve. It does not need revising.
[Nexus 6  Original Android Development] 12MaNy:
^ This made me actually Lol.

It's 1.12......not 1.1.2

I kinda get where you're coming from though. Usually a version goes to 2.0 after 1.9
[Nexus 6  Original Android Development] wrongway213:
Those lasts posts all made me laugh.. the idea that Imoseyon can debug every kernel issue under the sun but is just a little rusty on his 1's and 12's is indeed comical.

Anyone else on 1.12.1 with sensor_ind disabled? I'm currently testing the last possible system config I can to try to kill this wakelock/locate its source in relation to display, so I am curious to hear how it's going as I'm waiting to flash.. I wanna ensure the sensor_ind wakelock is still an issue with this config before disabling it, as I would much rather not need to do so if there is some sort of configuration that allows the wakelock to shut itself off like normal instead of holding. How's it working out for you guys testing it?
[Nexus 6  Original Android Development] Damon13:
Wrongway,

So far so Good, I have been on V1.12.1 and the sensor_ind has been non existent. I have adaptive on and ambient off. Its been over 5 hours and it doesn't appear at all in wakelock detector.

Thanks so much Imoseyon!
[Nexus 6  Original Android Development] buggerthis:
Well, that is mathematically correct. 1.12-1.11=0.01

But yeah it's version numbers, not math.
[Nexus 6  Original Android Development] Imoseyon:
leanKernel versioning

My versioning scheme is this:

[major].[minor].[bugfix/test] (ie. 3.32.3)

This is a pretty standard convention in the software world. Also very close to mainline Linux versioning scheme. For instance Linux 3.14 is not the same as Linux 3.1.4.

One drawback of this scheme is the small confusion it creates when the number goes from single digit to double digit. I try to avoid it when I can, and as soon as LP 5.1 kernel is released, it will be v2.x. :)
[Nexus 6  Original Android Development] PeenX2:
Been running v1.12 for a few days now on fresh Pure Shamu ROM, full GAPPS, everything on and installed. Facebook on, location services etc, all the battery draining stuff. Still getting well over 24hrs battery life with 4-5hrs SOT.
[Nexus 6  Original Android Development] ballaz:
The sensor_I'd fix has been working great. The stupid wake lock has been the biggest pain in the arse with regards to the N6.
[Nexus 6  Original Android Development] slekkas:
The sensor_ind fix has been working also fine with me. How can I set minimum to 300 and maximum 2600 for the CPU in this kernel?
[Nexus 6  Original Android Development] wrongway213:
A kernel tweaker app, I'd recommend Trickster Mod. Turn off mp-decision using lkconfig core control if you want the values you set in Trickster to stick, simply disabling mp-decision from Trickster Mod won't work and leaving it enabled will cause your values to be reset.
[Nexus 6  Original Android Development] slekkas:
Which option should I use. 2 or 3?
[Nexus 6  Original Android Development] wrongway213:
Personal preference, but 3 goes back to stock, personally I use 1.
[Nexus 6  Original Android Development] slekkas:
OK, thanks

---------- Post added at 04:17 PM ---------- Previous post was at 04:13 PM ----------

How are you finding this kernel concerning our common sensor_ind problem? Have you encountered any problems? How do you find battery life?

In regards to option 1 does it use 2 cores when idle and 4 cores when needed or it only uses 2 cores all the time?
[Nexus 6  Original Android Development] wrongway213:
I'm not entirely sure how it works and have yet to flash the test kernel with sensor_ind disabled, I'm still trying running ambient on, adaptive off to make sure this config also gives the wakelock problem - if it does I will then conclude there is no other fix and test the kernel myself... really just wanna flash and forget but not in the middle of testing a config, that'd be too much time watching wakelock stats wasted lol.
[Nexus 6  Original Android Development] slekkas:
Even if this works for you I don't like to use ambient display. Every other test I tried failed so testing this kernel is a one way for me.

If anyone cares to answer my question about which mp-decision I should use?
[Nexus 6  Original Android Development] wrongway213:
I dislike ambient display as well. As for mp-decision, it depends on if you want more performance, or more battery friendly. Keeping all four cores on will use more battery, keeping two on will be less performance-inclined.
[Nexus 6  Original Android Development] rignfool:
Option one is 2 cores all the time... With touch boost off

Option two is 4 cores all the time... With touch boost on...

Option three... Which I use... Is 4 cores with touch boost off...

I get like 6 hours SoT and... I can play real racing 3 for an hour...
[Nexus 6  Original Android Development] Damon13:
Sorry for this question, I am still trying to fully understand LK, Can I enable option 3 while being in power aware scheduling mode? This Kernel is great and i am currently in v1.12.1 and the sensor_ind after a day has not appear in wakelock detector.
[Nexus 6  Original Android Development] wrongway213:
Curious, have you tried 2 cores? AnTuTu scores are still 51k+ for me with two cores, makes me wonder if the difference in performance between two and four cores would even be noticable/worth the battery life hit.
[Nexus 6  Original Android Development] Imoseyon:
Option 1 will use all four cores when needed.
[Nexus 6  Original Android Development] wrongway213:
...and that would explain no drop in benchmarks. Beautiful!
[Nexus 6  Original Android Development] Damon13:
Imseyon, I would like to say thanks for the test build v1.12.1, The sensor_id is not existent and battery life is a much better. Can I enable option 1 or 3 within LK while being in power aware scheduling mode?
[Nexus 6  Original Android Development] Imoseyon:
My power of observation isn't that great but so far I haven't observed anything broken with sensor_ind wake source disabled. In fact, I feel like battery life is better with it disabled but it's only been a day so who knows.

yup powersaving mode are independent of the core control options.