I am having the same problem with my remote control...I used a stylus several times to calibrate it and it pushes buttons that are 2 buttons higher just as yours did Dino. Is there a way to update the O/S via the website? I dont have the ability to take a video like that but I can say that my remote has a standard background (still waiting on a template from a friend at work that has richer graphics etc)...but long story short I dont have nearly as many buttons as you do and they are spaced apart more but I still run into problems of unresponsive buttons occassionally along with buttons 1 or 2 higher or to the left and right of the original key I press.

Michael Ethier

Under the battery I have MX-3000 N4 listed with some weird bar code number (dont know if i should post that publicly)...and it says WIN CE .NET 4.2 core X11-15297

also have O/S 4.20.003.003N2 (OCT 28 2005)
Firmware: 2.22.3.51222

Just FYI folks, I have my MX-950 setup as a family remote, its screen looks as this


DAD

MOM

KIDS

GUEST

JUMP TO...


I set it up this way so my wife has a super simple remote when she uses it, the kids have limited access and only thier channels appear on the screen, and I ofcourse, have all the bells and whistles. Dinom was mentioning he needed something like this so I figured I would share.

MJE, so I'm not the only one!!! I thought I was going crazy, because URC kept telling me that I was the only one that had ever complained about this and that it must be the "way" I am pressing the buttons with my finger.

Well, the bad news is you cannot update the remote to fix this via the website. You must send it back to URC for them to update the OS, or they will just send you a new one (assuming you bought it from an authorized dealer).

Now, the good news is that they have a fix that improves this by maybe 75-90%. I still have some problems in one area of the screen more that others (upper left portion) where button presses sometimes trigger ones "below". This is a different scenario than before (as shown in my video), but it's still much improved.

I'm hoping URC comes out with a 100% fix for this, since for $1000 list, I'm expecting that. The first MX-3000 I owned (had another problem, so it got replaced) never had this issue at all, so I know it's possible to fix this 100%. They must have made some software changes that introduced this issue mid to late 2005.

Eric or Jeff, any more info on this issue? Or have you just settled on the current fix being "good enough"?

Dino

Also, that OS release date that you posted still had the full blown bug. It wasn't until the batch of MX-3000's shipped after or around December 1st that the modification was added.

Dino

dinom, I also have run into this in the past, what I have done was reset the remote back to default and then reload my config. This seems to work for me so far.

Yeti, this problem is deeper than that. The issue even manifests itself on the "systems" screen, you know the one you get to by holding down MAIN for several seconds. It's a problem in the OS/firmware and has nothing to do with the actual configuration file. URC has confirmed this.

Thanks for the input, though.

Dino

I got my remote control from Magnolia Hi-Fi as a gift...(a friend is an installer there who programs the remotes)...I seem to run into problems even getting mine to be calibrated cause with a stylus it doesnt even respond you have to hold the stylus there for about 5+ seconds and it will move. Have all the boxes and stuff however I just know I cant deal with buttons being compressed that are 2 higher than the one I am actually pressing.

-Mike

Mike, that's actually how the calibration works. You have to hold the stylus at each point for about 5 seconds for it to register. This is to make it more precise.

So, what have you decided to do? Exchange it or get it "fixed"?

Dino

i was hoping to hear the best thing to do from you guys...I'll probably exchange it at Magnolia Hi-Fi however i'd like to know which O/S version I should be looking for.

-Mike

Mike, the best thing you can do is call Joe Spinelli at URC at 914-835-4484 x320. Tell him you have the same issue as Dino (he knows me very well :-)

Actually, I just got off the phone with him to let him know that I'm not 100% satisfied with the current fix, as it still affects me 20% of the time, more so in the upper left side of the screen. I plan on making another video to show the problem as it stands now and will post it here soon.

Joe is going to speak with Eric Johnson later this week to discuss options. I'm even thinking of switching to an MX-950 (hence the other thread I started) if it ends up that this won't be fixed 100% anytime soon.

Let us know how you make out after calling Joe. He really is a great guy to work with.

Dino

Here's the video showing the problem as it exists today after the first fix. You can see it's much improved as far a frequency of occurrence is concerned (compared to my first video before the fix), but it's still not acceptable in my opinion. Now the bug manifests itself by causing buttons "below" the one being pressed to become active. This is different than the original problem. Also, the problem occurs more in the upper left than before where it was kind of random.

[Link: home.townisp.com]

I'll be sending this to URC for evaluation.

Dino

MJE,
I just got off the phone with Magnolia and they said there is no way they can tell what the O/S date is on each remote. They are trying to tell me it's user error since I programmed it myself.
They gave me 3 options:
1. Exchange it for another and take a chance on the date,
2.Exchange it for another and have them program it for $300 or
3. Get with the URC and exchange with them.

maxfli100, are you saying you have the same problems as MJE and me? I'm not following your post.

Dino

Sorry about that and yes I am seeing the same problem. It's more noticable if i'm pressing the buttons on a keypad screen.

My O/S date is 10/23/05.

maxfli100,

Please take my suggestion and call Joe at URC (see above). The more pressure we put on these folks, the more likely they will fix this 100%. My guess is, the more time that goes by, the more posts we'll see about this problem. It's just taken some time for the "bad" MX-3000's to trickle down to consumers.

Dino