Instructions not working for windows 10/11

[CreaGab]

Hi, I had trouble following the instructions from the main page and from the wiki.

The instruction for Windows simply doesn't work.

I had to install WSL and run the commands in ubuntu and then continue the Tizen command on native PowerShell.

I did following:

1. Install Tizen Studio + TV and Cert Add-On on Windows Host machine
2. Create certificate for your TV and connect your TV to your PC.
3. Install and RUN WSL and install + update NodeJS, git and npm
4. Create working directory (example mkdir /mnt/c/Jellyfin/)
5. Run git clone -b release-10.10.z https://github.com/jellyfin/jellyfin-web.git AND git clone https://github.com/jellyfin/jellyfin-tizen.git
6. You should now have 2 directories on your C drive.
7. Now run

cd jellyfin-web
npm ci --no-audit
USE_SYSTEM_FONTS=1 npm run build:production

7. Then run this

cd -
cd jellyfin-tizen
JELLYFIN_WEB_DIR=../jellyfin-web/dist npm ci --no-audit

8. Now you should have a www folder in the directory jellyfin-tizen
9. Now you have to add 2 directories from the Tizen-Studio to your Windows PATH for the next command to work. (INSTRUCTIONS)
   C:\tizen-studio\tools\ide\bin
   C:\tizen-studio\tools
10. With these two directories in PATH, you can now execute tizen commands everywhere without .\tizen prefix.
11. Before entering any new command for tizen please restart your Powershell.
12. Now go to your working directory example (cd C:\Jellyfin\jellyfin-tizen)
13. Enter this command to build package

tizen build-web -e ".*" -e gulpfile.js -e README.md -e "node_modules/*" -e "package*.json" -e "yarn.lock"
tizen package -t wgt -o . -- .buildResult

14. Run the Device Manager and connect your TV using the previous instructions.
    

15. Authorize sideloading apps in the Device Manager by right clicking your model and then selecting "permit to install applications"
    

16. Now you can run this command to transfer the application to your TV
    tizen install -n Jellyfin.wgt

Now you can start Jellyfin from the app-store!

[dmitrylyzo]

What exactly didn't work?
I guess you ran the commands for the command prompt, not PowerShell.

from Wiki
Commands in this guide are for Windows Command Prompt or Batch files. Most of them will work in Windows PowerShell. Special cases will be in collapsible command blocks.

[CreaGab]

What exactly didn't work? I guess you ran the commands for the command prompt, not PowerShell.

from Wiki
Commands in this guide are for Windows Command Prompt or Batch files. Most of them will work in Windows PowerShell. Special cases will be in collapsible command blocks.

I ran all commands from powershell. ^^

[CreaGab]

I added < feature name="http://tizen.org/feature/screen.size.all"/ >to the config.xml file, and did all instructions again, but nothing changed.

[CreaGab]

Is this maybe also needed?

[dmitrylyzo]

I added < feature name="http://tizen.org/feature/screen.size.all"/ >to the config.xml file, and did all instructions again, but nothing changed.

This line is already present.
#315 adds <tizen:metadata key="http://tizen.org/metadata/app_ui_type/base_screen_resolution" value="extensive"/>.

Is this maybe also needed?

At least width=device-width is present: https://github.com/jellyfin/jellyfin-web/blob/2b0f028b6f1c471db16996a36d0d6ee6f23bde57/src/index.html#L5

P.S.: I wonder why you are posting about wide screen problems in this issue. Please post in #231 or #315 (for PR related).

P.S.2: Also, if the PowerShell commands from the Windows guide work, this issue may be closed.

[CreaGab]

I added < feature name="http://tizen.org/feature/screen.size.all"/ >to the config.xml file, and did all instructions again, but nothing changed.

This line is already present. #315 adds <tizen:metadata key="http://tizen.org/metadata/app_ui_type/base_screen_resolution" value="extensive"/>.

Is this maybe also needed?

At least width=device-width is present: https://github.com/jellyfin/jellyfin-web/blob/2b0f028b6f1c471db16996a36d0d6ee6f23bde57/src/index.html#L5

P.S.: I wonder why you are posting about wide screen problems in this issue. Please post in #231 or #315 (for PR related).

P.S.2: Also, if the PowerShell commands from the Windows guide work, this issue may be closed.

Sorry, had #231 and #308 open.