[Galaxy Tab  Android Development] luigi_sa:
Juwe script feedback

Hey all,

Decided to “have at it” with testing juwe's script, taking into consideration that Alter has already built in performance scripts etc (Thnx Pharoahnough for confirming Alter's tweaking, in general).

Here's how it went -

Steps to setup baseline:

1. Re-stocked my tab

2. Cleared all Caches (JUST in case :)

3. installed OC Jupiter

Went through it as if I was re-doing my tab from scratch…

From there I went and installed SETCPU, Quadrant (and I’ll have a little to say about this app later), in an effort to keep the tab as close to "Jupiter stock" as possible. (boy the permutations are exponential when trying to get to a baseline any other way... :S anyhoo)

please also note that I almost always run at 200-1200MHz with no UV's done.

Quadrant Results:-

Before Juwe installed:

- ondemand = 1628 +/-

- Interactive = 1091 +/-

- Smartass = 1674 +/-

After Juwe CWM'ed into ROM:

- ondemand = 1908 +/-

- interactive = 1981 +/- (pls refer to Quadrant “feedback” below)

- smartass = 2012 +/-

I've been watching my battery over the last few days, pretty much since Jupiter released and I flashed to it, without Juwe installed (didn’t put it back from my Icarus days), and battery life is very good to say the least, min 48 hours between charges, with relative medium usage, and occasional heavy use in that time. I remember on Icarus, I was LUCKY to get anywhere near 30 hours out of my tab with Juwe installed. A reminder, I don’t OC past 1.2 GHZ and lock it to 200 MHz, as a standard, don’t play with the CPU at all after that. The only system changes I make is to lower my tab’s DPI to 192, and restore my apps (56 of them).

I’ve attached some pics I took with “Shootme” just to show the system’s and Elixir’s take on memory etc.

-	The android pics I can honestly say I’m dubious in using them, you can NEVER get the same services running at the same time, without some heavy time management and patience if you scrap it up at the last second…

-	In comparison Elixir could arguably give better input, especially when you see the Before & After show way less memory in use in the After shot. But, pls, its arguable… that very second the system could just have been super idle, or…. The permutations are a little to big to go into…

-	Even trying to “mean” the scores (on a suggestion from a mate”, wouldn’t work out too well. If anything it would more likely skew the view than bring in a better perspective.

Anyway, in a nutshell, from what I can see, without Juwe, battery life looks to more likely be a beauty on battery saving (if youre a battery conservationist), and WITH Juwe, your machine gives better Quadrant scores, with some definite signs of better load-times on a lot of apps (but your battery will suck down faster than a thirsty man running a 3 day marathon in the desert…)

THE CHOICE IS YOURS  :D

And lastly, but by no means least, my feedback on Quadrant.

Now on to a personal rant of my own, and pls, this is NOT aimed at anyone, just a perspective shared by a couple of others along with one OC team member so far… :)

As much as I truly appreciate the developer’s hard (considering i cant do it myself... :( ) work in this app, we have a device that (proven by the over-clocking/undervolting scenarios many of us are trying to get the best possible from), are governed by the chip which is almost a proven is different from one Gtab to the next… This (might be presumptuous of me here, but) is affecting Quadrant’s scores for each of us to a degree, that even if we replicated 3 devices (minimum number of items for any test) exactly, we would most likely find the scores changing enough to make the results be discounted. Classic example, on just my tab, was the INTERACTIVE score above, showing higher than ONDEMAND, which i find dubious at best. I know many rely on this to give a visual of how well their “baby’s” working, but just in this one test case I find it inaccurate enough to make me wonder about what its telling me.

Anyhoo, my rant over, everyone to their own (one man’s meat etc etc ). If you see anything here that I missed, pls let me know, am more than willing to get back in the test-drivers seat and bash at it again.

Have fun!