My Maintenance← Back to home
English

My Maintenance · 0.6.42 · Windows & Android

User guide

Contents
  1. Getting started and local data
  2. Categories and assets
  3. Maintenance plans and saving
  4. Calling and emailing service providers
  5. Cover photos, files and preview
  6. Spare parts, ordering and notes
  7. Completed work and automatic scheduling
  8. Counters and on-time maintenance score
  9. Maintenance notifications
  10. Android camera, notifications and background location
  11. Using the Windows application
  12. Location reminders
  13. Backup, restore and moving between devices
  14. Optional cloud sync and possible costs
  15. Appearance, privacy and support
  16. Updates and new-version notices
  17. When something does not work
  18. Where bought: products, search and files
  19. Synchronize over WiFi or Bluetooth

01 / Windows & Android

Getting started and local data

My Maintenance organises asset categories, individual assets and their maintenance plans. Windows and Android can each work independently without an account or cloud connection. Each device keeps its own data until you deliberately restore a backup, use Synchronize, or run cloud sync. Saving cloud connection settings alone does not transfer data.

The interface opens in English on first use. Change Language in the top-right menu or Settings. Your choice is saved on this device. Asset names, notes and other text you enter are never automatically translated.

In both applications, dates are shown and entered as day/month/year, for example 24/10/2026. Type a date into the field or open its calendar. The date order does not depend on the app language or Windows/Android regional settings. All calendars show the week from Monday on the left to Sunday on the right.

When leaving a form with unsaved changes, the form stays open and offers Save and leave, Discard changes, or Keep editing. Saving waits for the record and all pending attachments. A write error or invalid field keeps the form and entered data intact. Discarding changes navigates only after an explicit choice and does not delete an existing saved record. This applies to products, categories, objects, object types, maintenance plans and spare parts, maintenance history, rescheduling, location reminders, notification preferences and cloud connection settings. Saving a cloud connection does not synchronize data. Switching maintenance-plan tabs retains the draft within that open plan.

This record was changed or deleted after you opened it. Your input is still here. Open the latest record and merge your changes.

  1. Create or select a category in Asset categories.
  2. Use Add new to create an asset, such as a house, trailer or machine.
  3. Open that asset and use Add service to create a maintenance plan.
  4. Enter the equipment details, required work, due date and repeat interval, then save.

02 / Windows & Android

Categories and assets

All categories is a combined view. Real estate, Devices, Tools, Cars and IT equipment are starter categories; custom categories have the same asset and maintenance features. The search field matches asset and equipment names and other listed details.

Add category asks for the category name. Delete category lets you choose a category and shows a confirmation before deleting it and its assets, maintenance plans and associated attachments. Maintenance history and its attachments are retained under Maintenance history. The combined All categories view cannot be deleted.

  1. Use Add new to enter the asset name, location, service providers and notes.
  2. Optionally choose a cover photo or take one. Its preview appears beside the name; it is saved when you save the asset.
  3. Use Add file for an asset document. It belongs to the asset and does not require a maintenance plan.
  4. Open Edit asset to change details or add or replace the photo later. Delete asset is at the bottom of the asset view and requires confirmation.

03 / Windows & Android

Maintenance plans and saving

A maintenance plan is a permanent record of the equipment and service requirements. Completing a service or scheduling a new date keeps the equipment model, service provider, work description, notes, spare parts and files.

Enter the device or service name, location, model or serial number, work required, next service date and repeat interval. The interval must be a whole number from 0 to 3650 days or months. Monthly scheduling adjusts to the last valid day of a shorter month. For one-time maintenance or a repair, select Does not repeat or enter 0 as the interval. The two controls stay in sync. Recurring maintenance uses 1–3650 days or months. One-time work is saved in history normally, but automatic scheduling is disabled. You can still schedule a new date manually.

A maintenance plan has three tabs: Details, Spare parts and History. Details contains equipment information, service contacts, plan attachments and ordering and maintenance instructions. The green Save changes button remains at the bottom of this view. Save each spare-part row using its own button. Switching tabs keeps unfinished text but does not save it automatically. Save a changed repeat interval before creating a history entry with automatic scheduling. Find ordering details and maintenance notes in the expandable Ordering and maintenance instructions section. On wider Windows screens, equipment, schedule and contact fields appear side by side; they rearrange on smaller screens. Leaving for another view through the sidebar asks for confirmation if changes are unsaved.

Delete maintenance plan is at the bottom and asks for confirmation. Its history and history attachments are retained in the global history view.

  1. Fill in the plan fields and press a green Save button.
  2. Use Schedule next service to change only the next due date.
  3. Use Mark as serviced to record completed work in history.

04 / Windows & Android

Calling and emailing service providers

Store the provider name, mobile number and email address in the plan. Call opens the device’s configured phone application; on Windows this requires an application that handles phone links.

Send email opens your default email application with the provider as recipient. The subject includes the asset and service names. The body includes the device name, model, required work and all current spare-part rows. Attachments are not added automatically. Review and send the draft yourself.

Provider information in the asset details is a useful general reference. The plan’s phone and email fields determine the recipient used by its contact buttons.

  1. Check the mobile number and email address before using the contact buttons.
  2. If no application opens, configure a default phone or email application in your operating system.

05 / Windows & Android

Cover photos, files and preview

The top Add photo and Open camera buttons in a maintenance plan set the equipment cover photo beside its name. The equivalent buttons for a spare-part row set that part’s cover photo. Each asset, plan and spare part has one cover photo; selecting another replaces its previous cover.

Add file creates an ordinary attachment for the current asset, plan, spare part or history entry. The Photos and files section in a plan also has separate buttons for ordinary photos and files. History photos always stay with that history entry. Existing older attachments are kept in their original lists.

Tap a photo thumbnail or file to preview it. PDF and .docx Word documents open inside the app with page navigation. Legacy .doc preview is unsupported: convert it to .docx first. Word pagination may differ from the original document. Videos use the built-in playback controls if the device supports their format. The limit is 50 MiB per selected file, displayed as 50 MB in the app; this check happens before photo optimization.

Closing a preview returns to the same asset, plan or editor. Deleting a photo or file requires confirmation. Cover-photo deletion removes only the cover, not the asset or maintenance record. A photo opens fitted entirely inside the available viewer area regardless of file size. Zoom with two fingers or Ctrl + mouse wheel on Windows, then drag the enlarged image. Reopening restores the fitted view.

New photos are optimized automatically and locally when added on Windows or Android, including camera and gallery images, cover photos and ordinary attachments for assets, maintenance plans, spare parts, history and products in Where bought. Existing saved photos and the original files in your gallery or computer are not changed.

The app aims for roughly 200–400 KB per ordinary photo, preferably using WebP, with JPEG as a fallback. This is a target, not a fixed limit: detailed photos may remain larger. Photos are not enlarged, and an optimized result is used only if it is smaller. Orientation and proportions are preserved. Check the readability of equipment labels after adding a photo and keep important originals.

Small, already optimized, transparent, animated or unsupported special images are kept unchanged. If optimization cannot be completed, the original file is saved; preview support still depends on the format and device. PDF, Word, video and other documents are not recompressed. Backups, restoration and transfers use the stored photo bytes without optimizing them again.

On Windows, Open camera shows a preview from the built-in or connected camera. Allow camera access, choose a device if there are several, and select Take photo. The photo follows the same cover or attachment workflow for that item; save the item too when creating a new asset or product. The camera is released after capturing or cancelling. Android still uses the phone camera picker. If the camera is missing or permission is denied, choose an image file instead.

If a DOCX has no saved page breaks and its content overflows a page, the preview divides it into readable pages. Previous and Next also reach the overflow content. Where possible, breaks fall between text lines. The PDF viewer is unchanged; exact DOCX layout and page counts can still differ from Word.

  1. For a new asset, select or capture the photo and then save the asset.
  2. For an existing plan or spare part, selecting or capturing a photo saves it immediately. For a new spare-part row, its current fields are saved first.
  3. Use two fingers to zoom and drag a zoomed image or document to move around. On Windows, use Ctrl + mouse wheel where supported.
  4. Keep an independent backup of important original documents.

06 / Windows & Android

Spare parts, ordering and notes

Add spare part creates an editable row with Part, Order code and Remarks. Each row has its own Save and Delete buttons, photo and camera controls, and Add file. Attachments from one part never belong to another part or to the general plan files.

Save each row after editing. Adding a photo or file also saves that row’s current fields. Deleting a saved part asks for confirmation and removes its attachments; other parts and history remain.

The ordering fields are in the plan’s Details tab, in the expandable Ordering and maintenance instructions section. They store required supplies, the last supplier, product or shop link, last order date and maintenance instructions. Save them with Save changes. Open ordering link uses your browser.

  1. Add one row per part so order codes and remarks remain easy to identify.
  2. Use the part’s photo or camera button for its identifying photo and Add file for its documents.
  3. Check the spare-part rows before generating an email to the provider.

07 / Windows & Android

Completed work and automatic scheduling

Maintenance history records Provider, Date, Work performed, Technician name and Remarks. Date is the date the service was actually completed. In a plan, Maintenance history opens the History tab; choose Add service there to add an entry. Mark as serviced opens the entry form directly.

The checkbox Automatically schedule the next service using the repeat interval controls whether saving creates a new due date. When checked, the next date is calculated from the Date in this history entry using the plan’s last saved repeat interval. When unchecked, saving the entry does not schedule a new date. A confirmation shows the new service date when one is created.

Add photos, camera images and files to the saved history entry. Edit history entry changes that entry; automatic scheduling again requires explicit opt-in. The recorded original due date remains available for the on-time score.

In the main menu, Maintenance history is directly below Delete category. Maintenance history shows records across assets, including retained history from deleted assets or plans. Filter by asset, view its files and delete individual entries with confirmation. Deleting an entry does not undo or change an already scheduled next service date.

  1. Enter the actual completion date and describe the work performed.
  2. Tick automatic scheduling only if you want the next due date calculated now.
  3. Save the entry, check the confirmation, then attach supporting photos or reports.

08 / Windows & Android

Counters and on-time maintenance score

The top asset counter includes all assets, including those without maintenance plans. The selected category or asset limits the totals in the current view. All categories combines the categories.

Maintenance plans, Service due and Upcoming are buttons that open the corresponding lists. Service due turns red when a pending service is due today or overdue. Upcoming covers the next 30 days.

The green-to-red score is the percentage of completed services finished on or before their recorded due date. Late completions reduce the score. Entries without a recorded original due date are excluded. Before any qualifying service is completed, the view says there is no history. Pending overdue work is shown by Service due and is not itself a completed-history score entry.

09 / Windows & Android

Maintenance notifications

In Settings → Notifications, enable local maintenance reminders, select a time and save. One daily summary covers pending maintenance due today or overdue. Scheduling does not require cloud sync or an account.

The app schedules up to 90 days ahead and refreshes scheduling when opened or after relevant maintenance changes. Open it at least once every 90 days. If today’s selected time has passed, the first summary is scheduled for tomorrow.

Test notification in 1 minute schedules a local test. Close the app normally and wait. Check schedule reads the operating system’s scheduling status. A schedule acknowledgement does not guarantee exact delivery time.

  1. Allow notifications in the operating system.
  2. Enable reminders, set the time and press Save notifications.
  3. Use the one-minute test and check the phone or Windows notification centre.

10 / Android

Android camera, notifications and background location

Allow notifications for My Maintenance in Android settings. Battery saving can delay delivery; allow unrestricted battery use if necessary. Force stop also stops background work: reopen the app afterwards. Reopen after restarting the phone to check schedules.

Open camera requests an image through Android’s camera/file selection. Complete the capture and confirm it in the camera screen. Cancelling capture leaves the existing photo unchanged.

Location reminders need precise location, Allow all the time, enabled device location, notifications and Google Play services. Allow precise location first, then background location in Android settings. The maintenance diary works even if you decline these optional permissions.

11 / Windows

Using the Windows application

Use the installed Windows application for local storage and scheduled notifications. Windows can show scheduled reminders after the app closes, but the computer must be on; focus and notification settings can hide alerts.

Open camera shows a live preview from the built-in or connected PC camera. Allow camera access, select a camera if needed and press Take photo. Add photo chooses an existing image. The camera closes after capturing or cancelling.

Windows can prepare location reminders for transfer in a backup. Background arrival detection itself runs on Android. Email and phone buttons require compatible default applications.

12 / Windows & Android

Location reminders

Open Extras → Location reminder. Add a name, address or coordinates, radius, reminder text and repeat rule. Use an address search or current location on Android, then select the correct result. Address lookup may require internet. Coordinates can be entered manually.

The radius must be between 100 and 5000 metres. Choose Once or On each new arrival. A one-time reminder disables itself after notifying you. Repeated reminders require leaving and re-entering the area, with at least 10 minutes between alerts. Up to 100 locations can be active.

Arrival detection may be delayed by several minutes. If already inside the area when enabling a reminder, an alert may appear immediately. The phone must be on, with the required permissions and services enabled. Ordinary closing and force stopping are different; force stopping disables background operation.

13 / Windows & Android

Backup, restore and moving between devices

Settings → Backup and restore → Create backup creates a .mmbak file containing both the maintenance diary and Where bought, including their categories, records, photos and attachments, and saved location reminders. Choose a location you can find again and copy the backup to another device or secure storage. Each backup uses a new file name; existing backups are not overwritten. Success is reported only after the saved contents are verified. A failure may leave an incomplete new file: do not use it for restoration; retry with a new name. On Android, choose a location that allows both reading and writing.

Restore backup replaces the destination device’s data for the modules contained in the backup after confirmation. A current full backup replaces both maintenance and Where bought records; an older maintenance-only backup leaves existing purchase records unchanged. Restoration does not merge diaries. A backup made on Windows can be restored on Android and vice versa. Back up the destination device before replacing its data.

File sizes, available checksums and record relationships are checked. Missing or damaged active attachments block backup creation; an incomplete or damaged backup blocks restoration before records are replaced. Already optimized photo files are restored unchanged. Location reminders are restored disabled and need Android permission checks before activation. The cloud connection must be explicitly enabled again.

Backups are not encrypted. Store them securely. Uninstalling the app or clearing app data can delete local data; a source-code ZIP or installer is not a backup of your maintenance records.

Automatic Backup: A full backup is created offline while the app is running, or on the next opening after it becomes due. Backups do not run while the app is closed.

On Windows, use Browse to choose an existing destination folder. Android uses Download/MyMaintenance/Backups; Android 9 and earlier may ask for storage permission. Depending on the phone’s file manager, Open backup folder may open Downloads; then navigate to MyMaintenance/Backups.

The five latest automatic backups in this folder are kept. Older ones are removed only after the new backup is verified. Manual backups are never deleted. A backup includes both modules and attachments and is not encrypted.

Choose daily, weekly or monthly and save. The first backup runs after settings close. The next due time follows the last successful backup in device local time; monthly schedules clamp to the last day of the next month when needed. Back up now saves the selected settings and creates a verified backup even with scheduling disabled. The last successful time, result and file path are shown. Failed attempts retry after 15 minutes while the app is open. The destination and schedule belong to this device and are not transferred by restoring a backup. Configure cloud-provider backups with the provider.

Backups are processed in chunks with progress and cancellation before the database commit. Limits are 3 GiB of attachments, 20,000 files, 100,000 records, a 16 MiB manifest and 50 MiB per file. Free storage must accommodate the temporary archive and restored files.

An invalid backup does not replace existing records. New unreferenced files from failed or cancelled attempts are removed, including on the next launch after interruption. This cleanup never removes referenced restored files or older attachment folders. Cloud is disabled only after restored records pass validation; an uncertain commit leaves cloud disabled until you review it.

V1 maintenance backups preserve purchases. A V1 maintenance file may lack its original checksum: a warning is shown and a new checksum is calculated, but original integrity cannot be proved. V2 live files must have valid matching checksums.

Android system cloud backup and system device transfer are disabled. Use the app’s .mmbak backups or synchronization you explicitly enable. Cloud access keys are not included in backups.

  1. Create a backup on the source device and confirm the saved file exists.
  2. Copy the .mmbak file to the destination device.
  3. Create a safety backup there, then choose Restore backup and confirm replacement.
  4. Check the records and files. Enable local notifications and Android location reminders as needed.

14 / Windows & Android

Optional cloud sync and possible costs

Cloud sync is optional and runs when you press Sync now. Both devices must use the same cloud collection. Choose Maintenance database only or Include the Purchases database. The second option adds categories, products, photos and attachments. Location reminders, permissions and automatic backup destinations and schedules remain device-local. This choice applies to this sync. Maintenance-only leaves local and cloud purchase data unchanged. Update every device to version 0.6.40 or later before using the new cloud format. Data to share: Maintenance database only / Include the “Where bought” database. For offline sharing, use Synchronize.

For your own WebDAV cloud or NAS, create a separate empty folder, enter its full HTTPS WebDAV address, username and app password. The server must support strong ETags and conditional writes. Not all WebDAV services are compatible.

The source package also includes instructions for a Cloudflare Worker and a private R2 bucket on your own account. Cloud services may charge for storage, requests, traffic or other usage. Check the provider’s current pricing and account limits before enabling it; the app does not include or pay for your cloud subscription.

Create independent backups before the first sync. Check connection and then sync each device. If conflicts are reported, review the records and choose which side to keep. Deletions can propagate to other devices. Credentials remain in the operating system’s secure storage and are excluded from backups; cloud files are not end-to-end encrypted.

Cloud sync remains a separate final device-testing step for this project. Local backups and offline use are available without it.

If both devices choose different cover photos for the same record, review the conflict. The selected photo stays as the cover and the other is kept as an ordinary attachment.

Both devices created a category with the same name. Choose the category to keep; products from both categories will be linked to it and preserved.

15 / Windows & Android

Appearance, privacy and support

Open Settings with the gear icon. Light and Dark mode and language are saved on this device. Language is also available in the top menu. Estonian, English, Spanish, German, Finnish and Russian interface text and guides are bundled for offline use. Help gives quick instructions; User guide opens this detailed searchable guide.

Privacy and permissions explains local storage and optional services. Support the developer opens the voluntary PayPal donation link and QR code. The app is free and a donation is not required to use it.

16 / Windows & Android

Updates and new-version notices

Open Settings → Updates to see the installed version. On Windows and the Android test edition, use Check for updates, then Download update and Install update when offered. Save your work and create a backup first. Windows closes the app when it opens the installer. Update the existing installation; do not uninstall the app.

The app checks when opened, brought to the foreground or while in use if a check is due. After a successful automatic check, the next automatic check waits 24 hours. A failed network check is silent and can be retried after at least 15 minutes while the app is visible. Manual checks remain available when the online channel is configured. A closed app does not perform these checks. The app never downloads or installs an update automatically.

Tap A new version is available to open the update settings; unsaved changes may require confirmation before leaving. Later hides that version’s notice for 24 hours, while a different newer version can appear sooner. A successful manual check or update-file import also refreshes the notice. A previously downloaded update does not prevent later checks for a newer release. If the server withdraws an update, a successful check removes its availability notice.

Online updates require an update channel configured by the developer. For offline updating, Choose update file accepts a signed .mmupdate package supplied by the developer. File import also requires an app build configured to verify that package. If the check or file button is unavailable, obtain a compatible build or update package from the developer; a random APK, EXE or source ZIP is not a .mmupdate package.

The Android test edition may require Allow this app to install updates and permission in Android settings; return to the app afterwards and choose Install update. The Google Play edition uses Check on Google Play to open Google Play and follows its update process instead of importing a file. Complete any store or system confirmations yourself.

A signature, checksum, platform or version mismatch blocks installation. If a downloaded file is missing, incomplete or damaged, download it again or reselect the original signed .mmupdate package. An interrupted download must be started again. Do not bypass verification or uninstall the app to solve an update-file error.

After restarting the app, you may need to check and download again or reselect the .mmupdate file before installation is offered. Opening the system installer does not confirm that the update succeeded: complete its steps, reopen My Maintenance and check the installed version. Cancelling leaves the existing app installed.

17 / Windows & Android

When something does not work

If a photo or document does not open, check its type and whether the original file is readable. New files must fit the 50 MiB limit before photo optimization. An unavailable image may show a fallback icon. Do not delete the whole record to fix a preview problem. Keep the original and any working backups. If backup creation reports a missing or damaged attachment, resolve that specific file first; the app cannot create a complete backup from missing bytes.

For PDFs, use the app’s page controls; supply a password for protected PDFs. Convert old Word .doc files to .docx. Preview layout can differ from Word, particularly around complex formatting.

If a save fails, keep the form open, read the error and retry. Some asset fields or earlier attachments may already have saved; the editor retains the created asset ID so retrying does not create another asset. Save each spare-part row separately.

For notification problems, check permissions, device time, focus/battery settings and Check schedule. For location problems, also check precise and background location and Google Play services. Device-level delivery and background behaviour must be tested on the actual phone or Windows installation.

A maintenance plan also keeps its created ID if the screen refresh fails after saving; retrying does not create a duplicate. Unsaved spare-part rows are marked separately, and leaving the plan asks for confirmation when changes remain unsaved.

If the diary fails to load at startup, read the error and reopen the app to retry. Do not clear app data or uninstall it as a first step. If the error persists, keep your backups and report the error with the installed version to the developer.

18 / Windows & Android

Where bought: products, search and files

Where bought opens as a category menu. All categories shows every product, including uncategorized products. A category opens its product list; Back to categories returns to the menu. Add product retains the complete form and preselects the current category. Add category creates a custom category. Remove category lets you select any real category, including Other, then asks for confirmation; products remain uncategorized. All categories is an aggregate view and cannot be deleted. Defaults are initialized once and deletions are respected. Untouched default names follow the selected language; custom and renamed names remain unchanged. When adding a product during global search, select its category yourself; the previous hidden category is not assigned.

Where bought is a separate local product catalogue. You can add any product without creating a maintenance asset. Only the product name is required. Price is stored in EUR with two decimal places; an empty price remains unspecified. Product and category names are your own text and are never translated. Optional product fields include category, seller, website, phone, email, purchase date and warranty end date. The website, call and email buttons use compatible applications configured on the device.

Search is at the top of the Where bought landing page and in every category product list. It always searches the entire Where bought database, including other categories and uncategorized products. Search matches product names, sellers, category names, websites, phone numbers, email addresses and prices, ignoring letter case and common accents. Each result shows its category. While search text is entered, the category filter is hidden because search covers all categories. Clearing the text restores the open category list or the landing category menu. With an empty search, the category filter can show All categories or Uncategorized. Deleting a category preserves its products.

Photos and Camera select images; File accepts documents and other attachments. You can select several photos or files. The first photo selected through Photos or Camera becomes the proposed main photo if none exists. Press Save to store the product and selected files. If one upload fails, completed uploads remain stored and only the remaining files stay queued for retry.

The main photo appears beside the product name and in the product list. Use Set as main photo on another image to change it; the previous main photo remains an ordinary attachment. Pending choices are applied when saved. A saved image can be made the main photo immediately. Deleting a photo or file asks for confirmation and does not remove bytes another record may still use.

Open a saved photo or document to use the existing in-app viewer. Closing it returns to the same product, including any unfinished text. New photos use automatic local optimization; original gallery files are untouched. Documents are not recompressed. The limit is 50 MiB per selected file. Unsupported preview formats can still be stored; see Photos and files for viewer limits.

A full backup includes both modules and their files. Restore checks sizes, SHA-256 and record relationships. Older maintenance-only backups preserve existing purchases. Purchases can be included in cloud sync using the explicit scope choice.

  1. Open Where bought and choose Add product. Enter its name and any optional details.
  2. Create categories with Add category, then select an optional category in the product form.
  3. Choose Photos, Camera or File, select a main photo if needed, and press Save.
  4. Search from the landing page or any category: results include all purchase categories and uncategorized products. Clear the search text to browse the selected category again. Open a product to view or edit its details and files; deletion requires confirmation.

19 / Windows & Android

Synchronize over WiFi or Bluetooth

Extras → Synchronize connects Windows and Android, or two Android phones. Choose the same connection method on both devices: WiFi / local network or Bluetooth. No internet or cloud account is needed. Choose Send on one device and Receive on the other. Only one device creates the QR code; the other Android scans it. The sender may either create or scan the code. Windows always creates it. Keep both apps open; sleep, leaving the view or closing the app can interrupt the transfer.

For WiFi, both devices must be on the same local network and phone WiFi must be enabled; mobile data alone is insufficient. Guest-network device isolation can block access. Bluetooth does not require a shared WiFi network; pair devices in system settings first. Windows always creates the QR code; Android may create or scan it. Press Create QR code on one device and Scan QR code on the other Android. Select opposite roles and allow camera, local-network or nearby-device access when requested. The camera reads the live QR preview without taking a photo or saving frames. Tap the preview to focus if needed. Cancel or the phone Back button closes the scanner. Device names are automatically Windows or Android. QR pairing is approved automatically; the sender then presses Send data and the receiver finally presses Synchronize. The code expires in 5 minutes; keep it private. If several WiFi addresses appear, select the shared-network address.

Every new Send starts with Maintenance database only. Include the “Where bought” database explicitly includes both modules, products, prices, categories and seller contacts. Review the counts and attachment size and press Send data. The recipient sees the sender, scope and counts. File verification and temporary staging start automatically; they do not merge existing records. Credentials, settings and unrelated information are excluded. Maintenance-only sharing leaves purchases on the receiving device unchanged.

Files are transferred in chunks and checked for size and SHA-256 without optimizing photos again. Data is merged by record IDs, rather than restored as a replacement backup. Choose a side for each conflicting record or main photo; the other main photo remains an attachment. Same-name purchase categories require a merge decision. Finally press Synchronize. Cancel before saving to leave the current database unchanged. Both devices display green SYNCHRONIZED only after successful saving and final acknowledgement; transferring files alone does not produce this message.

Windows Firewall may request private local-network access. Allow the app on that network; do not disable the firewall or expose an internet port on the home router. Android may request local-network or Bluetooth connection permission. A connection or storage error preserves existing records. Start a new attempt. If final acknowledgement is lost, the destination may already have saved: check it before considering restoration.

Turn on Bluetooth on both devices and pair them in the system Bluetooth settings first. One device creates the QR code; the other Android scans it. Between phones, select the phone displaying the QR code from the paired-device list on the scanning phone. Keep both apps open and the devices close. No WiFi or internet is needed. Only already-paired devices are listed; the app does not scan nearby devices or request location access for Bluetooth. Selecting the wrong device cannot bypass the QR certificate and token checks. Either phone may send or receive. Large attachments are faster over WiFi.

If attachment verification fails, the message names the attachment and related record and distinguishes missing or unreadable files, size differences, checksum differences, and invalid verification information or storage references. The check applies to WiFi and Bluetooth, including local files before accepting a transfer. The sender QR appears only after successful verification. Damaged attachments are not skipped. For missing or changed files, check the original or a backup. If adding the original again, verify that the new attachment opens before explicitly removing the old broken attachment record. Do not restore an entire old backup without considering that it replaces records with that snapshot.

If a checksum is missing or malformed, the message offers Repair this attachment’s verification information. First check that the named file opens and its contents are correct; you can close Synchronize and open it in its related record. Then retry synchronization and press the repair button. The app reads the local file and asks for separate confirmation with its name and related record. Cancelling changes nothing. Confirming updates only that attachment’s checksum and modification metadata. Its bytes, name, role, relationships and other attachments remain intact. A mismatch with a well-formed historical checksum is never overwritten. Missing files or size differences cannot be repaired with this button. Changes to the file or attachment record while confirmation is pending require a new check. A new checksum does not establish historical authenticity. After success, restart sending; the recipient’s file verification resumes automatically. Repair itself does not merge records; final Synchronize consent is still required. Each affected attachment requires its own confirmation.

Synchronization also preserves deletion markers for previously removed attachments. An old deleted maintenance attachment may have no checksum or an older checksum format; it is not a file to transfer and its missing local file is not required. Its deletion marker and saved verification information are not rewritten, and it is not resurrected without an explicit conflict decision. Size, checksum, contents and relationship checks stay strict for active attachments. If the recipient’s local record structure is invalid, the error now explicitly identifies validation of the records on this device and receiving is not approved. Update both Windows and Android to the same latest version and start a new sharing session.

In the synchronization view, Send or Receive turns green only when selected; only one role is selected at a time. QR creation/scanning, sending and final Synchronize actions remain in the stationary bottom action area. Longer content and conflict comparisons scroll separately. On mobile, expand Connection instructions to read the guidance. Final confirmation stays disabled until conflicts are resolved.

No Wi-Fi connection to the same local network was found. Connect both devices to the same Wi-Fi network and try again. Mobile data can stay on.

← Back to home