Probleme beim Streamen von Filmen von der NAS

Hallo!

Ich bin neu hier und habe mir Kodi auf dem Amazon Fire Stick zugelegt. Ich habe allerdings ein Problem, meine Filme von der NAS zu streamen. Liegt es wohl daran, das der Fire Stick nur über WLAN läuft? Hätte ich mit der Box mit LAN-Kabel mehr Erfolg?
Ich möchte auch nicht unbedingt für 90 € die Box kaufen, wenn es dann wieder nicht funktioniert.

Kann es an dem Skin liegen, das ich ausgesucht habe?

Ich bitte um ein paar Tipps.

Ich muss dazu sagen, auch wenn ich technisch nicht ganz untalentiert bin, habe ich mir den Stick mit Kodi einrichten lassen. Ich wäre dir aber sehr dankbar, wenn du mir das etwas kleinschrittiger erklären könntest...

Okay, ich habe die Datei erstellt und in die Userdata eingefügt.
Dann habe ich ADB Shell geöffnet und den Quellcode eingegeben.
1. Problem: Er sagt unable to connect to Fire-TV-IP-
2. Problem: Der Rest funzt dann auch nicht.

Ich habe gemacht. Am Ende stand ganz viel Text. Das --> "13 KB/s (201 bytes in 0.015s)" habe ich aber nicht finden können.

http://imageshack.com/a/img537/3981/tPtIvQ.jpg

http://imageshack.com/a/img661/6378/BypAs4.jpg

http://imageshack.com/a/img540/4548/UlRX3h.jpg

http://imageshack.com/a/img903/7184/RJujpu.jpg

Komisch. Ich hab das nach Imageshack hochgeladen.

Sollte jetzt funktionieren:

http://www.imageshack.com/a/img537/3981/tPtIvQ.jpg

http://www.imageshack.com/a/img661/6378/BypAs4.jpg

http://www.imageshack.com/a/img540/4548/UlRX3h.jpg

http://www.imageshack.com/a/img903/7184/RJujpu.jpg

error: more than one device and emulator

Was mach ich jetzt?

Dieses mal gab es keine Fehlermeldungen aber ich glaube es ist wieder der selbe Text!?
Was mache ich verkehrt?
--------------------------------------------------------------------------------------------------------------
1|shell@android:/ $ adb kill-server
adb kill-server
shell@android:/ $ adb start-server
adb start-server
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
adshell@android:/ $ adb connect 192.168.178.37
$ adb connect 192.168.178.37
/system/bin/sh: $: not found
127|shell@android:/ $ adb connect 192.168.178.37
adb connect 192.168.178.37
connected to 192.168.178.37:5555
shell@android:/ $ adb push [definition='2','1']advancedsettings[/definition].xml/sdcard/android/data/org.xbmc.kod
i/files/.kodi/userdata
sdcard/android/data/http://org.xbmc.kodi/files/.kodi/userdata <
Android [definition='1','3']Debug[/definition] Bridge version 1.0.31

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device [definition='1','0']log[/definition]
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)

adb restore <file> - restore device contents from the <file> backup
archive

adb help - show this help message
adb version - show version num

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
1|shell@android:/ $
--------------------------------------------------------------------------------------------------------------

Ich habe in dem adbFire Programm auf ADB Shell geklickt. Dann kam ein schwarzes Fenster (DOS-Box?) und da habe ich den Kram eingetippt.

Sollte ich das nicht so machen?