yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] DREWHAMM974:
I have no reason to suck up. One I'm not a child looking for approval, and two respecting a fellow developers work is just common courtesy. Whether I use it or not I respect anything on XDA that obviously took a lot of effort. Also anyone acting entitled and saying a developer's work is disappointing on that developer's thread is bound to get a response. Sir, no disrespect but you are on a public forum with 5 and 1/2 MILLION registered members. Anything you post on here you are posting for each and every one of the users to answer you. Unless it's in a PM just assume that everyone is going to reply. There's no such thing as not asking someone's opinion on a forum, especially one of this size.

Also you saying you were "disappointed" in him and his work is criticizing him. It shows that you feel it is no good and that you feel strongly enough about that fact you must publicly voice that opinion for others to see.

If you had said, "Your work is fantastic and I appreciate you making it but lately you have not been updating the GPE kernel and that is the major appeal this kernel has for me. I understand you are very busy but could you please consider releasing an update for the GPE kernel with this changes as well?" That would have been a post I'm sure many would agree with.

I'm sorry for taking your thread so far OT Flar and I'm done with this conversation.

---------- Post added at 11:40 AM ---------- Previous post was at 11:37 AM ----------

This⬆ is exactly how I felt about it as well. It just rubbed me the wrong way knowing how hard the developers work for these things.

OT but you ever going to come back and visit us in Trinity?
[One (M8) Original Android Development] BrandonPrice31:
Agreed, I worded my post wrong. Wasn't my intention though.
[One (M8) Original Android Development] lukes91:
thank you [MENTION=4684315]flar2[/MENTION], i just flashed 0.14 and pocket protection works fine :D
[One (M8) Original Android Development] ChronoWerX:
No one have an idea? When I slide down, it comes only the lockscreen, not voicedial
[One (M8) Original Android Development] b0gd4n:
just a quick question: why does your signature says ElementalX 0.14?

EDIT: OK, I just read some more posts. I thought the latest version is 0.10 :D sorry for the stupid post :(
[One (M8) Original Android Development] flar2:
I did a lot of installing/reinstalling and rebooting today.

Stock ROM: everything working perfectly

InsertCoin: everything working perfectly

Viper: just restored from backup and updated to 1.6 and so far so good. Tried several reboots and messing with settings and each time the proximity sensor and all gestures were working correctly. I think they've fixed the weirdness with MLG that I was experiencing earlier.

If you are still having issues even with 0.14, please do a backup, then clean install (ie: wipe everything), get it up and running, install 0.14 and see what happens.

You can tell if it's working properly by waiting for it to completely boot up (ie: wait for a couple minutes), turn the screen off and on at least once. Then turn the screen off, hold your finger over the proximity sensor and try a gesture. If nothing happens, then it's working. Pocket detection should start working within a second or two of turning off the screen. If doesn't kick in for 5-10 seconds, then it's like on older versions and not working properly.

I think I can add this option.

On a technical note, the motion sensor can be set to stop polling (which will disable the camera shortcut), but I don't think it is ever shut down. The Motion Control Unit (MCU) seems to be on all the time and controlled by firmware. The kernel code in CwMcu.c isn't really a normal driver, it's an interface for communicating with the MCU. The MCU in turn talks to the proximity sensor, light sensor, gyro, etc. You can have the CPU completely shut down and the MCU keeps working. It is an extremely low powered device, so no noticeable impact on battery.

Check your lockscreen settings in Venom Tweaks, make sure swipe down is set to "default"

The last few versions are just working on custom gestures. I don't want to put it in the OP because people who don't follow the thread will install them and have problems (although 0.14 is working totally perfectly for me).

Also, GPE version is coming. It's very time consuming to switch back and forth from Sense to GPE. I use Sense on a daily basis, for me it's one of the appeals of an HTC phone.
[One (M8) Original Android Development] hdelvalle009:
The battery is consumed me quickly, any recommendation to adjust the frequencies of the kernel to last me more battery?

GOLDEN EYE 1.2 International stock

HTC ONE M8 - ELEMENTAL X 0.10
[One (M8) Original Android Development] bkeaver:
Flar what is the difference between version .09 and the latest. I actually get better standby and screen time on .09 for some reason.

This past weekend I was on .13 and after 5 hours I was down to 79% with 30 min on screen taking defaults. On .09 I am on battery for over 12 hours and am at 82% with 45 minutes on screen time. Just trying to figure this out.

And by difference I'm talking governor/scheduler not everything else.
[One (M8) Original Android Development] steve1996:
He removed hardfloat flag, that's the difference. It should be more battery friendly in theory according to flar2.

[MENTION=4684315]flar2[/MENTION] maybe enable the hardfloat flag back and let us see if it's better or worse in battery for next beta release please? I've seen many people posting about 0.9 having better battery life than the 0.10 and up, I think that's a good enough reason to try it.
[One (M8) Original Android Development] David Balfour:
[MENTION=4684315]flar2[/MENTION]. Thanks for the hard work and testing on this. I will go for a full wipe tomorrow.
[One (M8) Original Android Development] K-a-M-u-Z-u:
I have installed the kernel to get busybox installed, and then i have restored BOOT nandroid image i have made before.

after reboot i got back my old kernel and busybox is installed and working.

i have noticed leftovers from elementalx in /etc/init.d/99elementalx and /etc/elementalx.conf

i have deleted them using root browser, but after reboot, both of them are back.

is there a ay to remove them permanently? i dont want any init.d scripts.

thanks
[One (M8) Original Android Development] steve1996:
Restore system backup, the kernel is more than just a boot.img
[One (M8) Original Android Development] ChronoWerX:
Is on default
[One (M8) Original Android Development] flar2:
I would wipe cache and dalvik, and perhaps do a clean install. The best thing you can do to have a smooth running phone is keep it really clean, don't backup and restore a bunch of apps. Don't skimp on wiping data when you install a ROM.

But yes, the difference between 0.9 and 0.10 is the hardfloat flag, and I'm very reluctant to put it back. There are literally a hundred pages in my Nexus 5 thread about the subtle degradation of battery and performance from that change. The Nexus 5 is very similar to the m8, they are like brothers. In my testing there was a big improvement in battery life on both phones after changing it back to softfloat.

But one thing I've noticed about the m8 is very inconsistent battery drain. There are times when I'm a bit shocked at how fast it's draining, but I still often have 60% or more left at the end of the day. One time I had very bad drain, which was fixed by a reboot. I use Better Battery Stats and there was no explanation.

On both stock kernel and 0.9 and earlier, I was mostly getting about 0.9 to 1.1 % per hour while idle. Now I have anywhere from 0.3 to 0.7, which is probably close to as good as it will get, I think. Best I've had on Nexus 5 is about 0.2% per hour, but more typically 0.6% per hour.

Drain during use should be similar on all versions, I haven't noticed major differences. You could disable gboost.

You need wp_mod.ko so you can modify the system parition. Then you can just delete them. Or delete them while in recovery.

The voice dialer works for me on Viper. Not sure what the problem is, but it's not kernel. Basically, the kernel detects the gesture and sends an input event to the system. At this point, it is up to the system what to do with that input event, the kernel is completely out of the picture.
[One (M8) Original Android Development] muppetmaster916:
Everything is smooth as butter here on .14 and viper Rom latest, pocket detection works flawlessly, thanks for the hard work
[One (M8) Original Android Development] Shebee:
Proximity sensor still bugging in .14 in calls.

Also pocket detection gets stuck sometimes.

Works better than the previous versions though.
[One (M8) Original Android Development] jlevy73:
0.14 has been working great for me. I tried this on IC, Viper and Stock and pocket detection and proximity sensor working great. I think the key is letting the phone fully boot up without doing anything to it for a couple of mins.
[One (M8) Original Android Development] Shebee:
I'm not talking about it being dodgy after boot but hours into use.

Just now I called a mate and the screen was on all the time.
[One (M8) Original Android Development] ChronoWerX:
Thanks, was an user issues ;)

I have not install HTC Speak :rolleyes: But thanks for your help
[One (M8) Original Android Development] grega_slo:
Yup, same here.

I`m on Viper.

Screen on during calls but mainly it is for first call all other calls are ok.
[One (M8) Original Android Development] tomoffel:
I've noticed the same here over on ARHD 5.5 in calls the screen doesn't go off if I cover the proximity sensor.

Sometimes it works if you play with the power button (turn screen of will on call, turn it back on, and so on) but couldn't find a system in it or a sure way to fix it.

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Original Android Development] GelullaBarr:
With 0.9 i lost 9% in 8h of standby but with 0.10 just 2% and overall battery is better in browsing and gaming, so I don't want that hardfloat to be enabled ever.
[One (M8) Original Android Development] Freak07:
[MENTION=4684315]flar2[/MENTION]

hey,

regarding the inconsistince of battery drain. i know there was an ongoing discussion about the activation/deactivation of cores getting stuck. and that some people complained about a battery drain in correlation with that.

they monitored their cpu usage with eg faux clock. i have done that too, and i remember that sometimes all four cores were active and would not be deactivated regardles of cpu load until a reboot. I know also you were stating that´s due to the fact that the app for monitoring activates the cores. I used perfmon (from here: http://www.google.de/url?sa=t&rct=j...VhwebrtWN-1vGTk-PtveenQ&bvm=bv.66330100,d.ZGU) and when everything is correct all four cores are online for a short time after opening the app and drop to 300 mhz on one core. but sometimes i felt my phone becoming hot after using it for a while and the battery decreased faster then usually. Then i killed all running apps opened perfmon and all four cores were activated ( 2 of them at around 1 gh, the other at 2,ghz). i rebooted and the problem was gone.

maybe theres something wrong it a certain custom rom / kernel combination. but this issue was definitely there for me also.

when the issue was there i was on renovate nightlies with elemental 0.9

now i´m on arhd 5.0 for a week with 0.10 and the issue was not one time apparent
[One (M8) Original Android Development] K-a-M-u-Z-u:
Thanks! that did the trick.

mount the system partition in recovery and delete them through the twrp file manager.

saved me from full system recovery.
[One (M8) Original Android Development] mushages:
on viper 1.6.0 flashed elemental 0.14 after like 7 hours of usage all cores decided to stay active. reboot fixed it
[One (M8) Original Android Development] steve1996:
I'm also getting this on renovate. I've got great battery life, 3-4 hours with 50% left, then I entered faux clock and found out that all the cores are stuck in 1.9 ghz , then a reboot fixed it.
[One (M8) Original Android Development] Snah001:
I had this behaviour on Viper Rom before flashing 1.5.0. clean.

All 4 cores stuck at around 2 Ghz and drained the battery fast. I flashed 1.5.0 of Viper Clean and did set it up new and it was gone so probably Viper got corrupt.

But....hangouts still sometimes is causing core 3 to get stuck at max freq. and this is noiticable because the phone heats up.

Cleaning cache of the app restored normal working.

Have this on at least three last versions of Viper in combination with the kernel (from 0.8 up i guess)

It keeps doing it even after flashing Rom clean (on Viper 1.5.0 and 1.6.0), so it well could be a misbehaviour of the hangouts app. At least I know what is causing the drain and heat up and what to do to stop it.
[One (M8) Original Android Development] flar2:
I don't think I've had the cores being stuck issue. This could be a bug in mpdecision or pnpmgr, or perhaps an app (like hangouts) is acting up.
[One (M8) Original Android Development] mushages:
just want to say that i think battery on 0.14 is better than 0.10 but cores getting stuck after some time.
[One (M8) Original Android Development] p50kombi:
Could it be that people underclock via faux app?

If so, I read somewhere that if pnpmanager ramps the cpu up to a value higher than the underclocked value, the cores lock.

Maybe that's causing issues...
[One (M8) Original Android Development] flar2:
^^that's a good point.

It hasn't been mentioned much on this thread, but especially for HTC devices, it's generally a bad idea to manipulate CPU frequencies.

Don't try to set min or max, and be very careful with CPU control apps automatically trying to do stuff. I've seen TricksterMod lock the min frequency many times, if it happens to be boosted while TricksterMod saves your settings, it will stay there.

I will also check to see if gboost is acting up in any situations. You could try disabling it and see if the problem is resolved.
[One (M8) Original Android Development] flar2:
BTW, my battery drain was 0.2% per hour overnight, best ever on this phone.

It's too early to tell whether it has anything to do with the motion launch changes.
[One (M8) Original Android Development] mushages:
i noticed that in viper 1.6.0!!!! i usually use trickster but this time i didnt want the modding headache so i didnt use any app. set it in aroma and leave it. but when my cpu frequencies locked i went to venom tweaks>cpu and saw the min.freq was 1920 which is the maximum in power saving mode! reverted it to 300mhz but nothing happened. did a restart now its back to normal. also i only modified max screen off frequency which i chose to be 600mhz.
[One (M8) Original Android Development] jlevy73:
Wow, I can't get 0.2% per hour overnight with my phone off :D
[One (M8) Original Android Development] itzsnookums:
Agreed, I get almost 2% an hour.....wish I could get what flar gets lol
[One (M8) Original Android Development] ivicask:
[MENTION=4684315]flar2[/MENTION] could cores when power saver is activated be limited to 3?(option) That would for sure give some extra power saving without some noticeable performance lost.
[One (M8) Original Android Development] steve1996:
I didn't touch the cpu frequencies with faux clock. I use it just for under volt and color control.
[One (M8) Original Android Development] Snah001:
Just experienced it again with hangouts now keeping all 4 cores around 2 Ghz. Stopping the app immediately stopped it from doing that.

It happens ONLY with hangouts but since I know this when using it i check frequently ( easy done with viper just pull down the statusbar a bit) that it isn't stuck. You can't predict when it is doing that because it is random and only when using it.

Most of the time it happens once a day.

Sent from my Asus Infinity TF700 with Dock
[One (M8) Original Android Development] Freak07:
I suspected hangouts does its part but I had the issue, force closed it and the cores continued to be stuck.

[MENTION=4684315]flar2[/MENTION]

I never messed with frequencies as you advised because of mpdec and pnpmngr.

This is a really strange issue but I think most of the battery drains are related to this...

and one more question.

Do you greenify anything or have auto sync off?

I'm also getting sth like 0,2%/h but I have auto sync off.

Also do you have messengers like hangouts installed?
[One (M8) Original Android Development] Snah001:
Oh and I use the kernel as stock as possible so no fiddling around with frequencies

Sent from my Asus Infinity TF700 with Dock

---------- Post added at 07:20 PM ---------- Previous post was at 06:46 PM ----------

No other messengers installed, just using exchange (push) but that has no influence. It is pure the hangouts app doing this

Sent from my Asus Infinity TF700 with Dock
[One (M8) Original Android Development] elsworth1983:
Same [MENTION=311443]Snah001[/MENTION] only undevolting for me that's it

Sent from space
[One (M8) Original Android Development] iggdawg:
Flashed 0.14 yesterday and it's going quite well. My only non-stock selections were USB fast charge, 45 unervolt, and removing motion requirement from gestures. I find removing the motion requirement (and making sure my hand isn't in front of the prox sensor lol) makes the camera launch gesture work a whole lot more often. No issues from 45 undervolt, and USB fast charge works as expected. Top notch as always so far.
[One (M8) Original Android Development] itzsnookums:
Idk bit I'm tired of my battery draining so fast.....
[One (M8) Original Android Development] Savant:
Check your apps and wake locks. I don't have issues and neither does anyone else that stands out.
[One (M8) Original Android Development] itzsnookums:
Dude what thread are you reading, they have been several people who have reported battery issues....it's to do with the cores freaking out....flar has even acknowledged it.....

P.s., not everyone is a noob....
[One (M8) Original Android Development] DeeZZ_NuuZZ:
Not even with this kernel....sometimes it happens with stock kernel too that it drains really fast even if we don't use the phone really...standby seems to be good but if I immediately use the phone after that standby time it's draining like sh1t even if there is nothing really in background...using also greenify donated and greenified a few apps which let the phone even drain more battery... But this kernel is speedwise really awesome ? ?

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Original Android Development] itzsnookums:
Agreed, exact same thing happens here
[One (M8) Original Android Development] bkeaver:
Ok installed .14 wiped dalvik cache and cache. Been doing decent. After over 11 hrs I have a little over an hour of on screen time at 81%. Which is on par or a little better than .09. This is also with all arch frequencies and gboost not selected.
[One (M8) Original Android Development] flar2:
I don't think the inconsistent battery has anything to do with the kernel (stock or EX), it's something in the system, or maybe some apps.

Overall I'm getting great battery life on this phone.
[One (M8) Original Android Development] flar2:
UPDATE!

Added an option to disable volume buttons launch camera in landscape. Of course this only available if you select custom gestures.

For me, all the gesture stuff is working totally perfect. If there is anybody still having issues with pocket detection, proximity sensor or anything else, I would like to figure out exactly how to replicate it. I've tried many scenarios on several ROMs and it always works.

Download:

ElementalX-m8-0.15-Sense

Changes:

-option to disable volume buttons launch camera in landscape
[One (M8) Original Android Development] frankcck:
I have some battery drain issue these days, and I checked BBS and Gsam, and the issue was caused by Google play service.

Nothing wrong with kernel or Rom sides.

ViperOne@HTC One M8
[One (M8) Original Android Development] BrandonPrice31:
I really appreciate your work and effort and have been a long-time fan of your kernels..

I don't mean to be demanding, but do you know or can you put out some sort of ETA for the GPE version? I would really appreciate it.
[One (M8) Original Android Development] flar2:
GPE will come when all the gesture stuff is working properly. I can't do this kind of development while constantly switching between Sense and GPE. Then I will need to do some testing on GPE, which takes time.

Perhaps this weekend, but I will have guests staying at my house, so may not have time.
[One (M8) Original Android Development] beats4x:
[MENTION=4684315]flar2[/MENTION] just installed .15. All gestures working properly except for double tap. Any thoughts?

Also, even though I selected for vibration feedback on successful gesture input in aroma, there is no vibration.

Sent from my m8
[One (M8) Original Android Development] maynard_jk:
Which ROM are you using? ViperOne?
[One (M8) Original Android Development] elsworth1983:
For me this kernel is great am running stock rom as I like it for now (strange) :p with a huge amount of the system apps removed as sone said in the previous post(s) battery drain can be a large amount of things but the biggest one is Google locations etc there is plenty of helpful posts on xda on what you can do with them. I can easily switch my M8 on at 8am and still have battery life until around 10:30-11:00 pm I have no power savers enabled i have a few things synced and am on mobile Internet from 9:00 till 5:00pm my sot is usually around 5-7 hours. Thanks to [MENTION=4684315]flar2[/MENTION] for your time and work you have put into it there will soon be a donation coming your way :p

Sent from space
[One (M8) Original Android Development] Freak07:
Me too. And this kernel is outstanding! It gives the user so much more choices and the ability to control many things if needed. A big advantage is that once it's set, it's set and ready.

Don't wanted to ***** about the problem with the cores. Probably it's a combination of rom/apps/settings.
[One (M8) Original Android Development] Snah001:
Oh forgot to mention that I regularly get 4 to 5 hrs screen time a day and still battery is not lower than 50% at the end of the day!!

So in essence nothing is wrong with the kernel and hangouts freaking out the kernel is easy to solve. Just kill the app will work.

I wiped cache and settings of the hangouts app yesterday evening and since then it behaved normal, no warranty though.

Next time when it happens I will make a logcat etc. and send it to you so maybe you can detect where it goes wrong.
[One (M8) Original Android Development] grega_slo:
Same here with Viper and 0.15 kernel.

IMHO proximity sensor need a little more work :)

Otherwise all other stuff is working as it should.
[One (M8) Original Android Development] beats4x:
Yup yup

Sent from my m8
[One (M8) Original Android Development] sinosuke:
So glad when you are here too sir [MENTION=4684315]flar2[/MENTION]..My M8 is comming soon :D

Sent from my GT-I9500
[One (M8) Original Android Development] flar2:
This is very strange, can you check that /sys/android_touch/doubletap2wake is set to 1 and that /sys/android_touch/vib_strength is set to around 20. If you have the reduced vibration option, you may have to set it to a higher number for it to be felt.

Proximity sensor always works in calls for me since version 0.14. I've tried all scenarios of making and receiving calls that I can think of.

Could you guys try something:

Reboot your phone and don't touch it for about two minutes after it boots up. Then turn the screen on and off once and try it.

This will tell me if the problem is with startup or some hardware/firmware difference.

If the proximity sensor is initialized correctly, pocket detection will be working right away after you turn off the screen. If it takes 5-10 seconds to start working something didn't go in the right order during startup.
[One (M8) Original Android Development] slayer214:
This seems to be updated past 0.10. Do you mind if I ask if this kernel supports faux sound for the speakers and if it works on the cdma/verizon M8?