- Aug 26, 2011
- 29
- 15
I noticed a bug in setting MAC address of the WiFi interface on a Motorola RAZR XT910 (umts_spyder) running MIUI 2.12.14.
The MAC address of the WiFi interface is set to a value which seems randomised (although few users reported that two RAZRs running MIUI on the same WiFi network clashed due to non-unique MAC addresses being assigned, so it seems that the build enforces a pre-defined MAC address for all installations). This causes unexpected behaviour on networks which are configured to use MAC filtering or DHCP based on MAC addresses.
I tried to reconfigure WiFi driver by manually calling /system/bin/wifical.sh, however it fails due to a missing input file (/system/etc/wifi/TQS_D_1.7.ini) and erases WiFi driver non-volatile storage file (wl1271-nvs.bin) which forced me to reinstall MIUI.
Manually calling /system/bin/wifiupgradecal.sh didn't help as well (at least the config file wasn't erased and I was able to use WiFi).
I also wonder whether regeneration of wl1271-nvs.bin config file doesn't break WiFi regulatory settings.
The MAC address of the WiFi interface is set to a value which seems randomised (although few users reported that two RAZRs running MIUI on the same WiFi network clashed due to non-unique MAC addresses being assigned, so it seems that the build enforces a pre-defined MAC address for all installations). This causes unexpected behaviour on networks which are configured to use MAC filtering or DHCP based on MAC addresses.
I tried to reconfigure WiFi driver by manually calling /system/bin/wifical.sh, however it fails due to a missing input file (/system/etc/wifi/TQS_D_1.7.ini) and erases WiFi driver non-volatile storage file (wl1271-nvs.bin) which forced me to reinstall MIUI.
Manually calling /system/bin/wifiupgradecal.sh didn't help as well (at least the config file wasn't erased and I was able to use WiFi).
I also wonder whether regeneration of wl1271-nvs.bin config file doesn't break WiFi regulatory settings.