yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] BennTech:
Sorry haven't been around. Took a short vacation to NY. Been working on this in between catching up with my clients. Still able to reproduce at will. Researched the last of the registry differences I mentioned earlier and found nothing. Shame. Would have been easy to write an MortScript or tiny app to monitor/fix some registry entry. After that, I played with different radios & SPLs, focusing on testing the oldest and newest to see when the bug was introduced or when it was fixed.

Here's what I've tried:

ROM: ROMeOS v4.21.1 WM6.1. Haven't had time to flash new ROM, but we're using a lot of different ROMs that all have the problem--old, new, even stock--with a variety of applications (and no applications). However, I know I didn't have this problem with WM6.0 and Nika's been testing WM6 and has had no problems with sound. So if anyone wants to, flashing back to WM6.0 will fix your no sound problem.

"Old" Radio: Niki v1.58.11.07, Kaiser 1.58.26.20, and Kaiser 1.64.08.21 all had sound until I answered the first call. Then no sound during and after the very first call (2-way). AAAAHHH!!! It's even worse! Every Bluetooth on/off and vibrate/sound combination had no sound during and after first call.

"New" Radio: Kaiser 1.65.14.06 and Kaiser 1.71.09.01 fortunately don't have the horrific problems of earlier radios mentioned in #2, but still have no sound problem with my vibrate/Bluetooth/answer steps mentioned in earlier post.

HardSPL: Hate to disappoint, but both HardSPL 3.56 and old OliPof's 1.0 cause the no sound issue on all radios listed above. I don't think it's SPL anyway. SPL is just the initial boot loader and is the bare minimum required to start the phone and load the ROM (like a super stripped-down BIOS on a computer). Maybe it causes the problem, but I seriously doubt it.

And BTW, my Bluetooth hands-free still has sound even when I have the no sound problem on my phone. Interesting, as it shows audio is not completely dead. Haven't tested A2DP--might check that tomorrow.

So, this doesn't seem to be ROM, app, radio, or SPL specific, although it could be a bug introduced in WM6.1 or its new radios. I think many of us are in agreement on that or are at least highly suspicious. The question is, how do we find it and/or fix it? I used to do debugging and reverse-engineering (and a little cracking) on Windows with tools like SoftICE and IDA Pro, but I've never done development on WM and I don't think there are even any dissemblers like those for WM that can actively debug a device. If you know of any, let me know. MAYBE (note the big "maybe") I can uncover more information about the problem with a debugger, but I'm long out of practice and don't anything about ARM registers and stacks.

The only thing I can think to do at this point is to see if there are any other WM6.1 devices that have this problem, especially the Polaris and Nike/Niki whose radios we can share. Maybe we're not the only WM6.1 device having this problem? If anyone finds anything about a similar problem with other WM6.1 devices, let us know. Otherwise, I'll post in those forums to fish for similarly afflicted souls.
[Tilt, TyTN II, MDA Vario III General] denco7:
It is also happening to the Touch Pros and Fuzes.

That is why I can't believe it is hardware. Has to be 6.1 but why not everyone ?

http://xdaforums.com/showthread.php?t=422322&highlight=sound+calls

And the Diamond

http://xdaforums.com/showthread.php?t=421478
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Reproduce at will?

Ben,

How do you get it to reproduce???? :confused:

I have been trying for 72 hours to get this to happen again by using every combination of Bluetooth on-off, calls in, calls out, MP3 playing via Bluetooth, GPS on-off, data connection on-off, and I have not had the problem once since the SPL flash to 3.56. I've taken calls from other cellular providers and I've made calls to other cellular providers and the phone still works. I did start off with no vibration on the ringer and added it about 36 hours ago and that hasn't caused it to happen either.

The only thing I haven't done that I usually do is travel extensively since I've had a 5 day break from work. I'll do that this weekend and let you know what I find out.

Man this is frustrating me that we can't find a solution that works for everyone except to revert back to 6.0.

Is there something (registry, something else?) that I can email you to allow a comparison?
[Tilt, TyTN II, MDA Vario III General] nikagl:
Hey guys,

I've been using the 6.0 rom happily for many days now, and I really wonder why you stick to using 6.1 when we have a very good feeling it's solved in 6.0. Should we start the discussion why to stick to 6.1 or not?

Here's two reasons:

1. You really, really, really like the OPAL dialer - so far that's the only item I couldn't get going afaik

2. For fun you like to get new ROMs all the time, possibly having a bit (hardly noticable) more speed and/or RAM, or are "lazy" to figure out how to get your favorite apps installed (using cabs) on the WM6.0 ROM (which I can understand, cooks do a very good job getting everything you need, and therefore the "laziness" can save you much time!!)

3. You're happy with your ROM and don't want to spend time installing another one (but will spend time trying to figure out what causes this and/or you accept silent calls and in my case angry wife's ;))

Anything else?

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
A Nugget....

From the Raphael forum:

<<I'm having this problem only if the 3G icon is on. How about you guys?>>

That is one thing I have NOT been able to test. I only have Edge at home and have the phone set to use HSPDA when I can get it on the road.

Ben, if you have the ability to check this as the cause as they might be on to something. I'm not certain about my past usage, but it is entirely possible that the times this has happened in my home Edge environment is after coming back from a 3G environment....

Food for thought....

:::UPDATE:::

If somebody still having the problem can try this, it might help us find the problem.

When the "silent" call happens, open the music player and play a song. On the Touch, it seems to restore sound without doing a full soft reset. I'd be interested to know if this "fix" works on a Kaiser.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Well, here's my answers to your questions!

1. Hopefully I can find another finger friendly dialer that works with 6.0 and doesn't have a video call icon if I have to go back.

2. I enjoy flashing, but not that much. I was on stock AT&T and I prefer a cleaner ROM and found it with eOS....but....

3. I love the ROM and configuration I've got, so that is why I'm trying to find a fix for it. But yes, if it fails when I travel this weekend, next week I'm finding a clean 6.0, UC compliant ROM and starting the flashing process to avoid the wife's anger! Maybe Touch/Raphael folks will find a solution and I'll be able to flash again.... ;)

Thanks for you contributions to the thread!
[Tilt, TyTN II, MDA Vario III General] nikagl:
I've had my issues with both 3G (UMTS/HSDPA) and EDGE/GPRS...
[Tilt, TyTN II, MDA Vario III General] denco7:
As have I.

Will Manila2D work with 6.0 ? I have no love for 6.1, although my phone ( aside from the obvious ) is running so fast, smooth and bug free with HD III, I really really like my phone now.

Maybe Sakajati will cook us all a special HD II 6.0 rom.

Question ? How did we all upgrade to 6.1 ?

1. From an oem 6.0 to an oem 6.1 ?

2. From a cooked 6.0 to a cooked 6.1 ?

3. From a oem 6.0 to a cooked 6.1 ?

4. From a cooked 6.0 to an oem 6.1 ?

I went from a stock AT$T 6.0 to the stock AT$T 6.1 upgrade ( problem started ) to HD III rom.
[Tilt, TyTN II, MDA Vario III General] nikagl:
Yes, it does - I have installed the cab provided in the Manilla2D thread (v20 + update v21).

My phone is an original HTC TyTN II (no Tilt), upgrade to cooked 6.0 (many different ROMs), later on cooked 6.1 (many different ROMs). Never tried the stock 6.1...

(I ROM updated almost bi-weekly, bought the phone in sept 2007 when it was released here in NL)
[Tilt, TyTN II, MDA Vario III General] denco7:
So we have

1 Stock 6.0 to Stock 6.1 = problem

1 cooked 6.0 to cooked 6.1 = problem
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Darnit!!

The problem finally recurred this afternoon.... :mad:

Make it two OEM 6.0 to OEM 6.1 for the original upgrade.

Didn't notice the problem until after flashing Hyperdragon III Manila.

Flashed eOS after Hyperdragon III.

Anybody recommend clean, UC compliant 6.0 ROM like the eOS 6.1? :D I guess I'll be updating my UC script and doing an downgrade.

I've got Nika's threaded SMS recommendation. I'm also looking for a finger friendly phone skin that doesn't have the video call icon.

I wonder if the Diamond Comm Manger is 6.0 compliant? I wasn't looking forward to flashing 6.0...but I don't see a choice right now. :(
[Tilt, TyTN II, MDA Vario III General] denco7:
So now we have

1 Stock rom 6.0 to Stock rom 6.1 = problem

1 cooked rom 6.0 to cooked rom 6.1 = problem

1 Stock rom 6.0 to Stock rom 6.1 = ? to cooked rom 6.1 = problem

I see a pattern here ( no pattern )

Anyone else?
[Tilt, TyTN II, MDA Vario III General] BennTech:
Got some news...second one's kinda funny.

First, I read the links denco7 provided, and the Diamond one is a different issue, but the Raphael "Intermittent problem with sound during phonecalls" is definitely the same. However, they're inclined to believe it is a hardware problem, while we think it's a software bug because we have a working WM6 base to fall back on, while they're stuck with the [allegedly] buggy WM6.1.

Second, I tested the supposed media player fix, and it doesn't work. (I think I actually tried that long ago.) I tried using 3 different players: WMP, MortPlayer, and Pocket Music, all with and without A2DP. BTW, A2DP does have sound even when the no sound problem is present, but it doesn't restore sound on the phone.

This is what's funny--while trying to test, I couldn't get my sound to fail again. I tried and tried but always had sound. (What a great predicament!) Finally, I soft-reset my phone and I got it to fail again, which is the same thing I had to do earlier when I mentioned in my 3-step failure post that I had problems getting it to fail. Yes, twice now I had working sound and had to soft-reset to get it to fail again! LOL...the things I do for hacking. Which brings me to my last topic...

Nika! What blasphemy! That goes against XDA hacking! This is the kind of puzzle that gives keeps us hackers up all night tinkering and tweaking. Just the very fact that we flashed to WM6.1 implies we like hacking our phones. For shame Nika! :)

Seriously, I'm about ready to give up, too, and go back to WM6. I was anxious to update to WM6.1 because it supposedly included a plethora of Bluetooth fixes. But, alas, WM6.1 Bluetooth is just as crappy as ever, disconnecting after every hands-free call, taking a minute or 2 to reconnect, locking my phone with 100% CPU usage at every connect or disconnect, failing to connect A2DP on my Parrot automatically, etc., just like it did back on my WM5 Wizard and WM6 Kaiser. Not to mention that WM6.1 broke my Destinator app, and thus I have no working mapping software.

I'm with you Nika. I don't see any compelling reason to keep WM6.1.
[Tilt, TyTN II, MDA Vario III General] BennTech:
Maybe you're in the same ironic situation I mentioned in the post above when I couldn't get mine to fail. If I cannot get it to fail, then I just soft-reset, and then follow my 3 steps:

Vibrate.

Bluetooth handsfree.

Answer call.

Fails like a charm! :) Oops...I mean :mad:

I don't think your registry will be of any help, but thanks for the offer. I dumped my registry like a madman while testing and didn't find any useful differences among all the dumps.

I really think it's some behind-the-scenes system app crashing. If we could find which one, we could write an app or script to restart it. My big fear is that it's some low level WM6.1 kernel or radio kernel code that we don't even have access to or that will be damn near impossible to debug.

Actually, in writing this, I've got an idea. I think I'll get it to fail again, then try restarting devices and services in DotFred's Task Manager. If I can find one that restores sound, maybe I can write a script to automatically restart it. Plus, that would give us the source of the problem & make it easier to debug/hack. Sweet! Now I'm excited again instead of to the point of giving up. Give me a few days to test this out.
[Tilt, TyTN II, MDA Vario III General] nikagl:
Currently I use the first stock ROM available for download, but from the past I remember Dutty's ROMs to be the best there were. Not sure whether they're UC-complient because it wasn't used that much at that time...

I use the Nadavi & Dutty DualTouch dialer, but that has the video button (which I do not use either, but nevertheless - it's there). The dialer is just as good as the Opal dialer, just doesn't have the slide to lock/unlock feature. Not sure whether there's another one...though I remember the first (other than default) dialers to all be without the video button...

Yes, I have used it, although I now use the Blue dialer included with the M2D pack (v20). Here's the thread:

http://xdaforums.com/showthread.php?t=398173

ROFLMAO! I must say I can only totally agree with you - it is blasphemy, but I've spent so much time (starting way before discussing it in this thread) trying to figure out the reason, that I am now really out of options within the knowledge I have.

I must say that's one of the few things I haven't tried yet!! Sounds like a good thing to try, though my phone works like a charm now, and I can't reproduce it ;). Maybe sometime I will upgrade again, and check it out unless you guys can...

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] swanlm:
Bluetooth audio gateway the culprit?

Has anyone considered trying the see whether the bluetooth audio gateway is the problem? I get the feeling that the audio gateway software is muting the phone speaker and mic to transfer the call to the bluetooth device and then when the call finishes, muting the bluetooth device to return sound to phone but somehow not getting that right. It then ends up in a situation whether both the phone and the bluetooth device are muted. (Well that's a theory anyway). If there was a way to query to status of the audio gateway software, we might be able to check whether this was the issue. I'll hunt around.

I have, however, tried both the gw software that comes with MSVC and the OEM software but get the same issue. So it could be in the interaction with the driver.

Cheers.

EDIT Found this which might be useful http://xdaforums.com/showthread.php?t=459014.
[Tilt, TyTN II, MDA Vario III General] qps:
Hello Huys,

I have been reading this thread for a while and also other threads according to this problem. I have same problems on my HTC TYTN II.

Maybe there are some sort of other facts that cause the problem we never thought of. I have been wtching my device for quite a while and also made some experiments.

What I can say is:

1. notice)

I tried several ROMs, no changes in NSI (No Sound Issue).

What I noticed was, whenever I loaded a new ROM to test, the NSI first does not come up. The longer I use the ROM, the more often the NSI appeared.

2. notice)

First time the NSI occured my PDA securitysettings were set to 1 minute (settings / lock or password (just know the german version: EINSTELLUNGEN/SPERRE)) There you can set the timeout for locking the device from 0, 1, 5, ... minutes. Thats the timeout for not using the device and locking device with 4 digit password.

Since I changed the setting from 1 minute to 5 minutes I noticed that the NSI came up less. Maybe there is something according to the lock setting and NSI. My old PDA (HTC Blue Angel) had almost similar problems with that lock setting. Whenever I received a call and did not immediately entered the password, after the call the device hung up and could not be unlocked anymore. only reset helped....

So I presume, that maybe this locking function has to do with our NSI. Maybe when a call comes in and device is locked the bluetoothdevice unlock the phone but not the sound or something like this....

I will report on my further trials.. I will try to set the intervall higher...
[Tilt, TyTN II, MDA Vario III General] nikagl:
I had my phone on lock after 1 minute for a week or so, after my WM6.0 downgrade and haven't had the NSI. Then I added S2U2 and stopped using it. And still have no NSI ;)
[Tilt, TyTN II, MDA Vario III General] nikagl:
Yes, that's why I mentioned in post 99 that I used VJVolubis to turn it off again as it seemed to cause an issue...
[Tilt, TyTN II, MDA Vario III General] swanlm:
So did turning it off reenable sound when the bug was in effect or did you turn it off as a precaution before the bug hit because it was causing issues?

I've been trolling through the MSDN archives about bluetooth and if i was a programmer I might be able to test some of the settings. It would be really good to be able to query the state of the phone when the bug is in effect (and I don't think the registry is the place to look).
[Tilt, TyTN II, MDA Vario III General] nikagl:
I turned it off because I had the bug as a precaution only, not while having it... I'll turn it on again, and wait till I have the bug and try turning it on. I think it doesn't do much btw (only change some registry settings), I'll check that too...
[Tilt, TyTN II, MDA Vario III General] denco7:
Just to once again relay my history.

Started after I upgraded to AT$T 6.1 , after flashing to HD III to try to get rid of problem, problem was immediately back.

And I have never, since I bought it , locked it or passworded it.

Nor have I ever used a bluetooth headset. One would think that there was a commonality to all our phones, which is why I figured , maybe an informal poll could maybe find a pattern from how we all upgraded.

Obviously the link is 6.1, no NSI before upgrade, no NSI after downgrade, NSI when upgrade to 6.1. Now we need to identify , why our phones and not everyone's ?
[Tilt, TyTN II, MDA Vario III General] nikagl:
Hmmm...polling... maybe try to summarize our issues and usage using something like excel? See attached. My suggestion: modify attached, zip it and repost it for the next one to modify it, etc. If we get doubleposts, I'll copy/paste the data. If you have something else to add, please feel free :)
[Tilt, TyTN II, MDA Vario III General] qps:
ok, also turned off password lock, but NSI occured though.

what is that pollin zip about? I tried to read back the whole thread, but somehow I did not get what that polling thing is about...
[Tilt, TyTN II, MDA Vario III General] nikagl:
I added the polling zip to try to figure out what features people are using and which may be causing the issue. Some people don't even use BlueTooth and have the NSI, and in other cases it's 100% reproducible with some kind of action in combination with BlueTooth (like for me).
[Tilt, TyTN II, MDA Vario III General] qps:
modified the excel for easier adding entries :-) and created comment tags in the certain cells its easier to red the table, for details to the cells you can move the mouse over the red edges.

to create comments just rightclick cell and click add comment

hope this is ok with you...

i also came across a second thread here: http://xdaforums.com/showthread.php?t=352906&page=3

I think this one might be interesting too. espacially on page 3 there are two mentioned possible situations how we can reproduce the issu or what it could be:

1) HTC Home Plug In

2) Volume Control/ Notification Applet

I am not through all posts of that thread (now on page 6) , but i will report if I do find out anything further...

qps

edit: furtheron I found out something interesting and maybe usefull:

- when restarting device yesterday morning and connecting to BT headset, I left them both on table. Till this morning there were no incoming calls nor did I used the device. -- NO NSI up to now!

- last past 30 minutes I made some testcalls with BT or without voicedial, calling from landline, making outgoing calls from device etc... suddenly the NSI occured!

So somehow the NSI only occurs when making calls in certain circumstances. I have to figure out when exectly...
[Tilt, TyTN II, MDA Vario III General] nikagl:
The puzzle continues. I've added my radio to the excel (nice modifications, gps! :)). Furthermore some more comments from my side:

* I've tried soooo many different radio's from niki, polaris and kaiser, and none of them worked with wm6.1

* I've turned on audio gateway. No the funny thing that happens when I turn on my nav-system all sounds on my phone go through the nav (for instance the alarm sound, or simple clicking on the screen). After the first call, that stops... no NSI so far

* When I check I often use voicemail because I don't bug anyone with my problem. With calls less than about 15 seconds I can immediately call voicemail again and listen to my messages through the nav. With calls longer than 15 seconds, I need to turn off/on BlueTooth or my sound will be on the phone instead of on my nav (ie. no hands-free-calling).

Just giving all these comments because eventually we may see somekind of red-thread through this all (I now only see one: we all have strange issues with the phones!!).

Oh...suddenly remembered one more comment: If I use my Nokia with the nav, I have none of these issues at all...

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] denco7:
I think that both of those are separate issues . They have to do with Phone volume and volume controls. I have no problem with my volume controls.

The phone rings at properly set volume. It is just the call that is silent.All the notifications work, email sounds, SMS sounds ,alarm, all work properly, before and after silent calls.

I have never had a silent call and looked at the volume control and found it changed,nor after a soft reset to remedy a silent call have I found the Vol. changed.

Even after a silent call episode, after I hang up, all phone functions are normal, incoming calls still ring and vibrate. Only abnormal is no sound when I answer (even though phone shows connected) and no sound on outgoing calls (dialing sounds included ) even though phone shows call went through and is connected.