blocks|key|703888|text|我还需要ACCESS_COARSE_LOCATION许可吗？|type|blockquote|depth|inlineStyleRanges|entityRanges|data|703889|不是的。|unstyled|703890|我需要粗定位的用例是什么？|703891|如果您不要求ACCESS_FINE_LOCATION，但您需要位置数据，并且您愿意让这些数据是模糊的(例如，从用户的位置到城市街区附近)。在LocationManager的情况下，您只能使用NETWORK_PROVIDER；在Play服务融合位置提供程序的情况下，它们应该在内部处理这个问题。|offset|length|style|CODE|703892|很久很久以前，用户在安装时就被告知该应用程序是想要粗访问还是细位置访问。用户可能会接受那些想要粗略访问的应用程序，但拒绝那些希望获得良好访问权限的应用程序。|703893|由于这方面的UI已经发生了变化，用户在确定应用程序是否需要粗略的位置权限时会遇到相当大的困难，因此我怀疑大多数开发人员只是要求提供良好的位置权限。尽管如此，如果你知道你的应用程序不需要那么高的精确度(例如，你想要天气预报的位置)，请求粗略的定位许可是隐私方面的一个不错的“小菜一碟”，将来可能再次证明这是有益的。|703894|更新2021-11-16：如果您要求使用ACCESS_FINE_LOCATION，Android12会更改用户界面.访问，选择“近似”而不是“精确”。|BOLD|703895|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/training/location/permissions?hl=en#accuracy^0|0|0|0|6|K|1Y|F|2N|G|0|0|0|0|C|K|K|1M|2|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|12|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|13|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|14|8|@$I|15|J|16|K|L]|$I|17|J|18|K|L]|$I|19|J|1A|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1D|8|@$I|1E|J|1F|K|S]|$I|1G|J|1H|K|L]]|9|@$I|1I|J|1J|1|1K]]|A|$]]|$1|T|3|-4|5|D|7|1L|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

<blockquote>
Do I also need the ACCESS_COARSE_LOCATION permission?
</blockquote>
No.
<blockquote>
What's the use case where I need the coarse location?
</blockquote>
If you do not ask for <code>ACCESS_FINE_LOCATION</code>, but you need location data, and you are willing for that data to be fuzzy (say, up to around a city block from the user's position). In the case of <code>LocationManager</code>, you can only use the <code>NETWORK_PROVIDER</code>; in the case of the Play Services fused location provider, they should handle this internally.
Once upon a time, long long ago, users were told at install time whether the app wanted coarse or fine location access. Users might accept apps that wanted coarse access but reject apps that wanted fine access.
Since the UI for this has changed, and users would have a fair bit of difficulty determining whether an app wants coarse or fine location permission, I suspect that most developers just ask for fine location permission. That being said, if you know that your app does not need that level of accuracy (e.g., you want the location for a weather forecast), asking for coarse location permission is a nice &quot;tip of the hat&quot; in the direction of privacy and may prove beneficial once again in the future.
UPDATE 2021-11-16: Android 12 changes the UI if you ask for <code>ACCESS_FINE_LOCATION</code>. <a href="https://developer.android.com/training/location/permissions?hl=en#accuracy" rel="noreferrer">The user now has the option of downgrading you to only getting <code>ACCESS_COARSE_LOCATION</code> access</a>, by choosing &quot;Approximate&quot; instead of &quot;Precise&quot;.

blocks|key|2730784|text|不不需要使用粗糙的位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2730785|粗定位是指网络提供商的位置，而精细定位是指GPS提供者和网络位置提供者。所以很好的位置涵盖了这两个，你不需要使用另一个。|2730786|为了从NETWORK_PROVIDER或GPS_PROVIDER接收位置更新，您必须在Android清单文件中分别声明ACCESS_COARSE_LOCATION或ACCESS_FINE_LOCATION权限，以请求用户的许可。如果没有这些权限，当请求位置更新时，应用程序将在运行时失败。
如果同时使用NETWORK_PROVIDER和GPS_PROVIDER，则只需要请求ACCESS_FINE_LOCATION权限，因为它包括两个提供程序的权限。ACCESS_COARSE_LOCATION的权限只允许访问NETWORK_PROVIDER。|blockquote|2730787|这是供您参考的链接。|offset|length|2730788|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/guide/topics/location/strategies.html#Permission^0|0|0|0|0|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|V|8|@]|9|@$I|W|J|X|1|Y]]|A|$]]|$1|K|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

No you don't need to use coarse location.

Coarse location is for network provider's location and fine location is for both GPS provider and network location provider. So fine location covers both and you don't need to use anther one.

<blockquote>
 In order to receive location updates from NETWORK_PROVIDER or
 GPS_PROVIDER, you must request the user's permission by declaring
 either the ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION permission,
 respectively, in your Android manifest file. Without these
 permissions, your application will fail at runtime when requesting
 location updates.
 
 If you are using both NETWORK_PROVIDER and GPS_PROVIDER, then you need
 to request only the ACCESS_FINE_LOCATION permission, because it
 includes permission for both providers. Permission for
 ACCESS_COARSE_LOCATION allows access only to NETWORK_PROVIDER.
</blockquote>

<a href="https://developer.android.com/guide/topics/location/strategies.html#Permission" rel="noreferrer">This</a> is a link for your reference.

blocks|key|378048|text|地点可以通过两种方法来确定：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|378049|Using+NETWORK_PROVIDER
Using+GPS_PROVIDER|code-block|syntax|javascript|378050|使用NETWORK_PROVIDER
使用此提供程序所需的Android权限为ACCESS_COARSE_LOCATION或ACCESS_FINE_LOCATION。|ordered-list-item|offset|length|style|BOLD|378051|使用GPS_PROVIDER
使用此提供程序所需的Android权限仅为ACCESS_FINE_LOCATION。|378052|entityMap^0|0|0|2|G|0|2|C|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|I|7|T|8|@$J|U|K|V|L|M]]|9|@]|A|$]]|$1|N|3|O|5|I|7|W|8|@$J|X|K|Y|L|M]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

Location can be determined by two ways:

<pre><code>Using NETWORK_PROVIDER
Using GPS_PROVIDER
</code></pre>

<ol>
<li>Using NETWORK_PROVIDER

Android permissions required for using this provider are either
ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION.</li>
<li>Using GPS_PROVIDER

Android permissions required for using this provider are only
ACCESS_FINE_LOCATION</li>
</ol>

blocks|key|704044|text|简单地说，ACCESS_FINE_LOCATION给出了更好、更准确的位置，而ACCESS_COARSE_LOCATION给出了不太准确的位置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|704045|entityMap^0|5|K|13|M|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

In simple word <code>ACCESS_FINE_LOCATION</code> gives you better and accurate location and <code>ACCESS_COARSE_LOCATION</code> gives you less accurate location.

blocks|key|378090|text|ACCESS_FINE_LOCATION包括ACCESS_COARSE_LOCATION。然而，有一个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|378091|ACCESS_COARSE_LOCATION给你最后知道的位置，它是电池友好型的https://developer.android.com/training/location/retrieve-current.html#setup，它依赖于Google服务|offset|length|378092|但是，如果您需要实时/实时位置，请使用ACCESS_FINE_LOCATION它为您提供实时/实时位置。不过，您需要使用LocationListener。|378093|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/training/location/retrieve-current.html#setup^0|0|14|23|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

ACCESS_FINE_LOCATION includes ACCESS_COARSE_LOCATION. However, there is a catch:

ACCESS_COARSE_LOCATION gives you last-known location which is battery friendly <a href="https://developer.android.com/training/location/retrieve-current.html#setup" rel="nofollow noreferrer">https://developer.android.com/training/location/retrieve-current.html#setup</a>
This has a dependency on Google Play Services

However, if you need something like live/ real-time location, use ACCESS_FINE_LOCATION
It gives you live/ real-time location. You'll need to use a LocationListener though.

I am building an Android app that will track the user's geolocation and draw their route on a map.

I am using the Google Play Services location API, as described <a href="http://developer.android.com/training/location/index.html" rel="noreferrer">here</a>.

It is intuitive that my application requires the <code>ACCESS_FINE_LOCATION</code> permission, which I put in the manifest:

<pre><code>&lt;uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/&gt;
</code></pre>

Do I also need the <code>ACCESS_COARSE_LOCATION</code> permission?
What's the use case where I need the coarse location?

When should I use ACCESS_COARSE_LOCATION permission?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在构建一个Android应用程序，它将跟踪用户的地理位置，并在地图上绘制他们的路线。我正在使用Google服务位置API，正如所描述的。我的应用程序需要ACCESS_FINE_LOCATION权限，这是很直观的，我把它放在清单中：<uses-permission android:name="android.perm...

问什么时候应该使用ACCESS_COARSE_LOCATION权限？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么时候应该使用ACCESS_COARSE_LOCATION权限？EN