I'm running a script and want to log the terminal as the script is running. How do I do this?
Grab alogcat from the market or use 'adb logcat > FILE.TXT' advanced logcat has a switch to output it to a file but I do not know what it is.
Sent from my Incredible using Tapatalk
Related
Anyone know the correct codes for terminal with full root access and nand write access? I can't get su commands to work. I want to remove Sprint and other crap apk's from within terminal.
-------------------------------------
Sent via the XDA Tapatalk App
Not to hijack but what terminal app works best for the EVO?
I feel like such a tard.. i cant remeber the adb command to make the command prompt on my pc show the phones running logcat.
I tried adb shell logcat but the cursor just sat there looking at me like i asked something it couldnt do...
What command am i forgetting? I just want to see the logcat on my pc while i do thngs on the phone?
Sent from my PC36100 using XDA App
v_lestat said:
I feel like such a tard.. i cant remeber the adb command to make the command prompt on my pc show the phones running logcat.
I tried adb shell logcat but the cursor just sat there looking at me like i asked something it couldnt do...
What command am i forgetting? I just want to see the logcat on my pc while i do thngs on the phone?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I don't quite remember this either, but have you tried.... adb shell logcat > log.txt
I believe its:
adb logcat > name of rom.txt
Sent from my SUPERSONIC
The arrow key is just a space right so
adb logcat logcat.txt
Sent from my PC36100 using XDA App
v_lestat said:
The arrow key is just a space right so
adb logcat logcat.txt
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
no the arrow is the arrow
freeza said:
no the arrow is the arrow
Click to expand...
Click to collapse
Correct.
Sent from my SUPERSONIC
i just use adb logcat and it comes out. use control c to exit
If on Linux/Mac:
Code:
adb logcat > ~/logcat.txt
If on Windows:
Code:
adb logcat > %userprofile%\Desktop\logcat.txt
Hello,
I'm trying to troubleshoot why some kernels result in bootloops on my phone and others work just fine. (For example, KingxKernel CFS #8 would work, but not #9-#11)
I read somewhere about running a logcat during boot, but I have no idea how to successfully do this.
Any Suggestions?
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Cool man thanks for the tips.
This is def. A needed logcat command.
Sent from my PC36100 using XDA App
Try using ddbt, very useful for debugging in real time
Sent from my PC36100 using XDA App
sqeet said:
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Click to expand...
Click to collapse
Just to expand...
adb -d logcat>mylogfile.txt
if you want to save your output to a file. Though you are not going to see anything on the screen until you breakout (control c). Just type...
type mylogfile.txt|more
to view the file (or you could use notepad).
sorry meant ddms, not ddbt. It should be in the tools directory along with adb
Just to add that if you want to save the log file and see the output to the screen in real time you can
Code:
adb -d logcat &> log.txt
and then run
Code:
tail -f log.txt
provided that the command tail is available to your system.
Great stuff
sqeet said:
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Click to expand...
Click to collapse
Not a useless post at all. I landed here because I was searching for it. Thanks.
Just installed this ROM (Non-deodexed version) and after restoring my apps everything is hunky dory except for one thing. For some reason I cannot view Dmesg logs with either OS monitor, Lumberjack or any Dmesg log viewing app for that matter
Same thing for logcat
Does anyone know what could be causing this?
Sent from my Galaxy Nexus using xda app-developers app
Same here need an answer, il post here if i find one
stktd said:
Same here need an answer, il post here if i find one
Click to expand...
Click to collapse
I got my answer from the developer of the Lumberjack app (used to pull up dmesg)
In Jelly Bean, you now need root access to pull up dmesg (open up terminal emulator, type in "su" then "dmesg" and it will work), get the Lumberjack app and it will let you pull up dmesg (after you give it root access)
Hi
If u wana to logcat u can open treminal(on device)
Type
Code:
Su
Code:
logcat > /sdcard/logcat.txt
U will find ur log in root of sd
but for problems with boot this is no good
its best to do a full logcat in adb
http://forum.xda-developers.com/showthread.php?t=2141817
Ohhh I did'nt knew that!!!!
Sent from my GT-S5360 using Tapatalk 2
Thanks