yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] :
I thought that the driver got the information from the touch driver directly to get the reported touches and did its math based on that. When it detected the right values/checks, it sent the power key press.

Shouldn't that be at a lower level that apps and such? I could see if it was an issue in the gesture interface, since that relies on an app handling the report.

Unless I'm not understanding how it works. Our do you mean, like the driver is trying to turn the screen off and something else is trying to hold it awake/turn it back on?

Also, same driver and works fine for me as well.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] flar2:
The sweep2sleep driver (incorporated in the wake_gestures driver as you know) gets the input events from the linux input subsystem not directly from the touch driver. Android also gets the input events from the linux input subsystem, they basically see the same thing. There could definitely be race conditions if an app or a launcher is trying to do the same thing.

I'm pretty sure that people have run into userspace stuff interfering with sweep2sleep before. Sometimes I think about implementing it in userspace rather than the kernel, for the same reasons that I give whenever I decline to add doubletap2sleep in the kernel.

But for now it works good for me. I use sweep2sleep almost every time I turn off my screen.
[Nexus 6  Original Android Development] :
Makes sense. I didnt realize that the Hal (I'm guessing it's how you mean that the rom gets it) could intercept the calls to prevent other parts of the kernel from getting them. I'd always figured that out was kinda like abstraction layers where kernel > Hal > userspace . Where things could interfere left to right but not let to right.

Not that I'm trying to argue, you know way more about it than I do. But, xda is all about trying to learn and helping others learn right? :)

Thanks for the info!

Also, i think that I had tried adding dt2s into the driver at one point. The problem that I ran into was that it prevented android from working with double taps as the screen would always turn off. Of course when the screen came back on the double tap action had executed. Unfortunately... There's no way I could think of for the driver to know what's on the screen to decide whether or not to turn off. I guess it could be done though be reporting a double tap like a wake gesture (sorta) and have an app check the running apps to make sure the foreground is the home screen... But even then, that seems like a round about way for something that should just be in the framework.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] flar2:
doubletap2sleep can be done, you can work around that by checking if the screen is on or off. I added it to one of my kernels a long time ago but quickly removed it. The problem is the kernel is not aware of the screen content, so if you turn to landscape, doubletapping the side scroll thing would activate it: Or another example, the kernel can't tell if you're on the lockscreen or not, or what's showing on your homescreen.
[Nexus 6  Original Android Development] mwebb34:
I'm on VRToxin 6.0.1. If I install this Kernel will I have any trouble out of xposed or any modules that I have installed? Thanks!
[Nexus 6  Original Android Development] nathanchance:
You shouldn't. Just make a backup if you have any doubts.
[Nexus 6  Original Android Development] mwebb34:
Ok... thanks bud

---------- Post added at 06:22 PM ---------- Previous post was at 05:47 PM ----------

I like this kernel, just wish I could set the min lower than 300000 and would be even better to be able to have a screen off freq setting. Hells core kernel does all that, but can't run it with xposed...well I can but the modules that I use on VRToxin ROM doesn't get along with HC. This kernel will be fine with me. Gots ta have my cake n eat it too?
[Nexus 6  Original Android Development] Lancez:
Cataclysm thread is locked, any ideas?
[Nexus 6  Original Android Development] nathanchance:
I recall someone saying it is placebo that having the CPU run at lower than 300MHz helps battery.

Any ideas about what? Like what happened?
[Nexus 6  Original Android Development] Lancez:
Yes
[Nexus 6  Original Android Development] mwebb34:
I got really good battery life when I ran under 300mhz
[Nexus 6  Original Android Development] nathanchance:
I'll keep this short and sweet, you can PM me if you want. A developer had the Cataclysm threads moved from Original to Android Development because without source, atl4ntis couldn't prove originality. He made a post about it prompting some debate between that other dev and the users. Then a mod came in, cleaned the thread then a few minutes later closed all the threads. Then atl4ntis sent out a Pushbullet notification talking about him ending Cataclysm indefinitely. I'll leave it at that, anyone is welcome to PM me if you want more info, I don't want to derail the thread.
[Nexus 6  Original Android Development] Lancez:
Thanks for the info. My job kept me busy for the last few days, so didn't time to catch up.
[Nexus 6  Original Android Development] :
When Neo locked the thread, he said no more discussion on it. It's probably best to exclain it through pm when people ask, to avoid the wrath of the mods.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] flar2:
Update!!!

By default, all cores are kept online during suspend. This fixes potential instability with demand-based governors (ondemand, elementalx and conservative). One place where this was showing up reliably was trying to enable a wake gesture during suspend.

This does NOT make any difference in battery life, I've tested thoroughly. There is no point in taking cores offline during suspend, there is no gain and it can cause instability.

Download:

ElementalX-N6-3.09

Changes:

-add color profile option (@suku_patel_22)

-keep all cores online during suspend

-clean up sound

-updates for CFQ and TCP Cubic

-update installer
[Nexus 6  Original Android Development] nathanchance:
I just flashed 3.09 and my settings don't stick when I set them in Aroma. I tried twice. My ROM is pre-rooted with SuperSU 2.52. Is this due to SELinux being enforcing? I can set them in EXKM without problems, I'm just curious what could be causing that.
[Nexus 6  Original Android Development] flar2:
All my aroma settings stick. The installer is the same as on all my kernels, no change except adding the color options.
[Nexus 6  Original Android Development] nathanchance:
Huh it is weird since my settings usually don't stick after flashing them come to think of it and I have tried it on four different ROMs in the past. Not to much of an issue since I have the app and it must be a custom ROM thing since I know you use stock.
[Nexus 6  Original Android Development] Khizar:
I can confirm settings sticking but had to flash the kernel twice, didn't work the first time round. My rom also comes with supersu 2.52 and selinux is enforcing.
[Nexus 6  Original Android Development] flar2:
Still troubling if true. It gets harder and harder to deal with the fragmentation.
[Nexus 6  Original Android Development] nathanchance:
I tried it twice too. Let me do it one more time and see if that works.

---------- Post added at 10:36 PM ---------- Previous post was at 10:19 PM ----------

Alright so after more experimentation, here is what I have done:

Flashed 3.09 over default kernel with the auto flash of EXKM and within recovery manually, changes not saved.

Flashed 3.09 changed settings over 3.09 stock settings within recovery, changes not saved.

Changes: change I/O scheduler and read ahead, turn on sweep to wake in all directions, turn off sweep to sleep, turn on the key suspend option, and choose the deep rich profile. Everything else should be default. Don't know if that makes any difference or if it gives you anything to go off of but just thought I would throw it out there.
[Nexus 6  Original Android Development] flar2:
I just did a clean install of Pure Nexus, then flashed EX 3.09 and everything stuck.

There really shouldn't be any issue, these scripts have been working forever.
[Nexus 6  Original Android Development] nathanchance:
I am on Dirty Unicorns right now (trying out CMTE). I'm going to go back to Pure Nexus tonight when the new build gets released, I'll let you know how it goes. Is there a log that will help with this? Thank you very much for the update.
[Nexus 6  Original Android Development] Khizar:
I am on DU as well. I was on the stock DU kernel so just flashed elemental.

BTW like I reported a couple of days ago, I had this issue before on stock as well. Settings didn't stick so had to reflash kernel.

+1 on the log, is there anything I can post to help debug this?
[Nexus 6  Original Android Development] flar2:
Save the log at the end of the AROMA installer. Also check /data/local/tmp/elementalx.log after you boot into the system.
[Nexus 6  Original Android Development] nathanchance:
Included in the below zip is the AROMA log and the /data/local/tmp files (two of them). Fresh install of Pure Nexus, made the same changes as before and they did not stick after two installs (except for the color change which did).

EDIT: Lol tried a third time and it worked... Looking at the logs, it looks like it wasn't able to write to /data/data? Not sure but I do know that the settings are now working.
[Nexus 6  Original Android Development] joeyfong:
So recommend cfq or deadline? Thanks.
[Nexus 6  Original Android Development] gee2012:
Its best to try a few options, we all have different phone setups and needs and one size doesn`t fit all ;)
[Nexus 6  Original Android Development] magnamentis:
default is always the recommended setting, the rest is subject to personal preferences. i'm on deadline, was many months on fiops but

for the Nexus 6 i recommend explicitely deadline, it's sensitive to random reboots and not only because of this but i found a combo

with no RRs for months now. ( i overvolt slightly as well) i had a feeling that it depends a bit on the workload on boot ( congiguration/user space)
[Nexus 6  Original Android Development] derdjango:
May I know your reasons for overvolting and what it does? I undervolt by globally -50 to keep the CPU temp lower.
[Nexus 6  Original Android Development] :
Was the third time after another flash? Maybe it mounted data and left it mounted.

If you get bored, you could always delete the config from /data, reboot to recovery, Mount data, then flash and see if it works the first time.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] nathanchance:
It was ROM + GApps, flash EX, reboot, flash EX, reboot, then flash EX, and reboot. I'll have to try that next time I am in TWRP.
[Nexus 6  Original Android Development] flar2:
/data/data is the problem. It should be there, that's where all your apps are stored. Are you using twrp?

Or perhaps it's not there on a clean install before booting into the system?
[Nexus 6  Original Android Development] nathanchance:
Yeah, latest version of TWRP. That is what I am thinking since I always flash EX right after ROM + GApps. Shouldn't TWRP create that folder if it doesn't exist though?
[Nexus 6  Original Android Development] munkypoo7:
Just throwing out my experience as a data point and such.

Was on 3.08 with Bliss, had a specific color corrected setup, permissive (not enforcing), no dt2w, deadline, 512, gov: elementalx, 30% vibration strength etc. Flashed to 3.09 via Manager App (which is super sexy btw) as Express all settings stuck flawlessly. Super smooth upgrade.

Thanks flar2! :)
[Nexus 6  Original Android Development] flar2:
No, I think I do it from a script. I just have to change the command to create missing directories and give it correct permissions.
[Nexus 6  Original Android Development] Mark376:
[MENTION=4684315]flar2[/MENTION]

2457600 frequency is missing in undervoltage table, as I undevolt the other freq, I assume that particular freq will use the default voltage

could you check it out?

Thanks
[Nexus 6  Original Android Development] no.one.writeme:
Hi to you all,

I was wondering about the wake gestures in ElementalX. On the nexus 5 it cause more battery usage. Is it the same on the nexus 6, ie, I just set Double Tap to wake when I flashed EX 3.09. Should I expect a decrease in battery time?

Thank you for your time,

Best regards.
[Nexus 6  Original Android Development] Khizar:
I use all 5 gestures(DT2W, sweep left/right/up/down to wake) and have never noticed any battery drain due to them.
[Nexus 6  Original Android Development] magnamentis:
i mentioned it but no problem. i had random reboots which went away after changing to default governor and scheduler as well as overvolting by 10mA. also i mentioned that this may be due to specific loads my config puts on the device on boot with screen off. however reading through google search results it's a proven fact that the nexus 6 is more sensitive than the nexus 5 when it comes to electrical issues, there were many complaints of verious kinds and a bunch of RMAs due to similar or same issues. however my device is running stable now for months and you may have a better PSV/ASV level than mine and/or a configuration that puts less load on the device on boot. once i got rid of a problem i simply state under which condition i don't have issues and don't try to extrapolate each detail, hence it may well be that the governor and schedulers did the trick and voltages are just bywork but i won't make the effort to find out, what matters is that it works and with 4% battery drain in 14h idle i'm totally satisfied, not need for action on that side as well.
[Nexus 6  Original Android Development] rignfool:
Just for point of reference...

As electronics go...

They prefer more voltage than less... Your chip should run more efficiently with more voltage... Until you reach the point where you create too much heat
[Nexus 6  Original Android Development] ouyamaster:
Frustrated with elemental x and chroma rom for Nexus 6. Excellent features but can't fix random video pixelation. Happens on all apps and you tube 100% of the time. Returned to stock kernel. Video randomly becomes blocky and phone unusable until hybernate. Anyone have this issue and how did you fix it?
[Nexus 6  Original Android Development] nathanchance:
Never had this issue on stock, Chroma, Pure Nexus, Cataclysm or Dirty Unicorns, all with EX. Maybe try going into Settings > Developer Options and toggle Disable HW overlays.
[Nexus 6  Original Android Development] flar2:
This is nothing to do with the kernel
[Nexus 6  Original Android Development] Ferenczy68:
Without logs or at least a complete, step by step description of your setup process there is no way anyone can help you. Unless you're content with shots in the dark then please help us help you by providing more information. At the very least don't get frustrated and bash a ROM or kernel when you admittedly have no idea what the issue is...
[Nexus 6  Original Android Development] suku_patel_22:
Working fine here, as usual. No issues to report.

Thanks [MENTION=4684315]flar2[/MENTION] for including the color profiles.
[Nexus 6  Original Android Development] The Funky Pear:
Good day to you,fellow geeks :P [MENTION=4684315]flar2[/MENTION] i want to ask a question because

you

will probably know..

why there is no GPU overclock like lets say-to 700mHz?

i bought nexus 6 1 week ago,and i find that in some games, take for example "order and chaos 2:redemption", that it stutters A lot!

before nexus 6 i had the Galaxy s3 I9300 and a developer (genius) arter97,had gpu overclock and with that overclock games would not stutter at all

i bought this phone only,and i say only, for its size (media consumption) , snapdragon 805 and for gaming.

any suggestions??
[Nexus 6  Original Android Development] Gedablo666:
Im playing same game. I think its game problem. You will find later huge lags in some zones. Just bad optimized game nothing more. Same on my wifes z3.
[Nexus 6  Original Android Development] :
I believe on the n5, it's one of the devices that the wake gestures driver had to keep the screen on for the touch device to work. Kinda like a blacked out screen. This device just keeps the capacitive touch portion on (it is anyway).

More or less.

Which is why there isn't a difference in battery here but was on n5.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] ouyamaster:
I could try that and thanks. Sorry Flar2 it has everything to do with the Kernel. Went back to stock Kernel on chroma it magically disappeared. To boot I just flashed benzo Kernel and I'm liking it. So far no pixelation. It did take a while before it appeared on elemental x.
[Nexus 6  Original Android Development] daihard:
On Chroma 2016-01-18 and ElementalX 3.09. No video pixelation so far. I've had Chroma and ElementalX for a long time in the past as well and never run into issues like that. Just my personal experience.
[Nexus 6  Original Android Development] flar2:
No, really it doesn't have anything to do with the kernel. I know this for a fact.
[Nexus 6  Original Android Development] Ferenczy68:
Prove it, provide some logs...
[Nexus 6  Original Android Development] magnamentis:
unfortunately you're jumping to false conclusions. let's say a piece of dirt would make your car's engine and you would argue that it must be the cars fault and not the piece of dirt because you were throwing the same piece of dirt ( app or setup ) into a ship's diesel and the engine would still run. :) ;)

just imagine that some pieces of software (kernels) are high performance engines while others would stand for the ship's diesel. of course it's only an analogy but the question here is who/what is misbehaving, the kernel or the piece that does not behave within a specific (correct) range?

as we all know, any example lacks something but i still hope you get the point :) :cool:
[Nexus 6  Original Android Development] ouyamaster:
Heres an analogy certain medicines are good when taken by themselves. When they are taken with another medicine they can cause a deadly reaction in the body. They also have side effects over time. Some people never experience those side effects. Others are killed by them. All people are different and so are phones. I got pixelation after a while using both a fresh setup of elementalx and the express settings zip. I also fully wiped my phone and reinstalled everything and the video pixelation came back after a while. It stopped after I re dirty flashed the stock Kernel. I found benzo Kernel and flashed it and so far it hasn't come back. I was using the latest chroma rom and elemental x Kernel. I was and still am using nova launcher. I have the non carrier Google play edition of the Nexus 6. Even if I couldn't prove it was the Kernel it is suspect. Fact of the matter just like discontinuing a medicine because of side effects I have to watch the phone over this week. If fresh wiping the whole phone didn't take away the video pixelation problem and switching kernels did its a good chance it was the Kernel. I also tried clearing the caches multiple times in twrp but to no avail. If it works perfectly with this Kernel for now on I probably can car less since it has most of the same features. If someone else posts the same issue and it goes away by switching to another Kernel, I could rest my case.
[Nexus 6  Original Android Development] buzzwyzr:
Thank you [MENTION=4684315]flar2[/MENTION] and [MENTION=4144597]suku_patel_22[/MENTION] for providing color profiles in the aroma installer. I'm one of the weirdos who doesn't root and now I can enjoy vomer's IPS again. ?
[Nexus 6  Original Android Development] flar2:
There is no case. There is nothing in the kernel that will cause "pixellation." Not only that, this kernel is exactly the same as stock when it comes to graphics.

What you are seeing is known as a spurious relationship.
[Nexus 6  Original Android Development] jee'sgalaxy:
Do I have to be rooted in order to make the doubletap2wake and sweep2sleep to work? I did everything on the aroma, but the settings in the sys, did not work...
[Nexus 6  Original Android Development] nathanchance:
I believe so. You may try reinstalling but I think flar2 has said elsewhere those settings require root.
[Nexus 6  Original Android Development] Khizar:
You need root.
[Nexus 6  Original Android Development] jon.s.nelson:
Can anybody explain to me why I'm not seeeing vibration strength settings anywhere in kernel audiator? (I'm on 3.09)
[Nexus 6  Original Android Development] magnamentis:
no problem, you obviously are not willing to accept facts which don't meet your expectations, that's up to you, but it does not make sense to fill page after page with such opinionated posts. if you believe that it's the kernel's fault, which is your right (to believe what you want) you can simply use another piece of software which gives you (your configuration) a better experience and save us from the trial to be convinced of something we know for years (that's a point here looking at your stats) that it's not the case. you obviously did not understand my analogy and other than human bodies the hardware (body) in question, other than psv/asv level is the same and the software might differ while this is exactly what we try to tell you. the reason lays in your user space and you can easily find out what it is by following the linked procedure. it's work but those who really want to learn can do and the others will not be missed, especially not their righteous attitudes.

http://xdaforums.com/showpost.php?p=62192068&postcount=4059
[Nexus 6  Original Android Development] Khizar:
Really weird, flashed the kernel 5 times, the script is in data/data but settings don't stick.

I am on DU, was running it's stock kernel, used twrp to flash. Tried messing with the script permissions but no dice.

Attaching a log that I took the 5th time round. Data/local/tmp was empty.

Edit - Deleted the script and tried reflashing, script was there again but log was same and settings didn't stick.

Data/local/tmp still empty.

Edit 2 - Tried dirty flashing DU and elemental back to back, same deal.
[Nexus 6  Original Android Development] flar2:
There are no errors in the log and this installer works on every other ROM, and has worked for years. I suspect it's a bug in the ROM, or it changed something that it shouldn't have.
[Nexus 6  Original Android Development] RandomPooka:
Does this also apply to the sweep-to-wake functions, or are they implemented in a different manner than Google's DT2W?
[Nexus 6  Original Android Development] flar2:
Root is required to change sysfs settings
[Nexus 6  Original Android Development] RandomPooka:
Thank you. I'm going to take that as a yes :)
[Nexus 6  Original Android Development] buzzwyzr:
I set them in aroma but am not rooted and dt2w and sweep to sleep both work.

In order to change them via the app root is required.
[Nexus 6  Original Android Development] :
I'm not sure it's worth the effort....

Would it be worthwhile to make the installer add an init entry for like elementalx init.rc, and let people modify their sysfs values there via the script, and inject it into the ramdisk?

Seems like that would provide the people that don't want to root a way to use the features.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] flar2:
The settings could be handled completely in ramdisk, but then elementalx.conf can't work.

There are other solutions I'm looking at as well, but let's first see where Google goes with root and security stuff.
[Nexus 6  Original Android Development] :
even though there is a thanks button i wanted to post this and say THANK YOU to the OP and the team behind this fantastic kernel. been running it for the past few days and its smooth and stable as hell, love it.
[Nexus 6  Original Android Development] RandomPooka:
I suppose that I should have added whether I was trying to change them via the app or via the aroma installer