yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Metallice:
Yeah there is no 1.8 slot. For some reason it was way less stable than 1.9... made sure everything was set up right with the dividers and everything but still.

I recommend trickstermod if you want something to do it all. No frills is great though.

As a side note...

At the moment none of them support the new parameters for the next kernel version... current ondemand removed to become part of new touchdemand governor. Ondemand back to stock with added two phase freq. Touchdemand has some new parameters -.touch_floor_freq, touch_floor_time, and Touch_factor. Unfortunately right now setcpu seems to be the only app to show them... other than a file explorer of course.

Ondemand was just diverging to much... had to rename it and bring back old ondemand for those that might want it.

Sent from my Nexus 7
[Nexus 7 Android Development] prestige777:
That's interesting, maybe that is why it is so much more stable than what Clemsyn had. I could run 2ghz as long as I didn't push it too hard and 1.9 was only slightly better, but this is extremely stable. So far it screams on ESPN which seems to take control of tablet for some reason, I guess it's the java script they use anyway, this is amazing really. ;)
[Nexus 7 Android Development] johnnyman25:
Like u said my friend.so can anyone recommend some governor settings for this purpose?rly appreciate it. :)
[Nexus 7 Android Development] danielsf:
Bean running all your kernels since 22 in tern and I know this is a useless post, but just wanted ro let you know that this one is a definite improvement over a28 for me. In a28 and below I would often getting full 1-3 second system hangs where my tab wouldn't accept any input in random situation on stock and PA ROMS. My set-up is always the same, Ondmand, 1.5ghz and GPU at 600mhz with the lowest voltages for GPU, CPU, LP and RAM my SoC can handle, the only variable was your kernel versions. So unless there was something userpace that I wasn't able to find that has stopped slowing my device down all of a sudden, this new version is my favourite so far :) But on A29 things have been flawless for me, thanks :)
[Nexus 7 Android Development] CreepyE:
A29 is the best I've used so far. A28 caused way too many sod's for me, but this thing on ondemand with a 1.9 Max has been flawless. Thanks a ton for all your hard work man
[Nexus 7 Android Development] guidocioni:
Is this battery life normal? I got an huge drain over night cause something is waking up the device,I think.

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Android Development] denzel09:
touchdemand is in a29 or will be in a30? And can you please recommend me which parameters are ok for be stable to 1.9 like voltage etc? Thanks for amazing kernel
[Nexus 7 Android Development] bcvictory:
I know everyone's N7's are different but how much are you undervolting different things? I have my MPU -50 and my N7 can handle it fine. Does that mean everything else can go down that much?

Also, can somebody run a Antutu Benchmark on how 1.9 on performance goes?

I don't know why but My N7 can't even handle 1.7.
[Nexus 7 Android Development] gregdeberg:
1700 Mhz big probem

Hello everybody :)

Nobody had boot looping on 1700 Mhz ?

I could test 1900 mhz for a few minutes before my nexus...reboot.

Thanks
[Nexus 7 Android Development] berkos:
Mine is stable on -120, still I'm on stock clock
[Nexus 7 Android Development] Adinaky:
The only setting I can't change is down differential (stuck at 10). Do you have any ideas?
[Nexus 7 Android Development] cooldoud:
I see that you've got options for LP overclock up to 740Mhz in the sources, which kind of makes my initial request moot... compiled and installed it now, seems to be working fine so far!

Anyway, thanks for having these options in the sources, very helpful :)
[Nexus 7 Android Development] SkyboneNoya:
Feel like a29 is a25 but quick! 1.5 is more than enough for me, under volt and long lasting. Thanks!
[Nexus 7 Android Development] iamnotkurtcobain:
How can I oc and uc gpu? Which app?

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Nexus 7 Android Development] davisac:
Trickster MOD
[Nexus 7 Android Development] fossean:
I'd also be interested in some data on this. Is it advisable to undervolt RAM / GPU / LP by the same amount as MPU?

If anyone wants to share their voltages it would be appreciated.:)
[Nexus 7 Android Development] thisguy23:
So this is what I've been using the last few days. Stable. CPU 51-1500 ondemand. Gpu 446 with pictures below. I'm going to keep going to see how low I can get stable.
[Nexus 7 Android Development] denzel09:
Trying a29 from a while and atm i think it s better kernel for nexus 7 without problems, any.

waiting for touchdemand ;)
[Nexus 7 Android Development] Metallice:
Something woke your device up. You can see that right under the graph. Use better battery stats to figure out what.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] iamnotkurtcobain:
Thanks buddy

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Nexus 7 Android Development] Metallice:
Make sure that there's a 740 slot in the frequency table or else it will still only go up to 666.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] denzel09:
Metallice touchdemand will be better than ondemand?
[Nexus 7 Android Development] cooldoud:
Yep, there are entries in both tegra3_clocks and tegra3_dvfs. Thanks again!
[Nexus 7 Android Development] denzel09:
metal why you dont reply to my post never? :(
[Nexus 7 Android Development] VenomTheCat:
Give him a break! He is not glued to this thread answering stuff all day long!

Besides what kind of question was that for you to post?!?!? This is all experimentation to see what works better until we have a chance to test it there will not be any way of knowing if its better or worse also if he knew it was worse why would he release it.
[Nexus 7 Android Development] dotnetnightmare:
Great job on a29. I was an avid a26 user.
[Nexus 7 Android Development] Metallice:
Thank you. Spot on.

Also a29 ondemand is 2/3 of what a30 touchdemand is anyway.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Johnny424:
A-29 working great here..thank you for your continued work Metallice ..best n7 kernel by far imo..:D
[Nexus 7 Android Development] Allosaur:
A29 is the best kernel yet. Great work. I tend to clock to 1100 Max and undervolt so don't look for super silky performance yet this kernel is flawless.
[Nexus 7 Android Development] EvanA:
I'm attempting to compile the latest sources from alpha-mr1 and I'm getting this error.

LD arch/arm/mach-tegra/built-in.o
/home/evan/Kernels/toolchain/linaro/android-toolchain-eabi/bin/arm-eabi-ld: error: arch/arm/mach-tegra/board-grouper.o: multiple definition of 'tegra_usb_hsic_host_unregister'
/home/evan/Kernels/toolchain/linaro/android-toolchain-eabi/bin/arm-eabi-ld: arch/arm/mach-tegra/board-enterprise.o: previous definition here
/home/evan/Kernels/toolchain/linaro/android-toolchain-eabi/bin/arm-eabi-ld: error: arch/arm/mach-tegra/board-grouper.o: multiple definition of 'tegra_usb_hsic_host_register'
/home/evan/Kernels/toolchain/linaro/android-toolchain-eabi/bin/arm-eabi-ld: arch/arm/mach-tegra/board-enterprise.o: previous definition here
make[1]: *** [arch/arm/mach-tegra/built-in.o] Error 1
make: *** [arch/arm/mach-tegra] Error 2

Using the latest linaro toolchain snapshot. Ideas?
[Nexus 7 Android Development] Metallice:
Fix your config. Disable support for enterprise board under system type.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] ace-user:
just flashed a29 and i must say, it's really smoooooooooooth...lol...will test more for battery life...
[Nexus 7 Android Development] scottx .:
Hey Metallice, been a while. Finally sold that Galaxy Tab and snatched up an N7. Good to be here. Tons of the best development.

I'd run that kernel but I prefer aokp :)
[Nexus 7 Android Development] Metallice:
What about aokp?

Sent from my Nexus 7
[Nexus 7 Android Development] cooldoud:
Well AOKP's great... and you can use M-Kernel to make it even greater ;)

Running latest AOKP PUB + M-Kernel, great combo IMO
[Nexus 7 Android Development] scottx .:
Thought I read in the OP that it wouldn't work with aokp/cm. I shall reread.
[Nexus 7 Android Development] 93foxgt:
Using AOKP pub build with this kernel and it runs awesome.
[Nexus 7 Android Development] johnnyman25:
When i must stop messure battery life?when i say when i mean how much %.10% 5%?my eng sucks sorry.....

so here is my batterylife with a29.all of it was surfing and little movie watch.
[Nexus 7 Android Development] k29er:
Just flashed a29. The CPU voltage listed by trickster is just a starting point for over clocking? Or will some be stable at all the voltages this kernel sets? 1175mv for 1700mhz? I hope nobody is stable at this or I have a very bad n7.
[Nexus 7 Android Development] geroxx:
Hey guys,

everything works fine so far!

But it is possible that gpu undervolting is limited to a special value? i have set 900/850/600mV at all GPU frequencies but it works without any problem. Something must be wrong...

- geroxx -
[Nexus 7 Android Development] EvanA:
Ah thanks. It turns out I wasn't even using the right config file. I was using motley's instead of yours.
[Nexus 7 Android Development] Metallice:
Core voltage is a single voltage rail. The core will run at the highest voltage requested by the individual component dvfs. You could even set the voltages for the GPU to 0 and as long as the other components keep requesting sufficient voltage the core will run at that voltage and the GPU will work fine.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] thisguy23:
So then manually setting core gpu voltages is pointless? What about lp voltage, can is be lowered?
[Nexus 7 Android Development] Metallice:
No. Not at all. I never said that. Please read what I wrote again.

EMC, RAM, GPU, LP, and other parts of the core all run at the same voltage...whatever is the highest voltage needed/requested at the time.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Stable for me. Voltage variant 2 BTW.
[Nexus 7 Android Development] GoldElocks:
Just flashed a30 and so far so good. Will need some time to test it out but the change log looks really good. Was running a29 for last week with heavy usage and although battery wasn't the best it was very smooth. Sounds like a30 should improve upon battery slightly while keeping the smoothness and hopefully adding some more. I like the stock touchdemand governor parameters on a30 better too.
[Nexus 7 Android Development] denzel09:
Flashed a30, for now perfect :beer:
[Nexus 7 Android Development] FReaKRaNT:
+2

Cheers, FReaKRaNT
[Nexus 7 Android Development] element800:
Haha big troll, just flashed A29 30 minutes ago, now check this thread again A30 had been releases ;D

OT : Love it so far, verry smooth ;)
[Nexus 7 Android Development] sert00:
very good update metallice!

Tomorrow i will contact the trickster Devs to see what they could do with new options,i'll let you say what they will ansewer me(i'm IT translator\beta tester)
[Nexus 7 Android Development] ezas:
Loading a30 now. Reading the new features I'm glad to see you maintaining some battery saving features. A good balance of perf and battery life (and awesome stability) have always been a big draw to this kernel for me.

BTW saw your post about giving people butter in the PA thread. Good post.

<><><><><><><><><><><><><><><><><

Swyped from my N7

Current: PA 2.99 b9.9 & M-Kernel+ a29
[Nexus 7 Android Development] dstryrwiz:
So far a30 feels even more responsive than a29. With the new touchdemand governor I'm looking forward to seeing the new tweaks that this opens up for people to be able to do.

EDIT: I just noticed that Westwood+ isn't listed on Trickstermod? Is that by fault of the app?
[Nexus 7 Android Development] Metallice:
It's there. Just checked.
[Nexus 7 Android Development] johnnyman25:
its necessary to do wipe cache and wipe dalvik cache before install a30?im on a29 now!thx.
[Nexus 7 Android Development] scottx .:
Just flash the kernel and reboot.
[Nexus 7 Android Development] johnnyman25:
thx my friend!

edit:using the a30 version for 2 hours.first time things are so smooth and battery life seems so good!thx metallice for this awesome kernel!!! :)
[Nexus 7 Android Development] bjcrj:
Hey metallice, just flashed a30. Been using it for an hour or so......simply awesome! Thanks for your time and work!
[Nexus 7 Android Development] Leonhan:
Just flashed a30 and my tab is so smooth now! Just some questions though:

What does the touchdemand governor do differently than other governors? And why is it that everytime i reboot my device,it goes back to 1500mhz and fsync on even though i set it on boot(using trickstermod,and changed values to 1300mhz and fsync off)?
[Nexus 7 Android Development] Metallice:
Thanks. To answer your questions...

1. Did you read the change log?

2. That's not really related to the kernel, but try adding a delay to set on boot. Also make sure you actually set it on boot. Top right of app.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Nosferatu.:
a29 and now a30 are probably my favorite kernels for this device.

Great job dude!!! :D
[Nexus 7 Android Development] damagedgoods:
Hey Metallice, I've just flashed a30 more out of need than anything as it was one of the kernels supporting MultiRom and came highly recommended by others using PA. I've been using it for a couple of hours now and I have to say its really quite epic. I've been using Faux's betas up until now and whilst I have nothing bad to say about his kernel I think I'll be sticking here for a bit. Running at 580 GPU and 1.9Ghz CPU. Everything is buttery smooth and rock stable. Awesome stuff.
[Nexus 7 Android Development] Leonhan:
Yes, I did that on the upper hand of trickstermod. Anyway, how much delay should I input? And also, this is my very first time trying a custom kernel, any guides to increase performance of your awesome kernel? I'm, not really into the technical stuff so I don't want to tinker if I don't know what it does.xD
[Nexus 7 Android Development] ximmox:
A30 seems impressively smooth in the first minutes of testing, I'm interested in battery life during the day compared to my a28 configuration.

Thanks Metallice once again. And good luck with your studies!

Edit: neither touchdemand nor ondemand seem to clock below 340MHz, is that intentional?

And yes, I know how to set it in TricksterMod, it worked for weeks.
[Nexus 7 Android Development] porkovich:
I really need to ask this...... why does SETCPU report different default votage compared to TRICKSTER MOD.

For example , 1500mhz - TricksterMod - 1125 , SetCPU - 1175 (default value for stock 1300 Mhz) ? Can it be that every app reads the values different and set something as default ? or it's something else. One more thing i cannot cope is changing voltages in SetCPU , when i set a preferred value , there are 2 options listed , one is Current and one is Saved and the Saved on is the one i want to apply. So do the app aplly correctly or not ?

In Trickster MOD when I change something it changes, at least in the app, can it be that I am missing something, Trickster Mod warns if busybox functions are missing, but can It be something else ?
[Nexus 7 Android Development] androidkid311:
I've got both as well but trickster is muuuch better. I wouldn't bother with the set CPU values.
[Nexus 7 Android Development] Kearkan:
Logged on to report that a29 has worse battery than I expected (only 4 hours screen time with gov parameters set for power saving and undervolting) but now I see a30 is up and people are reporting improvements so off aflashing I go!

Edit: just read the change log, I get what's happening to touchdemand, but what do you mean ondemand is back to basic ondemand? Which version is it?

Edit 2: now I'm even more confused after looking at trickster for ondemand... What exactly does two_phase_freq do?
[Nexus 7 Android Development] yukkio:
Yes, I noticed it too. A29(ondemand) has worse battery than 246 motley(interactive) I hope A30 will be better.

Br.
[Nexus 7 Android Development] sjknight413:
Does anybody else have a problem with trickstermod not setting anything on boot? I have set on boot checked in the menu.

Also something in this kernel is messing with auto brightness, most of the time it sticks to the lowest possible brightness and only comes back up on light change for a second or so then goes back to low brightness. Flickers quite a bit too. I have screen dimming disabled.
[Nexus 7 Android Development] sert00:
Team trickster answered me that they will code all the necessary stuffs for a30 in next release.stay tuned!:laugh:
[Nexus 7 Android Development] Awesoham:
God bless you.

Also, Metallice, I'm glad to hear you study physics. The domain of the intelligent people :cowboy:.
[Nexus 7 Android Development] Metallice:
I wouldn't either. SetCPU is wrong.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Did people miss when i said a29 was for a26 lovers? Just like before the subsequent builds work down from there.

Ondemand is back to being ondemand. It hadn't been for a while. Removed all my modifications. Except for one new one... Two phase freq, which is an intermediate up frequency instead of jumping straight to max.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] cooldoud:
Think you must set a delay of ~30 seconds in the set on boot menu (to be safe, you could probably go much lower)
[Nexus 7 Android Development] Metallice:
Not by choice... Required :D... But it is pretty easy i don't get why all my classmates complain about it. I do like easy. Except for electricity. That sh** make no sense. Stupid Coulomb and Faraday.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] scottx .:
Pretty quick kernel.

Fastest Droid I've owned so far!
[Nexus 7 Android Development] element800:
What's the best cpu clock speed to be safe? I mean a clock speed that won't harm the CPU, I'm currently on 1.4 ghz ;)

And also a safe GPU overclock?

Ty ;D I love this kernel ;p
[Nexus 7 Android Development] Stuphologist:
Electricity is plumbing, with math. Everything else follows.

Dave

---------- Post added at 09:47 AM ---------- Previous post was at 09:35 AM ----------

Heat is the killer. As long as you don't setup your machine to run at full speed all the time there are no "unsafe" values. Your machine will FC/lockup/reboot if you drive it harder than your CPU can reliably run. Just what the reliability limit is varies from CPU to CPU, so you'll have to experiment to see. My N7 is a bit eccentric and flakes out if I try to run it above 1500, I leave it at 1400. Yours may work better...or worse. Ditto for the GPU as far as safety goes. Metallice posted an explanation of how to select GPU freqs a while back, my takeaway was that 600 was a mighty fine value and that's what I've been using.

My own take on CPU overclocking for the N7 is that it's nice to be able to tune your machine to whatever it's true maximum reliable frequency is, but it's a quad-core CPU. It hardly ever maxes out load at max freq. Much more important are the governor settings chosen by the user, and the many other parameters (hotplug, etc.) that are set by the dev. The best use for overclocking for the N7 isn't "over" clocking at all, it's being able to under-clock for battery life. I do that rather than carry a charger around, if I'm going to be out and about rather than home or in my office. Drop max CPU down to 1100 and I barely notice the performance hit, but I do feel (I haven't tried to quantify it) that it adds to the endurance.

Dave
[Nexus 7 Android Development] sert00:
is it supposed to works like intellidemand governor with 2 phase freq from faux?
[Nexus 7 Android Development] rumirand:
If I remember correctly you're on med school? Good luck with physics.

Right now using a30 and works really well.
[Nexus 7 Android Development] element800:
What's the most recommended rom for this kernel?
[Nexus 7 Android Development] cooldoud:
Personal preference really. I'm running it with AOKP PUB builds.
[Nexus 7 Android Development] Metallice:
Despite what many, and I mean many, might say, ROMs and kernels are pretty independent of each other. (Other than making sure the android version number match.)

For the most part one kernel wont run better on one ROM than another, other than any speed differences that were already present from ROM to ROM.

That being said, I run the latest PA in phablet mode at 190dpi for everything. This device is a tweener as is, and its nice to be able to tweak text sizing and layouts (dual pane vs single). For example I can make Reddit news use dual pane mode when on stock it uses the single pane mode.

I can easily recommend any original development ROM whether it be PA, CM, AOKP, RBJ, etc etc.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Well... Technically it works like ondemand with two phase freq... But yeah they are the same idea. An intermediate freq that on demand can (or can not, depending on a counter... Look in source if you want more info) jump to instead of always jumping to max freq.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] dstryrwiz:
I see Westwood, not Westwood+, or is that the same thing?
[Nexus 7 Android Development] Metallice:
Of course. Why would an old, inferior version of a protocol be in the linux kernel, and why would they the new version a different name?

Maybe I should rename m-kernel everytime i update it :D

On a serious note I believe westwood was updated to westwood plus in the 2.4 version of the linux kernel. We are on 3.1
[Nexus 7 Android Development] ximmox:
A30 didn't clock to 102 MHz the whole day, is that supposed to be so? Of course I did set 102 with trickster, but in contrast to all previous versions it doesn't seem to stick.
[Nexus 7 Android Development] Kearkan:
Yes I understood, I was just saying i didn't expect battery usage THAT bad.

And OK, thank you for that clarification.
[Nexus 7 Android Development] GoldElocks:
Strange, I haven't touched any of the settings yet and trickster shows it is using 102 MHz just fine even though trickster shows 340 MHz as the minimum as intended due to touch sound on open.

On another note a30 is running really great for me and like I said I haven't even begun to tweak settings yet.

Battery seems noticeably better as well. A30 is no doubt your best work to date! :thumbup: Going to attempt to tweak a few things on next battery cycle but not sure anything needs to be changed. :D
[Nexus 7 Android Development] VenomTheCat:
I've been using this kernel since I got my N7 back in a19 and never had an issue getting the settings to stick but now the settings where not getting applied after reboot so I had to set a delay of 30 to get it to work. I tried 5,10, 15, 20 and finally 30 now it working perfectly!
[Nexus 7 Android Development] ximmox:
Thanks, due to your answer I knew it was an error on my side.

I tried different things, in the end removing trickster from SuperSU and granting permissions again did the trick.

I have to agree, it's even more fluid than the previous versions, which I already found near to perfect.
[Nexus 7 Android Development] R3dbeaver:
using a30 for almost a day now, from a29.

ps: i'm an a26 lover.

it just rocks. very smooth. all settings default to kernel. i just changed max to 1.6 as before. launcher is much smoother than 28 or 29.

governor stocks to the something-demand as per OP said lol not the regular ondemand. it's great though.

ythink its ready for BETA now?
[Nexus 7 Android Development] johnnyman25:
can someone post his battery life with a30?
[Nexus 7 Android Development] Metallice:
Would it be that hard to flash it yourself and make your own assessment?

Sent from my Galaxy Nexus
[Nexus 7 Android Development] johnnyman25:
i have flashed it yesterday but i want some opinions of other ppl too!! :) me i still have 15% battery with 6 hours screen on time.stock governor settings and max cpu clock 1300MHz.all of it was surfing and watch youtube videos.is this good?
[Nexus 7 Android Development] GaboWinter:
Honestly the usage of another people won't be the same that yours, the best option is test by yourself many cycles not just one.
[Nexus 7 Android Development] johnnyman25:
i agree yes.is there a way to delete battery stats or something?