Archive

Posts Tagged ‘android’

An Update from Motorola on the eFuse

July 16th, 2010 John Mahlman IV View Comments

Holy cow, a third update in two days?!?  Yep!

Today Motorola responded to all of the eFuse nonsense with something that makes the situation a bit better.

Motorola’s primary focus is the security of our end users and protection of their data, while also meeting carrier, partner and legal requirements. The Droid X and a majority of Android consumer devices on the market today have a secured bootloader. In reference specifically to eFuse, the technology is not loaded with the purpose of preventing a consumer device from functioning, but rather ensuring for the user that the device only runs on updated and tested versions of software. If a device attempts to boot with unapproved software, it will go into recovery mode, and can re-boot once approved software is re-installed. Checking for a valid software configuration is a common practice within the industry to protect the user against potential malicious software threats. Motorola has been a long time advocate of open platforms and provides a number of resources to developers to foster the ecosystem including tools and access to devices via MOTODEV at http://developer.motorola.com.

This is very good compared to bricking the phone.  At least the phone can be recovered by the user instead of having to ship it to Motorola for a repair(not sure of the complete details and how warranty would work).  I’m also happy to see that Moto responded so quickly to the public.  However, this still does not sit well with me as Android was developed with developers and tinkering in mind.  If I want to mess around with my device, why can’t I?

(Thanks to Tom for pointing this out for me)

Categories: Hardware, Rant, Software Tags: ,

T-Mobile, Big Red, Samsung, and Moto dump on the Open Handset Alliance

July 16th, 2010 John Mahlman IV View Comments

Let me set the stage up for those who don’t know much background. In 2005, Android, Inc. (a small company in Cali) was acquired by Google. Android, Inc. was a start-up whose business was in developing software for mobile phones. In 2007 Google helped fund the Open handset Alliance (OHA) which is a consortium of several technology companies whose purpose was to develop open standards for mobile devices. Motorola, Samsung, and T-Mobile and among these companies. These companies should all be first in line to make phones more open and free, right?

Well…

Yesterday’s post has already shown us that Motorola should really rework some of their business practices, but it also puts them in a precarious position in the OHA by going against what the OHA is exactly trying to stop, carrier and corporate lockdown of mobile devices. Some even think that because of the eFuse Moto should be asked to leave the OHA, and I’m not entirely sure that they’re wrong in asking this. If they are supposed to abide by the OHA terms, they should. No deviations.

Now for another punch in the OHA/Android face, T-Mobile and Verizon are now installing “junkware” in their new Android phones that cannot be removed in most circumstances. The LA Times blog is reporting that, “the Droid X comes loaded with several nonstandard applications for Google’s Android, most of which cannot be removed” and that T-Mobile’s new Samsung Vibrant is also loaded with some extra apps that cannot be removed. What kind of apps are installed? Here’s a few snips:

Among the [Droid X's] so-called junkware is a Blockbuster video app and a demo for an Electronic Arts game called Need for Speed: Shift….The EA racing game, which provides limited functionality and a large button on the introduction screen urging players to buy the full version, can be removed…

Skype, which is included with other Android handsets Verizon sells, is a permanent fixture, as is a utility called City ID. The latter program provides location information about phone numbers on the incoming call screen. But it works for only 15 days before asking users to pay $1.99 per month…

The T-Mobile Vibrant phone from Samsung, meanwhile, has four of these extra apps staring you in the face.

One is the movie “Avatar,” permanently loaded onto the device…Another is a live video channel called MobiTV — good for only 30 days. The third is a link to install an EA game called The Sims 3: Collector’s Edition. The last is an outdated version of Amazon’s Kindle app.

There’s also Slacker Radio, which cannot be used before providing an e-mail address, and a button leading to Gogo Inflight Internet’s website, which includes a one-month trial for Web surfing (only on plans that provide the service).

Try as you might, none of these apps can be uninstalled.

That is an awful lot of software to load onto a phone that runs an operating system that is supposed to be “free” and “open” for it’s users. The fact that most of them cannot be uninstalled is the most enraging part. I’m also sure that these apps take up a good deal of storage space.

Samsung, Motorola, Verizon, and T-Mobile are completely going against the principles of the OHA which they are all (with the exception of Verizon) a part of. But I’d probably blame the carries more because in the end, they are the one’s with final say on what is loaded on their devices.

So, should all of them be asked to leave the OHA? I’d say that if they continue this trend then yes. The OHA should give them an ultimatum to stop and they should take it or leave. If the OHA fails to even deliver on that then what is the point of the OHA? If you’re not going to stand by one of your most basic principles then you have failed.

While I don’t think this is worse than the eFuse in the Droid X, it certainly is something that needs to be resolved just as rapidly. Putting a few small applications on a phone specific to your company is not really a problem, not allowing your customers to remove them is.

The Droid X and the eFuse: Moto shooting themselves in the foot

July 15th, 2010 John Mahlman IV View Comments

Last year I bought my first smartphone, a Motorola DROID from Verizon. This is my first Moto phone since I got a RAZR many moons ago and swore off Moto forever because of their shitty product. Now, I love my DROID, it does everything I need it to do and more, and I really think Moto got it right with the DROID (I also applaud Big Red for finally making their phones more open). Since the DROID came out Moto has yet to release another kick-ass Android-based phone; the CLIQ is a piece of junk so don’t say that. Verizon has released the DROID Incredible (an HTC device) which is also making the rounds as being an amazing phone, but people were waiting for Moto’s next DROID. The Droid X was to be the next amazing Verizon/Android/Moto Android phone but with its release something has popped up on the tech radar; the eFuse.

According to a source at My Droid World (and Motorola themselves), the Droid X has an eFuse chip installed in the device. The long and short of it is that Motorola has installed this eFuse in the new Droid X which checks the phone for the proper kernel, boot-loader, and ROM and if the proper software is not found it will automatically “trip a fuse” to corrupt the phone’s boot-loader forcing you to get it repaired and will most likely void your warranty. Oh and did I mention that the phone can ONLY be repaired by Motorola, so the Verizon Store won’t help you (well, they’ll ship it to them for you) and you’ll most likely end up pay for a new phone.

Why is Motorola doing this to their phones? According to the Motorola blog:

We understand there is a community of developers interested in going beyond Android application development and experimenting with Android system development and re-flashing phones. For these developers, we highly recommend obtaining either a Google ADP1 developer phone or a Nexus One, both of which are intended for these purposes. At this time, Motorola Android-based handsets are intended for use by consumers and Android application developers, and we have currently chosen not to go into the business of providing fully unlocked developer phones.

Now if I read that correctly, Motorola just told people to buy an HTC device (the Nexus One or a Google ADP1 dev phone) and not their product because their “Android-based handsets are intended for use by consumers and Android application developers.” So, the DROID was a fluke? Well…

When we do deviate from our normal practice, such as we did with the DROID, there is a specific business reason for doing so. We understand this can result in some confusion, and apologize for any frustration.

You’re joking, right? You deviated on the DROID for a “business reason” and now that everyone loves your Android-based phones, you’re going to change it? How stupid does that sound?

First, if you’re going to say you have a reason you could at least tell the people what that reason was even if it’s most likely about money. Secondly, why would you want to change something that has worked already? You know the whole “no fix if no broke” thing? The DROID was probably the best smartphone released last year because of it’s features and it’s openness. Taking one of those key selling points away is really going to piss people off. Also, not only is it frustrating, it’s just a punch right in the face of all the people who praised your phone for it’s openness.

What happens when (like the MyTouch 3g and G1, etc) the developers stop caring about a phone so much that they don’t release a new version of Android for it, when their phones are still capable of running them? Or if Motorola decides not to update the SenseUI on the phone and you’re stuck with whatever they stop with? Well, of course you’re supposed to buy another phone from them, but it probably won’t be a Moto phone if the eFuse is still there. But there are a lot of people want to get all they can from their device (I mean, you did pay $200+ for it!). So they’ll end up going the route of rooting a phone and installing a modded Android install and continue to be happy with your device. Does it change that fact that it’s still a Motorola brand phone? No, it just shows that your hardware still kicks ass 2 years after it was released instead of going to the bottom of the old electronics drawer or whatever.

I realize not everyone cares about modding their phones, hell it’s most likely a larger portion than the people who do care, but the issue is that Motorola is making it okay for a company to brick YOUR phone if they don’t like what you do to it. You know, the phone YOU paid for with YOUR money (which Motorola took of course!). A lot of people buy devices based on how much the company lets you tinker with the device after you buy it.

I’m almost positive that the phone will still be hacked, but this is going to cause a big backlash in the Android community against Motorola (and probably Verizon even though they most likely have nothing to do with it). A lot of Android folk are very pro-open-source and while the software is still “open” the hardware will strike you down if you try to change it.

While I won’t tell people not to buy a Moto phone again I will say that the Droid X will probably be a bad choice if you’re going to alter the base software or if you want the phone to last a long time.