This is what you're lamenting the passing of?

that was what I meant.. I know Android is meant to be an always connected phone, but why does it need that connection to be a high speed one to dl say.. e-mail.. I get email notices, and everything on the e71 that I had with Android, and the battery lasts longer on the e71, again, maybe its just me
 
I love that the e71 comes with the internet radio software.. I will listen to it sometimes, not for great lengths mind you, about the same as I would a normal radio..
 
That's because the E71 has a much smaller screen, much smaller number of screen pixels, a much slower processor, and far less RAM by multiples over the Epic.

It's like comparing the gas consumption of a four cylinder car in and a V8 powered car while idling.
 
But your e71 has constant email connection. Android devices, by default most often, have gmail, calendar, gtalk, market service, and many others I won't list, all constantly in push mode, always listening for updates to the network via the data connection. That's my point in all this, the Google services are very powerful, but that is why all android phones have poor battery life.

My tests I did show me how good the android kernel actually is at battery efficiency.

Hell I actually have in addition to all those services, 2 gmail accounts, 2 calendars, and my corp exchange account.

It goes deeper, but this difference is the cause. If I take it out of the picture, my nexus battery matches my symbian 5800 and n97 mini.
 
I know that those connections are in push mode on the android phones, would be nice to have them adjustable. the android kernal is great, no doubts there, just that google (and the cell provider) has to lay their stuff in on top and bloat it, and all. the E71 doesn't seem to have any of that, and still does what I need it to
 
The other thing that kills Android battery life is all the unauthorized data connections that applications do in the background. Most of the highly rated apps in the Android marketplace send information to ad servers without the user's knowledge and without notification in the EULA. Google "taintdroid" some time and you will find out just how much private information is shared. Like I said previously on another thread the complete lack of enforcement of security on Android is the main reason I will stay away from it.
 
Exactly. So many things talk thru the data connection that the user doesn't even know about. If only Google would allow an "offline" mode that keeps data off, and only opens connection when the user initiates something, like opening the web browser. Then we'd get best of everything.

I realize juice defender does something similar to this. But It's not quite the same.
 
Android push services aren't the same as true push services.

A push message to an android handset is very limited. It's something along the lines of "Hey, you've got an email in your gmail account. Go connect and get it". It gets the job done, but a lot of the lifting is still done by the handset.

It's not like RIM's push service, which is something like "You've got an email from xx in your google account. Here's the body. Let me know if you want the attachment".
 
But It's still data activity and that's what kills the battery. And actually the gmail messages are immediately fetched to the device as they come in real time. They are always downloaded in the client if instant I see them come in.
 
No, that's how the Android POP3 services work.



GMail is true push service. But it is a little different from RIM's because it uses sync.

GMail client and GMail services are in sync. They constantly check each other's state. If the client's state differs from the server, the server sends the message until the client's state is the same as the server's once again.

If you choose to delete or archive messages on the GMail client, client and server checks the difference of each other status, and that status will be recreated on the server, so the mirror image is maintained.

If I delete, archive or organize GMail on the desktop, client and server will check on each other's state, and changes will be made on the client to reflect the server's new state.
 
Back
Top