yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] clnzx2:
I vote for a higher freq build :)
[Nexus 6 Android Development] Xileforce:
So says the bin 1.... :P I'm sorry...I shouldn't pick on the less fortunate among us lol
[Nexus 6 Android Development] angiest:
I'm seeing something either new on 2.0, or that I simply never noticed before. Synapse is reporting my ROM type as Ubuntu. Anyone else have this?
[Nexus 6 Android Development] Xileforce:
I'm guessing u mean the ROM description section? To the best of my knowledge that's just the machine the ROM was built on. Mine says Macbeast.local and I'm euphoria.
[Nexus 6 Android Development] clnzx2:
Funny thing is I have had 0 issues pushing it to its limits
[Nexus 6 Android Development] angiest:
Maybe so. I'm on Chroma and I believe that is was zephiK uses. Strange that I never noticed it before.
[Nexus 6 Android Development] le1tho:
Can you also make GPU throttling temperature/frequency adjustable? In Faux's123 Kernel tool there is a slider for GPU throttling temperature but can't be changed even with his kernel so i don't understand why it is a slider then...

---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------

What about throttling?

Can you make a separate 2.0 kernel with 800 or even higher GPU clock? It can be set to 600MHz as default boot clock but adjustable to 1000MHz, that would be nice ;)
[Nexus 6 Android Development] Xileforce:
Maybe I'll make a separate kernel with crazy OC stuff. As for the GPU thermal deal that's not actually a slider it just tells you what the current temperature of the GPU is..I tried to slide it for like 10 mins before I saw it moving by itself and realized.......
[Nexus 6 Android Development] sparksco:
I used to do this a lot for the nexus 7 2012 because it needed it.. The problem is getting the voltages to match the frequencies so everything runs smoothly. Match the voltages with the frequencies properly will also allow you to get the highest possible clock speeds. Get your calculator ready lol
[Nexus 6 Android Development] Mistertac:
Shhhhh

Chroma + Vindi = Angry zephiK

[emoji6]
[Nexus 6 Android Development] Xileforce:
Yea and all the other things like bus voltages and such. Its just a pain O_o
[Nexus 6 Android Development] angiest:
Oh, I know. It also happens to be an awesome combination.
[Nexus 6 Android Development] Roland Deschain:
Chroma + a lot of things = angry Zephik, really.
[Nexus 6 Android Development] 9wire:
Used to try some crazy trinity kernels back when.
[Nexus 6 Android Development] MarceloSiciliano:
Zephik+everything= angry Zephik
[Nexus 6 Android Development] Xileforce:
Trinity kernels were great. Nice and simple but fast :) does morfic still dev? I've been out of the nexus loop for a bit.
[Nexus 6 Android Development] LunaticSerenade:
Haha, I'm like that. I like to push it.

I saw someone asked for a second super OC type build. That would be super cool, but if you don't have time, no worries. The fact remains that this kernel is awesome. :)
[Nexus 6 Android Development] dwibbles33:
Great Kernel and I love the variety of settings. I have only one issue involving my Xbox 360 Controller (wired). I search the source code on Github and it looks like you have included the Xpad driver in your code however my controller just won't work. Its odd because the OTG works and when I use USB Device Info app it sees the controller, but only in the Linux tab (as opposed to the android tab). Anyway, when I plug it it the lights on the controller flash but when I play a game using limelight it doesn't work. I have been able to make it kind of work with joypad center gold, but that app hardly works right and I'd like to figure out how to get it working without background apps that kind of work. Any information needed I'd be more than happy to provide, I've been researching the topic and haven't found any solutions that work. Thanks!
[Nexus 6 Android Development] Xileforce:
interesting. I've never attempted to do this before. Does this happen on all kernels or just Vindicator?
[Nexus 6 Android Development] sparksco:
[MENTION=4517211]Xileforce[/MENTION]

I finally was able to get strict-aliasing working. But what I did instead of hard coding it was made it a defconfig option for my device. Since like you said it will vary depending on the device. I thought you might be interested in making yours like I did mine as a option, but of course not really necessary. It just makes it more up to Linux kernel GPL standards I suppose.

I also did a similar thing for stack protector options. I did some research. The all option reduces performance. The strong option protects more functions but does not reduce performance like all does. The stack protector option is for ARM instead of device, so it should be easier to configure for various devices. In order to enable strong you'll need to keep the normal stack protector config option enabled since strong depends on that being enabled. It's on the wip branch of my kernel source.

https://gitlab.com/SaberMod/android-kernel-lge-hammerhead/commits/wip
[Nexus 6 Android Development] Liam Neeson:
Strict aliasing should be good performance imrpovement
[Nexus 6 Android Development] sparksco:
The strong stack protector is only a feature google added to upstream gcc 4.9. I think they still use gcc 4.8 for the kernel.
[Nexus 6 Android Development] Xileforce:
Interesting. May give it a shot. Have u tried it yet? Edit also gonna pull down source for new sm prebuilt in a sec and try it :) the previous build didn't support stack protector so I'm assuming that's been added back?
[Nexus 6 Android Development] dwibbles33:
I've tried Vindicator and Leankernel (both didn't work), however since leankernel is your base I'm guessing that doesn't really mean much except that it wasn't something you did to the kernel. I can test it out on other kernels or just compare source code with other kernels to see which ones to test. It's odd that the controller doesn't work because the thing I keep reading on the web is that its natively supported, I'll take a look into some other kernels and let you know what I find. If there is anything else you want me to try/do while I'm at it let me know. I figured I'd try you first since Imoseyon isn't as responsive as you are.

Additionally, if anybody else has the ability to test this out that would be a big help in trying to possibly narrow down the problem.
[Nexus 6 Android Development] Xileforce:
Awesome. Yea if u could try it on like Franco kernel that would probably be enough of a test. I will look into it as well but unfortunately I cannot test for myself. Please let me know if u figure something out :)
[Nexus 6 Android Development] Xileforce:
I'll also be compiling a build with the BFS scheduler that zen uses. Its a CPU scheduler not an io scheduler. Currently we have CFS and Power Aware as the two choices. I believe bfs will replace CFS. CFS is the stock option in Synapse ATM. I've been reading up onf BFS and I like the logic behind it thus far
[Nexus 6 Android Development] sparksco:
Yeah it works fine. I pushed the final patches to master branch of kernel.

The toolchain always supported it. I removed a folder last time that we needed so it was giving those errors.
[Nexus 6 Android Development] sparksco:
Thank you sir.
[Nexus 6 Android Development] Xileforce:
Awesome man. Pulling it down as we speak. Will let u know how it goes. I may try out that strong setting as well.
[Nexus 6 Android Development] dwibbles33:
Just flashed Franco and it works! Interesting, maybe it was cut out to make leankernel more "Lean"? Let me know if there is anything else you want me to do. Thanks for getting back to me so quickly!
[Nexus 6 Android Development] Xileforce:
grrr...this is gonna be harder because he doesnt upload his defconfig changes :/ which is where you would disable or re enable the modules etc. Ill scour around for it and see if I can find any disabled modules that may be related. thanks for testing!
[Nexus 6 Android Development] Xileforce:
also just curious but have u tried BFS instead of CFS on your kernel before?
[Nexus 6 Android Development] dwibbles33:
Is there possibly another ROM that you want me to test who does upload those changes?
[Nexus 6 Android Development] Xileforce:
ummmm.....you could try hydra. Man you are a good tester. If you ever wanna become a beta tester, just hit me up with your hangouts and ill add you to the group if ur interested :)
[Nexus 6 Android Development] sparksco:
Definitely read the descriptions I added. The descriptions are mostly from internet searches I pulled up lol. I think what google attempted with strong was to find a good balance between security and performance. If you want strictly performance I'd stick with the normal mode. But I thought I'd test it out for a bit at least since it's a feature Google can't use in their own kernel toolchains. And I'm sure people would appreciate the extra security. I'm also testing secure computing enabled.
[Nexus 6 Android Development] Xileforce:
very interesting. Please keep me updated on your testing! what is secured computing?
[Nexus 6 Android Development] sparksco:
No, there's no patch that works for my kernel version 3.4. [emoji26]

I've tried making other versions of bfs patches work too and they don't seem to work. I used it on my evo shift 4g for gingerbread and ICS though and it worked great.
[Nexus 6 Android Development] sparksco:
Pretty much what it says.

http://en.wikipedia.org/wiki/Seccomp

There's a couple config options CONFIG_SECCOMP

and

CONFIG_HAVE_ARCH_SECCOMP_FILTER

I use them both.
[Nexus 6 Android Development] dwibbles33:
Hydra works as well! I sent you a message about the beta testing, sounds great! Let me know if there is anything else I can do. I'd compile something on my own if I knew what I was doing as far as Git goes and adding features and such. Compiled a ROM and kernel before but just built it from source without any adjustments, for the learning experience (and to test out my computer's speed after I built it). Since I don't know how to do any of that I figure being as cooperative as possible would be the fastest way to reach the same conclusion. Thanks again for all the help with such a small issue.
[Nexus 6 Android Development] sparksco:
I hate that. It makes it impossible for anyone to compile the kernel inline with no defconfig changes. Well I mean you could, but the kernel wouldn't compile to turn out the way exactly like they compile it.
[Nexus 6 Android Development] Xileforce:
ikr :/ luckily i can pick out most of the needed defconfig changes by looking through the commits. but stuff like disabling modules, etc is impossible to know.

Edit:

Its all good we figured it out.
[Nexus 6 Android Development] sparksco:
IIRC bfs is enabled by default.
[Nexus 6 Android Development] Xileforce:
Yup. I was referring to the gamepad module support. It was called joystick in defconfig.

Edit never mind: apparently that didn't fix it lol. Gonna scoure through the defconfig and try different things.
[Nexus 6 Android Development] sparksco:
[MENTION=4517211]Xileforce[/MENTION] Thought I'd share my results with latest test. No overclocking of any kind and benchmarks are looking really well compared to most nexus 5's. This is with the current changes that are on GitHub with ARM cryptographic API's enabled.
[Nexus 6 Android Development] Xileforce:
Wow that's impressive! I'll have to take a look at your nexus 5 git.
[Nexus 6 Android Development] eltnav:
newb question

Pardon the lack of knowldge. Just want to make sure I am clear prior to flashing this kernel. I recently decrypted my nexus and am flashing it back to what I was using prior to whiping it today. I read vindicator does not force encrypt but is encryptable. I just want to make sure if I flash that I won't be encrypted again. I think I will be fine but just want to make sure. I had a fun time getting this phone decrypted. Don't wanna deal with that again tomorrow. Lol
[Nexus 6 Android Development] Mistertac:
You're safe. Vindi won't force encryption.
[Nexus 6 Android Development] eltnav:
Thanks! Just wanted to be safe rather than sorry.
[Nexus 6 Android Development] Xileforce:
Good call. Encryptable means it will just use whatever you have already. So if its encrypted it will stay encrypted and if its unencrypted u will stay unencrypted.
[Nexus 6 Android Development] sparksco:
Most of the features I've been enabling came with the previous arm patches I applied. Like the secure computing and arm cryptographic api's. Most of those arm patches should already be in the 3.10 kernel but maybe not all since the patches I backported from the Linux kernel 3.19 stable. Just thought I'd point that out in case you try to enable some options and they don't stick for some reason in the defconfig.
[Nexus 6 Android Development] eltnav:
It running good. Thanks! Is it possible to increase the bin? I've been making the mods suggested on the first page. But curious if the bin can increase or it is what it is. I'm a 5
[Nexus 6 Android Development] clnzx2:
The bin is the quality rating of the CPU and can't be changed. Be thankful you have a 5...I have a 1 :(
[Nexus 6 Android Development] le1tho:
Can someone post his voltage table? Would be good to compare if lower bins are really lower quality or only theoretical.
[Nexus 6 Android Development] Xileforce:
They are. The source code itself actually has a voltage table for each bin. Here's a pastebin I just made of them all http://pastebin.com/Q3tZ56YV the # after PVS is the bin. The first number in each table is the frequency the second is the voltage.
[Nexus 6 Android Development] le1tho:
Are steps 300-883 undervolted in your kernel? Because i am not sure if i just didn't set them lower by mistake.
[Nexus 6 Android Development] Xileforce:
I don't undervolt anything by default. The thing is imoseyons voltage control somehow picks a voltage table to give each bin. So even though u are a bin 10 for example u may use the bin 13 table. I honestly have no clue why that is. Lol
[Nexus 6 Android Development] Annie the Eagle:
What is the difference between SM5 and Linaro4.9.3 file?
[Nexus 6 Android Development] Mistertac:
He was testing which toolchain may be better. So the SM5 = SaberMod 5.0 and Linaro Toolchain is still at 4.9.3

All the actual kernel features are going to be the same.
[Nexus 6 Android Development] sparksco:
I had this bin problem with nexus 4 mako also. Some bin can undervolt more than others. Really strange how they do this. You'd think they could make all the devices with the same voltages but no.
[Nexus 6 Android Development] Annie the Eagle:
So the SM5 is the better one?
[Nexus 6 Android Development] Xileforce:
Most people seem to prefer that version yes.
[Nexus 6 Android Development] MMLP2:
I do enjoy it too
[Nexus 6 Android Development] USA-RedDragon:
So the beta testers actually had to revert back to the public release. I think this was the first time too. Overheating problems for a couple of people. And bad battery. In fact there is a small clip to show how we felt about it. https://docs.google.com/file/d/0B_ij7hzI7AmKbmhoREZ2N2Excnc/edit?usp=docslist_api

Oh, and the Qualcomm 810 and HTC One m9 had nothing on our heat. Lol
[Nexus 6 Android Development] USA-RedDragon:
[MENTION=4517211]Xileforce[/MENTION] Screwed up and made us all go crazy. This was our face
[Nexus 6 Android Development] sparksco:
Well that's why it's called beta testing. If you can't handle the risk no need to post such outrageous comments. People request things like extreme overclocking then freak out when their phone overheats.
[Nexus 6 Android Development] Liam Neeson:
For the love of god don't click the link! You can't unhear that sh!t!
[Nexus 6 Android Development] Xileforce:
He normally posts this stuff in beta chat. Sometimes he spills over into the thread :/ not a whole lot we can do for hims unfortunately. He refuses to take his meds.
[Nexus 6 Android Development] USA-RedDragon:
Thx
[Nexus 6 Android Development] dannieloco:
Is this kernel backwards compatible? will it work with 5.0.2? Im a running v1.5 and wanted to update, but just saw that v1.6+ is Android 5.1 compatible.
[Nexus 6 Android Development] Xileforce:
No. Only versions before 1.6 will work on 5.0 and only builds after 1.5 will work on 5.1 :P I've kept the downloads up for those still hanging back on 5.0. All new builds are strictly for 5.1
[Nexus 6 Android Development] MMLP2:
This kernel should come stock on Google s factory images
[Nexus 6 Android Development] stevepick2:
Some reason it doesn't like to wakeup from deep sleep
[Nexus 6 Android Development] Xileforce:
Oh! wow I shouldve realized that :P. I suggest just leaving it on the default governor, however if you have certain games that lag a lot setting it to performance may help when playing those games. I may consider adding in the simple on demand governor, but im unsure of its advantages.
[Nexus 6 Android Development] clnzx2:
If it helps anyone I have a bin 1 CPU :( and am still playing with voltages but so far -25mv across the board and 500mv at 98mhz is working with no problems.
[Nexus 6 Android Development] Xileforce:
you sir, are a true victim of luck and I honor your heroism in this time of hardship. Please let us know how far you manage to undervolt as a whole and if you get any SODs with 98.
[Nexus 6 Android Development] Xileforce:
A New Experimental Release 1.2RC1 is out! Main new feature is my first shot at GPU OC. For all I know it could be completely pointless but I figured I would let you guys test it if you wanted. There's anfew other changes you can find. In change log too. If you test it GPU OC may not workvat first. Simply drag GPU frequency slider down to 500 then back up to 685. Also for whatever reason I had to change 600mhz to 605 in order to get the OC to work...I have no clue why. Anyways best of luck! If you have issues please flash back to 1.1 and report the issue here. You can find a log in /sys/fs/pstore then I need the dmsg.
[Nexus 6 Android Development] philosophics:
Got another random reboot after not having one for an entire day. Thought I was in the clear...

https://docs.google.com/file/d/0B9NxD3jJTy-sT0lWaU80MEMzcGs/edit?usp=docslist_api

Sent by a Whale
[Nexus 6 Android Development] Xileforce:
Please give the new release a shot and report back. I believe I've fixed that crash. I had another person who's been running it for over a day without issues and he was having many reboots. I believe it was power suspend. TY for the log BTW!
[Nexus 6 Android Development] Mistertac:
Yep... Not one reboot on the latest one. I THINK everyone should be alright.
[Nexus 6 Android Development] Xileforce:
Sweet. Upcoming update should help stability further and fix one more reboot I caught.
[Nexus 6 Android Development] siddhesh.raikar:
Hey, really good job on the kernel..

Could you include the latest change from lk where the sensor_ind wake lock is disabled from within the kernel please..
[Nexus 6 Android Development] Xileforce:
I've been checking his github for that but he has not pushed it yet. As soon as he does I'll have that and the rest of the changes he makes :)
[Nexus 6 Android Development] VerdammteSeele:
Despair to Vindicator

I switched from Despair to your Vindicator kernel afer Despair reached 3 random reboots per day and I've had 1 reboot in 2 days since then (I like to change kernel settings too much). I've goten into Android development, specifically kernels recently and I'd love it if you would share notes on how you got to where you are. As for the kernel, have you looked into adding Same-Page Merge? I've looked into it and the theory looks great, but I've never looked at implementation.

Congrats on the kernel, it's working great!
[Nexus 6 Android Development] Xileforce:
Great to hear and hopefully that one reboot will get fixed up with the upcoming update! I'd be glad to help ya out. Hit me up on hangouts xileforce@gmail.com as for ksm I've considered it, however the whole idea behind it is you are trading CPU for more ram, and I'm of the belief that with 3gb of ram we are pretty good on that front already so I would rather not sacrifice more CPU and thus more battery life.
[Nexus 6 Android Development] VerdammteSeele:
Sounds perfectly reasonable to me. I'll message you sometime. Keep up the great work. I'll be flashing those releases as soon as I see them.
[Nexus 6 Android Development] Mistertac:
The next release should be pretty cool, been running it for a bit now testing things out and so far so good.

I won't ruin it and post screen shots of what's to come.. Although I want to! [emoji6]
[Nexus 6 Android Development] Xileforce:
Would anyone be interested in being a beta tester? Could use a few more. If you are interested, drop a post here with your hangouts and I'll add you to a group :).
[Nexus 6 Android Development] siddhesh.raikar:
Interested.. siddhesh.raikar
[Nexus 6 Android Development] Xileforce:
Added :)
[Nexus 6 Android Development] Swamphound:
I'm an idiot when it comes to kernels but I'd like to learn more and as noted earlier I'm a bin 8 if that matters for testing. I'll PM my hangouts and would be honored to test if you'll have me. Do you have any preferences with logs?
[Nexus 6 Android Development] Xileforce:
Added you :) and no worries we are all noobs. Sys/fs/pstore then the dmseg seems to be the best log we have atm
[Nexus 6 Android Development] USA-RedDragon:
I'm interested. I used to help with Despair kernel before he had to slow development because of stability issues. If you want, hmu on hangouts. jamcswain2000@gmail.com
[Nexus 6 Android Development] Mistertac:
How are you waking your phone, a wake gesture?
[Nexus 6 Android Development] stevepick2:
Power button and gestures. Sometimes I have to press the power button repeatedly and sometimes I have to do a hard reboot
[Nexus 6 Android Development] Swamphound:
Can you give us some more info about your rim and kernel settings? Not usually an issue for us.
[Nexus 6 Android Development] stevepick2:
I'm on Chroma

Max 2.9GHz

Min 35Mhz

Governor: interactive X

GPU: 700 Mhz

I/O Scheduler: fiops

Read Ahead Size:1536

TCP:Westwood

Fsync disabled

DoubleTap and Swipe 2 Wake enabled

GPU Acceleration

Just In Time Compiler

HSUPA Upload speed hack Enabled (Uncapped)

Super tweaks

Zipalign apps
[Nexus 6 Android Development] Mistertac:
Try setting all your Wake options using LKConfig. Definitely more reliable. And although none of us testers have a hard time waking up our phones with 35mhz being the min, you could try raising your min to 98 and then 300 if needed.

Also I've seen many Chroma users having this issue with Vindi... Is there something built into Chroma option wise for waking the phone... Maybe preventing accidental wake ups or something?
[Nexus 6 Android Development] Xileforce:
How are u using Just in time compiler on lollipop?
[Nexus 6 Android Development] stevepick2:
It's an option in the app I use called "Kernel Tweaker"

Some reason it is working normally now.
[Nexus 6 Android Development] Xileforce:
I wouldn't use that option. Lollipop no longer has Just in time compiler. That got replaced by ART. Who knows what that me be trying to do with that setting on. Good to hear its working well now though! :)
[Nexus 6 Android Development] stevepick2:
I've heard this kernel has had problems on Chroma. Mentioned it on the forum and they said people may get upset with me using it and to be prepared for angry responses. Don't know what all that's about
[Nexus 6 Android Development] Mistertac:
Lol I saw that. I don't know either man. We're all here to have fun, seems silly to me.

Most ROM devs won't offer too much support unless you're using the stock kernel that came with the ROM, that is understandable. But to get angry about it, seems a waste.
[Nexus 6 Android Development] Swamphound:
+1. We test this kernel on many ROMs and I personally run it on Chroma without issue, at least none that I give any notice to. The wonder of Android and it's open source is to experiment and mix things up and I'm thankful to be able to use the contributions of all in this community.
[Nexus 6 Android Development] MarceloSiciliano:
The chroma community is a little weird. If you don't use the things they want you to use they get mad with you. That's why I stopped using chroma

They are trying to do what apple do, but inside android hahahaha