yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Metallice:
Please try running the benchmarks again on both stock and alpha 23 (using performance governor if you're not), and try using a more restrictive GPU benchmarking app such as basemark 2.0 or GPUmark as wel.

Benchmarks can vary every time you run them so you have to make sure to run multiple benchmarks and run them multiple times.

If it turns out to be consistantly lower, then I believe I know why.

For the curious, some time ago I lowered some bus speeds to gpu freq * 2 (or maybe it was GPU * 1/2... Cant remember) as that is all they need to be instead of slightly more than GPU freq * 2 (or 1/2) . It didn't seem to affect performance and it would help battery.

Thanks for the feedback. Not really helpful at the moment :D , but if you, or anyone else reading this, could do as I outlined above, that would be super helpful.
[Nexus 7 Android Development] Metallice:
That would suggest that your device just can't handle anything above that... Every device is different in frequency and voltage tolerances.
[Nexus 7 Android Development] NicoGa:
Franco Kernel r30 (CPU 1300, GPU 520, LP 500)

Basemark ES 2.0 (several run):

OnDemand: 14.54

Performance: 14.54

Antutu

OnDemand: 12780 (2D~760, 3D~2600)

Performance: 13000 (2D~770, 3D~2700)

M-Kernel a13 (CPU 1300, GPU 520, LP 666)

Basemark ES 2.0 (several run):

OnDemand: 14.45

Performance: 14.61

Antutu:

OnDemand: 12500 (2D~760, 3D~2500)

Performance: 13000 (2D~780, 3D~2800)

Antutu benchmark show an important variability while basemark ES 2.0 are almost always the same

I dont have the image of the stock kernel.
[Nexus 7 Android Development] Metallice:
Thanks. From those results 3d scores seem fine. What about franco with performance for antutu?
[Nexus 7 Android Development] NicoGa:
I updated my post above ... also, CPU integer are higher with franco Kernel, float are identical.

Variability of Antutu is important (± 5% at least)
[Nexus 7 Android Development] Metallice:
With performance governor? Because I don't really care about any benchmarks with anything other than performance as cpu governors vary so much between custom kernels.
[Nexus 7 Android Development] denzel09:
Why franco kernel seems give better results ?

Inviato dal mio Asus Nexus 7 3g 32GB
[Nexus 7 Android Development] Metallice:
Basemark gave a higher 3D score for M-Kernel... so did Antutu (performance).

You know what just forget it. It's because franco kernel is just way better. So you should just go use his kernel. Happy?
[Nexus 7 Android Development] NicoGa:
Yes performance governor.

But in fact, gpu results from Antutu show too much variation (there are less for cpu). It would be needed to achieve at least 10 tests (I did 3 and rounded results).

(As an example, with performance governor, I can have 12700 to 13300 (running with the identical config).
[Nexus 7 Android Development] LINKSLOVESANDROID:
hey metallice. question for you good sir. this is something you might consider pasting in the OP.

As far as overclocking the gpu, i always just flashed the kernel you created that came pre-overclocked. Now that your leaving it up to us, the users, can we get a proper guide on how to do this? I have trickstermod installed and i set the max gpu to 600 with 1350. but that doesnt add any more frequencies in my table. it just jumps from like 412 or something to 600. is this a stable thing to do? or is there a method too add more freuqencies so it doesnt either run too low or over the top? Kinda a noob question, i know, but i figured this is a question many people have been asking themselves. Overclocking the CPU is ez peezy in comparison. thanks in advance. You the kernel king :p
[Nexus 7 Android Development] Metallice:
1 - That's how it is supposed to work and always has even before GPU OC was predefined. 2 - Yes that is a stable thing to do or else I wouldn't do it. 3 - No it is impossible.

It's better that way regardless. That way you only use the high GPU slot when it is needed.
[Nexus 7 Android Development] LINKSLOVESANDROID:
awesome. thanks a lot. what voltage do you run to make 650 and 700 stable?
[Nexus 7 Android Development] BillGoss:
I installed a22 on sparksco's AOSP 4.2.1 ROM http://xdaforums.com/showthread.php?p=34537858 and it worked very nicely, except for GPS. After 150 s I had 7 satellites and no fixes. Using the ROM's kernel I got a fix on 8 satellites in 16 s.

Sent from my Nexus 7
[Nexus 7 Android Development] jombo2323:
well gee, thats funny, today using this kernel i used a gps speedometer to test the offset from putting slightly smaller tires on my truck, i have to say that it acquired accurate satilite signal in under 30 seconds by far

paranoid android ftw anyone?
[Nexus 7 Android Development] BillGoss:
I'll try it out.

Edit: (Slightly OT) I'm actually looking for a 4.2.1 ROM, so PA doesn't meet my requirements. It was interesting that installing A22 fixed a problem with the allocation of /sdcard in sparksco's ROM, but broke the GPS. Performance, though, was very good. If it weren't for my going on a trip and needing GPS, I would have staid on A22.

Sent from my Nexus 7
[Nexus 7 Android Development] jombo2323:
paranoid android is 4.2.1 it just says 4.2 on the thread title, just like it says beta 5 but its really on beta 6. its really a great version, you should try it
[Nexus 7 Android Development] rpr69:
Ah yes, I knew that but for some reason I completely forgot. Sorry about that.
[Nexus 7 Android Development] Metallice:
Next build might work. Added some stuff from cm. Not going to install cm10.1 to find out though haha.
[Nexus 7 Android Development] Kearkan:
Thank you so much metallice, finally got to test a23, just did a burn in of 666@1500 and no reboot! Looks like you fixed it!
[Nexus 7 Android Development] Nburnes:
This works brilliantly, though I have no idea what custom things you have in your ramdisk. I've had 0 problems and great battery life. I just update with your kernel as you release them.

http://xdaforums.com/showthread.php?t=1849473
[Nexus 7 Android Development] sparksco:
There's nothing wrong with allocation of /sdcard in my ROM. It works fine.
[Nexus 7 Android Development] BillGoss:
True, the allocation of /sdcard is perfectly right - I didn't have all the facts straight. But there's more to this. See the discussion going on in http://xdaforums.com/showthread.php?p=35380413.

Sent from my Nexus 7
[Nexus 7 Android Development] Metallice:
Holy crap that screenshot just made me realize I've compiled over 545 nexus 7 kernels...
[Nexus 7 Android Development] denzel09:
Then in waiting for #546 :p

Inviato dal mio Asus Nexus 7 3g 32GB
[Nexus 7 Android Development] Stuphologist:
And posted 1596 messages in xda, for which you've been thanked 1021 times, making your T2P score about 0.64. Congratulations! :good:

Dave
[Nexus 7 Android Development] mrbeardy:
I gave Offworld a try there, good game, but i only got a very small change in temperature, only a few degrees.

In Cpuspy 620 is the most popular speed, so thats working properly ok.

I havent heard any unusual sounds either.

Im just running stock CM10, latest nightly.
[Nexus 7 Android Development] Metallice:
The popping sound is an extremely common bug with all kernels. It happens very often with a smart magnetic cover. I can't believe people are acting like this is a new thing with this kernel. It happens every once in a while for me with the stock kernel as well if I'm using a smart cover.

The heat thing is probably due to the LP overclock. Why cant you people all have the exact same device as me? That way your device would still be running cool like mine and everyone would be happy. It would make things a lot easier. I don't want to have to make multiple LP clock versions, but it looks like I will have to.

Hope to have some time to build a bunch of kernels tomorrow.
[Nexus 7 Android Development] kzakhar:
I don't use a smart cover and don't have any sound issues with any other kernel, custom or stock. The sound issue itself may be related to LP core overclock and is completely random: can happen on wake, in the middle of a game or while playing a movie.
[Nexus 7 Android Development] phonic:
Hrmmmm. Interesting tidbit about the smart cover (and magnet) being the cause. I never thought about that, but I can say that I didn't have any popping sounds (and loss of audio briefly) until around the time that I got the smart cover, so that definitely seems like a possibility.

Also, I can confirm that the 'pop' issue occurs on stock and custom kernels, so that is unrelated.

I do think it would be beneficial to have a non-OC-LP version for people with heat issues.
[Nexus 7 Android Development] :
I own 2 Nexus 7s (my son and I ) ,had them both since release ...I was on Eos 34 a few days ago and had crackle sound.. I do not have a magnetic cover and never heard it before on this device. Sure your right , I probably just didn't ever notice it before on other setups... If it wouldn't have been very quiet in the room I wouldn't have heard it the 2 times it did happen..
[Nexus 7 Android Development] phonic:
I think people might be talking about two different sound issues. Some people have reported "cracking sounds" when their N7 speakers were playing some type of audio. Basically a sound distortion. I personally have never had this (though if I use headphones, occasionally I get a slight distortion when the jack gets touched). It seems like those that have this issue have it more frequently, and is likely to be a hardware issue with either a lose connector inside, or something similar.

The other issue, which is what I was referring to, and others have experienced as well, is that occasionally, when a sound has to be played through the speakers (usually for me the "touch sound" when I touch the screen), you hear a clear "pop" like sound. For about 30 seconds to a minute after this, I get NO sound whatsoever. Eventually the sound comes back. But this doesn't seem to be dependent on a certain kernel or anything. I thought it might have been, but when I flashed 4.1.2 stock, and ran it stock for an hour or so, it happened again.

I've learned to live with it.
[Nexus 7 Android Development] :
Sound I was referring to happened when I set my tab on the table and it crackled through speakers, like a feedback sound.. Wasn't doing anything 1st time it happened then second time I was on xda...Both times I was in a room, alone, very quiet or I probably wouldn't not have heard it.
[Nexus 7 Android Development] Metallice:
Speaker crackling may be related to heat or your speaker just may be blown. The speakers in these things are the easiest thing in the world to break.

Hopefully those with heat issues and speaker crackling will be better served with a 579 or 513 overclock. Not sure which yet.

Speaker popping is a smart cover issue that happens on stock as well. May be the reason why this feature was never advertised.
[Nexus 7 Android Development] HoochieCoo:
I've had the popping sound on every kernel I've tried. Almost always with the smart cover; often even without. Its always the first sound that is whack. I've learned to just ignore it.

I personally like the LP overclock, and the M Kernel in general. Battery life has been very good. No SODs like just about every other kernel I try these days. I haven't noticed a heat issue. Could be my usage pattern. Could be I don't notice it because of the case. Could be that mine doesn't do it.
[Nexus 7 Android Development] kzakhar:
I'm not sure whether you guys are too lazy to read or there's some kind of a language barrier, although my English seems to be good enough :)

The issue I'm reporting is not a "pop" or "crackling" sound. It's a crackling sound + complete audio shutoff until reboot or until I launch another app and make it produce some sound. It happens randomly: on wake, in games, during movie playback, on Twitter refresh, etc. After the sound comes back, the speaker is completely fine and keeps working until the next quirk, which may happen in 10 seconds, 10 minutes or 10 hours - you never know.

I will reiterate that I do not experience this issue with any other kernel and I do not use a smart cover. Especially while watching a movie, you know...

Please let me know if you want me to produce any logs or anything, or if you're going to exercise the usual OSS 'works for me' approach. In the latter case I'll just flash another kernel that doesn't have the sound issue and gtfo.
[Nexus 7 Android Development] Ricolein_Rico:
First of all a big thx to Metallice for his great work on the Motely kernel and to Jay for his buttery goodness init.d optimization.

After a somewhat cumbersome update to 4.1.2 (assert stops, error 7, keep root + cwm) I have been running the M-Kernel + and Jay's buttery goodness for 3 days now. Overall performance is great and comparable to 4.1.1 with Motely's kernel. All benchmark scores are a tiny bit lower with M-Kernel + but I would not call this significant (maybe just artificially induced due to the different pixel handling). Screen rotation appears slower than before (kernel related or 4.1.2 related?) but overall responsiveness and app launch speed feels better. Battery life is definitely better.

Two strange issues though:

1) My max. cpu frequency does not want to stick with sytem tuner, although voltage and sd settings as well as jay's settings do stick. After each reboot the max. cpu frequency is automatically set to 1.5 Ghz, though I manually set it to 1.3 Ghz. As a consequence the cpu temperature after reboot is quite high (50-55 °C), going down to 43-46 °C after setting cpu frequency to 1.3 Ghz (@ 1050 mV). Since I did not check my cpu temps with 4.1.1 I cannot tell whether my current 1.3 Ghz temps are high or not.

2) Randomly during use the max. cpu frequency is automatically set to 700 Mhz?! Could not identify the reason yet. @Metallice: Did you experience these cpu frequency issues or know how to cix them?

Thx,

cheers from Germany

Ricolein

PS:

I also experienced the speaker crackling + mute sound (e. g. after tablet wake up, after incoming mail or when playing a flash video within the browser). Never experienced that before. Since I "upgraded" to Jay's script for 4.1.2 and did a couple of reboots it is gone so far.
[Nexus 7 Android Development] kzakhar:
I confirm that setting min/max CPU frequencies via System Tuner doesn't work: it puts the script where it's supposed to, but the script doesn't seem to affect the frequency (although sets voltages just fine). If you're using PA or another CM10-based ROM, try setting the maximum CPU frequency via system settings, works for me.

Haven't experienced this, my CPU seems to scale 100-1300 MHz.
[Nexus 7 Android Development] Ricolein_Rico:
I am on stock ROM, so system tuner was my best try to set the cpu frequency. I tried both boot seetings (set init.d script and set on boot completed) but none of them worked.

As to the 700Mhz issue I only found out since all of a sudden the home screen scrolling speed was significantly slower and I checked the cpu settings in sytem tuner.
[Nexus 7 Android Development] phonic:
I'm not sure why you seem to be indicating that no one is understanding you. I said twice that I experienced very similar issues to you. While attempting to describe the sound is very subjective (pop versus crackling), the underlying issues is the same. In my case, I've only experienced it immediately after wake, and only maybe 1/4 of the time after it's been sitting for a while. When I touch the screen and it makes the screen touch sound, it's shortened and sounds like a pop/crackle. Then, I have no sound for a period of time. Launching a sound app won't make it come back any quicker. I've even tried playing music, and I still get no sound for 30-60 seconds, then it comes back on it's own.

I examined the system logs, and found no indication of a problem. Which leads me to believe it is more likely HW related. The smart cover variable certainly makes sense, though others have said that they experienced it with or without a smart cover.
[Nexus 7 Android Development] Metallice:
Yeah setting the max frequency with init.d doesn't work. The kernel rejects any attempt to set the max frequency until after boot finishes. I can't say why it does this, maybe a safety reason with one of the patches I added. Setting the max frequency with any app works fine. The only issue is with init.d scripts since they execute before the kernel is ready to accept user parameters.

As a result, setting the max frequency at boot with system tuner won't work as it uses init.d scripts. Any other app for setting the max freq at boot should work however, as they don't use init.d... Trinity Kernel Toolbox... SetCPU... Franco.Kernel updater... NoFrills CPU... CM10 built-in... should all work fine for setting the frequency at boot.
[Nexus 7 Android Development] Jay Aristide:
I've actually stopped using the init.d option with system tuner. I stay current with PA, and it comes out pretty often with a new version, so having it set to run at boot complete is just less work for me.
[Nexus 7 Android Development] Metallice:
I tend to ignore people who insult me after I try to help them... but I guess you're just a more mature person than I am :highfive:. Yeah its the same issue all around. Many people experience it on all roms and all kernels. Usually at wake, but not always... and usually with a smart cover, but not always. This has nothing to do with this specific kernel. It's a hardware bug that's IMO so minor and occurs so infrequently that it's not worth worrying over. Wait 30 seconds... hey audio is back!

People give kernel tweakers way too much credit and way too much blame. It's just how it is.

EDIT:

Ha watching these download number is like watching a race... I've got my money on 446/620 but i must say 484/579 is putting on quite the show... but gotta keep my eye on 446/513, that kid's a fighter. 520/513 is winning so far... but can he hold that lead with such poor battery life????
[Nexus 7 Android Development] notko:
Tnx for new update. I'm on 513/520. Temperature is on 50 C. Is that normal?
[Nexus 7 Android Development] phonic:
I didn't even realize you uploaded new versions until you said that. Downloading 446/513 now.

Back when I was running motley's kernel on 4.1.1, I actually started experimenting with different GPU OC levels. Originally motley didn't provide them, so I compiled a few different ones (using his github source) and provided them to others who wanted to see how they worked. Overall, the majority of people saw little benefit over 484 and the cost of battery life outweighed the need to go any higher. But to each their own.

Thanks again, nice work Metallice!
[Nexus 7 Android Development] Metallice:
Well... here are the current download stats. Just cuz. Poor 446/579... nobody likes you...

M-Kernel_a2_513LP_446GPU.zip	2012-10-21 10:38:19 PDT	13

M-Kernel_a2_513LP_520GPU.zip	2012-10-21 10:39:41 PDT	15

M-Kernel_a2_579LP_446GPU.zip	2012-10-21 10:38:47 PDT	4

M-Kernel_a2_579LP_484GPU.zip	2012-10-21 10:40:09 PDT	13

M-Kernel_a2_620LP_446GPU.zip	2012-10-21 10:39:14 PDT	27
[Nexus 7 Android Development] Metallice:
I have no idea what a good "T2P" score is but I'll accept your congratulations :)

I'm going to need all the good will I can get for my upcoming BioChem527 Final :(
[Nexus 7 Android Development] o0boiboi0o:
U can have all my good luck for now! Rmb to return them back to me! :p
[Nexus 7 Android Development] R3dbeaver:
have fun and good luck! i work in a hospital (not a doctor) and all of my physician coworkers hates biochem lol
[Nexus 7 Android Development] Allosaur:
Good luck! I figure you may need coffee to fuel your brain so stopped lurking and hit the donate button.

Allosaur
[Nexus 7 Android Development] Metallice:
Thanks so much. Unfortunately my brain ran out of fuel and died about 6 hours ago. :) :( but seriously thank you I really appreciate the support.
[Nexus 7 Android Development] Metallice:
Believe it or not, the reason is that it is difficult.
[Nexus 7 Android Development] sparksco:
Are all of your kernels "dirty"? This means you have uncommitted changes in your source and probably not on your github. Your kernel version shouldn't read "dirty" at all and the GCC commit number in your kernel version should match your latest commit on github. This is the new GPL/GNU way linux kernel does things.
[Nexus 7 Android Development] Jay Aristide:
I'm sorry, how do any of those things affect the quality and stability of his kernels? :confused:
[Nexus 7 Android Development] sparksco:
I never said it did. Did I ever say that? :confused: Just a observation of the posted screenshot. Kernels are GPL required to post all of the source code for it, although a lot of kernel developers do not, apparently...
[Nexus 7 Android Development] Jay Aristide:
Ah, ok. I was under the impression it was more ettiquite than requirement. Learn something new every day :)
[Nexus 7 Android Development] MДЯCЦSДИT:
Some of my own kernels are labeled as dirty because for certain versions I revert/cherry-pick commits such as making GPU a different freq would divert from the source code and make it dirty.
[Nexus 7 Android Development] sparksco:
Cherry-picking will not do that unless you have a merge conflict in which case you'd need to fix the conflicts and commit your changes. Source can not be pushed to github with uncommitted changes in your source code.
[Nexus 7 Android Development] Metallice:
Make changes -> build -> test -> go back to step one or continue -> commit -> upload

Therefore, dirty.
[Nexus 7 Android Development] sparksco:
Right but which ones are stable using committed github commits on stable branch? I don't see dates or labels with stable, just ax with lastest download link.
[Nexus 7 Android Development] Milamber33:
Maybe there are no 'stable' builds yet? As you yourself pointed out, every release so far has been an alpha...

Which is not to say that some of those alphas aren't stable and usable, but there's a difference between an alpha which is stable enough for everyday use and a build which is marked as stable (which may or may not be stable enough for everyday use).
[Nexus 7 Android Development] Sveke:
Will this work on rasbean?

Sent from my Gimp Grouper
[Nexus 7 Android Development] sparksco:
On github there's a stable branch look for yourself. No need to get all pissy about it. I just wanted to associate which kernel versions are built from the stable branch and therefore would also be labled as the stable versions.
[Nexus 7 Android Development] ÜBER™:
Yes I'm using it now for a day or two see how it performs.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
In don't understand what you're saying. Regardless, the stable branch hasn't been updated in forever because there hasn't been a stable version yet... Alpha-mr1 is the newest.

I think we are very close to stable. Will update that branch then. After I add the auto USB mount stuff it might be there.
[Nexus 7 Android Development] xfrancis14:
I don't get why all that matters his kernel is still the best out in my opinion, why does it matter if it's alpha?
[Nexus 7 Android Development] sparksco:
I see. OK thanks for that, not sure why it took forever to get through that lol.
[Nexus 7 Android Development] TDO:
I just installed this kernel (a23) and really like it.

But there is one problem.

Now some (not all) flash content can not be displayed correctly.

The installed apps are all the same I only changed the kernel.

Is this a known problem or only a problem of my device?
[Nexus 7 Android Development] Jay Aristide:
"Search this thread" is your friend. Yes, this is a known issue. Metallice has no idea what's causing it, but as soon as he figures it out, he'll fix it.
[Nexus 7 Android Development] TDO:
Thanks.

The strange thing is that's it only with some content. (usually I don't use flash but many of the online christmas calendars are in flash)

I have also tested some other kernels.

lean kernel - same problem

trinity seven kernel - same problem

motley kernel - working

Maybe this information helps.
[Nexus 7 Android Development] wadimka:
hello,

maybe I'm blind or just a bit stupid, but will this kernel work with CM 10.1?

there is just the info for build a12, that this wont work with CM/AOKP. Is it still the case?