Closed GoogleCodeExporter closed 9 years ago
IMHO ideally, the user would not have to deal with those issues.
Can you describe your use-cases a bit more clearly? Under which situations
would you like the sync operation to stop? When would you like it to start?
Shutting down sync when Android detects "unconnected state" and re-starting it
on re-gaining connectivity is already implemented. I admit this relies on the
detection abilities of the Android system, and I don't know if they really work
well on all Android versions.
Original comment by andreas....@gmail.com
on 7 Aug 2011 at 10:54
In general I'd like the ability to override it simply because I wish to
prioritize limited network access to other applications; for whatever reason I
don't wish to spend any of the bandwidth/time I have on bitcoin at a given
time. Right now the user has no control at all over Bitcoin network usage, and
obviously a sync is the most intensive thing it does.
There do also seem to be bugs with at least Froyo though Gingerbread on the
Nexus S seems a bit better, I'm not at all reliably seeing the sync stop when I
loose access and if the sync stalls for some reason (with all versions I'm
often seeing it grind to a halt, probably as a result of random network access
issues) there's no way to kick it to recover except to disconnect from the
network and reconnect. The stalls could probably be fixed with a timeout but
unless the timeout is aggressive it'd be nice to be able to kick things if you
have reason to believe that something happened.
Original comment by broo...@gmail.com
on 7 Aug 2011 at 11:16
Oh, and on a related note (but really a separate issue) if we don't notice that
the network has dropped then you need to do the disconnect/reconnect dance to
resume peering - the application regularly reports that it has peers when there
is in fact no viable network connection.
Original comment by broo...@gmail.com
on 7 Aug 2011 at 11:19
I'd like to see where you can toggle the icons in the notification bar. I like
how it shows when you get BTC, but I don't like seeing peers and download %.
Also, if there were settings to have it so you can only sync on Wifi and not
3G. And a setting to only sync manually. So I don't use a lot of bandwidth when
I don't need to.
Original comment by jjj...@gmail.com
on 9 Aug 2011 at 2:39
First-time sync is now much less traffic intensive (downloads only block
headers rather than all transactions).
Also, there is now an option to autosync when your device is connected to
power. Typically at these places it will be connected via WLAN as well. I
recommend making use of this. Note that if I was adding an option to sync only
on WLAN you basically would also only be able to pay when on WLAN.
At the current frequency of Bitcoin transactions, traffic should stay well
below 100 MB per month. I understand that this still can be an issue.
Original comment by andreas....@gmail.com
on 29 Feb 2012 at 3:07
Issue 48 has been merged into this issue.
Original comment by andreas....@gmail.com
on 29 Feb 2012 at 3:10
Issue 80 has been merged into this issue.
Original comment by andreas....@gmail.com
on 1 Mar 2012 at 12:09
"Note that if I was adding an option to sync only on WLAN you basically would
also only be able to pay when on WLAN." I would in fact prefer that.
Original comment by pixiemot...@gmail.com
on 1 Mar 2012 at 9:01
I notice in http://code.google.com/p/bitcoin-wallet/issues/detail?id=48 you say
"Just a side note: If you close the app, it will not download anything. There
is no downloading in the background. No need to uninstall."
Could you then remove the icon from the notification bar? It is listed in a
section named "Running" (not sure if that's the English translation), which
very much looks like it is downloading. If Android is lying about it running, I
believe users would feel safer about their bandwidth limits if they didn't see
the icon there at all.
Or perhaps just write what you wrote in
http://code.google.com/p/bitcoin-wallet/issues/detail?id=48#c2 on the About
page.
Original comment by pixiemot...@gmail.com
on 1 Mar 2012 at 9:04
Its now possible to explicitly disconnect (see action overflow menu).
Also, you can automatically sync only on power.
I consider the origin issue to be fixed, for the additional ideas can you open
individual tickets?
Original comment by andreas....@gmail.com
on 16 Jul 2012 at 1:46
Original issue reported on code.google.com by
broo...@gmail.com
on 7 Aug 2011 at 8:49