2014-03-06, 22:33
(2014-03-06, 22:22)vbat99 Wrote: I'll check in about 3 hrs what "tvservice --status" says when
a) Raspbmc handles HDMI suspend
b) texturecache.py handles suspend.
c) I put the TV into suspend.
I figure It's something I'm missing in the procedure.
You should add some logging to your /home/pi/mytv.sh to make sure the calls are being received and handled correctly. I'm pretty sure they are, so I just need some clarity on what the actual problem is - is it XBMC exiting unexpectedly, or did none of your CEC commands work?
(2014-03-06, 22:22)vbat99 Wrote: BTW: When I type the command and press enter, I don't get the next command prompt. Have to Crtl-Z to get back to command prompt. (Above test I'll open an second PuTty window). And when we get this working, I'll need to figure out how to add running this on Raspbmc start-up, but figure their forum probably has info on how to do this.
Thanks for taking the time to look into this.
Rob
When you run the command at the command line it will never exit, it runs forever (it's a daemon, in that sense). You have to press ctrl-c to terminate it. Under normal circumstances it will be started automatically when your Pi starts (not sure how to do this on Raspbmc, on OpenELEC you just add an entry to autostart.sh) and will remain running until the Pi is shutdown. It doesn't really do much though, it's just listening for notifications and will be active only when it needs to do something which in the case of a Pi with virutal suspend support is only after receiving the OnSleep and OnWake notifications.