logcat

问题 until recently my logcat has been fine but all of the sudden whenever i try to view it in eclipse it just keeps clearing itself whenever anything is displayed making it impossible to read. viewing it in the adb works but I never bother with that since it is just such a pain to read and find anything you are looking for. is there a way to fix this problem? 回答1: It will show one line before erasing it to show the next one? Just click the verbose button again. 回答2: The Logcat messages were

问题 When I execute the command adb logcat while running the android emulator, all of the old logs blow past and so I figure they are stored in a file somewhere. Is there a command I can run to clear the logs and start fresh? If not, is there some other way to do this? 回答1: Have you tried this? adb logcat -c https://developer.android.com/studio/command-line/logcat.html 回答2: adb logcat -c didn't do it for me adb logcat -b all -c worked 回答3: Dup of How to empty (clear) the logcat buffer in Android

问题 I reverse engineered some android apks to add some instrumentation for functional testing. I want to know given an smali as following how can I add something like Log.e(TAG, "some descritpion", e); to each method in the .smali files. .class public Ld; .super Landroid/view/View; .source "SourceFile" # instance fields .field a:Z .field b:Lcom/rovio/ka3d/App; # direct methods .method public constructor <init>(Lcom/rovio/ka3d/App;)V .locals 2 .parameter .prologue const/4 v1, 0x1 .line 317 invoke

问题 Please note, unlike many other questions having the subject title "application has stopped unexpectedly", I am not asking for troubleshooting a particular problem. Rather, I am asking for an outline of the best strategy for an Android/Eclipse/Java rookie to tackle this formidable task of digesting huge amounts of information in order to develop (and debug!) a simple Android application. In my case, I took the sample skeleton app from the SDK, modified it slightly and what did I get the moment

问题 As I have noticed, logcat returns always 34 lines of crashlog, like this: 4cf7c700 401c0000 4cf7c704 48463ff0 4cf7c708 44d11f7c 4cf7c70c afd0cd89 4cf7c710 00000000 4cf7c714 82ab29dc libmyproject.so 4cf7c718 00000000 4cf7c71c 4cf7c73c 4cf7c720 836c44f0 libmyproject.so 4cf7c724 82f3a414 libmyproject.so 4cf7c728 4cf7c768 4cf7c72c 0000008d 4cf7c730 007ea0a8 [heap] 4cf7c734 00270100 [heap] 4cf7c738 e3a07077 4cf7c73c ef900077 4cf7c740 00000000 4cf7c744 4cf7c774 4cf7c748 836c44f0 libmyproject.so

问题 I have a log cat which is outputted to a text file but can't find anything on what each part means. For example, I have the following: W/Trace ( 857): Unexpected value from nativeGetEnabledTags: 0 E/ActivityThread( 565): Service com.android.exchange.ExchangeService has leaked ServiceConnection com.android.emailcommon.service.ServiceProxy$ProxyConnection@40d35408 that was originally bound here E/ActivityThread( 565): android.app.ServiceConnectionLeaked: Service com.android.exchange

问题 For my android app development, I am trying to get logcat messages from my real device (when starting an app on it from eclipse) and not just from my emulator. Does someone know how to enable such a feature? 回答1: You need to enable USB Debugging on your device. Go to settings, applications, development and tick "USB Debugging". Then when your device is connected by USB you can see its name in DDMS as if it was another emulator. 回答2: It works like the emulator, use the ddms or eclipse plugin

问题 I want to achieve the following but so far, no luck Open a file in the SD Card when the android application first started. Stream the logcat output to the file. When the application exits, stop the logcat streaming. In my ApplicationClass extends Application onCreate() method, I do this wwLogManager.openLogFile(); and here's the code in the openLogFile() private static final String LOGCAT_COMMAND = "logcat -v time -f "; String timestamp = Long.toString(System.currentTimeMillis()); String

问题 I'm developing an Android application and I would like to have some way to print debug statements as my code runs. Fortunately for me, Logcat was able to print out Log.d messages when I run my application on an Android 2.3.3 (API 10) emulator. However, when I tested the same exact application on a physical device (Samsung Galaxy S4 Android 4.2.2) I was unable to see anything other than dalvikvm and AndroidRuntime messages. com.android.internal.os.RuntimeInit <<<<<< 07-28 04:49:24.165: DEBUG

问题 Is there any way to access automatically any Log in Logcat by a double click ? Actually, when there is an error crashing my Android Application, I can double click on the line saying for instance at com.myapp.mypackage$Class.function(File.java:117) And by Double-clicking on this line, I am automatically redirected to the related line of my code. But, when I try to generate the same line in another Log, example : Log.e("TAG", "at com.myapp.mypackage$Class.function(File.java:117)"); The Double