Related
Background:
When jompao (his original thread on this is here) brought an interesting A2DP workaround to light I was intrigued:
Apparently there's this free, opensource taskmanager which, when running, corrects the Hermes skipping problem! So I tried it for myself and damn if it wasn't true! Not only did it allow my iPAQ stereo headset to operate w/o skipping but the non skip range on my HS-12W was doubled too!
So, I obtained the code and found out what was going on. Turns out, this free little gem of a task manager determines CPU usage by running an infinite loop thread (it does a "while(1)" for all you code jocks) at THREAD_PRIORITY_IDLE, then, based on a timer trigger, it periodically stops the thread and sees how much time it got. The more time it gets, the more idle the cpu being the rationale here.
btw: Thanks for generously donating your Taskmanger to the opensource community Yuichiro Ishitani!
Anyway, I said to myself "Heck Sleuth, you can build a service process that does this in about 5 minutes". So I did & now I listening to skip-free Jimmy Buffett on my iPAQ headset with my little A2DP fix service running in the background.
heheheheh.....
Installation Instructions
1. Transfer A2DPFix.cab from the attachment to your Hermes device
2. Tap on the cab to install. Note: you must install this to your device! The service dll can't run from extrom or your storage card!
3. When the installation is complete, reset your Hermes
4. Enjoy skip free A2DP!
Early implementor additional instructions
I had to change the service key to allow automatic start so you will need to manually remove the old key. You must do this before installing v1.0. Here's how:
1. Stop the A2DPFix service
2. Remove the entire HKLM/Services/A2DPFix key from your registry.
Latest Breaking News:
12/03/06
There may be registry settings, previously done in an attempt to work around the skipping problem, that are now hindering rather than helping. Changing quality and other A2DP settings with the Hermes registry Tweaker may actually contribute to this. If you are still skipping with a known good ROM/headset combination, please check your registry settings against these and report on your findings!
(all DWORD values are decimal)
/HKLM/Drivers/BuiltIn/BtA2dpSnd
remove any Priority256 value
HKLM/Drivers/BuiltIn/WaveDev,
Priority256=149
/HKLM/Software/Microsoft/Bluetooth/AudioGateway
Capability=37
/HKLM/Software/Microsoft/Bluetooth/A2DP/Settings
UseJointStereo=0
BitPool=58
MaxSupportedBitPool=80
Remove all other values from this key including SampleRate
Don't forget to reset your Hermes if you change any of these!
12/02/06
As promised, there's now a CAB based installation
ROM version dependency confirmed! This patch's effectiveness is inconsistent with the orignal v1.18 TyTN ROM. YMMV on this ROM for sure.
12/01/06
The success of this patch may also be related to the ROM version you're running. I have the latest TyTN ROM loaded and it has quite a few out-of-the-box performance tweaks which are also included in the latest Cingular and DoPod ROMS.
Known Good ROMs/Headsets
These ROMs are known to benefit from applying this patch:
TyTN v1.35 ROM
Cingular v1.34 ROM
In addition to the few headsets that used to work, the following additional Headsets now work with this patch (I'll add more as I find out)
SE HBH-DS970
Moto HT820
Logitech iPod Headset
HP iPAQ Headset
Jabra BT 620S
As always, Enjoy!
Tried it according to your instructions (imported the .reg with Total Commander), started BT and set my headset as Wireless Stereo (for some reason the TyTN doesn't keep the setting even when selected in the partnership settings.
And it still skips (drops audio) for me.
Is the service started? What A2DP headset are you using? Did you try the Taskmanager workaround I referenced, and if so did that work for you or not?
Sleuth255 said:
Is the service started? What A2DP headset are you using?
Click to expand...
Click to collapse
Yes, checked with dotFred's TaskMgr. It autostarts after a soft reset it seems?
It will auto-start only if you're also running SPB Pocket plus.
edit:
I'm trying a reset now to see if it's still working afterward....
edit2:
Still working for me. Set your following registry entries to the following and see what happens:
HKLM/Software/Microsoft/Bluetooth/A2DP/Settings
UseJointStereo = 0
BitPool = 58
MaxSupportedBitPool = 80
also: What ROM are you running?
Sleuth255 said:
It will auto-start only if you're also running SPB Pocket plus.
Click to expand...
Click to collapse
Yeah, I have SPBpp
Sleuth255 said:
It will auto-start only if you're also running SPB Pocket plus.
edit:
I'm trying a reset now to see if it's still working afterward....
edit2:
Still working for me. Set your following registry entries to the following and see what happens:
HKLM/Software/Microsoft/Bluetooth/A2DP/Settings
UseJointStereo = 0
BitPool = 58
MaxSupportedBitPool = 80
also: What ROM are you running?
Click to expand...
Click to collapse
Done, still skipping. Although it looks like it's skipping a little bit less now. Also, the TyTN is completely unusable when music is playing, it is VERY slow to respond to anything other then the pause/stop and forward/backward buttons on my headset.
ROM version: 1.18.255.3
ROM date: 07/22/06
Radio version: 1.03.03.10
Protocol version: 32.34.7010.01H
ExtROM version: 1.18.255.106
Yeah, that's normal with your ROM. You're on an original TyTN ROM. You'll even lose the digitizer occasionally with A2DP running. I wonder if this patch is ineffective on your ROM. I'm using the South African v1.35 TyTN ROM currently.
Edit:
Did you try the Taskmanager workaround? I'm betting that won't work for you either. Part of this patch's requirements may be upgrading to either the latest Cingular, DoPod or TyTN ROM. These ROMs have a quite a few performance tweaks that may just allow my A2DP patch to "take it over the top" from a skipping perspective.
What BT headset are you using btw?
Sleuth255 said:
Yeah, that's normal with your ROM. You're on an original TyTN ROM. You'll even lose the digitizer occasionally with A2DP running. I wonder if this patch is ineffective on your ROM. I'm using the South African v1.35 TyTN ROM currently.
Click to expand...
Click to collapse
I'm putting off upgrading as long as I can (don't feel like reinstalling all my apps all over again ) But it seems I might have to try that now.
Sleuth255 said:
Did you try the Taskmanager workaround? I'm betting that won't work for you either. Part of this patch's requirements may be upgrading to either the latest Cingular, DoPod or TyTN ROM. These ROMs have a quite a few performance tweaks that may just allow my A2DP patch to "take it over the top" from a skipping perspective.
What BT headset are you using btw?
Click to expand...
Click to collapse
That was the first thing I tried. I have the Jabra 620s headset
Hiryu said:
I'm putting off upgrading as long as I can (don't feel like reinstalling all my apps all over again ) But it seems I might have to try that now.
Click to expand...
Click to collapse
Yeah, I know what you mean... I'm getting used to the routine now tho but it still takes a while. Flashing itself is less stressful now that I have a known good computer with a known good USB port which I use for flashing. The 20 minute Hermes flash process caused high anxiety for sure the first time I tried it.
Sleuth255 said:
Yeah, I know what you mean... I'm getting used to the routine now tho but it still takes a while. Flashing itself is less stressful now that I have a known good computer with a known good USB port which I use for flashing. The 20 minute Hermes flash process caused high anxiety for sure the first time I tried it.
Click to expand...
Click to collapse
guess I will bite the bullet tomorrow and upgrade, It's 2am here and that's not a good time to do anything that stressful.
Have any good links for upgrading?
Not really. Here's some tips though:
Practice safe flashing techniques:
1. Windows XP with nothing else running
2. Screen saver off, sleep mode off, powersave mode off
3. Use a rear USB port. Make sure activesync works ok on it.
Do pof's SuperCID upgrade first. See his thread in the upgrading section for how. There's good step-by-step instructions. I'd read through the whole thread (takes a while) first to be familiar with any pitfalls.
The current TyTN ROM can be found in the Wiki along with flashing techniques and recovery for common errors.
and finally: don't exit until the ride comes to a complete stop....
Excuse me but I'm fairly new to Tytn and Windows Mobile devices. The .zip file should it be renamed to .cab once downloaded or is this something you will upload later?
Sleuth255 said:
Not really. Here's some tips though:
Practice safe flashing techniques:
1. Windows XP with nothing else running
2. Screen saver off, sleep mode off, powersave mode off
3. Use a rear USB port. Make sure activesync works ok on it.
Do pof's SuperCID upgrade first. See his thread in the upgrading section for how. There's good step-by-step instructions. I'd read through the whole thread (takes a while) first to be familiar with any pitfalls.
The current TyTN ROM can be found in the Wiki along with flashing techniques and recovery for common errors.
and finally: don't exit until the ride comes to a complete stop....
Click to expand...
Click to collapse
Thanks Sleuth! Upgraded and now I have no more skipping audio!
@jompao:
Sorry about this reply's delay: it's now morning here in the US Midwest. If you unzip the archive on your PC you'll find two files: the reg file and the dll itself. It's strictly for "early implementors" though so if you don't know what to do with these offhand, just wait a few hours and I'll have a full install cab posted. I have to code up a small program to start the dll automatically first.
@Hiryu: that's great to hear I'll add your jabra headset to the list of supported hardware. Btw: did the upgrade correct the problem that headset has with pairing or do you still have to go into bluetooth settings to get it to pair?
Sleuth255 said:
@jompao:
It's strictly for "early implementors" though so if you don't know what to do with these offhand, just wait a few hours and I'll have a full install cab posted. I have to code up a small program to start the dll automatically first.
QUOTE]
No worries! I will wait for the .cab file as to not mess up my device..
Click to expand...
Click to collapse
A big mahalo to you Sleuth!
Works great on the HTC v1.35 ROM to a pair of NBH-DS970's... one little skip while downloading over UMTS but fixed that by pumping up file caching to 4mb and audio buffer to 2000 msec on pocketplayer v3.01. No slowness whatsoever.
Email, internet, open and closing various programs all while jammin' to a little jeff beck's guitar shop...
Cheers
Damn! Streaming audio.... I'm jealous! No UMTS here yet
Sleuth255 said:
Damn! Streaming audio.... I'm jealous! No UMTS here yet
Click to expand...
Click to collapse
not to make you anymore jealous but i was streaming my xm radio off my phone... with UMTS it worked fantastic, and now with the patch there is no skipping
I picked up my Audi A4 last week, and the MMI + telephone connection high works to a limited degree with the Touch HD.
It correctly identifies the Orange network, 3G, varying signal strengths, and can dial out and receive calls, but I don't have access to other functions such as the phone's last dialled calls, missed calls, phonebook/contacts list (biggest problem!), etc.
I'm using the original 1.14.405.3 (22273) WWE rom which came with the HD, but has anyone had any success with the MMI by using other roms?
Guess this does not help, but I had the same problem with a brand new mercedes C200 and Dutty's 2.8 firmware...
Cheers
[update]
maybe this thread helps a little: http://forum.xda-developers.com/archive/index.php/t-456900.html
some say it worked after upgrading to 1.19...
personally I think bluetooth has always been ****ty
Pretty interesting that a version of Duttys made it stop working, at least it shows bluetooth compatibility is affected by different roms. Thanks for the link, it seems the JetWare program might work too, but updating the rom is a last resort for me since I've never done it before. I'll try JetWare first, and if it stops working after a few days, I'll go for the rom update. Thanks again!
You'r welcome! I am on Duttys 3.0 right now but never had a car again with bluetooth so couldn't test
If you never flushed your HD - try! You will be massively excited I swear
Compared to the original firmware the phone was unusable slow and had a ugly user interface... I can really suggest Duttys 3.0! Once you are through the process of flashing it's quiet easy...
Cheers
Heh, maybe I'll go for the regular handset option for my next car, seems like it'd be less of a headache. Anyway I upgraded my HD to 1.19 and there was no change in displaying phonebook contacts, so I decided to flash Dutty's v3.3 and it still doesn't work properly...but I'm liking Dutty's a lot, definitely glad I upgraded to it. Thanks for suggesting it!
I'm back to square one again though, so if anyone else has some advice/experience with getting it to work, I'm all ears
Anyone at all?
Is the Audi new or used? If it is used you might have an older version of the MMI software. Good luck getting Audi to do the upgrade for you. Check out the forums at Audiworld.com.
I have an A6 and have the same problems.
Have you tried Jetware? I used that for awhile but I found I would rather use a headset now.
I use a Touch Pro with my 09 A4 and I have the same problem. Everything works great except when it comes to syncing the phone book. After pairing the phone with the car, a message pops up asking if I'd allow the car to access my contact. I'd answer yes, but then nothing happens.
For some unknown reason, I was able to upload the phonebook once. I don't know what I did differently that time but the phonebook mysteriously showed up in the car memory. However, the next time I started the car the phonebook was gone.
Hi everyone. My HD works fine on my 2006 Audi A8L. After initial pairing with the MMI (default pairing code is "1234") you have to wait a little while and the phone book and recent calls pop up. In the Phone > Setup of the MMI I selected only to use phone memory.
One issue I have is that the 150 contacts I have are somehow displayed in 2 iterations of the alphabet, each showing only a half the contact list.
Also good to know. Pairing with Audi's MMI is only possible the first 5 minutes after you turned the power to the car on, ie. turning the key one notch, or starting the engine, so be sure to have your Touch HDs bluetooth on already.
Audi's Bluetooth phone features are on a phone by phone basis, Audi have a list of all the handsets that they have tested and the features that are available using that phone and the firmware for the phone that it needs to produce those results.
I work for Audi so if there's any questions I'll do my best to answer. (I work in parts)
I'm starting to struggle with my T-HD, I seem to have more fixing & patching applications on it than the nice day to day stuff you would want or expect on a high end device competing against the iPhone...
My current source of annoyance is that the bluetooth connection between the T-HD and my Landrover Freelander 2 that has been working fine for 6-months now either (a) doesn't connect or (b) does connect but when I dial out through the MMI saying "dialing" but then drops out or (c) we make a sucessful call but at the end the MMI states "phone disconnected" and when it reconnects it re-sync's the phonebook which all takes time...
Based on advice from the forum i've...
deleted and recreated the "pairing" ensuring everthing is visible,
used HD Tweak and Advance Config tools to fine tune the BT settings,
tried different BT COD values,
removed PhoneEX
installed JETware Mobile
All to no avail, the phone connection still drops.
My Nokia 6300 works fine by comparision and I can't fathom why, after 6-months of operation, this fault develops.
I've searched high and low for BT fixes, W6.1 drivers and HTC hotfixes but the options seem to be more "fixing applications" or a custom ROM nieth of which I'm keen to undertake as my T-HD is fill up with applications to fix basic functionality that should work.
Anyone else have any ideas? Can the BT drivers be replaced or updated?
HELP...
ROM ver 1.14.405.3 (22273) WWE
ROM date 12/09/08
Radio ver 1.09.25.14
BT ver 2.0/2.0+EDR
I got the same problem with my BT car Kit (Motorola T605).
I've only made it work if I connect the streaming on the BT configuration, but it have other problems as all the PDA sounds are routed through the car stereo, which can be uncomfortable if you are listening to the radio or a cd.
Could it be that problem is related to a 'power saving' configuration?
Hi there...
There seem to be plenty of fellow sufferers, strange that HTC don't seem to recognise their BT is flakey.
Sorry, what do you mean by "streaming"? I haven't seen that config.
and I have the "Power - Advanced" settings deselected (ie do nothing if inactive on mains power or battery)
All the best...
Well my HD won't sync it's phonebook with the Freelander 2... very occasionaly accepts an outgoing call via the mmi.
It will randomly lose connection also, requiring it to be re-synced.
Are you using the official ROM on your device? The bluetooth stack in the old official ROM is outdated, and honestly, garbage. Have you tried using a newer ROM, whether it's the official 1.56 ROM or a custom ROM? I used to have a ton of Bluetooth issues with my device and my car as well until I moved away from the official ROMs.
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)
I'm tryin to use my phone in my car using the build-in handsfree device (BMW 3-series). Sometimes it works but most times the car looses the pairing after a few minutes. After that the connection is only possible when I switch bt off and on again. But then again a pairing is not possible. I already used the phone with Android successfully in the car but only once or twice.
I used several sense-builds with a variety of different kernels such as mdjs and hastarin. I also changed the connection value in the bluetooth main.conf from 7 to 15 but without any success.
What can cause a problem like this where a connection is possible only for minutes but is working sometimes like expected?
Has anyone a similar problem with a Bluetooth headset?
Thanks for your help.
======================== SOLUTION ========================
Finally I found out, that it has nothing to do with radio ROMS, nothing with the WiMo-ROM nor with the Android itself. The failure lies in the sync between android and Outlook. One of my contacts included more then 80 telephonenumbers (3 particular numbers many times) what crashed the pairing between my car and the phone. I just deleted the contact and re-added it manually. Further I stopped the sync with Outlook and now only sync appointments of the calendar...
======================== SOLUTION ========================
Sent from my HTC HD2 using XDA App
Really no help for me...
I've got the Fiat Blue & Me system in by Abarth, it has similar problems to the one you're having in the BM, if I'm right in thinking that the Bluetooth stack is part of the radio ROM then trying a few different radio versions should help. I've found one that's fairly stable but still unpairs itself occationally. it's Leo_RADIO_2.15.50.14 running on mdee jay Evo Sense Evolution with hastarin's 8.1 kernel.
Updating the radio ROM didn't help. I could make one single call but after that it began losing pairing again. That's so sad because everything else is working pretty good so far.
Sent from my HTC HD2 using XDA App
I own a BMW 320d E90 and i have no problem with BT pairing.
I use the Androide 1.5 build done by Crazy_Cbr in htcmania.com (a spanish forum), with Radio 2.15 and Official Kernel #127.
Maybe your BT device needs a firmware update if your Serie 3 model is old. I have heard that you can update it in your BMW dealer, but not sure as far as i haven't needed to do it.
Greetings! (and sorry for my english)
Thank you... I have a 2010th E92 so I think the firmware is no problem. Furthermore the Version 1.5 is pretty old. I had this one with my G1 phone and was not very pleased. I also need Sense which is - afaik - not available for 1.5. Why do you not use a 2.x version?
Sent from my HTC HD2 using XDA App
This build is based in 2.2 but his name is "Androide 1.5", the point is that is a Senseless one...
Anyway i guess the problem is not in the build. Does BT work fine with WM?
Yes it worked pretty well with WM what brings me to the point isolating the problem on the hacked Android builds. Perhaps it'll work in the future.
@Nandeh: Which ROM Version do you use for your HD2 device (Radio ROM, WM-ROM and HSPL)???
Sent from my HTC HD2 using XDA App
I found out that the bluetooth pairing is stable as long as I don't have any phone numbers saved in my phone. Any ideas?
Any updates on this?
I have a 2005 1-series. First I was running WM 6.5 on my HD2 and never had problems connecting to the handsfree built in to the car. Then I installed tytungs NexusHD 2.9 NAND ROM (Android 2.3.5). After this, I can pair with the car, but the connection keeps dropping out and then reconnecting with some random intervals between maybe 3 seconds and half a minute.
I have tried to edit audio.conf and audio_pairing.conf, and also an earlier version of audio.so with no luck.
I really don't want to get a different ROM, as I really like the one from tytung.
(Link to tytungs ROM: http://forum.xda-developers.com/showthread.php?p=16555125#post16555125)