I am implementing Mobile application in android using phonegap plugin.
I have login option in my app. Once login and keep device idle for long time like 4 to 5 minutes then app becomes unresponsive.
Any one faced this issue before? or any suggestion to find the root cause of the problem.
Thanks in advance.
This is likely an ANR (Application Not Responding), there is a topic about it here:
Android - how do I investigate an ANR?
You can collect the ANR logs at: /data/anr/traces.txt
You should also check the logcat output to search for errors!
Related
I'm trying to get into the world of android-cybersecurity. I've programmed my first payload with msf venom and put it into an apk of an app I've developed. After exploiting in metasploit I can say that It'works, but It's far from being at least useful. When I closed my application the meterpreter session dies (and I can understand the causes) but I'm here to ask if anyone can explain how can I avoid this disconnection when I exit the app. Unfortunately I don't have any ideas and like I said I'm new to cybersecurity (But not to android programming) so when you'll try to explain try also to be as clear as possible. Thanks for any help you can give me :)
I have an APP_A. It will crash when it actived for a long time. I try to find out the resolution to solve the problem but still stuck in it. So I want to try a short term solution that launch APP_B in backgroud then detect the status of APP_A. If it crash, then APP_B will launch it again.
Is there any way to detect if APP_A crash or not?
When the system force stops your application, the entire process is simply killed. There is no callback made to inform you that this has happened but there is workaround and you can try:
https://medium.com/#ssaurel/how-to-auto-restart-an-android-application-after-a-crash-or-a-force-close-error-1a361677c0ce
You can use eventbus library (https://github.com/greenrobot/EventBus) to detect your crash on every situation in your apps and send mail to your mail ID to detect the crash report by using this library (https://github.com/ACRA/acra)
One method is to get the crash through FABRIC and check the logs in ANDROID STUDIO by analysing stack trace.
ANDROID STUDIO--> ANALYSE-->ANALYSE STACKTRACE
Recently my users are complaining that application hangs while using it and the data stored getting lost when the reboot the mobile.
Its not happening everytime too.
Can some one please tell me for what are all the reasons sqlite data will get lost.?
Also for what are the reasons android application freeze?
Background : My application perform sqlite operation from all the screens. The device
Model Number: Samsung GT-18160 , Android Version:2.3.6 , Kernel
Version:2.6.35.7-1219296 dpi#DELL210#2
You can assume no data should be lost. But you may want to nail down crash culprit first - luckily your user is on 2.x so tell him to use tools like aLogCat and grab the logs after your app crash. Then check what's there and fix. That should solve your "data lost" issue as whatever it is, it occurs after your app crashed. If it stop crashing then it should not trigger the snowball....
I have an android application that I have recently finished. So I have successfully finished each function and ensured that no errors are encountered.
When I have exported it to an apk file. It runs smoothly. It uses httpRequests to communicate with a remote mySQL server. But there are times that it spontaneously crashes?
For example, I have an activity that would receive input from the user then communicate with the server. It runs smoothly and quickly. But on next run it would crash. And when I restart the application it would run smoothly again even on the second run. I'm just going crazy from this. Are there any explanations for these?
Use ACRA to collect crash reports from your app. You don't need your own server, just a Google Docs form. The integration is described here:
https://github.com/ACRA/acra/wiki/BasicSetup#wiki-Setting-up_your_project
The advantage of using a crash report tool vs. logcat is that you don't need physical access to the device. There are also chances that you see crashes that you or your testers didn't even notice.
The first step to debugging your problem is to get a stack trace. If you can reproduce this on your own device, then right after you see a crash, connect it to your dev pc and run this command:
adb logcat > crash.log
Open the log file, copy and paste its contents on http://pastebin.com/ or similar and add the link to your question. Once we have that, we can try to figure out what's going on.
I'm developing an android application using eclipse (ADT).
I've been doing it for a few months now, but suddenly today, when I start the emulator, it's over logging the logcat with this message:
Level: D
Application: system_process
Tag: ThrottleService
Text: deleteing /data/system/throttle/407640534
I searched and could not find a single thing regarding anything similar to this problem, it is impossible to use the logging system like this since it prints the same message more than 10 times per second.
I can of course use filters, but sometimes you want to watch all of the logs.
Any idea what this message is about and why it's being logged so often?
Thanks a lot.
Try a hard reset of the emulator. Instructions are here.