Okay - now it's time to make the phone "yours" again! The applicability of this section will vary - as it stands it is pretty me-specific (it's what I did after all), but it seems like some of this might be useful to others (or others will have more useful ways of going about things, which they will hopefully share!).
- You can try a Nandroid Advanced Restore if you have a (preferably "clean" - see STEP 1 number 1 for more info) nandroid backup.
NOTE: THIS WILL LIKELY NOT WORK UNLESS YOU USE THE NEWEST CWM 4.0.1.4!
- Boot into CWM - IMPORTANT: Don't do this until AFTER the phone has had a chance to fully load at least ONCE after all the ROM flashing from the previous step(s).
- Go to "backup and restore", select "Advanced Restore", then select the nandroid backup you will use.
- Select "Restore data" - this should restore all User Data and apps.
- Reboot.
NOTE: Some user setups in the flashed ROM may be lost in the restore, and there is always a risk of odd app issues. That being said - if this worked and is problem-free, all of your personal data/apps should be restored!
- Other non-nandroid restore routes (listed in no particular order):
- Sync phone with Google account - this will get you a number of things (e-mail, contacts, calendar).
- Set up Google Voice (unless of course you don't use it) as your voicemail. I had an "error" setting it up, however it worked fine. You may need to dial a number to "activate" the forwarding (I didn't thankfully) - check here for more information.
- Import phone contacts that aren't Google-synced (unless of course you don't have any of those).
- Some have their phone set to "auto-restore" - I'm not a huge fan of this (mostly because I can't "control" it), so I try to disable such things (see STEP 3 number 5 for how).
- If you made backups (I use Titanium Backup - I highly recommend it), download the relevant backup app from the market.
- Load backed up apps - use the "Restore missing apps with data" batch option.
- If you encounter problems with Titanium Backup - word is you can click on the "Problem?" button and reinstall busybox (or there's always Busybox Installer). I did not have a problem, so I cannot verify this.
- Check market for updates (depending on when you did the backup, this may not be necessary) and download anything that couldn't be backed up (system apps; Google Maps, etc.).
- Lately it seems that after I launch LauncherPro for the first time the backup automatically is activated (along with the full version key) - while I have not tried it yet I would imagine the same would hold for GO Launcher EX. Just thought I would point that out.
- As previously mentioned, my partitions did not auto-convert to ext4 on first boot (no robot lady) - well, at least not the first install attempt (all subsequent attempts have had no issues). As CWM doesn't give accurate voodoo info (it's no longer an option even in newer CWM versions), download Voodoo Control to check (see the last few entries of STEP 3 number 4 for how).
- If there are any updates/mods needed to get your "base" in place (kernel, modem, recovery, update to ROM, etc.), the general policy is to go back into CWM (can get there through power menu, terminal emulator [type reboot recovery], ADB [type adb reboot recovery], or turn off then three-finger) and flash the desired patch/theme .zip file.
It's good policy to wipe cache/dalvik for these, as well as reboot after each - but it isn't always necessary.
NOTE: I get an "E:unknown volume for path [/sd-ext]" message when wiping Dalvik - this stems from no /sd-ext partition and is fine and of no concern.
- If you want to stick with imoseyon's kernel, I highly recommend updating it (found here - currently running version 1.2.2). If not, check out the kernels by imnuts (voodoo/novoodoo found here and an overclockable voodoo found here).
- When switching from a voltage/clock-tweaked kernel, it's probably a good idea to remove your personal settings (i.e. erase any boot settings you might have - if using Voltage Control check for a S_volt_scheduler file in /system/etc/init.d).
- If you want to try and verify what version of a kernel you are running, here are two things I've found that may help:
- This applies in general, but specifically is nice for imnuts kernels as he tends to include the date in the flashable file name itself. If you know around when a particular kernel was posted, you can check to see if the build date matches/is close in Terminal Emulator: OR by using ADB:
- If you already have the upgraded 1.2.2 version of imoseyon's kernel, you can verify the particular version by opening Terminal Emulator, then typing "cat kernel_version" (without the quotes of course). This is the same information that you find in /kernel_version (which is where you are directed to look per the changelog in the OP). This can also be checked via ADB, with the command "adb shell cat kernel_version" (again, no quotes).
- While this functionality exists within GC FE2 as well (see TO USE GUMMY TOOLBOX below, specifically option 3), if using one of the most recent imnuts kernels (0807 voodoo or novoodoo, or 0808 overclock) you can disable/enable logging. Logging (at least from the standpoint of the kernel) is enabled by default.
- When disabling, a reboot is required for it to take effect. To disable, open Terminal Emulator and type: OR in ADB type:
- adb shell disable-logcat
- adb reboot
- To enable logging again, open Terminal Emulator and type: OR in ADB type:
- I've heard of some using a kernel cleaner that you can find here - while this may be nothing more than user error this utility did NOT sit well with my phone. When I used it (when I was preparing to flash a different kernel) the end result was having to go through this whole fun process again (on the up side, I could check my guide). Based on my limited experience (which again could be drenched in user error) I don't recommend this, but if you want to check it out regardless I believe you would want to flash the samsung_ultimate_kernel_cleaning_script_by_lippol94.zip file in CWM. That being said, I doubt I will be using that anytime soon.
- This is something that applies to Lets Golf 2 and GC FE2 - if you want to fully and completely remove this -
NOTE: imnuts 0807 kernels (and 0808 overclock) make this a non-issue, as it uses that preinstall folder for swap space...
- Go into Manage Applications (ALL) and uninstall Lets Golf 2.
- Delete the folders within /Preinstall.
- This should make it so it doesn't re-install anymore (see here for more info).
APPS I WOULD RECOMMENDED FOR TWEAKING (and in general really - there are definitely other options, but again these are my preferences):
- Titanium Backup
- Root Explorer
- Busybox Installer
- Script Manager
- Voodoo Control
- Voltage Control
- Terminal Emulator (comes with GC)
- CPUSpy
- GPS Status & Toolbox
- ADW EX Launcher or Go Launcher EX
- Any I missed that others think should be here?
NOTE: Some of these are pay apps - and worth every penny!
-
GUMMY TOOLBOX -
MANY things can be done through the gummy toolbox... you should check it out! Note that much of what follows comes from the OP of
this thread - you should read it! Also, check out
this thread for some great visual guides on using gummy toolbox!
That being said, before checking out the gummy toolbox you need to -
UPDATE GUMMY TOOLBOX:
- Open terminal emulator
- Type "su" (without quotes - this gives you superuser access, which you may be prompted for allowing) and hit enter
- Type "updatetb" (again without quotes) and hit enter
- At the prompt, select 1 to update (2 doesn't seem to contain any links yet), then 1 to confirm update. After install, select 3 to exit.
TO USE GUMMY TOOLBOX:
- Open terminal emulator
- Type "su" (without quotes - this gives you superuser access, which you may be prompted for allowing) and hit enter
- Type "gummytoolbox" (again without quotes) and hit enter
- At the prompt, choose from the following options:
- OPTION 1 - Install/Delete Apps
- This allows you to either install pre-selected apps OR gives you the option of installing any .apk or removing any .apk from /system/app.
- OPTION 2 - Themes
- This lets you install a number of pre-selected themes (list is updated frequently)
- NOTE: Make sure to return to/be on DEFAULT theme (which is semi-blue) BEFORE installing a new theme!!
- OPTION 3 - Tweaks
- This lets you toggle on/off a number of tweaks.
- The rom defaults to blocking ads, deactivating logs, activating loopysmooth (so no need to do the loopysmooth tweak), and enables SDCard boosts.
- I prefer the ability to logcat, so I enable log.
- OPTION 4 - HANDY LINKS
- Here you can find links to donate and to kejar's twitter page.
- OPTION 5 - EXIT
-
TSM PARTS -
This is an amazing set of tweaks that was first ported to the Charge in GC FE2!
- There is one you will likely want to deal with right away. The first boot after installing GC FE2 will have your clock font color as a default of black (it looks like it isn't there). This is normal - just go to Settings > TSM Parts > Statusbar Settings > Text Color to change the clock font color. Once you click on/enter a color, click the center of the wheel to "confirm". Any changes you make to the clock font color won't appear until after a reboot. I've also heard that simply unchecking Hide Clock works, but I haven't verified this.
- Changes to Carrier Text and Hide Alarm require a reboot to go into effect as well.
- Most of the other tweaks under Statusbar Settings will "activate" after you rotate your phone into landscape.
- Choosing your answer type is located within the Misc Settings of TSMParts, although some have reported issues with the Puzzle not going away.
- If you use a lockscreen that has a custom TSM button, you MUST (under Settings > TSM Parts > Lockscreen Settings) set a Custom App BEFORE you try to use it!
- The Custom MSG under Lockscreen Settings doesn't really show on AOSP or 4Tab (you see a glimpse AFTER swiping a tab).
- If you double-tap the time/clock on the MIUI lockscreen it toggles on/off the music controls.
- I'm not sure how specific this is, but when using the MIUI lockscreen and connected to a computer the phone seems to get VERY hot (a good 15-20 degrees F warmer than when using the AOSP lockscreen - this was the only one I tested).
- You may get odd haptic feedback from tapping near the center of the SGSII lockscreen - not sure why, and it doesn't seem to cause any problems.
- When you Enable Volume Wake, pressing the volume rocker (either up or down) may not wake up phone if it's in deep sleep (my experience at least).
- Some people have reported issues with "hotboots" (the more common variation is like a half-reboot where it skips the Samsung logo and goes right to the boot animation). While not exclusive to this situation, typically this occurs most often when waking the phone. Given the increased issues with this seen when TSM Parts is integrated into Gingerbread bases, some progress has been made as to why these things occur (related to VM heap size and java usage, or so I've heard - see the OP for GC GBE2.1 here, and specifically the changelog for the GC GBE2.1 update patch). That being said I am not going to pretend like I know what is going on with this, but based on my past experiences with TSM Parts (on the Fascinate), it seems to be in some way influenced by setting a custom wallpaper - this seems to be hit-or-miss for which custom lockscreen wallpaper users it affects though. If this seems descriptive of an issue you are having, some have minimized/eliminated the problem by switching back to the default lockscreen wallpaper (which is not so bad as-is really). I have also heard that wiping cache/dalvik can help, but it seems more of a temporary fix.
-
FOR THOSE ABOUT TO OVERCLOCK/UNDERVOLT -
IF you decide to OC/UV - check out
here and
here for info/recommendations. The latter link also includes discussion for another commonly used OC/UV app called SetCPU - I have never used this, as Voltage Control has always done everything I needed it to do. That being said, there are those who swear by it (but watch out for profiles - rumor is they don't play nice with the Charge). I should also note that while I played with this a bit using imoseyon's kernel, I never messed around with the 0808 overclock variant of imnuts kernel - and such end-user overclock/undervolt changes are not possible using the 0807 kernels.
When using voltage control (and the included imoseyon kernel), my (boring) setup is:
- Under the Advanced tab all steps from 1000 down (except 600 w/ imoseyon) are green-light, the rest are red.
- Those same steps are all modified to -50 (this has been very stable).
- Under the General tab Deadline is set as the I/O scheduler, and conservative is set as the CPU governor.
- Any changes made brings up 2 buttons - one to apply and the other to discard.
- Hitting the menu key lets you Save As Boot Settings - but MAKE SURE your settings work for you beforehand.
- Also, you may need to apply a small fix to make your "Save As Boot Settings" settings stick after a reboot:
- Open up Script Manager (free app) and navigate to /system/etc/init.d.
- Select the S_volt_scheduler file.
- Check the box the says run on boot and select save.
-
FIX PERMISSIONS -
While I have rarely encountered force close issues, fixing permissions has been one method to dealing with them. Now that in the newest CWM the script is said to be working (I'm not completely sure on this - it seemed to go faster than it should have when I did this), I believe the way to do this is to:
- Reboot into recovery (by whatever means you deem appropriate - because you know how to do these things by now, right?).
- Go to "mounts and storage" and then mount ALL partitions (i.e. make sure all say "unmount" - to be honest I'm not sure if this is necessary).
- Go to "advanced" and then "Fix Permissions".
- Reboot.
NOTE: In my experience this does not seem to be working currently (per the fix_permissions.log file that winds up on the /sdcard), but I also have had no real need for it.
-
OTHER TWEAKS YOU MAY WANT TO CHECK OUT -
- While I have not had GPS issues that were severe enough to make any changes, many have applied the information learned here.
- Thanks to the extremely helpful guide by hazard209 found here and here, many are now enjoying a variety of awesomely enhancing tweaks. These include V6 SuperCharger, 3G TurboBooster, and KickAssKernel (download-relevant post within original thread for these is found here. The LoopySmoothness tweak (original thread found here - and a nice tutorial can be found here) is actually now part of GC FE2 - see hazard's guide for GC FE2-relevant instructions - also note that imoseyon's kernels play somewhat differently with V6 than others (again see hazard's guide).
- I never tried the KickAssKernel tweak, as there were some issues reported involving YouTube when I was looking into this. As far as I know some attempts at resolving the issue were being made, but I am unsure what the result was.
- When I used them I had some relatively minor issues with some of the newer beta scripts for V6 SuperCharger and 3G TurboBooster. I would recommend trying the updated ones first, but just in case you can get the V6 script I used here and the 3G script I used here. Since my initial usage of these scripts, my phone has gone through a variety of flashing episodes and I have yet to re-run them. That being said my experience with these was quite positive.
- While the above tweaks should help with the ever-present issue of "redraw" (e.g. it takes a bit for your launcher/home screen to load up after playing a game, etc.), there is an impressively simple fix that can be applied that I have been pleased with as well - see this post for instructions and references.