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

jaytv · #51 (**permalink**) 11-08-2007, 05:28 PM

the java lockups occured during BT use, so that is what I was attempting to recreate...
interesting the Esmertec java so far doesn't have this issue, but the embedded java does...hmmm.
No dpad issues to report, and other than JVM/Opera install, as per instructions, I have kept this configuration clean...

BTW: I let Sprint customizations run...

biglee · #52 (**permalink**) 11-08-2007, 05:37 PM

Quote:

Originally Posted by jaytv

the java lockups occured during BT use, so that is what I was attempting to recreate...
interesting the Esmertec java so far doesn't have this issue, but the embedded java does...hmmm.
No dpad issues to report, and other than JVM/Opera install, as per instructions, I have kept this configuration clean...

I can't get it to recreate the dpad issue either. I've been letting it sit for 10 minutes and sleep and power on and the dpad is working ok. Also, I haven't dropped BT at all YET. I'm gonna run with it for tonight as see how it handles over time. I still gotta put my programs back on it.

Did you let the sprint ca-ca install? I did.

sfaure03 · #53 (**permalink**) 11-08-2007, 07:21 PM

I did not allow the customs install.

I have isolated this to two modules, and am working to get those two modules converted.

I'm glad to hear some are having the same positive results i have.

vMAC · #54 (**permalink**) 11-08-2007, 07:54 PM

Quote:

Originally Posted by dcd

i cannot pull the touch bt drivers into the alltel 2.14 rom and make them function. so i started trying to pull the sprint 2.16 bt drivers into alltel 2.14 and cant get that to function either. something is fundamentally different going to 2.16, and its closer to the touch.

however, i feel that 2.16 is garbage, noone should be using it, and it wont do us much good to pull bt drivers into it. if you break the sprint 2.16 release down into parts, each individual part is bad in some way, other than SYS.

I'm actually loving the 2.16 upgrade, why do you say it's so bad? Of course I don't use the d-pad too much so that's not a problem for me, but other than that I'm seeing huge increases in battery life, and everything else is just as it was in 2.09 or better.

desairs · #55 (**permalink**) 11-08-2007, 08:00 PM

I dont know if anyone cares but i loaded the bin with radio 1.32 and i didnt add anything else. I turned bluetooth on took a nice 2 hour nap, woke up and the dpad didnt work. bluetooth turned itself off. i dont know if this helps but this is what ive found

ktwombley · #56 (**permalink**) 11-08-2007, 08:21 PM

I'd love to help test this, but I don't know which ftp you guys are talking about. Can someone clue me in via PM or something? Thanks.

desairs · #57 (**permalink**) 11-08-2007, 08:26 PM

click on qlinks on the top of the page and then click open ftp. go to titan/users/..... and its there.

biglee · #58 (**permalink**) 11-08-2007, 09:21 PM

Bluetooth has not dropped at all. A definite positive.

I also added Microsoft Voice Command 1.6 and was able to get the confirmations to finally work. I did however install the Apachehaxvc installer and now the confirmations work over bluetooth like they used to on the 6700. Another words, I press the button on my headset, say call tom at work, it confirms and I say Yes and it dials. Only problem I have with it, it doesn't announce it in the headset, but it does over the PPC speaker.

I have also noticed the the BT is also VERY loud with this setup.

I did however have a minor Dpad issue, but I think it was to due with me walking to the other end of my house while my headset was at the other end. When it was out of range, the DPAD got a little balky, but when I fetched my headset, all was well. Not sure if it was searching or what. I'm gonna keep an eye on it.

So far, I'm loving it. I've installed everything I normally have on it and its running OK. I'm thinking that I we can get the BT stuff isolated and installed on 2.08, 2.09 or even the Alltel or other ROMS, we may be close to making this thing.....usable.

dishe · #59 (**permalink**) 11-08-2007, 10:28 PM

it seems that 2.08 and 2.09 had vastly different BT setup than 2.16 does. 2.16 more closely resembles the touch as far as drivers go, so the files could be dropped in.
With 2.08 or 2.09, it fails to boot.

But, if this fixes the major issues with 2.16 (BT, Dpad and freezes), why go back to the older roms anymore?

**willysp** · #60 (**permalink**) 11-09-2007, 12:00 AM

Quote:

Originally Posted by dishe

it seems that 2.08 and 2.09 had vastly different BT setup than 2.16 does. 2.16 more closely resembles the touch as far as drivers go, so the files could be dropped in.
With 2.08 or 2.09, it fails to boot.

But, if this fixes the major issues with 2.16 (BT, Dpad and freezes), why go back to the older roms anymore?

Sprint should be mortified (they won't be of course) if the solution to the Titan BT problem is as simple as copying the Vogue drivers. That would redefine incompetence to me!