yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] gapone:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Hi guys! Is there a proper way to underclock with this kernel because the max frequency setting goes to default 1300mhz after screen off? I'm underclocking with hispeedfreq 1000mhz and above hispeed delay 900000 but would be nice to use hispeedfreq setting properly.
[Nexus 7 Original Development] poondog:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

If you flash a patched powerhal it should be fine. I have the nofreq one from the leankernel thread and it stays under clocked at 1100mhz :)
[Nexus 7 Original Development] gapone:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Those powerhals doesn't work properly. Just benchmark with antutu and watch the cpu stats from the better battery stats and you will see that cpu goes to 1.3ghz. Any suggestions to underclock properly?
[Nexus 7 Original Development] poondog:
They work for me. The only time I'm running at 1300mhz is when the freq hasn't been set, 20 secs after boot
[Nexus 7 Original Development] gapone:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Could you post your settings in franco app and bbs cpu stats?
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I'm going with 0 and min sample rate at 30k.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] ROFLkopter:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Lag has gone but the game itself is still a piece of crap...

Lag has also gone from MC4 and the minimal lag in NFS:MW seems to have gone too.

Sent From My AOSPA3.+/franco.Kernel Powered Nexus 7 With XDA Premium
[Nexus 7 Original Development] ÜBER™:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Awesome. Fully charged gunna see how it does today.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] Short Viking:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Not running the stock values, but thought i should share this anyways :)

Got about 2 hours more than my usual average, with about same usage.

(R39 kernel)

I can post more screenshots like the values i'm using, if it's of anyones interest.

Thanks for this awesome, supersmooth kernel <3 love it!
[Nexus 7 Original Development] DemosZevasa:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Share :)
[Nexus 7 Original Development] Short Viking:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Found that 900mHz is about enough for scrolling in apps etc. Preventing it to peak much over that unless it's loading apps and so on.

It does lose some frames in heavy games, set my gpu to 520 for compansation. That maybe uses more battery, but if i need my battery to last, I'm not booting up 3D games anyways. ;)

If you got input I'm glad to hear! I'm no professor in cpu tweaking afterall, just for hobby and to learn about how my system works :)

Edit: Noting that I've now set my hispeed delay to 80000 for a little more smoothieness.
[Nexus 7 Original Development] chaostan:
Appreciate if u can guide me how to tweak this kernel..
[Nexus 7 Original Development] tomeks:
Odp: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Is there any chance about correction for the baterry drain by baseband_xmm_power which is causing that the device is not going into the deepslep?

http://www.spinics.net/lists/linux-tegra/msg09035.html

The bug is only for the nexus 3g

Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
[Nexus 7 Original Development] osm0sis:
Raising the delay favors battery not performance, so shouldn't make it more smooth. :confused:

Check out yellowdie's post from the GN for more info on the tunables.

http://xdaforums.com/showpost.php?p=33161912:)
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

That's what I thought but real life seems that 20000 is faster and smoother than 0 for me.

0 gives me that wicked fing annoying "sticky" screen where scrolling seems to not be smooth.

I know its supposed to be the opposite but who the f*ck knows.

More coffee.

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Interesting! I'll have to play with it some more! That's the one that should be a multiple of timer_rate, so try it at 15000. Maybe give 30000 a shot too, see which you find smoother. :)
[Nexus 7 Original Development] Short Viking:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Yes maybe i didn't make myself clear. 900mHz makes it smooth enough in apps, that's why i set the limit high, making it step up if the load is high over time, like when I'm switching apps, so that i can save battery.

I now set it from 86000 to 80000 to get a little bit more smooth :)

I might check the link you posted to learn a bit more about the subject :) Thanks!
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Trying 30000 now.

Sent from my Nexus 7
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I have the same feeling as you. Right now I'm testing the stock settings but changed the scheduler to deadline. Let's see how it goes :)
[Nexus 7 Original Development] djdunn:
Just saying putting highspeed delay to 0 seems about the same as hsf to 1300 it just takes about a half second longer to reach that point. Ita go to 1000 instantly then 1300 a half second after touching the screen
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I'm running Westwood and row and it feels pretty good.

Default interactive settings. Went back to 20000, seems like my sweet spot. Gonna try 15000 soon.

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Just played around with that idea for about an hour since I was seeing some jitter in the App drawer, even with GPU OC'd to 520. This happened regardless of scheduler, but between deadline and row I found row just a hair more smooth in this situation, still both very close overall though, I think. What I did is I went to the first page of the widget drawer and then slow-paged back to the last page of the app icons and adjusted my tunables until the jitter disappeared.

I found an a_h_d of 15000 to be dramatically smoother than 0, and 30000 to be close to 15000 but a little less smooth again.

I also found that g_h_l of 98 or 99 made things a little but more rough, even with the improved a_h_d, so I dropped it to 96 as well.

15/96/45/15; 1000 hsf. 520 GPU. row. westwood. I think these will be my new daily drivers. :cool::good:
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I'm going to try your suggestion of lowering to 96 and see how that feels. Also lowered to 15000 based on your multiples logic. Let's see.

I also have my GPU at 446, I don't play games so that's fine for me, and I disable fsync since my tablet has never froze or crashed. Not worried about that.

Thanks.

Sent from my Nexus 7
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

The only place I consistently see any jitter is when opening the f.KU app once it has benn cleared from the recent apps list.

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Yeah disabling fsync would also help, but I prefer to be safe than sorry, since you never know when something's going to sh*t the bed. ;)
[Nexus 7 Original Development] exzacklyright:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

What governors are you guys using? Interactive, row, westwood or cubic?

Sent from my Nexus 7
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I hear you but I'm a risk taker. Haha

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Only one of those is a governor. :p
[Nexus 7 Original Development] liranvaknin:
Can someone please explain me what each of this numbers is corresponding to in the tweaking app?

for example:

15/96/45/15; 1000 hsf

And also is it better to tweak the kernel option with franco's app or i can use trickster MOD app?

Thank's!
[Nexus 7 Original Development] exzacklyright:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

How are these settings?

https://www.dropbox.com/sc/4mn3wv6eq5e4kfy/DztMLmYfB3

https://www.dropbox.com/sc/2jieto35rmu6ab7/YPoM80Zalk

https://www.dropbox.com/sc/s1mfvzjarufotwx/oPTVktsoRf

Sent from my Nexus 7
[Nexus 7 Original Development] Wynnded:
I always see jitter in Tapatalk HD, but it could be the app.
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I bought francos app a long time ago to support him but I use trickster.

Sent from my Nexus 7
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Yea that's the app. Scrolling is bad on every kernel I've tried. The phone app does the same on my Gnex.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] osm0sis:
You can use either, though they're laid out in the order of f.Ku.

a_h_d / g_h_l / m_s_t / t_r; hsf.

All but g_h_l are multiplied by 1000 to get the correct number of ms (g_h_l is a percentage, so is 0-100; and of course hsf is in MHz). Compare with your app of choice, you'll figure it out. :)

If you're trying to recreate my governor tunables from the last page (ie. 15/96/45/15; 1000 hsf. 520 GPU. row. westwood) then hispeed_freq should be 1000MHz not 900MHz. If you did that purposefully to try and save a little battery then that's fine, just be aware that it might be a little more sluggish. For your CPU settings, max 1100 doesn't work unless you've got a patched powerhal library flashed, otherwise it just reverts to 1300; something Franco hasn't gotten around to for us yet. Voltages I don't know about since I've never UV'd the N7, but if you don't freeze up on the regular with them I'd say you're fine.

Someone said before that the UV interface didn't work correctly since it went all the way down to 100MHz even though it only technically acted on the G-cores (which stopped at 400MHz). So I wonder if that works now since we don't use the LP and Franco modded the G-cores to scale all the way down to 100MHz... Might be time for me to start playing with it. ;)
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Yeah I think I'm good at 15000 and 96.

Feels good. Smoothest my N7 has been yet.

Thanks guys.

Sent from my Nexus 7
[Nexus 7 Original Development] wisnuhadi23:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Guys, you are all amazing. I have been watching this topic and testing almost all the combinations you suggest. And the last one with 15/96 which osmosis suggested feels smooth as hell. Thank you very much. Thank you to franco who has made this possible.

I am going to see how the battery life goes. My nexus 7 is charging now and I'll wait until 100% and see if the battery life is good or not.
[Nexus 7 Original Development] FReaKRaNT:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

This was explained a few pages back.

Cheers, FReaKRaNT
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

BTW, I flashed 39 last night, charged fully, unplugged before bed.

I'm now at 15 hrs up time, 3 hrs screen on, and 62% battery left.

Steller.

Sent from my Nexus 7
[Nexus 7 Original Development] whitedragonz83:
I don't have an N7, but am generally curious about these values of 15/96/45/15; 1000 hsf for example. This feels like you are making interactive into a 2-step ondemand governor with the high cpu load requirement of 95+. With the galaxy nexus our cpu load is set to 65% with a 'race-to-idle' thought. Is there an architectural difference here that doesn't exist on the galaxy nexus? Why not just use ondemand with a cpu ramp on touch? If any of this has been explained already, I apologize in advance.
[Nexus 7 Original Development] wisnuhadi23:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Woow, that's great.

Just to make sure, are you using 15/96/45/15 hsf 1000 ?
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Yup

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Metallice thankfully clued us in a couple days ago that the way interactive works now is drastically different from the implementation we've currently got on the GN. Check out pages 327 and 328: http://xdaforums.com/showthread.php?t=1823671&page=327. And you're right, it does sort of work more like ondemand now due to the target_load; that's just the way Google's taking it now.

The g_h_l was never part of the race-to-idle issue though; as I understand it they're unrelated issues. The important thing for race-to-idle was always screen off max. :good:

That does bring up an interesting point though.. now that we are only using the G-cores, we should probably have a screen off max setting, eh? Capping it 500MHz or something. No rest for the wicked, franco. :p
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Ok I'm running 15/96/45/15;1000;row @416 and I do find it smooth however I'm not completely blown away. There is still some jittery and hiccups every now and then on the app drawer and desktop screens. Im going to try 20/99/30/20;1300;row @416 and see how it goes

Edit: I found that very aggressive on battery so I'm down to 15/95/30/15;1000@416 and I kinda feel like is smoother than os tuneables :p
[Nexus 7 Original Development] ÜBER™:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Very light usage today. Not bad if I say so myself. Stock values GPU at 484.
[Nexus 7 Original Development] osm0sis:
Hmm I'll try them out. Lowering the g_h_l would make it smoother (at the cost of battery) since it would jump earlier, but changing the m_s_t from 45 to 30 should make it quicker to come back down from the higher frequencies.. which should negatively impact performance (improving battery). :confused:
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

This sounds very good in theory I'm trying it now :thumbup:
[Nexus 7 Original Development] TheByteSmasher:
Real Quick... What does GPL stand for in the thread title?
[Nexus 7 Original Development] osm0sis:
http://en.wikipedia.org/wiki/Gpl

Google first please.
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

My first thought was making it more batt friendly but keeping the performance boost, that's why I was trying m_s_t at 30 but I got some frame drops sometimes so I'm back to 15/90/45/15;1000@416

I'm still wondering what if we go back to the stock Freq steps. Maybe that will help. What do you think?

Edit: 15/90/45/15;1000@416 feels definitely smoother on my tablet that my previous attempts. I'm pretty happy with this combo. Then again I think that the less Freq steps the smoother it gets :p
[Nexus 7 Original Development] TheByteSmasher:
I know about the GNU, I thought it might have something to do with the Kernel because I rarely see it in Threads. Thanks.
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I said that a few days ago, the lower speeds CPU speed steps are smaller and the higher speeds have a larger step (some by 140mhz) so the CPU isn't constantly jumping from one speed to the next. If the CPU isn't constantly changing any lag would be less apparent and quite possibly save battery life by doing so
[Nexus 7 Original Development] osm0sis:
Yup, I was saying I liked that idea too. If this were a democracy it'd get my vote. :) :p

---------- Post added at 07:48 PM ---------- Previous post was at 07:45 PM ----------

Check those posts I linked by Metallice.. 90 is the target_load so go_hispeed_load needs to be higher, at least by a few points margin.. I wouldn't want to put it much lower than 95 really. Putting it at 90 is likely "being mean" to the governor again. :(

Really what we need is to tweak target_load a bit. I'm thinking target_load 85, go_hispeed_load 95.
[Nexus 7 Original Development] joaquinf:
Yessir. I double checked the metallice post before going for 90 but i thought that 90 would be just fine because of this line "go_hispeed_load should

not be lower than the target load for hispeed_freq". Im going to raise it to 95 then

EDIT: ok so that bring me up to 15/95/45/15;1000@484 <-- bumped the gpu clock a bit
[Nexus 7 Original Development] osm0sis:
If you think about it though, with the target_load of 90 it's always trying to be AT 90% load, which means that if you also set that as your go_hispeed_load it will pretty much always be at or above your hispeed_freq. Maybe not "being mean", but definitely should be rough on battery. :)
[Nexus 7 Original Development] joaquinf:
That makes so much sense. Thanks :) Maybe franciso can add the option to tweak target_load on his app so we can play with that value too :victory:

EDIT: i'm loading trickster (and uninstalling franco's) and changing the target_loads value just for science :p and i'll report back
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I'm running the same gov control as you but with 416 gpu, I'm not sure if your GPU settings are right at 484 I'm sure metallise and osmosis talked about it working best being divided by some **** but forget exactly what, church back around page 305 and when you see I join here gpu clock speed is one of the first thing I ask and thus starts osmosis and metallaice discussing it
[Nexus 7 Original Development] joaquinf:
yes buddy 484 is the right value according to the /2 rule :) thanks. In fact, that's trinity's stock gpu value, which was my reference point for gaming performance comparisson

---------- Post added at 07:22 PM ---------- Previous post was at 07:15 PM ----------

Ok these are my settings with the tweaked target_loads to 85 and gpu@416. So far they everything is running smoothly. I'm going to do some tests and see what happens
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

I couldn't remember the numbers they came up with except 520. Im guessing at 484 battery drain is minimal but does it actually make ant difference being only 68mhz faster?

Edit

What does timer slack do?
[Nexus 7 Original Development] joaquinf:
Check here and here for the correct freq numbers (thanks to osmosis and metallice)

Well, i bumped it to 484 because that's what i use to compare between trinity and franco but i'm back to the stock 416 and the t_l at 85 :good:

EDIT: i have no idea about the timer slack though. Maybe someone else can enlighten us, please?
[Nexus 7 Original Development] osm0sis:
Actually just finished updating that post to reflect all the Metallice info. :good: :D
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][19 JAN] franco.Kernel - r39

Cheers. Just for an update on what I'm trying now is 15/95/30/15 hsf 800mhz @416gpu

Really we should slightly change this quick format to include hsf so its actually in order to how its displayed in the app with an @xxx for GPU so we end up with 15/95/800/30/15@416 as it might easier to type out but its up to you guys if that's a format youd find easy to read or not
[Nexus 7 Original Development] currydude:
Just received the 6.5.2 update. No more force closes
[Nexus 7 Original Development] Salv0:
Confirm what I said yesterday: no reboots with runnable. Let's test today :D
[Nexus 7 Original Development] osm0sis:
Nobody? ..I went with 102MHz since that's what the app prescribes.
[Nexus 7 Original Development] Metallice:
I would just stay at 100mhz (51mhz gets bumped up if you try to set it.) If you stick to 100mhz then the 51mhz slot will be used when the screen is off.
[Nexus 7 Original Development] osm0sis:
Really.. So by default the kernel is 100MHz min and 51MHz screen-off max, but set via the app to 102MHz the screen-off max also becomes 102MHz? That sounds sort of buggy.
[Nexus 7 Original Development] :
Here's CPU Spy after setting 1000/52 MHz with Interactive.

Usually the Kernel Updater shows 1300 MHz, not sure if it sticks.

r5 and Bugless Pete 2012-09-07.

Edit: Clock Speeds work after setting them again, but seem to randomly revert to 1300 MHz. I'll try to get a logcat
[Nexus 7 Original Development] gnam:
This kernel is compatible with Paradroid 2.1.1?
[Nexus 7 Original Development] brianpee:
I'm using it on 2.1 and there's no problem.
[Nexus 7 Original Development] Metallice:
No by default it is 102mhz min while the screen is on and 51mhz min while the screen is off. There's no max involved.

If you set the min to 51mhz while the screen is on it will bump up the min to 100mhz because it won't go that low when the screen is on and when the screen goes off the min will go back down to 51mhz. If you set the min to 102mhz the min will be 102mhz for both screen on and max.
[Nexus 7 Original Development] osm0sis:
Fair enough, I think I get it now, but something still seems wonky when you can't get back to that once you set it to 102MHz.
[Nexus 7 Original Development] CharliesTheMan:
It's not just that way with this kernel, it's that way with all of them I know of.

---------- Post added at 04:22 PM ---------- Previous post was at 04:19 PM ----------

Many of the developers of custom roms with CPU control's in the rom's settings used to have disclaimers or posts somewhere in the thread to this effect. It's been a while since I read a disclaimer honestly, no idea if devs are starting to eliminate the problem but not allowing the user to see that step or if it's still that way.

It's such a habit to bump mine up to two or three hundred I don't ever really pay attention.
[Nexus 7 Original Development] :
Settings don't stick.

I'm still unable to get the OC settings to stick. Currently running Stock JRO03D with r5, and the settings seem to revert to 1300 MHz / 100 MHz min/max, Interactive Governor and Balanced whenever I restart the app.

Only troubling (as far as I can find) bit of log when changing a setting is this:

D/dalvikvm( 2031): Unable to stat classpath element /system/framework/framework2.jar

Happened when choosing 1000 MHz as the max clock speed.

Also, when starting up I find these:

I/ActivityManager( 332): Start proc com.franco.kernel for broadcast com.franco.kernel/com.marclandis.francokernel.BootReceiver: pid=1240 uid=10077 gids={3003, 1015, 1028}
E/Trace ( 1240): error opening trace file: No such file or directory (2)
I/System.out( 1240): [franciscofranco] ColorControl exception: java.lang.NullPointerException
I/System.out( 1240): [franciscofranco] GammaControl exception: java.lang.NullPointerException

D/franco.Kernel Updater - OC/UV( 1240): Max Freq: 1000000

I/ActivityManager( 332): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.franco.kernel/com.marclandis.francokernel.LicenseCheck bnds=[400,586][400,586] u=0} from pid 587
I/LicenseChecker( 1240): Using cached license response
W/InputMethodManagerService( 332): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@4155c8d8 (uid=10071 pid=587)
I/ActivityManager( 332): START {cmp=com.franco.kernel/com.marclandis.francokernel.Main u=0} from pid 1240
D/AndroidRuntime( 2107):
D/AndroidRuntime( 2107): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 2107): CheckJNI is OFF
D/dalvikvm( 2107): Unable to stat classpath element '/system/framework/framework2.jar'
D/dalvikvm( 2107): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 2107): Added shared lib libjavacore.so 0x0
D/dalvikvm( 2107): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 2107): Added shared lib libnativehelper.so 0x0

Still, it always reverts to 1300 MHz.

So, I don't have a framework2.jar, should it say framework.jar instead?

EDIT: SetCPU settings don't stick either though.
[Nexus 7 Original Development] osm0sis:
works for me, just selecting the apply on boot 102 sticks as my min
[Nexus 7 Original Development] Metallice:
Framework2.jar is a CM10 file I believe. What ROM are you running?
[Nexus 7 Original Development] :
I'm running on Stock JRO03D as I linked in my first post. :confused: