Database Info

[Public Beta] Crossbow Reloaded 1.7.1

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

WM6.1 and MS Voice Command

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

6.1 screen orientation issue

Hello all,
I just installed a 6.1 rom. When I slide out the keyboard the screen reorientates correctly. But when I slide it closed it doesnt switch back.
Anyone know a solution for this?

bryangauvin said:
Hello all,
I just installed a 6.1 rom. When I slide out the keyboard the screen reorientates correctly. But when I slide it closed it doesnt switch back.
Anyone know a solution for this?
Click to expand...
Click to collapse
Are you using the Dutty rom listed in your signature?
I had this issue myself on Sleuth's WM6.1 (ver 3.0) rom. When the screen failed to rotate back after closing the keyboard, I would just slide it back and forth once or twice and it would correct itself.
I went back to WM6 for the time being until we learn more about the new "feature" in 6.1 that supposedly allows carriers to tell if our phones are being tethered to our computers for ICS.

actually Im using DCS rom untill dutty comes out with his final 6.1. I have tried open shut many times and it does not reorient.
As for your "Feature" about tethering. I acytually work for AT&T and they have had the ability to tell if your tethering for a while now. If you are doing tethering they will eventually catch on and make you change features to continue.

Try HTCHome to reorientate your screen, maybe that will do?
bryangauvin said:
actually Im using DCS rom untill dutty comes out with his final 6.1. I have tried open shut many times and it does not reorient.
As for your "Feature" about tethering. I acytually work for AT&T and they have had the ability to tell if your tethering for a while now. If you are doing tethering they will eventually catch on and make you change features to continue.
Click to expand...
Click to collapse

Question to all Tomtom Users

Hi.
I have just installed Tomtom (vga-version) on my Touch Pro and found, that when trying to enter an Adress with the slide-out Keyoboard an aditional character is added after each pressed button. This Means: i press "a" and "a°a" appears on the screen.
Does anyone else have the same problem or maybe found a solution?

Never noticed that problem before. Using last version of TT7. Maybe a rom issue with the keyboard driver.
Usually I'm using the soft keyboard of TT7

Pizzamaka said:
Hi.
I have just installed Tomtom (vga-version) on my Touch Pro and found, that when trying to enter an Adress with the slide-out Keyoboard an aditional character is added after each pressed button. This Means: i press "a" and "a°a" appears on the screen.
Does anyone else have the same problem or maybe found a solution?
Click to expand...
Click to collapse
This is also happening to me, stock WWE updated ROM with TTN7 7.915. This is soooo lame!

fun_key said:
This is also happening to me, stock WWE updated ROM with TTN7 7.915. This is soooo lame!
Click to expand...
Click to collapse
I can also confirm that this is happening to me with TT 7.915. I'm not completely sure, but I don't think it happened to me with TT 7.910

Do you all use the vga-version? I think it did not happen with the not-vga version that was preinstalled on my device.

I tried with 910 and 915, and I still get this issue :-/

Its hapening to me also. im using TT7.450 (VGA)
Buts not a problem to me. Tomtom is very fingerfriendly and it goes very smooth.

On a slightly different issue, what sort of refresh rate are you getting on TomTom in terms of map redraws per second? I'd guess I'm only getting one, maybe two, but I've seen Sleuth's video, and he looks to be getting 3 or 4.
Any ideas?
Cheers,
Steve.

I also have this issue, although I never use the keyboard while navigating. If you didn't mention it I would have probably never noticed it! LOL

@maw: Well I bought a PDA-holder for my car which holds the Touch pro with the open keyboard, since I thought, that it would be really cool (which it is if it wasn't for the keyboard not working properly in tomtom)
@StevePritchard: I am not sure, but I think I get about 1-3 fps in Tomtom.

did you upgrade your ROM and noticed this problem? As I never used the keyboard with the previous stock ROM I can't say if the ROM upgrade effected the Tomtom interface with the keyboard. I updated my stock ROM with the new version that just came out. Maybe that is the problem, I don't really know.... Very good of you to signal this problem though. Otherwise I don't think this problem can be fixed, I guess we'll just have to wait on a new version of Tomtom to fix this problem. Have you reported it to Tomtom?

no I did not upgrade. I didn't even know, that there is an available update. I am running the stock rom (from o2 germany) that came shipped with the phone.
Is there an update from htc?
No, I did not report, since my Version fell from a truck... I was just wondering whether it was damaged during the fall or if everyone has this problem. ;-)

Pizzamaka said:
Hi.
I have just installed Tomtom (vga-version) on my Touch Pro and found, that when trying to enter an Adress with the slide-out Keyoboard an aditional character is added after each pressed button. This Means: i press "a" and "a°a" appears on the screen.
Does anyone else have the same problem or maybe found a solution?
Click to expand...
Click to collapse
Its a TomTom error, the newer TT versions dont have that problem.

I used to get this when running Elite RC2 - I moved to ROMeOS and never had the problem

komani86 said:
Its a TomTom error, the newer TT versions dont have that problem.
Click to expand...
Click to collapse
What do you mean by newer versions? I use 7.915 - Is there anything more recent?

I'm getting the same problem, and I've got 7.915 as well. No-one found a solution then?

i had this problem on 3 different versions of tomtom, along with hit or miss signal. it always thinks im inside a building but in the 1/20 shot it works i cant do anything or else "im inside a building" again. i just dont think tomtom was meant for the fuse

It is not a TOMTOM issue. It is an issue with the IME. Here is the fix.
I have attached KforTouchPro_v1.0.0.3.CAB
1. Install the cab
2. It installs to your games folder because this is a fix for several games that have had this issue (I originally discovered it because I had issues using the HW keyboard with logmein)
3. click the Switch to M$ IME button. Now you are good to go!

Thanks - I have just tried it, and TT now works fine.
The problem now is, that other things don't work anymore... I tried writing an E-Mail and it wouldn't let me abort the mail. It displayed the Messageboc, but did not accept any input. Since I write more Mails than I use TT and don't like to keep on switching Keyboard map I is not a real option.
Do you have any Idea?

Hmm.. odd, when I updated my TomTom it just disappered, I have your version aswell, good that there is a update though for you
that K for touch pro, is that KforRaphael that maps certain keys for MorphGear?
I had that installed, but cant recall if it was erroring before that, anyways, good it got solved

Blue toothe won't hang up

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).