Hello,
What i am current running is my raspberry pi 2 plugged into my amp, and my amp plugged into my tv (this is all via HDMI cables). Everything is being controlled by a Logitech harmony remote. Everything is working fine during operation, but the issue that i am running into is that after i power everything off (the harmony powers off the amp and the tv, but leaves the pi running), and then come back and power everything on, the pi will always be frozen on the video category screen (even though it is never left on that screen). To clarify, by frozen i mean that there is a cirecle of white dots superimposed on the screen that keeps rotating, but that i can not exit out of, or ever seems to go away on its own. The only solution so far has been to SSH into the Pi and reboot it. I have disabled the CEC adapter completely, as some posts had pointed at that being a possible cause. Currently i am running the most current disk image, with all updates applied.
I should mention that everything in this setup was previously running openelec 6 with zero issues. This includes SD card, power supply, TV, amp, and all cables.
Does anyone have any suggestions, as I have not been able to find anything to help with this issue thus far.
Thanks
Enable debug logging and when the issue appears upload logs from ssh with grab-logs -A
Do you have an IR receiver on the Pi? If so, I’m guessing that something in your power off/on sequence on the Harmony is sending a signal to the Pi.
What happens if you manually power off/on the TV and Amp, same thing?
When it gets into this mode, since you can ssh into the Pi, you can restart Kodi without a reboot
$ sudo systemctl restart mediacenter
Also, a post of the logs could be helpful
$ grab-logs -A
Hello,
Yes there is an RC6 IR receiver plugged into one of the usb ports. As for the remote itself sending commands to the pi during power on, it does send a power on command, which was always ignored previous by openelec. For the sake of argument i have rebuilt the commands on the harmony, to ensure that nothing has become corrupted on it. My logs are available at http://paste.osmc.io/ilefayiwip
Well not related to your issue but I wonder why you have “core_freq=250” in your config.txt
In regards to your issue. The last entries in your kodi.old.log are around data from Emby. May I suggest you check your emby setup and also maybe temproarly disable Emby in OSMC to see if the issue still exists to narrow done your issue.
20:36:46 1037.682251 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_genres.xml/VIDEO_TS.IFO
20:36:46 1037.682983 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_genres.xml/VIDEO_TS/VIDEO_TS.IFO
20:36:46 1037.683472 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_genres.xml/index.bdmv
20:36:46 1037.683960 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_genres.xml/BDMV/index.bdmv
20:37:23 1074.885864 T:1757590512 NOTICE: EMBY WebSocket_Client → Message: {“MessageType”:“ScheduledTaskEnded”,“Data”:{“StartTimeUtc”:“2016-04-20T02:37:22.8007400Z”,“EndTimeUtc”:“2016-04-20T02:37:23.8534120Z”,“Status”:“Completed”,“Name”:“Organize new media files”,“Key”:“AutoOrganize”,“Id”:“415f8db75e909cdef2a3da79d1e2c636”}}
20:42:25 1376.394897 T:1757590512 NOTICE: EMBY WebSocket_Client → Message: {“MessageType”:“ScheduledTaskEnded”,“Data”:{“StartTimeUtc”:“2016-04-20T02:42:23.8530270Z”,“EndTimeUtc”:“2016-04-20T02:42:24.8547270Z”,“Status”:“Completed”,“Name”:“Organize new media files”,“Key”:“AutoOrganize”,“Id”:“415f8db75e909cdef2a3da79d1e2c636”}}
20:47:25 1676.659180 T:1757590512 NOTICE: EMBY WebSocket_Client → Message: {“MessageType”:“ScheduledTaskEnded”,“Data”:{“StartTimeUtc”:“2016-04-20T02:47:24.8544510Z”,“EndTimeUtc”:“2016-04-20T02:47:25.6252620Z”,“Status”:“Completed”,“Name”:“Organize new media files”,“Key”:“AutoOrganize”,“Id”:“415f8db75e909cdef2a3da79d1e2c636”}}
20:48:01 1712.998291 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_random.xml/VIDEO_TS.IFO
20:48:01 1712.999023 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_random.xml/VIDEO_TS/VIDEO_TS.IFO
20:48:01 1712.999390 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_random.xml/index.bdmv
20:48:01 1712.999756 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_random.xml/BDMV/index.bdmv
20:48:57 1768.885742 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_recommended.xml/VIDEO_TS.IFO
20:48:57 1768.886475 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_recommended.xml/VIDEO_TS/VIDEO_TS.IFO
20:48:57 1768.886841 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_recommended.xml/index.bdmv
20:48:57 1768.887207 T:1957094320 WARNING: CreateLoader - unsupported protocol(library) in library://video/Emby - 7c6b1294b30d4c722993e4036d0425ac/7c6b1294b30d4c722993e4036d0425ac_recommended.xml/BDMV/index.bdmv
the core_freq=250 was entered because i thought that perhaps it was overheating and locking up due to that. i reduced the core_freq to see if the issue would resolve itself. I doubt that Emby would be the issue, as that server has been running for almost the last year with both openelec and OSMC on several different devices without any issues
Ok, just to clarify about your logs. Did you created that logs when the problem was shown before you restarted the mediacenter or afterwards?
i created that log after reproducing the issue again
Thanks for the help. Finally got this issued resolved. Issue was something to do with the commands being sent by the harmony remote. After completely trashing its configuration and rebuilding it everything works properly now.