[Nexus 7 Original Development] RealPariah:
Obviously, I mean within reason, if you really can't get to it then you can't get to it. In that case you would leave as much detail as possible. Also don't forget screenshots [again if applicable] should go along with the log. Again I usually just either place it in-line [ppart of the post] if it is 1 or 2, or attach it if it is more [to the post or via outside link whatever so long as they are there.

Again, below should expand the number of cases where you can get the log you need to pass along, but there are times where you may wipe something or be in a state where the log is just not something you can get at. As I stated in these cases you just give as much information as you can and maybe state sorry I can't get to the log to head any requests for it off.

Also here is a great reference if you can get to recovery and/or you wish to use ADB to collect LogCat Logs

LogCat Like a Pro via ADB! [or terminal emulator]

Note if you use Terminal Emulator just sub in >/sdcard/logcat.txt instead of desktop\blah and it will re-direct to phone storage. Also, don't forget to go in to developer options and enable the option that says allow root access Apps Only to Allow Root Access ADB and Apps if planning on using Terminal Emulator on phone.

---------- Post added at 08:33 AM ---------- Previous post was at 08:27 AM ----------

You should be able to correct this by restarting to recovery wipe cache wipe dalvick cache run fix permissions and restart. Fixed it right up for me.

This is the basic fix if you get an error you cant put a finger on or have a general issue you don't see mentioned as a problem for most...

[I use CWM TWRP has this same functionality, but I have had some odd issues with it so if this doesn't work for the specific issue I replied to here try to download ROM MAnager install CWM recovery and try this procedure again]

> Restart to Recovery

> Wipe Cache [Main Menu or Mounts and Storage]

> Wipe Dalvick Cache [Advanced Menu]

> Fix Permissions [Advanced Menu]

> Restart Device

*This will cause a longer than normal boot as it will regenerate cache on start-up [that Android is upgrading message you see on initial boots after flash]

---------- Post added at 08:43 AM ---------- Previous post was at 08:33 AM ----------

Right but the developer opening a longer LogCat Log and using something like I dunno the Find in page command in tons of text editors would enable them to have the information they need even if it has extra it is better to have it somewhere then have someone say something is a problem and have nothing to go on from there.

The point behind bug reports is A there is enough information there to find the issue in code to fix it

OR

B There is enough information there the developer can re-create the issue you had and can then go from there.

Of course, you do need to use common sense and do your best to help with as much information as possible the person who is donating their time for free to help you have an awesome device. This kind of work takes hours, days, weeks, and months to complete it is a labor of love that is usually done just for the love and not because you get paid for it.

Of course I also posted a free app's information on that post and explained how it has a home screen widget to easily start and stop the recording of a specific logcat for regenerating an error and providing only the pertinent amount of log surrounding the time you re-created it as well.