Skip to main content

How to get a logcat / system log to help with debugging an issue

By

Android 4.2+:

If you are rooted you can follow the instructions for 4.0.x and below.

Step 1: Reproduce the crash / issue with the app
Step 2: Enable developer options: Go to system settings -> about device -> click on "Build Number" roughly 7 times until you get a toast saying developer options are enabled.

adb tap build number seven times

Step 3:  Back out of About Device and Click on Developer Options
Step 4:  Find take bug report and click it.  If Take bug report is grayed out, you will need to check the "Enable USB Debugging" option to enable the bug report option
Step 5: Wait up to a few minutes for the bug report to generate, you will then be prompted to select an app to handle the bug report.  Select your email client / gmail.  (There may also be a notification saying the bug report was taken.. clicking on the notification will give you the prompt)
Step 6: Enter the email address to the dev you want to send the report to (gonemadsoftware@gmail.com if you want to send it to us)
Step 7: Send email

Android 4.1:

Android 4.1 users cannot send logs unless they are rooted.  If they are rooted follow the instructions for 4.0.x and below.

Android 4.0.x and below

Step 1: Download an app named catlog from google play (https://play.google.com/store/apps/details?id=com.nolanlawson.logcat).  
Step 2: Reproduce the crash / issue with the app
Step 3: Open Catlog
Step 4: Hit menu -> send -> attachment
Step 5: Select your email client/gmail
Step 6: Enter the email address to the dev you want to send the report to (gonemadsoftware@gmail.com if you want to send it to us)
Step 7: Send email

Popular posts from this blog

GoneMAD Music Player 4.0 released and is now free!

By
GoneMAD Music Player 4.0 is now fully rolled out!  After 14 years since initial release as being a paid app, I've decided to try something different and switch to being free with ads.  The market is completely different nowadays compared to the early 2010s.  Ads are everywhere and users typically do not want to pay for apps / games / etc.  But don't worry, those users who previously purchased the unlocker or in app purchase unlock will continue to get an ad free experience.  New users will also have the option to purchase an in app purchase to permanently remove ads.   Note: There is a bug with 4.0 where users with the standalone unlocker may see ads when they first upgrade.  You typically fix this by just force stopping the app and restarting.  Ads should not come back after that.  Alternatively you can contact gonemadsoftware@gmail.com and I can help you out as well.  I have no intention on making users who already paid see ads. W...
Read more

GoneMAD Music Player 4.0 fixes (4.0.1 - 4.0.4)

By
There have been a few updates for GMMP 4.0 fixing issues since the release.  This post covers all of them so far.  4.0.4 should hopefully be the last one for a bit.  I think I fixed everything that has been reported so far that I could reproduce. 4.0.4 is currently in review and should be available on Google Play shortly Changelogs: 4.0.4 (2025-08-22): Fixed crash playing audio with more than 8 channels Fix rare crash trying to seek Crossfade errors should no longer stop playback Fixed date added getting set incorrectly on a long/restarted initial scan Fixed issue updating album artist art for album artists with no associated tracks Fixed smart crossfade. It will no longer incorrectly crossfade on consecutive tracks Status bar icon color should now match toolbar icon color Fixed some text / button colors when using dynamic theme 4.0.3 (2025-08-18): Updated translations Another audioengine fix 4.0.2 (2025-08-14): Smart playlists should now show the correct results when nav...
Read more

4.1

By
4.1 marks the end of life for Android Lollipop (5.0/5.1).  Some of GMMP's dependencies require the SDK level 23 or higher, so I was forced to also increase the min sdk to 23 (android 6.0).  According to the google play store statistics there are around 50 or so users on 5.0/5.1, so I do apologize for dropping support.  10 years of support is fairly decent nowadays anyway.   I've also increased the target SDK to android 16.  With this increase I had to account for the forced "edge-to-edge" that google is making all apps support.  If any UI element ends up behind the navigation buttons, certainly let me know.  I am pretty sure I did everything correctly but I only had one device that I was able to test on (pixel 6a) 4.1.0 (2025-09-03): Updated target SDK to Android 16 Updated dependencies Updated translations
Read more