I would also like to say as a former G1 (HTC Dream) user, I am blown away by the fact that the Samsung iPhone (Vibrant) can DO THINGS, and DO THEM QUICKLY. Therefore, all the aforementioned "suck" is purely software issues, since CyanogenMod for the Dream has spoiled me...
This also is the part of the post where the disclaimer comes in:
This tutorial is provided “AS-IS” without warranties of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of this information is with you. Should this information prove defective, you assume the cost of all necessary servicing, repair or correction. In no event will any provider be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to follow this information (including but not limited to loss of data or data being rendered inaccurately or losses sustained by you or third parties or a failure of the program to operate with any other information). Patent claims generated through the usage of this information cannot be directed towards the providers.
2010-09-15 UPDATE: I flashed the new T959UVJI2 Firmware (the 2.1 "update1") from http://forum.cyanoge...rmware-release/, so this tutorial has been modified for both 2.1 and 2.1+update1. As of now, it's kind of disappointing, so you're not missing much (and most of the current mods are broken, as specified below).
2010-09-20 UPDATE: I finally caved in, and finally flashed a ROM. I recommend Bionix 1.2 for anyone who wants to do most of the things in this post, at once. I used ViralBlack's guide at http://forum.cyanoge...ed-vibrant-v12/
HEY YOU, READ THIS:
2010-10-10 UPDATE: At this point, Bionix 1.7 pretty much obsoletes everything in this post (maybe still useful if you wanted to change the boot noises or something). If you miss the good old days of flashing your G1 all day, erry' day, or want most of these changes performed for you in one flash, go get the Bionix rom from http://forum.xda-dev...ad.php?t=782027 and take a look at ViralBlack's tutorial (http://forum.cyanoge...ed-vibrant-v17/) for guidance. I recommend starting with the Stock choice for that "out of the box" experience.
And keep in mind we're still Vibrant-centric here. It does say "Vibrant" in the title of the post.
TwLauncher Tries to be the iPhone Launcher, Which it is Not
Applies to: all versions running TouchWiz
TwLauncher (TouchWiz Launcher) is the Samsung default home screen/launcher that came with the Samsung iPhone. With it, your phone is Samsung's take on the iPhone, and it isn't even a good knock off. The description I use is "the crap that takes the icons and puts boxes around them so it looks like the iPhone, with sideways swiping and stuff, also the four icon dock." This procedure does NOT require root, so what are you waiting for?
1. Open Market and search for ADW.Launcher or LauncherPro, whichever one maintains greater buoyancy on your seafaring vessel. The related websites for you non-market regions are http://jbthemes.com/anderweb/ and http://www.launcherpro.com/
3. Download and Install the launcher of your choice.
4. Hit the Home key. You will now be prompted to select a launcher. Select the one you just installed, and set it as your default. You can clear that later by updating a launcher, uninstalling, or going to Settings > Applications > Manage Applications > ADW.Launcher or LauncherPro > Clear Defaults
By checking the alternative Launcher as your default, TouchWiz will go away, at least visibly, since we can't actually uninstall it.
The Next (Optional) Step: I ALSO HATE PUZZLE PIECES (Replace the lock screen)
Applies to: all versions, but currently only works in 2.1 not-updated
If you hate puzzle pieces and translucent swiping rectangles and haven't 2.1+updated yet:
5. Root your phone (go to section: Root The Phone) and do the ADB Setup instructions.
6. Take a look at http://forum.cyanoge...en-for-vibrant/ for a screenshot, and http://forum.xda-dev...ad.php?t=782990 to get the actual jar file, which you will adb push to your device.
Fix the GPS
Applies to 2.1 not-updated. Source: http://forum.xda-dev...ad.php?t=728611
The GPS/GPS Compass has problem, namely, the Spirent GPS testing server that Samsung is using no longer exists. This may not work if you are not in 'Merica ('Merica must be said with heavy American accent, usually refers to the contiguous 48 United States) This procedure does not require root.
If you do have root, flash this file (http://forum.xda-dev...ad.php?t=782242) instead. (The 2.1-update GPS fix, without the 2.1-update)
1. Go to Settings > Location & Security > "Use Wireless Networks" > Disable it
2. Start the Dialer/Phone > Dial *#*#1472365#*#* (more star codes: http://www.askvg.com...n-secret-codes/). This will send you to the LbsTestMode menu
The LbsTestMode Menu is disabled in 2.1update1 because the "official" GPS patch is in place. If you read this far and hit this problem, you should check the "applies to" lines I keep putting at the top of sections. Pay attention next time.
3. Go to Application settings > "Operation Mode" > Change it to MS Based.
4. Hit Back, and go to SUPL/CP Settings > Server: > Change it to supl.google.com . Don't put www in front of supl. Also note, this is why it may only work in the United States, since Google may not have network data for other countries.
5. Right under that, Port > Change to 7276
6. Back out to the Home Screen and reboot.
7. Turn Use Wireless Networks back on to submit your location data to your Google Overlords. The way MS Based works, it uses your network location to "hone in" on your GPS location, so you will need to turn it on to see good things happen (and not break it even more).
8. IT'S GPS TIME. If it's still wonky, restart again to make sure.
Default settings if you jacked it up:
Operation Mode: Standalone
Server: www.spirent-lcs.com (if you try going there, it's a parked domain)
The Next (Optional) Step: Reset Your GPS Data
Same source as above. Once again, this may not work if you are not in 'Merica ('Merica must be said with heavy American accent)
9. Dial *#*#1472365#*#* to get back into the LbsTestMode menu
10. Go outside. Make sure you aren't under anything or next to anything that might impede your GPS fix (you should be able to look straight up and see sky.
11. Hit Delete GPS Data, then hit Get Position Test and stand still, preferably in a stupid pose so passerby will look at you funny.
12. Wait until your location data populates and you have an accuracy measurement around or smaller than 20 meters. You usually get that once you have 10+ fixes. You may get fewer fixes if you are outside at a bad time. If that bothers you, wait for the planet to rotate/GPS satellites to move, which means you may be outside for another 5 minutes.
13. Get back into air-conditioned-comfort before you suffer a heat stroke in the mid-day Texas heat. Restart your phone while you're at that.
Root The Phone
Applies to: all versions
XDA is full of one-click root utilities that take as few as seven clicks to root your phone. You should follow the relevant instructions for whichever method causes the most kinetic disturbance to your cotton or polyester based foot coverings. You should also note that everything in this post after this section requires root.
One Click Root without a PC: http://forum.xda-dev...ad.php?t=746129
One Click Root with a PC with ADB and Samsung ADB Drivers: http://forum.xda-dev...ad.php?t=739300
If you want to be a 1337 ph0n3 h4x0r and make you sound like you know what you are doing when you start your replies with "just start adb and...", do the With a PC option, and read Optional: Get ADB on your Computer, Step 5.
The Next Recommended Step: Pave the way for CyanogenMod with a Custom Recovery (ClockworkMod Recovery)
Half of the reason you're rooting is this part, so once you're rooted, fire up the Market and get ROM Manager by ClockworkMod (commonly known as ClockworkMod Recovery: http://www.clockworkmod.com/)
1. Go to the Market
2. Search for pub:ClockworkMod
3. Download and Install ROM Manager.
4. When you run it, it should ask for Superuser Permissions. For those unfamiliar with Unix term "superuser", what that means is apps being able to elevate to Superuser/root, just like how Windows applications run as Administrator/NTSYSTEM ("do YOU want this program to make changes?").
So What's a Recovery?
If you aren't familiar with the Recovery menu, that means you must be new to this whole custom ROM thing. The stock Recovery menus were intended for what they are named for: recovering a crashed/near-bricked phone. As a result, this is also a common test to see if Android devices are "bricked": Can you access Recovery? Standard Recoveries were usually designed to do one thing: look for a specific file named update.zip on /sdcard, verify the signature, and flash it to phone memory. You normally access a recovery by pushing a specific button combination when powering on the phone.
But that was before the modding community got their hands on custom recoveries. Now, most recoveries handle phone image backups (usually of the Nandroid variety) and setting up installs from within Android (no more startup button combinations). So, seeing as how you are in the CyanogenMod forums, you probably want to get a custom recovery to make your CyanogenMod installation experience as smooth as possible before we all crash the forum trying to download the CM 6.1 zip file.
5. Anyways, once ROM Manager is installed, open it up and hit Flash ClockworkMod Recovery, and accept the superuser request
6. Try Reboot into Recovery after it's done. You should now get a recovery menu with some tiny-ass text (but really crisp! Yay AMOLEDs!). The controls are Volume Up/Down to scroll and Power to select. If you don't see ClockworkMod Recovery, you may need to "reinstall packages" (but make sure you don't actually have update.zip packages to reinstall, yet).
When CyanogenMod does come to save us, you will want to get it through ROM Manager (the app you downloaded) or go manual: download the zip file yourself, stick it on the phone, reboot into Clockwork Recovery, and Flash zip from custom location.
Optional Get ADB on your Computer
Applies to: all versions
For the longest time, I thought ADB was a huge framework with an Eclipse plugin that I had to install. It's actually an executable with a couple of .DLL files which takes up 718 KB, and provides command line utilities when you enable USB Debugging and plug your phone into your computer. Vibrant users should probably get ADB because Swype with ConnectBot/Terminal Emulator seems kind of wonky, since you can't push an Esc key. (Camera button? Trackball?).
If you run away screaming whenever you see a command line or terminal, this section is not for you.
1. Open up a new tab and Download (source suggested to not hotlink these files)
Android Debug Bridge 1.0.26: vibrantsamsung.com/extra/files/adb_1.0.26.zip
Samsung Vibrant ADB Drivers: vibrantsamsung.com/extra/files/Samsung_Vibrant_ADB_Drivers.zip
Samsung Vibrant USB Drivers: x64 (64 bit): http://drivers.softp...ndows-x64.shtml or x86 (32 bit): http://drivers.softp...ndows-x86.shtml
2. Make sure your WinZip is up to date. http://filehippo.com/download_winzip/
3. Don't use WinZip. All I know is that's supposed to be funny or something, since that was in the CyanogenMod 6 RC Tips Widget. How do I shot inside joke
4. Unpack the stuff to somewhere you can find it. C:\ADB would work.
5. These steps are known as "Adding something to your PATH". By adding ADB to your PATH, you can type "adb" into your command prompt and use it without explicitly saying where adb.exe is (you would have to type C:\adb\adb.exe every time). Push Winkey+Break, or Open your Start Menu (someone else can write the Linux version of this tutorial) and right click on Computer, then click Properties.
6. Go to Advanced System Settings (should be the Advanced Tab in Windows XP)
7. Click on Environment Variables, then double click on PATH (or Edit it)
8. At the very end of Variable value, put in C:\adb; or whatever path it was to your adb folder. Make sure the last entry ended with a semicolon (insert one if necessary). All the PATH entires are separated with one.
9. Close and Reopen any cmd.exe/PowerShell windows to reload your PATH, and you should be able to type "adb" and get something that isn't an error.
Remove The Crapware
Applies to: all versions
Hey Samsung, we REALLY needed that Add To Home Screen app. I had no idea I was supposed to long press icons to do the exact same thing without it. How about an App to watch Avatar, a video file? MobiTV? Only auto-charges $14.99 a month once you hit accept! What a deal. And where would I be with these Sims 3 stub apks that aren't even apps, but just link to the market entry, since using the Market search is scary stuff.
1. Make sure your phone is rooted
2. If you plan on using adb, make sure the usb/adb drivers and ADB itself is installed. Otherwise, skip to the Alternative Method (Titanium Backup) section.
3. Fire up PowerShell or cmd or whatever CLI provides structural integrity to your personal shelter's upper protective layer.
4. Run adb devices to start the adb daemon
5. You should see a device in the list. If not, make sure you have Settings > Applications > Development > USB Debugging enabled
6. Run adb shell to start a Terminal session with your device.
7. Wake your phone (if the screen turned off), then run su. Your phone (not the computer) should pop up a superuser request. Accept it. Note that ADB shell will echo whatever you type in after it runs.
8. This is the part where stuff can break. You need to be careful with what you remove. The tentative list of Apps you can remove without jacking up your phone is in this CM Forum Post: http://forum.cyanoge...dpost__p__30948
Get write access to the system directory with this command:
busybox mount -o rw,remount /system
Then start doing stuff like:
cd /system/app rm AddToHome.apk rm AddToHome.odex rm MobiTV.apk rm MobiTV.odexKeep in mind that wasn't really an uninstall. However, you can now uninstall the related application entry (delete the leftover data) the "normal way" in Settings > Applications > Manage Applications (make sure to select Menu > Filter > Show All). If an entry is still sticking around because it still thinks it's a system app, you will need to reboot to clear that up.
EDIT: Or you can do it the real way (which should work as well):
adb uninstall PACKAGE
ALTERNATIVE METHOD (Titanium Backup)
Applies to: all versions
1. If you didn't install adb, are allergic to command lines, or want a nice app to do all this for you, hit up the Market for TitaniumBackup. Also, if you are having problems with adb shell (e.g. when you use busybox and you get a lot of "command not found"), TitaniumBackup can probably fix it.
2. Launch TitaniumBackup and accept the Superuser request. (That means you need a rooted phone for this.)
3. Hit the Problems? button. This downloads a new busybox executable (which should fix the previously mentioned 'command not found' problem). If you don't have a working busybox from rooting your phone, do this.
4. Hit the Backup/Restore button that should really be a tab, but whatever. If you can't seem to backup/restore anything, do step 2, and stop skipping steps unless I give you permission.
Reported issue by Hel: Titanium Backup's Backup Features don't work too well with the Samsung Vibrant's /system apps (http://forum.cyanoge...dpost__p__42310), probably due to those ODEX files. Use a different backup method, try a de-odex'ed ROM (look around on XDA), or flash back to stock if necessary. The Uninstall feature works fine.
5. If you're not sure about an App, back it up first, then uninstall. However, you need to be careful with what you remove. The tentative list of Apps you can remove without jacking up your phone is in this CM Forum Thread: http://forum.cyanoge...dpost__p__30948
6. Go to town on those APKs. Hit the relevant App, and hit "Un-install!"
7. Some Apps will leave behind data. To remove those, you can remove the related data the "normal way" in Settings > Applications > Manage Applications (make sure to select Menu > Filter > Show All). If the entry is still locked, you need a reboot to clear that up. The Application entry's name will be the package name (and should be really easy to spot, as a result).
Install Your Own APKs
Applies to: all versions
Samsung's Clock/Alarm app blows huge chunks. The clock app doesn't even have a... clock. Let's fix it.
1. If you liked the previous apps from CM, get the Nexus One CM updates from http://forum.cyanoge...y/6-nexus-one/. Either CM 5 or CM 6 works, but it depends on what APKs you want to pull from the roms.
2. Open up the zip file, and navigate to system, then app
3. Pull out the APKs you want. In this case, I wanted DeskClock.apk
4. Use adb to push it to the /system folder. Alternatively, you should be able to install this like any other APK you get off the internet (e.g. ASTRO, Dropbox, ZumoDrive, TitaniumBackup...) Make sure Settings > Applications > Unknown Sources is checked.
adb devices adb push DeskClock.apk /sdcard adb shell su busybox mount -o rw,remount /system busybox mv /sdcard/DeskClock.apk /system/app/DeskClock.apk
5. You can remove the old, broketastic, Clock-less clock apps by adb shell-ing and
adb devices // (if you haven't already done this) su // (if you haven't already done this) busybox mount -o rw,remount /system // (if you haven't already) cd /system/app rm ClockPackage.apk rm ClockPackage.odex rm DualClock.apk rm DualClock.odex
EDIT: You can also try using adb uninstall PACKAGE
Replacing the Calendar with The REAL Calendar
camrs73 found another XDA thread for replacing TouchWiz Calendar with the real calendar: http://forum.xda-dev...94&postcount=69
Get the Calendar and CalendarProvider APKs on the bottom of this post.
Replacing the Vibrant Camera with the Captivate One
I noticed this one a while back, but promptly forgot and therefore never tried it. Thanks to toolmoo (http://forum.cyanoge...dpost__p__45132) for reminding me. Chaoscentral over at XDA created a flashable zip to replace the Camera app on the Vibrant with the one that comes with the Captivate. If you've ever used a digital camera before, you may have noticed that digital cameras are optimized for adjusting settings and taking pictures. And, you may notice that the Captivate Camera interface looks like... a digital camera, with touchscreen controls. That would just make sense now, wouldn't it?
(Well, IP.Board, how bout' you just auto embed this video, even though I just wanted the link to be posted. Also, that's not me talking, that's chaoscentral from XDA.)
The zips are in the source thread (http://forum.xda-dev...ad.php?t=751031) and includes the Captivate camera along with the Vibrant, for reverting. Make sure you have a custom recovery installed (see section Root Your Phone on how to get Clockwork Recovery).
Stop the T-Mobile Startup/Shutdown Sounds
Applies to: all versions
FAST MOVING FLYING PINK TEXT DO-DO-DOO-DOOO-DOO
1. Make sure your phone is rooted. Otherwise, you can try the no-root alternative if you just care about the sounds (Silent Boot): http://androinica.co...start-up-sound/
2. Stop the sounds. Move/remove/rename the following files
Startup sound: /system/etc/PowerOn.wav
Shutdown sound: /system/media/audio/ui/Shutdown_128.ogg
And of course, you can replace them. The default i9000 Galaxy sound (which isn't too terribly exciting) is in this thread: http://forum.cyanoge...000-poweronwav/
3. Remove the existing shutdown animations
adb devices adb shell su mount -o rw,remount /system busybox mv /system/media/video/shutdown /system/media/video/shutdownbackupOnce these files are gone, you will get the default shutdown sequence where the screen goes blurry and you can see your "SD card is safe to remove" in the background.
If that doesn't excite you enough, you can also change your shutdown sequence to something else. Look in the source thread (http://forum.xda-dev...ad.php?t=732311) for more information. There are also the default (i9000) PNGs that I managed to find, complete with shutdown sound: http://www.mediafire...00_shutdown.zip
4. For the startup animation, you can replace the animations with the default Galaxy S (i9000) qmg files. Scroll down to theitguy's findings: http://forum.cyanoge...dpost__p__36615 to get them.
Experimental: "Lag Fix" (Proprietary File Systems? On MY Phone?)
Applies to: 2.1 not updated
It's more likely than you think. Continue for a FREE PHONE CHECK. A good find by Viralblack. Source: http://forum.cyanoge...fix-2-from-xda/. Not a lot of these have been updated to work with 2.1update1, so I'm going to blanket-not-recommend these to update1 users.
The idea is that these "lag fixes" create a 1.5 GB EXT2 partition on one of your storage devices and use it as a cache (backed by the underlying file system, Samsung's RFS). Now why would you do that? Well, given that the title of this thread is make your phone "not suck", that must mean RFS sucks...
People who need it:
- Run a lot of apps that do a lot of background I/O
- You see the screen go black for a split second whenever you unlock/switch/do something as a result
- And it really grinds your gears
Get the APK here: http://forum.xda-dev...ad.php?t=760571
The APK installs the 'One Click Lag Fix' app, which will do the EXT magic. "The app will automatically kill all running tasks, and enable flight mode. You should not use the device while the lag fix is running. If you accidentally hit back or home by mistake, re-enter the app and re-select the lag fix. It should still be running."
Technical summary: RFS is FAT32 with a strapped-on journal that still handles requests by blocking. If this sentence didn't make you cringe, read on for the lower-level explanation.
One of the big issues with it is how it handles multiple requests - it blocks. It blocks everything. When your mail app wants to read the mail you just tried to view, but your Twitter app is busy writing a new tweet it just received, your mail app is forced to wait.
This is bad, but it could be worse! And it is... your twitter app didn't just get one tweet, it got 50 tweets. It is busy writing the tweets one by one to the filesystem. This would be fine, since all modern filesystems will buffer writes, so instead of writing each one at a time, they will batch them together and write it as a big chunk. Uh oh - RFS does no buffering at all! After each write, it will also write an update to the grafted-on journal system. Guess what happened to your mail you were trying to view while all this happened? It 'lagged' and you got a black screen for half a second, before the mail popped into view.
Luckily, the hardware on the device is so good that you usually don't even notice the problem until you have a lot of apps running, all writing their updates when you unlock the phone.
This fix just grafts a buffer on top of the RFS filesystem, using a very, very simple and fast filesystem, EXT2. It fixes most of the issues by writing to RFS as seldom as possible.
YAY YOUR PHONE DOESN'T SUCK
Edited by TheGenericAsian, 10 October 2010 - 07:24 PM.