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.
Related
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
I am working on an iOS app which need to get push notifications(using GCM) from web service(Made of Python).
Currently the web service works fine with Android devices, but it reports Error=MismatchSenderId, when I check this error in the online doc, it suggests the sender_id and API_key are not matched. The thing is, as I understand it(could be wrong), for iOS SDK, unlike the Android's, it doesn't need sender_id.
The tricky part is I have no access to the web service yet(which the collaboration party claim the Android app works fine with it). Could anyone shred a light on what steps should I take to fix this issue?
THanks in advance.
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.
I was asked to see whether apple pay will work with mobile safari and if possible to integrate into our current mobile website/website. When i did my research I found that it only works with a native app. Is that true and if so why it does not work with mobile safari? Mobile safari or any other browsers in this case is also an native app and why cant apple expose the apple pay for browsers that websites can use using a javascript API?What are the risks?
As of now Apple pay APIs are only available for native iOS apps. Javascript API though is obvious future of Apple pay, is sadly not available with iOS 8-9.
Javascript API and browser (safari) is considered not secured enough (hackable) to be pass EPOS information from browser to website.
Chrome is integrating Wallet with browser as first step and hopefully in future we will have payment API to websites as well as for native apps.
Apple Pay uses NFC to get connected to EPOS for contactless payment and hence it follows device perspectives.
Apple Pay allows to interact with EPOS like PayPass,PayWave or online payments using the encrypted cards which we stored in the PassBook App(accessed with Your Touch id) but it does not doing any payment procedures Thats why third party payment processors are listed on the official website.
http://techcrunch.com/2014/11/27/identity-wars-why-apple-pay-is-about-more-than-payments/
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.