Does anyone know what changes they have made on the latest TR version? (2.1.349)

Hi kids!

I am slammed for time right now, or I would reply to all of the questions and comments made in the last few days. I only have time for a quick note.

Yes, there is a new Total Remote version, v2.1.349. This is what I would call a semi-critical bug fixer. The single most annoying bug was the "device tree of death", where going to the device tree could "lock" TR up and consume system memory at a rate of about 1MB/min until it ran out. The REALLY annoying part was a complete reinstallation could not help, since it was part of a reg key that is not deleted on app removal. It really came down to the IR database code choking on what turned out to be an invalid entry, and the database engine has been tweaked to avoid dying if this ever happens again.

Couple other tweaks, no big whoop. Absolutely nothing big, like repeats in CCF mode or other major requests. Sorry, all effort is going into getting this thing ready for a major OEMer we work with and the next gen of their gear.

Catch you all later.

Don

Howdy, I have been looking for the total remote package for my 4150. Where in london can I get it?

Am I the only one experiencing this? I've upgraded to the latest version and the I think the "device tree of death" has been resolved, but immediately a new bug surfaced. When I choose a particular device, (i.e Sony TV) as an active device, it points to the next device (i.e. Sony TV #2). Plus, I can't set my created devices as active. Any insights??? Or am I the only one experiencing this? To those who have already upgraded, any insight would be appreciated. Thanks!

Axim X5 is much more than 3m, min e throws 7m at least, both in TR andf in PDAWIN.
Very happy with the thing!
Only drawback kids are starting to play the games on it...
Barend

This is a problem, for sure. This is what happens when I don't have time for a week-long regression test. It has become bug priority #1. With luck it will be fixed in a day or two. This is a pretty critical bug for native mode, and basically makes it impossible to use. :( Luckily, this should have absolutely no effect on CCFs.

To the person who asked for UK dealers: I haven't a clue. I am merely a humble hardware engineer, and have next to no idea what is going on in the rest of the company. I would suggest either calling or dropping an E-mail to tech support and ask them to see if we have sold any to a dealer in the UK.


--Don

Don,

Just bought 2.1.349 for use on an HP 2210 (v1.10) and I am assuming that reading this entire thread, that 2.1.349 has not fixed the break in 2210 CIR support (any button pressed freezes for 8 seconds..)???

I am in no rush, as I can test it in irda mode, and it'll take a while to get the CCF's sorted.. but could you give us an indication as to when this is likely to be fixed???

cheers..

I can confirm that there is a uk dealer:

[Link: expansys.com]

I've been staring at this page for 3 hrs now. My concern is that the griffintechnology website states that the Ipaq 3800 is "Not internally verified. Should work based on hardware specs and existing system requirements."

Does it/Does it not work....? Can someone confirm?

Tell me about it. This is one of those obvious bugs that should not have been missed prior to release, but we were so eager to kill the "device tree of death" bug that we did not test adequately. Um, my bad.

Ironically, the lead programmer (and the only one who can fix this bug) went on vacation and will not be back until next week. This did give us lots of time to look for more bugs, and we came up with a record number of entries into our Bugzilla tracker ranging from urgent fixes to asthetic tweaks. They will ALL be implemented before I call it "v3.0", but the critical fixes will be out as soon as they are verified and will likely represent the last of the v2.x releases. Work should resume on Monday.

The primary change to what I expect to call v3.0 is the COMPLETE rewrite of the IR cores, learning and transmission. While Total Remote works perfectly for many signals we made a fundamental mistake in the early development and adopted a signal format that was too limiting. As some of you have discovered, Total Remote is flatly incapable of dealing with some signals that competing products CAN handle. This WILL be eliminated in v3.0, for the simple reason that I will not release it until it can do every single thing TVRC can do, and then some. My beta testers will end up doing the bulk of the verification work, since I never did have any of the gear that doesn't work with the current TR.

There are some other technical items that I will be able to discuss closer to the actual release date.

So:

v2.x - The Final Chapter = 2 weeks at best
v3.0 - A New Beginning = 6-8 weeks at the minimum

Hi Don.

Just tried 2.1.349 and both "my" bugs remain.
1. In CCF mode, all (yes all) IR codes ar repeated.
It works ok for my KRC-3 wich has separate codes
for everything but other devices don't like it.
SONY DVD and Esoteric DA

2. In CCF mode, discreet RC5 codes for don't generate
any signal.


I see that #2 will be adressed in 3.x but what about #1?

Regards, Magnus

Hi kids,

Total Remote v.2.1.381 is out. The ONLY change from v2.1.349 is to correct ONE SINGLE bug; under 2.1.349 your active device list could end up pointing to the next logical (from our database's perspective) device, so you might set up Aiwa CD player and get Apex TV!

This release was done SOLELY to eliminate this serious bug which could easily stop a user from being able to use it at all. We are neck-deep in the big IR code gut in preparation for v3.0, concentrating heavily on RC5 compatibility and minor refinements to the CCF support as well as a bunch of other tweaks. Unless someone finds a catastrophic error in this release of 2.1.381 I expect it will be the final version of the v2.x series.


--Don, Master Of The 880-940nm Band

When are you planning to release Total remote v3.0 and what do you mean by " We are neck-deep in the big IR code". What are the new changes in total remote v3.0

Please read the post I made about 4 messages back regarding v3.0. That is all I can tell you at this time, because that is all that matters: the IR core is getting overhauled. For those who know what this means, great. For those who don't, it means it will work better and with more devices.

FWIW, some of the beta testers are playing with the new build that supports RC5 codes, and it appears to work well. I _think_ we just crossed the last barrier to eclipsing TVRC. Gotta love it. :)

--Don, Developer of fine photonic cannons for Pocket PCs.

Don,

Please just give me some response even if it is just to say i am up a creek!

Total Remote IR transmitter device and IPAQ 3955 using CE 2002. The IRDA works however the TR IR Transmitter does not.

I have found that the IR's barely light with the current ROM version 1.11.

When Compact Audio setting are changed (Bass and Tremble setting) no visual changes are noticed with the IR's (viewed through a night vision camera). Now when i set the bass and tremble to max and change the backlight and power managment settings, then press a remote button several times through total remote, suddenly the light becomes very bright. Once i remove the IR transmitter or power the IPAQ off the IR's return to a diminished flash again.

I reinstalled the original ROM 1.0 and noticed the IR's are flashing bright, but will not control any devices. I made changes to properties (1.027, 0 repeats, with/without warm-up, and changed Bass and Tremble settings) but nothing has worked so far.

Rom Version 1.11 definatly is not working. Each time i updated the IPAQ to this version the IR's were deminished. I tried to install EUU3 by itself however i have yet to have a sucessful install, it fails each time it gets to the power management updates and the IR's continue to flash brightly but do not control any devices.

I would try to work with HP to see if this was a rom problem but my warentee has expired, so no techsupport for me.

Was there any special setup pre EUU3 to get the IR transmitter to work?

Have you looked at the IPAQ development kit from HP to possible resoved all IPAQ issues and ensure that it works?

Is this like any other problem you have seen with other PDA's?

Is there any chance this will ever get resolved?

Thanks,
Steve

A friend of mine has the same problem with a Loox 420, and unluckily the IR range of the Loox 420 is pretty short.

Total Remote and the audio transmitter work very well on his previous PPC, a Loox 610.