google tv used anymote protocol for remote control but the case with android tv does not looks the same. No official docs clearify if they still use the same.
I want to develop an app just like the app by google but with some changes and additions mostly on gamepad part. Additionally if anyone knew how apps like cetus play and droid mote for android tv work?
almost similar questions have been asked before as well but never properly answered. Any information and suggestions will be helpul
Related
I'm looking for a way to have an application just process voice commands every time I say a specific phrase. The behavior should be similar to Cortana, Alexa or others. The application will be deployed on a hands-free device, but the Speech device SDK cannot be used, because it runs solely on a PC.
Is there an addition to the Speech SDK with a custom wake word yet?
MS speech recognition uses RESTful APIs to cloud services. You can use them from any device.
You can use speech-to-text and voice command services on Android or iOS. https://azure.microsoft.com/en-us/services/cognitive-services/speech/?v=18.05: Examples exist for both Java and Objective-C.
I think you also want to check out the preview of speaker recognition.
https://learn.microsoft.com/en-us/azure/cognitive-services/speaker-recognition/home
Does this help?
Looks like you would need to go to a specific site to set a wake work as it's still in preview mode. That will generate some files that you'd download for the SDK.
There's more in this documentation page.
Android Management APIs are supposed to be "compatible with any device running Android 5.1 or above that has Google Play installed." I really want that to be true, but am having trouble with Android TVs. (Specifically, a NexBox A95x and a TX3mini I'm testing with.)
My stumbling point is how to enter the enrollment token into the device when provisioning it? I had no problem with a Samsung tablet. But, the Android TVs don't use the same startup wizard after hardware reset, so there doesn't seem to be an opportunity to trigger a QR reader, or manually enter the token. I've tried entering the enrollment token into Google Play app (in lieu of the email or phone number to log in), but no luck.
Any ideas or insight how to make this work? If anyone knows a definitive reason why this can't be made to work (e.g. Management APIs don't work on AOSP) that'd be helpful information too.
Clarification (Updated 26 Dec 2017)
Here's a minimal, complete, and verifiable example of the Google Management APIs. The Quickstart exercise from Google, themselves.
Problem: The Quickstart exercise doesn't seem to work with Android TV (tested on a NexBox A95x and a TX3mini). The blocker appears on this step: (Provision A Device). The Android TVs have their own setup wizards that do not accept an Android For Work enrollment token. (I have completed the Quickstart on a Samsung tablet without problem.)
Google's documentation says the Management APIs are "compatible with any device running Android 5.1 or above that has Google Play installed" so it seems these Android TVs should qualify.
Has anyone found a workaround to do complete the Management API Quickstart on an Android TV?
As far as I know the Android Management API doesn't supports Android-based OS's like Android TV, Android Wear, Android Auto or Android Things. It just supports standard Android for phones and tablets.
since I am new in the world of developing apps for watches, and the fact that it exists for smartphones the following frameworks:
Xamarin
PhoneGap
appcelerator
kony
Cordova
...
I wonder if there exists for watches apps similar frameworks? So that you code once but run overall.
Thanks
Edit 1:
At this day (12.05.2015) regarding to the answer of a nativescript maintainer here. I will go with nativescript to start writing app for wearables.
Cordova/PhoneGap apps don't work directly on the wearable devices/watches. Cordova/PhoneGap is basically a javascript API which can run on WebKit/WebView on all the mobile OS's. But the Android Watch and Apple Watch doesn't support WebKit and so the apps developed with Cordova don't work directly on Watch devices. But if want to extend some of the features from the existing Cordova app to the wearable app, you need to create the extension app in native language and the extension should be able to communicate with the paired app on the mobile device. The extension on the Watch will have only UI and the bussiness logic etc runs on the Cordova app on the mobile. It is possible to establish communication between these apps which will drive the display on the watch devices.
I am not sure about the other frameworks you listed above on how much they support wearable devices.
As #kiran and #NRimer have mentioned, these cross platform frameworks are relying on the WebKit/WebView which is the almost universal layer supported on every mobile device. They dont run directly on the device, but device runs WebKit platform that runs these cross platform apps. So comparing the capabilities of the native app with cross platform app, native app is bigger, because it can have a hands on device hardware related features. The thing particular to the smart watches is that they mostly rely on other smart phone device, and it uses it's communication protocols, that are hardware specific, and WebKit doesnt have its hands on it.
It depends on what you're looking to do with the framework. Watch apps build off data provided by their containing app. For example if you want to provide custom notifications on the watch, the app (or server for remote notifications) constructs them. When your watch app needs information, it makes a request to the containing app. Lets say you have a group of apps that you want to provide the same notifications or functions on each of their watch apps, you could make a framework that handles these functions for the containing app. As for the watch portion, think of it as more of a display of information provided. Unfortunately i dont think there's a way to generate frameworks for watch apps yet. If you're looking to have a lot of code within the watch app this might be more difficult but for simple display of information you should be alright.
I had my first Android TV app go live last night, but it has to be searched for in Google Play. How do you get your app listed in the Entertainment Apps section of the Home screen (and in the Google Play Store on Android TV) so people can actually find it?
It turns out that the Entertainment Apps section does not include all Android TV apps like I had thought. It is a curated list. So unfortunately that means Android TV apps have the same likelihood to be discovered as regular Android apps, and it makes the Andoid TV ecosystem look much smaller to the user than it (presumably) is. I guess I was expecting something more like Roku's channel store.
When you access PlayN's site you see that PlayN's logo uses Google colors: http://code.google.com/p/playn/
Also, Lilli Thompson talked about PlayN at New Game Conference in 2011 as a Google game developer advocate. http://www.youtube.com/watch?feature=player_detailpage&v=iK9Xl58IxKw&t=4 (I haven't watched the video.)
But she's not at Google anymore (http://plus.google.com/111647958621817995641/posts/EVptyYGHSfd and http://twitter.com/lillithompson/status/183299616647811072)
However, When you visit https://developers.google.com/games > Web games or > Mobile Games, there's no reference to PlayN. You find Android development, which links to http://developer.android.com/sdk/index.html. There's a Google Play Game Services (GPGS) too, that offers social features (achievements, multiplayer, leaderboard) for game development for Android, iOS and Web (http://developers.google.com/games/services). There are "Getting started" tutorials for GPGS for each platform (Android, iOS, Web). No PlayN, which compiles to these three platforms plus Java desktop.
So, is PlayN really supported by Google? Or was it once, and now the community is by itself?
Playn is a community supported project, and i suspect always will remain such. Google had a hand in making it, but their contribution recently has been waning. But it doesn't mean the project is dying or anything.