yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Haidary.T:
I was doing stuff including web browsing, Tapatalking, phone calls, text messaging... And that's about it.
[Nexus 5 Original Android Development] C3C076:
[MENTION=4684315]flar2[/MENTION]

Playing with wake gestures and I just found out sweep right is kind of hard to trigger. If you need any info or logs just let me know.

---------- Post added at 06:11 PM ---------- Previous post was at 05:59 PM ----------

Edit: looks like sweep right requires higher swipe velocity compared to other gestures.
[Nexus 5 Original Android Development] walpurgisnacht30:
Visual artifacts?

Edit: do you mean glitch or something like that? Sorry tho, English is not my native lang.

I've been using this kernel since 0.29 and never had one, unless when I was playing around with SoftkeyZ or XGels module my screen flickers, fixed that by rebooting. IMO that's not kernel related.
[Nexus 5 Original Android Development] BabboDemonio:
Yes, I reverted back to 0.39 and all seems OK...
[Nexus 5 Original Android Development] C3C076:
[MENTION=4684315]flar2[/MENTION]

Wake gesture in effect :)

http://ceco.sk.eu.org/ex_wake_gestures.3gp
[Nexus 5 Original Android Development] bexem:
No, you're not the only one. Me too! But I have thought that the glitch is because I've overclocked (2.8Ghz) but I've just rebooted the nexus and from yesterday evening I've no glitch at all *crossedfingers* :)
[Nexus 5 Original Android Development] BabboDemonio:
Forgot to say that I used default settings, I didn't overclock
[Nexus 5 Original Android Development] flar2:
Awesome. I'll try this when I get home (will also check that right sweep motion)
[Nexus 5 Original Android Development] drawde40599:
Your phone idles with it off ? Casue Mpdecision off with THIS kernel phone dosent idle I'm watching it right now its all over the place . unless we have a different definition of idle ,my definition of idle is screen on at homepage your phone gos to 300 and basicly stays there . and comparing this kernel that was built around mpdeciosn being on and trinity that was built with it off just don't really seem like good comparison to me .they don't act the same . I just don't get how battery could be any good with it off on this kernel when freq maxed out doing anything and everything .
[Nexus 5 Original Android Development] C3C076:
This is just a video. But I'll start working on a standalone module soon. Will take couple of days as I'm too busy these days. BTW, I created WakeGestureProcessor class which can be easily used in any other xposed projects. It utilizes observer pattern so consumers implementing WakeGestureListener interface simply register themselves for receiving gesture events.

The one and only attention has to be paid in what context the processor is instantiated since event2 device node is not readable for all.
[Nexus 5 Original Android Development] flar2:
Whoops, I'm at work so didn't notice it was a video. Take your time, I'm just happy you're working on it.

Also, I was going to ask you whether WakeGestureListener listens to event2 specifically, or is there a way for it to find the input device named "wake_gesture"

The reason I ask is because there is a possibility it might not be /dev/input/event2 for everyone.
[Nexus 5 Original Android Development] jumparound246:
You're right, elementalx is working with mpdecision, trinity does not. Flar2 mentioned it some time ago that he does not recommend turning mpdecision off but i did it just to see how's it going and i like it now. The online cores "idle" if there's no work for them...at least i believe it's that way. As you can see in the picture temperatures are low although all the cores are online all the time and they do fall back to 300MHz if there's not much to do for them. Anyways, don't wanted to start a ot discussion about mpdecision.

Just wanted to point out that long screen on times are also possible with 4 online cores 24/7...[emoji12]

Edit: just reread your post. Yes, it does not idle at 300MHz but if there's on work to do for some cores they also idle in higher frequencys...at least i belief that. Frequency is not proportional to power and current.
[Nexus 5 Original Android Development] drawde40599:
I may be coming across aggressive I'm not trying to :) I'm actually interested because it dose run better with it off , are u sure your mpdecision is off ? My phones do not idle at 300 with it off they may touch 300 but never stay there like it dose with it on . can I ask how your tuning it off ? Maybe I'm doing it wrong . I've renamed mpdecion file and wasn't necessary but also the power.msm8974.so file
[Nexus 5 Original Android Development] jumparound246:
Not coming across aggressive at all [emoji111]

I just edited my post. It does not idle at 300MHz all the time, it's jumping across the lower board. I've only renamed mpdecision file and nothing else. Don't know nothing about that power.msm file [emoji16]Your should give it another go for one or two battery cycles...

Edit: oh, and trinity does also not idle at 300MHz...
[Nexus 5 Original Android Development] gut4:
Does anyone working on non xposed app for wake gestures?
[Nexus 5 Original Android Development] Geordie Boyo:
Curious to try this kernel. Heard good things about it. Which version do I flash for use with Purity ROM? Thanks
[Nexus 5 Original Android Development] rhamej:
AOSP ☺
[Nexus 5 Original Android Development] szucsgf:
AOSP
[Nexus 5 Original Android Development] nexodus:
AOSP
[Nexus 5 Original Android Development] danarama:
Looks like I'm late to answer but my answer includes a tip...
[Nexus 5 Original Android Development] C3C076:
Good point. Currently I'm only checking wake_gesture in android_touch to find out whether gestures are enabled or not.

I'm not familiar with input devices that much but I suppose there's a list of devices somewhere within userspace? Or perhaps some api? I'll have to check that.
[Nexus 5 Original Android Development] pagratios:
I am using slimkat 5.4 amd after install 0.40 reboot to google logo all the time
[Nexus 5 Original Android Development] danarama:
This combination works fine for me. Not much help, but I'm ruling out the combination
[Nexus 5 Original Android Development] pagratios:
My bad luck :p
[Nexus 5 Original Android Development] notbrodie:
try going into recovery and manually wiping /system. then reflash rom, supersu, and kernel. if it still doesn't work, then you'll have to ask the slimkat devs why they broke kernel compatability
[Nexus 5 Original Android Development] yak84:
A bad download perhaps?

I'm running this kernel with slim 5.4 without a problem.
[Nexus 5 Original Android Development] 850T5m:
Just curious as to where to find mpdecision so i could try disabling it as well. I'm curious to the results! Thanks
[Nexus 5 Original Android Development] PetritH:
did u try using trickster mod app? just swipe left 2-3 times u will see mpdecision, turn it off
[Nexus 5 Original Android Development] 850T5m:
I didn't feel like installing it lol

I just wanted to rename the file so it isn't used anymore
[Nexus 5 Original Android Development] jumparound246:
You'll find the mpdecision file in /system/bin.

Have fun [emoji6]
[Nexus 5 Original Android Development] danarama:
/system/lib/hw/power.msm8974.so
[Nexus 5 Original Android Development] jumparound246:
What does that file do? Only renamed mpdecision in /system/bin. Just curious [emoji2]
[Nexus 5 Original Android Development] notbrodie:
that one only affects touchboost. with only that file renamed, the system still hotplugs

---------- Post added at 11:33 PM ---------- Previous post was at 11:32 PM ----------

if you've renamed mpdecision, you can ignore that one
[Nexus 5 Original Android Development] danarama:
Sure. Sorry maybe I've misunderstood. The only negative of mpdecision for me is jumping to 1267 Mhz instead of keeping minimum at 300. Not sure why we'd want no hotplugging
[Nexus 5 Original Android Development] jumparound246:
For me it feels even faster with no hotplugging. At least for me there's also no noticeable impact in battery life. But the speed up could be a placebo, though. I'm also overclocked to 2,5 ghz [emoji6]

This is my last post, we should go back on topic...
[Nexus 5 Original Android Development] Geordie Boyo:
Have only ever used the Franco kernel on my N5, so giving this a go to see what performance/battery life is like.

Using the express version on Purity Rom, with no additional tweaking, etc.

Will see how it goes...
[Nexus 5 Original Android Development] FAdrums:
Anyone using it with PA? If so what's your feedback? Thanks
[Nexus 5 Original Android Development] bartolinio:
[MENTION=918677]Geordie Boyo[/MENTION] on first use you should use aroma version ;)
[Nexus 5 Original Android Development] maatsby:
I've been using version 0.40 with PA beta 7 for the past couple of days and I've found no issues.

Overnight drain with all radios (WiFi, GPS, bluetooth, mobile data) switched off is around 0.3-0.4% per hour which is acceptable.

No performance issues that I've noticed though I haven't stressed the phone heaps, just emails, calls, messaging and some googling throughout the work day.

The only extra feature I'm using is the slide to lock which is working well. I'm not using double tap to wake cos it wouldn't be worth the battery drain in my personal case, I wouldn't use it enough. Maybe if I was sitting at a desk all day.

Hope that helps!
[Nexus 5 Original Android Development] FAdrums:
Awesome dude! Thanks for your feedback! Will flash it fresh later on! Rock on dude!
[Nexus 5 Original Android Development] gpvecchi:
I tried removing mpdecision: phone is absolutely snappier, battery consumption seems not very different, during one day I assume just some % point more...
[Nexus 5 Original Android Development] Soundigy:
First cycle, stock, anyone know what's going on here?
[Nexus 5 Original Android Development] njiki11:
I'm on mahdi rom (5/25) and elementalx with a slight undervolt and backlight dimmer and the phone is strangely warm around 42 Celsius and I've only been getting about 3-3.5 hrs sot. Can someone help?
[Nexus 5 Original Android Development] mhdsanto85:
So.... Which one do you guys reccomend? 0.38 or 0.40?

thanks!!
[Nexus 5 Original Android Development] CRIME INC.:
.40

Sent from my PARANOID HAMMERHEAD
[Nexus 5 Original Android Development] boxcar8028:
where do you guys get .40? its not on the OP. is there a .40 for CM11?
[Nexus 5 Original Android Development] CRIME INC.:
Post #8461

Sent from my PARANOID HAMMERHEAD
[Nexus 5 Original Android Development] drawde40599:
Betas don't go in OP till fully tested . if your on the xda site and look in the bar before posts start u can see a message displaying latest version and were to find it .( page 847) no cm version till AOSP version leaves beta , I'd imagine soon since 40 is flawless . but don't hold me to that ;)
[Nexus 5 Original Android Development] nmlssit:
With .40 my phone can't handle 725 UV anymore! Is there any particular reason?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] jumparound246:
Have had this strange wakelocks some time ago. Don't know what fixed it, unfortunately. A reboot did not?
[Nexus 5 Original Android Development] C3C076:
OK Guys.

For those who are interested in tasting some of wake gesture goodness, Xposed module for wake gesture handling is now available.

Here's its official thread: http://xdaforums.com/xposed/modules/app-wake-gestures-v1-0-t2768266
[Nexus 5 Original Android Development] drawde40599:
Must be something that was changed within kernel , just go up to voltage u can handle most likely won't even notice a difference , or if your stuck at bootloop and thats y your saying can't handle u might wanna try booting at stable voltage then changing it after your booted it SHOULD boot doing it that way but make a backup or be prepared to have things go wrong jic ;)
[Nexus 5 Original Android Development] jumparound246:
Jup, drawde should be right. I boot up with stock voltages and change after booting to 675 since...i don't know which version, feels like for ages [emoji6]

No difference for me on latest version
[Nexus 5 Original Android Development] Mr_Comple:
Hello people!

Could you please tell me which version is the latest for CM..?

sent from a real nexus device
[Nexus 5 Original Android Development] PetritH:
. 38
[Nexus 5 Original Android Development] hanschke:
.38 cm and I can confirm that .40 dont work with nightly from today. so dont try it!
[Nexus 5 Original Android Development] SunamY:
Does viper4android don't work with 0.40?

neXu5 - TR!n!ty p0wered P@r@no!d H@mmerhe@d
[Nexus 5 Original Android Development] Tylog:
Works. Viper has nothing to do with the kernel

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] SunamY:
Ok... My fault...

neXu5 - TR!n!ty p0wered P@r@no!d H@mmerhe@d
[Nexus 5 Original Android Development] flar2:
Thanks [MENTION=5008415]C3C076[/MENTION]

Installed and so far no problems at all.

To others:

For this to work, you need version 0.40, and you must enabled "wake_gestures" and enable some gestures (eg: sweep right, left, up, down, or doubletap) during installation.

You must also install the xposed framework and the wake gestures module from C3C076 and then define some actions in the wake gestures module.

Drain is the same as with sweep2wake/doubletap2wake, so I suggest using the timeout or powerbutton feature to extend battery life.

Download (Stock/AOSP):

ElementalX-N5-0.40
[Nexus 5 Original Android Development] C3C076:
Right. Just to add. Module can detect itself whether wake gestures are turned on at kernel level and gives warning when they are not. Moreover it will enable only those gesture actions (left,right,etc.) that were chosen during kernel flash (or later set via elementalx.conf)
[Nexus 5 Original Android Development] Manuelpz:
I just want say thanks to flat and C3C076 for awesome module :eek:, I am using it work :thumbup:
[Nexus 5 Original Android Development] boxcar8028:
Thanks for the info, it's most appreciated.
[Nexus 5 Original Android Development] Co.Tibi:
I guess there's still no match for this little guy... I'm on stock ROM with el.X 0.40. Thank you [MENTION=4684315]flar2[/MENTION]
[Nexus 5 Original Android Development] Nosferatu.:
just installed this kernel. So far very smooth and stable. :)
[Nexus 5 Original Android Development] Globespy:
phone unstable since recent FauxClock update

I've been running elementalx v0.38 for a while since Faux kernels since 12-17 have been causing lag on my device.

I of course love my Faux apps, and elementalx is highly compatible with FauxClock and runs (are least for me) much smoother.

However since the FauxClock update on May27 it's been causing my phone to lock up and freeze - I saw in the new FauxClock (build 201 v2.0.1) new options in the CPU hotplug section. I have mpdecision selected as this is the required option for elemental kernel.

No other changes to phone.

I've supported all Faux apps from the beginning so just want to keep using them. I'm just wondering if anyone else might have some ideas as to why the new FauxClock might not be playing nice with elemental anymore?

Thanks.
[Nexus 5 Original Android Development] notbrodie:
I'm using fauxClock with elex. even played with the userspace hotplug. no issues with fauxClock here
[Nexus 5 Original Android Development] szucsgf:
Likewise, no issues with fauxclock here. Did you try uninstall fauxclock, reboot, reinstall fauxclock?
[Nexus 5 Original Android Development] :
Has anyone tried this kernel on an f2fs system partition? I just switched to f2fs and I'm a bit hesitant to do anything right now.

Thanks in advance for the confirmation :fingers-crossed:
[Nexus 5 Original Android Development] italia0101:
I always seem tk have audiomix wakelock, anyone else suffer from this?
[Nexus 5 Original Android Development] Alfonso87:
Wrote before my solution to that issue.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] imritechere:
magnetic on/off on nexus5 top left side of screen

can you add magnetic off when s2w or dt2w are enabled like on the nexus 7.2
[Nexus 5 Original Android Development] flar2:
You mean turn off dt2w/s2w when you turn off the screen with the magnetic case?

Or option to disable magnetic on/off?
[Nexus 5 Original Android Development] J000rg:
I think the first one, as dt2w/s2w is useless when magnetic case is closed :D

I have another question:

I will get my N5 soon and I still consider flashing a custom Kernel or not.

You could help me by answering some questions I have:

1. Are there any issues with this kernel, if @ stock settings?

2. How much is Battery drain WITH dt2w? And are there any Issues with dt2w? (Unresponsive screen, freezing etc.)

3. Random reboots? (if leaving @ stock settingts and not UV or sth.)

and last but not least:

4. If I decide to return to stock boot.img, do I just have to flash it over Elemental or do I have to use a special .zip or remove some Modules manually?

Thank you =)
[Nexus 5 Original Android Development] prinz3nroll3:
hi,

how is the battery drain with the option doubletap2wake in the newest version?

thx a lot
[Nexus 5 Original Android Development] dead0:
1. none whatsoever

2. I don't use dt2w/s2w but I managed 5hrs screen on and battery lasted over 48 hours. tis was with data on during screen on for mainly benching, web browsing, facebooking, whatsapp, sms and the odd calls

3. had no random reboots and I uv'd by -50 to -75mV

4. u can flash the stock boot over elemental
[Nexus 5 Original Android Development] J000rg:
Great, thank you, so Elemental's gonna deflower my N5 :good:
[Nexus 5 Original Android Development] shawnaye:
Still the same as before.
[Nexus 5 Original Android Development] prinz3nroll3:
that mean worst with doppeltap on?
[Nexus 5 Original Android Development] notbrodie:
yes, battery drain is significantly increased with dt2w & s2w
[Nexus 5 Original Android Development] flar2:
Yes it causes significant drain, but there are a couple things to consider.

First it depends on your usage. For my usage, I leave doubletap enabled most of the time and I still have enough battery to get me through the day.

Second, there is an option to disable doubletap with the power button. So if you turn off the screen with the power button, there is no additional drain. I always use this at night and sometimes during the day if I know I will not be using my phone for a couple hours.
[Nexus 5 Original Android Development] Primokorn:
Using ES Audio player isn't a real solution on my end...
[Nexus 5 Original Android Development] J000rg:
If this option is enabled, does ist disable t2w only if locking screen with the actual PowerBUTTON, or generally if manually locked independent on the way you do it. (e.g. I have my "back"-Key in the nav-bar to lock my screen, if longpressing it - will this also disable t2w? )
[Nexus 5 Original Android Development] shawnaye:
Hah! WRONG THREAD! :silly:
[Nexus 5 Original Android Development] flar2:
If you really want the cooler colours, that is still an option in elementalx.

A note to all:

If you plan to use the gamma control app, make sure you leave that tweak disabled. If the cooler colours option is enabled, your custom gamma settings won't stick.
[Nexus 5 Original Android Development] flar2:
No, only the power button would disable it.
[Nexus 5 Original Android Development] J000rg:
Awesome, thanks !
[Nexus 5 Original Android Development] sirbanger:
hmmm, I have cooler colors enabled and the custom gamma settings are working fine
[Nexus 5 Original Android Development] danarama:
/system?
[Nexus 5 Original Android Development] :
Sorry. Still learning the jargon.

I'm on f2fs not ext4. Can I simply flash the latest kernel?
[Nexus 5 Original Android Development] danarama:
Yes. The limitation is that you must already have an f2fs supported kernel (which if you're, you have) using f2fs
[Nexus 5 Original Android Development] :
Thanks for the help!:good:
[Nexus 5 Original Android Development] Malnilion:
Just remember that, if you want to flash ElementalX with F2FS, you have to manually mount /system in recovery beforehand.
[Nexus 5 Original Android Development] butthurtlocker:
Anyone else having their stock minimum freuquency jumping to 1.2GHz by default?
[Nexus 5 Original Android Development] flar2:
UPDATE!!!!!

0.40 works great, I made a few more experimental changes in this one, let's see how it goes.

There is now an app to control Wake Gestures thanks to [MENTION=5008415]C3C076[/MENTION] (official thread and download: http://xdaforums.com/xposed/modules/app-wake-gestures-v1-0-t2768266)

To use, you must select wake_gestures and select some gestures during kernel installation AND install Xposed and the Wake Gestures module above.

It works very well. Instead of simply turning on the screen, you can assign various actions to each wake gesture. For example, you could make doubletap unlock the phone, or sweep down turn on the flashlight, or sweep left open your browser.

It still drains battery just the same as doubletap and sweep2wake always have on this device. As always, I suggest you use the timeout feature to minimize drain.

The other change in this version is the wake_timeout no longer flashes the screen on and off

Installer has been re-arranged a bit, and some defaults have been changed.

CM/CAF version is delayed due to possible instability

Download (Stock/AOSP):

ElementalX-N5-0.41

Changes:

-new wake timeout method

-various fixes and optimizations

-stereo call recording support (untested)

-update installer
[Nexus 5 Original Android Development] drawde40599:
Stereo call recording ?

---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------

Its your app displaying it wrong ,there's more info threw out the thread . but use a app like prefmon to look at freq
[Nexus 5 Original Android Development] butthurtlocker:
Thanks guys issue solved
[Nexus 5 Original Android Development] flar2:
I have no idea. People constantly send me PMs about this, and I saw a patch in the CM m8 gerrit review. So I threw it in.
[Nexus 5 Original Android Development] drawde40599:
Gotcha , pretty sure I no what it is , sure it will make few people happy :),. 40 was really nice trying 41 now , definitely feel the improvements from 38
[Nexus 5 Original Android Development] BabboDemonio:
[MENTION=4684315]flar2[/MENTION] I noticed that in 0.41 you changed the default readahead buffer size to 256 mb. Is it better than 512 mb which was the previous default value?
[Nexus 5 Original Android Development] jumparound246:
Guess it's default for a reason...

Give both a try and decide by yourself which values are fitting better for you.

Is it just me or is scrolling in crappy tapatalk app much smoother with 0.41? Nice work, thanks flar2 and also C3C076 for your work!

Edit: back on mpdecision train, again. Never had such a smooth scrolling experience in tapatalk on dalvik. Using stock settings but 128 readahead. No issues so far, thanks again for making a good one even better!
[Nexus 5 Original Android Development] danarama:
I assume that is a Quirk of TWRP?
[Nexus 5 Original Android Development] Laggalot:
so, what if i set min freq to 300mhz in a FKU? is that problematic?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] rhamej:
[MENTION=4684315]flar2[/MENTION]

I think something got messed up with the haptic feedback. On 41, changing the default 63 to 100 has no effect at all. This is doing a flash over 38. Or it could be just me :-/
[Nexus 5 Original Android Development] danarama:
300 is the default minimum for the Nexus 5
[Nexus 5 Original Android Development] szucsgf:
OP FAQ question 2.
[Nexus 5 Original Android Development] jumparound246:
It's default if you use mpdecision.

There's no need to set with Fku or any other kernel tweaker app.

With trickster it won't stick or it also causes troubles as users reported. Have had some strange behaviour using the tkt app...

So better leave it alone after you set up with the aroma installer. Monitor your cpu with e.g. system monitor and you will see your cpu fall to 300MHz when there's nothing to do
[Nexus 5 Original Android Development] AndrasLOHF:
Scrolling is definitely much improved for me in Google+.