Hmm, that's odd. For some reason the peer nodes must be rejecting the transaction, because it's very clearly sending and announcing the transactions multiple times.
What we really need to see now is a log from the other side.
mohawk38, do you have a synced Bitcoin-Qt client? If not, you can find me online at some point (I am TD in #bitcoin-dev and will be around for a few hours now, maybe again tomorrow during the day time Central European time) - then you can connect to my node.
I suspect this line is the smoking gun:
W/System.err( 817): 26823375 [PeerGroup-2-thread-4] WARN com.google.bitcoin.core.Peer - Received alert with invalid signature from peer Peer(bitseed.xf2.org/69.64.34.118:8333): URGENT: upgrade required, see
http://bitcoin.org/dos for details
The alert does
not have an invalid signature, so it indicates a problem I've seen hints of before - some old Android devices appear to have a broken BigInteger implementation that renders ECDSA calculations silently incorrect (!!!!)
If you have such a broken device, you may be simply unable to use any non-server side wallet with it. Even clients like BitcoinSpinner would be unable to operate correctly.
We still need to prove that this is the case. If there's a way to get a copy of the wallet I can check the signature myself, or you could connect to a node I run and I'd check debug.log for a signature verification error when you're around.