yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] osm0sis:
See I knew it! Every time I'm like "okay, time to go to bed", that's when the action starts! :D
[Nexus 7 Original Development] FitAmp:
Well, battery tests restart now :)

---------- Post added at 10:29 PM ---------- Previous post was at 10:28 PM ----------

Exact same for me x)
[Nexus 7 Original Development] franciscofranco:
Wait a sec, ****ing taking long to upload the files, ****ing internet connection in the US.
[Nexus 7 Original Development] FitAmp:
Its all good, no rush
[Nexus 7 Original Development] franciscofranco:
****ing there.
[Nexus 7 Original Development] zewelor:
Franco, can you add support for nfsv3 to your kernel ? Great job on kernel !
[Nexus 7 Original Development] The Gingerbread Man:
Deadline is now correct, the interactive tunables are slightly different from the winners but potentially a little more battery friendly with the lower hispeed freq so gonna stick with those for a while. This release feels noticeably faster and snappier than r60. All round good stuff here!

I am in agreement with Osmosis we are nearly ready for milestone just need the under volt working again and custom power hal
[Nexus 7 Original Development] franciscofranco:
For what purpose?

Why do we need a custom PowerHAL? The PowerHAL is just for increasing CPU frequency when it detects a touch event.

I have to re-code, again, the ****ing UV code. I'll have a look in a few days, not in a rush for that.
[Nexus 7 Original Development] zewelor:
To be able to use nfsv3 using your kernel. What cons can you see that won't allow adding it ? You have already nfsv2 compiled in so why not nfsv3 ? Or just make nfs as module. If nfsv2 is compiled in, but without nfsv3 support we can't even compile our own module to make it working.
[Nexus 7 Original Development] osm0sis:
Underclockers. The PowerHAL also prevents screen off from reverting the max freq, no?

Yeah, it'd be good to make sure everyone likes these over 90 / 15000 / 1000MHz / 45000 / 30000 / 80. :good:

Can some people in here try those versus the current defaults and give their opinions? Thanks in advance! :)
[Nexus 7 Original Development] The Gingerbread Man:
Under clocking was what I had in mind, there was a small something I worked on and it kind of needs the power hal to actually work as intended
[Nexus 7 Original Development] franciscofranco:
Ah! Thats easy, we move the power_hal_name_something.so to power_hal_name_something.so.bak and reboot like I do on Mako, done, no more ****ing HAL ****ing with us.
[Nexus 7 Original Development] franciscofranco:
Ok, I'll add NFSV3, built-in though, not modules, I hate them.
[Nexus 7 Original Development] osm0sis:
Ah nice so you just need to add the .fkbak backup line back into fkbootscript and we're set! Nice and easy one! :)
[Nexus 7 Original Development] franciscofranco:
Yes it should be fine. I gotta test it first though, never know what kind of magical bull**** Asus/NVIDIA/Google added here.
[Nexus 7 Original Development] zewelor:
Thanks that would be great. Nfs is sooo much better network file system than samba/cifs. Using Nfs you can easy watch 1080p movies via wifi, using samba they they choppy.
[Nexus 7 Original Development] franciscofranco:
You want client or server support? Or both?
[Nexus 7 Original Development] poondog:
Personally I always change hsf to 760 anyway, 1000 is too much imo

For me, using the values in r57 was smooth and with my use it spent almost an equal amount of time at each frequency. I haven't tried r61 though

Will removing the powerhal do anything else besides stop it resetting frequencies?

Sent from my Nexus 7 using the xda app :)
[Nexus 7 Original Development] zewelor:
Client only. I don't think busybox even support nfs server at all. Also it doesn't support nfsv4 afaik so addins nfsv4 will be pointless. Thanks !
[Nexus 7 Original Development] franciscofranco:
Done. Available on the next version.
[Nexus 7 Original Development] zewelor:
Thank you.
[Nexus 7 Original Development] The Gingerbread Man:
The only difference between these newer values and current tuna ones is the timer rate so I gonna turn it up to 30,000 on tuna and perhaps save some battery.

My I'm really happy with r61 I can finally delete r47 as a back up :p
[Nexus 7 Original Development] franciscofranco:
$bb [ -f /system/vendor/lib/hw/power.grouper.so.bak ] || $bb mv /system/vendor/lib/hw/power.grouper.so /system/vendor/lib/hw/power.grouper.so.bak
[Nexus 7 Original Development] The Gingerbread Man:
I understand the directory path but not a clue about $bb mv or $bb [ -f. I can also see you renamed it to a .bak. Does it mean the file is safe to just rename to have a .bak extension?
[Nexus 7 Original Development] franciscofranco:
$bb is the shell alias that I have on fkbootscript. Just do this on your machine:

mv /system/vendor/lib/hw/power.grouper.so /system/vendor/lib/hw/power.grouper.so.bak

You're done.
[Nexus 7 Original Development] The Gingerbread Man:
And that will stick accross reboots or you need to do it every time?

Sent from my Galaxy Nexus
[Nexus 7 Original Development] franciscofranco:
Sticks.
[Nexus 7 Original Development] jazzespresso:
Hey, like UBER did, can you post your complete full settings for us? I am trying to collect all settings people use to get the best possible settings for the kernel. like said, looking for very good battery life with no sacrifice on performance:D

---------- Post added at 07:46 AM ---------- Previous post was at 07:43 AM ----------

yeah of course, you got spoiled fast connection in Europe, in US we still like it is 90s :))))
[Nexus 7 Original Development] nexusmaniac:
I agree
[Nexus 7 Original Development] The Gingerbread Man:
That's what we are all trying to achevie, getting full performance is the easy bit just turn up pretty well everything but it comes at then cost of battery life. The tricky bit is getting good battery life, so my advice to you would be right now wipe Franco app data making sure all set on boot options are unchecked, reboot, then set TCP to Westwood and leave the rest absolutely as it is. A lot of work has gone into interactive governor and it took a good few weeks to get those deadline tunables good for performance on n7 and gnex. R61 is a mini milestone, like how r47 was. Let your battery stats have chance to recalibrate ;)

I am being a noob I keep getting an error about read only file
[Nexus 7 Original Development] jazzespresso:
OK..I got updated to f.kernel app to v9.3.1.

and I went ahead set my settings as below (based on UBER's settings). I am on r61.

ultimate goal (compare to stock kernel): better battery life without sacrificing performance.

I will see how this will performs. as always, any feedback or suggestions, greatly appreciated!

======================

Max: 1300

Min: 475

Max GPU freq.: 484

Governor: Interactive

=====================

Governor Control:

A_H_D: 15000

G_H_L: 99

HS_F: 760

Input_Boost: 0

M_S_T: 30000

T_R: 30000 (Per UBER's recommendation bump up to 30000, a bit more battery friendly)

T_L: 80

====================

Hotplug:

90 (high load threshold)

20 (med. load threshold)

40 (low load threshold)

====================

Custom Kernel Settings:

I/O Scheduler: CFQ

Fsync OFF

Both Loggers (Turn logger off and Turn Events logging off) OFF

=====================

Voltage:

All default settings (not alerted) - unless someone can make some recomendation, let us know

---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------

really? I was a bit hurry and did not see your respond after I posted...hmmm....."TCP to Westwood" where? how?
[Nexus 7 Original Development] The Gingerbread Man:
Trust me wipe your settings, you have it here as a reference if you don't like the new defaults. Wipe the app,reboot, set TCP to Westwood and toggle f sync off then on to ensure its on. Try for a few hours if you don't like it the settings are here.
[Nexus 7 Original Development] poondog:
Try in a file explorer checking system read/write

You need a root explorer like solid explorer

Any reason for choosing that congestion control other others?

Sent from my Nexus 7 using the xda app :)
[Nexus 7 Original Development] khaytsus:
Last night I decided to try changing the max freq to 760 in the Franco app, cleared CPU counters in CPU Spy so I could see what was being used, and fired up Symphony of Eternity for an hour or so.

Launched CPU Spy, and 55 minutes (92%) at 1300. Am I doing something wrong?

---------- Post added at 09:22 AM ---------- Previous post was at 09:21 AM ----------

Stupid question.. I have busybox on my Nexus 7, but not "installed" as sometimes that'll mess with the ROM as I'm still using the stock ROM. I assume there's a /proc point to poke to change the TCP? I'm confused why it needs busybox and the rest seem to not?
[Nexus 7 Original Development] The Gingerbread Man:
Westwood seems to be faster, thats the general consencus. Thanks forr your

help I had my noob brain on :p

As for TCP you do need busybox for that, download the app from the play store, install it and let it install for you. Once busy box is on your system you can change the TCP algorithm, Westwood seems to be one of the better ones
[Nexus 7 Original Development] sjknight413:
Why is everybody so bothered about changing the TCP congestion control algorithm?

It is to do with bandwith and network congestion, it will have no discernable effect on the speed of your device.

Obviously none of you have even bothered to read up on what it is.

Franco, r61 is perfect here.
[Nexus 7 Original Development] khaytsus:
Aaah okay this rings bells, the PowerHAL interferes with things. I googled a little and saw replacement PowerHALs, should I care about those or just renaming it is fine? Any adverse side effects (besides remembering to fix it next OTA ;) )

Thanks!
[Nexus 7 Original Development] The Gingerbread Man:
My brain has obviously gone to **** here or something but even after renaming it to .bak under clock won't work over a reboot. I would take a screen shot but it won't help. 1300 step is still used even though I set 760 Max and checked set on boot.

---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------

It doesn't actually appear to work so I'm going to edit my previous post.
[Nexus 7 Original Development] ÜBER™:
[MENTION=2918197]The Gingerbread Man[/MENTION]

You cannot calibrate your battery. You can let the kernel settle to get the best battery results. But battery calibration is a joke.

Sent from my Nexus 4
[Nexus 7 Original Development] khaytsus:
Aha. :( I wonder why they designed it this way.. This game (and others) that would likely run just fine at lower speeds eats battery like crazy, 20%/hr or so. Oh well. :)
[Nexus 7 Original Development] osm0sis:
Can we make that .fkbak like on tuna and manta? I just think it's nicer to leave a hint about what did the renaming. Consistency is good too, that way when OTAs come out for stock users you know you can just say "is there an .fkbak? Rename it to pass the OTA asserts." :)

I'm with The Gingerbread Man. Current defaults. Only thing different is westwood and 520GPU. Maybe the old winning tunables but I would still like more opinions so Franco can maybe go with the one everyone likes best.

Device no, connection speed, yes. Less choking means higher sustainable download rates. Check out Franco's comparison of speeds on each in the OPs of the GN thread. I've done my reading, thanks. ;)

Calibrating the battery itself is a myth, but the battery stats file calibrates itself, giving you more accurate battery usage data. Full charge and leave it for an extra hour or so to trigger it.
[Nexus 7 Original Development] ÜBER™:
Lol battery stats reset, they dont recalibrate themselves ;). Just charging to 100% triggers the reset.
[Nexus 7 Original Development] osm0sis:
Some devices need the hour as it happens sometime after it's 100%. And no, they calibrate. The device doesn't know exactly where it is with its battery the whole way down, there are points where it's accurate and it estimates based on usage between those. The full charge resets the app stats but also adjusts those set points of accuracy based on the previous discharge.
[Nexus 7 Original Development] ganeshp:
So am I the only odd one with lags in YouTube over 61

Im having everything default except for gpu - 520Mhz and TCP congestion control - westwood

Once I switch to ondemand lags are gone
[Nexus 7 Original Development] nexusmaniac:
Nope your not the only one, when r61 was released I had no perturbs with YouTube until today, I last all of the settings at default

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 7 Original Development] jazzespresso:
I don't know...I am kind of lost up until all start talking about changing TCP, westwood ...etc :p, since I have no idea why we need to change that....I guess I am going to listen my instinct and stick with all default settings in f.kernel r61 and let it run couple days and see...
[Nexus 7 Original Development] Shano56:
Franco...y u post from 1969??? Y u no like 2013? :p
[Nexus 7 Original Development] CamoGeko:
No lags on YouTube here after flashing r61.

Interactive + CFQ.
[Nexus 7 Original Development] Nexus7<3:
curious

I'm very curious why you don't like a CPU overclock in your kernel but you allow a GPU and low power CPU core overclock. If you have the time please enlighten me.
[Nexus 7 Original Development] Warren_Orange:
Which one to go for? r60 or r61?
[Nexus 7 Original Development] fozzie:
Whatever takes your fancy! Try them both and decide.

Or live on edge and just go for the latest!

---------- Post added at 06:33 PM ---------- Previous post was at 06:31 PM ----------

That's usually best; if you don't know what something does, leave it alone :)
[Nexus 7 Original Development] CamoGeko:
Go for r61.

I just played an HD YouTube video for about 15 mins and had no issues whatsoever.
[Nexus 7 Original Development] formicae:
His upload was so slow he had to travel back that far in time* to start the upload so it would be ready this morning.

*true stories: AMD was founded May 1, 1969; Intel was already a year old
[Nexus 7 Original Development] ÜBER™:
This is all I was able to pull, r58/r60. Going to flash r61 now and charge up. 6.5 is what I'm used to getting. I don't see how people get anymore than 6.5 with normal usage unless they spend quite a bit of time staring at the same page for hours.

Sent from my Nexus 7
[Nexus 7 Original Development] ÜBER™:
Oops.

Sent from my Nexus 7
[Nexus 7 Original Development] fozzie:
Did I miss something here? Should that library not be currently loaded or was it just a general response about how to disable it?

I only ask as mine is loaded & the fkbootscript doesn't do the renaming.

Ta.
[Nexus 7 Original Development] osm0sis:
Definitely r61, it's got all of our finalized scheduler tunables. :D

That's not in fkbootscript yet, but it's basically the line that will go in when he updates it. I'm hoping he'll make it .fkbak so it matches manta and tuna but otherwise we're good. You can put that in init.d for now (remove the $bb though first) or just rename it manually to .fkbak and underclocking will work normally in the meantime. Did so myself a couple hours back and it works great; underclocks persist through screen-off and reboots now.
[Nexus 7 Original Development] fozzie:
Thanks. If we're not under clocking, is it still not needed? I.e. it's loaded currently but unused at all? Ta.
[Nexus 7 Original Development] The Gingerbread Man:
Os any idea why under clock is not working for me across reboots? I have changed system/vendor/lib/hw/power.grouper.so to be system/vendor/lib/hw/power.group.so.fkbak rebooted and then set 760mhz max and set on boot (using a power mode) and it doesn't seem to have worked. Amy ideas? Screen shot of CPU stats taken after reboot and reset timers to clear the 1.3 times during boot
[Nexus 7 Original Development] sjknight413:
Pretty sure Franco still leaves the low power core disabled, he removed the option to overclock it from his app quite a while ago.
[Nexus 7 Original Development] osm0sis:
Good question. Francisco said it was used for input boost, but I don't think we use that currently. That's why Francisco's looking into it to make sure there isn't any "Asus/NVidia magical bull****" in there before he adds the command to rename it; GM and myself are just going trial by fire with it. ;)

Try it with just the usual Frequencies/Voltage section Max and Set On Boot toggle; that's all I did. Could be that Power Modes on boot are broken? They're the least used feature of f.Ku, especially on this device, so I really wouldn't be surprised that nobody noticed until now.
[Nexus 7 Original Development] The Gingerbread Man:
No dice I'm afraid. Set Max to 760 and set on boot, rebooted and as you can see if you look at the screen shot set CPU sees that 760 was meant to be the high speed but still records faster speeds used

Edit

The fku also detects 760 was meant to be max, it was displayed still in the min / max speeds but as we can see it didn't work.
[Nexus 7 Original Development] osm0sis:
Ah that'd be why I mistook it for working. Good catch.
[Nexus 7 Original Development] nexusmaniac:
Is this on auto brightness?

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 7 Original Development] ÜBER™:
No, around 30%
[Nexus 7 Original Development] nexusmaniac:
Also is this using the default settings or the ones you posted the other day?

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 7 Original Development] ÜBER™:
Yep.
[Nexus 7 Original Development] lollyjay:
Hahahaha!

Nexus 7 WiFi 32Gb | PA 3.15 13-Apr2013 | Nova Prime | Franco-Kernel r61

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Original Development] nexusmaniac:
Lol thanks for the answer ;) I'm pretty sure your using your custom ones.

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 7 Original Development] Jonnyredcorn:
I'm still running r47 have had no issues and petty good battery life (although I'd love to be able to get the standby time my iPad 3rd gen gets on an android device) I updated to r58 at line point but started to experience video & sound issues so I reverted back. r61 have any big advantages to it? I love flashing updates as much as everybody but so far with my nexus I'm going with tube if it aimt broke don't fix it.

Sent from my Nexus 7
[Nexus 7 Original Development] The Gingerbread Man:
With r61 the only thing you can't do is under volt and under clock. Everything else is working great. No audio issues, no screen wake up lag, no YouTube issues. New deadline tunables gives boosted SD performance and interactive has been made a more battery friendly. This replaces r47 as a current stable version. You could always back up r47 with the back up / restore facility built in and flash r61img with the app and you can easily swap versions. Its time for to you update :cool:
[Nexus 7 Original Development] nexusmaniac:
What kind of SOT are people getting with the default kernel settings?

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 7 Original Development] The Gingerbread Man:
Too early to tell about battery life yet. The thing is though if your trying to work out what's better between ubers settings and defaults thats absolutely fine but comparing two different peoples battery data without any testing of your own to compare to won't give any real comparison as we use different apps / games with so much other variance with other settings the data just wouldn't be conclusive enough to give a real comparison. Try some set for a few days, try another set for a similar time and compare screen shots you take along the way. Only you can judge for your own device and usage pattern
[Nexus 7 Original Development] Mr. Steve:
I'm still getting lag in Youtube on r61 while using stock settings (except for GPU at 520). While I was on r58 I was using interactive with the minimum set at 475 which worked to great success, I'm gonna try that on r61 and see how the battery life vs performance is.
[Nexus 7 Original Development] drose6102:
Still got it with GPU [MENTION=3705640]520[/MENTION]. Wiped app data and rebooted with r61 and stock settings. It starts stuttering after about 4 minutes. Going to try updating Eos to the latest April 20th build
[Nexus 7 Original Development] The Gingerbread Man:
Could you link to a specific video so we can all reproduce it? Iv been using mine all day near enough and had no issues with anything I have tried and tested most things
[Nexus 7 Original Development] drose6102:
https://www.youtube.com/watch?v=vurjINRTfrg&feature=youtube_gdata_player

Still had stuttering after flashing latest eos and r61 again so I went into the unknown and changed the medium load threshold to 20 and all is well. Changed it back to 25 and no issues either with the above video. I am lost
[Nexus 7 Original Development] Jonnyredcorn:
I have r47 backed up from when I updated to r58 so yea the backup and restore function in the app is great. Think I'll give it a try before I charge, thanks.

Sent from my SGH-I747
[Nexus 7 Original Development] franciscofranco:
I only have GPU overclock! I don't really like CPU overclock.

Don't go wrong with that, I get plenty of emails about the power modes, people use them. Although they need a bit of work soon :)

Weird thing about 1300MHz still being used. I need to look at it further.
[Nexus 7 Original Development] FitAmp:
I just tried that video and I also had stuttering :/ wtf ...

Edit: I just changed hispeed_freq to 1000mhz and the stuttering disappeared
[Nexus 7 Original Development] putomacao:
I tried that video and didn't even experienced a bit of stuttering. Im using CM10.1 nightly build 0429.

Sent from my Nexus 7
[Nexus 7 Original Development] Gabrieltan:
no problem for me to play this video....very smooth...
[Nexus 7 Original Development] osm0sis:
Watched it to the 9 min mark, all defaults (except 520GPU and westwood) with zero problems.. :confused:

Stock ROM of course.

Ah sorry, my mistake about the power modes. Check the Group for some new proposed ones. :)

As for the underclocking issue, I tried out imoseyon's 'nofreq' custom PowerHAL to test and I could still make it ramp up to 1000 and 1300 after I set my max to 760, so there's definitely something else going on here. :eek:
[Nexus 7 Original Development] Jonnyredcorn:
So I finally flashed an update(updating from r47) and I'm watching that knife making video right now and haven't so far experienced any stuttering. Also haven't change any settings. I noticed in the changelog that the min CPU freq was upped to 206mhz or whatever, just pointing out that on the CPU voltages menu it still shows 100mhz.

Only issue I'm having with the video is a ton of buffering which was also happening on r47 but I'm gonna have to attribute that to my connection.

Edit: so I am experiencing a lot of stuttering a few minutes into the knife making video. Reverting back to r47 till this gets straightened out. I don't have any knowledge of tweaking kernels or troubleshooting so I can't really contribute.

Sent from my Tablet
[Nexus 7 Original Development] putomacao:
The battery life in r61 is really amazing..maybe I can upload some ss later.

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Yeah UV is way broken. Francisco said he'll look into it again soon.
[Nexus 7 Original Development] Jonnyredcorn:
Yeah I remember reading it was broken just something I observed. I went back to r47 until something as stable comes along. Like I said before if it ain't broke don't fix it. However if a kernel updates has improvements with no expense to stability I'm all for it.

Sent from my Nexus 7
[Nexus 7 Original Development] nealkoy:
watched some hd videos today in youtube with r61 (all stock) and experienced stuttering mostly in the initial part of the vids. it doesn't happen to all videos though... changed to ondemand and it seems the problem is now gone.. must view more vids with ondemand and check.

Sent from my HTC One X+
[Nexus 7 Original Development] Lovrium:
I've experienced shuttering while changing volume.

No HD on stock kernel settings
[Nexus 7 Original Development] putomacao:
I'm not really sure why you guys experienced some stuttering on youtube, I remember what faux said...."not all chips are created equal"

Sent from my Nexus 7