Topic: Bitcoin Wallet for Android - page 17. (Read 121407 times)
I'm not sure if this has been addressed, but I think I accidentally sent bitcoins to an old address I had with this app. I have the prodnet.wallet fileand I was wondering how I can import the keys now that it uses a different wallet file.
What are the timestamps in the keys-file? Are they necessary?
Made up some timeformat and imported my vanitygen key \o/.For personal uses I now totally switched to the android wallet
Maybe a nice feature would be to be able to import private keys trough qr-codes
What are the timestamps in the keys-file? Are they necessary?
For those that need guidance, I wrote a piece on retrieving BTC: http://wekkelos.blogspot.nl/2012/10/save-bitcoins-from-android-bitcoin.html
I just released 2.31 final to market. So key import/export is now available to everyone. Well mostly everyone. I had to raise the minimum requirement to Froyo (Android 2.2) and above.
Thank you!!!!!
I've been patiently waiting :-)
Is there a way to import your own private key?
It's a process size limit:
https://groups.google.com/d/topic/android-developers/2tW-jKJsHFE/discussion
so there's no native-code get out of jail free card.
As I said, we already know the solution.
https://groups.google.com/d/topic/android-developers/2tW-jKJsHFE/discussion
so there's no native-code get out of jail free card.
As I said, we already know the solution.
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
In the first post it is mentioned that the Android heap limit is 4MB, on other devices it is 16 and 24 respectively. However, this heap limit applies to Dalvik, and not for Native code, so that's a solution, unless the author has already found a solution.
I just released 2.31 final to market. So key import/export is now available to everyone. Well mostly everyone. I had to raise the minimum requirement to Froyo (Android 2.2) and above.
Andreas, thanks for the updates!
Well, the problem is really that we haven't finished (or even started) deploying bloom filters. It means the RAM requirements are going up over time as Bitcoin usage scales.
There's no theoretical reason Bitcoin can't run well on your phone. But as Andreas said, we haven't finished all the programming for that yet.
There's no theoretical reason Bitcoin can't run well on your phone. But as Andreas said, we haven't finished all the programming for that yet.
It already runs well on mobile devices through web-based thin clients. It may not be your ideal security scheme nor be a node like you like, but it works just fine for the end user. And they will move on without your suggestions.
No, Bitcoin will not die because everyone and their grandma is not running a node. Mining nodes can become numerous enough.
Well, the problem is really that we haven't finished (or even started) deploying bloom filters. It means the RAM requirements are going up over time as Bitcoin usage scales.
There's no theoretical reason Bitcoin can't run well on your phone. But as Andreas said, we haven't finished all the programming for that yet.
There's no theoretical reason Bitcoin can't run well on your phone. But as Andreas said, we haven't finished all the programming for that yet.
Your device only assigns very little memory (32 MB) to each app. Thus, you are experiencing lots of out of memory errors. Try uninstalling all apps you don't really need.
[...] so your best bet is upgrading to a decent phone like the Galaxy Nexus.
[...] so your best bet is upgrading to a decent phone like the Galaxy Nexus.
Good to know that the problem is my aging device (HTC Desire HD)
I just released 2.31 final to market. So key import/export is now available to everyone. Well mostly everyone. I had to raise the minimum requirement to Froyo (Android 2.2) and above.
Well, the problem is that I use Windows (XP). Exporting the key to SD Card is no problem. The program also asks for a password to encrypt the private key thus exported. The point is: what should I do when I copy this encrypted private key to my Windows machine? I don't think that a bash with openssl commands will be at my disposal in windows.
There is OpenSSL for Windows. However, I can't help you with that since I use Windows only for gaming.
You can try importing the file into Multibit, it's also available for Windows.
Quote
Background: as with 2.23, I am having some trouble with 2.3 to get a fully updated blockchain in the Android app. Updating the chain is flacky (also after full reset of blockchain). It took me all day today to get it updated by restarting the app and numerous FC's. Now that it is updated, not all transactions are shown (compared to blockchain.info).
Don't worry, your e-mail inbox is probably full with my crash reports
Don't worry, your e-mail inbox is probably full with my crash reports
Your device only assigns very little memory (32 MB) to each app. Thus, you are experiencing lots of out of memory errors. Try uninstalling all apps you don't really need.
Quote
It is still the most gorgeous UI I have seen for an Android app so I hope the wrinkles will be ironed out in the future.
The plan is that memory requirement will be lowered considerably by receiving only transactions that are relevant to your wallet. However, this is still some time in the future (needs enhancements of protocol and upgrades of Satoshi clients), so your best bet is upgrading to a decent phone like the Galaxy Nexus.
Is there a guide on how to work with imported/exported keys?
I added a little bit of info to the README (see FILES section).
The main use case is backups, which should not need much explanation.
Well, the problem is that I use Windows (XP). Exporting the key to SD Card is no problem. The program also asks for a password to encrypt the private key thus exported. The point is: what should I do when I copy this encrypted private key to my Windows machine? I don't think that a bash with openssl commands will be at my disposal in windows.
Background: as with 2.23, I am having some trouble with 2.3 to get a fully updated blockchain in the Android app. Updating the chain is flacky (also after full reset of blockchain). It took me all day today to get it updated by restarting the app and numerous FC's. Now that it is updated, not all transactions are shown (compared to blockchain.info).
Don't worry, your e-mail inbox is probably full with my crash reports
Anyway, I want to know how I can access the funds in the wallet by other means if necessary.
It is still the most gorgeous UI I have seen for an Android app so I hope the wrinkles will be ironed out in the future.
Is there a guide on how to work with imported/exported keys?
For instance, what can I do with an exported key, how does the password relate to that (the private key is encrypted when exporting it from the Bitcoin Wallet app, etc). Will be useful for n00bs like me
For instance, what can I do with an exported key, how does the password relate to that (the private key is encrypted when exporting it from the Bitcoin Wallet app, etc). Will be useful for n00bs like me
I added a little bit of info to the README (see FILES section).
The main use case is backups, which should not need much explanation. On devices with SD card, export to your SD card directly or if external storage is in fact internal, pull your backup via USB cable. Importing is the other way round (-:
For many people, the usecase will be a wallet shared between two devices. However, I advise against such a setup (due to the risk of creating invalid transactions). For this reason, I have not documented it.
Wonderful!
Version 2.3 RC implements import and export of private keys to external storage. Would you help testing?
http://code.google.com/p/bitcoin-wallet/downloads/list
http://code.google.com/p/bitcoin-wallet/issues/detail?id=10
Quote
Version 2.3 RC implements import and export of private keys to external storage. Would you help testing?
http://code.google.com/p/bitcoin-wallet/downloads/list
http://code.google.com/p/bitcoin-wallet/issues/detail?id=10
Is there a guide on how to work with imported/exported keys?
For instance, what can I do with an exported key, how does the password relate to that (the private key is encrypted when exporting it from the Bitcoin Wallet app, etc). Will be useful for n00bs like me
Wonderful!
Version 2.3 RC implements import and export of private keys to external storage. Would you help testing?
http://code.google.com/p/bitcoin-wallet/downloads/list
http://code.google.com/p/bitcoin-wallet/issues/detail?id=10
Quote
Version 2.3 RC implements import and export of private keys to external storage. Would you help testing?
http://code.google.com/p/bitcoin-wallet/downloads/list
http://code.google.com/p/bitcoin-wallet/issues/detail?id=10
Thanks for the continued work, I like the improvement.
Bitcoin Wallet 2.23 fixes bugs and is based on bitcoinj 0.6.
The main user-facing feature is pictured in the image. You can watch pending transactions propagate through the network. As peers report the transaction, a grey circle grows. Finally, it is replaced by the well-known green block chain confirmation indication.
For the sender, this helps determining if a transaction was actually sent.
For the receiver, confidence in the validity of the transaction builds, as each peer should validate each transaction. However, this is just an indication. Nothing beats the validation power of the block chain.
Install/Upgrade Bitcoin Wallet from Google Play: https://play.google.com/store/apps/details?id=de.schildbach.wallet
The main user-facing feature is pictured in the image. You can watch pending transactions propagate through the network. As peers report the transaction, a grey circle grows. Finally, it is replaced by the well-known green block chain confirmation indication.
For the sender, this helps determining if a transaction was actually sent.
For the receiver, confidence in the validity of the transaction builds, as each peer should validate each transaction. However, this is just an indication. Nothing beats the validation power of the block chain.
Install/Upgrade Bitcoin Wallet from Google Play: https://play.google.com/store/apps/details?id=de.schildbach.wallet
Jump to: