yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] thebryceee:
I rebooted and haven't had one since. First time something like this has happened since T-Mobile's LTE launch in Vegas.
[Nexus 4 Original Android Development] franciscofranco:
I found out why some of you say r153 might be a little choppy when opening apps for example. This is what happens currently:

1. Touch the screen

2. If current cpu0 frequency is < input_boost_freq boost cpu0 current freq to input_boost_freq

3. The governor checks if the is_touching is true. If its true it checks if we're inside the 1 second window of boosted freq time after stopping touch screen interaction

4. If we're inside the window return from the function.

This return means that while that window is true cpu0 will be blocked at input_boost_freq, nor lower, nor higher. Sometimes some apps require more frequency than input_boost_freq and we're bottlenecking cpu0 heavily not letting it ramp up.

So we have to change 4. and make it like this:

4. If we're inside the window AND the new calculated freq is below input_boost_freq (prevents cpu0 to go below the boosted freq for smoothness) return from the function. If the new calculated freq is > than input_boost_freq we let cpufreq do its job and ramp it up. If is_touching is still true it won't ramp down cpu0 further than input_boost_freq.

I guess a r154 is mandatory :)
[Nexus 4 Original Android Development] franciscofranco:
Ok get r154, changelog post above. Good night!
[Nexus 4 Original Android Development] :
That's technical. But I found a non-technical solution. Everytime I flash your kernel, I also flash ROM & GApps, I'm using PA in particular. That ends all stuttering with r153. After several kernel flashes, I observe some stutterings. So kernel's not all to blame I guess. Well, just a guess. I'm no expert but it doesn't hurt saying this especially for some who always complain.

And r154 would be greater then. Cheers!

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
I don't see any correlation between flashing rom + gapps then Kernel and stutters.
[Nexus 4 Original Android Development] Nocturnal86:
download was quick and painless! Lets see how this baby works :)
[Nexus 4 Original Android Development] Mercado_Negro:
And here I was, wondering why I didn't get a notification about r154 when I realized I didn't install your application last night when I flashed RootBox lol
[Nexus 4 Original Android Development] thebryceee:
154 is ****ing flying
[Nexus 4 Original Android Development] aimcr7:
Download is now flawless, scrolling is way smoother on r154.

No more slightly lag here and there. Great work franco! As always.:)
[Nexus 4 Original Android Development] yoyoz808:
Theeeeerre ya go franco. r154 is muuuuuuch better. I knew there was something off with r153. It works like magic now lol.
[Nexus 4 Original Android Development] CarlosAbia:
R154 is GREAT!! THANKS, donated to your app
[Nexus 4 Original Android Development] Lamien:
Hello, I'm sorry to ask but does this kernel contain the fix like in cm stock kernel that gets rid of the annoying flicker when pie is enabled? Sorry for my english.
[Nexus 4 Original Android Development] Reatret:
Can't believe how fast it is going back home all of a sudden! That is one thing that irked me but now its gone! Unbelievable.
[Nexus 4 Original Android Development] goTouch:
r154 is definitely faster!!

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] cobhc:
Why? Those comments were about performance, not battery life. You don't need to wait a full battery cycle to judge performance...
[Nexus 4 Original Android Development] :
Finally the performance is rock solid in apps and games with r154 not seeing stutters with my aggressive settings on input_boost of course, thanks Franco
[Nexus 4 Original Android Development] nachordez:
Smoother than ever! :thumbup:

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound
[Nexus 4 Original Android Development] m3dd0g:
The best kernel for my N4. Big THX for all your hard work Franco.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] pac213:
What app do you guys use to change the settings of this kernel?
[Nexus 4 Original Android Development] Vangelis13:
Franco's app, of course! Support your dev. ;)

You can also user trickster mod or system tuner.
[Nexus 4 Original Android Development] Slymobi:
Or set cpu and prob loads more but Franco's is made for it so best to use it. Agree support the dev.

Sent from my Nexus 4
[Nexus 4 Original Android Development] pac213:
I can't see options to change hi_speedload and freq using trickster mod and system tuner. I'll try to buy the app but it's a bit expensive in my currency lol.
[Nexus 4 Original Android Development] pa.pn2:
what can i say,awesommeee franco

almost 50% left and 3h of screentime
[Nexus 4 Original Android Development] gkot71:
Just a very naive question guys. If I flash this kernel over my stock Rom, can I still get Google updates? Or shall I have to get back to stock kernel?
[Nexus 4 Original Android Development] alcurtis93:
You can but it will remove the kernel.
[Nexus 4 Original Android Development] alanwyl:
So, after the OTA update, reflash this kernel will work again?:confused:
[Nexus 4 Original Android Development] pac213:
There, just bought the app but I can't see any voltages on the voltage window.
[Nexus 4 Original Android Development] pro.aggro:
4 shizzle :D

Sent from Nexus 4 powered by PARANOIDANDROID
[Nexus 4 Original Android Development] Vangelis13:
;) which kernel version & which rom?
[Nexus 4 Original Android Development] benrees21:
You won't be able to update with a custom kernel or a custom recovery. You will have to download the stock updates from here when they get posted and flash through recovery and then flash the kernel. So you will be on the latest OTA update but just flashed by yourself.

Because I'm a Nexus b!tch and I like to run the latest source and binaries!! AOSPA!
[Nexus 4 Original Android Development] alcurtis93:
Not implemented yet for this kernel
[Nexus 4 Original Android Development] pa.pn2:
Darkbeanjelly+franco r22 @vangelis
[Nexus 4 Original Android Development] Ibsonic:
I can't go lower ! R22 is the sweet spot already :D this kernel is just friggin fluent now.

But if i have to choose and go lower, 65 / 918 here with max clock on 1350 Otherwise I'll irritate myself while seeing a lag..

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] alcurtis93:
I'm liking 70/918 with max clock of 1026... Smoothness shows the power of the krait cores
[Nexus 4 Original Android Development] benrees21:
Max:1242 Interactive.

Because I'm a Nexus b!tch and I like to run the latest source and binaries!! AOSPA!
[Nexus 4 Original Android Development] mundixx:
Impressive results!
[Nexus 4 Original Android Development] Bavilo:
Not sure where to ask this but I've noticed something strange with my sdcard.

For some reason, I get recursive listings of my sdcard such as /sdcard/sdcard0/0/0, etc.

Not sure if it's because of the kernel or because of Paranaoid Android. This problem just recently appeared around 2 days ago or so.

Any Ideas?
[Nexus 4 Original Android Development] djpry:
the best one yet....super smooth,fast...rock solid...battery backup is as good as 148..................

"franciscofranco" if u were a gurl ud have kissed u....my frnd :highfive::highfive::highfive::highfive:

god bless u
[Nexus 4 Original Android Development] gm.cinalli:
Yes, I see them! So it's normal that you have a no signal percentage, but in my case? I don't know why I have that values of no signal percentage without any red bar, and so without any signal lost.
[Nexus 4 Original Android Development] sNoxious:
So Franco reverted back to just 1 core only? Cos I only see 1 core online on System Monitor.

Sent from my Nexus 4
[Nexus 4 Original Android Development] sam razzy:
Hahah his kernel is baby.. My phone is a boy handsome sec'xy.. He is flirting smoothly to her.. ;) love to see tat..
[Nexus 4 Original Android Development] evostevo1:
R154 is very nice over here
[Nexus 4 Original Android Development] aventu:
not really no

edit: answer for 3 posts above sry
[Nexus 4 Original Android Development] drawde40599:
Im showing 2 on all the time, and under load all 4 kick in. Build 154
[Nexus 4 Original Android Development] cenonmin:
Not sure if its just me but i am getting data drops on 154, i reverted back to 151 and drop outs are gone.
[Nexus 4 Original Android Development] nachordez:
Sure that you haven't installed M2 instead of 154? It's still 2 core on...

nexus4 / stock / last Franco.kernel nightly / V4A sound

gt-p5110 / PAC rom / V4A sound
[Nexus 4 Original Android Development] zellleonhart:
r154 is so smooth, almost 0 lag in opening apps, scrolling in most apps are smooth (even XDA), butter scrolling in my fav twitter app Robird :DDD

But I have been getting high hsic wakelocks when not using wifi since r153, I know it is using the stock hsic. Will it cause a lot of drain?
[Nexus 4 Original Android Development] CerB:
Anybody have the colour settings from franco in trickster ?
[Nexus 4 Original Android Development] limeaide:
Tapatalk shows them just fine. Guess its a major derp on the xda app.
[Nexus 4 Original Android Development] Talvathir:
Ha, 154 even makes tapatalk smooth. Nice one Franco!
[Nexus 4 Original Android Development] eugenesan:
Dear [MENTION=3292224]franciscofranco[/MENTION],

Several people reported data connection instability issues and I believe many more just don't notice the problem since it appears after many hours and most of the people here flash/reboot on daily basis.

I am sure you are a busy man and probably not ignoring this issue on purpose.

But maybe you can find a second and respond?

Thanks.
[Nexus 4 Original Android Development] michael_ta315:
derp.

:silly:
[Nexus 4 Original Android Development] nachordez:
Lol...

nexus4 / stock / last Franco.kernel nightly / V4A sound

gt-p5110 / PAC rom / V4A sound
[Nexus 4 Original Android Development] GuestK00150:
the last two versions 153 & 154 are very loud on the headset, can`t hardly use it without exploding my ear on the lowest volume. would be really nice to see this turned a little lower.

thanks
[Nexus 4 Original Android Development] leets4uc3:
Whut.. There is setting in the app to change it.
[Nexus 4 Original Android Development] Redneck Trash:
I was concerned that having two cores running would have a negative affect on battery life but that hasn't been the case. I swear Franco is into some voodoo magic.
[Nexus 4 Original Android Development] Dan1234567890:
Maybe the best thing for you is to install app from the store that monitors signal and warns when signal is lost... Its mentioned in thread in last few days... It's called someting like "no signal" or so... These rom battery statistic has been quite inaccurate and misleading a lot of times...
[Nexus 4 Original Android Development] ImbaWind:
r154 got 2 cores running all the time, it's okay for battery life?
[Nexus 4 Original Android Development] BrandoHD:
Can Undervolting be the direct cause of a kernel panic?

Just a question for my personal knowledge!
[Nexus 4 Original Android Development] bokagavrilov:
there wasn't any huge drain when i tested but It felt much more hotter for my taste while charging (37+ while reading a book before Max I sow was 34) But this is just my personal opinion don't take it as a sentence ;)
[Nexus 4 Original Android Development] tiotempestade:
Also seeing this. 2 cores always up.. In system monitor they are at 384mhz and alternating to 1.5 often.. Is this behaviour expected?
[Nexus 4 Original Android Development] :
Its been like that since r152 bro, battery life impact is up to you to judge though
[Nexus 4 Original Android Development] nachordez:
Yes.
[Nexus 4 Original Android Development] thebryceee:
I'm never wrong.
[Nexus 4 Original Android Development] sabrezoo:
Sorry, noob question.

What is the difference between Milestone 2 Kernel and the nightlies Kernel like the latest R154?

I want to use this kernel, but confuse which one?

Sorry for my poor english
[Nexus 4 Original Android Development] elzafir:
Milestone is the latest stable version. Ready for daily use.

Rxxx is the nightly. It's what franco release whenever he made an improvement or modifications.

Eventually, one of the Rxxx will be considered 'good enough' to be released as a Milestone.

R154 is much, much newer than Milestone 2.

Sent from my Nexus 4 pimped with ParanoidAndroid and Franco.kernel
[Nexus 4 Original Android Development] GuestK00150:
only to turn the volume up, not to turn it down, I guess
[Nexus 4 Original Android Development] defffizz:
r154 is amazing, never experienced such speed while navigating, browsing pictures, just scrolling.. I'm sticking with it, can't be better than this

Nexus 4, Paranoid Francoid
[Nexus 4 Original Android Development] lordvj:
154 is kickass!! very smooth though the phone seemed a little hotter on 3g.
[Nexus 4 Original Android Development] nachordez:
It can, trust Franco... :thumbup:

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound
[Nexus 4 Original Android Development] jarayn:
Dont know if this is known issue.

Clear app data doesnt seem to work for GPU freq and some hotplug settings. It retains the custom value i previously selected
[Nexus 4 Original Android Development] PelegK:
Will test r154 !
[Nexus 4 Original Android Development] aventu:
The default settings will be loaded after a restart.
[Nexus 4 Original Android Development] :
Definitely +1000 this, thought Milestone 2 was fast then r134 came out then r140 was even faster now r154 is blazing, can't wait to see what Franco will do next
[Nexus 4 Original Android Development] jarayn:
Except they arent thats the point im trying to make.
[Nexus 4 Original Android Development] ridikolous:
This is what happens on a fresh install of fku app. But one I restart it all is fine. Is this normal? ROM I'm using is paranoid android. This didnt happen on the last version of fku app.

AK powered AOSPa halo.
[Nexus 4 Original Android Development] dapsANDpoundz:
So you all are saying r154 is definitely great performance wise, good. You guys still getting your typical battery life though? Probably gonna take awhile to notice I suppose. Is it worse or better, for you that is, as compared to your previous build.
[Nexus 4 Original Android Development] BakaPhoenix:
Battery life should be like 153 since franco fixed only a problem that caused lag in the 154 but the hotplug is the same
[Nexus 4 Original Android Development] Vangelis13:
Probably gonna take a while to notice. ;)
[Nexus 4 Original Android Development] Martin_Ro:
R154 is smooth as butter !

Some suggestion regarding touch-boost:

If I get it right, touch_boost raises the cpu speed to a given value (Default 1026MHz) and after a given time (1000ms) reduces it again.

Maybe you shouldn't do it timebased but loadbased ?

Sometimes there is no need for a boost for about a second but only for, lets say, 100ms. On other situations (after an big swipe on screen, tapatalk scrolls all the way down), maybe it's not done in a second, so the speed is lowered to early what maybe creates the microstutters we can see then.

Maybe like that:

....
if ((ktime_to_ms(ktime_get()) - freq_boosted_time >= 100) && cpu_load < 20)
is_touching = false;
...

In this example the touch boosted time would be lowered to 100 and after that it would be load controlled till the load falls under 20%...
[Nexus 4 Original Android Development] drakexpl:
With newest kernel 2 cores are staying online all the time. :/

Wysłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] carburano:
Really? Francisco never told us of this... :cool:

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] drakexpl:
Sorry but for me its really weird, im using beastly batt profile an i have 2 cores online all the time. Its not an energy saving option in my noobish opinion.

Wysłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] lorolouis:
Indeed many things are NOT in changelog ... but please, before asking just do a little search:

Search: Keyword(s): "2 cores online" .... you will see your answer in several seconds.

Shortly, 2 cores are on by design.
[Nexus 4 Original Android Development] tuilalnvinh:
So, after many fixes, the hotplug mechanism now acts likely stock mpdecision (2 cores online, boost to min 1ghz when touching...), doesnt it? :D
[Nexus 4 Original Android Development] RootTheMachine:
This is true. In a 12 hour day, I get a 2 hour hsic wakelock that definitely affects battery. It wasn't there before either with the non-stock hsic.
[Nexus 4 Original Android Development] trailblazerz11:
Thought stock locks min at 1ghz even when idle, but it's been awhile ;)
[Nexus 4 Original Android Development] Arstoien:
Edit: my bad, I was talking about something else.. :)

Yes, that's the intention. What's worrying you? If it's battery life, I haven't heard anyone complaining from decreased battery life since the default min.cores online was increased from 1 to 2, and I myself haven't seen any negative difference.
[Nexus 4 Original Android Development] TheIntruder:
He can't search or read so doubt he has the knowledge to worry about anything :P
[Nexus 4 Original Android Development] PJcastaldo:
So which gov are you guys using?
[Nexus 4 Original Android Development] franciscofranco:
Thats not reliable, specially in a code section that gets run almost 100 times every second and cpu_load changes too much, too fast.

Not at all.

What do you think?
[Nexus 4 Original Android Development] sspyed:
Don't know about through & through instability--data is solid as a rock on the phone itself, but USB tethering has been unstable since r140. If I tethered more often or knew the first thing about logcats I would definitely send in a proper report you could use Franco.

I know there's nothing you can do without a logcat but just letting it be known in case anybody who does know how to logcat is having similar issues.
[Nexus 4 Original Android Development] franciscofranco:
Dunno about that, HSIC stack is stock now.
[Nexus 4 Original Android Development] Cuzz1369:
In the last 8hrs (I was sleeping) I only had 23mins of hsic wake locks.

Carbonized and francofied N4
[Nexus 4 Original Android Development] PJcastaldo:
Everything seems nice with this kernel. However.. It seems all of my volumes are much quieter than before. Ring tones and in call.
[Nexus 4 Original Android Development] yokuyuki:
I haven't gotten a chance to switch to r154 yet, but on r153, SwiftKey lags from time to time causing me to mistype. Not sure if the change for r154 when opening apps will make a difference for it though.

r154 was out for 3 hours and you can say stuff about the battery?

26 min after 11 hours for me. I've been mostly on wifi though.
[Nexus 4 Original Android Development] saranyan:
If the screen is off and some process wakes up the phone, Still will two cores be activated or only one core? Screen off also minimum two cores?
[Nexus 4 Original Android Development] franciscofranco:
Screen off 1.
[Nexus 4 Original Android Development] eluspo:
I uv'd to -125 is that okey?
[Nexus 4 Original Android Development] realfelix:
You will find out if your phone doesn't reboot while playing with it.
[Nexus 4 Original Android Development] eluspo:
Well fortunately it doesnt, so am i good to go? :)
[Nexus 4 Original Android Development] ciprianruse88:
-125 is too much to start. -25 then -50 then -75 ....then -125 is the way. If it freezes and reboots while it scales to max freq set then your device can't handle the uv you did
[Nexus 4 Original Android Development] eluspo:
I started 150 then it rebooted then went down 125. Seems stable for me. If i get a reboot I'll lower down to 100.
[Nexus 4 Original Android Development] nachordez:
Try some demanding apps or games to see if it works. And try camera also, uses to be very UV sensitive

nexus4 / stock / last Franco.kernel nightly / V4A sound

gt-p5110 / PAC rom / V4A sound
[Nexus 4 Original Android Development] XsceneXhippieX:
Don't know if it means anything but I notice I big performance difference in app loading and scrolling from 153 to 154, hope my battery life gets better too, just tried undervolting -25 so fingers crossed
[Nexus 4 Original Android Development] manulemaboul:
Just had a signal loss.

I think it's due to the sun, there is a huge black cold spot on it since May and it can totally disturb radio transmissions on earth.

It's back now, even if he can't find any provider lol.

I see nothing that could cause that in the software since hsic driver is stock and has always worked so far.

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] freddysam:
Just because you are not rebooting, doesn't mean your system is not being corrupted by the uv. You need to run some stability tests for a good amount of time. There is no other reliable way to be sure you are at a safe uv level. Why are you uv'ing anyway?
[Nexus 4 Original Android Development] eluspo:
Will try camera and dh4 now. Will get back after the test.
[Nexus 4 Original Android Development] blankit:
Hows battery life in 154?
[Nexus 4 Original Android Development] nexusmaniac:
Depends on what your doing but it's been great so far :)
[Nexus 4 Original Android Development] blankit:
All I needed to know...will be flashing now
[Nexus 4 Original Android Development] m3lover1:
Correct me if I'm wrong, but isn't r154 supposed to boost both cores to input boost freq upon touch? Under system monitor it is only boosting cpu1...
[Nexus 4 Original Android Development] mkfort:
That's what r152 did. It was changed in r153.
[Nexus 4 Original Android Development] corwest:
Round 2...?
[Nexus 4 Original Android Development] :
Dude don't start this crap again, look at his name please
[Nexus 4 Original Android Development] jrxtepan:
I'm pretty sure that if you learn how to read... It won't be ****ing misleading. :rolleyes:
[Nexus 4 Original Android Development] m3lover1:
O really? I thought it was the other way around? R152 boosted one cores and then r153 changed it to both cores?
[Nexus 4 Original Android Development] DeepMemory:
Nightlies r154 does not have lockscreen lag compared to previous nightlies. Thanks Franco :good:
[Nexus 4 Original Android Development] mkfort:
Nope.
[Nexus 4 Original Android Development] italia0101:
Is r154 smoother than mp decision ? ..

Ive stayed on the Franco kernel included in the pa rom which has mp decision turned on , and get around 4 hours screen on ..
[Nexus 4 Original Android Development] kecinzer:
Someone tested Antutu Benchmark? With previous builds I had score over 20K, with Build 154 I have 15K.
[Nexus 4 Original Android Development] rmead01:
deleted.
[Nexus 4 Original Android Development] CarlosAbia:
I won't ever leave r154, not even for a M3 release :)
[Nexus 4 Original Android Development] xdviper:
Ok, same problem here. Using Purity and it was fine before. I've changed radios from .54 to .48 and it still didn't fix it. I think I'm going to do a wipe to stock and see if it's the kernel/rom related. But I doubt its the rom though as it was working loud and clear.
[Nexus 4 Original Android Development] Vangelis13:
I also find it annoying. And reported it weeks ago. Mods had a look, apparently it's ok. Also for Francisco. Still, annoying. But what can you do.

Now, discriminating / offending handicapped people goes way beyond all that. Please edit your post.
[Nexus 4 Original Android Development] manulemaboul:
By the way, thanks for proving my old theory Mr Franco :).

Hotplugging a core do drain as much as just leaving him idling at his min freq, 2 cores always on now and it doesn't drain more _at all_ :)

I love when I'm right :p

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] blankit:
Does anyone turn on mp decision on in r154? Is it best to leave it off?
[Nexus 4 Original Android Development] 75markus:
there is no more mpdecision in this kernel ;)