Dear all, We are trying to access to some *wpa_supplicant* functions that are not available in the API. The main goal is to access to the WiFi power management functions / states (i.e., controlling the WiFi sleep mode/state).
Instead of sending commands direct to the *wpa_supplicant, *we first try to access to the *wpa_supplicant* functions calling WifiNative methods through the NDK approach using JNI. Currently, we can run without problems the "isDriverLoaded()" functions from WifiNative using JNI approach, but the commands really related with * wpa_supplicant* have a strange behaviour. For instance, when calling "listNetworksCommands()" or similar calls the returned string is ALWAYS null. Is there a logic problem in this approach? Should send / create a direct interface to* wpa_supplicant* using the control interface or can we use this approach? -- Best Regards, Vítor Bernardo & Bruno Correia -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
