Rom developers... the BT stack on the Touch works-
 

UPDATE: I THINK WE DID IT!!!
Ok folks, we've had a great group of guys working on this almost non-stop for the last few days/weeks, testing theories, hacked drivers, and infinite possibilities of ROM blends... and I'm very happy to announce that we have what appears to be a SOLID, STABLE RELEASE!

It turns out that the Touch BT drivers weren't the secret after all... they only worked when dropped into the 2.16 rom, which still had the same problems (d-pad lockups, bt shuts off, device freezes, etc).

However, combining 2.09 with a newer AKU virtually eliminates the Bluetooth quality issues that everyone complained about, and 2.09 never had the issues that the later roms introduced.

The result seems to be the best combination possible:
-BT seems stable, stays on
-BT does not freeze device when in standby even when headset disconnects
-D-pad does not get locked up
-Devices wakes up on BT command
-Voice Quality problem appears to be gone

Known issues:
-Alarm problem is still there since that existed in 2.09.

However, some of the team think that its possible to package that up and extract the fix from the later builds. So, stay tuned for a new release soon.

In the mean time, please test the current release here:
ftp://ppcgeeks:ezupload@up.ppcgeeks....nkwegotsit.rar
Please post any problems here, with as much detail as possible!

Thanks to everyone who made this possible with your insight and tireless trial-and-error patience:
DogGuy, Jtrag, and sfaure03, for being the original determined members of our group. I simply couldn't keep up with all the work these and the rest of the team put into researching the problem. These guys are driven.
no2chem for the XIP and contributions to testing and theories.
Sonny, bepe, tadzio, DCD, IMCokeMan, for the sage advice and helpful suggestions.
double0four for the "universal" rom used to port to our device, and
The PPCGeeksDevelTeam, and the members/users of this forum.

For more info, see discussion in this thread.

UPDATE 11/21:
This rom seems to fix BT quality and stability for the most part, however after spending a few days with it, I feel that it is not yet perfect.
It has many of the setbacks that the original 2.09 rom that it is based on had, more specifically the device turns on by itself randomly (something that happened when roaming on the other roms as well, however not quite as often), and in some bizzare situations, the screen hue will change slightly when the display is tapped or the scroll wheel is used. It also seems to be a little bit less snappy than roms based on the later builds.

Still, if BT is important to you, this is really the best option at the moment!
There are more options being looked into...

Original post follows (for continuity):

does the touch use MSM7500 chipset?
i am pretty sure, it is not hard at all to grab those drivers, assuming they are for the exact same hardware.

I can confirm that the touch's bluetooth is awesome!
-mark

CPU is the same.
 

Both are using the same Qualcomm MSM7500 CPU/Chipset and BT chip is TI BRF6300 (http://forum.ppcgeeks.com/showthread.php?t=7991). Also there are references to BRF6300 in TIInit_4_2_38.bts - file in Titan 2.16 and Touch/Vogue firmware. BTW TIInit_4_2_38.bts is not present in Altell or old 2.09 Titan ROMs- just in Touch and new Titan.

There are few other files like BT_FIR_Param.txt, BT_Init_Script_TI_*.txt, BT_Name_INFO.txt etc. that looks very interesting.

I was able to port all of SYS and most of OEM from Touch to Titan successfully (some of OEMDrivers are not compatible), but not BTHCI.dll... Still have hope :-)

I really hope that something can be done. i mean havent gone back to 2.09 since bt is choppy (I just deal with it).


please ppc gods give us a miracle, since HTC nor sprint want to

I tried this - It worked, and then messed up the dpad so it didn't work anymore - unfortunately I don't seem to have time for anything lately so I didn't look into it more.

Nice find! Progress...

i am also thinking this is good news for bt users in general. if the touch has a working bt solution with identical hardware, the manufacturer will deploy the same thing for titan. if not, id be really confused as to why.

now, do we have a dump of the retail touch? i have a prerelease dump but id rather start with current.

maybe on htc's site?

what about the mms? what software is the touch using for mms?

sprintdude07:

Right now i'd take a copy of the pre-release if you have it.. Please upload

just so you know, the BT stack in the sys folder "BLUETOOTH" is the same for all builds of CE OS 5.2.

For all it's worth and if anyone thinks it's valid you folks might want to try this: http://forum.ppcgeeks.com/showthread...538#post116538

I am not near as savy as some of you gurus, but this is working for me and thanks to
8notime for pointing me in the right direction.

matt

@dcd
 

I have the shipped ROM (2.13) for the Touch... which file do you want? The whole exe file or just the RUU_Signed.nbh??

Here's what I've dumped so far... but don't know what to do from this point... http://www.megaupload.com/?d=PZSMBNZY

Ok, thanks to sfaure03, we've started testing the Touch BT drivers... apparently, they can just be copied from the Touch dump... no porting needed!
Volume is reported to be better, and it passed the "force BT to crash" test.

Now we need more testing, and if everything goes well, this should be a required addition to every custom rom!

I am very excited about this new discovery and hope that these BT drivers fix the many BT issues with the Mogul.

One thing that worries me though is that the Touch does not have WiFi. This may be why the BT works better.

If i remember correctly, the Mogul's WiFi radio and the BT radio are somehow linked...right?

I guess only time will tell.

Can't wait to see the new BT drivers in action!

-s

well, i WILL say, that wifi impacts bluetooth. If you're using wifi you're bt exp will be lessseened.. I think that is more driven by cpu load tho.

I would say someone should the Touch drivers into the 2.09 rom or even the 2.16 rom and see if it flys. I would be willing to give it a good test if you need a tester. I use WIFI and BT frequently

I would love to test as well. I tend to have some free time here at work to tinker with my phone and could test it on the way home talking to my gf.

hmm.....

lets see ftp site, its a titan, i'm a user, i'm sfaure03....

Titan/Users/sfaure03/2.16-{touch}?? .rar..

I forget the name. but if you crawl up there, you might find a jewel... Least one I like.

Remember this is a HUGE hack and is NOT advisable to use it or depend upon it until we get more testing in.

If you want to test, well go for it.

Thanks, sfaure03... but are you sure that's 2.16? It appears to me a WM5 ROM. Maybe I screwed something up.

yes i am its 2.,16

So if testing goes well, doesn't this mean developers could make a CAB of the touch BT drivers, just like superdave did for the Alltell keyboard drivers???

That would be... well.. amazing.

not 4 a lawyer u miight sue me snicker seriously yes.. we prollly can. IF this pans out.

Doesn't necessarily mean that. The keyboard issue wasn't as deep-seeded in the OS as the Bluetooth drivers are... the keyboard patch simply changed the status of the keyboard (from the character lock always being on) in certain situations- ie, the keyboard's OPERATION didn't change, only its status those cases. Its not like you would hit a Q and get a W, or press the caps lock and bring up the call history... that would mean the keyboard driver is messed up and probably require more than just a patch to fix.
The bluetooth drivers are not changing the status of Bluetooth, but changing the way bluetooth inheirently works. It may be technically possible, but its much more complicated than the KB fix patch is.

I think I explained this when the 2.16 rom came out in the first place, and everyone started asking why no one made a cab for all the fixes it came with...

is it possible to just install the files without flashing? (I re flashed yesterday, I'm a day late!, lol and i'm being lazy...but thanks for porting it over to the titan, impressive stuff...

I'm sure I'm not the only one wondering how this may fare on the 6700 as well, I will have to crawl around and give it a shot later today, or tomorrow...

DON'T!!!!
WHY WOULD YOU DO THAT??????

Perhaps you're not familiar with the situation, but the Mogul introduced some new hardware to Windows Mobile, and the Bluetooth drivers didn't work as well as expected. The touch, which uses the same hardware as the Mogul, fixed it. So, we're applying the same fix.

The 6700, however, uses the older hardware, and as far as I know works just fine. So, not only do you not need this "fix", this would probably bork your device because you don't have the same chipset!

THIS ONLY APPLIES TO HTC TITAN OWNERS WHO ARE UNHAPPY WITH THE BT PERFORMANCE!!!

Sue you? Nahhhh... well maybe, how much money do you have??? hahaha:mrgreen:

Thanks for the response! How is the testing going so far? What do you think the final process will be for us Mogulians, will we have to flash the BT stack or move some files around and soft reset or what?

I would help testing but My mogul is my only phone and I have a huge paper for law school due monday and so I can't fiddle with it right now. Plus I'm more of a graphic designer anyways lol.

6700's bluetooth wasn't anywhere as good as the touch's... (I always sounded 'soft' on that phone.. whereas I've heard complaints of being too loud on the touch..)
-mark

the drivers are modules and would have to be converted to files to be packaged in a cab, which would affect performance, and possibly stability.

But a Flash File (NBH) could be done just for flash the BT files like the Radio 1.40 or the Welcome Screen?

no, you would need to flash an entire ROM that includes the drivers.

Thanks for the prompt answer, I think there is nothing else to do, just install and test the only ROM with this option (sfaure) for now.

well, to date, i'm kind of waiting on people who have done just that to tell me i'm full of it.. snicker..

We shall see.

im trying to get mine to work.

sfaure03, i compared the BT*.txt and the files appear to be different.

Sfaure, which radio do you recommend?

it shouldnt matter, but i'm using the 1.47

I just flashed the 1.47 radio out of curiosity...along with your ROM...should be interesting
Perhaps my Touch willl show up today and make this all moot, but I am so temped to stay with the Mogul if we can fix this beast...

i looked over a touch yesterday... I dont WANT it.