My application need to create multi-group wifi-direct communication.But after testing I find that none of the following scenarios are feasible in Android:
1) a device plays the role of P2P client in one group and GO in another. 2) a device behaves as client in two or more groups.
I want to ask does the google have the plan to update the android Wifi-Direct API for suppporting one of above, so that we could implement multi-group communication easily?
Or are there some ways for two wifi-direct group communication with each other in android?
Thanks!!!!!!!!!!!!!!!!
Related
What Android parameter check for Device Not Supported on Google Voice & VoIP and other WiFi Android app.
We are Android 4.0 tablet device developer, Our current model is 7" WiFi only Android 4.0 using Action ATM 7013 CPU operating at 1.2GHz.
We develop and design our product for VoIP and SMS Android app, such as Google Voice, Talkatone, Pinger GrooVe IP, WhatsApp, etc.
But when we tried to install Google Voice, Google Play responsed with "Device Not Supported".
Can you please tell me what specific parameter these app check for in Android Compatibility Definition parameters?
Do you try to match any of these parameters for a table?
android.os.Build.MODEL
android.os.Build.BRAND
Or, do they check for any WiFi specific parameters?
thank you
Can't find any information online on this. I can't believe I am the only one with this issue.
Traveler on Android does not seem to support "conversations" view for emails (as Notes calls it). Otherwise known as "threaded email".
In terms of other mobile platforms, iOS supports this, clearly it's an irrelevance on Blackberry, not sure about Windows 8.
Having just moved from Blackberry to Android at work, my productivity is hugely hampered by this. I can obviously 'do' emailing, but I can't manage my email effectively.
Is this a known issue? Is there an upcoming update to add this for the Android platform that anyone knows about? Maybe it's a dependency on the OS API, as the iOS implementation looks like the native iOS email threading behaviour.
Any comments appreciated.
--
Using
Huawei u8860 JB
Galaxy i9300 JB
Bump
Nothing?
I'm guessing I'm not the only one who has some apps on the phone which could be used to dial phone numbers (between skype, google voice, different sip clients and some regional IP-based telephony apps).
So I'm wondering if an app exists or if there's an API provided by Google to build one which could be used as a standard dialer and then use some of these apps listed above to dial numbers based on dialplans?
Ideally it should be able to make calls thru the native SIP client (as configured in the phone), although I remember checking out if it was possible when the native SIP client was first introduced a while ago and there was no API to access the existing configuration from an app.
I have an issue which I can't even start to solve after hours of researching. I need to use GCM to facilitate peer to peer file transfer (JPEG image of circa 1.5 megabytes in file size to be specific).
Client A opens a socket and uses AirBOP to notify client B that it wants to send a picture and gives B relevant information (IP address + port to use, ephemeral I guess). B then connects to A and downloads the picture. All this behind NAT and via 3G/4G if at all possible. No server involved.
I looked into TTorrent, Snark, Cling, NAT hole punching, PWnat etc. but I still don't know how to achieve the above, and if it is possible at all..
This is a developer question but I'm restricted to General. I'm looking for a road map/guide lines/library/existing tutorials/projects on solving the above problem.
Thank you.
Lately I have been wondering why Android still does not have native support for CalDAV & CardDAV, when both have been the de-facto open standard for contacts and calendar sync for years. Is there no native support because Google wants it to make it more difficult to use alternatives to their services? (In my case: NextCloud/ownCloud, which I can add right away even to an old Iphone, but still do not work with android out of the box without something like DAVDroid) Or are there plans to integrate it into future versions?
What's the problem with installing an app? Android has a native API for contacts and calendars, so I guess they can't be accused of making it "difficult". They probably just don't want to make it "too easy".
One could also ask why 99,9% of app developers don't support APK distribution but require users to use GApps & Play Store …
xv22gk said:
What's the problem with installing an app? …
Click to expand...
Click to collapse
Which is not answering my question whether it is planned to have native support for CalDAV/CardDAV.
CardDAV / CalDAV are open standards for data exchange just like IMAP, NTP, SMTP and so on. It would be only natural for android to support them