Feathercoin daemon and wallet production version 0.19.1
Old daemon and wallet version 0.18.3

[DEV] Mobile Android and iPhone wallet app application Developments


  • | Tip Ilocans

    I was wondering:

    should we rework the wallet and not have a clone of the litecoin wallet but create our own version ? I don’t want to say anything wrong about the wallet, the one who did it, made a great work but I think it is a little bit obsolete now:

    Google suggest to use android studio not Intellj for the application dev

    Google suggest to use gradle and not maven

    I am not sure whe need anymore actionbarsherlock…

    What do you think ?


  • administrators | Tip MrWyrm

    It works.


  • Regular Member | Tip xonar

    It’s work.

    In few second it’s connected to 3 peers.

    Thank you very much for support.


  • Moderators | Tip Wellenreiter

    I was wondering:
    should we rework the wallet and not have a clone of the litecoin wallet but create our own version ? I don’t want to say anything wrong about the wallet, the one who did it, made a great work but I think it is a little bit obsolete now:
    Google suggest to use android studio not Intellj for the application dev
    Google suggest to use gradle and not maven
    I am not sure whe need anymore actionbarsherlock…

    What do you think ?

    Well, as feathercoin is based on Litecoin, it can be an advantage that we can just pull fixes through the github chain.
    If we create a totally independent wallet, we may ending up to duplicate work, as we may have to implement the same fixes as the litecoin devs, but can’t use their solution easily.

    Also, the wallet is only the frontend and as long as it is using feathercoinj, there shouln’t be too many fixes needed.

    My personal opinion is to keep the wallet as it is.

    A workaround to get the possibility to pull changes from the litecoin wallet directly is to create our own fork of thelitecoin wallet and copy all files of our current version into that fork.

    This would enable us to pull changes from the litecoin trunk directly.

    On the other hand copy/paste is also not a really big problem 😉


  • | Tip Oded

    Hi,

    My wallet doesn’t sync. It shows 3 weeks behaid but in last two days i left it open and still 3 weeks.

    what can I do?

    I want to put something in the market and without the wallet it’s a problem.

    Thanks


  • administrators | Tip uncle_muddy

    HI Oded,

    Which wallet is not syncing?

    UM


  • | Tip Oded

    Hi uncle_muddy,

    The android wallet.

    Thanks.


  • administrators | Tip uncle_muddy

    Before you do anything export your keys using the “Backup Keys” option, within the wallet app.

    Un-install the application from your device, using the settings menu on the device and then go back to the play store and install “Featehrcoin Wallet 2” once you have installed that, you should be able to sync without any problems, I have tested it on about 5 devices now and no problems as yet. Make sure you leave your device connected to the power as without it the sync will get interrupted.

    Once the sync is complete you can go and import your keys again from the “Backup Keys” option within the wallet app.


  • | Tip Oded

    It’s work.

    Thank you.

    Prodact on thw way to the market 🙂


  • administrators | Tip uncle_muddy

    Glad it’s working for you now. I’ll try and get some instructions written up properly at some point over the next couple of days but I’m a bit busy at the moment


  • administrators | Tip uncle_muddy

    Been doing some more testing with this today…

    What have we done to the QRCode scanner? it’s very near unusable compared with the old version, from what I can make out the old version of the wallet used to call in a barcode scanner app and then return the result to the wallet, it now looks like the barcode scanner is built into the wallet app.

    The scan box on the screen is way to small if this is the case, as I really struggle to scan a code that is 210x210 pixels, where as the old barcode app scans it really quickly and returns the correct answer.

    I need to understand whats going on here if possible please, as this will effect a project I’m working on massively

    UM


  • Moderators | Tip Wellenreiter

    Not sure which old version of the wallet you are refering to??? 😞

    I simply took the latest version created by hank from the github repository, changed two lines to fix the connectivity problem, changed the Android ID and pathes to avoid conflicts with hank’s version in playstore, created the package and uploaded it to playstore.

    I can test on a tablet only, and it was no problem to scan qr codes with the tablet or get the tablet’s wallet qr-code scanned with a phone…


  • administrators | Tip uncle_muddy

    The original version from the playstore, when you tried to scan a QRcode it used to say you needed a barcode scanner app for this function to work.

    I’m testing on a Sony Z if I remove the barcode app and go to the new version of the wallet it doesn’t ask for the barcode app anymore it just launches some form of scanner it’s self, but the focus part of the screen is tiny, and has great difficulty focusing on a barcode generated on a screen I have here.

    I have just tested it using a QR generated directly from Feathercoin-qt on my mac and that works fine, maybe I need to lower the bit count in the barcode I’m generating here to allow it to focus better. I’ll give it a go and get back to you.


  • Moderators | Tip wrapper

    I will be great to get some development done on the mobile wallet. I’ve made a list of a few bugs, and will be interested to learn more on Github to supply some patches.

    Wellenreiter has basically done the work to get the new version out, there are a lot of quick fixes that can be done already by patching the Litecoin updates.

    It’s a great way to get into development via the mobile application, because of the limitations of the mobile system, everything is split into manageable functions.

    As with all development projects, notes, updates or discussions should then be raised as issues on Github so a fix or update can be developed.

    Anyone can offer a patch, it will be the Github controllers (in this case Wellenreiter) job to apply those patches officially, ie. a mostly, managerial / strategic role.

    At this stage of development it is not Rocket science any more. Bug fixing / fine tuning / updating software is more about engineering or artistic knowledge.

    The specialised area of interface design, functionality flow etc is already done.

    Great.


  • administrators | Tip uncle_muddy

    I have lowered the bit count on the QRcode here and that has made the scanning work a lot better.

    It might be worth noting thou that something that used to work with version 20 QRCodes no longer does, but dropping back down to a version 10 QRCode fixes the problem, for what I’m doing version 10 is plenty as as you get 174 char with more error correcting than I can throw a stick at.


  • Moderators | Tip wrapper

    We need a separate to create a "Modes of “Failure and fixes for Mobile Applications” in the “Support Thread”, and Add the QR code info.

    I created those guides to compile all the fixes that had been done in support (and some extra from Litecoin etc) so that member could usually find the answer or support staff had an easy place to go to, when addressing a members issue.

    The QR fault should then be raised as an issue on Github, so those are noted and in the development plan for investigation. Individual projects can be done by a member or developed in a post thread in Technical Developments.

    It is important that all changes are public in order to take members along with them. The developers do not control the distributed system, if miners do not upgrade that can cause 2 or more splits in the Blockchain, or Hard Forks, so called because they are bad.

    Also, it can be disheartening to Developers to note bugs, but I as support love it. Those bugs are work, but they are also fixable things that make progress and get everyone up to speed. The more testing and slight improvements to fine tune the application the better. Even, and especially, if we end up posting those upstream.

    Feathercoin can not be about fundamental changes to the protocol it must be about fine tuning the open source tools. Gradual, small improvements can achieve that.


  • | Tip null

    Just wanted to say thank you to everyone involved on the thread.

    I’ll be upgrading my dinosaur flip-phone for a smartphone in the near future so a mobile wallet is something that I very well much want.


  • Moderators | Tip wrapper

    With regard to onward development, would the best plan to be Fork the Litecoin wallet, then add build the set of applicable Feathercoin patches from the old Feathercoin 2. It may turn out not to be (m)any anyway.

    We would be back as daughter applications and take advantage of the current great work of the Litecoin foundation and that would make life easier and more efficient in the long run…

    I’m looking at getting a guide to compiling the wallet and Feathercoinj in a Virtualbox, this would help with testing, and if any one wants to investigate the code.


  • | Tip Ilocans

    Hi,

    I decided to have a look to the code and the first thing I noticed there are a lot of reference of litecoin in the code (String, variable names,…)

    I have a fork of the project so I made the correction and commit it

    I don,t know well github, so if and want to share this with the master, how do this work ?

    Also I was wondering, with the new version of the wallet, I am not sure but I think we need to update feathercoinj, right ?

    Thanks


  • | Tip Ilocans

    The Android wallet isn’t working again.

    I guess I am right and someone has to update feathercoinj ?


Log in to reply