… and want in on the guild we are trying to form, leave your character name here. Note: comments are set to require approval, so it may take a few days for me to get to them.
Last night when I went to bed I was at 50% battery — this was with two GMail accounts fetching every 15 minutes. I’ve turned NuevaSync back on as a fetch service to test battery life today.
I think something is wonky with push. My yahoo account was set to fetch, but I think the push setting was overriding it . If I’m not alone on this, it might explain why the APIs for push on non-Apple apps was yanked from the latest beta.
Since I don’t need my calender updating constantly, if it saves on battery life fetch is fine.
I’ll report back tommorow.
I’ve been having some procedural issues with managing my calendars. The big problem is, I’m not a big fan of iCal, and entering calendar info on the iPhone is a bit of a pain in the ass because I can’t set the event name and its time all in the same screen. I much prefer Google’s calendar, where I can just click where the event occurs and type in its name.
The problem is, getting the Google Calendar to the iPhone with a minimum of hops. NuevaSync is beta testing a service that will sync your iPhone and Google calendars via push. I signed up for it, and it works great. However, starting late last week I noticed my battery life went to hell in a hand basket. In the “I can’t make it through the work day” bad. Last Friday my battery died around 8pm. Sunday wasn’t much better. Yesterday it died at 5pm. While that sucks, it’s not difficult for me to work around. I can keep it charged at work, and my truck has a charger for it, too. However, next week at Dragon*Con, poor battery life is going to be a big, big problem.
I saw this thread over at Arstechnica, where someone was complaining about poor battery life with push via Exchange. There was a key line in there:
So, I asked one of our IS guys to have a look at our Exchange HTTP logs, and here’s where it gets interesting. My phone was hitting the web server every five seconds. Now, we have about a dozen staff with iPhones, and mine is the only one exhibiting this behaviour.
I began to wonder if I was having a similar issue. For now, I’ve turned off NuevaSync entirely — for the record, I don’t think this problem is on their end, but some wonkiness in the iPhone software. If I can get through the day with amazing battery life I’ll know at least where the problem is.
However, that poses a problem with calendaring. Given my dislike of iCal and iPhone’s calendar, getting my Google calendar to the iPhone is going to take some monkeying around. I tried using the CalDav Google linkup, but I can’t edit the calendar on the iPhone. There’s a few things I’m going to need to test:
- Do more testing and see if it’s just the push technology hosing things up, and set NuevaSync to fetch and not push — right now, push is completely disabled on my iPhone. However, that’s going to end up being a problem when they come out of beta and announce their pricing scheme — it may be too damn expensive.
- Look into a solution like SpanningSync to sync iCal to Google. While I’ve spent $25 on worse things, it’s another process running and another point of failure.
- Look into MobileMe. Given how crappy that’s running, and paying $100/year to just sync my calendars seems a little much.
It’s probably going to be either the first or third options. I just know as soon as I drop the money on SpanningSync, Google is going to announce some sort of push technology.