I really want to help out devs by getting log cats but Microsoft Xp is a pain. Should I just change the os of my computer
Sent from my SGH-T959V using xda app-developers app
Sent from my SGH-T959V using xda app-developers app
Thanks for this guide! Been flashing files on android for some time now but never really got into ADB. The only reason I decided to check out ADB was because of a soft brick. ADB was the ONLY way I was able to fix it! Tried everything else and nothing! Due to this I might start playing around with ADB and see what I can do.
HOW TO USE ADB , DDMS & TAKING AN LOGCAT ..etc
WHAT IS ADB???
SETTING UP ADB :-
Awesome guide punny
I'd like to contribute a bit to the logcat part, take a look at this post by @doctor_droid knowing the little tip I added helped me solve a lot of problems I had when trying to flash CM7 and doing it wrong lol
Hello Guys
Im really having trouble with taking a LogCat. I created my own Rom and i get BootLoops. I tried to take a LogCat at the boot but it didnt work. I always get Empty Logcat.txt files. I even tried to take a LogCat of a WORKING ROM, but the same, i always get empty files. I tried to disintall and reinstall everything like OP showed in this guide, but it didnt change anything. Every Help is appreciated. I tried both, taking a logcat with CMD and taking a logcat with DDMS
Greetz Blackphantom
1)Which versiin of windows is your Workstation running on .. ??
2) whice Device ??
3) which version of Android is it runnin' ... ??
4) Are drivers installed on your PC ??
adb connect 192.168.0.3:5555
Yes I am 100% sure, even read that article and can someone else running windows xp try shift right click
Sent from my SGH-T959V using xda app-developers app
ok i have found a fix for shift + right click on windows xp follow this tutorial on youtube. if you have question reply to me not on youtube its not my video.
http://www.youtube.com/watch?v=OUHZgVBmTk4
but now i am stuck when i type adb logcat > logcat.txt it just says - waiting for device -
help????
Hello
Windows 7 64x Ultimate
Samsung Galaxy S4 I9505
4.2.2
Yes all Drivers installed and Up to Date
Greetz Blackphantom
adb connect 192.168.0.3:5555
Hi ildar2099, type that on the computer .In your manual says "Now type this in the terminal ." Terminal on the phone or computer?
EXPLANATION Whenever you create an android app or when you develop an Rom , it is important that you must deliver GOOD QUALITY APP or ROM , that are rid of Bugs ..Eventually you might come across a situation when your APP or ROM isn't working or it is bricking the device or some things are not working .These situation can be tackled only with a proper debugging tools ..So ADB ( android debug bridge) is a powerful Debugging tool and a tool which allows us to step through each line of code and examine the value of each variable.It offers us some of the powerful tools ..Debugging is not a big deal for the people who come from a JAVA programming background .Dalvik VM in android supports java debug wire protocol to attach to the device over ADBADBADB or ANDROID DEBUG BRIDGE is a command-line utility that is often used to communicate over the debug channel with a connected phone or virtual device (emulator). ADB can control your device over USB from a computer, copy files back and forth, install and uninstall apps, run shell commands, and more...
1) Install Java JDK :-Before installing the Android SDK, you’ll have to install Oracle’s Java development kit. You can download it from here...(click me !!)
Even if you already have the Java runtime (JRE) installed, you’ll need to install the JDK as well.
After installing Java JDK , you can now download the Android SDK from Google .
NOTE:- If you see a any type of Java-related error during installation, then download and install the x86 version of the JDK, not the x64 one ..
2) Installing android SDK:-
After clicking on "DOWNLOAD FOR OTHER PLATFORMS" , you will get an extended menu ..
After downloading the .exe file , then Double click on the .exe file and install it in C:\ Drive or on whichever drive you wanna install .
Once the Android SDK is downloaded and installed, launch the SDK Manager application from your Start menu.
Enable the Android SDK tools and SDK Platform-tools checkbox and click the Install button. This downloads and installs the platform-tools package, which contains ADB and other utilities.
After installing these packages , Go to the place where you installed ANDROID SDK . IN MY CASE , IT IS :-If you used a different install location, you’ll find ADB in the platform-tools directory,inside your ANDROID-SDK directory .Code:C:\Program files(x86)l\Android\android-sdk\platform-tools
Browse to platform tools and hold Shift and right-click inside it, and select Open command window here...
NOW YOU WILL SEE THIS :-
Note :- To use ADB with your Android device
1) you must enable USB debugging on it. You’ll find this option under Developer Options on your device’s Settings screen
2)You must install your device drivers :- Individual OEM USB drivers for windows are available for each manufacturer and are listed in the official document ..
After you have downloaded you device drivers, then we have to install on our pc. for that :-
a) connect the device to the computer
b) right click on MY COMPUTER and click manage
c) go to devices > other devices and right click on device and select update driver software.
d) you should see an option to " BROWSE MY COMPUTER FOR DRIVER SOFTWARE" , which you nedd to click on and point to the location of your device driver installation file..
To test whether ADB is working properly, connect your Android device to your computer using a USB cable and run the following command:Now it will show the devices connectedCode:adb devices
Now you have sucessfully installed ADB and now we are good to go further..
WHAT IS A LOGCAT :-
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
TAKING AN LOGCAT :-
Now type this in the terminal
Code:adb logcat -v long > logcat.txt
or
Code:Code: adb logcat > logcat.txt
you shall have a log file called name of logcat.txt inside your ADB folder.
SOME OF THE USEFULL ADB COMMANDS :-
– Installs the package located at C:\package.apk on your computer on your device.Code:adb install C:\package.apk
EG -adb install G:\xda.apk
– Uninstalls the package with package.name from your device.Code:adb uninstall package.name
EG :- you’d use the name com.quoordy.xdadevelopers to uninstall the Xda developers app.
– Pushes a file from your computer to your device. the command here pushes the file located at C:\file on your computer to /sdcard/file on your device .Code:adb push C:\file /sdcard/file
EG :-adb push G:\system\framework\framework-res.apk /system/framework
– Pulls a file from your device to your computer – works like adb push, but in reverse. EG :-adb pull /system/app G:\rom\system\app\Code:adb pull /sdcard/file C:\file
– View your Android device’s log. Can be useful for debugging apps.Code:adb logcat
– Gives you an interactive Linux command-line shell on your device.Code:adb shell
– Runs the specified shell command on your device.Code:adb shell command
When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \\sdk\platform-tools [Hit ENTER!]
C:\\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
adb connect 192.168.0.3:5555
adb connect 192.168.0.3:5555