DJI Windows SDK Sample - cannot view FPV mode - dji-sdk

I've cloned Windows SDK repo, open the sample solution with latest visual studio, fixed the dll ref for Windows SDK x86,
build the solution on x86 and activated the sample app with my key.
I've turned on WiFi mode on my DJI Mavic Air and connected my laptop to its WiFi, but nothing get displayed on the FPV screen:

Looks weird, Could you help to check the following steps?
Make sure your DJI Windows SDK Sample is updated to the latest version.
Make sure your Mavic Air is updated to the newest firmware version.
Try restarting the Mavic Air after switching it to Wi-Fi mode.
You could select the 'Component Handle' page of the sample app and try to get the name of the aircraft by which you could know if the SDK could get data from the aircraft successfully.
Also, you can check this documentation of running the sample code: https://developer.dji.com/windows-sdk/documentation/quick-start/index.html
If you still cannot see the FPV live video feed using the sample, please contact dev#dji.com for help.

Related

Why am I having trouble with the Android Emulator in VS Comm 2017?

I was having trouble using the Android emulator in Visual Studio Community 2017 and I decided to create a blank project to see if it will run. I get this error message when attempting to run it in the Live Xamarin Player:
Starting Android Emulator Android_Accelerated_x86_Nougat...
Failed to boot Android device emulator-5554...
Unable to deploy to Android_Accelerated_x86_Nougat, please ensure the Xamarin
Live Player app is open and the device is on the same network as Visual Studio.
Why would I have trouble running the emulator in a fresh blank project when I didn't even write a single line of code? Thanks for your help.
UPDATE: So I installed the latest Android SDK 8.0 along with they system image and tried to create a virtual device that uses it. But the Android Virtual Device Manager shows a, 'No system images installed' message when I selected the 8.0 framework. So I installed an earlier version of the SDK along with a system image (5) and was able to create a virtual device with it. So another question is why wouldn't the system images show up for the 8.0 framework?
The $(TargetFrameworkVersion) for Xamarin.Forms.Platform.Android.dll
(vv8.0) is greater than the $(TargetFrameworkVersion) for your project
(v7.1). You need to increase the $(TargetFrameworkVersion) for your
project
This means the Xamarin.Forms library is targeting Android 8.0 (API level 26) but your project is setup for Android 7.1 (API level 25). You can't change the Xamarin.Forms target version without downgrading, but you can change your project target version easily. You can learn more about these concepts from Xamarin. Be aware some of the details of that Xamarin blog post are already out of date!
There is another nice blog post from Xamarin which can walk you through the process of setting your system up for Android 8.0 API level 26. It's normally not this complicated, but Google changed their SDK tools internally between 25 and 26 in very major ways. They changed from GUI tools to command line tools.
You'll probably also want to get the (in preview) Xamarin Android Device Manager if you don't have a physical device to test with. This Xamarin Android Device Manager tool is the only way to create and configure API 26 and higher emulators without using the Google command line tools.
It seems as though Google has gotten rid of the GUI apps that manage the SDK and Virtual Devices in the latest version, so when you try to create a new virtual device with 8.0 it's not compatible with the GUI tools. Until Xamarin releases a GUI tool to replace them we can use the command-line to manage the SDK and virtual devices.
https://learn.microsoft.com/en-us/xamarin/android/troubleshooting/sdk-cli-tooling-changes
https://developer.android.com/studio/command-line/avdmanager.html

Can't Deploy App to my Windows Phone

I'm developing an app using the Cordova tools for VS 2015 Enterprise. I would like to test my app on Windows Phone, but when I try to debug using the built in "device" option, I get these errors:
Does anyone know how to fix this? For reference, I'm using a Lumia 550, in developer mode, which is plugged in through USB to a computer running Windows 10 (with the latest version of VS and the Cordova tools). I looked in my services app, and IpOverUsbSvc is running already. I'm using the latest version of VS and my phone was updated to the latest version of WP10 today.
I have tried doing a hard reset on the phone, as well as using WPPT to deploy the app, both of which did not work.
This is a known issue for Insider Builds. Please see similar case here.
Please try rolling back to stable version (e.g. 10586).
You can use Windows Device Recovery Tools to roll back.
Will this tool work on phones running Insider Preview builds?
Yes. When you use this tool on a phone that's running a preview build, it will reinstall the latest version of Windows approved for your phone by its manufacturer.

Basic Android App not working on Xamarin Android Player via VS2015

I have been trying to run basic Android App provided by Visual Studio 2015 via XAMARIN Android Player. Program gets build and deployed successfully, yet, App or anything does not appear on screen. Xamarin Player takes more than 20 mins to start and then nothing happens. Find Screenshots as well.
WIthin the Android SDK Manager look under Extras there is an package called Intel x86 Emulator Accelerator (HAXM Installer). Installing HAXM will increase the speed of the emulator when you use the Intel Atom CPU/ABI
Also when creating the emulator device check Use Host GPU for increaded performance.
I ran into few issues with Xamarin Android Player as well. Currently I am using Genymotion Emulator and it is much faster.
Well, Well, Well, I got my thing up and running. Following are the steps I performed:
After installing Xamarin for VS2015, I checked for latest Android SDK via SDK Manager. Got all the necessary updates installed.
Installed Xamarin Android Player and used emulator Nexus 5 KitKat API level 19.
Earlier I was using Nexus 5 Lollipop, was the reason why, it was not working. May be its not fixed for buil yet.
As, described by Mr.Pilatus in above answer, the particular HAXM things surely does help in accelerating emulator.
Got my Android app running.
Thank you all for all the necessary suggestion and guiding my in my baby steps in XAMARIN development. Gracias. NAMASTE!

Fail to create Android virtual Device, "No system image installed for this Target"

Unable to create Android Virtual Device
i follwed this link.
I installed all ARM images for each Android more than 4.0.
I installed intel & MIPs as well.
But, still my AVD Manager is saying "NO System images installed for this target".
why, so?
In order to create an Android Wear emulator you need to follow the instructions below:
If your version of Android SDK Tools is lower than 22.6, you must update
Under Android 4.4.2, select Android Wear ARM EABI v7a System Image and install it.
Under Extras, ensure that you have the latest version of the Android Support Library. If an update is available, select Android Support Library. If you're using Android Studio, also select Android Support Repository.
Below is the snapshot of what it should look like:
Then you must check the following in order to create a Wearable AVD:
For the Device, select Android Wear Square or Android Wear Round.
For the Target, select Android 4.4.2 - API Level 19 (or higher, otherwise corresponding system image will not show up.).
For the CPU/ABI, select Android Wear ARM (armeabi-v7a).
For the Skin, select AndroidWearSquare or AndroidWearRound.
Leave all other options set to their defaults and click OK.
Then you are good to go. For more information you can always refer to the developer site.
As a workaround, go to sdk installation directory and perform the following steps:
Navigate to system-images/android-19/default
Move everything in there to system-images/android-19/
The directory structure should look like this:
And it should work!
If you use Android Studio .Open the SDK-Manager, checked "Show Package Details" you will find out "Android Wear ARM EABI v7a System Image" download it , success !
I had android sdk and android studio installed separately in my system. Android studio had installed its own sdk. After I deleted the stand-alone android sdk, the issue of "“No system image installed for this Target” was gone.

Strange windows phone app crashes only from the store

I am trying to update a 7.1 app from the store. For some reason it crashes only when installed from the store and only on 7.1 or 7.8 devices. My Lumia 920 with the latest updates works fine. The app runs fine if installed from VS 2010 or VS 2012. Of course all emulators worked fine. I put a Messagebox at Application_UnhandledException and it displayed this:
The type 'MyApp.MainPage', specified in the x:Class of
'/MainPage.xaml' could not be found in any loaded assembly.
Of course the MainPage class is there.
The app uses GPS and bing map and has capabilities:
ID_CAP_LOCATION
ID_CAP_NETWORKING
Can anyone shed some light on this?
I have just solved a similar problem where I had this error message when running from Visual Studio on my phone but not in an emulator. My problem was that I had different versions of the Microsoft.Live Assemblies in my 'main' app and the Assembly which contained the 'MainPage.xaml'.
I had a weird issue where my app worked differently from the store than on my device and the emulator. In my case it was because of trial mode. Apps run as though they are purchased when deployed to the emulator or device. It worked on my device from the store too, but that's because I bought it. Any other device which had not bought it ran in trial mode, and that's why it worked differently. I am betting that is why you are experiencing this crash. If it is not then we'll need more information.

Resources