yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Imoseyon:
Someone asked for this: http://pastebin.com/ZyGA9Tec (stock freq/voltage table)

Sorry I can't answer everyone question in timely manner - gotta code. lol

Oh, if you're having trouble decrypting - try formatting data in recovery or fastboot.
[Nexus 6  Original Android Development] caspersfi:
I can't run a minimum frequency under 1267 without freezing up. Weird. I'm running NOSP and encrypted. If that makes a difference.
[Nexus 6  Original Android Development] mhsbrian:
I'm using setcpu using lowest mhz and highest mhz. Using noop with ondemand governor and everything is nice and smooth ;] °
[Nexus 6  Original Android Development] stuff:
Nope, I'm unaware of any other apps. Which should I try?

trickstermod told me it correctly earlier though. I ran antutu at that same time, and got a score of around 49-50k. Now get around 40-41k and it's telling me I am at 1.7ghz
[Nexus 6  Original Android Development] flyinj54:
I use faux clock but it's another paid app. How about trying cpu spy. You can check each clock speed and how many second the cpu was at that speed. You may want to play a game after you open it to be sure you will max the CPU out. Also I would remove trickster just to verify the app isn't affecting your cpu settings at all
[Nexus 6  Original Android Development] stuff:
cpuspy says it never touches frequencies above 1.728.

Though it does say it touched 2.6ghz for 3 seconds. Which is odd. Though I think it did that when I rebooted my phone.

Reverted back to v1.0, thinking MAYBE it was a v1.1 issue.

No change. Still stuck.

I'm out of ideas.
[Nexus 6  Original Android Development] Imoseyon:
Install Kernel Tweaker or Trickstermod and post a screenshot of your CPU stats (time in state). I don't think anything is wrong with your phone. It's quite normal for your phone not to use high frequencies often unless you're running benchmark applications all the time.
[Nexus 6  Original Android Development] stuff:
I'll let it run for a few moments before posting it. I just rebooted my phone.

Also, maybe I'm mistaken, but my mpdecision file is not located in /system/bin/.

It's simply missing. I copied the file over there a few times already, once it told me I was replacing it.

The other two times, after a reboot, it doesn't tell me; because it's not there.
[Nexus 6  Original Android Development] stuff:
This is a screenshot. Touched 2.6ghz for 4 seconds.
[Nexus 6  Original Android Development] laureanop:
I concur with Stuff. Stock kernel loves the 1479, 1728 and 2649 frequencies, while it rarely uses the 300 .

This is a screenshot of your kernel (default settings , interactive x)
[Nexus 6  Original Android Development] laureanop:
Screenshots
[Nexus 6  Original Android Development] stuff:
I know the frequencies are hard to control on this device. I don't mind that. But I simply can't get anything about 1728.
[Nexus 6  Original Android Development] simms22:
its all about how you set your cpu up. mine doesn't hang around 1728. i disable mpdecision for real, via terminal emulator, then change my cpu speed, adjust my governor/scheduler, and it always sticks.
[Nexus 6  Original Android Development] stuff:
Is disabling mpdecision simply

$ stop mpdecision ?

The thing is, my CPU max would stick earlier. Then all of a sudden it no longer does.
[Nexus 6  Original Android Development] laureanop:
As long as the device is fluid and responsive I don't mind the scarce use of the higher frequencies. Less heating and probably better battery
[Nexus 6  Original Android Development] stuff:
Well same here. But I would also like to know why it seems like it refuses to clock higher than 1728 :/
[Nexus 6  Original Android Development] laureanop:
Flash the stock boot image, clear all kernel control files leftover from previous flashes and then come back to LK. ( watch your encryption status)
[Nexus 6  Original Android Development] simms22:
its, in terminal emulator..

su(press enter)

stop mpdecision(press enter)
[Nexus 6  Original Android Development] stuff:
Flashed stock boot.img without force encrypt, cause I don't want to deal with that.

From what I can tell, my phone only goes above 1728 mhz during the boot phase. Once inside the OS, it won't hit above 1728.
[Nexus 6  Original Android Development] Imoseyon:
There's something wrong going on with your phone. Your screenshot of time in state is not normal. It's gotta be a cpu control app you have installed or a previous custom kernel you've installed that's left something behind that it shouldn't have (ie. touched something outside of kernel).

I bet things will become normal if you do a full factory reset, including re-flashing your system partition.
[Nexus 6  Original Android Development] Imoseyon:
custom mpdecision

Turns out the no-minfreq custom mpdecision I made is not adequate. It still modifies your max frequency more often than I would like.

So I created another one called nofreq-mpdecision.zip here: https://onedrive.live.com/?cid=F1ED4BADFEE3FC02&id=F1ED4BADFEE3FC02!394. This one should not mess with your min nor max frequencies at all.

Again, I recommend that you flash this custom nofreq-mpdecision, only if you like to set custom min/max frequencies. Otherwise, you're fine using stock mpdecision.

(small caveat - i haven't been able to trigger a thermal event in my testing yet so I haven't seen what thermal-engine is capable of. It does look like it's able to manipulate your min/max frequencies just like mpdecision but I haven't seen it in action yet).
[Nexus 6  Original Android Development] stuff:
I might just end up performing a full factory reset and wipe system partition.

I haven't flashed another kernel besides yours. So I really am not sure what's going on.
[Nexus 6  Original Android Development] Imoseyon:
You also mentioned that you don't see a file called /system/bin/mpdecision, even though you flashed one of my custom mpdecision zip files. So there's a clue that something is definitely wrong with your /system partition.
[Nexus 6  Original Android Development] old_fart:
I am going to jump in here and say "I did all that last week and it did not fix my device sticking to low frequencies" . . . . . I think I tried twice ! full factory, wiped system . . . . Hmmm . . . .
[Nexus 6  Original Android Development] Imoseyon:
I think your issue is most likely different than what stuff is going through. Your issue is probably solved by flashing the new no-freq mpdecision file (check a few posts before), or just sticking to stock mpdecision. Or just disable mpdecision altogether, although I'd prefer you use custom or stock.
[Nexus 6  Original Android Development] stuff:
Multiple times I rebooted and the file was completely gone.

In the process of flashing now though.
[Nexus 6  Original Android Development] Imoseyon:
If I were to guess? You got an app which disables mpdecision (poorly) by simply removing the binary instead of issuing the stop command. Why don't we move this to PM so we don't clutter up this thread?
[Nexus 6  Original Android Development] laureanop:
Two folders left over in root/data/app from Trickster Mod were deleting the binaries from system/ bin/ mpdecision. Had to delete those files , format and re flash system.

You were 100% correct Imo
[Nexus 6  Original Android Development] stuff:
Well in my situation, I flashed over the factory 5.0.1 files with the script.

Then flashed over latest twrp recovery.img. Same with the no-encrypt boot.img.

booted up, and downloaded cpuspy (since I didn't have root then). The cpu states still looked the same, 1.7ghz touched almost entirely.

Rebooted, flashed SuperSU 2.40, flashed v1.1 kernel. Still having troubles.
[Nexus 6  Original Android Development] frenchy714:
Can we just flash this newer version over the previous one, or do you recommend we flash the stock mpdecision file, then this updated custom one?

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] stuff:
Just to settle it, after staying up late, and multiple formats of /system, my issue finally is gone.

I formatted over /system 3 times in a row, just to be sure. Apparently it worked.
[Nexus 6  Original Android Development] old_fart:
I am rooting for you. I know ( and other people have experienced it also ) that it will be gone for a ( relatively short ) while and then the frequency sticking comes back. . Maybe the basic design of the 'thermal protection' is like 'mr. toads wild ride' !

Hmmm, it looks like other N6 kernels are talking about it too . . . .

http://xdaforums.com/showpost.php?p=57579626&postcount=621

---------- Post added at 07:30 AM ---------- Previous post was at 06:58 AM ----------

Thank you for your continuing effort. . . You got a full plate and then you have to deal with "us" whiney guys . . And the really old ones are semi lucid ! . . . I plugged in that new mpdecision you built ( eight hours old now ) and I am sorry to report it did not change "my" frequency stiction . . . Am using the 1.1ocuc .

.

I then ( just now ) plugged in the "stock mpdecision, and ran system monitor and then antutu and i saw that the 1.8 gigga willies were gone and it was ( occasionally ) displaying 2.9 gigga willies ! ! ! . . . . and then I see it about 31 per finished and it is not 2.9 any more but rather 2.5 and then the percent counter seems stuck and then it reboot. . . And it does the same routine three times in a row. . And the device it actually COLD to the touch. . . Hmmm ? . Did the heat sync / heat spreader fall OFF the cpu ? ? ?

.

And then I bumped the voltage to the cpu 50 millies and it no longer ( consistently ) rebooted at 31 percent finished . . . but rather made it ALL the way through the antutu torcher session and the score was : 50319 . . And the 'system monitor' is showing the freqs are NOT going to 2.9 and staying but rather bee bopping around in the upper range. It seems to like 2.5 over 2.9
[Nexus 6  Original Android Development] Imoseyon:
You can flash over the old one.

So contrary to what you thought, when you flashed a custom ROM you also most likely flashed a custom kernel that came with the ROM. Some custom kernels out there leave traces of "customizations" in /system, which makes it somewhat incompatible with stock kernel or stock compatible kernels like lean.

[MENTION=4375463]old_fart[/MENTION], you need to go back to everything stock (including /system - ROM), and slowly add your data/mods back one at a time to see what causes your issue. Ping me via PM?
[Nexus 6  Original Android Development] magnum870:
When you say "only if you like to set custom min/max frequencies" does that include your oc/uc frequencies? Or are those two steps automatically included in the stepping once we flash the oc/uc kernel?
[Nexus 6  Original Android Development] Imoseyon:
Unless you have flashed custom mpdecision (or disabled mpdecision completely) & disabled cpu-boost, if you set your min frequency above the kernel minimum, and/or set your max frequency below the kernel maximum, those settings will not stick. This is also in the FAQ but in different words.

I hope that answers your question. I'm not entirely sure if I'm clear. ;)
[Nexus 6  Original Android Development] magnum870:
Yeah I understand that, I just wanted to make sure that mpdecision could recognize the 233mhz and 2.9ghz slots without any modification by the user. I'm pretty sure it does, I just wanted to make sure the OC/UC kernel wasn't locked to stock clocks if we didn't modify mpdecision and such.
[Nexus 6  Original Android Development] Imoseyon:
That's correct. Mpdecision by default recognizes kernel maximums and minimums (cpuinfo_max_freq and cpuinfo_min_freq which are more or less immutable).
[Nexus 6  Original Android Development] magnum870:
Perfect, thanks for taking the time to clarify for me
[Nexus 6  Original Android Development] laureanop:
Imo :Is the line that sets minimum cores online to 2 in my default.prop overriding mpdecision and possibly deleting on boot??? Or is this how stock looks like?? ( I'm running custom ROM)
[Nexus 6  Original Android Development] stuff:
In another question, my PVS bin is 7.

I am running, and have been since 7am (its now 1pm) on voltages from the table at pvs 11. So far not a single issue.

I might try some other ones, but should it be stable that UV'd?
[Nexus 6  Original Android Development] Imoseyon:
2 is the stock value as well. Most likely either something in your ROM or an app that you installed is deleting mpdecision binary at boot.

Everyone's different. If you don't notice any weird behavior then it's stable. Personally I only UV the lowest frequency.
[Nexus 6  Original Android Development] laureanop:
Then what mp decision is being used if the binaries are deleted or no present ?
[Nexus 6  Original Android Development] 5FOOTER:
I know its not kernel related but does anyone else have WiFi drain when WiFi is off? And yes my settings are correct but I'm having to reboot 1 to 3 times a day to get WiFi to stop showing up in battery stats. It does it on stock rooted also just asking here cuz you guys seem helpful.
[Nexus 6  Original Android Development] drivel2787:
This kernel is great. I'm on version 1.0. I used app ops, greenify, and disable service, I believe I have found a GREAT combo. I'm on 26 hours since my last charge with about 2 1/2 hours on screen time. My battery shows I still have 1 day and 8 hours left. I was able to disable a few Google play services items that were causing battery drain, which didn't effect my performance or usage of any applications/services.
[Nexus 6  Original Android Development] gambit07:
Which play services did you disable?
[Nexus 6  Original Android Development] drivel2787:
Hopefully nothing bad :)

But AnalyticsService, BrokeredFitnessService, DeviceConnectionServiceBroker, GcmService, GoogleLocationManagerService, GoogleLocationService, NlpLocationReceiverService, SyncService, WearableControlService, and WearableService.

I haven't had any issues since disabling them. Google still responds to "Ok Google" I still get my email. I haven't noticed anything specific that it has created any issues with. Has made a huge difference in how quickly I see my battery drain though. I use to lose a good bit overnight while the phone was idle. I lost barely anything over the night maybe 1-2% I think compared to 10% or more before.
[Nexus 6  Original Android Development] Imoseyon:
If the binary does not exist, mpdecision is effectively disabled.
[Nexus 6  Original Android Development] knitler:
With ONLY this kernel and -50mV I was able to do 3.5hrs SOT, 24hrs of Google Music with 3 days over all battery use. That was on WiFi with HORRIBLE cell coverage.
[Nexus 6  Original Android Development] bradputt:
[MENTION=3357040]Imoseyon[/MENTION]

Is it possible to enable usb fast charge on your kernel please?

I miss the days where I could charge my phone on the PC port.

It did charge now but it's damn slow.

Thanks
[Nexus 6  Original Android Development] akellar:
He's already answered this
[Nexus 6  Original Android Development] Imoseyon:
I will actually add this to my todo list.
[Nexus 6  Original Android Development] rignfool:
There is a WiFi state machine error in logcat on every ROM/kernel combo I've tried...

Dunno if that is related
[Nexus 6  Original Android Development] bradputt:
Thanks Imoseyon! You're the best!
[Nexus 6  Original Android Development] blakmazk:
Does lean kernel has dt2w on by default?

If yes, is there a way to disable it?

Thanks...
[Nexus 6  Original Android Development] zephiK:
That's on the rom side not kernel. Most custom roms have this enabled by default.
[Nexus 6  Original Android Development] Rxpert:
Its kernel related as well
[Nexus 6  Original Android Development] zephiK:
Not really, it can be activated via ROM as its already embedded in Google's code.

If you're talking about sweep2wake/sweep2sleep, thats not in this kernel and has no plans being in LeanKernel.

For prior phones, yes dt2w is kernel related but specific to the N6, its already embedded in Google's code and is just disabled purposely by Google. No extra code is needed, just a toggle in a file.
[Nexus 6  Original Android Development] wrongway213:
Anyone have any tips for undervolting/specific governor settings that are helpful for a moderate heavy user (I use the phone often but almost always calls, texts, emails, music, maps and browsing Chrome) and a lot of the time I have my phone left untouched for hours at a time, wherein ideally my phone stays in deep sleep and my battery life evens out. Last time I flashed this kernel stock the kernel wakelock ended up keeping my phone out of deep sleep more than it stays stock and so I actually lost a bit of battery life, didn't really notice any device improvements or issues otherwise. On Rastapop, for what it's worth. Everyone keeps saying this kernel is where it's at for good battery life and SOT on the Nexus 6 but I dunno my way around Trickster Mod at all.. Searching has basically taught me what I could do if there was a KT kernel.. no specific numbers for LK or many other kernels anyway. If anyone has any advice for me I'd appreciate it.
[Nexus 6  Original Android Development] warrenis1234:
when i did this, the gps stopped connecting in google maps. doesn't happen to you?
[Nexus 6  Original Android Development] drivel2787:
I have google maps froze since I don't use it all the time. I would say re-enable the location based services (ones that have location in the name) and that will more than likely fix it.
[Nexus 6  Original Android Development] frenchy714:
What a blast from the past! Sup bud? (Sorry OP for the OT).

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] Imoseyon:
There appears to be a problem with charging on PC/USB, after being on a different charger type. For instance, I was charging the phone via wireless over night, and when moved to PC/USB, the charging driver kinda craps out and input current is severely reduced.

I also see an issue with the wifi driver.

Note that both issues should also exist on stock (ie. it's not a bug in leankernel)

I will work on both but probably after my vacation which is starting tonight. ;) I will try to release v1.2 tonight before heading out of town, and try to fix the above two issues for v1.3.
[Nexus 6  Original Android Development] drivel2787:
As you can see huge freaking difference. 48 hours since my last charge and over 4 hours on screen time.
[Nexus 6  Original Android Development] arcanexvi:
I'm not sure if it's even your kernel that causes this. Sometimes on the factory kernel I'll plug into my turbo charger and I'll get the charging icon yet the battery will still trickle deplete. It's very strange. If I go to the battery screen I still get the "charging via AC" but it is in fact not charging.
[Nexus 6  Original Android Development] Imoseyon:
Yup like i said, those issues should exist on stock as well. (maybe i should clarify even more :)). I think it's the same issue. I will get to the bottom of this! If i can't fix it, then i'm sure future google updates will. ;)
[Nexus 6  Original Android Development] noneabove:
Anything interesting you can tell us about 1.2 ? :)
[Nexus 6  Original Android Development] Pilz:
I think its a lollipop issue. My G3 does the same thing running LS (lolipop) and my Nexus has once. I just reboot it and it will charge. One time my G3 refused to charge so I let it die and plugged it in then it worked. I still don't know what caused the issue or if it's related but its not s big deal. Last night my Nexus was on my qi charger and charging when I went I bed. I woke up ant it was still at 27%. I plugged it into my turbo charger and 30 minutes later I was at 70% so that's too enough for me. Its odd because I use that qi charger every night without issue and it was charging fine when I tested it later.
[Nexus 6  Original Android Development] Imoseyon:
v1.2 is up: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

This version, along with other changes, boosts pc/usb charging current by 300-400mA. This is somewhat of an experimental change so if charging is totally broken for you, go back to v1.1 and wait until I come back from vacation end of next week. :)
[Nexus 6  Original Android Development] zephiK:
Have a nice vacation and happy holidays.
[Nexus 6  Original Android Development] RoscoeDpG:
enjoy ! and be safe !
[Nexus 6  Original Android Development] arcanexvi:
Enjoy the time away. ?
[Nexus 6  Original Android Development] tdamocles:
Nice kernel. Overclock is rock solid with no voltage change at 2880mhz and no crashing or rebooting in antutu.. I was having problems with the 'other' OC kernel with anything over stock with antutu crashing and rebooting. I'm definitely staying with this kernel. My cpu is binned pvs 9 and I thought I should have no problem overclocking and started to think that I had a lower spec'd cpu but your kernel proved otherwise.
[Nexus 6  Original Android Development] drivel2787:
Anyone else lose 4g and everything crashes on boot with 1.2? I had to flash back to 1.1
[Nexus 6  Original Android Development] modmouse78:
I just flashed 1.2 and lost data
[Nexus 6  Original Android Development] 5FOOTER:
If you lost data switch to airplane mode and back it should show up.
[Nexus 6  Original Android Development] Prod1702:
Got my 64gb yesterday great phone so far great kernel. after checking pvs it is a 4 kinda low? what is everyone else getting is a 4 Avg?
[Nexus 6  Original Android Development] tflogic:
unless your PVS lands at a 0, you shouldn't really need to worry about it. just enjoy your new toy :)
[Nexus 6  Original Android Development] oak:
I have a pvs 2 and am perfectly satisfied with the device. Runs great on LK. Great performance and 6-7 hours SOT. No problems whatsoever with 1.2.
[Nexus 6  Original Android Development] drivel2787:
Wasn't the only issue. Upon boot also got alerts of tons of processes crashing
[Nexus 6  Original Android Development] zephiK:
I'm using Euphoria with 1.2 and having no problems with data.
[Nexus 6  Original Android Development] Nalix:
I'm new to this community and I'm still trying to grasp some stuff. Regarding the always-on encryption on Nexus 6. It can be removed by flashing boot.img separately. If I flash leanKernel - it will include a new boot.img aswell, thus making the "fixed" boot.img obsolete? I also read that the Euphoria ROM is also disabling encryption, I assume that it also modifies boot.img.

Is it an correct assumption that I can remove encryption by either a) flash a custom boot.img without encryption OR b) flash leanKernel OR c) flash Euphoria (or other custom ROMs that disables encryption)?

Wouldn't this indicate that leanKernel and Euphoria conflicts with each other?

Any tips for a newbie like myself is appreciated :) (And yes - I have read the stickies over and over again :))
[Nexus 6  Original Android Development] dsmitty166:
I don't have time for a detailed reply. Hopefully someone else can.

1 you need to fastboot format userdata after flashing a non force encrypt kernel. Be warned this will delete EVERYTHING on your phone.

2 then you can flash what u want

3 they do not conflict. In fact Euphoria now uses leankernel as the shipping kernel
[Nexus 6  Original Android Development] cr4ck3r4lif3:
You're encrypted by default. You'd need to flash the modified boot.img or a custom kernel that supports decryption, then you have to factory data reset. Read up on this because you'll wipe your phone clean of all of your data.

Check out this thread: http://xdaforums.com/showthread.php?t=2946715
[Nexus 6  Original Android Development] rignfool:
OK... Here's how it works...

The stock kernel (boot.img) has forced encryption...

Most of the custom kernels you find here... Do not force encryption...

Now... If you are coming from stock... Your user data will be encrypted... You can flash one of the custom kernels and you will still be encrypted... But not forced to be...

If you want to not be encrypted... You need to flash one of the kernels without forced encryption... Then either FORMAT in fastboot or FORMAT in TWRP... Wiping data is not sufficient on this phone because it leaves /data/media intact...
[Nexus 6  Original Android Development] drivel2787:
What's the benefit of running unencrypted
[Nexus 6  Original Android Development] rignfool:
Better read/write speeds