> For the complete documentation index, see [llms.txt](https://docs.premium-positioning.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premium-positioning.com/guides/lefebure-ntrip-client-android.md).

# Lefebure NTRIP Client (Android)

These steps connect a Lefebure NTRIP Client (Android) to the Premium Positioning correction network over NTRIP, using Lefebure NTRIP Client app. They assume you already have your NTRIP credentials.

### Before you start

* Your NTRIP username and password, from your Premium Positioning welcome email or your account on the customer portal.
* Lefebure NTRIP Client app.
* A working internet connection on the controller or phone.
* A clear view of the sky at the point you are measuring.

### Network settings

These are the same for every Premium Positioning customer. Only your username and password are unique to you.

* Server or host: rtkpremium.xyz
* Port: 2101
* Mountpoint: COMMON
* Protocol: NTRIP

### Steps

1. Install and open the app: Install 'Lefebure NTRIP Client' from Google Play and open it. The main screen shows your position and fix status. Open Settings via the gear icon - it lists Display Settings, Receiver Settings, NTRIP Settings and Premium Features.
2. Pair your GNSS receiver over Bluetooth: Pair your RTK receiver in Android's Bluetooth settings first so it appears in the device list. (For a cm position inside other apps only, you can use the phone's internal GNSS instead - accuracy then depends on the phone.)
3. Open Receiver Settings: Go to Settings > Receiver Settings - this is where you tell the app how it talks to your hardware. Wording varies slightly by version; match by meaning.
4. Set the Bluetooth connection: Set 'Bluetooth Connection Method' to connect to an external receiver via Bluetooth, then pick your paired receiver. Enable 'Auto-Enable Bluetooth'. (For the phone's internal GNSS, choose the internal/standalone option here.)
5. Enable mock locations (only if feeding other apps): If you want the corrected position in other Android apps, enable 'GPS Mock Locations' here, then in Android Developer Options set 'Select mock location app' to Lefebure NTRIP Client. Skip if you only need the position inside Lefebure.
6. Open NTRIP Settings: Go back to Settings and open NTRIP Settings - where you enter the Premium Positioning caster details.
7. Choose the network protocol: Set 'Network Protocol' to NTRIP. If asked for a version, NTRIP v1 works for our caster (v2 also fine). Wording varies by version - pick the plain NTRIP option.
8. Enter the caster address and port: Set 'Caster IP' to rtkpremium.xyz and 'Caster Port' to 2101 (fixed for all customers). The field may read 'Caster IP' or 'Caster Address' depending on version - enter the same host value.
9. Enter YOUR username and password: Enter the NTRIP Username and Password from your welcome email - unique to you. If you don't have them, contact support.
10. Load the source table and select the mountpoint: Use the option that retrieves/updates the source table (often via the 'Data Stream' field or an 'Update Source Table' action) to download the streams, then select mountpoint COMMON as your data stream.
11. Set a reported location if prompted: The caster needs your approximate position to start sending corrections. If your receiver outputs GGA this is automatic; otherwise use 'Reported Location' in NTRIP Settings to supply an approximate position.
12. Connect: Return to the main screen and press 'Connect'. The app connects to the receiver and caster; you should see RTCM data received and a byte counter increasing.
13. Confirm a fixed solution: Watch the fix-status indicator. Under open sky it should progress from autonomous to 'Float' then to a fixed RTK solution ('RTK' / 'Fixed'), usually within a minute. A fixed status with cm-level accuracy confirms corrections are working.

### If the fix will not hold

Lefebure NTRIP Client is brand-agnostic and works with many Bluetooth GNSS receivers. Label names vary slightly between versions; match the closest equivalent. Mock locations is only needed to feed the corrected position to other Android apps. For a fix you need clear sky and an RTK-capable receiver; if you stay on Float, check sky view, credentials, and that the COMMON stream is selected.

For more, see RTK corrections troubleshooting and Fix inconsistent RTK accuracy on site.

### Need help

Support is available 24/7. Include your receiver model, the mountpoint, the solution status, and the correction age when you get in touch.