I have setup nginx file server on my old Android phone (Samsung A6). I did this using termux and running nginx on termux. This file server is used to serve media files to Kodi on my android TV. When I try to play a media file of size>2GB, it plays normally. But, I cannot forward to a point beyond the 2GB data point. Example media file is 4GB and duration of media is 2 hours. I am unable to skip to or resume to any point in the video beyond 1 hour 1 minute. I setup the same server with the same config in my new phone (Samsung S20FE). Everything works perfectly irrespective of file size. So, I am guessing there is some hardware limitation that I am unable to understand. Is there a way to solve this? My Samsung A6 can play large videos normally (in MX Player or VLC) but not able to serve via file server. I have tried splitting the media files to smaller chunks and playing through Kodi but Kodi recognizes it as a single media file and the same problem occurs. Curl response to the file server (on Samsung Galaxy A6) says Address not serviceable, but does not give this error when the same file is hosted on Samsung S20FE. curl -I http://192.168.1.55:14555/test.mkv HTTP/1.1 200 OK Server: nginx/1.25.3 Date: Tue, 23 Jan 2024 18:33:24 GMT Content-Type: application/octet-stream Content-Length: 3106324386 Last-Modified: Tue, 23 Jan 2024 06:48:51 GMT Connection: keep-alive ETag: "65af6153-b926bfa2" Accept-Ranges: bytes curl -v -r 2147483348-2147483647 http://192.168.1.55:14555/test.mkv > Trying 192.168.1.55:14555... > Connected to 192.168.1.55 (192.168.1.55) port 14555 > GET /test.mkv HTTP/1.1 > Host: 192.168.1.55:14555 > Range: bytes=2147483348-2147483647 > User-Agent: curl/8.4.0 > Accept: */* > " to save to a file. * Failure writing output to destination * Closing connection curl -v -r 2147483348-2147483649 http://192.168.1.55:14555/test.mkv * Trying 192.168.1.55:14555... * Connected to 192.168.1.55 (192.168.1.55) port 14555 > GET /test.mkv HTTP/1.1 > Host: 192.168.1.55:14555 > Range: bytes=2147483348-2147483649 > User-Agent: curl/8.4.0 > Accept: */* > 416 Requested Range Not Satisfiable

416 Requested Range Not Satisfiable

nginx/1.25.3 * Connection #0 to host 192.168.1.55 left intact As soon as the curl command requests file beyond the 2GB mark of the file, Nginx gives the 416 error. I am expecting Nginx to serve large files to Kodi without any issues. Nginx Config: #user nobody; worker_processes 1; #error_log logs/error.log; #error_log logs/error.log notice; #error_log logs/error.log info; #pid logs/nginx.pid; events { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; client_max_body_size 0; #log_format main '$remote_addr - $remote_user [$time_local] "$request" ' # '$status $body_bytes_sent "$http_referer" ' # '"$http_user_agent" "$http_x_forwarded_for"'; #access_log logs/access.log main; sendfile on; tcp_nopush on; tcp_nodelay on; #keepalive_timeout 0; keepalive_timeout 65; #gzip on; server { listen 14555; server_name localhost; autoindex on; client_max_body_size 0; directio 1G; #charset koi8-r; #access_log logs/host.access.log main; location / { root /data/data/com.termux/files/home/storage/downloads; index index.html index.htm; } #error_page 404 /404.html; # redirect server error pages to the static page /50x.html # error_page 500 502 503 504 /50x.html; location = /50x.html { root /data/data/com.termux/files/usr/share/nginx/html; } # proxy the PHP scripts to Apache listening on 127.0.0.1:80 # #location ~ \.php$ { # proxy_pass http://127.0.0.1 ; #} # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 # #location ~ \.php$ { # root html; # fastcgi_pass 127.0.0.1:9000; # fastcgi_index index.php; # fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name; # include fastcgi_params; #} # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # #location ~ /\.ht { # deny all; #} } # another virtual host using mix of IP-, name-, and port-based configuration # #server { # listen 8000; # listen somename:8080; # server_name somename alias another.alias; # location / { # root html; # index index.html index.htm; # } #} # HTTPS server # #server { # listen 443 ssl; # server_name localhost; # ssl_certificate cert.pem; # ssl_certificate_key cert.key; # ssl_session_cache shared:SSL:1m; # ssl_session_timeout 5m; # ssl_ciphers HIGH:!aNULL:!MD5; # ssl_prefer_server_ciphers on; # location / { # root html; # index index.html index.htm; # } #} } Nginx Build nginx version: nginx/1.25.3 built with OpenSSL 3.1.4 24 Oct 2023 TLS SNI support enabled configure arguments: --prefix=/data/data/com.termux/files/usr --crossbuild=Linux:3.16.1:arm --crossfile=/home/builder/.termux-build/nginx/src/auto/cross/Android --with-cc=arm-linux-androideabi-clang --with-cpp=arm-linux-androideabi-cpp --with-cc-opt=' -I/data/data/com.termux/files/usr/include -DIOV_MAX=1024 -march=armv7-a -mfpu=neon -mfloat-abi=softfp -mthumb -fstack-protector-strong -Oz' --with-ld-opt='-L/data/data/com.termux/files/usr/lib -Wl,-rpath=/data/data/com.termux/files/usr/lib -march=armv7-a -fopenmp -static-openmp -Wl, --enable-new-dtags -Wl, --as-needed -Wl,-z,relro,-z,now -landroid-glob' --with-threads --sbin-path=/data/data/com.termux/files/usr/bin/nginx --conf-path=/data/data/com.termux/files/usr/etc/nginx/nginx.conf --http-log-path=/data/data/com.termux/files/usr/var/log/nginx/access.log --pid-path=/data/data/com.termux/files/usr/tmp/nginx.pid --lock-path=/data/data/com.termux/files/usr/tmp/nginx.lock --error-log-path=/data/data/com.termux/files/usr/var/log/nginx/error.log --http-client-body-temp-path=/data/data/com.termux/files/usr/var/lib/nginx/client-body --http-proxy-temp-path=/data/data/com.termux/files/usr/var/lib/nginx/proxy --http-fastcgi-temp-path=/data/data/com.termux/files/usr/var/lib/nginx/fastcgi --http-scgi-temp-path=/data/data/com.termux/files/usr/var/lib/nginx/scgi --http-uwsgi-temp-path=/data/data/com.termux/files/usr/var/lib/nginx/uwsgi --with-http_auth_request_module --with-http_ssl_module --with-http_v2_module --with-http_gunzip_module --with-http_sub_module --with-stream --with-stream_ssl_module The system (Samsung A6) has a 32 bit processor.

I have an Amazon Fire TV Stick and a video file. I want to play on loop for a several hours. I have attached the USB to the Firestick using an OTG dongle. I have the Kodi app to play the video on a loop using a playlist set to repeat all. But I want to make sure, while it's playing, it won't turn off on its own due to some timeout or sleep setting even if it plays for like 6 hours straight. Does anyone know if it would happen and what settings to change to prevent this?

I am using the current latest Kodi version, which is [official website](https://kodi.tv/) But I don't know how to enable touch gestures to control playback, and I didn't find the relevant user manual on the official website. I only found [this](https://github.com/xbmc/xbmc/blob/Nexus/system/keymaps/touchscreen.xml) , but it doesn't seem to help me. The device I'm using is an Android tablet, not a TV. What I want is simple, like other players: 1. Double tap to control pause/play 2. Drag left/right to control playback progress. 3. Double tap left/right to go forward/backward for 10 seconds. 4. etc. How should I set it up?

**tl;dr** _How to prevent Kodi from continuing playback when you press Exit button on remote controller?_ ---- When you're playing a video file in any Android TV player that I have tested so far (about dozens) when you press Exit button on remote controller, your player **stops playback**. This is as obvious as it can be. "Exit" means "Stop". Someone at Kodi's development team doesn't understand that and figured out that it will be so cool to **continue playback** when in Kodi 19.3 user presses Exit button. Kodi truly exits to the menu, but continues to play current movie in the background in something that I call a "mini-player". This is as stupid as it can be, because usually I need to browse 5-6 menu screens until I get back to the home screen when I can turn this damn thing off. Is there any configuration switch that controls this? Is there any way to disable this stupid behavior? I think I have browsed each and every configuration section in _Expert_ mode and found nothing. So I just want to get myself confirmed that I must learn myself to live with this.

**tl;dr** *How to change a Samba source in Kodi that has become invalid, to make it valid again?* ---- I am using Kodi 19.3 Matrix on board Android 11. My entire library is based on a single SMB source in my home network (a NAS drive). I have updated my NAS' disk. The new one has a different label and thus network path pointing to it has changed a little bit. How can I edit (or delete) that single source in my Kodi? No matter where I go (library, settings), no matter what I choose, Kodi is shooting me with errors messages that path is invalid or playing given item has failed. But offers me know way to edit that source.

**tl;dr**: After 2+ months of using my Kodi 18.1 started to get a complete wako, by playing different movie than description, image, scoring etc. says. For example, it plays "The Hunt for the Red October" when I select "Zootopia". Tried everything (rebuilding library, removing and adding the source), all for nothing. ---- My SMB/FTP server structure: - Movies: - Animated - Drama - Political - ... I have added two sources to my Kodi 18.1: - "Animated" --> SMB/Movies/Animated, - "Movies" --> SMB/Movies. So, in fact, all animated movies can be listed / accessible through both sources (if that matters). Now, in Kodi I am selecting first source ("Animated") and browse to the end of list ("Zootopia"). I see everything perfectly: description, movie poster, ratings, year, actors everything is correct. The only problem is that when I start playing it, "The Hunt for the Red October" plays. This problem occurs for most of the database entries in the "Animated" source (but not for all). For example "Jason Bourne" places when "Shrek" is excepted etc. "Animated" folder in SMB/FTP is accessible both through "Animated" and "Movies" source in Kodi, but not the otherwise. I.e., if you open up the "Animated" source in Kodi, no movies from i.e. "Drama", "Political", "Action" etc. folders in SMB/FTP are accessible AFAIK. And yet, Kodi gets wako and plays movies from different source than use is actually browsing. Filenames are "purified" manually by me and files are named matching patterns "English title (Year)" exactly. So there is no way Kodi can get confused: - it claims that it is going to play _movie_ "Zootopia (2006)" in "Animated", - it actually plays _file_ SMB/Political/The Hunt for the Red October (1992).mp4. I have tried everything that came to my mind. I have cleared the database (but this seems to be only deleting references to non-existing files, it does not recreate / verify references to existing files). I have removed "Animated" source and added it again. I have used "Look for a new content"-like options. All for nothing. I have noticed that after removing the source and adding it back, Kodi still keeps information on what was watch and upon which time watching of given movie stop, i.e. still offers to "restart" watching from given position. So, it clearly suggests that removing and adding the same source again does not clear any cache or stuff like this. Any idea what I can do in this situation except for throwing Kodi to hell and start looking for some alternative player for my Android-TV home player?

I sometimes stream video using the Kodi app for my android Note 4. I will be traveling on a plane and would like to know if there is a way to capture and record a few movies and view them later. Does anyone know of such an App?