How To: Kitchens

[leanne]

I can't get a2dp to work with my headset and i'm using 20931 b.

[Donatom3]

Originally Posted by nttdemented

weirdness... I don't have any a2dp devices to test with. Unless I think I've seen my laptops bt services identifying that I can use it as an a2dp device. Maybe I can do some testing later tonight with this.

My Dell 355 BT adapter does support A2DP through the laptops speakers, but I've only tried with my Moto S9's so far.

[nttdemented]

Yeah same here I just got home and I'm gonna play with this a bit

EDIT: Oh SNAP! jejeje whent in to the comm manager to turn on my bluetooth adapter and it doesn't even turn on. If I go into options and tell it to enable it I get an error stating that I have no bluetooth hardware installed. Time to put on the mechanic's gloves.

[nttdemented]

Donatom, you used 20931 v3a right? I'm using v3b and already deleted v3a and my bluetooth wont even start. I started comparing the bluetooth folders from the 20757 sys vs this one and they are definitely quite different. I'm gonna try and switch over the folders from the 20757 SYS into this one and re-flash see if I can get my BT to work using the rest of the 20931 SYS.

[tobeychris]

ntt, the bluetooth was not touched from 20931 a to b. Only the two things I mentioned were.

leanne, kaiguy is right about the UC. The OEMs that I've put up are not necessarily perfect for everyone. I post the settings that I use, since I don't use UC, I removed it from the config file in the Telus Carrier folder. you can just copy that file from one of the other carrier folders and not have to do any editing

[tobeychris]

As for the size difference, 20931 a and b are the same size which is 20mb smaller than other SYS folders. I believe the reason for this is the module folders. In 20931 you only have the bin, txt, and S00x files. In other SYS, they have all those plus the file that is created by those 3 file types.
ie: shell32.exe folder has:
imageinfo.bin
imageinfo.txt
S000
S001
S002
For a total of 310KB.
In any of the other SYS packages, shell32.exe folder has all of those files plus the actual shell32.exe file.
For a total of 614KB in 20757.

What I'm trying to say, is that we made it faster to download and compile ROMs without knowing it, and you should be happy!

[InvincibleLiving]

Originally Posted by tobeychris

As for the size difference, 20931 a and b are the same size which is 20mb smaller than other SYS folders. I believe the reason for this is the module folders. In 20931 you only have the bin, txt, and S00x files. In other SYS, they have all those plus the file that is created by those 3 file types.
ie: shell32.exe folder has:
imageinfo.bin
imageinfo.txt
S000
S001
S002
For a total of 310KB.
In any of the other SYS packages, shell32.exe folder has all of those files plus the actual shell32.exe file.
For a total of 614KB in 20757.

What I'm trying to say, is that we made it faster to download and compile ROMs without knowing it, and you should be happy!

happy indeed

[nttdemented]

Naice naice... 20931 seems to be very good man. Only issue I found with it was BT not starting up, I'm currently testing out the 20757 SYS. I don't know if its the selection I made with BuilsOS but I'm testing a 20757 build with the exact same selections and I'm pairing my two older phones to it right now and my personal laptop and my dad's laptop so I can really hammer on the bluetooth and test it out. Any ideas on what might have caused BT to not even start for me with 20931?

[tobeychris]

I'm Kitchen v3, 20931 v3b, OEM 2.03. All stock settings (seeing as they're mine) and I can pair successfully to my H500. (I really need a new headset)

[tobeychris]

Oh Yeah