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

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.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

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>