To generate a record of events that occur in your application and that are causing problems such as ANR or Crashes, you can check:
Google Play Console.
In the case of having your application published in the Google Play Store, in the administration console you can track problems that are occurring in your application, whether they are ANR (Android does not respond) or Crashes (Errors), enter < a href="https://developer.android.com/topic/performance/vitals/"> Android Vitals and subsequently ANR's or Crashes ,
You can view the list and access more detailed information about the error, you can even view the stacktrace.
Fabric - Crashlytics
This framework can be implemented in a simple way in your application and you can get information about errors in your application but unlike Google Play Console, you do not need to have your application published, the error log will be made if the application counts with internet connection.
You can review more information here:
What is Fabric Crashlytics and how to configure it for Android?
Application Insights
Recommended by our friend @FredyFx
link
link
Regarding the error that your application shows:
has been installed on different android, 4.4.4, 5, 6. but there are two
smartphone that is stopped app one is version 6.0.1 and the other
android 8 oreo.
You must remember that for operating systems from Android 6.0 (API 23) some Permits that are considered risky :
should be required at run time and it is not enough to add them within the AndroidManifest.xml
file.
Review the documentation: How to request permissions at runtime
Examples:
Error showing the external file directory in an AlertDialog in android 6.0 (READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE)
Permissions at run time