Can't map buttons on WMP10?!

[cdcooker]

I don't know if this is a bug or not. I just updated Dell X30 to the latest ROM version, which has WMP10 included. I tried to remap some of the buttons of the player, like mute and toggling full screen. Right now, whenever I tap the assign button on the screen, and then press one of the hardware buttons on X30, it will go to the assigned program associated with that particular hardware button, and the assign button window is keep staying on top of the screen of WMP10, and I can't tap on anything on WMP10. I have to manually close the program in order to control WMP10 again.

Anyone experience the same problem? Or I did something wrong to remap hardware buttons?

thanks

[Jason Dunn]

I'm having the same problem - I can map to the action button on the d-pad, but not to the buttons on the right (email and home). I'll contact someone at Microsoft and see if this is a known issue...

[ADBrown]

I don't know if this is a bug or not. I just updated Dell X30 to the latest ROM version, which has WMP10 included. I tried to remap some of the buttons of the player, like mute and toggling full screen. Right now, whenever I tap the assign button on the screen, and then press one of the hardware buttons on X30, it will go to the assigned program associated with that particular hardware button, and the assign button window is keep staying on top of the screen of WMP10, and I can't tap on anything on WMP10. I have to manually close the program in order to control WMP10 again.

Anyone experience the same problem? Or I did something wrong to remap hardware buttons?

thanks

I too am having this problem on my X50v.

[delfuhd]

aaaaand WMP10's value just dropped dramatically for me
:wink:

[Darius Wey]

aaaaand WMP10's value just dropped dramatically for me
:wink:

You're letting a bunch of buttons deter you from it? :P

Another fine example of a standard Microsoft bug if you ask me... ;)

[delfuhd]

aaaaand WMP10's value just dropped dramatically for me
:wink:

You're letting a bunch of buttons deter you from it? :P

Well, since I use a 2215, and dont have WM2003SE, and would be surprised if anyone at HP remembers what an h2215 is, the way they seem to "forget" about models and come out with new ones, and so I can pretty much count on absolutely nothing from HP regarding my 2215 for the rest of it's life, WMP10 Mobile has already dropped to garbage in my book, and HP isn't really much better than that. HP is really really really really screwing us iPAQ users. I mean REALLY screwing us.

No WM2003SE update
Rarely any support for "older" models, and i do mean rarely.
Lying to us BLATANTLY about why they refused to work to please their
loyal customers by making updates to WM2003SE.
Not offering WMP10 to those who can use it, which is dumb anyway
because its WMP10!!!! WHY WONT YOU JUST LET US FREAKING HAVE IT wow
And within that, Trying to get us to by POS models by only upgrading
them, and not the "good" models.

I was a diehard HPer and though I know that I will probably by another HP pocket pc, HP is being a real jerk to everyone right now. Wow it just pisses me off that they can be so avaricious and greedy. Can't we just see who the bastard is that is making all these decisions? I mean seriously, does he really think he's fooling people? Does he really think we're going about our merry way buying one of their new pocket pc's every week because it has one piece of newer software?

[delfuhd]

Erm, not to get off topic, though. :wink:

[Darius Wey]

Well, since I use a 2215, and dont have WM2003SE, and would be surprised if anyone at HP remembers what an h2215 is, the way they seem to "forget" about models and come out with new ones, and so I can pretty much count on absolutely nothing from HP regarding my 2215 for the rest of it's life, WMP10 Mobile has already dropped to garbage in my book, and HP isn't really much better than that. HP is really really really really screwing us iPAQ users. I mean REALLY screwing us.

No WM2003SE update
Rarely any support for "older" models, and i do mean rarely.
Lying to us BLATANTLY about why they refused to work to please their
loyal customers by making updates to WM2003SE.
Not offering WMP10 to those who can use it, which is dumb anyway
because its WMP10!!!! WHY WONT YOU JUST LET US FREAKING HAVE IT wow
And within that, Trying to get us to by POS models by only upgrading
them, and not the "good" models.

I was a diehard HPer and though I know that I will probably by another HP pocket pc, HP is being a real jerk to everyone right now. Wow it just pisses me off that they can be so avaricious and greedy. Can't we just see who the bastard is that is making all these decisions? I mean seriously, does he really think he's fooling people? Does he really think we're going about our merry way buying one of their new pocket pc's every week because it has one piece of newer software?

And in a nutshell, go Dell! :wink:


Erm, not to get off topic, though. Wink

Ironically, everytime WM2003SE, WMP10 Mobile, and software updates are a central topic of a thread, it always ends up being a rant on company practices and how they're screwing over the consumer market.

It tells you something about consumer response to their current stance on this whole issue, doesn't it? I can't tell you how many threads I have read which eventuate into another discussion on why HP aren't making us happy.

But back on topic now... :D

[KimVette]

Hey HP/Compaq started it when they advertised their iPAQ line as being flash-upgradable.

[delfuhd]

Hey HP/Compaq started it when they advertised their iPAQ line as being flash-upgradable.

Hey now don't drag Compaq into this. Compaq did provide great support, and made some great pocket pc's. HP is really just a killer. I just really hope this doesn't last.

[Jason Dunn]

I've received confirmation from a source who knows that Dell screwed up and didn't implement the buttons correctly. This will have to be fixed in a ROM update. :-(

[cdcooker]

Oh my goodness, may be this is a penalty of early adopter. ROM update is just a pain, I have to reinstall everything and custom settings.

:|

[Sven Johannsen]

Normally upgrading via flash gives a significant change in the OS. That typically prohibits, or at least makes ill advised, restoring from a pre-update backup. If a newer release of A05 is in the works to fix this, it may be such that a backup and restore might work. It would really be in Dell's best interest to ensure that is the case, considering the inconvenience to their customers for their error.

Anyone loaded A05 yet? What else does it do?

[cdcooker]

Other than WMP10, I don't see any significant change that I notice right away. I am still waiting a way to let user to change the hardware wireless button to turn on WiFi only, instead of both WiFi and BT.

Also, when I use ActiveSync, I can no longer use the same device name as before. I have to change the device name to a new name and create a new partnership. This is very annoying, as that's the device name I would like to use, instead of the default "Pocket_PC".

[Jason Dunn]

Also, when I use ActiveSync, I can no longer use the same device name as before.

You need to delete the older partnership - FILE > DELETE PARTNERSHIP. Remember to back up your files first!

[Don't Panic!]

While you can't map the buttons you can use the d-pad and scroll wheel action button to map 9 different functions. In my case I have

Hold-Up as Stop
Hold Down as Pause
Scroll Wheel Action as toggle screen
And then the defauls for everything else.

I really think we got the Smart-Phone version with the Dell Update, The * for Full Screen and the # for mute kind of gives that away.

Don't Panic!
Bobby

[cdcooker]

I've received confirmation from a source who knows that Dell screwed up and didn't implement the buttons correctly. This will have to be fixed in a ROM update. :-(

Jason,

Any idea when Dell will release an update to fix this problem?

Thanks

[Jason Dunn]

Any idea when Dell will release an update to fix this problem?

No clue. I have a hunch it will be a while. :-(

[kyrkesmith]

And what about HP? Same issue on the rx3715, and they refuse to know about it at tech support.

[Jason Dunn]

And what about HP? Same issue on the rx3715, and they refuse to know about it at tech support.

Really? Oh wow....I thought it was a Dell-only problem. :-(

[kyrkesmith]

No, definately on the iPaqs too. It even seems to have survived a minor update in the ROM update. WMP10 was originally added in the 1.01.06 (I think), and the bug's still there in the current 1.01.10.

Obviously Microsoft's fault then...

[Jason Dunn]

Obviously Microsoft's fault then...

Not based on what I was told - Microsoft gave the OEMs a generic button mapping template or something, and they needed to update it to work with their hardware, but it looks like Dell and HP didn't update it....? :roll:

[kyrkesmith]

Oh right.

That's slightly incompetent! What's beginning to annoy me is the update's been out for about two months I think, and they still haven't done anything about it.