Hard Key Crash on 2.0.0.68

[tmorten]

I have a hard key mapped to execute a Girder call. When I press the key, Girder receives the action, but NR immediately dies. The same CCF works fine with 1.1.0.44...

Cheers,
Tim

[Ben S]

Hi Tim - We'll take a look. Does the button work if it's not a hardkey?

[danward79]

I am seeing a similar thing with my Dell X50v, I have remapped the hardkeys but they all cause NR to crash.

[MeSue]

I wrote this up before I saw there was already a thread about the hard keys problem, so I will just tack it on to this thread...

I'm a new user trying to get NetRemote working to control J. River Media Center on an Axim x51v. I tried the 1.1 version from the Web site last night, but was having some problems with it so I decided to try this beta. It was working pretty well earlier with the May 01 beta, but I was having a problem where the controls would revert to the wrong zone every time there was a song change. The correct zone's playlist continued playing, but the display would show the info from a different zone, and I would have to set the zone before using any of the controls. Also, most songs don't show cover images even though I have them in my library, and I can't browse covers at all.

I came on here and was going to post about that, but I saw there was a newer beta from the one I had installed, so I thought I would try it first. Well, it seems to have fixed the zone issue, but now I can't use the hard buttons on the Axim. As soon as I press a button, NetRemote just closes… no error, no nothing. And the cover image problem persists.

I'm trying to get this working to use poolside (Axim is in a Dry-Pak case) and it can be hard to see the screen in bright sunlight, which is why I'd really like to have the hard buttons working. Any suggestions?

PS: A high-contrast skin would be nice for the bright sun situation.

[Ben S]

I've found the issue. It will be fixed momentarily.

[Ben S]

MeSue - When you have a similar problem (changing zones), can you send me the MediaBridge.log file?

Regarding high-contrast, that does sound good. Any interest in creating this?

[MeSue]

MeSue - When you have a similar problem (changing zones), can you send me the MediaBridge.log file?

Sure.


Regarding high-contrast, that does sound good. Any interest in creating this?
I don't know. What would the learning curve be like? I'm good with graphics, but have zero programming experience.

[Promixis]

Sure.


I don't know. What would the learning curve be like? I'm good with graphics, but have zero programming experience.

The graphics are the key. If you just replace them, not programming at all.

[MeSue]

MeSue - When you have a similar problem (changing zones), can you send me the MediaBridge.log file?

Ben, I wasn't having the zone problem last night when I checked it At my desk, but today when I went out to the pool it did the same thing where it kept changing zones. I have the log file. How would you like me to send it to you?

[Ben S]

Email via this forum or PM would be fine. Is it multiple PC's with zones or multiple zones on one PC?

Back to hardkeys: Attached is a patch for Win32 and PPC versions to get beyond the hardkey error. Unfortunately some other issues have kept me from releasing a full build.

[tmorten]

Thanks Ben; that did the trick!

Cheers,
Tim

[Ben S]

Great! Thanks!

[MeSue]

Well I feel a bit silly, but I think my zone problem was caused by the fact that my PDA was set to power off after an idle period and that was causing it to drop the wi-fi connection.

My hard keys are working again now, too.

Can anyone tell me if the hard keys are skin-specific? I prefer the 640x480 skin from the 1.1 version, but when I use it in 2.0 the d-pad keys don't work. I would like to use them to control volume, play/pause, and prev/next.

[Ben S]

Regarding the wifi - Not a problem. The zone switching is actually something we'd still like to resolve, so maybe this is a good test once we have the code in place.

Regarding the hard-keys - Yes. It requires that both the skin is setup to use the hardkeys, and that the device has it's hardkeys mapped (from the config pages). If both are setup and it's still not working, then something is awry and needs to be fixed.