Next Steps and Testers wanted

[secp256k1]

Testing just uploaded: bitcoin-wallet-2.39_bitcoinj0.7_spendpolicies-test.apk

'Trusted Peer' set to: riker.plan99.net
'Skip Regular Peer discovery': set

The 'Peer Monitor' shows 'No peers connected'. Is riker.plan99.net alive?

Will install http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.0/test/ and try connect to it.

riker.plan99.net is only serving prodnet, not testnet. Sorry, I forgot to mention this.

However, on testnet its quite easy to connect to a 0.8 node. Just have a look at the peer monitor and see which peer its downloading from (printed in bold). Of course, its always good to connect to your own peer, for debugging purposes.

Running my own node on testnet.
Peer monitor shows it is connected.

I always get 'wallet isn't responding' OS message and need to close the app as soon as enter Peer Monitor Activity.

LogCat shows:

W/System.err(23852): 290979 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - Difficulty transition traversal took 39msec
W/System.err(23852): 291369 [Wallet auto save thread] INFO com.google.bitcoin.co
re.Wallet - Auto-saving wallet, last seen block is 00000000005675aa4a61b4f66248b
2eed522d697e82eff2e38a90d6434f7e5b0
W/System.err(23852): 291424 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - 50 blocks per second
W/System.err(23852): 292395 [Wallet auto save thread] INFO com.google.bitcoin.co
re.Wallet - Auto-saving wallet, last seen block is 000000002c5e306733b2a26847693
b100ef375ce47eacd93a6379ea99089ea30
W/System.err(23852): 293438 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - 27 blocks per second
W/System.err(23852): 294436 [Wallet auto save thread] INFO com.google.bitcoin.co
re.Wallet - Auto-saving wallet, last seen block is 00000000008f45ecaa1806b3ca8ef
defff8242ede3a5bfd2fa8656933489f272
W/System.err(23852): 294465 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - 23 blocks per second
W/System.err(23852): 295463 [Wallet auto save thread] INFO com.google.bitcoin.co
re.Wallet - Auto-saving wallet, last seen block is 000000000004d0a3b85431492bbce
f69284d617efb3812fe61ffcca4191c295c
W/System.err(23852): 295491 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - 54 blocks per second
W/System.err(23852): 296491 [Wallet auto save thread] INFO com.google.bitcoin.co
re.Wallet - Auto-saving wallet, last seen block is 0000000000f50172ca238e36bc4d9
2f66d640feaeb0d7f6e5a460896c7ae3900
W/System.err(23852): 296916 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - 3 blocks per second
W/System.err(23852): 297789 [Wallet auto save thread] INFO com.google.bitcoin.co
re.Wallet - Auto-saving wallet, last seen block is 00000000002704402ff14fb06f338
2a9c5be5a45d42a4f14e5a94a868aa6a4a7
W/System.err(23852): 297978 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - 15 blocks per second
W/System.err(23852): 298835 [Wallet auto save thread] INFO com.google.bitcoin.co
re.Wallet - Auto-saving wallet, last seen block is 00000000001f6cda2111f0ad8897e
5d52695771fa0458591da077325e20e60c0
W/System.err(23852): 298981 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - 53 blocks per second
W/System.err(23852): 299863 [Wallet auto save thread] INFO com.google.bitcoin.co
re.Wallet - Auto-saving wallet, last seen block is 00000000007a13c5d39841f3571ef
1bc3bd924557c1994686f34283603feec85
W/System.err(23852): 300614 [New I/O client worker #1-1] INFO com.google.bitcoin
.core.AbstractBlockChain - 8 blocks per second

[1713571025]

1713571025

[1713571025]

1713571025

[1713571025]

1713571025

[Andreas Schildbach]

Running my own node on testnet.
Peer monitor shows it is connected.

I always get 'wallet isn't responding' OS message and need to close the app as soon as enter Peer Monitor Activity.

You're probably running into

http://code.google.com/p/bitcoin-wallet/issues/detail?id=134
https://code.google.com/p/bitcoinj/issues/detail?id=310

Can you run a

adb pull /data/anr/traces.txt

just after the ANR message appears and attach it to the Bitcoin Wallet ticket? I will confirm if its the same problem.

[secp256k1]

Running my own node on testnet.
Peer monitor shows it is connected.

I always get 'wallet isn't responding' OS message and need to close the app as soon as enter Peer Monitor Activity.

You're probably running into

http://code.google.com/p/bitcoin-wallet/issues/detail?id=134
https://code.google.com/p/bitcoinj/issues/detail?id=310

Can you run a

adb pull /data/anr/traces.txt

just after the ANR message appears and attach it to the Bitcoin Wallet ticket? I will confirm if its the same problem.

Traces submitted, see Issue 136.

Yes, it looks like the problem you mentioned.

[Mike Hearn]

The workaround for now is to not open the peer monitor until block chain sync has finished.

[Andreas Schildbach]

I have updated the previews with the latest code from bitcoinj and Bitcoin Wallet:

http://code.google.com/p/bitcoin-wallet/downloads/list

There is a lot of small changes and optimizations, and the peer monitor lockup should also be fixed.