It looks like it's Android season in Alltel country, because four new handsets have just dropped on the regional provider's network. As of right now, Alltel customers can choose between the Motorola Milestone X - most of us know this one as the Droid X, the LG Axis - a low-end phone with a full slide-out QWERTY, the Samsung Gem - a tiny Froyo starter phone, and the HTC Merge - a mid-range Froyo device with a slide-out QWERTY.
The rumors surrounding the Droid X2's hardware have been kind of sporadic, but it looks like we are starting to get a more definite look at what will be packed under the hood of this device. Some benchmarks that have appeared over at Nenamark are basically confirming the presence of a Tegra 2 dual-core processor and a qHD display, the latter via the device's reported resolution of 960x540.
This new information suggests the device is most likely a finished product and that release is upon us, making a launch sometime in May seem even more plausible.
It appears Verizon has altered the terms of its "Certified Like New Program" ("CLNP") (pray they don't alter them further) to be a lot more demanding regarding the condition of exchanged devices.
Namely, if you send in your destroyed DROID, don't expect to get a shiny new replacement without a serious penalty - all phones sent in on warranty exchange must now meet the following requirements:
CLNR Cosmetics Standards
CLNR Cosmetic Standard Summary:
- No blemishes are permitted on front surfaces such as the touch screen, keyboard
- No more than two flaws, which must be less than 5mm in length, are permitted on other surfaces
- No flaws or defects on lens
- No dust, dirt, or fibers under lens
- Ports must be free of foreign material and corrosion, be in operating condition, and have the plugs in place if applicable
This means even if your Android device suffers from a warrantied defect and fails, you may be out of luck trying to get it exchanged if you haven't kept it in tip-top condition.
CyanogenMod 7 has earned its reputation as the most reliable Gingerbread ROM, even though it hasn't yet entered stable mode. And tonight, the fun goes on -
RC4 RC3.14159265358979323846264338327, as the CM team so lovingly refers to it, has just been launched for all supported CM devices.
While RC4 doesn't contain any ground-breaking new features, it does bring a number of bug fixes - for example, hardware acceleration has been added to the Nook Color, and EGL has seen a big fix.
TeamBlackHat has publicly released a leaked official Gingerbread (Android 2.3.3) software update build for the Motorola DROID X. To install the update, you must have the DROID X Bootstrapper by Koush. Instructions and download links below:
What an absolutely insane week it has been for unlocking encrypted and signed hardware!
First, the Thunderbolt, which turned out to be HTC's most closed off device ever, was cracked wide open by team AndIRC within days after release, including our own Justin Case (jcase), Jamezelle, scotty2, and others.
It appears that a major glitch like the recent SMS bug can help spur on support even for an ancient (in Android years at least) phone. The original Motorola Droid will start receiving an OTA update today, sporting several crucial messaging-related bug fixes. Update FRG83G brings the Droid's Froyo version up to 2.2.2.
Released over 16 months ago, the OG Droid has actually been fairly well-maintained by Moto, launching with Android 2.0 'Eclair,' and now running an updated build of Froyo.
In an internal memo leaked from SCK (the Radio Shack subsidiary that sets up wireless kiosks at Sam's Club) it appears that the Droid X2 is on its way very soon, and it may not be much of an upgrade over the original. The note to employees says that kiosks can expect to see the Droid X2 (which showed up at the FCC recently) "this week."
So surely Motorola's sequel is an exciting upgrade over the original, right?
Google continues to be admirably quick to react to DroidDream, the nasty Android Trojan we helped uncover on Tuesday. After removing the offending apps from the Market in just a few minutes of finding out about them, a new post on the Google Mobile Blog reveals that they're now ready to take further steps.
First off, no, we're not trying to be sensationalist. And I'll admit up front that we're a bit light on details at the moment, but we've got a guy who is a professional, seasoned coder, and that's not the type of guy whose opinion you ignore.