yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] ABQNM:
What is your display brightness? Tap on display in Gsam and show the screenshot from there. At high brightness, CPU settings become mostly irrelevant as the screen will drink down battery quite quickly.

Using not more than 50% brightness, I can get that kind of usage or better even clocked to 1.8GHz. Sometimes underclocking can negatively impact battery because tasks that could be completed quickly at high speed may take longer at lower speeds, keeping the CPU from idling as often as it should or keeping more cores online to make up the difference.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] ABQNM:
Yeah with that much usage at high to mid brightness, that is pretty normal. Your app and wake locks look normal so there doesn't seem to be much you can do aside from lower the display brightness if you want more runtime.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] remix92:
Ok thank you for this tip :D
[One (M7) Original Android Development] Osama Zabin:
Your phone was busy while idle for around 2 hours (higher than your SOT), Google Play Services and Facebook are the main reason as per your snap.

Try Hibernate them, and if you don't care for push notifications, follow below thread:

http://xdaforums.com/showthread.php?t=2357417
[One (M7) Original Android Development] Alfa Kenny One:
Thanks. I did. But i using this ROM since months. So i did a clean restore and installed again. And now it worked.
[One (M7) Original Android Development] ABQNM:
It was probably an issue with init.d running at boot not setting the configuration file. Glad you got it working.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] tgeza:
Need help ASAP

Hi guys,

I installed the latest 4.4.2 GPE version of this kernel (which is awesome) but I have a HUGE problem now - it seems to have PERMANENTLY modified some system files and now when I returned to stock Sense it still gives me the Google logo when i boot up and when entering the recovery.

I flashed back the proper HBOOT and stock recovery so these are not the issues. OTA updates also fail at verification in recovery btw.

Please help because I'm quite pissed at this otherwise excellent kernel.

Thanks
[One (M7) Original Android Development] ABQNM:
You need to restore a backup of the /system partition or reflash the system.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] tgeza:
I restored to stock with a Nandroid backup, that didn't work, then I reflashed the GPE RUU, that didn't work either. The TWRP backup of my orginal ROM doesn't boot up either, probably because the Nandroid backups phone ID don't match now.

I'm getting helpless here, what do you think I can do?
[One (M7) Original Android Development] remix92:
I have no push notification in Facebook .

All notification of Facebook are deactivated
[One (M7) Original Android Development] Osama Zabin:
Your results are showing 709 wakelocks of FB during 5 hours even though notifications are disabled. FB is one of the worst battery drain applications.

I believe this is going off topic and better to discuss it in related thread.?
[One (M7) Original Android Development] mrwilly:
Grennify Facebook
[One (M7) Original Android Development] Kenshinhimora:
Does having swipe or double tape 2 wake drain the battery more than having it off?
[One (M7) Original Android Development] Ktan188:
The search feature is a great thing.... my friend
[One (M7) Original Android Development] threetwentyfizzle:
Hey another New Mexican in the forums! I'm a fellow Albuquerque resident. Ok back on topic..
[One (M7) Original Android Development] flar2:
I will have a new feature for you all tomorrow

no
[One (M7) Original Android Development] tiny4579:
I'm not trying to start a disagreement here but one of the prominent CM maintainers for this device said that the wake features use considerable more battery so that's why it's not included in CM. Since it has to at least keep the panel on so it can receive input to wake it, it would at least increase the battery drain somewhat, though maybe not a considerable amount based on what you're saying. It sounds like not even a noticeable amount.

Could you shed a bit of light on what the wake feature actually keeps awake on this phone even if battery life is unaffected? I know with the pocket mode, it would have to make the proximity sensor available in order to prevent the screen from coming on.
[One (M7) Original Android Development] poondog:
I use flar's dt2w, I have used it for the past month or so and I find it great. It works 95% of the time, and battery is in fact hardly changed. When my phone sleeps its losing about the same amount of battery than with dt2w off.

Even though it introduces a wakelock to keep the screen ready for input, the battery drain is VERY light.

In theory though it should use more battery. In practise because its only the touchscreen (which does not use much battery especially in comparison to the display, CPU etc) the drain is very minute. In fact, in a days use lets say it takes 2% away from the battery (I'd say 1-4% a day is accurate) when I am sitting at 30% at the end, instead of 32% it doesn't really matter

For me, its as long as the phone lasts all day :)

I think the average perception is that keeping the wake options will keep the screen on, which in turn will KILL the battery (~5%/h) which is not true. Of course it drains battery, but I am with flar in saying that in the scheme of things it doesn't make an impact
[One (M7) Original Android Development] flar2:
CM never includes screen wake functions on any device.

I've tested it with and without sweep2wake on and there is no difference in battery drain.

Nothing is left on, we just enable irq_wake for the touch sensor, which means if there is an interrupt request from the touchscreen driver, the device is ready to wake up. Every time you touch the screen the touch driver wakes up. So if you touch the screen constantly, it will drain a tiny bit more battery. I've used this phone as my daily driver for the past year, keeping the phone in my pocket much of that time, and I find no difference in battery drain with wake functions enabled. Touching clothing will not wake it up, it has to touch your skin or something else conductive.

Pocket detection doesn't completely disable the wake functions when the phone is in your pocket, it only stops the screen from coming on while the proximity sensor is reading "near." The proximity sensor is only queried if there is a valid "doubletap" or "sweep" event. If you doubletap while holding your finger over the proximity sensor, it will check the proximity sensor only after the double tap, and cancel the wake up.
[One (M7) Original Android Development] flar2:
I've added screen wake functions to a number of devices, and on most of them it makes no difference. There are a couple exceptions.

On the Nexus 7 (2013), the wake functions only work if you keep the voltage regulators to the touch driver on. It drains about 0.2% per hour.

The Nexus 5 requires voltage to the touch driver to detect touches while the screen is off. Unfortunately the touch driver and the lcd panel share the same power source, if you turn off one, you turn off the other, so both need to remain on. This causes a huge drain of about 2-3% per hour.

People hear about this and assume it causes drain on all devices, but it's not true.
[One (M7) Original Android Development] picklerick:
I didn't notice any drain with s2w but I did notice a good amount of battery drain when using dt2w(fullscreen).

Also since I disabled s2s I haven't had any issues with my screen failing to wake.
[One (M7) Original Android Development] mitchst2:
If you installed a GPE RUU that's where the GPE firmware has come from. It's a full conversion to enable OTA's. Sense ROMs don't generally change your firmware hence why you are seeing GPE leftovers. Just flash the latest Sense firmware.
[One (M7) Original Android Development] Sebby:
i tryed fauxsound app en trickstermod voor de fauxsound

but i hear no difference in loudness

or does it not work with the htc stock music player

---------- Post added at 09:26 AM ---------- Previous post was at 09:13 AM ----------

would be a nice option to disabled s2s and leave the s2w

same for de logo2awake & logo2sleep

that would be nice
[One (M7) Original Android Development] atquila.78:
Thanks for your hard work flar2

Best Kernel for me

A good new feature -please swap ram support
[One (M7) Original Android Development] tiny4579:
What do you mean swap ram support? Do you mean swap support to add extra memory using the storage? If so that's pointless on this phone.
[One (M7) Original Android Development] krazyflipj:
Hi,

I was wondering if anyone experiences high ram usage which results in launcher having to reload when hitting the home button? I notice this when running custom kernels but not sure if it's kernel related or can be due to our phones being older.
[One (M7) Original Android Development] matitorres07:
I was an enemy of dt2w because in my old HTC onex it was a great battery drainer, but I recently moved to m7 after s4 and I got to say that I have incredibly battery life, I tested all variants with and with out s2w and dt2w and I haven't notice any difference I'm on bulletproof right now, but I reached excelents stats with elemental too.

---------- Post added at 05:58 PM ---------- Previous post was at 05:46 PM ----------

Our phone gettin older? You are over reacting man, you have the arrive of the m8 desease, not kernel related not experiencing that issue.
[One (M7) Original Android Development] donmarkoni:
Could be... This is old phone... Only 2GB of RAM, just 4 cores running at under 2GHz...

Or it could be some rogue process or application eating up your memory... ;)
[One (M7) Original Android Development] krazyflipj:
Thanks for the info. Do you leave your phone on all day? A simple reboot fixes the issue but it happens every now and again
[One (M7) Original Android Development] matitorres07:
Phone on all day, as I said I'm on bulletproof right now, try using greenify pro to hibernate process you don't need and titanium backup to freeze them , personally think greenify it's a must have app, I'm using around 500 and 600 mb of ram with normal use.
[One (M7) Original Android Development] pavik62:
Google Play Edition Android 4.4.2

ElementalX-m7-11.7

Does Kexec?
[One (M7) Original Android Development] flar2:
You have tons of free RAM. You shouldn't worry about RAM, it's exactly the same as on stock with my kernels and it's there to be used. I ran my phone for 12 days without rebooting up until last week and it was fine, no redraws of the ui or anything. If I didn't have to test new kernel builds I would never reboot.
[One (M7) Original Android Development] flar2:
Update!

Added SweepUp2wake. Sweep up from the bottom centre of the screen to wake. I started to get used to this motion on the m8, so decided to add it to m7.

Download (For Sense 5.5/Sense 6 Android 4.4.2):

ElementalX-m7-14.2

Changes:

-add sweepup2wake

-make wake vibration more immediate
[One (M7) Original Android Development] matitorres07:
Oh man you're the best
[One (M7) Original Android Development] tiny4579:
I'm havng issues triggering it. I've been trying several times but sweepup2wake doesn't wake the screen. Is there any special trick to sweeping from the bottom? I tried from off screen and from near the logo button both halfway up the screen and all the way. I wonder if it's just me.

Any news on making these m8 gestures work with the Sense 6 ports just out of curiosity?
[One (M7) Original Android Development] FauxAffliction:
Same here..sweep up doesn't seem to be triggering for me either.
[One (M7) Original Android Development] flar2:
starting at the HTC logo, swipe straight up about an inch and a half. Maybe I made the area too small.

For the Sense 6 gestures, the userspace part stops listening when it doesn't find the sensors it's looking for, so they don't work.

There is a way to make it work, but I would need someone working on the userspace side. I could create an input device that sends an input event for each gesture, the userspace part would need to listen for these events and do the appropriate action. If anyone wants to write the userspace part (I imagine a service listening for input events), I can do the kernel work.
[One (M7) Original Android Development] Lo_RaT_PeNaT:
I've tried several times, but still wake up the screen, waiting for solution, I like this way to wake up The screen will, maybe it is safer than dt2w.
[One (M7) Original Android Development] dupel:
Indeed, hard to get the swipe the screen working. Out of 10 times maybe I get it right 2 times.

Plus it's not just the screen, but the HTC logo too (I guess that's how you made it to work)
[One (M7) Original Android Development] Mikanoshi:
Not a single time wake up succeeded for me :) Maybe because my htc logo is not working at all, even Logo2Menu/Wakeup never works for me...

Is it possible to modify Sense 6 services to listen properly? I can make an Xposed module, it will be better than standalone service. If Sense 6 has a code already that captures those events, then it is possible to add any gestures directly to it.

It will be perfect to have a wake up gesture as a swipe up from bottom to top screen half. I added a swipe up gesture in Sense Toolbox on home screens and assigned device sleep to it, with swipe up 2 wake the same gesture could do both actions, that would be cool :)
[One (M7) Original Android Development] tgeza:
Strange thing is that i already did this process with a previous One (got replaced of course due to camera problems) and i didnt have any such problems then.

In the end I didnt find an RUU for my phone and i flashed a stock rom+firmwares+stock splash screen.

Still, thanks for the help
[One (M7) Original Android Development] Achraf4X:
Some feedback about sweepup2wake, it doesn't really work, from time to time only, compared to DT2W or S2W which work flawlessly, but those two are already enough for me and got used to them, thanks for that awesome kernel, never failed me once.
[One (M7) Original Android Development] rbrandser:
Sweepup2wake is working fine here. But I must sweep from the t in the logo. Sweeping with my right thumb works best, and makes one handed use of the phone easier. Very nicely done! Thank you.
[One (M7) Original Android Development] flar2:
I think the sweep area is just too small. On the m8 it works anywhere on the screen, not sure how that will fly here but I may try it.
[One (M7) Original Android Development] flar2:
Maybe it could work. I've never looked into the exposed framework, so I don't know what the capabilities are.

I haven't talked to any Rom devs about nodding the existing service, I'm not sure what work they might be doing.
[One (M7) Original Android Development] Mikanoshi:
Xposed can mod everything that is java, absolutely everything, from system services to signature permissions. If it is not JNI, then it can be changed. But even for JNI there are java wrappers that can be used.

So, just make data available (is it /dev/input/event3? current kernels stop passing x and y coords while sleep) and I'll figure something out :)
[One (M7) Original Android Development] flar2:
Right now the wake function doesn't create a separate input device, it just calls the power button.

I was thinking of creating a new input device and having a different key code for each gesture ( sweep left, sweep right, sweep up, sweep down, doubletap). Then a different action can be assigned to each. For example, sweep right would go to blink feed, sweep up would unlock, etc.

Does that sound like something that is possible?
[One (M7) Original Android Development] Mikanoshi:
I never tried getting data directly from input device. I think it is possible, but I thought about getting xy coordinates of current touch so any gestures can be coded in java, that way we can create new gestures as easy as in regular apps. event3 is already emitting xy coords, but it stops when screen is off.
[One (M7) Original Android Development] flar2:
Is it giving you -10 as the coordinates?
[One (M7) Original Android Development] Mikanoshi:
With screen on:

root@m7:/ # getevent -lt /dev/input/event3
[ 32269.342922] EV_ABS ABS_MT_TRACKING_ID 00000380
[ 32269.342922] EV_ABS ABS_MT_TOUCH_MAJOR 00000052
[ 32269.342922] EV_ABS ABS_MT_POSITION_X 000004f4
[ 32269.342922] EV_ABS ABS_MT_POSITION_Y 0000060b
[ 32269.342922] EV_SYN SYN_REPORT 00000000
[ 32269.406252] EV_ABS ABS_MT_TOUCH_MAJOR 00000051
[ 32269.406252] EV_ABS ABS_MT_POSITION_X 000004bb
[ 32269.406252] EV_ABS ABS_MT_POSITION_Y 00000610
[ 32269.406252] EV_SYN SYN_REPORT 00000000
[ 32269.414676] EV_ABS ABS_MT_WIDTH_MAJOR 00000009
[ 32269.414676] EV_ABS ABS_MT_PRESSURE 00000009
[ 32269.414676] EV_ABS ABS_MT_POSITION_X 000004a9
[ 32269.414676] EV_ABS ABS_MT_POSITION_Y 00000611
[ 32269.414676] EV_SYN SYN_REPORT 00000000
[ 32269.423221] EV_ABS ABS_MT_TOUCH_MAJOR 00000052
[ 32269.423221] EV_ABS ABS_MT_POSITION_X 0000048f
[ 32269.423221] EV_ABS ABS_MT_POSITION_Y 00000612
[ 32269.423221] EV_SYN SYN_REPORT 00000000
[ 32269.431736] EV_ABS ABS_MT_TOUCH_MAJOR 00000051
[ 32269.431736] EV_ABS ABS_MT_POSITION_X 00000474
[ 32269.431736] EV_ABS ABS_MT_POSITION_Y 00000614
[ 32269.431736] EV_SYN SYN_REPORT 00000000
[ 32269.440252] EV_ABS ABS_MT_POSITION_X 0000045c
[ 32269.440252] EV_ABS ABS_MT_POSITION_Y 00000615
[ 32269.440252] EV_SYN SYN_REPORT 00000000

With screen off:

root@m7:/ # getevent -lt /dev/input/event3
[ 32398.353421] EV_ABS ABS_MT_TRACKING_ID 00000383
[ 32398.353452] EV_ABS ABS_MT_TOUCH_MAJOR 00000052
[ 32398.353452] EV_ABS ABS_MT_WIDTH_MAJOR 00000008
[ 32398.353452] EV_ABS ABS_MT_PRESSURE 00000008
[ 32398.353452] EV_ABS ABS_MT_POSITION_X fffffff6
[ 32398.353452] EV_ABS ABS_MT_POSITION_Y fffffff6
[ 32398.353452] EV_SYN SYN_REPORT 00000000
[ 32398.387116] EV_ABS ABS_MT_WIDTH_MAJOR 00000009
[ 32398.387116] EV_ABS ABS_MT_PRESSURE 00000009
[ 32398.387116] EV_SYN SYN_REPORT 00000000
[ 32398.420871] EV_ABS ABS_MT_WIDTH_MAJOR 00000008
[ 32398.420871] EV_ABS ABS_MT_PRESSURE 00000008
[ 32398.420871] EV_SYN SYN_REPORT 00000000
[ 32398.463844] EV_ABS ABS_MT_TOUCH_MAJOR 00000051
[ 32398.463844] EV_SYN SYN_REPORT 00000000
[ 32398.472115] EV_ABS ABS_MT_TOUCH_MAJOR 00000052
[ 32398.472115] EV_ABS ABS_MT_WIDTH_MAJOR 00000009
[ 32398.472115] EV_ABS ABS_MT_PRESSURE 00000009
[ 32398.472115] EV_SYN SYN_REPORT 00000000
[ 32398.480600] EV_ABS ABS_MT_WIDTH_MAJOR 00000008
[ 32398.480600] EV_ABS ABS_MT_PRESSURE 00000008
[ 32398.480600] EV_SYN SYN_REPORT 00000000
[One (M7) Original Android Development] flar2:
I might be able to give proper coordinates when the screen is off, I just have to create a different notifier for phone calls, to prevent touches when screen is off during phone calls.

The other idea I had, creating an input device and assigning a code for each gesture, would look something like this:

EV_KEY GESTURE1 DOWN
EV_SYN SYN_REPORT 00000000
EV_KEY GESTURE1 UP
EV_SYN SYN_REPORT 00000000
[One (M7) Original Android Development] Mikanoshi:
If Android can get those codes in its java classes, then it will also be easy. I just don't want to read input devices directly, it will most probably require root and a standalone service.

With this method you'll have to implement all gestures youself, plus even super secret unlocking by tapping/swiping in particular areas will be possible with this mod and it can be done only using java.
[One (M7) Original Android Development] matitorres07:
Awesome greats ideas hope you can make this, thanks for everything!
[One (M7) Original Android Development] flar2:
[MENTION=5386198]Mikanoshi[/MENTION] [MENTION=3699616]mwilky[/MENTION] [MENTION=1186202]baadnewz[/MENTION] [MENTION=1225716]Turge[/MENTION] [MENTION=1631739]mike1986.[/MENTION] and anyone else who might be interested

This is a start on motion gestures. It needs userspace assistance (a service or xposed module or something). Various screen gestures could be mapped to specific Android actions (eg: sweep right could open blinkfeed, sweep up could unlock, etc). This would be like the motion gestures on the m8. You need to install this kernel: http://www.androidfilehost.com/?fid=23329332407589460

*Note to users: don't install this kernel unless you want to do some hacking. These gestures won't do anything without userspace stuff

Touchscreen coordinates are now available when the screen is off. I also created an input device called "wake_gesture" that generates the following codes for the each gesture when the screen is off:

00000001 -> sweep right

00000002 -> sweep left

00000003 -> sweep up

00000004 -> sweep down

00000005 -> doubletap

00000006 -> logo2wake

For example, if I sweep left to right across the screen, the following input event is generated:

adb shell getevent -lt /dev/input/event4
[ 97.560570] EV_REL 000b 00000001
[ 97.560570] EV_SYN SYN_REPORT 00000000

Let me know if you're interested in working on this and if I need to change anything.
[One (M7) Original Android Development] mikrosmile:
For now the default HTC's method to identify gestures is the numbers.

this is send when any gesture is performed.

Intent intent = new Intent("com.htc.intent.action.EASY_ACCESS");

intent.putExtra("easy_access_action", i);

sendBroadcast(intent, "com.htc.permission.APP_DEFAULT");

where "i" is the motion in numbers:

1 - Swipe up

2 - Swipe right

3 - Swipe left

4 - Landscape camera

5 - Double tap

6 -Swipe down

The question. How to get the intent from kernel?
[One (M7) Original Android Development] B BOY DRAW2:
Hmmm....feels like I'm getting some overheating on 14.2 that I wasn't getting in 14.0, so I've reverted back.

Anyone else?

Could be coincidental, but I couldn't exit The Walking Dead game using the back button on 14.2, where as I could on 14.0 as well.

Just putting it out there...otherwise I'm loving 14.0.
[One (M7) Original Android Development] Mikanoshi:
Kernel doesn't do intents)

What java class sends that intents? Cannot find it in main system frameworks/services...
[One (M7) Original Android Development] mikrosmile:
Ok, just asking as i dont know the kernel stuff. Anyway, how do we get which motion is performed in the app?

This is from EasyAccessService.apk
[One (M7) Original Android Development] Mikanoshi:
I'm trying to find where android services get their input events (native libs read directly from /dev/input/event and provide data for java class).

Still no luck. I found a method that receives MotionEvent at any time, but it stops when screen is off. Instead of input events java class triggers this: com.android.internal.policy.impl.interceptMotionBeforeQueueingWhenScreenOff(int). If it is a java limitation, I could bypass it, but if it is in native libs, then things will be a lot harder, we'll have to write our own lib to read events or read directly from devices and interpret X/Y coordinates as swipes for custom gestures. Reading wake_gesture device for predefined gestures is easier though.

This is all available sensors:

AK8963 3-axis Magnetic field sensor
AK8963 3-axis Magnetic field UNCALIBRATED sensor
BOSCH BMA250 3-axis Accelerometer
BOSCH BMA250 Signifcant Motion Sensor
CM36282 Proximity sensor
CM36282 Light sensor
R3GD20 Gyroscope sensor
ST 9-axis Orientation Sensor
ST Rotation Vector
ST Linear Acceleration
ST Gravity
R3GD20 Gyroscope sensor Uncalibrated
ST Game Rotation Vector
HTC Gesture sensor

but EasyAccessService listens only for this:

String s = sensor.getName();
if (s != null && s.equals("hTC Gesture_Motion"))
mHtcGestureMotionSensor = sensor;
else
if (s != null && s.equals("hTC Matrix Gesture"))
mHtGestureMatrixSensor = sensor;
else
if (s != null && s.equals("hTC Matrix Gesture HIDI"))
mHtcGestureMatrixHidiSensor = sensor;
else
if (s != null && s.equals("hTC Gesture Motion HIDI"))
mHtcGestureMotionHidiSensor = sensor;

event4 is not sending this for me, is it for swipes on buttons?