With all 2.03 Roms and even the original Htc Rom Pushmail is working but activesync will be closed after 30 sec - 1 min. Then when you open activesync a new conection to server is made. So when you start active sync 3 times you get 3 http watchdogs. Active syncs works but not as it schould be and does in the older roms. It even has more battery usage and it will take much longer that your emails will arrive. Thats because actice sync is closed by tasmanager i think automaticly and then when the http watchdog goes down active sync is startet again to make a new connection and so on.
Sorry for my poor english.
Hello Sebastian,
like you, I found the disapperance of AS in the taskmanager curious. However AS seems to work just fine if I leave the device in stand-by. My AS-log shows normal heartbeats starting at 480s, going up to 1680s which is the default maximum windows suggested by Microsoft.
If AS were to miss a heartbeat, the heartbeat interval would stay at 480s and not increase in 300s-steps.
I suggest that you put your device on the table for 1-2 hours and then examine the CtrlLog0/CtrlLog1-files in \windows\activesync . The most important value in the log is heartbeat interval.
Fwiw, I use the official 2.03 GER-rom from HTC.
Have fun!
Looking further, I have just reinstalled SKTools on my device and had a look at the running processes. Although the task manager will not show Activesync running, the process repllog.exe (window: ActiveSync) is running in the background, eating up some ram, and seemingly working.
Do you sync over gprs or w-lan?
GPRS - AUTD will not work over WLAN, this is by design. AUTD relies on the network to transmit data even if the device is dormant, and WLAN simply does not receive data in dormant mode.
It does not work as in older roms. Here is my log file. See yourself.
hi!
does anyone have any new informations about this activsync problem?
PUSH mail does not work with spanish 2.03
After migrating from a Trinity to a Diamond, I write to confirm that official spanish 2.03.412.2 ROM has the related bug with Activesync.
Yes, the AS process remains in background, but it does not work as expected.
It opens various stupid simultaneous https connections against the Exchange server, and it closes them after a little of time. Therefore, the heartbeat is never higher than 480 seconds, and the effect is just like a 8-minute PULL mail service, with a lot of battery drain.
I have been testing an account in a Exchange 2003 SP2, and after in a Zarafa & Z-Push linux server (just an Exchange Direct Push emulation), because linux offers me better control to monitor network connections.
A "netstat" offers us that the device drops its https connections after a few minutes. Then the heartbeat is lost.
After this incredible thing, I have just tried an official 1.93.412.1 ROM, and the same account works like a charm, with a perfect heartbeat increment from 480 to 780, 1080 and 1380 seconds.
1.93 is much slower than 2.03, but it really works with PUSH email.
Any success with 2.03?
Does push Gmail require my data connection to be on all the time? If so, how much battery drain does a constant data connection cause?
kgeissler said:
Does push Gmail require my data connection to be on all the time? If so, how much battery drain does a constant data connection cause?
Click to expand...
Click to collapse
no. ur using activesync so u have d choice of setting it to manual sync, or interval or immediate (always on)
if ur using edge, expect 8-9 hours.
3g, 6 hours top.
I’d just like to add my 2 cents in this so that people don’t get turned off by push email…
I happen to connect to an Exchange Server via Active Sync for my email. For 14 hrs a day, it’s set to sync “as items arrive” (i.e. push). During the night, I set the sync schedule to “manual”.
I get a moderate amount of emails each day and I have to say that I’ve not notice a substantial battery drain relative to an IMAP connection that polls every hour.
Push email doesn't require a constant connection as if you're always downloading something. It's more of a "pulse" connection. Try to research a bit into exactly how push email works and you'll see what I mean...
There are two ways to push gmail (or two that I've used recently). One is the new gmail sync, which is an Exchange server. Using that method, I was getting about 8 hours of battery.
The other method is the System Seven beta. I used this for a year+ on my Moto Q before gmail sync became available. I don't know how System Seven works -- it's not Exchange and it's not IMAP. But it works. It seems to be more reliable and quicker than gmail sync, at least for now. It never has gmail sync's problem with passing through attachments. On my TP2, with Seven, I can turn Direct Push off in Comm Manager, and I get more than 24 hours of battery. The only funny glitch with Seven is that on the TF3D home messaging tab, in the little envelope on the screen, instead of showing the beginning of the message, it says, "Click to view message." But that's o.k.; I wouldn't read messages on that screen anyway.
I recently switched back from gmail sync to Seven, and for now it's better. I expect that in a short while, gmail sync will iron out some bugs and become more responsive, and maybe I'll switch back.
One feature that neither of them have, and I'm dying for: The ability to synchronize flags, to mark a message as "Follow up" in Pocket Outlook and have it star the message in gmail. Gmail sync allows the flag, and it will sync with Outlook, but not directly with gmail on the web.
System Seven is here: http://community.seven.com/main.php
It's free and seems likely to remain so...
1) under yr email accounts, choose "as items arrive"
2) turn off data and 3g.if u are on mango. Keep the online chat connected.
3) u will notice that the email settings saying " not up to date" . thats ok and it means all push connections has been turned off .If u want to sync again. Just turn back yr data and 3g again. and yr push accounts will auto sync again
4) yr phone will rest in GSM mode most of the time consuming less power and data connections turned off.
This tip is for those who don't need timely email.
Basically what this does is turn off all connections to email server and data connection to web and act as on demand connectivity. The battery saver in mango only turns off push and msn chat.the connection to web and bytes data flow is still there.its still connected to the web
In case u didn't know when u turn on data , u are actually connected to the internet and there is a constant 2 way flow of bytes like the WiFi card in yr computer. The email app when set to push will check the server . It does not turn off this constant 2 way connection after checking . It only pushes email.
this consumes some power though it's little, over a long standby time , it can eat up a significant battery when u start using the phone phone the battery drains faster .
Magpir said:
1) under yr email accounts, choose "as items arrive"
2) turn off data and 3g.if u are on mango. Keep the online chat connected.
3) u will notice that the email settings saying " not up to date" . If u want to sync again. Just turn back yr data and 3g again. and yr push accounts will auto synnc again
4) yr phone will rest in GSM mode most of the time consuming less power
This tip is for those who don't need timely email.
Basically what this does is turn off all connections to email server and data connection to web and act as on demand connectivity. The battery saver in mango only turns off push and msn chat.the connection to web and bytes data flow is still there.its still connected to the web
In case u didn't know when u turn on data , u are actually connected to the internet and there is a constant 2 way flow of bytes like the WiFi card in yr computer. The email app when set to push will check the server . It does not turn off this constant 2 way connection after checking . It only pushes email.
this consumes some power though it's little, over a long standby time , it can eat up a significant battery when u start using the phone phone the battery drains faster .
Click to expand...
Click to collapse
While the theory behind that is correct, and thanks for the tips, there are a few points which aren't 100% correct I think. I've done extensive battery tests with smartphones that allowed it (WinMo and Android) and I think that the most gain from turning 3G off is when you have a non-optimal reception, as it eats more battery than just gsm only, when connecting/dropping/reconnecting/searching.
WiFi in comparison (always depending on signal quality though) eats more battery while transferring data, per second, but can also transfer more data in that second. On idle, WiFi looks to be less consuming.
But both won't be a huge battery drain on idle. That said, when I'm very very low on battery, I do turn off 3G too.
If you leave 3G on, but don't use it (with the battery saver or settings, and leave the phone idle), depending on your signal quality, the drain won't be major.
The push vs interval email check settings are a bit different in every platform. It all comes down on how good the 'push' implementation is and -again- your signal quality of course. This because -while interval check just opens the connection once every 15/30/60 minutes and then downloads emails if available- the push setting tries to keep the connection to the server pretty much alive, or rather it tries to keep the channel open so that the hotmail server can push the emails when they arrive.
This however is implemented differently on every platform. In google gmail in android it is pure perfection. The connection uses close to zero energy to stay alive and has a drop-retry pattern which is very optimized. You can try other email programs, even for gmail, on the same phone and it will come out using a lot more battery for push. I think that developing the server, push system and the client entitles them to optimizing it hehe.
Anyway, on WP7 there are no available battery drain monitors (you know the ones that log or tell you in real time the mA or mAh used) so one can't be sure. Being a very new operating system, I would tend to think push email drains a bit more than what android, which has been optimized for years, does with gmail.
Regardless of this, the drain of push email vs interval check (pull), occurs mostly if you receive emails very frequently. This because being contacted 20 times in 15 minutes to discharge an email from the server, possibly while not always in optimal signal strength, is more heavy than discharging all the 20 emails at once after 15 minutes.
It seems to me that when you manually or automatically lose the data connection, and then regain it, wp7 fetches automatically emails if the interval of time for the check has passed or, of course, if push email is on. This is quite better than what I experienced on android 2.1 where reobtaining the connection didn't always trigger an email check (withouth push). So I tend to leave push off and keep an interval around 30 minutes on wp7, but of course that depends on anyone's needs.
Lastly, I'm not sure if the push email energy use is affected by the entire push framework of wp7. Since pretty much a lot of the desktop relies on push (live tiles, notifications, etc), maybe the system is already busy mantaining the channel open with a single server, or mantaining multiple push channels open don't affect battery life, and thus push email doesn't really affect the battery because of this. Still, usually on smartphones, when push fails because the connection isn't reliable it falls back in a frequent-pull which can eat your battery pretty fast...
All in all, tips are good, but a second battery is best
my understanding is that the "as items arrives" is there for a reason. its the newer MS direct push technology
I believe a connection is set up. And the the phone operates on true push rather than pull ( time interval).Since its the server which 'pushes' the mail and the client (Phone) doesn't have to struggle to retrieve the mail......the only thing running is data connection ( G or 3G) which is always running anyway,
like many stated, it does not necessarily drain the battery because an open connection is set up, wheareas a time based interval when set to very small intervals like 15 minutes will drain yr battery more than an open connection.
Background:
In the past, before Direct Push Technology, devices were required to connect with the server at specified time intervals or they were triggered by SMS messages to re-sync using ActiveSync. This required a lot of system resources, notably bandwidth (needed to remotely connect the mobile device to the server) and battery life (needed to constantly run these lengthy synching processes). Direct Push Technology saves battery life and bandwidth by maintaining an open Internet connection and only downloading items as they change, instead of executing a lengthy synching process. The open Internet connection may be achieved in a number of ways: through connection to the ActiveSync cradle, through the wireless phone service itself (the device does not even have to be in active mode) or by Wi-Fi (the Wi-Fi connection must be open).
Direct Push depends on network conditions that support a long-standing HTTPS request. If the carrier network for the mobile phone or the firewall doesn't support long-standing HTTPS requests, the HTTPS request is stopped. The following steps describe how Direct Push operates when a mobile phone's carrier network has a time-out value of 13 minutes:
A mobile phone issues an HTTPS request to the server. The request tells the server to notify the device if any items change in any folder that is configured to synchronize in the next 15 minutes. Otherwise, the server should return an HTTP 200 OK message. The mobile phone then stands by.
If the server does not respond after 15 minutes, the mobile phone wakes up and concludes that the connection to the server was timed out by the network. The device reissues the HTTPS request, but this time it uses a heartbeat interval of 8 minutes.
After 8 minutes, the server sends an HTTP 200 OK message. The device then tries to gain a longer connection by issuing a new HTTPS request to the server that has a heartbeat interval of 12 minutes.
After 4 minutes, a new e-mail message is received and the server responds by sending an HTTPS request that tells the device to synchronize. The device synchronizes and reissues the HTTPS request that has a heartbeat of 12 minutes.
After 12 minutes, if there are no new or changed items, the server responds by sending an HTTP 200 OK message. The device wakes up and concludes that network conditions support a heartbeat interval of 12 minutes. The device then tries to gain a longer connection by reissuing an HTTPS request that has a heartbeat interval of 16 minutes.
After 16 minutes, no response is received from the server. The device wakes up and concludes that network conditions cannot support a heartbeat interval of 16 minutes. Because this failure occurred directly after the device tried to increase the heartbeat interval, it concludes that the heartbeat interval has reached its maximum limit. The device then issues an HTTPS request that has a heartbeat interval of 12 minutes because this was the last successful heartbeat interval.
The mobile phone tries to use the longest heartbeat interval the network supports. This extends battery life on the device and reduces how much data is transferred over the network. Mobile carriers can specify a maximum, minimum, and initial heartbeat value in the registry settings for the mobile phone.
You'll save a lot of battery power if you just set it to manual rather than "as item arrives". With this enabled, it will keep an open connection between the phone and the email server, so when you receive an email, it will go straight to your phone. While if you set it on manual it will only use 3G/GSM connection when its needed.
3G Connection No Concern with Batt Life
i have to agree, 3G connection has nothing to do with battery life, unless your area is weak in 3G network, which causes the phone to keep switching between 3G & 2G network.
it is interesting to note, if u keep ur phone in standby, you get longer standby time on 2G/Edge network compared to 3G.
BUT, you get better talk time on 3G network.
Why is this so, i have no idea. forgot where i saw this (it was on one of the brochures of a phone i used to have, either my LG Optimus 7, Blackberry Storm 9500 or Nokia 5800..)
btw, wp7 doesnt have Push Email.. nor iphone, android, symbian. the ONLY smartphone that has this, is RIM's Blackberry. This is done by having RIM's server check your emails constantly and forward to your phone as the email arrives (thus the monthly blackberry internet service / Blackberry Enterprise Service license fee to use their server)
vash_h said:
i have to agree, 3G connection has nothing to do with battery life, unless your area is weak in 3G network, which causes the phone to keep switching between 3G & 2G network.
it is interesting to note, if u keep ur phone in standby, you get longer standby time on 2G/Edge network compared to 3G.
BUT, you get better talk time on 3G network.
Why is this so, i have no idea. forgot where i saw this (it was on one of the brochures of a phone i used to have, either my LG Optimus 7, Blackberry Storm 9500 or Nokia 5800..)
)
Click to expand...
Click to collapse
Done quite a bit of testing and asked stuff to people who -I think- know this stuff. The end result was exactly like that. 3G is very efficient when used, not so much on idle, but that depends vastly on your signal strength. Anyway, yes disabling the data connection helps saving battery, disabling 3G, not so much. That mostly depends on other factors.
vash_h said:
btw, wp7 doesnt have Push Email.. nor iphone, android, symbian. the ONLY smartphone that has this, is RIM's Blackberry. This is done by having RIM's server check your emails constantly and forward to your phone as the email arrives (thus the monthly blackberry internet service / Blackberry Enterprise Service license fee to use their server)
Click to expand...
Click to collapse
I believe we're talking semantics here. Push email, to the best of my knowledge, as a concept is simply a channel (or socket connection) kept open where the mail server can send the email as soon as it has it, instead of waiting for the client to open the connection and pull it (ask for it).
While the classic implementation is BB, Google Gmail push and Hotmail push/Webdav are both push implementation. On the mobile platform push is hard to achieve compared to desktop and that's why it's flexible, it can fall back to frequent pull at times to simulate push. That's true especially when it's not convenient to keep trying having the channel open because the connection comes and goes.
I've spoken for quite a while with an android developer who made one of the most popular gmail alternative clients and he implemented push in it. He said that you have real push there, but you also need to fall back a lot on frequent pull...
Or... you could just use the built in "Battery Saver" feature that is new to Mango...
I **** you not I have gone a whole week on a single charge with my Focus with "Battery Saver" on. Way better than dinking around with toggling your crap on and off all the time. Just set it and forget it.
I have read that hotmail in wp7 uses Microsoft direct push .yes " as items arrive" is direct push. If u choose a time based schedule, its not direct push. its "pull"
For some reason I am seeing better battery life when set to as items arrive .
vash_h said:
btw, wp7 doesnt have Push Email.. nor iphone, android, symbian. the ONLY smartphone that has this, is RIM's Blackberry. This is done by having RIM's server check your emails constantly and forward to your phone as the email arrives (thus the monthly blackberry internet service / Blackberry Enterprise Service license fee to use their server)
Click to expand...
Click to collapse
as of 2010, hotmail was implemented with MS newer direct push technlogy found in exchange.
So u are wrong here.
downloaderintruder said:
You'll save a lot of battery power if you just set it to manual rather than "as item arrives". With this enabled, it will keep an open connection between the phone and the email server, so when you receive an email, it will go straight to your phone. While if you set it on manual it will only use 3G/GSM connection when its needed.
Click to expand...
Click to collapse
some clarification here.."as item arrives" is the true push. manual is pull and is no different than time interval. The difference is that u are doing it manually
obviously, fetch( pull) opens a connection to the server at specific intervals, whether you have anything to fetch or not ...and that means an internal background process /service is running all the time on the phone even though yr data is transfered at intervals. So it does not mean better battery life
push only opens a connection when the server tells it there is something available. the phone is triggered in these intervals .so how does this save battery life?
there shouldn't be a continuous connection needed. The server should simply send a small data packet to the phone ( yr phone data is "sleeping" or timed out) when it has something to deliver ..which should then trigger the phone to go 'fetch' (pull) it.
So in theory if u dont receive a any email on a day, u don't need to set it to time interval pull email as this will initiate processes thus consuming yr battery life.
email if u receive a hundred emails a day every hour , setting it to "as items arrive" will be still be better than hourly time interval .
In wp7 email account settings if u are using hotmail u will see this setting " as items arrive" . This is the true push technology . This is MS new "Direct Push technology" and it saves battery life by not initiating connections everytime the phone is set to check email in time intervals. It maintains an open connection to hotmail . Direct push only works in Hotmail in wp7 and not yahoo, google or other accounts which will use the older iphone style time interval push email.
this is how it works. What they mean by in open connection is through a unique identifier. this does not drains battery...as no data flow is taking place all the time. only yr Data connection is alive as per usual and even when its sleeping or idling, the phone receives info from Hotmail because hotmail knows where to send this info.
its like a pipe connected from A (phone) to B (hotmail) but no water flowing unless there is a need to.When u have a water to flow, B sends out a "trickle" to A to open up and establish contact and the water flows through. all this is through a unique identifier which B uses on the network . in addition the phone ( A) also periodically sends out trickles to B after studying network conditions. So direct push adjusts to any network conditions when sending out email.
As with time based intervals, the phone from A will connect to B and retrieve the water. with B having no part in it or being uncooperative not to waste A;s time even when there is no water..So if u set the wp7 time interval , u not only dont get timely emails but also wastage process as each time the phone will try to establish the connection again . There is no unique identifier involved. if for some reason the phone could not establish a connection , it try again and again in a loop and eventually returns an error, this has been seen with wp7 time based push repeatedly as an error pops out. and the email will not synchronize again at the next time interval and states " attention required". this means push email in the phone stops workig altogether because something at the other side has changed or expereicning problem
Uploaded with ImageShack.us
The problem with push, any push (email, live tile, etc) on mobile, is that your IP address, the technology (wifi or 3g), the infrastructure (firewall, router, etc) and the channel that is used to be reached, can switch quite often, as you lose signal or move from an area to another.
That can cause the phone to use battery in trying to keep the channel to the server alive. Just telling the server 'tell me when there's email' isn't enough. The phone needs to actively try to be reachable from the server, and that can be costly especially in bad reception areas. In your analogy, the problem is that the pipe can be disrupted quite often and needs to be rebuild.
The difference in battery you can see also depends on how many emails you get and how frequently you get them, of course. If you get one email every minute, push will use more battery than pull in any case as the phone will open the connection very often
andycted said:
The problem with push, any push (email, live tile, etc) on mobile, is that your IP address, the technology (wifi or 3g), the infrastructure (firewall, router, etc) and the channel that is used to be reached, can switch quite often, as you lose signal or move from an area to another.
That can cause the phone to use battery in trying to keep the channel to the server alive. Just telling the server 'tell me when there's email' isn't enough. The phone needs to actively try to be reachable from the server, and that can be costly especially in bad reception areas. In your analogy, the problem is that the pipe can be disrupted quite often and needs to be rebuild.
The difference in battery you can see also depends on how many emails you get and how frequently you get them, of course. If you get one email every minute, push will use more battery than pull in any case as the phone will open the connection very often
Click to expand...
Click to collapse
the connections ar eopened only when ther eis something to send
other than that the phone sends out heartbeats...
still no push on my wp7..
ok.. i did what you mentioned.. set my hotmail to 'as item arrives', make sure i have good connection to internet by surfing the net on the phone..
Now, i send an email from my gmail to my hotmail account.. 5 minutes passed still no mail.. (via PC)
i now go to emails (the linked email) and hit on 'sync'.. and there you go.. mail is in..
but that, i believe is pull email..
when i do the same test on blackberry, it prompts me within 30 secs ~ 1 minute after sending..
vash_h said:
ok.. i did what you mentioned.. set my hotmail to 'as item arrives', make sure i have good connection to internet by surfing the net on the phone..
Now, i send an email from my gmail to my hotmail account.. 5 minutes passed still no mail.. (via PC)
i now go to emails (the linked email) and hit on 'sync'.. and there you go.. mail is in..
but that, i believe is pull email..
when i do the same test on blackberry, it prompts me within 30 secs ~ 1 minute after sending..
Click to expand...
Click to collapse
There could be a delay at the gmail .
I just Have 3G off (in my country, it doesn't work with the TmoUS HD7 ) and the email I have synced in my phone is one I created specially for the phone, so I don't have all my friend's emails in Contacts..
Magpir said:
There could be a delay at the gmail .
Click to expand...
Click to collapse
nope, no delays at Gmail.i tried it again w Gmail opened in desktop.mail arrive bt not on phone.
Sent from my LG Optimus 7
I have a BB 9800 and my Mozart on v7712 both having the same Exchange account linked. My 9800 usually receives the email notification on average about 1 second faster than my Mozart. So there isn't really much difference.
vash_h said:
ok.. i did what you mentioned.. set my hotmail to 'as item arrives', make sure i have good connection to internet by surfing the net on the phone..
Now, i send an email from my gmail to my hotmail account.. 5 minutes passed still no mail.. (via PC)
i now go to emails (the linked email) and hit on 'sync'.. and there you go.. mail is in..
but that, i believe is pull email..
when i do the same test on blackberry, it prompts me within 30 secs ~ 1 minute after sending..
Click to expand...
Click to collapse
same for me. unreliable "push" in mango rtm
had to set it to 15min fetch as it was more reliable. although sometimes i open email and it says "last synced 19min ago" wtf?. buggy i guess