Database Users

Data card dropping out of Media Player

To all those frustrated Hermes users who have the problem of the data card dropping out of windows Media Player, DON'T wait on HTC to fix this issue in WM5. The new AKU 3.3.1 ROM update does not contain a fix at all.
I was about to dump my TyTN, but decided to flash WM6 as a last resort.
WM 6 Black 2.5 has solved the problem. I have been running for 10 days now without a problem in WMP 10 and no freezes, or necessity to soft reset at all.
I have not tested the other WM6 ROM's at all so I cannot comment on them but I presume that they will give the same results as they all seem to be based on the same base ROM at present.
BTW. The quality of the A2DP BT using a Nokia HS-12W and HTC BH S100 stereo headsets is awesome.
That's my opinion and personal experience.

I think I'm having this same problem, even on WM6.
http://forum.xda-developers.com/showthread.php?t=303798&page=29
My post is 286...
Is that the problem you were having?

over2land said:
I think I'm having this same problem, even on WM6.
http://forum.xda-developers.com/showthread.php?t=303798&page=29
My post is 286...
Is that the problem you were having?
Click to expand...
Click to collapse
I was having the same problem.
Maybe you should try Pro Black 2.5 with Radio 1.42
My phone is a TyTN and the ser.# is 630...........
It worked for me.

basilrsa said:
I was having the same problem.
Maybe you should try Pro Black 2.5 with Radio 1.42
My phone is a TyTN and the ser.# is 630...........
It worked for me.
Click to expand...
Click to collapse
Radio 1.42???

pietrucci said:
Radio 1.42???
Click to expand...
Click to collapse
As you can see from my CP: radio 142.00.10
Pse read the post carefully!

As a workaround, just delete the MSMETADATA folder on your storage card and then reopen mediaplayer and update the library.

there are about 5 topics that have already been closed about this...
there are two folders you need to delete MSMETADATA, WMRDM and the WmpInfo.xml file
Then update your library

I have added this tweak in the Hermes wiki. Thanks.

[Possible FIX] BT - FM Radio & misc. bugs faced in ROM's

The point of this thread is that 1.64.08.21 is compatible for some and incompatible for others; hence what I'm trying to express here is that the bug/issues caused are due to the Radio and NOT the ROM itself.
Since quite sometime I've been testing miscellaneous ROM's over various Radio versions. Also have been closely monitoring every single BUG pointed out in bepe and other chef's thread. The same bug issue has been also brought up in ASerg ROM. I personally feel his ROM is bug free as I haven't come across any issues.
My speculation has narrowed down towards one common problem giver i.e. the Radio v1.64.08.21 which is now used by 90% of the Polaris users.
I strongly feel that v1.64.08.21 is incompatible with the latest ROM version 19209 & Protocol 25.69.30.05 and even the earlier ROM versions i.e. 1920x.
To be sure of my study I've tested ALL possible ROM's in this forum using the factory radio 1.54.25.14 and till date haven't faced a single bug issue which has been repeatedly brought up by misc members on this forum.
To clear this problem, request some of you to help me test some things out:
- Can I request you to re-flash your radio to 1.54.25.14 and then test the same ROM for the bug's you have been facing
- All NEW Polaris owners, please DO NOT flash your Radio rather just the ROM.
- Existing Polaris owners on a non-1.64.08.21 radio, please test whether the bugs exist on your ROM's.
After all 1.6.4.08.21 is a Radio extracted originally from a Russian Kaiser ROM, it doesn't make it 100% compatible as the factory Radio for Polaris.
Strongly looking for some views and feedback from everyone

What are your noted bugs?

what the actual bug is?

@taiseer999:
I'ven't faced the same issues which other members on the forum have been mentioning, even using the same ROM which they are on as well.
@windirt:
I personaly feel that using a Kaiser Radio on a Polaris is "possibly" causing the BT to remain on and other miscellanous issues that have been brought up.

I'm using a self-cooked taiwan cht rom (wm6 18129) with radio 1.64.08.21. works very well for one more week, never encouter the BT issue as you described.

windirt said:
I'm using a self-cooked taiwan cht rom (wm6 18129) with radio 1.64.08.21. works very well for one more week, never encouter the BT issue as you described.
Click to expand...
Click to collapse
I also never faced any problems with Bepe 0.67 WWE release and 1.64.08.21. I can turn my bluetooth on or off, the blue light isn't flashing if my bluetooth is off, and I never had any problems connecting to a device or what so ever. Maybe there are revisions of the hardware...

I have been using 1.64.08.21 from
http://forum.xda-developers.com/showpost.php?p=2051354&postcount=1
and no problems with Bebe's ROM. WiFi, Bluetooth, and 3G work fine, only problem I am having is using Windows Live with 3G, which cant connect all the time. But this also happened with the original radio and ROM.

PB of BT
Hi,
very intersting post Jibreil. I think your right when you recomand not to change the original radio of polaris. Since I change my radio, I definitively loose my BT and my FM Radio. Both was working before I make the "update". now I have to send my polaris back to the seller and its a very very disturbing situation
So I confirm: do not change your radio if you want to be sure of kipping your BT. Another thing about that: maybe Im wrong but I think that the battery drain is much better with the last radio (1.64....) it's a shame !
nooms
067 bepe

nooms said:
Hi,
very intersting post Jibreil. I think your right when you recomand not to change the original radio of polaris. Since I change my radio, I definitively loose my BT and my FM Radio. Both was working before I make the "update". now I have to send my polaris back to the seller and its a very very disturbing situation
So I confirm: do not change your radio if you want to be sure of kipping your BT. Another thing about that: maybe Im wrong but I think that the battery drain is much better with the last radio (1.64....) it's a shame !
nooms
067 bepe
Click to expand...
Click to collapse
After flashing I noticed a drastic loss in my signal, may be it doesn't work well in this part of the world. I have replaced three phones, imagine how frustrating it must be for me
The point of this thread is that 1.64.08.21 is compatible for some and incompatible for others; hence what I'm trying to express here is that the bug/issues caused are due to the Radio and NOT the ROM itself.

Bluetooth and MSVC

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.

BlueTooth CarKit ISSUE

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)

Using HD2 Headset remote with Android ROM

Searched but can't find an answer.
How does every one else dealing with this situation? Is there a work around to make the remote button work with different Android builds?
Would it work if I use a matching OEM headset? For example, get the OEM EVO headset to use with EVO based build?

what is it ur specifically trying to do
hey what is it u wanna do bc I have the desire build and I use the headphones that came with my hd2 to control my music thats about it u can do with it and u know the basic use it to talk and what not but even than u have to have winamp installed on ur phone which u can get from the android market for free or it also works as a music controller on the htc music on android idk if it works for the other builds tho, hope this helps

Try the headphone come with iphone, it,s work!

silvscorp said:
How does every one else dealing with this situation? Is there a work around to make the remote button work with different Android builds?
Click to expand...
Click to collapse
What are you talking about? Headsets have been working properly almost since the start of Android porting.

Fedr0 said:
What are you talking about? Headsets have been working properly almost since the start of Android porting.
Click to expand...
Click to collapse
I think he means for controlling music. It may be a non-sense build issue. My original HD2 headset buttons don't work for skip forward, back or play/pause. This is on Bangsters V1.5. My bluetooth headset does work for these functions though. When I used desire builds the headset buttons would work, but only if the screen was on.

trmacdonal said:
I think he means for controlling music. It may be a non-sense build issue.
Click to expand...
Click to collapse
That's strange, I've never had that problem and I never use Sense builds. This with the screen either on or off, it doesn't make any difference.

Anyone solved this problem after NAND builds were released?
Somehow I managed to get my headset working just after flashing new build, but next morning I found no music control from headset whatsoever. Really annoying this is because I use them a lot when I go to work or enywhere else :/

npocmo said:
Anyone solved this problem after NAND builds were released?
Somehow I managed to get my headset working just after flashing new build, but next morning I found no music control from headset whatsoever. Really annoying this is because I use them a lot when I go to work or enywhere else :/
Click to expand...
Click to collapse
yes me too and I have found any solution the call/answer button enable only Voice Recognition and the (next/back) button enable nothing
@npocmo: I think that dosent work with the desire HD build portage. Did you tried with a nand Desire ?

i flashed MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC] and face the same problem.
is there any solution?

wow this thread is so old !! has anyone found the solution ? i flashed [Feb 02][DL DesireZ v3.4][DL Data2SD/Ext4 v2.7][Nand/SD/MAGLAR] yesterday and have the same problem, the remote doesn't do anything other than make the music player go crazy. solution please ? should i try with another android build ?

I have the same problem with this build!

actually these devs were saying that it was infact gingerbread who wasnt supporting the headset controls.. but now most of them do.. only thing you can do is thoroughly search the build thread to make sure that they work before flasshing them unto your phone so you know exactly what your getting into

Try changing kernel to gauner

Yes, the problem on kernel mdj.If you change kernel on to gauner it will works.

soberlam said:
i flashed MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC] and face the same problem.
is there any solution?
Click to expand...
Click to collapse
I changed the kernel and it working

Can someone explain how to fix it? I did not understand..
I have on my Leo's -= MDJ CyanogenMod 7 v. 2.6 [+ A2SD] [GRH78C] [RMNET] [Kernel: MDJ S10.4 OC]. Excuse my English but I'm Italian

Anyone can help me?

mylove299 said:
I changed the kernel and it working
Click to expand...
Click to collapse
so can i use NAND MDJ but use gauner kernel ?

How do I change only the kernel? without losing data?

where can i get gauners kernel please