yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flapjack:
It's definitely not related to MSVC, as the L26 V9 ROM doesn't have it. I DO, however, think it's related to BT. I ran the phone for 2-3 hours w/o adding my earpiece. BT was on, but no devices were paired. I had zero problems.

I added the earpiece and within a minute or so the ringer volume was set to 0, and the phone volume was set to 50% or so (I usually leave both on 80%). I switched it to vibrate. 5 minutes later, I got a call. I was expecting a vibration, not a 100% volume blast. I forced it to vibrate. A few minutes later, it was set to 40/0 again. No vibrate.

This is absolutely insane. I'm going back to WM6.0.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] commissionerg:
Yeah excuse my french but this **** is really starting to piss me off. I keep missing important business calls, if not I have to keep freakin checking my phone to make sure.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flapjack:
Yeah. It's funny that the hands-down, most irritating POS bug in WM61 is being ignored by cooks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gman8966:
Yeah, there's no doubt in my mind its related to bluetooth, when I have it off, it has never happened.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] btprice2001:
This isn't just a wm6.1 problem; I definitely had this issue with the HTC official wm6.0 rom.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lwizard:
Not related to BT!

No. I'm sorry but is not BT foult!

BT make the thing happens more frequently, but

for example now i have turned off BT, i set the tytn II on vibrate.

Than someone called me, i didn't answer.

After finished vibrating, the phone turned to sound on with volume zero as the usual bug!

Regarding WM 6.0, i had the bug too, but it was different:

sometimes the wheel in the upper left of the device was blocked on controlling volume even from the today screen, so putting the device away resulted in lowering the sound to zero, but it was a different bug and it happened seldom. Now it doesn't happen anymore in 6.1, but the new bug is much worst!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flapjack:
I had the problem with a few older Dutty ROMs, but none since. I just switched back to Q-Mobile 1.2 (WM6.0) on Thursday. I've been using my phone like crazy, and haven't had the volume bug once.

I miss threaded messaging and the ability to use the 1.65.20.29 radio, but it's worth it. The volume bug was so frustrating and annoying, it totally negated the benefits of the newer ROMs.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lcohen999:
The Official, my phone goes to silent mode with some bluetooth devices thread

As some of you know, there is a very annoying bug which I think only exists in 6.1 ROMS.

On/during/before or after a call, the phone could be on normal or vibrate, it will change to Silent.

At the same time, the volume for calls will be set to 0, so even if you change it to normal, it will occur again.

I am hoping people can help populate this thread and soon change it to solved.

I do not think it is ROM dependent as this bug happened from TNT's rom, through Dutty's and up to the new V9.

I have tried both a 1.58 and 1.65 radio.

It only happens when connected to my Audi Bluetooth handsfree.

Can anyone else report their findings and/or solutions?

Thank you
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] thomassster:
you use MSVC?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
No issues here with my Motorola T505 Bluetooth Speaker

http://direct.motorola.com/hellomoto/t505/
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Melkor:
Same here with my Motorola S9!

I can not reconstruct the bug but I think it happens when I shut down Bluetooth at my Kaiser and then it is mute...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kyphur:
I've experienced thsi behavior using the following headsets:

Jawbone (ver 2)

Motorola H700

Jabra BT8010

In fact I'm currently running WM6.0 Rom (XDA Live 1.5) on my spare with the Jawbone just to see if I'm going to return it or revert back to WM6.0

IMHO, WM6.1 is a huge step backwards in the BT Stack. They try to manage too much automatically and it has simply become unusable.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] curwiler:
I have seen this both on my Wizard (various TNT 6.1 ROMs) and now on my Tilt (currently running ROMeOS v2.3). I am using a Sony DS980 headset and a Parrot MK6000 carkit. When either of these devices disconnect, I see the "speaker" icon at the top change to X, showing silent mode has come on. At least on my Wizard that meant after disconnecting my headset or leaving my car, I would never hear the phone ring unless I manually adjusted the volume. I can't say I know for sure this is also true on my Tilt, but the icon at least changes.

Also, during the call I see it go to X, but the volume is fine. Changing the volume doesn't affect the icon, either, it still shows X during the call.

I do not use MSVC, or Cyberon for that matter, and neither are installed on my current ROM.

I do use A2DP as well as the handsfree on both of my bluetooth devices.

On older WM ROMs that I used on my Wizard, the volume used to be restored to the pre-bluetooth connection level. I didn't have the stock ROM on my tilt long enough to comment. :)

I wonder if anyone with a stock WM 6.1 device (not a leaked ROM, either) sees this issue??
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lcohen999:
Confirmed on not using MSVC...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Melkor:
I tried to reconstruct the bug but i can't reconstruct

Then I remembered that my ROM - Laurentius V9 - is using the new Diamond Bluetooth Stack.

If your signatures are right - none of you use this one!

Perhaps that is the solution for the bug? The new stack?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gman8966:
There is a thread that covers this exact problem. It has been pretty active lately...but no solution.

MOD Edit: Merged the two threads
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lcohen999:
Running V9, no difference
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kyphur:
I think tonight I'll recook XDA Live 3.0 (WM 6.1 Rom) using the WM6.0 BT Stack and see if that resolves my issues.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lcohen999:
We await with bated breath :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] PsiDOC:
Just found this thread whilst meandering by. This problem has happened to me a few times after I updated to hard SPL 3.29 when using the original WM6 rom on my phone.

Just my happening. Perhaps it's help.

Psi
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jdmba:
Out of curiosity, do you use VibraSwitch? I do, and it was my "volume at 0" problem.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kyphur:
I've experienced it both with & without VibraSwitch enabled.

So far today I haven't had it happen once and I've been running my WM6.0 XDA Live 1.5 Rom with VibraSwitch installed and bluetooth active.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rkrasny:
I've experienced this with many 6.1 cooked ROMs. I do have VibraSwitch and MSVC as well as BT (jawbone2).

I have tried to workaround this with setting the "incoming call" notification to "Vibrate and ring" - this usually causes one long, continuous vibration when the volume is inadvertently set to 0, but at least I have a chance of hearing it and picking up the phone.

RK
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] PsiDOC:
No never used Vibraswitch.

Psi
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jeepville:
I had the same problem with rynccpr v5

v6 seems ok so far.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jym04:
I own a Kaiser, using Dutty's Diamond ROM (Ok, sorry, dont know exactly which version, but I think it's his last ROM).

I experience this behavior almost everytime I try to turn AD2P on through my car handsfree. At least its less of a problem for me because I notice when it happens: it doesn't make the ad2p connect sound (don't know if its from WM or the Car Kit, since it is my only bluetooth device).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] benkus83:
Hi everyone - this is my first post but I have been reading and flashing my Kaiser since I got it in december. It is fantastic to see the effort everyone puts into these forums.

This is not a solution to the bug, but it may help. I use SPB Phone suite to control my profiles. You can download a free 15 day trial version which is fine if you are flashing a new rom all the time like me. Unless you have a full version.....

http://www.spbsoftwarehouse.com/products/phonesuite/?en

I have several profiles set up i.e.

'Loud' sound at 100%

'Normal' sound at 60%

'Quiet' sound at 20% - vibrate first then ring (useful at work)

'Vibrate' - vibrate

'Silent' - well... silent

'car' - Loudest settings - no vibration (in car holder for TomTom)

'night' - sound at 40% - Notify for calls only (no sms or emails)

You can set rules to control the profiles automatically ie:

Rule 1 - default profile = normal. (for when no other rules apply)

Rule 2 - If the time is between 10pm and 5am (ie night) & the phone is plugged into phone charger then activate night profile which is quiet and only notifies me if someone calls.

Rule 3 - If the time is between 8am and 5pm (ie work) & the phone is plugged into usb PC charger then activate quiet profile which is will vibrate first before ringing at 20% volume.

Rule 4 - Silent - when an appointment is set to busy activate silent.

Rule 5 - Vibrate - When an appointment is set to tentative activate vibrate.

Rule 6 - Car - When using car cradle - activate car.

It may sound a little difficult to set up but it is really very easy and only takes a few minutes as it is all laid out pretty well.

There are other features as well like turn on or off or adjust bluetooth, wifi, backlight, call filtering, cellular phone and auto answer in each profile but i dont really use this part.

It also has a pretty good today plug-in which is nice and compact as the HTC Home, as much as I like it takes up too much room. I prefer to see all my appointments all day long.

Anyway hope this may help some of you, plus saves effort of having to changes profiles throughout the day as it is all automatic.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] motocrossmann:
Same problem here. It happens ocassionally, and once I definately noticed it happened after disconnecting from my car's hands-free. Now I can't make it reliably occur, but I'm sure it will happen at an inopportune time. Perhaps it was coincidence???
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jdmba:
Well, for those who use VibraSwitch, and have it mapped to a PRESS-AND-HOLD button, it seems we have brought the volume-to-zero on ourselves.

In v1.2 of VibraSwitch the author put in a "feature" which sets the volume to zero if you hold the switch down for 1 second. Since press-and-hold is a longer hold, depending on how many nanoseconds you held it down, you would get caught by this "feature" and your volume would go to Zero.

I mention this to extricate those who have Vibraswitch mapped to a press-and-hold button from this analysis.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lwizard:
Petition

Since the bug is also present in the original HTC 6.1 rom update,

why not writing to HTC support to ask a solution?

Is there any cooker good enough to fix the problem?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aryehz2:
Unfortunately, I don't think HTC has "officially" released any 6.1 ROM yet so they wouldn't fix it. I could be wrong but I think everyone has just been using leaked and tweaked versions.

As far as a cooker good enough to fix it, I guess not.

What really drives me nuts about this is if it were really a 6.1 ROM issue, then there be alot more people with this problem?

A
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aryehz2:
BTW, I am still having the problem on the most recent leaked Sprint ROM
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lwizard:
??

There are two official 6.1 rom updates from HTC! (the latest has a different radio and i'm going to try it)

Otherwise i'll come back to WM 6.0
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Super Sheep:
I noticed this problem when using tomtom navigator, when I launch it in "vibrate" mode.

In the past I already noticed this issue with WM5 and TTN.

My workaround is : I don't launch tomtom when in vibrate mode ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bapssystupr3m3:
does anyone know if we can regdit so when we click the windows volume button it will bring up the profiles for spb phone suite?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aryehz2:
Really? Which ones are official? I'd love to try one also and see if it helps. Let us know how it goes.

A
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] chunkwok:
i think they do.... you can dl the 6.1 in htc web site.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asfoor:
I was able to duplicate the problem in the original post.... It has to do with a "Task manager" program that you had installed. Any task manager that resides its icon in the lower tray of the device will sometimes trigger the silent function, especially if you have increased the screen sensitivity.

My 2 cents...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lcohen999:
I am using pBar as my task manager

I will disable it on my way home and see what happens
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] drokkon:
My findings

Not sure this will help anyone, but I've been sitting here, staring at the sound profile of HTC Home and turning my BT headset (Jabra BT620s) on and off. It's obvious that connecting and disconnecting the headset is causing all of my problems.

Here are my findings. I've highlighted anything the phone did automatically in red. Whether or not this is desirable behavior is up to you.

EXPERIMENT 1 STEPS:

a. initial sound profile

(turn on headset, wait up to 30 seconds)

b. profile auto-changed to

(turn off headset, wait up to 30 seconds)

c. profile auto-changed to (wait up to 30 seconds)

EXPERIMENT 1 RESULTS:

1A

a. normal

b. silent

c. normal

1B

a. silent

b. silent (didn't change)

c. silent (didn't change)

1C

a. vibrate

b. vibrate (didn't change)

c. vibrate (didn't change)

EXPERIMENT 2 STEPS:

a. initial sound profile

(turn on headset, wait up to 30 seconds)

b. profile auto-changed to

c. manually changed profile to

(turn off headset, wait up to 30 seconds)

d. profile auto-changed to

EXPERIMENT 2 RESULTS:

2A

a. normal

b. silent

c. normal

d. normal (didn't change)

2B

a. normal

b. silent

c. vibrate

d. normal

2C

a. silent

b. silent (didn't change)

c. normal

d. silent

2D

a. silent

b. silent (didn't change)

c. vibrate

d. vibrate (didn't change)

2E

a. vibrate

b. vibrate (didn't change)

c. normal

d. silent

2F

a. vibrate

b. vibrate (didn't change)

c. silent

d. silent (didn't change)

Obviously there are some issues here, particularly when changing the profile while your headset is connected. Here are the scenarios which adversely affect me:

1A & 2B: Explains why I've been embarrassed at work multiple times when my phone rings and I'd sworn I put it on "vibrate" or "silent." My phone is on "normal" all night. I wake up, connect my headset, and talk to my girlfriend on the way to work. Then I set it to "vibrate" for the work hours. However, if I ever turn my headset off or wander too far away from it (for meetings), my phone automatically turns back to "normal." Crappy.

2C & 2E: Explains why I miss so many calls when my phone sets itself to "silent" after I've sworn I've set it to "normal." I'll start out in "silent" or "vibrate" (again, often because I'm at work), turn on my headset (to make some calls after work), and decide I want my phone volume to be on and set the profile to "normal." Now if I turn off my headset or wander too far from it, my phone automatically silences itself. Also crappy.

So maybe we already knew all this, but I thought I'd share. Either corroborate my results or slam me for redundancy, but this behavior is 100% reproducible on my Tilt with my Jabra headset. Whether or not it's by design, I'm not sure, but it bugs ME. I can confirm that my ROM doesn't have MSVC installed nor any other phone profile program like SPB Suite or something.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flapjack:
I experience exactly what you've described here. It doesn't matter if I'm using HTC or SPB, it happens just the same. The nice thing about SPB, is you can look at the speaker icon and if there has been an "unauthorized" change in volume, there will be a yellow asterisk on the icon.

I'm thinking of trying this ROM to see if the volume bug happens. Something tells me it has to do with HTC. This did happen with WM6.0 ROMs, just not as often. Dutty's were especially susceptible. The Q-Mobile ROM has no HTC whatsoever. Maybe that's why I don't have the volume bug on it.

http://xdaforums.com/showthread.php?t=405897
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
Having the same problem with a Jawbone and 100% agree that it BT related. I still get sound over the headset, just not the phone, no matter how I adjust the volume setting, turning on and of the BT, or anything else. Let us know whether Gullum's ROM has the issue. I've read most of the thread and didn't see anything. ThrottleLauncher looks cool too. Seems like there are other issues that might make that ROM less desirable, but hell, I've missed 3 business calls today alone. And I'm on my 4th SR!!! Thank God that Death boots quickly! :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
any progress?

just thought I'd get this back on th radar screen . . . .
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flapjack:
Flashed to the new Gullum ROM two days back. Have seen the volume bug occur once. That could be something I did, though. I'm going back to Q-Mobile 1.2 for other reasons, but I'll stick with this ROM one more day to try and verify the bug.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flapjack:
After a few days of testing, I can confirm the new gullum throttle rom has the bug as well. Unless HTC is still buried in that ROM somewhere, it's not an HTC thing. I really think this actually has something to do with the MS code in WM61. It would occasionally happen in pre-WM61 ROMs, but it was sporadic and limited to specific ROMs. In those cases, it probably had something to do with other possible causes people have posted (TomTom, Vibraswitch, inproperly configured programs, etc...). This definitely has something to do with bluetooth headsets connecting and disconnecting. I do not get the problem if my headset hasn't been paired. I'd even go so far as to guess that turning BT off would solve the issue temporarily. Wearing your headset 100% of the time is also a workaround, as my phone always sounds there, even if the phone's ringer volume has been dropped to zero.

Didn't know about the other thread. Thanks for the merge.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
BUMP . . . Bump . . .Bump

Just thought I'd get this back on the radar screen. Seems like a common problem so maybe with the ROMS being updated to include the new video drivers, this can be revisited.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] LimDul:
I have no idea what causes this bug, but it happended from time to time with the original rom and all other roms I ever flashed except the last one(L26_V9) I did not experience this when I used PointUI (regardles of ROM). I have no idea if the L26_V9 does not have this bug, or I'm just lucky with it. I started using my Kaiser as a mp3 player at about the same time I flashed V9, I don't know if that can be related, but who knows.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flapjack:
I'm pretty sure I've tried V9 and experienced the bug.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
Confirmed. Bug present on L26 V9. Using it right now for OTHER issues I couldn't resolve on Death v4. :( Not bad actually, but not the DEATH either . . .

maybe the new DK can fix it. Posted there moments ago. . .
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] LimDul:
I don't think this bug is ROM related, but it seems some programs that deal with sound can prevent it from happening. For me it was PointUI (switching profiles with it never caused this) and now it can be the latest HTC AudioManager. I remember that one of the older versions started with no sound once, but this one did not (yet maybye).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lcohen999:
anyone a good mortscript programmer

maybe someone can write a quick and dirty program which will fix the volume issue, when it arrises...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gman8966:
I use SPB mobile shell and this problem still happens to me, it is very weird. Whenever I am using bluetooth I always initiate it with my headset, make the call, and end it with the headset, sometimes the volume will drop to zero other times it will not. I know in the past I have heard people who use mobile shell don't have this happening to them.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] LimDul:
I do not use BT headsets and it still happened from time to time after swithich from vibrate to ring profile. Now it did not happen for a very long time, I have no idea why. My only guess is the AudioManager. When I am at work i have víbration profile on and when i go home i swith to ring and listen to music. Volume is ok in this case.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
This consistently only happens to me when I initiate my BT headset. Random, but it eventually happens at some point after no matter what. I think someone with a much better undertanding of the BT stacks needs to rip it apart and see what could be doing this.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jhego:
It happens to me too, when i constantly switch from vibrate to normal. I have the vibra switch mapped to PTT for easy access. I also have L26 V9.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
well this could be a weird link. While I don't have the PTT specifically linked to BT, I do have it linked to MSVC, which is what I primarily access using my BT. To clarify when not using my BT, I use the PTT to start MSVC. Maybe the connection lies with accessing a function that is in some way assigned to the PTT, even if not actually pressing the PPT.

Thoughts?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lcohen999:
It has nothing to do with anything but the 6.1 radios and the way they interact with the ROMs, bluetooth drivers specifically.

It isn't a MSVC, or PPTP, it is more low level than that.

I bet you could find the most naked ROM out there, the bug will still be there...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] laakness:
From the odd behavior I have seen I'd have to agree. I get this occasionally but when it does happen it is typically after using the BT headset. I have disabled MSVC and it still happens.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] thedogger:
I didn't have this problem for several days on the following config:

SPL 3.56, Dutty 24MB WM6.1 Hybrid ROM, Radio 1.58.16.27

Then I added SPB Time 2.2.2.

Within about 20 minutes, I got the drop to zero on ringer volume thing. I uninstalled SPB Time, and haven't seen the issue for another 2 days. I regularly use a bluetooth headset and MS Voice command v1.6.19209.

Maybe coincidence. Maybe not. I'll keep watching for it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] laakness:
Interesting...I have SPB Time installed.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
maybe there is something that eliminates it through the hybrid? That ROM has gone down as one of the most stable/bug free ones out there. maybe it's time to go back. . . . hmmm . . .