[Tilt, TyTN II, MDA Vario III General] qps:
NSI - Definition: (No Sound Issue)

Ok, I am through the posted link to the other NSI-Thread (http://xdaforums.com/showthread.php?t=352906&page=1)

So I can give you guys a short summary what they found out so far over the last months, maybe that could help us pointing out the source of our problem:

I think the most important thing they pointed out in their thread is, there are 2 kind of issues that are different from each other, but sounds nearly same if not reading carefully or explaining detailed, so we first have to figure out what issue we exactly are having:

------------------------------------------------------------

(now I am copying their definition of the 2 occuring NSI-Problem (No Sound Issue))

Vol_bug1 (I would call it NSI-1 for further reference):

Random, actual change of at least one volume slider from loud down to 0%. When this happens, no notifications are heard until the user reloads his profile (using HTC Home or SPB) or manually puts the sliders back in their correct place. This can even happen if your phone is set on vibrate, where something actually changes it to silent.

The occurance of this bug seems be related to background actions that occur when turning on or off your BT headset, making or ending a call with your BT headset, or initiating a call using MSVC. Without a BT headset "joined" the the phone, it would appear Vol_bug1 is not around. Even without any user action, the phone may dropped to zero. This has been speculated to have something to do with a BT headset turning on or off, or going in or out of range... but I've seen it happen with the earpiece and phone right next to each other, without using either. I could have not touched either for an hour, but then look at the phone to see the volume has been dropped.

Vol_bug2 (I would call it NSI-2 for further reference):

Not a whole lot is known about this bug, other than when it occurs, the volume sliders are left in place. It also seems to be a little harder to rectify, as simply moving the sliders, or changing your volume profiles doesn't change a thing. Ironically, vibrate mode works 100% of the time, which is great if you don't want to miss calls.

Some will either disable the HTC Home plugin, or reset their phone to get their sound back.

------------------------------------------------------------

So what I am talking about is, my problem at my HTC TYTN II with original ROM or some other ROMs loaded is NSI-2. So sound sliders are at their original positions, but no sound on device. Only solution as far I could see: softreset.

To continue the summary of the other thread (see top of my post) is:

Most of them, having the NSI-2 , are experiencing this with almost all ROM versions (WM6.1, Dutty, etc) and as it seems, it does not matter which radio version thy use, it still occurs.

- seems like no matter what ROM Version they use NSI-2 still occurs

- seems like no matter which kind of radio version they use, NSI-2 occurs

- some report that any kind of SPB software (SPB Time, ...) cause NSI-2, but after deinstalling, NSI-2 doesnt showed up again (not prooved)

- some report that HTC Home Plugin causes problem and after deactivating NSI-did not show up (not surely prooved yet)

- some report MSVC as a possible source for the issue (not prooved, as far as some of the users dont use MSVC)

- some report that deactivating SRS-WOW helped (not fully prooved yet)

- one of the last posts in the mentioned thread is that one user tried another ROM Version: HyperDragon III Pro + Manila2D . . .

He reports, that the 19th version of that HyperDragon is completely issue-free.

(see his posts: http://xdaforums.com/showthread.php?t=352906&page=25)

Other versions of the HypeDragonROM still have the NSI-2.

(So ... the 19th ROM uses CE OS 5.2.20273 Build 20748.1.4.0 while the later versions use CE OS 5.2.20753 Build 20753.1.4.0.)

So far this is a short summary of the other 25-page-long thread.

Maybe there are useful hints so far.

So I think we have to point out first if we all are talking about the same NSI-2 issue or if some are talking about the NSI-1 problem?