Fehler/Probleme mit Kodi in oATV 7.4

[Oetty]

Hallo zusammen,

7.5 läuft bei mir alles (VU+ Uno 4K SE und VU+ Zero 4K)

kurze Frage bzgl KODI:

unter 7.4 läuft Kodi 21 Omega gut
auf dem Feed ist Kodi (noch) nicht für 7.5 (VU+ Uno 4K SE) verfügbar ?

ist abzusehen wann das kommt ?

sonst muss ich wieder auf 7.4 zurück

Danke vorab

[Gelöschter Benutzer 150133]

https://www.opena.tv/viewtopic.php?p=566965#p566965

7.5 test Build Image, wo noch features und viele viele Updates fehlen, beta kommt in November

[Tzt]

Übrigens ist heute Kodi 21.1 released worden. Vielleicht nimmt man diese Version dann für 7.5

[listener]

Ich benutze hier branche Omega auf 7.5.
Weis nicht warum oe-a branch master benutzt der
branche braucht viel anpassungen om die stb patches
zum laufen zu bringen.
Omega functioniert prima auf 7.5.
Bin dabei de kodi player ausgang um zu leiten nach stb video/audo output.
Ist viel arbeid wen ich es schaffe mit meine zeit waere es schoen.

[Papi2000]

Übrigens ist heute Kodi 21.1 released worden. Vielleicht nimmt man diese Version dann für 7.5

Ich benutze hier branche Omega auf 7.5.
Weis nicht warum oe-a branch master benutzt der
branche braucht viel anpassungen om die stb patches
zum laufen zu bringen.
Omega functioniert prima auf 7.5.
Bin dabei de kodi player ausgang um zu leiten nach stb video/audo output.
Ist viel arbeid wen ich es schaffe mit meine zeit waere es schoen.

Dann hat er aber doch mit v21.0 nicht das NEUESTE vom NEUESTEN. Geht ja garnicht . . .
Nur, - was wenn bis November oder Dezember dann mal Kodi in v21.1 dazugebaut würde, bis dann aber vielleicht v21.1.032 rauskommt?

[gabywap]

Hallo, mir ist ein Fehler aufgefallen, das aktuelle Image startet KODI weder in 7.4 noch in 7.5, nur openatv 7.3, was immer noch gut ist.

Hello, I noticed an error, the current image doesn't start KODI in either 7.4 or 7.5, only openatv 7.3, which is still good.

[Papi2000]

You are talking about oATV7.3, oATV7.4 and oATV7.5.
How do you ensure, that the images get their needed unique Kodi on your attached datadrive?
Remember: all images use /media/hdd/.kodi for the content...

[gabywap]

You are talking about oATV7.3, oATV7.4 and oATV7.5.
How do you ensure, that the images get their needed unique Kodi on your attached datadrive?
Remember: all images use /media/hdd/.kodi for the content...

Was ich bisher beobachtet habe, war /home/root/.kodi/ in 7.3, das neue Image 7.4 würde hier nicht suchen. Jede Hisilicon-Box war gut, nur der neue KODI 21 ist das Problem, er ist bereits hier /media/hdd/.kodi/
Welches Box-Image auch immer funktionierte fast perfekt, aber mit Python 3.12 KODI 21 traten Probleme auf.

So far, what I observed was /home/root/.kodi/ in 7.3, the new image 7.4 would not search here. Any hisilicon box was good, only the new KODI 21 is the problem, it's already here /media/hdd/.kodi/
Whatever box image worked almost perfectly, but Python 3.12 KODI 21 problems came up.

Tut mir leid, ich benutze einen Übersetzer, sonst würde ich auf Ungarisch schreiben.
Sorry, I'm using a translator, otherwise I would write in Hungarian.

[sajid727]

You are talking about oATV7.3, oATV7.4 and oATV7.5.
How do you ensure, that the images get their needed unique Kodi on your attached datadrive?
Remember: all images use /media/hdd/.kodi for the content...

Was ich bisher beobachtet habe, war /home/root/.kodi/ in 7.3, das neue Image 7.4 würde hier nicht suchen. Jede Hisilicon-Box war gut, nur der neue KODI 21 ist das Problem, er ist bereits hier /media/hdd/.kodi/
Welches Box-Image auch immer funktionierte fast perfekt, aber mit Python 3.12 KODI 21 traten Probleme auf.

So far, what I observed was /home/root/.kodi/ in 7.3, the new image 7.4 would not search here. Any hisilicon box was good, only the new KODI 21 is the problem, it's already here /media/hdd/.kodi/
Whatever box image worked almost perfectly, but Python 3.12 KODI 21 problems came up.

Tut mir leid, ich benutze einen Übersetzer, sonst würde ich auf Ungarisch schreiben.
Sorry, I'm using a translator, otherwise I would write in Hungarian.

Hi Papi

You're correct that with oATV versions 7.3, 7.4, and 7.5, Kodi’s path handling has changed, especially with the introduction of Kodi 21. The issue with Python 3.12 compatibility is also a known challenge.

To ensure each image gets its unique Kodi setup on the attached data drive, you can manually set the path for Kodi’s configuration files by modifying the advancedsettings.xml file in each image. This way, you can specify a different path for each version, avoiding conflicts.

For example, you can set the Kodi data folder to something like /media/hdd/.kodi7.3/ for oATV 7.3, /media/hdd/.kodi7.4/ for 7.4, and so on. This will ensure each image searches the correct directory.

As for the Python 3.12 and Kodi 21 issues, unfortunately, they may require waiting for further updates or patches. Until then, sticking with a compatible Python version or using a different Kodi version might be necessary if the issues are too disruptive.

Best Regards

[Papi2000]

But user must adjust the settings and the pathnames by hand manually.
Have you seen or heard from users, doing that?
There is no GUI for that management. Even not all installations afaik support that.
But Kodi does not belong directly to the image as "usual" plugin.
Therefore it is not well supported. Only in the last few weeks, there comes up little support for it.

[sajid727]

But user must adjust the settings and the pathnames by hand manually.
Have you seen or heard from users, doing that?
There is no GUI for that management. Even not all installations afaik support that.
But Kodi does not belong directly to the image as "usual" plugin.
Therefore it is not well supported. Only in the last few weeks, there comes up little support for it.

You're absolutely right—manually adjusting the settings and pathnames for Kodi across different oATV versions isn't something that’s managed through a GUI, and not all installations support it.

I’ve seen a few users attempt this by manually editing the advancedsettings.xml file, but it's definitely not a straightforward process. It requires a good understanding of the file structure and careful management to avoid conflicts.

For those who are comfortable with manual configurations, it’s a viable solution, but it’s not without its challenges. Unfortunately, until a GUI or more user-friendly method is developed, manual editing is the only option.

If you’re not comfortable with this approach, it might be best to stick with one image or carefully test changes on a separate setup to avoid disrupting your main environment.

[gabywap]

But user must adjust the settings and the pathnames by hand manually.
Have you seen or heard from users, doing that?
There is no GUI for that management. Even not all installations afaik support that.
But Kodi does not belong directly to the image as "usual" plugin.
Therefore it is not well supported. Only in the last few weeks, there comes up little support for it.

You're absolutely right—manually adjusting the settings and pathnames for Kodi across different oATV versions isn't something that’s managed through a GUI, and not all installations support it.

I’ve seen a few users attempt this by manually editing the advancedsettings.xml file, but it's definitely not a straightforward process. It requires a good understanding of the file structure and careful management to avoid conflicts.

For those who are comfortable with manual configurations, it’s a viable solution, but it’s not without its challenges. Unfortunately, until a GUI or more user-friendly method is developed, manual editing is the only option.

If you’re not comfortable with this approach, it might be best to stick with one image or carefully test changes on a separate setup to avoid disrupting your main environment.

Here is the /usr/bin/ initialization files for kodi from 7.3 and 7.4, kodi-standalone is a text file.

[sajid727]

But user must adjust the settings and the pathnames by hand manually.
Have you seen or heard from users, doing that?
There is no GUI for that management. Even not all installations afaik support that.
But Kodi does not belong directly to the image as "usual" plugin.
Therefore it is not well supported. Only in the last few weeks, there comes up little support for it.

You're absolutely right—manually adjusting the settings and pathnames for Kodi across different oATV versions isn't something that’s managed through a GUI, and not all installations support it.

I’ve seen a few users attempt this by manually editing the advancedsettings.xml file, but it's definitely not a straightforward process. It requires a good understanding of the file structure and careful management to avoid conflicts.

For those who are comfortable with manual configurations, it’s a viable solution, but it’s not without its challenges. Unfortunately, until a GUI or more user-friendly method is developed, manual editing is the only option.

If you’re not comfortable with this approach, it might be best to stick with one image or carefully test changes on a separate setup to avoid disrupting your main environment.

Here is the /usr/bin/ initialization files for kodi from 7.3 and 7.4, kodi-standalone is a text file.

To analyze the potential reasons why KODI might be failing to start in the 7.4 version, I have compared the key elements of both initialization scripts, focusing on aspects that could directly influence KODI's startup behavior. The analysis identified several potential issues:

File Path Discrepancies : The kodi script references specific file paths and binaries, such as /usr/lib/${bin_name}/kodi-stb. If these paths have changed or are incorrect in the 7.4 version, the KODI executable might fail to launch.

Environment Variable Conflicts : The script sets multiple environment variables, including __GL_YIELD and MALLOC_MMAP_THRESHOLD_. These settings might conflict with the system's configuration or KODI's requirements in the 7.4 environment, potentially leading to startup failures.

Media Mount Handling : The script includes a function to check and set media mounts like /media/hdd. This affects the HOME directory for KODI's configuration. If this check fails or incorrectly sets the directory, it could cause KODI to fail due to improper file access or configuration issues.

Addressing these areas by verifying paths, simplifying environment variable setups, and ensuring correct media mount handling could help resolve the startup issues in the 7.4 version.

[Muhammad Qaiser]

Thanks for the detailed analysis! Just a quick question: do you think adjusting the environment variables could resolve most of the startup issues, or is the file path discrepancy more likely the root cause?

[DelthaBuegel]

Was soll das dämliche Fullquote, wenn der Beitrag direkt oben drüber steht?

[sajid727]

You're absolutely right—no need for the full quote when the original message is just above . I'll keep it brief next time! Thanks for pointing that out .

[sajid727]

Thanks for the detailed analysis! Just a quick question: do you think adjusting the environment variables could resolve most of the startup issues, or is the file path discrepancy more likely the root cause?

Great question! While adjusting the environment variables might help, I’d lean towards the file path discrepancy being the bigger issue . It’s more likely that KODI isn’t finding what it needs to start properly. But both should be checked to be sure!

[Muhammad Qaiser]

1. If the environment variables are causing conflicts, wouldn't that suggest deeper compatibility issues with the system configuration in 7.4 rather than just a simple path error?

2. If the file path discrepancies are the main issue, why didn’t this cause failures in previous versions.

[hammu]

1. openATV is not the primary environment for KODI. There are other platforms making it more comfortable to handle. You may not expect excellent support because it is no major part for developing in oATV or OE-Alliance.

2. "If the file path discrepancies are the main issue, why didn’t this cause failures in previous versions"
Because previous versions are not current versions. Fo more Details I refer to item 1 in this issue.
You may contact KODI experts from outside oATV but I promise there will never be a quick-and-easy solution coming.

[listener]

Dies ist ein deutscher Teil
Ja, es gibt ein Startproblem im Kodi-Skript
Lösung: Gerätekontrolle im Kodi-Skript entfernen
und setzen Sie die Variable $HOME nach Ihren Wünschen