Related
Hi guys,
I have searched up and down this forum and other forums, some problems get close but none of them hits the spot.
I am using an HTC Touch with Windows Mobile 6 Professional, Version: CE OS 5.2.1238 (Build 17745.0.2.3) and link it via Bluetooth with the car navigation system Becker Cascade 7944.
The link is established but calls are muted. Becker had this problem with some other phone models too and brought out an update version 3.7.
Now the calls are not muted anymore, but the sound is distorted. It sounds like the loudspeaker is broken. In short: not usable.
I posted this problem with Becker and after the update version 3.7 they sent me this mail (translated from German):
Dear xxxxxxxxx,
the System-Software 3.7 was sent to a lot of customers as update. Only
positive results came from this and we did receive no negative replies or
complaints except for two models from HTC.
Please contact the manufacturer of the mobile device and ask for a
possible software update.
We regret we can’t give you any other answer.
Sincerely
i. A. Martin xxxxxx
HARMAN/BECKER Automotive Systems GmbH
Quality Customer Service (QC)
Becker-Goering-Straße 16
D-76307 Karlsbad
Then I sent a fax to HTC Europe headquarters asking them for support and /or a solution. Nothing heard from them.
I then sent a fax with the HTC Europe headquarters fax attached to the Chairman of HTC (see www.htc.com) in Taiwan. Same result, no reply!
In the french forum www.planete-htc.com they have a post that the CAB-file WM6_BT_DUN.cab could solve the problem. I have not installed this file yet, since I don't know what it does or if it solves the problem.
Could it be that HTC uses a different bluetooth stack or CODEC-files?
Can anyone help me?
Thanks a lot
baucis99
Hi!
I've got the same problem with an other phone from HTC (MDA Vario 3 from T-Mobile) and my Becker Cascade. Spoke with Becker, no solution in sight. They said I've to talk with the producer of my mobile ..... grrr.
Bye the way, if you make a call and after being connected with the other side you can press "private" in the options menu to give the call back to the phone. Then again press "private" in the options menu and you have a clear connection without distortion!
Bye, Peter (Germany)
PS: Tried the CAB-file, no change
hi @ all I have the same problem with a becker Casscade pro and Firmware 3.61 and - now - 3.70.
This problems is only with HTC devices that have installed Windows mobile 6, (Wings, Kaiser, Touch..) with the older ones like T-Mobile Vario and Windows Mobile 5 it works fine.
by the way the same problem, the other side hear no sound from you, and you hear the other scrambled
and it is not depend to use Sim access profile or normal earphone profile.
maybe i think, the Becker car radios are not longer supported from the manufactur..
the right way is, to change the bluetooth stack on the HTC devices. there are some parameters between mobile and bluetooth called EHR
and this parameters are wrong. maybe by HTC configuration or Becker
A Nokia E61i and many other WM5 devices works well with Becker casscade pro.
i can try tomorrrow some AT&T Models with windows mobile 6 (Samsung and some other) maybe they works...
soon, now i test a becker casscade with a samsung shg 6xx smartphone with WM6.
BT Profile works very well with casscade 3.70 firmware.
so it´s a problem of all actually HTC devices with WM6 i think.
maybe we should change the BT Stack was inatlled as default...
joy.d said:
soon, now i test a becker casscade with a samsung shg 6xx smartphone with WM6.
BT Profile works very well with casscade 3.70 firmware.
so it´s a problem of all actually HTC devices with WM6 i think.
maybe we should change the BT Stack was inatlled as default...
Click to expand...
Click to collapse
Hi joy.d,
I thought of the same solution.
I tried one of ROM cooking guys in this forum about how to change the BT software, but no reply.
Do you know how to change the BT stack on the HTC?
By the way I am using the HTC with the Jabra BT320s and the Plantronics Discovery 640X. Both work well.
And the Cascade worked and works with all other phones I know of. There is a forum in Germany for the Cascade and they report only problems with the HTC.
Also, some in this forum have reported BT problems with the HTC Touch.
So, please let me know if the BT software upgrade/change works.
Take care
baucis99
hmm.. i have no time to cook my own rom with fixed bluetooth drivers. (maybe the actually bt version from broadcom, better knows as widcomm stack works well) we think in our company to change from htc to other manufactor, the bt problems not the only one problems ;-)
but if i found somethink i will tell you please let me know if you find something.
p.s. the BT update for htc kaiser dont change or helps.
maybe becker has a problem with her integration of bluetooth.. with the most bluetooth headsets works the htc devices. (i test over 20 different BT Headsets with HTC devices, but the most with WM5)
Same problems
I have the same problems. HTC Mobile 6 with Becker Cascade. To work around this issue, press [Private] in the [Options]Menu, once in a call, and then return back following the same keysequence.
According to the User Manual, Becker only supports the bluetooth HFP1.0 profile...
Hmm, and the Windows Mobile 6 Devices supports:
A2DP (Advanced Audio Distribution Profile)
HFP1.0 (Hands-Free Profile)
HSP (Headset Profile)
It´s work with a Samsung blackjack, so i think the Problem is by the provided BT Stack from HTC..
Headset profile
When the connection to the phone is made, a headset icon appears in the upper homescreen. It seems that the headsetprofile is initially used. When you execute the private workaround, the phone switches to handsfree...
hmm, i tried it with this private funktion, but the quality of sound is not really good or better. is not a really funtional workaround. I have test the Becker cascade now with an Asus P750 Phone, and it works well too..
i think it is a HTC Problem.
Cascade Pro + HTC Kaiser
Hi Guys
I am experiencing exactly the same problem with my HTC Kaiser and Becker Cascade Pro 7941. It really makes you upset when no one helps you, becker says its handset manufacturer's fault and HTC dont even bother to reply.
yes, that´s sad. if you found a solutions let it know us, in germany, there are some more users with exactly same problem. :-(
joy.d said:
Hmm, and the Windows Mobile 6 Devices supports:
A2DP (Advanced Audio Distribution Profile)
HFP1.0 (Hands-Free Profile)
HSP (Headset Profile)
It´s work with a Samsung blackjack, so i think the Problem is by the provided BT Stack from HTC..
Click to expand...
Click to collapse
Hi... not 100% related, but I have an HTC VOX and that works fine with the Becker High Speed Pro 7945 (same software as the Cascade) which I recently flashed to v3.6. The Becker works fine with 2 other HTC phones that I have, SP5 and SDA. The only difference is that the VOX actually displays the signal strength bars on the Becker bottom RH corner...
NOT all roses I am afraid as since I flashed my Becker, I lost ALL navigation functions..... but all other functions including the phone still work...
hi fwd, but your Fox and the other devices is running with Windows mobile 5, right?
With WM5 all devices from HTC works fine with becker
joy.d said:
hi fwd, but your Fox and the other devices is running with Windows mobile 5, right?
With WM5 all devices from HTC works fine with becker
Click to expand...
Click to collapse
Hi joy.d...
HTC VOX is a WM6 Standard (one of the first I believe)
SP5 is WM5
SDA is WM2003 Second Edition
uhh, jey thats right, is a HTC S710 ? I try it the next time, if i have one from my users ;-)
Hmm... sad..
joy.d said:
uhh, jey thats right, is a HTC S710 ? I try it the next time, if i have one from my users ;-)
Hmm... sad..
Click to expand...
Click to collapse
Yes joy.d, the VOX is the HTC S710... sorry should have mentioned that earlier - it is easier just to refer to it as the VOX
baucis99 said:
Hi joy.d,
<snipped...>
By the way I am using the HTC with the Jabra BT320s and the Plantronics Discovery 640X. Both work well.
And the Cascade worked and works with all other phones I know of. There is a forum in Germany for the Cascade and they report only problems with the HTC.
<snipped...>
Take care
baucis99
Click to expand...
Click to collapse
Hi baucis99... are any of these forums in English, and if so, do you have the address ? need some info on transferring maps to cf card...
Thanks
hi snippi
is in german, but feel free to post in english
http://forum.pocketnavigation.de/thread.php?postid=1934905#post1934905
joy.d said:
hi snippi
is in german, but feel free to post in english
http://forum.pocketnavigation.de/thread.php?postid=1934905#post1934905
Click to expand...
Click to collapse
Hey that's a good 'handle' !!!
snippi says DANKE... I will give it a go, thanks again
fwd (aka snippi)
I am in the process of moving from a TP to a TP2, and am configuring the latter, however (and I have seen this problem elsewhere regarding this phone) I cannot get my bluetooth headset to play nice with MSVC. Specifically the button to initiate the call.
I have tried the steps listed by bengalih and all should work. From what I have read, they are using a different bluetooth stack for the TP2 which is the issue.
So I have a few questions.
1. Has anyone got the headset button to activate MSVC successfully?
2. Is there a way to change the bluetooth stack without changing the ROM
3. will changing the ROM fix this? Any way I can tell which ROMS will have a working bluetooth stack?
I have Vodafone UK branded model.
This is I think the last thing that I need to make the phone 'functional' for my daily use, and so would be really grateful for any advice.
crazyC said:
[...]
1. Has anyone got the headset button to activate MSVC successfully?
2. Is there a way to change the bluetooth stack without changing the ROM
3. will changing the ROM fix this? Any way I can tell which ROMS will have a working bluetooth stack?
[...]
Click to expand...
Click to collapse
1. Yes, with certain headsets that will allow a verrry loooong press without turning off.
2. I suppose it's theoretically possible, but I do not know for sure.
3. Yes. Some of the cooked roms work fine with MSVC and bluetooth headsets on the TP2.
Could you give examples of the cooked roms that work?
Cheers
C.
any trick or hack we can borrow from "bt-MSVCworking roms" and transplant in stock roms? maybe a skilled dev might try to do something.... PLEASE guys!
crazyC said:
Could you give examples of the cooked roms that work?
Cheers
C.
Click to expand...
Click to collapse
NRGs Genesis ROM works for me. http://forum.xda-developers.com/showthread.php?t=553506
Gordon
Flashing now and will confirm experience with my two headsets shortly.
EDIT:
Only had time to test the specific problem identified at the start - both headsets work fine now. Hurrah. I do not know the specifics behind why, or if this will apply to all 6.5 based roms. But for anyone desperately seeking a resolution the headset initiation of MSVC, using the ROM above does fix it. And so far the NRG ROM does seem good.
crazyC said:
Could you give examples of the cooked roms that work?
Cheers
C.
Click to expand...
Click to collapse
I currently use EnergyROM version 20090822 (Titanium) with MSVC 1.6.21040.
Thanks to those above for their help.
thank you for the contribution, but for who is keeping stock rom, any possible solution??? I would sell my soul for this...
A "stand alone solution" for Touch Pro2s with an original ROM would be great. Possibly one of the ROM cookers can extract it for us.
Thanks a lot in advance,
Klaus
that would be really appreciated!!!
Got it to work, but...........
Hi I have a TP2 with MSVC installed. I got it to work by editing the regsitry and swapping SDDialer.exe with voicecmd.exe. It works great. I press the button on my bluetooth headset and MSVC is invoked.
The only problem is that the voice commaned that i say has to go through the TP2 microphone not the bluetooth headset microphone. Any one knows how to direct the audio input to the headset microphone???
I am using Miri cooked ROM 23017 with manila v2.5
rgd
Raed
this bluetooth activation is a real bugger!! does the audio from VC go to the device loudspeaker, or BT headset? that would be a beginning, somehow...
any luck with cyberon voice commander yet?
cyberpunk627 said:
this bluetooth activation is a real bugger!! ...
any luck with cyberon voice commander yet?
Click to expand...
Click to collapse
Well I have the Voda version of the TP2 and I also have a spare to play with (I cracked the screen on my first one and got a new one but they never asked for the old one back - it works fine) so I loaded the EnergyROM from a link elsewhere on this thread on to it. My bluetooth headset does not work with the Cyberon Voice speed dial program which I prefer - although this ROM does alow you to put all sounds through the headset. It worked fine on my old TyTn from Voda. Like you said, this is a real bu**er!
Barry
mmmh I'm becoming more and more obsessed with this. I googled everywhere but found anything... someone reports msvc and cvc as working, someone else not.. but nobody says it's working from BT headset... blame on htc that forgot such an important thing!
cyberpunk627 said:
mmmh I'm becoming more and more obsessed with this. I googled everywhere but found anything... someone reports msvc and cvc as working, someone else not.. but nobody says it's working from BT headset... blame on htc that forgot such an important thing!
Click to expand...
Click to collapse
It's all true
I understand that on the Telus ROM MSVC works with Bluetooth out the box
MSVC and CVC do work, UNLESS you want to use Bluetooth, when they don't (with stock ROMS in the EU) ;-)
I'm using MSVC on NRGs Genesis ROM and it works from Bluetooth as it should. If I get a Chance I'll install CVC and give it a try and report back.
Gordon
it would be nice if someone can mange to transplant needed files... I like the bluetooth stack on TP2, really better than usual, but this thing needs more attention from HTC and the 3rd party developers.
msvc is 3 years old as of now, no newer versions, same as cvc... too bad, technology evolved a lot it 3 years, and these programs might improve really really much!! especially the recognition algorythm, and functions.
well, I hope the new wm6.5 will bring some BT improvements for TP2 then...do not want to stick with custom roms yet. keeping my fingers crossed!
should you manage to try, let us know about cvc and make a little comparison for us! you lucky! ;-)
cheers
I´m usign Smaberg´s Touch X "HERO" EDITION and VC works just fine.
GordonTGopher said:
I'm using MSVC on NRGs Genesis ROM and it works from Bluetooth as it should. If I get a Chance I'll install CVC and give it a try and report back.
Gordon
Click to expand...
Click to collapse
As my touch screen has died I am without a TP2, so I can't do this for the moment
Gordon
I've had this problem sometimes on my VZW CDMA Touch Pro 2. my solution has been to turn off the headset and turn it back on. It seems the problem starts for me when I have the headset on when rebooting the phone. Possibly MSVC doesn't detect the presence of the headset or something to that effect.
If my Kaiser and my Leo got the Widcomm bluetooth stack, the Leo's must be broken. (I am coding in vb.net and with the 32feet.net sdk)
If I try to code a simple chat program, it just works in one way HD2 -> Kaiser the other way round it is blocked.
I also tried to code some Remote Control Program, where Happens something similar. I can Control my Kaiser with my HD2 but if I try to do it the other way round the hd2 hangs at "bl.AcceptBluetoothClient()".
Is that Problem known to someone?!
scilor said:
If my Kaiser and my Leo got the Widcomm bluetooth stack, the Leo's must be broken. (I am coding in vb.net and with the 32feet.net sdk)
If I try to code a simple chat program, it just works in one way HD2 -> Kaiser the other way round it is blocked.
I also tried to code some Remote Control Program, where Happens something similar. I can Control my Kaiser with my HD2 but if I try to do it the other way round the hd2 hangs at "bl.AcceptBluetoothClient()".
Is that Problem known to someone?!
Click to expand...
Click to collapse
Hello scilor,
Have you found any solution to the problem?
Thanks,
Adrian
There seems to be no real "solution" but the bug occurs, when you send to much data at once or you do not disconnect on a clean way
I know there are some issues with the Windows Bluetooth stack when they try to connect to certain GMC vehicles. There is a thread here on XDA that has some registry changes that make it work. I did it just a week or two ago to my bosses HD2 and she stopped whining...
Airborne Aircrew said:
I know there are some issues with the Windows Bluetooth stack when they try to connect to certain GMC vehicles. There is a thread here on XDA that has some registry changes that make it work. I did it just a week or two ago to my bosses HD2 and she stopped whining...
Click to expand...
Click to collapse
Where is the thread?
Hello all
I have HTC Desire and a VW with BT Premium Kit, which only supports rSAP.
I have been looking into forums for an application which can enable rSAP on Desire, but I have been unsuccessful in my searches.
Some say that this is working for Android 2.1 Update 1, but I was not able to pair the devices.
Does anyone have this working?
Is there any Android Apps Developer who is willing to try to do this?
Thanks
my desire works well with my VW BT
i can dial and have my contacts available
the only thing which is not working is sms
rSAP
Can you please tell me how you did it?
My VW detects my phone, but says always "phone not compatible" or something like that.
Did you get it working on the first try? Do you have RNS510?
What SW do you have on your desire?
rSAP
Ragardin rSAP for VW i can say the following:
It's not working
If u have new VW (i have Golf mk6) with new RCD/NCD 510 multimedia and u have bluetooth kit for mobile phone, Desire will not be able to be found by your/mine media system, coz android haven't this stupid rSAP protocol. I can't explain how mad I'm now about this. It has more than 10 protocols for BT, but not rSAP.
So i bought Desire today and turned it back in store 30 mins ago. This is extremely good device, but without rSAP its useless for me...
I took HD2 and i will turn it back as well btw
I hope that some1 could tell us, is the rSAP support hardware option or software. If its hw option - than it sucks...
Dear friends, please, follow the link:
http :// code .google .com
and add stars to "Issue 4402: rSAP / Sim access bluetooth profile"
Hope this action could help us.
android rSAP
yes, I already starred this issue with rSAP. It is soooo frustrating - having 2 perfect devices, desire and passat with handsfree, and they cannot speak together - really frustrating. Old parrot handsfree had no problems!
If anyone has a solution, please let us know.
are there any news on rSAP development ?
I have hope that some smart developer will figure it out, how to add it to andorid....
Best regards!
maybe this could be helpful for a developer:
http://allforfreelancers.com/getafr...Android-iPhone-J2ME-Nokia-Symbian-726296.html
Regards!
I am wondering why there is absolutely no response on rSAP development discussions?
Is it because no developer has a clue what needs to be done and if there is (even a tiny) chance to develop rsap support for Desire or is it just the lack of any interest from the side of the developers?
I am sure a lot of people would actually buy the app or upgrade that would enable this feature, so interest should be there...
I guess the main reason why nobody has written an app so far is that the necessary funtions for accessing the SIM card are missing in the Android RIL interface. So it will never be possible to write a universal rSAP app for all Android mobiles. Apart from that basic problem there are some other smaller obstacles to master. And of course you will need root access, at least to install the necessary files.
I did some reengineering on the HTC RIL lib and found a way to access the SIM card on the HTC Magic and probably on the Desire. I guess the other HTC mobiles should work too.
Next I've written a test app running on my HTC Magic that implements the rSAP protocol. It was working with an old 2G SIM card before the card expired. I tested it with a Nokia 616 and with a VW Passat. But now I'm having problems with my 3G (UICC) card. Currently I'm still not sure if I get it running but I'll keep on trying.
thank you for your answer and efforts. at least there is some hope that this will work until I sell my car...
did you use some of the Galaxy S libs?
please, keep us informed on the development!
Best regards!
No, I don't have a Galaxy.
Of course I'll let you know when I have it running. But it will take a few weeks at least.
HI rsap.
That sounds like great job!
If it worked on Magic, it would probably work on Dream/G1 as well, am I right?
If it does, would you help me out with it?
Thanks a lot in advance
it would be amazing, if you'd be able to achieve this =)
and i'm sure, people will pay or at least donate for this app! (me included)
thanks in advance!
Another user posted in this forum "Samsing just made the sourcecode (search: Samsung releases Captivate source code) so there seems to also be a ZIP file for the GT-I9000 (European Samsung Galaxy S)."..maybe this could help you further.
Regards!
I will donate!!!
i want RSAP also , any body have the solution yet? i know it works on Samsung Galaxy S but know i have htc Desire HD it only works us hand free profile!!!!
Regards!!
RSAP where are you? Any news?
You should check again the compatibility, with audi a4 mine hasn't been working but with the 2.29.405.2 it's like charm. Sends pb, received dialled calls and everything. Excellent.
It's still not working but I don't give up hope...
I know enough about the RSAP protocol, the HTC RIL lib and SIM cards. If there is someone out there who knows something about the HTC radio software, especially the AT commands it would be helpful. I could not find anything useful in the net.
Works again on my Magic! I need some time to clean up the software port it to Desire (and other HTCs) and make it installable.
I'll let you know!
WOW! Well done!
Would it be portable to G1 (Dream)?
Please, let me know.
Thanks a lot
Hello buddies,
this thread is about some strange behavior of bluetooth with current energy roms. details follow...
why a new thread?
I decided to start a new thread, because it leads to nothing to discussing this topic in the main thread ... found some people who shares my sorrow, never the less there was a lot of users who hit the answer button on page 1 and report "problem xy" or "hell yeah what a nice rom"
what is the problem?
I'm not able to pair my TouchHD with my car's Hands Free system. A2DP works fine, but when I turn on the Radio Unit a small blue headphone symbol blinks in the statusbar of the phone - no pairing succeeds. If I switch to BT audio, a black headphone symbol stays resident and the media player opens for playback, so A2DP works. Installing SIM access profile on roms without built in rSAP or other various tools in addition doesn't make it work. [see "what have been done" section!]
Just used the latest MIRI-Roms (discontinued) and it works like a charm for me. After initial setup, Hands Free (version 1.5) and Wireless Stereo where installed and activated - Serial Port left out unchecked. Then a popup message informs me, that a BT-Device is trying to access phones phonebook remotly - all went fine.
as reported by other users, this behavior occurs since ~may versions of energy roms...
about the environment
Using energy's rom on TouchHD [Blackstone] T8282 [BLAC100 32M]
flashing with USPL
phone's SPL: stock SPL-1.54.0000
radio: 1.12.25.16D3 - don't see a reason to update
protocoll: 52.60.25.33U
carrier: O2 GERMAN
what have been done so far?
I've tested the pairing of my device in various cars
tested with my Renault Megane 3 integrated car kit (arkamys audio / parrot)
tested with a 2010 Toyota Prius car kit
tested with a subaru 2010 car kit
tested with Blaupunkt Toronto 400 BT head unit by phitsc
I've tried programs, suggested by the xda community
installed Bluetooth_SAP_Profile.CAB
installed BT_SAP.cab
installed Gooru_Sense_BT_A2DP_Fix_Cab_by_JVH3.CAB
installed HeadsetFix.cab
installed JetBTHFExt_1.40.CAB
reg-tweaks on "HKLM\Software\Microsoft\Obex\ObexServiceMask"
roms tried
Miri_WM65_21891_Premium_Manila_2.5_V20.0_NoHtcMessaging.rar
Miri_WM65_21893_Premium_Manila_2.5_REV22.0.rar
Energy.BLACKSTONE.23563.Sense2.5.Cookie.HomeTab.Apr.23.7z
Energy.BLACKSTONE.23566.Sense2.5.Cookie.HomeTab.May.01.7z
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.16.7z
Energy.BLACKSTONE.21903.Sense2.5.Cookie.May.16.7z
HD_Miri_6.5.X_23541_SENSE25.rar
Miri_WM65_21893_V38.0_Premium.rar
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.22.7z
(green indicates a working rom)
dear community...
please use this thread wisely for recommendations or suggestions on this topic. keep this thread a productive discussion. if you have a contact to NRGZ, feel free to report this thread, cause my afford to reach him fails.
So I hope we can figure out, why it does'nt work as it should to...
kindly regards, FS
Hi,
I have the same problem with my Touch Pro and my Megane 3.
I have to switch back to an older version of the rom then..
Hi,
I'm using Energy ROM Titanium 18may.
Radio 1.17.xxxx
No problem here with BT of my car stereo.
I had this problem untill I delete the old pairing on the car BT.
After this, the phone pair great
firespawn said:
Hello buddies,
this thread is about some strange behavior of bluetooth with current energy roms. details follow...
why a new thread?
I decided to start a new thread, because it leads to nothing to discussing this topic in the main thread ... found some people who shares my sorrow, never the less there was a lot of users who hit the answer button on page 1 and report "problem xy" or "hell yeah what a nice rom"
what is the problem?
I'm not able to pair my TouchHD with my car's Hands Free system. A2DP works fine, but when I turn on the Radio Unit a small blue headphone symbol blinks in the statusbar of the phone - no pairing succeeds. If I switch to BT audio, a black headphone symbol stays resident and the media player opens for playback, so A2DP works. Installing SIM access profile on roms without built in rSAP or other various tools in addition doesn't make it work. [see "what have been done" section!]
Just used the latest MIRI-Roms (discontinued) and it works like a charm for me. After initial setup, Hands Free (version 1.5) and Wireless Stereo where installed and activated - Serial Port left out unchecked. Then a popup message informs me, that a BT-Device is trying to access phones phonebook remotly - all went fine.
as reported by other users, this behavior occurs since ~may versions of energy roms...
about the environment
Using energy's rom on TouchHD [Blackstone] T8282 [BLAC100 32M]
flashing with USPL
phone's SPL: stock SPL-1.54.0000
radio: 1.12.25.16D3 - don't see a reason to update
protocoll: 52.60.25.33U
carrier: O2 GERMAN
what have been done so far?
I've tested the pairing of my device in various cars
tested with my Renault Megane 3 integrated car kit (arkamys audio / parrot)
tested with a 2010 Toyota Prius car kit
tested with a subaru 2010 car kit
tested with Blaupunkt Toronto 400 BT head unit by phitsc
I've tried programs, suggested by the xda community
installed Bluetooth_SAP_Profile.CAB
installed BT_SAP.cab
installed Gooru_Sense_BT_A2DP_Fix_Cab_by_JVH3.CAB
installed HeadsetFix.cab
installed JetBTHFExt_1.40.CAB
reg-tweaks on "HKLM\Software\Microsoft\Obex\ObexServiceMask"
roms tried
Miri_WM65_21891_Premium_Manila_2.5_V20.0_NoHtcMessaging.rar
Miri_WM65_21893_Premium_Manila_2.5_REV22.0.rar
Energy.BLACKSTONE.23563.Sense2.5.Cookie.HomeTab.Apr.23.7z
Energy.BLACKSTONE.23566.Sense2.5.Cookie.HomeTab.May.01.7z
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.16.7z
Energy.BLACKSTONE.21903.Sense2.5.Cookie.May.16.7z
HD_Miri_6.5.X_23541_SENSE25.rar
Miri_WM65_21893_V38.0_Premium.rar
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.22.7z
(green indicates a working rom)
dear community...
please use this thread wisely for recommendations or suggestions on this topic. keep this thread a productive discussion. if you have a contact to NRGZ, feel free to report this thread, cause my afford to reach him fails.
So I hope we can figure out, why it does'nt work as it should to...
kindly regards, FS
Click to expand...
Click to collapse
Mine works fine without any cab fix.. your pda must search 4 a car kit as a bleutotth headset! comm manager /bluetooth/ set up BT headset turn your cars BT on and there you go!! i tell yo the energy roms work fine 4 me
+ 1 here
Don-Maco said:
Mine works fine without any cab fix.. your pda must search 4 a car kit as a bleutotth headset! comm manager /bluetooth/ set up BT headset turn your cars BT on and there you go!! i tell yo the energy roms work fine 4 me
Click to expand...
Click to collapse
sorry dude, not much help but i have the same experience; all energy roms (and i do mean all of them) work perfectly with my parot CK3100 but then i do task 29 before every flash & hard reset a few times after initial setup.
in addition, i also flash the latest stock rom from htc every so often.
i know this seems a bit ott but i rarely seem to suffer the buggy issues that many others do.
hope you get it sorted
It is not about Task 29.
I had problems with access through the original multi-functional touch panel in the Ford Mondeo. When I went to CLEAN ROM, all troubles are gone. The problem is that you must agree with access on the phone. This question is not on Energy ROMs displayed. I can pair phone but can not be used for handsfree calling.
Now I have a CLEAN ROM and everything is bugfree.
To be honest, no ROM to date consistently works with the in-car bluetooth kit in our Zafira. It works flawlessly with my old phone (K800i) and my wife's phone (W950i) but it's just not stable for the HD.
If it works, it'll drop the bluetooth connection after about 15mins. It's as if there is a time-out, but I've hunted the registry and both HD Tweak and Adv. Config for anything related to this but with no joy.
My current ROM seems to be about the best so far (kwbr's WM6.5 and Manila 2.1) but it still drops the connection randomly yet other times it may keep the connection for over an hour no problems.
Seems very very strange to me, but from what I've read, it's a common issue with the bluetooth kits in GM's euro cars (Vauxhall, Saab, Chevrolet etc.)
|WWE|BLACKSTONE|¯`·.¸¸.- Energy -.¸¸.·´¯ |BlueTooth CarKit ISSUE|`·.¸¸.·´¯`·.¸¸.·´¯)
@DaRulah
what kind of rilphone / radio rom do you use - pointing my research in this direction, may that's the reason... does bluetooth depends on the used radio rom?
@raistlin74 / @Don-Maco
tried all ways possible
car to phone
htc comm mgr to car
windows BT settings to car
@superseagull
having the latest carrier rom flashed before (comes with SPL 1.54 to enable flashing of 6.5+ roms)
what kind of rilphone / radio rom do you use? [EDIT: saw it in your signature ]
@malson
well, sounds logic ... the pairing won't succeed cause the phone's dialog to allow access doesn't appear. will try it with energy's titanium rom. never the less, the outdated MIRI roms /w sense 2.5 and windows mobile 6.5 works for me
@jonifen
as mentioned, the phone is compatible with my car - in basic. simply doesn't work with energy roms.
therefore I tried it with various other systems to exclude a mismatch with my car kit
well, thanks for you participation so far - may we get the clue with my problem
regards - FS
2 options?
Why only two options yes and yes? Why not a no option in the poll? I don't have a problem with nrg roms.
firespawn said:
@DaRulah
what kind of rilphone / radio rom do you use - pointing my research in this direction, may that's the reason... does bluetooth depends on the used radio rom?
Click to expand...
Click to collapse
Radio: 1.14.25.35 with the matching rilphone
Rom: Energy.RAPHAEL.23569.Sense2.5.GTX.Themed.May.13
i don't think it's a radio problem since i used that one with older energy roms, and had no problems with my car kit.
no problems here
I tried my phone with a bluetooth carkit in a BMW X5 and found no problems with it. I use latest NRG rom 21905 with CHT and latest Radio (1.17) with Rilphone 1.15. i suggest u upgrade to those as well.
GL
As this is about a genaral pairing problem I don't know if it will help u as u seem to be able to pair but just have Handsfree problems...
But as u didn't mention how u tested out the fixes I will post this here.
Remember i had a problem once when trying to pair my HD.
Base:
- Touch HD with some newer Sense 2.5
- A2DP wasn't working or Windows Mediaplayer hooked A2DP keys
AFTER I tried to fix A2DP problem (installed some "fix" cabs u mentioned above) I wasn't able to pair anymore.
Here is what i figured out:
- To get it working again it didn't help to over-install another fix - don't know why but seems that some fixes do reg changes wich break other ones.
- I had to hard reset the device
- so never try to install 1 fix after another to figure it out
- always do 1 hardreset + 1 fix then hardreset again
- only really good working fix for me was HeadsetFix.cab I posted in NRG thread - many other fixes broke my pairing capability
Now im on:
- actual NRG 2. June MaxSense 23xxx
- HeadsetFix.cab installed (otherwise Windows Mediaplayer pops up or it doesn't work for me)
- haven't had problem with pairing since several month with any NRG Rom (before it wasn't depending on NRG but on Sense 2.5 / but just had A2DP issue - pairing issue just with wrong fixes installed)
Radios I tested were .12 and .14
Tested BT Headsets/Caraudios:
- Motorola HT820
- some Sony MEX BT xxxx Caraudio
BTW for all who are interested in - i always install "AutoA2DP" or "AutoActiveSync" cause A2DP doesn't pair automaticaly in my car - just the Handsfree pairs by default.
Mimic NRG style ROM Thread !!!!!!!!!!!!
eddyve said:
Why only two options yes and yes? Why not a no option in the poll? I don't have a problem with nrg roms.
Click to expand...
Click to collapse
Yes + 1
Why only YES and YES option ...
No problems with any BT. Myy HD conects on any BT device that i have with no problems...
*****************************************************
PS: its not nice to use for your thread title the same format and characters that NRG use for all of his roms !!!!!!!!!!!!
Its a bit confusing for regular users and misleading....
And if i was you i will change the title not to mimic NRG ROM threads !!!!!!!!!!!!!!!!!!!!!!!!!!!!
colossus
|WWE|BLACKSTONE|¯`·.¸¸.- Energy -.¸¸.·´¯ |BlueTooth CarKit ISSUE|`·.¸¸.·´¯`·.¸¸.·´¯)
@eddyve
it is a yes poll (or call it simply a counter), because I want to know how many people have a problem like me
@DaRulah
well, good to know
@TheOne741
updating my radio rom asap, just to confirm that the radio version is not the source of my problem ... I will report on this
@FrEcP
thank you very much for your detailed explaination! I also do hard resets between the fixes. I will try HeadsetFix.cab in combination with AutoA2DP on a clean rom
@colossus_r
do you have anything useful to contribute? stay on topic please!
Well, thank you all so far, I will report my progress when the mentioned tips have finished... regards - FS
mimic NRG ROM thread
firespawn said:
@colossus_r do you have anything useful to contribute? stay on topic please!
Click to expand...
Click to collapse
@firespawn: Whats the matter with you? colossus_r is on the right way. Why only "Yes or Yes" in poll. And whats about mimic NRG ROM threads?
Please choose your own style for this thread.
On topic: No problem with Siemens HKW 720 Bluetooth Car Kit at all. Im using Handsfree-Profile and rSAP-Profile.
Issues with bluetooth ...
aleskow said:
@firespawn: Whats the matter with you? colossus_r is on the right way. Why only "Yes or Yes" in poll. And whats about mimic NRG ROM threads?
Please choose your own style for this thread.
On topic: No problem with Siemens HKW 720 Bluetooth Car Kit at all. Im using Handsfree-Profile and rSAP-Profile.
Click to expand...
Click to collapse
Again, it is used as a counter aaand again: stay on topic and stop cryin' like a baby about the choosen subject! I couldn't change it anymore!!!
Please do not post things like: Oh boy, mine is working fine *smiley*, cause this is worth nothing!
Sorry, I'm a bit frustrated, because a productive research on this problem seems to be impossible...
superseagull said:
sorry dude, not much help but i have the same experience; all energy roms (and i do mean all of them) work perfectly with my parot CK3100 but then i do task 29 before every flash & hard reset a few times after initial setup.
in addition, i also flash the latest stock rom from htc every so often.
i know this seems a bit ott but i rarely seem to suffer the buggy issues that many others do.
hope you get it sorted
Click to expand...
Click to collapse
Right is right i also never had bugs since energy roms march 2010
and the opera 10 never gave issues! so some flashers are doing somthing wrong! when using titanium the rom is superbly fast i also spice things up with the htc-performance.cab.
firespawn said:
Again, it is used as a counter aaand again: stay on topic and stop cryin' like a baby about the choosen subject! I couldn't change it anymore!!!
Please do not post things like: Oh boy, mine is working fine *smiley*, cause this is worth nothing!
Sorry, I'm a bit frustrated, because a productive research on this problem seems to be impossible...
Click to expand...
Click to collapse
We cant do any research if we dont have the problem
i think you should swich the the car bluetooth on and keep it pressed till the device finds it! thats what i did on other cars
or you will have to reset the cars bluetooth as shown in the manual
firespawn said:
@eddyve
it is a yes poll (or call it simply a counter), because I want to know how many people have a problem like me
@DaRulah
well, good to know
@TheOne741
updating my radio rom asap, just to confirm that the radio version is not the source of my problem ... I will report on this
@FrEcP
thank you very much for your detailed explaination! I also do hard resets between the fixes. I will try HeadsetFix.cab in combination with AutoA2DP on a clean rom
@colossus_r
do you have anything useful to contribute? stay on topic please!
Well, thank you all so far, I will report my progress when the mentioned tips have finished... regards - FS
Click to expand...
Click to collapse
set up you bT via comm.manager. dont turn Bt on just choose set up bluetooth hdset device etc/ turn you cars bt on an make shure it is visible etc by keeping the on button pressed in while searching with your gsm and thats it i think thats how it worked 4 me and will work 4 every one too!!!
study your old rom be4 you use a new one and you will know how to recognize the differenzesss amen
I've experienced something similar with my volvo. In my case it paired sometimes and usually in a call it disconnected. This happened with all kind of roms. It all disappeared after a radio update.
Somebody mentioned 1.17... with rillphone 1.15... works like a charm!
Hope it helps
(else you can try to let a mechanic update the bluetooth software in your car)