Filed Under (Android, Google, Technology) by Sean on September-12-2010

This is my first in a series of posts having to do with everything Google. From Google Apps to Android, I’m going to publish a series of posts detailing how to accomplish various tasks and workaround various bugs features after trial and error. I hope to evolve this series into something even more substantive, but you have to start somewhere. This post is a quick and easy beginning to help those still running early versions of Android (through Donut, otherwise known as 1.6), plagued by a particularly annoying bug.

Though I haven’t quite completely determined the circumstances under which this bug rears its head, it is evidenced by emails you send out using the GMail application on an Android phone stuck in the Outbox with “Sending . . .” but they never actually send. If it was a newly composed email, the solution was rather simple in that all you had to do was display the email, edit it and click the Send button again. Things are a little trickier with emails that are replying to a thread, however.

Rather than bore you with all the various things that didn’t work, allow me to jump straight to the punchline. Should you see such a message as a reply to an existing thread stuck in your outbox, here’s what you do: first, open up the offending thread. This can be either from the Outbox or whatever folder label the thread is under. Then, reply to one of the emails in the thread. It can be any email besides the Sending . . . email itself (you can’t open that one anyway). After you click Reply and you see the Compose Mail screen, click the Save as draft button. Then, go back to the Inbox by whatever means you choose (e.g., back button). Then, bring up the Drafts folder by selecting the Menu key and choosing View Labels and choosing Drafts. Open up the email thread you were just working on. You’ll note that at this point you’re actually editing the content of the original email that was stuck in the Outbox! Edit it as you see fit and click Send. Voila! If it gets stuck in the Outbox again, you can repeat this process as often as you like. In some extreme cases where you have to go perform this process via more than one iteration, you may have some stale empty Draft emails in the thread you can discard at a later time.

Look for my next Google post on how to share your GMail or Google Apps Calendar so the person with whom you’re sharing has complete administrative privileges over it.

Filed Under (Geekstuff, Internet, Social Media, Technology) by Sean on December-21-2008

I wanted to post this brief update about a new feature I discovered recently by accident while testing Twitter clients for my Android-based G1 smart phone. “@Replies” on Twitter now picks up tweets that are addressed to multiple people in a chain. These replies also appear to follow the same rules I pointed out in my previous post about Twitter in how @Replies work (alas it still appears most people don’t understand these important points, however). For example, if you send a tweet as follows: “@bob @jane @jim @jesus @mary @joseph have a good holiday,” then each and every person in that chain of addressees will have the tweet appear on their @Replies page! Note, however, if you interrupt the chain in any way, it breaks this behavior, e.g., “@bob @jane and @jim are you coming to my party,” @jim in this case will not get the tweet on his @Replies page. As noted, the rules from my previous post apply. In my first example, even if @mary doesn’t follow the person who sent the tweet, she will still get it in her @Replies tab nevertheless. Clients that use the Twitter API to track @Replies also follow these rules, as I found my accident when testing nanoTweeter for my G1.