The pre-compiled version of Mesh Tether currently at https://commotionwireless.net/download (dated 9/17/2012) somehow disabled the local DHCP client, which had to be re-enabled at Settings -> Wireless -> Wi-fi settings -> [menu button] -> Advanced. This consequently disabled DHCP requests for all other wifi profiles stored on the phone (aka no IP connectivity), which was a bit unsettling until I found the cause.
My suspicion is this happened when I clicked on the "commotionwireless.net" profile that Mesh Tether inserted into Settings -> Wireless -> Wi-fi settings, but it was indeed quite non-obvious that enabling this profile would effectively disable all other stored wifi profiles that require DHCP. Seems very likely another user could encounter the same problem, and come to think that Mesh Tether somehow 'killed' their phone's wifi.
I realize this may just be a limitation of how Android OS handles wifi profiles with static IP addressing. However, maybe even just a strategically placed pop-up message warning users about DHCP being disabled could help avoid mishaps.
The pre-compiled version of Mesh Tether currently at https://commotionwireless.net/download (dated 9/17/2012) somehow disabled the local DHCP client, which had to be re-enabled at Settings -> Wireless -> Wi-fi settings -> [menu button] -> Advanced. This consequently disabled DHCP requests for all other wifi profiles stored on the phone (aka no IP connectivity), which was a bit unsettling until I found the cause.
My suspicion is this happened when I clicked on the "commotionwireless.net" profile that Mesh Tether inserted into Settings -> Wireless -> Wi-fi settings, but it was indeed quite non-obvious that enabling this profile would effectively disable all other stored wifi profiles that require DHCP. Seems very likely another user could encounter the same problem, and come to think that Mesh Tether somehow 'killed' their phone's wifi.
I realize this may just be a limitation of how Android OS handles wifi profiles with static IP addressing. However, maybe even just a strategically placed pop-up message warning users about DHCP being disabled could help avoid mishaps.