yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] svnhvn:
Every persons has their own style, and perhaps that's is francisco's style.
[Nexus 4 Original Android Development] RockBoyEmy:
... Aaaaaand again it is doing the same thing. It worked once. Now I turned off my phone and rebooted it again.. And the problem is there again

Sent from my cool Nexus4 powered by PA 4+ and F.kernel
[Nexus 4 Original Android Development] serfer222:
Sometimes 3rd CPU core doesn't go offline, it's stucks at maximum frequency. I had this bug twice with latest 204 kernel + paranoid android ROM. Everything else is fine. Do you need more information to find this bug?
[Nexus 4 Original Android Development] leader288:
Well I would ignore it, unfortunately I'm looking at anything that affects my battery because I can hardly get more then 1.5hrs of SOT. That's why I'm asking.
[Nexus 4 Original Android Development] sd3993:
Happens with me too. A reboot fixes it though.

Msm_hsic_host doesn't affect battery badly enuf to cause 1.5 hr SOT. Something else is the problem.
[Nexus 4 Original Android Development] gecko316:
what rom are people using for the best battery life?

i've been using purity (very good) and have now switched to slimkat (latest stable release) and testing that for battery performance
[Nexus 4 Original Android Development] FalenDemon:
Maybe some app using ur 3rd core? Check it out. And it could be rom related, because PA still in beta. This happens on stock settings?

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Original Android Development] svnhvn:
IMO, purity was slightly better than slimkat in term of battery (with same apps and settings).
[Nexus 4 Original Android Development] serfer222:
Recent apps list was empty. This bug produces huge battery drain.
[Nexus 4 Original Android Development] FalenDemon:
Recent apps list dont show all the process running atm.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Original Android Development] CyanoBacteryMod:
I've a question for you guys If i install Franco kernel (with stock configuration) will i get a better batery life than using the stock one? With last PA4.

i ask this beacuse always that i tried to use franco kernel in my old Gnex i got a horrible battery life

Thank you guys :good:
[Nexus 4 Original Android Development] RootNightmareX:
r204 is damn good for battery life
[Nexus 4 Original Android Development] CyanoBacteryMod:
And you're using the stock kernel set up?
[Nexus 4 Original Android Development] RootNightmareX:
yes, sir :cowboy:

but as always if you want battery over peformance, go for matrix or hellscore
[Nexus 4 Original Android Development] 3dawg:
Since when has that ever been true? Franco's is the best for battery and worst for performance in my experience.
[Nexus 4 Original Android Development] Shubhamqweasd:
wth ??

in my opinion , franco kernel has the best gaming performance than any kernel available for nexus 4 .. but yes there r some kernels which can offer better battery but at a cost of significantly less performance :D

i think franco kernel is a perfect combination for performance and battery which can be possible for mako :D
[Nexus 4 Original Android Development] RootNightmareX:
exactly especially in the latest build
[Nexus 4 Original Android Development] Tung_meister:
Just picked up a Nexus 4 for my gf. flashed franco and the only issue I'm having is that auto brightness is far too low. I can't see anyway to change it in FKU so are there any init.d scripts or anything to do so?
[Nexus 4 Original Android Development] Bill Gamble:
Lux https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite
[Nexus 4 Original Android Development] Tung_meister:
I'm aware of Lux however I need to keep it simple for the gf, can the values not be returned to stock with an init.d or something?

Edit: I'm also experiencing wifi issues. Downloads are really slow ~400kbs until I toggle wifi off and on again then they go back up to decent speeds ~5mbps(comparable to my Nexus 5)
[Nexus 4 Original Android Development] FalenDemon:
I had this bug too. But on CM version of franco r204. When I changed max freq. 3rd core gone offline.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Original Android Development] Bill Gamble:
Unlike f.K for N5, f.K/N4 doesn't mess with the backlight, so Franco never had a need to create a tunable for that.
[Nexus 4 Original Android Development] Tung_meister:
Oh, I just presumed they'd been changed as next to my nexus 5 the screen is terribly dim on auto brightness.
[Nexus 4 Original Android Development] CerB:
How do you change the amount of cores to be online? Can't find any setting in FK app

Sendt fra min Nexus 4 med Tapatalk
[Nexus 4 Original Android Development] sidnoit22:
CPU Managet > Hotplug Control > load threshold edit it to 0.

Sent from my Nexus 4
[Nexus 4 Original Android Development] _BobsoN_:
Would to say about strange working of Franco r204 with Touch Contol.

Sometimes after I lock or unlock the phone with TC I see that all cores except first stack at 1.2 ghz. I try to disable wake gesture or sleep gesture but with the same result. But sometimes stack is gone. But when I turn on-off the screen a couple of times its returns. Today I install Franco r203 - its work perfect without stack cores.
[Nexus 4 Original Android Development] tlslaj0417:
I have the same issue as you about this stack core issue sometime...:(
[Nexus 4 Original Android Development] slinder154:
Same thing here.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] readon1:
Yup, here also

Verstuurd vanaf mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] McKael:
doubletap2wake

Hey

Are there people using the doubletap2wake feature on the Nexus 4?

I have tried to use it and it is nice, but there are a few issues with the current implementation.

Since I wanted to keep using it I have made a series of patches that fix/improve the dt2w feature, and add some useful (IMHO) stuff:

- fix double tap detection and improve reliability;

- reduce the tap2wake area to reduce false positives (can be disabled);

- add a tunable to disable dt2w when the power button has been pressed;

- add a tunable to enable dt2w when the phone is charging (either in addition to the normal behavior, or only when charging).

I've uploaded my tree to Github, I'd be glad to get some feedback:

https://github.com/McKael/FrancoKernel-mako/commits/dt2w

Esp. [MENTION=3292224]franciscofranco[/MENTION] if you could have a quick look and let me know if you think it can be merged...

If somebody wants to try it, I can provide a boot image for testing.

EDIT: image provided; see post #55380.
[Nexus 4 Original Android Development] _BobsoN_:
Wow! I want to try it.

tapatalked...
[Nexus 4 Original Android Development] swirly05:
I'm thinking it's time we all buy a Nexus 5...
[Nexus 4 Original Android Development] Firmino Neto:
Nah, i love my Nexus 4!

Enviado de meu Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] McKael:
doubletap2wake

OK, here's a boot.img.

A few notes on the new options:

/sys/module/lge_touch_core/parameters/doubletap_to_wake (bool)

* N: DT2W disabled (default)

* Y: DT2W enabled

/sys/module/lge_touch_core/parameters/doubletap_pwrkey_suspend (bool)

* N: Power button ignored (default)

* Y: DT2W is disabled when the power button is used

/sys/module/lge_touch_core/parameters/doubletap_full_window (bool)

* N: The DT2W area is limited to the bottom of the screen; margins left/right are ignored (default)

* Y: The whole screen can be used to wake up the device

/sys/module/lge_touch_core/parameters/doubletap_charger (integer)

* 0: Charger presence does not alter the behavior (default)

* 1: Normal behavior + DT2W is enabled when charging

* 2: DT2W is only enabled when charging (no battery drain)
[Nexus 4 Original Android Development] :
Wrong. upgrading to N5 at this point is kinda useless. Personally, I'm waiting for the N6. If you really want a new phone go for the Xperia Z2.
[Nexus 4 Original Android Development] swirly05:
Wrong. I'm a Nexus fanatic for life!
[Nexus 4 Original Android Development] RohanM:
Nope.. I now hate vannilla android.. Will be upgrading to G2...
[Nexus 4 Original Android Development] C4SCA:
Dont take it serious, just joking :P

sent from my diabetic Nexus 4 (too much KitKats)
[Nexus 4 Original Android Development] RohanM:
It's personal preference i Guess.. :cowboy:
[Nexus 4 Original Android Development] RootNightmareX:
It's real that a lot of users are saying that thet are still sticking with nexus 4 because nexus 5 is very buggy at camera and bad for daily use ? :confused:
[Nexus 4 Original Android Development] autoradio78:
Please guys..why buy a nexus 5? For follow a good dev?

Wait nexus 6 for jump;)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] philosophics:
I didn't upgrade because I didn't see it as that much of an upgrade. Also, the looks of the device seemed like a downgrade.

However, this is off topic. Unless we are discussing this because we're going back to a conversation about Franco not supporting this device anymore, which is false. Considering he still devs on the galaxy nexus, I would imagine this device still has plenty of life left in the kernel updates.

Let's get back on track now, guys and gals. Thank you!
[Nexus 4 Original Android Development] RootNightmareX:
I'll wait more. I want bigger differences. I just jumped these months from a ancient galaxy mini, and now the difference it's incredible .

BTW i Believe franco support is far from over.
[Nexus 4 Original Android Development] silvagroup:
Been on 204 for a week now.

AWSOME. As already mentioned great performance and battery life.

Thanks again Franco great job.

Nexus 4 Stock 4.4.2/Franco Kernel 203/xposed and mods/Optimized Dalvic and Bionic all sweeeet.
[Nexus 4 Original Android Development] domg73:
Good job!

That's exactly what I was looking for, thank you!
[Nexus 4 Original Android Development] McKael:
You're welcome. If you run it please let me know how well (or bad...) it works!
[Nexus 4 Original Android Development] domg73:
So far so good... everything seems to work as expected...

Would be nice to be able to select the screen area for the dt2w... bottom is ok... but someone (like me) may prefer the center of the screen...
[Nexus 4 Original Android Development] McKael:
Thanks, that's good to know.

I can try to make the area configurable (not before Saturday or Sunday).
[Nexus 4 Original Android Development] yanleites:
Can you make an option to disable the TC and the digitizer ? Because now, if I disable it, the digitizer keep working.
[Nexus 4 Original Android Development] RockBoyEmy:
Seriously I don't know what to do. Since I flashed r204, every time I reboot my phone the superuser doesn't apply to the franco kernel app. I have every time to delete the app from the superuser list and add it again. I tried re-installing francos app, I tried to reflash the superuser zip... Nothing. :/

But at least the r204 improvements are visible

Sent from my cool Nexus4 powered by PA 4+ and F.kernel
[Nexus 4 Original Android Development] svnhvn:
Clear app data also won't help you?

*reboot after you cleared your fku app data.
[Nexus 4 Original Android Development] RootNightmareX:
This week a lot of problems have appeared for me too. All types of them. Tryed difference roms and nothing.It's like a electro magnetic wave has attacked the kernel or something.
[Nexus 4 Original Android Development] sidnoit22:
Did you try rebooting? :cowboy:
[Nexus 4 Original Android Development] T-luvR:
Flash superSU
[Nexus 4 Original Android Development] RootNightmareX:
Wow why didn't i never though about that ...

Ofc man. I even clean flashed a lot of roms.

I used it for 1 week and this week i had a lot of problems.
[Nexus 4 Original Android Development] McKael:
I'm not sure I understand what you mean. What do you call TC?

(And how do you test the digitizer is still on?)

If you can give me the steps to reproduce I'll have a look.
[Nexus 4 Original Android Development] yanleites:
The touch control 2.0.2, works fine, but when I disable it, the cpu stays on 384mhz and doesn't enter deep sleep.

The touch control developer explained it as the digitizer stays on after disable TC. Can you do something to stop the digitizer?
[Nexus 4 Original Android Development] McKael:
Oh you mean the proprietary Touch Control module? No, I don't know what it does but you probably can't use both systems at the same time.
[Nexus 4 Original Android Development] yanleites:
I flashed your image and see no difference. Should I turn it on anywhere?
[Nexus 4 Original Android Development] RockBoyEmy:
Yeah man, I flashed the supersu already twice

Sent from my cool Nexus4 powered by PA 4+ and F.kernel
[Nexus 4 Original Android Development] Arstoien:
Very buggy at camera and bad for daily use? Certainly no. I've got both N4 and N5.
[Nexus 4 Original Android Development] RootNightmareX:
I'm just a little bit angry, i just bought a month ago the nexus 4 and now the nexus 5 is cheaper than nexus 4 in my country.
[Nexus 4 Original Android Development] Arstoien:
Man, I bought my N5 and literally a couple of days after Google opened the Play Store in my country. I had an option for only black or white 16GB version. Had I waited another couple of days would've had red option and 32GB for less money and no contract.
[Nexus 4 Original Android Development] :
I never understood day 1 purchases (of any kind). It's known that whatever the item in question is, be it a phone or a console etc., it will get cheaper and better (f.e. the xbox/ps4 firmware updates or the Android firmware updates) after a short period of time.
[Nexus 4 Original Android Development] Arstoien:
I bought it less than a month ago – much later then when it came out. Things seemed to have settled, no way of knowing that Google would've opened the Play Store.
[Nexus 4 Original Android Development] RootNightmareX:
Yeah, but you're in a better case than myself. Basically it's the same phone, at least for me the storage is not a big bonus.
[Nexus 4 Original Android Development] McKael:
Well I think it's good news, it means [MENTION=3292224]franciscofranco[/MENTION] can merge it and people not using DT2W won't see any difference ;-D

Yes, sure. The sys file switches are explained in my earlier post #55323.

E.g. (as root):

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

If Francisco decides to merge it, maybe he'll add the settings to his FKU app -- that would be awesome :)
[Nexus 4 Original Android Development] yanleites:
Great.

Works.

Now... How about battery drain?

After reboot I have to change the Y/N values.

It's ok?
[Nexus 4 Original Android Development] McKael:
Great :)

You tell me... :)

It actually depends on the options you set (and your usage... if you use your phone a lot the digitizer extra drain is probably not that important).

For example, if you set doubletap_charger to 2, it will be enabled only when the phone is charging so you should get 0 extra battery drain.

I set doubletap_pwrkey_suspend to Y (so that DT2W is disabled when I suspend the phone using the power button) and doubletap_charger to 1.

Yes.

(You can also automate it with an init script.)
[Nexus 4 Original Android Development] yanleites:
Everything works great !

About the battery, can you tell me percents per hour/day or it's impossible ?
[Nexus 4 Original Android Development] McKael:
It's almost impossible to say -- see all the posts about different battery drains in this thread!...

IIRC in my tests I had an extra drain of ~0.8%/h when the phone is suspended and DT2W enabled.

And as I said, the more you use your phone, the more insignificant this extra-drain is. So... I'd say, YMMV!
[Nexus 4 Original Android Development] yanleites:
Got It, Thanks again !
[Nexus 4 Original Android Development] McKael:
Yes: if you set doubletap_pwrkey_suspend to Y (or 1, it is the same), then when you use the power button of your phone to turn of the screen the device should go to sleep as usual, and the doubletap2wake feature will not be used. So you will save battery if you explicitly use the button to put the phone to sleep.

If the phone sleeps automatically after the timeout, then doubletap2wake will be active.

If you set doubletap_pwrkey_suspend to N (or 0), doubletap2wake will be active even when you use the power button. That is the default behavior.

I hope I made it clear... :)
[Nexus 4 Original Android Development] yanleites:
Very !
[Nexus 4 Original Android Development] deedeeceleb:
My min freq is always jumping to 918 MHz. Have to manually change it back to 384 via fku :-/

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] yanleites:
Is R205 on it's way ? ;)
[Nexus 4 Original Android Development] davemlinux:
Only god knows ldk too hahahhaa ???
[Nexus 4 Original Android Development] axlrvx:
No.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] anandbibek:
Someone care to explain what is up_threshold_any_cpu_freq and up_threshold_any_cpu_load ?
[Nexus 4 Original Android Development] icu64:
What makes you say no bro?
[Nexus 4 Original Android Development] svnhvn:
It's up to Francisco.
[Nexus 4 Original Android Development] Arstoien:
http://xdaforums.com/nexus-4/orig-d...ernel-r201-t2002782/post51642350#post51642350
[Nexus 4 Original Android Development] kol1124:
What's your UV values ?
[Nexus 4 Original Android Development] tiner:
-150 mv

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] xX NeOnShK Xx:
OT but did you change your username after you started having these problems or has it always been like this [emoji12][emoji16]
[Nexus 4 Original Android Development] striker280:
Ever since I updated to r204 from 203, my phone seems to get really hot really fast. I undervolt my phone -100 already, but still gets very hot quickly. Am I doing something wrong?
[Nexus 4 Original Android Development] joni_strokes:
i get this problem too, i'm on cataclysm rom, after undervolt -125mV i've got better temperature but still it was hotter than 201/200
[Nexus 4 Original Android Development] Firmino Neto:
I don't have this problem with OmniRom + franco.

Enviado de meu Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] svnhvn:
Yup, neither i on slimkat.
[Nexus 4 Original Android Development] i2k13:
As some already mentioned, the 3rd and 4th core doesn't seem to turn off after going online.

That's what probably causing the heat issue,

I've managed to solve this by setting cpufreq_unplug_limit to 1242000 under Hotplug Control.

If this doesn't work you should try to change it to 1.5ghz, my cpu max frequency is 1.2ghz.

Use system monitor to track this.
[Nexus 4 Original Android Development] McKael:
Here's a new boot.img (#2) with the change you requested. I have replaced doubletap_full_window with doubletap_area so that we can now choose between full screen, bottom, top or center.

I have tested it very quickly and it seems to work as expected :)

Summary of the DT2W-related tunables:

/sys/module/lge_touch_core/parameters/doubletap_to_wake (bool)

* N: DT2W disabled (default)

* Y: DT2W enabled

/sys/module/lge_touch_core/parameters/doubletap_pwrkey_suspend (bool)

* N: Power button ignored (default)

* Y: DT2W is disabled when the power button is used

/sys/module/lge_touch_core/parameters/doubletap_area (integer)

* 0: (default): full screen

* 1: bottom area (left/right margins excluded)

* 2: top area (left/right margins excluded)

* 3: center of the screen

/sys/module/lge_touch_core/parameters/doubletap_charger (integer)

* 0: Charger presence does not alter the behavior (default)

* 1: Normal behavior + DT2W is enabled when charging

* 2: DT2W is only enabled when charging (no battery drain)

(Repository updated.)
[Nexus 4 Original Android Development] domg73:
Thank you... Now it's perfect!
[Nexus 4 Original Android Development] eltonpestana:
hi

this kernel work on AOKP kk?
[Nexus 4 Original Android Development] bokagavrilov:
If it's cm-caf based the no
[Nexus 4 Original Android Development] eltonpestana:
How i know this? I install here hellscore cm b45 and havê problem with layout and cores.
[Nexus 4 Original Android Development] zobi123:
Does it work on the latest Paranoid Android?
[Nexus 4 Original Android Development] svnhvn:
Yes.
[Nexus 4 Original Android Development] punkeroso:
Hi McKael,

first of all, thanks for the effort spent trying to get better this features.

I would use this great features since francisco release it, but I didn't for two main reasons:

the second tap should be "near" the first: if my first tap is on the top of the screen, the second one, that actually wakes the phone, shouln't be on the bottom. There should be a threshold that, if the first tap was in x1;y1, the second one that wakes the phone should meet the condition (x2-x1)^2+(y2-y1)^2 <= threshold^2 (circles's equation).

the second issue is regarded the proximity sensor: when I'm in a call, the screen is off but the digitizer is always on, so almost certainly I'll tap somewhere on the screen or, even worse, I would hang up the call.

I hope that you fix the above issues, so I can start to heavily use this feature.

Bye
[Nexus 4 Original Android Development] McKael:
Thanks for the comments punkeroso,

I'll add that. I've not been much annoyed by this issue since I use the bottom area and not the whole screen...

OK. I'll have a look, I don't know yet if there's an easy way to know if there is a phone call.

Thanks a lot for the useful feedback.
[Nexus 4 Original Android Development] thiagoribeirorj:
Great work. Thanks for this great cooperation in our device.
[Nexus 4 Original Android Development] svnhvn:
FKU update? Thanks franco!
[Nexus 4 Original Android Development] yanleites:
There are no new updates...
[Nexus 4 Original Android Development] deedeeceleb:
There is a new FKU beta update!

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] bkraptor:
I can confirm that with 204 the last 2 cores are stuck at 1.2 GHz after a while. Changing the cpufreq_unplug_limit to 1242000 seems to fix this issue for the moment.
[Nexus 4 Original Android Development] yanleites:
Any one can download it?

If yes, where from?
[Nexus 4 Original Android Development] deedeeceleb:
Changelog here:

https://plus.google.com/106873500108976028532/posts/VdzHtcN4mFS

How-to is written in the comments

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] svnhvn:
Never had my core/s stuck. Or perhaps because i let 4 of them online?

If you join the beta channel then you can download it directly from playstore.
[Nexus 4 Original Android Development] FalenDemon:
If all cores online then battery life will be worse? Or you dont feel any difference?

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Original Android Development] svnhvn:
I don't feel any difference on battery side.
[Nexus 4 Original Android Development] scissorscrush:
I know it's not out of the blue but this kernel does not support usb OTG... I never use the cable but I had to use it today and mobile go app kept on asking to enable usb debugging. Already enabled. Am I missing anything here? :-\
[Nexus 4 Original Android Development] yanleites:
I don't see the new version in play store after signing as a tester...
[Nexus 4 Original Android Development] The Gingerbread Man:
Look in my thread in my SIG fku Learner lounge. Detailes instructions are there and all the links to stuff
[Nexus 4 Original Android Development] yanleites:
It didn't help me, I was hope for an Apk file for testers
[Nexus 4 Original Android Development] The Gingerbread Man:
You need to sign up to the g+ fku community. All the links are provided by me. You need the paid apk which then gets updates from the play store. I have provided all the info for you in that thread in post 1...
[Nexus 4 Original Android Development] dougiefresh36:
Hey, you think you can put your profile up again, my internal memory got wiped ?
[Nexus 4 Original Android Development] yanleites:
Your app is awesome!

Do you have any page on xda for updating or its only here?
[Nexus 4 Original Android Development] karthi89:
Just unzip fku or display control app, goto assets folder, copy all the color profiles and paste it inside fku folder in ur internal storage