blocks|key|952557|text|发生这种情况的原因有两个(来自这里)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|952558|每个应用程序都有高优先级的通知配额，如果发送的通知太多，操作系统将取消它们的优先级。|ordered-list-item|952559|谷歌要求用户与高优先级的FCM消息进行某种形式的交互(以防止开发者滥用)。因此，如果您发送“隐藏”的FCM通知，例如，显示在一个无声的通知通道中，您的应用程序的配额将被取消优先级。另外，用户需要打开应用程序，或者在某个时间间隔内单击通知(我没有看到记录的实际时间框架)。如果他们不这样做，它也会被取消优先次序。|952560|列表项目|952561|因此，听起来您的应用程序的FCM配额被取消了优先级，您需要弄清楚哪种方案适用。|952562|entityMap|0|LINK|mutability|MUTABLE|url|https://firebase.google.com/docs/cloud-messaging/android/message-priority^0|F|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$]]|$1|G|3|H|5|F|7|Z|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|10|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

There are 2 reasons this may be happening (from <a href="https://firebase.google.com/docs/cloud-messaging/android/message-priority" rel="nofollow noreferrer">here</a>):
<ol>
<li>There are high priority notification quotas for each app, and if you send too many of those notifications, the OS will de-prioritize them</li>
<li>Google requires that there is some kind of user interaction with the high-priority FCM messages (to prevent abuse by developers). So, if you send &quot;hidden&quot; FCM notifications that, for example, show up in a silent notification channel, your app's quota will be de-prioritized. Also, the user needs to either open the app, or click on the notification within some interval (I didn't see the actual time frame documented). If they don't, it gets de-prioritized as well.</li>
<li>List item</li>
</ol>
So, it sounds like your app's FCM quota was de-prioritized, and you'll need to figure out which scenario applies

blocks|key|238660|text|一般来说，你是正确的，如下文所述：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|238661|FCM被优化为与Doze和App备用空闲模式一起工作。FCM高优先级消息可以让你可靠地唤醒你的应用程序来吸引用户。在Doze或App备用模式下，系统传递消息，并允许应用程序临时访问网络服务和部分唤醒，然后将设备或应用程序返回到空闲状态。对于时间敏感的、用户可见的通知，请考虑使用高优先级的消息来启用Doze模式下的传递。高优先级消息预计会导致通知。有关更多信息，请参见FCM关于高优先级消息的指导。|blockquote|238662|然而，他们也提到：|238663|最重要的是，所有应用程序都应该能够通过正确管理网络连接、警报、作业和同步，以及使用FCM消息来支持Doze。对于一组狭窄的用例，这可能是不够的。对于这种情况，系统提供了一个可配置的应用程序列表，这些应用程序部分不受Doze和App备用优化的限制。部分豁免的应用程序可以在Doze和App备用期间使用网络并持有部分唤醒锁。然而，其他限制仍然适用于应用程序，就像对其他应用程序一样。例如，应用程序的作业和同步被推迟(在API级别23及以下)，并且它的常规AlarmManager警报不会触发。应用程序可以通过调用isIgnoringBatteryOptimizations()来检查其当前是否在豁免列表中。|238664|有时，OEM也会改变打瞌睡模式的行为，这会产生与Google文档中所述功能略有不同的功能。所以我建议按照他们在文件中的提示：|238665|用户可以在设置>电池>电池优化中手动配置豁免应用程序列表。或者，该系统为应用程序提供了要求用户豁免它们的方法:大多数应用程序都应该调用包含ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS的意图。满足可接受用例的应用程序可以调用包含ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS意图操作的意图，让用户直接将应用程序添加到豁免列表中，而无需进入系统设置。注意:+Google政策禁止应用程序请求直接豁免安卓6.0%2B+(Doze和App备用)的电源管理功能，除非该应用的核心功能受到不利影响。应用程序可以通过调用isIgnoringBatteryOptimizations()来检查其当前是否在豁免列表中。|238666|我相信这能解决你的问题|238667|博士-+https://developer.android.com/training/monitoring-device-state/doze-standby|offset|length|238668|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/training/monitoring-device-state/doze-standby^0|0|0|0|0|0|0|0|4|23|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|12|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|15|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|16|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|17|8|@]|9|@$Q|18|R|19|1|1A]]|A|$]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

In general, you are correct, as stated in:
<blockquote>
FCM is optimized to work with Doze and App Standby idle modes. FCM high priority messages let you reliably wake your app to engage the user. In Doze or App Standby mode, the system delivers the message and gives the app temporary access to network services and partial wakelocks, then returns the device or app to the idle state. For time sensitive, user-visible notifications, consider using high priority messages to enable delivery in Doze mode. High priority messages are expected to result in notifications. See FCM's guidance on high priority messages for more information.
</blockquote>
How ever, they also mention:
<blockquote>
lmost all apps should be able to support Doze by managing network connectivity, alarms, jobs, and syncs properly, and by using FCM messages. For a narrow set of use cases, this might not be sufficient. For such cases, the system provides a configurable list of apps that are partially exempt from Doze and App Standby optimizations.
An app that is partially exempt can use the network and hold partial
wake locks during Doze and App Standby. However, other restrictions
still apply to the app, just as they do to other apps. For example,
the app’s jobs and syncs are deferred (on API level 23 and below), and
its regular AlarmManager alarms do not fire. An app can check whether
it is currently on the exemption list by calling
isIgnoringBatteryOptimizations().
</blockquote>
Sometimes, OEM's also change the behavior of doze mode which creates bit different functionality than those stated in Google's documentation. So I'd suggest following their tip in the documents:
<blockquote>
Users can manually configure the list of exempted apps in Settings &gt; Battery &gt; Battery Optimization. Alternatively, the system provides ways for apps to ask users to exempt them:
Most apps should invoke an intent that contains the ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS.
Apps that satisfy an acceptable use case can instead invoke an intent that contains the ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS intent action to let the user add the app to the exemption list directly, without going to system settings.
Note: Google Play policies prohibit apps from requesting direct exemption from Power Management features in Android 6.0+ (Doze and App Standby) unless the core function of the app is adversely affected.
An app can check whether it is currently on the exemption list by calling isIgnoringBatteryOptimizations().
</blockquote>
I believe this should fix your problem
Doc - <a href="https://developer.android.com/training/monitoring-device-state/doze-standby" rel="nofollow noreferrer">https://developer.android.com/training/monitoring-device-state/doze-standby</a>

I'm sending a data-message via FCM with HIGH priority.
<pre><code>curl -X POST -H &quot;Authorization: Bearer ya29.c.b0AXv...&quot; -H &quot;Content-Type: application/json&quot; -d '{
 &quot;message&quot;: {
 &quot;topic&quot; : &quot;mytopic&quot;,
 &quot;data&quot;: {
 &quot;message&quot;: &quot;my_unique_data&quot;
 },
 &quot;android&quot;:{
 &quot;priority&quot;:&quot;high&quot;
 },

 }
}' https://fcm.googleapis.com/v1/projects/myproject/messages:send
</code></pre>
After receipt - I call a notification. If Android is active, this works.
But if the smartphone's screen is off, and the smartphone is stationary for a while, and I send the data message again, the notification doesn't show up until I little move the phone.
I guess the Android is in DOZE mode, but the documentation states that a high-priority message FCM puts the smartphone out of this mode.
Help solve the problem, please.

Why Android does not exit DOZE mode, despite the high priority of the message in FCM?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在通过FCM发送一条高优先级的数据信息。curl -X POST -H "Authorization: Bearer ya29.c.b0AXv..." -H "Content-Type: application/json" -d '{  "message": {    "topic" : "mytopic",   ...

问为什么Android不退出打瞌睡模式，尽管FCM中的消息具有很高的优先级？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么Android不退出打瞌睡模式，尽管FCM中的消息具有很高的优先级？EN