Android system settings may be not persistent after AMS application bootstrap

Bug #2092393 reported by Gary.Wang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Anbox Cloud
Fix Released
Medium
Gary.Wang

Bug Description

Certain functions required by Anbox use built-in hooks to modify Android system settings for proper functionality. However, as reported that, these settings are sometimes not persistent after AMS application bootstrap. For example, in Android 12, the "blast adapter" setting is intended to be disabled, but after launching a fresh instance from an application built on Android 12, the value remains null
```
root@ams-ctin5g1f2his8l2cm6q0:~# anbox-shell settings get global use_blast_adapter_sv
null
```

Gary.Wang (gary-wzl77)
Changed in anbox-cloud:
milestone: none → 1.24.2
assignee: nobody → Gary.Wang (gary-wzl77)
importance: Undecided → Medium
status: New → Triaged
Gary.Wang (gary-wzl77)
Changed in anbox-cloud:
status: Triaged → In Progress
Gary.Wang (gary-wzl77)
Changed in anbox-cloud:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.