yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Lawlrus:
He uses anykernel with his kernel like a lot of devs are now doing, so realistically it should boot on anything 6.0.1 . One kernel to rule them all, all being ramdisks
[Nexus 6 Android Development] pillo85:
Just flash it on tupac stock and is running really smooth, am planning on trying Krexus with this kernel later on the week but I will give tupac with Render a try
[Nexus 6 Android Development] garywojdan81:
Great on Pure Nexus. Thanks for sharing your work.
[Nexus 6 Android Development] :
Probably a noob question... But I noticed going through settings In k.a., that swappiness is disabled, do I need to set it to a value or leave as is? I've noticed every kernel I've used before this had some kind of value to it..really don't know what it does, but just wondering.
[Nexus 6 Android Development] rignfool:
Do you use a swap file?
[Nexus 6 Android Development] :
No I don't...so I guess that answers my question. Thank You!!
[Nexus 6 Android Development] GabrielSousa:
you had random boots with other kernels ?
[Nexus 6 Android Development] RenderBroken:
I know it had been quiet. I assure you I am still working on this kernel and have done my 3rd rebase/rebuild from scratch. I am aiming for a certain type of build and believe I have achieved it. I have some very minor changes I plan to make then I will release a full release. If you havent noticed, I have been using G+ for alot of day to day chatting and testing of test builds. You can find it here:

https://plus.google.com/u/0/communities/110618444908886909218

I have been crazy busy lately. I work 2 jobs and have a beautiful young family that requires my attention as well. But, hopefully with things settling down (FINALLY) I can get into a better release schedule. Thanks guys for hanging around so far. I still have plans to continue building into the foreseeable future. I do plan on purchasing the next Nexus phone. ;)
[Nexus 6 Android Development] Virus1x:
Can't wait.
[Nexus 6 Android Development] rignfool:
As long as I keep breaking things...

We're gonna have to wait longer...
[Nexus 6 Android Development] II_DiE_4:
Wow..

Tried the latest beta and its amazing.

Never saw 8h sleep with 1% lost before.
[Nexus 6 Android Development] NITRO_2:
Where did you find that? Or is it R3?
[Nexus 6 Android Development] II_DiE_4:
On the Google+ page..

https://plus.google.com/u/0/communities/110618444908886909218
[Nexus 6 Android Development] BeDesireS:
If you would read only 4 posts before yours, you would know it. [emoji6]

Send from my AOSiP powered Nexus 6
[Nexus 6 Android Development] NITRO_2:
Appreciate it.
[Nexus 6 Android Development] Lawlrus:
Read.... blasphemy !
[Nexus 6 Android Development] RenderBroken:
R4 is HERE!!!

Download

Things to note:

First, thanks to all the testers that have been giving great feedback and concise information. One tester has been more of a partner in the development of my latest build. I like to give proper credit so a very special thanks to [MENTION=3290808]rignfool[/MENTION] He has been with the development process on a constant basis and has been a tremendous help to this Kernel. There has been alot of very hard on this build since I felt that the kernel could be so much more but my previous kernel builds (R1, R2, and R3) did not have the needed ground work that I felt I needed to move forward. I completely rebuilt from scratch R3. Now once again, I completely rebuilt from scratch Release 4. But I will let the kernel speak for itself.

This is a culmination of a metric crap ton of work. Testing and building. When I release, I try to release milestone releases. Completed releases. If you want semi-dailyish builds then follow my G+ community. It just makes it easier for me to keep up with everyone.

But if I were to highlight some features/changes, here they are:

Updated to 3.10.202

Reworked Scheduler, CPUFREQ, Hotplugs (Now only using State_Helper from Neobuddy), RCU, Locking/Mutex, Perfected LMK and OOM, IRQ, Sleep/Power, Camera, Upstream F2FS and EXT4. And MANY MORE!

See Changelog for a massive list of changes.

Changelog
[Nexus 6 Android Development] Lawlrus:
[MENTION=5438598]RenderBroken[/MENTION] bout time !
[Nexus 6 Android Development] RenderBroken:
Ha, I know right? Been busy as hell with work and now my wife's car threw a timing belt! lmao. Two shops I called about fixing told me no and that they didn't even want to attempt it. . .uhg
[Nexus 6 Android Development] Lawlrus:
I could never understand that, I mean I get it. Timing belts are a pain in the ass to get right but money talks, its not like they wouldn't get paid for it.

But you know I was just breaking your balls, real life is always > development.

Last test runs great so I'm going to have to take this for a spin soon. Appreciate the work bro
[Nexus 6 Android Development] RenderBroken:
Of course I know how to take you man. We have known each other for at least a minute lol.

I agree. There has been so much tweaking and testing put into this build. It is the best I have felt about any of my own releases.
[Nexus 6 Android Development] wase4711:
nice! Flashing it now..

thanks
[Nexus 6 Android Development] rignfool:
I'm not sure if you're a car guy or not... but...

There are 2 types of engines... interference and noninterference..

If it's an interference engine... the piston and the valve occupy the same space at different times...

When the timing belt slips... the valve loses... and heads are expensive
[Nexus 6 Android Development] Lawlrus:
Nope, was always more into computers than cars, guess that makes sense though a s far as how much of a pain in the ass it can be.
[Nexus 6 Android Development] Dachfenster:
There's still something not going well with the wake gestures.

Can't get swipe to wake to work at all and double tap to wake is unreliable for me. However, swipe to sleep works.
[Nexus 6 Android Development] RenderBroken:
I have played with this and tested different versions of Wake gestures and still get the same results. Not quite sure what the problem is but I cannot see any gestures being more efficient than DT2W. Not to argue, but what gesture is missing for you that you use the most and why do you prefer it over DT2W. Honestly, I am just curious because you are not the only one to have such issues.

I will continue to look into it. Do you know of another kernel that it works properly in? Maybe I can compare. Let me know. Thanks!
[Nexus 6 Android Development] wase4711:
dt2w works perfectly for me and most others; its either his rom, or operator error..
[Nexus 6 Android Development] Dachfenster:
I personally like to use the swipe up gesture to wake it up. Can't say why, it's just personal preference I guess. :laugh:

It worked on the same rom with Blackbird kernel.

And I've linked a possible fix by flar himself in this thread here but since you've liked my post back then, I assume you've already seen and tried it. Yet here's the link again:

http://xdaforums.com/showthread.php?p=66350641

Welp, thanks for that. It's definitively not the rom (pure nexus) since it worked with the kernel mentioned above. It might be a combination of kernel + rom though, but I think that's pretty unlikely.

I can (not always rather often) provoke DT2W to misbehave. If I turn the screen off and immediately try to turn it back on by double tapping, it happens that it doesn't turn on. I use always the same speed/ delay between the two taps and on the second/ third attempt it'll finally work.

But that's - as I said - not always the case but I can definitively provoke it and in let's say 3 of 10 tries it will happen like I explained it.
[Nexus 6 Android Development] II_DiE_4:
Can i ask if still Synapse is recommended or Yoinx KA mod?

Render-UKM is from February so is it abandon?
[Nexus 6 Android Development] Lawlrus:
Modified ka
[Nexus 6 Android Development] AlkaliV2:
Did you switch custom kernels properly (as outlined here: http://xdaforums.com/showpost.php?p=67509651&postcount=26716) and wipe your kernel app data (synapse, Kernel Adiutor, etc) before installing the new kernel? Dirty flashing kernels on the N6 leads to undesirable results and if your kernel app tries to apply settings to a kernel that doesn't have them built-in you could have issues.
[Nexus 6 Android Development] Dachfenster:
Yeah, always do that - dirty flashing the rom before a applying a new kernel. Apart from that, I always kill KA after initial boot with a new kernel so it can't apply my old settings on boot. I don't clear app data since I've got plenty of profiles in KA.

However, this shouldn't be a problem at all because I activate my wake gestures via tasker on boot. Basically doing the things KA does in the background as flar2 has explained it in his kernel thread. And it always worked.

But I've also tried to deactivate the script and use KA instead - same results.

Edit: Everything works when using flar2's wake gesture app. Gonna stick with this now and see how it behaves.
[Nexus 6 Android Development] AlkaliV2:
In that case this may be a kernel that just straight up doesn't work with your hardware. My device, for example, absolutely will not cooperate with a kernel compiled using the Uber toolchain. I can't precisely pin down why my phone performance suffers so dramatically with one installed (I even tried Ubermallow with a stock kernel and still had issues) and so I now stay away from things compiled with that toolchain. It is possible there is a commit or a setting in the kernel that doesn't agree with your hardware and the only real way to know is to get some really great debug logs that capture what is happening (or not happening) when you pass the gestures to your device. It would help you and the dev find some concrete reason of why the command isn't being passed properly. I was going to recommend a logcat being output to your computer linux terminal via a USB cable and attempting the gesture commands, but I don't know that logcat will recognize anything of that nature with the screen off. Can't hurt to try though.
[Nexus 6 Android Development] Dachfenster:
Like [MENTION=5438598]RenderBroken[/MENTION] said it, it's not only me.

Sure I can grab a log if he says which one he needs. :)
[Nexus 6 Android Development] AlkaliV2:
In development it is better to find a cause rather than company. Here is a good place to start for finding kernel messages from your device that outputs over USB from a Linux terminal:

Link: http://bootloader.wikidot.com/linux:android:kmsg

Two logfiles saved to the device that store kernel information are:

/tmp/recovery.log and /proc/kmesg

Here's a pretty good guide on getting kernel information after a random reboot but also useful for general output:

http://android-revolution-hd.blogspot.com/2014/02/how-to-generate-kernel-log-after-random.html

Render may need another file, but KMesg should at least let you see if your gestures are being registered properly the way Dmesg recognized hardware changes.
[Nexus 6 Android Development] Lawlrus:
Dt2w works fine for me, so long as I don't try to use it on the bottom half of the screen, dead center up works perfectly every time, on any ROM I've flashed.
[Nexus 6 Android Development] RenderBroken:
I will compare my Wake Gestures code with Revs (Blackbird) to see if there are any differences. I use a modified version of Wake Gestures and it may not be compatible fully without using Flar's app. But that last part is just a guess. Thanks for the info, I think I can find out what I need from the context you have provided.
[Nexus 6 Android Development] berndt_toast:
Love this kernel paired with Pure Nexus. Best kernel I have found so far.
[Nexus 6 Android Development] PWn3R:
Hey [MENTION=5438598]RenderBroken[/MENTION] - are you compiling this using arm-eabi or arm-linux-androideabi? Elaborating a bit more - I tried building this with one of the Hyper toolchains, but I get this:

arm-eabi-gcc: error: unrecognized command line option '-pthread'

That's what I want to know how to fix.

Edit: I talked to the guy who makes Hyper toolchains, and he says these pthread is not supported in his current builds. I guess what I want to know is where to get a copy of the toolchain that will work to compile this. I just removed one of the flags to stop pthread thing but now I get this:

/bin/sh: 1: /home/pwn3r/bsx/prebuilts/gcc/linux-x86/arm/arm-eabi-5.3/bin/arm-eabi-ld.gold: not found
[Nexus 6 Android Development] TheGeekyNimrod:
Ran your kernels back when my S2 was still going strong. Now I find you here with the Nexus 6. My phone choices are stalking your kernels.
[Nexus 6 Android Development] RenderBroken:
Can you link you source with your Makefile? It may be as simple as he doesnt have that added to the 5.3 toolchain. I use an older (stable) version of arm-eabi 4.9. I have it pushed to my source if you would like to sync. It is on my Github.

I remember. Glad to see you around. The S2 was how I started out. I really wanted that KK release on our i777. No one was working towards that goal so I decided to make it happen. But with my crappy build machine. I soon found that I enjoyed working on kernels way more than Rom builds. IT also only took me (at the time) about 30 minutes to compile a kernel and upwards to like 11 hours to build a rom. lol. I have come a very long way in my development work. I have learned a metric crap ton and like to still share what I know with those that want to learn as well. I will not say that I am the end all be all kernel god but that I have been doing this long enough to have picked up a few things.

Let me know what you think with the latest build. Thanks for saying hello!
[Nexus 6 Android Development] Lucifer.S:
Working super with purenexus ROM
[Nexus 6 Android Development] golfgtiedition30:
I've been running this for a few days now. I have to say this kernel is great. I paired it with krexus ROM and it seems an awesome combination.

Thanks for your work dev :)
[Nexus 6 Android Development] PWn3R:
Thanks for the information Render. I'm going to try to drop the kernel part of the build to 4.9 and replace my existing Hyper toolchain with the 4.9 version you are using because it looks like pthread isn't supported and if I remove the flag to fix pthread, other stuff breaks using the 5.3 version I've been using (graphite optimizations i think).

Sorry for the noob questions.
[Nexus 6 Android Development] RenderBroken:
No sweat bro. Feel free to post developmental questions in the thread anytime.
[Nexus 6 Android Development] julius4364:
Is anyone facing troubles with usb otg??

When i stick my usb the phone frezzes and reboots.
[Nexus 6 Android Development] Lawlrus:
I can check when I get home.

When you post an issue at least list what ROM you're on, and grab a log if possible. But yeah, I'll report back after I get off work.
[Nexus 6 Android Development] julius4364:
This happend on pure nexus and now on candy six.

I have never had anyone issue so i don't know how to take a log.

Thanks anyway.....
[Nexus 6 Android Development] Lawlrus:
Thanks anyway? Lol I'm not sure if that means you think you're getting blown off or what, but if you don't know how to take a log, look it up, just like anything else.

What I would suggest is to download catlog from the play store, set a widget to start the log, then plug in the USB drive and let it get a log of what's going on.

If it doesn't become responsive after you remove it, there might not be a way to save the log that way, but IRS worth a shot. At least that's what I plan on trying.
[Nexus 6 Android Development] julius4364:
I wil give that a try ....

"Thanks anyway "was for your intrest for checking it after your work.
[Nexus 6 Android Development] Lawlrus:
Ah okay, I read it wrong. But yeah, it you wanna try that it would be great, helps out render if we can grab logs and such, I'm still going to give it a hot here in about four or five hours. I'll have to find my otg cable lol. Been a while since I've used it.
[Nexus 6 Android Development] julius4364:
I tried with catlog as you told me but it doesn't take log.

Still when plugging usb stick the phone frezzes and reboot...
[Nexus 6 Android Development] Lawlrus:
Yeah, I've got the same. Going to try to get a lastk msg tomorrow at work to post on g+
[Nexus 6 Android Development] cowboysgz:
Awesome kernel! Thanks for your hard work.
[Nexus 6 Android Development] 309041291a:
I'm running PureNexus and this kernel with the SmartMax governor. I have to say this kernel is incredibly smooth and stable. I was getting some weird freezes and SOD on the interactive governor setting though.

Anyways, what is everyone running for settings geared towards better battery? I only get around 3 hours SOT with WiFi (not data) right now. I'm trying to push for 4 SOT on WiFi and around 3.5 with data over a ~14 hour span (my regular use).
[Nexus 6 Android Development] Stylez Ray.:
IMO your SOT is normal. I think the problem we have in this community is that there are many people who post their 5+ SOT which lead us to think SOT with 3-4 hours is not normal. These people have a habit of tweaking their phone to death, crippling syncs, undervolt, underclock etc. Of course you can get such high amount of SOT but for an average person who uses his/her phone trough the day while having different scenarios (reception, Wifi on/off, switching networks...) 3-4 is totaly acceptable. In the end it all depends on how you use your phone. We can't be sure if those people who have 5+h SOT really youse their phones like a normal person, many want us to believe this but many of them can't prove it.

In addition: I have been in so many sub forums here for years as I had so many devices and if there is something I noticed, it is those people who wonder about their battery life because they are being told from others about ridiculous SOT. Really, this talk is in every single device forum
[Nexus 6 Android Development] II_DiE_4:
Exactly as [MENTION=966150]stylez[/MENTION] ray said.

They just want the sot time to show 5+ and doesn't care about anything else.

What you should worry is if the normal usage YOU are doing doesn't get you through the day.

If that's the case then you should look for some ways to increase it, either lower your brightness, check for wakelocks or do what they do, and UV uc your phone.

If nothing works then I'm afraid you got the wrong phone for you.
[Nexus 6 Android Development] RenderBroken:
For me, I just want to make sure that I can easily get to the charger at the end of a long day. I never try to not charge my phone at night unless I am doing some testing and such. Other than that, I believe everyone should be charging nightly anyways and waht does it matter if you have 15% or 45% battery left as long as you make no compromises to the user experience and get to the charger at the end of the day. I design this kernel with this in mind. While others use some sort of conservative based governor, I like to have performance first then battery savings.
[Nexus 6 Android Development] Formhault:
You're right. I've seen a post from some dude (can't find it anymore, ugh!) who claimed he got 7 hours of SOT with 100% screen brightness, while playing backgammon and streaming Spotify on low 4G signal. Now that I think of it, he must have been joking. Even though the discussion seemed very serious. :eek:

Besides, I've seen others reaching 6 hours... without dark themes & such.

My device can't make it through the day. Not if I'm away for 6+ hours without my external battery on me... but that's why I got the Xiaomi Mi Pro, eh :D

---------- Post added at 16:30 ---------- Previous post was at 16:29 ----------

What is "this", exactly? You design your kernel in such a way that when you're charging overnight, all dangers are removed or...? :D
[Nexus 6 Android Development] RenderBroken:
It means that I try to make my kernel perform better than stock. For me this means having comparable or better performance yet better battery efficiency.
[Nexus 6 Android Development] Root Wizard:
Has there been a fix to the usb otg freeze and reboot? I am experiencing this same issue. I can post a log or kmesg if needed to help diagnose. On Bliss ROM 6.4 from a totally clean flash and on f2fs for my cache and data partition. Using OpenGapps Pico(if this has anything to do with it, maybe a missing gapp doesnt let usb mount properly). Otherwise, I love the kernel, great SoT and performance, plus its one of the few kernels that actually work and support f2fs. Thanks!
[Nexus 6 Android Development] RenderBroken:
Sorry for the late reply. Been busy like always. Been spoiled with using G+. I have to remind myself to check here more often!

Yea, some logs would be great. Most likely, the log fro pstore would help better since it is the equivalent of last_kmsg on 3.40.x devices. It is located here:

/sys/fs/pstore/console-ramoops

This will have the info stored before rebooting. Thanks for the assistance!
[Nexus 6 Android Development] Root Wizard:
Aw man! I just moved over a few hours before your reply to xosp and EX kernel! Only if I had waited a few more hours. So sorry!
[Nexus 6 Android Development] RenderBroken:
No sweat! You will be back! ;)

Naw, EX is solid. Flar knows what he is doing.
[Nexus 6 Android Development] Root Wizard:
I just might be back once ext4 gets toooo obsolete for and slow for me xD. And all you devs here on xda know what youre doing! Keep it up.
[Nexus 6 Android Development] BigM69:
Bump...

---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------

What is the Render UKM?

I am on CM 13 and I have Render Kernel R4 as well as synapse.
[Nexus 6 Android Development] RenderBroken:
I agree! WTH Moto? Nothing like working in a meeting to have my Silent phone vibrate on the desk louder than my normal ringtone is!
[Nexus 6 Android Development] danmaman:
Hihihi :D

Yeah that's true
[Nexus 6 Android Development] Formhault:
Also an ex-G2 user here. Nexus master race :)

---------- Post added at 01:04 AM ---------- Previous post was at 01:03 AM ----------

Be aware that Kernel Adiutor has troubles setting custom vibration intensity on boot. The latest update broke that...

---------- Post added at 01:04 AM ---------- Previous post was at 01:04 AM ----------

So everybody's N6 vibrating motor is loud af?
[Nexus 6 Android Development] cujo6801:
Render Kernel/Westwood/Deadline/Interactive/Vibration 50%/Everything else is stock...

Running very smooth/On latest Benzo ROM....

Thanks....
[Nexus 6 Android Development] OptimaPrime:
Yes, the shamu vibration gives my wife vibrator a run for it's money....
[Nexus 6 Android Development] DonQuixote77:
I had to double check that I didn't accidentally wander back into the G2 forum �� [MENTION=5438598]RenderBroken[/MENTION] welcome!

Had a great experience with your kernel on my old G2, looking forward to taking this baby of for a spin. Cheers!
[Nexus 6 Android Development] DespairFactor:
[MENTION=5438598]RenderBroken[/MENTION] you finally got a thread going, glad you could join us
[Nexus 6 Android Development] RenderBroken:
Thanks bro. Only took me like 3 weeks to do so. lol

What a fantastic welcome guys!
[Nexus 6 Android Development] danmaman:
No Problem Mate

you're always welcome....

one question

the first pic is your conservative...the 2nd in the most other kernels

did you modified the governor?or is it an older version of conservative?

thanks in advance

cheers
[Nexus 6 Android Development] RenderBroken:
It is the stock version of conservative. Meaning I had not touched it in this source yet.
[Nexus 6 Android Development] danmaman:
OK it makes sense

Maybe we can get the newer version in an upcoming update? ;)