yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ftarules:
Can anyone recommend optimum settings for Franco Kernel updater app for Governer settings? I am usig Xylon with Franco 23. Also I don't see any option to Undervolt. Is that way its supposed to be? Lastly is there any Gamma correction available with this kernel with franco app? Sorry I am noob to this kernel.

See screen shot
[Nexus 4 Original Android Development] enviii:
Not that I'm complaining or anything, but my battery life has not improved or gone down since flashing r23. I flashed it this morning for the first time over stock.

Anything specific I should be doing in terms of settings to see a noticeable improvement?
[Nexus 4 Original Android Development] KyraOfFire:
I don't think Franco will implement UV for the N4. He said that a few pages back. Also, there is no Gamma correction option (yet).
[Nexus 4 Original Android Development] scream4cheese:
I tired already. It still doesn't change for some reason.

---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------

He will implement UV possibly in the near future. As of right now, he wants to release stable versions right now before messing with UV-ing.
[Nexus 4 Original Android Development] woeds:
That's off already
[Nexus 4 Original Android Development] PhantomGamers:
https://sundergaming.com/FastDL/franco.Kernel-nightly-r165.zip

mirrors:

https://docs.google.com/file/d/0BysS6RQJ1TyuWi1ia2FIUDFnVHc/edit?usp=sharing

http://www.sendspace.com/file/g3sj9f

https://mega.co.nz/#!wQoyACwZ!MmKWOkFqbgNHB5SVLZOvIFtrKzo49tHabR9icgh3S7Q
[Nexus 4 Original Android Development] :
Thank you very much, my friend!
[Nexus 4 Original Android Development] PhantomGamers:
Does anyone know how to deal with these?

WARNING: vmlinux.o(.text+0xab90): Section mismatch in reference from the function mako_hotplug_late_resume() to the function .cpuinit.text:cpu_up()

The function mako_hotplug_late_resume() references

the function __cpuinit cpu_up().

This is often because mako_hotplug_late_resume lacks a __cpuinit

annotation or the annotation of cpu_up is wrong.

WARNING: vmlinux.o(.text+0xada4): Section mismatch in reference from the function decide_hotplug_func() to the function .cpuinit.text:cpu_up()

The function decide_hotplug_func() references

the function __cpuinit cpu_up().

This is often because decide_hotplug_func lacks a __cpuinit

annotation or the annotation of cpu_up is wrong.

WARNING: vmlinux.o(.text+0xaf10): Section mismatch in reference from the function decide_hotplug_func() to the function .cpuinit.text:cpu_up()

The function decide_hotplug_func() references

the function __cpuinit cpu_up().

This is often because decide_hotplug_func lacks a __cpuinit

annotation or the annotation of cpu_up is wrong.

I've tried removing __cpuinit from cpu_up() which didn't seem to fix it and then I tried adding it to the functions that were mismatching but it doesn't seem to want to work no matter what I do... additionally CONFIG_NO_ERROR_ON_MISMATCH=y doesn't seem to do anything.

I'm not the most knowledgeable when it comes to kernels but if anyone can assist me that'd be great. :)

edit: it seems to build standalone this is just a problem with building it inline with cm, however as far as I can tell CM is using the stock google android 4.6 toolchain as well... hm...

edit2: i pulled in google's toolchain by hand and it's still erroring... if anyone has any ideas at all I'd really appreciate it
[Nexus 4 Original Android Development] maddyreddy:
Hey could you please upload r165 M3 or put a alternate link..thanks
[Nexus 4 Original Android Development] PhantomGamers:
r165 and M3 are two different builds
[Nexus 4 Original Android Development] maddyreddy:
I'm sorry M3
[Nexus 4 Original Android Development] monkey hung:
Download r165 and now my phone won't boot. It gets stuck at the Google logo forever.
[Nexus 4 Original Android Development] PhantomGamers:
if you downloaded it from the app try booting into recovery and flashing the zip from one of the mirrors above
[Nexus 4 Original Android Development] Floydfire:
The new fixed kernel will be 166 or replace 165?
[Nexus 4 Original Android Development] andyli1985:
Here you go. A mirror to M3

http://db.tt/bphtpRN3
[Nexus 4 Original Android Development] djpry:
updated to the latest one.....running fine and smooth...
[Nexus 4 Original Android Development] limeaide:
If he cant boot to android how is he going to flash a zip? I know how I would but doesnt mean this person does. Personally I would download the kernel image and fastboot flash it.
[Nexus 4 Original Android Development] OneDream:
Same damn thing happened to me. I was still able to get into recovery. Luckily, I had a nandroid backup.
[Nexus 4 Original Android Development] funkyblue04:
How do I fix my colours? Seems to be default even with Franco. I've tried resetting Franco but still washed out. How do I fix this issue?
[Nexus 4 Original Android Development] Taxiback:
Same here, stuck at the Google logo. Thought I had a nandroid backup but it seems to have vanished! I did a factory reset from within TWRP but still stuck at the Google logo.

What next? Will I have to try and install stock from the Nexus toolkit?
[Nexus 4 Original Android Development] gajira:
Flash the M3, if it doesn't work flash your ROM again and boot.

Just a question, it's normal that the kernel uses only two CPUs? I have the other two all the time offline, no matter what I'm doing.
[Nexus 4 Original Android Development] kecinzer:
[MENTION=3292224]franciscofranco[/MENTION]

Can you please paste here diff from 163 to 165? Thanks.

Also do you plan use translation from crowdin to fKu? In few latest releases still isn't latest czech translation.

Thanks.
[Nexus 4 Original Android Development] Redneck Trash:
It's normal to run on two cores. If you lower the high load threshold the other cores will come on more often.
[Nexus 4 Original Android Development] JeffyLube0:
I just started having problems getting certain settings to stick after reboot (GPU frequency and some governer settings) as previously reported. Anyone figure out how to get these settings to stick?

I've tried clearing app data followed by reboot and uninstalling app followed by reboot and reinstalling.
[Nexus 4 Original Android Development] keyra74:
no problem at all with r165 here, listened some songs, played a bit ect...
[Nexus 4 Original Android Development] Taxiback:
Used the Nexus 4 toolkit and up and running, all stock.

Not sure whether to bother with franco kernel until he sorts out these teething troubles. Last week the app would download the kernel but not flash it, I downloaded it 6 times before it worked. Now I get a soft brick when updating the kernel. Never had any of this trouble with franco in the past!

Oh, not quite all right, getting a lot of random reboots now. :(
[Nexus 4 Original Android Development] kerngehirn:
Is it possible that underclocking may result in a hotter device? I had to delete my app data recently and didn't set my values for a few hours. I had the feeling the device was cooler without underclocking.
[Nexus 4 Original Android Development] Luigiesin:
It shouldn't... Quite opposite.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.69

Kernel: Franco r163-Linaro

T-Mobile
[Nexus 4 Original Android Development] monkey hung:
Yeah r165 is totally messed up for me and by the looks of it, quite a few people. Downloading the zip and installing it through recovery gives me an error. Auto flashing r165 just soft bricks my phone
[Nexus 4 Original Android Development] jmartino5920:
So I was getting hot reboots (reboots to boot animation instead of Google splash first) trying to flash r165 from FKU. So I cleared data in the app, rebooted to recovery and wiped cache, dalvik cache and fixed permissions. Auto-flashed r165 with no problems.

Been running smooth since.

Was running smooth on r163 beforehand.

Gonna do a full wipe in a minute, after nandroid, to AOKP Milestone 2 with Franco r165 and LTE Mod. I'll report back in the morning.

Thank you Franco!

jmar

Sent from my LTE Mako
[Nexus 4 Original Android Development] Pure Drive GT:
stop crying around guys i flashed with fastboot and all was fine, there seems to be a problem with the direct app download, chillout and give franco a break we all know he'll fix it.

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] Taxiback:
Be nice if he tested it first though, the new style app has been nothing but a pain in the arse since coming out of Beta mode, at least the old app worked. :confused:
[Nexus 4 Original Android Development] Redneck Trash:
He does.
[Nexus 4 Original Android Development] mor_1228:
no problem with the new app v10.1.1 and r165 both are working without any problem i am using and i flashed with both methods auto flash and zip via recovery and i didnt get any softbrick bootloop or anything else. so the problem must be related to particular rom or devices.
[Nexus 4 Original Android Development] Taxiback:
Maybe so, but seeing as I'm running stock (and always have) I would have thought it would run smoothly. I thought the new version was 10.1.1.2
[Nexus 4 Original Android Development] Floydfire:
I think is a beta fault, I'm on beta and does the bug... Or a server problem because here in Italy I can't reach anymore.. I'm speaking of Francisco.minooch the minooch one work...
[Nexus 4 Original Android Development] Redneck Trash:
Could be. I'm not on beta and everything has been fine. It would be helpful if someone could grab a log.
[Nexus 4 Original Android Development] Taxiback:
I think franco has taken r165 down now as the app can't see it any more. I was not running any Beta version, I leave that to the guys that know more than me. :) I had the soft brick updating from v10.1.1.2

Wow, you forget how fast the stock kernel is until you have an incident like this. :)
[Nexus 4 Original Android Development] Floydfire:
I mean the v10.1.1.2 I don't know was stable.. BTW if you try to go on second server which starts with franciscofranco.minooch.com you can't reach, at least I can't reach and I think the app use it for download.. So if you want to download try the minooch.com server :)
[Nexus 4 Original Android Development] KiD3991:
Not sure if Placebo, but coming from r164, no more reboots and better battery.
[Nexus 4 Original Android Development] Taxiback:
It's very quiet in here, has everyone soft bricked their phones doing the latest update? ;)

---------- Post added at 11:18 AM ---------- Previous post was at 11:15 AM ----------

Reboots! until this soft brick updating to r165 I'd never had a reboot. Are you running one of those iffy custom roms?
[Nexus 4 Original Android Development] Lownita:
I think the problem is the server. Sometimes it takes very long until fku gets a connection and shows the current kernel versions. Might even be a routing problem if it only exists for some people.

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] Taxiback:
Got it to show r165 now, I'm too scared to flash it though, think I will wait for r166, I've done a nandroid in preparation. :)
[Nexus 4 Original Android Development] KiD3991:
Well, given I personally never liked Paranoid roms, I sticked to Cm10,1,2(waiting for CM10.2?)

So yeah. I modified some of the values using Trickster, underclocked to 1.0ghz.

Edit: The battery life is purely amazing. PURELY.
[Nexus 4 Original Android Development] Taxiback:
I couldn't live with a phone that kept rebooting itself. I'd rather have a stable phone and have to charge it every other day instead of whatever you're getting.
[Nexus 4 Original Android Development] mor_1228:
i guess u have network problem because its working fine here :
[Nexus 4 Original Android Development] hegemytouch:
Are you using r165?
[Nexus 4 Original Android Development] KiD3991:
Hmmm, that happened at 164, at 165 for a few hours, nothing yet. In 164, it happens.

Yeah, and I'm giving it a positive one.
[Nexus 4 Original Android Development] combatdeity:
A friend of mine and I both got stuck at the google logo on flashing r165. We were both on the same net, so that could be a common factor causing it.

Does the app check MD5 before flashing?
[Nexus 4 Original Android Development] Taxiback:
There's definitely something not right with r165. Only minutes before I flashed r164 and all went well so it can't be the app.

Does the app flash the download without checking it? I wouldn't like to say, but looking at the amount of people getting stuck on the Google screen I would guess it doesn't. I used to like the old version where you could see the progress of the download, now you just hit Auto update and hope for the best.
[Nexus 4 Original Android Development] manulemaboul:
If it can help, I had it stucked at the Google logo once after auto-flashing, but it was weeks ago.

So my guess would be that it's more of an auto-flash issue than a kernel issue.

Has anyone had a bootloop after flashing the zip version manually?

Worked OK for me, for both 164 and 165.

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Original Android Development] hegemytouch:
Just flashed the zip in recovery mode... No issues at all... no boot loop... as far as random reboots I'll let you guys know once I use my phone more.
[Nexus 4 Original Android Development] Taxiback:
Don't know if it's normal behaviour or not but when you get stuck at the Google screen you can't even turn the phone off completely. If you hold the power button it goes off, but then turns itself back on again. Knowing it will do this you only need to hold down the volume and it will boot into fast boot mode.

Is that a boot loop?
[Nexus 4 Original Android Development] ShinnAsuka:
I think the auto flash feature on the latest FKU is hit or miss. Before when you hit auto flash it would download and show a prompt asking you to reboot to set the changes to the kernel. Now it just hangs so your best bet is just using the download zip function and flash it manually in recovery mode.

---------- Post added at 08:38 AM ---------- Previous post was at 08:33 AM ----------

If it can't get past the Google logo then yes it is a boot loop of sorts. Traditionally a boot loop is a case where your device boots pass the boot loader but then reboots to the boot loader infinitely.
[Nexus 4 Original Android Development] Taxiback:
Blimey, looks like your XDA app is in a boot loop. :)
[Nexus 4 Original Android Development] ShinnAsuka:
Haha clever lol.... yeah it kept hanging on "receiving from server" so I kept on backing out and resubmitting lol... I'll try and delete the duplicates lol...
[Nexus 4 Original Android Development] Anytime1157:
I auto flashed r165 using FKU v10.1.1.2 without any problems. No reboot whatsoever so far. I'm on carbon rom if that matters :)
[Nexus 4 Original Android Development] lorolouis:
Take a break guys ... 5 days or so.

Allow some rest for Franco and yourself.

We all can leave one week with older release and no asking to help on obvious things, cant we :) ?

Everything will be fine then.

As long as he is not changing N4 to another phone, newer and better FK releases will show up.

Regards
[Nexus 4 Original Android Development] nachordez:
r165 performing nicely here.

I'm pretty convinced that bad download is what is giving problems to some people.

Nexus4 / Carbon / Franco / V4A
[Nexus 4 Original Android Development] manulemaboul:
Battery life is impressive on 165, 1h52 SOT and only lost 30%.

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Original Android Development] ShinnAsuka:
Play with voltages and underclock for even better battery life :)
[Nexus 4 Original Android Development] ayrtonforever:
witch cpu governor and I/O scheduler do you use?

TapaSwypato dal mio Nexus 4
[Nexus 4 Original Android Development] Fobz:
All the people having bootloops, just keep a copy of the reset kernel on the internal sd card then just flash that in recovery if it happens. No need to nandroid or wipe and clean flash.

Hope it can help some people.

Sent from my Nexus 4
[Nexus 4 Original Android Development] manulemaboul:
Interactive, row, - 100mV, gpu maxed at 200 and cpu at 1188 for my default profile.

Unleashing the full power for tapatalk only, haven't played yet today.

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Original Android Development] beckham_totti:
flashed through cwm.. it works perfectly.. thanks francis :good::good: much more stable compared to the m2 as well :silly::silly:
[Nexus 4 Original Android Development] The Gingerbread Man:
https://plus.google.com/106873500108976028532/posts/hfj5gqdA5aY
[Nexus 4 Original Android Development] KiD3991:
Well, he said its just for normal usage so we have nothing to worry.
[Nexus 4 Original Android Development] Cuzz1369:
It is a server or an app problem. I tried everything I could to get r165 last night. Nothing would work. Then a nice gentlemen posted a mirror and it flashed perfectly.

Carbonized and francofied N4
[Nexus 4 Original Android Development] occtec:
Flashed r165 using twrp 2.6.0.0 perfect!! Thank you Franco ;):beer:

Sent from the wizard of OZ
[Nexus 4 Original Android Development] Mo'HAWK:
So I've been using 4.3 for a bit and it seems that they have taken a lot from Francos kernel. Only missing his name on it.
[Nexus 4 Original Android Development] PhantomGamers:
you don't need to boot to android to boot to recovery...

Also, bump:
[Nexus 4 Original Android Development] jimbohurt:
Downloaded r165 myself then flashed on recovery. Works flawlessly.

I know for a fact that its an app/server error because I got in a boot loop when I auto flashed r163 like 2 weeks ago. Its cause it was a bad download and so it flashed like a half file. I'm guessing there is no check to make sure its good before flashing.
[Nexus 4 Original Android Development] Redneck Trash:
Has anyone having the auto update problem tried after the fKu update?
[Nexus 4 Original Android Development] Taxiback:
It's all well and good saying that now, but not a lot of help if your already in a bootloop. I had a nandroid backup but for some strange reason that had vanished too.
[Nexus 4 Original Android Development] BIFFTAZ:
Yes, With the premium app I tried to auto install 165 3 times but it failed. Installed fine the 4th time.
[Nexus 4 Original Android Development] Lynchz7:
I was trying to use the auto flash function using fku app, and without any prompts after it finished the download, the phone restarted itself, and got stuck at the Google logo. Had to reflash 4.2.2 stock android to get it to work again. But i tried fku another time and it seems ok. Thought i had to do a clean flash and re-setup everything. And no, i didnt do a nandroid backup, i live my life dangerously. :cool:
[Nexus 4 Original Android Development] Taxiback:
I see FKU has just updated to 10.1.1.3 maybe it was the app causing the bootloops.
[Nexus 4 Original Android Development] :
I always keep a Milestone zip in my download folder, helps always thinking ahead, just in case **** happens when using auto flash or to roll back and compare performance
[Nexus 4 Original Android Development] Fobz:
If your in a bootloop just enter recovery by pressing vol down and power. People are saying they have been restoring nandroids or wiping and reflashing their setups, so I guess entering recovery isn't the problem. I just figured it would easier and faster to flash a restore zip instead of the other choices.

From what you're saying though your internal storage got wiped from the flash?

Sent from my Nexus 4
[Nexus 4 Original Android Development] steviewevie:
Come on man, your logic is faulty. Just because it was fine for you doesn't mean that there isn't a problem somewhere. I suspect the problem is the auto-flash feature combined with high server loads - i.e. sometimes it gets borked.

I'm sure Franco will sort it out when he comes back from vacation. Trying to say there's no problem is just going to inflame things though, let's all get along nicely :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Redneck Trash:
According to the changelog v10.1.1.3 should fix the problem.
[Nexus 4 Original Android Development] Luigi_2:
r165 stock settings, 19k plus antutu points, not bad.
[Nexus 4 Original Android Development] limeaide:
Quoting this because it is relevant.

Also if you feel Francisco is not testing his stuff enough then uninstall his kernel and app.

I am not a fanboy, I just get irritated when people make wild accusations. Francisco would not be so popular if he did not have some sort of quality control. Plus the man is on vacation. He did NOT have to release that kernel he could have been a richard cranium and posted about how well it was working for him and told us to wait until he was back to get it.
[Nexus 4 Original Android Development] Doo Doo:
i updated FKU to 10.1.1.3 and the app still says fetching when trying to see the latest stable & latest nightly versions

in the changelog it said this was 1 of the things fixed but it ain't i guess

for people that are using r165 is the max cpu freq. hitting 1.5 like its suppose to?
[Nexus 4 Original Android Development] mitchdickson:
Clear app data?

Sent from my iPad 4
[Nexus 4 Original Android Development] Doo Doo:
i already did that
[Nexus 4 Original Android Development] zelendel:
Ok looks like I need to make it clear to some people where they are. This is a development forum, everything here is always a use at your own risk. IF you flash something you fully accept that it may not boot, may bootloop you or even brick your device. This is the chance you take when you mess with the OS of your device. Everything here is under active development which means things can go wrong. You flash things from this site and accept that you may brick yourself so there is no complaining, whining, or throwing of fits.
[Nexus 4 Original Android Development] Cuzz1369:
While I completely agree with everything you said. I feel it was completely unnecessary. There isn't any of that going on. People are just constructively trying to figure out the problem and helping each other try and fix it. I don't really see much complaining or blaming Franco for anything.

Carbonized and francofied N4
[Nexus 4 Original Android Development] ben_pyett:
We must also remember that these issues appear to have come from flashing the latest nightly....not stable release, the clue is there in the name.

Always take a nandroid if there is a single possibility that something could go wrong....which is always
[Nexus 4 Original Android Development] drawde40599:
WE! Tested for weeks BEFORE released there wasn't an issue i remember reading. U follow this thread u should no this ;)
[Nexus 4 Original Android Development] Lownita:
Little OT since there are some beach buggy blitz addicts in here: Riptide GP 2 just hit the playstore :D

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] uzii305:
Can somebody upload the most battery friendly settings so that I can apply them? Please.
[Nexus 4 Original Android Development] mitchdickson:
Max frequency: 384.

Sent from my iPad 4
[Nexus 4 Original Android Development] drawde40599:
I think there is still an issue there, something to do with throttling, fixed in 166 when come out. Franco posted bout it if u look threw his posts, sorry can't link u atm
[Nexus 4 Original Android Development] Bill Gamble:
A reboot fixed it for me.
[Nexus 4 Original Android Development] Doo Doo:
i seen Franco's post about it thanks but i was just asking because since he updated the app i thought that he just fixed r165 also without having to release r166
[Nexus 4 Original Android Development] trek85002010:
Can i put this new kernel in Nexus 4 with the leak 4.3??

Enviado desde mi Nexus 4 usando Tapatalk 4 Beta
[Nexus 4 Original Android Development] drawde40599:
No

---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------

Oh, i didn't even think of that maybe your right, im using my S4 today so cant check
[Nexus 4 Original Android Development] Doo Doo:
no the new 4.3 leak has a new kernel source
[Nexus 4 Original Android Development] trek85002010:
Ok, thanks a lot

Enviado desde mi Nexus 4 usando Tapatalk 4 Beta