Fixed
Status Update
No update yet.
Comments
ia...@gmail.com
ia...@gmail.com
Great, thank you for the update and analysis.
https://issuetracker.google.com/issues/122098785
pu...@google.com
pu...@google.com
I can just second this. This is the far most pressing issue of the Android ecosystem for developers and users and despite the Android's team promise to force OEM into being more transparent about the non-standard restrictions they are doing, nothing is really happening and the situation is worst and worst year a over year (with the only bright exception of Nokia)..
Not only new restrictions are being introduced year by year, but in addition OEMs maintain app whitelists which are highly anti-competitive and even more damaging for smaller developers..
The only education for the users on what is happening now comes from thehttps://dontkillmyapp.com/ project and in most cases it reaches them ex post when they are already angry with their developers.
Not only new restrictions are being introduced year by year, but in addition OEMs maintain app whitelists which are highly anti-competitive and even more damaging for smaller developers..
The only education for the users on what is happening now comes from the
au...@gmail.com
Hello
pc...@gmail.com
Hello, big thanks for paying attention to this issue and to update internal reports! This is very much appreciated.
I think issuehttps://issuetracker.google.com/issues/122098785 should be updated. Maybe back in 2018 the issue was mainly with Chinese vendors (see issue title), probably due to the missing regulatory effect of Play Store causing lower app quality in that region.
But now in 2021 the issue has grown immensely. We see this is a major issue with even non-Chinese OEMs with huge global market shares like Samsung. And their approach to process management which is devastating for many very useful apps and use-cases and for smaller devs is becoming a "defacto" standard.
I think issue
But now in 2021 the issue has grown immensely. We see this is a major issue with even non-Chinese OEMs with huge global market shares like Samsung. And their approach to process management which is devastating for many very useful apps and use-cases and for smaller devs is becoming a "defacto" standard.
ka...@gmail.com
Thank you for the update.
We’ve shared your update with our product and engineering teams. Please provide any updates within the issue
wc...@gmail.com
'still being investigated' can be just a joke. It's a 2-3 years issue and getting worse and worse. I'm also thinking I'd rather develop for iOS.
Take it more seriously. Are the covid tracker app not enough shame for you?
Take it more seriously. Are the covid tracker app not enough shame for you?
ch...@gmail.com
"is currently still being investigated" hahahahaahahahaahahahaa
ia...@gmail.com
redacted
au...@gmail.com
@6 Google, remember that it's not just things related to battery optimizations and killing of processes in weird situations. It has become way beyond this topic.
It's many times breaking behaviors by default, having their own made-up rules and permissions, and sometimes even against clear documentations on the Android website.
Example here:
https://issuetracker.google.com/issues/150627645
And this is on a relatively new Android version, and I'm sure it still exist on Android 11, and soon on Android 12.
It's many times breaking behaviors by default, having their own made-up rules and permissions, and sometimes even against clear documentations on the Android website.
Example here:
And this is on a relatively new Android version, and I'm sure it still exist on Android 11, and soon on Android 12.
vv...@google.com
Regarding
Could you please share with us a use-case where your app needs to be in the foreground and retrieve the accelerometer data under Doze?
Could you please share with us a use-case where your app needs to be in the foreground and retrieve the accelerometer data under Doze?
Description
What
User experience
What type of Android issue is this?
Battery / Charging
What steps would let us observe this issue?
What did you expect to happen?
Work
What actually happened?
When go to setting, Adaptive Charging, limit to 80% is gone
What was the effect of this issue on your device usage, such as lost time or work?
None - device worked normally
When
Time and frequency
Time when bug report was triggered: Nov 13, 2024 1:28 PM GMT+08:00
How often has this happened?
I don't know
Where
Component
Suggested component: <not visible> (1630575)
Build and device data
- Build Number: google/husky_beta/husky:15/BP11.241025.006/12620009:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 244433036 (24.44.33 (260408-694629214))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677803942 (131.0.6778.39)
System App (Updated)
Network operator: MY MAXIS
SIM operator: MY MAXIS
Network operator: YES
SIM operator: Yes 5G
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)https://developer.android.com/preview/feedback#feedback-app .
To learn more about our feedback process, please visit