Re: [android-porting] Android Wifi-Tethering

Hey Daniel, and Android's netd daemon is also not able to achieve this. The > SoftapController uses the private functions of the Broadcom driver > which are not supported by our driver. > > Yeah, the current code is pretty broadcom specific. Going forward, we will be using hostapd to provide mor

Re: [android-porting] wifi scan

Look at WifiSettings & WifiStateTracker. Its more frequent when you are in the settings (6s) than otherwise (15s). The WifiManager API allows initiatiation of scans at the rate an app wants to. On Thu, Aug 26, 2010 at 5:20 AM, guru wrote: > Hi all > > what is the default time gap between succe

Re: [android-porting] Re: wifi scan

/src/com/android/settings/wifi/WifiSettings.java > > frameworks/base/wifi/java/android/net/wifi/WifiStateTracker.java > > > > I looked these files. > > > > Thanks > > Gururaja B O > > > > I did not get where he is specifying 6s > > > > On Thu, Aug 26

Re: [android-porting] Re: How to enable/turning phone into a WiFi hot spot

Look at the following file: --- a/overlay/frameworks/base/core/res/res/values/config.xml +++ b/overlay/frameworks/base/core/res/res/values/config.xml @@ -132,6 +132,14 @@ "eth\\d" + + +"wl0.1" + + On Mon, Aug 30, 2010 at 4:40 AM, guru wrote: > Hi Andy Burns,

Re: [android-porting] wifi - signal strength

Look at wpa_cli for checking on values returned from supplicant # wpa_cli driver rssi It could be that the driver ioctls are failing. On Mon, Aug 30, 2010 at 10:52 AM, Robert Greenwalt wrote: > If the supplicant is returning an invalid signal strength, it's a > supplicant issue, not the applica

Re: [android-porting] Re: Android 2.2 Froyo Wifi Hotspot

In addition to getting the UI, these are the other pieces: - the driver needs to support it. As I understand, the ti wlan driver from AOSP does not support it. - the network daemon (look at system/netd) IOCTL interface is broadcom specific. You need to either use the driver specific IOCTLs or port

Re: [android-porting] WiFi always scanning after porting to Froyo

All the UI is doing is calling load driver & a start supplicant followed by running dhcp on receiving a connect from supplicant. If it is only showing "Disconnect->Scanning", it means the association never went through. You should verify if all the modules are loaded after doing a "turn on". Also

Re: [android-porting] wifi is not disconnecting in suspend mode

On Sun, Sep 12, 2010 at 9:27 PM, guru wrote: > HI All > > I heard that when phone goes to suspend mode, wifi should disconnect > and after we again press the power button then it should connect. > > Thats not correct. In suspend mode (which happens when you put the screen off), the driver typica

Re: [android-porting] wifi is not disconnecting in suspend mode

n, >> >> where this default 15min is specified in the code base? Please let me >> know. >> so if phone wakes up within 15min then wifi will still be in connected >> state. I will check this by waiting for 15 min. >> >> Thanks >> Gururaja B O >> >&

Re: [android-porting] doubts about wifi application

code is your friend. The API is documented at http://developer.android.com/reference/android/net/wifi/package-summary.html On Mon, Oct 25, 2010 at 3:45 AM, thirumalai Pachamuthu < thirumalai.andr...@gmail.com> wrote: > Hi irfan, > is there any documents to understand the wifi related stuf

Re: [android-porting] Cannot automatically detect AP SSID on wifi restart

> > > Now the thing is on first AP scan, it finds the AP SSID, and I'm able > to connect and browse the internet. However, for the second scan, the > AP name doesn't get displayed. If I manually enter the SSID name, it > immediately connects and is able to get an IP address and the wifi > network w

Re: [android-porting] android-2.2.1 cannot get AP SSID after wifi restart

> > However, if you just turn off and turn back the wifi on, it doesn't > automatically associate with the AP. > > You need to have more debugging enabled in the framework (WifiService & WifiStateTracker) to understand what is happening in the framework. Log the sequence of driver commands issued t

Re: [android-porting] Re: android-2.2.1 cannot get AP SSID after wifi restart

I continue to see scan failures in the wpa_supplicant log, investigate that. Look at how the interaction with the supplicant directly from the wpa_cli works. What happens when you load the driver, start the supplicant and initiate connection with a configured network from adb shell interface: # s

Re: [android-porting] " Wifi Driver reports HUNG - reloading". error with Android UI wpa_supplicant

On Sun, Sep 25, 2011 at 11:54 PM, Sudha Daram wrote: > Hi all, > > When i run wpa-supplicant through UI it always saying "unable to scan > for Networks" and my driver is always getting reloaded. > But my driver was able to scan for APs. > > This problem is not there if I run the wpa_supplicant ma

Re: [android-porting] E/NetworkManagmentService( 896): Unexpected response code 600

On Wed, Nov 2, 2011 at 1:59 AM, Sudha Daram wrote: > Hi all, > > I am porting wifi driver to android. It is getting invoked properly. > Wpa_supplicant is invoking the driver functionality. but soon after > starting wpa_supplicant, "supplicant died" error is coming. > NetworkManagementService erro

Re: [android-porting] dhcp fails on ethernet and wlan0 in android 4.0

You can do adb shell getprop | grep -i dhcp to see the dhcp related properties One of those should be dhcp..reason which indicates why things failed If that is not giving enough information - you have to go turn on manual logging in dhcp daemon to see what is going on. We do not have an easy way

Re: [android-porting] it is possible to connect group of devices using Wifi direct ?

Yes, a peer can discover an existing group and send a join request to the group owner. When the third device does a discoverPeers(), it can issue a connect() to the device with its group owner flag set (see isGroupOwner