Well well well, look who just showed up. I suggest that you review the thread [Link: remotecentral.com] for a truth-filled review of the prontong TSU3000. There is also some mention of the prontoprong in that thread too that you might find enlightening.

I find your promises of future firmware to be encouraging. Who knows, I may even consider buying a TSU3000 in the future, once (if) the problems have been worked out.

Unfortunately, I have since returned my prontong due to its overwhelming problems and poor performance. The only reason I continue to lurk on this forum is to follow up on any questions that some people may have with regards to my postings. After all, I don't want to be considered a troll artist that puts up a posting and never comes back to the conversation.

However, my suggestion for this posting is this:
Please update your website. Specifically, the specifications of the TSU3000 found at [Link: pronto.philips.com] where you indicate, "Typical battery life: 4 months".

This is a blatant lie and many court judges would view this as false advertising worthy of swift and appropriate penalties.

Thank you for your time,
Boogman.

Philips... How about posting beta versions (with proper disclaimers) for the next formal release? 3-6 months is a long time to wait for some of the fixes. In any event, you would get a lot of good feedback from the folks here and the firmware testing is free!

The danger of releasing beta firmware for a device like the Pronto is it could easily wedge the device beyond end-user repair (e.g. the device no longer communicates with the PC, goes into endless reboots, etc.) Even with disclaimers in place, there are still added responsibilities that Philips must shoulder:

- Extra development processes to cut public-quality
mid-cycle versions (including source control
branching, extra QA on those releases, etc.)

- New processes and people to capture and respond to
users' problems/feedback

- Burden of accepting extra units back for factory
firmware reset in the event of a hardcore
disabling bug


This is a lot of complexity for something that admittedly doesn't obviously (very critical word there) have much of a return for Philips. They could (and maybe do) have some kind of limited beta group they deal with that understand the process and the dangers, who knows.

Also implementing something like this could possibly lengthen the overall development cycle, which considering how long they already are, I'd rather not see personally.


_Luke

A robust, well writen boot loader that resides in the remote would allways allow for a new firmware download to the remote. If necessary just download the last working version of firmware if things dont go as desired.

I would hazard to guess that would add another burden on Philips before they could implement public betas:

- Write robust, infallable boot-loader

:-)

_Luke

I too would just like to thank the ProntoPro team for listening.

I would add though that I am another wanting the LCD to remain off when a hard button is pressed, and that the IR is just sent.

HNY to all,
Tony.

Thanks for posting Pronto Team. I'm another forum user waiting for the double press issue to be resolved BEFORE I buy the 3000. I'm afraid I need to preserve the setup of my existing remote and require one of the bottom buttons to fire a system off command with 1 press of a button when the remote is in standby mode (as it does on my UK 890 pronto), also play\pause for dvd viewing etc etc- the hard buttons are great but of little use to me as they are - I'm afraid I can't consider the unit as it stands.

Please take into consideration that for all the comments you view on this website there are probably a large number of potential owners waiting for the feature set to be proven to work as they require before they too buy one of your remote and add further to discussions\feedback of features.

Duncan.

I have the tsu 3000- I have latest edit software and I just downloaded firmware V1.1.6.3 and my pronto will not calibrate with finger or pointy object in 20 trys- HELP!

Like you said, use a "pointy object" such as a stylus.

On my 7000 the lower right touch point is 3 or 4 pixels off to the left of the x.

Keep trying, you will find the sweet spot on one of the press's.

Dave

Nice that you guys did post something to tell us all, I've had not much luck getting problems resolved through help desk. Hows about fixing the toggle bit problem with thomson remotes (Mines is a digital terrestrial tv receiver model DTI-1000), weird because the ru940 worked perfectly, whereas the ru950 doesnt.

The whole point of the calibration is to tell it where the 'x' is on your screen. If you have to press somewhere else to get it to calibrate, your unit must be outside of its design parameters (ie, they didn't expect the 'x' to be there). Probably not surprising since you beta-testers probably got less-than-perfect units at such a good price.

Barry

Anybody know whats new about firmware V1.1.6.3?

Hello Pronto Team,

Thanks for your participation and hope to hear more from you!

One thing I miss in my 7000. In the 3000 the hardbuttons had a bit of light from the backlighting and the glow through the buttons was often adequate. The 7000 is just pitch dark on the right side and 4 HB below the screen. What was the reason to exlude lighting these areas in the 7000? Wishing you could rectify this in the future. In a slightly dark room, I really have to work at seeing these 9 buttons.

Thanks!

Dave D'Arche
http://ProntoWizard.com

Those buttons are backlit, but you have to hit the backlight button.