Motorola Device Manager
Katina Piccirilli
The download has been tested by an editor here on a PC and a list of features has been compiled; see below. We've also created some screenshots of Motorola Device Manager to illustrate the user interface and show the overall usage and features of this Motorola updating program.
Motorola Device Manager contains USB drivers and software to connect your Motorola phone or tablet to your computer using a USB cable.For certain Android-powered devices, Motorola Device Manager can also update your software.
Features of Motorola Device Manager
- Backup operations: Backup and restore data on your device, including contacts, messages and other personal data.
- Device management: Manage and organize your device's apps and settings, such as disabling or uninstalling apps and changing system settings.
- File transfers: Transfer files between your device and computer, such as photos, music and videos.
- Firmware updates: Update the software on your device to the latest version, including security updates and new features.
- Phone manager: Connect your Motorola device to your computer and manage it from the computer.
- Solve common issues: Troubleshoot and diagnose problems on your device.
After dragging this horrible app to the MacKeeper shredder, it still prevailed. I could not locate its evil remnants even after following suggestions found here and in other forums. Finallly, I ran MacKeepers 'Smart Unistaller' and found it hidden somewhere in there and clicked delete only because I could not shred it there. Next I ran 'Disk Usage' where it will appear in 'Trash'- thats when I was able to drag it to the shredder and bid it adieu for good! Worst device manager ever! Slowed my Mac down and really wreaked havoc!
I am having the same problem where the Motorola Device manager software updater keeps opening up on my workstation and I cannot see how to delete it. In my Library>Application Support folder, there is no sub folder labeled Motorola Mobility. Where else can this updater be hiding? Thanks, Scott
All of the Motorola files (including the Uninstaller) are in the hidden library. Go to Finder, then under tab Go hold down option/alt and then select the library folder there. I deleted everything related to Motorola, Motohelper, and Motocast, I believe, and ran the uninstaller, which was in Application Support (in the hidden library, obviously). I also deleted the Saved Application State as that can make items come back from the dead sometimes. That did it for me!
Even though you've done everything Avatar71 said, you could still have this stubborn little thing stuck to your drive. Once you try to empty your trash basket, these little Moto things could refuse to leave you alone for good (it happened to me).
3.- Open your trash basket, go to the first "Moto" thing you find (folder, file, etc.), do the two-finger thingy on your mousepad (if you haver a MacBook), or do whatever you do on a conventional mouse to open the auxiliary window (right-click, maybe?).
I followed your instructions and was able to remove the items from my trash. However, when I restarted my computer from safe mode the very first thing that displayed on my screen was the same old Motorola Device Manager software update!
So i've deleted EVERYTHING that I can find, and yet every time I start up, this wretched little update shows up again. I've gone through safe mode and through the trash, but couldn't find the files that I deleted in regular mode. But, I've noticed in the activity monitor there is something called "MotoHelperDaemon". Every time I try to force quit it, it just pops back up and continues operating. Besides punching through my wall in frustration, what else can I do to get rid of this once and for all?
Only issue is the program imbeds itself in the users startup. I have the same issue I looked at my "open at login" items and it was there. Unchecked it, still appears. Its literally coded to be difficult, elusive and sorta perminant unless you know what you are doing. I see it in activity monitor but I still cant locate the files. Im making progress though. Just thought I would share because I dont know if that actually works because my trash has been securely erased several times since I thought I deleted the app.
I'm going to throw this in here because for me, it was installed under the library of my user and the library under root. I tried it the right way first, uninstall left the the network folder under the user folder... but then lost patience and just rm -r Motorola Mobility directories in both places in term.
I picked up a Motorola Luge for some testing. I plugged it into my Mac and it launched Motorola Device Manager. The device manager appears to check for updates (I presume for both the program and the device, but I'm not sure either guess is correct).
Motorola Device Manager is failing with the error message "An Internet connection cannot be established". Obviously, the Mac is online and the Internet connection works because I'm asking this question.
But I cannot get a connection between my new Moto E7 to the PC.
The Moto E7 app 'My Phone Explore' shows a USB connection when turned on but the PC end of the same program says that there is "No device connected".
The Win7 Pro device manager sees that the Moto E7 is connected but says that there are no installed drivers for the device.
Even after installing the latest Moto drivers there is no connection happening and still shows "no drivers for the device".
Uninstalling and reinstalling the same and then several other Motorola driver versions, the Moto E7 and PC will still not connect.
The EMDKManager instance will always provide only one object (singleton object) of each feature like BarcodeManager, ProfileManager etc. Any attempt to request a new object of the same feature will return the object that is already initiated.
The EMDKManager -> ProfileManager supports simultaneous usage in multiple applications. This means, an individual application needs to not release EMDKManager -> ProfileManager before going to the background. In the previous versions, if an application going to the background did not release the ProfileManager, no other applications could access ProfileManager.
For those who want to write a common application that is capable of running on both Zebra and Non-Zebra devices, care must be taken to use the EMDK components only on the Zebra devices as described below:
When the common app is launched on a non-Zebra device, the "ClassNotFoundException" exception may occur. To overcome this problem, do not implement the EMDK interfaces in the MainActivity. Instead, create a separate class (ex: EMDKAPIWrapper or any other name) and implement the EMDK related calls in that. When the activity starts, create the EMDKAPIWrapper object during the run time only if you are using the Zebra device.
The application must call EMDKManager.getEMDKManager to use the EMDK. It is recommended to call this method in the onCreate method to avoid a delay at a later stage. EMDKManager will call the interface EMDKListener.onOpened when the EMDK is ready to use and this callback will be called on main thread only; therefore the application must not block the Main thread to receive EMDKListener.onOpened callback.
The EMDKListener.onClosed gets called to notify the application that the EMDKManager object has been abruptly closed due to some failures at EMDK or a lower layer. When this occurs, the application must the release the current EMDK manager instance and get the new EMDK Manager instance
Note: If you are blocking the main thread, the application will not get notification when the EMDK closes unexpected reasons and therefore the application must not block the main thread to receive the EMDKListener.onClosed callback.
Zebra Technologies Mobile Devices running the KitKat Android OS will have the EMDK device runtime built-in, but devices running Jelly Bean Android OS will not have the EMDK device runtime built-in. The EMDK version on the device can be checked either by manually or programmatically.
c80f0f1006