yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] John Charles:
Hi Folks

Have been reading this thread with interest, having had the same problem, couple of points:

1. I'm very

very

new to this, got second hand tytn 2 three days ago, no previous experience

2. I've flashed WM6 onto the phone now and I'm having no problem whatsoever

However thought the description of what happened to me might be useful for you clever fellows.

Bought phone second hand, it came locked so I paid a shop to unlock it, when I tested it the unlock had worked but the no sound issue started almost immediately. I checked with the previous owner, he stated it hadn't been an issue before, true/false? No idea but it could have been a knock in the post or something in the unlcok process that started it so had to take it on faith.

My no sound issue was relentlessly consistent, when it happened the phone made no noise at all until a soft re-set. Things that caused it were:

1. I make one phone call out, that call would connect and I could speak, once call ended no sound.

2. I receive one call with ringer on, ringer would ring I'd answer the call it would show connected but no sound.

3. I receive a call with phone set to silent, I could receive and connect, I could do this once more, then no sound.

4. Any kind of media file played would cause no sound (no sound would ever come out)

My initial (non-experienced) thoughts were either this is a software issue or it is some kind of circuit shorting issue. No idea if the hardware has trip switches for different cicuits, in this case the speaker circuit, but thought this might be a case of overloading and tripping out, hence soft restart re-set the trip.

However W6 has totally fixed the issue (so far) so probably is the software but I noticed one more thing. On WM6.1 when I played the game bubble breaker the sound of the bubbles popping was very high pitch, straining the speaker to the point I thought it might rip it, on WM6 however the sound seems to be far gentler and putting less pressure on the speaker so possibly WM6.1 articulating sound in such a way as to cause a hardware trip out?

Also in respect of other comments, I didn't have bluetooth on at all and was running HD 111 Blackstone

Hope this helps, keep up the good work
[Tilt, TyTN II, MDA Vario III General] qps:
EDIT: ok, I did checked this entire Thread again and I am not sure anymore, maybe I and some other guys are wrong in this thread?!?!?!

The correct title of this whole thread is "no sound in calls...." . I didnt red that correctly and when reading most parts of the threads I think the thread turned from "no sound in call" to "no ringing sound and sound at all when using Bluetooth"....

so if I am in the wrong thread, please excuse! And if some other guys are also mistaken, we should move to the other thread where the issue is:

Using Device + Bluetooth Headset, after while, there is no sound on whole device anymore, but incoming calls are visualy shown in device, BUT you can talk and make your calls via Bluetooth headset. The issue is, you wont get a sound ringing notification when a call is incoming, so you will miss your calls!

Please read my post carefully, I did not say, that NSI-1 and NSI-2 are sourcing out of one problem or that they go together.... What I wat to say is, some people in the thread explain their NSI-1 problem or bug, which is definitley another problem than NSI-2 is, and other poeple in the thread might explain their NSI2- bug. So we have to clearly figure out what we are talking about!

Your problem is a third one!!!

Your sound settings are correct and you definitely hear your ringsounds and other sounds, but if you do a call, you cant hear the other one on the other end of the line.... or vice versa. I think your problem is another to our NSI-2 or NSI-1 problem described here in the thread.
[Tilt, TyTN II, MDA Vario III General] BennTech:
Our thread started off describing no sound in a call (and ultimately discovered on the whole device) which could only be fixed by soft-reset, while the other thread started off describing the volume slider inexplicably setting to zero, which could be fixed by moving the slider. These very first posts are people are what people are going to read when looking for a thread about their problem.

Unfortunately, there seem to be several different sound issues or at least variations on these two, and many people with sound issues are confusing one for another. Those of us who know which problem we have will just have to deal with those posting who don't know or who have a different sound issue for which neither thread is completely accurate. Such is the nature of the web. Even so, I'll go ahead and be the one to post the obnoxious, attention-getting message...

Make sure you are in the correct thread!!!

Make sure you are in the correct thread!!!
​

Make sure you are in the correct thread!!!
​

"Unexplained volume drop to zero": If your volume sliders inexplicably set themselves to zero and you can (temporarily) fix your problem by adjusting your sliders, then you should go to the "Unexplained volume drop to zero" thread.

"No Sound in Call (Intermitant)": This thread (the one you're reading) originally started as no sound during calls for either party but also causes no sound on the entire PDA and for many no ring/vibrate. The volume sliders stay in their correct positions. It can only be fixed by a soft-reset. If this is your problem, stay here.

If you have both problems, sucks to be you, but welcome to both threads! :)

I think the overlap in the 2 threads might be adding confusion to the actual cause of each. These problems might be related, but for now let's keep them separate until we can determine the cause.
[Tilt, TyTN II, MDA Vario III General] BennTech:
NSI Services & Devices Restart Tests

Services & Devices Restart Tests

Holy crap y'all were busy while I was testing restarting services & devices. But as promised dozens of posts back, I tried restarting various services and devices after causing NSI. Long story short, nothing worked.

I couldn't find any sound services for WM, so I focused on devices:

ACM1: Audio Compression Manager (gsm610.acm)

ACM2: Audio Compression Manager wrapper (acmdwrap.dll)

DSP1: radio? (adsprtossvccore.dll)

RIL1: Radio Interface Layer (ril.dll)

SPK1: speaker driver (wavedev.dll)

WAM1: Waveform API (waveapi.dll)

WAV1: Wave device, tested with both wavedev.dll & SRS WOWHD driver

WAV8: Bluetooth A2DP, tested with both bta2dp.dll & SRS WOWHD driver

What's really interesting is that restarting DSP1 with working sound caused the NSI on the PDA, but phone calls still had sound. Likewise, restarting WAM1 caused NSI but broke volume slider for PDA (always reset itself to zero) although phone slider worked. Vibrate worked, but not audible rings. However, media players could play music through speaker, but that still didn't fix NSI or slider. Also, after restarting DSP1 or RIL1, the phone always locked up in less than a minute & had to soft-reset. Restarting WAV1 or WAV8 locked up phone at first attempt to play sound & had to soft-reset. ACM1, ACM2, and SPK1 appeared to have no effect on anything.

If You Have a Bluetooth Device...

If anyone has a Bluetooth hand-free device, please try to replicate the NSI with my 3 steps and report if you can cause it to fail. I seem to be the only person can reproduce NSI at will, and the more of us who can cause it to fail with specific steps, the more likely we can debug/troubleshoot and/or harass Microsoft/HTC to fix the issue. Again, the steps are:

Active vibrate.

Connect to Bluetooth hands-free.

Answer incoming call and stay connected for at least 1 minute (there is apparently a timing issue here as short calls don't always trigger NSI).

After call, you should have NSI, specifically no sound on PDA, no ringing or vibrate, no audio during calls (2-way). However, Bluetooth audio (both hands-free and A2DP) still work. At least, that's how it is for me. If you still have sound, then soft-reset and try steps 1-3 again.

Please post if you can or cannot replicate NSI using these steps, or post any other method you have discovered that can reliably reproduce NSI. Thanks!
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Exactly!

This is where I was at until I spent all day yesterday putting my phone into the configuration in my signature. :(

My wife is gonna kill me if I spend another day going back to 6.1 if we find a solution to this!! ;)

Now, unfortunately the shogunmark threaded SMS didn't work with my ROM. I got no notifications of SMS messages except for the icon.

So far, all the calls I have gotten are not NSI!!! :)
[Tilt, TyTN II, MDA Vario III General] qps:
ok, after confusing everyone, I decided to stay in this thread :-)

So my NSI-2 bug comes sporadic. I can't trigger it or reproduce it by benntech's way.

I tried:

1) set Volume sliders to vibrate

2) connect BT by opening COMM Manager and activation BT. (headset is on during this process)

3) answering incoming call via headset (press button on headset)

4) left call for 1:23 minutes

5) hang up call via button on headset

6) tried to move volume sliders, still audio.

edit: after softreset tried each step again, this time 4:23 min and hang up at landline first and left HTC closing automatically. Still sound, cant reproduce it that way...

But I can tell one more fact: its the second day (53 hours) now for my second device, since reset and connectiong BT headset and left both at my desk. Still no NSI. On the second device (identical headset and phone) after some trials with calls in and outgoing several times NSI, but still cant figure out how to reproduce it 100%. (Since I never used vibration-mode, it also has to be reproducable without vibrate setting )

PS: when NSI-2 occurs, i still can talk on calls or the other party can hear me! Only all sound like notifications for SMS or incoming ringing calls or mediaplayer sounds are muted, although volume sliders are full open. So no sound at device, but I can answer calls (if I see them on the display) and talk to the caller via headset.
[Tilt, TyTN II, MDA Vario III General] BennTech:
Here's my input to the NSI-Poll. Don't think it'll help much, but hey, I'm all outta ideas again.

I wish we could get someone involved who knows more about WM devices to debug. If not, I'll either (1) go back to WM6 and spend the next week tweaking & customizing, much the annoyance of my wife, or (2) find a WM debugger and spend the next several months researching WM hardware structure and drivers, writing some test apps, tracing through kernel functions with notes and scribblings scattered all over my desk and floor, and ultimately loosing all my clients and getting a divorce because I'm spending night and day on this. Besides that, if history is any indicator, I'll soon wash my phone in my clothes washer like I accidentally do every year or two, and be forced to upgrade, although by that time I'll be bankrupt and can't afford it.

I think #1 seems like the more sensible option, but the hacker in me is really drawn toward #2. Of course, if this is affecting other WM6.1 devices like the Raphael, there's no point in switching/upgrading phones. Furthermore, if it is common to WM6.1, we have to find the problem before Microsoft reuses the buggy code in WM6.2 or WM7. Damn it. Looks like divorce & bankruptcy for me...

Bummer. I was hoping this would be universal so we could harass Microsoft/HTC with reproducible steps. As a developer myself, I know this is key to getting developers to troubleshoot their code, otherwise it's just "stupid user error" or at best "unable to reproduce".

Just to clarify, when you have NSI but still have audio on calls, is this for both Bluetooth and the phone, or for Bluetooth only? For me, I have Bluetooth audio only; all other sound/vibrate on phone is broken.
[Tilt, TyTN II, MDA Vario III General] nikagl:
Wheweeeeee, that's some reading I had to do in only 8 hours of time away from my computer :)

I am definately in the right thread. Sorry to hear shogunmark didn't work for your ROM, I'll try with mine today (don't really care about threaded sms, and therefore didn't have it installed) - I know it worked fine in the past for most WM6.0 ROMs I tested...

Important note:

In my case, it happens with one BlueTooth device (my nav-system: JVC), but not with another device (my headset: Plantronics). I've often heard that BlueTooth is a difficult protocol and many devices use it differently and have different issues with them. My previous nav-system for instance, a Pioneer HD3BT (Z3 for the US ppl), had an issue with both WM6.0 and WM6.1 where it wouldn't connect in the first 3 seconds of a call (which is mostly the welcome-message on the other side).

I wish we'd have someone with some more knowledge of the BlueTooth-stack on board, that knows how to test and/or diagnose these issues...

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] qps:
when NSI occurs, I ONLY can make calls (either outgoing or incoming calls) via BLUETOOTH HEADSET. On my HTC device at that moment I can't hear any sort of sounds (no ringing, no Windows media player files, no sms notifications, no dialing pad sounds, ...)

If NSI occurs, only way to get notice of incoming call is to stare on display. If you are lucky you will notice an incoming call when display shows incoming call without any sound notification.

I also tried to uncheck HTC Home plug in and activate it again, but for me, no gaining back of sound. Only way: softreset.
[Tilt, TyTN II, MDA Vario III General] nikagl:
I wonder whether it's an HTC specific issue, did anyone see a similar issue on the Ericsson Experia?
[Tilt, TyTN II, MDA Vario III General] denco7:
Are the roms for the xperia X1 written by HTC or S/E ?
[Tilt, TyTN II, MDA Vario III General] BennTech:
Doh! Here's the NSI-Poll

Doh! Forgot to attach the NSI-Poll to my last post. Here it is.
[Tilt, TyTN II, MDA Vario III General] nikagl:
Did you change Settings -> Personal -> Sounds & Notifications -> Notifications -> Messaging: New Message (Palm....

In my case I had to change it into a sound that actually exists...

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] denco7:
Here is my poll no bluetooth headsets of any kind
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
NO! NO! NO!!!!!!

I just had NSI with a 6.0 ROM installed.

A friend called and I answered and absolutely no sound. I had my daughter call me as well and absolutely no sound. Rings, vibrations, and no sound in the call. Soft reset and daughter calls and it works OK.

I just wasted a day going back to 6.0. :mad:

Nika, no I didn't change the sound, but it looks like for me, I might as well go back to 6.1....
[Tilt, TyTN II, MDA Vario III General] nikagl:
Oh noooo!!! Only thing for you to test: take the same ROM as I have. It might still be a ROM thingy....check my sig...
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
I'll Give It a Shot

I guess Monday will be HTC ROM day with Tilt Keyboard fix installed. ;-)

Alex's V5.2 is AT&T based.... I wonder if that is the key? I've got the survey open, I'll post it in a little bit.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
jpcrailjr NSI Poll

Since I have to put some words in the post....

OK, where's the attachment?

After struggling with it not being a zip file....
[Tilt, TyTN II, MDA Vario III General] nikagl:
Afaik I've never used a AT&T ROM....(unless it was fully cleaned by a cook, I've never seen any AT&T apps)
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Originally

I used AT&T stock ROMs for a long time. Alex's were AT&T based, but I used the lite version which just had Office built in and some other really basic non-AT&T stuff in it. I took all the bloatware off my first stock AT&T ROM because I don't need all that useless stuff.

I like CLEAN ROMs that I can customize instead of having to rely on the chef cooking in the right stuff. Before this issue became paramount I was going to try to cook my own ROM, but no point in it until we can pinpoint a cause.
[Tilt, TyTN II, MDA Vario III General] Larstein:
My phone would not answer incoming calls, silent - then would usually freeze for about a minute, following call. After hours of "thread reading" I flashed Hard SPL 3.56 in place of the HardSPL 3.29 that was part of Hyperdragon III Rom.

Success!!! The first time in weeks the phone rings and I can answer it

__________________

Laura Stein
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Hope it works!

I don't want to rain on your parade, but I tried 3.56 and went about 72 hours without a problem and then.... :(

I would check and see if you have vibrate selected either as part of your ring or in "vibrate and then ring". If you don't you might be OK. I know once I selected vibrate as part of my ringer the problems seemed to start again.

Please keep us informed!
[Tilt, TyTN II, MDA Vario III General] Larstein:
I am getting my umbrella out...Just put it on vibrate, still works - but what I neglected to mention is that I have to use the "hard button" to answer - slider doesn't work.

I'll let you know if I have to use that umbrella!
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
For Benn: Doesn't Work

Now that I am on 6.0, I tried to use this method.

With the phone in vibrate, the Bluetooth would not work at all. I had to answer the phone. It worked just fine. I let the call run for 2+ minutes.

Turned off Bluetooth, called again and....the phone worked just fine.

I have to admit, this method you outline did NOT work in 6.1 either when I tried it, but I did not let the call run for over a minute.

I have never been able to reliably duplicate the circumstances that cause the problem.

I'm off to plug the phone in to charge and try again tomorrow....
[Tilt, TyTN II, MDA Vario III General] nikagl:
FYI, I still cannot reproduce. All works fine for me whatever I do. Only thing I have is that BlueTooth won't pickup the call if the previous call lasts longer than 30 seconds (tested this multiple times!!) with my nav-system (speaker phone on handset works though).

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] qps:
one more fact:

in the beginning I thought the NSI comes up somewhen.... but now I surely can say my second HTC device, that still rests beside the connected BT headset for over3 or 4 days now still has sound (no calls and sms were incoming or outgoing since then....), but my first HTC device, that I use frequently day by day has this NSI-2 thing several times since then now. So it must happen after a call, imo.

What I also can see is, when hanging up a call for about 2 or 3 seconds there is completely no sound on the device. I tested it that way, that I immediately tap on the Volume sliders on top within those 2 or 3 seconds after hanging up, and then move the sliders up or down. Usually the will make a tick-sound when moving around , but within 2 or 3 seconds after a call its muted, like the CPU is busy an can't playback or like the sliders had to switch back from the in-call slider (where it is only one slider for speakingvolume) to the twin sliders (device notifications and ringingvolume) Maybe the NSI-2 is a problem in switching back from in-call-slider to standards-sliders. Maybe the visual sliders switch back correctly, but not the softwaresidepart of the audiodevice? I know my description is not technician-like, but maybe just an idea to think of?!?!?

It's just what I could observe on my device, so I though it might be interesting to report.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Reproduction?

Benn,

I've had a night to consider your steps to reproduction of the problem.... Maybe I am doing something wrong.

Do you set the whole phone to vibrate via HTC Home or do you put the ringer to vibrate, vibrate and ring, vibrate and then ring, etc. via Phone Settings?

I'm getting set to flash the HTC ROM Nika has to make sure we have a ROM that we can can reliably go to to fix the problem, and then I'll probably flash back to a 6.1 ROM to see if I can help find a fix.

Thanks to everyone who is contributing on this thread. To quote a soon to be President of the United States: "Together we can".
[Tilt, TyTN II, MDA Vario III General] BennTech:
I don't use HTC Home. I use HomeScreen++ (aka BatteryStatus), which shows CPU% on the topbar under the clock (not as accurate as DotFred's Task Manager), and I set vibrate via either sliders or Vibra (set to long red button press). And yes, the phone locks up with 100% CPU usage for a few seconds after calls. If you have Bluetooth, it locks up with 100% CPU usage for 30-60 sec and mine usually disconnects from my Bluetooth Parrot MK6000, then reconnects again about 30-60 sec after that. (I know because my Parrot plays a connection tone on my car radio whenever it connects.) That's why you can't get calls via Bluetooth for a short time after a previous call ends--but you're right Nika, there's a timing issue for Bluetooth and the call has to be longer than 30 sec. This is one of those problems that I hoped all the supposed Bluetooth fixes in WM6.1 would fix. <sigh> :(

I just want to absolutely clear here in that I know I didn't have this NSI ever on WM6. I am positive WM6 will fix our NSI. HOWEVER (note the big "however"), I also know that I had the NSI from the other thread (Unexplained volume drop to zero, aka UEVD) on WM6. Happened to me a couple of times. It was annoying, but rare and easily fixed by resetting the sliders, so I never gave it much thought. I haven't had that problem on WM6.1, although I would gladly trade our NSI for that slider problem.

Good News?

But enough of that...on to (maybe) good news. I found out that there are many debuggers for Windows Mobile, and even kernel-level debuggers, which are going to be required for this. Now the bad news. I can't use an emulator on my PC since I need my actual phone for Bluetooth & incoming calls to reproduce the failure, so apparently I need to setup a remote debugger from my PC to phone, which means I need my phone tethered to my PC. However, I can only reproduce the issue in my car where my Bluetooth Parrot MK6000 is. So I need to (1) find a WM debugger, (2) figure out how remote kernel debugging on a WM device works, then (3) go sit in my car with my laptop, my Kaiser, and my house phone and (4) produce the NSI while (5) debugging millions of lines of ARM assembly language code for WM drivers that I know nothing about, and (6) repeating steps 3, 4, and 5 ad nauseam. The proverbial needle-in-a-haystack doesn't even come close.

I was half-joking when I said it would take me months and end in my divorce and bankruptcy, but that may have been more apt than I thought. Unless I'm extremely lucking in locating the bug, it really will take me months to track down--if I even can. I am long out of practice reversing & debugging, and I have never done WM programming or cooked a ROM, so I don't know what WM files do what and I don't know the hardware either (even to this day I still don't understand exactly why the PDA's sound and camera are affected by phone's radio ROM). So once/if I start this, I'll probably drop out of posting for quite some time. Don't expect miracles (and it will be a miracle if I find anything).
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Shoulda Woulda Coulda....

Darnit! I wish I'd have thought to look at the sliders before I soft reset when I had the problem on 6.0 yesterday. :o

I can't relate to the technical problems you face, but I CAN relate to the months and divorce issues. :D You've got my support brother!

PM me if you want my phone number. AT&T to AT&T calls are free and if the least I can do is give you a free number to call instead of wasting minutes or dragging your land line phone out to the car on this, then I'll gladly help out.
[Tilt, TyTN II, MDA Vario III General] BennTech:
Thanks for the offer, Jim, but I can only get the NSI when I answer incoming calls, and my house phone is wireless so it's easier to call myself than to call you to tell you to call me. :)

The biggest problem (besides trying to track down this bug) is what do I tell my wife when she comes home from work and asks what I did all day? That I sat in my car with my phone and laptop and called myself all day?