yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] strikelight:
Correct, but the logic is as such: If the conditions of high load keep getting met, the lower timer rate along with all cpus online is going to have double impact on battery.. So if after maybe say 10 checks in a row where highload conditions are met, it might be wise for the routines to assume the user is going to be at high load capacity for a while, and up the timer to 30000 again, to save a little bit of battery while in performance mode, no? Also, it may help keep some micro stutters from happening to boot..

The battery savings from limiting the timer code from executing so often while in performance mode may be minimal, but maybe every optimization helps..
[Nexus 4 Original Android Development] pkelly517:
That's fine. I always have the kernel I want available for flash on the phone. Three more screen touches that I have to do with jrummy's ROM Tolbox. I thought I might just avoid a step, and stop spending 30 minutes compiling faux's kernel, which I don't use.
[Nexus 4 Original Android Development] nymerc21:
I barely ever post anything , but I have to say r125 is giving me phenomenal battery life ,10 hrs of normal use and still on 63% awesome
[Nexus 4 Original Android Development] hosmsdos:
Huge improvements in games and UI is smooth nicely done. I was waiting for something like this Franco. R125 is truly remarkable. Good Job man.
[Nexus 4 Original Android Development] Banished Angel:
Franco, would you consider moving the download path of the kernel to the franco.kernel_updater folder just for the sake of consistency?

Ex. I want to find something related to fanco kernel so i'll just open the franco.kernel_updater folder.
[Nexus 4 Original Android Development] dapsANDpoundz:
Don't know if its just me or has been mentioned before, but the app takes longer than usual to download new versions of the kernel than it previously did. Downloading via my WiFi same as always. Would take a few seconds before.. now maybe a minute or 2. Nothing to lose sleep over though.
[Nexus 4 Original Android Development] franciscofranco:
Oh its for your own use. Then you're fine :)

Sure, I can make that the default.
[Nexus 4 Original Android Development] franciscofranco:
Maybe the server is being hammered? Could happen.
[Nexus 4 Original Android Development] pkelly517:
Just to make sure...

If I build automagically from your Github, then the compiled kernel is fine for personal use, and would be the same a download.zip from the app?

I'll just be changing a file for building that changes from faux enhanced_stock to franco nightlies.

And, really, just because I say that's what I want to happen has absolutely no correlation to what actually happens. I give it a 10% chance of working the first time, with an increasing probability, based on the number of failures :)
[Nexus 4 Original Android Development] Cuzz1369:
Everyone wants your new kernel. Good job by the way. Watched the thread unfold last night/this morning and was astonished at how fast everything went. Your the man.
[Nexus 4 Original Android Development] Arstoien:
But the timer is not only used to on/offline cores but also to scale the frequency. So if it's higher value, the CPU will be slower to respond to higher load with ramping up the frequency, which causes the games to stutter.
[Nexus 4 Original Android Development] franciscofranco:
The kernel will be same, but the ramdisk that comes from my compiled boot.img will be obviously different from stock.
[Nexus 4 Original Android Development] strikelight:
Right, but at high performance mode, the frequency should already be topped out, so no scaling changes when the conditions remain the same.
[Nexus 4 Original Android Development] santeana:
Hey Franco? Speaking of ramdisk, I read in several other kernel threads that if one wants to switch to another kernel and are coming from Francokernel then they have to first flash the cleaner kernel because you use a different ramdisk than others. What is different about it and why do you prefer that? Why don't others use it in their kennels? I've always been curious but didn't want to get flamed lol
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Right. I've gone a whole night with 0% loss last week and drove to work only to see it drop 6% during the 1 hour commute. Yes there's flaws in that test, but do I really believe 0% on 3G with Latitude, Google Now, and a bunch of stuff syncing?

The battery meter isn't very accurate, especially over small intervals. Thus, if people are doing battery testing, it's best to do it over a long range of percentages, like running the phone from full to dead.

I think some phones definitely distort the 100% mark, especially my iPhone 5. I noticed this on my iPod Touch and 3GS too, but it hovers at 100% for a while before finally dropping. I haven't noticed this as much on the Nexus 4 until last weekend. But either way, we should take 1% over x hours with a grain of salt sometimes.
[Nexus 4 Original Android Development] mihkohuy:
125 make my Nexus 4's battery life back to the 2-cores Galaxy Nexus day, Great!
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
The proponents of letting the kernel settle are saying that it takes several reboots I thought. Mediascanner doesn't really have anything to do with kernel flashes does it? You could invoke it without a kernel flash.

And seriously, why the low blow?

Yeah, this is what I'm thinking too. There should be a theoretical reasons why these things happen. I agree with you that we shouldn't just do things because people are in the habit of, or because many people have said. Regarding the whole full wipe, etc, many developers use that as a form of caution. If you can force someone to do a full wipe, then it gets rid of the chances of dirty crap left over. Thus when people complain of FCs or reboots, as a developer, you can at least rule out left-over data from previous flashes. It's a way of easing debugging as well as making sure they're not at fault for a user messing up. But I think people should understand when full wipes aren't necessary all the time for certain installs/patches/flashes. It's all situation dependent.
[Nexus 4 Original Android Development] Arstoien:
No, that's not how it works. If it was, we'd hit the thermal throttle threshold in no time. Use System Monitor or Perfmon in a game that uses 4 cores and check it yourself. The frequencies vary, they're not locked at max.
[Nexus 4 Original Android Development] franciscofranco:
Because when using a custom ramdisk you got some more power and flexibility, which I use and abuse. And because it works best in conjunction with my app.

Freqs will still scale up and down during high load, they won't be always at the maximum freq, but if the tunables are scaled for performance it will go up much faster and will retain max freq much longer.
[Nexus 4 Original Android Development] Hanny:
yup, some of my tests before show that timer_rate has a significant impact on gaming performance (avg. fps). if it goes back up, the fps go back down thats it. the frequencies would never lock at top in "performance mode" of the governor but just be much more responsive (the demand of game also vary every millisecond). if it locks at 1512 as you've expected its not perfect because your phone will hit thermal throttle threshold in a few minutes or so, hence performance reduction.
[Nexus 4 Original Android Development] franciscofranco:
Thats correct!
[Nexus 4 Original Android Development] yokuyuki:
Including boot in measuring battery life is just a bad idea and because of that which is why I always flash a new kernel and then charge to full overnight and check battery performance the next day. If the rationale is because of boot apps though, then one charge cycle should be sufficient and not the 2-4 that people are recommending. Also just saying "wait for the kernel to settle" implies that the kernel is doing something.

Also media scanner is probably a bad example as that thing runs whenever there are changes on your storage :p

What was the default before this was implemented?

Oh, one full wipe makes sense after flashing a ROM, but there've been times when devs are recommending multiple wipes and at that point, it's like :confused:
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
From my understanding, NAND doesn't work like magnetic drives in the sense that you can't recover data in the same way, but it's not like wipes fully writes over NAND either so haha I can't even figure out the motivation behind that.

The best I can think of is to make sure that the dumb users have definitely wiped and didn't hit the wrong wipe. Once again, a limited liability issue. But, yes I encourage users to do some critical thinking on their own and not simply obey instructions without understanding what's going on.
[Nexus 4 Original Android Development] Eddy130306:
Thank you for your work Franco.
[Nexus 4 Original Android Development] Tarun95:
Don't know if its only me but I notice that when I listen to music through play music media scanner ****s battery on this kernel but doesn't do so on stock.
[Nexus 4 Original Android Development] franciscofranco:
30k

Media Scanner is a rom binary and rom operation, has nothing to do with the kernel.
[Nexus 4 Original Android Development] spicediablo:
Sorry if this is not related to kernel. I notice my screen timeout during call even when I'm using loud speaker. How can I disable this? I would like to black the screen only if I put it near my ears (use proximity sensor)

Sent from Mako⁴
[Nexus 4 Original Android Development] yethz:
WTF!! These kind of posts keeps popping up every page on this thread, which is not francos fault..

Hey, have u read the thread or u just post and leave without reading...

°[ Proud user of LG-E960 (Google Nexus 4) ]°
[Nexus 4 Original Android Development] beenja:
first of all, thanks for franco about this kernel. Got my N4 yesterday and have some questions

I just have a question, i have 122 kernel with PARANOIDANDROID 3.15

if i want to update the kernel for 125, i don`t need to reinstall the rom?

and if i update the rom, my data will be lost?
[Nexus 4 Original Android Development] spicediablo:
Perhaps franco can include this answer in q&a. Just my 2 cents. :)

Sent from Mako⁴
[Nexus 4 Original Android Development] strikelight:
My apologies, makes sense that there would still be scaling at high loads..no maas. ;)

timer rate decreasing causing higher frames and timer rate increasing causing lower frame rates seems counter intuitive though.. Perhaps because when the timer was increased, the frequencies were scaled lower, and when the timer decreased the frequencies were scaled higher.. Not sure if you were making a direct correlation between timer and fps, but the correlation of fps and timer rate might not be accurate, but rather fps and frequency... If that's the case, there may be still some wiggle room to alter timer frequency as I suggested earlier, but instead of switching between the 2 values, perhaps a third intermediate rate, as was hinted at by someone else earlier.
[Nexus 4 Original Android Development] Redneck Trash:
Try this

http://xdaforums.com/showthread.php?t=2050252
[Nexus 4 Original Android Development] Eaffon:
r125 is amazing. Butter smooth, and the battery life is great. I have 3 hours SOT and still have 45% battery. Thanks so much for this kernel!
[Nexus 4 Original Android Development] carhustler:
Thanks Franco I've been very pleased with my phone lately. And to think i really didn't like it when i first got it cause of the blown out colors and crap battery life

C. M. R122
[Nexus 4 Original Android Development] IAmReflex:
Quick question, if I had a reboot due to a kernel panic should I post a last_kmsg? I was able to grab one I just didn't know if it would be useful to post it.

Sent from my Nexus 4
[Nexus 4 Original Android Development] spicediablo:
Bump, anybody can advice?

Sent from Mako⁴
[Nexus 4 Original Android Development] Shano56:
Yep! As long as you don't undervolt. As many times undervolting is the cause of the reboot
[Nexus 4 Original Android Development] casonswag:
Battery seems better on 125:)

NEXUS⁴
[Nexus 4 Original Android Development] deani77:
Lucky me... Undervolt to 725mhz and so far rocking stable...
[Nexus 4 Original Android Development] IAmReflex:
Ahhh I see, never mind then I'm pretty sure I undervolted -25 across board at one point or another but either way thank you for that info so I know in advance next time :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] resynx:
Whenever my speaker sounds for the first time (like a new notification for example), it's always extremely loud at first. But after the first initial loud sound it will go back to it's normal volume. Is this happening to anyone else? It happens every time sounds go off.
[Nexus 4 Original Android Development] Luigiesin:
Just flash the new kernel... But before that clean Franco app Data.

Sent from my Nexus 7 \m/

ROM: PA 3.15

Kernel: Franco r58
[Nexus 4 Original Android Development] drawde40599:
Its Not kernel related , ask your rom dev but it works fine with AOKP no black screen......
[Nexus 4 Original Android Development] spicediablo:
Ok thanks , I'm on stock btw

Sent from Mako⁴
[Nexus 4 Original Android Development] ngkongArm:
Yup, battery life and performance improves much on r125. But unlucky me, the signal and mobile data not stable here. So, it keeps drain my battery. :D
[Nexus 4 Original Android Development] Koraboros:
Not sure about battery yet but some things seemed sluggish... Like opening up twitter, the device took like a whole second. And when I tried to unlock the screen there was 2 seconds of blank screen before it lockscreen came up.
[Nexus 4 Original Android Development] drawde40599:
Ya i dunno, it works like u want with aokp and 125 i dont no if its been coded that way in rom or if stock should do that also. But either way i dont see how could b kernel :)
[Nexus 4 Original Android Development] ceejay83:
you have Franco's app? Clear app data and reboot
[Nexus 4 Original Android Development] gvdprasad:
can you add powersave gernal ?

thank you
[Nexus 4 Original Android Development] yokuyuki:
In that case, I'm confused how this change will improve battery for low loads if it's the same as before.
[Nexus 4 Original Android Development] Koraboros:
Don't have franco's app, sorry.
[Nexus 4 Original Android Development] kojaraty:
Why Google did not hire you until now Franco? :D

I love my Nexus 4 more now thanks to you.
[Nexus 4 Original Android Development] franciscofranco:
I decreased min_sample_time from 45k to 20k so that it stays less time in higher freqs and I increased above_hispeed_delay so that it doesn't go over hispeed_freq if hispeed_freq is lower than the max. min_sample_time makes a lot of difference.
[Nexus 4 Original Android Development] GerhardKi:
so far r125 is running very smooth for me, no hiccups, even scrolling in typically laggy apps has improved a lot, don't know about battery life yet

thanks Franco
[Nexus 4 Original Android Development] pitjago74:
Franco,the M1 its Butter,Butter,Butter:D:D:D

M2 soon or with M1 ist suficiente??? Thanks crack

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] blueren:
R125 is uber smooth! Just one rant.. noticing that the gallery animations have micro stutters. And by gallery animations, I mean opening/closing images. The scrolling/swiping is however super smooth as always!
[Nexus 4 Original Android Development] Eric-1987:
Since when does he work for Google?
[Nexus 4 Original Android Development] noneabove:
Milestones are just renamed nightlies, so if you're just worried about instability, wait a few days for reports and then just flash the newest nightly if everythings good with it, which, francoly(see what i did there?), it usually is haha
[Nexus 4 Original Android Development] DrunkFuX666:
I think what he meant to say was...

"why hasn't Google hired you yet"

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Adnan008:
hi franco, do you thinking about adding gpu oc 487mhz? cuz im using matr1x kernel just because of that... :(

and is there built-in thermal throttle in your kernel? i dont want to my phone throttle, i just delete thermald.conf and everything is fine

thank you.
[Nexus 4 Original Android Development] franciscofranco:
No GPU overclock, its pointless here... no wonder you're having thermal issues.

Of course there is thermal throttle, but I have mostly re-written the driver and it works as it should. You can also change the threshold value to meet your usage.
[Nexus 4 Original Android Development] AndroidKills:
Just wanted to say, First time flashing and just bought your app.

Stoked to try this kernel out!
[Nexus 4 Original Android Development] amarb70:
Hey world, im kind of new to this kernel, I am currently using r111 as it has best battery/performance levels so far. Yesterday I tried the latest r125 and my phone was quite hot, measuring at 65'C. The phone was doing some simple multitasks, listening to music, on the web etc. Is it normal for it to be this hot? If so, how could I set the levels in the app etc. Oh and I'm on carbon 17/4 nightly :o

Just wanted to add, this is a great kernel and I wanted to say thank you Franco! :)

..sent from space
[Nexus 4 Original Android Development] Beremus:
Same here!
[Nexus 4 Original Android Development] Adnan008:
okay it may seem to you that is pointless but i just want my phone more powerful than htc one, because htc one's gpu also overclocked,

cant i just decompile your kernel add oc and compile again?

im just saying, if you add oc, you can pull users from other kernels users

(my english is bad but im thinking i wrote my problem understandable)

but overall, your work is great, i appreciate it, you are nexus 4's gokhan moral :laugh: (when i was using galaxy s3, his kernel was best)
[Nexus 4 Original Android Development] franciscofranco:
I don't really care about being powerful or less powerful than the HTC One, nor is my desire to pull users from others kernels, each one uses what they like the most.

You can grab my sources and add the GPU overclock that you want.

Thanks for the compliments :good:
[Nexus 4 Original Android Development] roi14:
like you would give a damn bout losing users. XD

you have a good reputation and don't mind me if i say this on your behalf,,,

IT'S THEIR LOSS.... haha

by the way, actually quite happy with the upgrade from 122, i immediately noticed the increase in "snappiness", thanks again franco! getting really nostalgic when i remembered your glory days on our little optimus one... rock!!!:victory:
[Nexus 4 Original Android Development] steviewevie:
Undervolting typically causes a pure reboot though, not a kernel panic. So I would still suggest to the guy that he still posts his last_kmsg.

Sent from my Nexus 4
[Nexus 4 Original Android Development] naishadh:
Hi friends I am new to Franco .yesterday I flash Franco on pa3+(16/4 build).and I get worst battery life in every 10 min 5 % battery lost I do full wipe and clear battery status but I don't get any good result.pl help me.
[Nexus 4 Original Android Development] Martin_Ro:
I think, PA has also implemented the CM "wifi fix". And that fix brings a higher batterydrain for kernels without the support of that fix.

And before somebody ask's again:

Franco has implemented that fix in his kernel in the past but reverted it and will now wait for an official google update to the kernel :p

By the way:

Minco v7 comes with R125 and really is übersmooth ;)
[Nexus 4 Original Android Development] italia0101:
I'm on the latest pa with Franco r125. Battery life has been great
[Nexus 4 Original Android Development] drawde40599:
I HAD same issue with heat coming from 111 to newer versions, i did everything i could possibly think of to fix it and nothing worked till i did FULL wipe, sometimes **** gets "gummed" up and wiped is only way out. Backup your phone and try it, should solve your issue, cause at this point your only one with heat issue
[Nexus 4 Original Android Development] bokagavrilov:
yes its nice I'm on stock settings and atm I'm on 60% with 1h and 50 of screen on ;)
[Nexus 4 Original Android Development] Luigiesin:
I had the same issue... You have to flash Franco on top of PA and the fix is gone.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.1 (Mar28)

Kernel: Franco r125

T-Mobile
[Nexus 4 Original Android Development] brian88:
I dont know anything's wrong here but my default hotplug value is

High load threshold: 90

Medium load threshold: 25

Low load threshold: 55

I think it's so weird. So I changed these to

High load threshold: 90

Medium load threshold: 50

Low load threshold: 30

I did it right, guys?

Sent from my Nexus 4
[Nexus 4 Original Android Development] wathefak:
Default high-medium-low: 90-25-50
[Nexus 4 Original Android Development] Curtis7990:
I have the same configuration, no problem. Battery drain is even improved! Especially in idle and in low work for the CPU.
[Nexus 4 Original Android Development] spicediablo:
This is my battery life on r125 and stock ROM

Sent from Mako⁴
[Nexus 4 Original Android Development] steviewevie:
I know it looks odd at first glance, but 90/25/50 is what I have for my defaults. It's intentional, it's not a mistake. Franco confirmed and explained it some time back.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Cantacid:
Its like my phones on speed! Damn lasts real long since franco hit it!
[Nexus 4 Original Android Development] brian88:
Yeah, I dont understand much

But I'll change back value like default setting. Maybe I miss something in a few page ago :confused:

Sent from my Nexus 4
[Nexus 4 Original Android Development] C0qRouge:
[MENTION=3292224]franciscofranco[/MENTION]

Could u take a look into this and give us a reply what u think about that, would be really appreciated!!!

http://xdaforums.com/showthread.php?t=2181820

Since the dev is seeking kernel-devs I was wondering if u are aware of this thread and is current progress.
[Nexus 4 Original Android Development] fozzie:
Yes, he's aware. Go back a couple of pages and you'll see it's already been discussed.
[Nexus 4 Original Android Development] Cantacid:
I m seeing a seconds delay to wake up the device,is kernel the reason?
[Nexus 4 Original Android Development] dhruvmalik:
Getting a massive amount of msm_hsic_host wakelocks. Close to 9% all from R120 onwards. As soon as I reverted back to r111 and rebooted, let the device sit for sometime and its gone down back to 1.2% or so.
[Nexus 4 Original Android Development] scream4cheese:
No delay here.
[Nexus 4 Original Android Development] alcaprone:
For me the latest version in super smooth..the only problem is a bit higher battery consumption when performing basic tasks such as browsing xda
[Nexus 4 Original Android Development] pmicho:
Amazing battery life

Since 121 battery life has been amazing. Thank you Franco!
[Nexus 4 Original Android Development] PetritH:
Sry for off topic, whats the name of weather widget in your signature?
[Nexus 4 Original Android Development] nachordez:
It was changed afterwards, in 119 or 120. Someone proposed that, and Franco liked it. And its working fine! If you search, there was explained how this idea work...

Anyway, you can always try different things and see if it's better for you and your phone use, and share your researches if there are interesting conclusions. It's the way to help Franco improve the kernel!

Nexus 4, stock kernel, last Franco.kernel nightly
[Nexus 4 Original Android Development] amarb70:
Thank you for your response :what:

When you say a full wipe, you mean only data and cache/system etc through custom recovery yeah? And I think that may fix it to be honest, I have been flashing rom updates and kernels through dirty flash every time recently, I haven't fully wiped in some time:|

..sent from space