yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Stretlow:
Was an interesting read that, im not an expert but from this it looks like the ASOP build has massive improvements, especially in the kernel.

Doesn't it the make sense then for devs to use this latest version of the kernel rather than the older one?
[Nexus 4 Original Android Development] Sukhi:
Yes it has for sure....the JSS build outperforms the JW in battery and performance. The idle battery drain is equivalent on both the builds but you can easily manage to get better SOT on JSS w/o compromising on the performance. I have been monitoring them closely and the JSS kernel governor is the real game changer.
[Nexus 4 Original Android Development] Roye_V:
If I'm using 4.2.2, what's the newest build I can flash?

does r172 also fits 4.2.2?
[Nexus 4 Original Android Development] Stretlow:
Sorry for my ignorance but given what you've said above why would anyone then bother with the development of the JW version if the JSS is superior?
[Nexus 4 Original Android Development] jak3z:
r165 or Milestone 3

172 is 4.3 only
[Nexus 4 Original Android Development] Danny.ns:
r165 is the latest you can use for 4.2.2. r172 does NOT work with 4.2.2.
[Nexus 4 Original Android Development] bombadier:
Read the OP properly,M3 or r165 for 4.2, r172 for 4.3(and only ROMs based off JWR66V at the moment)

Tapatyping from my Nexus
[Nexus 4 Original Android Development] blsrbl:
Nope. r165 or M3 are the latest for 4.2.2. r172 for 4.3.
[Nexus 4 Original Android Development] mountainloafers:
I too am hoping someone might be able to provide stock values for 4.3 color settings. Haven't been able to make adjustment that I like better and want to go back... ;)
[Nexus 4 Original Android Development] franciscofranco:
I forgot to merge Fast Charge.

Stock colors are 100% the same on 4.2 and on 4.3. The colors I ship this Kernel with have been merged since r14 or something.

My app does not hold any wakelock, does not waste any battery. Thats just a coincidence.

1 - I forgot to merge Fast Charge.

2 - Coincidence. You rebooted to flash stock Kernel, all you possibly needed was just a reboot, and thats what you did.

1 - That has been like that for a while

2 and 3 - I believe thats a problem with the SU binary, I have the same problem and I had that before once on 4.2.2 with a corrupted SU. I wipe my device and see how that works.

Those freqs were also there at stock 4.2, I removed them back then, but I didn't remove them now.
[Nexus 4 Original Android Development] linkinx64:
So 172 is not for JSS right?

found the answer

"r172 won't work on JSS compiled roms. I plan to release a compatible Kernel for JSS Android builds soon. For now it only works on JWR66V. Have fun"
[Nexus 4 Original Android Development] mountainloafers:
Hmmmm? Not so sure about that. Not trying to be ugly, but they do not look the same. Going to reflash system.
[Nexus 4 Original Android Development] Haomuch:
It's glad to see all the functions of Franco kernel have come back for 4.3. But the r172 really feels little laggy compared to the Android 4.3 stock kernel. Given that the stock kernel has been improved a lot in respond speed and battery life, the performance of the r172 seems really not that satisfying. Anyway this is the first fully working Franco kernel for 4.3 and thanks for your work. Let's see what could happen afterwards.
[Nexus 4 Original Android Development] mangomonkey00:
i flashed franco r172 and i'n not able to set colors fully i mean i'm not able to change all color setting

not with francokernel updater and not even with trickster mod
[Nexus 4 Original Android Development] ki2luminati:
I cant get volume boost and headset gain to Work. How about you guys?
[Nexus 4 Original Android Development] jmejiaa:
IIRC Google made the phone louder in 4.3. Not sure if this is affecting the kernel or maybe that's why you don't think it's working but I figure I'd mention it. :good:
[Nexus 4 Original Android Development] juggies:
Franco kernel is usually worse performance than stock, just better battery life.
[Nexus 4 Original Android Development] franciscofranco:
The colors are the same. If they look different to you then the changes they made on the composition layer affected the colors somehow, but the color/gamma values are 100% the same as they were on stock 4.2.

Where do you feel its lacking performance?

Turn the screen on/off.

Google made a lot of changes on the sound layer, maybe that is affecting it. I'll have to take a deeper look.
[Nexus 4 Original Android Development] slinder154:
Right, especially the gallery is suffering under lags...

But I hope that will get sorted out soon as I don't want to go back to stock colors.

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] franciscofranco:
Have you tried to increase the input touch freq? That might help you out. You're too used to stock with parks CPU to 1512MHz when you touch the screen, but well... that will **** your battery life and heat will go up in flames.
[Nexus 4 Original Android Development] Anytime1157:
I just realized that the high load threshold is now at 60, wasn't it 70 before this?

And the default io scheduler now is noop is it?
[Nexus 4 Original Android Development] franciscofranco:
Default IO scheduler should be row. And the threshold is now 60 yes.
[Nexus 4 Original Android Development] slinder154:
Input boost freq? Didn't help, also never had that problem under 4.2.2 before, without having anything modified.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Well, my device feels responsive and I have no lags, thats for sure.
[Nexus 4 Original Android Development] linkinx64:
What rom are you guys using that is JW? should I stick with JSS and wait for the updated kernel?
[Nexus 4 Original Android Development] slinder154:
Ja, absolutely. The only thing is the lagging gallery, it also remained after a full wipe.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] mangomonkey00:
i did that still no effect i even tried setting it on boot and than rebooting it worked for few time but then again back no changing
[Nexus 4 Original Android Development] thebryceee:
I put the minimum frequency at 1ghz for gallery.
[Nexus 4 Original Android Development] mountainloafers:
Could very well be true...
[Nexus 4 Original Android Development] franciscofranco:
Dunno, it works for me. If I can't reproduce it I can't fix it.
[Nexus 4 Original Android Development] slinder154:
Set everything to max now and that kind of made it better, only lags for some seconds.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] Flypwnz:
Stock is a beast for now and I will stay with it until Franco brings better performance/battery life or new features. I got better performance and battery life on stock compared to 172 undervolted Franco :)
[Nexus 4 Original Android Development] Redneck Trash:
Even after clearing app data and rebooting noop is displayed as default for me as well.
[Nexus 4 Original Android Development] llsantiago:
I have tried to wipe all and install the stock 4.3 + SuperSu 1.51 and still having problems with undervolt.
[Nexus 4 Original Android Development] Anytime1157:
Now that I've tried it myself, I have to agree. It's displaying noop for me too after clearing and rebooting
[Nexus 4 Original Android Development] hamad138:
franco is it possible for u to make gamma mode without screen on / off?

Thanks.
[Nexus 4 Original Android Development] nachordez:
I confirm. Default for r172 is noop.

Nexus4 / Stock 4.3 / Franco
[Nexus 4 Original Android Development] Redneck Trash:
I forgot to mention that's on app v10.1.2, the version before that and the beta between the two.
[Nexus 4 Original Android Development] Anytime1157:
Same set up then dude ;)
[Nexus 4 Original Android Development] Lynchz7:
Color controls are back. Thanks franco!
[Nexus 4 Original Android Development] Floydfire:
Just flashed 172 and app say that default si noop, also can you make in the app by default ticked the option of per app service disabled? I think is better for those who don't want perapp...

Wiped data in fku and says that noop is default...

And also input boost is 1100 by default previously was 1000 or I'm wrong? Only asking/reporting what I can see, BTW for me seems like stock and Franco 4.3 have worse battery life but I think is some app that doesn't is fully compatible for 4.3 I mean logcat show an error with lightflow.. Someone use it and can confirm? Sorry, I know is off topic only want to know if someone here have this problem :)
[Nexus 4 Original Android Development] nachordez:
Yes to noop (I think mistakenly by Franco) and 1100.

No to battery drain. Battery had improved for me. Probably app, as you said. It's really soon for apps in 4.3! ;)

Nexus4 / Stock 4.3 / Franco
[Nexus 4 Original Android Development] uly609:
I know this might be a dumb question to some of you but, what is the difference between the I/O Schedulers (Row, Deadline, CFQ, Noop)? What advantages does one have over the other? I did some searching on this forum and on google but can't really find a straight answer.
[Nexus 4 Original Android Development] drawde40599:
Your not going to get the values, read the changelog and ull c y.
[Nexus 4 Original Android Development] llsantiago:
I'm not Franco but he said will try to correct this issue in a future release!
[Nexus 4 Original Android Development] Floydfire:
Yeah I don't know how to see what app is causing this trouble because with wakelock app sometime the major app that wake CPU is Facebook, sometime is Google+ (I let my phone use all the thing like GPS and other feature like gnow) but is similar than 4.2.2 maybe after update app will be better... I'm too lazy to try without my app for see if battery is better... BTW with stock I had play for 1h with riptide gp2 and it wasn't so bad only I had better battery but I'm now on default setting Franco and not like before with my CPU at 1000 MHz and per-app using... So maybe is also that. BTW only for knowing with stock kernel 4h on battery with ~3+hours (gaming with various game like riptide gp2, worms, pvz) is a good life or not? Because it's was like that... What is the time in gaming on battery with default setting on Franco? I'm really curious to see if is really ****ty my battery life or not to worry about...

Lol I have now see that maybe I use it like... Too much xD 4h 20min on battery with screen on 3h 20m xD and I'm with 36% of battery don't know if this is better than before with all stock setting in Franco, I don't remember but hey seems not bad to me..
[Nexus 4 Original Android Development] slinder154:
Funny story. A restart totally did the job. Should have known as a software developer...

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] mashedbymachines:
Yes same here. Something is wrong with undervolt. Also, please bring back so I can manually type the voltage value, It makes it so much easier. Also I use more fine tuned values than 25mv increments :)
[Nexus 4 Original Android Development] hamma:
http://xdaforums.com/showthread.php?t=1369817
[Nexus 4 Original Android Development] :
That's actually the problem I was asking for stock 4.3 ROM colors not the colors you've been using since r14, or alternatively a color profile that would allow me to use stock ROM colors, they were slightly tweaked by Google and I like them
[Nexus 4 Original Android Development] eng.stk:
acpuclock-8064.c and acpuclock-krait.c are very diferent from JB 4.2.2, at first sight it seems that JB 4.3 lacks some of the functions for bin calc, this function has a bin type that does'n exist (FASTEST), really weird...

static int __init get_pvs_bin(u32 pte_efuse)
{
uint32_t pvs_bin;

pvs_bin = (pte_efuse >> 10) & 0x7;
if (pvs_bin == 0x7)
pvs_bin = (pte_efuse >> 13) & 0x7;

if (pvs_bin == 0x7) {
pvs_bin = 0;
dev_warn(drv.dev, "ACPU PVS: Defaulting to %d\n", pvs_bin);
} else {
if (pvs_bin == 1)
cpu_type = "SLOW";
else if (pvs_bin == 2)
cpu_type = "NOMINAL";
else if (pvs_bin == 3)
cpu_type = "FAST";
else if (pvs_bin == 4)
cpu_type = "FASTEST";

dev_info(drv.dev, "ACPU PVS: %s\n", cpu_type);

}

return pvs_bin;
}

Does'nt seem a su bug, i tried other kernel like faux for instance, with UV/OC and it sticks fine.

Hope you can crack it [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 4 Original Android Development] franciscofranco:
I'll say again, stock 4.3 has the same colors as 4.2 stock, same values.

I don't know what it is to be honest, I just tried on [MENTION=4446775]cgollner[/MENTION] N4 and it worked :) I'll take another look later today.
[Nexus 4 Original Android Development] m3nster:
4.3 on 172

I'am getting graphical glitches when swiping across screens with 172 on 4.3 cm 10.2 unofficial. All is good with the stock kernel.
[Nexus 4 Original Android Development] BrandoHD:
The official build is for OTA or JWR based ROMs

Cm 10.2 may be JSS based which is slightly newer and flashing kernels based on one to the other is going to produce those glitches

I hope you understand what I just typed

Sent from my Nexus 7
[Nexus 4 Original Android Development] nexusvolt:
That's because that build isn't compatible with 172, I think cm 10.2 is android build jss something..

Skickat från min Nexus 4 med Tapatalk 4 Beta
[Nexus 4 Original Android Development] m3nster:
I'll just revert to CM10.1 with Franco!

sent with my Nexus4
[Nexus 4 Original Android Development] limeaide:
Those of you complaining about the undervolt ability being broken. Chill out for a week or so. If I am not mistaken some of that code has changed just enough Francisco needs time to work out the bugs. Plus if all you are doing is complaining without logs to help him you are being ignored its that simple.

Those of you that are complaining about having to turn the screen on and off so gamma setting take..STOP. Francisco has stated it is a work around he implemented for people (like myself) that have a kernel freakout and reboot if the screen is turned off while they are being applied. This is not a big deal. So please just chill out until he figures this out like he has said he wants too.

For things Ive not covered people please give the man some time. He is only one person and has multiple nexus devices to develop for. Its not just copy paste on it all the older phones have variations in hardware and the Nexus tablets are slightly different too.

Francisco I read up on that volume mod I posted about. What it appears it does is stop the phone from asking about safe volume setting. I guess the Nexus devices do not have that option in sound or settings. However I reverted the mod last night to see if there was a difference. I can say I do notice your volume module changing the volume levels with the mod enabled but not with it off. It seems to me that instead of the 20 steps its more like 3-4 steps. If a couple other people can test this and post their results Im sure it can be of some help right?
[Nexus 4 Original Android Development] thebryceee:
Just had a SOD on 172. Had one also on 171, no clue what it's from. Phone was left on home screen both times.
[Nexus 4 Original Android Development] shakatu:
I love this kernel and use it all the time. I tried to be ballsy and use the 172 kernel and it wasn't compatible with my ROM. Well that's okay, except I rebooted to recovery to flash back and the touch didn't work in TWRP anymore. So I flashed the original kernel in fastboot, still no touch in TWRP. I had to flash TWRP in fastboot as well to get it back. Don't think this should have been an issue... I'm running the latest boot loader and TWRP so it shouldn't have happened AFAIK.
[Nexus 4 Original Android Development] franciscofranco:
Thank you.

Are you using chromecast with Netflix app?
[Nexus 4 Original Android Development] rmead01:
Even without chromecast, netflix causes this. Happens every time I watch something on netflix and is not a kernel issue.
[Nexus 4 Original Android Development] thebryceee:
No sir. It was idle for several hours during my nap, probably 3.5 hours. Lol 3.5 hour nap
[Nexus 4 Original Android Development] franciscofranco:
Dunno then, need logs.
[Nexus 4 Original Android Development] zephiK:
Did you undervolt?
[Nexus 4 Original Android Development] thebryceee:
Oh yeah, BTW I checked back earlier and all the voltages reverted back to stock except 384. I think 384 is still undervolted, my derp. I forgot undervolting can vary between builds.
[Nexus 4 Original Android Development] simarilon:
Deleted
[Nexus 4 Original Android Development] AndroidKills:
I love this kernel and the app along with it is wonderful, but is there something wrong with what I'm doing, when my phone reboots the frequencies are all reset (i do have the option checked where they're set on boot) along with the custom kernel settings ( like headphone/volume boost). It's a small thing nothing too serious but I'm just curious.

version r165, PA3.69
[Nexus 4 Original Android Development] zephiK:
Hehe just play around with it and +25 and see if it SODs. My phone is fast (the grep PVS thingie that was posted way back for cpu stype) and runs solid on 750 v but yeah it varies between phones.
[Nexus 4 Original Android Development] nixie2121:
so pa rom is releasing 4.3 rom based on JSS... does this mean no more franco kernel for me right now? just wanted to be sure I don't flash something I should not! thanks
[Nexus 4 Original Android Development] BrandoHD:
That didn't answer the question though, with the Netflix bug, once you open the app (you don't even have to watch a movie), it's going to happen, whether it be 10 minutes or 10 hours later, the only way to not have it happen is to not open the app at all after reboot.

So you used that app at all, that is e reason for the issue, and Chromecast has nothing to do with it, I know because I haven't received mine as yet :(

Sent from my Nexus 7
[Nexus 4 Original Android Development] leets4uc3:
No you cannot use Franco kernel on jss. Please read at least one or two pages back before posting or do a search. :)
[Nexus 4 Original Android Development] markd0wn:
Can't use it right now, compatible version will be released soon.

And reading even further than one or two pages leads to finding out that a JSS version is coming :)
[Nexus 4 Original Android Development] franciscofranco:
Just fixed the UV interface. I'll push r173 asap.
[Nexus 4 Original Android Development] thebryceee:
I have Netflix greenified so it wasn't even active in RAM at the time when it happened.

It probably happened because 384 was -100 uv
[Nexus 4 Original Android Development] BrandoHD:
Read the thread in the General Section, it doesn't have to be active, basically, once you use it, forget it (for those affected), SOD, I suspect that a lot of people may come here thinking it's a kernel issue, so we have to mindful of those type of SOD reports.

I'm on Tapatalk, too lazy to link the actual thread

Sent from my Nexus 4
[Nexus 4 Original Android Development] thebryceee:
Weird.
[Nexus 4 Original Android Development] ciprianruse88:
Awesome !!!!!! Please consider JSS version too :)

Sent from Inferno
[Nexus 4 Original Android Development] zephiK:
He is, just be patient and stop asking before he changes his mind :p
[Nexus 4 Original Android Development] cobyman7035:
R173 has gamma control and its 4.3?

I also miss fast USB ac charging

Via my 4.3 Mako NeXus⁴ using XDA Premium
[Nexus 4 Original Android Development] bokagavrilov:
Yes even 172 has gamma BUT it's for jwr for now
[Nexus 4 Original Android Development] Raijin:
Can you tell us the stock values to use them with your kernel? Thank you.
[Nexus 4 Original Android Development] jak3z:
And this is why we all love franco.Kernel :cowboy:
[Nexus 4 Original Android Development] cobyman7035:
My build is leaked mako ROM JWR66V. can I still flash r173?

Via my 4.3 Mako NeXus⁴ using XDA Premium
[Nexus 4 Original Android Development] franciscofranco:
r173:

* Fix UV interface

* While using interactive if the cpu load is above or equal to 50% the CPU gets boosted to hispeed_freq (default 1GHz)
[Nexus 4 Original Android Development] N_lover27:
YEs u can
[Nexus 4 Original Android Development] franciscofranco:
Not yet, I need to do some changes and I've been short on time...
[Nexus 4 Original Android Development] markd0wn:
We'll be patient. At least you'll get to play with the newer commits (even if you won't end up using that kernel yourself), looked like you were excited about that before the tearing mess was discovered.
[Nexus 4 Original Android Development] anazhd:
Still waiting for JSS kernel. Even Franco is short on time, JRW development is still quite fast.
[Nexus 4 Original Android Development] franciscofranco:
Guys don't take this the wrong way, but saying "still waiting for JSS build" or something along those lines won't do any good. I'll get to it when I have more time and when I feel like its time to do it. I also need to **** my device and flash a JSS rom to test a JSS Kernel. All of that takes time and testing. I also need to make my ramdisk compatible with CM, and that also takes a bit of time because they do a lot of ramdisk changes. Just be patient please.
[Nexus 4 Original Android Development] JNewms:
Think of it like this guys. It'll be like going awhile without seeing your favorite girl/guy or whatever you're into. It sucks waiting, but it's that much sweeter when you're reunited!
[Nexus 4 Original Android Development] benrees21:
Sorry Franco but your slacking mate! Hahaha. I'm just teasing! People give the man some breathing space and be patient! I know you are all wanna tear it up with the custom ROM's and kernels as do I but just gotta hold out for a bit longer, the devs here are working extremely hard. OK I'm done.
[Nexus 4 Original Android Development] ben_pyett:
Take your time, I'm personally still waiting for a rock solid AOKP JSS build to land before needing a Franco JSS kernel, I appreciate that with every improvement, code change and additional piece of previous functionality that you currently implement in 4.3 will just ensure that our first true ASOP release will be more complete and polished.

Thanks stock users for testing and helping in creating the finished ASOP JSS kernel.
[Nexus 4 Original Android Development] bokagavrilov:
Franco there seems to be a problem with the 4th core I just tried my 4.2 settings (thanks to you) with the 4 cores always on underclocked the first 3 are Okey but the 4th keeps going over the value that has been set (700)in this case I have used system monitor for monitoring with the flying windows

Edit: cleared apps data and did everything from start it's fine now sorry for the wrong report :thumbup::thumbup:
[Nexus 4 Original Android Development] JNewms:
That Stifler.. He's got some timing. LOL
[Nexus 4 Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION] I'm setting the frequency at 325mhz gpu, but is returning to 400mhz.

JB 4.3 - r172
[Nexus 4 Original Android Development] fozzie:
Hey Franco. Am I right in thinking that the thermal led trigger is missing at the moment?

Thanks.
[Nexus 4 Original Android Development] jak3z:
Confirming r173 fixed the UV not sticking :) :good:
[Nexus 4 Original Android Development] steviewevie:
Apologies if I'm misunderstanding, but I wonder if this discussion is going on at cross-purposes. I summer that Franco kernels for 4.3 have the same colours by default as 4.2 Franco kernels, but that's not the same as stock 4.3 kernel or stock 4.2, is it?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Redneck Trash:
I can as well. Can also confirm they apply after reboot. ROW now shows as default I/O scheduler.
[Nexus 4 Original Android Development] Manbot27:
I was wondering the same, I'm pretty sure stock android 4.3 has different colors than stock 4.2.2. I don't know if Franco would be able to tell you the values for stock aosp 4.3 colors as I've mostly seen other users give those values.
[Nexus 4 Original Android Development] Karlo666:
Hey great work even you where on vacation!

BTW i noticed bug in app or in kernel dunno wich one but i chosen recommend color profile(obsanity) the profile was not active but it has applyed after i turned screen back on.