Updated to latest build tools
Fixed crash when no host is provided
Bumped version number
Fix looping on Galaxy S5 running 4.4.4

What I've observed is that when the video stops and the onCompletion() method is called, the position of the video is not the same as the duration of the video.  For example, a gfy with a duration of 6800 will end at 6600, or another one with a duration of 7400 ends at 7340.  I don't know why this happens.  Waiting in the onCompletion() method for the duration to finish does not work.  Attempting to call seekTo() and start() also does not seem to work.

I did however notice this message:
2263-2263/net.danlew.gfycat E/MediaPlayer﹕ internal/external state mismatch corrected

Calling mediaPlayer.isPlaying() before seekTo() and start() does not prevent the error message, but does appear to enable looping.

Interestingly a call to pause() before seekTo() and start() seems to prevent the state mismatch error and also enable looping.  For some reason the internal state of the MediaPlayer object is not right and is preventing looping from working on my particular device.
Merge pull request #14 from megaclite/patch-1

Fix looping on Galaxy S5 running 4.4.4
Handle ACTION_SEND intents of text/plain type

- Added text/plain send intents to the manifest
- Fixed bracketing
- Removed unnecessay if-statement
- Changed text null check to TextUtils.isEmpty()
- Added null checks on mGifUrl and mGfyName
- Added a URL check on parsed text field
Updated changelog
Added contributors to README
Merge pull request #12 from megaclite/master

Handle send intents
Updated CHANGELOG
Added video progress bar
Fixed progress bar thread start/termination

The condition keeping the thread running would sometimes prematurely terminate when the video loop reset.

There was also a problem if the activity was backgrounded and restored (ex. the screen is turned off and on again)
Reverting back to FrameLayout
First working attempt with RxJava

Definitely needs to be cleaned up