It is not really a programming question. I have this app that continues to crash on my phone, but works fine for everybody else. I used to program android apps, so I have knowledge in this field.
It something on my phone probably it always crashes at the same stage. I did not program this app. How can I still get the details of the error or the trace of the exception?
I would suggest plugging the phone into your computer or laptop, opening up the Logcat tab in Android Studio and viewing the exception details as the app crashes.
This can be done separately from Android Studio using ADB but it involves more steps.
Of course, make sure that you have enabled USB debugging on your device before this.
Related
I'm experiencing pesky SIGSEGV faults in my Android app. They are inconsistent to reproduce and mostly happen after my app has been restarted a couple of times. The problem is, when the app restarts, Android Studio stops showing the logs, making it very hard for me to figure out what the issue is. When I restart the app using the Android Studio restart button, it loads a fresh install of the app onto my phone, which is an issue because the errors don't seem to happen on very fresh installs.
My question is: can I somehow have Android Studio still show the live logs WITHOUT reinstalling the app every time, OR can I run the app without being connected to any PC, and dump a crash log file locally to the phone when the app crashes, so that I can open the logs later on?
Filtering logcat
The problem is, when the app restarts, Android Studio stops showing the logs, making it very hard for me to figure out what the issue is.
It sounds like the logcat in android studio is filtering by application. You can change it to no filter and set the text filter to your application's id. This way the logcat will not be cleared once the application process dies/restarts.
Extracting the tombstones
Since this is an Android native crash it will not be sent to bug capturing software such as Crashlytics or Bugfender etc.. you can pull the tombstone[s] directly from the device with adb.
adb bugreport bugreport.zip
Once extracted, the tombstones will be under path /bugreport/FS/data/tombstones/.
Typically 10 tombstones will get saved to device storage but will get overwritten by earlier native crashes once the limit to the number of retained tombstones has been met.
Android documentation: Using bugreport
Android documentation: Debugging tombstones
I am designing an experiment in unity. It is running on it but not on the android phone. I have tried by changing all the settings. I don't know much about coding but the program is just copied from another program where it is working correctly.
Try to connect your android device with android device monitor and run the app. So that you will get to know which causes the problem to crash the app.You can check the log on using this monitor. Please have some google search to get more info regarding this.
For more info follow the following link.
https://developer.android.com/studio/profile/monitor
I've been working with PhoneGap for about two weeks now, yesterday I've build a new android app all went well except that the app starts very slow on my android device. It first shows me for three seconds just a black background except the navbar. So I want to ask how to boost it up or which files I could remove or what I've done wrong please I would be happy if you explain me also the file structure. Thanks in forward for your answers!
Your question is little bit vague. Please, give us more information about your app, about your config and what you’ve already tried.
If my app is slow on any device, I do generally the following:
Check if the same problem occurs in the browser
What’s going on at the start of the app in the browser (Chrome Dev Tools)
If nothing unusual happens, check the logs on the device
For Android, I’m using Logcat for checking what’s happening on the phone.
In order to use Logcat:
1.) Enable debugging mode on your Android phone
2.) You need Android Studio
3.) Connect your phone to your computer and start Logcat in Android Studio 3.1.2
4.) Check the logs while you are starting your app on the phone
I am using Android Studio 1.5.1 IDE.
I plugged up a Samsung phone to test with. Without even running the application I am testing, the LogCat constantly just scrolls data and it makes it difficult to focus on my app.
Is there a way to stop the console from showing phone debug logs and just show me my app when I am running it?
Yes, when running the application you are able to select your application in the dropdown highlighted in green here:
This causes only the output from that specific application to be shown during debugging/running.
If you're asking to never ever show the logs from your phone, I cannot help you with that.
I have installed some android application on google nexus 7 ( tablet) , I want see the log of those applications.
This applications are not created by me, but yet i want to see where the application crashes through the log.
I was able to do this with my iOS device, by simply connecting and opening the console in xcode. How to do this for android.
Can anyone tell, what code or what procedure is to followed. ?
You can install the android tools and use adb logcat to monitor to logcat output from your device.
You will be able to see the crash stack trace, but not the code which makes it crash.
Well, I got the page which explains this better.
http://developer.android.com/tools/device.html