Device compatibility is an exact-model question.

Brand names are useful navigation labels, not compatibility verdicts. Use this page to frame a cautious check for your own hardware, software, regional variant, and applicable line conditions.

Important: Pathly does not diagnose devices or provide technical support. The manufacturer’s current documentation for your exact model is the primary source. Confirm any line-specific condition with the responsible provider or network operator.

Begin with a compatibility record, not a guess

“I have a Galaxy” or “I have an iPhone” is a reasonable shorthand in conversation, but it is not detailed enough for a travel decision. Product families span years, sizes, chipsets, regional releases, and distribution arrangements. A model may look almost identical to another while its supported radio features, physical SIM layout, or eSIM handling differs. The safest workflow is deliberately ordinary: identify the exact model name and identifier, confirm the region associated with that unit where possible, check the current system version, and read the official specification or support documentation that matches those details.

Then separate hardware capability from device status. A compatible model may still be affected by a carrier or organisation policy, a device lock, a management profile, or a condition inherited from how the device was obtained. Those issues cannot be inferred from a marketing page or a generic compatibility list. The party that administers the device or line is better placed to explain them. If you cannot verify an important condition before travel, plan around that uncertainty with offline copies and another way to reach essential contacts.

Check sequence: exact model → regional variant → current software → existing line and lock status → applicable terms. Keep each answer tied to the correct source rather than treating one website as an answer to every layer.

Six starting points for manufacturer documentation

The notes below are not a list of compatible products. They describe what to look for when you are already holding a device from one of these product families. Features and labels change over time. Use the manufacturer’s current documentation, your device settings, and the relevant line information to reach a conclusion for your particular handset or tablet.

Apple

iPhone

Start in the device’s official About information and identify the exact model and region. iPhone generations can differ in physical SIM arrangements and eSIM behaviour depending on market. Do not assume that a model family name alone tells you which combination of lines is possible.

Check carefully: the model identifier, current iOS version, the available mobile service menus, and whether the device has a restriction or lock. Apple’s current documentation is the place to confirm how the exact model manages cellular lines and which settings labels apply.

If you use the phone for authentication, observe how calls, messages, and data are assigned before changing anything. A system update can move controls or clarify them differently. Record the existing setup before travel so that you can recognise an unintended change.

Samsung

Samsung Galaxy

Galaxy is a broad family that includes different series and regional variants. A phone with a similar retail name in another market may not have the same cellular arrangement. Find the exact model number in the device settings or official materials, then use Samsung’s current model-specific guidance.

Check carefully: the hardware variant, software version, SIM manager or mobile network controls, and any administration or lock condition. Labels can vary with One UI version and regional configuration, so a screenshot from another device is not a reliable instruction.

Where more than one line is involved, read the phone’s own descriptions of default calls, messages, and data. Verify how the relevant line is expected to behave through its responsible source rather than assuming a feature has identical implications across networks.

Google

Google Pixel

Pixel devices have a recognizable software experience, but that does not remove the need to identify the exact model and region. Review the official Pixel specifications and the current Android help material that applies to your software build. Carrier-distributed devices may have conditions worth confirming separately.

Check carefully: the model name and identifier, Android version, network and SIM controls, and any policy that affects device use. Pay attention to whether the interface distinguishes saved profiles from enabled lines and whether it explains a default for data separately from calls and messages.

Use plain, documented tests when preparing: can the device display its current line state, and can you identify its existing data source? Do not rely on general online commentary for an answer about an individual device’s lock status or regional capabilities.

Xiaomi

Xiaomi hardware is distributed across several regions and software environments. Names, model variants, and menu labels may differ by market or system build. Locate the precise model identifier and consult Xiaomi’s official material intended for that version, not merely a review of a similarly named phone.

Check carefully: the device’s regional edition, the installed operating system version, cellular settings available on that unit, and its status with any organisation or line administrator. An import device may merit extra verification because its documentation context can be different from where it is being used.

Before a journey, identify where mobile network choices appear in your own menus and note the current state. If documentation does not clearly address your exact configuration, avoid treating an assumed eSIM capability as critical travel infrastructure.

Motorola

Motorola’s range also varies by generation and country. The useful question is not whether “Motorola supports eSIM,” but whether the exact model in your hand, in its intended regional configuration, has the relevant capability and is free to use in the way you expect.

Check carefully: the complete model designation, official specifications for that designation, Android version, and any limitations applied through how the phone was supplied. Manufacturer support material may distinguish features that are otherwise grouped under one family name.

Keep the line-selection vocabulary clear: a line may be stored, enabled, chosen as default, or selected for data. If the device presents these as separate controls, read the built-in explanations and current documentation before relying on them while travelling.

Larger screens

Tablets

A tablet may be Wi-Fi only or include mobile hardware. Even mobile-equipped tablets vary in their support, line handling, regional versions, and software controls. The presence of a large screen does not make the question simpler; it makes exact specification checks just as important.

Check carefully: whether the tablet has cellular hardware at all, its exact model and regional edition, operating system version, and the intended role. A tablet used for navigation or work may have different battery, hotspot, and security considerations than a phone used for messages.

Where a tablet is meant to complement a phone, decide which device holds the essential offline documents and which is expected to provide data. Avoid creating a circular dependency in which one device needs the other online to reveal the travel information you need.

Read device settings as a map, not an instruction sheet

When you open a device’s mobile settings, you may see labels for SIMs, mobile service, cellular plans, network, or connection. Each is a presentation layer over the device’s particular capabilities. The sensible goal before travel is orientation. Find where the phone reports its model; find where it shows enabled lines; find where it identifies the data source; and notice where roaming and network selection controls live. Do not change an unfamiliar setting solely because a guide for another model uses the same word.

A short written note can make this less stressful: “Line A is my usual number; Line B is currently off; mobile data is set to A; roaming control is here.” That record is personal, not technical documentation, but it helps you detect what has changed. It also gives you a simpler description to use if you consult official manufacturer or line documentation later.

Prepare for updates and resets with caution

System updates can be helpful, but they are not a task to start at a departure gate. They can require power, time, storage, a stable connection, and a restart. If an update is relevant, do it early enough to observe the phone afterwards. Do not reset network settings as a generic first response to a travel issue; that action can remove saved Wi-Fi details and other configuration. First identify the symptom and use the source responsible for that symptom.

A compact pre-departure device checklist

Find and record the exact model name or identifier from the device itself.
Check current manufacturer documentation that corresponds to that exact model.
Confirm the installed system version and read the matching help material.
Review whether a device lock, management policy, or other status may apply.
Identify the existing line used for calls, messages, and mobile data.
Save key travel information offline before making changes.
Test normal charging and plan how you will preserve battery during transit.
For any condition involving a mobile line, consult the responsible provider or network operator.

This checklist is intentionally modest. It does not promise a configuration, and it does not substitute for official documentation. It reduces the chance that a broad brand claim is mistaken for a fact about your particular equipment. After the device check, continue with the travel preparation guide or read the country notes for route-specific questions.