yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Xileforce:
That's a good point lol. I do try to make it so that "out of the box" its already on pretty solid optimal settings to aid ease of use a bit. I really only drop my voltages, change my TCP algorithm, and enable zram. Everything else I leave standard.
[Nexus 6 Android Development] wrongway213:
Don't get me wrong, defaults are nice on this kernel, but four MAJORLY different hotplugs to choose from = basically four different kernels imo. I call the profiles Vindicated lean (no hotplug), Vindicated Faux, Vindicated stock (why anyone would, I dunno) and what I personally use, Vindicated Franco. This is basically four kernels in one plus optimizations and patches from others and your own personal stuff - if you apply a single tweak you often wanna apply the others that compliment it, lol.
[Nexus 6 Android Development] Xileforce:
Haha for sure. That was actually one of the goals I was shooting for. I liked Franco's kernel, but I also liked how lean was very upstream and had some nice features plus was very stripped down. That's why I basically decided to take lean as a base, since its already very up to date with upstream and slimmed down. Then I pretty much entirely merged Franco into it. I run it in quad core mode ATM. I heard that's Franco's new default. Not sure.
[Nexus 6 Android Development] wrongway213:
Well you have succeeded then, haha. And yeah that's Franco's/Google's new default lol
[Nexus 6 Android Development] harvickgm:
I have been having some issues, I'm on sprint, and so far I have had Sinless 3.0.0 and now I'm on MeanPop 2.08, but I have issues during the initial boot. Even after I do a completely clean install all over again, it puts the phone into a boot loop and it starts to get hot, I put it in the fridge to cool it and after about 6 boot loops with optimizing apps every time it finally went thru. But every now and then it will just completely freeze the phone and I have to do a hard reset. It would even freeze on the lock screen after a reboot.

I am not running any OC or UV, so that shouldn't be the problem. Any ideas what's going on. I love the kernel but the freezing and reboots are getting annoying
[Nexus 6 Android Development] f100cleveland:
One thing you can try is when it loops, boot into recovery and reflash the kernel and then clear cache and dalvik and try again.

Does it only do it on this kernel or did you flash a diff kernel first?
[Nexus 6 Android Development] harvickgm:
I've tried that, even tried it just after a fresh ROM install. I have not noticed it on Franco's kernel, but I like this one better. I know with Franco's kernel you have to flash a new boot.IMG, do I need to do this here at all?
[Nexus 6 Android Development] Xileforce:
Try this. Clean flash ROM. Do not flash kernel. Boot into ROM. Reboot to recovery and flash kernel then reboot again. I've heard this fixes issues people have on some roms

.
[Nexus 6 Android Development] idiotzach15:
Well, whatever I do, I cannot seem to get V4A to work with this kernel. Otherwise, I love this thing. I'm running Chroma, and I've tried the aforementioned methods using extreme beats. Nothing seems to work... I miss the HiFi
[Nexus 6 Android Development] poipen:
This way is working. Had problem last week but when I tried this way it's work. Have a great battery on this kernel.
[Nexus 6 Android Development] Xileforce:
Interesting. Does v4a completely not work?
[Nexus 6 Android Development] Mistertac:
I've not had an issue with Viper for some time now ( other than the aux Jack issue we were just talking about ) and I use this Zip :

https://www.dropbox.com/s/g0nc6kv1jxxt1is/viper_v2.3.4.0 - remove fx build fix.zip?dl=0

I set my SELinux to Permissive still, install Viper driver, reboot and I'm good.
[Nexus 6 Android Development] harvickgm:
Tried that too, same thing still happens
[Nexus 6 Android Development] wrongway213:
Ended up finding out aux issue definitely wasn't fixed by Extreme Beats - came back with a vengeance. Ended up ditching Extreme Beats and just using this zip, still can't find a way past the aux issue though (other than the super slow plugin).
[Nexus 6 Android Development] idiotzach15:
Just flashing the V4A zip works, but no output from the audio jack.

Every other method yields a viper app that does nothing, or causes Play Music to crash momentarily.
[Nexus 6 Android Development] Xileforce:
Interesting. So does this issue still occur on lean or Franco? I don't use viper, so I'm just going off what people tell me. If it doesn't work on other kernels maybe its a 5.1 issue?
[Nexus 6 Android Development] idiotzach15:
It worked on franco, just using the one V4A zip. I actually just got it working on this kernel though. The problem seemed to be that the SELinux setting wasn't sticking in Synapse for some reason. After I reinstalled the driver in V4A using the SELinuxModeChanger app to set to permissive and rebooting, it worked. So that seems to have been my problem.

so in full here's what I did:

1. Installed ROM

2. Installed Kernel

3. flashed the extreme beats mod, wiped caches

4. rebooted to system

5. back to recovery

6. flashed V4A fix zip, wiped caches

7. back to system

8. set SELinux to permissive (and make sure it stayed that way)

9. install the V4A driver

10. reboot

11. Make sure SELinux us still permissive

12. eargasm
[Nexus 6 Android Development] wrongway213:
Aux connection is working normally this way? I got it to work following these steps the other day but haven't been able to since, trying to figure out what the culprit is. It works but I have to plug it in super slowly or else audio comes through the earpiece instead of external speakers via aux - before using this method I did not have to do that.
[Nexus 6 Android Development] Xileforce:
Interesting. Synapse can be a bit buggy at times. You may want to set permissive through lkconfig. That will ensure it sticks. Interested to hear if this works for others.
[Nexus 6 Android Development] Xileforce:
Quick question. Do you guys want mako default to continue to be 4 core mode or back to pre 5.1 Franco of 80 load threshold (2 cores minimum but will plug more cores if load exceeds 80) mako is the default hotplug from boot BTW.
[Nexus 6 Android Development] harvickgm:
I think Franco's is good, best of battery life and performance. This phone still flies even with 2 cores
[Nexus 6 Android Development] Xileforce:
Well that's the question :P Franco currently uses 4 cores all the time. He used to use 2 cores all the time + hotplugging. Which would u prefer? We currently use 4 cores all the time. That can be changed of course through kernel apps though.
[Nexus 6 Android Development] harvickgm:
OK, I thought Franco's was balanced. I normally change my hot plugging based on my needs at the time. If I need longer battery life I use the conservative 2. But if you come up with a good balance between 2 and 4, I would love to test it out
[Nexus 6 Android Development] Xileforce:
I think what I'm going to do is put it back to old Franco, and then make some profiles that you can choose in synapse to make it quadcore, dual core, or default. And u can still tweak it manually too.
[Nexus 6 Android Development] harvickgm:
I haven't used synapse, I use fauxclock but that pretty much does the same thing. Im new to the N6 and came from a long line of LG and HTC, so LG kernels weren't that customizable so I am still learning a lot about what this device is capable of
[Nexus 6 Android Development] Xileforce:
Give synapse a shot. It has tonnnnnss more options and supports all the features of the kernel.
[Nexus 6 Android Development] wrongway213:
I think this is a good idea. Default to hotplugging for sure - I've heard both sides of the camp and their respective takes on the new Google quad core thing, and I have to say based on my own observations since 5.1 dropped, I do not believe that running four cores saves power... or boosts performance. All I see is faster battery drain, I've yet to have issues on my N6 of it not boosting the load when need be.
[Nexus 6 Android Development] harvickgm:
I just downloaded it and removed fauxclock, but a lot of it I don't know about so I won't mess with. One thing did have me curious tho, you can change your radio setting to a preferred setting. Stock it is WCDMA preferred, but under the listing it says that's for GSM, but I'm on sprint network, shouldn't it he on a CDMA based setting?
[Nexus 6 Android Development] Xileforce:
I have no clue about all the radio settings and what not. I don't touch it. I just use the normal ROM settings for that stuff. BTW have your reboot issues been fixed? Or are you still getting random reboots?
[Nexus 6 Android Development] harvickgm:
I went back and reflashed TWRP and your 1.9.2 kernel with flashify. It boot looped once and then did the normal optimizing apps that takes awhile to finish and it booted. So far so good but it scares me when it gets so damn hot after that start up, it was up to 118* after it booted. But I will see the longer I use it
[Nexus 6 Android Development] sbollero:
I kept getting a freeze of v4a after selecting driver to install. I tried a few times and finally got through it. If you are getting freezes, keep trying.
[Nexus 6 Android Development] Grubbdog:
Hey guys, loving the kernel, awesome work man. Just wanted to post my current setup for undervolting and see if it helps anyone out. I've been messing around with it for around a week now and its completely stable for me. I'm a bin 7 and run the default 500@35mhz, then 610@98mhz, 625@300mhz and step up 10 MV all the way till 883mhz@705mv then 960mhz@731mv and step up 10mv all the way till 2035mhz@871mv, 2112mhz@886mv, 2188mhz@901mv, 2265mhz@921mv, 2342mhz@931mv, 2419mhz@946mv, 2496mhz@961mv, 2572mhz@981mv, 2649mhz@1016mv, 2880mhz@1135mv. This is what I'm currently running and is completely stable and getting amazing battery life!!
[Nexus 6 Android Development] Custodian:
Can run this on cm 12.1?
[Nexus 6 Android Development] Xileforce:
It should but that's just a guess. If you try it report back and let us know.
[Nexus 6 Android Development] Xileforce:
Wow man! Your awesome for sharing these settings! You can also run 98mhz at 500mv ;) i dont defailt that one because i havent tested it on a bin 1 yet. Maybe my lowly bin 5 can pull those off :( your first thanks is on me ;)
[Nexus 6 Android Development] harvickgm:
Where do I look to find my bin, I hear different methods yield different results
[Nexus 6 Android Development] Grubbdog:
Ooh thanks man! Just set 98mhz to 500mv ;) yeah you can try those out and if you run problems maybe try raising 5 MV at a time globally :) my main problem child was 2649mhz haha originally had it set to 980mv but had to keep upping it til 1016 which is stable for me :) 2649 and the step below are really the ones I had to tweak the most the rest might be stable for you :)

---------- Post added at 11:08 PM ---------- Previous post was at 11:05 PM ----------

I'm using synapse btw if anyone is wondering :)

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

He actually explains how on page 1 :) but I'll quote what he wrote to help: To find your CPU binning run this command in terminal emulator:

su (enter)

cat /proc/cpu/msm_acpu_pvs﻿ (enter)

(Put a space between cat and /proc)

note that the number may be displayed at the beginning of the next line.

It will then display a number from 0-15. 15 being the best.
[Nexus 6 Android Development] Xileforce:
My default for 2649 is 1100mv O_O u are nearly 100mv undervolt there.
[Nexus 6 Android Development] Grubbdog:
Haha ;) should join me at 1016 ;)
[Nexus 6 Android Development] harvickgm:
OK, well update. i updated some apps and rebooted and it went into a crazy bootloop again, it took about 10 times to come up and running. so im at a loss as to why this is happening. it doesnt matter how or when i flash it, it continues to have the same problem during boot.
[Nexus 6 Android Development] LunaticSerenade:
Got my replacement today. It's Bin 7 (old one was 8), and it is taking undervolting like a champ.
[Nexus 6 Android Development] Xileforce:
I try to be cool like u guys and get instant reboot :( I can see you guys wearing your party hats with your bin 7s all the way from my bin 5 :(
[Nexus 6 Android Development] idiotzach15:
For what reason is 15 the best? Physical heat capacity?
[Nexus 6 Android Development] wrongway213:
I know that feel, bro, bin 5 and I instantly reboot trying to OC lol
[Nexus 6 Android Development] Xileforce:
It has less leakage. Basically the processor is more efficient so it needs less voltage to run the same frequency as a lesser bin.
[Nexus 6 Android Development] Xileforce:
I've found 1160 works for 2.9ghz 1155 works too but I bump it a bit to be safe.
[Nexus 6 Android Development] donnellyian:
Hi guys, using this kernel, whenever I do any sort of video playback (twitch.tv, youtube, snapchat, vine, facebook), it locks my CPU at 300 mhz. Any idea why this would happen? it causes screen tearing and such. Thanks for the reply in advance! And should I post a log or anything?

---------- Post added at 01:46 AM ---------- Previous post was at 01:41 AM ----------

Hey, feel lucky, i'm chillin at bin 2...
[Nexus 6 Android Development] Xileforce:
D: I pity you sir. As for the 300mhz thing. Lemme take a look. Have u tried switching governors? I watch videos all the time and havent had any screen tearing.
[Nexus 6 Android Development] donnellyian:
I've tried interactivex and conservative, lemme try performance or something

---------- Post added at 02:04 AM ---------- Previous post was at 02:00 AM ----------

Locked at 300 even on performance kernel.
[Nexus 6 Android Development] Custodian:
Works on cm 12.1, smoother than it does on on chroma and Rasta...
[Nexus 6 Android Development] donnellyian:
I lied, it ran at 2.64 (max) but still lagged my phone to s**t and caused screen tearing.
[Nexus 6 Android Development] LunaticSerenade:
The party hats are for all bins!

This kernel is spectacular on a phone that doesn't have a swelling battery. :D
[Nexus 6 Android Development] Grubbdog:
Awww I'm sorry xileforce might have to play with it.. But I bet you can undervolt more than 36 for some of the mid range and lower voltages ;) took me forever to undervolt much as I did
[Nexus 6 Android Development] harvickgm:
well, I am completely at a loss, i went back and flashed 1.9.1 and 1.8 with the same issues. then i wiped and flashed a new rom with 1.9.2 and had the same issue again. I then flashed ElementalIX, Franco's R21 and Faux123's 007 Kernels and all of them ran fine, without the bootloop issues. i really love the features in this kernel but it seems it just does not like my phone
[Nexus 6 Android Development] Xileforce:
Could u see if lean kernel has issues? We share the same ramdisk
[Nexus 6 Android Development] harvickgm:
OK, so I tried the latest LeanKernel and it seems fine and boots fine. Not including the initial boot, I rebooted 7 times without any boot loop. It did do the "Optimizing Apps" process one time that took awhile but it did still boot. Normally with yours it wants to optimize every time and it will get thru that and either freeze (black screen of death) or start the Motorola boot screen all over again. So I am not sure what would causing this. I even flashed the new LMY47M radio and boot loader to see if that would change anything and it was still the same.

So I have tried different flashing methods, installed new and different Roms and even going back to older versions with the same results
[Nexus 6 Android Development] noahthedominator:
I've tried this kernel on clean rom and on Resurrection Remix. Both times I got stuck in boot loops and had many problems. What Roms is this kernel working on?
[Nexus 6 Android Development] LunaticSerenade:
Fun fact: 2.9 GHz got very unhappy at 1070 Mv. Works great at 1075 Mv. :D
[Nexus 6 Android Development] Drefsab:
I'm running this on chroma with no issues have been for quite some time. Updated to the latest ROM and kernel only this morning.
[Nexus 6 Android Development] Admiral2145:
For some reason when I turn the screen of with interactivex and turn it back on... It goes to 300mhz vs staying at 35mhz...running meanpop rom...
[Nexus 6 Android Development] jackpollard:
Been working great on Benzo for quite some time.
[Nexus 6 Android Development] le1tho:
This kernel causes me random freezes and then reboots, clean installation of stock LMY47I firmware, stock voltage, other kernels have no issues even with -50mV. I have bin 8.

Tested performance with 3DMark Ice Storm Unlimited and ondemand or InteractiveX are giving me lower scores than stock Nexus 6 in their database or with other kernels-tried ElementalX and Lean-those are around 23000 with stock clocks, ondemand governor and msm-adreno-tz or simple_ondemand governor for GPU.
[Nexus 6 Android Development] oOflyeyesOo:
I was getting some System UI FC's on Chroma, the OP replied that it was a missing torch commit in the kernel that was causing the issues. I will post a logcat if it happens again. Here is the post: http://xdaforums.com/showpost.php?p=59808086&postcount=10218

Also, I tried to enable doubletap2wake in Synapse, and it didn't seem to want to save.

BTW, I am in love with your kernel, such amazing battery life. Best kernel to date!
[Nexus 6 Android Development] Xileforce:
Have u tried flashing the ROM. Booting up and then flashing kernel? It should work on all ROMs unless they have modified their ramdisks. I'll look into it further for V2.0
[Nexus 6 Android Development] Xileforce:
Does it lock the min at 300? Or does it stay at 300. before dropping back down to 35?
[Nexus 6 Android Development] Xileforce:
This is interesting I'll mess around with it in 3dmark. I use antutu and get around 55k with graphics score of ~18200. Im not sure what would be the cause of this. If anything with a GPU oc it should be a bit ahead of other kernels In that department. There's only one thing I can think of ATM. If you are going to benchmark turn off Power efficient workqueues in the CPU settings of synapse.
[Nexus 6 Android Development] Admiral2145:
I set it to 35 then when screen comes back on its @ 300... And synapse shows it moved up on its own...
[Nexus 6 Android Development] Xileforce:
Thanks for sharing this I'll take a look!
[Nexus 6 Android Development] Xileforce:
Have you changed any other settings? What governor are u using? I have not heard of this issue before.
[Nexus 6 Android Development] SunShine.CID:
Vin and Bootloops

FYI I've been around the block and your Kernel is pretty awesome. Been watching the debate with bootloops and ROMs and thought I'd chime in. I use Chroma and have only had luck getting 1.7 to work with it. I haven't tried 1.8 but both 1.9.1 and 1.9.2 have not worked. Hope this helps.
[Nexus 6 Android Development] Xileforce:
Very helpful. Could u try 1.8 if you get a chance? Would narrow it down quite a bit.
[Nexus 6 Android Development] SunShine.CID:
Tested. 1.8 has problems too. Here's the breakdown as far as i can see. On boot mostly goes through app optimization process, and reboots. Upon next boot very quickly goes through the optimization process again and then gives black screen. LED notification light is on. Usually doesn't respond to buttons but one time it did bring up the power menu.
[Nexus 6 Android Development] Xileforce:
OK that's helpful. I'll look through what was added in 1.8 for anything suspicious O_o
[Nexus 6 Android Development] jackpollard:
It seems so odd that different devices can make such an impact on the operation of the kernel. I did flash another kernel last week, just to test it, I always come back to this one, however when I did flash the other kernel, I had the same issues as you all are having. I realized I had 2 different kernel tools running and it was causing me havoc.

I have Benzo rom and it has a kernel tool, then I had synapse. I had to make sure both were turned off, then I was able to flash the kernel with no loops or anything.

I booted into my last good nandroid, turned off all kernel tools and rebooted. Then I flashed the kernel and it worked with no issue. Just a thought.
[Nexus 6 Android Development] Xileforce:
Yea that's what is confusing me so much...people on the exact same ROMs are reporting 100% different things :/
[Nexus 6 Android Development] Xileforce:
ok guys I have an idea of what may be the culprit. Ill compile a build with the fixes and post it here for people with issues to try.

edit:

Here ya go. Those having issues let me know if this fixes it. https://drive.google.com/file/d/0B6n0VW96A9MoOW9jeE0zTkVocWM/view?usp=sharing
[Nexus 6 Android Development] gamewarden234:
This kernel is sweet. Over six hours SOT. So smooth. I will never stray again. Well done bro
[Nexus 6 Android Development] Xileforce:
Thanks man. Next release should be even smoother.
[Nexus 6 Android Development] noahthedominator:
Yes I've tried that and no luck.:(
[Nexus 6 Android Development] harvickgm:
I sent you a pm back, but the test kernel did the same. I going to give 1.7 a try as was suggested by another member and see what happens there
[Nexus 6 Android Development] SunShine.CID:
Figured I'd try it these ways reviewing the posts.

Downloaded it, installed it into Chroma 03-31 with Synapse: No Go

Installed it into Chroma 03-31 without Synapse: Loops, loops, then boots, no sim card error, not enough storage space error, everything is crashing (Chrome, Pushbullet, Google App) but I get my home screen. Then I reboot, into loops again.
[Nexus 6 Android Development] harvickgm:
Go back and try 1.7 and see if it bootloops. Mine stopped with 1.7, so now I'm playing with GPU OC and see if that's it
[Nexus 6 Android Development] Xileforce:
Hmmm its possible its the higher GPU oc. We had 700mhz before. Maybe 800 is too much for some people. I'll try reverting that.
[Nexus 6 Android Development] LunaticSerenade:
Awwwwwwww. :P
[Nexus 6 Android Development] harvickgm:
Set the default at 600 and let people OC if they need it. That way we can have all the new features. I hope it works lol
[Nexus 6 Android Development] poipen:
I have same problem. I was running 1.9.1 in two day but then I was back in a loop. And couldn't install it agen without boot loops. I try to flash 1.7 now and it works good.

Didn't work.

Tapatalk Nexus 6
[Nexus 6 Android Development] LunaticSerenade:
Any possibility of increasing the OC to 3.03 GHz?

I saw that in Zen kernel, and thought about flashing it, but I have Vindicator tweaked for some sweet performance and battery life, so I kind of don't want to change kernels.

Sorry to be needy! :angel:
[Nexus 6 Android Development] Xileforce:
I actually had a build with like 3.1 GHz but It was kinda unstable. But yea I'll add 3.03 step in Elemental has had that for awhile. As long as my bin 1 beta tester can run it. :)
[Nexus 6 Android Development] LunaticSerenade:
Haha, that's so mean! :P

I appreciate it though. I like have more sliders!
[Nexus 6 Android Development] Admiral2145:
Found it... Meanpop rom has it built in so.. When screen is off 300-1.6ghz and screen on 300 to 2.6ghz...its on the 1st page of his thread... Not sure how to disable it
[Nexus 6 Android Development] clnzx2:
Always gotta call me out :P
[Nexus 6 Android Development] donnellyian:
hmm that's strange this works with Chroma for me except for screen tearing with video playback. I clean flashed Chroma, booted up, then flashed vindicator 1.9.2.
[Nexus 6 Android Development] Xileforce:
Anyone with issues willing to give this build a shot? https://docs.google.com/file/d/0B6n0VW96A9MoV1kyclozWFJLOUE/edit?usp=docslist_api
[Nexus 6 Android Development] henrybravo:
I'm one of the guys you were chatting with in the Benzo thread that's been running this test9 build. After using the ROM for about a half hour, I've had a couple of random lockups. I think your overclocking might still be a tad aggressive for some phones, as my phone normally isn't unstable. What CPU/GPU frequency settings are you using in test9?