Login at Kodi Home

shidarin · 2012-06-03, 23:40

My Win7, Macbook Pro, Macbook, and AppleTV2 all running Eden, all updated themselves from 2.0 to 3.0. Not a big deal, I just rolled back and it didn't bother me again until 3.0.1 was released.

Then they updated again- I rolled back to 2.0 again.

But now, every time I start up XBMC, within 20 minutes it tries to apply the 3.0.1 update again. I keep having to go back to the Add-on menu, and rolling back manually- especially aggravating since the skin update blacks the ATV2 for 5 minutes, and all the other devices for at least 1 every time it updates.

Every now and then XBMC also starts yelling that the add-on (Aeon Nox 2.0?) has been marked broken in the repository. I keep answering "NO" to that, but it keeps asking just the same.

From searching, I hear about "changing the add-on id" and "changing the skin name" but I can't find a post or a wiki page on that topic, that would allow me to keep Aeon Nox from updating- it doesn't seem to be covered on the Wiki Skinning Page. Perhaps my search-fu is weak.

If someone could point me in the right direction, I'd much appreciate it. I think 3.0 is cool looking, it's just not for me.

Thank you, let me know if I need to post any log files to further describe this behavior.

phil65 · 2012-06-03, 23:44

you have to change skin name / id in addon.xml and name your skin folder accordingly. it won´t auto-update then anymore.

shidarin · 2012-06-03, 23:48

Thank you. I didn't want to start changing items semi-randomly and have it stop working, etc.

Also, I figured since the rollback from 3.0 worked and stuck, but the rollback from 3.0.1 isn't sticking, it might also be a problem with 3.0.1 worth reporting.

phil65 · 2012-06-03, 23:50

(2012-06-03, 23:48)shidarin Wrote: Thank you. I didn't want to start changing items semi-randomly and have it stop working, etc.

Also, I figured since the rollback from 3.0 worked and stuck, but the rollback from 3.0.1 isn't sticking, it might also be a problem with 3.0.1 worth reporting.

no, nothing to do with 3.0.1. must be related to something else, we do not have any influence on updating behaviour.

kelendral · 2012-06-04, 05:03

Experienced the same thing with 3.0.1 as well. I gave up and just replaced /packages/skin.aeon.nox-3.0.1.zip with a 0 byte file and then made the file a hidden read only file. Now it pops up the error about failing to update every so often. No clue why 3.0 to 2.0 rollback works and mostly sticks. Meanwhile 3.0.1 rollback to 2.0 does not (even tried removing just the package for 3.0 thinking maybe it was because was rolling back 2 versions, but nope, same thing even when only 3.01 and 2.0 were options).

Zokkel · 2012-06-05, 08:31

(2012-06-03, 23:44)phil65 Wrote: you have to change skin name / id in addon.xml and name your skin folder accordingly. it won´t auto-update then anymore.

Are you saying you have to give it a total random, non-default name in the addon.xml and skin folder, so that XBMC doesn’t recognized it as the default skin of Aeon Nox, but -lets say- your own creation?

I have the same problem that it keeps updating, but 3.0.1 has not the same features of 2.0 which I use and like... so 2.0 for me (Best skin yet! Thanks for the hard work)

Zokkel · 2012-06-05, 18:45

Did what I was told.
Changed the skin name AND skin ID in addon.xml (in folder of the skin) and rename the skin folder accordingly.
It stopped updating, so: huray there.
But all my skin-settings were gone...
next step: in guisettings.xml (userdata-folder) you have to change the characters "skin.aeon.nox" by "skin.the-same-name-as-skin-folder". Then all your skin-settings will be kept! (Be sure you do that BEFORE you start xbmc again, or it will automaticly create your settings in guisettings and then you have to delete them first...)

**Martijn** · (This post was last modified: 2012-06-05, 19:06 by Martijn.)

(2012-06-05, 18:45)Zokkel Wrote: Did what I was told.
Changed the skin name AND skin ID in addon.xml (in folder of the skin) and rename the skin folder accordingly.
It stopped updating, so: huray there.
But all my skin-settings were gone...
next step: in guisettings.xml (userdata-folder) you have to change the characters "skin.aeon.nox" by "skin.the-same-name-as-skin-folder". Then all your skin-settings will be kept! (Be sure you do that BEFORE you start xbmc again, or it will automaticly create your settings in guisettings and then you have to delete them first...)

What you could have done is change the skin version number in addon.xml to version="6.0.0" (or whatever) so it would only update if a higher version was available.
This would have kept your settings

phil65 · 2012-06-05, 19:15

(2012-06-05, 19:06)Martijn Wrote:
(2012-06-05, 18:45)Zokkel Wrote: Did what I was told.
Changed the skin name AND skin ID in addon.xml (in folder of the skin) and rename the skin folder accordingly.
It stopped updating, so: huray there.
But all my skin-settings were gone...
next step: in guisettings.xml (userdata-folder) you have to change the characters "skin.aeon.nox" by "skin.the-same-name-as-skin-folder". Then all your skin-settings will be kept! (Be sure you do that BEFORE you start xbmc again, or it will automaticly create your settings in guisettings and then you have to delete them first...)

What you could have done is change the skin version number in addon.xml to version="6.0.0" (or whatever) so it would only update if a higher version was available.
This would have kept your settings

right, would be easier. but you´d loose the ability to install 3.0 next to it.

cheeksmonkey · (This post was last modified: 2012-06-06, 02:37 by cheeksmonkey.)

(2012-06-05, 19:06)Martijn Wrote: What you could have done is change the skin version number in addon.xml to version="6.0.0" (or whatever) so it would only update if a higher version was available.
This would have kept your settings

I tried this and seem to have broken my XBMC now. Here's what I did. Hopefully someone call help me fix it.

First I launched XBMC and rolled back to 2.0. Then I closed XBMC. I went to the folder:

C:\Users\Andrew\AppData\Roaming\XBMC\addons\skin.aeon.nox

I opened addon.xml and changed version="2.0.0" to say "version="10.0.0".

Then when I launched XBMC it defaulted back to the default theme (the name escapes me). I went to settings and it still says "aeon.nox" in the settings but if I go to the addons section the aeon nox skin is not listed anywhere in my enabled or disabled addons. What can I do? I really don't want to lose my 2.0.0 settings.

phil65 · 2012-06-06, 02:58

skin settings are stored in guisettings.xml. back-up that file and you can always re-apply your settings.
lookin in debug log and posting your addon.xml would help.

cheeksmonkey · 2012-06-06, 03:50

Here is my addon.xml:
http://pastebin.com/WigTbmPJ

And xbmc.log:
http://pastebin.com/YWSGRGcT

phil65 · 2012-06-06, 04:19

(2012-06-06, 03:50)cheeksmonkey Wrote: Here is my addon.xml:
http://pastebin.com/WigTbmPJ

And xbmc.log:
http://pastebin.com/YWSGRGcT

that´s no debug log.

cheeksmonkey · 2012-06-06, 04:21

My bad, I had debug turned on but must have turned it off at some point. Will it be very helpful if I turn it on now and then grab the log or will it be useless at this point?

phil65 · 2012-06-06, 04:42

yes, could be helpful. it shows whether it tries to load the skin.
you must have changed something concerning file/folder naming or concerning the addon.xml, othewise it´s not explainable.