Friday, November 20, 2015

I wanted to get Hubot working in our slack channels at work and I thought I would share the process I took to get it working and running on Azure Websites.

First, make sure you have nodejs installed

> choco install nodejs.install -y

Make sure npm is up to date

> npm install -g npm

At this point, I also installed coffee-script because the first time I tried running it, I got errors about coffee script

> npm install -g coffee-script

Install the azure-cli node modules to generate the deploy file that will be used

> npm install –g azure-cli

Next we install the yo hubot generator

> npm install –g yo generator-hubot

create a directory for your hubot. I have found that you should not initially name it “hubot”, as npm will fail with some of the package installs (specifically, the hubot package). Then lets start the hubot configuration

> mkdir myhubot

> cd myhubot

> yo hubot

Now you will answer the question it asks to configure hubot. Again, I wouldn’t name it “hubot” when it asks. I will show you where to change it later so it will respond to hubot.

Mine showed some error messages while running this, but still functioned correctly.

Now lets install the slack adapter

> npm install hubot-slack --save

next we need to create the azure deploy command.

> azure site deploymentscript –node

lets now make a couple tweaks to the hubot files:

first, open up external-scripts.json and remove

"hubot-heroku-keepalive",

"hubot-redis-brain"

if you want to use azure blob for the brain we can set that up now. while still in the external-scripts.json, add the line:

Login to your Azure portal and create a new Web App: (The name has to be unique)

If you are using Azure blob for the brain, create the storage account as well.

After the storage is created, we will need the Storage Account Name, and Primary Access Key. Copy these for use a little later:

Go in to the settings for your newly created web app and click on “Continuous Deployment”. We are going to configure Azure Web Site to pull directly from the Github repo for the hubot configuration.

Choose Github as the provider and then authorize Azure to connect. Then choose your Hubot

Finally we have to set up the environment variables that Hubot needs to function:

You will create the following keys:

HUBOT_SLACK_TOKEN: Your Slack Token for Hubot when you enable the integration

HUBOT_SLACK_TEAM: myslack (from https://myslack.slack.com)

HUBOT_SLACK_BOTNAME: The name of your hubot

HUBOT_ADAPTER: slack

HUBOT_BRAIN_AZURE_STORAGE_ACCOUNT: The storage account name we saved from above

HUBOT_BRAIN_AZURE_STORAGE_ACCESS_KEY: The storage access token we saved from above

Go to your webapp to test that your hubot is working.

http://myhubot1.azurewebsites.net/hubot/help

Sometimes it doesn’t respond the first time, but if it continues to fail when requesting, there there may be an issue. Try running locally (you will have to remove the azure-blob when running local) and see if everything is working.

Friday, November 6, 2015

If you are familiar with .bash_history or just wish you had a history of your powershell commands persist between sessions here is a handy little script. It will persist command history when you exit a powershell session to a file in %USERPROFILE% called .ps_history.

Copy the code below and save to a file called “Microsoft.PowerShell_profile.ps1” and save it in “%USERPROFILE%\Documents\WindowsPowerShell”

Saturday, October 31, 2015

To add to the my list of hobby projects, I created a fork of an addon for Kodi that provides browsing of videos on Microsoft Channel9. This was my first attempt at a Kodi addon, and really my first time working with writing python. I started out by just reading over the original code and tweaking it a bit because some things were not working. Then I started following the pattern that existed and implementing new features, like being able to browse Channel9 authors, and Channel9 events.

Once I got these features in place, I started doing some real refactoring of the original code base. There was a ton of code that was duplicated in multiple places. I spent a few hours of the day really rewriting the entire addon. As the project stands right now, it is basically a complete rewrite of the original addon.

Sunday, October 4, 2015

Over the weekend I was bored and decided to start a project to automate the process of standing up an IE VM with powershell. I would like to introduce PSIEVM. A powershell module that allows you to stand up an IE VM in VirtualBox (other hosts coming in the future) in one line.

PS> Get-IEVM –OS Win7 –IEVersion 9

That is the simplest form of the command.

Installation

To install, download from the github project releases page and extract to $env:USERPROFILE\WindowsPowerShell\Modules. Then to use it just import it

The version of IE. This is dependant on the version of Windows (See the table below).

6

7

8

9

10

11

Edge

Shares

NO

String[]

[Empty]

These are the paths to add as a share in the VM through the VMHost. May not be fully supported in all VMHosts.

AlternateVMLocation

NO

String

[Empty]

By default the VM images will be downloaded from Microsoft, but if you have the images downloaded already, you can use this to tell the script where to get them. This can be a URL, Network Share, or a local path. The images need to follow the following pattern:

Friday, September 18, 2015

This is a pretty big release for being a maintenance release. There are some bug fixes and a couple new features.

New Features:

Sqlite files are now edited using Sqlite Browser. This tool is far more stable, and advanced than the tool that was included before in Droid Explorer. The way this tool works, the database that you want to query/modify will be copied to your PC. You can query or modify the data. Once you close the Sqlite Browser, it will ask you if you want to push the changes back to the device.

ScreenCast is now called Screen Monitor and now uses a fork of Android Screen Monitor. The fork just removes the need to have the user select the device, since Droid Explorer already knows the device.

Screen Capture: This allow you to record your device screen for up to 3 minutes.

Rotation is done when you copy the video to the PC. This uses FFMpeg to do the rotation.

Sample video:

Changelog:

Fixed the install apk shortcut to default to install. [workitem:17512]

Added screen capture functionality. The Plugin will show up if the connected device supports screen capture. [workitem:17417]

Tweaked the SaveFileDialog, OpenFileDialog, & FileDialog to better support an 'initial directory'.

Tweaked the way the plugin toolstrips are created to hopefully support reloading when connecting to another device.

Fixed launching screenshot from the shortcut or jumplist item. [workitem:17416]

Replaced the JNLP with a more active developed androidscreencast and launch a jar file directly.

Changed the window of the ScreenRecorder to be fixed.

Updated the InstallDialog to make use of the PluginHost which provides device and other information.

Fixed the regex for checking if an app was installed successfully and fixed the regex for getting the permissions

Fixed the device backup so it launches correctly from the shortcut.

Added Sqlite Browser to replace the feature lacking sqlite explorer that was part of this project. See http://sqlitebrowser.org/ for info on Sqlite Browser.

TransferDialog now usable by plugins. [workitem:17521]

Consolidation of some string resources in to the Global App Resources

Default the file name when saving a screenshot to be 'screenshot-{yyyy-MM-dd-hhmmss}.png' [workitem:17516]

All PluginForms now require IPluginHost to be passed in.

Updated image resources for the screenshot plugin

added toolbar item to screenshot to "edit in default application"

removed SqliteEditForm since it isn't used any more.

fixed the saving size of the screenshot. It will save as the original source size [workitem:17517]

Sunday, September 13, 2015

I want to give a sneak peak of a feature in the upcoming release of Droid Explorer called Device Screen Capture. On devices that support it, you will be able to record screen activity for up to 3 minutes.

If you choose to copy to your computer after capture, you will be able to also apply rotation to the video.

Tuesday, September 8, 2015

There is a new release of Droid Explorer that is now available for download. This release is mainly some bug fixes. The most important is fixing support for the changes to ADB where the feature ‘status-window’ was removed. Droid Explorer used this feature to monitor the status of the connected devices. The removal of this required a little reworking of the monitoring, but at this point I think I am happy with the new functionality.

Tuesday, August 11, 2015

I have been a user of Growl for Windows for a long time. I recently upgraded to Windows 10 and installed Growl, like I usually do. I liked the way the new notifications in Windows 10 looked and wanted that look for Growl so I created a Windows 10 Style Display for Growl.

Right now, there is really only one option to set, and that is where you would like it to show up on screen.

Monday, August 3, 2015

There are a lot of tutorials out there that are for previous versions of Windows that say to right click on the VPN and choose properties, then select IPv4 and click properties. The problem is with Windows 10, at least for me, nothing happens when you click the properties button.

The way I have found to enable this functionality is via PowerShell.

Start PowerShell as an administrator then run Get-VpnConnection

Next run Set-VpnConnection –Name MY_VPN_NAME –SplitTunneling $trueReplace MY_VPN_NAME with the name of your VPN connection.

Sunday, March 8, 2015

I just published a minor update to Droid Explorer. This fixes a couple bugs with the Shell console where some lines that should be on a new line are not. There are some new shortcuts now added to the start menu for quick access to launch the shell console, device backup, apk installation, taking a screenshot, and to launch the screencast plugin.

Also addressed is an issue where some older devices do not show up in the device selection. This was because Droid Explorer now uses ‘adb devices –l’ to get more detailed information about the device, but it appears that some older devices do not display this information. To resolve this, it will try to look for the additional information, if it isn’t found, it will fall back to use the information without the details. A downside to this, which I may address later, is the device icon will not be the true device icon because the web service will not know what device it is.

Tuesday, March 3, 2015

My Hangouts app in Chrome has been vanishing on me on my home computer and I could not figure out why. I tried to uninstall it and reinstall it. Nothing fixed it. When I would close it and restart the app, it would show the “loading spinner” as normal size, but then it would shrink to an extremely tiny icon. If I then tried to click on the Hangouts app, it would vanish, never to be seen again until I reloaded the app again.

After some searching, turns out that this is a bug, that is being tracked here.

Here is how I worked around the issue, not sure how permanent this work around is though.

Monday, March 2, 2015

As I posted in my previous post, I recently bought an Amazon Echo. I saw some videos of people using their Echo to do home automation with a Raspberry Pi or Adriano. They did this by using something like Node, or python to monitor the tasks that are added to the Echo. To do the monitoring, they used the undocumented, unsupported, Api of the Echo.

I wanted to play around too. While I really don’t do anything related to home automation, I still wanted to explore the Echo Api and see if I could implement some type of wrapper for it in C#.

Here is what I found with the undocumented Api:

The desktop app connects to a WebSocket on the Echo device. I have not yet successfully connected to the socket, nor have I tried yet.

There is a url to get the latest “cards” - /api/cards?limit=N

Get the tasks - /api/todos?type=TASK

Get the shopping list - /api/todos?type=SHOPPING_ITEM

Get registered devices - /api/device

Get the media state for a device - /api/media/state?deviceSerialNumber={0}&deviceType={1}

Get the connected bluetooth devices - /api/bluetooth

Get music accounts - /api/music-account-details

logout - /logout

Get the capabilities of each provider - /api/media/provider-contenttype-capabilities

I also found that I should be able to send commands to Play, Stop, Next Track, Previous Track, Shuffle, Repeat, and set the Volume. The web app does this by first doing an HTTP/OPTIONS request, followed by an HTTP/POST. The post contains a JSON payload that contains the meta data of the device and what the volume is (if setting the volume). I have been unable to successfully POST these commands as there should be a CSRF token sent along with the POST. This token should be available in the cookies, but for some reason that I have not figured out yet, the token does not exist in the CookieContainer.

Currently, I have a working wrapper Api to Login, Logout, Get Tasks (TODO or SHOPPING), and update a task. I have posted my code on GitHub and I will push changes when I make them. This is just a little toy project that I decided to play with when bored. I will continue to work on it in free time, while I am interested in it. Feel free to fork it.

Sunday, March 1, 2015

I bought an Amazon Echo last week. I was looking for a Bluetooth speaker and for $100 (for Prime Members), it is a decent Bluetooth speaker, plus it integrates with Prime music, and other Amazon services. It allows you to purchase items from Amazon directly from the Echo. It also has other features like TuneIn radio, iHeartRadio, a timer, an alarm (seems like it should support more than one timer and alarm, hopefully they will add this functionality in the future), todo list, and a shopping list.

The Echo has a companion app for iOS and Android devices, and it has a web app for your desktop. I was playing around with the CSS the other day while I was off work and decided to re-theme all (or most) of the desktop app using Stylish (Chrome|Firefox).

Friday, February 13, 2015

Today is Friday the 13th, but it doesn’t mark a day for superstition. Instead it marks the release of a long over due update to Droid Explorer. I have been working hard the past couple months getting this release ready. As I have mentioned in some previous posts, there are a lot of redesigned components, like the Shell Console, LogCat Console, the Device Selection dialog, and much more. Another key change is the handling of, non-issue, questions. Instead of being part of the discussion on CodePlex, there is now a tag on Android Enthusiasts. If using Android Enthusiasts, be sure to be detailed in what your issue is. I am not the only one that would be monitoring questions there. I wouldn’t want to see the questions closed because of lack of information.

On top of the changes that went in to Droid Explorer, I am also announcing the launch of http://de.bit13.com/, a new home for the Droid Explorer project. Besides being a place that contains screenshots and information on the releases, it acts as a central service for the device icons that are displayed when choosing the device to connect to and the icon that is shown in Explorer. As I get more information on devices, more icons will be added. Over time, other features will possible integrate more with the website.

Highlights of the Changelog for 0.9.0.0

Added support for connecting to devices via TCP/IP New web service for getting device icons.

Tuesday, January 20, 2015

Extensions in Droid Explorer can already handle specific file types. The shell console and sqlite explorer are good examples of that. When you right click on a file that is handled by an extension you will see it as an option.

Extensions can now implement DroidExplorer.Core.Plugins.IFileTypeIconHandler. This will allow an extension to define how the icons for the specified file are rendered. Here you will see the new PictureExtension. It shows a small thumbnail of the picture as the icon of the file.

These icons will be cached in the users Droid Explorer Data/Assets directory so they can be loaded from the cache to load faster.

Saturday, January 17, 2015

A few days ago I showed some screenshots of some of the work that I have done in the next version of Droid Explorer. One of the things that I talked about was how I will monitor the DroidExplorer tag on Android Enthusiasts. Here is how that will also play a part in the next version of Droid Explorer.

Right from the UI, you will be able to quickly get to the Android Enthusiasts questions that are tagged with DroidExplorer. If those don’t help, you can ask your own question. Just make sure you use the correct tag and that your questions are detailed and specific. If they are bug reports, they will not be answered and they will probably be closed. Bug reports will still go on the Issue Tracker.

I have also implemented another way to keep up to date with new releases and new code commits. If you are a Pushbullet user, you can subscribe to the Droid Explorer Channels:

Wednesday, January 14, 2015

I've been working on some updates to Droid Explorer (which will probably get a name change with the next release).These updates include:

Being able to connect to devices via TCP/IP.

A new Shell Console (which is much needed as the old one is very buggy and only works on a few devices correctly, or at all) that has full color processing.

A new layout for the Device Selection dialog. Less clutter, more information.

An updated debug console

An updated logcat console.

Effective immediately, I will be monitoring a tag [DroidExplorer] over on Android Enthusiasts Stack Exchange for non-bug related support. If it is an actual bug, it should be created as a bug, if you are just having an issue, or a question, then you can ask it over on Android Enthusiasts.

Finally, I am considering moving the source code to Github. If I do decide to move it, releases will probably still stay on CodePlex, at least for the time being. They have a good api that is already built in to my build scripts so I can easily publish new releases.

Some of the reasons I may be moving:

It seems that Microsoft has abandoned CodePlex.

The blog hasn't been updated in over a year.

Performance of the site has decreased.

Analytics have been having issues since October. And I have attempted to contact the CodePlex team, via Email and Twitter, without a response.

I wanted to get Hubot working in our slack channels at work and I thought I would share the process I took to get it working and running on Azure Websites.

First, make sure you have nodejs installed

> choco install nodejs.install -y

Make sure npm is up to date

> npm install -g npm

At this point, I also installed coffee-script because the first time I tried running it, I got errors about coffee script

> npm install -g coffee-script

Install the azure-cli node modules to generate the deploy file that will be used

> npm install –g azure-cli

Next we install the yo hubot generator

> npm install –g yo generator-hubot

create a directory for your hubot. I have found that you should not initially name it “hubot”, as npm will fail with some of the package installs (specifically, the hubot package). Then lets start the hubot configuration

> mkdir myhubot

> cd myhubot

> yo hubot

Now you will answer the question it asks to configure hubot. Again, I wouldn’t name it “hubot” when it asks. I will show you where to change it later so it will respond to hubot.

Mine showed some error messages while running this, but still functioned correctly.

Now lets install the slack adapter

> npm install hubot-slack --save

next we need to create the azure deploy command.

> azure site deploymentscript –node

lets now make a couple tweaks to the hubot files:

first, open up external-scripts.json and remove

"hubot-heroku-keepalive",

"hubot-redis-brain"

if you want to use azure blob for the brain we can set that up now. while still in the external-scripts.json, add the line:

Login to your Azure portal and create a new Web App: (The name has to be unique)

If you are using Azure blob for the brain, create the storage account as well.

After the storage is created, we will need the Storage Account Name, and Primary Access Key. Copy these for use a little later:

Go in to the settings for your newly created web app and click on “Continuous Deployment”. We are going to configure Azure Web Site to pull directly from the Github repo for the hubot configuration.

Choose Github as the provider and then authorize Azure to connect. Then choose your Hubot

Finally we have to set up the environment variables that Hubot needs to function:

You will create the following keys:

HUBOT_SLACK_TOKEN: Your Slack Token for Hubot when you enable the integration

HUBOT_SLACK_TEAM: myslack (from https://myslack.slack.com)

HUBOT_SLACK_BOTNAME: The name of your hubot

HUBOT_ADAPTER: slack

HUBOT_BRAIN_AZURE_STORAGE_ACCOUNT: The storage account name we saved from above

HUBOT_BRAIN_AZURE_STORAGE_ACCESS_KEY: The storage access token we saved from above

Go to your webapp to test that your hubot is working.

http://myhubot1.azurewebsites.net/hubot/help

Sometimes it doesn’t respond the first time, but if it continues to fail when requesting, there there may be an issue. Try running locally (you will have to remove the azure-blob when running local) and see if everything is working.

If you are familiar with .bash_history or just wish you had a history of your powershell commands persist between sessions here is a handy little script. It will persist command history when you exit a powershell session to a file in %USERPROFILE% called .ps_history.

Copy the code below and save to a file called “Microsoft.PowerShell_profile.ps1” and save it in “%USERPROFILE%\Documents\WindowsPowerShell”

To add to the my list of hobby projects, I created a fork of an addon for Kodi that provides browsing of videos on Microsoft Channel9. This was my first attempt at a Kodi addon, and really my first time working with writing python. I started out by just reading over the original code and tweaking it a bit because some things were not working. Then I started following the pattern that existed and implementing new features, like being able to browse Channel9 authors, and Channel9 events.

Once I got these features in place, I started doing some real refactoring of the original code base. There was a ton of code that was duplicated in multiple places. I spent a few hours of the day really rewriting the entire addon. As the project stands right now, it is basically a complete rewrite of the original addon.

Over the weekend I was bored and decided to start a project to automate the process of standing up an IE VM with powershell. I would like to introduce PSIEVM. A powershell module that allows you to stand up an IE VM in VirtualBox (other hosts coming in the future) in one line.

PS> Get-IEVM –OS Win7 –IEVersion 9

That is the simplest form of the command.

Installation

To install, download from the github project releases page and extract to $env:USERPROFILE\WindowsPowerShell\Modules. Then to use it just import it

The version of IE. This is dependant on the version of Windows (See the table below).

6

7

8

9

10

11

Edge

Shares

NO

String[]

[Empty]

These are the paths to add as a share in the VM through the VMHost. May not be fully supported in all VMHosts.

AlternateVMLocation

NO

String

[Empty]

By default the VM images will be downloaded from Microsoft, but if you have the images downloaded already, you can use this to tell the script where to get them. This can be a URL, Network Share, or a local path. The images need to follow the following pattern:

This is a pretty big release for being a maintenance release. There are some bug fixes and a couple new features.

New Features:

Sqlite files are now edited using Sqlite Browser. This tool is far more stable, and advanced than the tool that was included before in Droid Explorer. The way this tool works, the database that you want to query/modify will be copied to your PC. You can query or modify the data. Once you close the Sqlite Browser, it will ask you if you want to push the changes back to the device.

ScreenCast is now called Screen Monitor and now uses a fork of Android Screen Monitor. The fork just removes the need to have the user select the device, since Droid Explorer already knows the device.

Screen Capture: This allow you to record your device screen for up to 3 minutes.

Rotation is done when you copy the video to the PC. This uses FFMpeg to do the rotation.

Sample video:

Changelog:

Fixed the install apk shortcut to default to install. [workitem:17512]

Added screen capture functionality. The Plugin will show up if the connected device supports screen capture. [workitem:17417]

Tweaked the SaveFileDialog, OpenFileDialog, & FileDialog to better support an 'initial directory'.

Tweaked the way the plugin toolstrips are created to hopefully support reloading when connecting to another device.

Fixed launching screenshot from the shortcut or jumplist item. [workitem:17416]

Replaced the JNLP with a more active developed androidscreencast and launch a jar file directly.

Changed the window of the ScreenRecorder to be fixed.

Updated the InstallDialog to make use of the PluginHost which provides device and other information.

Fixed the regex for checking if an app was installed successfully and fixed the regex for getting the permissions

Fixed the device backup so it launches correctly from the shortcut.

Added Sqlite Browser to replace the feature lacking sqlite explorer that was part of this project. See http://sqlitebrowser.org/ for info on Sqlite Browser.

TransferDialog now usable by plugins. [workitem:17521]

Consolidation of some string resources in to the Global App Resources

Default the file name when saving a screenshot to be 'screenshot-{yyyy-MM-dd-hhmmss}.png' [workitem:17516]

All PluginForms now require IPluginHost to be passed in.

Updated image resources for the screenshot plugin

added toolbar item to screenshot to "edit in default application"

removed SqliteEditForm since it isn't used any more.

fixed the saving size of the screenshot. It will save as the original source size [workitem:17517]

I want to give a sneak peak of a feature in the upcoming release of Droid Explorer called Device Screen Capture. On devices that support it, you will be able to record screen activity for up to 3 minutes.

If you choose to copy to your computer after capture, you will be able to also apply rotation to the video.

There is a new release of Droid Explorer that is now available for download. This release is mainly some bug fixes. The most important is fixing support for the changes to ADB where the feature ‘status-window’ was removed. Droid Explorer used this feature to monitor the status of the connected devices. The removal of this required a little reworking of the monitoring, but at this point I think I am happy with the new functionality.

I have been a user of Growl for Windows for a long time. I recently upgraded to Windows 10 and installed Growl, like I usually do. I liked the way the new notifications in Windows 10 looked and wanted that look for Growl so I created a Windows 10 Style Display for Growl.

Right now, there is really only one option to set, and that is where you would like it to show up on screen.

There are a lot of tutorials out there that are for previous versions of Windows that say to right click on the VPN and choose properties, then select IPv4 and click properties. The problem is with Windows 10, at least for me, nothing happens when you click the properties button.

The way I have found to enable this functionality is via PowerShell.

Start PowerShell as an administrator then run Get-VpnConnection

Next run Set-VpnConnection –Name MY_VPN_NAME –SplitTunneling $trueReplace MY_VPN_NAME with the name of your VPN connection.

I just published a minor update to Droid Explorer. This fixes a couple bugs with the Shell console where some lines that should be on a new line are not. There are some new shortcuts now added to the start menu for quick access to launch the shell console, device backup, apk installation, taking a screenshot, and to launch the screencast plugin.

Also addressed is an issue where some older devices do not show up in the device selection. This was because Droid Explorer now uses ‘adb devices –l’ to get more detailed information about the device, but it appears that some older devices do not display this information. To resolve this, it will try to look for the additional information, if it isn’t found, it will fall back to use the information without the details. A downside to this, which I may address later, is the device icon will not be the true device icon because the web service will not know what device it is.

My Hangouts app in Chrome has been vanishing on me on my home computer and I could not figure out why. I tried to uninstall it and reinstall it. Nothing fixed it. When I would close it and restart the app, it would show the “loading spinner” as normal size, but then it would shrink to an extremely tiny icon. If I then tried to click on the Hangouts app, it would vanish, never to be seen again until I reloaded the app again.

After some searching, turns out that this is a bug, that is being tracked here.

Here is how I worked around the issue, not sure how permanent this work around is though.

As I posted in my previous post, I recently bought an Amazon Echo. I saw some videos of people using their Echo to do home automation with a Raspberry Pi or Adriano. They did this by using something like Node, or python to monitor the tasks that are added to the Echo. To do the monitoring, they used the undocumented, unsupported, Api of the Echo.

I wanted to play around too. While I really don’t do anything related to home automation, I still wanted to explore the Echo Api and see if I could implement some type of wrapper for it in C#.

Here is what I found with the undocumented Api:

The desktop app connects to a WebSocket on the Echo device. I have not yet successfully connected to the socket, nor have I tried yet.

There is a url to get the latest “cards” - /api/cards?limit=N

Get the tasks - /api/todos?type=TASK

Get the shopping list - /api/todos?type=SHOPPING_ITEM

Get registered devices - /api/device

Get the media state for a device - /api/media/state?deviceSerialNumber={0}&deviceType={1}

Get the connected bluetooth devices - /api/bluetooth

Get music accounts - /api/music-account-details

logout - /logout

Get the capabilities of each provider - /api/media/provider-contenttype-capabilities

I also found that I should be able to send commands to Play, Stop, Next Track, Previous Track, Shuffle, Repeat, and set the Volume. The web app does this by first doing an HTTP/OPTIONS request, followed by an HTTP/POST. The post contains a JSON payload that contains the meta data of the device and what the volume is (if setting the volume). I have been unable to successfully POST these commands as there should be a CSRF token sent along with the POST. This token should be available in the cookies, but for some reason that I have not figured out yet, the token does not exist in the CookieContainer.

Currently, I have a working wrapper Api to Login, Logout, Get Tasks (TODO or SHOPPING), and update a task. I have posted my code on GitHub and I will push changes when I make them. This is just a little toy project that I decided to play with when bored. I will continue to work on it in free time, while I am interested in it. Feel free to fork it.

I bought an Amazon Echo last week. I was looking for a Bluetooth speaker and for $100 (for Prime Members), it is a decent Bluetooth speaker, plus it integrates with Prime music, and other Amazon services. It allows you to purchase items from Amazon directly from the Echo. It also has other features like TuneIn radio, iHeartRadio, a timer, an alarm (seems like it should support more than one timer and alarm, hopefully they will add this functionality in the future), todo list, and a shopping list.

The Echo has a companion app for iOS and Android devices, and it has a web app for your desktop. I was playing around with the CSS the other day while I was off work and decided to re-theme all (or most) of the desktop app using Stylish (Chrome|Firefox).

Today is Friday the 13th, but it doesn’t mark a day for superstition. Instead it marks the release of a long over due update to Droid Explorer. I have been working hard the past couple months getting this release ready. As I have mentioned in some previous posts, there are a lot of redesigned components, like the Shell Console, LogCat Console, the Device Selection dialog, and much more. Another key change is the handling of, non-issue, questions. Instead of being part of the discussion on CodePlex, there is now a tag on Android Enthusiasts. If using Android Enthusiasts, be sure to be detailed in what your issue is. I am not the only one that would be monitoring questions there. I wouldn’t want to see the questions closed because of lack of information.

On top of the changes that went in to Droid Explorer, I am also announcing the launch of http://de.bit13.com/, a new home for the Droid Explorer project. Besides being a place that contains screenshots and information on the releases, it acts as a central service for the device icons that are displayed when choosing the device to connect to and the icon that is shown in Explorer. As I get more information on devices, more icons will be added. Over time, other features will possible integrate more with the website.

Highlights of the Changelog for 0.9.0.0

Added support for connecting to devices via TCP/IP New web service for getting device icons.

Extensions in Droid Explorer can already handle specific file types. The shell console and sqlite explorer are good examples of that. When you right click on a file that is handled by an extension you will see it as an option.

Extensions can now implement DroidExplorer.Core.Plugins.IFileTypeIconHandler. This will allow an extension to define how the icons for the specified file are rendered. Here you will see the new PictureExtension. It shows a small thumbnail of the picture as the icon of the file.

These icons will be cached in the users Droid Explorer Data/Assets directory so they can be loaded from the cache to load faster.

A few days ago I showed some screenshots of some of the work that I have done in the next version of Droid Explorer. One of the things that I talked about was how I will monitor the DroidExplorer tag on Android Enthusiasts. Here is how that will also play a part in the next version of Droid Explorer.

Right from the UI, you will be able to quickly get to the Android Enthusiasts questions that are tagged with DroidExplorer. If those don’t help, you can ask your own question. Just make sure you use the correct tag and that your questions are detailed and specific. If they are bug reports, they will not be answered and they will probably be closed. Bug reports will still go on the Issue Tracker.

I have also implemented another way to keep up to date with new releases and new code commits. If you are a Pushbullet user, you can subscribe to the Droid Explorer Channels:

I've been working on some updates to Droid Explorer (which will probably get a name change with the next release).These updates include:

Being able to connect to devices via TCP/IP.

A new Shell Console (which is much needed as the old one is very buggy and only works on a few devices correctly, or at all) that has full color processing.

A new layout for the Device Selection dialog. Less clutter, more information.

An updated debug console

An updated logcat console.

Effective immediately, I will be monitoring a tag [DroidExplorer] over on Android Enthusiasts Stack Exchange for non-bug related support. If it is an actual bug, it should be created as a bug, if you are just having an issue, or a question, then you can ask it over on Android Enthusiasts.

Finally, I am considering moving the source code to Github. If I do decide to move it, releases will probably still stay on CodePlex, at least for the time being. They have a good api that is already built in to my build scripts so I can easily publish new releases.

Some of the reasons I may be moving:

It seems that Microsoft has abandoned CodePlex.

The blog hasn't been updated in over a year.

Performance of the site has decreased.

Analytics have been having issues since October. And I have attempted to contact the CodePlex team, via Email and Twitter, without a response.