Related
Hi All,
I have been reading a lot of messages on both 8525 and 8125 trying to isolate the issue and there doesn't seem to be a straight asnwer anywhere and hence I am trying to get the attention of the users here...
I have a pioneer navigation system with a bluetooth built-in. My previous phone (blackberry) and my wife's treo650 both stay connected with car's bluetooth when on call (never a disconnect). But my new 8525 gets disconnected mid-call (usually after 2 to 5mins, but have also seen a disconnect within 1min). That is, it does pair with the car kit and when there is no call going on, the bluetooth connection never dies. This disconnect only happens mid-call, almost all the times.
I have the latest ROM (1,34.502...., radio: 1.16), got the phone about 2 weeks ago from Amazon.com. Called cingular and they say could be faulty phone and I have searched other forums like audi message board where their car kits are also having the same disconnect problem with 8525, so I doubt this is a single phone issue.
I have taken the 'band' hack and forced the phone to be in either GSM or WCDMA mode and in either modes, the phone still exhibits the same problem (there might not be any connection between the two at all, bluetooth with GSM/WCDMA, but thought there might be some weird connection...but not the case thankfully).
I read somewhere about some bluetooth tweaks on 8125, but never found what those were. I need some help here otherwise I am going to return the 8525 and stay away from it. I need the bluetooth to work efficiently.
thanks for all your help
Phal
San Jose, CA
please help
I really need some help, clue or direction on solving or at least isolating this bluetooth issue. I love the 8525 but if I cannot fix this bluetooth mid-call disconnect issue, I will unfortunately have to return, which I don't want.
What headsets the 8525 works fine with (no drops mid-call)? May be that is a starting point.
Please also give me some links to 8125 tweaks that some talked about? pof/other moderators/anyone?
thanks a lot in advance!!
Phal
I have an Motorola H700, and every once in a while it will disconnect, looking at the phone after that, BT is turned off, turn it back on and it works again...
There are problems with the hardware and the API used to access it, good phone, but I don't think it was ready for the market yet when they released it. It is likely to be corrected in the next ROM release, last I heard from Cingular is mid 2007, but by the way things go, prolly around late 07/early 08.
I'm having similar issues with the BT headset I use, which is a Samsung WEP150. It'll drop midcall to the handset. I'll look and BT is turned off.
The only remote correllation I've found is that it seems to occur when I've received a new email or something a la ActiveStink.. And I haven't really been able to confirm that... But I have definitely noticed it happening then though.
my 8525 does this as well with my factory BT in my 05 Acura TL. Kind of frustrating, have not been able to figure it out yet.
Problems w/ Audi BT as well
Same issues with my Audi Q7 BT. I have seen posts in this and other forums blaming the MS bluetooth stack.
My 8525 worked flawlessly with my Garmin NUVI 660, never disconnected or failed to connect automatically. This is frustrating.
8525 Fix
I had the same problem with the 8525 and my Pioneer Avic-Z1 bluetooth kit.
I hacked the registry to force the bluetooth radio to stay ON, rather than going into sleep mode. This seems to have fixed the problem (although with limited testing at this point).
My calls would consistently disconnect with 2-4 minutes. After the hack, I've had 2 45-minute+ conversations with no trouble.
Here's the fix... install a registry editor (like PHMedit), and add a DWORD here:
HKLM\System\CurrentControlSet\Control\Power\State\ Suspend
Add a DWORD called btl1: (note the colon, the colon must be there), with a DWORD value of 2.
Good luck!
My Q7 as well i took the advice of wolfgram and did this to my phone i will let you know how it works it would be a shame to give up this phone but it is really useless if this feature does not work right.
Well this is what i did i did what wolfgram said and it still cut out but not as much so i took the checks off in the advance power mode and never let the phone go to sleep and it works all the time. HTC needs to upgrade thier bluetooth setting not to go to sleep. It must stay active at all times MY phone book and all other info posted into my Q7 with no issues at all and it even sees the bluetooth b4 the MMI system in the car Boots up..
Lance
Resolution I think
I turned off 'Making device discoverable to other devices' and it seems to have solved this problem, I am using the phone with a parrot kit and it kept disconnecting now it works all the time.
Treo 750 doesn't have this problem
Well, hopefully you owners of Hermes have figured out the fix. I had to return it and now got the Treo 750 and can gladly say the problem is not there. The treo 750 has the v1.2, but I guess following the replies here, that possibly Palm fixed the problem by keeping the BT radio on at all times.
In any case, here is the post I wrote in avic411.com forum - if you want to see any follow up responses by other owners..
http://avic411.com/forum/viewtopic.php?p=24170
cheers
Phal
Bluetooth cut out
I am having the problem too with the garmin Nuvi and the Tytn - which is ineresting seeing as how one poster had no problem with the Garmin device. Here is something else that is interesting - I did not have the problem when I had the HTC 1.18 Rom installed. After I flashed the HTC 1.35 Rom, the problem began. I have already tried upgrading my firmware on the Nuvi - that did not help. I also use a Nokia 800 bluetooth headset - and that never cuts out with either ROM. I will try turning off the bluetooth discovery first. If that does not work, will try editing the registry. Keep you posted.
Turning off bluetooth discovery did not work.
Turning Off Bluetooth Did Not Work For Me Either
this worked for me.....
http://forum.xda-developers.com/showthread.php?t=247520&page=10
drains the battery quicker, but no more bluetooth problems.....
Hey guys, has anybody found a solution for the auto turning off of the BT in suspend mode? its gettin really annoying
ok.. I read a couple of threads regarding this issue but could not find any solutions. one guy said that ak3.3 fixed his problems but 3 have a spv m3100 and I don,t know wich update pack should I choose besides cingular wich doesn't have video calling.
Any thoughts?
Doesn't anybody have the same issue and managed to solve it?
I had the same issue when I upgraded to WM6, I fixed it by installing the GPS radio ROM. This fixed it straight away.
In installed the latest 1.35 ROM and that did not fixed it and even with XDA live that did not work. Where can I find the GPS Rom?
andrei318ti said:
Doesn't anybody have the same issue and managed to solve it?
Click to expand...
Click to collapse
My 8525 was disconnecting from my car constantly after getting the phone a few days ago. My TyTN never had this problem. Even after installing the exact same ROM onto the 8525 that was on my TyTN I still had the same problem.
Basically, after a minute or two of being connected to my car the bluetooth on the phone would turn off. It didn't just disconnect. It turned off completely. This phone did it just like the Treo 750v (very unreliable phone by-the-way) did.
The problem appears to have gone away now that I have installed WM6 on my 8525. I have not done anything special to get it working aside from installing the LSVW WM6 ROM. It is definitely worthwhile to give it a try.
I believe that 1.35 is the "GPS enabled, but not initialized" rom.
OJ2000 said:
I had the same issue when I upgraded to WM6, I fixed it by installing the GPS radio ROM. This fixed it straight away.
Click to expand...
Click to collapse
I had it fixed by changing the registry values for bluetooth power saving. Upgrading to VM6 and to radio rom 1.35 (gps enabled) bringed back the problem... now I cannot find anymore what registry value I had changed...
stepir said:
I had it fixed by changing the registry values for bluetooth power saving. Upgrading to VM6 and to radio rom 1.35 (gps enabled) bringed back the problem... now I cannot find anymore what registry value I had changed...
Click to expand...
Click to collapse
Ohhh....please try to find them because I searched high and low and still no solution.
Try this:
http://forum.xda-developers.com/showthread.php?t=245887&highlight=bluetooth+power+saving
Ok I tryed the small fix on that link and did not work at all. I also inslled WM6 LSVW and still nothing. Any other ideas?
Try this: "jetware.hands-free.extension.1.24".
Installing the leaked Cingular ROM fixed the problem for me. Prior to this, it would connect briefly, then disconnect, and would come and go, but mostly would not connect. Now, every once in a while, it disconnects very briefly, but for the most part is solid.
Tryed jetware but still no go. Any other idea? doesn't anyone that has a hermes use a car handsfree bluetooth system? From what I know all devices suffer from this?
Nothing? Hasn't anybody found the solution to this problem? From what I read it happens to almost all hermes devices.
Yes, had the same problem.
Have a SPV M3100 with the Audi A4 Bluetooth (part of Gen II GSM Prep).
My old MDA Vario worked flawlessly.
SPV3100:
1. Pairs and makes / receives calls.
2. After 10-15 Mins calls are not routed through car kit.
3. When making / recieving call after 10-15 Mins, handset thinks its connected to handsfree (headset symbol in phone dial pad) but car does not pickup call hence no handsfree and no sound in handset ear piece!
4. Occasionaly, handset reconnects to car handsfree automatically on an incoming call.
5. Connection of in car charger SEEMS to improve realiablility.
6. Switching Bluetooth off then on on the handset will initiate a new connection that again works for 10-15 Mins.
Mark
temoore said:
Installing the leaked Cingular ROM fixed the problem for me. Prior to this, it would connect briefly, then disconnect, and would come and go, but mostly would not connect. Now, every once in a while, it disconnects very briefly, but for the most part is solid.
Click to expand...
Click to collapse
I get the problem with the new rom also, have been using it for weeks now. The new ROM does NOT resolve the issue, at least with the Acura HFL system.
So it seems that there is currently no fix to this issue.
bsica said:
I get the problem with the new rom also, have been using it for weeks now. The new ROM does NOT resolve the issue, at least with the Acura HFL system.
Click to expand...
Click to collapse
Well, it did resolve it on my '07 Audi Q7.
I tried to contact HTC and this is what I got
Thank you for your enquiry. An IMEI check of your device indicated that it is a network branded phone.
IMEI:? 357719003647231? Network: Orange Romania SA
Unfortunately we do not offer technical support for network branded handsets, as both software and hardware can be altered by the network provider.
Please contact your provider for any support that you might need, including repairs and software updates.
Click to expand...
Click to collapse
Can anyone with a TyTN contact HTC and ask for a solution?
Thanks temoore,
Looks like I need to get my boss to upgrade my car from A4 to Q7 to get the phone hands free to work.
It just might work.......;-)
Hello all. This is my first time posting a new thread although I've been lurking around here for a while soaking up all the information from this wonderful site. That said, I have been researching my problem for days now both here and on google and have found no solutions that work. So I'll see if there's anyone here who can help. Here goes....
I have recently flashed DCD's 3.2.6 ROM on my Verizon XV6800 and it works great (love the aGPS too, Thanks GC14) in every area but my car. I have a 2004 Audi A4 with the RNS-E Nav system with integrated bluetooth. Before I flashed to DCD, I had the original stock ROM (2.09.605.8 with Radio 1.30.00) which gave me full functionality with Jetware Mobile (Phonebook and Recent, Received & Missed Calls all transferred). Now, with DCD, it'll only connect to the car and won't transfer anything. If I try to load Jetware, it'll just lock up my phone while I'm connected to the car. Thanks in advance for any help you can provide.
No one else has this problem or a fix for it?
TGabriele said:
No one else has this problem or a fix for it?
Click to expand...
Click to collapse
I wish I was rich enough to afford such a car, then I could maybe help you out. LOL
But I would gladly accept such a car as payment for figuring out your problem.
Nevermind that the car is an Audi. Does anyone else have this problem with a factory BT system that transfers the phonebook to their car.
I had this same issue on my X3 and it seemed to be the way the PPC wanted to transfer the phonebook was by using some file transfer protocol the car did not understand. I could sync it and make and receive calls but no phonebook. Took it to the sprint store and we tried a blackberry and a standard moto handset. The blackberry did not sync the phonebook either but the standard moto phone did. I don’t think it’s possible based on the profiles in the car so I gave up on the phonebook. Try changing the bluetooth stack in the rom, you will have have to make your own rom and beware of the stack you use to make sure it is one for your phone.
I flashed DCD's rom using the kitchen, so making a custom rom from there is no problem to me. What I'm not sure of is how to change the bluetooth stack. I thought it is part of the hard coding for the OS? If you or someone else reading this thread has any information on this or can point me to some info on this it would be greatly appreciated.
I have the 6800 with DCD 3.2.6, and an Audi, with full phonebook transfer so I'll try to help you out:
1. Which 6800 radio are you using? I have found 3.42.50 to be the best as far as Audi bluetooth compatibility is concerned.
2. Jetware will not work with WM 6.1 on the 6800, but you don't need it, since 6.1 included phonebook transfer enhancements.
3. What version of Audi software are you at? There have been several releases since your year. You should be able to get more info from www.navplus.us and of course from your stealer.
4. You do have your bluetooth settings set for "discoverable", right? And, (I don't know why this is the case) it seems when OBEX is on, the phonebook and other items transfer quicker.
If you have the 6800 radio and Audi software updated, you should have no problem. Jetware is no longer necessary.
1. I am using radio ROM 3.42.50
2. The reason I loaded Jetware is to have it sort my contacts by Last,
First. Is there another way to do this?
3. I am running sw0200 on my RNS-E, but was considering moving up to
sw0260.
4. I haven't tried this, but I will.
Lately I've also had the issue where if the phone is connected to the car for a while, the bluetooth on the phone will shut itself off and not turn back on until I do it manually. I'm beginning to wonder if I should just hard reset and start from scratch. Any ideas? Thanks in advance.
I'm sure there's a reg tweak for listing First name first in contacts. Hunt around here or at ppcgeeks. If you want to stay on 6.1 jetware will not work (unless they release a new version).
Definitely update the Audi software to the newest version.
DCD has done nicely fixing power settings in the last few ROMS to solve the bluetooth shutting off issue, although when memory gets very low, it may still happen. You must have some other program or process running that sucks up memory if you are still experiencing this.
It never hurts to hard reset, as long as you have the time.
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
TGabriele said:
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
Click to expand...
Click to collapse
I'm running an after market HU (Pioneer AVH-P4000DVD) and DCD's latest ROM, and Jetware works fine on mine. Just re-transfered my phone book earlier today....
Hello,
I have recently bought the Parrot Minikit bluetooth speaker but it seems that there is something wrong with connection between it and the touch cruise.
pairing is performed with no issues but when i want to make a call it RANDOMSY sometimes transfer audio yo the Parrot minikit but sometimes it does not and the call stays in the phone (which of course makes me unable to hear...)
I really do not know what to do. i have tried several ROMs and several Radios (including the original ones) but it seems the problem is consistant with all of them.
Please of anyone knows if there is someway to solve this problem make some bluetooth patch to the polaris or an alternative bluetooth stack i can install that may help ... or any other suggestions...
Please Help
Thanks
Same problems here. How can I downgrade to BT 1.2?
Hi guys,
This problem was handle before. Just look in http://forum.xda-developers.com/showthread.php?t=437888&page=4
Succes
WAS
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)