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.
Related
While I try to get new Android 8 (or P) Application Standby Bucket using UsageStatsManager.getAppStandbyBucket, I receive this error, gave every permission possible to app, but still crashes :
java.lang.SecurityException: MATCH_ANY_USER flag requires
INTERACT_ACROSS_USERS permission at
com.android.server.pm.PackageManagerService.getPackageUid:4959
com.android.server.pm.PackageManagerService$PackageManagerInternalImpl.getPackageUid:25142
com.android.server.usage.UsageStatsService$BinderService.getAppStandbyBucket:932
android.app.usage.IUsageStatsManager$Stub.onTransact:274
android.os.Binder.execTransact:731 : Neither user 10228 nor current
process has android.permission.INTERACT_ACROSS_USERS.
I posted the same question some days ago, like chrispher said, it's a bug, two issues has been filled in :
https://issuetracker.google.com/issues/111102580
https://issuetracker.google.com/issues/111857669
I know that on the first developer preview, the function was working, so maybe you can download the factory image, put it on an emulator or a device and make your test, a bit of a trick but at least we can test this way...
Edit: Good news ! https://issuetracker.google.com/issues/111102580
We are good to test, the release is here !
My LogCat is often not showing null pointer exceptions..
Sample:
ProgressDialog pd;
ps.show();
Application stops (do not reacts for any action), but there is no information about any reason in logcat.
Another sample is with database - if there is no DB and I'm making actions on it, the same happens.
I tried (that action with DB) on my colleague's phone and there was normal error. I have all needed programmer options in my phone turned on.
Maybe someone know , why it is so? It was not burdensome, when I had small app, but now when it's bigger, it can be really frustrating.
I get this with android studio too...
Close android studio, restart ADB, and generally it starts working for me.
If that does not work then put a breakpoint at the line .show(); ... Then open up the logcat and then skip over the breakpoint. It then shows, I have similar issues.
(Windows 7 64 bit - Android Studio 0.82)
I dont like the IDE logcat option honestly.
The SDK comes with an adb binary, use the logcat option from there via
adb logcat or my personal favorite built in alias, adb lolcat
This will give you the log information for EVERYTHING happening on the device, and can be useful tracking down issues caused by device state.
For example, you can see network changes in the logcat, and if your app crashes on network call you wouldnt have any idea why if you just used the logcat output from your app.
In my case I was using: Thread.setDefaultUncaughtExceptionHandler in my application file. If that is not turned off during debugging you won't see any exception output. ( Just make sure to turn it back on again when you release so you can still handle your issues ).
Has anyone experienced something like this ? My app works but after I add the line "Parse.enableLocalDatastore(this);" in my Application class it stops. Eclipse tries to launch it but right after the white screen, it turns black and LogCat notifies this warning "05-24 14:15:20.683: W/ActivityManager(382): Launch timeout has expired, giving up wake lock!"
First time I experience such thing, tried searching on Parse.com and nothing.
Additional info:
Android + Google APIs v4.4.2
Parse v1.5.0
Well, it wasn't the SDK's fault.
Solution: Had to create a new AVD to test my app after adding the line "enableLocalDatastore".
^true, same here, I lost ~10h to find out why!!!! seems it is parse.com lib BUG!!!!! when build the android application on release mode!!!!!!!
solution add this :
Parse.enableLocalDatastore(this);
before
Parse.initialize
I am in a process of developing an Android app ... Therefore I have tested everything on my 3 android phones and everything was fine... I asked some friends to play with the app and app crushes...
I tried to use LogCat to receive errors on Galaxy S4 but it is impossible because log list is flooded by:
AbsListView D unregisterIRListner() is called
This happens every 0.1 second... All apps (expect CatLog 1.4.4) ... I've tried already resetting the phone, clearing apps cache, ...
Any idea?
Interesting. Can you see which app spawns the console. Anyway, for your problem. You can add filters to LogCat, thus only showing the information of your app. So for example you can use the TAG to filter your messages:
private static final String TAG = "MyActivity";
Log.v(TAG, "index=" + i);
And then use this command to filter:
adb logcat -s MyActivity
Its much easier to do this in an IDE. ;) You can find much more information on using logcat especially with console command here.
For this kind of situations, i recommend ACRA - automatic crash reporting library. It is very easy to configure.
How it works? Everytime your app crashes, it automatically sends stacktrace along with tons of other information to GoogleDoc form. Very useful tool, when you give your application to testers. It can even be configured to show dialog asking user if he wants to send crash log, and write some comment on what he was doing when app crashed...
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!