Bug 32476 - [Hackweek] Android Log isn't shown by default when debugging an Android app
Summary: [Hackweek] Android Log isn't shown by default when debugging an Android app
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: Trunk
Hardware: Macintosh Mac OS
: --- enhancement
Target Milestone: master
Assignee: Greg Munn
URL:
Depends on:
Blocks:
 
Reported: 2015-07-27 13:10 UTC by Stephen Shaw
Modified: 2017-05-16 14:49 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_ON_ROADMAP

Description Stephen Shaw 2015-07-27 13:10:02 UTC
Should we be showing the Android log when debugging an Android application? I know we have the application output, but does it include all of the possibly helpful information that the Android log would show?
Comment 1 Greg Munn 2015-09-10 14:10:14 UTC
I'm not sure about this. I think there might be a few issues with it.

1) The android log shows *a lot* of information by default so it's very noisy for most debugging sessions I think, especially for newcomers

2) There is a bit of a latency between first connecting the android log to the device and getting to the last events in the log. This is because ADB caches the last x number of events (I've seen around 5k to 7k events cached). This should only be a problem the first time we select the device in the log pad, but it's still something to keep in mind.

I do agree that we don't promote the android log as much as we could, unless you stumble onto it, I doubt many people would know that it's there. 

I also agree that there are some additional event types that are logged to logcat that we could provide in the application output as well - I'm thinking of ActivtyManager off the top of my head.
Comment 2 Kirill Osenkov 2017-05-15 21:22:08 UTC
Bumping this bug so we can make a decision either way.
Comment 3 Greg Munn 2017-05-16 14:49:32 UTC
Right now my inclination is not to. Yes, there is a bunch of information there but it's also information overload for the user and simple debugging like

> Console.Writeline,

which a lot of people use are buried or not available there. Maybe we can make the device log more visible but I don't think it should be at the front in normal conditions.