Originally Posted by aliensquale
regarding what you say below...
That's unrelated to whatever slowdowns you're experiencing. But, to clean up /cache, just boot into CWM and "format /cache".
it seems very slow now running 1.3, prior to this I was running CM7 and the tablet was much faster.
Yeah. The performance is pretty bad and I'm not sure exactly where the problem lies. Most people point to the paucity of memory being the culprit, and while it may contribute quite a bit, I don't think that's all there is to it: For one thing, there are phones with just 512 MB of RAM comfortably running ICS on them. For another, I see a lot of ANRs and processes being sent SIGQUITs (SIG 3 in the logs) to generate those ANRs. For yet another, the CPU load looks very high when there's lag.
I also see that the ro.build.type
is set to "userdebug
" in /system/build.prop instead of the commonly seen build.type of "user
". Changing the build.type to "user
" stops most of the ANRs. I don't know how Android is built, but, in the Linux world, we usually have 2 kinds of builds for a product: release (what gets shipped) and internal (AKA engineering). The difference is mainly in what compiler flags are used when building the product. For engineering builds, compiler optimizations are turned off and the debugging flags are turned on. These builds are pretty slow and use a lot more memory and CPU than the release builds. Going by what I said about the build.type and ANRs above, this is one thing for the devs to check.
Try these things to reduce lag:
In Settings > ROM Control (set on boot if you're happy with)
1. Reduce dalvik VM heap size for apps to 64M.
2. Reduce the free memory setting to 50MB.
In Settings > Developer options (need to set on each boot)
3. Reduce the no. of Background Processes to 1 or 2.
4. Check the Destroy Activities ... option.
Those last 2 really make a noticeable difference, but, you can, if you wish, skip 1) and 4) and still not impact performance all that much.
It's the battery
the other issue I have on my Gtab... not sure if this is related to the ROM or not.. is that my battery indicator ALWAYS shows 100%. I tried wiping battery stats multiple times in Clockwork but not luck. I also let the tablet's battery drain down to power off. Then plugged it in, booted into clockwork and did another battery stats wipe. Still not luck.
. Don't know what triggers it, though, or how to fix it. I'm trying to look into it.
One final thing before I hit the sack:
Most things that people do to detect bad blocks on the NAND (only looking at the dmesg output, for instance) is not very effective. Here's a simple way to be absolutely certain that the ROM has been installed correctly and fully
onto the gTab. The idea is an old one, going back to Dan Farmer and his COPS package (early 1990s). Basically, it is to:
1. have the ROM packager calculate on his dev box the SHA1 checksum of every file that will be installed.
2. Install this SHA1 checksum file along with the ROM--as, let's say, /system/etc/ROM-files.sha1
. (Remove entries for files not installed during installation--not very hard)
3. User can check using a shell script (or the command below) that the ROM is OK any time he/she wants. If the checksums compute OK, then you too, like me, can sleep blissfully, untroubled by thoughts of any bad blocks doing naughty things to your nice ROM.
Sample creation of ROM-files.sha1
on packager's dev box. Assuming that all files that go into the ROM are in the system/ and data/ directories in their correct locations:
$ sha1sum `find system data -type f` | tee ROM-files.sha1
To check ROM state (on gTab):
gTablet# cd /
gTablet# sha1sum -c system/etc/ROM-files.sha1 2>&1 | fgrep -v OK
gTablet# No news is good news