Home Artists Posts Import Register

Content

Every once in a while people run into issues, and when they do they usually report them to me for fixing, which is good, but more often than not these reports lack substance, preventing me from actually addressing whatever the issue was.

What makes or breaks a bug report is whether it comes with a log-file capturing whatever the error was that caused the problem in the first place or not.

I understand that not every user comes from a technical background, so I decided to release a two-part series of short videos showing all of you how to create meaningful logs to go along with your bug reports.

This is part 2 out of 2, showing all of you how to create logs via a Windows computer.

This is the logging method of choice for all issues that prevent you from booting your device, if your device is booting fine you might be better off using the on-device method described here.

- Black-Seraph

Files

Capturing Android Logs for Bug-Reports (from a Windows computer)

We developers do our best to provide you all with the best possible software we can, but sometimes things inevitably go wrong, and when that happens its important that all of you report what went wrong so we can fix it. But there's one additional thing you can provide that will drastically improve your chances of us being able to fix whatever was plagueing you, a log. This video will show you how to capture a log that we developers can use to identify and fix issues via the adb running on a Windows computer. This is the method to go with if your device is stuck in a bootanimation loop, if your device is still booting fine you might be better off using the on-device method shown here: https://www.youtube.com/watch?v=G4g5zvcCfOI You will need: ► SDK platform tools: https://developer.android.com/studio/releases/platform-tools Where to follow us: ► Twitter: https://twitter.com/teamblackseraph ► Patreon: https://patreon.com/blackseraph

Comments

No comments found for this post.