2021-10-06, 03:18
I've been using Amber for a couple of years now and it is hands-down the best Kodi skin out there. Great work and much appreciated!
I do have one issue that I've never been able to figure out. Originally I thought this might've been related to my Windows Kodi instance, or my Harmony remote, but I recently moved to a completely fresh install on a Shield and it's still happening.
What I'm seeing is this: I have pretty much all of my media views set to Icon. I would say a few times a day (usually the first time I enter either my TV or Movies section during that Kodi startup), it will show the expected Icons view, and then switch to List view automatically after about 2-3 seconds. I then need to switch back to Icons where it will usually stick until I close and reopen Kodi.
I've tested out multiple other skins and have not seen a repeat of this behavior, so it is specific to Amber. I even tried renaming the List view from xml to bak, but then it just switches to whatever the next view is.
I can try to isolate this in a log file if need be. Kinda hoping that maybe someone else has run into this and there's a known fix for it.
I do have one issue that I've never been able to figure out. Originally I thought this might've been related to my Windows Kodi instance, or my Harmony remote, but I recently moved to a completely fresh install on a Shield and it's still happening.
What I'm seeing is this: I have pretty much all of my media views set to Icon. I would say a few times a day (usually the first time I enter either my TV or Movies section during that Kodi startup), it will show the expected Icons view, and then switch to List view automatically after about 2-3 seconds. I then need to switch back to Icons where it will usually stick until I close and reopen Kodi.
I've tested out multiple other skins and have not seen a repeat of this behavior, so it is specific to Amber. I even tried renaming the List view from xml to bak, but then it just switches to whatever the next view is.
I can try to isolate this in a log file if need be. Kinda hoping that maybe someone else has run into this and there's a known fix for it.