yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] flar2:
Indeed, I started looking at these logs and the behaviour of the sensors is quite different.

The good news is I should be able to tell which version you have and adjust accordingly.

Not sure if it's different hardware or firmware.
[One (M8) Original Android Development] tiho5:
Yes, what can I say... This is what they call development. Right here. Thanks, Flar!
[One (M8) Original Android Development] dukat0s:
0.16version

hey [MENTION=4684315]flar2[/MENTION] i was testing and playing around with your 0.16 version seems so good . all working great .the best battery life i ever have in your version s since your start at m8.keep up the great work =) i never use eco mode or ultra power saving in my test.i am able to see 10+hours of SOT with eco easily

i m on pvs 15 a lot of uv and testing . 100% Stable no reboots or freeze with viperone combo its the best out there =)

i just install v. 0.17 i test it hardly again with more uv and i report soon =)
[One (M8) Original Android Development] GelullaBarr:
[MENTION=4684315]flar2[/MENTION] the kernel is great for battery life, I choosed everything almost stock, just max freq to 2450 or so, and choosed only HTC gestures, no swipes or custom gestures, but stock swipping is less responsive with your kernel. I also have DotView case and double-tap is not working really well, and I must swipe 2-3 times to answer or reject calls..Double tap is less responsive also wtihout dotview case also. Can you work on that because I like your kernel for battery life, other things I don't need.
[One (M8) Original Android Development] Shebee:
Open venom tweaks and manually set the gestures to default (even if they already are).
[One (M8) Original Android Development] Tikerz:
Does anyone have the stock GPE kernel in flashable form?

Edit: Nevermind, I just extracted the boot.IMG from the ROM and flashed it with Flashify.
[One (M8) Original Android Development] MajikUF:
[MENTION=4684315]flar2[/MENTION] I know that we've (this forum) have previously discussed a few differences between this current version of the kernel, and one that will work for Verizon devices. If the differences are just limited to partition differences, in your opinion, is it possible to have a Verizon branch that just hard codes the partition variables differently so that Verizon, potentially sprint, and possibly any other different variant out there can enjoy your kernel too?

I've used your kernels before and was disappointed to see that you don't support some of the other devices, but I know there are enough intelligent people out here that could easily make the greatness of your kernel available to a bigger audience.

Thanks

Maj
[One (M8) Original Android Development] kuailan:
Believe me that is one of the first thing i tried trying to figure out how to make it work. Anyway, i will try to wipe out the rom, and reinstall fresh ...see if it does work and report back...
[One (M8) Original Android Development] GermanGuy:
[MENTION=4684315]flar2[/MENTION]. So far sticking with the .10 Kernel since later versions unfortunately do cause some issues for me. Could you, by any chance, add the slimbus OC Mods, that you included in the .12 kernel, to the 0.10 version. If not, that's ok, I understand.
[One (M8) Original Android Development] flar2:
What are the issues exactly?

I haven't made changes that will screw things up other than the custom gestures, which should behave as stock if you select that.
[One (M8) Original Android Development] GermanGuy:
With every version after 0.10, stock gestures stop to work. I do choose stock settings in Aroma. As soon as I switch back to 0.10, everything works again.
[One (M8) Original Android Development] bamboosensei:
Are you allowing for some time for the easy access service to initialise? From my understanding, the main change to the kernel has been the introduction of a delay. I haven't had any issues with the gestures but I'm not sure if this is the correct reasoning behind it and maybe someone else like Flar could chime in. Maybe give it 2 minutes after boot up, then switch the screen off and on with the power button and finally check whether the gestures work?
[One (M8) Original Android Development] GermanGuy:
Yes. I did that. It's ok though. 0.10 running great for me.
[One (M8) Original Android Development] Shudder123:
I just got my m8 and this may have been mentioned already, but does this kernel fix the issue where 100% dips to 99% really quickly?
[One (M8) Original Android Development] SeanHacker:
That's every device made in today's market. Its not an issue. Its a safety feature. Its why cell batteries can last as long as they do nowadays without the need for replacement because of over charging. ;)
[One (M8) Original Android Development] blacklistedcard:
Latest version 0.17 is working great for me. Gestures all working fine.

Good job!
[One (M8) Original Android Development] aamitabh28:
I am on viper 1.6 and motion launch gestures dont seem to register when enabled from settings and set to default in venom tweaks.

Proximity sensor either works or it doesn't in calls.Its very random.If it does work it works perfectly..

I have the asian variant so maybe its something to do with the hardware or firmware as mentioned above.It sucks we cant S OFF as of yet :(
[One (M8) Original Android Development] kuailan:
Flar, I finally figure out how to fix my gesture issues. I have done reflashing ROM clean (full wipe) at least 3x...and still does not work....but having trying out each of the venom tweaks in the 1.6.0. ROM, finally I get to the bottom of the issue. In venom tweak ---> Kernel section ---> I have to disable both the Sweep2Wake and DoubleTap2Wake, and reboot the phone. Only that way, I can have all my gestures (slide down, up, right, left) to work properly....including activating the HTC speak. For some reason, those SweepWake features cause/break the gesture. Dont know but with the old (but for me I think pretty stable) .10 version....I can use those sweep to sleep/wake...and yet use all my gestures properly.
[One (M8) Original Android Development] aamitabh28:
This doesnt work for me.

Its very strange and very random..seems to have to do with viper rom
[One (M8) Original Android Development] jlevy73:
To help flar, post a log of your device when gestures don't work.

You can do this from adb using the following command:

dmesg > /sdcard/dmesg.txt

Then post the dmesg.txt file from your sd card here.
[One (M8) Original Android Development] aamitabh28:
Okay..so i try using it.and then when it doesnt work i take the dmesg ryt?
[One (M8) Original Android Development] flar2:
I think a lot of people have had this problem. The settings in Venom Tweaks are for old the old version of sweep2wake and doubletap2wake.

There are other apps (eg: TricksterMod) that might try to set s2w and dt2w to other values, overriding the ElementalX settings.

These settings mess with the gestures even if you select stock gestures. As soon as something tries to turn on doubletap2wake or sweep2wake, custom gestures are enabled. In the case of sweep2wake, only sweep right or sweep left will be enabled.

The gestures all work for everybody, no matter what firmware/hardware you have. If they don't work, it's because of something interfering with your settings.

The only problem with the custom gestures right now is the proximity detector, which I think will be fixed in the next version.
[One (M8) Original Android Development] kuailan:
Flar, can you then tell us which app we can use to take advantage of your kernel without any issue??? Or maybe you can make one for your own kernel???
[One (M8) Original Android Development] jlevy73:
Kcontrol works very well with this kernel.
[One (M8) Original Android Development] kuailan:
I don't think so? I have tried ....and still give the same result. When you enable both sweep and double tap...then I loose all my gestures ...just like the venom tweak. Beside when you run the app first...you will see they are only 78% compatible with the kernel/hardware? So plenty are not yet supported?
[One (M8) Original Android Development] shasen1235:
Here is the experience I've been getting since my first phone DHD

If you don't really need an app to control your kernel,just leave it as it is

The most impressive thing for me in Flar's kernel is most of the features can be selected while installing or changed by just editing scripts

This really allows us to get rid of kernel tuning apps

In this case,we can truely experience the fine tune kernel devs want to provide and that is incredible:good::good:

Using kernel app just never seems right for me but sadly I needed them for more features back in time when I was using DHD

Thankfully we got Flar here in M7 and M8 and I'm really satisfied with his works!
[One (M8) Original Android Development] tim.ton:
I second this!
[One (M8) Original Android Development] My Beer Belly:
I've been going about nearly two days on .17 and had no issues. Gestures have been working as expected and I rarely get phone calls, mostly texts, so I have really had a chance to notice if proximity sensor is working. I did use the feature to auto answer a call if pulled to your face and the auto lower ringtone when picking up phone on .16 with no issues so I'm assuming it's still working on .17

For any comparisons, I'm on US T-Mobile with their newest firwmware released a week ago. I'm on ARHD 7, S-off and supercid. I also have the modified hboot with no red text, but I doubt that matters.
[One (M8) Original Android Development] aamitabh28:
Ill share why it doesnt work for some people on viperone.

Dont set on boot in any kernel tweaking app as it sets the sweeptowake option in venom tweaks also which isnt compatible.

Reboot and custom gestures will work just fine
[One (M8) Original Android Development] djmatt604:
This kernel and Trickster play very well together. Phone runs like a dream normally but the tweaks are just icing on the cake. So glad I invested in this phone and the dev community is awesome. Thanks again for the work flar, loving it.
[One (M8) Original Android Development] cepheid46e2:
Can anyone tell me if "Disable Max Screen Off Frequency" increases or decreases battery life?
[One (M8) Original Android Development] aamitabh28:
Increases.Limits cpu frequency when screen is off
[One (M8) Original Android Development] flar2:
Update!

Let's see if this gets the proximity sensor working properly for everyone.

Remember, if you have any issues with the gestures, make sure there are no apps messing with your settings.

Once I get it fixed, the GPE version will be updated.

Download;

ElementalX-m8-0.18-Sense

Changes:

-add proximity enabled flag

-adjust sensor initialization
[One (M8) Original Android Development] Savant:
Badass thanks.
[One (M8) Original Android Development] kfasheldon:
Flashed .18 .. Boots amazingly fast and initialized quicker, very nice indeed
[One (M8) Original Android Development] My Beer Belly:
Not really noticing a difference in .18 from any of the ones before, but that's because everything has worked flawlessly for me since I first flashed .10
[One (M8) Original Android Development] aamitabh28:
Working great so far!!

Awesome work!!
[One (M8) Original Android Development] jlevy73:
No issue thus far with 0.18.
[One (M8) Original Android Development] lukes91:
0.18 is great! Wonderful work [MENTION=4684315]flar2[/MENTION], as always ;)

Sent from my Venomed Mate
[One (M8) Original Android Development] TugBoatTed:
Wake gestures seem to be working better on 18. Thanks flar2!
[One (M8) Original Android Development] stathis95194:
Edit: It seems that the problem had to do with trickster mod conflict. I deleted my post not to confuse anyone. Everything fine with 0.18
[One (M8) Original Android Development] tiho5:
Flashed 0.18

Proximity during calls works now!

Don't seem to have any problems.

Will use it and report here if there's something.

Great work! Thank you, Flar!
[One (M8) Original Android Development] tsaojam:
I tried to do a search but wasn't sure about this - how do firmwares / ROMs affect the performance of the kernel? With the recent spate of firmware updates (WWE is up to .10), does this affect whether we can use the latest ElementalX kernel? Will there be incompatibilities?
[One (M8) Original Android Development] grega_slo:
Great job Flar2!

Now proximity sensor works just fine :)
[One (M8) Original Android Development] jlevy73:
Firmware update should not effect being able to use this kernel. Neither should the Rom you chose to run. Some people running Viper have had some issues but from what I can discern, viper has their own custom gestures mods and could have an impact on what this kernel is trying to accomplish if those are modified. Looks like most of that has been resolved though.
[One (M8) Original Android Development] mrosen:
It seems like my Organization is blocking downloads from Androidhost.

Can anyone share Kernel 0.18 on Dropbox please?
[One (M8) Original Android Development] jlevy73:
Had a bunch of call throughout the day and proximity sensor worked perfectly. I did a bunch of tests with pocket detection including trying to double tap the screen through my jeans and couldn't get it to wake.
[One (M8) Original Android Development] donmarkoni:
Hey mate! I'm glad your problems are finally over! :victory:

Sorry [MENTION=4684315]flar2[/MENTION] for off-topic, but I just had to say it. :D Great kernel, as always. :)

Cheers!
[One (M8) Original Android Development] idrOiding:
Every thing is working just perfect .

Thanks flar2
[One (M8) Original Android Development] WESBAR:
External SD Card

Hi. I have an external micro USB card reader. It continually mounts and dismounts when plugged in. It also does this on the stock kernel. Is there an way to make it mount? I think it's because the card reader has a light on it. Cheers.
[One (M8) Original Android Development] tiho5:
There is something else I want to mention:

When I am on a call (on phone speaker or loudspeaker) I sometimes have my screen turned off by pressing the power button or using wipe2sleep gesture.

Near the end of the call I used to double tap on the screen or use a swipe gesture, which used to turn the screen on again at which point I was able to press the end call button. This was using ver 0.10 and stock gestures.

Now with ver 0.18 I can’t do that as the gestures aren’t turning the screen on any more while I am still on a call. I have to use the power button for that. May be you can take a look. Not a big deal anyway.

So far everything is working flawless. Thanks again!
[One (M8) Original Android Development] flar2:
I'm not sure if I can fix this, I'll try my card read and see if I experience the same.

Right now, the touchscreen is disabled while the screen is off during a call, so no gestures will work. I did this so there are no accidental button presses if you touch the screen with your face during a call. I'll mess around with it a bit to see if there's another way.
[One (M8) Original Android Development] dukat0s:
Testing your v0.17 again great results for the first charge. Same settings no oc or eco mode .a lil bit more wakelocks than previous0.16propably for messenger
[One (M8) Original Android Development] electric turd:
Does this kernel do anything with the battery life on this phone? Also i'm using the AOSP lockscreeen on Venom, will tap 2 wake work with it that way?
[One (M8) Original Android Development] flar2:
Well, I've tried to improve battery life.

tap2 wake will work with AOSP lockscreen if you choose "Traditional S2W/DT2W" during installation.
[One (M8) Original Android Development] electric turd:
Crap!!! just noticed no verizon support. Do you have any plans for that?
[One (M8) Original Android Development] dsymbol:
Hi,

I'm still on stock kernel & would like to try ElementalX kernel & have a few questions please.

For stock kernel, my settings are as followed:

Settings > Power > Sleep mode - OFF

Settings > Power > Power saver > Data connection - de-selected/unchecked.

(Please see the attachment).

Which means I want to keep data connection ON.

I've gotten pretty good battery life. However, my data connection gets cut off & I cannot receive Whatsapp messages when the phone sleeps.

So, by turning on Power Save (conserve CPU usage), does that mean I'm reducing CPU speed?

With ElementalX which settings that would give me maximum battery life & performance like Power Save mode, & Most Importantly, do not cut off data when phone sleeps?

Thank you for any advice.

EDIT: I forgot to add: I do not need gestures at all. I turn them all off in settings > Motion launch gestures.
[One (M8) Original Android Development] stathis95194:
Can someone try this to see if they get similar results as myself? If a calendar event pops up on lockscreen while screen is off, try to DT2W on the area where the popup is. It doesn't register the first gesture. If you DT2W again all is well.

This is with 0.18 btw
[One (M8) Original Android Development] guyd:
Since flar2 does not own a Verizon M8, he's not developing for it.
[One (M8) Original Android Development] GermanGuy:
0.18 working great including custom gestures. Thanks Flar.
[One (M8) Original Android Development] Fatos:
Sprint m8

Sorry if it has been asked before.

Does this kernel work with sprint M8. i hasve s-off and i use it in Norway. Im not sure if it does have any thing to say.
[One (M8) Original Android Development] SeanHacker:
You could always try reading the OP? :)
[One (M8) Original Android Development] Fatos:
I read that but i thought that means only for those who wants to use the phone on Sprint network. Im not so god with this. Forgive my ingnorance i just thought maby it wont apply in my case.

Thanks any way.
[One (M8) Original Android Development] SeanHacker:
You asked if it works with Sprint. That question is answered in the OP. You never mentioned anything about using a sprint device on another network other than you use the device in Norway. So I really don't know how to answer your question.
[One (M8) Original Android Development] shawn0223:
I don't think it will. If I remember correctly cdma devices are partitioned differently and write kernels and stuff to different partitions than the gsm variants. I know Verizon is like that but I believe that applies to Sprint too
[One (M8) Original Android Development] Vandam500:
I also saw issues with proximity sensor not working all the times on calls with .16. Flashed .18 and so far it is working perfectly!
[One (M8) Original Android Development] nickespi:
What are the best setting for battery life? Have not been in the game for a while all these different schedulers and variants have me trippin:confused:
[One (M8) Original Android Development] steve1996:
I've got excellent battery life today, 6 hours screen on time

2.3 ghz, -45 mv in aroma, stock gpu clock, and I've uninstalled kernel control apps
[One (M8) Original Android Development] metaphz:
Is there a write-up where I can read more about features and settings for this kernel? I feel like I don't know enough to get the most out of this custom kernel for my needs.

ETA: Just flashed this kernel in TWRP. Screen when black when I hit finish. Can't get TWRP to light back up...

ETA2: Went in to ADB and forced a reboot. Any idea why that would happen? I had the same problem when I flashed ViperROM the screen went black when it finished and didn't reboot. When I plugged the device in to the PC via USB it lit back up.
[One (M8) Original Android Development] flar2:
Hold power and volume up until it reboots and all will be good.

This is a bug in TWRP/Aroma. If you have the screen timeout set in TWRP and take longer than that timeout to finish the aroma setup, the screen will go black and you can't turn it back on.

I think the default settings are best. I have quite a bit of info in the OP.
[One (M8) Original Android Development] metaphz:
Thanks for such a quick reply. I just wanted to say I appreciate your work!
[One (M8) Original Android Development] aamitabh28:
Anybody has an idea why the kernel(Android OS) Eats up the battery so much?

Ive tried clean installation and wiping cache
[One (M8) Original Android Development] SeanHacker:
Android OS drain isn't usually kernel related. It can be caused by quite a few things. One of the more common causes is GPS service, Google location, ect... Use the app Better Battery Stats to see what's happening. Who told you Android OS was kernel related?
[One (M8) Original Android Development] aamitabh28:
This screenshot from GSAM.

Bbs shows nothing out of the ordinary..it is a very persistent problem.

Thanks for the help
[One (M8) Original Android Development] SeanHacker:
Will that app give you a log that you can post here. It makes me curious.
[One (M8) Original Android Development] bamboosensei:
I have the same issue and have noticed this from v0.16 onwards. Haven't had time to try out v0.18 as of yet though. If there's anyway I can debug, would be nice to get to the bottom of this.
[One (M8) Original Android Development] aamitabh28:
No it doesn't.

If you could tell me how..i could get one for you..
[One (M8) Original Android Development] SeanHacker:
What app is that?
[One (M8) Original Android Development] aamitabh28:
Gsam battery monitor
[One (M8) Original Android Development] driftmetal:
Hi flar2,

This is my first time using your mod.

Someone maybe have issue by cut shell command without busybox installed.

How about the inline modification below?

---S2W="`grep S2W $ELEX_CONF | cut -d '=' -f2`"
+++S2W=`grep S2W $ELEX_CONF`
+++S2W=${S2W#*=}
...
---WVIB="`grep WVIB $ELEX_CONF | cut -d '=' -f2`"
+++WVIB=`grep WVIB $ELEX_CONF`
+++WVIB=${WVIB#*=}
[One (M8) Original Android Development] silvercat:
Hi flar2,

Is it possible to implement ntfs read/write support in the kernel instead of using a 3rd party app for mounting the hard drive ?
[One (M8) Original Android Development] Giblet-dono:
How are these both drains?

One of you has been on battery for 11 hours and still has 73% left!

The other is on 1 day and 21 hours!

What do you honestly expect? Do you want the device to not use ANY power? if so, just turn it off..

the kernel (Android OS) "application" is there on every android phone..

It takes care of a lot of things like CPU and memory resource management

The wakelocks you see from the battery service are from Gsam (as far as I know)

but with just 8.2s and 14s of wakelock time they hardly impact battery life!

All the included processes are system processes

kworker" is a placeholder process for kernel worker threads, which perform most of the actual processing for the kernel, especially in cases where there are interrupts, timers, I/O, etc. These typically correspond to the vast majority of any allocated "system" time to running processes.

The migration kernel process distributes workload across CPU cores. You should have one migration process per processor core.

And so on, every one of them is a necessary part of the kernel!
[One (M8) Original Android Development] bamboosensei:
This is precisely why I said I would like to get to the bottom of it. I never said that it was a major issue for me but if it was the underlying basis for a greater problem, it would be nice to be able to contribute to the xda community somehow. Yes, the wakelock time is not long and yes, I understand that the majority of my battery drain has come from Google Play Services and Google Search, which have collectively caused over 3000 wakelocks in what ended up to be just over 2 days of uptime but the Android OS, as per GSAM anyway, still ranked higher in battery consumption and CPU time. Whilst the wakelock was only a few seconds, the CPU time was a lot higher.

I note that my on screen time ended up just over 7 hours so I am NOT trying to say that it is the fault of the kernel in any way detracting from battery life. Quite on the contrary, I appreciate the work Flar has put into optimising the kernel for performance and battery life. In fact, this was when the cpu was clocked at 2.8ghz. I just want to reiterate that if I am able to contribute somehow, I would like to make that meaningful contribution. If the input of others suggests this is normal, then I am fine with that. So thank you for your comment, I am at ease.