Load legacy Bluetooth user data at start
While switching to be a mainline module, the com.android.bluetooth app will change its name to be com.google.android.bluetooth. If we don't do anything, we will loose user configuration. The BluetoothMigrationForMainlineUser content provider give us a way to save the data from being deleted. Data retrieved is: * access permission (shared pref) * volume map (shared pref) * opp settings (shared pref) * device metaDatabase from bluetooth_db (sqlite) * opp database (sqlite) Removing previous migration in native code (it was for beta3 user) Bug: 241152450 Test: Manual testing Ignore-AOSP-First: Apex module is renamed only on internal for now Change-Id: I47ca62b076a683947ea772efa7c143dc828df06f
Loading
Please register or sign in to comment