yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] clshack:
I have flashed it. Works very fine !!
[Nexus 4 Original Android Development] Arstoien:
Not here. It's fine for me.

PS: my bad. I was on ondemand. There's some weird frequency locks on some cores when using the system power modes and changing the governor.

Sent from my Nexus 4
[Nexus 4 Original Android Development] blueren:
Never had these stutters of 180 on demand.

Sent from a Nexus
[Nexus 4 Original Android Development] snorfu:
After flashing r181 my signal bars won't turn blue -.- my 3g is working and i also did a manually sync but nothing changed...any suggestions?
[Nexus 4 Original Android Development] handols:
This is the fastest kernel I had with franco. R181 is the best so far!

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
r181 is pretty good.. My phone's power button has been fixed at LG Center, bye bye battery drain.. We'll see how the battery holds up with r181.

Nexus 4|PA 3.99|Franco Kernel
[Nexus 4 Original Android Development] nileshgr:
Franco, can you enable mpdecision (not QCom one, the one which is tweak able) in next release?
[Nexus 4 Original Android Development] :
Nexus 4|PA 3.99|Franco Kernel
[Nexus 4 Original Android Development] nileshgr:
I've been using TC since the day I found about it because my N4 was imported and doesn't have warranty in my country (though it was officially launched by LG 3-4 months later after my purchase). I just fear the power button going kaput, so I always use TC :D
[Nexus 4 Original Android Development] franciscofranco:
How can I reproduce that exactly?

No, why would I use other hotplug drivers if I've built my own?
[Nexus 4 Original Android Development] Arstoien:
I've gotta test what exactly triggers the freq locks and I'll do when I've got more time tonight. But I've seen that disabling the per-app settings service fixes it. More details tonight when I test it.

For now I can tell you for a FC of the app: Clear the app data and restart. Wait for the cpu to finish with the startup load and open the app. Go to Per App Power Modes, the second tab (Default System Mode). Change the governor from ondemand to interactive, tap SAVE, and wait a few seconds. Then change it to ondemand, click save and after a few seconds (if not instantly), it'll force close. Then every time I open the app, after a few seconds it FC-es. I sent a report through the MC menu a couple of mins ago.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Chochiwpg:
It's been a while since I have used a custom kernel on my N4. I want to give Franco a go but have a few questions. Can anyone tell me the default settings of the kernel out of the box? Meaning frequencies, voltages, vibration strength, governor, GPU, colours etc.

Just want to get a general idea before I make a final decision to flash or stick with factory kernel. Thanks guys.
[Nexus 4 Original Android Development] Arstoien:
If I were you I would install his app, backup the current kernel, then flash the latest nightly from within the app and see everything. If you decide you want to revert, just restore the backed up kernel.

You can also backup the current kernel with Flashify by Christian Gollner.

Sent from my Nexus 4
[Nexus 4 Original Android Development] kissa121277:
hello everybody .....

can someone post the link for r181 for JWR nexus 4 kernel ????`

THANKS A LOT
[Nexus 4 Original Android Development] DesertVelo:
Here you go....

http://xdaforums.com/showthread.php?p=45147202

Sent from the singletrack...
[Nexus 4 Original Android Development] nileshgr:
I was playing with settings to see how performance governor affects battery life. I set hotplugging all cores to 75% and suspend_max_freq = 1512.

I saw absolutely NO difference in battery life (theroetically, it should increase more, at least if it was a Intel CPU).

So instead of hotpluggin all of them together, it would be useful if it can be done in 25% phases.

Load Cores

0-25 1

25-50 2

50-75 3

75-100 4
[Nexus 4 Original Android Development] Chochiwpg:
r181 running very smoothly so far, love the increased vibration strength, enjoying it more than stock, working well. Thanks for the suggestion.
[Nexus 4 Original Android Development] jak3z:
The problem with this is that to keep the phone smooth, when the load is at 25% and you turn on only 1 core, the device won't ramp it up to max speed suddenly afaik, so it's better to have 2 cores run at a lower freq than 1 at max freq.
[Nexus 4 Original Android Development] franciscofranco:
I don't see a point in doing that. Basically you'll be onlining the second core every damn time you interact with your device because 25% load is as easy as touching the screen or swipping. So it will go online-offline-online-offline-online-offline. I hate that. 50% for 3 cores is too low, it will reach 50% easily opening an app or just swipping around the app drawer/widget drawer. We don't need 3 cores when doing that. and 75% for 4 cores is a bit steep, some games do not tax the CPU that much so it won't online them all that easily. And core management without averaging the load or doing any sort of semi-intelligent polling for some sustained time before deciding what to do - its not funny for your device. Onlining/offlining costs a lot in terms of processing. We want to avoid that operation as much as possible. Thanks for the feedback though, I got to talk about Kernel development for once :)
[Nexus 4 Original Android Development] Bill Gamble:
I dunno, 181 doesn't seem as smooth as 180 to me.
[Nexus 4 Original Android Development] pm~:
r181 is running great Franco, it's still early to say anything about battery life but everything feels pretty smooth and responsive.

scrolling in apps like g+/youtube/instagram is awesome... didn't notice any lags whatsoever.
[Nexus 4 Original Android Development] Redneck Trash:
Speaking of battery life I'm not sure it isn't my imagination but battery life when the screen is on seems a little better. Obviously that would help overall.
[Nexus 4 Original Android Development] HarbingerIV:
r181 is an absolute beast performance wise.. haven't run into any lag yet. I also noticed a slight increase in battery life as well. Wish I took a screenshot before my phone died but I got just over 4 hours SOT while playing about 45 min of games and lots of web browsing and texting. I'm very impressed with this latest test build :D

Sent from my Nexus 4 using aliens.
[Nexus 4 Original Android Development] ciprianruse88:
Just flashed r181 and I love it ! I also love the change to ondemand !:thumbup:
[Nexus 4 Original Android Development] zellleonhart:
r181 is god sent. so fast.

Just to ease some people's mind, r181 works with TC well, I have no issues at all.
[Nexus 4 Original Android Development] clshack:
I will wait this release :D
[Nexus 4 Original Android Development] zellleonhart:
Why wait when you can flash it right now.
[Nexus 4 Original Android Development] Burlito:
Just had my first reboot ever after finishing a call.

Edit: Using Stock ROM with r178
[Nexus 4 Original Android Development] jak3z:
Looks like Radio driver derped or something is wrong with your eMMC
[Nexus 4 Original Android Development] clshack:
I wait official release.

I will wait the update post.
[Nexus 4 Original Android Development] drawde40599:
I no , its smoother!:P 180 was good 181 is great, definitely feel the difference here, i no personally 165 was my favorite build and 181 is definitely starting to feel as snappy as that one did.
[Nexus 4 Original Android Development] Testraindrop:
Had also a reboot while watching pics in the gallery...
[Nexus 4 Original Android Development] Lap823:
r181 is awesome. So smooth. :)
[Nexus 4 Original Android Development] dmourao:
I second that.

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] sordna:
With what kernel version ?
[Nexus 4 Original Android Development] Testraindrop:
Latest of course r181 JSS.
[Nexus 4 Original Android Development] sordna:
Ok, we gotta specify every time to make it clear for franco, since not everyone is on latest. The person you responded too had a crash on r178 ! Other folks are on r176, or r180, etc :)
[Nexus 4 Original Android Development] Arstoien:
Other than these force closes, here's the steps I found to lock the second core on max freq:

1. clear app data, reboot and wait for the load to fall under 10% for cpu0 and cpu1

2. open the app, go to Per-App Power modes, go to the second tab "Default System Mode" and click save without changing the settings

3. back out of the app

4. go to the Default System Mode tab and change the governor from ondemand to interactive; tap save

Some times this doesn't start a series of FC's, but it does lock the second core on max freq each time I do it.

Let me know if you (anyone) can or can't reproduce it.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Testraindrop:
Yeah agree with you, sorry forgot to mention it in the first place. ;)

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] BlueFlame4:
r181 flies :)

Thanks for merging all those patches from Flo and changing to OnDemand! :)

Sent from my Gameboy Color
[Nexus 4 Original Android Development] Shardzmi:
Do we need Display Control if we already have Franco Kernel Updater ? :)
[Nexus 4 Original Android Development] Testraindrop:
No

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] Lap823:
For me Franco kernel updater does not save profiles nor load saved profiles. Not sure if its just me or not. Force closes on me if I load a saved profile.
[Nexus 4 Original Android Development] snorfu:
All my dreams came true with 181 :)
[Nexus 4 Original Android Development] Shardzmi:
I'm only using the recommended settings ( don't have enough time to deal with small changes :P )

Thanks for both of your answers - I thought so too :)
[Nexus 4 Original Android Development] JaqaL06:
franco i was using pa rom with stock kernel.. and i have never experienced deep sleep issue about 3 week.. but it's wasn't good enough for battery and i decided to flash your magic.. but now deep sleep issue started.. sometimes phoe stuck at minimum frequency until reboot.. what can i do for it? same apps same build.. didn't changed anything..

Sent from my Nexus 4
[Nexus 4 Original Android Development] oska3:
ondemand or interactive is better for battery safe-r.181
[Nexus 4 Original Android Development] Arstoien:
That's a good question. Why don't you try and give us your opinion? Ondemand is newly added, so there isn't a general consensus on what's better.

I'd like to compare them but my day-to-day routine is simply too inconsistent. As far as I've seen they've got very similar impact on the battery.

Sent from my Nexus 4
[Nexus 4 Original Android Development] nyyankees1237:
Is r181 close to be officially pushed via fku? Just curious, sorry if this was answered already.
[Nexus 4 Original Android Development] redsmith:
Clear app data and reboot... no problem here loading saved profiles.
[Nexus 4 Original Android Development] BlueFlame4:
I just had a reboot with r181 while playing GTA Vice City and listening to TuneIn radio.

Looks like the device was overheating, wasn't it? I left everything on stock (65°C threshold). Last_kmesg will be up soon.

I hope I could help you :)

Sent from my Gameboy Color
[Nexus 4 Original Android Development] Royvin:
Just purchased your franco.Kernalupdater app today but I don't see this kernal available to download. I am kind of new to the Nexus 4 scene I'm just running stock/rooted 4.3 JWR66Y and I installed knightly #178. My question is when is the 181 going to show up in the app? Or is the #178 the most up to date. Thanks for all you hard work!:good:
[Nexus 4 Original Android Development] jak3z:
178 is the latest nightly, r180 and 181 are more "test" nightlies that will made it to the app when enough feedback/confirmation that it's working is acquired.

Welcome to the franco.kernel family :)
[Nexus 4 Original Android Development] Lap823:
Still not working for me. I downloaded color control and works good. Just wish I didn't need to use color control for it to work.
[Nexus 4 Original Android Development] Royvin:
Awesome thanks for info jak3z and happy to be here!
[Nexus 4 Original Android Development] nexusmaniac:
R181 is perfect, although I've said that about all of the updates ;)
[Nexus 4 Original Android Development] Husy:
Guys, sorry for the question. I am running Stock and latest 4.3 and I am running r178 JWR, and I was wondering can I just dirty flash r181. No need to wipe anything?

Thanks in advance!
[Nexus 4 Original Android Development] Testraindrop:
yes, you can.

Just clean the app data of FKU, maybe be helpful as there is a change to ondemand from interactive.
[Nexus 4 Original Android Development] LibiSC:
Franco did you push the latest changes to your github... I pulled but says already up to date

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] dapsANDpoundz:
Been running r181 for a few hours. Initial impressions are its smooth of course but some of you are exaggerating the "complete" loss of lag or stutter. Certain apps still stutter but that may be the apps fault. Certain functions still produce lag like multitasking too quickly, but this is the best performance from any of the kernels so far.

As for battery life, slightly worse for me. Been on WiFi and its usually better for me at this point but I'll give it a full day before I make any other comments about it.
[Nexus 4 Original Android Development] sordna:
Correct, no need to wipe anything when updating franco kernels. You can even flash stock and franco back and forth without worry. I use either the Franco Updater app to do so, or Universal Kernel Flash app.
[Nexus 4 Original Android Development] zephiK:
Do note if you're on a AOSP ROM you cannot use the FKU to update as it only downloads the JWR version of the kernel. So if u use a JSS rom, download manually from the website
[Nexus 4 Original Android Development] michelemascia7:
Wipe cache and wipe dalvik cache :) wipe factory is not needed :)

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] Husy:
But some people just said no need to wipe anything at all.
[Nexus 4 Original Android Development] sordna:
no wiping is needed, franco has mentioned it several times in this thread, use advanced search of this thread and look for wipe or wiping, by username franciscofranco
[Nexus 4 Original Android Development] ciprianruse88:
Wipe your nose :p No need to wipe...just flash :thumbup:
[Nexus 4 Original Android Development] Husy:
Thanks guys, Ill make sure I search for it the next time! Won't happen again promise hehe :D
[Nexus 4 Original Android Development] lwkkazz:
Hey guys, where do I get the newer versions? I using the jss 4.3 r178, I have seen ppl said that installed r181.

Thanks in advance, sorry for my noobness, I new to Nexus 4
[Nexus 4 Original Android Development] zephiK:
Search the thread. You being new to the N4 doesn't mean anything, its basic fundamentals of a forum.

On above the thread "Search this thread" (Search) (Settings).... type in r181.

Done.
[Nexus 4 Original Android Development] Beerad875:
Weird man, tried flashing the JSS build of r181 through flashify and it doesn't seem like it wants to flash, it goes to the twrp flash screen for a split second, then goes to the main menu. Running slim beta 3.

Edit: went straight to recovery and flashed from there, worked that time.
[Nexus 4 Original Android Development] Pure Drive GT:
Got a weird message about my language on xda... Anybody else got similar messages/warnings before? It's kind of weird cause i didn't use this offensive language against any user but more to emphasize my statement: "this is fücking great" now he mentioned me not to bypass the filter with the ü, so can i write ****ing like this or is ****ing not allowed at all?
[Nexus 4 Original Android Development] C4SCA:
No! Simple dont use that language. Todays english language is evolved enough (as any other language) to have specific words or expressions to describe ur feelings, toughs,...

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Original Android Development] closedcircuit:
I think I may have found a bug with kernels 172 thru 178. While in China using a 128k sim. Android com.android.phone will crash upon boot. Somehow the combination of Franco and a China Unicom 128k wcdma SIM creates this fc and breaks root so trying to restore the kernel previously backed up via the Franco app is futile.
[Nexus 4 Original Android Development] franciscofranco:
Just write as you wish. As long as you don't offend anyone directly you're free to write as you please- People seriously need to realize that swearing is not offending.

Kernels don't give force closes like that - you fúcked something else up ;)
[Nexus 4 Original Android Development] LibiSC:
Did you push latest changes to your github from 181 ?
[Nexus 4 Original Android Development] ziddey:
look at jss branch
[Nexus 4 Original Android Development] LibiSC:
That one has the commits but I use jwr I guess I'll have to cherry pick... Thanks for the info

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] closedcircuit:
Perhaps I should mention that these same kernels 172 - 178, work fine on both PA 3.96 & 3.99 while using a T-Mobile US SIM in the phone.
[Nexus 4 Original Android Development] franciscofranco:
Oh sorry I forgot to push for the JWR branch. Will do.
[Nexus 4 Original Android Development] SaReDnAL:
I have just installed r181 JSS version with cm10.2 nightly

Everything running smooth. I will post my battery life experience with interactive governor.

Enviado desde mi Nexus 4 usando Tapatalk 4 Beta
[Nexus 4 Original Android Development] solrac.dc:
Yes it does ;)
[Nexus 4 Original Android Development] alcurtis93:
No I'm not an idiot it's just not good that even on 1ghz under clock is still overheating
[Nexus 4 Original Android Development] awtacular:
Yup, It's the same. I bought both of them. I didn't know it at the time but whatever. The money went to a deserving person.
[Nexus 4 Original Android Development] drawde40599:
Throttling dosent mean overheating ;)

---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------

I've been running 26 since you dropped it, data issue seems to be gone ,been on internet for last hour with no issues 24-25 wouldn't have made that far without data issue , 26 still just as smooth , lag free and no heat , . if i wouldnt have read it here on XDA i wouldn't have even known u lowered high speed.... . feels just as smooth/ fast on AOKP .

Thanks !
[Nexus 4 Original Android Development] alcurtis93:
I'm aware of that but for throttling to take place it must overheat above the thresholds.
[Nexus 4 Original Android Development] franciscofranco:
So what setup are you using? Rom, kernel version etc? I can't make it heat if I wanted, it starts to throttle when the cpu reaches 55ºC. For example on the GN I can only start feeling heat in the back when the CPU reaches 65ºC.
[Nexus 4 Original Android Development] alcurtis93:
Latest cm10.1 and r23. I think it's just games such as need for Speed but is strange it's generating that much heat.
[Nexus 4 Original Android Development] franciscofranco:
Question is: can you reproduce that on Stock rom + stock kernel?
[Nexus 4 Original Android Development] alcurtis93:
Good question. I'll investigate :) please will you add faster CPU binned voltages to this kernel as it may reduce heat
[Nexus 4 Original Android Development] franciscofranco:
I'm not gonna mess with anything related to frequencies unless Google adds it on their sources. Phone is good as it is, they will know better than me or anyone else if they should add support for Faster chips.
[Nexus 4 Original Android Development] drawde40599:
Butting in on this conversion ,with stock ROM and kernel i couldn't do normal web browsing without it throttling , this kernel has made total 100% turn around with this phone with heat issue . OK butting out now ;P
[Nexus 4 Original Android Development] bongostl:
Franco-how much impact do you think the toolchain you build the kernel with has?

I notice a dramatic difference on a 4.7 with -03 on the rom...

(And, if you don't mind sharing, what toolchain do you compile with and why? )

Thanks so much.I learn a ton from reading your thread!
[Nexus 4 Original Android Development] sionyboy:
Flashed r26 this evening, coming from r23, will report back if anything isn't at should be. I'm sure it won't be though! ;)
[Nexus 4 Original Android Development] DaX05:
All is good on r26. :)

Beamed via Nexus 4
[Nexus 4 Original Android Development] Roscopcoletrain:
Like i said, zero issues playing need 4 speed, stock rom, R23. Smooth a butter. Maybe even smoother lol

Sent from my Nexus 4
[Nexus 4 Original Android Development] Globespy:
It was late.... Of course I meant governors :)

No intention of adding them? That changes my decision on buying your kernel app then as it's been clearly documented that ondemand/interactive governors are not even close to the efficiency of newer governors like SmartassV2, lulzactive etc.

Hey, but it's your show man!

BTW - I am already supporting you, just bought your screen color app for the N4
[Nexus 4 Original Android Development] franciscofranco:
I use Google's 4.7 toolchain from androidsource git repo. Rom gets more benefits from flags than the kernel though. I only compile with -02, -03 is stupid for the kernel. I don't know much about toolchains though.
[Nexus 4 Original Android Development] franciscofranco:
SmartassV2 is obsolete for a long time, doesn't work correctly with multi-cores.

lulzactive is **** and its a buzzword.

Interactive is being developed every day by Google.

I really would like to know what idiot told you that those stupid governors are better than Ondemand (mainline kernel governor that is developed by the smartest and best programmers in the world), and Interactive (worked on by Google since 4.1). Lulzactive and Smartass are forks of the first interactive code 2 years ago. I really get pissed off by this. Not pissed off about you, just pissed about the subject!

You have your answers ;)
[Nexus 4 Original Android Development] Gaheris:
So what about the reported r23 random reboots? is thre release still going for a milestone?
[Nexus 4 Original Android Development] franciscofranco:
Use r26-test.
[Nexus 4 Original Android Development] ApriliaM3:
Are you serious?

You cannot make your point without 1. Swearing and 2. Bypassing the swear filter to break the rules even more?

If the swear filter censoring your post is not indication enough for you, then I'm not sure how much simpler I can make it...

I was quite clear in my PM to you but instead of replying to my message and asking me, you decide to come here and post it all again in public.

RULE 2.1 Language: XDA is a worldwide community.

As a result what is ‘ok’ to say in your part of the world may not be ok in someone else’s.

Please think about who is reading what you write and don't use profanity, sexually explicit language, rudeness or swearing.

Conversely, while reading member posts, remember that word you find offensive may not be to the writer. Tolerance is a two way street.

Wrong! ...and you've been warned in the past that this is unacceptable.

You're making a mockery of the rules and mocking Moderators who are trying to do their job by coming here in response to reports requesting us to clean up the mess.

^^^ Exactly this. Thank you.

Do not swear here

Do not attempt to circumvent the swear filter

Going forward, anyone who cannot follow these rules should simply not post here... because you will be dealt with as per the rules.
[Nexus 4 Original Android Development] eagleeyetom:
Do you have a problem with that?
[Nexus 4 Original Android Development] svnhvn:
Geez.. Franco vs guy above its just like watching kirk vs spock.
[Nexus 4 Original Android Development] :
Swearing has never been acceptable in any place, with any race or culture as far as decency, professionalism, proper conduct and good values are concerned. Having the basic right of freedom of expression doesn't mean being able to say anything. Along with such right is an inherent moral obligation to observe public policy. Viva XDA!

Nexus 4|PA 3.99|Franco Kernel