How to use adb logcat?

First, thanks for the answer.

Second, here is what I didn't know. you wrote:

"Run adb through the command prompt (with command line argument logcat) that comes with the Android SD$$anonymous$$ while running the game on the Android, still connected via USB to the computer."

I had no clue that I needed to actually copy the cmd.exe file into the "platform-tools" folder and activate the command prompt in there so it would work. (or to write to exact location of the adb.exe file in cmd) in no tutorial there was an explanation for this, and only this guide actually explained that

Not all of us are Software Engineers.. otherwise I would'nt ask this question. :)

By the way, this utility only shows the unity console? or is there some more important info I can get using it?

You don't need to be an engineer to know about the command prompt. But that's cool, dude. I saw your pain, reason why I decided to write a detailed answer. Glad I could hit something! ;-)

This shows the android console. It has nothing to do with Unity, it doesn't even need to know Unity exists. There might be some more important info you can get using it, but that will most likely be true only if you're using tools outside Unity (which you probably aren't).

You really don't need (and shouldn't) copy cmd.exe into the android tools folder. adb is "just" a program. To run it you have to specify the right location of the program.

This can be done by:

• "browsing" to the actual folder inside your command prompt where the adb exe is located. The "cd" command (change directory) might be useful.

• Create a shortcut to adb.exe and edit the shortcut properties to add additional parameters you want to pass to adb

• Same as above but more versatile: Create a shortcut to cmd.exe and change the working directory to the directory of your adb location. When you open the cmd with this shortcut it should start in the tools directory and you can directly type "adb xxxx"

• The most common one is to add the directory to the default search path. This is what i do with most tools which i know i'm going to use them quite a lot ;). If you've done that, you can start the ADB from any command prompt from any directory. $$anonymous$$eep in $$anonymous$$d to restart cmd or the changes wouldn't apply. Before you ask how you add an directory to the PATH environment variable, see this

Update: Going to my SD$$anonymous$$ Platform-tools folder I held the shift key and right clicked in the folder then chose "Open command window here" This gives you the path and you can start typing adb logcat. With this method I got "-waiting for device-" however the devise is plugged in and stuck at the splash screen of the app.

So Shift + right-click in the folder with the adb.exe may be of use to someone.

Another Update: $$anonymous$$y trouble was corrupt drivers. uninstalling and re-installing never worked but a Universal ADB driver got my phone recognized by ADB. Hope that helps others save some time.