yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Xileforce:
I run my phone at stock 2.7ghz max and leave GPU at 700mhz. You can under clock GPU if you have issues. Stock is 600. 2.88 and above can become unstable on my device :( I'm only a bin 5. Also double check that your phone is dropping down to 35mhz. Sometimes it shows its set to 35 MHz in kernel apps but it is really set to 1497. Seems to be a bug with msm limiter ATM.
[Nexus 6 Android Development] BrianTX:
I am running 1.9.1 with latest chroma and have had zero issues. This kernel and lean kernel are the only two that don't give me random reboots. Really appreciate your work!
[Nexus 6 Android Development] SunShine.CID:
I've installed this build and it boots successfully! Super Thanks! If I notice any issues I'll let you know.
[Nexus 6 Android Development] Xileforce:
Thanks man! Glad to hear its working for you. It seems like the latest test build resolved the majority of the boot loop issues for most people.
[Nexus 6 Android Development] Xileforce:
Sweet! Just be careful that builds got 3.03ghz OC option! Who knows what kind of terrible things could happen if u accidentally turn that on O_o. Also that's also got msm limiter which means your min frequency may or may not be stuck at 1497 until you re set it back to 35. Even if it shows 35 as the min. I'm working on it :P
[Nexus 6 Android Development] SunShine.CID:
Wait wait... Spoke just a little too soon. Shortly after boot screen goes black, reboots to app optimization. Force stopping Synapse seems to resolve the issues though.. But my phone is getting MUCH warmer than I'm used to TWRP reports 43C. Going back to 1.7 for now.
[Nexus 6 Android Development] jlokos:
No issues on benzo with the test build. My GPU is set to 600 and yes my phone is dropping to 35 mhz.
[Nexus 6 Android Development] Xileforce:
43c is very cool. I'll try removing the 3.03ghz OC to see if that's part of the issue.
[Nexus 6 Android Development] Xileforce:
could you give this build a shot if you dont mind? https://drive.google.com/file/d/0B6n0VW96A9MoX3BTbUhmTVN2eVE/view?usp=sharing only change is no more super high oc which may have somehow been getting used and causing instability.
[Nexus 6 Android Development] poipen:
Got 2 reboot and two black screen but Now it's works. Don't know if I can take the chance to use it now. It's sleeping time soon.

Tapatalk Nexus 6

---------- Post added at 12:33 AM ---------- Previous post was at 12:32 AM ----------

Download it now. Report back soon.

Tapatalk Nexus 6

---------- Post added at 12:42 AM ---------- Previous post was at 12:33 AM ----------

Boots good. But I didn't see any app optimization?

I keep it and report back tomorrow how it's run.

Tapatalk Nexus 6
[Nexus 6 Android Development] Xileforce:
Sweet thanks for trying it out. You shouldn't see any app optimizations if things go normally ;)
[Nexus 6 Android Development] LunaticSerenade:
Gave the test kernel a shot. I got a little aggressive on the UV, and got a reboot, but good since I bumped it up a hair.
[Nexus 6 Android Development] Xileforce:
gotta watch that UV :P I can do 25mv completely fine. sometimes even like 30 but ive had reboots in the past on 30 when playing 3d games so I stick to 25
[Nexus 6 Android Development] donnellyian:
Multi-rom

Ok so I flashed multi-rom while on franco kernal accidentally, can I still just flash this kernal or will it bug up multi-rom?
[Nexus 6 Android Development] Xileforce:
Yup. We've had multi ROM for almost a month
[Nexus 6 Android Development] donnellyian:
Sweet. Will I need to reinstall multi-rom after I flash the kernal or no?
[Nexus 6 Android Development] 9wire:
All this UV and oc stuff, I looked, and apparently I don't have a bin #? Did the terminal command and it came up with "# (blank)" on synapse where it's supposed to show it's blank as well.
[Nexus 6 Android Development] Xileforce:
That I do not know. I don't think so
[Nexus 6 Android Development] SunShine.CID:
Boots, Synapse Runs, Games Run, 30 Minutes in, this one's looking good! I'll let you know if something starts flaking out. Looking forward to future releases!
[Nexus 6 Android Development] Xileforce:
Wooo. Hope your not getting my hopes up only to crush them :(
[Nexus 6 Android Development] Xileforce:
Could you post a screenshot of the terminal output? And the synapse bin display does not work ATM. Maybe I'll see if I can fix that myself.
[Nexus 6 Android Development] 9wire:
Ttapatalk won't let me post pics, terminal just has a #, and no number.
[Nexus 6 Android Development] Xileforce:
Typically the number shows up at the very beginning of the next line. In front of the normal text. Like the very first digit. Kinda hard to explain.
[Nexus 6 Android Development] 9wire:
OK, looks like a 7 then, thanks.
[Nexus 6 Android Development] Xileforce:
Lucky u! I'm a bin 5 :( you can undervolt quite a bit more than a lowly peasant such as myself.
[Nexus 6 Android Development] Mistertac:
How about that guy with the Bin 1 though.... Damn.
[Nexus 6 Android Development] jackpollard:
Elite bin 8 here, sorry for those less fortunate. I generally undervolt so much I use my phone as an ice pack its so cold. It may take 5 minutes to bring up my screen, but damn I have sot's I measure in days. :D
[Nexus 6 Android Development] poipen:
Test10 build works good so far. No problem at all.

Tapatalk Nexus 6
[Nexus 6 Android Development] joshm.1219:
Im bin 1 too :(
[Nexus 6 Android Development] oOflyeyesOo:
I am bin 8 also, NICE! I am ready for the new build. I will have time to run a test build tomorrow unless another build drops.
[Nexus 6 Android Development] bgenesis12:
nice kernel

I can't account for longer battery life although I can say that since I've been trying this kernel magic 2015 runs a lot smoother. Still minor lags but way better now.
[Nexus 6 Android Development] donnellyian:
Bin 2

Im not doin much better than you all im bin 2 :(
[Nexus 6 Android Development] Xileforce:
Lol. Its okay guys. No need to be upset :(
[Nexus 6 Android Development] Xileforce:
Hoping to have another build out today :)
[Nexus 6 Android Development] angiest:
And bin 9 here.
[Nexus 6 Android Development] Grubbdog:
This may be a noob question (although I am a noob so...) But what is the difference between the mako hotplu and the intelliplug? Like is it how the cores are controlled or is it more of a governor type control?
[Nexus 6 Android Development] Xileforce:
basically, the hotplug driver (mako, intelliplug,mpdecision) controls when your cpu cores get turned on. For instance, Intelliplug will use 1 core when it needs to, but if your phone needs more performance it will add a second core. If it needs even more it will keep adding cores until it has sufficient power. Mako hotplug does the same thing just in a different way. Its really down to personal preference though im likely going to replace intelliplug with blu plug in the next build because intelliplug has been giving me some issues and Its just not actively developed by faux atm :(
[Nexus 6 Android Development] eltnav:
thanks

Just found this Kernel today, mostly reading the entire thread which has been very informative. Thanks again!
[Nexus 6 Android Development] jackpollard:
Dang and I felt like a king for a day with my lousy bin 8. Oh well, back to the mines for me. :crying:
[Nexus 6 Android Development] LunaticSerenade:
I had an 8, but the battery swelled. Pretty happy with my 7 that isn't swelling.
[Nexus 6 Android Development] wrongway213:
Me and my bin 5 don't wanna hear a single complaint out of you, lol
[Nexus 6 Android Development] x0nar:
Hey there. I did what you said and here's what it returns. Am I doing something wrong ?
[Nexus 6 Android Development] Swamphound:
You need a space between "cat" and "/". I did the same thing.
[Nexus 6 Android Development] x0nar:
Okay. Thanks. Apparently It's Bin 5.
[Nexus 6 Android Development] Xileforce:
Sadly you cannot increase your binning # :( but 8 is actually really good! You can probably do an across the board -48mVolt undervolt! Basically the binning is how they rate the quality of each chip. Its to prevent waste. Essentially it means that your processor leaks more voltage than a higher rated binning if my understanding is correct. Thus it takes your CPU more voltage to run each frequency, your CPU won't be any slower or faster based on a binng though. Im a bin 5 and usually run -36mv undervolted across the board. Unless I am over clocked in which case I leave the 2.88 GHz frequency at the stock voltage. Also FYI. 98mhz can really be undervolted. I usually undervolt it to 500mVolts which is as low as the phone can go. The reasoning is that in every batch of CPUs they make they always have various defective wafers, and or completely broken ones. Instead of simply dumping them they use binning to essentially account for the deficiencies. In computer chips this explains why they have different models of chips. For instance an amd 6000 series chip is just a poorly binned 8000 series chip, most likely with two malfunctioning cores so they simply sell it as a 6 core processor instead of an 8. Hope this helps clear up binning a bit. I'm not an expert.
[Nexus 6 Android Development] Swamphound:
Ty [MENTION=4517211]Xileforce[/MENTION] I just learned some things! UVing right now. I also just ran lkconfig and ck'd my wakelocks and my top one was that smb135x one so I disabled it.
[Nexus 6 Android Development] Xileforce:
Awesome! And for sure run 98 at 500mv. As a bin 8 ur fine. I'm so jealous :( if u do get any weird reboots tho try raising it. You would be surprised how frequently the phone uses 98mhz. In fact for most people its probably the most used frequency. So getting that voltage as low as possible really helps idle and just overall battery life.
[Nexus 6 Android Development] OverSu:
Nice to see a lot of help like this ! :D

After some test, this is what I've done to make Chroma and Vindicator works together.

As [MENTION=611473]clnzx2[/MENTION] said, you need to start the Chroma with the original kernel first. And when you restart the second time in order to flash the Vindicator, you will have a lot of "PlayService Crashes". I guess this is normal. I had just to update every services using the Play Store. And after some reboot, updates and tears, they are working together like a charm !

Chroma configured, Vindicator configured, just wait until tomorrow to share you my battery cycle. :laugh:
[Nexus 6 Android Development] Swamphound:
And we're off! Ty for the help. Ive said this before on other threads but the Nexus 6 community is really great and Xileforce you are another good addition.
[Nexus 6 Android Development] Xileforce:
Hope that works well for you!! And thanks!
[Nexus 6 Android Development] duminduweera:
I'm on the latest CM nightly, and the settings app crashes if I enter any of the settings. This only happens if I'm using this kernel, so I think it might be kernel related rather than the ROM.
[Nexus 6 Android Development] Xileforce:
This happens to me sometimes. Usually its related to themes. Try changing you theme to stock and then back to your existing theme. Usually itnahppens to me after the theme gets updated. Lemme know if that works
[Nexus 6 Android Development] DespairFactor:
Running 98MHz is useless unless you can't run 223MHz at 500mv. You will not be saving any power with a step that is slower with the same voltage requirements.
[Nexus 6 Android Development] duminduweera:
Yeap, that did the trick. Thanx ;)
[Nexus 6 Android Development] philosophics:
I'm just interested to know why Deep Sleep isn't used...

Sent by a Whale
[Nexus 6 Android Development] Xileforce:
Something's up because mines sleeping fine. Have u checked your wakelocks? Also Could you please give a little info on your configuration. May help track down the problem. Only other potential cause could be you have had the screen on entire time or doing something like playing music. As a test try stopping any background tasks (music etc) and then locking phone (screen off) for like 10-30 seconds. It should then enter deep sleep. Mine entered sleep after about 1-2 seconds of screen off when I just tested.
[Nexus 6 Android Development] philosophics:
Ah ha!

I used the settings provided in the faq and shazam!

LiquidSmooth 020415 cm

Mako Hotplug

InteractiveX min 98 max 2.88

Fiops 1536

F2fs cache

Bin 7

Undervolted to the settings pictured above a few posts back also seems to help.

Also, what's a good gpu governor to use? There are a few options but I haven't seen anything that describes them...

No random reboots since as well

Sent by a Whale
[Nexus 6 Android Development] Xileforce:
Not true for many reasons. First of all its not that simple, Along with a reduced main clock speed, the cache frequency is more than halved, and the mandatory memory bandwidth value is lowered as well. Both of those will save power. The bus is also going to use less voltage. The most important fact, however, is that voltage is simply not the only thing that relates to power draw. Power consumption is linear to the clock speed and increases to the square of voltage. This is because as the clock speed increases it must also draw more current. This means that just based on the frequency alone and not counting the reduced cache,bandwidth and bus 98mhz, which is about 56% less than 223mhz, will use 56% less power draw from the frequency portion of the equation. Thus your statement that it will not save any power at the same voltage is completely erroneous. The amount of power saved, may be smaller than that saved by reducing the voltage, but it is power saved nonetheless and I doubt anyone would willingly use more power. I will more than likely remove 223mhz next update.
[Nexus 6 Android Development] DespairFactor:
Whatever you say
[Nexus 6 Android Development] Xileforce:
By guy governor I'm assuming you mean CPU? If so InteractiveX is what I run and recommend. Its the most updated and it supports Franco's CPU boost. Intellicactive is another solid choice. Its a governor by faux that's been around for awhile and is pretty popular. If you prefer better battery life you may want to try conservative.
[Nexus 6 Android Development] philosophics:
Stupid auto correct!

Sorry, I meant GPU governor.

Sent by a Whale
[Nexus 6 Android Development] Xileforce:
This! BTW wrongway. Ik u r familiar with hydra kernel. Do u prefer msm hotplug or bricked?
[Nexus 6 Android Development] wrongway213:
MSM MSM MSM MSM MSM you see where this is going lol
[Nexus 6 Android Development] Xileforce:
I think I c what ur getting at here O_o
[Nexus 6 Android Development] Deathrowy2k:
Lowly 13 bin here.
[Nexus 6 Android Development] jackpollard:
The bin contest has a winner! Check or Money Order for the prize?

All kidding aside, have you tried uv'ing? I would wonder how low you can go without locking up your phone.
[Nexus 6 Android Development] Deathrowy2k:
I only go about 50 or 60mv under I could and should probably go lower but I think I am happy with it ATM.
[Nexus 6 Android Development] Xileforce:
Only 50 or 60...... I go 25........5 mv past that I'm being adventurous....
[Nexus 6 Android Development] Deathrowy2k:
Lol
[Nexus 6 Android Development] donnellyian:
UV

Guys, I'm bin 2 and I am stable at 90~110 mv undervolt, depending on the frequency.
[Nexus 6 Android Development] Xileforce:
What!....wait...what! How u do dis?
[Nexus 6 Android Development] donnellyian:
Well, I'm not a heavy user, and I haven't benchmarked at all, so it may lock up if I tried to use it heavily, but why try?? XD With how I use my phone (music, social media, calling, texting) I dont really overpower the cpu. I also have load threshold in mako set to 100, forcing it to 2 cores, so that could have something to do with it.
[Nexus 6 Android Development] LunaticSerenade:
For real. At bin 7, I can only really do -30 across all frequencies and stay stable.

I test by running AnTuTu, and if that works, then I take a couple pictures.
[Nexus 6 Android Development] Xileforce:
Yea. If it runs antutu ik its solid. Otherwise I'll get random crashes.
[Nexus 6 Android Development] donnellyian:
Voltage Comparisons

If anyone wants to know, here are a list of the stock CPU voltages of a bin5 user, and the voltages I run stable as a bin2.

Stock voltages of a Bin5 user, according to lean kernal's voltage table (my bin2 stock were even higher) :

(mhz) (volt)

300 760

345 770

422 780

499 790

576 800

652 810

729 820

806 830

883 840

960 840

1036 850

1113 860

1190 870

1267 880

1344 890

1420 900

1497 910

1574 920

1651 930

1728 940

1804 950

1881 960

1958 970

2035 980

2112 995

2188 1010

2265 1025

2342 1040

2419 1055

2496 1070

2572 1085

2649 1100

And my voltages are:

35 500

98 500

300 620

345 630

422 640

499 650

576 660

652 670

729 680

806 690

883 700

960 725

1036 735

1113 745

1190 755

1267 765

1344 775

1420 785

1497 795

1574 805

1651 815

1728 825

1804 835

1881 845

1958 855

2035 865

2112 880

2188 895

2265 915

2342 925

2419 940

2496 955

2572 975

2649 1010

Sorry for the long post, figured it would make it easy to read.

Edit: Ran fine in my normal use for 3 days, however crashes in antutu.
[Nexus 6 Android Development] Deathrowy2k:
I actually have a txt file with the stock voltages for all the bins if anyone is interested in it.
[Nexus 6 Android Development] Deathrowy2k:
I posted that because you may be surprised that the terminal bin number is wrong for a lot of people. I have seen people discuss this before on other sites like this one http://www.reddit.com/r/nexus6/comments/2ofpm8/nexus_6_cpu_binning/ and others.
[Nexus 6 Android Development] Xileforce:
No the terminal is the correct one. The one in clock_krait_8974 is incorrect. That is the voltage table that you use which imoseyons voltage control lists in that file. Imoseyon himself said the one I have listed in my 3rd post is the correct binning. Hope that makes sense. So my understanding is that he gives certain bins a certain table by default. So basically bin 5 or whatever uses the voltage table for bin 13. Idk really why its like that. I just had that question too and remember IMO saying the first way was correct.
[Nexus 6 Android Development] Deathrowy2k:
OK so then I have a lot of confused people giving me bad info, I really hate that. Thanks Xileforce.
[Nexus 6 Android Development] Xileforce:
Don't worry I'm confused too. Like I said, I just remember someone asking imoseyon and that's what he said and imoseyons pretty smart :P
[Nexus 6 Android Development] Deathrowy2k:
So is the txt file that I uploaded for the bin numbers correct.

---------- Post added at 12:09 AM ---------- Previous post was at 12:05 AM ----------

Never mind I got it.
[Nexus 6 Android Development] Grubbdog:
Yeah under volting 80~ish on bin 7 is totally stable even benchmarked I posted my set up a couple pages back and it's totally stable on bin 7 benchmarked and real world use and its close to 80 90 MV undervolted
[Nexus 6 Android Development] LunaticSerenade:
Interesting. Once I get to about -60, I get reboots.

Granted, I run OC, so that almost certainly has something to with it.
[Nexus 6 Android Development] Grubbdog:
-60 on what frequencies? I don't undervolt anything over 2649, I have 2880 at 1135 haha but 2649 is at 1021 (1016 seemed a little unstable pulling up the camera from the lock screen from time to time and switching apps fast) 2572 is at 981 MV though :) the lower frequencies are more easily undervolted than 2572 and 2649, those were the ones I had to tweak the most.
[Nexus 6 Android Development] Xileforce:
Yea don't undervolt 2.9. 2.7 u can undervolt a bit tho.
[Nexus 6 Android Development] Grubbdog:
[MENTION=1375627]LunaticSerenade[/MENTION] I'd be curious to see if you could run the voltages I run considering you're a fellow bin 7.... If you want to try I posted my voltages on page 88 and upped 2649 to 1021 like I said for further stability. If you want you can try it out and see if it works for you too :)
[Nexus 6 Android Development] LunaticSerenade:
I'll give it a shot tomorrow.

I figured undervolting the OC frequencies were my issue.

As usual, I am the cause of my own problems. :)

[MENTION=4517211]Xileforce[/MENTION], I'm running the 2.0test9 right, and I have to say, this thing barely sips battery. I UV'd the whole thing by -25, and it's super stable. :)

[edit] [MENTION=5944353]Grubbdog[/MENTION] by tomorrow I guess I meant right now. Just ran AnTuTu, no issue (and the highest score I've gotten) with the following:

35	500

98	500

300	625

345	635

422	645

499	655

576	665

652	675

729	685

806	695

883	705

960	731

1036	741

1113	751

1190	761

1267	771

1344	781

1420	791

1497	801

1574	811

1651	821

1728	831

1804	841

1881	851

1958	861

2035	871

2112	886

2188	901

2265	921

2342	931

2419	946

2496	961

2572	981

2649	1016

2880	1135

3033	1155
[Nexus 6 Android Development] :
Could any of you guys please share the Recommended settings for battery and performance.

Thanks in advance
[Nexus 6 Android Development] Xileforce:
Hehe I'm already on test16
[Nexus 6 Android Development] Xileforce:
For battery I recommend switching your governor to conservative and raising the load threshold for mako hotplug to around 80. You can try intelliplug too but Its been having issues lately and is being replaced in 2.0 by msm hotplug. You may also want to reduce your GPU frequency max to 600.
[Nexus 6 Android Development] :
Thank you so much for your help, appreciate it :)
[Nexus 6 Android Development] Xileforce:
NP. Next build will have a bit more tweaking for battery life too.
[Nexus 6 Android Development] :
Looking forward to it, i'm using the Benzo Rom and your v2.0 is implemented by default there so i'm very pleased with the results so far, nice work

and good luck
[Nexus 6 Android Development] jackpollard:
You will find even on stock settings this kernel literally sips power. I would say I'm a moderate user. Web, various informational apps (zite, twitter, etc.), music (using high def in V4A) for probably an hour or 2, messaging, calls, etc. I turned on my phone at 5:30 am yesterday and when I turned it off at 11:30 pm, I still had 52% left. For me, thats as good as it gets.

I changed very few settings; I uv'ed -25, use mako at 80% so 2 cores are usually offline, tcp congestion is westwood, vibe = 52%. Thats about it. I also use Benzo rom. No adaptive brightness, but ambi display is on. I manually sync gmail and make sure I have no google wake locks.

If the rom/kernel combo was what google offered as "stock", I'm thinking we would still be waiting for it to come off of backorder.
[Nexus 6 Android Development] :
Indeed, thank you for your help my friend.
[Nexus 6 Android Development] Grubbdog:
[MENTION=1375627]LunaticSerenade[/MENTION] sweet man! Is that the lowest undervolt you've tried so far? :)
[Nexus 6 Android Development] gamewarden234:
I use four cores like Franco kernel with conservative and on demand gpu and am getting the best battery life ever on this phone. I noticed when I bring the minimum cpu up to 300 my phone scales up and down alot less. At the minimum it always is going up and down and at 300 is just stays there. I think it improved my battery life how I use my phone. My bin is 14. Got lucky.
[Nexus 6 Android Development] Grubbdog:
And [MENTION=4517211]Xileforce[/MENTION] I'd be curious to see if you could run the same amount of undervolt just from your stock voltages and not from my bin 7 voltages. If you want I already did the math and your 2649 voltage would be 1041 for a -59mv undervolt and 2572 [MENTION=333787]1001[/MENTION] for a -84mv undervolt. Try the 2649 first and just see if its stable and if so throw the 2572 in there and see what happens :)
[Nexus 6 Android Development] LunaticSerenade:
Pretty much. It's scary how stable this is.
[Nexus 6 Android Development] Grubbdog:
I know right... Welcome to better battery life :P
[Nexus 6 Android Development] Xileforce:
Wow that's amazing battery! The next update will also have a toggle for FB Notifiers which are disabled by default in synapse. This will give better battery life for those using ambient display.