Roku Developer Program

[errr]

I posted this in the general too but Im not getting any response so I thought I would try it here..

I have made a remote, and it works great, unless my roku is "sleeping" during this time you can not ping the roku so you cant telnet in.. I know "waking" it up is possible to do because my Android remote is able to do it from my G1. How do i do it in my app though? Should I be looking at using WOL or is there something else that will work?

Thanks

[renojim]

I'm not sure what exactly your problem is. Are you saying that you can't ping your Roku's ip address when it's in screensaver mode (and by ping I mean using the actual ping command)? I can certainly ping my Roku at any time. I assume you're telnetting to port 8080 to send the remote commands. If you're box is in screensaver mode, the first command should wake it up just like pressing a button on the remote, at least it does for me although sometimes I have to issue two commands for it to wake up.

-JT

[errr]

Yes I am saying when the Roku is in Screen Saver Mode I am unable to ping and so when I try to open a socket to port 8080 it fails.

[TheEndless]

"errr" wrote:
Yes I am saying when the Roku is in Screen Saver Mode I am unable to ping and so when I try to open a socket to port 8080 it fails.

Not that it helps you at all, but I'm still able to telnet to both of mine when they're in screensaver mode. Both of mine are hardwired, though. I don't know if that makes a difference or not.

[errr]

Actually that did help out.. I am using wifi and I switched to wired to test and this doesnt seem to happen when I use a hard wire. Also even the droid app does not wake the Roku up if its been "sleeping" for long periods of time. If I can not ping it then no network based remote work.

[renojim]

That's strange. Mine is wireless and I don't think I've ever had a problem with pinging it. I do have a problem at times with telnet occasionally, but I think it has more to do with whatever I'm developing at the time crashing and taking something else down with it. The next time it happens I'll make sure to see if the box still responds to pings. I guess none of this really helps you, though.

-JT

[errr]

"renojim" wrote:
That's strange. Mine is wireless and I don't think I've ever had a problem with pinging it. I do have a problem at times with telnet occasionally, but I think it has more to do with whatever I'm developing at the time crashing and taking something else down with it. The next time it happens I'll make sure to see if the box still responds to pings. I guess none of this really helps you, though.

-JT

This has been very helpful. I have found that this is only an issue with the wifi. I am going to switch back to wifi and start a timer to see how long it takes for the wifi to go to sleep and drop its connection. I wonder if there is a way to keep the wifi from doing that.. Or if there is just a way to WOL the wif connection.. I tried doing the WOL for the wifi but never could get it working..

Thanks for all the replies.

[errr]

Also, is it possible that it is something in my router that is causing the connection to go to sleep? I am using a WRT54gL with Tomato firmware on it..

[renojim]

I was wondering if it has something to do with your router. Does your router have any DHCP settings that could be affecting this? Maybe the DHCP lease time? I'm using a 1 week lease time and also a static client lease for my Roku, so its ip address never changes. I was just able to ping my Roku after it had been sleeping for about 8 hours.

-JT

[damageplanpc]

I'm rather new to this SDK and generally a "Tool Time Tim a.k.a. Allen" type -O owner of a VA Beach Based PC Managed Services and Custom Builds (e.g. Motor Coaches, Drag Racing Telemetry One Offs, and Ye old worst investment any man can make, "A Boat" perplexed, then buy a big one!) Ok, to the LAN Remote Based dilemma.. I would place all my energy in the router category as a prime suspect in the (correct me if I'm totally off base) inability to "wake" your Roku from a "standby" S1, S3 %S% state. Assuming the "ping" (as used in a very broad sense) starts at the host, tunnels, and generates correct packet data, there are a wide variety of variables that can still through you a ringer. For instance, you know everything is working if you eliminate the wireless variable and that's a big bonus in and of itself! Now you have a map to follow and time to use the process of elimination. I would first translate the raw IP data into a map while you are testing the Droid or the Virtual Remote. Then pay particular attention to latency and timings of data transfer (Wi-Fi vs. wired) Nuff about that. Finally, is the "handshake" happening? In other words is the router configured for port forwarding or simple UPNP and how's those doors? (port 8080 is often the killer w.r.t. use) make sure the router isn't utilizing port 8080 for another access point and it might be beneficial to grasp a little of Microsoft's Link Layer Topography Responder requirements if you are mixing old with new with Linux and colored Ubuntu .... Finally, if all else fails, garb a big hammer, and beat the Sh_t out of the old router with HAK5 Tomato, ROM! (good stuff, but basics are my personal start point when pushing the round peg through the square hole begins) vision and try something like a Netgear WNDR 3700. System Internals offers some simple tools that are free and very effective for trace, ping , and ports of call. TCP/UDP endpoint viewer.
I'm presently working on some similar stuff w.r.t. Sling Media, Motorola Droid, device directory and remote push. assuming I don't grab something more destructive than a hammer within the next hour, (thinking along the lines of atomic) I will post again and be happy to pull a CISCO or other out of my hak pile!" (alluding to the earlier boat owner's brotherhood of perpetual misery!" How Much!?

Take Care and hope my sarcasm didn't make you scream!

RRBM