yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ÜBER™:
Just flashed r125 and have been using for a while now. I can't say I'm a fan of this dynamic gov control. I understand the logic. But the smoothness for the sake of battery life is killing me. My tunables suited me and gave me good enough battery life. Does it help in games and benchmarks? Yeah but couldn't you just set the tunable your self prior to opening the game/benchmark. Why does the gov have to do it. Is it nice that it does, yes, but I don't like the compromise. Just my opinion and would prefer to go back to the norm.

Sent from my Nexus 4
[Nexus 4 Original Android Development] decouvrir:
do not know if it is kernel related, left my phone on lock and went to sleep, woke up and couldn't turn on.

search the forums and it is something called the 'red dot of death', power on for 60 seconds and insert charging cable and the phone was back alive. hmm
[Nexus 4 Original Android Development] franciscofranco:
This is actually helping on battery life as during low load the tunables are much more battery friendly. Anyway was for testing obviously I plan to add a toggle to turn on/off the scaling.
[Nexus 4 Original Android Development] jarjar124:
+1. Although it did provide a nice boost in gaming, the compromise in return isn't that great. Great idea though. I think a toggle would be nice.

Edit: Looks like it was planned. :P
[Nexus 4 Original Android Development] ÜBER™:
Maybe you should define loads in percentage. Under 20% load tunables favor battery. Under 50% tunables are a little more aggressive. Under 75% and it'll get a little more aggressive and over 75% it will favor performance.

Sent from my Nexus 4
[Nexus 4 Original Android Development] pyr0sphere:
I believe you're the first person (in addition to myself) to say that battery life is worse. Things definitely are smoother in r125 but battery has taken a hit
[Nexus 4 Original Android Development] Cuzz1369:
That's not what he said at all. It was quite the opposite.
[Nexus 4 Original Android Development] JarGnex:
Done :) loving the latest nightly however Idk if its kernel related or not but phone screen becomes irresponsive below 5% of charge
[Nexus 4 Original Android Development] Shano56:
Do you undervolt?
[Nexus 4 Original Android Development] JarGnex:
No. I have touch control tho you think that's causing it?
[Nexus 4 Original Android Development] pyr0sphere:
Just re-read his post. Don't see how it can be taken as him saying battery life is actually an improvement instead of a downgrade
[Nexus 4 Original Android Development] Cuzz1369:
He said he wasn't happy with the performance. And he didn't want to sacrifice performance for battery.

---------- Post added at 11:13 PM ---------- Previous post was at 11:13 PM ----------

---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------

---------- Post added at 11:14 PM ---------- Previous post was at 11:14 PM ----------

---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------
[Nexus 4 Original Android Development] pyr0sphere:
I see what you mean now
[Nexus 4 Original Android Development] ÜBER™:
I mean it as, you lose smoothness for the sake of battery life. Not the other way around. :\

Sent from my Nexus 4
[Nexus 4 Original Android Development] pyr0sphere:
I must have some messed up settings then, because everything is much smoother than the previous version. This is most noticeable when scrolling in apps like tapatalk. Also, my phone runs hotter (checking using the Franco app) compared to before) although my idle temps seem to be cooler
[Nexus 4 Original Android Development] franciscofranco:
What settings do you use?
[Nexus 4 Original Android Development] Shano56:
Not sure. I don't usually keep my phone that low so can't say I've experienced your issue. Under volt is the only thing I could think of. Who knows :p
[Nexus 4 Original Android Development] drawde40599:
Agree, its smoother and faster, battery seems about the same not better or worse here
[Nexus 4 Original Android Development] kd8bny:
I would second this....reverted back to 121.

I truely believe Franco is headed in a great direction...just a little more tweaking. Battery life is impecable though!
[Nexus 4 Original Android Development] michael_ta315:
why not r122?
[Nexus 4 Original Android Development] franciscofranco:
That is a very interesting approach!! What I'm currently thinking is if we should rely on automatic calculation of the tunables based on the load % instead of using static values. We know which values to increase and which values to decrease to achieve our goals - that research being done a long time ago we can now just make a small calculation for example if we want smoothness (performance values): timer_rate = timer_rate/(load/10), which in heavy usage would be something like 30000/10 = 3000 which equals to 3ms. But in the "battery mode" we could simply do timer_rate = timer_rate*(load/10) that would be 30000*1,5 = 45000.

How does that sound?
[Nexus 4 Original Android Development] Tarun95:
Franco if I go and change the tunables will it change for low load ? Because the scrolling smoothness has definitely gone down

Edit: it becomes the same again
[Nexus 4 Original Android Development] JarGnex:
Hmm I'll try not to let it go that low then :D thanks
[Nexus 4 Original Android Development] franciscofranco:
The tunables will change again if the high is load and you'll lose yours. This r125 is a proof of concept, thus the customization of the governor is a bit limited at the moment.
[Nexus 4 Original Android Development] alanwyl:
Would this constant calculation slow down the whole process?
[Nexus 4 Original Android Development] Tarun95:
Battery seems to be excellent on this compared to any version but performance has definitely gone down
[Nexus 4 Original Android Development] michael_ta315:
Franco i'm just being curious and a little off topic :silly: what ROM are you using now? I assume there's no differences between your kernel here and your kernel on the Minooch V7 ROM right? :p
[Nexus 4 Original Android Development] franciscofranco:
Nope, we're not scaling the tunables every time, its kinda sporadic. If we were doing divisions every 10th of a second...then yes :)
[Nexus 4 Original Android Development] franciscofranco:
I'm using MiNCO v7. No, same kernel.
[Nexus 4 Original Android Development] ÜBER™:
On r122 i was using

Above_hispeed_delay: 15000

go_hispeed_load: 99

hispeed_freq: 1188

input_boost: 0

min_sample_time: 30000

timer_rate: 25000

Now im using the default ones.
[Nexus 4 Original Android Development] strikelight:
Are we sure of this, in performance mode? Ie. When the CPU is stressed, I would hypothesize that it might be possible for micro stutters to occur during the frequent calls to the timer routines, as the CPU has other tasks at hand, which since such tasks are causing the CPU load so high, it would be easy to assume that these tasks would be sensitive to the CPU being distracted with the frequent timer. Obviously, this is just conjecture, and simply a hypothesis.
[Nexus 4 Original Android Development] Jakey-O:
Hello! Is there a way to disable mpdecision via Franco Kernel Updater app? Because I can't find it..
[Nexus 4 Original Android Development] trailblazerz11:
Latest kernels use Francos custom hotplug

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Which routines? The scaling of the tunables only happens once when the load is big, if you're playing the routines are not called anymore, it just skips it. Then when its low again it will call them again just once, and won't call them again. And so forth.

I know what I'm doing :p Nevertheless what you said is correct!
[Nexus 4 Original Android Development] GerhardKi:
Done! 5 Star review.
[Nexus 4 Original Android Development] immature:
Hi, I've just flashed r125 and had a question - the release notes mentioned that Interactive governor is the one to use for r125, should this be set as the default? I can't seem to change it in the app, it keeps resetting back to Conservative. Clearing app data and rebooting also defaults to Conservative :(

Not using any other app to control governor apart from the f.K app...

Thanks!
[Nexus 4 Original Android Development] .coomb.:
This.

We need to squeeze more battery life out of the N4 during general usage, I think. I did a non scientific test and for about 2hrs of screen on at maximum brightness and I'm already on 50% just sending messages and navigating through the UI, no gaming at all. 10 minutes of wifi and that's it, no data. I think there are improvements that can be made and your idea surely sounds promising.
[Nexus 4 Original Android Development] Eric-1987:
I guess your opinion is the only one that counts.
[Nexus 4 Original Android Development] Hanny:
Okay so now we have a smart calculation inside the smart governor along with the smart hotplug

We really need a buzzword for our situation - Intersmartttive^3!!!

Back to the topic, you mean

First we have some original tunables - in your example 30000 - can be configured by user

1 core / 2 cores / 3 cores -> Power-Saving-Without-Neglecting-Idle-Responsiveness Smart Values - doing timer_rate*(load/10) based on user's settings in the original part

4 cores -> Performance Smart Values - doing timer_rate/(load/10) based on user's settings in the original part

****, timer_rate*(load/10) is ****. lol.

In idle/very low load we will have our original tunables which is more to the moderate - the one we think its smooth for us without microstutters

and in more load (+more cores) before reaching 4 cores, the values are just going to be more and more and more power saving / preventing unnecessary spikes. This is really awesome...

For the smart performance one, first we have to be aware that games dont really put 100% stress at all times, well although even if the mode is on (4 cores staying), the load becomes e.g. 60, the timer_rate is still 30000/6 which is 5000. Still ****ing responsive so this may not be our concern.

second thing - during normal UI activities there are moments that when opening some really bulky apps (facebook!) / at certain moments the load would spike above 90 for a few seconds. Now timer_rate would (entering performance values) still be 15000 but after smart calculation the few seconds will be 3000. Therefore some timer counting 4 cores is staying for a certain period before activating the Performance Smart Values would be good!
[Nexus 4 Original Android Development] ayamary:
If you want it that badly, fork it and do it yourself. Being passive aggressive like that isn't going to help anything.
[Nexus 4 Original Android Development] Eric-1987:
I'm not I was being serious. If I knew how to code that well I'd just make my own kernel.
[Nexus 4 Original Android Development] 75markus:
Rated 5***** :)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] hitokiri.pr:
Anyone?
[Nexus 4 Original Android Development] andyli1985:
In the app, click on download latest nightly kernel, it will show the change log.
[Nexus 4 Original Android Development] spicediablo:
I'm having frequent freezes when unlocking after upgrading to r125. I've posted a log few pages back. Franco, is this caused by the kernel? Or is it something else ?

https://www.box.com/s/e7sgch1m03rbdilbajo4

Sent from Mako⁴
[Nexus 4 Original Android Development] franciscofranco:
Changelog is still there :(

That is really strange:

[ 3277.794036] resout_irq_handler PMIC Initiated shutdown

[ 3277.794280] PMIC Initiated shutdown cpu_power_off cpu=0

[ 3277.794494] Powering off the SoC

[ 3277.794891] Calling scm to disable arbiter

[ 3277.795165] SCM returned even when asked to busy loop rc=-4

[ 3277.795532] waiting on pmic to shut msm down

4 Corrected bytes, 0 unrecoverable blocks

Boot info:

Last boot reason: hw_reset_or_poweron

I guess something told it to reboot. Are you undervolting?
[Nexus 4 Original Android Development] spicediablo:
All stock values as I'm not expert, dare not touch the settings. I have touch control install. No freezes on r122 though. Do you think I should freeze touch control? Perhaps the log was taken after reboot? I can't take the log before rebooting as my touch screen totally not responsive

Sent from Mako⁴
[Nexus 4 Original Android Development] franciscofranco:
I've been thinking of a real formula to use for it to scale the tunables automatically without static values but I haven't managed to get a good one so far. :/

What I'm testing right now is:

For performance (4 cores):

above_hispeed_delay = 0;

go_hispeed_load = 70

timer_rate = 15000

min_sample_time = 80000

For medium load (2 or 3 cores):

above_hispeed_delay = 50000

go_hispeed_load = 99

timer_rate = 45000

min_sample_time = 20000

For low load (1 core):

above_hispeed_delay = 15000

go_hispeed_load = 99

timer_rate = 30000

min_sample_time = 45000

It seems a good compromise to me to be honest based on the feedback.
[Nexus 4 Original Android Development] Anytime1157:
Oh my, smart things are coming in! Its like feeding books to my phone, it keep getting smarter! :D

Thanks Franco for your effort! Can't really understand the calculations done but I know it would be great ;)

r125 working flawlessly that sometimes I feel the phone is moving faster than my fingers could touch the screen :p

Rated 5* and will always be
[Nexus 4 Original Android Development] Hanny:
all are pretty cool, though in low load (1 core), i would like to try timer_rate 25000 and min_sample_time 30000/35000

because I think we need more immediate responsiveness when theres load from idle, while min_sample_time can be lowered abit for battery
[Nexus 4 Original Android Development] hoseth0711:
I never figure out how to do that. Can somebody please tell me where and how?

Sendt fra min Nexus 4 med Tapatalk2
[Nexus 4 Original Android Development] franciscofranco:
We can try that, why not.

Very simple:

Color Control -> Load Your Color Profile -> Load color profile presets. Magic.
[Nexus 4 Original Android Development] nachordez:
In color control -> load your profiles

(Or something like that, I'm reading in Spanish)

Touch above on load profiles. It will download the proposed ones. You'll see them below.

Then press on the one you would like to try. You'll see the values and the option to set it.

Done

Simple! :p

Nexus 4, stock kernel, last Franco.kernel nightly
[Nexus 4 Original Android Development] franciscofranco:
Ok lets try another r666.
[Nexus 4 Original Android Development] aventu:
Dynamic governors are a good idea, but the responsiveness will decrease. So what about an option for "input_hotplug" with 0 to 4 cores (2 default)? Every time you touch the screen 2 cores will go online with an medium load governor scaling. I know this sounds like mpdecision, but the frequency scaling wouldn't be locked at 1GHz and francos holtplug driver disables the cores a lot faster. This option can guarantee a smooth ui with all the battery saving features.
[Nexus 4 Original Android Development] Wezi:
Suspend backup

Getting heavy wakelocks. R125
[Nexus 4 Original Android Development] franciscofranco:
Second core goes online when you touch it because the load is big enough to kick it in simply by touching the screen.
[Nexus 4 Original Android Development] aventu:
Is the cpu load calculated independently from the governor sample time?
[Nexus 4 Original Android Development] franciscofranco:
Yep, its a different driver, nothing to do with the governor itself.
[Nexus 4 Original Android Development] Hanny:
franco didnt post the final automatic values of this 666:

For performance (4 cores):

above_hispeed_delay = 0;

go_hispeed_load = 70

timer_rate = 15000

min_sample_time = 80000

For medium load (2 or 3 cores):

above_hispeed_delay = 50000

go_hispeed_load = 99

timer_rate = 45000

min_sample_time = 20000

For low load (1 core):

above_hispeed_delay = 15000

go_hispeed_load = 99

timer_rate = 25000

min_sample_time = 40000

In performance mode, go_hispeed_load has decreased from 85 in r125 to 70, and I feel theres more 1.5ghz showing up while playing gta

0420 r666:

GTA maintains 36-37 fps as r125, but with some hints of 38 avg fps showing up. Although it didnt stay for >10 secs therefore I dont count it in the results.

Beach buggy blitz maintains 58 avg fps at the beginning of the game, same as r125.

(note to testers: at later parts of the game the coins spawn increases from 1 in a row to 2 in a row and 3 in a row. increased no. of coins spawning and hitting will decrease average fps overall.)

in terms of UI responsiveness initially its pretty cool, especially for 1 core loading. have not experienced a notification-press-microstutter yet. more accurate feedback on this after a day :)
[Nexus 4 Original Android Development] franciscofranco:
Hmm if the gain in fps isn't significative I'll drop increase go_hispeed_load to 85 and that will help on heat on the long run.
[Nexus 4 Original Android Development] Hanny:
yup, agree!
[Nexus 4 Original Android Development] TheLawIX:
All of a sudden I randomly can't connect to wifi or use data after my phone has gone into deep sleep. What's up with that?
[Nexus 4 Original Android Development] fozzie:
Default scheduler is Deadline in the latest r.666 deliberately? Just checking ;)
[Nexus 4 Original Android Development] tlf55:
I'm having some data drop issue too with the lastest r125 .. I'm comming from Faux kernel which didn't have this issue..
[Nexus 4 Original Android Development] Spec-Chum:
You could kinda optimise this a bit by using powers of 2, such as dividing by 8 and multiplying by 2 instead of 10 and 1.5

That way GCC should compile the code to shift instructions instead of muls and divs which can be very computationally expensive whereas shifts are usually 1 or 2 clk cycles.

Doesn't sound much but if the code is being run many times it'll have quite an impact.
[Nexus 4 Original Android Development] franciscofranco:
Yeah thats a good idea if I go down the path of automatic scaling without static values, which is what I'm doing right now, using static values.
[Nexus 4 Original Android Development] realfelix:
Seems logic :thumbup:
[Nexus 4 Original Android Development] Nethojs29:
Just flashed r125, god is perfect even in stock I was used to play gta 3 at high details and all, now maximum feel smooth ad low details, hope tomorrow I'll see how the daily use goes with this. Thanks!!

Enviado desde mi Google Nexus⁴
[Nexus 4 Original Android Development] spicediablo:
Update : I cleared data for touch control and it seems to fix the unlock freeze issue.

Sent from Mako⁴
[Nexus 4 Original Android Development] Goku80:
sorry to ask this....which would you guys recommend? ondemand or interactive to get the best of both worlds? what i mean perfomance and battery life....

loving the latest app look by the way with all the preloaded profiles...using franco's profile and i love it:D (and this is me not kissing tooshy by the way:D)
[Nexus 4 Original Android Development] aventu:
[MENTION=4550577]Goku80[/MENTION]

Just read the changelog for r125

http://minooch.com/franciscofranco/Nexus4/4.2.2/appfiles/nightly-changelog

and

http://xdaforums.com/showthread.php?t=1663809
[Nexus 4 Original Android Development] DesertVelo:
Interactive has been getting great results for everyone.

Sent from the singletrack...
[Nexus 4 Original Android Development] Goku80:
Thanks guys much appreciated...will keep updated regarding battery life:)
[Nexus 4 Original Android Development] DrunkFuX666:
I think interactive is the default setting if I'm not mistaken...??

Which setting is for slight compromise on performance but the best battery life...??

Sent from my Nexus⁴
[Nexus 4 Original Android Development] aventu:
[MENTION=3687104]DrunkFuX666[/MENTION]

Interactive is better adjustable than Ondemand and all the current tweaks from franco are for the Interactive governor.
[Nexus 4 Original Android Development] paaaulo:
RR3 with r125 avg fps was up to 37. With #666 it reaches 40.
[Nexus 4 Original Android Development] notbrodie:
I just recently started using Franco's kernel and I noticed that I had a large suspend_backoff wakelock. The phone was idling on my bed while I slept, so it shouldn't have had any wakeups at all.

Is this the sort of thing you'd want a log for?
[Nexus 4 Original Android Development] Crenshaw-PCGH:
Hey Franco do you still plane to add dual core only mode? :)
[Nexus 4 Original Android Development] fengxshui:
Don't know if anyone is having this issue. After installing r125 and rebooting the phone. All my data was reset and the phone keep telling me Google services has stopped and I can't get out of the window had to reinstall ROM and everything

I am using root stock with supersu with busybox
[Nexus 4 Original Android Development] Testraindrop:
Sounds like a bad flash, have you checked md5 before flashing?
[Nexus 4 Original Android Development] CrimsonSmear:
May want to lower go_hispeed_load to preempt 2nd core loading. I know these multipliers are rudimentary, but it indicates the concept.

For performance (4 cores):

above_hispeed_delay = x0.0

go_hispeed_load = x0.9

timer_rate = x0.5

min_sample_time = x2.0

For medium load (2 or 3 cores):

above_hispeed_delay = x3.0

go_hispeed_load = x1.1

timer_rate = x1.5

min_sample_time = x0.5

For low load (1 core):

above_hispeed_delay = 15000

go_hispeed_load = 90

timer_rate = 30000

min_sample_time = 30000
[Nexus 4 Original Android Development] fengxshui:
No. I just use the app to do a auto flash. Should I download the zip file then flash?
[Nexus 4 Original Android Development] scream4cheese:
try this

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

info

https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/suspend_backoff

http://xdaforums.com/showthread.php?t=1878828
[Nexus 4 Original Android Development] dapsANDpoundz:
Battery life has been steadily getting worse for me. Can't get >3hrs SOT consistently and without compromise like I used to. Think something's wrong with my phone though because this happened with stock kernel too a bit.
[Nexus 4 Original Android Development] zephiK:
Check wake Locks using better battery stats
[Nexus 4 Original Android Development] Tarun95:
I went back to m1. That just seems to do it for me. Guess I'll just wait for the next milestone. Sorry I am not involved in the testing the nightlies anymore:) need a ultra fast phone and m1 does the job :) really appreciate your work dude:) not kidding your kernel makes my phone fly with amazing battery. :)
[Nexus 4 Original Android Development] notbrodie:
I'll greenify chrome and see what happens. Its a bit weird, though, because I never got this wakelock when I was running faux's kernel
[Nexus 4 Original Android Development] scream4cheese:
Try this as well:

Go to chrome

Go to settings

Go to developer tools

Uncheck "Enable tilt scrolling"

Reboot phone
[Nexus 4 Original Android Development] teamjm:
Hi everyone, after installing Rom Paranoid. Downloaded Franco's app and asking me to pay again for his app, which i already did before installing the rom. How do i restore it? thanks!
[Nexus 4 Original Android Development] scream4cheese:
Pay again. :laugh::laugh::laugh::laugh::laugh:
[Nexus 4 Original Android Development] teamjm:
Huh?! Really!? :confused:
[Nexus 4 Original Android Development] DesertVelo:
Auto flash is fine. They can be used if you want to flash from recovery. For example, updating your ROM then flashing the kernel.

Sent from the singletrack....
[Nexus 4 Original Android Development] drawde40599:
Just clear playstore data and reboot or check your data connection clearing Google services may be option also if first 2 suggestions don't work
[Nexus 4 Original Android Development] Redneck Trash:
Email Franco from the account associated with the Play Store.
[Nexus 4 Original Android Development] resynx:
Love this kernel! Always can rely on it for good battery life and a smooth overall experience :)
[Nexus 4 Original Android Development] drawde40599:
Your signature made me laugh, R. I. P. Samsung captivate :P
[Nexus 4 Original Android Development] kd8bny:
I had some strange reboot on 122......never narrowed it down but never seemed present in 121
[Nexus 4 Original Android Development] thebryceee:
Not seeing any stutters anywhere with #666². Performance feels smoother.