Rom developers... the BT stack on the Touch works-

[sfaure03]

nosmohtac: umm.. a script was running? Interesting, cause that would have to be launched? I'm gonna bet the script was launched somewhere. We'd love to hear what script was running if it happens to you again.

All: I AGREE. This is not the "fix" for everything, it is, however, a big step forward with this device. I dont like the quality as well as i did the other combination, but i do like the added stability. However to be discouraged. No2Chem was ALWAYS using this aku and we hear/think he may just have reachede a good compromise place with an AKU.7+216 phone. Last night i reflashed a phone to aku.7 and 216. I will say the QUALITY of the sound of bluetooth was/is better than the combination we're using here. The march goes on. We do need you're testing and feedback, so we can catch things we might not otherwise in the next run. I expect we may have something new for you to test say friday or so.

Thanks for you're help in making this a better phone everybody

[willysp]

Originally Posted by sfaure03

nosmohtac: umm.. a script was running? Interesting, cause that would have to be launched? I'm gonna bet the script was launched somewhere. We'd love to hear what script was running if it happens to you again.

All: I AGREE. This is not the "fix" for everything, it is, however, a big step forward with this device. I dont like the quality as well as i did the other combination, but i do like the added stability. However to be discouraged. No2Chem was ALWAYS using this aku and we hear/think he may just have reachede a good compromise place with an AKU.7+216 phone. Last night i reflashed a phone to aku.7 and 216. I will say the QUALITY of the sound of bluetooth was/is better than the combination we're using here. The march goes on. We do need you're testing and feedback, so we can catch things we might not otherwise in the next run. I expect we may have something new for you to test say friday or so.

Thanks for you're help in making this a better phone everybody

Shawn - I'm glad you're taking positive & constructive feedback in the manner in which it's offered!

Again - thanks for all you and others are doing to improve this device. I'm currently carrying both a Touch and Titan, so always eager and available to test stuff on the Titan.

I still suspect that part of the problem with the Titan is narrow HW design tolerances, and that my particular device is tighter than average. Any thoughts on that?

Anyway, I think my particluar Titan along with my nXZen DSP headset will continue to be a challenging testbed!

[TC1]

Originally Posted by willysp

I still suspect that part of the problem with the Titan is narrow HW design tolerances, and that my particular device is tighter than average. Any thoughts on that?

While this might have been possible in the "old days" (and yes, I'm old enough to remember, lol), today's modern handsets process the radio and audio signals almost entirely in the digital domain, ie, the "signal" is just a bunch of numbers that are being manipulated using DSP algorithms like Fast-Fourier-Transforms. Digital electronics aren't as susceptible to manufacturing tolerance problems as analog circuits are. Digital chips either work or they don't, they don't "drift" due to minor variations in temperature, voltage, and other factors.

It is possible to get a bad batch of digital chips, but in that case they would have failed factory go/no-go testing. Infant mortalities (the chip fails shorty after being utilized by the consumer) would manifest themselves as inoperable units.

[willysp]

Originally Posted by TC1

While this might have been possible in the "old days" (and yes, I'm old enough to remember, lol), today's modern handsets process the radio and audio signals almost entirely in the digital domain, ie, the "signal" is just a bunch of numbers that are being manipulated using DSP algorithms like Fast-Fourier-Transforms. Digital electronics aren't as susceptible to manufacturing tolerance problems as analog circuits are. Digital chips either work or they don't, they don't "drift" due to minor variations in temperature, voltage, and other factors.

It is possible to get a bad batch of digital chips, but in that case they would have failed factory go/no-go testing. Infant mortalities (the chip fails shorty after being utilized by the consumer) would manifest themselves as inoperable units.

Yes - I'm familiar with the 'old days', too! (I've designed & constructed circuits using both tubes and IC's; and written LISP/SNOBOL/ALGOL programs and embedded assembly language drivers) Good days ... :=)

Perhaps the explanation is as simple as the fact that I'm more 'picky' and observant than some others, and work in a building with poor cell reception - which causes frequent switches to roaming, which made 2.16 an absolute phone-killer for me. And perhaps people with good BT experience haven't listened to the other end of calls with the Titan.