Just recently i couldnt upload photos or any other kind of media from my phone to my computer, in one second its connected, next thing u know when I open media manager, it disconnects the phone and I try reconnecting and that did not help obviously. Is there a solution or something that I need that is missing?
I gave up after I experienced what you've been experiencing...one moment it would show my phone, then the next day it wouldn't connect when I'd have a data cable or bluetooth device connected, so I went with P2k Tools 0.8.6....you can download it for free off of motomodders.net
Is it true that there is a place in a man's head that if you shoot it, it will blow up??
Well I tried installing different drives and such, the thing is I have no idea how to work on p2k, I remember solving this once but now I cant seem to remember how I solved this prob, It is weird how at first MPT worked how it should, I dont know how in the world it stoped working the way it was supposed to. Usually when I start it shows an error and usually I ignore it. could that be it?
Phones communicate in two different ways: AT Commands (like a modem) and OBEX. When Motorola Phone Tools opens the Multimedia Center it switch the phone into an OBEX mode (which uninstalls the TAPI modem from control panel). The more data that resides on the phone the longer it takes to switch into and out of OBEX mode. When you close the multimedia center, we tell the phone to switch out of OBEX mode and back into AT command mode.
If it is locking up at this point though, this can be caused by the OBEX push function locking up on the Phone. Please remove the Battery temporarily from the Phone (approximately five seconds) then power the Phone up. After this is done reconnect with the software and attempt a file transfer again.
What? I don't think so.
I don't think so.Obex doesn't have an operation called "push".
11.4 OBEX Interoperability Requirements
11.4.1 OBEX Operations Used
There are 5 OBEX operations which are used in the Object Push Profile: Connect , Disconnect , Put , Get & Abort.
11.4.2 OBEX Initialization
Since OBEX authentication is not used by this profile, OBEX initialization is not applicable.
11.4.3 OBEX Session Establishment
For the Object Exchange, the OBEX connection can be made with or without OBEX authentication. All application profiles using GOEP must support an OBEX session without authentication.
11.4.4 Pushing Data
It is highly recommended that the Push Client use the Type Header when pushing objects to the Push Server.
11.4.5 Pulling Data
In the Object Push Profile, the Push Client only pulls data from the Push Server when it is getting the Default Get Object (owner’s business card).
If there is no Default Get Object, the Push Server must respond with the error response code "NOT FOUND". The Push Client must be able to understand this error response code.
The Push Client must use the Type Header when getting the Default Get Object from the Push Server.
The Name Header is not used when getting the Default Get Object from the Push Server. If the Push Client sends a non-empty Name header, the Push Server should respond with the response code "FORBIDDEN".
Note, the above text contains excerpts from the Bluetooth SIG's Specification, as well as various interpretations of the Specs. For complete details of the various sections, consult the actual Bluetooth Specification.
Most Moto phones (as well as a large number of other makes) use the OBject EXchange (OBEX) protocol. OBEX was originally defined by the Infrared Development Association (IrDA) to be used for IR transfers but the transport layer was deliberately not defined. As a result, many mobile phone manufacturers have chosen to use the OBEX protocol on top of transports such as IR, Bluetooth, USB and TCP/IP.