yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] franciscofranco:
Indeed! They changed the bloody build.id to JLCsomething, which fúcks FKU not-so-smart detection algorithm! :'(
[Nexus 4 Original Android Development] Bobtehblob:
Same thing happens on cm, just have to download and flash manually :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Zainiak:
Just dropping by, been on Franco for 6 months now, tried others every now and then. I always come back to Franco and purity. My favorite combo. Except maybe pa now that you are on the team. Its always felt much slower than other Roms to me, but I love the features. Hopefully that changes. But thanks for the great kernel!!
[Nexus 4 Original Android Development] franciscofranco:
Ok I have a small gift for all of you that run FK for almost a year on this device. I always said that I would never implement any of those functionalities to wake the device without pressing the power button - point is that LG G2 has brought this feature, Oppo N1 has something very similar and... I've been getting emails that users are having the Power Buttons wore off. Initially I implemented this on the new Nexus 7 as a challenge and to have some fun. Couple code lines later I had the functionality working fine and dandy. The device deep sleeps and the only thing that is being kept active is the digitizer for this to work. I sent it to a couple of people and they enjoyed it specially because it worked better than other Kernels that had implemented similar options. Good, so lets try and implement it on Mako. It's 100% my code, pretty simple, and easy to understand. Please refer to git (I just pushed the code) for how it works in the touch driver and input subsystem.

By default this option is disabled, but you can enable it by doing:

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

After this is enabled you can power up the display by double tapping just like the LG G2, and you can swipe from whenever you want on the display and it will power up. There is a 100ms (0.1s) minimum interval where the algorithm will detect touch events so filter ghost touches and some unintended shít. It seems very low value, but when we're touching the screen the digitizer is capturing hundreds of touch events every minute, and dozens every second. So this works as a filter.

If you're using touch_control and you want to test this, please disable the module and reboot your device or you'll most likely get into some **** problems. And the same thing other way around.

Oh and interactive is back to default, it just gives me more consistence results all around.

Attached goes two test zips, flash, enable the touch thingy, test, and report back.
[Nexus 4 Original Android Development] otariq:
Noobish question but I enable it by typing that command in terminal emulator?
[Nexus 4 Original Android Development] jak3z:
Yes
[Nexus 4 Original Android Development] franciscofranco:
Either that, adb, a file explorer with root (eg Root Explorer) by going to the file and overwriting the content. Whatever you feel comfortable with.
[Nexus 4 Original Android Development] resynx:
Nice!! Flashing NOW! :D
[Nexus 4 Original Android Development] sordna:
Hope that the new FKU will allow calling a user defined shell script at startup! That would come very handy for the new kernel setting (and future ones as well)
[Nexus 4 Original Android Development] Redneck Trash:
Not working for me on stock ROM.
[Nexus 4 Original Android Development] franciscofranco:
Path is correct O.o

What Kernel version does it show on the About Phone thingy?
[Nexus 4 Original Android Development] franciscofranco:
That is a big possibility that its going to happen :)
[Nexus 4 Original Android Development] franciscofranco:
Ups, fixed the path. Coded for too many hours today, pretty damn tired.
[Nexus 4 Original Android Development] stylobil:
Same here, version in the about screen is #185. Shouldn't JSS be tagged with the version number? Cause I downloaded the JSS version.
[Nexus 4 Original Android Development] franciscofranco:
I fixed the path, check again ;)
[Nexus 4 Original Android Development] eluspo:
Where can i make the changes in root explorer? Also what are the exact commands in terminal emu? Thanks for the update :)
[Nexus 4 Original Android Development] Redneck Trash:
#185
[Nexus 4 Original Android Development] xFuGiToiDx:
Those of u having issues with terminal emulator. Type this instead

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

Franco accidently switched the parameters folder and lge_touch_core folder
[Nexus 4 Original Android Development] stylobil:
Okay, now it's working. Sweet feature!

Gonna test it for a day or two and come back with some feedback.

Thanks for your work!
[Nexus 4 Original Android Development] Redneck Trash:
Works now. Go take a break.
[Nexus 4 Original Android Development] davidbar93:
Purity rom combined with Franco kernel r184... Pure awesomeness.
[Nexus 4 Original Android Development] franciscofranco:
Read the post please -.- I don't waste my time to code these stuff and then people don't read my post explaining it. Please, just read it, but read it fully to understand what it is, what it does and how you enable it/disable ;)
[Nexus 4 Original Android Development] xFuGiToiDx:
To disable the touch to wake, do I just type in echo 0 instead of echo 1?
[Nexus 4 Original Android Development] franciscofranco:
There is no time for breaks, now its time for gaming and relax, it was a pretty big day for me with this work and the announcement of me joining PA for real. Will be fun :)
[Nexus 4 Original Android Development] franciscofranco:
Exactly.
[Nexus 4 Original Android Development] xFuGiToiDx:
Thanks man im not that familiar with terminal emulator commands that's why. I just wanted to make sure.
[Nexus 4 Original Android Development] eluspo:
Okey will read it again
[Nexus 4 Original Android Development] franciscofranco:
That's the spirit ;)
[Nexus 4 Original Android Development] Nocturnal86:
Wow thanks for your work franco! Cant wait to try it out :) One question. Would the new touch to unlock waste extra or any significant amount of battery? For example running normally untouched or if its in your pocket or in hand and with the screen facing/touching your hand or leg? Thats the only thing thats stopped me from using touch control or anything like that..
[Nexus 4 Original Android Development] copi:
it work, but no need to double tap.. even with slide of finger its wake. does it intend to act like that?

edit : after 1 minute the slide is no longer working,, ok then. just excited with new toy. but its really sensitive this touch to wake of yours. 2slide is also work. have to try put on my pocket first.

thanks franco :)
[Nexus 4 Original Android Development] Nocturnal86:
read his post he said you could do both
[Nexus 4 Original Android Development] eluspo:
Dont know which one is correct but its working now. Thanks franco! The Best!!
[Nexus 4 Original Android Development] drawde40599:
Touch wake

Looks like touch wake is working but u dont have to double tap, or swipe, just touching the screen at all wakes the device . Running on cyanogen ATM
[Nexus 4 Original Android Development] Mercado_Negro:
It's worth quoting a second time:
[Nexus 4 Original Android Development] stylobil:
Yep, touching the screen just one time wakes up the phone. CM too.
[Nexus 4 Original Android Development] eluspo:
After a reboot i lost the touch to wake.
[Nexus 4 Original Android Development] Mercado_Negro:
It should be done after each reboot. These type of commands do not survive reboots.
[Nexus 4 Original Android Development] Nocturnal86:
I think it needs to be enabled everytime you reboot
[Nexus 4 Original Android Development] Andre_Vitto:
working.. well done sir.. kinda sensitive.. whats next? let users decide sensitivity and swipe gestures?
[Nexus 4 Original Android Development] PhantomGamers:
This is awesome, I really appreciate you adding this in.

Do you have any plans for the double tap to sleep feature as well?

(The G2 does it so if you double tap while on the homescreen it shuts the display off and if you are in an app only double tapping the notification bar or nav keys does it... probably a pain to implement though)
[Nexus 4 Original Android Development] justibasa:
Done the command 10 times and still not working. Tried both codes posted. Running cm10.2 with the posted experimental kernel. Oh well.

Don't like me.........BITE ME!!!
[Nexus 4 Original Android Development] shockem:
Hope this new feature and gets implemented into FKU soon. Amazing work once again :)
[Nexus 4 Original Android Development] resynx:
With the new tap to wake, while in a call the screen while flicker on and off nonstop. Just reporting my finding :) Thanks for everything Franco :D
[Nexus 4 Original Android Development] svnhvn:
Brilliant franco, works for me.
[Nexus 4 Original Android Development] Nocturnal86:
Works great but seems pretty sensitive. When picking up the phone if your hand is near the screen it will usually unlock the screen. Idk if this is able to be modified in anyway down the line? Cause it seems pretty awesome to have!

I think double tap would be better to have implemented only, than slide to unlock cause double taping would be harder to recreate on accident and if the possibility of modifying the speed of the taps to be done to unlock the screen or something like that it would make the possibility of accidentally unlocking the screen a bit hard and not as sensitive. Just my thoughts! I know this is not a "key" or important feature on your list franco!
[Nexus 4 Original Android Development] Haomuch:
Great feature, will wait for the fku update
[Nexus 4 Original Android Development] rysup:
Was working for me at first except you don't need to double tap, single tap will wake it.

After that the touch screen somehow got disabled completely, only power and volume buttons worked, had to hard reset the phone.
[Nexus 4 Original Android Development] kingmaliQue:
pa 3.99 rc2 with latest test kernel..all good so far and the new feature is working great!
[Nexus 4 Original Android Development] drawde40599:
R u giving SU permissions?

su

echo 1 > /sys/module/lge_touch_core/parameters/touch_to_wake
[Nexus 4 Original Android Development] alanwyl:
[MENTION=3292224]franciscofranco[/MENTION] Was testing the touch-to-wake feature, after some locking and unlocking of screen, I seem to see two touch on either side of the screen registered. Rebooting doesn't help, after a few minutes, the touches are back. Then I echo 0 to touch_to_wake, lock then unlock, the points are gone.
[Nexus 4 Original Android Development] sjeik1985:
after i flash franco.zip i got my network error! it keep showing no network coverage
[Nexus 4 Original Android Development] CatsAreGods:
Hi, Trying the new touch kernel on stock 4.3, noticed that there's no battery stats for apps or services showing up in Settings.
[Nexus 4 Original Android Development] :
Love the new feature and have one minor gripe with this touch_wake, double tap and slide to wake should be configurable on and off between them (either one or both), I pocket my phone (facing leg) and it accidentally gets turned on and random things are pressed while in the pocket, due to double tap to wake, I would love to use only slide to wake cause its a more deliberate action and very difficult to do accidentally while in my pocket, don't use screen protector and even bumping the screen against my leg twice (wearing formal trousers) turns it on so please consider it
[Nexus 4 Original Android Development] nokiagye:
+1
[Nexus 4 Original Android Development] sordna:
There's an app I discovered recently, Automaton that uses the proximity sensor to lock/unlock the screen, it might work better for you than touch control if you pocket your phone without putting it in a case. You can also shake the phone to lock/unlock it.
[Nexus 4 Original Android Development] swirly05:
Anyone lost wifi??
[Nexus 4 Original Android Development] whittikins:
If I'm running ParanoidAndroid (or another AOSP rom for that matter), is it possible to use your ramdisk? All I know to do from this point is to flash your .IMG using the provided instructions, but I don't quite understand the ramdisk comment.

Thanks!
[Nexus 4 Original Android Development] digweed4me:
franco first of all thanks a lot for this kernel .

i am using matrix 2.0 kernel which he uv to -100 mv and slightly oc gpu by default and i am getting amazing battery with 5 hour screen on time and it doesnt get hot either. i think if u implement undervolt -100mv yours kernel could get to 6 hour screen on time cause i am already getting 4.5 screen on time with your kernel.
[Nexus 4 Original Android Development] Stretlow:
Any performance issues with the new govnor settings?
[Nexus 4 Original Android Development] franciscofranco:
Wait until I get an image compatible with CM, no need to be all hasty and rushy.

I answered that the last page. UV comes when I think its a good time for it. I do my own thing, not follow what other people do on their kernels.

Nope.
[Nexus 4 Original Android Development] JNewms:
I am a little confused about about the ramdisk thing too. I understand it isn't ready to play with cm yet but is it good to go on aosp? This sounds like an awesome kernel, just need to know what ROM i can use it with
[Nexus 4 Original Android Development] Noobla_Khan:
Compatible with AOSP based roms, not compatible with CM.
[Nexus 4 Original Android Development] dankoman:
Latest build breaks GPS for me. Anyone else? On PA 2.99 build 6.
[Nexus 4 Original Android Development] zueda:
PA used to be based in CM but is now based on AOSP.
[Nexus 4 Original Android Development] Puzzlegirl:
No GPS problems here (on MoDaCo ROM).

Kernel running great so far today - battery going down very slowly :)
[Nexus 4 Original Android Development] nbeebe24:
Nope GPS works here. On AOKP
[Nexus 4 Original Android Development] Vanhoud:
When i click the screen my CPU still scales to 1.02GHZ each time i press
[Nexus 4 Original Android Development] elliot.newnham:
remove your previous boot settings and reboot.
[Nexus 4 Original Android Development] renna1992:
hi franco

would you mind taking a look at faux's kernel - the new beta? he mentioned something in the changelong which - as first reports indicate may have fixed the msm_hsic_host-wakelock. I don't know if you have the time to take a look or if you are working on it for yourself but I'd really appreciate it if you'd have the time to check his git or something :)

as I said before: no hurries or anything and if you don't have the time to look into this i'd totaly understand.

thank you :)
[Nexus 4 Original Android Development] ctfrommn:
So if I am reading this right we should NOT use a tool to change the frequency? If we do it will revert all your scaling tweaks till rebooting?
[Nexus 4 Original Android Development] jaestreetss:
Wondering the same thing - every app i put to set oc/Uv. To anything else it won't stick....

I want to put min-8 or 9 something

And Max @ 1.3
[Nexus 4 Original Android Development] ctfrommn:
It will stick for me using No Frills, but it still jumps to 1026mhz on every touch and spends a lot of time there. I already cleared cache/data for all apps that could control frequency and still no change. Rebooting just leaves it at OS defaults of 1026/1242.
[Nexus 4 Original Android Development] dankoman:
okay sorry i fixed it. i had to go into location settings and turn 'access to my location' off then back on again, then agree to the dialog that popped up. i think it had something to do with me clearing my play store/services framework data earlier (had to do this to make my calendar events show back up).

anyway, note to anyone else who clears data for play store / google services framework: you may need to do the same in order to get gps working again.

thanks for your help guys!
[Nexus 4 Original Android Development] franciscofranco:
This is a Nexus, all builds are AOSP.
[Nexus 4 Original Android Development] franciscofranco:
Yes, for now thats the way to go, just let it work without trying to change the freqs. I'll think of another way to make it less hacky in the future. For now, that works fine.
[Nexus 4 Original Android Development] abjexstallion:
Sorry for my noobyness Francisco, the GPL in the topic means what? Also, if I have a question related to your display app, should I PM you or directly to your email? Thanks
[Nexus 4 Original Android Development] defnz:
Wifi issues are most likely due to the fact that when the phone sleeps multicast and broadcast requests are filtered out, As ARP relies on broadcast requests devices on the network aren't able to determine whether your phone is alive.

This thread contains the info, in short edit /system/etc/wifi/WCNSS_qcom_cfg.ini and change McastBcastFilter=3 to McastBcastFilter=0

Save then reboot.

I was also having inconsistent results with notifications, sometimes instant sometimes not till I changed it
[Nexus 4 Original Android Development] Bigzinewicz:
Keyboard lag on stock 4.1.2 ROM

Running stock rooted ROM 4.1.2 with Franco kernel obviously and have had the lag on keyboard on all builds since the first. No lag on stock kernel so not sure if kernel related but seems that way. Stock keyboard and Swiftkey. Switched to Swiftkey to try to solve lag problem but it has only made it slightly less noticeable. Only happens when typing very quickly.
[Nexus 4 Original Android Development] steviewevie:
Bear in mind that those using reader apps (like XDA's own one) won't be able to see anything below ...
[Nexus 4 Original Android Development] iGoogleNexus:
Meh data keeps dropping. Places i always have connection now seems to drop ... Reverted back to r26. =] still love this kernel

#Team MiNCO

**G1→N1→NS→GN→N⁴**
[Nexus 4 Original Android Development] scream4cheese:
What the heck?
[Nexus 4 Original Android Development] drawde40599:
Google voice has built right in no hack needed ;)
[Nexus 4 Original Android Development] awtacular:
Same thing here.. Went back to r26 since I had no problems with it.
[Nexus 4 Original Android Development] bilguun1:
Data dropped, r27. R23 was fine, had no problem
[Nexus 4 Original Android Development] drawde40599:
27

Been on phone for last 2 hours at work , build 27 , everything just as great as build 26 no lag , on anything ! , battery great, did have data drop after 30 min right after i installed but never happen agn , don't no what that was about , data dose seem slower though compared to 26 , but wont no for sure till I'm home later , . everything great

Thanks Franco

BTW never once had data drop with 26 . 24-25 were bad with drops tho
[Nexus 4 Original Android Development] scream4cheese:
I know but he wasn't using the reader app.
[Nexus 4 Original Android Development] g47:
Just flashed 27, not having any other kernel flashed before.

I payed your app Franco on google play, firstly because it is worth it and secondly because I flashed my kernel with one touch.

Thank you.:good:
[Nexus 4 Original Android Development] thuynh022:
Just flashed r27, coming from r23 which gave me no problems. Will let you know if I experience any data drops.

R23 made a huge difference from stock. Best version I've ran so far. Hope 27 is even better.
[Nexus 4 Original Android Development] TheByteSmasher:
Data drop on 27. Had to reboot to resolve. :confused:

Sent from my Nexus 4
[Nexus 4 Original Android Development] Godaemon:
I' m running some benchmark tests on antutu trying to figure out the governor settings in each case could someone tell me from what the CPU floating point is affected? Thanks in advance :)
[Nexus 4 Original Android Development] drawde40599:
anyone that can be reproduce data to drop try to get Franco some cat logs
[Nexus 4 Original Android Development] prim3:
Overall kernel is performing well, except lag in some games like NFS Most wanted....
[Nexus 4 Original Android Development] Godaemon:
Running r27 new data drop unlike r26.I'm going to check wakelocks and report back.
[Nexus 4 Original Android Development] Armin_van_buuren:
You need to do a wipe to change the kernel?

I was trying other things but I go back to r27.
[Nexus 4 Original Android Development] scream4cheese:
No need to wipe. Just flash.
[Nexus 4 Original Android Development] Mercado_Negro:
I didn't. It's working fine here.
[Nexus 4 Original Android Development] xFuGiToiDx:
Tested to touch to wake for about 3 hrs and for some reason my phone wasn't reading touch correctly. I had a hard time unlocking my phone and I couldnt press the app drawer icon at all. Even the whole phone was lagging. I had to reboot my phone to get it back to normal. It probably did that cuz I undrclocked my CPU to 1.1 GHz and my max screen off is only 594 MHz instead of 702 MHz. I think im better off disabling the touch control. Its too sensitive for me, I might give it another shot soon. Hopefully u can implement the double tap to wake the screen.
[Nexus 4 Original Android Development] :
My phone is in a case btw

Just don't have a screen protector and prefer facing screen towards my leg
[Nexus 4 Original Android Development] drawde40599:
Nope all is good here. Lost like Inop or grey bars lost?
[Nexus 4 Original Android Development] swirly05:
No Wi-Fi just don't turn on, Idk why??
[Nexus 4 Original Android Development] xFuGiToiDx:
No issues here with WiFi. Are you running stock or custom ROM?
[Nexus 4 Original Android Development] swirly05:
PA
[Nexus 4 Original Android Development] xFuGiToiDx:
Not sure what's wrong. I'm running purity ROM. Try flashing back to r184 and see if WiFi works and then try 185 again
[Nexus 4 Original Android Development] sordna:
touch to wake on r185 works, with some caveats

The touch to wake feature works for me, and I noticed the kernel is now r185 even though the OP hasn't been updated :)

It's a neat feature but is a bit inconsistent, sometimes 1 tap wakes up the phone (rarely), sometimes (most often) 2, and sometimes (occasionally) 3.

Also it seems that if I tap the screen, wait about 3 seconds, tap it again, wait 3 seconds, tap it again, it turns on. I think it should avoid turning on unless we have 2 taps happening within 1 second. If more than 1 second passes from a tap, the kernel should ignore it and start over. Maybe the time could be configurable...

Also I noticed that somitems the 2nd tap also opens an app if I happen to hit an icon. So if possible, once the screen is turned on, I think the digitizer should avoid passing input to the launcher/apps for 200ms or 300ms or so.
[Nexus 4 Original Android Development] jmudrick:
5 seconds or less between two taps opens screen for me.
[Nexus 4 Original Android Development] Andre_Vitto:
Works on PA rc2.. A tad bit too sensitive for me.. opens phone in pocket.. hopefully configurable swipe settings next
[Nexus 4 Original Android Development] Svid:
I think the hw_reset appers only on cm. I'm using purity and didn't had random reboots at all.
[Nexus 4 Original Android Development] giebeka:
So maybe it's time to compile build with OTG Working?

#Tapnięte z Nexusa 4
[Nexus 4 Original Android Development] Nocturnal86:
please just shut up with that already. OTG is a hack its not able to work hardware wise so he wont implement it ever! This has been stated multiple times... If you want the hacky OTG you can search the forums.
[Nexus 4 Original Android Development] nokiagye:
After reboot you must run again the command..
[Nexus 4 Original Android Development] stankyou:
Or just make an initd script for it if you dont wanna do it everytime you reboot.

via xda app
[Nexus 4 Original Android Development] Mercado_Negro:
Touch to wake is working as expected here, Franco.

I went back to stock a couple of hours ago and flashed this test right after, using the latest version of your app. Put it in my pocket and walked around (even tapped my pocket), and the screen was off all the time. Sensitivity seems spot on to me. Let's see how it behaves during tomorrow. Thanks.