QuinnLion
commented
2 weeks ago I've found out that this special backup just takes a copy of /data/misc/apexdata/com.android.tethering/WifiConfigStore.xml This file does set the MAC address used by the system. (Not just talking about randomized MAC address) wiping the file with /dev/null and rebooting (not nicely) seemed to have fixed my IP/WLAN Association conflict now.
Though I'm not sure the new MAC generated by the system upon reboot is the real MAC address. OUI is now correct though. the addresses set in /sys/class/ieee80211/[addresses,macaddress] are null (00:00:00:00:00:00) Not sure how to get the real hardware mac address.
Feel free to mark as solved or close this issue
Description Restored special.wifi.access.points to have it 'restore' the WiFi MAC of the device the backup was taken from.
Reseting Wifi and Bluetooth also baseband settings from within android did not fix it. I fear nothing short of a complete wipe will clear it. What file does this backup read and write to?
It should be noted that I've never had this sort of issue with TitaniumBackup. Different methods?
Steps To Reproduce
Expected behavior Expected to not restore unique device identifier to device that restores the backup. Screenshots No logs to collect at this moment.
System Information(please complete the following information):
Additional Notes
If you're on the latest Test version(from the TG-Channel or Matrix-Room) please report there directly, not here.
If you're on the latest github version:
If you're not on the latest github version. Update, then make sure that the bug is still there. If it's go further with reporting.
Thanks for reporting.