WiFi Direct on Android | IT IS TERRIBLE

Wifi Direct; a  wireless communication channel that runs in parallel with your Wifi connection, guaranteeing point-to-point communication at speeds much faster than BLE. It sounds perfect for a local multiplayer game, or a camera peer network. It works up to 20 meters in open space and penetrates a single wall given your antenna is strong.

Sounds perfect? I really wish it was. I spent over a month trying to ensure it works on as many devices as possible. In principle, it works exactly the same as BLE. You make your device visible for a wifi direct connection, and another device upon discovering it connects to the former.

If you're planning to use Wifi Direct, I'd suggest you don't and figure out another mechanism.

Here's a list of problems I faced:
The SDK:
  • The heart of the issue is each phone functions differently.
  • The Android Software Development Kit ensures all devices above API 19 provide the same set of APIs, but the lower layers manufacturer implementation is different for each device. All the Android SDK really does is provide an abstraction layer above individual driver implementations. This is true for most hardware specific APIs in the SDK, but I suppose the device CTS (a compatibility test suite to validate whether a device is fit to be sold as an Android compliant device) doesn't do a very good test at testing wifi direct.
  • A couple simple examples of this erratic behavior; LG Q6 changes its device name if there is a device failure,  Nexus stops connecting randomly post 2 unsuccessful connect() attempts
  • Unlike other APIs in Android, each of the Wifi Direct APIS responds through an onSuccess() or an onFailure() callbacks.
  • If one command is called but not yet processed, any other call will throw onFailure(). 
  • Broadcast receivers for wifi direct are messed up! They may return the same information anywhere between once, to thrice, hence messing up the listener's logic - for example, onConnect() may return twice.
Discovery:
  • Discovery time is dependent on who started discovery first. It can take anywhere between 2-10 seconds to discover. 
  • Discovery may even fail at times even if startDiscovery() returns true; the only way out here is to stopDiscovery() and start it again, but this is tricky because you can only call startDiscovery() once the call from stopDiscovery() returns.
Connection:
  • Some calls don't return; for example, there is no timeout for connect() call, and if the device you're connecting to doesn't accept, you can't fire any other command until this returns. Thus, you have to implement your own timeout for each call.
  • There is no way for a non-group owner to know the details of everyone in the group other than to query it from the group owner.
I ended up implementing boolean flags to ensure we don't trigger commands and get unnecessary onFailure() callbacks and have a message queue for retrying failing commands after 2 seconds. The alternative and better solution is to use a message queue only and no boolean flags; let the APIs fail with onFailure() and then add the same message back to the message queue. This makes sense because you can then consistently use the message queue throughout to implement timeouts, and retry on onFailure() calls.

The library works about 95% of the times on all devices I've tested, and I'm content with this. The only problem is discovery times are fairly high; up to 10 seconds, and I can't pass any metadata apart from the information in the name of the device being broadcasted.

So, what next? Android provides another set of APIs for Network Service Discovery (NSD) over Wifi Direct. My hunch was it only performs a service discovery after the initial wifi direct discovery; but a colleague was certain it'd work faster as we'd been using NSD over Wifi for quite some time.
It turns out, it performs worse than the simple wifi direct discovery.

 Specific problems with Wifi Direct NSD:
  • The only advantage is that you can send metadata bundled with the service info (port, IP, name, etc.) without pairing up with the connection. 
  • You do not get a service lost callback, so you will still have to rely on the former discovery lost mechanism for invalidating old/lost connections
  • It fails half of the time to discover when the normal P2P discovery works, and we're clueless as to why.

Comments

Post a Comment

Popular posts from this blog

Finding My Parter

Finding my partner feels more like finding  my kind . I’m this mix of an Indian boy with Indian familial ties, but European hobbies and a European way of leading life. I've lived in both worlds for 15 years each. There aren't many that have seen and lived in both worlds, and experienced completely different ways of life. Maybe I am asking for too much, but I don’t understand why one wouldn’t. If I have high standards for most things that I do in life, why wouldn’t I hope or want my partner to think from the same lens? Here's my value system. Be generally optimistic. A positive, happy person whose baseline state is to lean towards an optimistic outlook towards everything in life. Be fit. If one is not physically fit, there's low chance they're mentally fit. Plus, being fit shows discipline and consistency. Be hard working. Everything in life is a project. From raising children, to picking up groceries weekly, to building a home. And no one wants to work with a lazy ...
Continue reading »

Two Worlds, Two Lives

I’ve been in India for the past two months now, and for the first time in my life, I can imagine myself live here again. Nothing drastic has changed in my day to day life, nor in either of the nations per se, but maybe I’ve had enough time to experience the flip-side to know what India’s strengths are. I’ve always acknowledged how I get the chance to live in two different worlds. But this is the very first time I’ve realized I also lead two different lives each time I switch countries. For me, Germany is a nation where you put the self first - you learn about yourself as an individual. It’s also a country where you learn to live life in the way they show us in movies - walks in parks, play sports any time of the day, vacations in every season the climate has to offer, meetups at little cafes with chairs out on the street. Work is secondary, rarely one’s primary driver in life. Therefore, it is also rarely one’s identity. The country and the mindset is averse to change. The philosophy h...
Continue reading »

Keeping Fit in India

I have a bold claim to make: As compared to Europe, it's much easier to get and keep fit in India. But it's far less likely. Easier because: Relatability In India, you can relate to the others' bodies. Everyone around you has the same body style, our carb heavy diet that causes so many of us to be skinny fat. And so when you go to a calisthenics gym, it really helps to be able to look around and see that a person who looks like you is fit . That shines hope, telling you that it is possible in the first place. In Europe, the same is counterproductive. Looking at the European's low body fat, tall yet muscular physique makes me think they're just born with it. (Which is not true. I suppose they really do have great genes, but their meat heavy diet and walkable/cycleable cities help with keeping fit). Food is easier in India. You know your food here. You know the spices we use and how it tastes. It's that familiar feeling of eating something you know, as opposed to...
Continue reading »