search

ManojNimbalkar / bitcoin-wallet

Automatically exported from code.google.com/p/bitcoin-wallet
0 stars 0 forks source link

blockchain not updating #21

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
I sent 0.01btc to bitcoin-wallet to confirm it accepted money, it received it 
and confirmed it after receiving 6 confirmations from a blockchain update. I 
then sent 5btc to bitcoin-wallet. Again received and confirmed, but this time I 
forwarded the total amount to my secure wallet where it was received and 
confirmed by both bitcoin-wallet and my secure wallet.

Now I have transferred another amount to bitcoin-wallet, which it accepted and 
confirmed and forwarded 0.01btc to my secure wallet. This transfer is not being 
confirmed by bitcoin-wallet (but it is confirmed in my secure wallet) so I 
believe the blockchain is not updating. Last update shows at midday today.

This means I can't move the rest of the funds off the phone as it is waiting 
for confirmation of my new balance.

I have tried restarting bitcoin-wallet and the phone, but it does not update. I 
also have 6 connections to other users.

What version of the product are you using? On what operating system?
Most recent version available from the android market on a Samsung Galaxy S II 
running android 2.3.3 gingerbread

Original issue reported on code.google.com by mickleov...@gmail.com on 19 Jul 2011 at 5:31

GoogleCodeExporter commented 9 years ago 
Can explicitely state the version of Bitcoin Wallet? Can you try with 1.14?

Original comment by andreas....@gmail.com on 19 Jul 2011 at 6:15

GoogleCodeExporter commented 9 years ago 
I've just noticed the update on the market.

Will this wipe my wallet.dat file?

Thank you for the rapid response

Original comment by mickleov...@gmail.com on 19 Jul 2011 at 6:26

GoogleCodeExporter commented 9 years ago 
I have updated to 1.14, wallet still intact.

Peer connections are forming but bitcoin blockchain sync is stuck at 0.0% 
finished.

Original comment by mickleov...@gmail.com on 19 Jul 2011 at 6:30

GoogleCodeExporter commented 9 years ago 
v1.14 has a trusted peer mode. Can you try the following:

- make sure your Android device and your PC are in the same physical network 
(WLAN).
- put the IP of your PC in Bitcoin Wallet -> Options Menu -> About -> Trusted 
peer (scroll down)
- exit Bitcoin Wallet
- start the Satoshi client on your PC (make sure it is on top of the block 
chain)
- start Bitcoin Wallet

If it doesn't update, I'll need a "adb logcat", so I can see what's happening.

Original comment by andreas....@gmail.com on 19 Jul 2011 at 7:03

GoogleCodeExporter commented 9 years ago 
Hi andreas,

The issue seems to have rectified itself overnight. I disabled wireless,
removed my trusted peer and cleared the blockchain.

The update was slow but complete. Could my wireless router be interfering
with the blockchain update but still allowing peer connection?

Thank you for your help.

Mickleovertech

Original comment by mickleov...@gmail.com on 20 Jul 2011 at 8:59

GoogleCodeExporter commented 9 years ago 
Hello,

I had a similiar problem, the blockchain update always stopped
and the icon was gone. But the blockchain wasn't complete, had
to kill the app with a taskkiller and restart it a gazillion times
until the blockchain download was complete.

Also the app could really need a exit button and a blockcounter.
Apart from that I am impressed, really cool stuff.

Original comment by hotchil...@googlemail.com on 27 Jul 2011 at 1:06

GoogleCodeExporter commented 9 years ago 
Exact same issue and resolution. It does keep happening occasionally..

If you need me to run any kind of debug on the software please get in 
touch and I'll send you whatever might help the situation.

Cheers for the app.

Original comment by mickleov...@gmail.com on 27 Jul 2011 at 1:09

GoogleCodeExporter commented 9 years ago 
Some update on this issue: Beginning with Version 1.20 (just released to 
Android Market), handling of peers was moved from the app into the framework 
and was completely rewritten. This probably renders all bugs related to 
blockchain download invalid, and opens several new ones.

One known issue with the new handling is that sometimes the download progress 
notification icon (sync icon) isn't cleared. This does *not* mean there is 
still some process trying to download, consuming battery or memory. It just 
"forgets" the icon, that's all. The icon should disappear if you exit the main 
screen by pressing the back button (NOT the home button), because this closes 
the app and removes any remaining allocated resources.

If your download does not progress for some minutes, that's also normal, 
because Bitcoin Wallet tries to connect block chains or re-organizes the block 
chain. This is quite some work that can take up to two minutes without visible 
progress. Be patient. It is also possible that a peer is just responding very 
slowly.

One last known issue, the app currently does not handle unreliable or 
non-existent internet connectivity well. Don't expect the blockchain download 
to succeed while you are carrying your through elevators, subways, high-speed 
trains and the like. If you have stable WLAN again, it is best to exit the app 
(remember, BACK not home button) wait until the sync icon disappears then 
restart. I will work on getting this reliable as soon as possible.

Feel free to add to this report if you find something not covered in this 
comment, but please make sure you've tested on Version 1.20 or later.

Original comment by andreas....@gmail.com on 27 Jul 2011 at 9:13

GoogleCodeExporter commented 9 years ago 
I started using version 1.29 a few days ago, and eventually successfully got a 
partial confirmation of one payment to its address.  But since then it hasn't 
seemed to download any blocks (no "sync" indicator), though it typically has 
several connections, so the confirmation of that one hasn't completed (nothing 
to spend yet), and another payment I made to it hasn't arrived.  I've left it 
running for hours with no more progress.

I've never force-closed it or anything, even though it also tends to get stuck 
in sub-windows.  E.g. if I start to donate, or if I read the safety notes, it 
will keep coming back to that page when I quit it (with "back") and then 
re-open it from the android home screen.  If I hit "back", the app goes away 
rather than bringing me back to the main page.  But after waiting and/or 
running lots of other apps it eventually will start up on the main page.

I just upgraded to 1.31 and still no new blocks or syncing.  I generally have 
good connectivity.

I haven't tried the trusted peer approach yet.

When should we try the "about"/"reset blockchain/transaction" fix ("only when 
being instructed")?

Is there a way to see what block it is on?

Thanks.

Original comment by neal...@gmail.com on 21 Aug 2011 at 3:59

GoogleCodeExporter commented 9 years ago 
Ahh - the comment on getting debug help via adb logcat in the README was very 
helpful!
 http://code.google.com/p/bitcoin-wallet/source/browse/trunk/README

It led to this string of messages which were repeated every few minutes, and 
which should help diagnose the issue.  It repeatedly tries to load Block 139105 
and several subsequent ones and concludes that they don't connect.  For some 
reason the peer gets disconnected, and there is also a note about "Difficulty 
transition point but we did not find a way back to the genesis block."

   1869:2011-20-20T22:39:30 W/System.err( 2657): 3882838 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 000000000000047e4a871d7711bad87b8a331767f7222866fcf100f2f0f740c1
   1870:2011-20-20T22:39:30 W/System.err( 2657): 3882838 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(000000000000047e4a871d7711bad87b8a331767f7222866fcf100f2f0f740c1)
   1871:2011-20-20T22:39:31 W/System.err( 2657): 3882888 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 00000000000004d1532ef2cf1b078eb510861713fc03bab96fbdb651e1487c7b
   1872:2011-20-20T22:39:31 W/System.err( 2657): 3882888 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(00000000000004d1532ef2cf1b078eb510861713fc03bab96fbdb651e1487c7b)
   1873:2011-20-20T22:39:31 W/System.err( 2657): 3882936 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 00000000000004ab2808dc3c0d65a5f653311b8c432bf306c3ce4dbcf5cb9786
   1874:2011-20-20T22:39:31 W/System.err( 2657): 3882951 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(00000000000004ab2808dc3c0d65a5f653311b8c432bf306c3ce4dbcf5cb9786)
   1876:2011-20-20T22:39:31 W/System.err( 2657): 3883000 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 000000000000023879d63b11b833c176691c31996cf01469acc7918ad03509e6
   1877:2011-20-20T22:39:31 W/System.err( 2657): 3883000 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(000000000000023879d63b11b833c176691c31996cf01469acc7918ad03509e6)
   1878:2011-20-20T22:39:31 W/System.err( 2657): 3883011 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 00000000000000d2a9bbc133b1c9dfb0e075d0f5f1d98794d4126ed07e4d5bfe
   1879:2011-20-20T22:39:31 W/System.err( 2657): 3883012 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(00000000000000d2a9bbc133b1c9dfb0e075d0f5f1d98794d4126ed07e4d5bfe)
   1880:2011-20-20T22:39:31 W/System.err( 2657): 3883024 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 0000000000000441a7516eed0348baf0b3f8855ba4bfeb8adae593a174ac3dd6
   1881:2011-20-20T22:39:31 W/System.err( 2657): 3883025 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(0000000000000441a7516eed0348baf0b3f8855ba4bfeb8adae593a174ac3dd6)
   1882:2011-20-20T22:39:31 W/System.err( 2657): 3883041 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 000000000000075d43e9af8e59cb0d8a945620e60eab34cb337e0582c9c2cd53
   1883:2011-20-20T22:39:31 W/System.err( 2657): 3883041 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(000000000000075d43e9af8e59cb0d8a945620e60eab34cb337e0582c9c2cd53)
   1884:2011-20-20T22:39:31 W/System.err( 2657): 3883056 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 00000000000002d3e564d1e4ed87dfb18cb95c552c9f4ff1997ccdf8c34e7db9
   1885:2011-20-20T22:39:31 W/System.err( 2657): 3883057 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(00000000000002d3e564d1e4ed87dfb18cb95c552c9f4ff1997ccdf8c34e7db9)
   2083:2011-20-20T22:40:25 W/System.err( 2657): 3937681 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 000000000000000aeac173d93b0cce953be5e8266e1a61f997bc2a935b3b44d4
   2084:2011-20-20T22:40:25 W/System.err( 2657): 3937682 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(000000000000000aeac173d93b0cce953be5e8266e1a61f997bc2a935b3b44d4)
   2085:2011-20-20T22:40:25 W/System.err( 2657): 3937688 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.BlockChain - 0 blocks per second
   2325:2011-20-20T22:41:22 W/System.err( 2657): 3994033 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 000000000000053ce57e75c5c78eb675a58936ebc06e6fb9f70bdab6be1c9fd8
   2326:2011-20-20T22:41:22 W/System.err( 2657): 3994034 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(000000000000053ce57e75c5c78eb675a58936ebc06e6fb9f70bdab6be1c9fd8)
   2327:2011-20-20T22:41:22 W/System.err( 2657): 3994054 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.BlockChain - 0 blocks per second
   2551:2011-20-20T22:42:17 W/System.err( 2657): 4049802 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 00000000000000b0f11852ad2d0f77505f668daa7e237b66543e080a22ec651e
   2552:2011-20-20T22:42:17 W/System.err( 2657): 4049802 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(00000000000000b0f11852ad2d0f77505f668daa7e237b66543e080a22ec651e)
   2553:2011-20-20T22:42:17 W/System.err( 2657): 4049809 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.BlockChain - 0 blocks per second
   2720:2011-20-20T22:43:12 W/System.err( 2657): 4104676 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.BlockChain - Block does not connect: 000000000000035537a7e83be91aeb326ae4b7c799d5430a413d468049c75043
   2721:2011-20-20T22:43:12 W/System.err( 2657): 4104677 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(000000000000035537a7e83be91aeb326ae4b7c799d5430a413d468049c75043)
   2722:2011-20-20T22:43:12 W/System.err( 2657): 4104678 [PeerGroup-2-thread-1] ERROR com.google.bitcoin.core.PeerGroup - error while talking to peer
   2723:2011-20-20T22:43:12 W/System.err( 2657): com.google.bitcoin.core.PeerException: java.net.SocketException: Connection reset by peer
   2724:2011-20-20T22:43:12 W/System.err( 2657):    at com.google.bitcoin.core.Peer.run(Peer.java:153)
   2725:2011-20-20T22:43:12 W/System.err( 2657):    at com.google.bitcoin.core.PeerGroup$PeerExecutionRunnable$1.run(PeerGroup.java:248)
   2734:2011-20-20T22:43:12 W/System.err( 2657):    at com.google.bitcoin.core.BitcoinSerializer.serialize(BitcoinSerializer.java:111)
   2735:2011-20-20T22:43:12 W/System.err( 2657):    at com.google.bitcoin.core.NetworkConnection.writeMessage(NetworkConnection.java:165)
   2736:2011-20-20T22:43:12 W/System.err( 2657):    at com.google.bitcoin.core.Peer.blockChainDownload(Peer.java:378)
   2737:2011-20-20T22:43:12 W/System.err( 2657):    at com.google.bitcoin.core.Peer.processBlock(Peer.java:207)
   2738:2011-20-20T22:43:12 W/System.err( 2657):    at com.google.bitcoin.core.Peer.run(Peer.java:135)
   2743:2011-20-20T22:43:12 W/System.err( 2657): 4104697 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.PeerGroup - connecting to Peer(192.168.1.104/192.168.1.104:8333)
   2749:2011-20-20T22:43:13 W/System.err( 2657): 4105218 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.NetworkConnection - Connected to peer: version=32300, subVer='', services=0x1, time=Sat Aug 20 22:38:44 MDT 2011, blocks=141854
   2751:2011-20-20T22:43:13 W/System.err( 2657): 4105221 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.Peer - blockChainDownload(0000000000000000000000000000000000000000000000000000000000000000)
   2753:2011-20-20T22:43:13 W/System.err( 2657): 4105278 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.PeerGroup - running Peer(192.168.1.104/192.168.1.104:8333)
   2754:2011-20-20T22:43:13 W/System.err( 2657): 4105496 [PeerGroup-2-thread-1] INFO com.google.bitcoin.core.BlockChain - 0 blocks per second
   2755:2011-20-20T22:43:13 W/System.err( 2657): 4105501 [PeerGroup-2-thread-1] WARN com.google.bitcoin.core.Peer - Block verification failed
   2756:2011-20-20T22:43:13 W/System.err( 2657): com.google.bitcoin.core.VerificationException: Difficulty transition point but we did not find a way back to the genesis block.
   2757:2011-20-20T22:43:13 W/System.err( 2657):    at com.google.bitcoin.core.BlockChain.checkDifficultyTransitions(BlockChain.java:385)
   2758:2011-20-20T22:43:13 W/System.err( 2657):    at com.google.bitcoin.core.BlockChain.add(BlockChain.java:189)
   2759:2011-20-20T22:43:13 W/System.err( 2657):    at com.google.bitcoin.core.BlockChain.add(BlockChain.java:124)
   2760:2011-20-20T22:43:13 W/System.err( 2657):    at com.google.bitcoin.core.Peer.processBlock(Peer.java:192)
   2761:2011-20-20T22:43:13 W/System.err( 2657):    at com.google.bitcoin.core.Peer.run(Peer.java:135)
   2762:2011-20-20T22:43:13 W/System.err( 2657):    at com.google.bitcoin.core.PeerGroup$PeerExecutionRunnable$1.run(PeerGroup.java:248)

Original comment by neal...@gmail.com on 21 Aug 2011 at 5:10

GoogleCodeExporter commented 9 years ago 
In your case I'd reset just the blockchain. That should help get the blockchain 
going.

Original comment by andreas....@gmail.com on 21 Aug 2011 at 7:32

GoogleCodeExporter commented 9 years ago 
I got the same problem, with version 1.33. 
Sync stays at 1%, even if I connect to a trusted peer.

BTC did arrive, however, I am unable to load the blockchain. What todo ?

Original comment by peter.me...@lunaluna.be on 5 Oct 2011 at 5:02

GoogleCodeExporter commented 9 years ago 
Can people with this issue upgrade to Version 1.36? Please report the content 
of new bottom status line. It should say why it is not updating.

Original comment by andreas....@gmail.com on 5 Oct 2011 at 9:21

GoogleCodeExporter commented 9 years ago 
I did update to 1.36
I am using Andoid 3.2.1
My wireless is very good.

I see in the status line 
"Blockchain is 12 weeks behind"

And then nothing happens, not even after 12 hours.
Connecting to trusted peer does ont help.

What should I do ?

Original comment by peter.me...@lunaluna.be on 6 Oct 2011 at 5:16

GoogleCodeExporter commented 9 years ago 
Can you send me your logfile after you've run the app for several minutes?

You can use aLogcat to extract the log from the device. Send it to 
wallet@schildbach.de

Original comment by andreas....@gmail.com on 6 Oct 2011 at 7:08

GoogleCodeExporter commented 9 years ago 
Some side info that may be interesting to people with this problem. Bitcoin 
Wallet checks for the following before downloading the block chain:

1. (obviously) You need to be connected. If Android detects an unconnected 
state, a message will appear at the bottom of the main screen. If Android 
cannot detect unconnected state, but the device is still unconnected, 
blockchain will simply not download.

2. You need to have at least 10% of battery available. Otherwise, a message 
will appear at the bottom of the main screen.

3. Internal storage cannot be "low" or depleted. Otherwise, not only Android 
will warn you but also Bitcoin Wallet will print a message at the bottom of the 
main screen.

4. Your time AND your timezone needs to be correct. Otherwise, it may happen 
that blocks are not accepted because of time checks. Unfortunately, I don't see 
an easy way to detect misconfigured time zones. It is not enough to just look 
at the time, you also need to check the time zone in your Android settings.

Could you all make sure that all of these preconditions are met?

Original comment by andreas....@gmail.com on 6 Oct 2011 at 10:34

GoogleCodeExporter commented 9 years ago 
Thanks, my timezone was not properly set, i did put this right now.
Do I need to reset ? Blockchain ? Transactions ?

Original comment by peter.me...@lunaluna.be on 7 Oct 2011 at 5:34

GoogleCodeExporter commented 9 years ago 
Actually if this was really the cause of your problem, it should start 
downloading the block chain by just restarting the app. You can also reset just 
the blockchain if you want.

Original comment by andreas....@gmail.com on 7 Oct 2011 at 7:51

GoogleCodeExporter commented 9 years ago 
You are right, setting timezone ok worked fine.
Blockchain in,in a few minutes. Thanks.

Original comment by peter.me...@lunaluna.be on 7 Oct 2011 at 10:06

GoogleCodeExporter commented 9 years ago 
I'm closing this bug, since there were some reports of it being fixed.

If you are experiencing the same problem, please make sure you are running the 
latest version (currently: 1.52). Feel free to report a new bug.

Original comment by andreas....@gmail.com on 29 Feb 2012 at 2:52