mad buttons on nw-e507

[jmax]

Hi everybody, I,m from Spain and it,s my first post in this forum... and I have a problem. I bought the nw-e507 in Japan, and after installing SonicStage and download music to the player it was all OK for two days. Then something strange happened.

When I touch any button (Play, volume, etc), the song goes back (and Shuttle is not pressed). The Disp and Search buttons don't do anything. Reseting the player and upgrading firmware don't solve the problem, and of course I'm very accurate whit the player (no shock, no water, etc).

Can someone help me? Because this player only worked fine 2 days. Now I only can see how the songs list go back without touching any button.

PD: I try enter the test mode, but in HOLD state, pressing Play+Reset only make a simple reset ("Data access" is showen)

Thanks

[Guest Stuge]

Hi everybody, I,m from Spain and it,s my first post in this forum... and I have a problem. I bought the nw-e507 in Japan, and after installing SonicStage and download music to the player it was all OK for two days. Then something strange happened.

When I touch any button (Play, volume, etc), the song goes back (and Shuttle is not pressed). The Disp and Search buttons don't do anything. Reseting the player and upgrading firmware don't solve the problem, and of course I'm very accurate whit the player (no shock, no water, etc).

Can someone help me? Because this player only worked fine 2 days. Now I only can see how the songs list go back without touching any button.

PD: I try enter the test mode, but in HOLD state, pressing Play+Reset only make a simple reset ("Data access" is showen)

Thanks

←

I think the way ur player is behaving is not normal.I will consult u to take ur player to nearest sony service station.As ur player is new & it is in warranty(But u should have a overseas warranty for that ,as u bought ur player from japan.

Best of luck

AND ALSO ADD UR COUNTRY(IN UR FORUM PERSONAL DATA)

Edited October 29, 2005 by Stuge

[imagine_]

Have you upgraded the firmware to 2.0? Maybe this might help if it is a bug with some revisions of the board...