MfE 2.0.0 has fixed heartbeat, while 2.3.0 and later have dynamic heartbeat. MfE 2.3.0 and alter tries to get the longest heartbeat possible in your environment. FYI, heartbeat only matters for Always on.
When you tell me that your heartbeat is only 1 minute, it tells me that you are not using the best AP for your network. Maybe because you have not paid enough or maybe there are multiple ones your provider allows. Try another one. Here in the US, I use AT&T and get 30 minutes, which is great.
Your battery life is being severely impacted because the phone is constantly being disconnected and then using lots of power to reconnect. This is with 2.3.0.
Anyone using Always on with heartbeat less than about 8-10 is suffering from this problem. Use the right access point, or switch to interval sync (hourly or whatever). With some carrier's access point settings you can simply remove the proxy settings under AP 'Advanced' settings. Other time this will not work at all. Make a copy of your AP before trying this.
MfE 2.0.0 is trying 15 minute heartbeat, and I assume failing (but not giving an error message). In a few minutes it tries again. Maybe this allows better battery life, but you are not really Always on. You may be disconnected most of the time. I forget the exact behavior of 2.0.0 now that it's been a while.
If you pay attention to the MfE application (where you configure your settings), you may see this.
Your AP is configured to drop you after 1 minute because it thinks your connection is inactive. However Activesync requires connections with no activity to maintain Always on.
Here is a link about Windows Mobile implementation of this feature. Nokia has implemented the same mechanism.
http://technet.microsoft.com/en-us/library/aa997252.aspxThere might also be more information about this in the MfE Troubleshooting Guide.