yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] FuMMoD:
Yes yes yes!
[Nexus 5 Original Android Development] rogem_kk:
I am on Nov 17 kernel and none of these things work? I have the KControl app too.
[Nexus 5 Original Android Development] show-p1984:
Those features are available in BETAS only, as clearly stated in the first post and in all other posts.
[Nexus 5 Original Android Development] davelikestacos:
Anyone else experiencing the min freq being reverted to 960000 by itself? This is on the 11/20 beta.
[Nexus 5 Original Android Development] show-p1984:
After thermal throttling occured?

cat /sys/kernel/msm_thermal/stats/*
[Nexus 5 Original Android Development] wera750:
Double tap working good so far. I have to enable s2w to be able to s2s. Will that change in the future?
[Nexus 5 Original Android Development] show-p1984:
In the future everything will change.

I could add a minor code modification to allow s2s without s2w.
[Nexus 5 Original Android Development] vegas217:
There are 2 downloads on the beta page that were uploaded/updated today. How do I know which one to install?

1)

20131120_050104_exp-7a040c3.zip	e14f7d4...7a040c3	931d95a778186029cdfe152b2172177232e96cbe 5ced5cf497f74e05a26efb13d41864c2

2)

20131120_043310_exp-e14f7d4.zip	cdc15b8...e14f7d4	f78ae14a633d92d13c8cc1b52e13ff3bb36fe3b7	14f9385fca9305dfa6fcfc4fd301d564
[Nexus 5 Original Android Development] show-p1984:
Seriously?

Have a cloooooosseeee look at those numbers in the beginning. Could it be date & time?

btw: Newest = top.

That list is automagically generated by one of my php scripts. I most certainly don't write it myself and even if I would write it myself I wouldn't put the newest kernel right in the middle just to confuse people.
[Nexus 5 Original Android Development] ethantarheels123:
is there any way to change the double tap speed? Lol, I think we all have faster fingers than the minimum recognized speed right now :P
[Nexus 5 Original Android Development] vegas217:
Just getting confirmation. I haven't downloaded from this dev before...Thought I would check with the community beforehand. Thanks.
[Nexus 5 Original Android Development] show-p1984:
There is no minimum recognized speed. Only a maximum: 700ms.

Be sure that you are on the last beta kernel (20131120_050104_exp-7a040c3) since the previous one had a dt2w issue I swiftly fixed.
[Nexus 5 Original Android Development] theesotericone:
LOL. You just quoted "this dev"

OT: Knock Knock. You rock. lol Nice work with this. I'm looking forward to show and faux and franco combining their stuff. Really enjoy when devs respect each other. So my respect to all of you.
[Nexus 5 Original Android Development] shawnaye:
BUT I WOULD WALK 500 MILES AND AH I WOULD WALK 500 MORE!
[Nexus 5 Original Android Development] shaker2k:
Does Kcontrol have enable knock option yet(just bought it ;)) also on your kernel I made it past 21‰ on antutu.

Edit : nevermind figured it out.
[Nexus 5 Original Android Development] ethantarheels123:
would knock knock to sleep be hard to implement? Maybe it could recognize the taps in the same regions as s2s? i.e. the navigation button bar, so like maybe we could double tape anywhere across the navigation bar to go to sleep?
[Nexus 5 Original Android Development] Deegan87:
Flashed newest beta, and dt2w is not showing up in kcontrol. It still thinks s2w is version 1. Am I missing something? I dirty flashed the new kernel over the beta from Nov 18.
[Nexus 5 Original Android Development] show-p1984:
That would be generating soooo many false positives.

KControl has no option for that, yet. Tomorrow. :p

S2w is still version 1(.5), so KControl is correct. When the algorithm of s2w2 is finished that section will change completely.
[Nexus 5 Original Android Development] DevShaft:
You can always use GMD gesture control for this, available in store.
[Nexus 5 Original Android Development] thejonesyboy:
Yep same here. With s2w and/or dt2w enabled, while in the dialer and the proximity sensor covered, the screen registers touches as if the display were on. This doesn't happen anywhere else as far as I can tell, so it must only be an issue with the dialer proximity sensor display off.
[Nexus 5 Original Android Development] george241312:
I am pleased.
[Nexus 5 Original Android Development] akaHardison:
Come on,is that very necessary?Maybe they overclock.You can overclock your phone.Note3 has 3gb ram so it gets high score.But right now,I UV and uc.The system still smooth.And it saves lots of battery.Of course you can buy a note3,but about system update.I only can say:haha.

If you don't like your phone just sell it and buy another phone
[Nexus 5 Original Android Development] vegas217:
sysfs?

I am new to editing sysfs. How would one 'activate through an app or over sysfs: echo 1 > /sys/android_touch/doubletap2wake' ?
[Nexus 5 Original Android Development] noonecanhide:
I tried to flash the latest stable Kernel with cwm over cm11-unofficial, resulting in a bootloop of the bootloader (Google Logo appears, then reboot). Do I need to flash the stock Boot.img as cm11 contains a own Boot.img?
[Nexus 5 Original Android Development] george241312:
You got the wrong idea i was not angry with the result i was happy...
[Nexus 5 Original Android Development] MontAlbert:
the s2w setting in the K-Control app does not hold over on a reboot even though i have set it. Anyway, changed my mind, i have nav bar hidden and leaving this on causes me to lock my phone whenever i scoll the dock..lol...

using tasker to turn dt2w on at each boot as that doesn't hold over from a reboot either (not sure if that is standard)

thanks for a great addition. Faux has said he uses your s2w implementation.

I know it is early days but will this get faux sound (which is still beta for this phone as i understand it)?
[Nexus 5 Original Android Development] PippoX3:
[MENTION=1320503]noonecanhide[/MENTION]: Flash the "bricked_uninstaller_hammerhead.zip" in 1st post (& wipe caches) otherwise perform a dirty flash of your rom (& wipe caches).

[MENTION=396102]MontAlbert[/MENTION]: For S2W, you have to set "Apply settings on boot" into KControl settings. And for DT2W until app allow to setup, you have to launch every time or make a script that launch on every reboot.

[MENTION=5088877]vegas217[/MENTION]: connect your device to usb and use adb.

Type:

"adb shell"

"su"

"echo 1 > /sys/android_touch/doubletap2wake"
[Nexus 5 Original Android Development] ilbert:
I solved the reboot problem with a script
[Nexus 5 Original Android Development] MontAlbert:
i did mate- that's what I',m trying to say. I have it ticked inside K-control but it turns itself off on reboot.
[Nexus 5 Original Android Development] PippoX3:
You have to turn two slides, inside options... "set on boot" and "sweep to wake" ...
[Nexus 5 Original Android Development] MontAlbert:
did that too. doesnt worry me- not using s2w anyway.
[Nexus 5 Original Android Development] PippoX3:
I understand... in my case KControl, after a reboot, spend about 40 sec. to obtain Superuser rights. Only then S2W is active. Otherwise it don't works.
[Nexus 5 Original Android Development] Alpione:
Dt2w works great. Battery drain overnight was almost 3%/hour rather than normal 1% or so. To be expected at this point.

A
[Nexus 5 Original Android Development] davelikestacos:
Loving this kernel. On the 11/20 beta, here's my first run of AnTuTu: http://i.imgur.com/21wR7HG.png
[Nexus 5 Original Android Development] Starymari:
Hi all! I totally love this kernel but I'm having a hard time enabling sweep2wake and doubletap2wake... I'm planning on buying the kcontrol app tomorrow but was wondering if anyone could give me a little run down on how to do it myself...? Sorry for the dumb request. OP - Thanks for this kernel and your time making it amazing!
[Nexus 5 Original Android Development] globen:
Awesome work on the latest beta. One question, when I'm on a phone call the proximity sensor blacks the screen out but If my face touches the screen it activates the buttons.. like hanging up on someone. I realize this happens because of the screen wake features, but just wanted to know if this would ever be rectified?
[Nexus 5 Original Android Development] miesa:
Had random reboots suddenly this evening. Used the uninstall script and reverted to stock Rom. Works fine now. Last kmsg here

https://docs.google.com/file/d/0B7JCw9FX-2LLRFFVMEt3WUVpV1U/edit?usp=docslist_api
[Nexus 5 Original Android Development] shadrach47:
My phone also sets min to 960, I change it and it goes right back. Don't have KControl installed.

When running cat /sys/kernel/msm_thermal/stats/* I get:

0

low 0

mid 0

max 0

Anything else to check? Thanks
[Nexus 5 Original Android Development] nobnut:
Until you get the app, just download and unzip the attached file. Paste the contents to /system/etc/init.d and set the file permissions to rwxr-xr-x

and then reboot.

The very first time you try to wake the device from a fresh boot you may have to use the button. But each subsequent sleep and wake can be executed using the screen :)

EDIT: Upload failed for some reason :(

Just create a blank file in the above folder and paste the following into it:

#!/system/bin/sh

echo 1 > /sys/android_touch/doubletap2wake
echo 1 > /sys/android_touch/sweep2wake

Name the file something like '90wake'

Once you have the app installed, you can delete this file.

EDIT 2: File now attached :)
[Nexus 5 Original Android Development] show-p1984:
Android isn't sending off the boot trigger earlier. Nothing I can do about that. :(

That's what I needed. Seems to be a rare touch boost issue then. I will check the algorithm tonight.

You would be the first ever experiencing a random reboot on bricked. By the way, would be great if you could enable access to that Google drive file next time...
[Nexus 5 Original Android Development] miesa:
Uh enabled it. Forgot about that. Anyway I was using qi charger mount in my car and apparently it got quite hot. I'll remember not to use that when the weather here is hot

it's exceptionally hot here today. I was on v17 using Waze to navigate when the reboots started and didn't save the last kmsg. Flashed beta 20 when home to see whether it still happens.
[Nexus 5 Original Android Development] show-p1984:
You are crazy right? :)

When its hot outside you don't leave your electronics on the table in the sun and you most certainly don't leave electronics in the hottest place you could imagine, your car, in the sun.

One thing you absolutely don't do even if the above is true is charging your phone under those conditions. Every electronics device has a specification of what you can or can't do with it, and charging it with an ambient temperature of 40-45 degrees Celsius will most certainly lead to abnormal behavior in any device.

I will look at the file you enabled access to when I am back home.

EDIT:

I took a quick peak at the first few lines. That kmsg is from stock kernel and not use able as such.
[Nexus 5 Original Android Development] show-p1984:
That's the input boost (aka most hacky thing I have ever seen).

What happens is this: (try to follow the chain)

The !kernel touchscreen driver detects and processes a touch and sends it to android. Android now reacts with it's power hal and sends the input boost notification to the mpdecision binary. The mpdecision binary starts the input boost by instructing the !kernel to boost the min freq. After a specified time, the mpdecision binary removes the boost by instructing the !kernel to do that again.

If you followed it closely you will notice that we went outside of the kernel, to jump through 2 hoops and then come back to it. Twice.

As a normal human being you are baffled. Everyone should now ask themselves:

Why?

That's pure insanity.

On bricked:

The kernel touchscreen driver registers the touch.

My msm_mpdecision has a callback that is now called, with the name of the device that triggered this input event. If it matches a predefined list (containing 'touch' in it's name in this case) it will boost the freq inside of the kernel. After a time it is unboosted inside of the kernel again.

So we didn't go outside of the kernel ONCE.

We saved 2 steps along the way.

(and we are not even talking about how often this occurs. If you swipe or keep your finger on the screen there are 5-20 touch events each second. Depending on the touchscreen there could easily be more.)

Why is there an error spammed?

Because I don't push a modified power hal anymore to patch out the mpdecision binary input boost. That breaks compatibility with other kernels that still use that crap. So I keep it. So android will complain about that path not being existent.

Btw: By the sheer number of power hal request errors you can also see how often this occurs. It's just a waste of resources.

Why doesn't Qcom do this inside of the kernel?

Most probably because all kernel code is subject to GPL and some lawyer felt the need to protect that apparently super secret sauce and forbid the developers to disclose it. Which sucks. But we can work without their source, as my msm_mpdecision proves.

Nope.

Android has no knowledge about when and how the throttling occurs or even what the system temperature is. It doesn't care and it is right not to do so. That is either system stuff (bios) or kernel stuff. It does not belong in userspace.
[Nexus 5 Original Android Development] ealvinito:
Kernel running great!

---------- Post added at 09:33 PM ---------- Previous post was at 09:26 PM ----------

Sorry probably a noob question but when you click on download it goes to a landing page of 4 links. What's the difference. Any?
[Nexus 5 Original Android Development] Emilius:
Oh yes, killer kernel is here. Knock knock is coming? nice!!! One question... Why is "Ok Google" not working on screen off. Any help from kernel side? Cold you make it listen all the time?
[Nexus 5 Original Android Development] show-p1984:
Different releases. Top is the most recent (as seen by the dates).

You can click on the 'changes'-links to get a diff between them directly from my github repo.

No. that's disabled inside Google's Now app and supposed to be that way. It even disables on low power: https://plus.google.com/u/0/108262968419038009038/posts/UeWZi4EAApr
[Nexus 5 Original Android Development] franciscofranco:
Absolutely.
[Nexus 5 Original Android Development] Striatum_bdr:
Is there a way to avoid modifying system files or at least having an uninstall zip to restore original files?

Would be more simple to go from your kernel to others.
[Nexus 5 Original Android Development] ganeshp:
[MENTION=4195844]show-p1984[/MENTION] ahh finally I got to run this kernel on my device after pyramid...great kernel as always ....and im just waiting for my credit card to arrive to purchase your app :) (my debit card sucks ..the playstore purchases not happening anymore :/ )

OT: I was all there in your bricked IRC channel lurking and secretly testing the pyramid kernel when you have first written that mpdecision code where your dear friend [MENTION=3640615]hlenforcer[/MENTION] is testing all the iterations of it and posting kmsg's :D
[Nexus 5 Original Android Development] psxsnake:
why your stock boot image are 22mb instead than 8mb from other N5 stock?
[Nexus 5 Original Android Development] montbazon:
Aroma installer + his high optimized code
[Nexus 5 Original Android Development] show-p1984:
Due to this kernels high optimization level I had to export some drivers as modules in order to get a zImage that still fits inside our boot IMG. (Speed optimized code is usually larger)

Those modules have to contain debug information:cool: so useful information is created in the unlikely event of a crash, hence they are quite big.

The modules are pushed to /system/lib/modules and will not interfere with any other kernel. (They can only be loaded on the bricked kernel version they were compiled for)

Just btw, the zips are not 22mb, but rather roughly 11.

The only system files modified are mentioned during install and in order to ensure normal operation I can't divert from that.

(2 files in /system/bin are renamed to be disabled: qcoms mpdecision and qcoms thermal daemon)

I can cook up a reset zip to revert those changes.
[Nexus 5 Original Android Development] Striatum_bdr:
Yes I understood that fact, but renaming back those files manually to flash Faux123 kernel for example will ensure you many questions...

Thanks anyway you're very kind.
[Nexus 5 Original Android Development] bkeaver:
figured I'd give this Kernel a shot :) Lets see how well this plays with my phone.. :good:
[Nexus 5 Original Android Development] psxsnake:
sorry i meant stock not your kernel...becouse i come from franco one and I wanna try your...so before have to flash stock boot img
[Nexus 5 Original Android Development] bkeaver:
i came from Franco's kernel and just flashed this without the extra boot img file and am ok...
[Nexus 5 Original Android Development] GCbard:
Great kernel! I take it that GPU control has not yet been implemented.....
[Nexus 5 Original Android Development] show-p1984:
There have been a few driver changes. Once I adapted the kcontrol module all should work perfectly.
[Nexus 5 Original Android Development] SetiroN:
Any chance for a CAF kernel?
[Nexus 5 Original Android Development] IAmAN00bie:
Your awesome app was the biggest reason for me switching to your kernel on the nexus 4. Glad to see the support for the nexus line continue!
[Nexus 5 Original Android Development] bkeaver:
so far so good with this kernel. This is kind of light usage so far but way better than I was getting with almost any other kernel.
[Nexus 5 Original Android Development] drdrewdown:
Same here. so far so good & much better than the other kernels I've tried
[Nexus 5 Original Android Development] miesa:
I normally drive long distance at night so got used to charging while using GPS :cyclops: A bad habit I know~

Edit: It's from stock? I did flash stock when it rebooted and then only I saved the last kmsg. I'll read more on how to save the last_kmsg properly and test the kernel again later to see if it happens. If it doesn't then it's most likely the heat and it just so happens to have cooled down when I flashed stock. Anyway no issue at all before this not even when I tried overclocking for a bit and later on undervolting for a while.
[Nexus 5 Original Android Development] keda51:
When attempting this above I get : Permission denied

Any ideas?
[Nexus 5 Original Android Development] edisepic:
I flashed this kernel for the sweep to wake which is cool. I bought the kcontrol app too. is there ways to make adjustments to how the sweeping works
[Nexus 5 Original Android Development] nobnut:
See this post :)

http://xdaforums.com/showpost.php?p=47643867&postcount=355
[Nexus 5 Original Android Development] scottdouglasdick:
Does this kernel work fine when using "ART"? Also, what are people scoring in geekbench 3?

Thanks!
[Nexus 5 Original Android Development] hotnikkelz:
kernel has nothing to do with ART

How do i activate dt2w without using the app. I currently use and like performance control app (somewhere in the forums) Thanks in advance
[Nexus 5 Original Android Development] cgjjaf:
I followed the instructions but I can't get it to work, any suggestions? Thanks.
[Nexus 5 Original Android Development] nobnut:
Pre-requisite - make sure you are using that latest beta kernel version which you can download from here (top link)

1. Download the zip file attached to that post I made earlier.

2. Extract the file inside it.

3. Paste a copy of that file into the folder /system/etc/init.d/

4. Change the file permissions to 'rwxr-xr-x' using Root Explorer or whichever other file manager you use.

5. Reboot, then wait for 30 seconds or so. You will find it works just fine.
[Nexus 5 Original Android Development] show-p1984:
You forgot that one needs to have busybox installed in /system/xbin for this to work. :)
[Nexus 5 Original Android Development] ethantarheels123:
You need to use a root browser, go to sys/android touch/dt2w and change value 0 to 1

Edit: Oops,wrong quote
[Nexus 5 Original Android Development] cgjjaf:
Thanks, that did it.
[Nexus 5 Original Android Development] nobnut:
Doh!
[Nexus 5 Original Android Development] scottdouglasdick:
Delete
[Nexus 5 Original Android Development] Nickamina:
Read before you post. Please. I could cry...
[Nexus 5 Original Android Development] n3ocort3x:
[MENTION=4195844]show-p1984[/MENTION]

MAn i really have to thank u here for ur aweseome touchscreen magic. again u have outdone urself and the new implementation is just aweseome and even i guy like me can track things on how u commit on gihub. Its really nice to know a guy like u and i´m really looking forward to ur next big bangs OBI ONE :)
[Nexus 5 Original Android Development] FlolB:
Hi, nice kernel. Can you include s2s? I miss it. :D Very nice work.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] AndroidKills:
wow insane kernel, just bought the app and all too.

Was wondering if it would be possible for a double tap to lock or something thatd be awesome :3

edit - thanks [MENTION=5372360]magnamentis[/MENTION], that does seem pretty ridiculous and full of hassles.
[Nexus 5 Original Android Development] magnamentis:
this has been answered a few post before yours :)

http://xdaforums.com/showpost.php?p=47643867&postcount=355
[Nexus 5 Original Android Development] FlolB:
with trickster mod you can activate all the funktion.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Remoteconcern:
Loving sweep2wake. I know this has been mentioned by showp as an idea but I would just like to say I would love to have swipe2wake enable only when charging...would work amazingly with my wireless charger but I like to maximise battery life elsewhere.
[Nexus 5 Original Android Development] ahfunaki:
When I try this it won't let me save the file? Anything special that needs to be done?
[Nexus 5 Original Android Development] paul_59:
Just out of interest how did you achieve that score ?

Was ROM stock and only kernel custom, if so could you detail your settings and indicate if that is a repeatable score.
[Nexus 5 Original Android Development] NineInchNails:
Latest betas I cannot get to boot up. 11/18 works fine but dirty flashed or fresh flashed, over top nand restore, using uninstaller and not. Still no go. Just reboot to Google startup.

Fixed by using TWRP recovery.
[Nexus 5 Original Android Development] show-p1984:
Works fine. There were some issues reported with CWM. For some reason it sometimes garbles the ramdisk and the kernel cannot read it on bootup.
[Nexus 5 Original Android Development] Cyberz22:
just flashed the 20131120_050104_exp-7a040c3.zip and it stuck in a loop
[Nexus 5 Original Android Development] NineInchNails:
That's probably my issue then. Twrp it is

Edited. Confirmation that CWM was the issue.
[Nexus 5 Original Android Development] Alfonso87:
Same kernel installed here, and no loop. Have you got any ROM on your n5? mine is stock. Don't forget to flash the stock kernel-->boot-->recovery->flash brickedK. I had some trouble with EleX too while tried to flash on other kernels.
[Nexus 5 Original Android Development] bsg411:
+1

I used trickster mod too and after flashing latest beta kernel...the section for screen wake control just appeared!! I enabled dt2w and set kernel settings and SysCtl Editor on boot, and set a 0 sec delay for activation of kernel settings.

Also locked the CPU frequency so it didn't change back to 960 after leaving the app. So after reboot dt2w stays and works pretty quickly after bootup.

My phone has had two random reboots today however and once has had the issue that someone else mentioned where while in a call the phone hit buttons that I didn't pick and made a conference call on its own!! That was crazy !! Still not quite sure if the proximity sensor made the screen come on and my cheek did it or not. I'm using the setup in my signature.

All in all this is truely an awesome kernel. Thanks to all involved.

Edit: Also of note....I could not get this kernel to flash using CWM....I eventually ended up using TWRP and it worked!!
[Nexus 5 Original Android Development] terodeg:
cant enable doubletap2wake, there is an app control?