DarthJabba said
A new record for the Cube! Using the overclocked #352 kernel (cpu1800, gpu768, ddr720) I've got an Antutu score of 22357.

I'm joining to Club22k+ with my 22097 That's on #352 kernel (cpu1800, gpu768, ddr667). Other benchmark scores are down below with percentage difference compared to beta1 (cpu1800, gpu798, ddr667). The UI experience is much better now, but benchmarks show that gaming should be much better too. Overall, I'm quite happy with the changes Cube did in this beta.

The only bug I have noticed so far is some weird screen flickering (like a vsynch over 60fps), and screen corruption (but only on a small part of the screen for a brief time). Some people also reported it before me. Most of the time it happens on the navigation bar on the bottom, when scrolling launcher homescreens, when scrolling apps in Settings/Apps, when browsing the content inside gallery, and even in 3DMark and NenaMark2 benchmarks, so I guess it will be visible in other apps sooner or later. I still can't confirm that since I'm completely stock now, but anyway it would be nice to get rid of it. So if anyone knows how to deal with it, I'm open to all suggestions.

And now the results...

Benchmarks (FHD):
AnTuTu = 22097 (+3,6%)
Quadrant = 6043 (+7,3%)
T-Rex HD = 7fps (+16,7%)
Egypt HD = 18fps (+20%)
NenaMark2 = 60fps (+36,4%)
Epic Citadel = 50fps (+51,5%)
3DMark = 4197/3151/4207 (+18,9%/+13,4%/-0,2%?)

And one more thing worth noting. If you're using the stock launcher (I think it would be no problem with others), do not ever disable or freeze Google Search in this beta! I like to do that because I never use it, and it doesn't reminds me every now and then about the update. If you do disable it, then the first side effect will be not able to get back to homescreen. And if you undo your changes while you still can, then that's no problem at all, but if you restart your Cube (like I did, thinking it's something else), they you will find you can't boot your tablet as it will be waiting on the animated Cube logo indefinitely. But that's not where the fun starts, because even restoring your CWM backup won't help. Not even completely wiping the whole damn thing, and installing fresh CWM rom (for the life of me I can't figure out why that didn't help). The only way to bring it back to life (at least in my case) was flashing Kasty's rom with RKbatch tool first, and then do the whole thing over again (CWM, JB rom, mods, kernel, setting up the settings, restoring apps, ...). Arrgghh. Now I did the same mistake, but I was carefuly checking if everything's ok after each major step, so I was able to figure out what is going on. If I was a developer of that stupid stock launcher, I wouldn't go into infinite loop waiting for Google Search widget to automagicaly appear from somewhere, I would instead not load it or something. And that's how it was on every rom until now. But the way it is now, all hell breaks loose because of that widget. So save yourself a headache, and leave that alone.