Manet Manager can get into a funky state where it will refuse to setup the manet about android-manet-manager

[duhmojo]

Oh, and jrobble, I noticed that Manet Manager no longer seems to have issue with Wifi being enabled before starting the manet? I'm both scanning for wifi access point and connected to the manet at the same time. If this is true then it solves my issue with starting/stopping ManetManager, which I also have working pretty well now.

[duhmojo]

Actually scratch that last comment. Manet Manager now seems to be ok with flipping wifi in the OS on and off. However if you have a manet established and turn wifi on, that node in the manet will disappear. If you disable/enable the manet again, it will rejoin without any headaches. This is still good information, as I know that if Manet Manager and wifi get in a conflicting state, I can easily recover from it be restarting the manet.

[jrobble]

Turning the Wi-Fi on though the Settings app while the device is in ad-hoc mode will mess up the Manet Manager. Doing so will reload the Wi-Fi drivers and cause the Android framework to run wpa_supplicant, which will put the Wi-Fi chip in managed mode (causing it to drop out of ad-hoc mode). Under the hood the olsrd routing protocol will still be running. Thus, the Manet Manager will be in a bad state and show both the enabled and disabled icons.

"SET failed on device eth0 ; No such device." is most likely caused by a problem with loading the Wi-Fi driver.

I tried to implement the Manet Manager so that it will gracefully turn off the Wi-Fi if it's active before starting ad-hoc mode. To be more accurate, Wi-Fi is still active under the hood, but the Android framework doesn't know about it.