WiFi roaming and handoff

by BenYL » Fri, 26 Feb 2010 01:26:59 GMT

Sponsored Links
 We are setting up a WiFi VoIP network in the office, but are having
trouble getting smooth roaming with Android phones (dev 2). They seems
to wait until the signal is very weak before negotiating a hand-off.
The iPod Touch handles this process much more smoothly. Can we tweak
roaming performance with calls to the Android OS?



WiFi roaming and handoff

by a2ronus » Fri, 26 Feb 2010 05:22:09 GMT

 I assume your dev phones are running wpa_supplicant? If so, try the
website and mailinglist of wpa_supplicant as well.


Good luck,



Sponsored Links

Other Threads

1. Nexus can't install/update software anymore

Hi everyone,
today, when I debug my software on my nexus one, suddenly can't not
install correctly, then I check the logs as following:

06-22 22:50:33.341: DEBUG/VoldCmdListener(54): asec list
06-22 22:50:33.350: INFO/ActivityManager(85): Displayed activity
com.android.packageinstaller/.InstallAppProgress: 392 ms (total 392
06-22 22:50:33.470: INFO/PackageHelper(1673): Size of container 3 MB
1728967 bytes
06-22 22:50:33.480: ERROR/PackageHelper(1673): Failed to create secure
container smdl2tmp1
06-22 22:50:33.480: ERROR/DefContainer(1673): Failed to create
container smdl2tmp1
06-22 22:50:33.480: DEBUG/VoldCmdListener(54): asec create smdl2tmp1 3
fat {} 10073
06-22 22:50:33.480: ERROR/Vold(54): ASEC file '/mnt/secure/asec/
smdl2tmp1.asec' currently exists - destroy it first! (No such device
or address)
06-22 22:50:33.480: WARN/Vold(54): Returning OperationFailed - no
handler for errno 98
btw, my nexus has been updated to Froyo(2.2).

After that, I found that I can't install or update software anymore,
through the log, problem maybe on the '/mnt/secure/asec/
smdl2tmp1.asec' file, but I can't browse it because of permission.

Hope somebody can help me out, thank you.


2. Motorola Droid - QCIF Camera Preview and Capture


I am seeing a very annoying behavior on Motorola Droid when trying to
do a simple camera preview at QCIF resolution. And I was wondering if
someone experienced something similar. Is there a workaround? Am I
doing something wrong?

Let me explain the situation.

Firstly, right after boot-up, using native camera application there is
nothing out of ordinary, I see preview each time and it is all
perfectly well for as long as needed as many times as I want.

The "interesting" behavior starts when I use the slightly modified API
Demos (full app available in Android SDK, modified file is attached).
My goal is to preview (and later capture) video at QCIF (176 x 144)

Using CameraPreview module in API Demos application I can start
preview and capture normally only the first time picture is clear,
focused, normal colors, etc. Preview and all is nice. The second time
I do preview I see a very over-exposed picture, I need to turn it away
from any light source to see anything, otherwise it is all white. And
even in the shadow, everything is grainy, as if picture is taken with
too sensitive settings (high ISO) with too long exposure. The third
time, it is the opposite the preview and capture is way too dark. I
need to point the camera directly into the light source to see even a
faintest picture. Pointing out of the window does not help, it has to
be straight into the lamp or sun. The effect is like taking pictures
with much too low ISO setting it is way too underexposed.

The overexposed and underexposed sessions interchange, but it is not
clear-cut which one appears first. So far the prevailing pattern is
that overexposed one starts first. Now surprise comes when I try using
native camera application. The pattern continues! It is as if hardware
or or software (camera process) got "tainted" with the QCIF. This
continues until I reboot the device.

Another interesting point is that if I allow device to "rest",
symptoms are much less pronounced after 10 minutes, then in 15 minutes
they become barely visible. However, it all comes back after the first
time I capture in QCIF. Nothing like this is visible when resolution
is higher, say, CIF, VGA or similar. The problem is that, for my
purposes I need it to be QCIF.

This does look like a problem in HW, drivers, or somewhere around OS.
Any ideas, workarounds, tricks?

If it is not too much to ask, can somebody try the code modifications
below to try on your device? I am curious which devices are working
properly and which are not. Shall we have a vote?

=== Device Information ===
Firmware version: 2.1-update-1
Baseband version: C_01.3E.03P
Kernel version: 2.6.29-omap1-g7fa8788 android-bu...@apa26 #1
Build number: ESE81

=== To reproduce ===
Open CameraPreview.java from <SDK root>/samples/android-7/ApiDemos/src/
com/example/android/apis/graphics, and add the following method:
    protected void onMeasure(int w, int h) {
        super.onMeasure(w, h);
        setMeasuredDimension(176, 144);

Also in the surfaceChanged method, add the following line:


3. how to bring up text to speech settings in my app?

4. Personalized Screen lock

5. BroadcastReceiver and abortBroadcast()

6. Are developers now tech support for the Market?

7. Android build error for superh arch