WiFi Manager 2.1.6
Subtitled: why I never buy any Andorid devices made by Samsung.
This update has a workaround for a firmware bug on the Samsung Galaxy Tab 10.1.
About a month or so ago, someone left a Market comment saying that the app crashes on his Galaxy Tab 10.1. With no way to contact the user via Market (thank you, Google, one way “communication” is so effective!), I had no way to verify and resolve the issue. In fact, I have two Honeycomb based tablets, and the app works just fine on both of them.
Now, two days ago, a very nice user contacted me via email, reporting that WiFi Manager crashed when trying to disable the device’s WiFi. He provided screenshots, one of them had an error message displayed by the firmware: “
the application does not have the android.permission.CHANGE_NETWORK_STATE permission“.
I added the permission, emailed the apk to the user, the issue went away.
And here is why I “looove” Samsung.
Working with WiFi does not require
android.permission.CHANGE_NETWORK_STATE. It requires
android.permission.CHANGE_WIFI_STATE, which is a different permission.
The firmware on the Galaxy Tab 10.1 thinks that
CHANGE_NETWORK_STATE is required for disabling WiFi – probably because the device also has a 3G modem, and disabling WiFi kind of, sort of, like, maybe implies enabling 3G (which might be done a bit later by the firmware and not by the application that disabled WiFi).
This is wrong and is clearly a bug in the firmware.
All my users will now need to update the app manually due to the added permission, which is an inconvenience.
I wonder how this one slipped past Google’s certification testing. Perhaps this is not tested by the CCD, or perhaps firmware updates are not required to be submitted for testing, only the initial releases are.
The latter seems likely – seeing how the 3.2.1 firmware for the Motorola Xoom also has a serious issue with WiFi APIs (a thread deadlock, it seems).