android-logcat

How would one write logs from inside Native code in Android (NDK)? What are the available options? For example, can logcat be used from inside of NDK to write logs? Or since its more upper level in android, it can not be accessible from NDK? At the moment I am just aware of writing times from C code with: millis = System.currentTimeMillis(); And with function that would write this time plus any messages to a custom log file. AnkitSomani You can use the Android logging #include <android/log.h> #define APPNAME "MyApp" __android_log_print(ANDROID_LOG_VERBOSE, APPNAME, "My Log"); Also Make sure

Android logcat "application" column is always empty. I have latest version of android tools. aij I tried all the other suggestions here and none of them worked. For me, the application is shown when running on the emulator, but not on my Galaxy Nexus. It turns out I needed to add android:debuggable="true" to <application> in my AndroiManifest.xml . See http://developer.android.com/guide/topics/manifest/application-element.html . People who use Eclipse don't see this problem because apparently Eclipse enables debugging automatically according to http://developer.android.com/tools/device.html .

I need to get the Android device timestamp in the format hh:mm:ss:SS. I am able to view the time displayed in the Logcat of Eclipse. Is it the computer's time or is it the Android device's time? If you are running your app on Android device then it will print device's time, if on emulator then it will show computer's time. To be ensure just match the Log's time with device's time and with computer's time you will find your answer.. From the docs of logcat you can see that there is an option to specify how the output is formatted ( -v ). To get a timestamp, you can use the command logcat -v

I wanted to filter what is shown in the Android Studio Logcat to show what is relevant to my application only. I have chosen Show only selected applications from the drop down at the top of the logcat as shown in the following screenshot: But in the drop down menu above it which is supposed to show running application(s) (and other options) from which we can choose our application to see Log messages related to it only, I see No debuggable Applications as the only option. Why? WHat should I do to fix this? Note: It does not happen every time I run the project. Sometimes it happens, sometimes

UPDATE: This turned out to be a bug in R14 of the SDK tools. It has been fixed in R15 which was released on Oct/27/2013. Updating to the latest release solves the problem as suggested in the accepted answer. I use the LogCat window in the Debug view in Eclipse to diagnose and fix crashes in my code. I've noticed that the LogCat output will automatically scroll down anytime new lines are added (but only after you scroll to the bottom yourself). This is great if I'm waiting for an exception stacktrace to come up, but extremely annoying if I'm trying to read something in the log and more lines

Since the phone restarts and thus gets disconnected from the Eclipse debugger/LogCat while it's booting up, how do I see where my boot complete broadcast receiver is crashing? I am performing some actions in the onReceive() of my public class BootCompleteReceiver extends BroadcastReceiver { ... } This is crashing and popping up a force close dialog when the phone boots. How do I debug this and see where the problem is? The question holds true for debugging any BOOT_COMPLETE broadcast receivers. Thanks! EDIT Yes, we can see the system logs in LogCat as the phone is booting up but my app Log.d

I don't now the meaning of this LogCat entry. Can someone help me? 12-26 18:33:09.651: E/AndroidRuntime(26038): FATAL EXCEPTION: main 12-26 18:33:09.651: E/AndroidRuntime(26038): java.lang.NullPointerException 12-26 18:33:09.651: E/AndroidRuntime(26038): at android.widget.ArrayAdapter.createViewFromResource(ArrayAdapter.java:394) 12-26 18:33:09.651: E/AndroidRuntime(26038): at android.widget.ArrayAdapter.getView(ArrayAdapter.java:362) 12-26 18:33:09.651: E/AndroidRuntime(26038): at android.widget.AbsListView.obtainView(AbsListView.java:2090) 12-26 18:33:09.651: E/AndroidRuntime(26038): at

I'm working on an app that uses Android's MediaMuxer for recording the screen. Using Crashlytics, a significant number of users have the "Failed to stop the muxer" crash, but I can't reproduce it locally on any of my devices. According to another question , the MPEG4Writer logs generated while MediaMuxer is running should indicate what the source of the problem is, but since I'm unable to reproduce it locally, I need to collect those logs remotely and pass them over to Crashlytics. So here's my problem: MediaMuxer and MPEG4Writer are system classes, so obviously I can't edit them to add