I can discover a host with no issues, but when I click Connect, nothing happens - it drops me back to the same screen you get when you click Cancel. This happens with 1.3.0 beta 1 and 2, and whether I add a host manually or via zeroconf. It did work the first time I tried, but hasn't since. Any idea if this is the same problem, or a separate bug?
Please run xbmcremote with "-d connection" arguments and send me the output via email. Right now I can't thell whats happening. In my experience this happens mostly because of issues in the network connection, bad settings in xbmc or some firewall on the host where xbmc runs on.
If the connection still fails when launching xbmc for the first time after rebooting the PC, then you can at least tell its not caused by the bug I mentioned earlier.
Please run xbmcremote with "-d connection" arguments and send me the output via email. Right now I can't thell whats happening. In my experience this happens mostly because of issues in the network connection, bad settings in xbmc or some firewall on the host where xbmc runs on.
If the connection still fails when launching xbmc for the first time after rebooting the PC, then you can at least tell its not caused by the bug I mentioned earlier.
It looks like the problem disappears once I remove the overclock on the machine running xbmc, so it's not a bug after all. Sorry to have bothered you! Great app by the way, it's working absolutely flawlessly now.
When using aeon nox skin, and adding widgets to the home screen page, there's a step in which you're asked to type the name of the widget. If you click ok in the n9 remote the new keypad goes away but the dialog in xbmc remains and there's no way to close it. Happens all the time. This didn't happen with beta1.
When using aeon nox skin, and adding widgets to the home screen page, there's a step in which you're asked to type the name of the widget. If you click ok in the n9 remote the new keypad goes away but the dialog in xbmc remains and there's no way to close it. Happens all the time. This didn't happen with beta1.
Thanks,
Can't find it. Can you provide more detailed instructions where this happens?
