[Touch Diamond, MDA Compact IV ROM Development] bill48105:
Howdy. First off thanks for the great ROM! Excellent work but sad to hear you have moved on to the HD stuff. Stinks the HD has no US 3G (that I know of anyway) and the price tag.. OUCH! For now I'll continue to love my Diamond *if* I can get it to work reliably with my Bluetooth cordless phone system. :)

Since deciding I needed to replace my reliable HTC S710 slider with a touch screen model I've been on a quest. I started a thread about my Bluetooth woes with my US Touch Dual which I gave up on for now because no one ever posted any responses so I got a Diamond to try since the Fuze I tied with stock ROM seemed to work better than the Dual but was still flaky. Your ROM is the only Diamond one I've gotten to work reliably with my AT&T EP5632 Bluetooth cordless phone system, even stock roms (As noted in my thread I did find a NIKI Dual ROM that worked better with my cordless phone than the stock ROM but I need 850 band & US 3G so I sold that & got the US Dual NEON but I never found a replacement ROM for it) My newer US Diamond I got today has stock ROM still & like my Fuze it seems I have to delete the headset & go through the pairing process which is a ROYAL pain because it is sometimes 10x per day. I am not the biggest fan of cooked ROM's but yours seems close enough to stock to make me happy especially since it works well with my phone! An odd thing I noticed is that the Bluetooth in your LITE one seems different than the FULL one even though I don't see any notes on BT changes.. On the Lite, my cordless doesn't always connect *until* I get a balloon popup asking if i want to make it my default car kit. Once I choose that the Bluetooth icon changes to have a headset around it & it seems to work OK but I couldn't consistently get it to ask & sometimes it is like it gets disabled with no way to trigger it again. With your Full rom I never get that balloon BUT there is a 'Car kit' tab in Bluetooth settings (well as others have noted there are 2 of those tabs) and once I set my cordless phone as default there, the headset icon gets added & it works great! I wanted simple so put the Lite rom back on to find those tabs are missing.. And I have not seen them on any other rom, official or cooked. (Granted I haven't tried every rom out there but I have tried a lot lol)

My question is what is different between your FULL & Lite (or others) that makes the balloon vs Car Kit tabs appear?? Is it possible for me to tweak a registry entry or replace bluetooth files or such on the Lite or stock ROM to add that Car Kit tab?? This is partially a learning experience for myself but in my quest to fix my Bluetooth issues I've come to realize that LOTS of people have Bluetooth issues (especially with car kits & WM 6.1) so perhaps figuring out what is different might help many others too.

Sorry so long winded, I hoped to be as thorough as possible in the history of this adventure. Thanks in advance to you or anyone else with input on this.

Bill

UPDATE:

Searching the registry & files for anything 'car kit' related I found:

[HKEY_LOCAL_MACHINE\Services\HTCAP]

"BluetoothCarKit"=dword:00000001

"Prefix"="HAP"

"Index"=dword:00000000

"Order"=dword:00000009

"Keep"=dword:00000001

"Context"=dword:00000001

"DisplayName"="HTC Application Service"

"Description"="HTC Application Service"

"Dll"="HTCApplication.dll"

and

[HKEY_LOCAL_MACHINE\Software\HTC\HTCSettings]

"DefaultCarKit"=hex:7e,5d,07,a0,11,00,00,00

"EnableCarKit"=dword:00000001

Those settings definitely point to the Bluetooth stuff I am looking for & they don't exist on my stock US Diamond.

I searched around xda & google for those registry paths/keys and HTCApplication.dll with no useful info. I tried copying HTCApplication.dll to \Windows on a stock ROM & importing those keys but it didn't work. As a matter of fact after rebooting my phone locked just as TF3D was loading & I had to press the reset button & it booted up that time. I tried using FdcSoft Task Manager v3.1 to register the dll but it gave the error "\Windows\HTCApplication.dll was loaded, but the DLLRegisterServer entry point was not found. This file can not be registered." which I assume means other files are missing but at this point I have to figure out what.