Well since my last post I have been getting more frequent bt disconnects (every couple of hours). also when my headset gets out of range of the phone, or the bt discons itself the d-pad doesn't work. if I go into comm manager and turn off bt it clears up.

Same situation here. :(

There's definite progress, though, because before this ROM, my Pioneer car stereo would never connect with the hands-free profile and the audio profile at the same time. It still doesn't auto-connect (which is my main concern), but when I manually connect it, it does both simultaneously, which is good.

First - thanks for posting your work for us to try and test. I appreciate your and others' efforts!

Unfortunately, I installed your 2.16_touch OS only on top of a 1.40 radio, and it froze within an hour. No apps installed, no BT, no calls.

I'm beginning to think my Titan has narrower HW tolerances than most.

Check if the 2.16 ROM actually "upgrade" your radio to 1.47.

I posted tonight a couple new rom's i've been testing with. Those who have been following this thread may want to take a peek and see whether they make a difference.

I believe i've seen some differences {for the better} on the one you see in my folder.

They both seem to work better, but the bttest111507+tbt.rar is I think the most promissing.

A couple dll swapouts from other roms and some registry adjustments. If you have the time and want to try them out please do.

As always i'll be watching for you're feedback.

I kinda need more info on "froze" yer phone after an hour. maybe pm me if necessary, but we have had very few issues on this freezing the phone up. you might also make sure that you are running the 1.40 radio. I had a rom up, last week, that forced you back to 1.47. These newer ones leave it to you which radio.

the 1.47 radio, from everything i can figure out, has a significant fault visa-vi roaming, and it swapping in and out of roaming, and not necessarily when you are in a weak signal area. There "appears" to be a bug in it that freezes the phone up trying to go into / out of roaming when some people are even setting accross from a sprint tower.... Unless you've been running stably on 1.47 i would recommend you either..

1. Lock you phone either into sprint or into roaming in its configuration.
2. Change to one of the older radios that have not had this reported problem.

Sfaure, glad to see there is a new version coming out. Thank you for that. I will try that one.

So far the problem with the 2.16+1.40+BT ROM I have experienced:

1. Turn on BT, wait for the phone to go sleep, then turn on the phone, d-pad not working. If I turn off BT, it starts to work again.
2. I seldom use BT. For test purpose, I tried twice sync using BT. Yesterday night I think my phone freezed. It was when I tried to copy one file to Mogul and install one application at the same time using BT sync.

dpad issues happens w/ w/o bt enabled on this phone. they are not necessarily related, though i think they are exacerbated by each other. any kind of "significant" driver change states can get the dpad back online. often the dpad will come back online on its own, or after a forced sleep/susp/resume with power switch.

BTW the dpad issue seems to ALSO get into a larger than normal "cpu" usage state sometimes in this susp/resume state fail state. Exhibited by symptom that the dpad works, but is very sluggish, and indded other functions of the phone are less than normal in responsiveness. If you get into that i'd encourage another forced pwr susp/pwr resume to get that to "settle down". It has often worked for me w/o having to flash the bt stack.

Again, further detail when you get into these will help us know which areas to look at

Thanks for the feedback.

Please be "reminded" this is NOT a release thread. This is a testing thread where we are testing combinations to find a better working solution. If/when we find something that we think makes a difference we will update then, but this is the "investigative" thread, not a release.

I'm going to give this a shot on my virgin(no custom ROM) Mogul tonight. I'm doing it mostly because the bluetooth stack on my Mogul is crap. One question though - does this stack support SPP? The Mogul's stock BT Stack supports HSP but not SPP - which is odd, since HSP requires SPP. Bleh. Dumb Sprint/HTC. I need SPP to connect my SCP-7050 to my PPC-6800 and use the SCP-7050 as a bluetooth GPS receiver. Can anyone comment as to whether SPP is included w/the Touch drivers?

Thanks!
-George

thats a protocol i know nothing about. this thread has the drivers for the touch applied, and we are primarily concerned with making sure the phone works reliably for phone call processing. adding / ensuring protocols that the vendor didnt originally ship the phone with is not really one of my goals here. That will have to wait for others to build up from this, or for htc/sprint to get us upgrades.

EDIT, and even if the touch drivers support it, we most assuredly did not copy over the CONFIGUATIONS, that would integrate it into the other parts of the os.

Sfaure03, I read somewhere that the touch supports SPP. I'm going to use it either way, since it'll make the Mogul better:) I'm just curious if it does support SPP - Can you go to your bluetooth settings, and then COM Ports, and tell me if it says "New Outgoing Port" only, or if there's some verbiage for Incoming Port too? SPP is the bluetooth Serial Port Profile, btw. HSP is the headset profile.

sorry, cant get into that habit. Feel free to try it though.

Ok.. New rom, i did have a bt failure, however tihs was after a 20 min sleep and the system had been up for a full 14 hours {unusual for me}. If you use this newer rom and have an issue, it probably is a good idea to include a rough idea of how long since last reset, as well as detail of any power state changes just prior to you're problem. Will make our efforts to recreate much easier. Thanks

Hrm well ok then... That was real friendly and helpful. The whole half-a-second it would have taken to look while you were fiddling with your bluetooth settings anyway... and was the response like that really necessary?

I'll test it out and report later. You might just get credit for fixing TWO bugs not just one... but shrug.

dude, that's uncalled for. Some of us haven't even had a moment to respond to the questions some folks ask... at least he took a second to write something!

Excuse me? It's absolutely called for. No answer would have been better than the post he made. He basically told me "no, stfu noob," on something that would take him a half-second to do. Not only that, but read the post he made. It was pretty uncool and uncalled for... I'm not a jerk, a jackass, or an idiot. I have no problem helping to beta(alpha?) test this ROM - I'd love to help, but now I wonder if I should. You guys want to encourage cooperation, etc, in this forum but yet your lead developer can't even be bother to be polite to a new poster? If nobody responded to my question - fine - I wouldn't post it a second time. I know forum etiquette. What "habit" was sfaure03 unable to get into? The habit of fostering cooperation, or the habit of answering questions he thinks are unrelated to the ROM? Believe it or not, a side-effect of the changed BT Stack might be to fix that issue... but why would you want to advertise a second fix when sfaure03 here thinks that his reason for hacking the ROM is the only one there is?

/rant

The habit of checking for new feature/application cross checks requests. I'm working solely on the bt issue ponicg. The comment was not intended to be rude, only that I saw you're request, and rather than just blowing you off, figured i'd tell you that i wouldnt persue it. I had responded to you before that I was not focusing on testing this kind of feature implementation, and you returned again asking me to again test it. I simply cannot "get into the habit" of cross checking against other issues especially when they are features that the original rom did not support.

You're comments that "this would only take a couple seconds" NEVER turn into a couple seconds, indeed they often take up days once you start down the path, and I need to stay as focused on this as I can.

Sorry you took it wrong. I do NOT think this is the only problem with the ROM, but i DO think it is a SIGNIFICANT ONE, and it is the ONE i am trying to find a fix for, and what we're addressing here.

If this fix also has the side affect of fixing other issues, yes i would like to see and hear about that. But its not my INTENT to track down every possible combination people come up with. This approach and focus has been stated and restated in the thread many times. The "habit" i cannot get into is to be distracted by other requests. Sorry you took offence, it was not intended as such.

Shawn,

My apologies then too. I took offense to it based on tone - In retrospect(hindsight is 20/20... bleh) I should have realized that internet posts have no tone and not read into what you wrote. I also could have responded differently. I appreciate the apology and offer my own apology, as well as an offer to help in any way I can. I write .NET software for a living, and have been dabbling recently in the .NET CF. Perhaps if we determine that the bluetooth issue is related to comm manager, I can help build a replacement, depending on how easy it is to touch the drivers w/the .NET CF.

The only reason I felt that my issue was related to yours is that they both related to the bluetooth stack on the device. Regardless of whether they're inter-related, it really would have been a two-second check. You'd click the COM Ports tab, and read that 30 word page for the word "incoming" - If you didn't see it, you'd know that it wasn't fixed. I had someone else check it, and indeed it does not fix this issue. I still intend to install it tonight and see what happens.

-George

As I had said before because we didnt adapt the configurations i wouldn't expect the other subsystems to start trying to offer a service not otherwise available.

The 2 second test would have required me to build again and then "reflash" to test that. so 2 seconds is at least 15 minutes, and then its more to cross check whether i even loaded the right thing, etc etc etc....

Appreciate the comments back, and once we are "happy" with the bt HSP functionality, seeking out other protocols and options will be another round of fun.

No - it did not.

I downloaded and installed this file (216_140_Touch-Rel2.rar) and I already had the 1.40 radio installed. This file upgraded my radio to 1.47 although I didn't notice it for a couple of days (I didn't experience the lockups like I did with the original ROM released by HTC).

if you'll read back, the 216_140_touch-Rel2.rar unfortunately was missnamed, and DID have the 1.47 radio embedded in it.

Sorry, I had read the whole thread earlier and have been checking back each day. I must have missed that.

Thank you for your work. This is a very stable release. I haven't had perfect luck with BT, but everything else works great.

Uhh sorry if this is noobish but:

I glazed over 13 pages and I have yet to find any file/link/attachment holding any BT stack files or a ROM to flash.

Am I missing something? Is it because I'm too new of a member to get them?


BTW
I was surprised to hear this thrown into a ROM, usually its just a matter of porting the files over, followed by a soft reset & voila but I have to admit I only did this with standalone-PDAs, never did this with a PDA-phone. :/

Anyway any help would be great thanks.

If you click on the qlinks on the top of the forum page, then click on open ftp site, then click on "titan", "users", "sfaure03", you'll see the file.

most of the ROMS will be found under users here.

The BT stack on the Mogul is somehow lacking, but the BT stack on the touch seems to work well. The hardware in the mogul and the touch are almost identical, as such some have tried getting the BT drivers from the touch to work with the mogul.

From my understanding, these drivers are tied in to the OS and as such cannot be bundled in a .cab file to add on to your OS. I don't fully understand why, but from what I've read that is the case.

I've owned previous stand alone pda's that I've been able to install different BT drivers, but I'm sure the BT chips in those PDA's were quite different than the BT chips in these newer phones where many things are integrated in to the same circuit card.

Very helpful
 

Clear answer, Thanks.



Yeah I was thinking that was the case, I assume the general PDA was/is easier & simpler because it didn't/doesn't have this deep integration or locks on the ROM & stack like these PDA-phones/Smartphones. :/

Thanks again Nosmo..

Drivers and dll's are interrelatted. one calls another. If they dont match close enough they dont work well, and a poor matchup can cause real issues. The drivers in question can, so far, only be used on a couple versions of teh rest of the os. So its easier to "control" the test by making a single rom solution

These drivers are integrated in as modules. Modules have a slight performance gain.. We are working on something very "time sensitive" and have an "opinion" that we may be making it all worse if we pushed these "modules" into seperate dll's and chasing more issues. We also, are strongly coming to the conclusion that it's really not the bt drivers at all, but is a power/sleep/state configuration. Remember that the released rom's fix was to address two "major" issues. 1. blue tooth low quality. 2. Alarms not going off when the phone was sleeping.

I'm strongly leaning towards its the alarm fix we need to back out {no2's idea on his thread, but I believe he's onto something}. However the question is "how" to do that.

In the mean time it seems to be a tradeoff. You want bluetooth to work well all the time? Keep you phone out of any kind of sleep state and it will be pretty good, but you're battery life is going through the crapper...

I actually dont think the solution we've been trying on this thread makes much of a difference at all. Once we load a rom, we all keep a close eye on the stack to be sure it works. This tickles the phone to keep out of its deep sleeps. so it seems to work better. We then relax and leave it alone, and presto the problem is back. Thats made worse by its not "everytime" that the phone has an issue either.

Anyway, my "train of conciousness" for the morning. Off to high-school football game, its finals time..

sfaure03

lol i made a post asking DSD about the same thing if u remember/ saying that it might not necessarily be the BT drvrs directly but in directly/ then what i said was if it might be the extra bloatware that a provider adds to the rom/ thus maybe they might perform alot better when they dont have the extras added/ u didnt get a copy of my radio 1.39 and i dont know if there is a version of it available but i do recommend that u try it if possible because qwest didnt load alot of crap into the rom and so it would come with the least baggage and make for possibly the easiest to work with/ is it possible that when HTC releases a rom that it works good then the carries screw it up?

Wow - not a period, comma, sentence capitalization, or paragraph anywhere in that comment! ;=)

Thanks for nothing willysp.... I was hoping you were going to translate :-P

I tried, but got a headache!

WE DID IT!
Or at least, I think so... updated the first post with more info, but in short, the BT from the touch WASN'T the answer after all!

It appears that 2.09 was a decent build, but it had the quality problem. Instead of trying to fix it at the source, Sprint/HTC dropped the BT drivers from the touch (which didn't have a problem) into a new rom which DID fix the BT voice quality problem, but had all sorts of new compatibility problems, which was our 2.16 rom. This is one theory, at least.
In any case, this new build seems pretty stable.
Try the link in the first post, and test it!

One of the things i didn't like about our latest attempt {see page 1 of this thread for link} was that the volume was lower than I had become accustomed to w/ bluetooth and the touch drivers.

I found another thread that gave me the following regedit that seems to help get it back:

HKLM/SOFTWARE/Microsoft/Bluetooth/AudioGateway
SpkVolume dword=10

I've tried different values, IMHO 10 did help, not sure others did. You will want to make this edit before pairing you're bluetooth device, or if you've already paired remove the current pairing and repair it.

I hope you're experiences with this new rom is as good as what we saw in testing this weekend,

Enjoy

i looked and didnt see a spkvloume....i was able to follow everything but once i got to audiogateway i didnt see a value or string for the spkvolume...am i looking at the wrong spot, i looked after i flashed my phone with the latest file and before i paired any bluetooth??
________
Nadira live

Sorry, i didnt mention that it WONT be there. You have to do an ADD first and name it SpkVolume

Thanks...i will give it a try
________
Ebony Webcams

Seems that the only known issue so far is the alarm bug. I know that 2.16 improves the memory management a lot over 2.09. Is memory management still an issue? Thanks.

Just curious, What is the initial setting you changed to 10?
Mine is set at 14. I am trying 10 to see if I notice a difference.

I too am curious whether Memory Management and the increased battery life from 2.16 are included in this new ROM.

I've seen a few posts claiming that 2.16 had better memory management, but my observation is that there's no difference. I gave up and moved to "up" to WM5 a couple of days ago. I'm pessimistically hopefull that the promised {sic} 1Q 08 release will address the memory problem and restore my Mogul to a WM6 device.