I wrote SIP client to register my phone, and make and receive SIP calls. I am able to successfully implement it in Android phones. But the ultimate aim is, I need to implement this for Android watches using Android wear 2.0. Before flashing the watch with Android wear 2.0 image, I tested with Android wear 1.x and found that SIP Api support is not there for 1.x. As the preview image will void the watch warranty, I wanted to make sure what features can work on Android wear 2.0 before starting the implementation. When I searched for, I don't see anywhere that SIP API support is in Android Wear 2.0. Can someone confirm whether Android wear 2.0 has support for SIP or not? Thanks.
It seems that SIP API is not supported (or maybe not yet?) in Android Wear. From this documentation:
Note: Not all Android-powered devices support VOIP calls using SIP. You should always call isVoipSupported() to verify that the device supports VOIP calling and isApiSupported() to verify that the device supports the SIP APIs. Your application must also request the INTERNET and USE_SIP permissions.
I'm not sure with this since I don't try yet, but according to this SO answer, you can use 3rd party SIPStack implementation to make SIP supported.
You can find in this link the only features that Android Wear 2.0 supports.
Related
I am wondering if anyone knows if it is possible to use the ML Kit SDK on Wear OS devices? I know Wear OS is based on Android, and I've seen references online to Firebase notifications working on Wear OS.
I have googled combinations of the terms "ML Kit", "Firebase ML Kit" and "Wear OS" but not found any definitive answers.
I don't have code on hand, but I am wondering would it even be possible to import/use the SDK on Wear OS apps in the first place.
Expected results would be being able to instantiate and use some of the machine learning models from the ML Kit API on a Wear OS watch.
Battery usage and efficiency are secondary at the moment, I'm just wondering if it is possible at all.
I have never tied it but I think it is possible. In the end, the Andorid Wear 2.0 (WearOS) is just another regular Android and it supplies direct internet access from the device.
I was able to succesfully use RenderScript on Wear devices but on the other hand I've faced an issue that Google Awareness API was not available on Wear. THis seem not to be the expected state.
Probably in the end you will need to do feasibility study on your own.
You can try to use some android MLKit sample and simply run it on Wear device.
I would like to use Xamarin software as developing "Smart eye glass" which is Sony products.
I am wonderring that "sony_smarteyeglass_sdk_v1.5" is allowed to use in "Xamarin"?
I know that "AndroidStudio" is compatible with Sony products(Smartglass).
The SmartEyeglass SDK is really just a set of java libraries for Android that give you the correct interface to the SmartEyeglass device. All of the code runs on the Android device and therefore you have access to any functionality that any other Android app has.
I'm making app with bluetooth device with using Xamarin.forms. (PCL Project)
It's great platform and many great developers participate it.
I love it.
I have a question, let's say, I have to do porting third party library(SDK) from each native SDK for Xamarin. (ex-facebook / Of course I know there is facebook SDK for Xamarin already. It's just for example.)
What documents should I look?
In my actual case, I have to make app that uses DFU OTA to nordic bluetooth mcu. Nordic company gave to their developer native code(iOS and Android) for that.
Now I have to convert or use it on Xamarin.forms.
I learned dependency services and it works great.
Should I use dependency services?
I'm trying to learn something about iBeacon and I have a question:
As far as I understood Apple provides API in order to develop iBeacons app since IOS7, but for android how does it work? The only thing I found is that It works only from version 4.3 (Is it correct?) But are there any sdk or library to use?
Yes, you can use the open source Android Beacon Library, which gives Android the same basic capabilities to detect and transmit as beacons as provided by CoreLocation on iOS devices. This library is designed to be vendor neutral, and works with a wide variety of beacons. There are also a number of proprietary Android SDKs offered by beacon manufacturers, some of which harness special features that only work with those beacons.
The main thing to understand on Android is that while 4.3+ devices can all detect Bluetooth LE transmissions, there is no native beacon framework, and working with beacons typically requires quite a bit of logic beyond reading the Bluetooth LE packets they send out. As a result, Android beacon apps typically bundle a small library like mentioned above with the app to provide beacon detection and/or transmission capability.
Full disclosure: I am the lead developer for the Android Beacon Library.
You can use as well kontakt.io Android SDK which handles Beacons with IBeacon profile. In the latest release some optimizations in terms of battery consumption were made. Additionally, it supports filtering and modes (Android Lollipop and upwards) according to which scan is performed (explanation in brief here).
To start, visit http://docs.kontakt.io/android-sdk/quickstart/ and follow the instructions.
There is a sample app demonstrating SDK functionalities here. I suggest observing the project as it is the first place where new changes are being introduced.
As #davidgyoung pointed, there is no native framework for IBeacons in Android at the moment.
I just come across about ibeacons technology which introduced by Apple but haven't got any API/framework from Microsoft.
Is there any API or framework available from Microsoft which gives support for Ibeacons implementation?
Thanks
Unfortunately, this is not possible with Windows Phone 8, because it only supports Bluetooth 3.1 iBeacons require Bluetooth 4.0, also known as BluetoothLE.
In October 2013, Nokia announced that upcoming phones would have Bluetooth LE support. Unfortunately, these only allow OS-level pairing with Bluetooth LE devices. There is no public api.
This makes it impossible to develop a third-party iBeacon Library for the Windows Phone similar to the Android iBeacon Library.
Unfortunately, Windows Phone users will have to wait for a later release with either native iBeacon support or a public BluetoothLE API that allows a third party to develop a Windows iBeacon Library.
Update: this appears to remain impossible with Windows Phone 8.1. See my comment on the answer from #keni
Update:
Windows 10 will support Bluetooth LE Advertisements. Current status as of today (4/23/2015) is that the preview build of Windows 10 still has an incomplete SDK implementation and a few bugs. However, next week a new build will be introduced and it can be safely assumed that we'll get a good glimpse on how this will actually work.
Sending and receiving pure Advertisements works already. Have a look at the Sample that you can download from github here:https://github.com/Microsoft/Windows-universal-samples/tree/master/bluetoothadvertisement
Update
a public BluetoothLE API will come in Window Phone 8.1
http://allaboutwindowsphone.com/flow/item/19234_Windows_Phone_81_receives_Blue.php
Please read the following blog post for BLE for developers in Windows 8.1
http://sviluppomobile.blogspot.com/2014/02/ble-for-windows-81-part-i.html