I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Atra said:
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Click to expand...
Click to collapse
What else do you have loaded on your phone(s) that have this issue. I use VC on all WM6 and WM5 roms that I've run (and ones I've cooked, like the Crossbow Reloaded ones you mentioned) and have never had this error and I've never tweaked around registry settings. I just install the cab and it works...
Are you installing VC 1.6 US?
With all the WM6 roms i've used (not as many as some but i'm new here) I haven't had an issue with VC 1.6 US either.
don't think it's a definite answer, but i did have this problem in the past when i installed voice command on my memory card rather than on phone memory. sometimes during loadup after a soft reset i would get that error...think it's because it takes longer to load from the card and voice command is setup to run right away (always in the background)...
if it's installed on the phone memory...dunno...sorry
I run VC 1.6 US and have never had a problem with it. I always install it in main memory.
I give..
Going back to WM5 Molski. To answer some of the post..
It's VC 1.6
No other software loaded..Fresh flash.
Installed to device, not storage *only option offered for install location*.
Get a message during device install: (...recommend installing to main memory. Do you still want to install to "."...) I answer Yes because it just aborts install to say No.
Thanks for the replies guys..
<--[Totally Screwed]
OK, now I have no sound from the speakers and Mic not working. While in Phone mode, the speaker button stays in the On position and won't turn off. Got the old Voice Command registry settings in place but it seems the new problem is the culprit. Going to start a new thread with new problem unless someone has any ideas..
Closing out
Back up and functioning on Molski 3.3 Crossbow. From what I can tell, during the WM 6 load, the speaker phone option became stuck in the On position but the speakers and Mic were not functioning. Voice Command seemed to know there was a problem and gave the "..restart VC.." message. After re-flashing Molski (a few times, still no joy), I flashed with the wired earbud/Mic connected. After flash and phone restart, I removed the headset while in phone mode. Speaker button reset to normal, phone speakers/mic started working again. Reloaded Voice Command and all worked.
aaahh the joys of PDAdome.. Where else can you get the thrill of accomplishment by getting back to the same friggin place
Thanks again for the replies all..
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Give Molski a try..
Avatar28 said:
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Click to expand...
Click to collapse
I didn't have any problems with his roms (..and went back to it with no probs). Only started having problems after I tried the Faria WM6. If the Molski works for you let me know. We'll give Faria a nudge.. Good Luck!
VC issues I've run across
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
At one point I had a strange issue with the bluetooth microphone.... VC would work fine (I'd ask "what time is it" and it would tell me the time) but when I was in a call, no one could here me.... I ended up enabling and then disabling auto gain control... wallah, mic works again.... weirdness.... (don't think this was rom related)
Anyway... the roms that I've had this problem with was XDA Mobile 6 (release 1... relase 2 is kicking a$$) and I think NBD 7.1... never had a problem with a ny Pandora cooked roms.....
Anyway... my $.02... (I'll probably get change)
kudo's to the rom wizards that be...
never had a problem. Installed in a few different roms. works fine
installed to main memory.
wolverine9827 said:
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
Click to expand...
Click to collapse
Voice Command Bluetooth Fix
View attachment 43147
I can't take credit for this and I can't give credit but Thank you...!
I've used this and has worked when VC w/n initiate via earpiece.
There's several threads on the specifics of this cab.
Related
Ok, I'm posting this in its own thread as people seem to have missed my post earlier today as it got buried in the Crossbow Reloaded 1.7 thread:
I've uploaded a test rebuild (couldn't sleep last night and was up early this morning). This is version 1.7.1 . The differences to 1.7 are:
A lot of the compression I did in 1.7 has been removed
Adobe Reader Removed due to the compression on other things making the rom too big
AltTab added and is mapped to the Comm key (this should fix the problem with Voice command people complained about).
Now built with the Core Kitchen
A few other things that I don't remember now
People that have had the dialpad issues in the 1.7 release are what this is really aimed at. If 1.7 was working for you, then stick with that version (unless you need to have a flash "fix" ). I've flashed 1.7.1 to my phone and so far it seems fine, but I really haven't tested it much, so consider this a public Beta. [Edit... Been on my device all day today and so far no issues that I've seen, but then 1.7 was fine for me too...]
I reserve the right to pull this off of RapidShare if I find something I don't like or if others find the keypad issue still exists (I'll post if I do this). Please do NOT MIRROR this without my permission as this is NOT an official release but one I'm trying to see if it fixes the issues with 1.7 that some have had.
Download Link:
Crossbow Reloaded 1.7.1
Please post feedback in this thread. I want to see if the keypad issue is gone now (mainly).
.
The new version is brilliant. I'm loving it so far.
Thanks man.
Does it Have Pocket Outlook?
If it doesn't how do I add it back. Ta, Rin.
Wise choice with the kitchen lol
Thx for mentioning. It makes me proud to hear/read that
I hope it didn't gave you any more trouble.
Did you already started to modify it not to use default install ? Cos if you didn't i'd suggest to wait a day at most ..i am trying to rebuild it. That thing bothers me too.
Running smooth!
I really liked the reloaded 1.5, was running the reloaded 1.7 version, liked it a lot exept the comm button and some OS stalls.
Flashing the 1.7.1 version now and will let you know how it's going in this threath. Also curiuos how the core kitchen is doing
After 30 minutes flashing I killed the shelltool. Since the phone seems stuck I gave it a soft reset and it booted with WM6 splash screen referring to farias rom. Gave it a factory reset and it seems working. Don't have acrobat so I asume it's the 1.7.1 version. Will start working on it now.
Weatherpanel, cybercom voice dialing, tomtom all running smooth. Some little tweaks (I changed under HKLM\SoftwareMicrosoft\Bluetooth\A2DP\Settings the key "Bitpool" and MaxSupportedBitPool to "40" decimal for my Jabra 620) and no problems sofar. Now do some VOIP settings. It never worked, now it's time to get it working on my private asterisk
Ok, working on with the new Beta rom I had some stalls (Three). Green light blinking only no responsive power button. After a reset I repeated my actions before the stalls only I couldn't reproduce it. Since about twelve hours of usage no problems
Mirror the download, please
Can someone mirror the download to some where else? Rapidshare is SUCK.
Flashed it 30 minutes age, installing soft right now, and everything seems to be ok. I had problems with dial pad in 1.7, but in this its ok. Will post in case of any issues
A new 100mbit mirror
Yo mfrazzz, got you a mirror again:
Mirror
TheWizzard2203 said:
Yo mfrazzz, got you a mirror again:
Mirror
Click to expand...
Click to collapse
Thanks for that mirror, but nobody else mirror this for now. I'll wait a day or so for reports of problems then decide if its the final version.
If you flash this and it works fine, please post that. If there are problems with the rom, please post those.
testing new version... no probls found...
Same here, just flashed it and testing now. So far the dialpad issue looks to be resolved. Not certain yet, will post problems that occur.
Nice rom
fast and easy to use
BUT...
I think i have a pb with my battery
lose 5% by hour ... is it normal?
ps : but all is perfect
I just had time to come back to XDA since I loaded CBR 1.5.
I have had the dialpad issues in 1.5 and thought it was just additional software I added. The device didn't lock up and all other functions worked.
The solution I found that worked was to pull the battery for one minute, then do a soft reset once it booted up.
Will load 1.7.1 tonight.
Thanks and keep up the good work!!!
ndoeberlein said:
I have had the dialpad issues in 1.5 and thought it was just additional software I added. The device didn't lock up and all other functions worked.
Click to expand...
Click to collapse
You had dialpad issues with 1.5??? Nobody has ever reported that (that I remember), and 1.7.1 is directly built off of 1.5 (thats before I used compression or anything. 1.7.1 does use compression on a few things, but very minimal compared to what I did with 1.7). While there were definetly dial pad issues in 1.7, I think if you did have dialpad issues in 1.5, it truely was due to 3rd party apps, or tweaks on your phone.
Please report back how 1.7.1 works for you. Overall I'm happy with it, but I felt 1.7 was actually a faster rom than this one (there are times this one feels slightly slugish in places and I may have to turn on overclocking (where I never considered overclocking 1.7)).
So far 1.7.1 is looking good (but so did 1.7 for about 24 hours). I may make this an official release as is if I don't hear anything before tomorrow evening.
kwanice said:
Nice rom
fast and easy to use
BUT...
I think i have a pb with my battery
lose 5% by hour ... is it normal?
ps : but all is perfect
Click to expand...
Click to collapse
I am running version 1.7 but the battery life on this build is superb. Today I only made one call, left push E-Mail on a turned WiFi on and off a few times. After 13 hours I was down to 98% ! This is with a one month old battery.
How old is your battery ? Mine started to fail after 14 months.
i have not had any problems yet. It's great! will let you know a few days if I ran into any problems.
Voice command issue is it gone?
Hi mfrazzz,
Thanks again for another new version.In the previous version I reported one issue with voice command. Is that resolved in this version.
Issue was the voice command could not be activated using bluetooth headset. I have seen the keypad issue in 1.7 and sometime few error messages as well.
banerjeez said:
Hi mfrazzz,
Thanks again for another new version.In the previous version I reported one issue with voice command. Is that resolved in this version.
Issue was the voice command could not be activated using bluetooth headset. I have seen the keypad issue in 1.7 and sometime few error messages as well.
Click to expand...
Click to collapse
There was no issue with Voice Command and BlueTooth headset in 1.7 that I know of. I have a Plantronics Voyager 510 BT headset and a Bluespoon Spider stereo (A2DP) BT headset, and both pair up fine, and both control Voice Command fine for me. I know others using 1.7 and BT headsets worked fine with Voice Command for them also. It could be an issue with your headset and WM6, 3rd party software, or something else.
The only Voice Command issue I know of in 1.7 was that there was a button mapped by default that wouldn't work properly. I fixed that so that the Voice button (Button 4, upper right side of phone) now maps to AltTab app. AFter you install Voice Command it will map to your Messages button (button 1), but thats how Microsoft installs it, not my doing. You can then redo the buttons in Settings > Buttons and you are good to go (although I really like AltTab now, so I left it on Button 4 and only use Voice Command via my BT headset).
i had problems with 1.7...in that i the dialpad keys disappeared after first flash. i did a clear storage (1234, etc) and the dialpad came up. flashed this version (downgraded to official t-mobile 2.26, as I always do first) and i don't seem to have the same problem. everything was in working order the first time around. the rom actually feels a bit faster than 1.7. thx.
monkey_knight said:
i had problems with 1.7...in that i the dialpad keys disappeared after first flash. i did a clear storage (1234, etc) and the dialpad came up. flashed this version (downgraded to official t-mobile 2.26, as I always do first) and i don't seem to have the same problem. everything was in working order the first time around. the rom actually feels a bit faster than 1.7. thx.
Click to expand...
Click to collapse
if I wanna flash to the official t-mobile rom first can I use the rom program of t-mobile itself?
RUU_Prodigy_2210205_22102108_021911_TMO_NL_DUT_Ship.exe is my default rom I think
Did anyone get it to work on wm6.1? i install it and it installs, but when i try to go to settings it will not go any farther. I like to have in say whos calling. Its a feature i can't live without! any help would be appreciated!
wolfskin
I think this is a problem when using the "official" 6.1 base. When I load it, it freezes after the install (like when it tries to load the "Help" file) and I must SR the phone. The next boot will be fine until it seems to start the Voice Command program, at which point will freeze the device. I had to hard reset to recover.
Others have reported Dutty's and other 6.1 releases not based on the "official" ROMs work with Voice Command.
i have it installed, haven't noticed any problems or than it needs to be tweaked to anounce calls. all other features, buttons, menus work.
i cant resist this one
READ THE FORUMS
http://forum.xda-developers.com/showthread.php?t=365118&page=6
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Mine works with Schaps...
I am the same way, i must have MSVC for my blutooth carkit...Schaps is the only one i could get it to work well on; however, I din't try it on Dutty's
Just Tested on Alex's WM6.1 Home BETA 2
Works Great.
No problems...works on WM6.1
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Same Here, no issues (Except the caller id anouncement)
Works fine for wm6.1 and its fine with my parrot carkit actually bluetooth audio much much better now
WM6.1 VoiceCommand 1.6 US
Works fine here - in fact BETTER than with original TYTN release where it would often hang just after hoing the lookup till you hit the Red Phone Key.
Now that it sounds like BT volume is better with 6.1, has anyone taken the time to compare registry settings between WM6 and WM6.1 to see what the differences are?
asking it to play music, and than anything works for me, no issues.
Laubscherc said:
Same Here, no issues (Except the caller id anouncement)
Click to expand...
Click to collapse
Did you go into Settings-Personal-VC and check "announce incoming callers"?
Mine is working completely without any hacks.
In the official 3.03 used in Alex's 6.1 Beta 1, MSVC didn't work for me, crashed the settings.
Now with Alex's Beta 2 he used official 3.02 and MSVC works perfectly.
asfoor said:
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Click to expand...
Click to collapse
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
MELPHBOY said:
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
Click to expand...
Click to collapse
Use Kaiser Tweak in disable the trusted certification.
alltheway said:
Use Kaiser Tweak in disable the trusted certification.
Click to expand...
Click to collapse
Not true....
The Voice Command.asx is NOT part of Kaiser Tweak Menu. There are only two certificates to disable or enable. Even if you were to disable both the WiFi certificate announcement or the BT Certificate announcement, the VC.asx certificate right violation still shows when you request or command the VC, and will not respond to the command.
Did you locate the certificate disable/enable on your phone Kaiser Tweak before you decided to post your response?
Unless you can prove me wrong, I AM WAITING.........
pkley said:
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Click to expand...
Click to collapse
What radio did you upgrade to ? just tried all 3 and still doesnt work for me
Until about 3 days ago the sound on my phone worked perfectly, I have installed dutty's rom for about 1 month ago. On friday or something the sound simply dissapaired from the phone, and now I am only able to hear sounds through headphones/earplugs.
I have discovered that if i press the wheel on the side inwards, the sound returns as long as I am holding my finger there. What is causing this, and how can i possibly fix it?
I can't anylonger hear when the phone is ringing or anytthing
What radio are you using? Try updating your radio and reading the wiki.
http://wiki.xda-developers.com/index.php?pagename=DuttySeriesKaiser
Problem: I have no sound.
Solution: You need to install a Windows Mobile 6.1 radio.
Click to expand...
Click to collapse
List of Kaiser radios:
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Radio
From what I get he didn't flash anything new or change anything? I would try a hard reset and see if that fixes it if not flash a new ROM and Radio that is known to work and if that doesn't work trade it for a refurb from your provider.
I just tried both hard-reset and installing a new rom. It is not working as I have seen yet. I don't think its a hardware error because i have never lost the phone on ground yet, and it has never been in contact with water. I have also tried to reset the software, but nothing helps
I also can't remember installing a software or making any changes other then gps fix previously before the problems started occuring. Might it be possible that somehow a change or something somewhere have made my phone uncompitable with the current radios?
As I said previously, I get trough the headphone. the odd thing is that i get the sound on the phone back if i press the scrollwheel inward a bit hard. I think there is a registry error or something somewhere.
Though this is very annoying because I can't hear when the phone is ringing. The phone is too big to be in my pocket, and then i need to keep it in my jacket.
I would be grateful if anyone could provide a solution to this-
though i have read through the wiki, and I find it strange that a rom and radio that previously were working, suddenly stops working.
amik5 said:
though i have read through the wiki, and I find it strange that a rom and radio that previously were working, suddenly stops working.
Click to expand...
Click to collapse
I fully agree. I have the same problem with all Dutty's ROM. Once I pair the bluetooth device the first time and have it connected, from then on the sound goes to bluetooth headset. Thus, I miss calls if I am not wearing my bluetooth headset 24/7.
When the bluetooth headset is disconnected, still there is no sound from the phone. Again, I miss calls.
The Radio which I use with Dutty's ROM is alway included in the ROM.
Maybe, some registry settings?
KOR!
But the strange thing here is that the sound worked perfectly until some days ago, but maybe i should try to just reset the whole phone back to its original setting, and then reinstall everything?
I think its just annoying that something like this occurs when the phone is working perfectly.
Though i don't need to wear headsets when i am talking in the phone; the inbound speakers are working as they are supposed to
Ok, i have tried every radio possible now, and none of them works
amik5 said:
Ok, i have tried every radio possible now, and none of them works
Click to expand...
Click to collapse
Try to install a different ROM which has built in Radio with the ROM. Such as this:
http://forum.xda-developers.com/showthread.php?t=381837
Hope this is helpful.
KOR!
flash it to original radio and rom, if it still does not work i think it's time to get that replaced. you may have to warranty it.
How do I do that? If there is any help, I have 2 other htc kaisers at home if there is possible to retrieve anything from them
amik5 said:
How do I do that? If there is any help, I have 2 other htc kaisers at home if there is possible to retrieve anything from them
Click to expand...
Click to collapse
Just flash some other ROM and see what happens. Either flash the ROM from the link I have given or flash the original ROM.
Spend half an hour and you will know if it is software or hardware problem.
The easy way is to download the ROM from the link given above and let us know the results!
KOR!
Same problem here. I noticed that it only happens after pairing it with bluetooth. I was on the ROM for a month before i pair it with bluetooth and then voila ... no sound.
However, my problem can be temporarily solve by resetting the phone. I was about to flash to the latest Dutty's and see how...
amik5 said:
Until about 3 days ago the sound on my phone worked perfectly, I have installed dutty's rom for about 1 month ago. On friday or something the sound simply dissapaired from the phone, and now I am only able to hear sounds through headphones/earplugs.
I have discovered that if i press the wheel on the side inwards, the sound returns as long as I am holding my finger there. What is causing this, and how can i possibly fix it?
Click to expand...
Click to collapse
You should have made this post in the thread of the ROM you're using!
You don't have a signature so we don't know what the @#$% you have on your phone.
It's not like Dutty only has 1 ROM out.
There's several individuals who go thru Dutty's threads & help individuals like yourself.
So, if you post there....you will get the help you need.
Moderators.....please close this useless thread !
Leechoonhwee said:
Same problem here. I noticed that it only happens after pairing it with bluetooth. I was on the ROM for a month before i pair it with bluetooth and then voila ... no sound.
However, my problem can be temporarily solve by resetting the phone. I was about to flash to the latest Dutty's and see how...
Click to expand...
Click to collapse
Has anyone tried reinstalling the BT then.
Leechoonhwee said:
Same problem here. I noticed that it only happens after pairing it with bluetooth. I was on the ROM for a month before i pair it with bluetooth and then voila ... no sound.
However, my problem can be temporarily solve by resetting the phone. I was about to flash to the latest Dutty's and see how...
Click to expand...
Click to collapse
Just tried Dutty's April 1 (no April fool) ROM and it doesn't have the above problem. Here is the link for it:
http://forum.xda-developers.com/showthread.php?t=380991
KOR!
In the future, please reply to an existing thread when reporting problems. Please do not create new threads.
If you're not sure why this thread was closed, see the forum rules or watch this video.
Resetting the Rom
I have a phone where the hardware is malfunctioning, and i want to send the phone back for repair. The only problem is reinstalling the previous OS.
I had originally a norwegian OS (1.56.409.8711). I do have acess to another kaiser with the OS i want, so is there anyway to retrieve it from the phone?
Hi,
Is anybody else experiencing issues with losing sound on their phone? I have been experiencing this on a number of different roms and initially put it down to an incompatible radio, but I have sinced flashed back to one of Dutty's roms (including radio) and it happened again. I have now flashed back to the stock bootloader and HTC rom and it has happened again!
I am at a bit of a loss now - am in the process of hard resetting my phone to see if it happens on a bare device as I had a number of apps installed although none of them had caused this problem before that I am aware.
Would be interesting to know if anyone else is getting this - don't know if its possible that any of the recent radio/rom releases could have done something permanently damaging to cause this. Will be sending mine back to HTC if it happens again, unless someone identifies a fix?!?
Cheers!
captainsensible2002 said:
Hi,
Is anybody else experiencing issues with losing sound on their phone? I have been experiencing this on a number of different roms and initially put it down to an incompatible radio, but I have sinced flashed back to one of Dutty's roms (including radio) and it happened again. I have now flashed back to the stock bootloader and HTC rom and it has happened again!
I am at a bit of a loss now - am in the process of hard resetting my phone to see if it happens on a bare device as I had a number of apps installed although none of them had caused this problem before that I am aware.
Would be interesting to know if anyone else is getting this - don't know if its possible that any of the recent radio/rom releases could have done something permanently damaging to cause this. Will be sending mine back to HTC if it happens again, unless someone identifies a fix?!?
Cheers!
Click to expand...
Click to collapse
happened to me yesterday. i had to hard reset and my phone still isn't customized 24hrs later.
Do you remember what apps you had installed?
I'm starting to think all of this has something to do with MSVC.
well i have consistently been using version 19209 whilst having these problems. Going to try 17913 again and see how that goes.
Mine too
I've been getting this alot lately, too. I think it's either MS VC or S2U2 1.01, or a combination of them.
I've done the same thing, flashed multiple ROMS and radios, but I've stayed in the WM6.1 family. I was running Confused Stu's Vista 1.2 forever and it suddenly started doing that - loosing sound. I went to 1.3 and then over to a Dutty build, and have now settled on L26_WM6.1_PROV4_(3.51.502.0_WWE)_Multimedia... This time I went slow and only loaded a few apps at a time. I thought it was Calendar+... But I don't have that on here yet.
It seems like it ran fine until I put S2U2 on here, but like I say, I use MS VC to announce everything so maybe it's some action there that didn't happen until after I put s2u2 on there, or maybe coincidence.
I wonder if anyone else is seeing this? I think I'll start over without S2U2 - even tho it rocks! - and chill a week.
Do you use S2U2? Do you use Caller ID in S2U2? How about slide 2 answer, slide 2 end key options? What about blank screen on talk option?
Thanks,
H
s2u2 v1.01 could be the culprit as i have been using it. After slowly reloading apps this morning sound had gone again, and one of the last to go on was s2u2. I don't think MSVC is the problem as it has never done it before plus its cooked into a lot of new roms, whereas s2u2 isn't. Am going to uninstall s2u2 and see what happens. It was one of the last things I put on and sound had been stable before that.
Im getting this issue as well, what radio are you guys running just out of interest, im running duttys 6.1 build 19199 with radio 1.65.14.06
I haved the same problem and resolve it by flash ing TNT 19202 Series PRO with radio 1.65.14.06. Best regards.
Well, the issue came back on the stock rom when I bit the bullet and installed a slightly older version of S2U2 (0.99p)!
I have now reflashed Hard-SPL and the latest Dutty Rom (with MSVC included) and have resisted putting S2U2 on and so far, so good!!
Hey, Zaf, do you run S2U2 or MS VC?
I flashed back to the AT&T Tilt stock ROM (downloaded from HTC web site, incl the radio) and reloaded S2U2 1.01 and MS VC. I lost sound within a couple of hours.
I did a hard reset and have not installed EITHER... I plan to run for a day like this, then put MS VC back on for the weekend, and then S2U2 after that.
I think it's S2U2 and I think it's been around since .99p. But I think 1.01 is worse than .99p or 1.0.
Well, at least we're narrowing down the variables!
Hey, everyone - watch http://forum.xda-developers.com/showthread.php?t=390977
for a similar discussion.
I flashed TNT 19202 Pro thus morning and the sound died few hours later again... Don't use S2U2. I posted more here - http://forum.xda-developers.com/showpost.php?p=2207600&postcount=18
I have lost sound 3 times, it is only through the speaker though, my bluetooth headset continues to work. Once I flashed a new rom to fix it, the other time it fixed itself over a few hours. The third time is happening now!
I have never used S2U so it can't be that. Have been using Dutty's roms, my radio is currently 1.58.16.27.
are we talking about sound in calls, if so i have been experiencing calls dropping and other people can hear me fine but then it suddenly goes quiet for the other caller and they can barely hear me? is this a fault with my kaiser or to do with flashing with custom ROMs.
I think we need to be very clear here what the symptoms are of a specific problem.
My symptoms were that sound would initially be ok after flashing a new ROM (whether it had MSVC cooked in or not) and then I would go through the process of installing my 'regular' apps which has always included S2U2.
Then, at some point after doing this, all sound would disappear - from the device and also during calls (interestingly, during calls, the other party could not hear me either).
I cannot explain for one moment the issues that people who don't use MSVC/S2U2 - some of these might be explainable by radio issues but I am not an expert by any means so would not be prepared to blame that!
All I know for certain is that up until recently I could use MSVC 1.6 build 17913 alongside S2U2 0.99 with NO issues at all - this is why I think that MSVC 19209 combined with S2U2 is the reason.
One other thing, I have not tried S2U2 on its own, without using MSVC, mainly because I am fed up with flashing! Perhaps someone else could confirm or deny if this has caused problems?!?
Yes, my symptoms are EXACTLY as the captain describes in his post... Everything fine for a little while after flashing, but soon after I get all my apps reloaded I call someone, or someone calls me, and there is no sound. No audio at all from the speaker, bluetooth, or in-call speaker. The caller can't hear me, either. I have to soft reset or power cycle to get sound back but it doesn't last long.
All day I've run with the AT&T stock tilt ROM from HTC's web site, still hard SPL'd, and I did not load MSVC, S2U2, or HTC Home yet.
R 1.27.14.09
G 22.45.88.07H
D 1.62.00.00
I have run all day with no sound problems. I am now about to plunge and I think I'll put MSVC on there first and run another day, only because on a whole it's cooler than S2U2. Lets see what tomorrow brings.
Hey, I just found this one: http://forum.xda-developers.com/showthread.php?t=391262
I am using an older build of MSVC... I grabbed the latest build and will give that a shot first. What build are you using? I WAS using 1.6.17913 but aparently it is old. I just grabbed 1.6.19209
Its interesting that you're seeing the issue with the older build of MSVC as I never had it with that build, although I can't remember if I used that build with the latest version of S2U2.
My phone has gone a whole night now with no issues without S2U2 installed, so I think that proves there is a link. Not sure if I can be bothered trying S2U2 without MSVC as, like you, I prefer having MSVC over S2U2.
What is also interesting is that there has not been much (one post I think) mention of this on the S2U2 thread. I may bring it up...
The trouble is, in 6 weeks of trying to deal with the problem by re-flashing ROMs and radios, I would still have the issue. Even though I never install MSVC nor S2U2. I even had the problem on a "clean" setup - just the ROM, I setup Internet connection, ActiveSync wireless Exchange and Note2Self - that's it nothing else. And I would lose sound within 3 to 20 hours with this setup. That's the cleanest setup I could get - I don't need my phone if I don't have Note2Self )
Just saw another of the symptoms... Another thing it would do would be to just crash after a call. So hitting END leaves the screen stuck with whatever's on it, and no way to get off that dialer screen. OK doesn't work, though when I push my VC button I hear it beep. This just happened after a call.
Anyway, I did a power cycle and it's back now. But I do not have S2U2 on here, though the MS VC lady is getting a real workout today... Anyway, sergeb will still tell us that neither app matters, anyway.
Uggh. Still resisting urge to put S2U2 on here.
Anyone have this issue or a fix? BT connects perfect, works, perfect, but the command to hang up on the BT device dosen't properly hang up, and the phones returns the #777 error.
It does answer from the BT device properly. It does with with my other cell phones.
TP2 VZW
I had the same problem with my Voyager Pro headset and found that if I hit the button once, wait a second and hit it a second time it hangs up. Maybe it will work for you.
I have the same issue.
Using Moto HT710 and VZW stock ROM
same issue in w/ 09 bmw nav/bt connection. I have to grab the phone and press the end button as it never hangs up.
cab might fix it
Over at PPCGeeks.com some have fixed the issue using the cab in this thread: http://forum.ppcgeeks.com/showthread.php?t=90155
I am having the issue with my Ford Sync system. I will test the results of the cab this afternoon and post them. Hopefully this works because it is fairly annoying.
Here is the cab if anyone wants it.
Well it didnt work for my Verizon TP2 and the Ford Sync system, hopefully someone else has better luck with it.
This seems to work for me. It hangs up almost instantly now. Thanks for the find.
rsbrown69 I am glad I could help, could you post which version of the TP2 you have (verizon, tmobile, ATT). I just want to know if it worked on another verizon phone or not, if so I will hard reset and give it another shot.
wlawyer said:
rsbrown69 I am glad I could help, could you post which version of the TP2 you have (verizon, tmobile, ATT). I just want to know if it worked on another verizon phone or not, if so I will hard reset and give it another shot.
Click to expand...
Click to collapse
I am using the mostly stock Sprint TP2. The only main modification I have done is the Touch Pro 2 cleanup http://forum.ppcgeeks.com/showthread.php?t=88640
Looking at the thread on PPCGeeks it looks like mostly sprint users having luck with the cab as well. Hopefully something will come along for the verizon version as well.
I have the Sprint version and have installed the cab. I do not see any improvement. I experience intermittent problems with or without the cab. It doesn't seem to make a difference. FWIW, I use the Jawbone Prime and Jawbone 2. Same with either.
Just out of curiosity did you do a soft reset after the install? I remember someone mentioning that in the original PPCGeek thread.
Yes, I did a soft reset. Actually, a soft reset with or without the cab seems to solve the problem....for a while. Then it shows up again. It is a bit strange.
doesnt work
I tried it on my Sprint TP2 and it does not work either. I installed it and did a soft reset and it still does not work for me either.
It would be the best thing that happened if it did work cause I use my BT all day and this sleep mode BT thing on the TP2 is cool for battery life but it sucks for using the BT feature which to me is more important than battery life and I have car chargers and usb chargers so I would rather have a working BT.
Does anyone have a cab or fix that will allow the BT to function like the old Touch Pro? That phone had a great BT even if the battery life was poor.
Thanks for the attempt to fix the issue but it is a no go here.
Does not work on stock VZW rom
Didn't work on my TP2 VZW either.
The one person that has responded that it worked had the cleanup cab installed. I am going to try a full reset and put only the cleanup cab and the bluetooth cab on and see if I can get results. Yeah this bug is that annoying to me. http://forum.ppcgeeks.com/showthread.php?t=88640
Ok I did a hard reset, programmed the phone, installed the cleanup cab, installed the bluetooth cab, joined the phone to my ford sync system, made a call, and guess what... the phone hung up beautifully using my standard steering wheel control for sync. There must be something in that cleanup cab that is either A) the actual fix or B) a necessary piece of the fix. Sorry but I am not going to hard reset again to test it, mine is working so hopefully this info can help you guys as well. On a side note that cleanup cab is pretty nice but read the thread to make sure you want/need all that is included.
wlawyer said:
Ok I did a hard reset, programmed the phone, installed the cleanup cab, installed the bluetooth cab, joined the phone to my ford sync system, made a call, and guess what... the phone hung up beautifully using my standard steering wheel control for sync. There must be something in that cleanup cab that is either A) the actual fix or B) a necessary piece of the fix. Sorry but I am not going to hard reset again to test it, mine is working so hopefully this info can help you guys as well. On a side note that cleanup cab is pretty nice but read the thread to make sure you want/need all that is included.
Click to expand...
Click to collapse
The cleanup cab alone hadn't fixed the problem for me so that is when I tried this threads fix. So far it works more often than not but it still does not hang up every once in a while. Must be a combination of things between the cleanup cab and this one but still not the correct fix, better but not enough.
Mine worked none of the time before, I basically had to wait for the caller to hang up or pull my phone out of my pocket and press end, so any improvement is huge for me. I am traveling this weekend and next week so hopefully I will have more info to report at least with my setup with Sync (never got into the earpieces, so not testing that).