Abit for Android
Can't even send a message the app just crash ( Google pixel )
Looks great, easily understandable. My issue is i cannot create any message / add a contact. When clicking the fab i get 2 entries (broadcast & message / scan qr code & create contact). But once i click any of those entries nothing happens.
First of all thank you for the mobile port, I was just wondering if it is alot of trouble for you to implement a progress bar for the proof of work... I am not a developer so I do not know, but I think it would be a nice addition.
Is this fully open source? The app looks great but for something like bitmessage fully open sourcecode is a must.
The developer did a fantastic job, finally a Bitmessage client for Android. Works awesome too and is easier to use than an email client. Keep it up, I love this app!
Instant crash htc m10 6.0.1 when sending message contact for logs
I had somehow gotten into a state where it crashed every time I tried to open a message, but reinstalling seems to have fixed it. Developer responded quickly, but now am unable to reproduce. Much nicer interface than pybitmessage. All it needs now is Orbot support!
I'm very happy to see this app! I love bitmessage, as a secure messaging platform it's great. As of currently due to limited connection speed I cannot currently verify full functionality so keep that in mind when reading my say here. I couldn't get the app to generate deterministic identities. I've experienced and underwent several reboots and possibly crashes? but unsure of the status of the operation or if the POW for all this is on progress or what. There's really no interface showing what POW is queued up and running and I would REALLY APPRECIATE such an enhancement, since running a full node on mobile is taxing on the device, I'd like to have a little bit more ongoing information somewhere of what exactly it's processing so I know when the client is busy synchronizing to the network, doing POW, Exactly what kind of request is getting POWed on; is it broadcasting for a key for example?; and any possible estimate of how long POW may last. Now I know there are some small indicators of state in and around the app in general but they are not enough information. I would like to have some activity that simply lists everything the app knows it's processing and trying to achieve, so I can more easily decide when to run full node mode and when it would be unnecessary. I will edit more into this review when I confirm more by touching with a faster wifi connection and seeing if that helps my client catch up and start to see things trickle in. Function seems stable now, after spending some time on a faster connection. Seems solid now that any potential "initial synchronization" has taken place
Does not work at all.
Cannot receive messages
Eats battery power like hungry dog. Eats processor resource up to 100%. Time gap between sending a message and receive confirmation via whatsapp - up to 20 minutes! That's the only thing I've been impressed about this app. BUT! Keep trying. We NEED this app working. Thank you.
Unfortunately, tons of bugs and lack of any error display makes the app unusable. The app won't even show trusted node connection status, there's no way to tell if it even tried to connect to it.
An excellent start to a sorely needed port of bitmessage to Android - good on you for doing this, & doing it surprisingly well.
I had somehow gotten into a state where it crashed every time I tried to open a message, but reinstalling seems to have fixed it. Developer responded quickly, but now am unable to reproduce. Much nicer interface than pybitmessage. All it needs now is Orbot support!
Keep on going that pretty thing you have born. However, what you think about adding a option for routing through tor and how about f-droid? Bdw. orbot runs on both rooted non rooted phones.
Especially a preloaded suggested defaults. As well as qr scanning chans. Oh and nicer UI for chans too.
It looks good. I had a few crashes but no big deal. I used Abit on a S4. It *does* work but it takes a long while before you receive or send your messages. As mentioned when the app starts, running a full node on a phone is no good idea... It sucks CPU and battery *a lot*. I like the effort of the author to offload the proof of work on an external node but I could not see it work.
Barely works on s5. Crashes a lot.
If it did what it was meant to it would be a great interface but unfortunately I am yet to successfully send or receive a single BitMessage. :(
Doesn't actually send anything yet (at least it doesn't seem to) Option for orbot would be nice, too. If it works properly I'll give you 5 stars
by M####:
App now working again as intended. Thanks for quick fix.