Remote not working (build: 1529)

[toastie]

I've just gotten the app, but I am not able to get it to work with my
Roku XDS (version 2.9, build 1529, no Roku build updates available).

I only have the ability to connect my Roku wirelessly, but I've
verified that my phone (a Hero with 2.1) can connect to the IP:8060
via internet browser.

I've unplugged the Roku box a bunch of times. I've re-added the device
a bunch of times.

What else can I try?

[Gregg Reno]

It seems like some people running wireless are having some problems.   I'll have to test again with my box again in a wireless setup to see if I can recreate it.

I'll let you know what I find,  but it may take till Saturday until I can get to it.
-Gregg

[Gregg Reno]

Toastie,
Can you do one more thing to help me trouble shoot?  Download the app alogcat.  Run the Roku remote app and click through a bunch of buttons.  Close the app then immediately run alogcat.  Hit the menu button and pick send to email me a copy of the error logs.
Thanks,
Gregg

On Feb 10, 2011 10:08 PM, "toastie" <toa...@gmail.com> wrote:

[toastie]

Hi Gregg,
No need...it is working now!

All I can think of that might be different today is that, prior to
running alogcat, I ran a utility which made sure that Roku Remote had
been exited, and I then restarted Roku Remote. Each time I had
normally exited Roku Remote last night, I am not sure if it was still
running in the background or not.

Thanks for your quick reponse.
Toastie

On Feb 11, 7:16 am, Gregg Reno <gregg.r...@gmail.com> wrote:
> Toastie,
> Can you do one more thing to help me trouble shoot?  Download the app
> alogcat.  Run the Roku remote app and click through a bunch of buttons.
> Close the app then immediately run alogcat.  Hit the menu button and pick
> send to email me a copy of the error logs.
> Thanks,
> Gregg

[Gregg Reno]

That's great!  Glad it's working for you.  

What utility did you run?  Is it a task killer?  I have a couple of other users reporting a similar problem. I'm also wondering if the upgrade to the new version didn't close a running older version.

Thanks,
-Gregg

--
- Gregg Reno

[thehypercube]

Hi Greg,

The title of this post summed up my problem too, so I wasn't sure
whether to create a new thread. Hope I'm not threadjacking here. Have
the same version of Roku Player, but I purchased the remote app
yesterday hoping to use my Nexus One as my remote.

The Roku is on the wifi network as I confirmed in the settings, and it
streams all channels perfectly using our Airport Extreme. My N1 is on
the same network as I confirmed through Airport Utility on the Mac.

The phone will not find the Roku via scanning. I typed in the IP
manually and it did not work. I tried to use the browser to connect to
the IP:8060 to no avail.

I am not able to test it wired in as the router wouldnt be near a
display. I power cycled the Roku with no luck. Reset the app by force
closing in the settings panel and also rebooted the phone to no avail.
Any thoughts? The airport extreme uses a 10.0.1.X DHCP format.

Thanks
Aaron

[Gregg Reno]

Aaron - since the test to IP:8060 didn't work,  the only thing I can think of is that your phone and roku are somehow connected to two different wireless networks.  Is that possible?
-Gregg

[Aaron]

The phone and roku are definitely connected to the same network
without question. The only thing I am not sure whether it affects how
the remote works, but I am using 2 Airport Express units as wireless
expanders for my Airport Extreme. Using the Airport Utility software,
I can see both items listed, by IP in the DHCP wireless clients list.
I will try and post some screen captures tonight that illustrate my
point. I also tried typing in the IP:8060 address through my netbook's
browser which I had handy.
Will follow up later this evening, thanks for your reply.
Aaron

On Feb 15, 1:34 pm, Gregg Reno <gregg.r...@gmail.com> wrote:
> Aaron - since the test to IP:8060 didn't work,  the only thing I can think
> of is that your phone and roku are somehow connected to two different
> wireless networks.  Is that possible?
> -Gregg

[Aaron]

After some fiddling, I was able to get the phone to connect after
forcing the Roku XD to reestablish its connection to my network. That
is some weird bug on Roku's side, I guess, since it was still
streaming all channels perfectly.

On to my next issue to solve now, which is counting to "eight one-
thousand" before any of the android remote's commands take effect.
Also in alpha-numeric search characters are dropped once they reach
the Roku's text field.

[Gregg Reno]

Aaron,

I wish I could help you out on the network stuff, but I really don't know what I'm doing there.  I'm thinking the delay is still somewhere in the network rather than the app.  One way to test it is to bring up the web browser and send it a key command - something like this, which should be the same as hitting the Left key on the remote:

http://192.168.1.1:8060//keypress/Left

My app sends HTTP commands, just like the command above.  How long does that take, and do you get any errors in the browser?  Also, I would suggest you try the above command on the home screen rather than within a screen like the Netflix gallery.  The keypress commands don't work well there, which is why I send separate keydown and keyup events.

-Gregg

--
- Gregg Reno

[Gregg Reno]

Oh, and substitute your IP address

--
- Gregg Reno

[Aaron]

You know, I have no idea what is going on here. I swear I'm fairly
adept with figuring out technological issues, but this is just weird.
The phone works perfectly now. Very responsive as of tonight, and the
browser will still connect to port 8060, but it refuses to send the
key commands via HTTP. As long as the app seems to be working for now,
I'm happy.

Thanks for your support!

On Feb 16, 9:39 am, Gregg Reno <gregg.r...@gmail.com> wrote:
> Oh, and substitute your IP address
>
>
>
>
>
>
>
>
>
> On Wed, Feb 16, 2011 at 12:39 PM, Gregg Reno <gregg.r...@gmail.com> wrote:
> > Aaron,
>
> > I wish I could help you out on the network stuff, but I really don't know
> > what I'm doing there.  I'm thinking the delay is still somewhere in the
> > network rather than the app.  One way to test it is to bring up the web
> > browser and send it a key command - something like this, which should be the
> > same as hitting the Left key on the remote:
>
> >http://192.168.1.1:8060//keypress/Left
>
> > My app sends HTTP commands, just like the command above.  How long does
> > that take, and do you get any errors in the browser?  Also, I would suggest
> > you try the above command on the home screen rather than within a screen
> > like the Netflix gallery.  The keypress commands don't work well there,
> > which is why I send separate keydown and keyup events.
>
> > -Gregg
>

[Gregg Reno]

Glad to hear you got it working.
-Gregg