yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] xtzz:
Tested v2 on latest CM nightly (cm-12-20150313-NIGHTLY-shamu). Went past the animation, finished rebuilding apps cache and went into bootloop after that.

reverting t v1.17 for now.

P.S.: previous animation with the flying dots is better :)

Edit: corrected SM -> CM.
[Nexus 6  Original Android Development] djcsurf:
Is that ROM 5.1?

V2 kernel is ONLY for 5.1 as imoseyon has previously stated!
[Nexus 6  Original Android Development] xtzz:
:eek:

Tnx... I definitely need to get some sleep already.
[Nexus 6  Original Android Development] Imoseyon:
Ah that was an interesting side effect on Note 3 and not intentional. Doesn't work on Nexus 6.
[Nexus 6  Original Android Development] old_fart:
I haven't had an LED light up since my second install of 5.1 ? Was I smoking something ( mind altering ) when I read the core added aid to the light emitting diodes ? Was that only applicable to the N5 ? - - - - Well maybe LEDs are broke ( for me ) because I froze 30+ system ( google bloat ), multi-megabyte hogs. I felt a necessity to re-install after testing / comparing six separate kernels. Psst... Secret... Imoseyon makes the best. The scores indicate the camera support could (maybe - possibly ) be better. But the kernel is a very dynamic beast. A ten headed snake ? . My intuition says - he improves one area to the possible detriment of another area.
[Nexus 6  Original Android Development] tibere86:
Not sure if it's the lack of coffee, but I can't find your cpu workqueue reversion commit. Mind pointing me to it :p
[Nexus 6  Original Android Development] jkc120:
I'm on v2.0 and it seems like about half the time it won't wake up when I pick it up. It's not after a notification. If I turn the screen off and put it down for a minute then pick it up, it often doesn't wake the screen. Anyone else?
[Nexus 6  Original Android Development] michmeister:
I'm on att I don't have advanced 4g lite option in cellular settings like others have with 5.1.
[Nexus 6  Original Android Development] PhilDX:
if the sensor_ind wakelock is disabled in v2, you might try re-enabling again
[Nexus 6  Original Android Development] GPS3:
Would someone mind pointing me the way to the flashable stock 5.1 kernel? Imoseyon mentioned he uploaded it but I am not seeing it. I would like to have it "just in case". Thank you.
[Nexus 6  Original Android Development] jkc120:
Indeed it was. Was it on by default in 1.x? Because I don't recall having any problems with this on 1.x.

---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------

Additionally, if anyone has a link to a stock 5.1 kernel with force encrypt disabled, I'd like that as a backup.
[Nexus 6  Original Android Development] Jaspah:
Because AT&T doesn't support the Nexus 6 with VoLTE (yet).
[Nexus 6  Original Android Development] PhilDX:
I believe so, yes. I've been reading some comments on your issue in Franco's thread suggesting that google made changes related to this in 5.1 and now ambient display is laggy if the wakelock is disabled. no idea if that's really true though.
[Nexus 6  Original Android Development] Imoseyon:
Stock no force encrypt kernel is in my onedrive folder.
[Nexus 6  Original Android Development] jkc120:
Interesting, thanks! I'm sure imo will figure it out in due time :) Was this the wakelock that was causing some people to have battery drain with hangouts?
[Nexus 6  Original Android Development] IcipherPT:
My device doesn't enter in deep sleep, got stuck at 300... Clean install of rastapop with lean 2.0.1. Already try to reflash kernel and nothing :(
[Nexus 6  Original Android Development] jkc120:
Hmm, I'm stock with v2.0 and seeing only 5% wake time, almost all due to ambient display.
[Nexus 6  Original Android Development] GPS3:
Oh OK. I didn't see a version number so I assumed it was the original 5.0.x.

Thanks for all the hard work. :)
[Nexus 6  Original Android Development] Smallsmx3:
There's a couple on the forums.... Only IMG files though, no zips
[Nexus 6  Original Android Development] colinmcg71:
Could be the Google Play Services wakelock, what version are you on?

The latest version 7.0.96 from APKmirror has cured it for me.

http://www.apkmirror.com/apk/google...ices-7-0-96-1785884-430-android-apk-download/

Edit: fix link.
[Nexus 6  Original Android Development] old_fart:
I saw you mention 2.01 ( un-announced ( as far as I know ) ) test version. Hmm, what is he fixing ? I dnld'd it and am running it. Ugg ! Is eighteen percent slower than 2.0. I double checked . . . Back to 2.0 !

.

At what battery level does android roll your perf. capabilities back ? . . Is it 28 percent ?

.

ya, low battery messed with it !
[Nexus 6  Original Android Development] IcipherPT:
I'm aware of wake lock and service was blocked with disable service app... But I didn't update it. Going to try that and report, thanks :)
[Nexus 6  Original Android Development] akellar:
I'm getting a lot of bluesleep lock. Probably a 5.1 thing and not the kernel but thought I'd mention it.
[Nexus 6  Original Android Development] spinkick:
Do you have a android wear device? Lots of us were getting the same wakelock on 5.0
[Nexus 6  Original Android Development] akellar:
Yeah I know the wakelock is needed. I think it may have been related to another device it was trying to connect to but couldn't. Forgot that connection and it's improved.
[Nexus 6  Original Android Development] reinert012:
is sensor_ind wakelock on by default or do i need to change something? I;m not new to kernels but new to specific things about kernels.
[Nexus 6  Original Android Development] IcipherPT:
Still got wakelock and stuck at 300 :\ I tried another kernel and the problem remains, maybe it's not related with this
[Nexus 6  Original Android Development] colinmcg71:
Sorry to hear that. Do you have Better Battery Stats or Wakelock Detector installed to find out what's holding the Wakelock?
[Nexus 6  Original Android Development] rauschkugl:
Wake gestures from flar2 don't seem to work on version 2.0. When plugged into the charger Core 4 turns off and didn't turn on again for me. Everything else is running really smooth until now.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] old_fart:
For wake, use terminal emulator and go into su / lk, and set it to the one [MENTION=3357040]Imoseyon[/MENTION] created.

.

Ya, ( for me ) all four cores wink on and off from 300.

hth.

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

I had it ( twice, honest to God ) where one kernel 'screwed the pooch' on leankernel and I could 'only' get it all back happy with a clean install ( wipe data, and system and cache ) . . . . .

---------- Post added at 08:27 PM ---------- Previous post was at 08:18 PM ----------

Ran benchmark Vellamo Metal on 2.01 and got :

1969 ( kick every one else's a$$ really bad ! )

dhry / linp / bran / stre / ramj / stor

286 / 292 / 168 / 320 / 339 / 565
[Nexus 6  Original Android Development] rauschkugl:
I'm not totally stupid and of course did enable them before. But only Google d2w works for me and not the implementation from flar for d2w and s2w.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] CatInTheHat422:
Not sure if kernel issue but after making a call and turning the screen off I can't wake the phone using gestures. If I use the power button the screen will come on and afterwards respond to gestures. anyone else get this?

Ambient display is set to off also.
[Nexus 6  Original Android Development] GregNexus:
Does anyone know, how long the input_boost_duration is? 3 secs like on stock?
[Nexus 6  Original Android Development] rauschkugl:
It seems to be lower when watching it in sysmon. Could be wrong though, I don't know what the update cycle of the app is.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] old_fart:
You are right, I apologize. Appears running 'stock' broke all of this goodness. There is a aosp 5.1 - hmmm, I'm going to go try that on next . . .

.

franciscofranco says they made changes in the touch driver.

http://xdaforums.com/showpost.php?p=59438886&postcount=4280

.

I just used trickster to turn 'on' dt2w and s2w, and they work. They don't work 'great' but they work . . .

.

Am now on [MENTION=2746542]Stephen[/MENTION]'s aosp 5.1 and the gestures are pretty much the same as in stock . . ie. ( for me ) working poorly . . .

Oh, stephen's build runs zippier !
[Nexus 6  Original Android Development] rauschkugl:
Do you guys have all cores running on stock 5.1? For me only two are on now. Don't know if the others hotplug on load but at least it's not like on stock kernel where all cores are on all the time.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] old_fart:
Am using '3C Toolbox', and it says all 'on' all the time, mostly at 300 . . .

---------- Post added at 09:47 AM ---------- Previous post was at 09:33 AM ----------

Mr [MENTION=3357040]Imoseyon[/MENTION], sir . . . First I apologize if this has been reported already . . . In lkconfig, min freq is reported to be a gig and a half ( and we all know that it really isn't ) and that is because the option 11, mpdecision is 'on' by default and messing with the reporting of reality . . . ? ? ? ? With four cores cranking all of the time ( no hot plugging ), do we need a booster too ?
[Nexus 6  Original Android Development] hellsgod:
Yes mpdecision (power HAL) boosts the frequency to 1497mhz for about 3 seconds on all cores. Thats the way google wants it, if its really needed is questionable. Like the decision to leave all cores on by default.

hells
[Nexus 6  Original Android Development] Imoseyon:
Ok I'm back in town. Let me start working on v2.1 - there are some minor bugs I need to fix as well. I may need to crank out a Note 3 LP kernel first so v2.1 may take a few days.

Here you go: https://github.com/imoseyon/leanKernel-shamu/commit/079ad4c9b57518f434078ef2187ca701b90809f8

Turns out I reverted that a long time ago. :)

I haven't looked into this yet but I'm thinking v5.1 fixes the sensor_ind wakelock issue and I can safely re-enable it by default. I'll probably do that as part of v2.1 release.

You probably have an app that's preventing the phone from going into deep sleep.

Ah yeah I'll fix this soon.

Yup all cores are running by default with android 5.1. If you don't like mpdecision messing with your minfreq, you can disable mpdecision (via lkconfig) but once you've done that any cores that go offline (ie. thermal events) won't come back online automatically.
[Nexus 6  Original Android Development] reinert012:
What is sensor ind wake lock, do I need to enable it to help with wake locks?
[Nexus 6  Original Android Development] grayskul:
Well how's people's battery life going on 5.1? That's what I'd like to know!?
[Nexus 6  Original Android Development] old_fart:
lp5.1 has a "new" way to improve battery life. And I think google's new trick is sneeky and crappy at the same time. But I'm a performance maniac. I want POWAH ! ! ! . . . . there's this new thermal folding in play. I remember it of a couple months ago and then the dev cured it. . It's back ! . . . Well, along with a new, "battery at less than 40 percent" fold . . . . we get an sizable, auto slow down.

.

There is confusion on the Euphoria Rom thread. They "just" brought their 5.1 version out in beta ( last couple bugs scurrying here and there ) and because they have a working 'themes' ( not rro ) engine, the SePolicy ( permissive ) and then the ramdisk have to be right.

http://xdaforums.com/showpost.php?p=59469478&postcount=2647

I thought mosey clobbered all that policy stuff weeks ago ?

Is lk2.0 the same as lk1.x in this respect ?
[Nexus 6  Original Android Development] hazard209:
Try this with the Tasker app if you have it or are willing to shell out a couple of bucks for it. It worked for me though.

1. Create a profile based on "Event > System > Device Boot"

2. Add a "Run Shell" action with the command "pm enable com.google.android.gms/.update.SystemUpdateService" and tick the "Use Root" option

3. Add a "Run Shell" action with the command "pm disable com.google.android.gms/.update.SystemUpdateService" and tick the "Use Root" option

Credit: eurochild on Google+
[Nexus 6  Original Android Development] Jaspah:
Definitely has improved in my case. The modem update seems to have improved my reception and my time without signal went down significantly (from 20-25% to 3%). Less time searching for a cell signal means a much better battery. :)
[Nexus 6  Original Android Development] Xileforce:
He did but in the update to 5.1 he removed most CM related stuff in this commit https://github.com/imoseyon/leanKernel-shamu/commit/b86b5da60cb648efd86b0be71e9cc282c13ed9b9 however Imo has already fixed this and will most likely release today. Euphoria Dev was working with him and they got a test build working :) I believe flashing a permissive.zip after flashing kernel is a temporary fix ATM. Don't hold him to that release tho lol. I'm just passing on what I've heard from euphoria Dev.
[Nexus 6  Original Android Development] old_fart:
You must not be on t-mobile. . Yikes, poor t-mobile has a black eye and a bloody nose trying to go from 5.0 to 5.1 - wtf ! This is a billion dollar company . . .

.

Ah, the old story of "missing" pieces for the asop crowd . . .
[Nexus 6  Original Android Development] Imoseyon:
Yup custom ROM selinux support is officially coming in v2.1, but v2.0.6 (in testbuild folder) also has it.
[Nexus 6  Original Android Development] Jaspah:
Haha, AT&T actually. But it's basically the same GSM frequencies. The building I work in just has terrible reception.
[Nexus 6  Original Android Development] boysetsfire:
I'm on stock kernel at the moment, but for me has improved quite a lot, been getting 5 hours of screen on time really easily on a typical day with a pretty heavy usage too. Now going to flash lean, can't stay without all the goodies it provides [emoji12] also I'm curious to see if battery will get even better, but seeing the previous releases I'm pretty confident it will [emoji16]

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] imna357:
Wooo, its been a long time, Imoseyon is back I used to use his lean kernel 2 or 3 years ago, before FRANCO AND ELEMENTAL came out, this is the best kernel before and probably now=).
[Nexus 6  Original Android Development] Franzie3:
hey [MENTION=3357040]Imoseyon[/MENTION] , i had the issue where the phoen shuts down before getting to 0%. I was at 4-5% and the phoen randomly shutdown. This was on my first cycle after flashing LK with Chroma 5.1 build. Let me knwo if there is anything i can grab you if i see it again
[Nexus 6  Original Android Development] lainemac:
I see 2.1 is up! Waiting for an official word on the new goodies. :D
[Nexus 6  Original Android Development] Imoseyon:
v2.1 is up.

Not a huge update. Just a few minor fixes. CAF updates. sensor_ind wakelock is now enabled by default. Should work on custom ROMs like Euphoria now.

Full changelog: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog
[Nexus 6  Original Android Development] gannjunior:
Hi [MENTION=3357040]Imoseyon[/MENTION]

I've read in the faq your kernel support the color management.

and I've read this post:

http://xdaforums.com/showpost.php?p=59092146&postcount=3017

Are those value usable in all nexus 6 or they are usable only on that specific nexus 6 ?

Since for example I calibrate the monitor of my pc one time every month but the calibrations settings are useful only for my specific monitor sample...

In trickstermod app I can adjust only R-G-B and no other settings...

What do u suggest?

Thanks for your job

ciao!
[Nexus 6  Original Android Development] Berlino:
You can use Kernel Adiutor from Playstore for KCAL settings or Savoca's app. :)
[Nexus 6  Original Android Development] suku_patel_22:
KCAL is so similar to the other KCAl(kilo calories), wish that was adjustable by some settings :D. Would solve lot of issues
[Nexus 6  Original Android Development] fahadali2315:
Just flashed 2.1 on Euphoria 3-16 5.1 build. No SystemUi crashes anymore ;) Everything is solid..
[Nexus 6  Original Android Development] michmeister:
Is it best to enable mpdecision ?
[Nexus 6  Original Android Development] old_fart:
I was reading over in the MeanPop thread. . . . ( I'm sorry, I'm a sucker for blinky/winky lights ! ) . . . Veteran rom cooker [MENTION=2712518]mikeyxda[/MENTION] and then also guru [MENTION=426561]scrosler[/MENTION] were / are trying to cure the BUG with black screens on calls for lp 5.1 . . .

http://xdaforums.com/showpost.php?p=59493456&postcount=273

They've combed thru the rom code and they're thinkin that "maybe" it's a kernel problem . . .

Question : do your new fixes in lk 2.1 fix this issue ? ? ?

.

And then also . . .

Because the google gods have come out and "admitted" there is a memory leak in lp 5.1 and they're not sayin when they'll be puttin out the fix. ( they gotta fix ! ! ! ) . . . Will you be reverting your reverts and increase the cache ?

re "Revert tweaks to reduce cache to give more RAM to apps, because 5.1 fixed memory leak issues? Right?"
[Nexus 6  Original Android Development] Imoseyon:
This is a bummer. I was hoping the behavior got better with 5.1. :/ I guess significant battery life offsets this somewhat.

You can use lkconfig for color management as well as apps mentioned in above post.

I'll take a look at this black screen issue - I haven't seen it myself. (edit: he's talking about proximity sensor - this would most likely be a rom thing, and not kernel)

As for the LP5.1 memory leak, can you point me to some information on that? I kinda assumed Google would have fixed it in 5.1.
[Nexus 6  Original Android Development] Franzie3:
Yea i know i thought the same thing. I usually never get that low on a charge but i was having such great SOT i was being greedy and pushed it. By chance do you know if it was ever reported to El Goog? Not sure if anyone on a Stock ROM/Kernel has had the same issue. I thought i had seen someone did somewhere
[Nexus 6  Original Android Development] neobuddy89:
-- delete --- :P
[Nexus 6  Original Android Development] Franzie3:
[MENTION=3357040]Imoseyon[/MENTION] just an FYI, AOSP now has build LMY47E for Shamu.
[Nexus 6  Original Android Development] amelo28:
Is anyone else getting a video3 kernel wakelock on v2.1? BBS is telling me that video3 is keeping my phone awake when the screen is off (for 1 hr 20 mins) and it's really killing my battery. Does anyone know what this wakelock is..?
[Nexus 6  Original Android Development] wrongway213:
Source? Not finding it on AOSP or Google Code
[Nexus 6  Original Android Development] Franzie3:
Sorry..Meant factory images.... Source can't be far off
[Nexus 6  Original Android Development] Imoseyon:
Don't see kernel source yet but when it shows up I'll be ready! :)

Edit: if ramdisk differences between 47d and 47e are any indication, the kernel is same between 47d and 47e as well.
[Nexus 6  Original Android Development] Yank555:
From what I read, they fixed it, but since we have a new version, they "planted" a new leak... to keep the suspense going ;)

JP.
[Nexus 6  Original Android Development] chris23445:
Just curious, what carrier are you on? I see people getting 4+ hours SOT on GSM carriers. I am on Verizon and can't even get to 3 hours with stock rom and kernel. I installed lean yesterday and hopefully I can hit 3 hours. I don't even use it crazily.
[Nexus 6  Original Android Development] Franzie3:
Since being on 5.1 with LK 2.0 (now 2.1) i eeked out 5 hours SOT mixed between wifi and LTE
[Nexus 6  Original Android Development] chris23445:
Are you also on Verizon?
[Nexus 6  Original Android Development] boysetsfire:
I'm in Italy and on Three, so GSM for me! Currently I have 3 hours of screen in a 12 hours period, battery is sitting at 49% but I was on Wi-Fi all the time today... Even though sometimes I feel like my battery lasts longer on 3G/4G :confused:
[Nexus 6  Original Android Development] Franzie3:
Yes Sir
[Nexus 6  Original Android Development] mkcbbusiness:
Yesterday I also got 4+ hours of SOT with v2.0 and stock rom. Probably could have gotten more but had to go to sleep lol.
[Nexus 6  Original Android Development] Franzie3:
Sleep is for the weak!! LOL I was 4 hours 54 minutes yesterday with heavy use, lots of rebooting due to flashing radios, kernel, rom, restoring tibu etc etc.

I will say even today im at about an hour of SOT an only at 80%, mainly being on LTE. I had to reboot once to check somethign on the bootloader, but overall this is probably the most solid release i've ever seen.

And to be honest i expected it. a new version of Android was bound to have little issues here and there, stuff done in 5.1 seems to have very nicely cleaned it up making it super stable and smooth. Im really curious as to what the Droid Turbo with 5.1 OTA will be pushign out with that massive 3900mah battery lol
[Nexus 6  Original Android Development] magnum870:
Its kinda weird stuff, and not an exact science. The first 2-3 months I had my phone I was pretty easily getting 3+ hrs screen on time (pretty good for me, very little reception in my office at work), but recently (the last month or so) I've been only getting about 2. Not sure what's changed, but its strange. I'm on AT&T now, but started on VZW the first month or so. Basically my post is to alleviate fears of it being carrier related, but also to say that I'm at times befuddled as to how people get the good battery life even though I do sometimes get it too!
[Nexus 6  Original Android Development] jfcooley:
Funny this screen on time has come up, I've been testing mine for daysz.

Yesterday 4 hours heavy use. I just flash the kernel, do little else other than Greenify. My sot is a little lower during the week, Sprint signal blows where I work.

That's for the great kernel.
[Nexus 6  Original Android Development] rauschkugl:
With 2.1 wake gestures are working again but the Problem while in call is still there or back. Single taps don't do anything but if I perform a gesture for screenwake during a call the display turns on and the call ends at the same Moment. I don't even have to press the hang up button.

Could you have another look at this problem?

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] eep2378:
I flashed 2.1 last night on stock 5.1 image. Went to bed and woke up with the phone completely off. Power button would not wake. Had to long press power to start. It was fine for a few minutes and then it was time for my alarm to go off so I hit snooze and it made this weird buzzing noise and rebooted again. When the device rebooted the alarm tone was still going off. Weird.
[Nexus 6  Original Android Development] michmeister:
On 5.1 euphoria with 2.1 lean kernel everything working except phone will not go into a deep sleep.
[Nexus 6  Original Android Development] akellar:
Not necessarily (pretty unlikely) a kernel issue.
[Nexus 6  Original Android Development] wrongway213:
Sensor_ind being "fixed" on 5.1 = false. Just had a 21m wakelock on a 5.1 ROM with 5.1 radio, 5.1 BL and LK 2.1 running. I finally disabled it via lkconfig and it still didn't end until a reboot.
[Nexus 6  Original Android Development] chris23445:
I saw that someone else posted about the video3 wakelock. I went to bed with 96% and put my phone on airplane and now I'm at 61%. Video3 wakelock kept my cpu awake for 8 hours. Any ideas as to what this is?
[Nexus 6  Original Android Development] indigo888:
Look here http://xdaforums.com/showthread.php?p=59526759

It's not a kernel issue. Proven.

Awesome kernel!Thanks dev!
[Nexus 6  Original Android Development] gannjunior:
[MENTION=3357040]Imoseyon[/MENTION]

I tried lkconfig by terminal: I believe the old "type bar" is always the best! thanks!