Uday,
So glad you got ARO working.
Now you have a trace and are looking to understand battery drain.
When I think about battery drain, the biggest culprits on a mobile device are:
1. screen
2. radios (Wi-Fi/cellular/GPS/Bluetooth)
ARO uses a model based on actual data I collected on a phone to collect the power used by your app. On the Best Practices tab, you'll see an entry "Energy Consumed" This tells you the # of Joules your app used.
Your phone's battery will have a Wh and V rating.
Wh*V*3600 = joules in the battery
So for a Samsung S4:
9.88 * 3.8*3600 = 135,158J, or 135 KJ
If your trace used 2,000J that's 1.5% of the battery.
To improve that number:
Reduce the number of connections. the less the radio is on - the more power you'll save. TCP Control bursts are caused by CONNECTION_CLOSE packets. The connections are closed several seconds later - but the radio timers are reset. Close the connections right away.
look at the documentation in the ARO section of this site for more ideas.
Doug