Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
Which developer feature does your feature request relate to? [ID: 1145660]
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Does this feature request already exist in the tracker? [ No ]
Identify the developer feature that is most relevant to your feature request: [ ] Data API [ ] Admin API [ ] Measurement Protocol [ ] BigQuery Export
Briefly describe the feature request. Add an official option in Android's Developer Options to allow users to change their display resolution (e.g., from Full HD to HD or 4K) directly from the device settings. This feature would provide a native, user-friendly way to adjust resolution based on performance or battery-saving preferences, similar to resolution scaling in Windows or other operating systems.
Expected Interaction and Outcome: In Developer Options, users would find a new "Display Resolution Scaling" section with selectable resolutions supported by their device. Selecting a resolution would instantly apply the change without requiring third-party apps or external tools.
(Optional) How does this feature request affect Google Analytics users that use your application? N/A
(Optional) How does this feature request affect Google Analytics developers? N/A
(Optional) What alternatives are you/your users using right now instead of the requested feature? Currently, users rely on ADB commands like adb shell wm size or third-party apps that often require root access to change the display resolution. These methods are not accessible for non-technical users and may compromise device security.
(Optional) If this feature request is not implemented, how would you address the issue at hand? Without this feature, users will continue relying on external tools or complex workarounds, which limits accessibility and could pose risks to the device. Implementing this natively would enhance the user experience for both developers and general users.