yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] RohanM:
phew.. ohk then will try it now. I am out of thanks, so thanks mate. :)
[Nexus 4 Original Android Development] 4NDR345:
I reboot and tried a reflash...but its still on...it woke up on double tap and long press....
[Nexus 4 Original Android Development] franciscofranco:
I don't know what the frack you guys are doing with your phones. I showed you all the source code, its OFF by default. If its on in your phones that's your own derp and I got nothing to do with it.
[Nexus 4 Original Android Development] rirozizo:
flashing a kernel breaks multiboot, you have to reflash multiboot for the boot screen to show up.

Sent from my Nexus 4
[Nexus 4 Original Android Development] farmerbb:
Just reboot to recovery, go to Advanced -> MultiROM -> Inject current boot sector and MultiROM will show up again. You need to do this every time you update the kernel.
[Nexus 4 Original Android Development] giovaorama:
Try to disable usb debugging form the developer options and the usb fadt charge from the fku

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] kecinzer:
Ha! Finaly someone else who have problem with ossacional long wake up time. I have this issue too!
[Nexus 4 Original Android Development] Cantacid:
Man [MENTION=3292224]franciscofranco[/MENTION] this bootpulse at 1,000,000 and input boost at 918Mhz has worked wonders on battery! Why would i want to update now!

Only if the mic gain is introduced!

Sent from my Nexus 4 now Free
[Nexus 4 Original Android Development] theclaytons:
[KERNEL][GPL][N4] franco.Kernel - r190 - JWR & JSS

+1

At least make this an option or default settings in FKU. Battery saver vs performance or similar. Didn't that used to exist a few months ago?

EDIT: Sorry, that sounded rude. It would be great if there were default settings for battery saver, performance etc.
[Nexus 4 Original Android Development] Testraindrop:
You can make different system profiles yourself (old FKU) and even set everything specifically per app as you wish...
[Nexus 4 Original Android Development] franciscofranco:
I don't want to be a party crasher but there's a bug on r190 that will boost the device to hispeed_freq if input_boost_freq is lower than hispeed_freq, so I'm pretty sure you ran all day with 1,2GHz touch boost. So mentally you thought you were running in a power-saving mode, while you actually weren't and still you see great battery life. See how placebo works? Unless you decreased hispeed_freq too, in which case I'm wrong :)

Anyway pushing r191 now, exciting new changes.
[Nexus 4 Original Android Development] MaxFTW:
Haha, Franco The Minds Controller :D
[Nexus 4 Original Android Development] Whosdaman:
r191 is up now on the server, the non-JSS version. Wonder what the new exciting changes are?! :)
[Nexus 4 Original Android Development] RiThBo:
Are you still working on the doubletap_to_wake? Or is that a low priority? I think it would be a really useful feature.

Just wondering.
[Nexus 4 Original Android Development] franciscofranco:
r191:

* interactive changes: input_boost_freq down to 1134MHz, but boosted duration was increased from 0.25s to 1s

* Fix a bug on interactive where it would boost to hispeed_freq instead of input_boost_freq

* Fix cores_on_touch functionality of the hotplug driver which was broken for a while. You can now choose to online more cores on touch if you want

* Add mic gain sysfs to sound control. echo X > /sys/class/misc/soundcontrol/mic_gain

* Boost speaker gain from 12 to 15 again

Please test the mic gain thingy and let me know if it works, I'm not 100% that I figured the correct register.

Its still priority but I had other things to work on first - I always give priority to UI interaction stuff before I mess with features.
[Nexus 4 Original Android Development] MaxFTW:
JSS is available now as well

---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------

@franciscofranco I guess you should update this info in OP as it may be misleading as CM is using CAF stuff now
[Nexus 4 Original Android Development] MaxFTW:
(Delete it please, something's wrong with xda and it doubled my posts)
[Nexus 4 Original Android Development] limeaide:
I bet they are using a fork of the kernel. One of those created by other members.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Cantacid:
Wtf, thats a bummer. Placebo to the core, damn you.

Anyhow updating to r191 now. This time i shall not bow down to them placebos.
[Nexus 4 Original Android Development] Arstoien:
Unfortunately the cores on touch doesn't seem to work as it should. It offlines the cores as soon as you lift your finger. I'd think it should keep the extra cores online for the bootpulse duration?

PS: Not really a feature I use or think is needed given the performance of two cores online and the flexibility of the rest of the tunables. Just reporting.
[Nexus 4 Original Android Development] franciscofranco:
Yes I will do that.
[Nexus 4 Original Android Development] limeaide:
I don't remember if you said you would or not. But did you merge the faux sound patch to make his sound so work? Stupid autocorrect .:(

Sent from my Nexus 4
[Nexus 4 Original Android Development] hughfollett:
Let's hope someone reads the OP before flashing ;)

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] JaMeVu:
r191 great speaker sound with smooth screen performance !

Good job franco thanx a lot

Nexus 4 üzerinde Tapatalk ile gönderildi now Free
[Nexus 4 Original Android Development] pitjago74:
I think the same.....+1

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] David9519:
4 cores on touch work now for me and gives me a great smotheness :)
[Nexus 4 Original Android Development] franciscofranco:
I dont need to merge any of his patches I just need to change the sysfs entries name, which I forgot, but will do next release.
[Nexus 4 Original Android Development] Redneck Trash:
[MENTION=3292224]franciscofranco[/MENTION] Since you're working on a new version of fKu thought I'd remind you that the headset gain is messed up in the current version. A negative value increases gain, positive value decreases gain.
[Nexus 4 Original Android Development] Deeco7:
I updated to r191 via FKU and now everything stutters like mad!
[Nexus 4 Original Android Development] Redneck Trash:
No stutters here. Did you clear app data and reboot?
[Nexus 4 Original Android Development] Deeco7:
I used the auto flash option in FKU and did what you said just now and it made no difference. Very bad stuttering!

Would appreciate quick resolution, thanks.
[Nexus 4 Original Android Development] Redneck Trash:
If you're on a custom ROM there's a chance fKu downloaded the wrong version. Go to the OP and manually download the correct .img version for your ROM. Then move it to /sdcard/franco.kernel_updater/kernel_backups and flash through fKu.
[Nexus 4 Original Android Development] Deeco7:
Your right. Found that it flashed a JSS version. If this is known, then why hasn't the download function been disabled in FKU? I know Franco is re-writing the app, but still. Many thanks for your help, much appreciated!
[Nexus 4 Original Android Development] Redneck Trash:
He's aware of it but ultimately it's Google's screw up because what's in AOSP is different from what was pushed to the Nexus 4. If Google doesn't have it's **** together with 4.4 Franco's head might explode.
[Nexus 4 Original Android Development] JNewms:
I'm really liking 191 so far. Massive improvements in smoothness over 190. Great job Franco. I really am liking the new FKU UI, as well!
[Nexus 4 Original Android Development] Grover289:
If r191 isn't the smoothest kernel then I don't know what smooth is! There are no lags whatsoever and apps open and load as soon as I click it!
[Nexus 4 Original Android Development] swirly05:
Wi-Fi broken for anybody??
[Nexus 4 Original Android Development] arlenwoot:
Working fine here.
[Nexus 4 Original Android Development] quiquegabriel:
What is actually for the mic gain? thanks:good:
[Nexus 4 Original Android Development] franciscofranco:
What Kernel were you using before?
[Nexus 4 Original Android Development] Spartoi:
I have a minor using the app with the SlimBean ROM. For some reason, the app downloads the JSS version instead of the JWR version which the ROM uses. Any way to correct this or will I have manually flash the JWR version every time?
[Nexus 4 Original Android Development] int abacus:
. For some reason, the app downloads the JSS version instead of the JWR version which the ROM uses. Any way to correct this or will I have manually flash the JWR version every time?[/QUOTE]

You can download and flash it manually for time being. It was briefly discussed before. The app is not reading the build properly for your ROM.
[Nexus 4 Original Android Development] yoyoz808:
Happen to be on kecinzer's aokp rom?
[Nexus 4 Original Android Development] ksrokiller:
How to online more cores on touch?
[Nexus 4 Original Android Development] jarjar124:
In hotplug control

Sent from my Saber-Tooth mako
[Nexus 4 Original Android Development] drawde40599:
. For some reason, the app downloads the JSS version instead of the JWR version which the ROM uses. Any way to correct this or will I have manually flash the JWR version every time?[/QUOTE]

Its not downloading wrong build its downloading what your Roms build prop tells it to , your ROM build prop says its a jss.. ROM when that's not completely tru since it uses a jwr kernel . so FKU is working correctly
[Nexus 4 Original Android Development] nibla101:
Do 2 cores always have to be active? When I set cores_ on_touch = 1 there still is 2 cores online all the time.
[Nexus 4 Original Android Development] stark_br:
Because you have 2 cores online on touch, by default.
[Nexus 4 Original Android Development] nibla101:
Yeah I know its there by default but it stays like that when i've changed it too,
[Nexus 4 Original Android Development] NYLimited:
What are valid values / range for X?

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] franciscofranco:
2 cores is the minimum while on screen on.

0 to 10.
[Nexus 4 Original Android Development] svnhvn:
[MENTION=3292224]franciscofranco[/MENTION] : Thanks for r191 man!!
[Nexus 4 Original Android Development] Luigiesin:
Man this version is hardcore! I likes! Frack!
[Nexus 4 Original Android Development] Bobtehblob:
Could someone please tell me how to adjust the mic gain via terminal? I'm not very good with terminal commands :)
[Nexus 4 Original Android Development] Mercado_Negro:
Open Terminal Emulator and type:

Where X is a value between 0 and 10
[Nexus 4 Original Android Development] ksrokiller:
Does enable all 4 cores on touch consume more battery?
[Nexus 4 Original Android Development] franciscofranco:
On the long run I wouldn't be surprised if it did, but I don't have numbers that back this up.
[Nexus 4 Original Android Development] Cantacid:
Will the mic gain stick with a reboot? Or it restores back to default?

What do you guys suggest should the gain value be to attain just enough improvement?

Sent from my Nexus 4 now Free
[Nexus 4 Original Android Development] franciscofranco:
sysfs entries ALWAYS reset to their default values on reboot :mad:
[Nexus 4 Original Android Development] Redneck Trash:
R191 has brought back that liquid smooth feel.
[Nexus 4 Original Android Development] Bobtehblob:
What's the default value?
[Nexus 4 Original Android Development] Mercado_Negro:
As far as I can see, zero.

---------- Post added at 01:28 AM ---------- Previous post was at 01:28 AM ----------

No, it won't survive a reboot. You can use ROM Toolbox Lite to create a script that could be run at boot.
[Nexus 4 Original Android Development] NYLimited:
Thanks! One more question (wouldn't you know?)

The mic_gain file currently contains 0. Is that the default value? That suggests that I can increase the gain but I cannot decrease it which is what I was hoping to try.

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] franciscofranco:
I didn't think of negatives, I'll add it next time.
[Nexus 4 Original Android Development] NYLimited:
Thanks, dude, but I need to ask... Do you ever sleep? :p

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] Mercado_Negro:
Just a friendly FYI in case you missed it: there's only one new parameter to tweak in r191 - > max_gain. We're still missing the actual Limiter Level and Noise Gate Threshold :)
[Nexus 4 Original Android Development] giovaorama:
[MENTION=3292224]franciscofranco[/MENTION]

Just a small idea that may help you to help your app to download the right kernel version. It may be useful also for the future if you ever plan to support a specific rom that need a special build.

Anyway, why don't simply add a ro sysfs entry with the fingerprint of your kernel that the fku can read to understand which kernel version is currently installed?

Ok, this works just after the first right install but then all should work automatigically.

As many of us already stated, if someone is able to manually flash a custom rom then he must be able to understand by itself which kernel works with this rom. To all the people that complain screen tearing, gamma problems or whatelse i will ever answer nothing but rtfm and the f is not for forgotten

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] Deeco7:
In FKU it is showing me 'SLOW' under CPU Type, does that have any affect?
[Nexus 4 Original Android Development] SpasilliumNexus:
You're on a roll, aren't you? Search the thread.
[Nexus 4 Original Android Development] Andre_Vitto:
There are 4 different types of CPU bin.. slow, fast, faster, fastest.. something like that..

does not affect anything other than UV...

I think you can UV more in slower chips than faster ones or vice verse.. nothing more..
[Nexus 4 Original Android Development] Deeco7:
Some things never change in xda. Tone down the attitude, and please have a look at your previous comments and reflect.

Thanks Andre_Vitto.
[Nexus 4 Original Android Development] Yamakasi508:
Which version should I install on CM10.1.3 ??
[Nexus 4 Original Android Development] otariq:
Jss
[Nexus 4 Original Android Development] blankit:
I've read a lot of comments on how many cores should be on when the screen is touched but none seem to answer my questions. Forgive me if this has been discussed in previous posts but why does it need two cores exactly? Is the demand that high?
[Nexus 4 Original Android Development] gambe89:
Just a little correction.. The 4 different types of cpu bin are slow, nominal, fast, faster.. More info here
[Nexus 4 Original Android Development] Mercado_Negro:
I think r165 was the latest version for 4.2.2
[Nexus 4 Original Android Development] shengovind:
R169 was the last one I think..
[Nexus 4 Original Android Development] Matteo Mazzu:
Hi! I was curious to know if someone uses the per app setting and if it does really some battery improvement :) maybe with some examples of yours app setting if it doesn't mind you :) (I'mbegi nning to use it, but some tips could be useful!)
[Nexus 4 Original Android Development] giovaorama:
Look for the version for 4.2.x in the first post. It should be m3 or r164 (anyway a number below 170)

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] Andre_Vitto:
examples for you.. like when you play 3d games like asphalt or NFS then you might wanna ramp your CPU to highest.. while when you are on home screen you might wanna reduce the max cpu.. this might save a little battery for you...
[Nexus 4 Original Android Development] Arstoien:
Franco, do you wanna receive crash reports for Project Pringles?
[Nexus 4 Original Android Development] Andre_Vitto:
He mentioned in the thread that he wont.. its for visual feedback and suggestions only...

When in beta he will start looking after bug reports.. :cowboy:
[Nexus 4 Original Android Development] AndyYan:
I noticed today that CM10.2 has merged Android 4.3.1, aka AOSP JLS36I, so I dirty upgraded to the latest nightly (too much user data, too little time for a clean flash) and flashed Franco r191, but after the Google logo, the screen got covered in cyan stripes (seems to be a repeated fraction of the CM boot animation). Honestly I've searched in the thread but nothing related showed up. For reference, latest Faux (026) has this problem as well. Can anyone tell me if Franco/Faux works properly on their 4.3.1 ROMs or not? My guess is that changes need to be made to adapt to 4.3.1.
[Nexus 4 Original Android Development] forever_lol:
search "colorfix.zip" in this thread.
[Nexus 4 Original Android Development] karthi89:
[MENTION=410271]fransisco[/MENTION] franco Minimum no of cores online on touch should be atleast 2? Tried setting it to 1 via fku, but still 2 cores online on touch..
[Nexus 4 Original Android Development] Andre_Vitto:
hau.. min 2 is must wen screen on..
[Nexus 4 Original Android Development] llevo3:
this rom with r191 is the smoothest combo i've ever tried
[Nexus 4 Original Android Development] marhensa:
i tried "4" on Cores online on touch input, in Hotplug control.

from System Monitor I still notice 2 other core is offline.

is it just me or..?

FK 191

Sent from Android device using Tapatalk 4
[Nexus 4 Original Android Development] mohitgalaxy3:
Franco in 191 have you changed the default color profile, it's looking a bit blueish.

If yes, could you please tell me how to restore original colors??
[Nexus 4 Original Android Development] miniAndroidian:
Hey there :)

got a little issue with the kernels since r187 i think. Today i just flashed r191 JSS for CM10.2 and now all my colours on the screen went weird.

Blues are now yellow and orange. My bootanimation is now totally full of blue tiles.

i made a short video of the bug:

http://www.youtube.com/watch?v=ad_4Eh83uAE
[Nexus 4 Original Android Development] Bill Gamble:
This has been discussed ad nauseum. Search this thread for "colorfix.zip".
[Nexus 4 Original Android Development] yousseefs:
Disable? Oo
[Nexus 4 Original Android Development] myweca:
Hello there!

I am using franco.Kernel 191 JSS NIGHTLY with CM10.2-20131011-NIGHTLY.

I also installed the colorfix.zip, so everyhthing is OK.

My question is:

How can I get back to stock CM?

How can I uninstall franco.Kernel and the colorfix?

Apparently only flashing CM10.2-20131011-NIGHTLY is not enough, I must also Uninstall the ColorFix - but how can I do that?

:confused::confused::confused:

Thanks!
[Nexus 4 Original Android Development] Bill Gamble:
You can't disable the system monitor, but you can decrease the resources it uses by turning off battery history (system monitor/settings/app)
[Nexus 4 Original Android Development] Tennic:
"Format system" (in recovery) will remove the rom, kernel, and Colorfix (which is in a folder system).

Next, install the rom CM 10.2 you want ... Council also wipe cache and Dalvik ;)
[Nexus 4 Original Android Development] myweca:
Thanks!

Well, since I am gonna do everything from scratch, I think it is time to flash.... Paranoid Android!

Thanks again!

:D:D:D
[Nexus 4 Original Android Development] Tennic:
If you're going to change rom, I advise you to do also factory reset ;)

Otherwise, if you want to leave the same rom (or later), you can also do not factory reset, and retains all the apps, data and settings. I always do that to switch from one nightly to the next ;)
[Nexus 4 Original Android Development] anurag549:
working grt with crdroid!!!
[Nexus 4 Original Android Development] sysak:
Would anybody know why sometimes when i'm playing music with Google Play Music and the phone is sleeping the sound stutters and breaks. It happens to me sometimes with this kernel and I haven't been able to fix it with any settings. I've seen that few people were complaining about this but there was no definite answer to this.
[Nexus 4 Original Android Development] mitchdickson:
What's your suspend frequency? And are you undervolting?
[Nexus 4 Original Android Development] cAase:
Yesterday while running for the buss i dropped my N4 on the asphalt. Got a little crack on the top right, about 1x1 and now only half of the touch is responded :( For an example when i'm going to write , my pin code i can only press 1,2,3,4,5, but not the rest, and back button.

How does warranty answer to this? I guess they'll tell me to fk off :D
[Nexus 4 Original Android Development] wildestpixel:
Post in General Nexus 4 please. Your unfortunate drop is nothing to do with Franco dev.
[Nexus 4 Original Android Development] Pipusz:
In Hungary, warranty doesn't include dropping the device. Not sure about other countries.
[Nexus 4 Original Android Development] CoolApps:
Since it is just hardware they shouldn't complain about anything, even if you need it stock you can just go to the bootloader and flash the stock rom.
[Nexus 4 Original Android Development] cAase:
True that, I forgot. Since 50% av all time being spent is on this forum it felt natural posting it here. Haha i'll try in general section.

Thanks.

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

True that, I forgot. Since 50% av all time being spent is on this forum is on franco felt natural posting it here. Haha i'll try in general section.

Thanks.

---------- Post added at 05:11 PM ---------- Previous post was at 05:10 PM ----------

True that, I forgot. Since 50% av all time being spent is on this forum is on franco felt natural posting it here. Haha i'll try in general section.

Thanks.
[Nexus 4 Original Android Development] bardriel:
Where I can find the changelog for the r165 for cm10.1? I can´t find any changelog.

Btw, is there any problem with this kernel or I can use it without any problem?
[Nexus 4 Original Android Development] wildestpixel:
Its not just you I also "see" the same both on Mako and Flo.
[Nexus 4 Original Android Development] franciscofranco:
Sometimes ;)

Yes, don't worry I didn't forget ;)

That won't work. The only way for this **** to be finished is for 4.4 to drop, that's what I'm counting, I'm tired of 4.3.

Two cores are always online no matter what you do. When it screens off the second core goes offline for the device to enter in its deepest deep sleep mode. When the screen is back on it goes back to two cores. Not that the demand is that high, but onlining/offlining cpu1 all the time does more harm than good, so rather just leave it on.

Nope, not yet ;)

Minimum is 2 cores online always.

System monitor polling time is 1 second, if you just touch the display the cores will come online/offline faster than the application can notice. If you swipe a little bit you'll see the cores in the monitor because while you're touching it won't turn them off.

Of course I didn't change the colors on r191 -.-
[Nexus 4 Original Android Development] nexusmaniac:
Hey Franco, does flashing the userdata.img for your AOSP ROM wipe all of my data?
[Nexus 4 Original Android Development] The Gingerbread Man:
It would wipe all your stuff
[Nexus 4 Original Android Development] nexusmaniac:
Thought so, just checking :) I don't need to flash it for his ROM to work though do I?
[Nexus 4 Original Android Development] wildestpixel:
Probably best to titanium everything up, clean flash his AOSP and titanium everything back.

You may be asking for a lot of FC trying to retain your data and go from one rom to another unless its complete stock to complete stock or pure cm to pure cm etc etc.
[Nexus 4 Original Android Development] nexusmaniac:
I'm wiping the system, data and cache partitions but to my knowledge if I flash userdata.img then it'll wipe the internal SD card, which is something I don't want :)
[Nexus 4 Original Android Development] wildestpixel:
copy your files by USB to a computer including your obb's etc.

I only ever use stock via fastboot flashing and i can be reflashed and up and running as if nothing happened in about 30 mins flat with titanium backup, copy titanium files and other media and obb's to my laptop and back etc.