yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Metallice:
No. Also there weren't any errors as I went higher if I changed everything correctly. That was the problem. Meaning the clock timing just thought it was at 800Mhz for example making the memory think it was at 800Mhz even though the 800Mhz was really only being timed for 667Mhz.

Unfortunately PLL_M is a boot clock divider set at 667MHz and there's no way around that at this time.
[Nexus 7 Android Development] Metallice:
The best thing you can do for battery with little to no impact on performance is to set you maximum number of cores to 2. I have yet to see a game or app need more than two cores (all games are fill rate bottlenecked on the T3, never CPU). Also the majority of the time that 3-4 cores are used it is while opening an app or switching between portrait/landscape. These operations are short lived meaning the additional cores are then quickly shut off, meaning a nice waste of battery. Sure, this contributes to "snappiness" and makes everything nice and quick, but if your looking for an easy way to improve battery this would be it. If you don't have your animations turned down to 0.5x I doubt you will ever even notice as the stock animation speeds give plenty of time for two cores to open an app or switch between them.

People say that Android was designed for 2 cores, and having monitored cpu cores and freqs in real time for a while, I'm inclined to believe them.
[Nexus 7 Android Development] slimno19:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Very nice setup.......when u set GPU to 2 does that mean only 2 cores are working? Just asking because my battery life is amazing
[Nexus 7 Android Development] Metallice:
I can't tell you why Trinity works for you at 1.7GHz, but the stability with Clemsyn's kernel at 1.8GHz is very likely due to the extremely high core voltage he set. Also, Clemsyn's kernel was broken when it came to GPU overclock as it was limited by PLL_C being capped at 533MHz.
[Nexus 7 Android Development] slimno19:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Lol sorry I should have just read the last post......oops
[Nexus 7 Android Development] berkos:
wow just set 2 cores max and i don't see difference in FPS in games like dead trigger, wild blood and shadowgun thd...loading times are bit longer but yeah perfomance wise...not a big difference.this leaves me kind of disappointed...do you think google can do something about it in a future which can benefit our devices? i mean here we are anticipating devices with 8 cores and yet we have this kind of optimization now.
[Nexus 7 Android Development] bervin:
metal, any thoughts on boosting our device headphone volume at a kernel level?
[Nexus 7 Android Development] Metallice:
Of course Google can do something in the future. It's their OS. Better optimization for quad-core processors is something that is most likely coming in the future. Although the real truth is that other than the examples I listed before like opening/switching between apps or rotation, where Android tries to do it as quickly as possible, nothing in Android really stresses the CPU enough to need more than two cores, even current games. (one notable exception is quickly scrolling through the widget drawer, although to need more than 2 cores you have to scroll faster and more chaotically than you'd do in real use.

Of course things will eventually catch up as they always do. Android 5.0 will be slicker and smoother and require more CPU power and RAM, and at that point Android will likely be better optimized for quad-cores.

Also we are not really anticipating any 8 core devices in the near future. We are anticipating quad-core devices that can switch between a low power cluster of 4 cores and a high power cluster of 4 cores. AKA arm's big.LITTLE architecture. Basically similar to Nvidia's implementation except way less sucky and way more useful. Unlike Nvidia the chips actually use different architecture (arm7 efficiency and a15 power), and the fact that their are four power efficient cores that actually scale all the way up means the system doesn't have to switch over and then back every time the cpu load temporarily rises and having the number of cores and frequencies identical between the two clusters has other benefits for efficiency. Much better battery and at times better performance. On a side note, I really have no idea why Nvidia decided to use an a15 for the Tegra 4's Low-power core instead of an a7.
[Nexus 7 Android Development] pollanza:
Mmmh are we sure that the trickstermod app can set this kernel to use max 2 or 1 cores?

Because even if I set "max active CPU cores" to 2 or even 1 (and apply the setting) I can see from the trickster mod info page that the other cores are active.
[Nexus 7 Android Development] Nico_60:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Works fine here with only 2 cores selected

Phone: GT-I9100P

Kernel: Dorimanx > Development Thread < > Help Thread <

ROM: 4.2.1 Vanilla RootBox > Development Thread < > Help Thread <

Tablet: Nexus 7

Kernel: M-Kernel+

ROM: 4.2.1 Vanilla RootBox
[Nexus 7 Android Development] pollanza:
That's the point. It's working too fine... I think that trickstermod isn't limiting at all the active cores number. You set 2 cores in trickstermod, then you play a game and it's smooth like with 4 cores active because you have really 4 cores active, not 2.

Not really sure about that though.

EDIT: i've tested with an app that show you an overlay with a bar for every core and it is really limiting them. So games are fluid also with only two cores!

Good to know!
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Yeah i wasn't lying... I actually test these things out before running my mouth :) or keyboard I guess.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Frankie1588:
Is touchdemand governor not recommended anymore?

I also have the problem where my battery dies at 20-30%, but stays at 100% for hours. Please let me know if this holds over a long charge and I will do a factory reset as well.
[Nexus 7 Android Development] EvanA:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Read the OP. Touch demand is still recommended, but that doesn't mean you have to use it.

Sent from my AOSPA 3.+ and m-kernel a33 Nexus 7
[Nexus 7 Android Development] Metallice:
I haven't considered it before so no.

Why do you ask/want?
[Nexus 7 Android Development] y0brando:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I keep looking and looking, but I can't find the "set max cores" function in trickster. :confused:

sent secretly from my paranoid 7
[Nexus 7 Android Development] davisac:
Do you have 1.13.532 or later?

It's on the last tab above the voltages.
[Nexus 7 Android Development] xfrancis14:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Cause you have a mod conflicting with it like Kingbeatz I have the same problem I had to choose cores or audio but I went with audio
[Nexus 7 Android Development] Southrice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

From what I understand is that, ondemand is better for battery life because it scales up the CPU depending on how much CPU the app your using needs at the time. But yes touchdemand is still recommended.

Correct me if I'm wrong.
[Nexus 7 Android Development] skylinegt77:
i think ondemand will also scale up the frequency just by touching the screen, but i might be wrong...
[Nexus 7 Android Development] y0brando:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

That's probably it, king beats. I'll keep my audio.

Thanks for the speedy replies gents!

sent secretly from my paranoid 7
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Well... You are :)

Sent from my Galaxy Nexus
[Nexus 7 Android Development] FitAmp:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Its not hard to guess what on demand is. Its kind of in the name...
[Nexus 7 Android Development] adstraylight:
So is there any way to tweak the settings to increase the multithreading to take full advantage of the fact that we actually have a quad core processor? Based on the evidence here, in general use, two of the cores are pretty much redundant at the moment, or am I reading it wrong?

2nd question: would reducing the processor latency actually increase performance though?

EDIT: I suppose the question I'm really asking is would splitting the load across more cores alow a reduction in maximum processor speed whilst maintaining performance level?
[Nexus 7 Android Development] ximmox:
Interesting question, Metallice will most likely be able to enlighten us on this one. :confused:

As I suspect, due to the negotiable impact when limiting the quadcore to only 2 cores in general use (games excluded) there must be another limiting factor when for example switching apps and so on. RAM maybe (not the amount, the speed of it)?
[Nexus 7 Android Development] R3dbeaver:
i switched off the 2 cores in TricksterMod, and a few games was a little laggy.... cleaned cache, rebooted, make sure it stays at 2 cores max, and voila. smooth as butter. no lag in anything.

then again, my animations setting are at 1.5x.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I already included a patch that sets the minimum number of cores based on the average number of running threads. That's the best way to do what you're describing. ...and I implemented it an while ago :)

Sent from my Galaxy Nexus
[Nexus 7 Android Development] piupiu piu:
When I set cpu to 1.7 ghz my n7 just reboot.
[Nexus 7 Android Development] gorillajuice:
Not all devices will operate @ 1700. IMO anything over 1400 is overkill.
[Nexus 7 Android Development] eduardo_b:
min/max recommendation

Using similar recommended settings from several posters has worked well with a34 (haven't flashed a35 yet), except one of them suggested 204/860 min/max, but I don't see where this is applied. Frequency profile default has vastly greater values. Is this min/max referring to another setting? :confused:
[Nexus 7 Android Development] uberbania:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

No, 204/860 is referring to the min/max freq for the main cpu.

In trickster, under General, these are the values set in cpu frequency control
[Nexus 7 Android Development] eduardo_b:
So, these actually are the GHz frequency min/max minus the zeros?

-----

I see...TricksterMod uses fixed values
[Nexus 7 Android Development] uberbania:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Close. These are MHz (204/860 mhz)
[Nexus 7 Android Development] EvanA:
204 MHz is the minimum value and 860 MHz is the max value. It shows up in Trickster as 204000 and 860000 because those are in Hz not MHz.
[Nexus 7 Android Development] eduardo_b:
I'm thinking of UV by -35 for all frequencies, which has worked well on my phones with custom kernels. Cumulative improvement with battery without causing FCs or other issues. I see others going with -50 or more, but I prefer reliability over maximum battery. Yes...no?

-----

And I can use global offset to do this for each section?
[Nexus 7 Android Development] NicoGa:
You will have to try various value as this is different for every devices. If you are lucky yours could be perfectly stable with - 100 mV across the board ...
[Nexus 7 Android Development] uberbania:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Agreed. I've undervolted main cpu to -150mV without issue. But if I even look at the voltage values for gpu or LP core, my nexus has a sh**fit
[Nexus 7 Android Development] berkos:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I use global and UV by 110, even though not every chip is the same I think you can push it more, remove set on boot, uv, stress CPU and test
[Nexus 7 Android Development] treIII:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

How do i apply two cores only in trickster mod? Thanks. Any help is appreciated.

Can someone please help me with this? Thank you
[Nexus 7 Android Development] NicoGa:
As a rule of thumb you could verify your cpu_process_id in /sys/kernel/debug/t3_variant. Then undervold by -25*cpu_process_id.

But again it really depends on your very own device and you will have to experiment.
[Nexus 7 Android Development] treIII:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

This kernel is not letting me change governors. I am using milestone 2 rom. It stuck on touch demand. Thanks if anyone can help
[Nexus 7 Android Development] eduardo_b:
Ah, I was wondering about other sections besides cpu. I'll stay away from them. I assume mpu is cpu?

---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------

You have to set to use new settings (applied using checkmark at top) on boot...got to settings icon in upper right-hand corner.

---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------

Look under Specific, about half-way down.
[Nexus 7 Android Development] treIII:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

OK. So what do i change? Looking half way down i see balance to the right. What do i change? Thanks
[Nexus 7 Android Development] eduardo_b:
You see Max active CPU cores? Change 4 to 2.

-----

If you don't see it...I have Pro version, although I don't know if this makes a difference for setting cores.
[Nexus 7 Android Development] treIII:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

This is what isee under specific
[Nexus 7 Android Development] Allosaur:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

But you should see...
[Nexus 7 Android Development] ximmox:
This does not seem to be M-Kernel.

Or an extremely old version <20 that I haven't seen before.
[Nexus 7 Android Development] eduardo_b:
It must be the difference between free and Pro ($2.86)...well worth the price IMO.

-----

Or, as noted by ximmox, it's not M-Kernel (which had crossed my mind, but...given the forum you posted in).
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I don't use cpuquiet hotplugging so that's definitely not Mkernel.
[Nexus 7 Android Development] treIII:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I apologize. It is not m kernel. I had to revert because when my screen went to sleep and i rewoke the device i had black streaking on the lock screen and couldn't get the screen unlocked. What can i do to fix that VB problem? I want to use this kernel but got caught in the moment when the screen began doing that. Kind of panicked.
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

You are using another kernel! Not this
[Nexus 7 Android Development] dstryrwiz:
I asked this, then changed my mind when I saw that my question was about what you were talking about, but I double checked and am on M-Kernel yet still do not have the Max CPU Cores setting. Unless the M-Kernel packaged with my ROM is messed up, then I don't know why it would be happening. To double check, I will try reflashing the kernel.

Edit: Currently this is what I see under specific.
[Nexus 7 Android Development] dstryrwiz:
Reflashed, still same thing.
[Nexus 7 Android Development] davisac:
Check and see if you have the latest TricksterMOD.
[Nexus 7 Android Development] dstryrwiz:
Just did, and I do.

Edit: If by any chance this may have an effect, I am using Dirty Rootbox currently, but I wouldn't think that would be the cause.
[Nexus 7 Android Development] geroxx:
AW: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

use the kernel-cleaning-script from this thread ( http://xdaforums.com/showthread.php?t=2121649 ) and then reflash m-kerrnel. This solved the problem for me.

- geroxx -
[Nexus 7 Android Development] treIII:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Can anyone explain why i keep getting the flashes of black across my lock screen when i install this kernel? Is there a fix for the problem? Thank you
[Nexus 7 Android Development] dstryrwiz:
Fixed the kernel, but broke the ROM. Now I need to reflash the ROM.
[Nexus 7 Android Development] eduardo_b:
So you used only the kernel script and it broke the ROM? In what way? I think the kernel resides in its own partition.
[Nexus 7 Android Development] dstryrwiz:
There were init.d scripts as part of the ROM and they were wiped. Also my custom per app DPI settings were reset. Once I reflashed the ROM the problem came back. I feel like the issue may be ROM related.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Maybe the default GPU overclock?

Set it back down to stock with trickstermod and see if it goes away.
[Nexus 7 Android Development] eduardo_b:
So is the recommended setting in OP of 446Mhz considered overclocked, almost stock or...?
[Nexus 7 Android Development] treIII:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Here's what fixed my problem. Check it out. Seems alot of people are having similar problem as I. http://xdaforums.com/showthread.php?p=37280794
[Nexus 7 Android Development] berkos:
let me share this one with you, i run a little test, charged till 100% used franco r42 till 60% with conservative settings.

i have experienced some lag in UI and games, for the rest of the time i used m35 set to max two cores touchdemand with more battery friendly settings and max cpu freq to 860mhz, strangely i got performance like on stock kernel in UI, 3fps difference in wild blood, in the first scene compared to stock, and absolutely no difference in shadowgun. WiFi was always on, background sync also, did a lot of gtalk, triple town, an hour and a half of youtube, the rest was browsing with dolphin and xda app with no scrolling lag. i can't get that mileage with that kind of usage using stock m35 and stock kernel but performance wise it's pretty much close to stock settings, maybe not as much in UI but in games and apps it's pretty much the same. in trickster mod i noticed i used 102mhz little bit more than 666mhz and if i could manage to get 340mhz slot used more frequently at the cost of 666mhz slot i think i could even get more battery life.

im kind of new to android since my first sammy galaxy, but it baffles me that i basically removed 2 cores, lowered freq by nearly 500mhz and practically got similar results as stock settings...stock kernel or any other
[Nexus 7 Android Development] aaronpoweruser:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Just curious why you no like the quiet?
[Nexus 7 Android Development] Leonhan:
Just a question, does the kernel cleaning script clean only the kernel or it wipes everything on your n7?
[Nexus 7 Android Development] dstryrwiz:
Just kernel, however many ROM devs include init.d scripts with their ROMs, so that zip would cause you to lose some ROM features in the process, some more than others.
[Nexus 7 Android Development] EvanA:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I'm curious about this as well.

Sent from my AOSPA 3.+ and m-kernel a33 Nexus 7
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Performance. Just not as smooth. I tested it a while back and everyone preferred the stock hotplugging. I try it every once in a while but then realize that nothing has changed and it's still laggier.

Would it be worth using cpuquiet and having to make the CPU governor scale up faster to compensate? I dunno.
[Nexus 7 Android Development] NicoGa:
To be sure you can have a look to the updater-script inside the zip

(see http://xdaforums.com/showpost.php?p=37628248&postcount=17)
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Niether of those things. It doesn't touch the kernel.
[Nexus 7 Android Development] Leonhan:
So if Im using stock rom, im off the hook?
[Nexus 7 Android Development] NicoGa:
What do you mean ? Which kernel are you using at the moment ?

If it is the stock kernel, you can flash M-kernel directly.

I'm on stock rom, sometime switching between kernels (always coming back to M-kernel) and I never had to use such a kernel cleaner script (yet).

But anyway as I read in an other thread:

"The only thing we wipe around here is our butts."
[Nexus 7 Android Development] bASKOU:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Have a huge loss to the GPU performances on a35. Come from a32 and now games like shadowgun deadzone can't run smoothly in ultra high quality. Benchmarks also show the loss to the GPU.
[Nexus 7 Android Development] prestige777:
Seems like 4.1 kernels were a lot faster and more stable, I got better battery life at higher speeds than I do now. I hope with future android updates, kernels get back to being great again. Something changed to make it less stable at high speeds, than what it should be.
[Nexus 7 Android Development] dstryrwiz:
I thought the whole point of it was to wipe the kernel? I know it resets the ramdisk, wipes init.d, and does a cache wipe, so it doesn't actually entirely wipe the kernel though?

---------- Post added at 06:24 AM ---------- Previous post was at 06:23 AM ----------

The kernel cleaner is useless if you're on stock as the point is to bring you back to a stock-like environment before flashing another kernel.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

It wipes init.d and does a dalvik and cache wipe. That's it, and the dalvik and cache wipe is pointless anyway.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] dstryrwiz:
Then why when I reflash M-Kernel after running that script over Dirty Rootbox do I get the Max CPU Core setting back in Trickstermod which when I emailed Trickstermod, they said I would only get that setting if I had the file /sys/kernel/debug/tegra_hotplug/max_cpus? I don't understand how having init.d wiped would allow M-Kernel to flash that file, when if I try and flash M-Kernel over that ROM without using that script it won't work? Also that script breaks a bunch of features in Dirty Rootbox, such as per app DPI, amongst others, which I would assume would be independent of init.d.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

It's obviously not then. The kernel creates the max CPUs file on boot. There shouldn't be a problem. If the script fixes your issue, then that means there HAD to be some init.d script causing conflicts that was removed.

That, or the init.d script that was removed enabled something on boot that interfered with trickstermod's ability to read the file.

That's the only possible and logical conclusion. There's no point in debating it.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] eric-filth:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Metallice im testing your kernel and i have some observations.

1- I ticked 1300mhz, but after restart the tablet processor still use 1500mhz for a little time but still using, its normal?

2- Im using fixed brightness but i see changing the bright i little

3- Undervolt GPU its a really working? I set to 800mV to 446mhz and 380mhz without a problem.

Enviado do meu Nexus 7
[Nexus 7 Android Development] noodles2k:
1. the os? defaults to 1500 on boot, it'll change once the startup script kicks in.

2. The fix for that is in his sig.

3. Maybe he set limits to stop idiots setting stupid values. :p
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

1 - The boot max frequency is 1500MHz so it will be using 1500MHz for a bit until your app sets the max to 1300MHz.

2. Disable smart dimmer in trickstermod.

3. Yes, but there are some quirks that I have explained many times in the thread. I don't have time to retype it right now on my phonr as it's a long explanation.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] dstryrwiz:
For some reason the file isn't there though, that's what I'm not understanding. How would an init.d script stop M-Kernel from being able to write that file? I'm not trying to debate, just trying to figure out why I'm having this issue.
[Nexus 7 Android Development] eric-filth:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Thanks for answer, i will read all topic to find

With ddr voltages same thing only 667mhz are corret, with 408mhz and 102mhz i can set any value, dont have effect.

Enviado do meu Nexus 7