News for hackers. Stuff that matters.
Re:How my iPhone made me miss my first flight of the year by mortenjorck on Saturday January 01, 2011 @03:48PM (#2058384)
Once is a fluke, but twice is a pattern:

http://blogs.wsj.com/digits/2010/11/01/iphone-alarm-bug-wake...

Apple is going to have to restore faith in the clock app like Google needs to restore faith in Android's SMS app.

Re:How my iPhone made me miss my first flight of the year by nosht on Saturday January 01, 2011 @06:48PM (#2058848)
What is wrong with Android's SMS app? I don't want to start another Google VS Apple thread, I honestly haven't noticed anything.
Re:How my iPhone made me miss my first flight of the year by pierrefar on Saturday January 01, 2011 @07:21PM (#2058927)
Re:How my iPhone made me miss my first flight of the year by gaustin on Saturday January 01, 2011 @08:53PM (#2059133)
Interesting. I get mail addressed to people with GMail addresses that are similar to mine (gaustin vs. g.austin). I sometimes wonder if other people get emails addressed to me...
Re:How my iPhone made me miss my first flight of the year by pierrefar on Saturday January 01, 2011 @09:06PM (#2059154)
Don't worry: both these addresses are yours! See the first item in this help page:

http://mail.google.com/support/bin/answer.py?answer=10313...

Re:How my iPhone made me miss my first flight of the year by philwelch on Sunday January 02, 2011 @03:44AM (#2059760)
It could be because G. Austin is a fairly common first initial and last name. I'm [email protected] and every damn P. Welch in the world thinks they have my email address.
Re:How my iPhone made me miss my first flight of the year by commandar on Saturday January 01, 2011 @11:01PM (#2059348)
Not what the OP was complaining about but the big issue I've run into is that large threads bring it to an absolute crawl. Get over a couple of hundred messages in a thread and it gets slow; at around 800 or so it'd take several seconds to load a thread and would cause the phone to hang entirely on occasion. This is on a G2, so it's not like the hardware's underpowered.

The only thing I can figure is that it loads the entire thread into memory when it's opened rather than just displaying what's visible. Fairly annoying either way.