Here's the problem. I unlocked my phone and installed the 2.17.7.2WWE rom onto my phone thinking it enabled the a2dp function. The update went on without any problems, I bought the ht820 bluetooth headphones and it didn't work. Then i read that there is the same rom with the a2dp fix and i tried to install and i got an error "pc cannot communicate with phone" First question, do I have to unlock the phone everytime I want to update the rom? I'm not sure why I'm getting this error. I tried it twice and got the same error. So I tried the tornado cab file and i'm confused on the registry part, I don't have the reg keys listed in the directions and i'm not sure how to import this a2dp.reg file into the registry. I'm using the mobile registry editor. someone please help..
getting closer
well about 5 minutes later i finally figured it out.. but now the set wireless stereo is greyed out and i cannot select it.. now what to do?
Finally working!!
Got it figured out
Thanks to all your post's they were all very helpful!
So.....What did you do to fix it? Some of us newbs would love to know. :?
The fix explained
First I updated the rom to 2.17.7.2 WWE (I'm not sure if the rom update needed to be done or not) Then I used a registry editor called TRE v.90, downloaded the tornado_a2dp.zip, followed the directions in the zip folder, then imported the a2dp.reg file (thats also in the zip file) into the registry using TRE, after i did that i had the option in bluetooth settings to set as wireless stereo but it was greyed out and couldn't enable it. so i deleted the headset in bluetooth options rebooted the phone repaired the headset with the phone then i was able the use the stereo headset. and i must say.. the motorolla headset sticks out a little far from your head, but they were definalty worth $80 !
Related
After watching for months the issues that many have suffered over this problem, I finally found a solution that will fix all the woes.
A few months ago I was one of the many here that upgraded to 1.11 ROM, had the problem. It drove me crazy to the point that I went back to the 1.06 ROM that was rock solid. Well the other day I did a hard reset to have a clean slate. While looking at the Extended ROM I saw the file DefaultV_1.12 in the EXT Rom (Compared 1.11 ROM on FTP to my device). This was the same file that a XDA developer member had modified to somewhat solve the GPRS problem a few months ago.
At this point I had a hypothesis, so I pulled the same file from the older 1.06 ROM which was rock solid and did not have the “Cannot Connect” problem. In this EXT ROM it is named Default_Version_WWE_106150.sa.CAB.
Installed it first on my Blue Angel as a guinea pig, then for the next three hours I would sit there and disconnect and reconnect. I did it manually by holding the red button to disconnect, then I would reconnect to another webpage, then would have a call come in while in the middle of the GPRS session which would suspend it. After done with the phone call I would reconnect manually by clicking connect as well as by just hitting a link on the webpage.
The Results: No “Cannot Connect” problem.
So off I went to my Magician:
Upgraded to 1.11(I have 850 JAM)
Installed Default_Version_WWE_106150.sa.CAB
Put the phone through its paces, I have been disconnecting and reconnecting without a single problem. I receive phone calls that suspend the GPRS session and I am able to reconnect without a problem. Activesync is able to make OTA connections without a hitch.
During my trials I used the same programs:
Which included:
Photo Contacts(newest version)
Activesync
WEBIS Mail 2
xVbar
PocketZenPhone
Regking 2003
As the only variable throughout the trials was Default_Version_WWE_106150.sa.CAB
This is the solution folks.
At least until someone says it does not work.
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
1st of all let me say this is a great site for the HTC devices, I found it years ago when i had the first XDA (Wallaby i think) and now i own a O2 Mini.
I have just installed your patch and i'll let you know how it goes.
I wonder if this patch does the same as the "downgrading" of the caller id as detailed in this thread: http://forum.xda-developers.com/viewtopic.php?t=20428
The downgrade has been succesful for blue angel users too.
randomshots said:
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
Click to expand...
Click to collapse
Many thanks for posting this information.
For a relative newbie like me who has never manually fiddled with ROM files, can you please explain what I actually have to do to "install" the CAB file, i.e. in which directory on the device do I put it, and how do I run it?
- Peter
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
don't work for me
don't work for me. same problem as before, can't connect due unknown reason.
thanks anyway.
Orcas what is your ROM?
randomshots said:
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
Click to expand...
Click to collapse
The downgrade of caller-id to an earlier version has also solved the problem totally for me and several other people, both blue-angel and magician users. Thats why I was curious just what your patch did. Seems that it is something similar, you are maybe downgrading more of the rom?
Did you try downgrading of the caller-id first? Not just photo contacts but downgrade to the specified earlier build of caller-id?
randomshots said:
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Click to expand...
Click to collapse
Hi there,
Just thought I'd report that I've just installed it. My ExtROM now reports as 1.06.150 WWE.
And... so far, so good!!! I've connected/disconnected to GPRS multiple times, interrupted GPRS with a phone call and then reconnected, have sent files to my device via BT while GPRS is on, and still no problem. It's looking very good!!!
And I'd swear it connects faster than it did previously.
Anyway, I'll keep hammering at it over the weekend and report back on Monday.
Thanks again randomshots!
Well, I'm back already, because I still have the problem. DARN IT!!!!!! :x
The thing that made it happen was that I made a phone call while GPRS was on. When I ended the call and tried to reconnect to GPRS, I got the blasted error. So it seems that receiving a phone call does not cause the error to happen, but making a call does. At least for me.
Oh well, it was worth a try. Back to the drawing board.
Same problem in Hong Kong
I upgraded to ROM v1.11 a few days ago and since then I have the GPRS connection error after 1 or 2 connections. Soft reset will solve the problem. This problem was not encountered at all before the ROM upgrade. It must be the new ROM that mess things up!
As this "default cab" from an old rom seems to solve the problem and also an older version of caller-id solves it there is probably something wrong in the communication between caller-id and some of the customisations from this cab on newer roms. Btw the problem is also in 1.12 roms.
Nice too see that we have two possible solutions here, I will stick to the downgrade of caller-id as it has solved the problem totally for me but it would be interesting to know what the real cause is...
Hi again. Just to answer the previous question to my post: my rom version is 1.12.00 WWE, radio 1.12.00, extrom now says 1.06.150. i think the only thing this cab changes is this rom number, nothing else
orcas
orcas,
I believe you are absolutely right. When the extended rom has finished installing the programs, it runs this .cab file to 'brand' the Magician with the build number. Nothing more or nothing less. But faith can move mountains, as we all know...
I guess some of you know that there is another (older) thread about GPRS problems. If you do not, there is a link below.
Anyway, I finally tried the most recent suggested fix in that thread (downgrading the device's CallerID program to an earlier version) and like a number of others I can happily report that so far, it has fixed my GPRS cannot connect problem. Looking good.
Here is the thread:
http://forum.xda-developers.com/viewtopic.php?t=20428
- Peter
Just thought I'd share that the second fix I tried (downgrading CallerID) has continued to work for me. I have no more problems with GPRS. All is well with my Magician. At last.
Has anyone else found that PocketZenPhone doesn't work properly after upgrading their ROM (O2 Exec) ?
The profiles switch, but if I click on the settings icon it doesn't do anything so can't customise profiles
Have just downloaded latest version of PZP and makes no difference...
i too can't open the settings but no rom upgrade was done. zendrui is aware of it but we couldn't figure it out why. my other option is to hard reset but decided not to. let me know if you figure it out.
Works for me...
The only thing I've had difficulties with lately is that the .txt files appear to be out of step with what the programs expects to see, somehow.
Try reinstalling with the ones that come set up with the program, then recustomising those ones? That's what I did, and now it works fine (though this was BEFORE the upgrade).
Ant
Got it working now - hadn't installed the PZP tools CAB properly
Hi
I have discovered this site just now as a was searching for information on how to updrade by qtek9100 for a2dp and use a bluetooth stereoheadset with it.
I found some leads but they all ended in my not being allowed to change the registry settings for
"local machine"\drivers\BuiltIn\"
I can not add BuiltIn\BtA2dpSnd and therefore not conclude the setup.
Is there anyone who can give me some advice on how to go about this ?
I have updgraded to the latest official ROM for sweden.
Lars
Try the CAB file attached
You might have to unlock your phone before you try and change the registry settings.
lars_s_e said:
Hi
I have discovered this site just now as a was searching for information on how to updrade by qtek9100 for a2dp and use a bluetooth stereoheadset with it.
I found some leads but they all ended in my not being allowed to change the registry settings for
"local machine"\drivers\BuiltIn\"
I can not add BuiltIn\BtA2dpSnd and therefore not conclude the setup.
Is there anyone who can give me some advice on how to go about this ?
I have updgraded to the latest official ROM for sweden.
Lars
Click to expand...
Click to collapse
The cause for the problem may be one of the following:
1, you used a desktop ActiveSync-based registry editor.
Don't use desktop tools to chage the Registry. As is pointed out in my Registry Editor Bible, it won't work. Use a PPC-only registry editor.
2, you didn't shut down the PPC entirely after this (or waited long enough for the changes to be written to the Flash ROM as is explained in many of my WM5 & registry & flash ROM-related articles); this is why the changes haven't been stored.
Note that this has NOTHING to do with your phone's being locked. You do NOT need to unlock your device.
This is one of the issue of bother me most for X1. Apply this fix (driver taken from HD), install Cyberon Voice commander/Voicedial (search yrself for whatever version you want), and the button on yr BT headset should bring up the app. (Work for my rom w/ Sony DS-205)
http://forum.xda-developers.com/showpost.php?p=3234724&postcount=2
Edit: Sorry bro. Just tried it today on stock R2A image and it's not working. But it's sure working under my rom and therefore probably more files which I already included is needed (mostly files from HD). I am too busy to look into this issue but those files should give you some hints what is needed.
does it works on the original ROM?
jackleung said:
This is one of the issue of bother me most for X1. Apply this fix (driver taken from HD), install Cyberon Voice commander/Voicedial (search yrself for whatever version you want), and the button on yr BT headset should bring up the app. (Work for my rom w/ Sony DS-205)
http://forum.xda-developers.com/showpost.php?p=3234724&postcount=2
Click to expand...
Click to collapse
Jack, I tried to install the fix but when the bar fills up it says that the installation was unsuccessful. I am using your rom v2.4 btw.
I am trying to solve this bluetooth problem for days, I hope this fix will do it for me (if I get it to install).
Have any solution????
XavierGr said:
Jack, I tried to install the fix but when the bar fills up it says that the installation was unsuccessful. I am using your rom v2.4 btw.
I am trying to solve this bluetooth problem for days, I hope this fix will do it for me (if I get it to install).
Click to expand...
Click to collapse
I update the post w/ manual install method which should work at least for 2.4. (just tested and not working for stock R2A rom).
jackleung said:
I update the post w/ manual install method which should work at least for 2.4. (just tested and not working for stock R2A rom).
Click to expand...
Click to collapse
So does it work in your rom or not? (I am using your 2.4). Yesterday I just extracted all the files from the cab and put them on the installation folder of the cab. Then extracted the registry keys I found on the cab and imported them on my X1. Still it doesn't work.
I think that the reason it won't work is that you don't replace the BTAGExtModule key (that in your rom is vcbthag.dll) with another dll. So vcbthag still calls MSVC and Cyberon is never called.
XavierGr said:
So does it work in your rom or not? (I am using your 2.4). Yesterday I just extracted all the files from the cab and put them on the installation folder of the cab. Then extracted the registry keys I found on the cab and imported them on my X1. Still it doesn't work.
I think that the reason it won't work is that you don't replace the BTAGExtModule key (that in your rom is vcbthag.dll) with another dll. So vcbthag still calls MSVC and Cyberon is never called.
Click to expand...
Click to collapse
Oh yes. Please change it back to OEMAGW.dll and let me know yr result.
jackleung said:
Oh yes. Please change it back to OEMAGW.dll and let me know yr result.
Click to expand...
Click to collapse
Unfortunately with that dll it just continues to do what it did before MSVC, "nothing". I wonder how they do it on Touch HD.
I will release 2.5 soon and you can play around w/ it later. At least I am able to call Cyberon VC w/ BT button now.
jackleung said:
I will release 2.5 soon and you can play around w/ it later. At least I am able to call Cyberon VC w/ BT button now.
Click to expand...
Click to collapse
Good news, waiting for your new release.
Jack, I don't see the BT fix on your linked page. How did you finally solve this problem? Is it the method listed in this thread, or something else? I would like to get Cyberon working on my X1a without completely changing the ROM.
UP.... UP..... ?
Hi.
I am having some trouble with my LEO!
When I try to enable bluetooth trough comm manager, I recive a message that says "can not enable bluetooth".
When I am going on advanced settings menu and touch the bluetooth icon it gets highlighted but nothing happends. All others connections and icon do work perfect.
I have had my device for 3 days, and have never tryed bluetooth on it before. I have stock ROM on it.
Hope that someone can help me with this problem.
Sorry for crappy english! =)
Do you have TomTom installed on your machine? That navigation software can screw up the Bluetooth stack on the HD2 by installing and overwriting WM stock bluetooth files...
Drakknar said:
Do you have TomTom installed on your machine? That navigation software can screw up the Bluetooth stack on the HD2 by installing and overwriting WM stock bluetooth files...
Click to expand...
Click to collapse
Yes, I have tomtom installed. Is my only option hard reset, and never use tomtom again?
When device is starting up I got a warning: BTTrayCE.exe is not a valid pocket PC program.
Any ideas?
It's very simple to fix this:
remove BtCoreIf.dll from Windows folder and softreset.
ghale said:
It's very simple to fix this:
remove BtCoreIf.dll from Windows folder and softreset.
Click to expand...
Click to collapse
Thank you so much! It is working perfect now! =)
You're welcome.
Same problem, trying to apply the same solution, but can't delete the file. I've tried with Total Commander but it says it can't! Any ideas what the 'user error' here is?
Please check if the attribute of the file is ROM.
If is ROM, then you have the original file.
If ROM is not set, then try to soft-reset the device then with the native file manager choose "Show all files" and delete the file.
Then soft-reset again.
It is read only, system and in ROM according to Total Commander. The native file explorer has now lost the delete option completely! Properly stuck now!
It's a normal behaviour of the file Explorer. You can't delete a ROM file.
You have the original file.
Try to delete BTTrayCE.exe, then and then restart.
It will be restored automagically.
Let me know.
That is also a ROM file and won't delete.
Ah!
I don't know, then, what is the problem.
What type of issue you have on your mobile?
Exactly the same as the OP, when the phone starts it has a Bluetooth Error, then won't start Bluetooth.
Ok, but you can write what message you see, exactly, please?
paulrockliffe said:
Exactly the same as the OP, when the phone starts it has a Bluetooth Error, then won't start Bluetooth.
Click to expand...
Click to collapse
Factory reset will fix it, and was for me the only way to get it to work again.
For fun.. Try your FM radio. It does also not work anymore!
Sorry, I can't help you, then.
Yes, unfortunately in some cases it's impossible to delete the files modified by the TomTom install. At first I have done a hard reset, too; then I prepared a modded TomTom CAB file without the BT drivers so that now everything works fine. If you should need it, I can upload it somewhere.
Hmmmmm! I'm not going to run a factory reset until I can put HSPL and a modified ROM, it's a pain not being able to use my bluetooth headset, but not worth the hassle of reinstalling everything. While I'm waiting I'm going to try out loads of other bits of software and workout how to use Sashmi etc to make it much easier to restore everything when I change ROMs.
Drakknar, if you could upload that file somewhere that would be useful, not just for me I'm sure. Maybe email it to the guy who's doing the hints and tips thread to attach it to that perhaps?
I'd be glad to share the link with everyone, but I think that posting a link to TomTom Cabinet in XDA-Dev would be against the rules. If it's allowed, I'll send the link to the author of the tips n tricks post, otherwise I can send a PM with the updated .cab to those who are interested
Drakknar said:
Yes, unfortunately in some cases it's impossible to delete the files modified by the TomTom install. At first I have done a hard reset, too; then I prepared a modded TomTom CAB file without the BT drivers so that now everything works fine. If you should need it, I can upload it somewhere.
Click to expand...
Click to collapse
maybe renaming the file will work?