title: Why Google Nearby Connections needs ACCESS_COARSE_LOCATION and/or ACCESS_FINE_LOCATION permissions?
body: <p>I googled very hard and still no explanations &quot;why?&quot; these permissions are needed to establish <strong>offline</strong>(no internet) connection between devices. I have simple app that requires only p2p-star strategy to exchange data between devices in master-slave pattern and I have troubles explaining to my users why my app needs them. &quot;Just because lib said so. That's why&quot;.</p>
  <p>Official documentation also said nothing to me.</p>
  <p><em>&quot;A primary goal of this API is to provide a platform that is simple, reliable, and performant. Under the hood, the <strong>API uses a combination of Bluetooth, BLE, and Wifi hotspots</strong>, leveraging the strengths of each while circumventing their respective weaknesses. This effectively abstracts the vagaries of Bluetooth and Wifi across a range of Android OS versions and hardware, allowing developers to focus on the features that matter to their users.&quot;</em></p>
  <p>PS: as I know ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION are about GPS</p>
  <p>PSS: in case this question will be answered here
  <a href="https://github.com/android/connectivity-samples/issues/204" rel="nofollow noreferrer">https://github.com/android/connectivity-samples/issues/204</a></p>