Bluetooth not working with new Unified 3.5 ROM Kitchen

[jrs]

Jbabey,

I'll test. I'm want to get this fixed. it worked great except for the bluetooth problem which I am also experiencing

[chuque]

I too am willing to test for this problem. but also don't have the files in question.

[JBabey]

I think i got this fixed.

\OEM\APACHE_Drivers\

Replaced btd.dll

EDITED cfb04a95-153f-4319-9832-3f76821a03b3.rgu

Replaced [HKEY_LOCAL_MACHINE\Comm\BTPAN1\Parms]

With

[HKEY_LOCAL_MACHINE\Comm\BTPAN1\Parms]
"BusNumber"=dword:0
"BusType"=dword:0
"AdapterType"="PANU"
"ServiceId"="{00001115-0000-1000-8000-00805f9b34fb}" ; PANU
"FriendlyName"="Personal Ad-hoc Network"
"Description"="Bluetooth PANU service"
"ConnectionTimeout"=dword:7530 ; 30000
"AcceptConnections"=dword:1
"MaxConnections"=dword:10

\OEM\AKU3xx_BTA2DP

Replaced Avrcp_MPplugin.dll
Replaced bta2dp.dll
Replaced sbc.dll



Been testing on a flash for 2 days, constantly turning BT on and off everytime i get near the phone and make a call. works fine.

I got some of the replacement files from WM6 kitchen, and some from AKU 3.5.2 UNIVERSAL kitchen and others from Helmi aku 3.5 build 2. had to mix and match for about 4 flashes before i got the files that i needed all working togethor. I have NO idea what the hell these files do so please dont ask.

As far as the registry, i pulled that from a 3rd kitchen by Helmi for AKU 3.5 build revision 2 over at XDA from an OEM apckage for a2dp

NONE of this work is my own, i dont have the skills neccesary to troubleshoot something like this. All i have done is collect bluetooth rescources from kitchens that are KNOWN to have bt working properly.

If my tests are conclusive after this weekend, i will build a ROM and make it public, I will also zip up the files neccessary to recreate the "fix" on this thread.


On a sidenote, i also replaced the WModem files from WM6 and they seem to be working on every try, no more "COM OPEN ERROR" when its launched. Again, im going to test through this weekend and post back here.

\OEM\WModem\

Replaced WModem.exe
Replaced SwitchModem.dll

[Perasite]

Do you ever do anything other than screw with your phone?

[luv2chill]

You were getting COM OPEN errors in the Unified 1.0.0 Kitchen? Odd, because I replaced wmodem in there already and that cured those errors for us.

Also, in regard to your BT stuff, please itemize which files came from which source. I think you may have overkilled it though as the BTPAN stuff should be in NAP mode, not PANU and A2DP shouldn't have anything to do at all with the issue of turning BT on and off.

[JBabey]

Originally Posted by luv2chill

You were getting COM OPEN errors in the Unified 1.0.0 Kitchen? Odd, because I replaced wmodem in there already and that cured those errors for us.

Also, in regard to your BT stuff, please itemize which files came from which source. I think you may have overkilled it though as the BTPAN stuff should be in NAP mode, not PANU and A2DP shouldn't have anything to do at all with the issue of turning BT on and off.

yes, i got the COM OPEN error every single time i tried to make a connection AFTER i already made one. In my first class i hook up and wmodem out. After class i shut it down, pull the cable and shut down my laptop. In my next class 15 minutes later, i would hit start, and get the COM OPEN error and have to soft reset the phone to get it to work again. Since i pulled the wm6 kitchen wmodem files i have not had the error once during classes all week so i figured i found me some gold!

RE: the bluetooth stuff, ima send you a PM. I hope i didnt jump the gun early or something and possibly be wreaking havoc on my "alpha" testers (read me/girl/co-workers) haha.

thanks for the info chill!

[bro4ever]

I am using saridnour's pr6, I am facing the same problem here, but the different is I cannot receive any file from another device (I used nokia phone). Everytime I tried, it always gave me "sending failed" message.

However, I could send a file to my nokia phone over BT connection.

Any idea why? the registry thing & soft reset didnt overcome my problem.

[collindv]

I also got alot of com open errors.

Good work JBabey. I will be happy to test as well once the files are posted.

[friguy3]

any new luck on this? the bt on the unified rom is killing me. having the same major problems with turning on/off bt and i dont have the prerelease rom to install anymore cant we just change the bluetooth "stuff" from the prerelase to this one.

[JBabey]

Originally Posted by friguy3

any new luck on this? the bt on the unified rom is killing me. having the same major problems with turning on/off bt and i dont have the prerelease rom to install anymore cant we just change the bluetooth "stuff" from the prerelase to this one.

I know a few others are working diligently to resolve this issue permanently but RL issues & time are tight for a lot of people right now.

For some reason pulling the files from the pre-release does not work. Its working in my current ROM but it took some nasty un-optimized garbage to do so. Ive packed up the changed files & registry in a cab file for you guys.

*IF* my cab file works, it should still only be considered a temporary fix until the team can work out something optimal.

Please, please post back your results. You can uninstall this cab file at any time in your add/remove in case of instability.




Anyways.... heres to hoping.....

EDIT: attachment removed, not working. I have a new one, but for stabilities sake, im reccomending trying my BETA rom first... if working solid, ill post a CAB patch.