2016-03-11, 14:57
Nvidia Shield running 16.0 Jarvis and I updated to 2.2.8 thru the EPG Repo and not "Available Updates" and i had no problems or freezes. Updated quick and is back up running smooth.
(2016-03-12, 16:48)ljhookem14 Wrote: Jurial, why is it Everytime I restart KODI my widgets aren't populated? All it takes is for me to fix one widget and then all the widgets seems to begin to work.I've also been experiencing this. Widgets sometimes fail to load after restarting Kodi and the fallback image is displayed instead. Doesn't happen all the time, but happens quite often. Re-setting the widget in the skin settings seems to fix the issue temporarily before it stops displaying again after a while.
On the 2.2.8 Zephyr Update people are seeing:
The 2.2.8 update is coming from the EPG ninja repo and the version is actually 2.2.7 of Arctic Zephyr. He just named it 2.2.8 so people in his clairvoyance build would get an update.
(2016-03-12, 14:59)riccioluca Wrote: Feature request: i also posted it in the ashes mod, the "add to couchpotato" button in the extended info would really be awesome. Check it http://forum.kodi.tv/showthread.php?tid=228970
(2016-03-11, 19:14)baruchin Wrote: I'm still on Kodi 15.2 and today I recieved an update (2.2.8 I think), wich I suppose it's intended for Kodi 16. And I say I suppose, because when it downloaded I got a message telling me that this addon was incompatible with my Kodi setup and if I wanted to disable it. Of course I didn't disabled it but my update is still pending on My Add-ons menu "Updates available". Any suggestions?
I already checked and Artic: Zephyr is still not available on Kodi 16 official repo, so why the update?
(2016-03-12, 16:48)ljhookem14 Wrote: Jurial, why is it Everytime I restart KODI my widgets aren't populated? All it takes is for me to fix one widget and then all the widgets seems to begin to work.
On the 2.2.8 Zephyr Update people are seeing:
The 2.2.8 update is coming from the EPG ninja repo and the version is actually 2.2.7 of Arctic Zephyr. He just named it 2.2.8 so people in his clairvoyance build would get an update.
(2016-03-13, 18:18)baruchin Wrote: Hi jurialmunkey! I just installed skin github version for my recently updated Kodi 16.1 RC on Fire TV 2. Everything is working amazing, but I have noticed a strange behaviour not present in previous skin versions. While a video is playing, bringing OSD controls is kind of slow, I mean, not super slow but still noticeable. Also, while bringing OSD controls there's a micro pause in video that's almost unnoticeable, but it's certainly present. I don't know if this is due to heavier skin animations, or due to Kodi 16 being more cpu resource intensive. In any case, I think Fire TV 2 has enough power to handle both cases, but maybe I'm wrong.
Again, thank you for your wonderful work for this skin.
(2016-03-14, 20:27)jbaconbits Wrote:Really? First time I heard of having a different skin behavior depending of wich method you choose to install it from. But I read you say that this is specifically true with Fire TV? Right? I really hope this is the case, because the video micro pausing I noticed while bringing OSD controls is even more noticeable than I originally thought, and this becomes a big issue for me.(2016-03-13, 18:18)baruchin Wrote: Hi jurialmunkey! I just installed skin github version for my recently updated Kodi 16.1 RC on Fire TV 2. Everything is working amazing, but I have noticed a strange behaviour not present in previous skin versions. While a video is playing, bringing OSD controls is kind of slow, I mean, not super slow but still noticeable. Also, while bringing OSD controls there's a micro pause in video that's almost unnoticeable, but it's certainly present. I don't know if this is due to heavier skin animations, or due to Kodi 16 being more cpu resource intensive. In any case, I think Fire TV 2 has enough power to handle both cases, but maybe I'm wrong.
Again, thank you for your wonderful work for this skin.
Installing skins from a git has always done this on Fire TV, but the official repo version will always work fine. Not sure if it's because of everything being compressed for the repo or not, but it should go away once you get it from the official repo.