yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] cabagekiller:
I found out how to make this kernel faster. You rub cheetah blood on your tablet and sacrifice a goat.
[Nexus 7 Android Development] Metallice:
I can't imagine a scenario where that would be useful.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] cooldoud:
Think maybe i wasn't clear here, i meant adjustable maximum lp frequency ? Idea being that my LP seems to tolerate a Max frequency higher than 666, so why not push it a bit more.

But yeah I'm not sure how useful that would be really, fell free to leave it out. Maybe that will motivate me to try and compile this kernel myself too, haven't done that since my university days :)
[Nexus 7 Android Development] katestar:
Looking at trickster mod and I like to have my gpu at 600mhz with 1225mv as heat isn't bad and it's only 25mv above stock for my binned SoC, forgetting of course most heat is from the charge/ discharge of the resisters and increasing the frequency means more charge/discharge cycles in the same time meaning more more heats produced at higher frequencies even at the same voltage. But the heat out put is well with in safe limits. Away noticed the OC frequency replaces 416mhz. Meaning when the gpu scales it may be using 600mhz when it's not needed. The frequencies seem to be 234,285,332,380 and then your OC of say 600mhz. I'm not sure on the geforce upls scaling logic but that seems quite inefficient. Wouldn't it be better to spread those frequencies out a bit and adjust scaling logic to suite new frequencies. Or if it's possible stick in a couple new frequency slots. As 380 to 600mhz is quite a jump. Just thinking it could be a nice idea to save power for those who would like to overclock there gpu's a nice amount. :)
[Nexus 7 Android Development] Metallice:
Because I guarantee your LP core can't handle 860MHz, the next slot up. I could add a ton of inbetween frequency slots, but that would just be wasteful.

Sent from my Nexus 7
[Nexus 7 Android Development] Metallice:
Yes I've considered all of that before, but the current method is still the best way to do it.

For one your suggestion to adjust the lesser frequencies would be difficult to impossible. Also those are the only GPU frequencies allowed by PLL clock dividers so the increases per freq would have to be all the way up to the subsequent freq. Additionally, I'm not sure how tegra scales GPU, but unless it scales via a target frequency it would also be an unneeded waste of battery.

Your second suggestion to insert additional slots after an overclock would be a good way to do it but is impossible.

Sent from my Nexus 7
[Nexus 7 Android Development] adstraylight:
I've noticed that setcpu offers an adjustment to ondemand that is not available in trickster: ui sampling rate, independent of straight 'sampling rate'. Is this useful or a red herring?
[Nexus 7 Android Development] Metallice:
It does nothing. Leftover from something I don't use / don't have enabled.

Sent from my Nexus 7
[Nexus 7 Android Development] VenomTheCat:
I am using a28 and PA 2.99 beta9.5 for me the difference between a25 and a28 on battery is not too significant
[Nexus 7 Android Development] Metallice:
Yeah there's no reason to be on a25... a28 is just like it but better.

Sent from my Nexus 7
[Nexus 7 Android Development] johnnyman25:
This is my battery life with a28 ondemand default settings.im very happy with it.thx for this awesome kernel.

The only prob i have is ui scroll lag.when i leave it for 2 secs to one homescreen then scroll to another it lags.
[Nexus 7 Android Development] AglarondTX:
I had the same problem, but fixed it in the trickster mod settings:

Scheduler row

Buffer 4096

Min 204,000

Max 1,400,000

Governer ondemand

Ondemand settings:

Down differential 3

Up threshold 85

Thanks to everybody here for your tweak posts. I used info from several posts to put these together. Everything is butter smooth now.

-mS
[Nexus 7 Android Development] johnnyman25:
What about battery life with these settings?thx for sharing.
[Nexus 7 Android Development] jamesst20:
If I were you, I would only change the threshold from 95 to 90 which should fix lags issue pretty well without breaking really much battery life :)
[Nexus 7 Android Development] AglarondTX:
I get about 10 hours or so of screen on time. That usually lasts me a couple of days.

Running a28, by the way.

-mS

---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------

I tried that and the lag issues were still there but definitely better. If you have a problem with battery life, 90 is good, but 85 works well for my uses.

-mS
[Nexus 7 Android Development] Frankie1588:
I just flashed a28 and used these settings. 10 hours of on screen time would be fantastic! Are you using WiFi the entire time? Hopefully I can achieve the same results. :)

Thanks for posting!
[Nexus 7 Android Development] AglarondTX:
I am running WiFi the whole time and don't have the 3g radio. I'm also running AOKP right now, if that makes a difference. Was seeing similar results with the Paranoid Android beta.

-mS

---------- Post added at 10:14 PM ---------- Previous post was at 10:09 PM ----------

Not sure. Mine shows 1.6 as the max, but I had stability problems that high. Looking at cpu usage, I spend very little time at 1.4. I'm guessing games would eat up a lot more, but I'm not much of a gamer.

-mS
[Nexus 7 Android Development] Frankie1588:
I think I just forgot to save the settings. I reapplied it and it is showing 1.4 as the max. It did show 1.6 as being the absolute maximum, but it was previously saying 1.3 was the maximum I had it set to. All figured out though.

I am on Paranoid Android Beta 9 myself so that is good to hear.

Thanks!

EDIT: I change the down differential to 3, but it doesn't seem to save this setting. I keep going back and it says 5. Any reason for this?

I also have it set to run at boot, but the minimum will refuse to go to 204000 after a reboot. It always defaults to 340000. Any way to fix this?
[Nexus 7 Android Development] tazwik:
smooth rom with bricked kernel

Is this compatible with smooth ROM with bricked kernel?
[Nexus 7 Android Development] NicoGa:
Are you applying your new setting in Trickster Mod (a button at the top-right)?

Concerning the min freq this have been over discussed in this thread and I invite you to use the search function ...

Envoyé depuis mon Nexus 7
[Nexus 7 Android Development] Frankie1588:
Yeah, I actually hit the button at the top-right several times and it always goes right back to 5 when I go back into the menu. It saves the up_threshold of 90 from 95, but won't save the down_differential from 5 to 3.

I will use the search regarding minimum freq.
[Nexus 7 Android Development] FierceMist:
Do you even realize what you just asked?
[Nexus 7 Android Development] tazwik:
Not really. :)
[Nexus 7 Android Development] hyperxguy:
been running SmoothROM+a28, everything is fine. However, every time I selected a route to go in NavigonGPS, it FCs. I threw on 4-5 different kernels and none of them has this issue. Man, I like M-kernel very much (as it appears to have the best battery life for me). Luckily, a25 works fine.
[Nexus 7 Android Development] icytrey:
Doesn't ever stick for me either:confused:
[Nexus 7 Android Development] federico72:
Yep. Happens to me too with the older PA rom.

Reduce considerably the lag and subtract just a bounce of battery's minutes.

+1. Is the unique setting I can't change. I tried to reboot and apply the setting but wont apply.
[Nexus 7 Android Development] Stuphologist:
Me either.
[Nexus 7 Android Development] _DrG_:
Its sampling down factor to set to 3 anyways, down differential does not move from 5 seems baked in
[Nexus 7 Android Development] seandarcy:
On n7 3g, with a28, temasek v16, trying to set Fsync, but:

ls /sys/class/misc/fsynccontrol

/sys/class/misc/fsynccontrol: No such file or directory

Nothing close under /sys/class/misc.

How do we (can we?) set Fsync?
[Nexus 7 Android Development] sNoxious:
Trickster Mod on Play Store?
[Nexus 7 Android Development] johnnyman25:
yes!!

https://play.google.com/store/apps/...xLDEsImNvbS5iaWdleWVzMHgwLnRyaWNrc3Rlcm1vZCJd
[Nexus 7 Android Development] Metallice:
Yeah I just checked with solid explorer. /sys/class/misc/fsynccontrol/fsync_enabled definitely exists for me.

You could also do /sys/devices/virtual/misc/fsynccontrol as well.
[Nexus 7 Android Development] AglarondTX:
Consider me corrected. Ignore my post from last night. I apparently didn't actually apply the 85 threshold. When I did, it got buttery smooth, but I could almost watch my battery count down. Looks like 90 is a sweet spot.

Apologies for the bad info.

-mS
[Nexus 7 Android Development] VenomTheCat:
a29 flashed and working

Here is your BUTTER!,,

OC to 1.9 performance governor and GPU at 700 my N7 seems to handle it even though it get warm quick! And I am not keeping these settings to know what the battery usage is

Now I am back to default/recommended settings I hope the battery doesn't suffer with this release it seems smoother than a28
[Nexus 7 Android Development] luke05dee:
Managed to get 1.9ghz stable at 1225mV which is very low compared to defaults and heat isn't bad :eek: But for battery can't imagine 1.9 is going to be good at all, even undervolted a lot so back to 1.5ghz. I know quadrant is crap but it's the only benchmark I have installed along with glbench. I managed to get 7050 :D and 16465 on the cpu score. Although I seem to be getting a larger memory score on quadrant with this release, as in normally I get about 3500, but seem to be getting about 3800 on this, maybe quadrants just being it's usual temperamental self :D
[Nexus 7 Android Development] denzel09:
1.9 GHz really? :confused::confused::confused: 1.9 GHz :p:p:p

but it's stable without sod or restart ? Really sure?
[Nexus 7 Android Development] lrefra:
Min Frequency CPU in Trickster say 340. Before was 102

Now increased?

PD. Sorry my bad english
[Nexus 7 Android Development] VenomTheCat:
Min should still be 102 mine is
[Nexus 7 Android Development] guitarhero2:
Guys i think i have a problem. My brightness is changing costantly, it seems i have autobrightness but i don't have it checked! Is it supposed to be like this?
[Nexus 7 Android Development] S3tArtist:
It not supose to be like that. I have solid brightnes. U tried to check and uncheck autobrightnes?
[Nexus 7 Android Development] Metallice:
Set your min and hit apply. Don't worry about it again.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Does disabling WiFi stop it?

Sent from my Galaxy Nexus
[Nexus 7 Android Development] _DrG_:
Using trickster turn smart dimming off, install lux from playstore. Win.

xda n7
[Nexus 7 Android Development] Metallice:
Yep. Its either PRISM as you said or the WiFi GND issue. Scotch tape FTW.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] seandarcy:
Tried that. Maybe I'm blind, but where is Fsync set in Trickster Mod?
[Nexus 7 Android Development] davisac:
The last tab "Specific." There's a toggle switch for On/Off.
[Nexus 7 Android Development] seandarcy:
Well, not on mine. Odd.

Is fsync_enabled the default? If so, I'm ok.

BTW, others suggested Fsync could be enabled in Trickster Mod. I didn't see where you could do that.
[Nexus 7 Android Development] Metallice:
Sent from my Nexus 7
[Nexus 7 Android Development] johnnyman25:
so how is battery with new version a29 compared with a28?
[Nexus 7 Android Development] oldlight:
Why don't you try it your-self, mate?

I can see my N7 run smoother than in A28.

Battery is not a problem anymore :D

^^
[Nexus 7 Android Development] johnnyman25:
i just installed it!!lets see now!! :)
[Nexus 7 Android Development] Metallice:
The answer to "How is performance/battery with the new version?" is and always will be - "you tell me".

Remember guys, these are alphas, meaning you all are testers. The process from alphas -> milestone release requires "mostly" unbiased, uninfluenced (is that a word?) feedback.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] stijndebruin:
Gonna test now!!! Thanks.
[Nexus 7 Android Development] sNoxious:
I remember Metallice said that a29 is for the people who loves a26? Is that true? :)

Sent from my Samsung Galaxy S III
[Nexus 7 Android Development] Metallice:
I've always gotten memory scores from the 3400s to the 3800s. Normal but still good . Memory scores will go up some with the higher g cpu rate too.

Also just a useful tip...

You can compare battery use (which probably tells you something about heat generated and overall "safeness") when combining overclocking with undervolting with f*v^2

For example if you wanted to overclock to 1.9GHz but use the same battery as 1.5GHz at 1300mV you would do:

(1500000000)*(1.3^2) = (1900000000)*(x^2)

x = 1.15508 or 1155mV

So you would want to run a 1.9GHz at 1155mV if you want to it to use approximately the same amount of battery as 1.5GHz@1300mV

Sent from my Nexus 7
[Nexus 7 Android Development] Metallice:
Read two posts above yours please. Honestly flashing a kernel takes no time. You can find out on your own much faster than waiting for a response.

Sent from my Nexus 7
[Nexus 7 Android Development] stijndebruin:
A29 is indeed smoother then 28 for me. I like. Overall the kernel performs better then others I tried recently. Faux an Franco.

Thanks again for the hard work!
[Nexus 7 Android Development] 93foxgt:
As beautifully as m-kernel runs on the n7 , I wish there was one for my gnex. :D
[Nexus 7 Android Development] xateeq:
OP What are your thoughts about LP core.

Is it just a marketing trick to sell more goods or does it actually hold ground.

I am asking such questions to almost every kernel developer to understand how it actually work.

As for now, it is super battery efficient ninja core that taker over when small process need to do some thing and wont bother other big cores.

But some kernel developer seams to disable it, Does disabling it cause any good or just a hope towards saving little more battery ?

Just let us know what you think of LP core.

Thanks.
[Nexus 7 Android Development] Metallice:
Sampling rate - Technically it's the sampling interval, but still that directly determines the sampling rate. It's a lot easier to enter 50000 as the sampling rate instead of 1/50000. Lower numbers means more responsive scaling. Overhead is pretty minor, but you don't want the system to become TOO responsive. If it's too low then the freq will be bouncing up and down rapidly, changing with every minor load fluctuation, which can lead to degradation in both performance and battery.

Sampling down factor - Your description of how it works is correct, but it's not there to decrease overhead when load is high, but to prevent scaling down too quickly as load in reality can be variable. You don't want the cpu to scale down if there's only a temporary decrease in load, otherwise you'd have to scale back up immediately after dropping down.

Up Threshold - That's not right at all. There is no such "freq_step". if (max_load_freq > dbs_tuners_ins.up_threshold * policy->cur) then go to max freq. If (max_load_freq < (up_threshold - down_differential) * current_freq) then go to (max_load_freq / (up_threshold - down_differential)).

Down differential - It's an up_threshold modifier when scaling down to prevent triggering the an increase back up to max freq too quickly afterwards. Your description appears to be right.

Your final conclusion is wrong. A LOW down differential and a LOW sampling down factor will make the cpu scaling twitchy and hyper. A HIGH down differential and a HIGH sampling down factor will make the cpu scaling smoother, at the cost of battery. Up threshold is what controls "butter", although smoothness does play a role.
[Nexus 7 Android Development] davisac:
I can't seem to set the CPU min below 340mhz. I'm trying to take it down to 102 with 1100 max.

In Trickster when I click the check mark it says "applied successfully" but when I close and reopen the app it's always back to 340.

I'm using the default settings other than turning off F-Sync.

Thanks.
[Nexus 7 Android Development] _DrG_:
It'll be set mate, if you need to 'see' it play some sound first then go into trickster to see the 102

xda n7
[Nexus 7 Android Development] davisac:
Have some music playing and watching the live meters in Trickster one core just rests @ 340.

ETA: now it's dropping down to 102. Thanks.
[Nexus 7 Android Development] ezas:
And/or get the well named Cool Tools from the Play Store and watch it in real time and you can see your device use 102.
[Nexus 7 Android Development] Metallice:
If you have music playing the min will be 340. One it stops it reverts to 102.

A touch sound is initiated when clicking on trickstermod to open it, so it reports the min to be 340, even though it drops back down the 102 shortly after.

If you set it to 102 and hit apply you should be good.
[Nexus 7 Android Development] AglarondTX:
Running a29 now and it's great. Very minor tweaking got my tablet to a nice, smooth point. Will follow up later with battery life as I haven't really been able to put it through its paces, yet.

-mS
[Nexus 7 Android Development] johnnyman25:
Can u post ur tweaks pls? Thx :)

now something else.when i scroll cpu speed is at 860mhz and not 666mhz like a28 version.anyone have same issue?
[Nexus 7 Android Development] Stuphologist:
Thanks! I found three different descriptions that didn't agree. I think I understand what's going on now. Thanks for the help.

Dave
[Nexus 7 Android Development] Metallice:
You're very welcome.
[Nexus 7 Android Development] zachf714:
The person that was talking about Gp the lp core if i remember right the lp core is the 5th core in a quad core processor that is under the clocking of the other 4 for when you are doing less processor intense tasks and while out is in sleep/deep sleep :) it is basically a backup core

Sent from my Nexus 7 using Xparent ICS Tapatalk 2
[Nexus 7 Android Development] azoller1:
1.9 GHz seems scary but if its needed its needed thanks for the update!
[Nexus 7 Android Development] AglarondTX:
Scheduler row

Buffer 4096

Min 20,4000

Max 1,400,000

Down differential 10

Up threshold 90

It's very smooth with AOKP. It doesn't look like my battery has taken much of a hit, but if battery life is your priority, don't use these settings. There are definitely more conservative settings. That said, I should still get a couple of days out of a charge with my usage.

-mS
[Nexus 7 Android Development] johnnyman25:
thx for the settings but battery is the priority for me and smooth ui scroll.what settings can i use for this?thx again!
[Nexus 7 Android Development] Metallice:
So... which is it? Is your priority battery or smooth UI?

Sent from my Nexus 7
[Nexus 7 Android Development] N@th_OC:
If i understand well, he want both. :eek:
[Nexus 7 Android Development] AglarondTX:
You'll have to pick one. One comes at a sacrifice to the other.

-mS
[Nexus 7 Android Development] dstryrwiz:
I think battery is the first priority, but he doesn't want to fully sacrifice smooth performance in the process.

I'm somewhat in the same spot, I like having as long a battery life as possible, however I don't want a situation of diminishing returns. If I have the opportunity for a bit of a leap in UI performance in exchange for a small loss in battery life, then I would gladly take it, but I wouldn't want to take a huge cut in battery life for minimal performance gains.
[Nexus 7 Android Development] notko:
In system tuner just click clear button and you will be on the stock voltages on kernel you installed.
[Nexus 7 Android Development] Juzman:
Just flashed a3 (332/620) + CPU UV from Jay's Buttery Goodness and Nexus Louder. Running fine so far, keep up the work!
[Nexus 7 Android Development] Evo_Shift:
Is an LP of 475 underclocking the LP core? Is 500 stock?
[Nexus 7 Android Development] B-Man2005:
im running glaze 2.0 android 4.1.2 rom and i want to disable fsync via init.d script but it doesnt work

any suggestions ?
[Nexus 7 Android Development] Ricolein_Rico:
"stock voltages on kernel you installed" does not equal stock voltage of stock kernel but that is what kzakhar wanted to know...
[Nexus 7 Android Development] Kearkan:
Ah, ok, thanks for clearing that up for me.
[Nexus 7 Android Development] mrbeardy:
Giving a3 446/620 a try now. Youre updating these quicker than i can drain the battery! :)
[Nexus 7 Android Development] Metallice:
Some of the hotplug tweaks I made for a3 were heavily battery focused. Good to know that they appear to affect performance for you. Thanks for the feedback.
[Nexus 7 Android Development] kzakhar:
They do: a3 @ 1.5 GHz is slower than a2 @ 1.3 GHz in benchmarks and subjectively feels not as smooth.

Unfortunately, this is not the only feedback I've got: I'm afraid, a3 446/475 causes the sound to disappear the same way as a2 did :( Assuming that 475 MHz is the stock LP frequency, it's not the LP overclock that is causing the issue.
[Nexus 7 Android Development] mrbeardy:
I ran a few antutu benchmarks and the scores I had were the same as i had been getting before using the a3 kernel.

446/620 a3 but no change in voltage.

Antutu:

~12300 @ 1500mhz

~13300 @ 1600mhz
[Nexus 7 Android Development] Metallice:
Benchmarks seem fine to me. Is 5800 at 1.5Ghz bad? I dunno.

And give the new kernel some time. You've had it for less than a day.
[Nexus 7 Android Development] Metallice:
Is that good bad or normal?
[Nexus 7 Android Development] kzakhar:
I was consistently getting 4.4-4.5k in Quadrant with a3 (446/475). I will check again, may be I did something wrong; but had to flash PA kernel back — will need sound tonight :(
[Nexus 7 Android Development] mrbeardy:
Stock kernel and speeds scored under 10000 in antutu if i remember correctly.

Quadrant scores:

4400 @ 1500mhz

4800 @ 1600mhz
[Nexus 7 Android Development] DRSdroid:
a2.1 - secret extreme-battery version is working great for me in PA 2.5. Very fast, very smooth. I'm clocked at 1400-102 (deadline & ondemand) via setcpu. I'm using Jays Tweaks w/o ZRam and I undervolted 30mV across the board. When i bump the clock speed to 1.6ghz i can get a 5700+ quadrant score.

Most of my scores are a bit lower than they were on motleys in 4.1.1, but the speed and responsiveness is flawless so it's definitely not resulting in any noticeable drag. Scroll speed in particular seems to be REALLY fluid and battery life has been great. I flashed it last night and i haven't had any audio issues or lockups/crashes/FC all day.

Thanks for your work!
[Nexus 7 Android Development] batman368:
a3 is awesome, no sound issues, quadrant gives 5700 at 1.5ghz, but much more important is absolute smoothness of rom. i use pa 2.5 with jay's buttery stuff with 128zram. great combination, super smooth. and battery is great too :)
[Nexus 7 Android Development] kzakhar:
4400-4500 — this is what I was getting at 1.5 GHz, didn't try 1.6 GHz though.
[Nexus 7 Android Development] mrbeardy:
Im not worried about benchmarks anyway, i really like how this kernel performs. It doesnt seem to get as hot under load as it would with older kernels and it never feels slow.
[Nexus 7 Android Development] stonebear:
How do you do that? Reflash the rom without wipe or is there an actual flashable stock-PA kernel?
[Nexus 7 Android Development] Metallice:
Neither am I, but its still strange to see such a discrepancy. I'm consistently getting 5700-5900. Oh well.
[Nexus 7 Android Development] prestige777:
Thank You Metallice, this flies and is incredibly stable once it sets in. I get a freeze up sometimes on boot but then the next boot is fine and it takes everything I can throw at it. I had trouble with system tuner it keeps showing a slot for 1.8mhz but it freezes on trying to move the slider past it onto 1.9. I tried other controllers and they show it skipping 1.8mhz which I figured must be right. Im using no frills since it seems the most stable with it, is there a particular controller you recommend?