Q 1: Specifying SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION doesn’t seem to hide navigation and status bars?
A: You need to tell the system how you want it laid out. SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN: Full screen, with the status bar floating above the app; SYSTEM_UI_FLAG_LAYOUT_STABLE: Keeps the view stable, using the most extreme layout.
SetSystemUiVisibility () only takes effect when the specified view is visible. More specifically, the specified view must remain visible for the navigation bar to remain hidden.
Q2: Are there detailed documentation on optimizations for hardening and hot fixes?
A: These are probably not special features that most developers need to touch, and different hardening and hotfixes have different designs and implementations. We have worked directly with most common hardening and thermal repair vendors to ensure that their solutions guarantee maximum compatibility and performance. If you have a more specific problem, please contact your hardening or hot fix solution provider.
Q 3: After the MAC address is randomly assigned, if the router sets a MAC address whitelist, the mobile phone cannot be connected to the router. How do I solve this problem?
A: The system knows the real MAC address, but it doesn’t report it to the application. You can view the actual MAC address on the system Settings page and add the MAC address to the whitelist.
Q 4: Android 10 has a lot of changes in security features. Are there any technical documents that can guide developers on how to upgrade and adapt?
A: See the Android developer website (specifically privacy enhancement, behavior change, and migration guidelines), as well as general best practices.
Q 5: How do I track users when I reinstall (non-login) applications after the system is upgraded from Android P to Android 10?
A: Use SSAID (Secured Settings Android Id). This ID is the same among applications signed by the same developer’s signature key under the same system user. But it will be changed when it is restored to factory Settings.
Q6: What is the scope of SAF access for an application?
A: In Android 10 and earlier, apps can access any specified directory with the user’s consent. As we mentioned earlier, in the next big version of Android, certain directories won’t be accessible. If this causes problems with your application, please tell us the specific use case.
Q 7: Non-SDK interface restrictions: Will changes to this restriction in future Android versions make it difficult for developers to maintain? Will static scan tools be added to the build process in the future?
A: We will continue to provide documentation and technical support for non-SDK interface changes. The static scan tool is a one-line command to run, and you can add a postbuild command to the build process yourself.
Q 8: Device ID: Indicates whether the Android ID can be used to ensure that devices do not duplicate each other. According to statistics of other departments, Some Android ids are duplicated.
A: Statistically, Android ids have very low repetition rates. If you find two devices with the same ID, please tell us the manufacturer and model of the device.
Q 9: Sandbox storage: Android 10 allows path access to media resources. Is the DATA column in the media resource queried by the ContentResolver available?
A: DATA is deprecated and you should not use it. If you want to use paths to access media resources, you can use the java.io.File class. You can use it to access media files that belong to your application or that your application is authorized to access.
Q 10: Is single/interim authorization currently supported?
A: Not at the moment, but we are considering providing support.
Q 11: Permissions: Provide authorization logs/records?
A: Under what circumstances is it needed? For privacy reasons, applications should not obtain permission request records from other applications.
Q 12: Access to screen content is restricted. Does the screenshot function belong to “screen content access”?
A: Screen access protection means that one application accesses the screen content of another application. If this refers to the application accessing its own DrawingCache, no special permissions are required.
Q 13: Activity detection and screen recording, how compatible with older devices? Will the restrictions on Android 10 apply to apps with targetApi 29, or all apps running on Android 10?
A: Please refer to this documentation for the relationship between the permissions associated with active detection and the targetSdkVersion of the application.
Q 14: The next release preview mentioned in the file storage talk is the next minor version of Android 10?
A: This refers to the next major release.
Q 15: Does a foldable device have a callback to know whether it is currently in collapsed or expanded mode?
A: No, we want the application to be more universal with support for different screen resolutions. Please use onConfigurationChanged or tell us more specific requirements.
Click here toSubmit product feedback suggestions
