Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The BlackBerry does not poll the server to look for updates. It simply waits for the update to arrive and notifies the user when it does.

... keeping an open connection to the server. Its not like the BlackBerry is in standby mode until a magical bit travels through the air to wake it up. Keeping a connection active takes battery too.
 
I don't know about push being a battery conserving feature.

Let's think about this.

Without getting too technical, Push can easily drain your battery if changes/updates are constant and abundant. Imagine receiving Push emails every 5 minutes instead of the usual 15 minutes Fetch (aka Pull). I find it extremely hard to believe Push in this case or others, that it would conserve battery life. Essentially, a lot of us are already on Fetch is doing a semi-push by checking our emails/etc pre its 15 minute timer.

Now, if you don't get too many changes/updates (facebook, email, twitter, etc), which I doubt many of us don't, then Push can preserve battery life and provide us with instant up to the minute stats.

Having a non-user-replaceable battery could potentially be a reason why Apple still doesn't have Push, iono.

Uhm, just to let you know. I do have push email on with my me.com account and also with my exchange server account. I have found no difference in battery life with it on or off. Push as a whole is actually designed to save battery life over the traditional fetch technology that you speak of. It is not that it is made to conserve your battery life when compared to say, doing no checking of emails or status updates at all...I don't know why people keep getting this mixed up.
 
That doesn't sound right. If you read this third-party analysis (below sponsored by RIM), it shows that a BlackBerry keeps a constant "server connection" when waiting for information, too.. Just like an iPhone. The analysis shows that RIM sends the device a UDP packet to initiate a fetch, not a SMS message.

Basically, the assessment shows that RIM is significantly more efficient all-around in how it does push (as compared to Microsoft's Direct Push, which is used by Exchange Servers).

http://na.blackberry.com/eng/ataglance/get_the_facts/Rysavy_Email_Efficiency_Study_2008.pdf


That's how RIM does it too. Deletions are sent to the server the next time the BlackBerry talks to the server (i.e. gets a new email), or after 20 minutes, whichever happens first. It doesn't just waste battery calling out to the server every time you delete something.

Man that PDF sure makes the MS solution appear to be quite wasteful (which is probably why battery life is impacted).
 
It take less than 2-3 secs or sooner for an email I send to my iPhone to notify me it has arrived. That is not fetch! Your battery would not last 30 minutes if it was constantly polling, or even checking every 2 secs.
Other mail services like AOL, etc are fetched.

Push is instant for me too. It's not a glorified fetch. It's not constantly polling a server. I agree with you.
 
This post is getting more ironic as time goes on. :D

Seriously.

He also posted this:

Which could explain the next generation iPhone rumored to be getting more processors.


Steve to Scotty, (of apple iphone engine room):

Steve: GIMME PUSH FACTOR 5!
Scotty: She can't do it sir! She'll break up!
Steve: I don't want excuses I want PUSH FACTOR 5!!!!
Scotty: Then' will 'av to add more processors to the iPhone sir!


..adding more proc or cores for push.... right.......
:rolleyes:
 
The BlackBerry listens for new information and notifies the user when it arrives by vibrating, changing an icon on the screen or turning on a light. The BlackBerry does not poll the server to look for updates. It simply waits for the update to arrive and notifies the user when it does.
I'm glad you're so in love with this model because it's virtually the SAME METHOD that Apple appears to be using for push notifications. You seem to have it stuck in your head that Apple's going to use the same method for pushing app notifications that it's using for pushing email. I've seen nothing that says that. Apple Push Email != Apple Notification Services

See the pretty picture below? See how the Apple Push Notification Service works exactly like a RIM NOC by pushing info to the device that always has a "server connection" (using your terms)?

wwdc-keynote_125.jpg

http://www.engadget.com/2008/06/09/iphone-push-notification-service-for-devs-announced/
 
Push email does not drain the battery. I've tested this.

It does. Just not to the degree that most people complain about.

it's basic battery life laws. if you do more stuff more often (push email for instance) you will drain the battery more.
 
Steve to Scotty, (of apple iphone engine room):

Steve: GIMME PUSH FACTOR 5!
Scotty: She can't do it sir! She'll break up!
Steve: I don't want excuses I want PUSH FACTOR 5!!!!
Scotty: Then' will 'av to add more processors to the iPhone sir!


..adding more proc or cores for push.... right.......
:rolleyes:

hahahahaha! that's great........ hey! seriously! if you know nothing about technology don't post! gosh!
 
Push email does not drain the battery. I've tested this.

Based on the Pdf posted earlier it looks like it could drain the battery less if it used UDP instead of TCP for data transmission. It also looks like it could use some inline compression as well.


it = Microsoft Direct Push. Would figure MobileMe uses TCP as well, but can't comment on compression.
 
Alright boys and girls. Google "conserve iPhone battery life" select the first link. You'll discover that it's a primary source from Apple. It clearly suggests to turn PUSH OFF to improve battery life.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2_1 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5H11 Safari/525.20)

Is this thread about MobileMe Push or Exchange Push or Yahoo Push? The OP does not say. Or does the OP think they all work the same?
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2_1 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5H11 Safari/525.20)

Is this thread about MobileMe Push or Exchange Push or Yahoo Push? The OP does not say. Or does the OP think they all work the same?

seriously, i'm not sure if he even understands what hes talking about, maybe he shouldn't comment anymore
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2_1 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5H11 Safari/525.20)

Is this thread about MobileMe Push or Exchange Push or Yahoo Push? The OP does not say. Or does the OP think they all work the same?

Let's thrown in the differences between B.I.S Email and B.E.S email just for the fun of it.... :D
 
Activesync uses considerably more bandwidth than RIMs push method. You cant dispute the facts.

If you have an OS designed to be multi-threaded, and supply the necessary processing power (which Apple is rumored to be doing) your phone becomes far more efficient and consumes less power. Just because your phone has 4 processors doesnt mean they are capping at 100%... that wouldnt be the point and yes, would be detrimental to your battery life.

Putting it simply... If you have a 1GHZ processor doing all of the work for you and multitasking, its going to consume far more power than say... a phone with 4 processors running at 400hmz each. Why? Simple. It takes less power to run a slower processor!!! With proper load distribution, you would be looking at a very efficient phone. I am not sure what Apple is going to do in this aspect but the possibilities are endless.

They could have a single core processor running your main phone apps with a higher clock speed (media etc), and other cores running at lower speed for processes not requiring too much processing power. So if you loaded up say beejive, SMS, mail etc... (programs that dont require a lot of processing power) they would be shifted to the less power hungry processor. THUS, you use less power.

I got 10 emails today, no phone calls, 6 text messages. Battery already down to 86% because push is enabled. Usually when I leave work, im at around 95-97% battery with push OFF and fetch at 30 mins.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2_1 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5H11 Safari/525.20)

Is this thread about MobileMe Push or Exchange Push or Yahoo Push? The OP does not say. Or does the OP think they all work the same?
The thread is actually about NONE of the above.

It's about the "delayed" background notification services, which Apple has said will use push.
 
It does. Just not to the degree that most people complain about.

it's basic battery life laws. if you do more stuff more often (push email for instance) you will drain the battery more.

When a push email arrives, I don't think it downloads the entire email. It shows the icon badge, the subject field and a few lines of the message, but you'll notice that it's not downloaded until you try to read it. Therefore, I don't think pushing emails use much battery. Even checking every 15 or 30 minutes is still going to make a connection to the server.

Look at it this way. Lets say you get 4 emails in 1 day. That means your iPhone only connected to the server 4 times to tell you that you have email. However, if you have it set to fetch every 30 minutes... the iPhone has to connect to the server 48 times per day. Push seems like a battery saver to me.

Let's thrown in the differences between B.I.S Email and B.E.S email just for the fun of it.... :D

Don't forget the B.S. too!
 
When a push email arrives, I don't think it downloads the entire email. It shows the icon badge, the subject field and a few lines of the message, but you'll notice that it's not downloaded until you try to read it. Therefore, I don't think pushing emails use much battery. Even checking every 15 or 30 minutes is still going to make a connection to the server.

Look at it this way. Lets say you get 4 emails in 1 day. That means your iPhone only connected to the server 4 times to tell you that you have email. However, if you have it set to fetch every 30 minutes... the iPhone has to connect to the server 48 times per day. Push seems like a battery saver to me.

seems correct to me too.
 
I'm not the one that thinks apple needs to throw more cores at it to solve the problem where RIM has done it with their measly little single proc...

:rolleyes:

But maybe you are right, maybe if unicorns had more cores, they would have two horns...

:rolleyes:

TheSpaz:

Actually I left out the possibilities like you mention so you are right. But a lot of people that use push have multiple emails accounts going so they tend to use more. So it depends on a lot of variances.
 
seems correct to me too.

Its completely WRONG. Your phone pings the server (push) every 15 minutes asking to keep its connection alive. Its not asking 4 times per day, it would be asking 4 times PER HOUR.
 
I heard somewhere that Apple decided not to give us full Flash support due to battery life.

But what I don't get is why they don't just give it to us, but as an option. If we really want it despite battery life we can choose to enable it, if not we can disable it. What's the big deal?

I have to agree but knowing what Apple are like I'm sure you would expect this behaviour. Unless it is done properly, they don't want to know about it.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2_1 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5H11 Safari/525.20)

aristobrat said:
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2_1 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5H11 Safari/525.20)

Is this thread about MobileMe Push or Exchange Push or Yahoo Push? The OP does not say. Or does the OP think they all work the same?
The thread is actually about NONE of the above.

It's about the "delayed" background notification services, which Apple has said will use push.

I partly agree. But the OP is saying the reason for the delay is because of the current Push Service. I asked which Push Service is he taking about. Still would like to know.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2_1 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5H11 Safari/525.20)



I partly agree. But the OP is saying the reason for the delay is because of the current Push Service. I asked which Push Service is he taking about. Still would like to know.


Push notification for apps. Its going to be basically the same thing, just a whole lot more traffic.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.