Frequently Asked Questions

Password Safe (Pro)

View category →

There are three different types of license. Follow the instructions that are relevant to your type of license.

1. Original license (installed separately)

2. In app purchase

3. Dual license

The procedure for repairing\refreshing your license varies depending on which type you purchased.

If you still have a problem after following the instructions below, please open a support ticket stating your Support Number and Version as shown on the “About” page of the app along with the type of license you have.

1. Original License

Ensure you are using version 3.3.9. Earlier version had a bug that prevented license working on some devices.

Press “Back” until Password Safe Pro completely exits then start it again and log in.

2. In App Purchase.

Version 3.2.4 and below: When you purchase you should receive a notification telling you that the app is unlocked. If you received this notification but you have since reverted to trial mode you should press the Icon on the login screen, your license should be refreshed and trial mode deactivated again. You can also press the “Refresh my license” button that appears when you start the app.

Version 3.3.3 and Above: This should never happen unless you have installed Password Safe whilst you were logged into Play Store with an account that did not purchase it. Uninstall and reinstall whilst logged in using the account that owns the license.

3. Dual License

You should ensure your Windows application is not running in trial mode and then restore your data from your PC to your device using one of the available transfer methods such as Dropbox.

Step by step this would be.

1. Enter license key into Windows app.

2. Backup your data from Windows.

3. Create a new wallet and restore the backup you just created.

These instructions are also contained in the email you received when you first purchased your dual license. You can get a copy of this mail at http://services.kuffs.co.uk/resendkey.aspx


You have stored large images in the database and your device is unable to load them.

Image storage was intended for small thumbnails not multi megapixel photos.

Delete the image fields from your data and try again.


You have to wait a whole minute (at the default settings) WITHOUT EXITING THE APP.

There is a progress bar on screen that counts down although it is rather small so you may not realised that it is a progress bar.

If you close the app, open another app or allow the screen to turn off the countdown will begin all over again next time you open the app.


Restoring data is a simple file replace operation. Your current database is completely replaced by whichever data file you choose. No checks are made that the database is a valid Password Safe file. Any file with an extension .db can be restored but of course only a valid Password Safe file can be opened by the app.

If your app crashes or contains unexpected data then you most likely have not restored the file you intended.

For example, depending on certain app settings, a backup to Dropbox can place the backup file in different places on different devices.

Check for other backup files. You may not be using the one you think you are. To confirm this, create a uniquely named folder and place your backup into this folder. This way, when you locate the backup within the app, it will always be inside the folder you created.

If you are changing phones, backup to this unique folder on your old device then restore from it on your new one. This will ensure that both devices use the same file.

 


This one was 100% my fault.

I migrated my project from Eclipse to Android Studio and mistyped a value in the manifest.

It is fixed in Version 3.3.4

If you installed Version 3.3.3, you will need to uninstall it before installing 3.3.4

3.3.4 has no functional changes over 3.3.3 so there is no real need to update but 3.3.4 and any possible future update will not install if 3.3.3 is already installed.

I can see from my app statistics that only 0.86% of the user base for Password Safe have 3.3.3 installed so the number of affected users is small but if you are one of those users, I am VERY Sorry for the inconvenience.


This is a problem installing the app and not a problem with the app itself.  Because of this, support is available directly from Google who are responsible for supply and installation of all apps from Play Store. The error number may change but the effect is the same. The app does not install.

Possible quick fixes:

1. Uninstall the old version and then reinstall the new one. This resolves it for 99% of folks. 

Please remember to backup your data to a safe place before uninstalling. If you backup Dropbox, ensure the backup file is safely there before uninstalling the old version. Check your file in Dropbox so that you know which folder it is in (the default is Apps\Password Safe Pro) and that the date of the backup file matches the date you just made the backup. (See highlighted in the image below)

2. Install manually (avoiding Google Play). The apk is available from here:

http://www.kuffs.co.uk/android-update-3-3-3/

3. http://goo.gl/wMtQte

4. http://www.lmgtfy.com/?q=error+24

5. Contact Google Support directly at https://support.google.com/googleplay/digital-content as it is they who support Play Store.

I attempted to get an answer from Google Developer Support as to what causes this error but they were unable to help me and simply gave me this stock response.

Thanks for contacting Google Play Developer Support. We’re happy to help with issues that Android Developers experience while using the tools and services needed for distribution of apps through Google Play, however we don’t support Play Store error messages.

To provide users with the best help, please direct them to contact Google Play User Support at https://support.google.com/googleplay/digital-content

I’m sorry we couldn’t help you any further, though if you have any issues distributing Android apps through the Google Play Developer Console, please feel free to let me know.


Are you sure you are using the correct password?

Are you using the correct password for the wallet you are attempting to open? Each wallet has an independent password.

Have you recently restored your data from a backup? Your password will revert to the one that was in use at the time of the backup.

Do you have data wipe turned on? You may have mistyped your password and unwittingly wiped your data.

A query that sometimes arises is “I recently update the app in Play Store and now my password does not work\my data is gone“.  If the update process proceeds normally, your data files remain untouched. It can happen sometimes whereby the update procedure malfunctions and removes your data. On one occasion I am aware of the phone corrupting the data files making them inaccessible to the app.  For this reason, you should always backup your data before updating.

If you are sure you are using the correct password but the app does not accept it, your database may have been corrupted. You should restore your data from a backup but remember that the password that was in use at the time of the backup will also be restored.

Another common mistake is to use the wrong backup. Make sure the backup file you have restored is the one you think it is and not a different one that was made at a different time with a different password that you only ever used as a test. (It has happened).

It is not possible to recover a lost password or to find out what password was used to encrypt your data.

The only absolute certainty is that if the app tells you you have entered an incorrect password then you really have.


Refunds for Android apps are available by following the instructions here:

https://support.google.com/googleplay/answer/134336?hl=en-GB

If your request falls outside the 2 hour limit, you should contact Google directly.

Developers do not know your details so supplying your Google account details does not help.

https://support.google.com/googleplay/contact/play_request_refund_apps

Refunds for Windows applications are not available. Sales are final because there is a 14 day trial period which you can use to decide if the product meets your needs. After a license is issued, there is no way to cancel it.


There is nothing that can be done to make the app work as it once did on a pre-KitKat device.

Please read this article.
http://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/

Password Safe already requests the WRITE_EXTERNAL_STORAGE permission which gives it access to any public folder on the internal storage and read permissions for any folder on external storage.

What you have to do is only attempt to save backups to the apps accessible private folders on your SD card which is locatedcan be created on your SD card at :
Android/data/uk.co.kuffs.free.passwordsafe/

Please see here for more technical information: http://source.android.com/devices/tech/storage/

In summary, you are now restricted to a specific folder and can only save backups in that folder. There is now no way that any KitKat device can have unrestricted access to the entire SD card (root capable apps on rooted devices excepted of course)


When attempting to backup to Google Drive and an error comes up “Operation Failed: 10-”

The error number could be different.

It is the Google Drive service that is failing not the app.

Try forcing a re-authorisation by revoking the apps permissions to your Google Drive Account. You can also try uninstalling/re-installing the app (backup your data somewhere else first) in case something on your device has corrupted.

Revoking permission: Go to Google Drive web site, Choose “Settings” then “Managing Apps”

Alternative Method: https://accounts.google.com/b/0/IssuedAuthSubTokens

If this persists, please contact Google Support as we have no control over Google Drive accounts and cannot help if it malfunctions.

Google drive is actually not recommended as a primary backup location as it proven to fail for many users with no obvious fix. E.g at the time of writing this, I have one device that errors when a drive backup is attempted but it works on all other devices.

If you are restoring data and google drive is your only copy, download the file and move it to dropbox or to your phone internal storage and restore it from there.


The likely cause is that the file you are restoring does not contain the data you think it does.

Possibly you have multiple backup files and are restoring the wrong one or you have overwritten your backup file with an empty wallet by accidentally backing up instead of restoring.

Restoring a database only replaces your current data file with the backup file. It does not change the contents of either file and can never display data it does not contain.

If you store your data in Dropbox, you can recover earlier versions of the file using the Dropbox web site. https://www.dropbox.com/en/help/11


There is no guarantee that the backup folder is in the same place on a different phone. Your new phone is most likely looking in a different location to the old phone.

This article mentions this fact.

This article gives a full description of how SD storage work.

You can test this by creating a new uniquely named folder in your backup folder using your old phone and then trying to find that folder in your new phone. Another test would be to see if you can remove your SD card from your old phone yet still see your backup files on it.

The backup files will be visible when you navigate to the correct folder. If no backup files are displayed then it means you do not have any backup files in the folder you are currently viewing.


Password Safe Lite is identical to Password Safe Pro except for:-

  • No desktop application is available for Lite
  • Lite does not have WiFi or Dropbox Backup.
  • Lite does not have Remote wipe by SMS (Version 3 and above now does)
  • Password Safe Pro requires Password Safe License to unlock the trial.
  • Password Safe Lite is not a trial.

Both apps use the same database format so to move data between apps, you should perform an SD card backup from one app and then restore the same database to the other app.


You can enable 256Bit by choosing the option from the menu on the “Change Password” Screen. After changing the password, the selected encryption strength will be in use.

New wallets will use 256Bit by default.


Turn off “Auto Sort” in the preferences.

You should now see a new “Sort” option in main menu.

Auto sort can be turned on and off separately for folders\cards and fields.


To purchase only the Android app, you do this by upgrading within the app.

To purchase the Windows application or the dual license bundle which contains both Windows and Android apps, please see here.


When Password Safe was originally written, there was only one way to access Dropbox from within other apps which was to allow apps full access to your whole Dropbox folder.

Password Safe created a folder called “Kuffs Password Safe” (or whatever you set your Dropbox Path setting to) and saved the wallet files there.  Although it did not abuse this access, the ability to access any of your Dropbox files was a necessity of using the Dropbox backup feature.

From Version 2.0.8.0, an updated method based on new Dropbox functionality was included. This allows you to limit the access of the App so that it can access ONLY files within it’s own folder. This is now the default setting.

In comparison:-

Old Location : Dropbox Access Level Setting:  ON

<Your Dropbox Folder>\<Dropbox Path>

 

New Location : Dropbox Access Level Setting:  OFF

<Your Dropbox Folder>\Apps\Password Safe Pro\<Dropbox Path>

Note that <Dropbox Path> refers to the preference setting of the same name within the app.


No. You are the only person who ever knew your password. If you cannot remember it, you need to uninstall\reinstall the app and start all over again.

You do not need to buy the app again. Your purchase is stored in your Google account. You can re-install apps you have purchased at any time.


Your data is not automatically saved. You must use the “Backup” feature to save your data.

Any problem which causes data to be lost can be resolved by reinstalling the app from Google Play and then restoring your data from your latest backup.

If you failed to use any of the backup features of the app in the time you have been using it then you have permanently lost your data.


There are a number of reasons an app can Force Close.

If the app force closes as soon as you start it then it is likely been damaged. Apps are simply files on a small computer and if the computer crashes, the files can be damaged just like on their full size computer counterparts.

Uninstalling the app and then reinstalling should resolve the issue in this case. You can then restore your data from your latest backup.

If the app force closes when a specific operation is performed then it is likely that something unexpected is contained within the data and it does not know how to handle it or the data file is damaged.

Again, try restoring your data from a backup.

If the problem still occurs after you have restored, please fill in a support ticket giving as much detail as possible about the problem such as when it occurs, what you are doing/pressing at the time etc. Please also detail what steps you have taken so far to try to resolve the problem.

Some versions of our apps have a “Send Log” feature which will allow you to email the app log directly to us.


To re-install the paid version of the app without paying again, please see this link.

https://support.google.com/googleplay/answer/113410?hl=en


According to Google, in app purchases will be charged to the account that originally downloaded the app so you could uninstall the app and then download it with the account you want to be charged on.

 


This depends on what you have a problem with  but always include the version number and Support number if you have one.

winver The Windows application displays the version number at the bottom right of the screen when you open your wallet.
 andver Android apps display the version number on the bottom of the login screen or in the “About” section of the app.
 andlic The support number (previously called the license details) are displayed on the “About” page of the Android app. It is a sequence of 15 characters separated into 5 groups of 3 characters each.


Password safe by it’s nature is a single user app but it can be made to work for more than one user if some care is taken.

If the users require only access via the Android app then there is no issue as they can simply use a common Dropbox account.

Care must be taken to avoid overwriting each others changes. It would be better if one user was given the responsibility for updating or changing data but using a common Dropbox account and turning on “Auto Backup” and “Auto Notify” could help if both users wanted to make changes.

If the users want to use the Windows application also then it gets a little more complicated as each Windows license will only work with the gmail address it was purchased for but you could create a common gmail account and add it to each phone and then use this account when purchasing the Windows license.

Each user would install the application normally and use Dropbox to keep their data in sync like they would with the Android app.


It is unlikely as it simply is not my area of expertise and the user base would be very small.

I wrote the apps for myself then it grew from there so I wrote what I already knew.

I would be happy to share the database specifications if anybody wanted to take on the task.


“How do I open the .db file on my computer?”

“I am unable to open the .db file using the dropbox app. How do I do this.”

It is like opening a PDF file without using a PDF reader. You will see the file contents but they will not make sense.

Opening the .db file is not possible without using the app that created it. To do so would negate all security.

Similarly, you cannot open the data file on a Windows computer unless you use the Windows version of the app. If you could do this, there would be no point to the app.

The dropbox app only allows you to authorise the app with your dropbox account. You still need to use Password Safe to open the file.


Reinstall your app license if required:

http://support.google.com/androidmarket/bin/answer.py?hl=en&answer=113410

How to move your data from your old phone to your new phone.

If you are using Dropbox, ensure that both phones have the same settings for “Dropbox access Mode”.

On your old phone:

Upgrade to the same version of the app you have on your new phone if necessary.
Choose “Backup\Restore” from the menu.
Choose the backup method you wish to use. Dropbox is easiest. SD card requires that you manually copy the backup to your new phone.
Press “Backup” button

On your new phone:

Install app from Google Play Store
Set up an empty wallet using the same password (this is only so you can log in and access the backup menu)
Choose “Backup\Restore” from the menu.
If you chose SD card backup, copy your database to the same location on your new phone as it was on your old phone. Note this
Choose the same method you chose in the previous step.
Press “Restore” button
All your data is now on your new phone.

Note that the password will be also be restored with your data so if your backup used a different password then you will need to log out and then back into the app.

This method can also be used to copy your data to multiple devices. Dropbox backup is recommended for ease of use.


Lightwaver

View category →

Occasionally you may receive an error when importing your rooms and devices from the LightwaveRF portal.

First of all, please check that you have correctly entered your email address and pin number into the location settings.

If your login credentials are correct, the portal is possibly returning incorrect data and usually corrects itself. This is not a fault in the app. It simply means that the app is unable to interpret what the portal is producing.

All the app does is download data from this URL and parse it into its component parts.

http://www.lightwaverfhost.co.uk/getsettingsxml.php?action=D&email=<your email address>&pin=<your pin number>

Note that you may need to use the “View as source” function of the browser for the above data to be displayed correctly.

 


This is a common issue for new users as they do not fully understand how LightwaveRF the system works.
Each hardware device (switch\dimmer\relay etc) can be paired with up to 6 software devices (room\device number combination) and/or hardware remote controls.

If multiple lights are reacting to a single button it is because your lights are paired to multiple room\device combos or multiple devices have the same room\device pairing AS WELL AS the one you actually want.

e.g it is possible for the same light to react to commands for R1D1 (Room1, Device1), R2D2, R2D5, R4D9 etc etc all at the same time. It all depends on how you paired them.

Pairing a device does NOT remove all previous pairings. There is a specific “Clear Pairings” procedure (found in the manual for whatever type of  device you are using) that must be followed if you want the device to stop reacting to commands you have used in the past.

If you have trouble such as the one you are experiencing, you should clear all pairings and re-pair to the button/remote you actually want.

This is not a Lightwaver issue. You would have the exact same issue if using the official app. In fact, the problem would be more apparent if you are trying to use both apps at the same time .
For example. Consider this scenario:
All devices controlled by apps, are identified with their room and device number.
In Lightwaver you have set up a light as R1D1 and a socket as R1D2.
Using a different app, you add the same device but the the other way around. You set up the socket as R1D2 and the light as R1D1.
What you are doing when you are pairing with an app is telling a bulb/switch etc “hey, please respond to this Room/Device number combination”
Essentially you now have a bulb that is R1D1 in one app and R1D2 in another app. If you now pair your devices in Lightwaver using the normal pairing procedure and turn on the light, it works fine. The problem is that turning on/off the switch in the other app ALSO operates the light. You have sent a command to operate R1D1 and ALL devices that have been given this identifier will respond.
If you want to use multiple apps, you MUST ensure that all of the devices are identical in all apps.

Lightwaver is not intended as a companion for the official portal. It is a replacement and as such does not offer the ability to upload your data into it.

The intention is that you import your data (if required) and then use Lightwaver exclusively. The portal and official app simply do not have the ability to hold the amount of information that Lightwaver potentially uses.

Official app and portal only allow 1 location. Lightwaver has up to 200 locations.
Portal and official app allows 8 rooms with 6 devices per room (128 devices)
Lightwaver allows 15 Rooms with 16 devices per room. (240 Devices)
Therefore up to 112 devices would be completely missing from the first location if an upload was attempted and every room/location/Device would lose its icon.  All locations except the first would be completely gone.

If you wish to use both apps or the portal then you can edit your data in the official app or on the portal and then import it into Lightwaver when required.


Please read the instructions in the manual which is accessible from the Help menu within the app and also on this site here.

Specifically you need the section named “LightwaveRF Accounts”

 


Sometimes you may find that when you try to turn on one device, another one also switches. This is not a fault of the app, more an effect of how the system works if you are not fully aware of the implications of certain actions.

Each LightwaveRF device has 6 “slots” that determine what commands it responds to. This gives you the ability to pair up to 6 different remote controls to control the same device.

If you use the LightwaveRF link box, you can also control devices using apps or other software. The LightwaveRF box translates simple text commands to RF frequency commands.

For example, Each virtual room you create in the app (Lightwaver or LightwaveRF’s own app) is assigned a number from 1 to 15.  Each virtual device you create in each of those rooms is assigned a number from 1 to 16.

When you press a “button” in the app, you are sending a command to the LightwaveRF box which essentially says “Turn On/Off, device number X in Room Y”

Problems can occur if you move a device from one room to another but do not clear any existing pairings before making a new pairing.

For example:

Assume you have a switch in your living room. The switch is brand new and has never been previously paired.

You then create virtual room in Lightwaver and also a virtual switch. As this is the first room and device created, they are assigned the identifiers of “Room1, Device1” (or R1D1 for short).  Putting the hardware switch into pairing mode and pressing the virtual ON switch will use one of the slots in the hardware to remember to respond whenever a command is received to control R1D1.

Later, you move that device to your bedroom so you re-pair it and this time it gets the identifier “R2D1”. You remove the first virtual Living Room device from the app and forget that it ever existed. After pairing your switch, it now responds to BOTH commands R1D1 AND R2D1. Luckily, you do not have anything in your app that would send that command.

Months later, you buy a new lamp. Put it into your Living Room and set up a device in Lightwaver for it. By chance, it is given the identifier R1D1. The lamp is paired to R1D1 so it responds when the appropriate button is pressed.

Now you notice that whenever you turn on your Living Room lamp, your bedroom switch also comes on. This is because your bedroom switch has 2 memory slots used. One for R1D1 and also one for R2D1.

Turning on the bedroom switch does not affect the lamp because the lamp is only responding to R1D1 when you are sending the command R2D1.

To avoid this. Make sure you remove the existing pairing when you move your devices around. (Instructions to do this are in the manual for each hardware device).

Remove a single pairing:
If you find that you press a button and the wrong device responds, put that device into pairing mode and press the “Off” button in the app. This should remove the pairing for that single virtual device just as pressing the “On” button would create a pairing.

Remove all pairings:
If you do not remember what hardware device is paired to which software switch, the easiest thing to do is to clear all pairings of all of your devices one by one then re-pair them with the current configurations of rooms etc in the app.

If you just have one device that is responding to a button that you would

Also a point to note: If you use more than one app, be careful because what could be Room 1 in one app, could very easily be Room 5 in the other so whilst they may be named the same, they are actually completely different as far as pairings are concerned. Similarly, even if the rooms numbers match, the device numbers may not so you could end up with multiple devices responding to multiple different software buttons.

 

 

In summary. The pairings do not identify a specific device. They simply store a Room\Device number combination in one of the 6 slots and the device responds when a command is received that matches one of the Room\Device number combinations it has stored in those slots.

An extreme example would be that the same lamp could possibly respond to any of the commands such as R1D1, R1D5, R2D10, R5D11, R7D2, R2D2 which as you can imagine, would be incredibly confusing.

 


This is a problem installing the app and not a problem with the app itself.  Because of this, support is available directly from Google who are responsible for supply and installation of all apps from Play Store. The error number may change but the effect is the same. The app does not install.

Possible quick fixes:

1. Uninstall the old version and then reinstall the new one. This resolves it for 99% of folks. 

Please remember to backup your data to a safe place before uninstalling. If you backup Dropbox, ensure the backup file is safely there before uninstalling the old version. Check your file in Dropbox so that you know which folder it is in (the default is Apps\Password Safe Pro) and that the date of the backup file matches the date you just made the backup. (See highlighted in the image below)

2. Install manually (avoiding Google Play). The apk is available from here:

http://www.kuffs.co.uk/android-update-3-3-3/

3. http://goo.gl/wMtQte

4. http://www.lmgtfy.com/?q=error+24

5. Contact Google Support directly at https://support.google.com/googleplay/digital-content as it is they who support Play Store.

I attempted to get an answer from Google Developer Support as to what causes this error but they were unable to help me and simply gave me this stock response.

Thanks for contacting Google Play Developer Support. We’re happy to help with issues that Android Developers experience while using the tools and services needed for distribution of apps through Google Play, however we don’t support Play Store error messages.

To provide users with the best help, please direct them to contact Google Play User Support at https://support.google.com/googleplay/digital-content

I’m sorry we couldn’t help you any further, though if you have any issues distributing Android apps through the Google Play Developer Console, please feel free to let me know.


Refunds for Android apps are available by following the instructions here:

https://support.google.com/googleplay/answer/134336?hl=en-GB

If your request falls outside the 2 hour limit, you should contact Google directly.

Developers do not know your details so supplying your Google account details does not help.

https://support.google.com/googleplay/contact/play_request_refund_apps

Refunds for Windows applications are not available. Sales are final because there is a 14 day trial period which you can use to decide if the product meets your needs. After a license is issued, there is no way to cancel it.


Lightwaver does not do this. The import is only for rooms,devices and sequences. It is intended as a “starting point” when you first set up the app to save you entering all of the rooms and devices from scratch. Lightwaver was created as a replacement for the official app and portal rather than as a companion to them.

The import screen specifically states that it imports “Rooms and Devices”. Translation from the LightwaveRF timer/sequence portal data to Lightwaver data is not possible as their data formats are quite different.

I did attempt to make the process 2-way and have the ability to sync data back to the portal but this was abandoned as it would have meant losing some of the features such as changing icons etc as there is no provision for storing the extended data Lightwaver uses on the official portal. Also, Lightwaver offers double the number of rooms and devices that the official app/portal do so any sync would only ever work for the first 8 rooms which could be very confusing to users.


Your data is not automatically saved. You must use the “Backup” feature to save your data.

Any problem which causes data to be lost can be resolved by reinstalling the app from Google Play and then restoring your data from your latest backup.

If you failed to use any of the backup features of the app in the time you have been using it then you have permanently lost your data.


There are a number of reasons an app can Force Close.

If the app force closes as soon as you start it then it is likely been damaged. Apps are simply files on a small computer and if the computer crashes, the files can be damaged just like on their full size computer counterparts.

Uninstalling the app and then reinstalling should resolve the issue in this case. You can then restore your data from your latest backup.

If the app force closes when a specific operation is performed then it is likely that something unexpected is contained within the data and it does not know how to handle it or the data file is damaged.

Again, try restoring your data from a backup.

If the problem still occurs after you have restored, please fill in a support ticket giving as much detail as possible about the problem such as when it occurs, what you are doing/pressing at the time etc. Please also detail what steps you have taken so far to try to resolve the problem.

Some versions of our apps have a “Send Log” feature which will allow you to email the app log directly to us.


To re-install the paid version of the app without paying again, please see this link.

https://support.google.com/googleplay/answer/113410?hl=en


According to Google, in app purchases will be charged to the account that originally downloaded the app so you could uninstall the app and then download it with the account you want to be charged on.

 


It is unlikely as it simply is not my area of expertise and the user base would be very small.

I wrote the apps for myself then it grew from there so I wrote what I already knew.

I would be happy to share the database specifications if anybody wanted to take on the task.


Password Safe (Windows)

View category →

Windows Password Safe is now discontinued as like its Android counterpart, it has been superseded by Lockrz.

New sales are no longer possible but previous purchasers can continue to download from this link.

http://services.kuffs.co.uk/downloads/kps.msi

Note that you will need your offline key as explained here:

http://www.kuffs.co.uk/faqs/what-is-the-activation-number-for-the-windows-application/

 


Your full license details and instructions were emailed to you after you made payment.

As explained in that email, the online server is now no longer available (as the application is no longer sold) and so online activations are not possible and you should use the offline activation file that you created each time you activated a wallet online.

Your license key enabled you activate a wallet online whilst simultaneously saving your offline key.

If you ignored the instructions and failed to keep a safe copy of your offline activation file, I’m afraid that you can no longer activate new wallets.

Please do not contact support asking for a copy of the file. The offline files are generated on YOUR computer and therefore we do not have any copies.

 


Are you sure you are using the correct password?

Are you using the correct password for the wallet you are attempting to open? Each wallet has an independent password.

Have you recently restored your data from a backup? Your password will revert to the one that was in use at the time of the backup.

Do you have data wipe turned on? You may have mistyped your password and unwittingly wiped your data.

A query that sometimes arises is “I recently update the app in Play Store and now my password does not work\my data is gone“.  If the update process proceeds normally, your data files remain untouched. It can happen sometimes whereby the update procedure malfunctions and removes your data. On one occasion I am aware of the phone corrupting the data files making them inaccessible to the app.  For this reason, you should always backup your data before updating.

If you are sure you are using the correct password but the app does not accept it, your database may have been corrupted. You should restore your data from a backup but remember that the password that was in use at the time of the backup will also be restored.

Another common mistake is to use the wrong backup. Make sure the backup file you have restored is the one you think it is and not a different one that was made at a different time with a different password that you only ever used as a test. (It has happened).

It is not possible to recover a lost password or to find out what password was used to encrypt your data.

The only absolute certainty is that if the app tells you you have entered an incorrect password then you really have.


Refunds for Android apps are available by following the instructions here:

https://support.google.com/googleplay/answer/134336?hl=en-GB

If your request falls outside the 2 hour limit, you should contact Google directly.

Developers do not know your details so supplying your Google account details does not help.

https://support.google.com/googleplay/contact/play_request_refund_apps

Refunds for Windows applications are not available. Sales are final because there is a 14 day trial period which you can use to decide if the product meets your needs. After a license is issued, there is no way to cancel it.


You have not set the correct network adapter in your settings. You must choose the network interface that is using the same network your phone is using.

If you fail to tell the application the correct network interface, Backup is possible but Restore will always fail because the application will send the data to the wrong place.


There is no special procedure.

Simply install as normal, create a new wallet and import your current data from your device.

See this video for a full step by step guide.


The likely cause is that the file you are restoring does not contain the data you think it does.

Possibly you have multiple backup files and are restoring the wrong one or you have overwritten your backup file with an empty wallet by accidentally backing up instead of restoring.

Restoring a database only replaces your current data file with the backup file. It does not change the contents of either file and can never display data it does not contain.

If you store your data in Dropbox, you can recover earlier versions of the file using the Dropbox web site. https://www.dropbox.com/en/help/11


To purchase only the Android app, you do this by upgrading within the app.

To purchase the Windows application or the dual license bundle which contains both Windows and Android apps, please see here.


No. You are the only person who ever knew your password. If you cannot remember it, you need to uninstall\reinstall the app and start all over again.

You do not need to buy the app again. Your purchase is stored in your Google account. You can re-install apps you have purchased at any time.


Quick Answer:

Either in the current installation folder OR in your Documents folder.

Full Answer:

That depends on how you use the application and which operating system you use.

When a wallet is created the application first tries to save it to the same place that the application is running from so if you have installed the application normally using the setup file then this location is most likely to be C:\Program Files\Kuffs Software\KPS.

Operating systems such as Vista or Windows 7 will prevent a standard user saving files here in which case your Documents\KPS folder is used.

This is to allow you to copy the whole application onto a USB drive and run the application on any computer that has .Net Framework 4 installed.

i.e If, after installation, you copy the whole folder C:\Program Files\Kuffs Software\KPS onto your USB drive with the letter E and run it from there, the the wallets will be saved in E:\KPS

Note that the file extension for wallet files is .SDF


Password safe by it’s nature is a single user app but it can be made to work for more than one user if some care is taken.

If the users require only access via the Android app then there is no issue as they can simply use a common Dropbox account.

Care must be taken to avoid overwriting each others changes. It would be better if one user was given the responsibility for updating or changing data but using a common Dropbox account and turning on “Auto Backup” and “Auto Notify” could help if both users wanted to make changes.

If the users want to use the Windows application also then it gets a little more complicated as each Windows license will only work with the gmail address it was purchased for but you could create a common gmail account and add it to each phone and then use this account when purchasing the Windows license.

Each user would install the application normally and use Dropbox to keep their data in sync like they would with the Android app.


It is unlikely as it simply is not my area of expertise and the user base would be very small.

I wrote the apps for myself then it grew from there so I wrote what I already knew.

I would be happy to share the database specifications if anybody wanted to take on the task.


I thought it worth making this support request public. It may help others.

“When I try to start the program I get a box with the logo and a moving bar and Starting….

This just keeps going.

Behind it a dialogue box comes up that says
Password Safe has encountered a problem. we are sorry for the inconvenience.

Configuration system failed to initialize.”

It sounds like your configuration data has been corrupted.

You can delete this data and it will re-create itself.

On Windows 7 the folder to delete is located at
C:\Users\USERNAME\AppData\Local\Kuffs_Software

Other operating systems may locate the file in a different place but this link will show how to locate it:
http://kb.mozillazine.org/Finding_the_profile_folder_on_Windows


The application remembers the locations and states of your windows.

If you close a window whilst it is minimised then the window will be minimised when you reopen it.

The same thing applies to each of the dockable panes within the application and they may no longer be in the optimal position or may even be completely missing.

Sometimes you can simply resize your windows to make the data visible again like this https://www.screencast.com/t/EibVR9XiwQq

You can reset the location of all windows and dockable panes. You can do this by holding down the Shift key when you log in.

i.e Type your password. Hold down the Shift key. Press OK. When your wallet has opened, release the Shift key.

 


The “Basic Template” was designed exactly for the type of situation where you want to import data from a text file or csv file but the format the data is in is currently not supported.

In this demo, I will use a csv file created by a program called “MyPadlock”.
1. Press the “Use a Basic Template” link which you will find on the first page of the import wizard. This saves a basic CSV file that you can add your data to. (You can also use the attached template- just remove my demo data)

2. Copy the data from your MyPadlock file to the correct columns (See attached image). I used Google Docs but Microsoft Excel works even better.

3. Fill in the other columns as the picture shows to name your fields.

4. Download or save the resulting file as CSV format and import it directly into Password Safe using the import wizard.

Original_File
Basic Template

Capture


Password Safe for Windows displays an update box from which you can download the update.

Alternatively, you can also download the latest version directly from http://www.kuffs.co.uk/windows

To install, simply double click the downloaded .msi file and complete the install wizard.


Password Safe (Lite)

View category →

You have stored large images in the database and your device is unable to load them.

Image storage was intended for small thumbnails not multi megapixel photos.

Delete the image fields from your data and try again.


You have to wait a whole minute (at the default settings) WITHOUT EXITING THE APP.

There is a progress bar on screen that counts down although it is rather small so you may not realised that it is a progress bar.

If you close the app, open another app or allow the screen to turn off the countdown will begin all over again next time you open the app.


This is a problem installing the app and not a problem with the app itself.  Because of this, support is available directly from Google who are responsible for supply and installation of all apps from Play Store. The error number may change but the effect is the same. The app does not install.

Possible quick fixes:

1. Uninstall the old version and then reinstall the new one. This resolves it for 99% of folks. 

Please remember to backup your data to a safe place before uninstalling. If you backup Dropbox, ensure the backup file is safely there before uninstalling the old version. Check your file in Dropbox so that you know which folder it is in (the default is Apps\Password Safe Pro) and that the date of the backup file matches the date you just made the backup. (See highlighted in the image below)

2. Install manually (avoiding Google Play). The apk is available from here:

http://www.kuffs.co.uk/android-update-3-3-3/

3. http://goo.gl/wMtQte

4. http://www.lmgtfy.com/?q=error+24

5. Contact Google Support directly at https://support.google.com/googleplay/digital-content as it is they who support Play Store.

I attempted to get an answer from Google Developer Support as to what causes this error but they were unable to help me and simply gave me this stock response.

Thanks for contacting Google Play Developer Support. We’re happy to help with issues that Android Developers experience while using the tools and services needed for distribution of apps through Google Play, however we don’t support Play Store error messages.

To provide users with the best help, please direct them to contact Google Play User Support at https://support.google.com/googleplay/digital-content

I’m sorry we couldn’t help you any further, though if you have any issues distributing Android apps through the Google Play Developer Console, please feel free to let me know.


Are you sure you are using the correct password?

Are you using the correct password for the wallet you are attempting to open? Each wallet has an independent password.

Have you recently restored your data from a backup? Your password will revert to the one that was in use at the time of the backup.

Do you have data wipe turned on? You may have mistyped your password and unwittingly wiped your data.

A query that sometimes arises is “I recently update the app in Play Store and now my password does not work\my data is gone“.  If the update process proceeds normally, your data files remain untouched. It can happen sometimes whereby the update procedure malfunctions and removes your data. On one occasion I am aware of the phone corrupting the data files making them inaccessible to the app.  For this reason, you should always backup your data before updating.

If you are sure you are using the correct password but the app does not accept it, your database may have been corrupted. You should restore your data from a backup but remember that the password that was in use at the time of the backup will also be restored.

Another common mistake is to use the wrong backup. Make sure the backup file you have restored is the one you think it is and not a different one that was made at a different time with a different password that you only ever used as a test. (It has happened).

It is not possible to recover a lost password or to find out what password was used to encrypt your data.

The only absolute certainty is that if the app tells you you have entered an incorrect password then you really have.


Refunds for Android apps are available by following the instructions here:

https://support.google.com/googleplay/answer/134336?hl=en-GB

If your request falls outside the 2 hour limit, you should contact Google directly.

Developers do not know your details so supplying your Google account details does not help.

https://support.google.com/googleplay/contact/play_request_refund_apps

Refunds for Windows applications are not available. Sales are final because there is a 14 day trial period which you can use to decide if the product meets your needs. After a license is issued, there is no way to cancel it.


There is nothing that can be done to make the app work as it once did on a pre-KitKat device.

Please read this article.
http://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/

Password Safe already requests the WRITE_EXTERNAL_STORAGE permission which gives it access to any public folder on the internal storage and read permissions for any folder on external storage.

What you have to do is only attempt to save backups to the apps accessible private folders on your SD card which is locatedcan be created on your SD card at :
Android/data/uk.co.kuffs.free.passwordsafe/

Please see here for more technical information: http://source.android.com/devices/tech/storage/

In summary, you are now restricted to a specific folder and can only save backups in that folder. There is now no way that any KitKat device can have unrestricted access to the entire SD card (root capable apps on rooted devices excepted of course)


The likely cause is that the file you are restoring does not contain the data you think it does.

Possibly you have multiple backup files and are restoring the wrong one or you have overwritten your backup file with an empty wallet by accidentally backing up instead of restoring.

Restoring a database only replaces your current data file with the backup file. It does not change the contents of either file and can never display data it does not contain.

If you store your data in Dropbox, you can recover earlier versions of the file using the Dropbox web site. https://www.dropbox.com/en/help/11


There is no guarantee that the backup folder is in the same place on a different phone. Your new phone is most likely looking in a different location to the old phone.

This article mentions this fact.

This article gives a full description of how SD storage work.

You can test this by creating a new uniquely named folder in your backup folder using your old phone and then trying to find that folder in your new phone. Another test would be to see if you can remove your SD card from your old phone yet still see your backup files on it.

The backup files will be visible when you navigate to the correct folder. If no backup files are displayed then it means you do not have any backup files in the folder you are currently viewing.


Password Safe Lite is identical to Password Safe Pro except for:-

  • No desktop application is available for Lite
  • Lite does not have WiFi or Dropbox Backup.
  • Lite does not have Remote wipe by SMS (Version 3 and above now does)
  • Password Safe Pro requires Password Safe License to unlock the trial.
  • Password Safe Lite is not a trial.

Both apps use the same database format so to move data between apps, you should perform an SD card backup from one app and then restore the same database to the other app.


You can enable 256Bit by choosing the option from the menu on the “Change Password” Screen. After changing the password, the selected encryption strength will be in use.

New wallets will use 256Bit by default.


Turn off “Auto Sort” in the preferences.

You should now see a new “Sort” option in main menu.

Auto sort can be turned on and off separately for folders\cards and fields.


No. You are the only person who ever knew your password. If you cannot remember it, you need to uninstall\reinstall the app and start all over again.

You do not need to buy the app again. Your purchase is stored in your Google account. You can re-install apps you have purchased at any time.


Your data is not automatically saved. You must use the “Backup” feature to save your data.

Any problem which causes data to be lost can be resolved by reinstalling the app from Google Play and then restoring your data from your latest backup.

If you failed to use any of the backup features of the app in the time you have been using it then you have permanently lost your data.


There are a number of reasons an app can Force Close.

If the app force closes as soon as you start it then it is likely been damaged. Apps are simply files on a small computer and if the computer crashes, the files can be damaged just like on their full size computer counterparts.

Uninstalling the app and then reinstalling should resolve the issue in this case. You can then restore your data from your latest backup.

If the app force closes when a specific operation is performed then it is likely that something unexpected is contained within the data and it does not know how to handle it or the data file is damaged.

Again, try restoring your data from a backup.

If the problem still occurs after you have restored, please fill in a support ticket giving as much detail as possible about the problem such as when it occurs, what you are doing/pressing at the time etc. Please also detail what steps you have taken so far to try to resolve the problem.

Some versions of our apps have a “Send Log” feature which will allow you to email the app log directly to us.


To re-install the paid version of the app without paying again, please see this link.

https://support.google.com/googleplay/answer/113410?hl=en


This depends on what you have a problem with  but always include the version number and Support number if you have one.

winver The Windows application displays the version number at the bottom right of the screen when you open your wallet.
 andver Android apps display the version number on the bottom of the login screen or in the “About” section of the app.
 andlic The support number (previously called the license details) are displayed on the “About” page of the Android app. It is a sequence of 15 characters separated into 5 groups of 3 characters each.


Password safe by it’s nature is a single user app but it can be made to work for more than one user if some care is taken.

If the users require only access via the Android app then there is no issue as they can simply use a common Dropbox account.

Care must be taken to avoid overwriting each others changes. It would be better if one user was given the responsibility for updating or changing data but using a common Dropbox account and turning on “Auto Backup” and “Auto Notify” could help if both users wanted to make changes.

If the users want to use the Windows application also then it gets a little more complicated as each Windows license will only work with the gmail address it was purchased for but you could create a common gmail account and add it to each phone and then use this account when purchasing the Windows license.

Each user would install the application normally and use Dropbox to keep their data in sync like they would with the Android app.


It is unlikely as it simply is not my area of expertise and the user base would be very small.

I wrote the apps for myself then it grew from there so I wrote what I already knew.

I would be happy to share the database specifications if anybody wanted to take on the task.


Reinstall your app license if required:

http://support.google.com/androidmarket/bin/answer.py?hl=en&answer=113410

How to move your data from your old phone to your new phone.

If you are using Dropbox, ensure that both phones have the same settings for “Dropbox access Mode”.

On your old phone:

Upgrade to the same version of the app you have on your new phone if necessary.
Choose “Backup\Restore” from the menu.
Choose the backup method you wish to use. Dropbox is easiest. SD card requires that you manually copy the backup to your new phone.
Press “Backup” button

On your new phone:

Install app from Google Play Store
Set up an empty wallet using the same password (this is only so you can log in and access the backup menu)
Choose “Backup\Restore” from the menu.
If you chose SD card backup, copy your database to the same location on your new phone as it was on your old phone. Note this
Choose the same method you chose in the previous step.
Press “Restore” button
All your data is now on your new phone.

Note that the password will be also be restored with your data so if your backup used a different password then you will need to log out and then back into the app.

This method can also be used to copy your data to multiple devices. Dropbox backup is recommended for ease of use.


Comments are closed