yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] evostevo1:
152 has actually smoothed out for me quite a bit. I'm running stock ROM. I like this release.
[Nexus 4 Original Android Development] flakinarist:
r152 lags definitely more while playing" the Simpsons: tapped out" as on previous releases. :(

But I appreciate your work!
[Nexus 4 Original Android Development] Arstoien:
It does lag more after a reboot for some reason but after the media server has done scanning and the extra load is back down to <3% (a couple of minutes for me) it's smooth and actually I can feel the scrolling being improved quite a lot! Facebook and Google+ haven't been this smooth in a very long time. And I even have the hotplug threshold increased to 70 and dynamic scaling off. 60 is too low for me, it runs on 4 cores too often when it can do all with 2. The change in the default timer rate for 2 cores is also welcomed, should compensate for any extra juice drained by having 2 cores all the time, which imo shouldn't be that much in the firs place.

Sent from my Nexus 4
[Nexus 4 Original Android Development] nyyankees1237:
Loving the battery life and smoothness on r151 here. My favorite release so far, I'll probably skip out on 152. Thank you Franco for making my N⁴ amazing.
[Nexus 4 Original Android Development] eluspo:
So far so good here, but will be testing more.
[Nexus 4 Original Android Development] lordvj:
glad I bought your app yesterday and today you release this peach of a kernel. 152 is amazing really smooth :thumbup:
[Nexus 4 Original Android Development] trailblazerz11:
Pretty sure they've been pushed for a couple days now barring anything new on Francos local git. I've been using since it was pushed and haven't experienced any of the mentioned lag.
[Nexus 4 Original Android Development] rockafellor:
[MENTION=3292224]franciscofranco[/MENTION]

Using German fku

When loading a colour profile it says "Belastung" for Load in German. This is wrong and should be "Laden"

Sent from my francofied paranoid Nexus 4 with Tapatalk 2
[Nexus 4 Original Android Development] Overdose1986:
Im having HUGE battery drain when browsing with chrome using 3G... I mean 15%+ in less than 5 mins
[Nexus 4 Original Android Development] drawde40599:
If u go into the app and hit the menu button in right hand corner theres a button for 'help translation' i think he's 100% dependent on community for all translations
[Nexus 4 Original Android Development] Lothaen:
Chrome or Chrome Beta?
[Nexus 4 Original Android Development] nyyankees1237:
Disable tilt scrolling.
[Nexus 4 Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION]

Can you make the input_boost_freq 1350 or 1026, 702 is too low, it's laggy, at 1350 everything else stock settings, it's super smooth, even tapatalk 4 that misbehaves with mpdecision is giving best performance I've ever seen, thanks for your great kernels and the new app looks gorgeous

I'll post battery life results at 1350 later since that will be a concern
[Nexus 4 Original Android Development] aimcr7:
That's how it works, if you clear app data and not reboot the value is still the same because it was set on boot, if you tick clear app data when flashing new kernel, it's actually clear your app data before reboot so the setting will be default kernel value when your phone booted up.

---------- Post added at 12:54 PM ---------- Previous post was at 12:49 PM ----------

Franco already mentioned earlier that it's maybe something in the code. someone already tried to change input boost to 1350 but it still a bit laggy than r151.

And I don't have any lag with r152, except I feel beach buggy blitz suffers occasional frame drops but it still very playable and you won't notice it if you never played it with r151. :)
[Nexus 4 Original Android Development] Fobz:
I dont game on my phone just do the general browsing and reading. I gotta say r152 has been the smoothest so far. Even on tapatalk 4. Thx for the awesome kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] wngmv:
More importantly... Franco did you get a phone??!! I'm not rooting it because your kernel's not out.
[Nexus 4 Original Android Development] Prod1702:
Franco current kernel does just fine for the time being. I can't wait for his app to get updated so i can ditch setcpu. i want Voltage control.
[Nexus 4 Original Android Development] franciscofranco:
Yes I managed to order one today :)
[Nexus 4 Original Android Development] ctfrommn:
Nice......now the fun begins :)
[Nexus 4 Original Android Development] whittikins:
16 or 8 gb? (1-2 weeks or 6-8 weeks) :)
[Nexus 4 Original Android Development] franciscofranco:
But the battery temp shouldn't be used to measure heat in the kernel driver. It makes sense that when it hits 79ºC it goes into deep thermal throttle mode, I increased the threshold to 80ºC, so maybe we're int he right path here. Thanks for the testing!
[Nexus 4 Original Android Development] ctfrommn:
I'm wondering if the battery is more prone to heat related failure than the processor is and that's the reason they tied it to that instead. I've heard that from a dew different places now.
[Nexus 4 Original Android Development] franciscofranco:
16GB one, should be 1-3 weeks :)
[Nexus 4 Original Android Development] franciscofranco:
Can you give me some links? Thanks.
[Nexus 4 Original Android Development] ctfrommn:
Sorry, meant Ive heard that the throttling temp is tied to the battery, the rest is just conjecture.
[Nexus 4 Original Android Development] aimetti:
awesome
[Nexus 4 Original Android Development] lnfound:
Based off personal knowledge / opinion, battery heat is likely much more damaging to the battery than an extra 10 15c to the CPU. This may also just have to do with the LG Chem batteries being limited to a lower temperature to achieve those higher numbers of charges before reaching 80% capacity lifetime.

So, in my 2c, I'd say the throttling is more about ensuring some lifetime LG/Google had in mind rather then preventing immediate failure.
[Nexus 4 Original Android Development] leets4uc3:
This
[Nexus 4 Original Android Development] franciscofranco:
Makes total sense! We'll be able to fix that when my N4 comes I'm pretty sure of that!
[Nexus 4 Original Android Development] stormtroopercs:
Sorry to being off topic but when do you get your N4?
[Nexus 4 Original Android Development] Prod1702:
He said he just ordered today and that it should ship in 1-3 weeks
[Nexus 4 Original Android Development] wngmv:
congrats on finally ordered a phone! On the other hands 1-3 weeks, which puts us around Christmas!

(I'm secretly waiting for the color calibration in the kernel, in fact)
[Nexus 4 Original Android Development] droidmakespwn:
Used your app to flash your kernel directly after every ROM flash on my galaxy nexus. Looking forward to the same thing on the n4.
[Nexus 4 Original Android Development] brianbgrp:
Color calibration it looks is in the stock kernel. So may have a way to play with it while you wait as well

Sent from my Nexus 4
[Nexus 4 Original Android Development] wngmv:
Thanks but I in no way know enough to tinker kernel. All I know is how to flash it.:D

I'll wait. I like Nexus's color. I just want all the "Nexus 4 is washed out" people to shut up.
[Nexus 4 Original Android Development] lazer155:
Currently at 55% and after watching a few embedded videos (about 25 minutes) on wired.com, it seems a little excessively hot. I'm not sure how I should measure the exact temperature since the Franco updater app reports temperatures as n/a but based on feel it does seem hotter than usual. I'll post the temperatures if I can find an app to show them.
[Nexus 4 Original Android Development] dzap:
My Nexus 4 has bootlooped twice since updating to r22. msim_hsic_host has definitely gone down in time (it was 3 hours+ at one point..now I'm seeing around 2 minutes or less).

First (and second) time it has ever bootlooped since I got it.

Just changed hispeed_freq and go_hispeed_freq though, so I'll reboot and try another day and see if it bootloops again.
[Nexus 4 Original Android Development] CMNein:
'Normal' for the N4 unfortunately, no matter what the kernel or ROM. Battery reporting is borked...badly.
[Nexus 4 Original Android Development] Simer03:
GTA vice city seems to crash to the home screen after resuming a game! Anyone else??

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] 3thman:
guys I dont care about the battery .. I just want the fastest phone that I can have.. what is the settings to get the fastest performance ???
[Nexus 4 Original Android Development] superbobup:
1500/1500, interactive, deadline
[Nexus 4 Original Android Development] ceejay83:
I guess, if you want a battery that lasts for a hour and is burning hot
[Nexus 4 Original Android Development] wera750:
Or if you want a red flashing led of death
[Nexus 4 Original Android Development] superbobup:
Ha. It was more of a joke :p

In all honesty, Franco's defaults seem good for most. If anything, you can lower the threshold value and increase the hi_speed_freq
[Nexus 4 Original Android Development] lazer155:
I noticed something strange. I can't seem to adjust my volume. I push the buttons and the loudspeaker volume symbol box comes up and it changes but the actual sound level doesn't match what is displayed in that box. For example if I turn the volume all the way down, it still makes sounds when using the navigation bar buttons etc. My volume worked fine before flashing r22. Does anyone else have this issue?
[Nexus 4 Original Android Development] Ballastatuz:
Trying the same settings. Seems pretty smooth.
[Nexus 4 Original Android Development] jjcandroid2012:
That sounds like a ROM issue not kernel.. What Rom you using?
[Nexus 4 Original Android Development] franciscofranco:
I'll have to do some changes to the thermal throttle driver, its taking a little longer than I'd want to to throttle back to reduce heat. This is when it gets interesting finding the sweetspots for every aspect in the device! Keep those interactive tests coming guys, I wanna hear about it.

I merged this: https://github.com/franciscofranco/mako/commit/26d6d69e5d12e0fc217bbcc4bb39700708d9e31a a few hours ago and will possibly fix some weird random reboots very few users have! Thanks to codeaurora of course. Been testing ROW since today's morning and I see no difference compared to Deadline in real world usage.
[Nexus 4 Original Android Development] Vertana:
I'm glad to hear you're working on the thermal throttling issue. Thanks for keeping us informed. No rush, I'm positive you'll find the solution in time.
[Nexus 4 Original Android Development] lazer155:
It's the stock ROM. I haven't flashed any custom ROMs yet.
[Nexus 4 Original Android Development] yokuyuki:
I got a random reboot on r21 and I'd provide a last_kmsg, but looking at the date of it, it's dated Dec 3rd which is odd because I didn't even have my phone then.
[Nexus 4 Original Android Development] 3thman:
I played with the maximum and the minimum CPU frequency ... what are the defaults settings for them? Thanx
[Nexus 4 Original Android Development] resynx:
384 / 1512
[Nexus 4 Original Android Development] republicano:
patch works well, i have been playing with the settings and for the first cycle of r22 its been good, restricted the cpu speed so it wont get hot,

10.34hours

msm_hsic wakelock, 9m 20s (560s) 1.5%,

5 hours screen with 11% remaining.
[Nexus 4 Original Android Development] drawde40599:
Just cause its stock means nothing , i dont c how could b anything but a ROM issue but just reinstall 22 ( try agn ) or just restore your N backup
[Nexus 4 Original Android Development] aimcr7:
Edit.... Damn tapatalk :mad:
[Nexus 4 Original Android Development] DesertVelo:
I hate it when it does that....

Sent from the singletrack...
[Nexus 4 Original Android Development] Overdose1986:
Chrome
[Nexus 4 Original Android Development] :
I found r151 great except in Temple Run 2 it lagged during long runs when you're not touching the screen, r1222 performed great overall but my settings were really aggressive (1188 hispeed_freq and 1350 input_boost)and battery life suffered, barely managed 4hrs SOT with almost 2hrs of Beach Buggy Blitz plus browsing, calls, youtube etc. I have to test r152 some more but my initial impressions are its the best I've used so far (chrome beta and tapatalk 4 almost no lag)
[Nexus 4 Original Android Development] :
I'd just like to report that the UV settings don't stick on boot, or that setting to do that doesn't work. Franco.Kernel Updater v10.0.3,

It was also happening on a couple of previous versions, and I did try reinstalling/wiping app data.

Nice work though, consistently getting 4+ hours SOT and 2 days of battery time with CM10.1!
[Nexus 4 Original Android Development] SneakyGuyDavid:
Hmm , r152 is laggy for me (coming from r151 of course) , especially at boot , but I'm a big dirty flasher so might just be me ...

After opening a few apps and spending a while after a reboot , its almost normal I guess (cache ?), but still , never did that weird lag before

Sent from my Nexus 4
[Nexus 4 Original Android Development] zephiK:
Not just you, read the past couple of pages.
[Nexus 4 Original Android Development] G4neStarT:
Great battery life with #151 will try the new one and let you known guys
[Nexus 4 Original Android Development] xanthrax:
Only once I've had that md5 problem , can't remember which version , since then I'm using the option "download" and then "bring it on" , never happened again plus , I'm having the zips saved into to my phone

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] monkey hung:
r152 is giving me infinite bootloops
[Nexus 4 Original Android Development] Floydfire:
Trying 152 and isn't smooth as 1222, the drop in performance, also a little in ui, is really noticeable

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] Bobtehblob:
I also feel like r151 was smoother than r152. Didn't try test kernels mind you so I can't comment on that.
[Nexus 4 Original Android Development] leets4uc3:
I am on carbon with 152. I drop max freq to 1188 and only some lag in taptalk 4 beta but that is expected. I just browse and stuff, no games and I don't see any other lag.
[Nexus 4 Original Android Development] lordvj:
how can i change the value of go_hispeed_load ? and is it the same as up_threshold in the /cpufreq/interactive directory
[Nexus 4 Original Android Development] Mercado_Negro:
Are you using a color profile? Maybe it's crashing on boot while screen off, which is a known bug. Don't let it turn the screen off on boot and it should be OK.
[Nexus 4 Original Android Development] nachordez:
For me, in stock ROM, absolutely smooth 152 (151 was also).

I also think the lags can be ROM dependent, or something in between, but not purely kernel.

But Franco will say what he sees... :thumbup:

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

gt-p5110 / PAC rom / V4A sound
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks. I did a search but I couldn't find anything about this until I read your post. That answers my question:
[Nexus 4 Original Android Development] Confused_Cheese:
Getting a lot of stutters on 152 that I don't remember 151 having, mainly when scrolling through lists or websites. Even the xda app stutters now too
[Nexus 4 Original Android Development] schizophrenia:
sorry for not having time to search post.

for r152, is it normal to have at least 2 cores always online during screen on, even without any touches or foreground running any apps? it never happened on r151 or before

all franco kernel settings are default.
[Nexus 4 Original Android Development] zagzag99:
With latest Franco Kernel Updater 10.x I only get to this screen without the "Status" title and I can't swipe open the side panel to change to other screens.

Anyone else experiencing this ?

I'm on UKG.
[Nexus 4 Original Android Development] Bobtehblob:
Yes it is.
[Nexus 4 Original Android Development] panart:
http://xdaforums.com/showpost.php?p=42382291&postcount=35866
[Nexus 4 Original Android Development] trailblazerz11:
That's the main improvement 152 made, rather than constantly online/offline core1 it just leaves then both on. 151 did not have a threshold for dual core, it was only on touch so it should help for apps that could use 2 cores but don't need 4.

Odd some people are experiencing more lag from 152. Was a rather aggressive change towards better performance.

Not sure about the overall lag and stutter people have, very smooth UI for me. But for heavier app try lowering the threshold for, games and also chrome seems to run better on quad cores.
[Nexus 4 Original Android Development] :
On r152 I noticed slight stutters here and other especially when opening contacts from my homescreen, but those are negligible really. The best thing is, it keeps my device cooler than r151.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Nocturnal86:
Im stock rooted and moved from r148 to r152 and I dont see any lag either i tried out a game of temple run 2 and no noticeable or interfering lag at all it was and seemed as smooth as it should even when things sped up. I was weary about downloading r152 because of all the reports of lag but decided to give it a go finally and see for myself and so far so good! Not sure why all the reports of lag. Just thought id give my experience so far. Im hoping 152 battery is about on par with 148. Thanks for all your hard work franco!
[Nexus 4 Original Android Development] JamesInsights:
Hi guys i've always known interactive to be the performance oriented governor so I've stayed clear from that on other kernels. Trying franco for once and realised interactive was default. Has franco done his own tweaks to interactive to make it better for battery or is ondemand better for battery?
[Nexus 4 Original Android Development] Luigiesin:
Franco works mostly with interactive governor.

Don't change it.. Leave it like that ;)

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r1222-Linaro

T-Mobile
[Nexus 4 Original Android Development] hwies:
With R152 there were always at least 2 cores online. In some apps i got noticeable (more) stutters. Went back to R1222 where it seems to be better for me (rooted stock version with Nova launcher).
[Nexus 4 Original Android Development] kecinzer:
That's weird. With latest test build (1222 I think) people were ok, and now, with 152 they doesn't. There are no differences.
[Nexus 4 Original Android Development] strainhunter:
Hello.

I just installed fku again after a while and noticed that the option "turn fsync off" us ticked by default? Is this normal? Few months ago it was different. And I turn it off then and after a crash I got all my data corrupted. Don't want to experience that again^^

Gesendet von meinem Nexus⁴ <CarbonROM>+franco.Kernel(faux123 atm)
[Nexus 4 Original Android Development] kara mustafa:
No problem here, no stutters after boot. I think that people have something wrong with theirs setups.
[Nexus 4 Original Android Development] snorfu:
i get about 7-10% hsic wakelock on 3g...franco can you fix this? please.
[Nexus 4 Original Android Development] ludorexmundi:
What's the default scheduler I/O on 152?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] nexusmaniac:
Deadline :)
[Nexus 4 Original Android Development] G4neStarT:
PAY THE DAMN APP ... PLEASE TO SUPPORT FRANCO. Franco said before that is a security measure against hack FU app.

I DONT MEAN TO BE AN ASS BUT WHY COMPLAIN WHEN U HACK THE APP?? COME ON DONT BE THAT GUY!!!

Sorry but i had enough of people that complain about hacking app!
[Nexus 4 Original Android Development] jphilippon:
152 is butter for me. Very satisfied. Weird hearing about lag...
[Nexus 4 Original Android Development] strainhunter:
I think the problem he has comes not from hacking it, it comes from not hacking it. He maybe just installed the app and not bought it from gplay. Or maybe he just did not crack it right ;) (which is even more pathetic ^^)

Gesendet von meinem Nexus⁴ <CarbonROM>+franco.Kernel
[Nexus 4 Original Android Development] z3r0_x:
r1222 isn't equal to r152 - so it's not a placebo that people experience performance issues
[Nexus 4 Original Android Development] G4neStarT:
Hahah lol but i think that must paid app that are download from the net are pre-Hacked or pre-cracked to avoid the licence checker or something :)

the funny thing is that he come here to complain about it :cyclops:
[Nexus 4 Original Android Development] gm.cinalli:
UP!
[Nexus 4 Original Android Development] :
I find r152 better than r1222, with different input boost 1350, it's the best so far, hasn't slowed down and it's sipping battery real slow
[Nexus 4 Original Android Development] z3r0_x:
For me those both setups are equally smooth, but r152 with such a high input boost is really draining my battery :(
[Nexus 4 Original Android Development] djpry:
152 is rock solid and battery usage is great.......great job......:good::good::good::good::good::good::good::good::good::good:
[Nexus 4 Original Android Development] Floydfire:
After some hour goes a little better but I think 1222 was more fluid... Also swipe on Google keyboard are less responsive...

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] Net.silb:
[MENTION=3292224]franciscofranco[/MENTION]

The new touch boost code seems to be missing something...

for_each_online_cpu(cpu)
{
if (cpu < 2)
{
cpufreq_get_policy(&policy, cpu);
__cpufreq_driver_target(&policy, TOUCH_BOOST_FREQ,
CPUFREQ_RELATION_H);
}
}

You aren't making sure the current cpu frequency is lower than the touch_boost_freq and therefore when the current frequency is higher than touch_boost_freq it's being lowered to touch_boost_freq when the user is touching the screen...
[Nexus 4 Original Android Development] Sukhi:
+1
[Nexus 4 Original Android Development] fozzie:
Ticked is not the default.

Clear the app settings and reboot.
[Nexus 4 Original Android Development] kecinzer:
[MENTION=1842024]z3r0_x[/MENTION]

There are no new commit on github since r1222.
[Nexus 4 Original Android Development] Net.silb:
You're wrong. In r1222 only cpu0 was boosted on touch (to 1026 MHz), in r152 cpu0 and cpu1 are being boosted on touch (to 702 MHz).

https://github.com/franciscofranco/mako/commit/a5b8037f987ea6e4fe083e673bed6c6129eafe75
[Nexus 4 Original Android Development] z3r0_x:
Exactly, that's the difference that Franco stated...
[Nexus 4 Original Android Development] manulemaboul:
From what I see and feel, imput boost seems to take a bit too long to kick in, and I think that's why some reports some stutters, which I can also feel.

That's just right when I touch the screen in the first place, once imput boost has kicked in, everything is butter smooth.

It seems to be longer to boost 2 cores than one or something, It kicked in faster with r1222

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] Mixy:
I've been very satisfied with this kernel, and the updater for a long time now :)

Am I the only one who've experienced more wakelocks with the last few nightlies? Ever since about 143 msm_hsic and suspend_backoff have both been pretty high. Have tried wiping data and uninstalling any new apps I've installed.
[Nexus 4 Original Android Development] kara mustafa:
Changing input boost to 1 GHz should make the Phone buutery smooth right? Stock is 702? For what is hispeed freq?

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] schizophrenia:
i want to be more specific so bear with me

any ingress players here?

have you been experiencing some lagginess and big drop of FPS in recent builts?

just checking, not complaining.
[Nexus 4 Original Android Development] .coomb.:
No, I haven't experienced frame drops other than those due to the laggy nature of the game itself. If anything, r151 seems to be the best so far for playing ingress.