My sample app using GoogleFit API of GooglePlayServices runs on Android mobile (using Android-M) but the same sample app gives error as API_UNAVAILABLE on Android TV (using Android-M) even though PlayServices version is latest version on TV.
My intention is to only to READ the Google-fit data.
Is it so that device like TV might not have health/fitness sensors and hence GooglePlayServices does not enable Google-Fit API (even though an application might be only interested in reading data)?
Any pointers available on this on how to enable GoogleFit APIs on Android TV?
EDIT1
Tried with 365 Body Workout apk https://play.google.com/store/apps/details?id=com.peirr.workout.play&hl=en on AndroidTV having latest GooglePlayServices [11.5.09 (836-164803921)] and found that it does not work as indicated in the below picture
Related
I am trying to implement Proximity Beacon Api for Android.
I downloaded the project from
https://github.com/google/beacon-platform/tree/master/samples/android
I can successfully run the project and after clicking on SCAN button in app nothing gets displayed.
I converted one of my Android device into EDDYSTONE beacon by installing app from
https://github.com/google/eddystone/tree/master/eddystone-uid.
But still did not find any luck in scanning beacons.
I also had a doubt that, where should I use clientID generated in google developer console.
Please help.
Did you try Nearby Messages API?
https://developers.google.com/nearby/messages/android/get-beacon-messages
I wrote react native application. The application is simple, more informational, it is used by Redux, Saga, several linked npm packages. The app runs in normal mode, not full-screen. The structure of the application was built on the basis of Ignite.
The problem is that on the phone (Samsung Note8) the application is recognized as a game. E.g. while app is running there is a message "The game is running" on the lock screen. Also there are additional buttons for the gamepad or something like that. In additional, app has a paddings on the top and on the bottom when it's working on real device (Samsung Note8). This effect real exists when some games running. When app is running on another device (e.g. ZTE Blade 610) it's running as usual and without any side effects.
The main version is the cause of all is Game Tools that's existed on Samsung Note8 but others apps have no similar effects and running as expected.
Is there a possibility to make a react native app as a real app but not a game? Why Game Tools recognizes my app as a game? Or what is the reason and how can it be affected?
Thanks.
I think there are few possibilities.
you (or one of your dependencies) have included the google play service API which inside of play service API has a module named games that samsung will automatically treat it as game.
You could find which of your dependency is loading google play service API and create a exclude like:
compile (project ('your.dependency')){
exclude group: 'com.google.android.gms', module:'play-services-game'
}
Your application id (can see on build.gradle) is registered on samsung game database. You could check by going into playstore and search for your application id
this is something that can happen on samsung phones due to the package name of your app.
we cant change this after the initial release, you must contact samsung developer support and they can fix it on the fly.
i wrote a gist on github about it:
https://gist.github.com/Adnan-Bacic/718eb3b4e70380696c91dc21c4804112
I'm trying to run an android app on Android Things OS.
The app uses facial detection as a first step filter for reaching facial recognition.
The recognition process is made by a third party (remote) API, so there is nothing to worry about it, but the detection is being carried out by the Google Mobile Vision API for Android. The problem I'm facing is that the app crashes every time a camera preview is about to start.
The code of the app is derived from this example: https://github.com/googlesamples/android-vision (Face tracking). So if this code runs, my app runs.
I also know that there is a known issue with the raspberry pi and the camera trying to create more than one output surface.
My questions are:
(1) Is there a way to successfully run the code in the example https://github.com/googlesamples/android-vision (Face tracking)?
(2) When is going to resolved that known issue?
Thanks in advance.
Attentive,
Gersain Castañeda.
The latest version of Android Things(DP6) which is with API 27, supports the new camera API Camera2 as its explained here.
Camera2 API supports more than one output surface and its runnable on Android Things.
For getting more inspirations of how doing this check this tutorial(how to use camera2) and this very useful sample(how to use Google Vision).
We have developed an app using Xamarin Forms which targets iOS, Android and Windows Phone. We are using camera feature to take/select photos to be uploaded to the app and the feature works well on all three mentioned platforms.
We have some users facing issues on few windows devices. When a user tries to download the app from Windows App Store, they receive following error:
"This app is not available for your phone because it requires front facing camera”
I have attached screen shot showing the error for reference. The screen shot is taken from Nokia Lumia 635. Our finding that this device has only back camera, no front camera and we believe this might be the reason for above mentioned issue.
Ideally, users should not get this error as this device has back camera and they still can get the photos.
Is this a known issue in windows phone world?
Can this be fixed from code, device permissions?
Is this a device specific problem?
Any ideas?
I have created a APP using GCM which works correctly on Android platform 4.1 and 4.03 (I.e. Gets a RegId and register itself in my server and can even recieve a GCM), but when I start the emulator for android 2.3 (API 10) then the app gets installed but never registered I.E never gets RegId. When I start (install) the application for the first time then it receives a GCM message which I do not understand where it comes from but I can see that the device is not registered in my server. I also used a HTC phone with 2.3.3 android software and stil same result. Can any one see what the problem might be?
On the emulator it should normally not work, because it will not have a google account tied to the device. It is requiered for a device to have a google account and Google Play installed to register for an id.
The phone on the other hand should work.
GCM will Work from Android 2.2.
Refer this tutorial it may help you,
http://androidv5.wordpress.com/2012/08/15/how-to-implement-google-cloud-messaging/
it works fine for me.