yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] franciscofranco:
6am, still no sleep, can't get enough of her :p
[Nexus 4 Original Android Development] brian88:
Hey guys, I found out a weird thing this morning, I dont use Touch Control or something like that, but I could wake up my phone by double tap on screen. Is that unusual?? I'm using Franco r191 + Primal based on Carbon v18. When I flashed Primal Kernel v10 it disappeared
[Nexus 4 Original Android Development] jokkir:
I'm sure this has been asked before (and it has after a quick thread search) but I'm having problems with the msm_hsic_host wakelock on my Nexus 4 using the r191 JWR kernel. It's really high for some reason.

And yes, I'm going to ask: how is this fixable if possible? I'm just on Stock Rom, Greenify handling a lot of my apps when the screen is off and nothing that should keep the counter that high.

Oh, and I have not changed anything on the kernel as far as I'm aware.
[Nexus 4 Original Android Development] franciscofranco:
I have nothing to do with what others do by compiling from my source, its not my problem and you should ask in that "primal" something thread.

No.
[Nexus 4 Original Android Development] shubhdeep99:
Its a feature in franco kernel ....

@ franco :- sir please disable this feature by default , it eat battery when in pocket, and if possible then include on-off option for this on fku...
[Nexus 4 Original Android Development] franciscofranco:
ITS DISABLED BY DEFAULT GOD DAMNIT.
[Nexus 4 Original Android Development] Rohit02:
Calm down pal..

If people are saying it on by default it is on. There is no point getting annoyed on people.

Yesterday I flashed a new rom and r191 and it was on by default..

Please look into it simple.:)
[Nexus 4 Original Android Development] ziddey:
That's wildly rude.

Your rom ****ed up. Simple as that.

https://github.com/franciscofranco/mako/commit/4e5073dfb2c5a3f10a4cbbb09fbb3d1b9ce7cc0c

https://github.com/franciscofranco/mako/commit/8cb718ad547c474a23c3f8fcaea2771602ddc2a1

+bool touch_to_wake = false;
+module_param(touch_to_wake, bool, 0664);
[Nexus 4 Original Android Development] Redneck Trash:
Are you sure it's not something to do with the ROM?
[Nexus 4 Original Android Development] shubhdeep99:
Actually sir,

Flashed r191 over carbon and slimrom on both rom double tap to wake is on by default....
[Nexus 4 Original Android Development] franciscofranco:
Its the second time I post this today, its the last time I post this forever. Next question about this and I'll remove it from the Kernel, no explanations will be given, I'm tired.

https://github.com/franciscofranco/...rivers/input/touchscreen/lge_touch_core.c#L60

bool doubletap_to_wake = false; <- false means disabled, deactivated, not-operational, shut-down, not available, not working etc.
[Nexus 4 Original Android Development] Redneck Trash:
Ain't that way on stock ROM.
[Nexus 4 Original Android Development] Rohit02:
No, I have tried r191 on carbon, slim and purity in all the cases it was on by default. It was not a rude reply but I was politely asking Franco Sir to calm down.

So many people are saying the same thing means there is some problem somewhere..
[Nexus 4 Original Android Development] shubhdeep99:
May be i have not tried...
[Nexus 4 Original Android Development] sordna:
I have an idea, put this control in FKU (paid version only), and just tell people: if you want to make sure it's turned off at boot, you have to buy the app :)
[Nexus 4 Original Android Development] franciscofranco:
Eheh, I'm not that bastard ;)
[Nexus 4 Original Android Development] ziddey:
I haven't been able to reproduce this phantom enabling, but I do agree that enough people with various third party roms have been mentioning it. At the same time, I can't imagine how a rom would have any effect, especially since "doubletap_to_wake" is unique and thus wouldn't be accidentally explicitly targeted.

Only thing I can think of would be that it should be static? Can't see why that'd produce unexpected results only with certain roms though.

static bool doubletap_to_wake = false;
[Nexus 4 Original Android Development] TheDarkDefender:
Doesnt happen here. Running carbon. And 191. Im pretty sure its something you previously flashed.

Sent from my Nexus 4
[Nexus 4 Original Android Development] sordna:
Well, I'm not saying to force it on to annoy people, just tell them, that if their ROM turns it on, they need to either install an rc script, or get the FKU app and choose the appropriate setting at boot. Nothing wrong with that.

Ideally, fix the feature right AND add the setting in FKU, best of both worlds, but easiest/quickest would be to add the toggle in FKU first. I think it's key that FKU has all toggles available, gives people more incentive to buy it. Don't let competitive apps like trickster add toggles for your own kernel before you do.

BTW a while back I suggested about a feature to allow FKU to run a user-defined shell script after applying the boot settings. This will allow people to easily add/remove the new experimental sysfs toggles, without you needing to update FKU all the time.

It will be a great feature for users, and huge time saver for you.

You can even provide a script template, with things like touch2wake echo commands already in place (echo'ing a 0 of course).

That will even solve the issue of ROMS turning it on !
[Nexus 4 Original Android Development] Redneck Trash:
Disabled by default. Nothing to fix. This is why we can't have nice things.
[Nexus 4 Original Android Development] GForceXIII:
Not happening here, but I'm on stock rom
[Nexus 4 Original Android Development] sub1287:
Fine on PSX, clearly not a kernel issue.
[Nexus 4 Original Android Development] sordna:
Read my post carefully, I'm in 100% agreement with franco. Of course it's disabled by default. Anyway, he will get what I'm saying.
[Nexus 4 Original Android Development] fozzie:
There must be at least one or more third party ROMs or app that is installing an init script that's enabling doubletap_to_wake; it's up to you guys with the problem to work out which it is, by a simple process of elimination. It should only take a few cycles of removing the init script, ROM flashes, app installs/un-installs & reboots. It's seriously not hard. Once you find out what it is please post here so we can kill this once and for all.
[Nexus 4 Original Android Development] benbugohit:
The problem is

[MENTION=332323]fozzie[/MENTION]: +1,

the "many people are saying the same" didn't get time to check their :

- /system/etc/init.d/*, etc/init.d/*, /system/addon.d/ scripts,

- and their apps restored by google process, as TC or S2W enabler...
[Nexus 4 Original Android Development] limeaide:
This is a very likely cause. I guarantee if you wipe the entire phone including system flash stock rom and then franco it will not be turned on. Now do the same effing thing and flash your rom of choice and if it is enabled then your stupid rom is the culprit.

I also imagine this was Francisco earlier.
[Nexus 4 Original Android Development] Diunka:
Here too...
[Nexus 4 Original Android Development] Pipusz:
I'm on Purity, r191 and it's not enabled by default. For some users, it's probably time to do a clean flash.
[Nexus 4 Original Android Development] The Gingerbread Man:
Did you get my PM?
[Nexus 4 Original Android Development] svnhvn:
To the folks that claimen touch to wake is enabled by default: this pass week i flashed (from stock) cataclysm, purity, psx, and back to stock with r191, such thing was never occured. I always did a clean install. If you guys still persisted only one answered linger.

Its an alien.
[Nexus 4 Original Android Development] fajarlazuarding:
Actually it also happened to me before, it happened when i came from hells kernel. So i think, another kernel that have that feature enabled by default or you have enabled it before doing that magic on your phone.
[Nexus 4 Original Android Development] bongostl:
Hi all.just an fyi....Franco no longer works on carbon nightlies as of 10/23. They took some things from cm telephony , and carbon now fcs on boot with Franco. Here is the line from the carbon change log: Many system changes in telephony and camera from CM. May cause fc on boot if you have a custom kernel with a custom ramdisk.
[Nexus 4 Original Android Development] franciscofranco:
I was pretty pissed indeed.

Yes, I'll reply later, Im on a trip, going to stay with my GF for a couple days.
[Nexus 4 Original Android Development] franciscofranco:
Why are they merging CM ****? What is the real benefit?
[Nexus 4 Original Android Development] Batur97:
Hi;

I think try to install this kernel but I have got a question. How is battery life on daily use thanks :)
[Nexus 4 Original Android Development] franciscofranco:
Good.
[Nexus 4 Original Android Development] Mercado_Negro:
I'm glad you're doing that... Because last time you were on a trip Google released 4.3 :p
[Nexus 4 Original Android Development] 777.300:
Perfect on my Nexus in combination with ParanoidAndroid

Sent from my Nexus 4 with Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
I was on vacation during 4.3. My GF will never forgive me for wanting to work instead of going to the beach lol
[Nexus 4 Original Android Development] svnhvn:
Never flashed another kernel. Might tempted by semaphore though.

Then perhaps Google will launch 4.4 during your vacation as with 4.3?

LOL
[Nexus 4 Original Android Development] Batur97:
Thanks guys :D I will try it :)
[Nexus 4 Original Android Development] franciscofranco:
Please no!
[Nexus 4 Original Android Development] SnoopHTC:
Hello, I don't know, it's the root app of slimrom v1.9... ??? :)
[Nexus 4 Original Android Development] svnhvn:
Ditch that and flash Chainfire's.
[Nexus 4 Original Android Development] arcticrobot:
Here is a reply to the similar question by Carbon g+:

I wont pretend to understand why, but to keep the new features and stability coming, we need to remain up to date with Cm commits. that is my understanding of the siutation. because we use Cm repos for a ton of our stuff and by doing so alot of our code gets updated automatically. if we didnt merge this new Cm stuff, we would have to create tons of repos of our own and keep them up to date manually, which were divert all of our attention unecessarily to keeping the code up to date instead of being able to work on new features.﻿

Edit: the statement is from their PR.
[Nexus 4 Original Android Development] David9519:
Really nice battery life again! :)

I lost the first 6 hours 20% because of wakelocks, I didn't use my phone there,so in facts I could get more sot :)

Something doesn't work,so I cannot upload the pic.
[Nexus 4 Original Android Development] David9519:
Please delete
[Nexus 4 Original Android Development] David9519:
Sorry for next post,but my app is doing weird things :/
[Nexus 4 Original Android Development] martinsjt:
You can use the "Trickster MOD Kernel Settings" app, on the SPECIFIC tab you have a toggle for "Double Tap 2 Wake", switch on hit apply and you are good to go. ;)

https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en

Best

This Franco Kernel version solve some issues with latest CM versions:

http://xdaforums.com/showthread.php?t=2487246
[Nexus 4 Original Android Development] SnoopHTC:
Hello, SuperSU v1.65 flashed and it's ok for the root access, thanks manS !! :)

the last "bug" is my GPU clock who don't stick at 320 or 200 Mhz in FKU/frequencies-voltages or in per-app settings :confused:

@++
[Nexus 4 Original Android Development] JaqaL06:
guys I deleted pa half breed color profile .. now I need it .. can anybody upload it ? thanks anyway .

Sent from my Nexus 4
[Nexus 4 Original Android Development] PeQuEsan:
You can redownload all color presets from within FKU...

Desde el móvil con Tapatalk...
[Nexus 4 Original Android Development] JaqaL06:
nope i couldn't.. cleared data and reboot then uninstalled app and re-download.. still there is no PA Half Breed..

Sent from my Nexus 4
[Nexus 4 Original Android Development] maxver0:
Is it good enough?

Wysłane z mojego Nexus 4 przy użyciu Tapatalk 4
[Nexus 4 Original Android Development] JaqaL06:
yes it is same as PA_contrasty_Titi profile now i recognized :thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] namurt:
this reply is perhaps a little too late to the party to enjoy full efficacy, but...

FRANCO, WHY U NO ENABLE DOUBLE_TAP_TO_WAKE ON MY GIRLFRIEND BY DEFAULT?!

(and yes, when i say "tap" you know what i'm talking about ;))
[Nexus 4 Original Android Development] cpanos:
No such option here
[Nexus 4 Original Android Development] daivee:
That my friend is a user error I believe. Mine works by default :sly:
[Nexus 4 Original Android Development] TestingCharts:
How to apply for Project Pringles?
[Nexus 4 Original Android Development] zephiK:
Join the test @ https://play.google.com/apps/testing/com.franco.kernel
[Nexus 4 Original Android Development] TestingCharts:
That's why I asked how to apply. Already tried that link before
[Nexus 4 Original Android Development] Mercado_Negro:
IIRC you must be part of franco.Kernel G+ community first.
[Nexus 4 Original Android Development] NUNsLAUGHTER92:
This is fake, right?
[Nexus 4 Original Android Development] mymeatb18:
No its to test the upcoming Franco app
[Nexus 4 Original Android Development] _artem_:
First join here https://plus.google.com/u/0/communities/117966512071636110546

Then become a tester here https://play.google.com/apps/testing/com.franco.kernel
[Nexus 4 Original Android Development] zephiK:
No........ why would a user of 9000 forum post post something fake?

Pretty much what artem said.
[Nexus 4 Original Android Development] jimbohurt:
Your lack of an avatar does make you seem more shady :P
[Nexus 4 Original Android Development] limeaide:
he has a avatar cant you see it?
[Nexus 4 Original Android Development] drawde40599:
I think they dropped 4.2 while he was on vacation also :P Franco u no what u have to do :P
[Nexus 4 Original Android Development] kypeth:
< 3 you franco, hate to bother you with trite info.. the latest few images have broken root access, or at least my recovery has reported has much post flashing. CWM 6.0.4.3 (also 6.0.4.0-.2)

nothing crucial at all, I always keep the supersu zip on my root because of this potentiality, just haven't seen anyone else post regarding it.
[Nexus 4 Original Android Development] RohanM:
@ op please fix songs/music stutter issue.. it's annoying..
[Nexus 4 Original Android Development] zorginho:
Hey guys i found a very good setup for Franco 191 and I'm very happy with it:

Gov settings:

Decrease the timer to 20000

Increase touch boost to 1350mhz

Hotplug settings

High load threshold 50

UV -100mv

Scheduler IO noop ( I found that row gives me random and strong lags noop generates less overhead and all is really smooth in all cases)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] _artem_:
Bought franco updater couple of weeks ago... Then cm went caf, I wasn't able to use it anymore with franco (at that time there was no color fix yet (and I hate to use crappy workarounds I just want things to just work). So I flashed in 2 days 10 different roms and mods (pa, aokp, pacman, slimbean, rasbean jelly, purity and some other) - all were just piece of crap - the biggest crap was pa's hybrid options, per app s**t - once I changed the transparency of nav bar for next launcher - it completely stopped saving changes it always went back to default, the default dpi crap - I hate to see settings app like on tablet. On tablet it's ok but on n4 it's almost unusable - just look at that WiFi label (icon + wi.. + switcher) on purity I guess it had only (icon + switcher) without those cutted one-two letters - but then I found that crappy option in per app settings.

Then I tried carbon and was amazed - it had all the features I want from a ROM (move clock, change nav bar height, transparency, nav button color, status bar clock and icons color, WORKS WITH FRANCO KERNEL) - that's really what I need from a ROM. But now carbon stopped working with franco (phone app FC) because franco is the only custom kernel which modifies ramdisk. Carbon team said it's just couple of lines which have to be added to the kernel source to make it work. AFAIK franco won't do this changes. I'm very pissed of switching roms just because Francisco is too stubborn to add those lines. I really like franco kernel but at the same time I'm pissed of it gets incompatible with more and more roms. I know it's all about cm's crapcode that's pulled into most every custom ROM sources. But all the other kernels just work with those changes (I'm not talking about caf) - of what I heard faux, hells core work just fine on latest carbon build - but I don't want to use another kernel and I don't want to switch roms at least until 4.4 is out or omnirom gets more features to customize.

Any suggestion to get the same as on screenshots but with "long-term franco kernel support", it should be 4.3 jb (whatsapp and viber dash clock extensions require jb 4.3+)
[Nexus 4 Original Android Development] bar-aka:
Why not just stay with a nightly of Carbon ROM that works with this kernel? I'm on the 19th and don't plan on flashing any newer ones unless it will be compatible with this kernel. There's nothing really crucial in the latest nightlies of carbon that I would need.

We can just wait for 4.4 and see how things turn out on that end.
[Nexus 4 Original Android Development] martinsjt:
Try this Franco Kernel version:

http://xdaforums.com/showthread.php?t=2487246
[Nexus 4 Original Android Development] _artem_:
Just tell me which ROM is based off jb 4.3, lets me change nav bar height, nav button color, move clock, change color of status bar icons, doesn't use pa hybrid crap, is compatible with official franco kernels
[Nexus 4 Original Android Development] kalpik:
Apart from changing Status bar icon colors, Purity has everything you need!
[Nexus 4 Original Android Development] franciscofranco:
No. Recovery is dumb as hell.

There is nothing to fix because nothing is broken. I listened to music yesterday for 3 hours straight on my N4, stock Kernel settings, 0 problems.
[Nexus 4 Original Android Development] sir*mez:
If you have any kernel experience, you just need to add telephony-msim.jar into the bootclasspath.
[Nexus 4 Original Android Development] matesc:
Most stable and close to stock ROM is Cataclysm. It has some great unique features (fullscreen lockscreen, smart 3G), it is not bloated and source is stock ROM with some cherrypicks from AOSP (like launcher).

Also you don't have nightlies, you get only stable releases. I am very satisfied with that ROM. And it's Franco compatible.

It is very nice to see, that people bother more about kernel first, than search for a compatible ROM. Nice, Franco! ;)
[Nexus 4 Original Android Development] The Gingerbread Man:
Can we not just say cm is not supoorted anymore? I follow Franco on gnex, n7, n7 2013, n4 and littetally all you hear about is stuff going wrong with cm or cm based roms. If these users want the refined product of Franco then they should use aosp rom or stock rom. Cm just keep going off doing things in ways that don't work in compatible ways, starting with colour control last summer I believe. Since then it has gone on to them using completely different drivers for certain Qualcomm chips and frankly if everyone moves to keep things compatible with cm then there won't be time for new development. So I propose you make your bed and lay in it if you choose cm based roms or be happy with aosp. Its splitting android into further fragmentation. Cm are now a buissness, they have gone corporate leaving bed room devs behind
[Nexus 4 Original Android Development] Mercado_Negro:
What didn't you like about Slim? It has everything you're looking for. I've been using franco.Kernel with Slim just fine.
[Nexus 4 Original Android Development] bongostl:
I don't have any experience with this---but I would love to learn! If you don't mind passing on some info, it would be appreciated!

(in the thread, via PM, or dsbogard at the g to the mail)
[Nexus 4 Original Android Development] jtwlbz:
What's the reason not supporting cm? I hear it should be easy fix.
[Nexus 4 Original Android Development] eainyow:
Because Franco doesn't like cm :p
[Nexus 4 Original Android Development] The Gingerbread Man:
Its more how they code things, using drivers that aren't compatible with stock. Saying he doesn't like them makes it sound personal which it isn't. Its just how they work and code is being a huge pain in the butt for just about every developer and every other developer cherry picks from them incorporating codes which on certain nughtlies break things, just because cm decided to change something for what ever reason they saw fit.
[Nexus 4 Original Android Development] zephiK:
If its so easy, then why don't you "fix" it ;)
[Nexus 4 Original Android Development] TestingCharts:
CM used to be an awesome ROM. With all the crap going on there right now it doesn't feel like it's a real need. We all must say the developers of CM have great abilities but seems like they are using it (or not using it) to make money, a while ago.
[Nexus 4 Original Android Development] zorginho:
Slim has all u need!

U need only to set the DPI to 320 if u like the stock dimensions.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] sordna:
Exactly, the only scalable way to support CM, is for someone other than franco to lead the project, and modify franco.kernel for CM every time franco has a release. I believe this is already being done:

http://xdaforums.com/showthread.php?t=2487246

Maybe it will help if franco can "bless" this fork of his kernel, and add a link to hte OP.

Anyway, this is really the only scalable way to avoid slowing down development of the mainline kernel that most of us use, and as a reminder, is a 1-person effort.
[Nexus 4 Original Android Development] The Gingerbread Man:
I agree it used to be great back in the days of eclair to gingerbread i used it as stock android was slightly **** at that time and it was the best and most featured rom at the time. Now android has changed to be great, beautiful and very functional without needing to mess around too much. Cm have changed from just Steve and Kouch to a whole team and buissnes making software that can can ship on opo n1
[Nexus 4 Original Android Development] Jurai:
main issue I see with CM at the moment is that they build off latest AOSP, which unfortunately has issues on the N4 as the branches beyond JWR see the deadlock problems with the graphics driver, probably won't see a solution til google drops kitkat
[Nexus 4 Original Android Development] zephiK:
JWR has never received AOSP. AOSP has always been the JSS series. JSS AOSP ROMs resolved the deadlock issue by using the same JSS base but with a JWR Kernel. I've been using Carbon which is on JSS with a JWR kernel and have had 0 deadlocks.
[Nexus 4 Original Android Development] wildestpixel:
JWR66x does have AOSP in the form of 4.3 r1.1. JSS is r2.2.
[Nexus 4 Original Android Development] TestingCharts:
I went stock because of deadlocks and Franco. I don't regret it and I'm really fine with that. If CM go back to full AOSP and the new KitKat sources solve deadlocks, I'll probably go back to CM. There are some very useful things on CM, but not that essential.

For me, it's CM or stock. I don't like PA or any other ROM.
[Nexus 4 Original Android Development] hencke:
Do you use undervolting? On my device I got music stutter and glitches when I searched for the maximum stable undervolting. I had to reduce the undervolting by one step to get rid of the problem.