Skip to main content

Iphone vs Android switch to new phone experience

I signed up 2 year contact and got new phones today for me and my wife. My wife upgraded her Samsung Infuse to Samsung Galaxy S4 and I upgraded my iphone 3gs to iphone5.  Off course the first thing you want to do is dont have any change in the life and just upgrade the hardware.

Well that is exactly I got from Iphone. Apple really nailed this thing. All I did was went to Icloud and did a backup which was off course incremental so took 2-3 minutes. Then I setup my new iphone as a phone with existing icloud backup. All I needed was to provide my Apple Id 2-3 times during restarts/restore and within 15 min I was up and running and ditched my old phone for good.

Also AT&T activation was a piece of cake never seen someone porting numbers between services within 5 min. Best part is I didn’t needed to interact with any human at all.

Now I needed to repeat it for android and it was mess.  God knows what was wrong but I didn’t found a similar backup/restore on android, there all these 3rd party apps that will do the backup restore but I don’t trust any of them.  So I compromised and said to my wife that I would import your contacts and rest we can just do via usb cable which is mostly photos. And importing contacts is a mess. it seems I or she had turned on syncing new contacts to gmail contacts when they were added or may be I imported it from sim card 2 years back but now the android wants me to save it one by one which is a mess as she had 700+ contacts (many duplicate as her contact list was a mix of facebook + gmail contacts and most of them without phone numbers).

Anyway long story short I had just 1 hour as I was tired so I just synched up my gmail phone contacts on her by adding my gmail account to galaxy S4 in addition to hers, we share 80% of our contacts so would at-least get her going for tomorrow and rest she or I can input manually if needed.

But I got to say just because of this feature I may never go back to Android.

Comments

Popular posts from this blog

Haproxy and tomcat JSESSIONID

One of the biggest problems I have been trying to solve at our startup is to put our tomcat nodes in HA mode. Right now if a customer comes, he lands on to a node and remains there forever. This has two major issues: 1) We have to overprovision each node with ability to handle worse case capacity. 2) If two or three high profile customers lands on to same node then we need to move them manually. 3) We need to cut over new nodes and we already have over 100+ nodes.  Its a pain managing these nodes and I waste lot of my time in chasing node specific issues. I loath when I know I have to chase this env issue. I really hate human intervention as if it were up to me I would just automate thing and just enjoy the fruits of automation and spend quality time on major issues rather than mundane task,call me lazy but thats a good quality. So Finally now I am at a stage where I can put nodes behing HAProxy in QA env. today we were testing the HA config and first problem I immediat...

Adding Jitter to cache layer

Thundering herd is an issue common to webapp that rely on heavy caching where if lots of items expire at the same time due to a server restart or temporal event, then suddenly lots of calls will go to database at same time. This can even bring down the database in extreme cases. I wont go into much detail but the app need to do two things solve this issue. 1) Add consistent hashing to cache layer : This way when a memcache server is added/removed from the pool, entire cache is not invalidated.  We use memcahe from both python and Java layer and I still have to find a consistent caching solution that is portable across both languages. hash_ring and spymemcached both use different points for server so need to read/test more. 2) Add a jitter to cache or randomise the expiry time: We expire long term cache  records every 8 hours after that key was added and short term cache expiry is 2 hours. As our customers usually comes to work in morning and access the cloud file server it ...

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...