[Samsung Galaxy S Blaze 4G] jparnell8839:
Ok, so there's a lot of new people in the Blaze forums here on XDA, and that's great! That means we got more people buying a Blaze, which means more popularity, which hopefully means more support.

However, that also means the forums are getting choked up with "X isn't working, how do I fix?" on things that aren't known issues, and certainly are not the norm.

The first thing

everybody

should do BEFORE flashing a new ROM is to read all posts made by the OP, usually the top 2 or 3. Those contain critical information, directions, known bugs, fixes, downloads, etc.

Once you flash, if you run into a problem, what should you do? Ask about it in the dev forum?

Read the ENTIRE post. The whole thing, from page one to the last. If the post is more than 20 pages long and you've spent less than 35 minutes reading it, then FAIL.

Once you've read the entire forum post from front to back and you're 100% sure this hasn't been covered, then should you ask about it?

Not necessarily.

Logcats. Logcats are important. Logcats are Android's method of telling developers

instead of it being a functioning operating system.

Logcatting is easy. Its fun. It makes you feel important when you give the devs something to go off of instead of "duh, it aint workin', bossman!"

So here's how to logcat:

FIRST! You must have the latest version of ADB on your computer. The only surefire way to get ADB that hasn't been compromised or altered in a malicious way is to download it directly with the Android SDK >>>HERE<<<

For the minimalist, you can get ADB and Fastboot only. See [MENTION=4631577]Romman0[/MENTION]'s post #6

There are installers for Windows, Linux, and OS X.

Prerequisites

You must have the Android SDK and/or ADB on your computer already set up

You must have your phone's drivers installed on your computer

Your phone must be able to boot past the loading screen

You must connect your phone to your computer with the supplied manufacturers USB data/charging cable

How to logcat: Linux, Windows, and OS X

WARNING! With Android 4.3 (CM 10.2 and 10.2-based ROMs), ADB version 1.0.31 is REQUIRED. You can find out your adb version by running:

~/.android/sdk/platform-tools$ adb version
C:/Android/SDK/platform-tools>adb version

You may also need to fully boot into Android and and accept Debugging from that computer (you will have to check the box marked always accept, or always trust, or something along those lines) and restart your phone to start the logcat

(Pictures coming soon guys, I'm tired lol)

Open up a terminal (Linux or OS X) or a command prompt (Windows).

Navigate to where the Android SDK is installed on. I always install at:

Linux: user@host: ~$: cd ~/.android/sdk/platform-tools
Windows: C:/Windows/System32> cd C:/Android/SDK/platform-tools
OS X: I dont know where, never done it on Android, but I will soon for the sake of this guide

Your location may be different!

type the following command to make sure ADB recognizes your device is connected. If it's not, Google "ADB wont connect to my device"

Linux: ~/.android/sdk/platform-tools$ adb devices
Windows: C:/Android/SDK/platform-tools>adb devices

If it is connected, power off your phone completely and type the following command:

Linux: ~/.android/sdk/platform-tools$ adb logcat > {name of logcat here}.log
Windows: C:/Android/SDK/platform-tools>adb logcat > {name of logcat here}.log

I normally name my logcats with a naming convention, example:

logcat-ROM-version-device-date_time_timezone_of_log.log
example:
CM10.1-20130729-UNOFFICIAL-t769-09AUG2013-2033EST.log

This way, when looking at my logcats, I know:

[LIST]
[*]The Rom
[*]The Build Number
[*]The Device
[*]The date and time the logcat was captured
[/LIST]

your terminal/command prompt will say "Waiting for device to connect...". THIS MESSAGE WILL NOT CHANGE! Just trust that the log cat is will start as soon as the adb service on the phone initiates.

Power on your phone as normal

Try to make the problem appear again

When you've catted as much log as you think you need, hit CTRL + C on Linux or Windows (It's probably CMD + C on OS X, as I said, I've never done this on Mac (yet), but I know how they like to be aggravatingly different so that when I'm using Synergy to share a Mouse and Keyboard between Linux, Windows, and OS X, I keep hitting the wrong keystrokes because I re-grew accustomed to whatever OS i'm using as the primary at the moment). Now hit dir.

Upload your logcat for developer review

Now, I know for a fact that Samsung USB Drivers and ADB communicate perfectly well with the Blaze using the following operating systems. I have tested them personally.

Ubuntu 12.04 x64

Ubuntu 12.10 x64

Ubuntu 13.04 x64

Fedora 17 x64

Fedora 18 x64

Fedora 19 x64

Windows 7 x64

Windows 8 x64

Windows 8.1 Developer Preview x64

I will test out OS X 10.8.4 tomorrow and make sure it works for certain-like

That's it. Any questions, comments, gripes, or complaints? Write your congressman!