Bluetooth Contacts issue with 6.1 6800 / touch

[shdwknt]

OK..

I have tried searching with no luck.

I am not looking to get flamed - just some help.

Ever since I have upgraded to windows mobile 6.1 on my 6800 and a friends Touch - I can not send contacts to or from the devices via bluetooth.

At work we use 2 different tools - 1 is a cellbrite machine and the other is RMS - niether of them will properly put the contacts into the devices.

Is there a fix for the bluetooth on win mo 6.1?

What could i be doing worng?

Thank you!

[sinclairj75]

you aren't getting any contacts to move over at all???

[shdwknt]

It does not even give me the option to send via bluetooth..

and when I try to send a .vcf (vcard) to the device via bluetooth - it fails.

Cellbrite can connect to the phone - but will not send contacts.. it starts to and then says that there is an error with the device. The only option I get when I highlight a contact and click on send is via infra-red on the 6800 and nothing on the touch.

I know it is just not my devices - EVERY 6.1 touch and mogul that we have tried to do at work - will not copy over..

ANY information on these devices and the problems with sending contacts via bluetooth would be great.

[PhantomApolyon]

the mogul with 6.1 will work on the cellbrite via IR provided you let your cellebrite auto update via HTTP(have done tons of them here)

however the overall fix that we do is this:

1. get a windos mobile 6.0 phone for the store to keep for transfers.
2. when a 6.1 phone comes in, backup the pim file(from the 6.1 device) to your microSD
3. load that pim into the store phone(6.0 device)
4. transfer as normal with cellbrite

[shdwknt]

HMM.. yes I forgot about the infra-red on the mogul.

How are you doing the PIM backup on the 6.1 device to the mem card to swap back into the 6.0 device? Can you elaborate on this? Thanks for the input

- Shdw

[PhantomApolyon]

1. open "my device" on the 6.1 phone, copy the pim file
2. open the storage card on the 6.1 phone, paste the pim file
3. put that mem card in the 6.0 device
4. open "my device" on the 6.0 phone and rename the pim file to "pimold"
5. menu->edit->paste->soft reset the 6.0 phone
6. Use the cellebrite to transfer as usual

[shdwknt]

That helps with getting OFF of the device.. what about GETTING INTO a 6.1 device? Like - customer has a rumor - wants to goto a touch and the touch is 6.1 RMS wont work, cellbrite cant (bluetooth issue and no infra-red on the touch)

and no win mo 6.0? Would coping the PIM info from a 6.0 work going into the 6.1 same way? Running rumor to a 6.0 then 6.0 to 6.1?

Inquiring minds would like to know

[PhantomApolyon]

Originally Posted by shdwknt

That helps with getting OFF of the device.. what about GETTING INTO a 6.1 device? Like - customer has a rumor - wants to goto a touch and the touch is 6.1 RMS wont work, cellbrite cant (bluetooth issue and no infra-red on the touch)

and no win mo 6.0? Would coping the PIM info from a 6.0 work going into the 6.1 same way? Running rumor to a 6.0 then 6.0 to 6.1?

Inquiring minds would like to know

if they have a rumor, do a normal transfer to your in store 6.0 device and then just copy the pim file to the 6.1 touch

we're a repair center here so its our job to know the tricks ... heck your lucky to find a store in town that knows their *** from a hole in the ground in reguard to WM, or BlackBerry OS, or let alone *Gasp* Palm OS

[Nikkirox_1]

I came on this site looking for a solution to my inability to send via bluetooth or IR any contact from another phone to my recently updated Mogul Win Mobile 6.1 phone. I was able to do this before I did the update.

[shdwknt]

Originally Posted by Nikkirox_1

I came on this site looking for a solution to my inability to send via bluetooth or IR any contact from another phone to my recently updated Mogul Win Mobile 6.1 phone. I was able to do this before I did the update.

Apperantly after talking to a guy at a comtronics store - there has been a fix created by the guys at xda-delevolpers - my problem is.. I cant find it.. everything they are pointing to is a registry edit on the device - that setting is already done with no fix to the problem.

Any other bright ideas?