yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Danny.ns:
I cleared data (checked box for boot) and installed 176, and haptic feedback was set to 100 as default. I use stock JWR rom.
[Nexus 4 Original Android Development] aventu:
I like that operator
[Nexus 4 Original Android Development] Mercado_Negro:
Make sure to set it to 100 as well in the ROM itself (Settings/More). Yeah, we've only had two governors for a few builds already.
[Nexus 4 Original Android Development] riza_hakam:
[MENTION=3292224]franciscofranco[/MENTION]

i flash your r176 jwr, but I didn't understand where it goes wrong.. but it always reboot to recovery.. it boot and until nexus logo shown.. but after that suddenly it reboot to recovery.. i flash your kernel, wipe dalvik cache and partition cache.. is there something wrong with my way? please enlighten me
[Nexus 4 Original Android Development] zephiK:
Haven't been on Franco since 4.2, played around with the unofficial but didn't stay on it for too long.

No... that depends on ROM, my ROM doesn't have vibration settings under settings -> more. Plus I feel the difference
[Nexus 4 Original Android Development] Mercado_Negro:
Sorry, I don't know why I thought you were on cm10.2. My bad.
[Nexus 4 Original Android Development] ScoolAir:
what about stable version? in the future?
[Nexus 4 Original Android Development] Surgik:
Are you flashing a boot img cause you're going to want to flash the zip (?)
[Nexus 4 Original Android Development] Mercado_Negro:
Which ROM, Recovery?
[Nexus 4 Original Android Development] resynx:
Looks like there's a new toy to play with tonight :) Thanks Franco :good:
[Nexus 4 Original Android Development] Chintao:
WoW you are the man! Just in time, as always! i <3 you. flashed it about 5 minutes ago, working fine so far with cm 10.2, undervolted by 100 overall, smooth as always. will tell you any bugs i will encounter ;)
[Nexus 4 Original Android Development] ScoolAir:
i flashed the JWR #176 on my PA 3.96+, in the franco updater its say i have #177 and the latest nightly version available is #176, how?
[Nexus 4 Original Android Development] Chintao:
franco already answered this question:
[Nexus 4 Original Android Development] schizophrenia:
a couple of pages back he already said it's a minor mistake

don't worry about it. it's 176
[Nexus 4 Original Android Development] bixano:
It's a mistake, franco already talk about it !
[Nexus 4 Original Android Development] ScoolAir:
ah ok
[Nexus 4 Original Android Development] andyli1985:
:)

Edit: ninja'ed
[Nexus 4 Original Android Development] franciscofranco:
What SU is PA using by default? SuperSu or Superuser by Koush?
[Nexus 4 Original Android Development] Jens1969:
Superuser by Koush
[Nexus 4 Original Android Development] namartlu:
Running CM 10.2 with franco kernel R176 JSS version. Understood that benchmark score doesn't mean a lot, but my quadrant score is 4412... with stock CM10.2 I think I got 5xxx by default... Something I need to fine tune? Thanks!
[Nexus 4 Original Android Development] Pure Drive GT:
I think all major rom devs prefer open source superuser cause they like to integrate it into the rom :)

Btw how is the first cm 10.2 nightly keeping up? ;)
[Nexus 4 Original Android Development] Mercado_Negro:
Good so far.
[Nexus 4 Original Android Development] eezak:
Yay the hybrid radio seems to have fixed the need to enter pin code randomly, since this morning I did not have a problem thanks !
[Nexus 4 Original Android Development] ghul21:
First kernel which doesn't break root on jss slim bean ;)

Awesome :D

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] digitalfrost:
r24-test has strange battery behaviour. Phone was at 99% shortly after I unplugged it. Now I turn the screen on an battery is at 100% after 1h18mins. Battery app shows just a flat line.
[Nexus 4 Original Android Development] yokuyuki:
I think they're just disabling latitude.
[Nexus 4 Original Android Development] lazer155:
Don't you need latitude and location reporting on for google now to work?
[Nexus 4 Original Android Development] Vangelis13:
Known bug, hopefully (surely) 4.2.2 will take care of it.
[Nexus 4 Original Android Development] ceejay83:
No works fine if you disable latitude location reporting
[Nexus 4 Original Android Development] shamu11:
Yeah I don't get it...
[Nexus 4 Original Android Development] scream4cheese:
I thought you were going back to trinity. Lol
[Nexus 4 Original Android Development] franciscofranco:
Guess she's back here :victory:
[Nexus 4 Original Android Development] Vangelis13:
Good ol' benrees21. Lady of mystery.. ;)
[Nexus 4 Original Android Development] squadz:
How would you do that?
[Nexus 4 Original Android Development] estallings15:
I love how everyone thinks Ben is a chick.

I have zero problems to report with r24. It runs like a champ and battery life is great.
[Nexus 4 Original Android Development] Vangelis13:
:thumbup:
[Nexus 4 Original Android Development] m3lover1:
It does seem like my signal is couple bars lower than r24. Might just be a placebo effect though as my signal is kind of inconsistent at my house anyways. Also maybe cause I keep reading about the supposed data issues here and check the signal more frequently than before and happen to look at it when it's fluctuating. Either way r24 is working great for me. Only thing I changed was I/o to row.

:thumbsup:
[Nexus 4 Original Android Development] benblb:
Go to Maps/Settings/Location settings/

Then turn off "Location reporting" and uncheck "Enable location sharing". For best Google Now results, check "Enable location history".
[Nexus 4 Original Android Development] benrees21:
I love it too Lol. Yea I'm back here. Battery is epic on this kernel. Franco, you dropping r25 soon or tomorrow? It's like 2:20AM here and I'm thinking of just going to sleep.

You can all imagine I'm the woman in my avatar if it makes you feel better! Hahaha :p

Because I'm a Nexus b!tch and I like to run the latest source and binaries!! AOSPA!!!
[Nexus 4 Original Android Development] shamu11:
Thanks mate!
[Nexus 4 Original Android Development] TheByteSmasher:
Who is the woman in your avatar?

Sent from my Nexus 4
[Nexus 4 Original Android Development] benrees21:
Eve Myles. Actress. Big here in the UK.

A Nexus b!tch called Ben (Work that one out :P) AOSPA!!!

---------- Post added at 02:50 AM ---------- Previous post was at 02:42 AM ----------

I'm going to bed. See you tomorrow people. Look forward to flashing the update.

A Nexus b!tch called Ben (Work that one out :P) AOSPA!!!
[Nexus 4 Original Android Development] ayamary:
I still love you
[Nexus 4 Original Android Development] k_nivesout:
I've been flashing Franco on and off, mostly on :), since ~r14. I've got to say though, not until r24 test have I finally started to get the battery performance a lot of others seem to have. Wakelocks have been pretty dramatically reduced for me, even compared to r23. I've been on Wi-Fi most the day, but haven't noticed any data issues whatsoever.

While I feel like the stock kernel is ever so slightly smoother, the reduced wakelocks and cooler phone definitely make Franco's kernel worthwhile for me :) And to think this is even without UV is exciting!
[Nexus 4 Original Android Development] Karlo666:
I just flashed r176 but in about phone it says r177 .I'm running stock OS
[Nexus 4 Original Android Development] wvcadle:
I freakin' love the way you deal with certain kinds of questions! And when I ask one (I'm sure I will), be sharp with the tongue!
[Nexus 4 Original Android Development] Davirus849:
Working nice so far. (PSX rom)
[Nexus 4 Original Android Development] sordna:
already answered, it's just a cosmetic bug (typo), safe to ignore it :)
[Nexus 4 Original Android Development] snak3ater:
V.176 broke the root in latest PA..

Anyways who cares.It just take a sec to flash SuperSu ;)
[Nexus 4 Original Android Development] Bobtehblob:
Surprisingly solid. Only issue i've had is trebuchet being well... trebuchet. Having the odd close/ icon moved dissapeared on reboot... :confused:
[Nexus 4 Original Android Development] ghul21:
I prefere Kouch's superuser ;) on slim works well. Simply love it ;)

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] franciscofranco:
So thats the bloody reason. Thanks.
[Nexus 4 Original Android Development] Flypwnz:
My phone reboots to recovery after boot :( All is fine with 164. Stock 4.3 without mods.
[Nexus 4 Original Android Development] wvcadle:
I came home to Carbon late last night, and home to Franco today. Both official, with nightlies to come.

Within seconds of installing Franco, I noticed an immediate boost in... um... 'zip'. This damn thing just flies. I am partial to Franco's kernels, but subtracting that out of the equation, I'm very happy with the performance I'm getting out of this with Carbon.

Now on to see how battery life is over the next couple of days!
[Nexus 4 Original Android Development] max4wdc:
164 is for 4.2.2 not 4.3 , you must flash 176 for 4.3
[Nexus 4 Original Android Development] franciscofranco:
And what can we do about it? Something is fúcked there, r164 is for 4.2.2.
[Nexus 4 Original Android Development] silviu_iliescu:
Saw the update Franco. Does the new kernel brake root or not? Thanks in advance!!! :)
[Nexus 4 Original Android Development] Flypwnz:
Sorry :) 174 version.
[Nexus 4 Original Android Development] franciscofranco:
Oh yes I forgot to say you can now choose the touch boost duration. Default is 1000 = 1s. Path is /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq_duration

Increase that value for more smoothness, but kiss goodbye to your battery. Decrease for the contrary effect.
[Nexus 4 Original Android Development] Redneck Trash:
Apparently it does with Superuser. I haven't had it happen with SuperSU.
[Nexus 4 Original Android Development] sordna:
Did you flash the kernel zip or img? Try to flash the .img with usb cable, ie: fastboot flash boot boot-r176.img

If that's what you already did, try to flash the .zip with your recovery. One or the other should fix your problem.
[Nexus 4 Original Android Development] wvcadle:
Is it too hard to ask one to flip back through the pages to find the post regarding a new release, and at least read forward from there.

I mean, I have asked many a question that was previously answered, but I always at least try to search for the answer first.
[Nexus 4 Original Android Development] sordna:
I have an idea, but it would be more work for Franco: Whenever he updates the thread topic with the new version, he could also edit the OP and add a link to the post that is announcing that version. Maybe even keep links to 1-2 previous kernel announcements.

This way, folks that don't check xda every day, can easily jump to the right page containing the version announcement.
[Nexus 4 Original Android Development] Flypwnz:
Tried both, but no luck.
[Nexus 4 Original Android Development] wvcadle:
As for me, I'm perfectly happy with the amount of work Franco is already doing.

It took me all of about 60 seconds to flip back and find the post where he announced the new kernel.

Here are the steps I took:

1. Went to the original post. Found the build #.

2. Searched the thread for the build#.

3. Found the post and read from there.
[Nexus 4 Original Android Development] Chintao:
someone with brain!
[Nexus 4 Original Android Development] Nocturnal86:
Im sorry but you are quite dumb... Exuse my language. This is his firs nightly for 4.3 and you excpect it to be perfect? wtf? What kind of thinking is that? COME ON but peace no one is keeping you here...
[Nexus 4 Original Android Development] sordna:
Did you try flashing back to 174 ? As a last resort you could flash stock boot.img and stock recovery.img to get the phone working again, and then try to reflash to the custom stuff. It's weird that your phone always boots into recovery! ... Unless a volume button is stuck :)
[Nexus 4 Original Android Development] Nikos69:
is volume boost or headset gain working in R176? thx
[Nexus 4 Original Android Development] Flypwnz:
I completely reinstalled my rom with factory image and now it works :)
[Nexus 4 Original Android Development] Nocturnal86:
Franco just cleared FKU data and installed 176 and went into settings to change theme to blue holo then I went to change update checker to manual and when I selected manual the FKU force closed the setting stuck but it still forced closed. Just thought id let you know.
[Nexus 4 Original Android Development] Remoteconcern:
Same. Exactly the same situation.
[Nexus 4 Original Android Development] drawde40599:
I Didn't have any of the issues u do, and his kernel is fully tweekable to your liking so.......
[Nexus 4 Original Android Development] JeroenGijselaar:
[MENTION=3292224]franciscofranco[/MENTION] May I know what ROM you are currently running? :D
[Nexus 4 Original Android Development] derPianist:
so that means you can fix it ? :3

P
[Nexus 4 Original Android Development] Cuzz1369:
Is the app gonna be able to tell what build we are on to flash the proper kernel or is gonna have an option on which version to flash?
[Nexus 4 Original Android Development] mountainloafers:
Really jss support? For realz?

PSX - unofficial r175 - exposed moded - N4

Shoot I got like 30 pages to lurk upon...

PSX - unofficial r175 - exposed moded - N4
[Nexus 4 Original Android Development] zephiK:
I have absolutely no idea what you're saying. Yes there is JSS official support now.
[Nexus 4 Original Android Development] Luigiesin:
LOL! Me neither :)

Sent from my \m/ Nexus 4

ROM: PA 3.96

Kernel: Franco r176
[Nexus 4 Original Android Development] Karlo666:
I after flashing lastest r176(r177 is apparently for stock Google)and using it for about 2 hrs i experienced several slowdowns and deadlocks.
[Nexus 4 Original Android Development] mefistos:
Franco will FKU know if I use JSS or JWR when downloading next build? Or is it working right know like that?
[Nexus 4 Original Android Development] franciscofranco:
JSS bug.
[Nexus 4 Original Android Development] franciscofranco:
Dunno havent thought about it.
[Nexus 4 Original Android Development] franciscofranco:
App doesnt know which Android build you're at. I wrote that in the changelog.
[Nexus 4 Original Android Development] Karlo666:
In running JWR66V not JSS
[Nexus 4 Original Android Development] Shano56:
Can a root app not look that information up?
[Nexus 4 Original Android Development] mefistos:
But it will work right?:)
[Nexus 4 Original Android Development] mountainloafers:
Hey, thanks for the correct answer, clueless.

PSX - unofficial r175 - exposed moded - N4
[Nexus 4 Original Android Development] Haomuch:
Just updated the jwr r176 img and it shows as r177. Want to know whether the headphone volume boost work now and if touch control module is supported.
[Nexus 4 Original Android Development] Karlo666:
Can you tell us is r176 or r177 for Stock Google so i can flash via fastboot??
[Nexus 4 Original Android Development] yonpa:
Thanks franco. The new version works great for me, better than others kernels that I tried. Jss build
[Nexus 4 Original Android Development] namurt:
[MENTION=3292224]franciscofranco[/MENTION]

please, oh pretty please, won't you consider changing the official fku app icon to stifler? if only for a week, the hilarity of the inside joke would bring joy to me, and i assume many others as well. :)

p.s. i'm about to return to school for the first time in over a decade, having many a year gone-by from when i first started off toward a comp sci degree. it was a degree i never finished, but dedicated devs like you inspire me to go back and get it done. :good:
[Nexus 4 Original Android Development] jdayscokn:
there is only 176, the 177 was essentially a typo on Franco's part. Works on jwr and jss now
[Nexus 4 Original Android Development] Karlo666:
Well i just flashed the boot.img seems its good now.

I wanted to know which one of these two are r177(costum ROM) boot-r176-JSS.img or boot-r176.img
[Nexus 4 Original Android Development] jdayscokn:
The 177 was a build typo on Franco's end. It is 176

He said; Ups ￼ its supposed to be r176, I forgot to change the .version number when I changed branches. Not a problem though.
[Nexus 4 Original Android Development] cpanos:
Having the app check build version can be tricky. For example, the latest paranoid android rom is marked as a jss build while it requires jwr kernels.
[Nexus 4 Original Android Development] szkorhetz:
Just tried r176 and everything seems to be much smoother even the game. (my son loves the game, so it is a main factor)

Thans for your work.
[Nexus 4 Original Android Development] elite_gamer04:
Obviously a new addition as I wanted to check what the default was on r174 but doesn't exist. Could you tell if the new value of 1000 is more or less, because I've had no issues previously and don't want battery life to change. Thanks!
[Nexus 4 Original Android Development] Cuzz1369:
So for now the app will only download JWR?

Just to be clear.
[Nexus 4 Original Android Development] elite_gamer04:
Still having issues setting Max GPU Frequency to 325Mhz in FKU 4.1.2 with r176. I select in either System-Wide Power Mode or Voltages option pages but it does not sick when you go to another page and back in, interesting enough when you try to select any other Mhz other then 325 it's fine...

Anyone experiencing same bug? I've rest App Data twice and even moved from r174 with no luck...
[Nexus 4 Original Android Development] brian88:
Excuse me, how could I use the Kernel backup/restore in Franco's app

Sent from my Nexus⁴
[Nexus 4 Original Android Development] simorangkir_dcs:
Use it to backup and restore your kernel or to flash new kernel. Put boot.img in kernel backup folder and you can restore/flash via fku app
[Nexus 4 Original Android Development] digkong:
hello..

i fashed v176 on stock jwr, but the phone reboots into recovery everytime..

finally i fashed the stock img to get it to boot..!!

bdw i tried to log it,googled it actually.. but was unable to ..

so if you would tell me how to do it,ill pull the log file and give..
[Nexus 4 Original Android Development] simorangkir_dcs:
Never happened to me. Maybe you flashed the wrong zip or img?

Did you flash it via recovery, fastboot, or fku app? You can try other way if one way didn't work
[Nexus 4 Original Android Development] digkong:
downloaded both zip and img.. tried both.. but did not work.. finally had to flash stock img.

and am sure I did download the correct version.
[Nexus 4 Original Android Development] Droid2drummer:
Usually I Dont flash custom kernels on stock as it may need the stock values and assets but god knows things change in this environment. Lol
[Nexus 4 Original Android Development] sordna:
franco.kernel is designed primarily for stock. So you can safely use it, and if you are worried about values and parameters simply don't tweak them :) I love the fact this kernel doesn't use kernel modules, making it much less intrusive that other custom kernels that install all kinds of stuff to your /system/ ... This one doesn't.

.img rulez !
[Nexus 4 Original Android Development] bigknowz:
@ilarrain comment on GNex thread

franco, not sure if you saw this from [MENTION=3313300]ilarrain[/MENTION] on GNex thread, I see you're more active here.
[Nexus 4 Original Android Development] svnhvn:
Did you update your recovery? Mine always looping like that if i update either cwm or twrp.
[Nexus 4 Original Android Development] kevin0164:
Just update from r174 to r176 via FKU.

Everything's fine.

Thanks [MENTION=3292224]franciscofranco[/MENTION], what a great work!!

It feels like even more smoothy than r174.
[Nexus 4 Original Android Development] Karlo666:
The main thing i want to ask:

Is franco app downloading JSS or JWR version of kernel.

Thats why i asked wich one is r177 and i know it states r177 on both.

I flashed earlier via app and i got problems(slowdowns,deadlocks)until franco said its JSS bug then other people report thats all fine.

So it seems it flashes JSS version sometimes via app.
[Nexus 4 Original Android Development] BigDig:
No it doesn't! App flashes only JWR! Of course if you download the IMG file manualy, you can flash it with the app, but you can't download it from the app
[Nexus 4 Original Android Development] jdayscokn:
Download r176jss here

http://minooch.com/franciscofranco/Nexus4/4.3/
[Nexus 4 Original Android Development] scandalousk:
The app only downloads and flashes the JWR version of the kernel. If a person would like to have the JSS version, they'd have to download it manually from the ftp and flash it manually as well. Also, R177 does NOT EXIST, or has yet to be released. The most current released nightly is r176. r176 is the most up to date version for both JWR and JSS. The app showing r177 is due to the fact that franco made a typing error when he made the kernel, typing 177 instead of 176.
[Nexus 4 Original Android Development] riza_hakam:
first i flash via cwm, and then after i face this reboot problem i flash via fastboot, but it still happen

stock rom rooted, cwm recovery but not the last version..

it seems i am not the only one face this priblem.. i tried both via cwm and via fastboot but still it reboots to recovery.. so i flash again r174 and it's fine..

can anyone tell me what is wrong? because i can't find what make it goes wrong
[Nexus 4 Original Android Development] dapsANDpoundz:
Updated to r176 no problems here.
[Nexus 4 Original Android Development] franciscofranco:
Of course there are no problems, everything works as it should :)
[Nexus 4 Original Android Development] Luigiesin:
Hey man.. 176 feels with more Flow than 174! Like like!

Sent from my \m/ Nexus 4

ROM: PA 3.96

Kernel: Franco r176
[Nexus 4 Original Android Development] franciscofranco:
Yes, there were some good improvements on r176 :)
[Nexus 4 Original Android Development] drawde40599:
There is no 177, read the op, and read few pages back,
[Nexus 4 Original Android Development] elite_gamer04:
Cannot for the life of me get this working... Max GPU Frequency set to 325Mhz will not stick - tried setting via the Frequencies/Voltages and Default System Mode option pages and as soon as you flick off the page and back, its reset to 400Mhz. My root is in tack (SuperSU v1.51) as other Apps/Options within FKU are fine...).

Ideas?
[Nexus 4 Original Android Development] Mercado_Negro:
Will the app have this in the future?
[Nexus 4 Original Android Development] Redneck Trash:
I just tried setting the GPU to 325 and had the same result. Don't know if the app is reporting it wrong or if the setting just doesn't stick.
[Nexus 4 Original Android Development] jamel_tza:
Perhaps, In the meantime try TricksterMod. Its good for super fine-tuning kernel settings.
[Nexus 4 Original Android Development] elite_gamer04:
Huzzah - I'm not going mad, thank you for confirming :). Hopefully Franco will see it (might already be fixed in Beta FKU...). What is the manual file path for GPU Freq?
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks for the suggestion but I'm not in a hurry, I can wait for Franco if he decides to add it :)

I use TricksterMod for stock kernels, not Franco's :thumbup:
[Nexus 4 Original Android Development] Redneck Trash:
I'm using the beta. I don't know what the file path is.
[Nexus 4 Original Android Development] resynx:
Amazing :D This kernel makes PA smoother than the stocker kernel does! ;):highfive:
[Nexus 4 Original Android Development] blueren:
Franco how come your thread doesn't have the DevDB tag attached?
[Nexus 4 Original Android Development] apatal:
I flashed r176 but my phone says it's #177. HALP! :D
[Nexus 4 Original Android Development] sub1287:
Just went back to stock 4.3 and figured I'd give this kernel a go and so far so good!
[Nexus 4 Original Android Development] leets4uc3:
Holy Fúck.
[Nexus 4 Original Android Development] KiD3991:
We're going to repeat again and again. Its a typo. Nuff said.
[Nexus 4 Original Android Development] Redneck Trash:
I think the big smiley face indicates he knows that.
[Nexus 4 Original Android Development] sub1287:
Lol calm down people it was funny.
[Nexus 4 Original Android Development] ranasrule:
JSS15 official franco kernel?? did I miss something ?
[Nexus 4 Original Android Development] Dark Emotion:
Yeah, you missed the OP