Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to run Elementum on Android 10 #669

Closed
Wampukas opened this issue Jan 2, 2021 · 253 comments
Closed

Not able to run Elementum on Android 10 #669

Wampukas opened this issue Jan 2, 2021 · 253 comments

Comments

@Wampukas
Copy link

Wampukas commented Jan 2, 2021

Expected Behavior

Just install Elementum plugin. It works for Firestick 4K, Windows 10 PC but not for new Google Chromecast with Google TV

Current Behavior

Cannot install from ZIP file Elementum repository. It tires to install and run after installation but getting an error with permissions.

Possible Solution

Steps to Reproduce (for bugs)

  1. Install Kodi
  2. Install Elementum from ZIP (I have tried all in one or a separate arm package for android)

Context

Your Environment

  • Version used: Google Chromecast with Google TV
  • Environment name and version: tried with plugin.video.elementum-0.1.64.zip and plugin.video.elementum-0.1.62.zip
  • Operating System and version: Android TV 10 + Kodi Matrix
@elgatito
Copy link
Owner

elgatito commented Jan 3, 2021

@Wampukas

2021-01-02 23:39:38.634 T:10415   ERROR <general>: [Errno 13] Permission denied: '/data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm/elementum'

Have no idea. I have no android and no chromecasts to test.
You can try to manually start the binary somehow.

@Wampukas
Copy link
Author

Wampukas commented Jan 3, 2021

@Wampukas

2021-01-02 23:39:38.634 T:10415   ERROR <general>: [Errno 13] Permission denied: '/data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm/elementum'

Have no idea. I have no android and no chromecasts to test.
You can try to manually start the binary somehow.

@elgatito
No such directory '/data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm/elementum' There is only '/data/data/org.xbmc.kodi/files/.kodi...'

As I understand it does not installs correctly

@elgatito
Copy link
Owner

elgatito commented Jan 3, 2021

@Wampukas you may have specific Kodi home directory. Try to find where you have Kodi plugins directory, and Elementum directory.

@Wampukas
Copy link
Author

Wampukas commented Jan 3, 2021

@Wampukas you may have specific Kodi home directory. Try to find where you have Kodi plugins directory, and Elementum directory.

@elgatito

If I compare directories on firestick 4k and chromecast devices, I can see all the same path:
/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.elementum/...

I adding compared log from Amazon Firestick 4k: http://paste.kodi.tv/garusewapa
Original from Google chromecast with TV: http://paste.kodi.tv/reditalije

The installation is not customized at all. Only Simple IPTV addon and Elementum. I believe everyone will face with this issue using that device.

@elgatito
Copy link
Owner

elgatito commented Jan 3, 2021

Have you installed Elementum from the big archivewith all architectures?

@Wampukas
Copy link
Author

Wampukas commented Jan 3, 2021

Have you installed Elementum from the big archivewith all architectures?

@elgatito
Yes, from the biggest. I also have tried from arm and arm 64 as well. It is the same. I believe the issue is somewhere here:

2021-01-02 23:39:38.564 T:10415 WARNING : [plugin.video.elementum] elementumd: start args: ['/data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm/elementum'], kw: {'stdout': -1, 'stderr': -2, 'cwd': '/data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm', 'env': {'PATH': '/sbin:/system/sbin:/product/bin:/apex/com.android.runtime/bin:/system/bin:/system/xbin:/odm/bin:/vendor/bin:/vendor/xbin', 'ANDROID_BOOTLOGO': '1', 'ANDROID_ROOT': '/system', 'ANDROID_ASSETS': '/system/app', 'ANDROID_DATA': '/data', 'ANDROID_STORAGE': '/storage', 'ANDROID_RUNTIME_ROOT': '/apex/com.android.runtime', 'ANDROID_TZDATA_ROOT': '/apex/com.android.tzdata', 'EXTERNAL_STORAGE': '/sdcard', 'ASEC_MOUNTPOINT': '/mnt/asec', 'BOOTCLASSPATH': '/apex/com.android.runtime/javalib/core-oj.jar:/apex/com.android.runtime/javalib/core-libart.jar:/apex/com.android.runtime/javalib/okhttp.jar:/apex/com.android.runtime/javalib/bouncycastle.jar:/apex/com.android.runtime/javalib/apache-xml.jar:/system/framework/framework.jar:/system/framework/ext.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/android.test.base.jar:/apex/com.android.conscrypt/javalib/conscrypt.jar:/apex/com.android.media/javalib/updatable-media.jar', 'DEX2OATBOOTCLASSPATH': '/apex/com.android.runtime/javalib/core-oj.jar:/apex/com.android.runtime/javalib/core-libart.jar:/apex/com.android.runtime/javalib/okhttp.jar:/apex/com.android.runtime/javalib/bouncycastle.jar:/apex/com.android.runtime/javalib/apache-xml.jar:/system/framework/framework.jar:/system/framework/ext.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/android.test.base.jar', 'SYSTEMSERVERCLASSPATH': '/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar:/system/framework/com.android.location.provider.jar', 'DOWNLOAD_CACHE': '/data/cache', 'ANDROID_SOCKET_zygote': '14', 'ANDROID_SOCKET_usap_pool_primary': '15', 'KODI_ANDROID_SYSTEM_LIBS': '/system/lib:/product/lib', 'KODI_ANDROID_LIBS': '/data/app/org.xbmc.kodi-runCNYq7yBXdi5nAvYzPDQ==/lib/arm', 'KODI_ANDROID_APK': '/data/app/org.xbmc.kodi-runCNYq7yBXdi5nAvYzPDQ==/base.apk', 'KODI_BIN_HOME': '/data/user/0/org.xbmc.kodi/cache/apk/assets', 'KODI_HOME': '/data/user/0/org.xbmc.kodi/cache/apk/assets', 'KODI_BINADDON_PATH': '/data/user/0/org.xbmc.kodi/cache/lib', 'HOME': '/storage/emulated/0/Android/data/org.xbmc.kodi/files', 'PYTHONHOME': '/data/user/0/org.xbmc.kodi/cache/apk/assets/python3.8', 'PYTHONPATH': '', 'PYTHONOPTIMIZE': '1', 'PYTHONNOUSERSITE': '1', 'SSL_CERT_FILE': '/data/user/0/org.xbmc.kodi/cache/apk/assets/system/certs/cacert.pem', 'OS': 'Linux', 'LC_CTYPE': 'C.UTF-8', 'LD_LIBRARY_PATH': '/data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm:', 'GODEBUG': 'madvdontneed=1'}, 'close_fds': True}
2021-01-02 23:39:38.609 T:10415 ERROR : Exception in thread
`

@elgatito
Copy link
Owner

elgatito commented Jan 3, 2021

Again, you need to find the directory which contains Kodi plugins. If it is the same - try to run the binary manually.

@Wampukas
Copy link
Author

Wampukas commented Jan 3, 2021

Again, you need to find the directory which contains Kodi plugins. If it is the same - try to run the binary manually.
@elgatito

When I am trying to disable and reenable Elementum addon, it is showing error popup, that something wrong with permissions. How to run manually on android ? This device is not rooted.

I have found relative info here: #237

@elgatito
Copy link
Owner

elgatito commented Jan 4, 2021

@Wampukas I'm comparing your paths from log files and they are equal for both Chromecast and Fire.

It can be something with execute permissions on Android 10.
Or maybe binary has to be compiled in a different way.

It's hard to guess, because I have no android device like that to test.

Try to run console on Chromecast device, and open that directory /data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm/ and run the elementum binary.
Also good if you copy-paste output for running:
ls -la * in that directory.

@Wampukas
Copy link
Author

Wampukas commented Jan 4, 2021

@Wampukas I'm comparing your paths from log files and they are equal for both Chromecast and Fire.

It can be something with execute permissions on Android 10.
Or maybe binary has to be compiled in a different way.

It's hard to guess, because I have no android device like that to test.

Try to run console on Chromecast device, and open that directory /data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm/ and run the elementum binary.
Also good if you copy-paste output for running:
ls -la * in that directory.

@elgatito

Here is the permission output log: https://paste.kodi.tv/duxalasijo.kodi
Here is an error trying to run elementum: https://paste.kodi.tv/fukirutizo.kodi

What I can see more:

2021-01-04 23:04:19.152 T:9984 ERROR : [Errno 13] Permission denied: /data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm/elementum'

2021-01-04 23:04:23.649 T:9951 INFO : CPythonInvoker(2, /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/service.xbmc.versioncheck/resources/lib/runner.py): script successfully run

How can I help more?

If It would help I can archive and share FireTV and Google chromecast all content from the storage. I backuped by using adbLink

@elgatito
Copy link
Owner

elgatito commented Jan 5, 2021

@Wampukas okay, so you jsut run adb commands from your device.
Then, please, run and share what it shows for these commands:

ls -la /
ls -la /data/
ls -la /data/data/
ls -la /data/data/org.xbmc.kodi/
ls -la /data/data/org.xbmc.kodi/files/
ls -la /data/data/org.xbmc.kodi/files/plugin.video.elementum/bin/android_arm/
ls -la /storage/
ls -la /storage/emulated/
ls -la /storage/emulated/0/
ls -la /storage/emulated/0/Android/
ls -la /storage/emulated/0/Android/data/
ls -la /storage/emulated/0/Android/data/org.xbmc.kodi/
ls -la /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.elementum/resources/bin/android_arm

@Wampukas
Copy link
Author

Wampukas commented Jan 5, 2021

@elgatito
Copy link
Owner

elgatito commented Jan 5, 2021

@Wampukas Thanks.

Can you also show output for this one:

ls -la /data/user/
ls -la /data/user/0/
ls -la /data/user/0/org.xbmc.kodi/
ls -la /data/user/0/org.xbmc.kodi/cache/apk/assets/
ls -la data/user/0/org.xbmc.kodi/cache/apk/assets/addons/
ls -la /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/userdata/
ls -la /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/userdata/plugin.video.elementum/resources/bin/android_arm

@Wampukas
Copy link
Author

Wampukas commented Jan 5, 2021

@elgatito
Copy link
Owner

elgatito commented Jan 5, 2021

@Wampukas And these, please:

ls -la /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/plugin.video.elementum/resources/bin/android_arm
ls -la /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/plugin.video.elementum/
ls -la /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/

@Wampukas
Copy link
Author

Wampukas commented Jan 5, 2021

@elgatito

Here you are: https://paste.kodi.tv/osifedisuc.kodi

If I understand correctly, elementum cannot be installed in standard location ?

@elgatito
Copy link
Owner

elgatito commented Jan 6, 2021

@Wampukas Can you try to replace daemon.py file, attached here, over the one that is inside of your Kodi:
addons/plugin.video.elementum/resources/site-packages/elementum/daemon.py
daemon.py.zip

@jakearchibald
Copy link

I still get:

2021-01-06 16:24:35.504 T:7469    ERROR <general>: PermissionError
2021-01-06 16:24:35.504 T:7469    ERROR <general>: :
2021-01-06 16:24:35.504 T:7469    ERROR <general>: [Errno 13] Permission denied: '/storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/userdata/plugin.video.elementum/bin/android_arm/elementum'
2021-01-06 16:24:35.504 T:7469    ERROR <general>:

@Wampukas
Copy link
Author

Wampukas commented Jan 6, 2021

@elgatito

I replaced. It seems the situation is the same. Elementum canot start
image

If it would be easier, I could forward port outside, that you could connect from your home to Google Chromecast directly. I could write domain name and external tcp port in pm
Also, maybe teamviewer on google device.

@elgatito
Copy link
Owner

elgatito commented Jan 7, 2021

@Wampukas Sad to say, but I don't have more ideas.
There are people who run on Android 10, so it is probably not the Android 10 changes, but Chromecast specific security or file storage.
Maybe someone with chromecast will be able to play with this issue and find the proper way of running executable on that device.

@antonsoroko do you use Android > 10 with Elementum?

@Wampukas
Copy link
Author

Wampukas commented Jan 7, 2021

@elgatito
Copy link
Owner

elgatito commented Jan 7, 2021

@Wampukas No, its not related.

@Wampukas
Copy link
Author

Wampukas commented Jan 7, 2021

@elgatito
I have done one more test, via adb did backup amazon Firestick 4k sdcard and then restored to google chromecast. The situation is the same, permission error. Just interesting, when I restored data I saw that for example other apk software was still installed and working such like Spotify, IPTV or other. These software were not on Amazon Fire TV stick. So from that google chromecast somehow is dividing storage for applications maybe. Something bullshit...

Update: Also have tried to use usb hub and attached usb stick, moved kodi application (using chromecast feature) to usb stick. The permission error still persists.

Update2: The issue is with kodi 19. I have installed Kodi 18.9 from google play store and Elementum installed perfectly and it works. After that updated from apk to kodi 19 and the situation is the same. Permission error. So where could be the problem?

Update3: I have installed kodi and elementum on google phone with Android 10. The problem is the same. Can you help to rise a case on main kodi github?

@elgatito
Copy link
Owner

elgatito commented Jan 8, 2021

@Wampukas It is not a Kodi bug, because Kodi works fine.
When you run application on Android, it gives you emulated path, with does not have execute permissions, only read/write. That is why Elementum is ablt to copy the binary, but not run it.
There is a logic of using "/data/data/orm.xbmc.kodi", or something like that, for getting real path, where Kodi stores files.
Since you run Kodi, and Kodi then runs Elementum - starter of a binary is a valid user, that runs Kodi, so all files of Kodi are readable to it.

And it works fine usually. But probably something has been changed.
If you say on same device Kodi 18 is working fine, and Kodi 19 is not, then it can be a change in permissions of Kodi or other changes.

Again, you need a device to see it.
You cannot run from adb, in the same way Kodi runs, because you are a different user there. This needs making changes to elementum python scripts to see where it can change files, and where not.

@Wampukas
Copy link
Author

Wampukas commented Jan 8, 2021

@elgatito
I have replicated that issue on my mobile phone with Android 10. So using Android 10 with kodi 18+elementum is ok, but on android 10 kodi 19 - elementum does not work. So the issue is not the Android 10. The difference is only Kodi 18 and 19 versions on the same device.

@Wampukas
Copy link
Author

Any other confirmation regarding Android 10 is?

@serkud
Copy link

serkud commented Feb 22, 2021

Any other confirmation regarding Android 10 is?

Yes, I have the same issue with 19 on Android 10 after clean install.

@thedamn316
Copy link

thedamn316 commented Feb 23, 2021

I have the same issue as well on Kodi 19, but on Kodi 18.9 + Android 10 + Elementum no issues at all. I tired to run the binary, but I still get Access denied.

@elgatito
Copy link
Owner

@thedamn316 @serkud @Wampukas
As I've said before, only person with a problem can try to find the solution for this problem.

What to do:

  1. Start Kodi.
  2. Open daemon.py file at: /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.elementum/resources/site-packages/elementum/daemon.py (https://github.com/elgatito/plugin.video.elementum/blob/master/resources/site-packages/elementum/daemon.py#L80)
  3. Try to play with xbmc_data_path or dest_binary_dir variables to find the directory, which allows Kodi to start the binary.

xbmc_data_path - Kodi's Userdata directory (https://kodi.wiki/view/Kodi_data_folder#Location)
dest_binary_dir - The directory which contains elementum binary for this platform.

The problem is that Android uses links to directories that do not have execute permissions.
The task is to find path to Elementum binary, which allows execution.

@notgood
Copy link

notgood commented Feb 24, 2021

Don't want to be the bearer of bad news, and hope I'm wrong, but perhaps this problem can't be solved easily, if at all.

Kodi 19, at least google play version is targeting SDK29, and as a consequence:

Quoting https://developer.android.com/about/versions/10/behavior-changes-10
Untrusted apps that target Android 10 cannot invoke exec() on files within the app's home directory. This execution of files from the writable app home directory is a W^X violation. Apps should load only the binary code that's embedded within an app's APK file.

@elgatito
Copy link
Owner

elgatito commented Jul 1, 2023

@killwarez Try to use v0.1.88 everywhere. There are changes that allow properly using multiple Kodi's with one Elementum binary, that can be started anywhere.
I will try to find some time and create a doc that lists how to make multi-Kodi setup.

@killwarez
Copy link

@elgatito , cannot find 0.1.88 nor in releases neither on homepage. Could you post a link?

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

Had issues with release process. Should be available now.

@killwarez
Copy link

It is. Going to check later today. Thank you.

@ShlomiD83
Copy link

Anyone running Elementum in docker and found a way to stop the daemon spamming the logs when kodi is closed?
It constantly trying to connect to the remote host.
Is there a way to "put it to sleep" until the remote host is active and will send a request to connect to the daemon?
@elgatito your thoughts?

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

@ShlomiD83

Anyone running Elementum in docker and found a way to stop the daemon spamming the logs when kodi is closed?

What messages?

@ShlomiD83
Copy link

@ShlomiD83

Anyone running Elementum in docker and found a way to stop the daemon spamming the logs when kodi is closed?

What messages?

@elgatito
2023-07-03T16:19:23.465426129Z INFO main ▶ main Starting Elementum daemon
2023-07-03T16:19:23.465520072Z INFO main ▶ main Version: 0.1.89 LibTorrent: 1.1.14.0 Go: go1.19.4, Threads: 4
2023-07-03T16:19:23.466325186Z INFO config ▶ Reload Reloading configuration...
2023-07-03T16:19:23.466471923Z INFO config ▶ Reload Setting remote address to 192.168.2.101:65221
2023-07-03T16:19:23.481654843Z ERRO xbmc ▶ executeJSONRPCEx dial tcp 192.168.2.101:65221: connect: connection refused
2023-07-03T16:19:23.481786322Z CRIT xbmc ▶ executeJSONRPCEx No available JSON-RPC connection to the add-on
2023-07-03T16:19:23.481808655Z WARN config ▶ fetchConfiguration Can't continue because addon info is empty
2023-07-03T16:19:23.481892338Z WARN config ▶ Reload Could not get configurations: Could not get addon information from Kodi
2023-07-03T16:19:23.482131463Z ERRO main ▶ main Could not get addon configuration: Could not get addon information from Kodi

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

@ShlomiD83 To know settings Elementum needs either a running Kodi, that would return settings, or starting with local config, then Kodi is not required for that.
You cannot ignore missing Kodi if Kodi is required to work.

@ShlomiD83
Copy link

@ShlomiD83 To know settings Elementum needs either a running Kodi, that would return settings, or starting with local config, then Kodi is not required for that. You cannot ignore missing Kodi if Kodi is required to work.

where inside the container should the settings.xml file be located?
I want to map it from my host.

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

where inside the container should the settings.xml file be located?

It is little easier (as for me) with >= 0.1.89.

Run elementum with -exportConfig=/path/to/file.yml and it will connect to Kodi, read setting and save them to that file location.
Then when you start elementum with -configPath=/path/to/file.yml - it will read setting from there, even if Kodi will be available.
Of couse make sure you enabled an option in Kodi to not start a binary from Kodi.

@ShlomiD83
Copy link

ShlomiD83 commented Jul 3, 2023

where inside the container should the settings.xml file be located?

It is little easier (as for me) with >= 0.1.89.

Run elementum with -exportConfig=/path/to/file.yml and it will connect to Kodi, read setting and save them to that file location. Then when you start elementum with -configPath=/path/to/file.yml - it will read setting from there, even if Kodi will be available. Of couse make sure you enabled an option in Kodi to not start a binary from Kodi.

that's a command? env variable? volume?
I'm using docker compose it it'll help.

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

that's a command? env variable? volume?

Command line variable.
You can run elementum -h to see all the options. There are few new options added.

@ShlomiD83
Copy link

services:
elementum:
image: shlomid/elementum:latest
container_name: elementum
environment:
- TZ=Asia/Jerusalem
- ELEMENTUM_NEW_PATH=/storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.elementum
network_mode: "host"
cap_add:
- NET_ADMIN
- SYS_MODULE
volumes:
- /wdred/Config/Elementum:/storage/emulated/0/Download/tmp
ports:
- 65220:65220
command:
- elementum
- -localHost=192.168.2.130
- -remoteHost=192.168.2.101
restart: unless-stopped
labels:
- 'com.centurylinklabs.watchtower.enable=false'

that's my stack. how should I proceed?

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

@ShlomiD83

command:
- elementum
 -localHost=192.168.2.130
 -remoteHost=192.168.2.101
 -configFile=/path/fo/file.yml

Generate config file, add to the the docker runtime, and import on startup. And you will probably not need localHost and remoteHost. Unless you want to connect from outside - you can set localHost=0.0.0.0.

@ShlomiD83
Copy link

the configfile path should be on the host or inside the container?

@ShlomiD83
Copy link

ShlomiD83 commented Jul 3, 2023

I have a settings.yml file from another machine and i've added the command -configPath but I get this error:

2023-07-03T17:02:21.339456790Z INFO config ▶ importConfig Importing configuration from a file at: /wdred/Config/Elementum/settings.yml
2023-07-03T17:02:21.339705636Z WARN config ▶ Reload Could not get configurations: open /wdred/Config/Elementum/settings.yml: no such file or directory
2023-07-03T17:02:21.339853356Z ERRO main ▶ main Could not get addon configuration: open /wdred/Config/Elementum/settings.yml: no such file or directory

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

@ShlomiD83

the configfile path should be on the host or inside the container?

Any. If it is on the host - then proxied to a container.
For import/export elementum supports yaml/json files. And that is not the same as Kodi's settings.xml files.

@ShlomiD83
Copy link

@ShlomiD83

the configfile path should be on the host or inside the container?

Any. If it is on the host - then proxied to a container. For import/export elementum supports yaml/json files. And that is not the same as Kodi's settings.xml files.

it's written different? I wasn't able to export..I'll try again.

@ShlomiD83
Copy link

ShlomiD83 commented Jul 3, 2023

root@openmediavault:/# elementum -exportConfig=/storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/plugin.video.elementum/settings.yml
INFO main ▶ main Starting Elementum daemon
INFO main ▶ main Version: 0.1.89 LibTorrent: 1.1.14.0 Go: go1.19.4, Threads: 4
INFO config ▶ Reload Reloading configuration...
WARN config ▶ Reload Could not get configurations: Could not get addon information from Kodi due to missing connection to Kodi
ERRO main ▶ main Could not get addon configuration: Could not get addon information from Kodi due to missing

what am I doing wrong?

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

@ShlomiD83

WARN config ▶ Reload Could not get configurations: Could not get addon information from Kodi due to missing connection to Kodi

When you want to export setting - you need to take them somewhere, so connect properly to Kodi. You can start with remoteHost pointing to Kodi IP.

@ShlomiD83
Copy link

@ShlomiD83

WARN config ▶ Reload Could not get configurations: Could not get addon information from Kodi due to missing connection to Kodi

When you want to export setting - you need to take them somewhere, so connect properly to Kodi. You can start with remoteHost pointing to Kodi IP.

I'm connected to Kodi, the addon on the remote host is working.
but I'm not able to export the settings.
I can't just create the settings.yml manually?

@elgatito
Copy link
Owner

elgatito commented Jul 3, 2023

@ShlomiD83

elementum -exportConfig=/storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/plugin.video.elementum/settings.yml

You are connecting to localhost Kodi.

@ShlomiD83
Copy link

I'm unable to use the export command, it keeps failing.
If I manually create the "settings.yml" file with the configuration from a running Kodi, map it to the container and run it with the command -configPath it should work? I'm getting a new error:

2023-07-03T17:45:17.623053884Z INFO config ▶ importConfig Importing configuration from a file at: /settings/settings.yml
2023-07-03T17:45:17.626648702Z WARN config ▶ Reload Could not get configurations: yaml: unmarshal errors:
2023-07-03T17:45:17.626986881Z line 1: cannot unmarshal !!str <settin... into config.ConfigBundle
2023-07-03T17:45:17.627085453Z ERRO main ▶ main Could not get addon configuration: yaml: unmarshal errors:
2023-07-03T17:45:17.627157266Z line 1: cannot unmarshal !!str <settin... into config.ConfigBundle

@elgatito
Copy link
Owner

elgatito commented Jul 4, 2023

@ShlomiD83

If I manually create the "settings.yml" file with the configuration from a running Kodi, map it to the container and run it with the command -configPath it should work? I'm getting a new error:

As I was saying, Kodi's settings.xml is a different format, don't try to use that file anywhere.

Since you have this mount

  • /wdred/Config/Elementum:/storage/emulated/0/Download/tmp

Then you should probably export config into a file on that mount, and then read it on startup.

command:
 elementum
 -localHost=192.168.2.130
 -remoteHost=192.168.2.101
 -exportConfig=/storage/emulated/0/Download/tmp/elementum-config.yml

Then use it:

command:
 elementum
 -localHost=192.168.2.130
 -remoteHost=192.168.2.101
 -configPath=/storage/emulated/0/Download/tmp/elementum-config.yml

@ShlomiD83
Copy link

ShlomiD83 commented Jul 4, 2023

@elgatito I'll try that.

@ShlomiD83
Copy link

@elgatito I think I've managed to export the config and run Elementum from the exported config file.
thanks again.

@elgatito
Copy link
Owner

elgatito commented Jul 7, 2023

@Wampukas Can you verify if this issue is fixed or no. I feel we need to close it finally.

@Wampukas
Copy link
Author

Wampukas commented Jul 7, 2023

@elgatito I think we can close.

@Wampukas Wampukas closed this as completed Jul 7, 2023
@mochoandre
Copy link

LT2http still gives permission denied error 13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests