Skip to main content

My first blog from my android tablet

Acre Iconia Tab A500
I picked up my Acer Iconia. A500 tablet from BestBuy yesterday. 24hrs later, the screen looks like its been used for 6 months. It's scary how these things keep you captivated. There are thousands of reviews out there, so I am not going to bore you with another "in-depth" review. Here is short and sweet account of my rendezvous with my new found love interest.



First day retrospective
  • For an android user, this should be a treat, the dual core processor makes the ui and apps snappy. The screen is brilliant but it is glossy, so it was very hard for me to use it on the train to and from work. Maxing out the brightness helps a bit.
  • The battery life is simply out of the world. I did not believe the specs and had carried the charger along. And at the end of the day, It still has about 60% of the juice.
  • I dearly miss the Swype keyboard. Although the large screen has larger keys, I got so used to swype that it feels slow typing old-school way. I am going to have to find an alternative very soon.
  • The mail app is awesome. So is the Gmail app, gtalk app. Skype calling on video is sweet. Turning on my laptop to video chat with mom is no longer necessary.
  • There is no memo app. Really. Not that it's a deal breaker. But I am just saying there is NO MEMO app.

Issues found:
  • The browser crashed at times, when the page had multiple flash ads/content
  • YouTube video links open in browser (unlike as in my Galaxy S,  they open in the YouTube app )
  • Games are slightly slower in compatibility view.
It has been a while I have blogged. With the new tab, hopefully i will be motivated to write again.

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour...

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> ...