How do I update the video driver for my Droid 2 Global? I have a custom Cyanogenmod installed but YouTube videos have a green bar, green tint, or are garbled.

We often get out of storage messages on our Motorola Droid Turbo 2 phone. We delete an App, and, say it's a 100 MB app, we only see about 10 MB free up. Likewise we've transferred and deleted gigabytes of pictures and videos from the phone, but only a tiny amount of space gets freed up. We're deleting and deleting and deleting, but we still have no room. Right now, looking at "Internal shared storage" - It shows 23.27 GB used of 24.06 GB but only 5.06 GB used for Apps and 7.32 GB used for imaged, 18.73 MB for videos, 0 for Audio, 475 MB for other and only 1.34 MB for cached data (so it's not cached data). Those don't add up to anywhere near 23.27 GB! Apps and Images numbers go down as we delete, but the total GB used barely moves! What is happening? How can we get our storage back? Per Robert's comment, we downloaded Disk Info, screen shot below. But, all it did was show that we used most of the "Data". There's no insight as to what is using it, or why as soon as we delete apps, photos, and videos, most of the amount we just freed appears to be instantly taken back up.

I have Droid 2 Global (droid2we) and I've tried Power + Volume Up, but that doesn't load any recovery mode. I've also tried Power + X but that loads the standard Android System Recovery , which won't install unsigned zip files. I can load the Bootstrap Recovery app which will let you reboot into Clockwork Recovery mode, which does work. However, that requires a functioning system which makes it a pointless way to launch a recovery mode!

I recently re-activated an old phone with my carrier. (To give you an idea how old, it is running Android 2.3.3, whereas the latest available for this phone is 2.3.4) It doesn't have the latest OTA update, but when I try to check for new updates ("Settings":"About Phone":"System Updates") I get the message "Checking for available update. Please wait..." and a spinner which just spins and spins. It never progresses past this point. If I back out and try to check again it usually doesn't even get to the spinner, sometimes I have to tap it many times before the spinner will even come up - some taps appear to do nothing and some appear to flash the "Checking..." for a split second. The phone has been rooted, but as far as I know that shouldn't affect an OTA update (although I understand the update will remove the rooting). Is it possible that OTA updates are discontinued after a while? This update is 2-3 years old. Is there anything else I can do to troubleshoot what the problem is? (I realize I could try wiping the device, in case there is something on the device that is preventing the update, but my concern is that if OTAs do expire then I would be stuck with an even older version on the device.) Update: It looks like the BlurUpdater_VZW.apk (and odex) were missing. However, the only copy I found appears to be from the 4.5.629 update and not the 4.5.608 that is on the phone, and it exhibits the same behavior. If I run the 4.5.629 version on a device with 4.5.629, I get a message that no updates are available, so maybe this means that if I can find a 4.5.608 version of the BlurUpdater files, that will work?

I want to put a custom ROM on my D2G, but I think I went about it in the wrong order. I thought that I had to do a factory reset, but that wound up setting me back. The phone demands that it be activated, but I can't get past that step. I don't want to go back to Verizon with this phone. How can I get past activation? I don't want to use the phone on another carrier. I just want access to the phone.

I used to use a program called "camera" to take pictures. I was able to see what had been taken, and save (or not) as I took them. And when I attached the phone to the USB port of my (linux) computer, I could find the pictures in the phone's memory card file system, which could be mounted. The program "camera" appears to have auto-updated. I can still take pictures - but that seems to be all - I can't access them, either within the program or via the SD card. I didn't see anything relevant in the program's menu(s) - neither the one I get from the phone's menu button, nor the one I get, briefly on the right side of the screen, when I tap a small non-descript image on the upper left. Perhaps I'm now supposed to access photos via some other app - on the phone at least? Any idea what it might be called? And how on earth am I supposed to get access to the underlying files? The phone claims to be running Android 2.3.4

I picked up a DROID R2-D2 from a coworker who has given up on the device. Knowing I like to tinker with these things, she offered me the phone in whatever condition I can muster from it. A few weeks ago, she dropped it into some water and from that point on, the android OS will no longer boot. The bootloader screen comes up when powered on (without forcing this mode using the hardware volume buttons), but that's as far as it goes. I don't believe this is a boot-loop, as the phone does not automatically reset itself, but I'm somewhat new to the terminology. I don't believe this question is quite a duplicate of this one , as the screens I am able to access are different. I also have a DROID X (similar question for this model ), but for those unfamiliar, the bootloader presented using the volume-button-on-boot method does not produce the same screen. on the X, there are actual options, such as loading fastboot, etc. With the 2/R2-D2, there are no options, just "OK to program". I am not sure if the bootloader is unlocked or not. The working D2 is in stock condition, and the bootloader menu is minimal as compared to that of the X, and the non-working bootloader is identical. If the stock condition is locked, then I assume that this is the case. I can force recovery mode (holding the keyboard 'x' while booting), but the options there do not help. From the bootloader screen, this is what I see: >*Always this header*: Bootloader D2.37 >*if battery is charged*: Battery OK OK to Program >*if battery is depleted* (I think, the batt's full at the moment and my memory may be off): Battery low Unable to program >*if no USB connected*: Connect USB Data Cable >*if USB connected (to PC or straight power)*: Transfer Mode: USB From the recovery screen (after loading the ! image and getting to the actual menu by pressing both the volume up and down buttons at the same time), this is what I see: Android system recovery Android system recovery utility reboot system now apply update from sdcard wipe data/factory reset wipe cache partition Of the above options, I have tried all, but I know the sdcard option was done incorrectly, as I am not sure which files are required for this update. The other options, which 'worked' resulted in no change in the boot behavior. The phone is detected by my Windows 7 machine. i.e. When I plug the device into the PC, Windows detects the hardware and recognizes the R2-D2 as being the same (no new drivers required) as the Droid 2, and I can see it in my list of devices in My Computer. However, I can't run any debug functions on it. i.e. The D2 (essentially the same phone, same hardware, drivers, etc.) that I regularly connect to my PC to test my own programmed apps, and ADB works flawlessly. Any attempt to debug the device results in the device not being found by adb. While in either the bootloader or in Recovery Mode, the R2-D2 cannot be detected by adb devices. If I plug in the functional D2, adb immediately is able to display the device ID. Also tried to see if fastboot would detect the device, but it did neither at the bootloader, nor in recovery mode. I downloaded a series of .sbf files from various sources (this being the only one I can find at the moment), and reflashed using RSDLite. I am new to this and so I used numerous walkthroughs from the web to get me this far. I am somewhat confident that I've learned how to flash properly, since some of the attempts failed and caused the bootloader to fail, but a few of them at least got me back to the same 'working' condition the phone was in when I picked it up. At this point, I don't care if the phone is rooted or not; I don't care if I have a custom or stock ROM loaded; I don't care if the OS is buggy once running. I would just like to be able to get the phone to boot at all. The original owner has since picked up a replacement from Verizon, so worst-case scenario (the phone is a brick) is not the end of the world. Especially given the fact that I have a nearly identical phone to work with, is there some way I can rip the .imgs from the working model and load it onto the broken one? Is there a step in the .sbf reload that I could be doing incorrectly? Are there any other tips or sources to help me get this phone up and running again?

I have a Droid 2 Global and I can't seem to access the contacts on my sim card. How do I access them and transfer them to the phone?

The middle third (long-narrow thirds way) of my digitizer seems to have crapped out. Diagnosed from having vary hard time unlocking and weird selection issues, to suspecting digitizer, to getting a drawing program installed and seeing no record of movement over that part of the screen when drawing. This makes unlocking (non-secure) with the "slide to unlock" tab almost impossible - takes 20 or more tries to get it to work sometimes. Since that button does not move when the screen rotates, I can't get it to live where the digitizer works. I thought I might be able to make it work with "pattern unlock" but that won't set a pattern with the middle third out of operation. Same issue affects the sound on/off (and trying to unlock often sets the sound on or off instead.) **So my answerable, stack-exchange-ish question, essentially, is whether there is any way to move/reorient the "slide to unlock" tab, or let the keyboard do that function.** Phone has not been wet, but I tried drying it anyway since many digitizer problems seem to be water related. No help. On/off/reboot battery in/out also make no difference. While it's irritating, if I could get something else (like the keyboard) to do what the slide-unlock is doing, but reliably, I could live with it as is for as much as I use the touchscreen. I'm on a rooted (basically so I could install AFWall+, as I'm using it on a prepaid service primarily to make/take calls with, and really wanted to make double sure that any data use was restricted to WiFi, ONLY.) "Gingerbread" (2.3.4) Motorola Droid 2 Global if it makes a difference. I'm no great shakes at android-ness, I basically tracked down a root tool method that was purported to work, and after finding that many versions of it didn't discovered one "not the most updated" version that did work, despite dear old VZ making it more difficult. (*I'd also like to ask about replacing the digitizer, but after reading the help page 3 times I'm **still** not sure if that's considered on or off topic, since it's more about "hardware running android" than about "android as such" but it is "a problem I'm trying to solve on my android device"*)

I purchased an old Droid 2 with a clean ESN today, rooted it, installed Droid2Bootstrap, loaded Monster_D2_2.3.2_4.5.153 onto the sdcard, cleaned the cache, wiped the data, rebooted into recovery, loaded the new images, rebooted. Came back up just fine. Now, here is a problem you may not have experienced before. I am not a Verizon customer. Just wanted the phone to develops Apps and play with. How can I get past the phone number activation requirement?

I just broke my *Droid DBA* so im switching back to an old phone (*Droid 2*). But my lock screen is not responding properly: it shows, I grab the lock, but it doesn't unlock (or it just doesn't register). Does anybody know whats wrong?

Why can't I use the latest version of Cyanogen ROM for Droid 2 Global? The latest available version for this phone is CM 7.2, while the current version is 10.2. The [wiki page](http://wiki.cyanogenmod.org/w/Droid2we_Info) just says 'hardware limitations', but is not explicit. I'm not aware of any limitations other than it might go a bit slower than a new phone. What would happen if I installed the latest Android Open Source Project on a D2G?

I went to the getfirebug.com web site, where I was able to install Firebug under Firefox 1.10.6 (the Beta version of Firefox from the Play store). It said the install was successful. Now what? How do I activate Firebug? There are no new icons that I can click on like there are on the desktop version, and long-clicking on the page isn't doing anything either. I see no new menu options either. In the add-ons menu I see Firebug, but it only offers the choice to disable or uninstall, so I know it's there and installed.

I have been deliberately avoiding the latest Verizon D2G update for a few months now. It is really annoying that there is no way to make it stop asking me. But tonight I was tired and my finger slipped and it accidentally accepted instead of delaying 12 more hours. My phone started to shut down to install but I quickly pulled the battery out. Now every time the phone boots after about a minute of starting services it apparently remembers it was going to update so it starts shutting down the phone. I have tried going to updates and manually looking for an update, in the hopes that this would confuse the phone and it would start asking me again if I wanted to update, but in the middle of searching for an update it just suddenly aborted and threw me back to the setting menu, and subsequent attempts just immediately aborted. [edit:I tried this again, this time immediately looking for updates as soon as I could login. This time it immediately started searching, and continued searching until the auto-shutdown started.] I also tried looking at the processes with a system monitoring app I have but wasn't able to identify a process to kill before it started shutting down - and even if I did I am afraid it might still start updating when I'm not watching later. Is there any way I can abort the install? I am afraid to let it actually start installing because I don't know what to expect. Does it offer me a chance to cancel? If not, I fear I might brick my phone if I pull the battery after it starts to update. And in case you are wondering, I absolutely will not allow this update because of the risk of the update breaking some obscure feature I depend on. For another, this is the update that removes the ability to root. My phone is not rooted, and I really don't have the the time or inclination to root it at the moment (it is another risk I don't want to take) but I won't accept the ability to be removed. Edit: The following information is from the adb log: 07-XX XX:31:15.883 1306 1433 I ActivityManager: Start proc com.motorola.Upgrader for broadcast com.motorola.Upgrader/.UpgraderReceiver: pid=2334 uid=1000 gids={3002, 3001, 3003, 1015, 2001, 1007}^M 07-Xx XX:31:15.953 2334 2334 W UpgraderReceiver: !!! INSTALL UPDATE !!!^M 07-XX XX:31:15.961 2334 2334 W RecoverySystem: !!! REBOOTING TO INSTALL /cache/Blur_Version.4.5.608.A956.Verizon.en.US.zip !!!^M 07-Xx XX:31:15.961 2334 2334 I RecoverySystem: in google bootCommand, 23103 disalbed^M 07-XX XX:31:15.961 1306 1340 D ShutdownThread: Notifying thread to start radio shutdown^M So, it wants to install 4.5.608.A956.Verizon. [update: actually, that can't be right, because that is the version I am already running! ] Also, the following did not work: bash-4.1$ ./adb uninstall com.motorola.Upgrader Failure bash-4.1$ ./adb shell kill $(./adb shell ps | grep com.motorola.Upgrader | awk '{ print $2 }') could not kill pid 2379: Operation not permitted Update: Well, I am thinking it is looking like maybe the only way to avoid the update is to actually root my phone. :-(

By mistake I checked data usage from android widgets, and now its in my droid 2 welcome screen. How can I remove it from the welcome screen?

I did a factory reset on the phone, to switch to a different email account. Since it's cell service contract expired a while ago, I used [this](http://theunlockr.com/2010/09/20/how-to-bypass-the-activation-screen-on-the-motorola-droid-2/) to bypass activation and get to the home screen, then connected my google account. Before the reset, I had the google play app, and had used it without a problem. Now it's gone, replaced by the Market app. Whenever I try to open the Market app, it sends me to a web page with the google Play TOS, but no "Accept" button. How do I update to the google Play app? ***EDIT*** Nevermind, my phone seems to have re-installed all of the apps from before it's reset, including google Play.

I am experiencing this on a Droid2 Global running Froyo, but it was happening on a Droid Pro as well. It did not happen on my Droid running Cyanogen or stock Froyo. When I'm typing in the gTalk app or using Tweetcaster, my text is auto-corrected. Even when I have auto-correct turned off in the keyboard settings. I use a lot of shorthand, and this gives rise to interesting conversations some times as auto-correct turns abbreviations like "DX" and "D2" into "PD" and similar silliness. So, the question is: Is there more than one setting for auto-correct? If so, where is it hidden. *It seems to be global since more than one app suffers from it.*

How to get the droid 2 to enter fastboot? Running rooted phone, CM7 nightly 239 Power + x gets me recovery Power + Up gets me bootloader

I have a Droid 2. I have a long, resource-intensive game (spectral souls) that I would like to leave running while I'm not using my phone. If I hit the Android "Home" button to get back to the home screen and then immediately re-launch the game, it will be right where I left off. Same if I hit the power button to sleep, and then immediately turn on the phone, unlock, and re-launch the game. If I leave it for some amount of time (a few hours), then when I come back and launch the game, it starts fresh as if it were never running. The phone hasn't been used for anything in the meantime, although syncing is on. My question is twofold: how can I get more information about what apps are killed when & why, and how can I set it up to allow this app to continue running? I don't need it to DO anything in the background, I just want it to still be there when I come back. I'm familiar with the concept of Android clearing memory as it's needed and not needing a task killer, but I want it to not kill THIS task unless I really exit it.

I recently got a DROID 2 Global with Verizon and am looking to maximize my battery life. I am aware of the need to dim my display, disable Wi-Fi and GPS when not using it, increase sync intervals, and all that good stuff. However, in my continuing effort to maximize my battery life without shutting down stuff I really need, I came across the network mode settings. Since I am not planning to leave the U.S. any time soon, I don't need global so I've switched it to CDMA. I have heard that this might not make a difference because the phone only searches for the Global network if it can't find CDMA. However, the source didn't seem fully reliable **Question**: Will switching to CDMA-only use less resources (and power) than Global, or will it make no difference because Global and CDMA-only perform the same in the presence of network?