You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is a clear and concise description of what the problem is:
Set up a new FTVS4K as a replacement for a 1.Gen Stick, which properly ran - though with less "horse power" with 18.0.x version attached to an "HD Ready only" Samsung TV.
The cloned 4K stick ran properly when still attached to my Teac AG-D500 AVR's AUX port, but when put to the Samsung's HDMI port Amazon works, but Kodi won't start.
(Was a bit confused about that and started a thread in a German forum as my first guess was, that I screwed some configs, eb, by "power cycling the 4k stick.)
Though 17.6 on 4k stick works as well when attached to that TV.
Expected Behavior
Here is a clear and concise description of what was expected to happen:
Kodi should start.
Actual Behavior
18.0 won't start while installed on FTV 4K device
Possible Fix
Either use 17.6 on 4k stick
or use (1. Gen) stick with 18.0.x
To Reproduce
Steps to reproduce the behavior:
Install 18.0 on ATFV 4K still and attach to TV with low resolution 1080i? only
Here are some links or screenshots to help explain the problem:
Additional context or screenshots (if appropriate)
Here is some additional context or explanation that might help:
Your Environment
Used Operating system:
Android
Kodi version: 18.0
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.
The text was updated successfully, but these errors were encountered:
when you attach the FireStick to your TV, is your AVR on or off in this situation? I suppose you are using the ARC to get audio from your TV to the AVR? Reason I'm asking is, that I have the same issue when I try to run KODI natively on my Philips AndroidTV and KODI does only start when the AVR is on. It's somehow related to missing HDMI video device info or something like that.
One is a (Samsung LE40B679) TV, but FullHD with the AVR in my living room, while the HDReady LE37S62B TV where I have the issue is a "stand-alone" one in another room.
Bug report
Describe the bug
Here is a clear and concise description of what the problem is:
Set up a new FTVS4K as a replacement for a 1.Gen Stick, which properly ran - though with less "horse power" with 18.0.x version attached to an "HD Ready only" Samsung TV.
The cloned 4K stick ran properly when still attached to my Teac AG-D500 AVR's AUX port, but when put to the Samsung's HDMI port Amazon works, but Kodi won't start.
(Was a bit confused about that and started a thread in a German forum as my first guess was, that I screwed some configs, eb, by "power cycling the 4k stick.)
Though 17.6 on 4k stick works as well when attached to that TV.
Expected Behavior
Here is a clear and concise description of what was expected to happen:
Kodi should start.
Actual Behavior
18.0 won't start while installed on FTV 4K device
Possible Fix
Either use 17.6 on 4k stick
or use (1. Gen) stick with 18.0.x
To Reproduce
Steps to reproduce the behavior:
Install 18.0 on ATFV 4K still and attach to TV with low resolution 1080i? only
Debuglog
The debuglog can be found here:
Here are some logs:
AFTV 1.Gen stick with Leia attached to "problem" TV working
FTVSw18.0onTV.kodi.log
AFTV 4K stick with Leia attached to Teac AVR working
FTVS4Kw18.0onAVR.kodi.log
AFTV 4K stick with Leia attached to "problem" TV not working
FTVS4Kw18.0onTV.kodi.log
Screenshots
Here are some links or screenshots to help explain the problem:
Additional context or screenshots (if appropriate)
Here is some additional context or explanation that might help:
Your Environment
Used Operating system:
Android
Kodi version: 18.0
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.
The text was updated successfully, but these errors were encountered: