Closed matthijskooijman closed 3 years ago
thanks @matthijskooijman for the report!
ConfigKey
conflicts with a6db43416838e6b5e553716542a89149cea6dff9 and AllowedProtocols
with b540f4460624b2267be1ba268adf2a3ab478ea79 from PR https://github.com/mnalis/android-wifi-upgrade/pull/5 by @jimklimov
@jimklimov can you share what Android version and phone model you use? Obviously what works for one fails for other and vice versa, so I'd like to at least document it in readme (or maybe add options to select which to use).
For now I've documented it and created a new wapi
git branch, and reverted those two changes in master
.
If I get more information about what OS version require WAPI support, I'll update and maybe make it a config option.
Thanks for your report!
I see this issue is closed, but figured I'd add a note here: I am on Android 11 & LIneageOS and master
appeared to work fine here.
BTW the file location changed to /data/misc/apexdata/com.android.wifi
in recent Androids. Plz add to the README
@ildar thanks, added
I tried your script today to import a wpa_supplicant.conf from Android 7 (Fairphone Open OS) into Android 10 (Lineage 17.1), but it needed some changes to work. In the hope that this might benefit others, I'm documenting what I did here.
Without changes, the produced file produces the following logcat warning:
Comparing the system-generated file with the script-generated file confirms that there should not be a dash between the SSID and the keymgmt. Other changes are the file version number (1 vs 3), but that does not seem to matter, Android autobumps it. And some of the Allowed fields have a few more bits in the script-generated version (probably because the script allows everything by default). However, the AllowedProtocols field does seem to cause a problem:
Bit 3 is WAPI, I suspect Android 10 does not support it anymore (here is also some docs with the WAPI value grayed out). Unsetting that bit, fixes the error.
With the changes below, I managed to import 63 of my networks (one failed, but that one is a bit weird in wpa_supplication.conf).