Reply to thread

Message

<blockquote data-quote="Guzzi" data-source="post: 1092406" data-attributes="member: 55213">First of all: I did my own test - and can confirm, that for whatever reason, MyFilms seems not to receive anymore the messages for standby/resume.Actually, MyFilms is designed to receive signaling for standby/resume and reload the catalog on resume.That is really strange, but interesting to find out what change happened.Skin changes for sure are independant. Not sure, if av intercepts anything like messages - but don't think so.No, this only affects if the pc will wake on those events and should not be related - but as MyFIlms listens to os powermanagement changes, revert the change and see, if that brings it back - just to be sure.I see a lot of errors in the logs about problems loading the database, which are hints about corruption or invalid xml format. Those are not directly related to the standby problem, but could cause other problems, so I would check the reason anyway. After looking in the code, I see, that the standby handler register in the activation phase - so any resume actions only work, if you ever had at least once entered MyFilms once (so the handlers are initialized). One test would then be to once enter MyFilms and do standby/resume after that and see, iof it works then as expected. You should find something like &quot;PowerModeChanged() - MyFilms is resuming from standby&quot; in the logs - which means MF has received the message and this will kick the reload.If you can confirm, this is working, then I think we have to move the powermanagement handlers to the init phase, as with introduction of precaching, MF indeed can miss DB updates with current approach.</blockquote>

[QUOTE="Guzzi, post: 1092406, member: 55213"] First of all: I did my own test - and can confirm, that for whatever reason, MyFilms seems not to receive anymore the messages for standby/resume. Actually, MyFilms is designed to receive signaling for standby/resume and reload the catalog on resume. That is really strange, but interesting to find out what change happened. Skin changes for sure are independant. Not sure, if av intercepts anything like messages - but don't think so. No, this only affects if the pc will wake on those events and should not be related - but as MyFIlms listens to os powermanagement changes, revert the change and see, if that brings it back - just to be sure. I see a lot of errors in the logs about problems loading the database, which are hints about corruption or invalid xml format. Those are not directly related to the standby problem, but could cause other problems, so I would check the reason anyway. After looking in the code, I see, that the standby handler register in the activation phase - so any resume actions only work, if you ever had at least once entered MyFilms once (so the handlers are initialized). One test would then be to once enter MyFilms and do standby/resume after that and see, iof it works then as expected. You should find something like "PowerModeChanged() - MyFilms is resuming from standby" in the logs - which means MF has received the message and this will kick the reload. If you can confirm, this is working, then I think we have to move the powermanagement handlers to the init phase, as with introduction of precaching, MF indeed can miss DB updates with current approach. [/QUOTE]

Verification