A couple of days ago we told you about the much needed update coming soon to DROID X owners. No it’s not Ice Cream Sandwich, but it will fix a lot of bugs that have been a mainstay ever since Gingerbread landed on the device. We have good news because the soak test has officially begun, which means we could see the full release later this week. As a reminder, this update will bring your software version to 4.5.621.MB810.Verizon.en.US. Hit the break for the full changelog.
Owners of the Motorola Droid X might want to start hitting the ‘check now’ button in the system updates menu as Verizon has just released the change-log for the impending 4.5.621 update.
The OTA update is set to bring a number of bug fixes and systems enhancements to improve on the device’s previous gingerbread update. Highlights include browser improvements, music player stability, improved OTA push as well as the promise of less memory issues and force closes.
It may not be as exciting as an update to ICS however there are certainly some major improvements worth getting your hands on. The update weighs in at 15MB and should only take 5-15 minutes to download.
Check out the change-log as well as a handy guide on how to install in the link below.
source : verizon
Honestly, when I heard about the Droid X2 I was pretty excited because the original was a great phone, that is until the Gingerbread update that was installed but that’s neither here nor there. Well it seemed that the X2 came and went with little luster from what I remember, even though Verizon is still selling them. I believe that this was in part due to the fact that it was really difficult to customize in the beginning and partly due to the fact that Motorola over did it on new handsets in 2011. So the X2 really didn’t see any exciting news in terms of rooting and developing, even after the one-click method was released. However that is no longer the case as XDA forum member dragonzkiller has been able to successfully get CM7.2 working on the handset. It comes with the following features: Read more
Any Droid X owners out there, that like me, are a bit depressed they can’t get a Galaxy Nexus right now? Well, here is something that made my day and should make yours too. Rootzwiki member firstEncounter has whipped up a CM9 based ICS ROM for the Droid X and let me be the first to tell you, it’s FAST and Ice Cream Sandwich tastes great! Be warned though that this is a beta, so do not flash this ROM unless your prepared to deal with some bugs and certain things not working. I also haven’t been running this ROM long enough to express any battery concerns, but this is a great treat to be able to try out ICS on the X and see what everyone is clamoring about for myself. If you need help or more details, be sure to head over to the Rootzwiki thread in the source link for all the details and fixes. Links to download and a list of what currently works and what doesn’t are right after the break.
Researchers at North Carolina State University revealed some major findings regarding Android devices. Using a tool called “Woodpecker” that was developed the researchers, they found noteworthy vulnerabilities on HTC, Samsung and Motorola smartphones. The specific phones studied were the HTC Legend, EVO 4G, and Wildfire S; the Motorola Droid and Droid X; the Samsung Epic 4G; and the Google Nexus One and Nexus S. Woodpecker analyzed the pre-loaded pieces of software on each phone, probing for capacity leaks– sensitive application and operating system privileges left exposed to other applications in ways that would allow them to be accessed by a malicious app without requesting permission from the device user. The researchers were “surprised to find out these stock phone images [on the devices tested] do not properly enforce [Android’s] permission-based security model”.
Basically the capacity leaks fell into two categories, explicit and implicit. Explicit leaks allows applications to exploit a public interface or service of another app without making a permission request. Implicit leaks allows other applications to inherit permissions from another application signed with the same digital certificate (this allows applications from the same developer to automatically interact with each other). They found that while implicit leaks were not as serious a problem, explicit leaks were. Sensitive information such as geo-location, address book, SMS messages, etc.– were leaked on the pre-installed apps. Moreover the researchers found “an untrusted app on these affected phones can manage to wipe out the user data on the phones, send out SMS messages (e.g., to premium numbers), record user conversation, or obtain user geo-locations—all without asking for any permission”. This study is definitely eye-opening, but not surprising as there are examples of some HTC phones and Motorola DROIDs being vulnerable.
So what do you as an Android owner take from this study? First pay close attention to the permissions that each and everyone of your applications of your smartphone or tablet may have. Remember gang, we have a nice little tip sheet for how to spot questionable applications and verify permissions in order to keep your Android protected. Second– Android manufacturers (and even Google) will need to take software security much more seriously. Hopefully the new generation of Android devices will alleviate our fears and concerns for these software holes found in the Android OS.
[via ars technica by North Carolina State University]
The consensus for Motorola’s DROID RAZR has been overwhelmingly positive and as our Editor-in-Chief found out last week during TalkAndroid’s Droid RAZR unboxing and review, to hold this 7.1mm device is to truly appreciate its inherent sex appeal. Now, the Chinese are getting a glimpse at their own RAZR (or XT910, pictured above on the right) CDMA2000 and TD-SCDMA variants. The device’s specs, particularly their 13MP cameras are familiar and beg the question, are we looking at the Dinara we saw back in July of this year and again with that leaked 13 megapixel test photo from September?
First up is the Motorola XT928 (pictured left), with CDMA2000 radio, 13 megapixel camera (up from the RAZR’s 8MP) and Dolby Digital Plus certification. China Telecom confirmed this device as a RAZR variant, but externally, it looks as though it could easily become part of the Droid X series here in the States, with some presuming it may even surface in the US as the Droid X3.
Next is the beefier, rounded MT917 (pictured center to the others) with TD-SCDMA radio. This device packs a larger 4.5-inch (1280×720) LCD screen and thusly adds 1mm of thickness and 11g of weight, though keeps the same 13-megapixel cam.
Official launch dates are presently unavailable, but they are rumored to be released sometime before the end of this year. Hit the break for a few more leaked snap shots.
Last last week, it came to our attention that a new update was ready for the DROID X, and it looks like it is rolling right now. A few of you have written to me letting me know you go the update, but unfortunately it’s not available to me yet. You can check your phone by going to Menu/Settings/About Phone/System Updates to see if you can manually pull it.
This update will bring you to build 4.5.605.MB810.Verizon.en.US, and the only fix is keyboard stability and usability issues. It wasn’t a problem for all, but I know many of you were complaining about it. Please let us know if you were able to get it.
Thanks Greg and Tom
We all know how buggy the original Gingerbread update was for the Droid X. Those issues were slowly fixed with updates, but the one lasting issue was the buggy keyboard. Well Droid X fans, it appears you guys can finally say that all of your Gingerbread problems have been addressed. The latest fix comes in at a whopping 113 MB, but if it works, who’s complaining? The fix will start rolling out on the 19th.
High hopes were had for the Droid Bionic’s successful inclusion in the one-click root we showed you a couple weeks back that easily satisfied the needs of virtually any other Gingerbread-running Motorola device. Alas, no worries, the Bionic has in fact joined the ranks of the Droid X, Droid 3, Droid X2 and others as most had suspected. Here are the instructions for all you hold outs:
1. Make sure you have Motorola drivers installed – Download Drivers
2. Download and unzip MotorolaOneClickRoot.zip file.
3. On your phone go into Settings>Applications>Development > USB Debugging (check box).
4. Plug phone into your computer and select “Charge Only” mode.
5. Navigate to MotorolaOneClickRoot folder and run MotorolaOneClickRoot.exe.
6. Follow instructions in the command window and unlock the phone after each reboot.
Remember: You are rooting at your own risk and don’t forget to hit the break for a link to RootzWiki if you need further support.
Earlier today we reported XDA forum member dirbliss had successfully rooted the Motorola DROID 3. Now, thanks to Framework43, krazykrivda, and psouza4 over at rootzwiki, we have an uber simple one-click root method for stock Gingerbread. I have tested this out on my Droid X running 4.5.602 and everything went flawlessly. As per P3Droid, this method should work on the Droid 3, Droid X, Droid X2, Cliq and Cliq 2. Here’s how it goes down, but proceed at your own risk:
- Motorola drivers need to be installed – 32bit here and 64bit here
- Download and unzip ‘Droid 3 easy root script v7′ to your PC from here
- Turn on USB debugging on your phone by going to Settings > Applications > Development > USB debugging(check box)
- Plug phone into your computer and select “Charge Only” mode from your phone’s notification drop down (pull down your notification bar and tap USB connection to change).
- Navigate to ‘Droid 3 easy root’ folder you unzipped to your PC and run ‘Click to root your Droid 3.bat’
- Now just follow the instructions in the command window and unlock the phone after each reboot
No more SBFing back to Froyo on the Droid X! Thanks to everyone that set this up. Make sure to check the source link below for any updates.
WARNING for Droid X: Previously rooted DX owners who took an OTA update and then lost root should proceed with caution. This seems to only work flawlessly on SBF’d DX’s or fully factory stock ones(read: never been rooted). The problem is with getting Superuser installed because it is already on your phone from when you were rooted previously.