I'm working on an app that occasionally does updates in the background over
the network. I have it log things using Log.d, Log.i, etc so I can see
what it's doing while out and around.
These log entries never last very long though. It could run an update and
then an hour later there aren't
On Tue, Jan 29, 2013 at 2:55 PM, Kevin khant...@hotmail.com wrote:
Android 4.1.1, rooted, aLogcat moved to be a system app so it can see all
logs.
Have you tried on a non-rooted device? Perhaps an emulator to verify the
behavior?
Non-rooted device wouldn't help since you can't see the logs of other apps
in Jelly Bean unless it's rooted. I haven't noticed the behavior in an
emulator, but there's a lot less going on in an emulator too.
I know the logs are kept in circular buffers, is there a different
(smaller) buffer
On Tue, Jan 29, 2013 at 3:17 PM, Kevin khant...@hotmail.com wrote:
Non-rooted device wouldn't help since you can't see the logs of other apps
in Jelly Bean unless it's rooted.
I thought you were trying to see your own logs ... ?
I am, but aLogcat (or any viewer) can't see any logs but its own unless the
device is rooted. The only way I could see my own app's logs without
rooting is to make my own log viewer and put it in my app...which seems
like a lot of work.
On Tuesday, January 29, 2013 1:33:53 PM UTC-8, TreKing
On Tue, Jan 29, 2013 at 3:42 PM, Kevin khant...@hotmail.com wrote:
I am, but aLogcat (or any viewer) can't see any logs but its own unless
the device is rooted. The only way I could see my own app's logs without
rooting is to make my own log viewer and put it in my app...which seems
like a
6 matches
Mail list logo
