• 1
  • 3
  • 4
  • 5(current)
  • 6
  • 7
  • 8
v18 Whitelist modes missing?
#61
Well, this didn't work for me.  Same problem as before.  Nothing above 30Hz for 1920x1080 and no resolutions available below 1920x1080.  
I downloaded the file and used X-plore to install it.  I didn't delete/remove anything prior to the install.  
Did I do it right?  
Thanks
Reply
#62
Also tested this build on my setup - same result - no duplicates in the Whitelist - but also nothing above 30Hz for 1080. I do see 720 - also with frequencies from 30 Hz down. When selected Kodi does use 720 for content in that range but in my case the upscaling by the TV (if it does upscale) look horrible. If not selected Kodi selects 1080/24 which looks fine.

Fingers x-ed for a fix  & Thnx for all the effort!
Reply
#63
All those people getting 1080p and 720p resolutions for 30Hz and below only.  Are you running nVidia Shield TV?

If so what is your nVidia Shield TV output format at the Android level?  Mine is 2160p 50Hz 4:2:2 12-bit Rec 2020, and I get all 1080p and 720p modes in my whitelist.

I also make sure that my TV and AVR are in-circuit and powered up and I do a full power cycle of my Shield TV when I install/update Kodi - to ensure EDID for the TV and AVR are read properly by Android at boot up.
Reply
#64
And don't forget your Debug Log ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#65
It has been reported for quite some time now that not all resolutions are "reported" to Kodi when Shield's output is set to one of the 4:2:0 modes. I don't know why it is like that, but it has been this way since Nougat update I think.

Old SPMC topics on this issue: 
https://github.com/koying/SPMC/issues/1060
https://github.com/koying/SPMC/issues/1061
Reply
#66
(2018-07-01, 09:23)wesk05 Wrote: It has been reported for quite some time now that not all resolutions are "reported" to Kodi when Shield's output is set to one of the 4:2:0 modes. I don't know why it is like that, but it has been this way since Nougat update I think.

Old SPMC topics on this issue: 
https://github.com/koying/SPMC/issues/1060
https://github.com/koying/SPMC/issues/1061
 Good. So nothing at all to do for us here. They should fix their broken firmware. The missing DESKTOP res is a kodi bug though.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#67
(2018-07-01, 09:32)fritsch Wrote: Good. So nothing at all to do for us here. They should fix their broken firmware. The missing DESKTOP res is a kodi bug though. 
Yep! the missing DESKTOP resolution is the only thing that needs to be fixed Smile
Reply
#68
Hello,

I am not running on an NVidia Shield and I have the same problem. 
I have the resolution 1080p 60hz and 50hz but not the 24hz like I used to have in kodi 17.6.
I am running on a freebox player mini (french box running on android nougat).

I just try the test apk above, I have a new duplicated line for 1080p 50hz and that's all.. Still nothing for 24hz Sad

What could I do or try ?

Thanks a lot,
BR
Reply
#69
Nothing. Android is unmaintained and bugs are only fixed by volunteers from other subsystems that invest a bit of time to help out. Best bet is: Get your hands dirty and try to fix them.

What about this build (32 bit arm): http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk <- more resolutions available?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#70
And here is the log

Same thing as the alpha2 version, 1080p 24hz resolution is found but nothing in the white list or refresh rate settings Sad
Quote:10:40:15.542 T:18446744072280344864  NOTICE: CAndroidUtils: window resolution: 1920x1080
10:40:15.542 T:18446744072280344864  NOTICE: CAndroidUtils: Current resolution: 1920x1080 1920x1080 @ 50.000000 - Full Screen
10:40:15.542 T:18446744072280344864  NOTICE: Previous line repeats 1 times.
10:40:15.542 T:18446744072280344864  NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 24.000000 Hz
10:40:15.543 T:18446744072280344864  NOTICE: Found resolution 1280 x 720 for display 0 with 1280 x 720 @ 50.000000 Hz
10:40:15.543 T:18446744072280344864  NOTICE: Found resolution 1280 x 720 for display 0 with 1280 x 720 @ 60.000000 Hz
10:40:15.543 T:18446744072280344864  NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 60.000000 Hz
10:40:15.543 T:18446744072280344864  NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 50.000000 Hz
10:40:15.543 T:18446744072280344864  NOTICE: Found ([email protected]) at 20, setting to RES_DESKTOP at 16
Reply
#71
Indeed, the version tested is the 32 bit arm, only new resolution between alpha2 was the duplicated 50hz.

Anyway, why do you think it's an android problem as it was working with the kodi 17.6 ?

Thanks again
Reply
#72
Well, I did try something with your version :

Put my box resolution to 24hz, restart the box, start kodi, and now I can see the whiteList settings for 24hz resolution BUT... still no auto refresh rate adjustment Sad.
Reply
#73
Final idea: http://jenkins.kodi.tv/job/BuildMulti-Android/57/ wait until androidrf-647eb47 androidrf-67c340a  hits the mirrors (see above for the directory, will build for arm and arm64).
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#74
It seems a LE Rockchip developer fixed some whitelist issue with the following patch.
Maybe it can be useful for Android and other platforms too?
Quote:From: Jonas Karlman <jonas@Kwiboo.se>
Date: Sun, 1 Jul 2018 15:15:18 +0200
Subject: [PATCH] Resolution: use desktop screen width in whitelist fallback
xbmc/windowing/Resolution.cpp | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/xbmc/windowing/Resolution.cpp b/xbmc/windowing/Resolution.cpp
index 7d24e0f733..f3e7f646f6 100644
--- a/xbmc/windowing/Resolution.cpp
+++ b/xbmc/windowing/Resolution.cpp
@@ -128,15 +128,15 @@ void CResolutionUtils::FindResolutionFromWhitelist(float fps, int width, bool is

CLog::Log(LOGDEBUG, "No double refresh rate whitelisted resolution matched, trying current resolution");

+ const RESOLUTION_INFO desktop_info = CServiceBroker::GetWinSystem()->GetGfxContext().GetResInfo(CDisplaySettings::GetInstance().GetCurrentResolution());
+
for (const auto &mode : indexList)
{
auto i = CDisplaySettings::GetInstance().GetResFromString(mode.asString());
const RESOLUTION_INFO info = CServiceBroker::GetWinSystem()->GetGfxContext().GetResInfo(i);

- const RESOLUTION_INFO desktop_info = CServiceBroker::GetWinSystem()->GetGfxContext().GetResInfo(CDisplaySettings::GetInstance().GetCurrentResolution());
-
// allow resolutions that are desktop resolution but have the correct refresh rate
- if (info.iScreenWidth == desktop_info.iWidth &&
+ if (info.iScreenWidth == desktop_info.iScreenWidth &&
info.iScreen == desktop_info.iScreen &&
(info.dwFlags & D3DPRESENTFLAG_MODEMASK) == (desktop_info.dwFlags & D3DPRESENTFLAG_MODEMASK) &&
MathUtils::FloatEquals(info.fRefreshRate, fps, 0.01f))
@@ -154,10 +154,8 @@ void CResolutionUtils::FindResolutionFromWhitelist(float fps, int width, bool is
auto i = CDisplaySettings::GetInstance().GetResFromString(mode.asString());
const RESOLUTION_INFO info = CServiceBroker::GetWinSystem()->GetGfxContext().GetResInfo(i);

- const RESOLUTION_INFO desktop_info = CServiceBroker::GetWinSystem()->GetGfxContext().GetResInfo(CDisplaySettings::GetInstance().GetCurrentResolution());
-
// allow resolutions that are desktop resolution but have double the refresh rate
- if (info.iScreenWidth == desktop_info.iWidth &&
+ if (info.iScreenWidth == desktop_info.iScreenWidth &&
info.iScreen == desktop_info.iScreen &&
(info.dwFlags & D3DPRESENTFLAG_MODEMASK) == (desktop_info.dwFlags & D3DPRESENTFLAG_MODEMASK) &&
MathUtils::FloatEquals(info.fRefreshRate, fps * 2, 0.01f))
Reply
#75
Quote:+ if (info.iScreenWidth == desktop_info.iScreenWidth &&

Those make sense - thank you. Without that it would compare apples with pies ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  • 1
  • 3
  • 4
  • 5(current)
  • 6
  • 7
  • 8

Logout Mark Read Team Forum Stats Members Help
Whitelist modes missing?0