yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] p50kombi:
Just to confirm that using your motion launch gestures, the dot view case stops showing anything when using double tap or sweeps.

So back to stock for me...shame...
[One (M8) Original Android Development] flar2:
Until I release a fix, you can have full vibration automatically at boot by reinstalling with gesture vibration disabled.
[One (M8) Original Android Development] topjohnwu:
Well, actually it's not working after disabling gesture vibration. It seems that these two settings aren't conflicting.

Hope you can sort this out :), I will wait for the fix patiently. This isn't a serious issue though, I can run the command per boot.

Edit: And I figured out that 100% strength is the voltage set at 3100(or something near)
[One (M8) Original Android Development] flar2:
Yes, you're right, I think it's conflicting with the gboost setting in Aroma. gboost is set to 1 by default, and this is causing the reduced vibration flag to be set.
[One (M8) Original Android Development] Gamesoul Master:
Ahh, I get it. So it's 8-bit binary converted to decimal, meaning if I want all directions to work, I should change it to 15.

But as for something setting it that way... The first couple times I installed the kernel, sweep2wake was set at 15. The time that it was set to 1, I believe I played around with the touch controls settings in Trickster MOD, which I'm assuming is what changed it to 1 somehow (say, if Trickster is assuming the value is boolean like most of the others)?

Either way, if it's the ROM causing the issue, how would something like that be fixed? Are you thinking it's still related to the EasyAccessService?

And although this may be a bigger question than I'm thinking (and this is purely for my curiosity, so I apologize if it's too much to ask about), what change was made that would cause Motion Launch gestures to just stop working now as compared to them working just fine in v0.10 and earlier?

Edit: As expected, changing it to 15 immediately enabled all 4 directions of swiping to work. Thanks for that tip. Although I know it will eventually function as intended, I'm currently very happy with this setup. Finally I don't have to lift the phone to check it! :D
[One (M8) Original Android Development] flar2:
Here's a more detailed explanation of the new wake gesture settings that can help troubleshooting

Modes

There are three modes

Mode 1: Stock Motion Launch Gestures

For stock motion launch gestures, /sys/android_touch/wake_gestures, /sys/android_touch/sweep2wake and /sys/android_touch/doubletap2wake must all be set to 0. Enabling any of these overrides the stock gestures. Obviously Motion Launch Gestures must be enabled in the system settings.

Mode 2: Remove motion requirement

For this, you must set /sys/android_touch/wake_gestures to 1 and enable at least one gesture in /sys/android_touch/sweep2wake or /sys/android_touch/doubletap2wake and Motion Launch Gestures must be enabled in system settings. In this mode, when you sweep or doubletap, the appropriate input events are generated and acted upon the EasyAccessService (i.e., the system app that handles gesture actions).

Mode 3: Traditional S2W/DT2W

In this mode, wake gestures and actions are handled entirely by the kernel. The gestures will turn on the screen and that's it. For this, you must set /sys/android_touch/wake_gestures to 0 and enable at least one gesture in /sys/android_touch/sweep2wake or /sys/android_touch/doubletap2wake. It doesn't matter if Motion Launch Gestures is enabled or disabled in system settings, the gestures don't interact with it in this mode.

Options

For modes 2 and 3, there are several options.

Sweep2Wake

Gesture........Value

Sweep right......1

Sweep left........2

Sweep up.........4

Sweep down....8

Add up the values for each gesture you want to enable and put the total in /sys/android_touch/sweep2wake. For example, to enable all gestures, the value is 15 (1+2+4+8). To enable sweep right, sweep left and sweep up, the value is 7 (1+2+4)

DoubleTap2wake

Set /sys/android_touch/doubletap2wake to 1 to enable DT2W, and set to 0 to disable it.

Pocket Detection

Set /sys/android_touch/pocket_detect to 1 to enable pocket detection, and set to 0 to disable it. Pocket detection is experimental right now, I'd say it's about 90% functional, but there is an occasional bug where it either doesn't work or works too well.

Vibration Strength

Haptic feedback can be enabled for the wake gestures in /sys/android_touch/vib_strength. This setting takes a number between 0 and 60. Default is 20, which is the same vibration as the stock gestures. Setting this to 0 disables haptic feedback.
[One (M8) Original Android Development] Gamesoul Master:
Wow, thank you for taking the time to lay all that out. I really appreciate it :)

So going from that, and playing around some, it seems that as soon as wake_gestures is set to 1, that's when waking the phone stops working completely. Having it at 0 with pretty much any other settings as I set them (except sweep2wake at 0 of course) still allows sweeping/tapping to wake the phone, though no Motion Gestures to launch/do anything else.

Which, in the end, seems to lead exactly to what you first said, about EasyAccessService being the problem. Essentially, I have danced around to figure out exactly what you already knew... lol.
[One (M8) Original Android Development] flar2:
Good observation on the bit settings for sweep2wake ;)

I really don't know why the stock gestures would be affected. The code path is exactly as stock if all the gesture stuff is disabled. Enabling wake_gestures also should work fine, all it does is generate the same input events as the stock gestures, which the userspace service recognizes and acts upon. So far I've tested it on ARHD and Viper and the gestures work perfectly in all modes.

Did you try disabling and re-enabling Motion Launch Gestures in the system settings? That might be all that's needed.
[One (M8) Original Android Development] Gamesoul Master:
Yeah, tried that already with no effect. Also tried disabling and enabling each gesture through InsertCoin's options (wasn't expected anything, so that did nothing as expected).

If I go in and manually change all three to 0, stock gestures work fine. DoubleTap2Wake wouldn't let me manually change it (error saving), I had to change it in Trickster MOD, and I'm guessing Trickster was the reason setting it to stock seemed to do nothing, as it probably changed the dt2w file back to 1 upon boot.

So the good news is... Everything else works as expected when wake_gestures is set to 0. Vibration setting, sweep directions, dt2w, stock gestures, all of it. Only setting wake_gestures to 1 causes any problems.

EDIT: Also, not sure if this matters or not, but although setting wake_gestures to 1 seems to disable being able to wake the phone with sweeps or taps, hitting a volume key while holding the phone in landscape mode still wakes the phone and launches the camera app.
[One (M8) Original Android Development] psycho_somatic:
Hi, sorry to bother you.. just wondering if it's possible to fix the bluetooth audio with the kernel. Basically phone audio with bluetooth is very low and adjusting the volume in call doesn't work for some reason. Media audio works perfectly. I'm aware it's an issue with android 4.4.2

Thanks
[One (M8) Original Android Development] djcense:
How did you get this to work with AOSP lockscreen
[One (M8) Original Android Development] flar2:
How does the dot case work exactly?

Do you swipe and doubletap on the case cover? Is this how you get it to show the time and weather? Maybe I can try testing with magnets or something.

When you say back to stock, do you mean stock gestures or stock kernel? Because that should all be working if the custom gestures are disabled.
[One (M8) Original Android Development] flar2:
I doubt I can fix that. I basically never mess with bluetooth, it's a complicated mix of kernel and system libs, and HTC has its own unique implementation.
[One (M8) Original Android Development] style154:
I had no issues with Bluetooth when using stock with this kernel maybe it is a Rom issue? Maybe a lib got removed as flar just said they rely on
[One (M8) Original Android Development] p50kombi:
It works with tapping and/or swiping, depending on what you want to do on the front of the cover.

ou can answer calls etc and end calls.

works with .11 with stock gestures enabled...
[One (M8) Original Android Development] psycho_somatic:
nah, noticed straight away when I got the phone, it was fine with the Nexus 4

just tried the newly released AOKP rom also, same problem

---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------

okie dokie, it was worth a try. thanks for replying though, i've asked this question loads of times on other threads and your the first to respond :silly:
[One (M8) Original Android Development] shorty1483:
I've chosen AOSP lockscreen in Viper Tweaks App. Then flashed ElementalX Kernel with Option 3, native Ta2Wake and Swipe2Wake support. I have no swipe gestures working in sense manner, but Double Tap 2 Wake works well.
[One (M8) Original Android Development] michagol2:
Just an update on these settings - i posted screenshots with my most recent results - best battery life I've ever had on a phone.

[MENTION=4684315]flar2[/MENTION] you earned yourself a beer sir - 79T83810DS309754A
[One (M8) Original Android Development] flar2:
So it's detecting the swipe and doubletap without you actually touching the screen. I see a hover function in the source code, that must be what it's using. My gestures rely on touch coordinates, so not surprised they don't work.

How thick is the front cover and how big are the holes? Is there any skin contact with the screen?
[One (M8) Original Android Development] flar2:
HTC bluetooth stack is known to be flaky with specific hardware. I don't ever use bluetooth, but I've heard in other threads that some things work perfectly and others don't.
[One (M8) Original Android Development] TheMathMan:
Bluetooth is faultless with my Sony car stereo. It drops out with my JBL/Nokia Play Up speaker
[One (M8) Original Android Development] meleelord:
All good with 0.11, gesture controls without motion. Only thing I noticed is when in a call and I have the handset to my head the phone vibrates.
[One (M8) Original Android Development] flar2:
Thanks mate! Much appreciated

I'll have to double check that later. Is it registering button presses as well?
[One (M8) Original Android Development] Forsaked:
0.11, did i missed something?
[One (M8) Original Android Development] meleelord:
Didn't notice anything with the buttons, but I'll check when I'm next on a call.
[One (M8) Original Android Development] jreyno10:
Flar2 posted a beta a few pages back. 87 I think.

Sent from my M8
[One (M8) Original Android Development] GSLEON3:
[MENTION=4684315]flar2[/MENTION] - I thought I'd answer this, having the case as well...

EDIT: (Pics removed for video)

First, here is a video of the case in action:

[YOUTUBE]WGbGwFpFUN0[/YOUTUBE]

As you can see, the holes are small (about the tip of a ball point pen), no contact is made with the screen. There is a small magnetized are in the case flip cover that activates the DotView mode. It allows you to activate voice actions, answer calls, DT2W to see time & weather & also see notifications. It also allows you to answer or decline incoming phone calls by either swiping or but just placing the phone to your ear. The flip cover is about as thick as any other flip cover & is a soft touch tpu type of material.
[One (M8) Original Android Development] steve1996:
I've just measured my for view case, the flap is 2mm thick, the holes are 1mm in diameter, there's a thin layer of rubber in those holes so there's no contact between the finger and the screen. Only the holes where the flap is covering the speakers are empty.

When nothing is happening, just normal idle, when you double tap the case it shows the time and weather, and there are no other actions when idle. When you double tap again when it's on the clock and weather screen, the screen turns off and goes back to idle. If you don't double tap, it goes back to idle after 10 seconds. When there's a call, there's a big picture of receive call and decline call. Swipe up to answer and swipe down to decline. I think that's about it.
[One (M8) Original Android Development] DREWHAMM974:
Hey [MENTION=4684315]flar2[/MENTION] not asking for an ETA of any kind but can we be expecting a kernel for the aosp Roms that were just released?
[One (M8) Original Android Development] GSLEON3:
Hmmm... Never noticed that before, the holes not penetrating. Makes sense I guess from a pocket protection standpoint. Those holes would be big enough to let a fine piece of sand or whatever thru & could potentially scuff the screen.

I have also intermittently noticed that sometimes it will see me reaching over it & activate without any direct touch. This happened on .10 running viper 1.50, but hasn't since updating to Ex .11.
[One (M8) Original Android Development] p50kombi:
What he said ^^^^:)

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M8) Original Android Development] Johnny424:
I wont pretend to speak for flar..but that would be a ton of kernels to support for one device..sense,gpe,aosp,cm..that's quite a bit for one person's shoulders for one single device lol
[One (M8) Original Android Development] DREWHAMM974:
Very true, but I am consistently switching between elementalx and trinity on my Nexus 5 and although I like sense more than the other OEM skins my heart lies with AOSP. So truly hoping for an AOSP Rom on here as well. I can't run any of the new builds right now very long because the default kernel is so slow compared to this kernel and I truly enjoy a fluid system .
[One (M8) Original Android Development] flar2:
I just tested a makeshift cover case witht he wake gestures. It consisted of 10 pieces of white paper and a magnet.

Laying the paper over the screen, I then set the magnet down to turn off the screen. Double tapping on the paper indeed made the dot view show up. EDIT: also works with call answer/decline

If it can work through ten peices of paper, I see no reason why it shouldn't work with the dot view case.

I don't think the kernel would speed them up too much right now, those projects are under heavy development. They're more focused on getting things working than optimization.

I will most likely be sticking to Sense and GPE on this device.
[One (M8) Original Android Development] Savant:
Not bad at all.
[One (M8) Original Android Development] steve1996:
It would be nice if there's an option to disable volume button camera launch, I use boombass and every time I want to increase the volume the camera starts, which is very annoying.
[One (M8) Original Android Development] flar2:
I just installed InsertCoin and EX 0.11 and all custom gestures are working fine. The custom actions in kontrol also work. I really don't know why it's not working for you.
[One (M8) Original Android Development] Gamesoul Master:
Me and jlevy both. I'm assuming from what he said that he's using a newer version of InsertCoin than me. I'll be downloading the latest full ROM tonight... I'll dirty install that and 0.11 with a cache wipe and see if that does the trick. If not, I'll give a full wipe a shot just in case.

It's just weird that everything worked 100% when I was running 0.10. But if it works for you, it must be something on my end. Maybe before I try all that, I'll just do a good cache wipe first.

Any other thoughts about the situation before I continue with my plan? lol

EDIT: Cache wipes did nothing (except lower my vibration by 500 again despite not actually installing anything this time), so I suppose I'll be waiting until a little later and playing with the newest InsertCoin to see what happens.
[One (M8) Original Android Development] bkeaver:
Flar2, sent you a little something for all you do. I use your kernels exclusively on my N5, M7 and M8. Thank you!!!

Transaction id: 0XR3573784208214B. :)
[One (M8) Original Android Development] hdelvalle009:
Where is the version of this kernel for CM

HTC ONE M8 - GE 1.1 INTER-STOCK

ELEMENTAL-X 0.10 BETA KERNEL
[One (M8) Original Android Development] flar2:
Thanks!

I stick to Sense and GPE on HTC devices.

If it works with traditional s2w/dt2w, then the kernel part is working, your touchscreen is sensing touches and can register gestures. If wake_gestures=0, the gesture causes the kernel to send a power button press, if wake_gestures=1, the gesture sends a key press that is understood by HTC's Motion Launch gestures. It's as simple as that. If it doesn't work, it's because something in userspace (ie, ROM side) is failing to act on the input event.

I've installed three different ROMs and it works perfectly with all of them. I would suggest you do a full wipe and a clean install without doing a lot of tweaks.
[One (M8) Original Android Development] Gamesoul Master:
No worries. As I basically said, I'm not questioning your kernel. I figured it's something on my end, but I figured I'd ask in case it was something I could do besides a full wipe.

I apologize if I sounded like I was questioning your kernel. I've loved your kernels for a very long time, and I'm very happy with how they've enhanced my phones. I'll report back later tonight after installing the updated ROM and kernel with and without the full wipe.

And thank you again for all the time you've spent on this. Tomorrow I will be sending some additional appreciation your way for all the work you've done :)

And even more, I appreciate the patience you've shown me with explaining things. I'm the kind of person who strongly likes to know how things work, and you've been very patient with explaining things to me (and everybody else who's interesting in reading what you've said).
[One (M8) Original Android Development] flar2:
UPDATE!!

A minor update, the only kernel change is an update to the slimbus oc from poondog and zeroinfinity.

I've also fixed the installer issue where it was incorrectly reducing the vibration level.

Download:

ElementalX-m8-0.12-Sense

Changes:

-update slimbus oc (poondog/zeroinfinity)

-fix installer (incorrect vibration setting)

Here's a recap of the new wake gesture options:
[One (M8) Original Android Development] jlevy73:
I'll try with 0.12, but with 0.11 on IC Rom, I've checked all the settings and with motion detection disabled, swipes do not turn the screen on. It wants to, as in a swipe up gives me the vibration but the screen doesn't turn on. Only thing working is S2S. I'm sure it's all working, I just cannot get it to work.
[One (M8) Original Android Development] flar2:
The vibration means it's definitely working, an input event is being sent but the system is not responding to it. I wonder why no action is triggered, especially since it works on my installation of IC? Did you check the custom settings in Kontrol? And Motion Launch Gestures are definitely enabled in Settings? Another possibility: IC has a ton of options to remove apps and customize, maybe one of those options causes a problem. I went with mostly stock settings and didn't choose to remove many apps.
[One (M8) Original Android Development] Johnny424:
Kinda strange, I just flashed 12, selected the same as you (motion detection disabled) gestures still enabled via settings, I feel the vibration when swiping from different directions but the screen will also not come on. Sweep to sleep (left to right) works fine .. except I am running the stock att rom, the only mod I am using is sense toolbox
[One (M8) Original Android Development] p50kombi:
Ok, I'll try again using your motion gestures.

Very strange..

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver

---------- Post added at 05:31 AM ---------- Previous post was at 05:19 AM ----------

Just tried .12 and I can't use your disable motion option. It just won't work with the dot view case.

Maybe one of the other owners of the case can confirm if it's working for them...

The phone vibrates, but the screen won't come on.

And it only seems to vibrate of I switch the screen of before closing the case.

If I close the car with screen on, I can tap and swipe all I like. Nothing happens.

Sorry mate.

Other than that, your kernel rocks...

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M8) Original Android Development] jlevy73:
Same issue as you. Besides that though, 0.12 is great.
[One (M8) Original Android Development] SizAndals:
Loving the speeds of the kernel...no jitter or lags. But I have a concern about notifications. I receive SMS messages but no notifications of them. Settings are checked properly. Happened on both Coin & Viper where both had it working before flash.

Sent from my HTC One_M8
[One (M8) Original Android Development] grega_slo:
Hey flar2!

Love your kernel, but can you check this out please?

http://xdaforums.com/showpost.php?p=52497901&postcount=3834

I don`t know if it is kernel related but I *think* it started to happen with 0.12 :)

---------- Post added at 09:21 AM ---------- Previous post was at 08:58 AM ----------

Update to this one...

It IS kernel issue.

I flashed 0.10 and all is working great again.
[One (M8) Original Android Development] p50kombi:
Not a problem in arhd with 0.12...

Just tested and all working as should.

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M8) Original Android Development] grega_slo:
It could be Venom tweaks / kernel glitch...

ARHD is close to stock so probably not problem there...
[One (M8) Original Android Development] pritamsl:
Hi flar2, I'm not sure if this is kernel related either but is there a way to modify the default brightness values for auto brightness? I find that the brightness is too high at night. With power saver enabled brightness is sufficient in most cases except when in direct sunlight. When it's sunny out I have to turn off the auto brightness (in power saver mode) and manually crank up the brightness as I have trouble reading the keyboard. If auto brightness could be modified I could create a more energy efficient profile that is still useable in the sun. Thank you for your great kernel.
[One (M8) Original Android Development] digitaldazz:
Thanks for kernel reverted back to .9 as too much battery drain on10. Not sure why but its a big difference in battery life.

PS: I'm on GPE
[One (M8) Original Android Development] vegetaleb:
Anyone can confirm this on ViperOne?
[One (M8) Original Android Development] grega_slo:
Found the cause.

In Venom tweaks DO NOT touch kernel settings and all will be just fine :)
[One (M8) Original Android Development] grega_slo:
Uuuups another one.

When incoming call answer when I first put my phone to ear screen won`t go off. Then I just remove it from near ear and move it back and it works...

Huh something is really borked in this version, with 0.10 no problems at all.

** LAST UPDATE **

Found exactly what is wrong...

If you enable POCKET DETECTION in Venom Tweaks proximity sensor goes crazy-.
[One (M8) Original Android Development] p50kombi:
So in other words it's rom related, as it's clearly only on venom

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M8) Original Android Development] grega_slo:
Most probably yes.

But in 0.10 no such problem exists... I think it has sth to do with pocket mode...
[One (M8) Original Android Development] vegetaleb:
I never use this mode anyway,it eat battery for nothing

Btw is it me or the Fast battery charge is not fast? Charging with USB from desktop PC it has the same charging time as if it was Off