Another thing that I believe Android has built into Lollipop is trying to coalesce app syncs - instead of letting each app sync whenever it feels like it, group them all together to run at once, so you only fire up the CPU and radios once.
I also wonder now how those pagers worked. Seems kinda impractical to listen continuously at those power levels. I wonder if the device polled the tower periodically, or only listened at some interval?
The pager is likely running a very lean embedded processor and doesn't have nearly the same energy requirements.
They do. For example the iPhone 6 Plus lasts 16 days on standby. Remember they also have to listen for other messages (push notifications, local notifications, alarms, calendar events etc.).
Regarding your dumb phone statement they had about the same standby time as the iPhone 6 Plus I mentioned but they had much smaller batteries and the battery technology (I guess) was much less developed.
I find it quite believable. My own phone keeps working for around 20 days without recharging (and that is without Airplane mode - it has constant connection to the cellular network and occasional wifi or 3G connection).
I'm not sure what's going on with it in the iOS world, but Google seems to be working on this with the power management changes in Lollipop. They still have a long way to go, since the first thing I noticed on upgrading to it was random massive battery drain for no apparent reason. It seems to have gone away since I uninstalled Foursquare, but that was a random guess, and I'm still not sure if it was the main reason. Anyways, point is that the OS-level changes to make it easier to sip power are good, but app compliance is still spotty.
I think that what we really need in Android is a good, OS-level way of monitoring which apps are actually causing idle wakelocks, GPS usage, and other non-obvious power drains. If the users can see that App X is what's killing their battery, they will presumably uninstall it and yell at the App developers instead of at Google, or maybe decide that the app does actually need to do that, and it's worth it, but at least they know it's the app's fault, and not Android's. Possibly some sort of option to notify the user if an app's idle power usage is over some threshold and ask them if they're really okay with that.