yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] crzycrkr:
So glad I decided to try this kernel. Flashed 17 two days ago with Chroma 4/25. I run DPI at 420. This is the first kernel I've tried that gives me literally no screen tearing at all. I'm afraid to flash anything else now, lol
[Nexus 6  Original Android Development] purian23:
That's cool, we invite you to stay lol
[Nexus 6  Original Android Development] slick4mitch:
I too love Zen17, awesome kernel! Keep up the great work!
[Nexus 6  Original Android Development] crzycrkr:
I mean I'm even afraid to flash updates, lol
[Nexus 6  Original Android Development] Byrd San:
??? I'm in the same boat as you. I just flashed another kernel and couldn't even stay on it for 10 minutes cuz of the loss of smoothness. I think this is the kernel for me from now on. Great work devs!
[Nexus 6  Original Android Development] warfenix:
Anyone here using f2fs? If so do you think its worth it?
[Nexus 6  Original Android Development] Lazy79:
Here. Not sure. In general, yes, for /cache and perhaps /data but I never compared it to ext4 on the phone. From the feeling, no noticeable difference. However, I'm using f2fs on my desktop and so.. well, why not. In general, should be better (minimal better) but is the stuff with recovery and so on worth it? No, don't think so. I'm waiting for tux3 (just a stupid joke)
[Nexus 6  Original Android Development] Megaflop666:
If you're getting the screen tears, half the screen freezes or blanks and the other half keeps working; I HIGHLY recommend you get with your carrier to get your phone replaced or repaired. The screen tearing will eventually follow you to every kernel, every rom and it will get worse. It's a hardware defect that Motorola has already acknowledged and you can get it fixed for free.
[Nexus 6  Original Android Development] crzycrkr:
Link? Seems many have it and I haven't read that, although I know some have gotten replacements. I believe I had read Franco said it was a display or graphics driver problem. I was only getting running non-stock DPI with custom kernels. Non-stock DPI on stock kernel led to no problems at all
[Nexus 6  Original Android Development] numerouknow:
i am still on zen17 and loving the performance and battery life.

i am facing an issue with (haptic) dt2w.

i get random vibrations while i am on a call. its really annoying.

i can confirm that i don't have any notification vibrations enabled.

i am pretty sure this happens due to the (haptic) dt2w option that i am using.

i never had this issue while i was on lk but again lk has an option to use stock dt2w (no haptic feedback) and thats the one i used.

now i've tried synapse, kernel auditor, francokernel updater and none of them have stock dt2w option. on all 3 apps dt2w works with haptic feedback by default and there's no way i can disable this vibration.

synapse and kernel auditor have an option to adjust vibration intensity but i believe that would affect the overall device meaning alarm vibration, etc.

its strange that no one else has posted about this issue. which makes me think that i might be missing a point here/doing something stupid.

although this is not directly related to the kernel i am posting here hoping someone might suggest an alternative method.

also is there something you can do to support/implement stock dt2w in a way that its enabled by default without having to use another app to enable it.

regardless of whether or not i get a solution to my dt2w issue, i am here to stay with zen. ;)

thanks for your time and effort. much appreciated.
[Nexus 6  Original Android Development] Megaflop666:
I don't have a direct link and don't have time to search at the moment but you can Google nexus 6 split screen issue and you will find lots of links. I had to get mine fixed, long story, because of the screen tears. My new phone has been tear free since I got it. On any rom and any kernel. I purposely tried to get it to do it when I got this particular phone because it took me 6 phones to get one that worked right.
[Nexus 6  Original Android Development] bbedward:
Hi, I don't know what apps control this specific vibration but it can be disabled with the official wake gesture app:

http://xdaforums.com/android/apps-games/app-wake-gestures-t3030399

Alternatively you can enable it with this method:

http://xdaforums.com/nexus-6/development/compiled-power-shamu-to-enable-double-t2971463

I know there's a simple file you can write to simply enable the stock dt2w function, but I'm not sure where this file is located exactly. I'd think any apps that allowed this before would allow it here but I'm not sure :)
[Nexus 6  Original Android Development] crzycrkr:
I have searched. Haven't seen anything about Motorola acknowledging it as a hardware other than them replacing a few phones. That's common for anything they can't fix over the phone.

Don't get me wrong, I'm not saying you're wrong. Very well could be a hardware issue. I'm just more inclined to believe what some of the devs have said about it being a driver issue. Could be bad interaction with a minor hardware variance on some phones. The fact that certain ROMs and kernels won't do it at all for me leads me to lean that way.

I do have Moto Care, so if it becomes an issue long term, or with every ROM and kernel, I'll send it in
[Nexus 6  Original Android Development] funcrusher:
I've noticed the same thing. I always used stock dt2w on lk as well.
[Nexus 6  Original Android Development] Xileforce:
I'm almost positive I remember reading Franco say it was not a custom kernel issue because even he got it on stock kernel as well as his own kernel. I myself have never gotten it on any kernel :/
[Nexus 6  Original Android Development] funcrusher:
I actually tried the 'Nexus 6 Double Tap to Wake' app, but it enables the same haptic dt2w.

Fyi
[Nexus 6  Original Android Development] Xileforce:
Have you changed ROMs since switching from lk? Because some ROMs implement googles DT2W which is ROM side not kernel side. AFAIK lk uses flars wake gestures he just modified them a bit for lk and lkconfig.
[Nexus 6  Original Android Development] funcrusher:
Nah, I'm on stock all day every day. :)

He does have flar's gestures, but also the Google version of dt2w.
[Nexus 6  Original Android Development] crzycrkr:
He did say it's not a custom kernel thing. I believe he said it was a poorly developed graphics or display driver.

No matter what I do I don't get it with the stock kernel. Ran it for a month with different DPI with no problem. Franco was horrible with tearing for me. Hydra minimized it. I have had a single one with Zen
[Nexus 6  Original Android Development] bbedward:
I will disable haptic by default next :)
[Nexus 6  Original Android Development] Megaflop666:
Cool. I tried looking real quick but couldn't find the link again. I took mine up to tmo and they knew about the defect and replaced it. My problem was they kept sending me refurbs that had the same defect. I finally fought hard enough that they gave me a brand new phone and haven't had any problems since thankfully.

It started off with me as only a couple ROMs or kernels doing it. It eventually followed me to every ROM and kernel including stock and was happening a few times an hour. It was bad.
[Nexus 6  Original Android Development] Xileforce:
Good luck on ur presentation! My cat wishes you luck! Since loading zen kernel onto my cat it deep sleeps even better than before!
[Nexus 6  Original Android Development] resynx:
Zen19 test, if I try to dt2w the screen will stay off and the phone immediately starts vibrating nonstop for a few seconds and then reboots.

console-ramoops-0: http://pastiebin.com/55428d5fcf6f0

dmesg-ramoops-0: http://pastiebin.com/55428dc6586c6

console-ramoops-0: http://pastiebin.com/55428e0207e81

dmesg-ramoops-0: http://pastiebin.com/55428e2af1590
[Nexus 6  Original Android Development] bbedward:
OK I will push a new test a little later.
[Nexus 6  Original Android Development] Xileforce:
Is there a log created when the phone fails to boot? I've always wondered this. Like stuck on google screen or even gets to boot animation but loops.
[Nexus 6  Original Android Development] bbedward:
If it gets to the boot animation it may have written changes to the file system somewhere. Maybe pstore. sometimes at boot animation you can get adb debugging on too.

Before the boot animation I'm not sure. A typical Linux system will show a panic or whatever before file systems mount and the standard init process starts, but android is different I've never seen anything about getting pre init logs.
[Nexus 6  Original Android Development] niko2931:
Hey [MENTION=2632235]bbedward[/MENTION] if you dont mind me asking, what rom are you using together with your kernel? :good:
[Nexus 6  Original Android Development] bbedward:
I don't really like to recommend ROMs (although I pop by some ROM threads with feedback now and again) because I don't want people to think one is worse than another or better than another. It's really whatever you prefer the most :) I know how much of a pita it is to build aosp (requires long build time, lots of hard drive space, etc.) so I commend all the guys who build aosp :p

I switch around now and again to different ones, but most of the time I find myself on something near stock or stock aosp. I only like basic modifications, like circle battery, reboot options, lock screen weather, stock theme, etc.

But when it comes to a ROM they all will offer slightly (or sometimes wildly) different things from one another. It's best for people to pick and choose what they like best :) All I do is improve the kernel space :p
[Nexus 6  Original Android Development] Xileforce:
:( that definitely makes it hard to troubleshoot these bfs issues lol
[Nexus 6  Original Android Development] bbedward:
The vrq stuff just isn't stable on many configurations from what I've seen, one of those configurations is the N6 one :p maybe in time
[Nexus 6  Original Android Development] Xileforce:
:( thanks for crushing my dreams
[Nexus 6  Original Android Development] bbedward:
Compared to test1 reverts all wake gesture changes, but disabled haptic feedback by default.

3.10-zen19 "Show Stopper"

Changes:

Revert to MPDecision by default. I don't have the time to fully implement a replacement ATM

BFS: Sync try_to_wakeup_* and ttwu_*

BFS: Replace resched_task with resched_curr

BFS: add soft_affined flag

BFS: sync context_switch and finish_task_switch

F2FS: Numerous upstream updates

MSM/KGSL: CAF Fixes/Updates

MSM/MDSS: CAF Fixes/Updates

MSM/mmc: CAF Fixes/Updates

MSM/vidc: CAF Fixes/Updates

MSM/QoS: CAF Fixes/Updates

Misc general upstream updates

Wake Gestures: Disable haptic by default

3.10-zen19 Recovery Zip Download

3.10-zen19 boot.img (install via fastboot/twrp IMG) Download

3.10-zen19 ZenyKernel Zip (Use on top of ROM dirty flash if issues with the above two)
[Nexus 6  Original Android Development] shopealope:
I have a question that's probably stupid, don't hate me. With 5.1, wasn't MPdecision disabled? Just curious because I don't know whether to toggle it on or off in trickster.
[Nexus 6  Original Android Development] bbedward:
Partly. It's functionality related to hot plugging was removed in 5.1. Some other functions remain though like input boosting.
[Nexus 6  Original Android Development] jdavis7882:
Aww I loved haptic feedback on double tap to wake :(
[Nexus 6  Original Android Development] purian23:
Most kernel apps should be able to get that back online for you pretty easily.
[Nexus 6  Original Android Development] bbedward:
"echo 20 > /sys/android_touch/vib_strength" will set what it was before.

Also most apps supporting the gestures should work for it :)
[Nexus 6  Original Android Development] zeroxg4:
I follow the instructions in your "[HOW-TO] Convert to F2FS on Nexus 6 (Any Rom)" thread (specifically step 11) on every new ROM flash. My steps usually include flashing the ROM, Gapps, SuperSU, your newest AnyKernel version, then doing Step 11 (copying the tools) while still in recovery and rebooting.

My question: Since I installed a ROM (Chroma) and flashed your anykernel zen18, you've updated with zen19 and I'd be interested in flashing it :p Would I still need to copy the tools again (Step 11)?
[Nexus 6  Original Android Development] bbedward:
Nope only when you reflashing a ROM you do :)
[Nexus 6  Original Android Development] shopealope:
In that case, I'll leave it enabled. Thanks for the explanation! Not to mention, the awesome kernel.
[Nexus 6  Original Android Development] info[]box1:
Well put. Prefer the same also. 5.1.x stock is so good in it normal state, you got to have a real good reason to venture off in to the wild.
[Nexus 6  Original Android Development] jiv101:
Benzo I have to say is doing a fine job though..
[Nexus 6  Original Android Development] Custodian:
Does zen use Franco conservative?
[Nexus 6  Original Android Development] bbedward:
Nah I haven't really touched any governors except for interactive.

I could investigate some conservative and on demand adjustments for next release though.
[Nexus 6  Original Android Development] Custodian:
OK. Was just wondering cause conservative runs smoother than interactive for me....using your kernel
[Nexus 6  Original Android Development] bbedward:
I think interactive is less aggressive by default :)
[Nexus 6  Original Android Development] jdavis7882:
That did it thanks!
[Nexus 6  Original Android Development] Xileforce:
Lol how ironic. Interactive is less aggressive than conservative.
[Nexus 6  Original Android Development] bbedward:
Conservative is based on ondemand and is probably more conservative than ondemand :p, but interactive is a google product
[Nexus 6  Original Android Development] urrgevo:
[MENTION=2632235]bbedward[/MENTION], on zen 19 can mpdecision be turned off and input boost tweaked like in zen 18? I'm still trying to figure out which setup works better for me. Thanks
[Nexus 6  Original Android Development] bbedward:
Yea you can do the same.

stop mpdecision

/sys/modules/cpu-boost/parameters

I think those are the relevant paths but I know kernel auditor and probably others allow those to be changed.
[Nexus 6  Original Android Development] grayskul:
A friend and I both had the same issue and had to get replacements. Was told it was a hardware failure
[Nexus 6  Original Android Development] crzycrkr:
I don't doubt Google and Motorola support has addressed it as such. Easiest way for the phone jockies to handle it. I just find it odd the amount of people that have it happening, but only with certain ROMs or kernels. I'm more inclined to believe the idea supposedly floated by devs here that its driver related

If I get to the point I get it on every ROM and kernel combination I try, then I will definitely be buying into it being hardware. As if right now I seem to have two combinations that have never once given me a screen tear
[Nexus 6  Original Android Development] bbedward:
Software can exaggerate hardware issues ;)

I ha e pulled in numerous GPU driver and panel driver updates so maybe some of those have helped :)

Likewise some hardware faults can be covered up with software
[Nexus 6  Original Android Development] Xileforce:
I'm inclined to support this thinking. Because if there wasn't any hardware aspect to it then it wouldn't make sense for some people to even get it on stock while others such as myself don't get it no matter what. Software alone typically doesn't produce those kinds of inconsistencies.
[Nexus 6  Original Android Development] mimsiroll:
Op, have you tried franco kernels r28? The consistency of the kernel's deep sleep is outstanding how bout checking it out for some implements, i think Franco wouldn't mind it. If it's for all for development.
[Nexus 6  Original Android Development] italia0101:
This was overnight on zen19, deep sleep pretty good for me
[Nexus 6  Original Android Development] bbedward:
I think deep sleep is good on zen. What kind of issue do you have with it?

The only real concern is you don't want the phone to wake itself out of deep sleep if it isn't necessary, so keep it to a minimum. I think zen doesn't have a problem with that.
[Nexus 6  Original Android Development] numerouknow:
i cant thank you enough. wasn't expecting this at all.

i am hoping my problem will be solved with this. will flash and report back.

---------- Post added at 12:42 PM ---------- Previous post was at 12:38 PM ----------

thanks so much for confirming what seemed like an issue no one else had.
[Nexus 6  Original Android Development] Xileforce:
Zen literally sleeps better than my cat...
[Nexus 6  Original Android Development] crzycrkr:
I definitely think there's a hardware aspect involved, just not sure it's an actual failure or defect per se. I'm just thinking it could be no different than how some drivers for computer hardware don't seem to play nice with certain combinations of hardware. But I could be completely wrong too, lol. Time will tell
[Nexus 6  Original Android Development] bbedward:
Comes natural
[Nexus 6  Original Android Development] Xileforce:
My cat has started exhibiting this sort of erratic deep sleep behavior too and its simply unacceptable! Definitely uninstalling and trying Franco for its more consistent sleep.
[Nexus 6  Original Android Development] dwang:
Great job on zen19. My phone has never been smoother and battery life has been excellent.
[Nexus 6  Original Android Development] bbedward:
Yea I think 19 is doing great.

I just stressed my phone for the past 4-5 hours non stop running to my web service through my app to control my senior design project.

60% battery still :laugh:
[Nexus 6  Original Android Development] Xileforce:
So, what would happen if I only pulled a few of the vrq commits? Like if I only did the very first one. Would it even boot?
[Nexus 6  Original Android Development] bbedward:
Yea probably, I boot tested a bit. But stability I am not sure
[Nexus 6  Original Android Development] Xileforce:
Where is erryone?
[Nexus 6  Original Android Development] bbedward:
No issues to report ofc. 1 with an issue is louder than 19 with none
[Nexus 6  Original Android Development] numerouknow:
zen19 is running perfectly.

all issues with random vibrations during call are gone.

thanks so much for your time and effort. much appreciated.
[Nexus 6  Original Android Development] mimsiroll:
When i turned off the mp decision it became dual core. Why? Switched from fk updater to kernel aduitor.
[Nexus 6  Original Android Development] pantmunu:
What the hell is vrq ?? ??
[Nexus 6  Original Android Development] bbedward:
Not sure why this happens, but you can manually turn cores back on in kAuditor

Variable runqueue locking for BFS. Basically it's a solution that's supposed to reduce locking contention on BFS.
[Nexus 6  Original Android Development] dwang:
experiencing multiple reboots in the last 12 hours with zen19 using chroma. I've attached some logs.
[Nexus 6  Original Android Development] Xileforce:
In laymans terms: It improves multithreaded performance :)

Someone just sent me a log like this too and I don't see the actual crash in the console ramoops, interested to see what bbedward says. I'm a noob still so I probably am missing something.
[Nexus 6  Original Android Development] dwang:
The crashes happened when the screen was off and I was trying to turn it on with dt2w. The screen doesn't turn on, the power button doesn't turn on the screen eiether, and it eventually reboots.
[Nexus 6  Original Android Development] Xileforce:
OK that explains why it reports a key press. So its a SOD. Are you undervolted? Sometimes that can lead to a crash.
[Nexus 6  Original Android Development] dwang:
nope, not undervolted. Stock settings.

The only thing I changed was I enabled haptic feedback with dt2w using wake gestures app.
[Nexus 6  Original Android Development] bbedward:
There is a panic in the dmesg-ramoops but it's at the watchdog notifier so not sure if it's relevant I'll have to look into it more.

How consistently does it happen? On 19 or 19_test1?
[Nexus 6  Original Android Development] dwang:
very consistent. I've experienced it 3 times already. I'm on zen19 from the front page. Always the same thing, dt2w doesn't turn the screen on and it reboots.

wondering if its related to the haptic feedback. I can load zen19 back and disable haptic feedback and see if it reboots anymore

I'm back to zen18 for now.
[Nexus 6  Original Android Development] bbedward:
Yea try to load it up and disable haptic feedback :)
[Nexus 6  Original Android Development] lexus91:
I'm also on chroma with zen 19. Probably its the haptic feedback. Haven't expirienced any random reboot so far.. Been using it since the first day zen 19 released
[Nexus 6  Original Android Development] kingston73:
I apologize if this has been asked before, I couldn't find anything about it- if I am on this kernel and want to flash another can I just flash over or do I need to refashion the rom frat before trying another kernel? And same in reverse, if I'm on another kernel and come back to this?
[Nexus 6  Original Android Development] lexus91:
Cmiiw. But for me i just flash over between kernel. Cleaning dalvik before and after flashing them. Never had any problem till now. And yes you can always come back to this easily.
[Nexus 6  Original Android Development] pantmunu:
Interesting. Although I don't understand what u are saying lol but interesting. Thanks for you awesomeness man. :)
[Nexus 6  Original Android Development] bbedward:
I don't think lock contention is an issue on BFS to begin with, except its speculated at 16+ CPUs the global lock may cause contention issues.

Of course any time you can make a lockless path through code versus a locked/synchronized one it's a good thing. With VRQ, some routines (like idle scheduling) are able to be done pretty much free of any locking :)

The initial VRQ patches actually performed worse than BFS with the global (GRQ) locks. Because all it was doing was creating more locks. They weren't global but things were locked a lot more, creating more contention than just using the global lock.

Newer versions of the patch optimizes several routines to eliminate or reduce locking though, which has proved better for performance
[Nexus 6  Original Android Development] urrgevo:
I understood none of this^^^, but I understand this

Right about at 36 hours, minimal use but it's my normal level of use when I'm working. Kudos for a great kernel, best I've run since the og evo
[Nexus 6  Original Android Development] bbedward:
Because zen was on the og evo too amiright ;)

Thanks for the feedback :)

BTW no idea how you get that battery even with zen. Ridiculous.
[Nexus 6  Original Android Development] numerouknow:
i am using the exactly same rom-kernel combo. chroma + zen19.

never had any reboot issues.

but i haven't changed the haptic feedback either. i left it disabled.
[Nexus 6  Original Android Development] dawiseguy77:
I keep getting bad gateway when trying to downloading showstopper
[Nexus 6  Original Android Development] Manson79:
Hi,

Best kernel I tried (for me) with Chroma rom!

The battery life is perfect for my use but the most important for me is the use in general UI... and it's awesome. For example this is the only kernel without any waiting period when I press the multitask button and if I press the clear all button I go back to the homescreen immediately (not the case with other kernels). No lags or stutters... perfect kernel!

I don't undervolt or overclock and I'm running Ondemand governor (tweaked a bit for better performance and set BFS rr_interval to 4) with Deadline i/o scheduler and some VM tweaks. Benchs are great too, Antutu gives me good scores... I'm happy :D

Thanks [MENTION=2632235]bbedward[/MENTION] for your work ;)
[Nexus 6  Original Android Development] iStayHigh:
My battery stats so far on zen 19 "The Show Shopper"

P.S my phone really loves this kernel

Zen'd N6
[Nexus 6  Original Android Development] SignalX:
wanna try this kernel on my new nexus6 running CM12.1

one question, is there any app for controlling kernel settings?
[Nexus 6  Original Android Development] bbedward:
Looks like andro file host is backup

I like kernel auditor because its nice and open source, but any of the appa should work for you :)