Skip to main content

Why Acer a500 ICS update's distribution strategy is a failure

Acer released the Android Ice Cream Sandwich (ICS, aka 4.0) update on Apr 27th 2012, for its A50x line of tablets. The owners were ecstatic about the news. Nevertheless, the process of deployment for Acer and the installation for the end-users was nothing short of a disastrous saga.

For a couple of days, users saw one of four cases.
  1. Downloads not start at all - while the update app claiming "Network coverage is currently poor: Please move to a better location with better network coverage to continue." (which is appalling for users sitting right next to their routers)
  2. Downloads started but not finish (the progress bar waited, as if eternally, until the download window finally disappeared).
  3. Downloads finished 100% but not kick off update installer (this and the next one is probably the most heart-breaking).
  4. Update installer failing claiming "Invalid update file"

A lucky few could get the whole thing complete without breaking. However, it wasn't the case for the majority of the users.

The failure of this distribution strategy could be summarised into one major point. The release payload was centrally distributed and was made available only though the update app. This means, the ~400MB download must be served to each user (and the repeat requests due to failed attempts) by Acer's own servers. Add to that the "primitive" update application handle the download process. For what ever reason, this doesnot sound rational. Even though there may be geographically load balanced CDNs, The fact that the download process is interwoven with update program itself is beckoning Murphy's law.

Presumably, the user reaction's were ranging from dissappointment to wide spread despise. As with any update release, Acer should have planned better. Torrent distributions, and http downloads are much more standard. They could have made an encrypted file available for download sans the controlled delivery mechanism. The upload tool could decrypt the user downloaded file, and install it. May be in future, Acer will not repeat this mistake. Well atleast it released updates pronto, unlike some other industry leaders (read Samsung)

update: I went through all four cases above and finally got ICS on my Tablet. Thank you Acer! and take my advice distribute your updates in the "open" way, in future.

Popular posts from this blog

One page Stock

Alright.. That was a long absence. The whole last week I dint blog. I dint go away. I was "occupied". I was learning stock trading. Its very fascinating. I have a good weeeked blog for you all. Here is my experience. I can literally hyper-link every word from the following paragraphs, but I am writing it as simple as I can so you can look up the italicised words in wikipedia . I got a paper trading account from a brokerage firm . You need one brokerage account first. Then it can be an Equity account where all your money is yours or a Margin account , where some of the money is lent by the brokerage firm. Then I get Buying power , which is the dollor value of how much stocks you can buy. I can make profit by simple rules. Buy when Price is low. Sell when price is high. There is another more intersting way of earning money. Selling short . Thats when price is not high, per say, but when are confident that the price WILL go down. then buy back when its lowest. This is what

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>