yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] fone_fanatic:
Franco, this guy on reddit got his N4 back with what seems to be a test/debug build on it. It's still 4.2.2 but do you think the kernel might have anything of use to you (and other kernel devs)?

From the reddit post:

Kernel Version:
3.4.0-perf-g2c26718-00003-g469a130
taeju.park@fanta #3
Tue Aug 6 09:38:09 KST 2013

Build Number:
full_mako-userdebug 4.2 LGEP19 b7db016445
test-keys
[Nexus 4 Original Android Development] franciscofranco:
Nothing to see without sources.
[Nexus 4 Original Android Development] momomok:
double tap to wake is working fine :)

also notice that a long press (about 0.5 second) will also wake the device with latest test kernel
[Nexus 4 Original Android Development] Goku80:
Anyone help to enable this please? New to terminal emulator you see. Thank you
[Nexus 4 Original Android Development] Doo Doo:
Posted By Franco

Here's another preview of the doubletap to wake feature with a bunch of code improvements over the last preview (check git as usual). Swipping to wake is disabled because instead of having swipping and double tapping together in the same code I'll be having two different options completely independent and for swipping I need more work.

The old path on this release is now obsolete because the touch_to_wake variable has changed to doubletap_to_wake:

To enable:

echo 1 > /sys/module/lge_touch_core/parameters/doubletap_to_wake

Don't double tap TOOOO fast or it won't wake up because I have a piece of code that protects against ghost touches and against consecutive fast touching. You'll get used to it, just double tap normally.

I won't be able to do Kernel work until Saturday night, tomorrow I'll be going to visit my GF so I won't dedicate any time to coding, but please leave feedback because I'll be visiting XDA to read it.
[Nexus 4 Original Android Development] dark_ente:
use root explorer, go to that folder, press on the file, choose edit and delete the N, then input 1. Save and exit, done.
[Nexus 4 Original Android Development] Goku80:
That's easier. Sweet and that's in the init folder I presume

---------- Post added at 08:09 AM ---------- Previous post was at 07:57 AM ----------

I'm completely lost now. :(

---------- Post added at 08:10 AM ---------- Previous post was at 08:09 AM ----------

I'm completely lost now. :(

---------- Post added at 08:33 AM ---------- Previous post was at 08:10 AM ----------

got it working...how can i be so stupid.....:banghead: thanks everyone for your help...so freaking easy to enable....i feel so silly and stupid...franco this is amazing feature and without TC maybe this can save bit more juice to
[Nexus 4 Original Android Development] theclaytons:
Double tap works fine and is good feature.

There a couple of oddities I found.

1. The maximum allowable time for double click is too long in my opinion. I.e you can press screen and then press it again within the timeout and the screen activates when this is not the intention.

2. Long press activates the screen
[Nexus 4 Original Android Development] Puzzlegirl:
That's easy enough to do in other ways, like with browsers that use gestures. I use Nova to swipe down to quick settings, tap Go to Sleep and job done in 2 gestures.

Franco, latest touch to wake working fine; the only thing to note is as someone else pointed out, that a single long press will wake up the device.
[Nexus 4 Original Android Development] ki2luminati:
I love the new touch to wake feature, but im having some issues. Sometimes i need to touch the screen several times before it Wakes. The same with swipe. It seems kind of unreliable to me. Im using stock rom
[Nexus 4 Original Android Development] Floydfire:
The last update of test work better but without swipe to wake...

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] :
Same issue as before for me I'll just wait for a new test version where I can enable swipe to wake only, it just turns on while in pocket and randomly makes calls and opens apps, same thing happens with Touch Control so I never use double tap to wake, back to r184
[Nexus 4 Original Android Development] saobang3886:
Agree, time between touch should shorter, and I don't like long press active :) Maybe slide to wake from left to right of far distance is better
[Nexus 4 Original Android Development] pitjago74:
Perfect doubletap here;):D

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] t0ph0id:
I've been running CM nightlies with FAUX Kernel up until today, this morning in installed Slim ROM and want to try franko kernel.

I've installed the paid updater app, and tried to install the kernel using the auto-flash method, but every time it reboots I check on the status page within the app and it still shows Slim ROM kernel. Any idea why it's not flashing correctly?

I've also tried downloading the kernel and was going to flash using ROM manager, but I can't find the download in my files. Where does it save?
[Nexus 4 Original Android Development] theclaytons:
Saves in the root of the sd card.....
[Nexus 4 Original Android Development] Serris:
So r185 is available in the updater app?
[Nexus 4 Original Android Development] theclaytons:
No, is beta or test version. Read back a few pages. There is link from franciscofranco.
[Nexus 4 Original Android Development] t0ph0id:
Ah got it, thanks.

Second question, the Slim ROM I'm using is JWR build, but the only franko kernel available to download is JSS. Are these compatiable?

Edit: Actually looks like Slim ROM is a JLS build with a JWR kernel, so I should be fine to flash JSS franko kernel?
[Nexus 4 Original Android Development] theclaytons:
You need JWR kernel, JSS not compatible. Both are available for download, check again.
[Nexus 4 Original Android Development] TheDarkDefender:
Would someone be kind enough to check if this stuff(d2w) is trickstermod configurable?

I'm aware it can be configured via terminal and scripts. Just asking.

Sent from my Nexus 4
[Nexus 4 Original Android Development] MuertoKo:
No, said many times, like really, many. It's still in testing phase so no configurable for now. Moreover, said many times franco hates using d2w acronims, call it double-tab to wake as it's intended.

Or just use search, like 10 posts about this, most in last 3 pages.
[Nexus 4 Original Android Development] TheDarkDefender:
Read the last couple of pages. Only found solutions on using emulator and init.d. Sorry,must've missed it. But definitely not 10 posts above, im on mobile,i use the app, so all I can do for now is read through pages. Last 3-4 don't have anything related to TM,else i must've skipped it or whatever.

Mod Edit: Sometimes it's best to just walk away ;)

Anyway, thanks for your input.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Taxiback:
So do we enable this with Terminal Emulator or a script manager?

Also what happened to: "Don't bother asking for this as I will ignore you: sleep2wake" A lot of people have gotten it in the neck for asking for this feature from the go get!
[Nexus 4 Original Android Development] MuertoKo:
I'm sorry but it's not my personal desire but OP's desire, I'm pretty used to s2w notation as well but as it's his thread it's good manners to fill his desires. Perhaps I should have stated even clearly before it's his will and not my personal feeling about the naming?

http://xdaforums.com/showpost.php?p=45922828&postcount=48124

http://xdaforums.com/showpost.php?p=45911521&postcount=48083

And yes, he answered about this being a test feature and not implemented in FK or similar stuff yet. Search might be choppy and it's easy to lose posts some times, Tapatalk 4 paid version works pretty nice for searching features withing the app though.
[Nexus 4 Original Android Development] TheDarkDefender:
No problem. No offense intended. I read that part. I'm aware that fku doesn't have that yet. Trickster supports it, but he has to make it configurable, which i think is what he did. Thanks anyway. Trying out now.

I think he just said that as a request and was being jovial about it. Franco isn't the serious type, lol. You might have mistaken what he was trying to say, im sure he wasn't trying to make silly rules in the thread.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Jaza78:
I do it whit script manager....Touch to wake work perfect :)

Poslato sa Nexus 4 using Tapatalk 2
[Nexus 4 Original Android Development] Serris:
Screen was unresponsive after I woke the phone, this has occured twice, duno if it has something to do with double tap to wake, or kernel itself.

I'm on latest CM10.2 nightly. Anyone any clue why this happens?
[Nexus 4 Original Android Development] XNemia:
OTG

Hello mates, is the OTG works with Franco kernel?

Thank you in advance
[Nexus 4 Original Android Development] zygis10:
No it doesn't work.
[Nexus 4 Original Android Development] soupmagnet:
Sooo...I trust this is the end of it?

Thread cleaned
[Nexus 4 Original Android Development] ciano865:
Just flashed 9.26 nightly of CM 10.2 and last JSS kernel beta (manually wipe of caches).

Double touch works fine, no issues.

from Nexus 4 with Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
1 - The max allowable time is 2 seconds starting from the first touch. I can decrease to 1 second and test.

2 - Yes, I haven't been able to find a successful way to go around it.

OEM's are starting to add this double to wake feature, and I've been getting an exponential number of emails asking for this because their power button is bazinga so I thought it could be a cool challenge to build this from scratch as I had no previous knowledge about the input subsystem or how I could go around to detect consecutive touches if the display was disabled. And its a feature that is disabled by default and will ALWAYS be disabled by default.
[Nexus 4 Original Android Development] Taxiback:
So, in case my power button were to fail, how would I enable this, seeing as you have it disabled by default?
[Nexus 4 Original Android Development] pitjago74:
Me too...after a phoneCall and i didnt't answer.....The screen unresponsive too......i reboot with power buttom...:what::what::what: keep looking for.more issues

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] pawo99:
me too. I'm on Carbon ROM latest nightly.

Odoslané z môjho Nexus 4 pomocou Tapatalk 4
[Nexus 4 Original Android Development] riza_hakam:
i believe if your power buttom really fail which means you can't turn on screen, it means you must service your phone.. because how if your phone dead from battery and you can't power on?

and why it bu default is disabled because average user and some people (like me) didn't need this feature but need franco kernel it self.. so if this feature has been enabled by default than average user who didn't understand about terminal emulator will be confuse how to disable this feature..

i believe if someone want to enable this feature, they already understand about terminal emulator so he can enabled it with only 5 second.. and you just need to use your power buttom once to turn on the screen and than use terminal.. like i said before if you can't use your power button at all i believe service your phone to get new power button..

that's just my opinio
[Nexus 4 Original Android Development] franciscofranco:
ADB. If one is here in the first place its almost mandatory to have an ADB set up.
[Nexus 4 Original Android Development] Jaza78:
Mee to,just now hapend....Long press unlock screen to,i am on PA 3.99 RC2
[Nexus 4 Original Android Development] franciscofranco:
I just made 3 calls in a row, no issues. Are you guys using Touch Control module or any of that stuff?
[Nexus 4 Original Android Development] sixdaysandy:
Plug it into a charger to power on the screen and use the existing methods to enable. Alternatively do it all through ADB.
[Nexus 4 Original Android Development] Jaza78:
Mee to,just hapend now....Long press unlock screen to...I am on PA 3.99 RC2

Poslato sa Nexus 4 using Tapatalk 2
[Nexus 4 Original Android Development] pitjago74:
No.Franco..I.never used touchcontrol beafore....I.keep try:D

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] pawo99:
I'm not using Touch Control, now. I have uninstalled it yesterday.

Odoslané z môjho Nexus 4 pomocou Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
I cannot replicate that. Thanks for the feedback.
[Nexus 4 Original Android Development] remydlc:
Me too. I got it during a call. I turned the speakers on then off, then couldn't do anything only to reboot it. I'm using active display built-in to the carbon fw. Maybe that was it?

Gonna try to replicate it. I Love this feat.

Update: I couldn't replicate it
[Nexus 4 Original Android Development] sordna:
Where is the "Go to Sleep" button? Is it on a custom rom only ?
[Nexus 4 Original Android Development] PeQuEsan:
[MENTION=3292224]franciscofranco[/MENTION], you said you've gone back to interactive as default because you've got more "consistent" results if I recall well... Can you elaborate a little bit around this? I haven't tested your last touch enabled nightlies, but I do remember to have enjoyed your kernels since you made ondemand as a default... That's why I ask.

Thanks! Just wanna learn...
[Nexus 4 Original Android Development] Bill Gamble:
Yeah, custom rom. Cataclysm has it, for example.
[Nexus 4 Original Android Development] sordna:
I agree, 1 second would be much better... 2 seconds is too long of a time (just as it would also be for a mouse double click).

Most likely taps that are more than 1 second apart are unrelated. I'm estimating that double taps typically would have taps that are 200-500ms apart. I would put a maximum of 1 second, and a minimum of 100ms (I tried hard to do double tap as fast as possible too and it still woke up the phone, which increases the chances of an accidental wake).

And thanks for this feature, it has reduced my usage of the power button from 50-60 times a day, to 1 or 2. It will honestly prevent a lot of buttons from falling apart in the future !
[Nexus 4 Original Android Development] Serris:
Ok, so no more screen freezes when double tap to wake is disabled. Too bad, I really liked it... :(
[Nexus 4 Original Android Development] kecinzer:
ADB method doesn't work for me.

After I send echo 1 > /sys/module/lge_touch_core/parameters/doubletap_to_wake

Tap to wake doesn't work and all touch screen don't react after I turn display on by power button. I had to set value to 0.

After I do this from terminal emulator, it works.
[Nexus 4 Original Android Development] defffizz:
Double tap to wake works great so far :) i assume this feature uses less battery than touch control?

Sexy Nexy, Purity + franco
[Nexus 4 Original Android Development] thebryceee:
[MENTION=3292224]franciscofranco[/MENTION] do you know how to code it so that you can use the proximity sensor to detect when the device is in a pocket?
[Nexus 4 Original Android Development] Jeremy:
If you guys really need a "screen off" button, here is my Tasker task code. Just import it with Tasker and you're all set. There is no need for a kernel level implementation of this.

Be sure to have Secure Settings (and Tasker of course) installed.

Then just go to your home screen and add a tasker widget of this task.

Click below for code:

<TaskerData sr="" dvi="1" tv="4.1u3m">
<Task sr="task5">
<cdate>1380166186717</cdate>
<edate>1380208562085</edate>
<id>5</id>
<nme>Screen Off</nme>
<Action sr="act0" ve="3">
<code>11820</code>
<Bundle sr="arg0">
<Vals sr="val">
<com.intangibleobject.securesettings.plugin.extra.BLURB>Lock Device</com.intangibleobject.securesettings.plugin.extra.BLURB>
<com.intangibleobject.securesettings.plugin.extra.BLURB-type>java.lang.String</com.intangibleobject.securesettings.plugin.extra.BLURB-type>
<com.intangibleobject.securesettings.plugin.extra.SETTING>force_lock</com.intangibleobject.securesettings.plugin.extra.SETTING>
<com.intangibleobject.securesettings.plugin.extra.SETTING-type>java.lang.String</com.intangibleobject.securesettings.plugin.extra.SETTING-type>
<com.twofortyfouram.locale.intent.extra.BLURB>Lock Device</com.twofortyfouram.locale.intent.extra.BLURB>
<com.twofortyfouram.locale.intent.extra.BLURB-type>java.lang.String</com.twofortyfouram.locale.intent.extra.BLURB-type>
<net.dinglisch.android.tasker.subbundled>true</net.dinglisch.android.tasker.subbundled>
<net.dinglisch.android.tasker.subbundled-type>java.lang.Boolean</net.dinglisch.android.tasker.subbundled-type>
</Vals>
</Bundle>
<Str sr="arg1" ve="3">com.intangibleobject.securesettings.plugin</Str>
<Str sr="arg2" ve="3">Secure Settings</Str>
</Action>
<Img sr="icn" ve="2">
<nme>hd_ab_device_access_secure</nme>
</Img>
</Task>
</TaskerData>
[Nexus 4 Original Android Development] franciscofranco:
What Ive been noticing with Ondemand is that it tends to get nervous and jumps to higher frequencies quite easily. Also half of the time it doesnt jump to the indicated touch boost freq. While it may perform a little better in games I've been feeling that interactive with all the changes Ive made just cuts it more gracefully for everyday usage.
[Nexus 4 Original Android Development] thebryceee:
Hm. Long press doesn't turn on the screen for me, only double taps. CyanKang.
[Nexus 4 Original Android Development] franciscofranco:
Yes, I will reduce to 1s. Thanks for the feedback.
[Nexus 4 Original Android Development] SevansD:
Longpress definitely wakes on this N4, PA.
[Nexus 4 Original Android Development] whitedragonz83:
I don't see any interactive changes in GitHub. He is likely referring to the past year+ of Interactive changes he has made. Not changes in the past few days to interactive as it was already amazing prior to this Ondemand experiment.
[Nexus 4 Original Android Development] David9519:
Isn't there a possibility to decrease the sensibility of this feature?

Send from my Nexus 4 with**crDroid AOSP** ROM using xda-developers app
[Nexus 4 Original Android Development] kecinzer:
For now is double touch to wake too much sensitive for me.

But I now it becomes better and better :)
[Nexus 4 Original Android Development] agascon:
+1

I think that would be great combined with the double tap to weak functionality. In any other case, I can guess it will drain the battery rather quickly...
[Nexus 4 Original Android Development] capncybo:
+1 to this question...

I have been using the application... "Auto Screen On" for several months which also uses the Proximity sensor.

It's awesome & TBH from an electronics veiwpoint continuously powering a Proximity Sensor has to use less current than powering a Digitizer.

I've set it to stay on until a very low battery level like <30% and don't really notice any significant battery drain when using it.

When I pull it out of my pocket it turns on, I have a bumper/case so I place it face down on tables etc... but when I pick it up It's On.

I've set a gesture (double-click on nothing) to turn it off (and have a short 30 second display off)... It's one of my favorite things about my phone.

As long as the proximity sensor is covered it stays OFF. No false positives or phantom touches.

Personaly Franco I think it's a better way to go.

Thank you for all your awesome Kernel Magic, and keep up the good work ;)
[Nexus 4 Original Android Development] franciscofranco:
What do you mean by too sensitive? Please explain better.

I would love to do that but I don't know yet. I don't know if the Kernel has any awareness of the Proximity sensor readings. It should have, but its something I haven't checked. But if I can do that I would be very happy.
[Nexus 4 Original Android Development] kecinzer:
Phone wakes up on almost every touch, I only tap on display (not doublet tap) and it turns on.
[Nexus 4 Original Android Development] pitjago74:
And with a Long press turn screen on too.:D

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] alanhenrique:
problem...

sorry my stupid question ...

'm paranoid in RC-2 3.99!

I tried to use the kernel matrix and have lags when using the phone.

i tried franco kernel, I flash the boot.img as described at the beginning of the post to AOSP rom. But I have the same problems I had with the matrix!

PS: i have more performance, but i have this problem lags on change screens or apps, i see on AnTuTu 1512Mhz !

sorry my stupid questions,

if algue can help me step by step I'll be grateful!
[Nexus 4 Original Android Development] franciscofranco:
Are you running the preview from yesterday or the first preview that I released?

You have to flash the JWR version: http://minooch.com/franciscofranco/Nexus4/4.3/boot-r184.img
[Nexus 4 Original Android Development] defffizz:
How to set double tap to wake on boot? Cause it doesn't work after I rebooted device.

Sexy Nexy, Purity + franco
[Nexus 4 Original Android Development] CMNein:
No data drops for me on R26 or R27; I typically have stupidly good signal however thanks to tight tower density. Those with drops, have weak signal usually?
[Nexus 4 Original Android Development] awtacular:
Nope, I'm always 3 or 4 bar.
[Nexus 4 Original Android Development] iGoogleNexus:
Lol nah my building is AT&T and Bank Of America .... Always have full bars and awesome data =]

Also have I mentioned I'm AT&T ? Lol

#Team MiNCO

**G1→N1→NS→GN→N⁴**
[Nexus 4 Original Android Development] JNewms:
I doubt anyone is going to waste any time with this as it is well known that benchmarks are completely useless. The introduction of project butter in jelly bean is the main reason. If anyone who is more savvy in this area wants to elaborate, feel free. But, yea, you're wasting time running benchmarks.

Sent from a Paranoid N4
[Nexus 4 Original Android Development] CMNein:
Any idea of dbm and asu? I'm usually between -55 to -75 dbm and ~25 asu. The bars have a fairly coarse resolution, ~ -90 is 4 bar IIRC.
[Nexus 4 Original Android Development] scream4cheese:
Nope. I live in the city so cell reception is everywhere. I think it's the kernel. Data drops stopped after I tried wiping cache or rebooting. Strangely enough, I never had to wipe.
[Nexus 4 Original Android Development] CMNein:
Well that's convenient :highfive:
[Nexus 4 Original Android Development] Nexitus:
I really only my data drops at work, where I work downtown which technically has better towers. However, I work in a concrete building which gives me a max of 2-4 bars. Only here, do I notice my phone always searching for signals, which in turn uses tons of battery and heats up quite a bit.

Currently at -109 dBM with 2 asu and jumps to -95 dBm with 10 asu
[Nexus 4 Original Android Development] sethyx:
@Franco, are you sure there is nothing you can do about the PowerHAL touch_boost (E)rror output in logcat?

It makes (especially ROM) development pretty difficult because I can't just filter logcat to show one simple application, I usually need to see everything it spits out.

With this "extra" output I touch the device and *boom* I have to scroll back 20 pages to see the actual log I need, and I haven't experienced this error so far with any other kernels I tested.

Thanks.
[Nexus 4 Original Android Development] awtacular:
Usually showing -91 to -98 dbm and 8 - 10 asu at least where I'm at now and that's with 3 bars. I switched back to r26 because I haven't had this issue with any of the previous kernels.
[Nexus 4 Original Android Development] dwang:
3g data drop is back for me in r27.

No issues w r26.
[Nexus 4 Original Android Development] yokuyuki:
Any chance of a flashable zip?

What does wifi optimization even do?
[Nexus 4 Original Android Development] Roscopcoletrain:
No issues with r27 for me. Nfs plays perfectly. No data drops.

Thumbs up Franco
[Nexus 4 Original Android Development] iGoogleNexus:
=D Optimizes your WiFi!

Was trying to be funneh... Don't mind me lol

#Team MiNCO

**G1→N1→NS→GN→N⁴**
[Nexus 4 Original Android Development] Luigiesin:
I'm doing just fine with R26... The wakelock is still there... But no biggie... I'm sure Franco will work those little things little by little... Staying put with R26 for now ;)
[Nexus 4 Original Android Development] digweed4me:
Yep its true
[Nexus 4 Original Android Development] Stefa.:
Is it your battery life increased?

I remeber you had some problem with the battery. :)