title: Is READ_LOGS a normal or dangerous Android permission?
body: <p>I am getting very conflicting information regarding the use of <code>android.permission.READ_LOGS</code> Android permission. Firstly, the Android Documentation website does not specify the protection level of this permission. It is neither classified as normal, nor dangerous. They do specify the following:</p>
  
  <blockquote>
    <p>"Not for use by third-party applications, because Log entries can
    contain the user's private information."</p>
  </blockquote>
  
  <p>Some websites say not to use it for the same privacy concerns.
  However I have some issue with that:</p>
  
  <ol>
  <li>When I tested this permission in my app on Android 7.1.1 (Nexus 5X) and Android 4.4.2 (old Samsung 8" tablet), neither of them prompted me that the app required this permission. Both said that the app requested "no special permissions". This only happens if the permission is deemed "normal", in which case it is automatically granted.</li>
  <li>Secondly, using this permission, I can only view logs from logcat pertaining to my app, which does not log any personal information. Hence, I don't violate any privacy either. I thought this permission may allow me to see other app's logs, causing privacy issues. </li>
  </ol>
  
  <p>So, if this is the case, then is it deemed safe to use this permission in a production version of the app? It would help me a lot in debugging strange bugs users face if they can send me a logcat by the press of a button.</p>
  
  <p>EDIT: Ok, now I am quite confused. It appears that I don't need to explicitly specify this permission in the manifest either.</p>