View Single Post
  #31840 (permalink)  
Old 05-26-2011, 11:38 AM
kyderr's Avatar
kyderr
Regular 'Geeker
Offline
Location: Rochester, NY
 
Join Date: Dec 2009
Posts: 313
Reputation: 1180
kyderr is halfway to VIP status based on repkyderr is halfway to VIP status based on repkyderr is halfway to VIP status based on repkyderr is halfway to VIP status based on repkyderr is halfway to VIP status based on repkyderr is halfway to VIP status based on repkyderr is halfway to VIP status based on repkyderr is halfway to VIP status based on repkyderr is halfway to VIP status based on rep
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Re: |ROM|¯`·.¸¸.- Energy -.¸¸.·´¯ * |May 14| 21916|29020 * Sense 2021 + flavors

Quote:
Originally Posted by camtah View Post
Check on over at the Google groups. There is a LOT of posts on the IMAP problem that started late last week. Seems that they may have been a "update" or change that is affecting everyone with a WM phone and it still isn't resolved.
It appears to be resolved now.

Best answer - Sarah (Google Employee) Go to this answer
All -

The roll back has completed, and a fix is out for review.

There is a possibility this was the root cause of the WinMo issue. We started advertising support for a new command at connection time (ID) but our response to this command was incorrect. Most clients either don't issue the command, or ignored our response, but it appears that some considered our response broken.

Of those, it appears that some would just wait for the correct response, which would never happen, and eventually the connection would time out after 10 minutes or so. That could easily explain the increased battery requirement, though not really the increased CPU usage.

In any case, I'm considering this thread closed as the main problem is now fixed. We can continue any further discussion of the WinMo issues in the WinMo thread.

Again, sorry for the inconvenience.

Brandon
Reply With Quote
This post has been thanked 3 times.