Google Vision FaceTracker shows a black screen - android

Can someone try Google VisionAPI FaceTracker and see if it works?
Here's the official page.
All I get when I try running it is a black screen (after fixing one error). I don't get any errors in the logs either.

The sample works for me. Of particular note: you should not need to modify the samples to make them work, they should just work.
As such, I also just ran the Face tracking sample as follows:
git clone https://github.com/googlesamples/android-vision
(Install Android Studio)
Import android-vision/visionSamples/FaceTracker into Android Studio
Click the Android Studio things that install SDK 24 / build tools 24
From the android-vision/visionSamples/FaceTracker folder ./gradlew assemble
Create a Google API virtual android device with Nexus 5X, setting advanced to a camera when you create the device
Start your device
adb install -r ./app/build/outputs/apk/app-debug.apk
Open up app, accept permission, turn your camera sideways
App looks like this:
The following could be helpful in diagnosing your issue:
Can you share the output from adb logcat?
What Android version is the device you're testing the sample on?
How are you resolving when encountering the "check permission" error?
What SDK / build tools are you building with (the sample is 0.24)?
Googley Eyes was a little trickier from the emulator because it uses the front camera.

Related

when i use "tns preview" to start an android emulator i get an error code

i want to preview my nativescript code on an android emulator which as i use the command line which is, i navigated to my app folder which which was successfully but when i type "tns preview" to run an android emulator to see my code in action i get
Found peer TypeScript 3.1.6
#
# Fatal
process OOM in insufficient memory to create an Isolate
#
TypeScript compiler failed with exit code 3221225477
and an android emulator is connected successfully, even nativescript notice the emulator, please what do i do
i have tried the Nativescript sidekick to start the emulator but the nativescript sees the android emulator and it did not report an error indication but when i select the android emulator and click "Run on Device" i get
Build failed. TypeScript compiler failed with exit code 3221225477
even i have tried using my android device for previewing it which i install the nativescript playground & nativescript preview but if i scan the QR Code it is not previewing, please help out
please i need a solution
Preview is to be used with real device for quick testing. The basic idea is to avoid setting up whole iOS / Android SDKs on your local machine.
Produces a QR code which can be used to preview the app on a device without the need to install various SDKs and tools or configure your environment for local iOS or Android development.
To scan the QR code and deploy your app on a device, you need to have
the NativeScript Playground app:
App Store (iOS):
https://itunes.apple.com/us/app/nativescript-playground/id1263543946?mt=8&ls=1
Google Play (Android):
https://play.google.com/store/apps/details?id=org.nativescript.play
If you want to view your app on your android emulator, run the command
'tns run android --emulator'
This is assuming you already have an emulator set up on your machine.
To see a list of your available devices run the command
'tns device'
If you have not set up an emulator follow setup here: https://docs.nativescript.org/tooling/android-virtual-devices

Problems running app on actual device

OK, please take it easy on me, I am new to the whole Xamarin community. I have built a simple calculator app using MVVMCross. When I run the app in an emulator everything works great. It still needs some UI attention, but functionally it all works. When I go to archive it and make an install on my phone, it installs just fine. The issue is when I go to run it. As soon as it opens I get an error message. "Calculator.UI.Droid has stopped" Open app again. I have gone through everything I can find online to do this and nothing is working.
Here is my setup:
Visual Studio 2017 Community with latest updates
Windows 10 with latest updates
Latest Java SDK
Project Properties:
Compile using Android Version 7.1 (Nougat)
Minimum Android Version 5.0
Target Android Version 7.1
Use Fast Deployment - false
Generate one package (.apk) per selected ABI - unchecked
Enable ProGuard - checked
Linking - SDK and User Assemblies
Android Phone:
Google Pixel 2 with latest updates.
Any help would be appreciative. Just let me know if you need more information. Thanks in advance
I myself are also using Xamarin, and quite often I get this problem, most times it is related to the code, so please make sure that's the case.
comment out your calculator stuff, and try running the basic app on your physical device. if that works try to find the problem, idk if you can use breakpoints because your problems happens on boot.

how to debug a javafx application for android in eclipse

I create a big JavaFX application that works fine in desktop.
In Android, its size is about 20 Mbytes.
Now, for deploying it for Android, I have installed Gluon (JavaFxPorts).
With a small program (using the JavaFX transitions notions, timeline, ...), I have generated an .apk by calling the androidInstall gradle task. That works fine, except I cannot automatically install the .apk file in my phone. I do copy/paste from my desktop to my phone.
BUT, when I want to do the same process with my big application, at the end, my phone screen is already black.
Therefeore, even if this big application works fine on my desktop, it is necessary to debug it for Android on my desktop, too. But, I don't know how to?
What to do with apkDebug gradle task, ..?
gluon+gradle does not provide a kind of Android emulator that allows to finalize the debug on desktop for a smartphone with its specific features (size of screen, landscape orientation). Do you agree?
What is the additional tool that allows to do that?
Moreover,when the application is deployed in the smartphone, does it exist a tool that allows to finalize the debug on smartphone?
Thant you for your response
Note: I have installed Android SDK manager and its AVDM in Eclipse, but with the JavaFX use, it is impossible to use it, isn't it?
Debugging JavaFX projects on Android so far doesn't work on Android emulators.
Command Line
The usual approach is just log messages to the console (i.e. System.out.println() or Log.v()...), and then using adb logcat.
On command line, go to your Android sdk folder, enter into the platform-tools folder and run adb logcat -v threadtime. That will give you all the log messages from your device, so you'll need to find your FXActivity pid there and filter through it.
Another possibility is using Android's monitor under the tools folder, a GUI tool that will allow filtering the console messages.
Eclipse
There is an ADT plugin for Eclipse, that can be installed following this question. This will allow you displaying logCat and device windows among others. Basically this will offer the same options as the monitor tool.
However, this doesn't seem to work with recent versions of logcat.
Android Studio
You can import your gradle project with Android Studio and enable the Android framework, so you can open the Android Monitor, and easily filter the logcat messages, or switch to the monitor tab with live charts of memory, cpu, ...
Black screen
Typically a black screen means you have some exception going on, so you need to use any of the above mentioned logging methods to track it down, solve it and try again.

Program successfully installed but not displayed on device

I have just started programming on nexus 5 phone and sony smartwatch. I tired to install a sample program (HelloLayouts) on the device and it shows the following msg:
[HelloLayouts] Uploading HelloLayouts.apk onto device '.......'
[HelloLayouts] Installing HelloLayouts.apk... [HelloLayouts] Success!
[HelloLayouts] \HelloLayouts\bin\HelloLayouts.apk installed on device
[HelloLayouts] Done!
I checked applications from Smart connect but it doesn't show any installed program name hellolayoputs. I also checked the smartwatch, but didn't see any installed application. Not sure if I am missing anything.
any suggestion to solve this problem would be highly appreciated.
Just a few questions:
Did you modify the HelloLayouts sample file at all or did you just run the sample right after installing it? If you did modify it try creating a new sample from scratch and running it again.
Are you running your samples with Eclipse, or Android Studio, etc...?
Are you using the latest Android SDK v 23.0.2?
Also you may want to try restarting your phone and watch to see if you can at least see the app showing up in the SmartWatch 2 app.
May be Launcher Activity is missing or corresponding 'category' tag is missing from 'intent-filter' of launcher activity your Android Manifest file. Check it or post your AndroidManifest.xml file.

Android SDK emulator doesn't run my programs?

I recently got introduced to Android via a school course. Did some very simple examples earlier, and decided to installed all the required peripherals at my home computer too. I was on my way to develope all kind of cool stuff, until i noticed that something is wrong with my Android SDK or the emulator itself - it won't run any of the programs i try to.
I've got Eclipse & All the required add-ons / plugins installed. I get no error messages at any stage ( in eclipse or in the emulator itself ). Whenever i press run at Eclipse, the emulator takes it's time and starts up, but doesn't start the program, and doesn't actually show even the slightest hint of it. Looks just like if i had tried to start only the emulator. I've tried to create several different AVD's, and tried to use different versions of Android on them. No luck.
Im using windows 7 x64, and after a couple of rounds with Google, i found a few other guys who are having the same problem with the same OS.
Any help is greatly appreciated, as im running out of options here.
You need 32 bit eclipse and 32 bit JVM. There should be an error in the "console" window in eclipse if you hit run.
Click on the Menu button of the emulator to unlock it. You may then need to rerun the app.

Categories

Resources