Troubleshooting Import Errors

Troubleshooting Import Errors in TimeTrack Pro – Complete 2026 Guide

Importing your exported location history files (JSON or KML) into TimeTrack Pro is designed to be instant and reliable, but Android exports differ significantly by device manufacturer (Samsung, Xiaomi, Huawei, OnePlus, Nothing, Pixel, Fairphone), Android version (14–16), Google services status, export method (direct vs Takeout), file size, storage permissions, available RAM, battery level, background restrictions, and even temporary system glitches. When import fails — with errors like "File format not supported", "Invalid file", "No locations found", app crash/freeze, "Permission denied", wrong/missing timestamps, partial import, corrupted data, slow parsing, or unexpected empty timeline — this guide provides exhaustive, step-by-step fixes for every common and many rare issue reported in 2026. Each problem includes multiple causes, diagnostic checks you can do immediately, quick workarounds, permanent solutions, device-specific quirks (One UI 7/8, HyperOS 2, HarmonyOS 4/5, OxygenOS 15/16, Nothing OS 3, stock Pixel, custom ROMs like GrapheneOS/CalyxOS/LineageOS), privacy-safe troubleshooting steps that never require uploading data, how to preserve existing imports during fixes, when and how to re-export, how to test with minimal files first, advanced recovery techniques for stubborn cases, and exact instructions for contacting support if nothing works. All advice is current as of January 2026 and based on real user reports and developer testing.

1. Universal First-Aid Steps – Do These Before Anything Else

These five quick actions resolve ~70–80% of import problems without needing deep troubleshooting:

  1. Completely restart TimeTrack Pro: swipe it away from recent apps screen, wait 10 seconds, relaunch
  2. Restart your phone: full power cycle clears temporary storage, permission, and RAM glitches
  3. Charge phone to at least 50–60%: low battery can interrupt large-file parsing or cause freezes
  4. Close all other background apps: frees RAM (especially important on 4–6 GB devices with >100 MB files)
  5. Test with a tiny known-good file: export just 1–3 days of very recent data → import that small file first. If it works but your main file fails, the problem is almost always file size, corruption, or format mismatch

After these steps, proceed to the specific error below that matches what you see.

2. Error Type 1: "File format not supported" / "Invalid file" / "Cannot parse file"

Typical symptoms: App rejects file immediately after selection, shows red error banner with one of these messages, no progress bar appears.

Most frequent causes (in order of likelihood)

  1. Wrong file selected (e.g. .zip from Takeout not unzipped, screenshot instead of JSON, log.txt file)
  2. File corrupted during download, transfer, or save (incomplete Takeout download, interrupted direct export)
  3. File is not valid JSON or KML (malformed XML in old KML, broken JSON syntax)
  4. Huawei HarmonyOS proprietary export format (not standard JSON/KML)
  5. Very old export (pre-2022 KML with non-standard structure)

Immediate diagnostic checks

  • Check file extension in Files app: must be .json or .kml (case insensitive)
  • If from Takeout: confirm you unzipped the .zip → use Location History.json inside
  • Tap file in Files app → Open with → Text editor / Code viewer → does it start with { (JSON) or
  • File size: 0 KB or very small (<1 KB) → empty/corrupted export

Step-by-step fixes (try in order)

  1. Re-select correct file: navigate to Downloads → ensure you pick the .json/.kml, not .zip or screenshot
  2. Unzip Takeout file fully if applicable → move JSON to Downloads
  3. Re-export from device: Settings → Location → Timeline → Export → choose 1-week range → JSON if offered → try importing new file
  4. If Huawei device: export again → check if format is proprietary → use online converter to standard JSON if needed (rare)
  5. Open original file in text editor → look for obvious errors (missing closing braces/tags) → if broken, re-export
  6. Clear app cache (not data): Settings → Apps → TimeTrack Pro → Storage → Clear cache → retry

Prevention tips

  • Always export directly to Downloads folder
  • Verify file opens in text editor before import attempt
  • Prefer direct device JSON export over Takeout whenever possible

3. Error Type 2: "No locations found" / "Empty timeline" / "0 entries imported" after successful-looking import

Typical symptoms: Import finishes with "Success" or no error, but timeline view shows nothing, "No data for this period", or 0 entries.

Most frequent causes

  1. Exported date range had genuinely no recorded movement (Location History off, phone powered off, airplane mode, no SIM/Wi-Fi)
  2. Wrong Google account used for export (multiple accounts on device)
  3. Location History was paused, turned off, or deleted during/for that period
  4. File corrupted or incomplete (partial download)
  5. Custom ROM without Google Play Services (no Timeline data generated)

Immediate diagnostic checks

  • Open Google Maps → profile picture → Your Timeline → scroll to same dates → do they show locations? If empty in Maps → no data to export
  • Check which Google account was used: Settings → Accounts → confirm correct one for Location History
  • Settings → Google → Location History → is it ON? Was it ON during the exported period?
  • File size: if <10 KB for multi-day export → likely empty

Step-by-step fixes

  1. Verify data in Google Maps Timeline → if empty, turn Location History ON → walk/drive around 1–2 hours → re-export recent days
  2. Switch to correct Google account → re-export
  3. If history was off/paused: accept data loss for that period → focus on new exports
  4. Re-download/re-export file → test import again
  5. On de-Googled ROMs: use microG Location History or manual device log export via ADB

Prevention tips

  • Before any export, always check recent data exists in Google Maps → Your Timeline
  • Keep Location History ON for periods you care about (pause only when you want no logging)
  • Export soon after movement — reduces chance of deletion/pausing gaps

4. Error Type 3: App crashes, freezes, hangs, or becomes unresponsive during import

Typical symptoms: Progress bar stuck at 0–50%, app closes unexpectedly, black/white screen, very slow import (>5–10 min even for small files), or device reboots.

Most frequent causes

  1. Very large file (>150–500 MB) on device with low RAM (<6 GB) or background apps consuming memory
  2. Phone low on battery (<30%) during long parse
  3. TimeTrack Pro restricted by battery optimization/doze mode
  4. File corrupted or malformed (incomplete download, bad unzip)
  5. Manufacturer aggressive RAM killing (Xiaomi HyperOS, Realme UI)

Immediate diagnostic checks

  • File size: >200 MB? → likely size issue
  • Battery % when error occurred
  • RAM usage: Settings → About phone → Memory → check if near full

Step-by-step fixes

  1. Close all background apps → free RAM
  2. Charge to >70% → retry
  3. Settings → Apps → TimeTrack Pro → Battery → set to Unrestricted + Allow background activity
  4. Restart phone → import in airplane mode (no network interference)
  5. Export smaller chunks (1–3 months or 1–4 weeks) → import one at a time
  6. Re-download/re-export file if corruption suspected
  7. On Xiaomi/Realme: Settings → Privacy protection → Special permissions → All files access → allow TimeTrack Pro

Prevention tips

  • Never export "All time" — split into monthly/quarterly ranges
  • Import when phone is charging and idle
  • Set app to unrestricted battery permanently
  • Keep device updated — parsing bugs fixed regularly

5. Error Type 4: "Permission denied", "Cannot access file", or file not visible/selectable in picker

Typical symptoms: File appears in Files app but tapping in import picker gives permission error, or file/folder invisible.

Most frequent causes

  1. Scoped storage restrictions (Android 11+ default behavior)
  2. TimeTrack Pro not granted "Files and media" or "All files access" permission
  3. File saved in app-private or restricted folder
  4. MIUI/HyperOS/One UI extra permission layer

Step-by-step fixes

  1. During first import attempt: when permission prompt appears, tap Allow / Allow all files access
  2. Settings → Apps → TimeTrack Pro → Permissions → Files and media → Allow
  3. On Xiaomi/Redmi/Poco: Settings → Privacy protection → Special permissions → All files access → enable for TimeTrack Pro
  4. Export directly to Downloads or Documents folder (default on most devices)
  5. Use built-in Files app to move file to Downloads if in wrong location
  6. Restart app after granting permissions

Prevention tips

  • Export always to Downloads
  • Grant permission once during first import — it persists

6. Error Type 5: Timestamps wrong, shifted by hours/days, missing dates, or timeline gaps

Typical symptoms: Times off by 1–8 hours, dates wrong by 1 day, random gaps in timeline, or entries appear in wrong order.

Most frequent causes

  1. Phone timezone or daylight saving change between recording and export
  2. Export/import on device with different timezone setting
  3. DST transition during exported period
  4. JSON/Takeout bug (rare in 2026 versions)
  5. Manual edit of file before import

Step-by-step fixes

  1. Ensure phone timezone correct before re-export (Settings → System → Date & time → Time zone → automatic or manual correct)
  2. Re-export the period after timezone fix
  3. Open original export file in text editor → timestamps are UTC (Z suffix) — TimeTrack Pro converts to local time — verify phone time zone
  4. If DST gap: export periods avoiding transition days or add manual notes
  5. If file edited: re-export clean version

Prevention tips

  • Keep automatic timezone enabled
  • Export soon after recording — minimizes timezone/DST issues

7. Manufacturer & ROM-Specific Import Quirks (2026)

  • Samsung One UI 7/8: Large files may freeze — set unrestricted battery + export monthly
  • Xiaomi HyperOS 2: Permission bug — enable "All files access" in special permissions
  • Huawei HarmonyOS: Proprietary format — may need conversion to standard JSON
  • GrapheneOS / CalyxOS: No Google Timeline — use microG or manual log export
  • Nothing / Fairphone stock: Clean — very few issues
  • LineageOS: Depends on GApps/microG — test small file first

8. Advanced Recovery Techniques When Basic Fixes Fail

  1. Export tiny test file (1–2 days recent) → import → if works → problem is main file size/corruption
  2. Try alternate export method (direct vs Takeout)
  3. Clear app cache only: Settings → Apps → TimeTrack Pro → Storage → Clear cache (keeps data)
  4. Reinstall app: uninstall → reinstall → import again (back up exports first)
  5. Check phone storage health: Settings → Storage → look for warnings/errors
  6. Contact support: email [email protected] with:
    • Device model & exact Android version
    • Exact error message + screenshot/video
    • File size, format, export method
    • Result of small test file import
    • Manufacturer skin (One UI, HyperOS, etc.)

9. Prevention Checklist – Avoid 95% of Future Import Errors

  • Export small ranges only (1 week–3 months max)
  • Always prefer JSON direct export
  • Verify data exists in Google Maps Timeline before export
  • Charge >60% & close apps before import
  • Set TimeTrack Pro to unrestricted battery permanently
  • Grant storage permission once on first import
  • Backup exports offline before deleting
  • Enable app encryption for sensitive periods
  • Test small file import first on large histories
  • Keep app & phone software updated

10. Summary & Realistic Expectations

Import errors almost always come from file size, format mismatch, empty data ranges, permissions, battery restrictions, or manufacturer-specific quirks — all fixable with the steps in this guide. Export small JSON ranges, verify data first, keep phone charged, grant permissions once, and use unrestricted battery mode for the app. TimeTrack Pro handles clean imports reliably and keeps your data 100% private, offline, and under your control. Most users experience zero errors after following best practices.

Still facing an issue after trying everything? Email [email protected] with full device details, error screenshot/video, test file results, and export method — personal reply within 24–48 hours guaranteed.