doogie

Wanted to say "thanks" - recovered a dead F900BT today. Pioneer really should ship these things with a "blow away and restore" SD.

So you didn't do any of the other registry changes that the post I linked to mentioned? If so, do you know what those are for exactly. Thanks.

Trial and error was essentially how I arrived at what I posted. The other changes essentially null the phone's Bluetooth MAC as well as the last connected device's Bluetooth MAC..which seemed redundant.

The way I look at it..I want to modify as little as possible.

Happy to do another .cab that does the full meal deal, but if this works for folks I'd rather leave it alone.

Again, much appreciated for tracking the solution down, this is a life saver.

The attached file can be installed on your Touch Pro 2 to (hopefully) solve the problems with Bluetooth documented in this thread.

Before installing this, make sure you're experiencing the problem described and have the right hardware.

I have tested this file on my Touch Pro 2, using the stock Verizon WinMo 6.5 ROM as well as MightyROM 1.20.10.

To keep modifications to a minimum, the fix assumes that you do NOT have any Bluetooth devices paired. Therefore, you should delete the connection for your phone on your AVIC, and re-pair following installation of the fix. Alternatively, hard reset the Touch Pro 2.

The file makes the following modifications to the registry, and will take effect after a soft reset:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\HandsFree]
"HFDeviceType"=dword:00000002
"SupportedFeatures"=dword:0000002D

[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BTConfig\General]
"DisableReopenAudio"=dword:00000000

PioneerAVIC_WIDCOMMBT_Hotfix.zip

1.9.2 build 500 here. Verizon is my carrier and I'm currently on stock 6.5 ROM, moving to MightyROM later today.

Still working solid here as well.

Heavy use of the phone last night (on-call for work)..

Got in the car today, got 2 calls while on the road, placed 1 from the AVIC dial pad.

No problems, looking real positive here.

Just documenting while I try to understand what these settings actually mean.

Following reboot and re-pair:

HKLM\Software\WIDCOMM\Plugin\HandsFree

SupportedFeatures to 45 - stayed the same

Add value HFDeviceType decimal 2 - stayed the same

* LastConnectedBda was created and was set to the AVIC's BT MAC

HKLM\Software\WIDCOMM\BtConfig\General

Change bdaddr to (no value) - reset itself to the BT hardware's MAC

Add value DisableReopenAudio dword 0 - stayed the same

Initial result is huge success..

Previous behavior was:

-Incoming calls ring for ~1 second and get rejected to voicemail

-Outgoing calls work from the phone only, and do not display the Phone UI on the AVIC device

Now:

-Incoming calls ring with the "Pioneer" ring for a short moment, then switches to the phone's ringtone

-Incoming calls working fine, UI displayed, caller ID looks good

-Outgoing calls work from the phone or from the AVIC UI

I had not paired my AVIC to the phone, and in fact had just hard reset. So I was missing some of the settings called out in the PPCGeeks post.

I changed:

HKLM\Software\WIDCOMM\Plugin\HandsFree

SupportedFeatures to 45

Add value HFDeviceType decimal 2

HKLM\Software\WIDCOMM\BtConfig\General

Change bdaddr to (no value)

Add value DisableReopenAudio dword 0

Following a soft reset, I paired the AVIC and was astounded that it worked.

I will too give this a couple of days, reflash, reverify, and create a CAB for you guys.

giving this a try. THANKS for keeping us posted.

I would too. I've called Verizon about the same problem several times, and it seems I hit some sort of threshold: the last 2 times, I got a replacement device (which, of course, changed nothing). This time, they said they'd "escalate to HTC".

Probably not too much different from dougthug emailing HTC support, but, well, it's something I suppose.

I was offered a 4th replacement, which was entertaining. I declined.

yeah..well, this is unfortunately becoming a showstopper. I really like the TP2. I've tried disabling all voice command and system sounds via bluetooth, I've blown away the F900BT as well as the TP2, tried custom roms on the TP2. I got nothin'.

Can't answer a call on the F900BT or on a Jawbone headset. The caller gets sent straight to voicemail, the phone hangs for ~20 seconds, and the F900BT (usually) requires a power cycle.

I can, however, make calls, but in the F900BT's case, the phone UI does not show up. The audio is muted but the unit otherwise acts like no call is in progress.

My Touch Pro and Mogul were both fine and worked perfectly; I tried a Droid Eris and that was fine, as well. Unfortunate that HTC has decided to integrate the Widcomm software instead of the Microsoft BT stack.

Does the Motorola DROID work okay?

slow..but stable for sure. They beat Sprint, which is a surprise

I'm a MightyROM junkie too and am also finding the 1/4/10 release to be much better performing, on the phone itself as well as BT.

+1. same scenario for me, F900BT with Verizon Touch Pro 2.

Sent you a donation IDT. Thanks for the hard work.

 

Is there any documentation or wiki on this stuff yet? Seems overdue, what work has been done, how can I help?

 

thanks for the donation bro, i'll try to have a kinda quick guide included on the next one,

I am happy to help on documentation, please let me know how I can help.

Sent you a donation IDT. Thanks for the hard work.

Is there any documentation or wiki on this stuff yet? Seems overdue, what work has been done, how can I help?

An overall good experience for me..1 failure at 99% while "Data upgrading" on SD #2. Funny that the retry logic was built in, I wonder if it routinely failed in testing, what the backstory is there. Either way it carried on just fine.

The upgrade is painful in terms of time taken. 51 minutes start to finish for me.

The result, though, is the way the unit should have shipped initially, in my opinion. Very solid so far.

Because 3.0 is not available thru official channels, that I can see. Maybe I missed an announcement.

My F900BT update just shipped.

Nothing here yet. "Awaiting shipment"

Dammit. I wish I had looked at this thread earlier, what a moron!

After paying $28.92/mo for the last 9 months (2 radios + NavTraffic + 128K XM Online), I called today and got $77/year for each radio, no if's/and's/but's. Thanks for posting this, saving a ton (now).

I have 2 Patriot-branded SD cards; one 2GB (used for testmode/mods/updates) and one 16GB (music). I have the best luck formatting them FAT32 (required) with 4KB allocation units. Windows 7 wants to use 8KB on the 16GB card by default, although I frequently got hangs ("Now Loading") using that scheme.

Additionally, the F-series seems to prefer many folders (e.g. albums) rather than many files in the root directory. Same reasoning here; load time.

Just wanted to say thanks, this helped me out.

ha, was able to confirm that my F900BT backup works just great, it saved me yesterday..

Anybody interested in a 2.006 backup? Really it's just a merge of 2.0 + the 2.006 files from Pioneer's .zip.

Yeah, no joke. Thanks cmh..much appreciated. I'll dig in and see what's different, hopefully make a contribution here rather than just taking others work.

Love the new Samantha. One funny problem though is, with street names like:

"148th Ave NE" (One hundred forty-eighth avenue northeast)

Samantha pronounces that as "One Hundred forty-eighth avenue Nebraska"

Which is, you know, humorous...is there a way to fix that? Street names that begin with NE, as in "NE Union Hill Rd", are pronounced correctly.

I looked over the files in \config but there's nothing in rules.ini or any of the .csv's that seem to override this.