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
Voice Command has always been the holy grail of mobile phones for me, and enabling it just by pressing your Bluetooth Headset's button took it from godly to supreme ultimate heaven.
I was trying out some new ROMs today and none of them could activate VC via BT Headset.
However I remember my old ROM before could do it. I am not sure I think it was Ranju's/Tomal's old ROM. Does anyone know which version it was? V8.0 of Tomal doesn't work.
If you get the 19209 build, you should have no problem doing this. PM/IM me if you need help with it.
Rather than a PM...
Could you instead post me to a link which has said build version? The ROMs I have been trying are buidl 19000.
Tomal's ROMs are readily available in the forum threads titled as such.
I tried MSVC with Tomal's 6.1 and 7.7, can confirm BT MSVC activation worked with both.
enigma1nz said:
I tried MSVC with Tomal's 6.1 and 7.7, can confirm BT MSVC activation worked with both.
Click to expand...
Click to collapse
Yeah I moved back to 7.7 and it worked. Incidentally I was also able to get it to work with EFN's 2.20. Thanks.
When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?
I'm using 1.6.21040.
Gave an error during installation, but seems to be working as far as announcing calls and reading texts.
I have tried to installed version 1.6.21725 and it seems to work fine, but I tried to link to the key virtually using AE Buttons, everything collapsed. The lnk file just got deleted: any suggestion.
How did you guys use to assign to a key?
Was asking the same question. Install worked with one error message. The program works when I start it manually, but I cannot find a way to assign execution to a specific button press. Looking for ideas here.
Toby
i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way
I've switched to 21725 and used aebutton plus to assign it to long press windows key, all works perfectly now.
I dont want to use aebutton plus, so I tried to use the old Long_Send.lnk and had no luck, am I doing something wrong?
or is it a diffrent name in 6.5
MSVC
I got that error too but it has stopped for some reason and now works well.
Version is v1.6.21040
I tried to upload a cab for you but it wouldn't upload.
I use MSVC for text to speech, to announce calls, read emails to me and announce calendar reminders.
This version won't read text msgs.
I don't use it for voice commands, Cyberon Voice Speed Dialer is much better for that.
mallman said:
When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?
Click to expand...
Click to collapse
mallman said:
i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way
Click to expand...
Click to collapse
WHICH LINK DID YOU USE, THE SHORT OR LONG ONE??
Thanks!
I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.
MSVC cab
Oops!
Got it.
NotATreoFan said:
I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.
Click to expand...
Click to collapse
So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.
bill340 said:
So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.
Click to expand...
Click to collapse
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.
I Think I've Found An Answer
If you go into the registry and go to:
\\HKLM\Software\OEM\VoiceCommand
and edit the value for VoiceCmdEnable to 1 (it was set to 0 on my HD2), then soft reset.
Now you should be able to get Voice Command working through BT, at least it's working for me at the moment.
It does not help fo rme at all...
No change!
Which version of MSVC do you use?
I'm not entirely sure, but in the Voice Command settings it shows v1.60.4622.0
weepatc said:
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.
Click to expand...
Click to collapse
In my case it is very similar, but when i activate voice command with the assigned button on my HD2 and not via the headset, everthing works as it should. Maby thats a indication how to get it worki`n the right way.
VoiceCommander Working
Hi,
Initially I couldnt get the BT to connect to VC (just got a BT disconnect beep in my ear).
Tried installing 2nd time (over the top), and seemed to 1/2 work but sometimes I would have to say name I wanting to dial through handset - then it would put call through BT - strange.
Finally, I noticed that if the BT headset was on when the phone was switched on (fluke that happened), it worked fine.
If the BT headset is switched on after the phone, it still plays up. Not tried turning BT on handset off and on whilst BT headset turned on yet - something to try tonight I guess.
Note : this only started working a day or so ago so not tested throughly yet.
My VC version is 1.6.4622.0.
I also noticed that on handango - a new VC version is available (updated 20/11/2009) which says works with Touch HD2 - but only USA voice at the mo so I'm waiting for the UK (hopefully released soon).
Hope the above helps.
Looks like I have an old version of Voice Command MSVC1.6.19214. How do I get a later version? Don't see why I should have to pay for it again when it is still 1.6.
Sorry, my bad - not working anymore. Worked for one day, then I get the same as everyone else
This has been an ongoing problem with my last two phones. First was an HTC Touch Pro, now an HTC Touch Pro2. It doesn't matter if I am on a stock or custom ROM or whatever.
I noticed that when I called people, especially when the headphone jack was plugged in (using the auxiliary port in my car speakers) that people would be unable to hear me for a good 5 to 30 seconds. I could hear them but they couldn't hear me. Eventually they'd be able to hear me.
I kept killing processes one by one until I narrowed it down. It was Microsoft Voice Command! I was really surprised because I use the program only for announcing who is calling me (very nice feature so I don't have to run to the phone if it's someone I don't care about). I don't use it for dialing or anything of the like.
I have Googled for hours and a few people have the same problem but the only fix appears to be "don't use Voice Command" which sucks. I guess what I'm asking is if either a) there's a way to fix MSVC so this doesn't happen or b) there's a program that announces who is calling you that I can use instead of MSVC.
MSVC was annoying anyway because when you click "mute ring" when someone is calling you it still repeats the name! Pretty stupid. So I guess I'd just like some sort of replacement program for announcing incoming calls. Any suggestions would be greatly appreciated.
Have you tried fixing this issue using this?
http://forum.xda-developers.com/showthread.php?t=586901
Pumpiron579 said:
Have you tried fixing this issue using this?
http://forum.xda-developers.com/showthread.php?t=586901
Click to expand...
Click to collapse
Thanks but that program did little more than allow me to change the volumes and speeds.
I have the same issue with my Blackstone. When I check the running process I find that Voice Command takes almost 100 pct and James everything else.
I also Need it to announce who is calling.
Yeah I'm essentially giving up on MSVC ever working correctly, so if anyone know of a program that just announces who is calling, that would work just great.
daddylonglegs said:
Thanks but that program did little more than allow me to change the volumes and speeds.
Click to expand...
Click to collapse
LOL,Yea, it does a lot but I would ask your question about your headjacks in that forum. I am sure you would get an answer.
um, what versions are you guys using?
tried using an up to date one?
Microsoft_Voice_Command_v1.6.23562.cab
(for 6.5.x)
Microsoft_Voice_Command.v1.6.21881.cab
(for 6.5)
pyrorob said:
um, what versions are you guys using?
tried using an up to date one?
Microsoft_Voice_Command_v1.6.23562.cab
(for 6.5.x)
Microsoft_Voice_Command.v1.6.21881.cab
(for 6.5)
Click to expand...
Click to collapse
I am on 6.5 and your CAB is actually older than what I have cooked into the ROM... :\
MVC1.6 - no please! i am looking for a Voice activated app...
What good is that MVC1.6 if you have to Press a button and then say command? its called crap. Such a Program is already inbuilt in my WM6.
I am looking for a Voice program that keeps running in the background and its always in the listening mode and I can simply "SAY" these commands "as well".
1) WakeUp - wakes up my PPC
2) Sleep - PPC goes to Sleep mode (PPC is On though)
3) Programmed to wake me up at a particular time (by a beautiful Virtual Girl)
4) and Features of MVC1.6
is there anything like that for PPC WM6 ? CE5.2 version?
regards
fifthelement