New Kitchen (Helmi_APAC_WM3.5_NEW_Kitchen_R2) Bugs

[johnny2678]

Ok, I might just be really slow, so thanks for bearing with me

which OEM is the BT PAN RGU entries contained in? Did this OEM change from R0 to R2? If not, then flashing the BTA2DP, BTFTP, and CambridgeBTProfiles did not get BT PAN working on my unit. However, when I installed the above cab, all is fine.

Which OEM was I missing?

[colonel]

In the OEM folder is OEM_BT_PAN. This does not show up on the BuildOS list, but it is installed. However, this OEM does not have the btd.dll in it. The btd.dll can be found in module form in Apache drivers in the OEM folder. I have replaced this for R3.

[johnny2678]

Colonel,
ok, i see it now... I had moved everything without the 'OPTIONAL_' prefix into the sys folder.

Not sure why BT PAN wasn't working then... I will try again when R3 comes out.

[colonel]

Ok, here is what you need to try. Copy the btd.dll module (folder) out of the Apache Drivers OEM and replace it with the btd.dll file from the patch you posted. That should fix it. Let me know.

[johnny2678]

LONG POST, SORRY

Ok Colonel, in short, I got it to work. Here's was my method:

I removed the btd.dll module out of the apache drivers folder and copied in the btd.dll file from the cab I used to get BT PAN working... flashed... and it didn't work (Unable to detect service)

Then I remembered that BP PAN worked right out of the kitchen (no modifications needed) with the Unified 3.5 ROM. So I searched through that ROM, pulled out the btd.dll file and threw it in the apache folder. The file size was the same but the date was different, so I thought it was worth a shot... reflashed... and still unable to detect service.

Then I thought to compare the reg entries the R2 kitchen made to the reg entries that were found in the working cab, and there were some:

BTPAN differences
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\pa n
key: ActivateOnBoot
kitchen dword=1
cab dword=0

HKEY_LOCAL_MACHINE\Comm\BTPAN1\Parms
key: AdapterType
kitchen string=PANU
cab string=NAP

key: Description
kitchen string=Bluetooth PANU service
cab string=Bluetooth NAP service

key: FriendlyName
kitchen string=Personal Ad-hoc Network
cab string=Network Access Point

key: MaxConnections
kitchen dword=16
cab dword=1

key: ServiceID
kitchen string={00001115-0000-1000-8000-00805f9b34fb}
cab string ={00001116-0000-1000-8000-00805f9b34fb}

I was going to start changing one by one restarting the phone and checking BT PAN functionality. Good thing I started from the bottom because as soon as I changed the ServiceID string (basically a 5 to a 6) and restarted, it worked!

what I should probably do is change the 6 back to a 5 and confirm that the change again disables BT PAN... and further more I should change the ServiceID value in the OEM_BT_PAN RGU, reflash and check that BT PAN works up startup... but I'm too tired tonight and my phone is finally back to normal.

Hope this helps with future kitchens.

[colonel]

R3 tomorrow.

[helmi_c]

wow... U guys are really busy here.. It seems that I've miss a lot...lol...
sorry guys.. been hell busy with real life crap... oh btw colonel... u're amazing...!! and kolano thanks for ur big support also, thanks, btw please try to use the original module (btd.dll) with the modify registry and post the result... cos module with bluetooth (device drivers) usually make more durability on overall performance...

[johnny2678]

Helmi... I'm on it. I'll post back when I have results

[nmeister]

At what point should I run the patchlogo program? I read the walkthrough, and changed the createrom as jbabey suggested. However when I run the patchlogo program, it is looking for a .fat file, and I cannot find that anywhere. I thought that it would be looking for the nk.nba, but like i said it is looking for a .fat file.

[colonel]

To do patchlogo, you need to use the nk.nba from the ROM folder. This is your "base" .nba that is patched during the build process so this is the one you want to edit the splash screen on if you want that screen to show up everytime.

Now, copy that .nba to the patchlogo folder and rename it to nk.fat. convert your image with the conversion tool to a .nb file. Then run the patchlogo app. Now rename the .fat to .nba and copy back to ROM