yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jamel_tza:
Hey [MENTION=3292224]franciscofranco[/MENTION]

I just want to say thank you for your kernel, time and all the effort you've put in coding. For the first time I'm running your kernel with the stock ROM and I must say that this configuration has proven to be a match made in heaven. Everything works as it should, all available FKU settings work without lag, stutters etc. Its works, and it works well. I'm issue free (other than reboots from snapchat (known issue)).

Thank you
[Nexus 4 Original Android Development] dark_ente:
touch to wake work fine with slim, I haven't put the phone in my pocket but on the table it works as expected.
[Nexus 4 Original Android Development] TaRsY:
Touch wake is too sensitive now.

Max time between the double tap should be less, and there should be a restriction for the place of the second tap. Second tap should be near the first one.

The minimal slide also should be longer.

These could avoid unnecesary wake ups.

Anyways great to see this feature and l'm happy to use your kernel with Slim again.

Küldve az én Nexus 4-ről Tapatalk 4 használatával
[Nexus 4 Original Android Development] bouaroudj:
+1
[Nexus 4 Original Android Development] Andre_Vitto:
words from my mouth..
[Nexus 4 Original Android Development] waleedshiekh:
Using r184 with SlimBean. Cpu Type : Fastest

Can anybody please let me know the safe lowest UV values. I'm using the following values.
[Nexus 4 Original Android Development] dark_ente:
I think you can go -50 more
[Nexus 4 Original Android Development] Matteo Mazzu:
Wake on touch working, but too sensitive.. tried touching one time the screen, count till 10, re touching it and it wakes up! XD
[Nexus 4 Original Android Development] dark_ente:
confirmed that after some time, screen is frozen and no touch input is registered. I have to hard-reset the phone

maybe it's the problem with nexus's digitizer?
[Nexus 4 Original Android Development] s1m4an:
Coming from PA's enhanced kernel running 3.99 rc2 WiFi simply won't turn on, even flashing r184 doesn't fix it.
[Nexus 4 Original Android Development] Andre_Vitto:
Running pa rc2.. wify fine..
[Nexus 4 Original Android Development] shubu000:
Thanks Franco for your good work. I too think that the time between touches should be shorter
[Nexus 4 Original Android Development] svnhvn:
[MENTION=3292224]franciscofranco[/MENTION] : Blessed the stock ROM, its ****ed up free.
[Nexus 4 Original Android Development] Pipusz:
How do you change kernels? Please try the following if you haven't already:

- format system, cache, dalvik (data will be preserved if you don't do anything else)

- reflash ROM, Gapps

- reflash kernel

- reboot.
[Nexus 4 Original Android Development] s1m4an:
Chill guys, its probably because the enhanced kernel has newer WiFi drivers. And there's no need to reflash rom or wipe system when flashing kernels (usually).

This time flashing rom first then franco's kernel works, WiFi turns on.
[Nexus 4 Original Android Development] Pipusz:
If you're coming from another kernel, it's suggested to do this. I read it here (point T8) once, doing this ever since and no problems whatsoever. (OK, not true, I'm on Franco's since I bought my N4, but I did this on the GNex.)
[Nexus 4 Original Android Development] endursa:
i installed the test kernel on a fresh cm 10.2 nightely install, and played around a bit

my observations so far show that double tap2wake seems a bit broken, try taping the display once every 1-2 seconds, after the third tap it will wake the device!

also the dt2w and s2w options should be activateable seperatly, because i noticed that accidential wakes inside my poked occured!

but the biggest problem i found just happend, my digitizer stopped responding completely only a device reboot helped here. i could not get any logs or something because i have no usb cable on me, and adb over wifi is not activated, but i try to reproduce it.

it happend right after the test with multiple single taps!
[Nexus 4 Original Android Development] dark_ente:
yes, I also experience the same thing.

on slim build 1.2, UV a -150, did you UV too?
[Nexus 4 Original Android Development] CamoGeko:
Working well so far here, thanks for finally taking a look at this feature Franco!

So far the only niggle I have is that it doesn't seem to work after a missed call.

Also, would love to see the configuration implemented in FKU at some point.
[Nexus 4 Original Android Development] endursa:
-50 UV here but i don't think that SoC UV has anything to do with digitizer though
[Nexus 4 Original Android Development] :
I think my is set to "breathe-to-wake" :laugh:
[Nexus 4 Original Android Development] PedroBustamonte:
I noticed that you just have to hold down your finger on the screen to wake it.

sent from my toaster
[Nexus 4 Original Android Development] BakaPhoenix:
Works fine on mine. But i notice that the time set for recording the double tap is really long.

Also if i put it on my pocket (screen towards me) it always unlock the phone, maybe is done by the press and slide wake
[Nexus 4 Original Android Development] myfluxi:
Francos implementation of s2w will not work. It's quite a bit behind showp's version with all of it's early bugs. showp's movement detection is solid. dt2w will probably not work reliably at all on our device because the first touch is sometimes ignored.

The cure to all problems would be an active i2c bus which is not always the case. Franco should concentrate only on this aspect. I once solved this for the i9100, not sure if it can be done for mako. Just look at LG's own hacky workarounds. My sleep-workaround for mako still has a 1-2% failure rate.
[Nexus 4 Original Android Development] rysup:
Yeah this was what i was doing when the digitizer froze too.
[Nexus 4 Original Android Development] manulemaboul:
I confirm what everyone said, working great but way too much sensitive.

Envoyé depuis mon Nexus 4 avec Tapatalk 4
[Nexus 4 Original Android Development] michelemascia7:
now, the touch on my phone doesn't work ahahahah D:
[Nexus 4 Original Android Development] jak3z:
Use a mouse bro! It's the future!
[Nexus 4 Original Android Development] SevansD:
+1
[Nexus 4 Original Android Development] michelemascia7:
thanks :D it work!
[Nexus 4 Original Android Development] SevansD:
Really look forward to T2W when it's working. It was way too sensitive before the digitizer froze.

Congrats [MENTION=334712]francisco[/MENTION] on joining the PA team! Great combination.
[Nexus 4 Original Android Development] mendozaram:
it would be nice a double tap to sleep. :)
[Nexus 4 Original Android Development] Net.silb:
I like the touch to wake but its to sensitive at the moment...

I think all the types of touch gestures that wake the device should be more specific. For example, it has to be a quick double tap or a longer swipe on a specific area of the screen. In addition, we need to pocket test this thing...

All in all its a good start.

Actually now that I'm thinking about it, I think that we shouldn't use swipe at all, only double tap.
[Nexus 4 Original Android Development] readon1:
Can someone recommend a color profile that is the most color accurate? Thanks in advance.
[Nexus 4 Original Android Development] jak3z:
Color profiles > , Gamma 2.2
[Nexus 4 Original Android Development] panart:
I totally agree, there's no need for swipe to unlock.

I suggest double tap to wake and slide to lock (similar to Touch Control app).

What i hope is that it won't consume too much battery (Touch Control does have significant battery usage for me).
[Nexus 4 Original Android Development] visceralpsyche:
Try my profile in FKU - 32_visceralpsyche

I did a proper calibration and saved the results. For absolute match use Brightness at 50%.

HTH

Cheers,

Paul :)
[Nexus 4 Original Android Development] Waldos:
Thats fuking amazing!

So you will be on the same boat as PA?
[Nexus 4 Original Android Development] michelemascia7:
try 43bundi_22 :D
[Nexus 4 Original Android Development] CamoGeko:
+2

Frozen here too, had to reboot.

sNox.

Sent from my baked potato
[Nexus 4 Original Android Development] jak3z:
On my screen, green and red are over-saturated and blue just a little bit so what with what you calibrated it?
[Nexus 4 Original Android Development] CamoGeko:
Double post.
[Nexus 4 Original Android Development] franciscofranco:
This is just a preview, obviously needs improvements, some of those you enumerated.

No.

I haven't had that problem, still worked after having it enabled whole night.

Please don't call it dt2w or s2w, I simply hate those terms or acronyms or whatever you want to call it. Its either double tap to wake, or swipe to wake. Anyway I concur with some of the observations and now its time to just improve the code based on the feedback.
[Nexus 4 Original Android Development] leets4uc3:
[MENTION=3292224]franciscofranco[/MENTION] do you ever hit up Ibiza? The club life there is insane!
[Nexus 4 Original Android Development] CamoGeko:
Ibiza is old news mate, you should go clubbing in London. ;)

Sent from my baked potato
[Nexus 4 Original Android Development] Floydfire:
I can live without swipe to wake but double tap seems a lot good and simply, I didn't used the touch wake app before because it's a little uncomfortable for me but simply double touch to wake it's really good.. So if in the next release we can select witch one is active is a lot better for me... I don't know maybe it's too tricky and you're not interested but I think having some few gesture (for me one is enough) that open an app isn't a bad idea (maybe for the kitkat kernel) like "yo I have to make a call" swipe up and tadaaa phone is waked and phone app opened. Just a suggest I know your way of thinking and I share you point that a simply and clean kernel is better but if this feature isn't too tricky I think it's a good add on!

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] leets4uc3:
I need to move out of the US. Everything awesome is too spread out! Europe is the place to be! :(
[Nexus 4 Original Android Development] Waldos:
GalaxyS4
[Nexus 4 Original Android Development] justibasa:
Yes I am. I'm not that stupid.

Don't like me.........BITE ME!!!
[Nexus 4 Original Android Development] jak3z:
I suggest to not go to Europe and stay in the US ;)
[Nexus 4 Original Android Development] Andre_Vitto:
okey lots of reboots with 185.. while using flashlight is one that i recall.. was at work.. so no log..
[Nexus 4 Original Android Development] leets4uc3:
Most likely a ROM issue or panic. Kernel shouldnt of done that. (To my knowledge)

No issue with mine. I'm on a really old carbon version where everything works for me.
[Nexus 4 Original Android Development] panart:
I've cleaned the screen with a glass cleaner liquid and the screen woke up and started opening and closing the lock screen widgets, at the end it opened google now via the bottom swipe gesture.

I can't remember if that happened when i briefly tried out Touch Control app, but it's possible that by using double tap only to wake the screen this won't happen.
[Nexus 4 Original Android Development] drawde40599:
Ok..... Whos SU r u using? I can say EVERY strange issue ive had with 4.3 i can trace back to koush's SU , IF your using his SU try chainfire's instead ive had 0 issues with his, theses roms using koush's SU should stop IMO open source or not if it dosent work right it dont make sense ;)

[MENTION=470754]Franco[/MENTION] 185 has been great no issues on CM latest, your screen wake preview works but is pretty sensitive (one tap will turn it on) i also had screen lockup but only after i kept turning off and on off and on testing feature out, if u use phone correctly no lockups (for me)

Thanks for your time!

I
[Nexus 4 Original Android Development] franciscofranco:
I thought about going to Ibiza this summer to see Mr. Armin van Buuren, but my GF couldn't afford (its not a cheap trip) it and going alone is stupid. Maybe next year :)

Yes current code makes it too sensitive, but I already have a couple of ideas to make it better. Its new territory for me, never did any of this before. Was also pretty nice to learn how the input subsystem worked, Kernel documentation is great.
[Nexus 4 Original Android Development] chiwou:
Tried the touch to wake feature, but after a few minutes it stopped working couldn't touch anything anymore, but could still wake the device tough ;)
[Nexus 4 Original Android Development] fozzie:
I had all sorts of problems this morning with the new touch to wake feature on stock ROM.

Either I could enter my unlock pattern but then there was no further touch response, or I couldn't even enter the unlock pattern.

At one point, with my phone on the desk, the screen would come on (on the pattern unlock screen), I'd hit the power button to turn it off but it would just turn straight back on again... and not take any touch input, over and over again.
[Nexus 4 Original Android Development] jak3z:
You can come to party over my place anytime bro, I got a free room ;)
[Nexus 4 Original Android Development] franciscofranco:
Weird O.o

Thats also very weird. Thanks for testing though, its super experimental stuff at the moment. I'll drop another preview later today after I code some stuff :)
[Nexus 4 Original Android Development] sNoxious:
Maybe the touch to wake option can be set through FKU so it'll be automatically set on boot? Just a thought. You did a great job on this Franco! :good:

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
That is obviously intended at some point - but currently there are two setbacks:

1 - This touch to wake thingy is TOO early, I just released as a preview and to get feedback

2 - I'm currently re-writing FKU from scratch - takes a lot of time from me

Glad for me and for FK users that this is currently my full time job :)
[Nexus 4 Original Android Development] sNoxious:
For this to be in early stages, it's a remarkable job. Good luck on being part of the PA Team btw!

Sent from my Nexus 4
[Nexus 4 Original Android Development] fozzie:
I've just had a thought - are those people having problems with touch input not responding (when using touch to wake) running Lux?

I remembered there's an issue relating to display overlays (that prevented input on a pop up window on a VPN client I was using).

I've just disabled Lux and haven't had a touch input problem so far...
[Nexus 4 Original Android Development] Puzzlegirl:
I haven't had any problems all day and I don't use Lux: it would be interesting to find out if your theory is correct!
[Nexus 4 Original Android Development] pitjago74:
By default this option is disabled, but you can enable it by doing:

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

How can I enable using My N4?

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] Mercado_Negro:
Use Terminal Emulator from Play Store.
[Nexus 4 Original Android Development] pitjago74:
Yes,thanks..but.its.not doing anything

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
Type su first....
[Nexus 4 Original Android Development] Mercado_Negro:
Did you grant superuser permission?
[Nexus 4 Original Android Development] sNoxious:
Type 'su' then enter. Type in the command for enabling touch to wake then enter. Done.

It needs Root access in order to perform that command. :good:

Sent from my Nexus 4
[Nexus 4 Original Android Development] pitjago74:
Now it works PERFECT:D:D:D

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] tandr:
it is not just double tap

franciscofranco,

Just broke my hand, and this feature coming as is G-d sent! (I would prefer triple tap actually, but that just me)

Thanks,

A.
[Nexus 4 Original Android Development] pitjago74:
By The way.....Franco.will you enjoy PA dev.??

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] dark_ente:
yes, I've been using Lux since last week.

I'll try to disable Lux and see
[Nexus 4 Original Android Development] franciscofranco:
If I wouldn't enjoy it me and moles wouldn't talked about it.
[Nexus 4 Original Android Development] pitjago74:
So.next rom i will try is your PA.....any Link??:D:D:D

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
It's not my PA and there is no link...
[Nexus 4 Original Android Development] Arstoien:
Just thought to share with the guys asking for double tap to shut off the screen:

You can use a custom launcher which supports gestures like Nova or Apex. Download Smart Task Launcher. Then I assign the double tap to Smart Task Launcher to act as if I'd pressed the power button. If you use it only for this, I don't think you need the paid version of the second app, though it has awesome capabilities if you're a fan of edge swipes.

Sent from my Nexus 4
[Nexus 4 Original Android Development] pitjago74:
Ok....i.mean your PA,cause if you work with them...nevermind.....i keep watching Real Madrid:D:D:D

And The 185 is very smooth,thanks Franco;)

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] orangestrawberry:
Liking the touch to wake very much indeed
[Nexus 4 Original Android Development] jak3z:
FranciscoParanoidAndroidFranco.Kernel

Sounds easy and awesome ! :cool:
[Nexus 4 Original Android Development] pkelly517:
I had the touch screen go completely non-responsive after enabling touch on 185. I'm also using Lux.

Touch screen, nothing. Hit power button, see unlock screen. No input accepted on lock screen. Screen goes blank.

AOKP, hope to be former Touch Control user.
[Nexus 4 Original Android Development] genkralyz:
franco kernel rocks! \m/

kewl touch2wake/swipe2wake feature, thanks francisco ;), will monitor the battery perf .. hehe

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Can you test with Lux disabled? Thanks

Please, call it touch to wake or swipe to wake. I hate those names with a "2" in between, doesn't sound professional or serious at all :)
[Nexus 4 Original Android Development] ben_pyett:
Franco and lux user, I've previously loved sweep to wake style features on my previous HTC device and would love them again on my N4.

Keen to see how this pans out
[Nexus 4 Original Android Development] genkralyz:
sorry for that :)

one i noticed, its a little bit sensitive when i put the phone in my pocket the touch to wake activates, my screen wakes inside my pocket, after a few minutes i took my phone inside my pocket and the touchscreen is not responding, so pressed the power to hard reboot... that's what I experienced from 185 beta test :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] ziddey:
You could use an app to enable/disable touch to wake based on the proximity sensor.
[Nexus 4 Original Android Development] jak3z:
I've measured Nexus 7 2013 touchscreen power usage during 3 hours, and the average use was 45mV, don't know on the nexus 4 but should be around the same.
[Nexus 4 Original Android Development] jamel_tza:
What is the touchscreen's average power usage without Touch To Wake enabled? For comparison's sake.
[Nexus 4 Original Android Development] jak3z:
It was below 20mV if I recall correctly.
[Nexus 4 Original Android Development] pkelly517:
Reloaded, re-enabled and Lux turned off for now.

I'll post if I see any issues tonight. Phone will go onto a wireless charger overnight.

Like I said, if the kernel can match the capabilities of TC, I'm all in. Shoot, I'd buy another FKu for my daughter, who just got an iPhone.
[Nexus 4 Original Android Development] alanwyl:
[MENTION=3292224]franciscofranco[/MENTION] What kernel would be bundled into PA later on? Night lies or milestones?
[Nexus 4 Original Android Development] Fed4Lyfe:
Paranoid Android

Hi Frankie.

For the latest PA Rom, do I need to download the nightlie or the AOSP 4.3 version?
[Nexus 4 Original Android Development] ziddey:
Oh yikes. Just an update for anyone who wants to try this... you need to make sure touch_to_wake is enabled BEFORE the screen shuts off (say enabled on boot), after which it's a-ok to disable it.

If touch_to_wake is not enabled BEFORE the screen is off (digitizer off), and is enabled WHILE the screen is off, the digitizer remain stuck off even when manually waking the phone up. The remedy would be to disable touch_to_wake while the screen is off again.
[Nexus 4 Original Android Development] dark_ente:
I disable lux but still get screen frozen after 4 hours.

Looks like lux is not the culprit here
[Nexus 4 Original Android Development] sordna:
How do you measure that? Would like to try it!
[Nexus 4 Original Android Development] Jeremy:
Woops. Delete
[Nexus 4 Original Android Development] jak3z:
You have to create a script that outputs the value from /sys/class/power_supply/battery/current_now to a file in the sdcard every X seconds, I always use 60 seconds and let it run for 1 hour at least without touching the device.
[Nexus 4 Original Android Development] svnhvn:
[MENTION=3292224]franciscofranco[/MENTION] : I'am using lux and i can confirm that your touch2wake can run as it supposed to be. No problem whatsoever.
[Nexus 4 Original Android Development] kaluoshi:
If you wanna enable at boot until francisco add it to fku put this script in system/etc/init.d folder and set rwx rwx rwx permissions. Remove ".txt" from filename it was for allowing the upload.
[Nexus 4 Original Android Development] cjay73:
Worked perfectly fine. One question when the next OTA update comes around do I have to flash the stock kernel in order to receive the update. Pretty new to this stuff.
[Nexus 4 Original Android Development] sagaofsage:
I had similar issues with TC on my N4 when double tap was enabled, but no issues with the swipe to unlock enabled. So with double tap enabled the lock screen occasionally refused any touch inputs, and it happened without Lux.
[Nexus 4 Original Android Development] int abacus:
delete
[Nexus 4 Original Android Development] defffizz:
He's asking is the STOCK kernel required to receive new android OTA. And answer is yes, of course :) i believe new fku has option called 'prepare' for OTA.

Sexy Nexy, Purity + franco
[Nexus 4 Original Android Development] sordna:
Yes, "prepare for OTA" should be used, IN ADDITION to flashing the stock kernel, before an OTA.
[Nexus 4 Original Android Development] cjay73:
awesome that's what i thought i kept a back up of the stock kernel but I will enjoy the FK until then

---------- Post added at 10:54 PM ---------- Previous post was at 10:10 PM ----------

I'm looking for the prepare for OTA option on the FKU but I can't seem to find it.
[Nexus 4 Original Android Development] sordna:
It's in the Support section.
[Nexus 4 Original Android Development] momomok:
Isn't 755 permission is enough?
[Nexus 4 Original Android Development] TheDarkDefender:
I thought it was rw- r-- r-- ?

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
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] nokiagye:
Franco on your plans is to lock with double tap or we don't see this feature? Thanks
[Nexus 4 Original Android Development] franciscofranco:
I dont plan that. Its tricky to do and I see potential issues rising from it. It would also require a better panel/touch firmware because this panel absolutely sucks.