I have noticed on the official Android blog that WiFi Direct APIs are supported on google phone which are having versions 4.0 or later. Also I have seen the code to access WiFi Direct API.
But I have doubt that on some blogs people have written that some 2.3 version android devices also support WiFi Direct. So same code we are writing for 4.0 or later , will work on the 2.3 version android devices which support WiFi Direct?. I have failed to find the code which is compatible to android version 2.3
Again I have noticed ,Alternate solution for this is "AllJoyn" (https://www.alljoyn.org/) , but don't know that is it the right way to use WiFi Direct ?
Can anybody please help me ?
The fact that a device supports WiFi Direct (eg: version 2.3) doesn't necessarily mean that you have access to the WiFi Direct API (available from 4.0)
On the version 2.3 examples, consider that the feature is there but the app developer can't
directly interact with it.
I think that on the blogs you are talking about, the guys have just enabled the WiFi Direct on 2.3 but don't do anything by code.
If you want to do something by code with WiFi Direct, you need a device WD enabled and which runs on 4.0 at least so you have access to the API.
AllJoyn won't solve your problem. AllJoyn provides a layer on top of the transport APIs so the developer doesn't have to care if the data will be transferred via Bluetooth, WIFi legacy or WiFi Direct.
Related
I want to understand how xender app works programmatically ?
I want to implement same feature in my app to transfer files and messages without internet connection.
Is their any library which can help me ?
Android 2.3 must be supported to my app.
I research many stack Overflow questions but not helpful.
WiFi p2p, WiFi direct and NsdManager all having limitations to support lower android versions, it not give support to below android 4.0 version.
wifi p2p is what xender uses. But that feature sadly needs android api level 14 or greater. If you want to share files offline anyway on lower api, the only way is to connect the 2 devices on the same local n/w using wifi hotspot or something, once connected you can start the apps and everything should work just like xender.
I need to develop an app for windows for data transfers to android devices via mtp. That is when android is connected to windows via USB cable and android offers mtp menu as protocol for USB.
Can someone tell from which android version onwards can I assume that the device definitely has mtp support. Can this assumption be even made ?
Secondly is it android feature or does the mtp support depends on manufacturer regardless of android version ?
If you check the Android Compatibility Definition Document for Lollipop/Android 5.0 section 7.6.2 states that:
Device implementations MAY use USB mass storage, but SHOULD use Media Transfer Protocol
As it doesn't read 'MUST', I'm afraid there are no guarantees that devices which would have Google Play would have MTP, but I would be surprised if the major manufacturers didn't follow it and have an MTP implementation.
You can check the documents for older version of Android here:
http://source.android.com/compatibility/downloads.html
The [MTP] was added since Android API 12,
which Platform Version is [Android 3.1.x].
so, the [above a certain api] may be android 3.1
and ,this is the android feature,and I think the manufactur has no reason to unenable it.
Android API : developer.android.com
I am wanting to use Wi-Fi Direct in a solution but am unsure which platforms will support it.
Is Wi-Fi Direct dependent on phone type or Android version?
I need to know if I can develop an App with Wi-Fi direct features on a Xiaomi running MIUI version of Android 4.2.2
Android Developer site Wifi-Direct tutorial
Wifi Direct support was added in API level 14, i.e. ICS, so the phone you specify is likely supporting the feature.
I want to connect my Xbee module to my android phone and communicate with it by sending AT commands.
I do know of the USB host facility provided by Android phones, but I do not know how to send data to it.
I have the java-Xbee API and I am able to talk to the Xbee using my computer but since my project involves using the Android OS, any help on this topic will be appreciated.
According to this Google Code Page, the java-Xbee API requires Java >= 5 and RXTX. Considering those two requirements:-
RXTX on android is not an out of the box lib and may require some hacking which may or may not work.
I'm not a Java VM expert, but i know desktop OS JVMs work differently from Dalvik.How well would Dalvik run code developed for JVM? Here is a nice StackOverflow topic discussing the two.
Faced with the above challanges, are you brave enough to boldly go where no man has gone before?
Could you also consider the following well documented and supported approaches:-
Ytai Ben-Tsvi & Sparkfun's IOIO-OTG
Saves you the headache writing android 3.1+ USB host code and thus allows you to use cheaper phones that run droids 1.5 to 2.3 (without hacking the latter).
Digi's WiFi to Xbee
Allows you to link your android phone (or any other programmable wifi enabled computer) to your device over the internet.
I am involved in a Android Project that connects the sensor using Bluetooth 4.0. AFAIK android didn't support Bluetooth 4.0. I tried with my laptop bluetooth 4.0. I tried with Broadcom using this. Later i came to know my Laptop Bluetooth 4.0 is Atheros Bluetooth 4.0 and later i searched for Atheros Bluetooth 4.0 API using android mobiles and tablets. I saw Qualcomm having Bluetooth 4.0 tablet. I want to know, is Atheros giving API for Bluetooth 4.0 for Android SDK.
Finally, long way of search, i found that up to today(23/12/12), Atheros not giving Bluetooth API for developers. But they are providing other API's for Audio, Camera, Device Info and Sensor(mobile shake). So, can't try on laptop also. Dgel comment and link helped me a lot and made me, come to the conclusion.
Android Bluetooth (and other) API's are not specific to the hardware (or software stack).
They are generic and fairly high-level, and Yes they include Bluetooth 4.0.
The actually support for BT 4 depends on the device. Recent Nexus devices support BT4 (both in hardware and in software) as long as they have the Android 4.2 update.
If you root your device you can get to the 'raw' vendor API's, but I don't know what that looks like for BT4, or wheteher any of that is published. In most cases that is Broadcom based, not Atheros.
EDIT:
I just saw this:
http://code.google.com/p/broadcom-ble/
I'm not familiar with this, but I suspect that it was just a stop gap measure before BT4 was added to the official Android API in 4.1.