yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jaggyjags:
Yes nexus 4 stops charging when battery reaches 45°C. I'm not saying to disable this throttling, but to reduce maybe max cpu/gpu frequency (let's says when reaching 44°C) to avoid it reaching that temperature so it keeps charging all the way.

On my tests cpu temp never reached throttling temperature (gaming). So couldn't avoid the battery from overheating.
[Nexus 4 Original Android Development] drawde40599:
No Its normal, that guy that told u it wasn't is wrong, these last few builds get a lil warm in 3g, thats still a normal temp tho

Edit :Btw mines at 60° c , doing same thing u r
[Nexus 4 Original Android Development] sam razzy:
Guys.. When I was using Gnex, I use to flash Franco kernel but at that time I use to find a setting to make battery extender option where we can make 99% or 100% to save the battery life. But after coming to Nexus 4 and flashing his kernel, I cannot find those option..

Bdw: if I plug my phone into charge till morning, Will it cause any problem to life of my nexus battery ?
[Nexus 4 Original Android Development] franciscofranco:
r145:

* Several custom improvements on Interactive's code to save more battery when there is low load and to boost performance when there is higher load requirements. Code changes are on git

There are 3 new tunables that I created, but I will explain then later or if [MENTION=3614073]Miasmic[/MENTION] is around he can explain them while I'm not here. Thanks to [MENTION=3614073]Miasmic[/MENTION] for testing my crazy **** on his gaming routines, I can say this is a major success :) Also its a continuation of r999 changes, just improved.
[Nexus 4 Original Android Development] jaggyjags:
Nexus 4 charges to a max of 97% AFAIK. Even though it shows 100% when fully charged. This is to extend battery life on a long term (battery is not replaceable, take that in mind.)

I have not seen an option to change this value on any kernel out there or application.
[Nexus 4 Original Android Development] PelegK:
Great .. will try the r145, thanks alot !
[Nexus 4 Original Android Development] resynx:
I'm all over it! r999 was performing great for me so I'm glad to hear it's a continuation of it :)
[Nexus 4 Original Android Development] pikachukaki:
Thanks for the update..i will test it with my own values to see if its better than 142!!
[Nexus 4 Original Android Development] rockafellor:
this is f***n awesome!

I just bought your app bro :d support him

franco = hero
[Nexus 4 Original Android Development] vjales:
Guys, I forget to wipe my dalvik cache after flashing the new version. Should I wipe it, or just leave it as it is now?
[Nexus 4 Original Android Development] ceejay83:
you never have to wipe cache when flashing kernels
[Nexus 4 Original Android Development] huczek12:
My wifi don't work after install r145. On 142 worked great. How I can fix it?
[Nexus 4 Original Android Development] Luigiesin:
Ok.. Just flashed 145.. Franco, cpu0 sill stuck in 1GHz... That's with screen on and without touching anything.... Cleaned the apps data 3 times.

It's not draining battery like it would and the smoothness is unbelievable like this.... But makes me wonder if that's a good idea to keep cpu0 ramped to 1ghz while screen on...

For example while reading usually after waiting about 10 seconds and then scrolling, with past builds it would stutter just a hair... Keeping cpu0 at 1ghz eliminates that completely and so far I can't see any battery draining... Basically same battery draining as r143.

The phone still enters deep sleep while screen off though... It's just when the screen is on it keeps it at 1GHz... If I do anything a little bit more intensive then it fires up the cpu1 to 300mhz.

It's been happening since last night when I flashed 999.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r145

T-Mobile
[Nexus 4 Original Android Development] jarjar124:
Reflash your ROM
[Nexus 4 Original Android Development] pyr0sphere:
New default in r145: noop and westwood?
[Nexus 4 Original Android Development] figuremania:
My app still shows r143 as latest while it'd show r145 changelog when I click to install the latest nighty.

I just went ahead to auto flash but it was giving me md5 error so I directly downloaded it from FTP.

So far so good...
[Nexus 4 Original Android Development] ceejay83:
You probably got a background app doing something. I'm sitting lovely at 384mhz with screen on/doing nothing

---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------

Yes, all you need to do is wipe app data and reboot for defaults
[Nexus 4 Original Android Development] thegtfusion:
Will you include these patches in your gnex kernel also?
[Nexus 4 Original Android Development] yethz:
Screen-On just sits on 384....

Thats #145

• Sent from Nexus 4 via Tapatalk

• Rom: AXI0M / Kernel: Franco #999
[Nexus 4 Original Android Development] Luigiesin:
Nope... No apps in the background... Everything the way I had it in 143..

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r143

T-Mobile
[Nexus 4 Original Android Development] huczek12:
On r142 I've got 20000+ in antutu, now I've got 14738...
[Nexus 4 Original Android Development] pikachukaki:
RMA your phone...its hardware fault for sure!!! Get serious!
[Nexus 4 Original Android Development] thebryceee:
Benchmarks = pissing contest
[Nexus 4 Original Android Development] ciprianruse88:
r145 is a masterpiece.stock interactive hispeed_freq is at 702 now and the device is freaking smooth.I expect great battery results with this new stock freq for hispeed_freq ! Thank you Franco ! :thumbup:
[Nexus 4 Original Android Development] franciscofranco:
Maybe. Now I'll concentrate on the app, then on GN and then N7 ;)
[Nexus 4 Original Android Development] xanthrax:
Same here, 110 mA drainage on wifi and 250 on 3g when on Tapatalk, half than v143

Sounds Damn good and touch control works also

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] konfuzed:
if Max CPU freq is set at 1026mhz it won't scale back down to the cpu min(384mhz). anyone have this problem with r145? if I raise Max to anything higher than 1026mhz it scale back to my min
[Nexus 4 Original Android Development] thegtfusion:
You are the boss! :D I can't wait till you concentrate on gnex :D :D
[Nexus 4 Original Android Development] ciprianruse88:
Yep.tested with perfmom.if max cpu freq is set to 1026 it will get stuck at that freq
[Nexus 4 Original Android Development] rxmxsh:
Jesus. Are you as active in those thread as you are here? That has to be time consuming.
[Nexus 4 Original Android Development] Luigiesin:
Same here...

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r143

T-Mobile
[Nexus 4 Original Android Development] Haomuch:
Got a very excessive msm and suspend wakelock last night with r143.
[Nexus 4 Original Android Development] pikachukaki:
Give the kernel and the phone time to adapt..don't come out with conclusions 1hour after you flashed the kernel!!
[Nexus 4 Original Android Development] Luigiesin:
The only way is to keep it at 1.3 or higher... I usually have my max freq at 1.1

If I keep it like that, cpu0 won't scale down to min freq... I think it's a bug.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r143

T-Mobile

---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------

It's being happening since 999...

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r145

T-Mobile

---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------

It's being happening since 999...

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r145

T-Mobile

---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------

It's being happening since 999...

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r145

T-Mobile
[Nexus 4 Original Android Development] republitarian:
I was waiting for someone else with this problem. I'm not sure where its coming from but I did solve this problem by using greenify and setting f.ku app to manually update rather than search for updates.
[Nexus 4 Original Android Development] pikachukaki:
Ok then you have problem! :P
[Nexus 4 Original Android Development] vjales:
I think you have some bug on your rom, or some app, because mine oscilates from 384-7xx not so frequently. I think it's the way to be. R145 + cm 10.1 rc3 here.

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] figuremania:
145 seemed ok at the beginning but sometime after cpu0 got stuck at 1512 and made phone somewhat hot... I went back to 143 for time being.

Oh and my app still shows 143 as latest although I cleaned data several time. Should I uninstall fku and reinstall?
[Nexus 4 Original Android Development] franciscofranco:
Ok so there are 3 new tunables are:

go_hispeed_load_low

go_hispeed_load_high

These two work together. They define the load range (defaults are low=50, high=75) where the next new frequency will be hispeed_freq (if the current frequency is lower than hispeed_freq on that sample). Lower those values and the device will hit hispeed_freq more often. Make them higher and it will be more conservative.

go_hispeed_load_high

up_threshold

This two are also important (go_hispeed_high is tied to two checks). After the initial checks above there is one more check to make sure to cover high load cases. If there are 3 or more cores online and if the load is equal or greater than go_hispeed_load_high the next frequency will be max. If the number of online cores is 2 or less and if the load is greater than 90 (up_threshold) the next freq will be max.

Its a bit hard to understand at first and hard to explain clearly, so if you don't know know what I meant just stick to the defaults.

EDIT: I haven't had any "stuck" to max freq, but a bit more info could help like whats the min/max freqs set. Something might've slipped unnoticed.
[Nexus 4 Original Android Development] pikachukaki:
Where are those so we can edit them??
[Nexus 4 Original Android Development] mundixx:
I miss the LG presets though! But damn this kernel flies!!
[Nexus 4 Original Android Development] Luigiesin:
Try clearing Dalvik and Cache.... Reinstall kernel again... Clean Dalvik and Cache...

Reboot router after disconnecting it for 20 seconds.... Report back
[Nexus 4 Original Android Development] franciscofranco:
So I've been testing the msm_hsic wakelock bug fix from qualcomm in the last 6 hours and I have roughly 11s spent on that wakelock, which is normal and expected. I might drop r22 in a little containing only that fix as a change.
[Nexus 4 Original Android Development] Monkeybrew:
I'm an artist, so I'm quite picky with colors.

Tried matching colors to my calibrated eizo s-pva screen.

My settings :

223

204

195
[Nexus 4 Original Android Development] superleeds27:
Anyone uding this with slimbean? just wondered about battery life.

I know slimbean n franco kernel on the nexus 7 is good, just wondered about the n4
[Nexus 4 Original Android Development] c_86:
Cannot wait! Thx man! Love your kernels!
[Nexus 4 Original Android Development] noneabove:
Wait what?? Qualcomm fixed it and insanely well?! That's amazing! Thanks Franco!! In 6 hours i normally get at least an hour of msm wakelock!
[Nexus 4 Original Android Development] franciscofranco:
Seems to be fixed on my device at least thanks to their work :)
[Nexus 4 Original Android Development] evostevo1:
Meh........ You would have fixed it.
[Nexus 4 Original Android Development] javacody:
Can't wait for 22 Mr. Franco!
[Nexus 4 Original Android Development] franciscofranco:
Probably not. Its not very easy to come by and debug a driver like that without any prior knowledge of how all that driver works.
[Nexus 4 Original Android Development] evostevo1:
True.
[Nexus 4 Original Android Development] franciscofranco:
Get r22, only patch is the msm_hsic_wakelock fix from Qualcomm.
[Nexus 4 Original Android Development] noneabove:
Is the 22 up in app the good new one ? :) just wanna check since you didn't have a chance to update change log yet XD

Nvm there's the changes :)
[Nexus 4 Original Android Development] digitalfrost:
I like the smell of fresh kernels in the morning :D
[Nexus 4 Original Android Development] Luigiesin:
Just flashed it! Let's test this baby!

Thanks Franco :cool:

Lu
[Nexus 4 Original Android Development] evostevo1:
I like poppin me some fresh r22 kernels.
[Nexus 4 Original Android Development] Luigiesin:
Franco... Quick question... I'm using your app to update and flash your kernels.... When I flash a new revision, does it do the kernel reset before flashing?

I guess what I'm saying is that coming from the HTC sensation, flashing kernels one after the other one, it used to create problems in the system after so many kernel installs... My phone is working amazing right now and although I nandroid every time, just want to confirm there's no problem with flashing kernels consecutively.

Thanks! Love your work!

Lu
[Nexus 4 Original Android Development] franciscofranco:
There is 0 problems, its flash and go - I wouldn't make an app feature to auto-flash etc if it wasn't safe ;)
[Nexus 4 Original Android Development] Haomuch:
My governor also revert back to dynamic scaling after reboot even set on reboot is ticked.
[Nexus 4 Original Android Development] franciscofranco:
Governor files... /sys/devices/system/cpu/cpufreq/interactive something like that.
[Nexus 4 Original Android Development] figuremania:
I didn't change any setting. So it was on default. 384/1512.

Maybe the issue could be rom related since Luigiesin and I both use PA it seems....
[Nexus 4 Original Android Development] pikachukaki:
You kill me...im not so good with code....i thought they will show on your app!! :)

But with my values for hotplug and interactive im getting a crazy battery life and smoothness!!
[Nexus 4 Original Android Development] ciprianruse88:
[MENTION=3292224]franciscofranco[/MENTION]

Stock kernel settings. Just insert max cpu freq 1026 and it gets stuck at that freq. After inserting again 1.5 ghz max cpu freq the cpu works without a problem.
[Nexus 4 Original Android Development] jack1984:
I noticed the scheduler default is noop now.

Sent from my Nexus 4
[Nexus 4 Original Android Development] PetritH:
Was going to ask this too... nice got my answer.
[Nexus 4 Original Android Development] Luigiesin:
I don't think it's PA related though... 140-143 was fine... Setting max freq to 1.3 instead of 1.1 fixed it.... But I still would love to downclock to 1.1 if possible.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r143

T-Mobile
[Nexus 4 Original Android Development] ciprianruse88:
It's not Pa issue. I am not on Pa :). Eighter way I don't use 1026 freq as my max cpu freq.I like 1.5 ghz and so I will have no problem :)
[Nexus 4 Original Android Development] nexusmaniac:
Yay more updates to grouper :)
[Nexus 4 Original Android Development] figuremania:
Yes I realize that it can not be rom related, and I hope so since I've been liking PA quite lot. And I like 1.5 too :D. I just didn't like it stuck at 1.5.
[Nexus 4 Original Android Development] Atari-:
I rarely post but... I just wanted to say that this is the first time the phone doesn't fry eggs when playing a graphic intensive game (r145)... I love you...? Oh and I was testing out Eternity Warriors 2, before it would freeze when zombies would spawn from the ground... Not anymore!
[Nexus 4 Original Android Development] ansontyl96:
When I wake the device, it will lag for a few second when I use it, anyone can confirm this?on r143now
[Nexus 4 Original Android Development] zephiK:
No problems when I used r143... r145 is out by the way ;)
[Nexus 4 Original Android Development] Haomuch:
How come the high speed frequency 702mhz is even lower than the input boost frequency 1188mhz?
[Nexus 4 Original Android Development] trillo69:
Same happened to me on 143, but I really didn't care...
[Nexus 4 Original Android Development] pikachukaki:
Did anyone ever notice a guide or something like that so we can "translate" color profiles from other kernel application to franco?thanks!
[Nexus 4 Original Android Development] dumber89:
read the changelog and the new update is what I really wait for. thumbs up, Franco. Thanks much! :fingers-crossed: :good::good:
[Nexus 4 Original Android Development] nyyankees1237:
Frequency is idling at 1.5ghz without even touching the device on r145. Rebooting temporarily fixed the problem but soon after it came back.
[Nexus 4 Original Android Development] drawde40599:
Not seeing that with stock settings and aokp, did u change something?
[Nexus 4 Original Android Development] dapsANDpoundz:
r142 has been so good for me I'm scared to try anything else haha but I'll give r145 a whirl because it looks substantial enough to merit a quick flash. Keep up the good work.
[Nexus 4 Original Android Development] bleuwave:
Wow...the scrolling is just so smooth in r145...

Gotta check out other aspects too though like heat etc...

Well done so far.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ki2luminati:
Is noop default sheduler in r145? Thanks
[Nexus 4 Original Android Development] sNoxious:
Yes.
[Nexus 4 Original Android Development] zephiK:
yes

10char
[Nexus 4 Original Android Development] nyyankees1237:
Turned off logger and undervolted by 75. Nothing major, I'm on carbon ROM.
[Nexus 4 Original Android Development] thebryceee:
Idles at 384 on Liquid Smooth
[Nexus 4 Original Android Development] Luigiesin:
We're like 4 people having the same issues with stock settings BTW.

I'm sure Franco will find the issue... He always does ;)

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r145

T-Mobile
[Nexus 4 Original Android Development] kaiser_tytnii:
Same observation
[Nexus 4 Original Android Development] manulemaboul:
Noop's the new default because of recently posted IO bench results I guess :).

I like 145, it makes tapatalk 4 beta launching noticeably faster :thumbup:

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] nuwan32:
hmmm with r145 i also got idle at 1188 mhz (thats my max cpu) for some reason. cpu spy only shows times for 1188 and deep sleep because thats all it used. i didnt change any settings in the app flashing from r143 --> r145. i even reset the app settings and still the problem persisted. now i flashed back to r143 and it is working perfectly again. hope this can help fix the problem franco.
[Nexus 4 Original Android Development] cassius_20:
Just flashed r145 and left it for 15 minds before playing around with it. Not seeing the idle at 1.5 on this end. Perhaps for those that do, and if you have system monitor, record it for a few minutes and see of Franco needs a log of it?
[Nexus 4 Original Android Development] Savant:
No problem like that I wonder why everyone is having with this kernel.
[Nexus 4 Original Android Development] thebryceee:
So, is it just people on PA that is experiencing this stuck frequency issues?
[Nexus 4 Original Android Development] nuwan32:
i think some people mentioned it only happens to people with PA, and im running PA so this may be why. for those that dont have this problem, are you guys on another rom?
[Nexus 4 Original Android Development] thebryceee:
No idling problem on Liquid Smooth
[Nexus 4 Original Android Development] fakudolan:
a little off-topic but can you share what font you're using please? thanks!
[Nexus 4 Original Android Development] Bobtehblob:
Beta app isn't pushing kernel update notifications.
[Nexus 4 Original Android Development] sNoxious:
It's called 'Sony Sketch'.
[Nexus 4 Original Android Development] kaiser_tytnii:
I am on AOKP but still having issue, back to r143 for now
[Nexus 4 Original Android Development] bleuwave:
Idles at 384 on SlimBean ROM.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ceejay83:
It gets stuck if you underclock
[Nexus 4 Original Android Development] PetritH:
Not experiencing this, running latest alpha build
[Nexus 4 Original Android Development] username8611:
Using trickster mod, I really can't change but 1 or 2 settings for the interactive governor... none of them stick, is this intentional?

Edit: Using M2
[Nexus 4 Original Android Development] franciscofranco:
At this point I don't really know why some users are having their devices stuck with max freq. I'll try to find out.

I think I found the cause, more news soon.
[Nexus 4 Original Android Development] Luigiesin:
Franco... Underclocking to 1.3 fixed my issue.. So it isn't just Underclocking.. It's with certain frequencies.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r145

T-Mobile
[Nexus 4 Original Android Development] Arstoien:
It seems if the max frequency is equal or lower than input_boost_freq, then after a few interactions with he screen cpu0 gets stuck on the max freq. I tested with lowering input_boost_freq to 702, and underclocking to 1026, and it works fine. If input_boost_freq is 1026 or higher, cpu0 would stick to 1026.

The default input_boost_freq Is 1188 (one step below 1350), that's why underclocking to anything higher than 1188 is working fine.
[Nexus 4 Original Android Development] Luigiesin:
I just tried lowering the max freq to 1.1 and the input boost freq to 1GHz... Still got stuck though.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r145

T-Mobile
[Nexus 4 Original Android Development] vaibkulk:
Its only for 1.1 GHz. Same here stucks at max freq 1.1Ghz on idle

Sent from my Nexus 4
[Nexus 4 Original Android Development] Arstoien:
True, confirming. So it's not as simple as I thought.
[Nexus 4 Original Android Development] ticiano_arraes:
CPU was behaving weirdly with interactive governor. All four cores online and frequencies going from 384 to 1512 constantly. Changed to conservative and everything is ok
[Nexus 4 Original Android Development] franciscofranco:
Not really. I've been testing this code for the last 3/4 days, never saw such behaviour, sorry.
[Nexus 4 Original Android Development] enkode:
I don't think the nightly supports the newest cyanogen display feature of being able to adjust the priority of brightness responsiveness. I could be wrong...
[Nexus 4 Original Android Development] 3dupunk:
Honestly, I flashed 145 and I am amazed.....I didn't think this kernel could get significantly better...I was wrong. :thumbup:.
[Nexus 4 Original Android Development] ÜBER™:
Dynamic tunable seem to be running much better than previous iterations. Might be useable now. So far so good on r145.
[Nexus 4 Original Android Development] franciscofranco:
Problem solved :) In the process I managed to optimise some ****s as well. New build in a few minutes.
[Nexus 4 Original Android Development] osm0sis:
Just updated the f.Ku Emergency Reset Zip to support A LOT of other kernel control apps, also userinit.d scripts. :D

Details and download: http://xdaforums.com/showpost.php?p=35648172&postcount=35726 :good:
[Nexus 4 Original Android Development] franciscofranco:
r146:

* Fix a bug that appeared on r145

* interactive: Optimised more code and removed some useless code

Also increased first_level threshold to 90, I don't feel the need for 80 at this point. Feel free to change though.
[Nexus 4 Original Android Development] sspyed:
Now THAT'S a good dev ;)
[Nexus 4 Original Android Development] zephiK:
Quick responsive fix to the problem. :) flashing r146 now
[Nexus 4 Original Android Development] nuwan32:
will give this a go, and report back. thanks franco for the quick fix!
[Nexus 4 Original Android Development] Luigiesin:
It works like a charm.. No more frequency bug... Thanks man!

Also moves pretty fast with hi load 90!

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r146

T-Mobile
[Nexus 4 Original Android Development] tanwg:
I was also getting a lot of signal drops when I was on cm 10.1 RC 3, Franco r143. I updated to cm 10.1 RC 4 and Franco r145 and the signal is OK again...
[Nexus 4 Original Android Development] int abacus:
that's a quick turn around... you must love to program... good stuff though!