[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Just ran both Blue Skies and Koi and both worked without any problems.

On GtabComb (and, possibly, other HC ROMs), the wallpaper is set in /data/system/wallpaper_info.xml. Take a backup of a good wallpaper setting, and then if anything gets screwed up, just boot into CWM, use adb to restore the good one. (You might even be able to remove the file using adb while the system is bootlooping.)

[I]Save wallpaper settings locally[/I]
C:\> [B]adb pull /data/system/wallpaper_info.xml .[/B]

[I]To restore, while in ClockworkMod[/I]
C:\> [B]adb shell mount /data[/B]
C:\> [B]adb push wallpaper_info.xml /data/system/wallpaper_info.xml[/B]
C:\> [B]adb shell chown 1000.1000 /data/system/wallpaper_info.xml[/B]
C:\> [B]adb shell chmod 600 /data/system/wallpaper_info.xml[/B]
C:\> [B]adb shell umount /data[/B]

As to your problems with GtabComb, I'll just echo what others here have said and say that I've not encountered any major problems with the ROM. It installed perfectly the first time. I've also messed with it pretty severely (resulting in boot loops, hangs, what-have-you, ...) and still managed to get it working again without reinstalling it once. If you have problems with the ROM, its better to find out what it is instead of blindly reflashing it again and again. Get a logcat output using adb and look through it for clues. You can even do this while the ROM is installing itself.

---------- Post added at 11:52 PM ---------- Previous post was at 11:45 PM ----------

Set a timezone, then run a Terminal Emulator app (or use Root Explorer) and check the contents of the /data/property/persist.sys.timezone file. Then reboot and check it again. It should have the same contents. If it doesn't, report back here.

$ [B]su[/B] [I]Become superuser[/I]
# [B]cat /data/property/persist.sys.timezone[/B] [I]Check timezone[/I]
Asia/Calcutta [I]Mine is correct[/I]
#

Note: Type only the stuff in bold

---------- Post added 18th September 2011 at 12:39 AM ---------- Previous post was 17th September 2011 at 11:52 PM ----------

You can get the gTab to go into a long-term suspend state (LP1) wherein the CPU is halted and processes are not executed by going into Wi-Fi settings and setting the Wi-Fi disconnect policy to "When screen turns off". Otherwise, the system goes into LP1 mode only for short periods of time. During an SOD-related test that I ran last week, the gTab running GtabComb-b3.3-bl1.1 went to this suspend state for almost 4 days and then woke up just fine. No user processes were executed and the system used up ~ 0.85 % of the battery each hour.

Well, you can halt the CPU, but if you want to also switch off the DRAM for the hibernate mode as on laptops, you will need to store the DRAM contents somewhere. On Linux, this means saving the contents in swap. But, since none of the kernels we have for the gTab (VS stock, Clemsyn, Pershoot) support swap, this route is out.

OK, now the question becomes, if swap is enabled, then can we hibernate? Well, I'm not entirely certain about this, but, I don't think the (Harmony) Tegra SoC supports this. Even in its lowest power state, LP0, --which, for some reason, is disabled in the VS kernel patch (and which has been carried over in all the kernel sources I've looked at)-- some power is supplied to enable DRAM self-refresh.

Some experimentation is definitely called for here...