Operation A2DP (A2DP for all devices) - One step closer

[universaldoc]

I have downloaded the new T-Mo MDA Pro ROM and decoded it with the tools made by mamaich and with the procedure given by Buzz.

I then dumped the contents of the "nk.nba" file to a subdirectory called Dump . I opened the subdirectory and noticed that it had all the ROM files in it including those for Bluetooth (obviously). I also noticed many BT files as shown in the screenshot below.

Now, what is the next step that we need to do to be able to port A2DP and probably even the Remote SIM access profile to the other devices? I know its possible, i just want to know how!!!

Ideas anyone?

[universaldoc]

Contents of the "imageinfo" text file of "bta2dp.dll":

"Module name: bta2dp.dll
e32_objcnt: 00000004
e32_imageflags: 0000212E
e32_entryrva: 0000B3E8
e32_vbase: 016D0000
e32_subsysmajor: 00000005
e32_subsysminor: 00000001
e32_stackmax: 00010000
e32_vsize: 00018000
e32_sect14rva: 00000000
e32_sect14size: 00000000
e32_timestamp: 663CB98F
e32_unit[0].rva: 0000C090
e32_unit[0].size: 0000009A
e32_unit[1].rva: 0000BF24
e32_unit[1].size: 0000003C
e32_unit[2].rva: 00000000
e32_unit[2].size: 00000000
e32_unit[3].rva: 00017000
e32_unit[3].size: 000008A0
e32_unit[4].rva: 00000000
e32_unit[4].size: 00000000
e32_unit[5].rva: 00018000
e32_unit[5].size: 00001000
e32_unit[6].rva: 00001000
e32_unit[6].size: 0000001C
e32_unit[7].rva: 00000000
e32_unit[7].size: 00000000
e32_unit[8].rva: 00000000
e32_unit[8].size: 00000000
e32_subsys: 00000009

o32[0].o32_vsize: 0000B12A
o32[0].o32_rva: 00001000
o32[0].o32_psize: 0000B12C
o32[0].o32_dataptr: 20000203
o32[0].o32_realaddr: 016D1000
o32[0].o32_flags: 60002020

o32[1].o32_vsize: 000092E4
o32[1].o32_rva: 0000D000
o32[1].o32_psize: 00000200
o32[1].o32_dataptr: 00000000
o32[1].o32_realaddr: 016DD000
o32[1].o32_flags: C0002040

o32[2].o32_vsize: 000008A0
o32[2].o32_rva: 00017000
o32[2].o32_psize: 000008A0
o32[2].o32_dataptr: 00000000
o32[2].o32_realaddr: 016E7000
o32[2].o32_flags: 40002040

o32[3].o32_vsize: 00001000
o32[3].o32_rva: 00018000
o32[3].o32_psize: 000001F8
o32[3].o32_dataptr: 10000000
o32[3].o32_realaddr: 00000000
o32[3].o32_flags: 42002042

Can someone make anything out of this? The folder called "bta2dp.dll" also contains 4 other files named:

1) S000
2) S001
3) S002
4) S003

[universaldoc]

All the files in the dump with the letters "bt" in them can be seen in the attached screenshot.

Notice there is a folder with the name "BthAGPhonebook.dll"

[bepe]

Sorry for by bad english

Have you tried to move this modul to another ROM and to set this in the registry

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd]
"Dll"="bta2dp.dll"
"Prefix"="WAV"
"Order"=dword:8
"Index"=dword:8
"Flags"=dword:10002

[universaldoc]

Hi Bepe,

Your English is fine!

The problem is that the BT dll files are packaged into folders rather than the regular .dll files. I cannot create a dynamic link libray (dll) file without the help of applications i don't know and don't have.

If someone has the knowhow, i will be more than happy to upload the file for you guys so that you can do the necessary.

Cheers.

[universaldoc]

I have attached the BT files from the ROM just to save time Let me know if you guys need any other files.

[bepe]

Yes I know, this folders are moduls.
But it is posible to integrate this folders/moduls to other roms using viewimgfs.exe and BuildImgfs.exe.

Or are you traying to convert a folder to a regular .dll?
This would difficult, I only managed to rebuild resource-dll's.

[universaldoc]

Hi Bepe,

I was trying to rebuild the dll's but it was difficult just as you said. Luckily, Asukal has uploaded the Bluetooth dll files from this T-Mobile MDA Pro.

I copied over all the dll files to my Jasjar but it messed up my device so i had to restore everything through a backup i had taken. I am now going to add only the a2dp and acrcp files to the Jasjar and see what happens.

Will keep you all posted.

[universaldoc]

Well, i just ported "bta2dp.dll" and "btavrcp.dll" to my Jasjar and added the necessary registry entries, but still didn't get the Wireless stereo profile when i was pairing with my headset.

Something is missing somewhere. Anyone else have an idea what it could be?

[Asukal]

i compared carfully.

1:TMUK has more dll than i-mate

sbc.dll
Avrcp_MPplugin.dll
bta2dp.dll

2:also some dlls file size were different.
other dlls are seems to be same size in explore,
but actualy sizes were very little diffenrt each other.

for your refference