can not use in my tvbox m9s android lolippop .please help . can not send to usb pen drive.

.github/CONTRIBUTING.md

@@ -0,0 +1,137 @@
+# Contributing to Quasar
+
+Looking to contribute something? **Here's how you can help.**
+
+Please take a moment to review this document in order to make the contribution
+process easy and effective for everyone involved.
+
+Following these guidelines helps to communicate that you respect the time of
+the developers managing and developing this open source project. In return,
+they should reciprocate that respect in addressing your issue or assessing
+patches and features.
+
+
+## Using the issue tracker
+
+The issue tracker is the preferred channel for [bug reports](#bug-reports),
+[features requests](#feature-requests) and
+[submitting pull requests](#pull-requests), but please respect the
+following restrictions:
+
+* Please **do not** use the issue tracker for personal support requests. The
+  [Kodi forum thread](http://forum.kodi.tv/showthread.php?tid=257967) is a better place to get help.
+
+* Please **do not** derail or troll issues. Keep the discussion on topic and
+  respect the opinions of others.
+
+* Please **do not** open issues or pull requests which *belongs to* third party
+  components.
+
+
+## Bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful, so thanks!
+
+Guidelines for bug reports:
+
+1. **Use the GitHub issue search** — check if the issue has already been
+   reported.
+
+2. **Check if the issue has been fixed** — try to reproduce it using the
+   latest version of the add-on.
+
+3. **Provide logs** — this cannot be overstated enough; bug reports
+   without logs will likely be dismissed and closed.
+
+
+A good bug report shouldn't leave others needing to chase you up for more
+information. Please try to be as detailed as possible in your report. What is
+your environment? What steps will reproduce the issue? What browser(s) and OS
+experience the problem? Do other browsers show the bug differently? What
+would you expect to be the outcome? All these details will help people to fix
+any potential bugs.
+
+
+## Feature requests
+
+Feature requests are welcome. But take a moment to find out whether your idea
+fits with the scope and aims of the project. It's up to *you* to make a strong
+case to convince the project's developers of the merits of this feature. Please
+provide as much detail and context as possible.
+
+
+## Pull requests
+
+Good pull requests, patches, improvements and new features are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**Please ask first** before embarking on any significant pull request (e.g.
+implementing features, refactoring code, porting to a different language),
+otherwise you risk spending a lot of time working on something that the
+project's developers might not want to merge into the project.
+
+Please adhere to the [coding guidelines](#code-guidelines) used throughout the
+project (indentation, accurate comments, etc.) and any other requirements
+(such as test coverage).
+
+Adhering to the following process is the best way to get your work
+included in the project:
+
+1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
+   and configure the remotes:
+
+   ```bash
+   # Clone your fork of the repo into the current directory
+   git clone https://github.com/scakemyer/plugin.video.quasar.git
+   # Navigate to the newly cloned directory
+   cd plugin.video.quasar
+   # Assign the original repo to a remote called "upstream"
+   git remote add upstream https://github.com/scakemyer/plugin.video.quasar.git
+   ```
+
+2. If you cloned a while ago, get the latest changes from upstream:
+
+   ```bash
+   git checkout master
+   git pull --rebase upstream master
+   ```
+
+3. Create a new topic branch (off the main project development branch) to
+   contain your feature, change, or fix:
+
+   ```bash
+   git checkout -b <topic-branch-name>
+   ```
+
+4. Commit your changes in logical chunks. Please adhere to these [git commit
+   message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+   or your code is unlikely be merged into the main project. Use Git's
+   [interactive rebase](https://help.github.com/articles/interactive-rebase)
+   feature to tidy up your commits before making them public. Also, prepend name of the feature
+   to the commit message. For instance: "SCSS: Fixes compiler results for IFileListener, fixes `#123`"
+
+5. Locally merge (or rebase) the upstream development branch into your topic branch:
+
+   ```bash
+   git pull --rebase upstream master
+   ```
+
+6. Push your topic branch up to your fork:
+
+   ```bash
+   git push origin <topic-branch-name>
+   ```
+
+7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
+    with a clear title and description against the `master` branch.
+
+
+## Code guidelines
+
+- Indentation must be 4 spaces for Python files. Follow proper indentation for
+  other file types.
+- Always run `flake8` before committing and pushing changes.
+- Run `./scripts/xgettext.sh` if you're updating translations to make sure
+  your changes are valid.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,47 @@
+<!--- ISSUES ABOUT PROVIDERS DO NOT BELONG HERE -->
+<!--- If you open an issue about providers, it will get closed,
+      its title and content will get removed, and your GitHub
+      account will be blocked from this repository.
+      Proceed to the next steps if you understand this warning. -->
+
+<!--- Describe the issue briefly and as best as you can in the Title above -->
+<!--- Issue titles like "Last version crashes", "0.9.x crashing",
+      or "Nothing works after update" are the worst. Put some effort
+      in describing your issue properly, and we'll put some effort
+      in fixing it as soon as possible -->
+<!--- Bug reports without logs will likely be dismissed and closed -->
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Version used:
+<!--- Which version of Quasar are you using? -->
+* Environment name and version:
+<!--- Which Kodi version (16 [Jarvis] or 17 [Krypton]) and OS, eg. SPMC, OSMC, OpenELEC, LibreELEC, etc. -->
+* Operating System and version:
+<!--- eg. Android 4/5/6, Windows 7/8/10, macOS 10.11, Ubuntu 16.10, etc. -->
+* Link to Kodi debug log:
+<!--- See http://kodi.wiki/view/Log_file/Easy or paste to http://paste.ubuntu.com directly -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,41 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+<!--- Pull requests for translations can skip the following, simply title
+      your pull request as "Translation update for [language]" and squash
+      your commits into a single one with the same title, if possible. -->
+
+## Description
+<!--- Describe your changes in detail -->
+
+## Related Issue
+<!--- If suggesting a new feature or change, please discuss it in an issue first -->
+<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
+<!--- Please link to the issue here: -->
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Screenshots (if appropriate):
+
+## Types of changes
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+- [ ] Translation
+
+## Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] My code follows the code style of this project.
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.
+- [ ] I have read the **CONTRIBUTING** document.
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.

.gitignore

@@ -21,6 +21,8 @@ var/
 *.egg-info/
 .installed.cfg
 *.egg
+*.zip
+# bin/
 
 # PyInstaller
 #  Usually these files are written by a python script from a template
@@ -40,10 +42,6 @@ htmlcov/
 nosetests.xml
 coverage.xml
 
-# Translations
-*.mo
-*.pot
-
 # Django stuff:
 *.log
 
@@ -52,3 +50,7 @@ docs/_build/
 
 # PyBuilder
 target/
+
+# Other
+# resources/bin
+resources/web/static/js/*.map

.gitlab-ci.yml

@@ -0,0 +1,61 @@
+image: alpine:latest
+
+stages:
+  - test
+  - build
+  - release
+
+test:
+  image: python:2.7-alpine
+  stage: test
+  before_script:
+    - pip install -r requirements.txt
+  script:
+    - flake8
+    - ./scripts/xgettext.sh
+
+build:
+  stage: build
+  before_script:
+    - apk update
+    - apk add git make zip
+    - git submodule update --init --depth=22
+  script:
+    - make
+  only:
+    - master
+
+release:
+  stage: release
+  before_script:
+    - apk update
+    - apk add git make lftp zip
+    - git submodule update --init --depth=22
+  script:
+    - make
+    - make zipfiles
+  after_script:
+    - |
+        lftp -c "open 'ftp://$FTP_USER:$FTP_PASS@$FTP_HOST'; \
+        cd plugin.video.quasar; \
+        mirror --reverse --verbose --exclude '.*' --exclude '.*/' --include-glob addon.xml; \
+        mkdir -p -f $CI_BUILD_TAG; \
+        cd $CI_BUILD_TAG; \
+        mirror --reverse --verbose --exclude '.*' --exclude '.*/' --include-glob *.zip; \
+        exit;"
+  artifacts:
+    paths:
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.android_arm.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.android_x64.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.android_x86.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.darwin_x64.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.linux_arm.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.linux_armv7.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.linux_arm64.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.linux_x64.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.linux_x86.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.windows_x64.zip
+    - plugin.video.quasar-${CI_BUILD_TAG:1}.windows_x86.zip
+  only:
+    - tags

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "resources/bin"]
+	path = resources/bin
+	url = https://github.com/scakemyer/quasar-binaries

.travis.yml

@@ -0,0 +1,42 @@
+language: python
+python:
+  - 2.7
+
+git:
+  submodules: false
+
+before_install:
+  - git submodule init
+  - git submodule update --depth=22
+
+install:
+  - pip install -r requirements.txt
+
+script:
+  - flake8
+  - ./scripts/xgettext.sh
+  - make
+  - |
+    if [ "${TRAVIS_PULL_REQUEST}" = "false" ] && [ -n "${TRAVIS_TAG}" ]; then
+      make zipfiles
+    fi
+
+deploy:
+  provider: releases
+  api_key: $GH_TOKEN
+  file:
+    - plugin.video.quasar-${TRAVIS_TAG:1}.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.android_arm.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.android_x64.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.android_x86.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.darwin_x64.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.linux_arm.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.linux_armv7.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.linux_arm64.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.linux_x64.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.linux_x86.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.windows_x64.zip
+    - plugin.video.quasar-${TRAVIS_TAG:1}.windows_x86.zip
+  skip_cleanup: true
+  on:
+    tags: true