You probably remember Apple's campaign with the apps from the App Store, yes, that one with "That's an App for that". Motorola, taking the example of Apple, makes fun of its obstinacy for denying flash on its iDevices, starting its own campaign, named "Flash Websites? There's a phone for that". The phone which is advantaged by the campaign is, of course, Motorola's Droid 2, which has recently been launched.
This is nothing more than a hit in Apple's face, which has been aggressively attacked from all directions with the Antennagate madness, which, paradoxically, has drastically increased the request for the iPhone 4. The original Droid was sold quite good, so, considering this, I'm expecting for the Droid 2 to be a successful device. And this will, definitely, increase the market-share of Android, which, according to some recent studies, has overpassed Apple's iOS market share in the US.
Showing posts with label motorola. Show all posts
Showing posts with label motorola. Show all posts
Sunday, September 5, 2010
Saturday, July 17, 2010
Motorola Droid X doesn't really breaks if you install a custom firmware on it.
There were lots of discussions about the recently-launched Droid X, and why it seems to get broken when trying to install a custom firmware on it. Motorola came up with an declaration, claiming that these who tried custom firmwares on their phones didn't actually break them, their phones just went in recovery mode by themselves.
What creates the "problem" is eFuse, which is an system designed by Motorola to verify the bootloader which runs on their phone. More exactly, if eFuse detects unapproved software, it will automatically enter the phone in recovery mode. When the user tries to boot with an official firmware, eFuse detects that as an approved software, and lets the phone boot normally.
This is really interesting, I am sure that there will be soon methods of avoiding eFuse (or making it think that custom firmwares are actually approved software).
What creates the "problem" is eFuse, which is an system designed by Motorola to verify the bootloader which runs on their phone. More exactly, if eFuse detects unapproved software, it will automatically enter the phone in recovery mode. When the user tries to boot with an official firmware, eFuse detects that as an approved software, and lets the phone boot normally.
This is really interesting, I am sure that there will be soon methods of avoiding eFuse (or making it think that custom firmwares are actually approved software).
Subscribe to:
Posts (Atom)
