You can now remotely install an app in a simple way. No need for Windows 10 SDK to get winappdeploycmd, You can use Device Manager in a browser locally or on the phone to do it. Here's how. The previous blog covered the basics about app packages, deployment and setting up for sideloading. This blog covers remote app installation and in phone app installation using Device Manager running in a browser.
You can now remotely install an app in a simple way. No need for Windows 10 SDK to get winappdeploycmd, You can use Device Manager in a browser locally or on the phone to do it. Here's how. This blog covers the basics about app packages, deployment and setting up for sideloading. The next blog covers remote app installation and in phone app installation using Device Manager running in a browser.
An issue has arisen with the last two Fast Track Windows 10 Mobile OS versions this week. You can’t deploy apps from Visual Studio to phones with those versions. Jump off Fast Track for now to Slow Track or “slower”. If you have one of these versions on your phone there isn’t a simple way to unwind. The problem as I see it is one of connectivity and sounds a bit like the issue we had last November with IoT-Core.
My next attempt is to get Blinky to work as part of an Android app. I found some relevant code but my device fell over so I can’t test it yet. Here is the code thus far.
This completes getting Blinky running as a shell script on a Dragonboard 410c
In this activity we will use the ADB command line and shell running on the development system, to directly manipulate the Dragonboard 410c GPIO pins. A version of "Blinky" will be implemented that periodically flashes a LED of the target. A second version will turn the LED on/off under control of a press button. The "app" will run as batch file of ADB commands on the dev machine remotely controlling Dragonboard. A Linux shell script running on the target will also be used that encapsulates the batched ADB commands..
In this exercise we will use Android Studio to create a single screen Android UI app that will access the sensor class to get the number of established sensors on a device. Don’t worry if you don’t have any sensors, It’s just that its more interesting than doing yet another “Hello World”. My system didn’t have any sensors enabled.
This blog will cover getting the development environment set up on a Windows 10 development machine. It also covers (an issue I wrestled with for some time) getting the target connected to the development machine. The second blog in this sequence will cover app development and deployment. Given my Windows background, it might have made sense to do the app development in Xamarin, the cross platform .NET app development environment for which you can simultaneously develop code for Windows, Android and Apple. You can also code in Visual Studio and deploy to an Android device. That will be the topic of a subsequent blog as I wish in this first instance to use the generic Android develop environment (Android Studio). I will then cover Android specific development in Visual Studio (2013) using a plugin. The hard part of the installation is getting ADB set up.
The Dragonboard 410C from Arrow has been certified for Windows 10 IoT-Core. It comes though with the Android OS installed. Whilst a subsequent blog will cover the Windows 10 installation to it, this blog focuses upon getting a feel for the board’s capabilities and how to use it in the Android context. This will then will lead to expectations of the board’s functional capabilities in the IoT-Core context for the next blog. The previous blog covered the board’s features.
The Dragonboard 410C from Arrow has been certified for Windows 10 IoT-Core and comes with Android installed. This blog takes a close look at the board’s features. Subsequent blogs will look at using the board in Android and IoT-Core modes.