Motorola DROID hangups and bugs
I recently bought a Motorola DROID smart phone on the Verizon Wireless network. The phone seems to be very durable, and the Android operating system is a wonderful competitor to Apple’s iPhone. There are a growing number of apps available for these phones, with some notable ports of iPhone apps to the Android platform. There are some weaknesses of the Motorola DROID phone that potential customers should know about. The ones that I have stumbled upon are that text messages get deleted often by the phone, even when the auto delete setting is switched off, the fact that the phone has pathetically small internal memory for apps (about 256 megabytes, which is pathetic), and that multimedia messages take up so much internal memory that you might end up deleting apps just so that the phone dialer storage doesn’t run you into the wall when its growth runs wild, and vanishing bluetooth devices.
- Text message threads are set to auto delete when they hit a certain number of messages. You can alter or turn off this default behavior in the test message app settings, but it will eventually delete them anyway. It happened to me several times and it is happening to others our there. The only thing you can do right now is to install SMS Backup, a nifty free app that will copy your text messages to your Gmail account for archiving. It works, and there are paid apps that will also do this for multimedia messages (picture and video containing messages).
- The Motorola DROID has a pathetically small internal memory of 512 MB, half of which is available for apps. To add insult to injury, Verizon is advertising that phone as having 16GB of memory due to the micro SD card that they ship with. The problem is that Google has made it so that only internal phone memory is available for app executables, and most apps are made in a way that they use the internal memory for everything, so if you install many apps you run out of memory pretty quickly. Regular apps are small, but install a few games or some data crazy apps and see how far you get. Shame on Motorola for cheaping out on memory, Verizon for false advertising, and Google for not allowing some more leeway for using the SD card for applications, although they cite security and piracy concerns.
- The “phone dialer storage” app seems to store data of some sort on the phone, and it tends to runaway with itself as you create more message threads, especially those rich with photos or video attachments. The obvious cure would be to delete the photos and other attachments or purge your text messages every so often, which works up to a point, but I found that my phone dialer storage held it’s data cache even after I purged. The phone got sluggish and rebooted itself a few times too. Finally after one spontaneous reboot, the cache was somehow purged. Perhaps there is some internal software setting that does this, but it’s VERY annoying and not a graceful way to go about it. The best thing that Android users who hit their phone’s memory limits can do in the meantime is to get an app management application which allows them to shuffle apps around from the SD card back to phone memory. What this means is that you have to archive the app to the SD card and then uninstall it through the management app. If you want to use it later you can reinstall it from the archived copy. This allows you to archive those many megabyte game apps that you might not use everyday but don’t want to ditch for good. It’s a compromise but it works.
- My bluetooth ear piece, a Samsung WEP470, occasionally vanishes from the phone. Usually rebooting the ear piece fixes the problem, but I found that one time it did not. Sometimes turning the phone’s bluetooth on and off would fix the problem. One time nothing worked, and you could hear the incoming phone call beep in the ear piece but when the call was answered no sound came through the ear piece. I thought the Samsung bit the dust and even started shopping for a new one. I tried a shot in the dark approach of turning the phone off and removing the battery for a few seconds, about 10, and then powering it up again. My bluetooth ear piece now worked fine again. Go figure.




