Brand new out of the box,configured and wotrked for one day. Next morning, took the remote out of the cradle and black screen, no sounds. If returned to cradle, indicators show it was charging , then after a few minutes went out.

Remote also remains dead if I try to use it while cradled.

If I reset the remote, it dodes come alive, it displays my last configuration properly (date fine, time incorrect at 12:00am), but gors dark and dead in 15 seconds (not sure if it is dying in 15 secs, or the screen display is timing out).

I was able to successfully download the config from PC to remote, so I don tthink it is corrupt.

Any advice?

I have exactly the same problem, with the exception that I haven't yet connected the Pronto to a computer. Mine doesn't die every fifteen seconds, but it does die regularly enough that I'm concerned.

I, too, have to push the reset button to get it to spark back to life.

I have barely started to program the device - all within the remote itself (setting a few brands, etc.), not externally, so whatever is happening is not caused by an external source. My home theater isn't even set up yet, so I don't even really use the remote much - the first time it died I was just simply trying to show my father-in-law what a cool thing the Pronto is, but it didn't turn on. Yep, cool.

Have either of you downloaded and installed the latest firmware from Philips?

If not, try this first.

Lyndel

Mine acted up as you have described just twice so far and I have owned my TSU7000 for some time now. All I did was unplug and replug the battery back in, then immediately flash the firmware before the screen goes dark. This did the trick for me. The remote then wakes back up as it should and stops dying repeatedly.

I would check the firmware version of your remote first. You don't have to update to the latest firmware. Reflashing the firmware is what's important. Yes, the latest firmware is supposed to take issue with the remote dying so much, but the latest firmware may introduce a whole new set of problems for you. If it does just revert back to the prior firmware update before that. Not the most recent one.

-Lowpro

Upgraded firmware and all is well. I can't quite figure out why things were okay for a while then didn't work, but I am up and runnign and happy!! Thamks for everyone's input.

I haven't upgraded the firmware, but I will. I guess I just kind of expected a $1000 device would turn off and on properly without needing to upgrade it right out of the box.

Thanks for the advice. Based on the other poster's response, upgrading the firmware seems to do the trick.

I don't know what version of the firmware you currently have, but there were a couple of memory leaks and buggy interrupt handler that was causing lockups during the beta testing of the 7000. These have been fixed. Both Peter Dewildt and myself can vouch for that.

My 2p. Please don't take offense, I'm not trying to flame you. I just wanted to illuminate another viewpoint. That of the software developer and the retailer.

OK, you buy a new computer with Windows from Best Buy, Dell, HP, or any other vendor. What's the first thing you do? You go and download fixes from Microsoft. Why? Because you want the computer to operate correctly and get the latest bug fixes.

As you have no idea how long your nice new remote sat on a vendor shelf, you don't have a guarantee that it has all the latest fixes.

If Dell, HP, Best Buy were to break open the package on every PC before it ships or leaves the store just to upgrade it in hopes that someone would buy it, you'd have many "open box" deals as folks would immediately consider the equipment used. Retaliers go out of business, warranties voided, etc...

That $1000 remote you purchased is no different than a computer (it has an internal CPU, memory, keyboard, etc) or Palm Pilot or other handheld PDA. Upon purchase, you entered into an unwritten contract that you should stay current, or as current as possible with fixes to ensure that your computer runs correctly. If you are current and find a bug, then you have rights to complain LOUDLY.

Software, as we all know, can and often does have bugs that are exposed only when the software reaches users hands. Having developed software for 22 years now, I know that no matter how careful I may be, a bug or 2 may slip through.

Warmest regards,
Lyndel McGee
TSU7000 beta tester.

Lyndel -

Many apologies if my post came across poorly. I didn't mean it to be - especially not directed at you. I certainly understand the perils of being an early adopter. I also have developed software for many years (18). What I am surprised by, with the Pronto, is that it fails to work when it isn't actually being used. My remote sat idle for 5 days. I simply picked it up after that period of time and it was dead. I would consider it more than reasonable for a bug to be exposed during normal use (e.g. a sequence of button pushes not tested by the developers), but, at the risk of sounding like a broken record, I haven't yet started using my Pronto.

As for upgrading Windows machines right out of the box, that's why I am a Mac user at home. Never had to upgrade one of those beasts immediatley after opening the package (I really hope I didn't just start a Mac vs. Windows debate here). Being a Mac user is why I haven't upgraded my Pronto's firmware yet - I either have to do it on a PC at work (which isn't easy, as we have 300 Linux boxes and 100 Macs, but only a handful of Windows machines) or borrow my father-in-law's laptop.

Once again, thanks for the info as to how to fix the problem. I didn't mean to sound as if I was shooting the messenger.

All the best,

Bob

Bob,

No offense taken.

FYI, the bug that caused the lockup resulted from a press of a button just as the screen was fading out. As you went to put the remote into the cradle, if the screen began to fade and your finger grazed a button, the lockup could occur. You would never have known the problem existed until you picked up the remote to use it again.

IMHO, that was one of the hardest bugs for all of us to find. I spent at least 6 hours trying to reproduce during Beta Testing and was never successful.

Lyndel, your comments regarding immediate updating for software on computers is fine, but with a device like a remote to need amjor update of the firmware to works a specified doesn't make sense to me... Then you have the issues that I do, and the firmware update won't load as the thing can't connect to the computer as it should.... What do you do then?

I have the same problem. It seems to be that every time someone has a problem a firmware reflash does the trick. I can't get my PC to recognize the pronto, what do I do now?