Beta Tester Manual
For early-access testers — what to expect and how to report issues
Welcome to early access! This page is for testers trying the app before its full release. It covers what the beta is trying to prove, the behaviours that are normal (please read those before reporting a bug), and how to send a useful report. For the detailed setup walkthrough, use the regular User Guide — this page doesn't repeat it.
1. What the beta is for
The app works on the developer's own car and phone. The beta exists to validate the three things that can only be proven on cars and phones the developer doesn't control:
- Auto-start — the bridge starts by itself when you get in the car.
- Screen-off survival — it keeps streaming for the whole drive with the phone in your pocket, on every manufacturer's flavour of Android battery management.
- Data correctness — what ABRP shows matches what your car actually did.
So the most valuable thing you can do is simply drive normally and tell us when something doesn't match that description.
2. Prerequisites
Every tester needs all of these:
- A fully electric BMW or MINI with built-in connectivity that supports CarData streaming.
- You are the main (primary) user of the vehicle in your BMW account. Joint and secondary users cannot create a CarData client, and there is no way around it. This is the single most common reason people cannot take part.
- An ABRP account with a vehicle profile and a Live-Data token — a free account works. (ABRP Premium adds Android Auto, traffic, weather and speed cameras, but is not required.)
- An Android 12+ phone.
- Available in 31 countries: the EU-27 plus Liechtenstein, Norway, Switzerland and the UK.
- Willingness to disable battery optimisation for the app, and to send a log when something goes wrong.
3. Getting set up (about 15 minutes, one-time)
- Install Install Nexiter LIVE from Google Play: https://play.google.com/store/apps/details?id=com.flaxcreative.nexiter
- Open the app Read and accept the disclaimer.
- Run the 6-step setup wizard It walks you through creating your BMW CarData client, authorizing the app, linking a car in ABRP as Generic to get your live-data token, and picking your car's Bluetooth. The detailed walkthrough with screenshots is in the User Guide. Important: when you enable the data stream in the BMW portal, tick the 25 attributes listed in the User Guide's Choosing which data to stream — without them the app connects but has nothing to send.
- Disable battery optimisation when the app asks — and double-check in Android Settings → Battery → Unrestricted. Without this, Android will kill the bridge mid-drive.
- Verify Check the dashboard shows your car's live state of charge, then take a short drive and confirm the data shows up in ABRP.
4. Known behaviours — read before reporting a bug
These are all normal. Reporting them is not wrong, but they're already known and by design (or outside the app's control):
- After any phone or app update, open Nexiter once. Until you do, the app will not auto-start on your next drive. Android puts updated apps in a "stopped state" that blocks all background triggers — this is by design and not fixable in-app.
- The bridge only runs while you're in the car (Bluetooth connected) plus a short grace period. Stopping after you park is intended, not a crash.
- The first drive after a long park can take up to ~60 seconds before the first data reaches ABRP — the car is handing off from garage Wi-Fi to its mobile network. The bridge recovers on its own.
- Install the bridge on ONE phone per car. Two phones on the same BMW account fight over the single streaming slot and both lose.
- The My BMW app's own trip list is independent of Nexiter. How BMW splits or merges trips there says nothing about what reached ABRP.
- A thank-you for useful feedback. The 14-day trial in the User Guide applies to you too. Send us a bug report, a log, or how setup went. A particularly useful report can earn a free lifetime code (a Google Play promo code). Closed-test testers who stayed through to launch already qualify.
- ABRP updates when the battery level changes. BMW sends a new state of charge each time it moves by 1 % — about every 90 seconds on the motorway, less often in town. Nexiter passes it on within seconds; ABRP can take up to a minute more to show it. The gap between updates is BMW's cadence, not an app delay.
- ABRP shows an old SoC, but Nexiter says it pushed a few minutes ago? ABRP sometimes keeps the SoC a plan started with (for example the level from before you charged) instead of the live value. Tap your car in ABRP, then tap "Use live SoC". Nexiter's data was already there; ABRP just wasn't using it for that plan yet.
- Not every ticked attribute arrives. On the developer's iX1, 7 of the 25 never do. That depends on the car, not the app. If ABRP shows your battery % and range, the important ones are coming through.
5. How to report an issue
Something didn't behave as described above? That's exactly what the beta is for. Send your report to [email protected] — one report per drive/event if possible, with:
- Date + rough time of the drive.
- What you expected vs. what happened.
- Your phone model + Android version, and whether the phone updated that day.
- If you can: a screenshot of the trip in the My BMW app and of the ABRP track for the same drive.
When the app itself misbehaves, "Share logs" in the app attaches redacted diagnostic logs — those help a lot.
6. Privacy
The beta follows the app's privacy policy. In short: log sharing is opt-in — nothing is sent unless you choose to send it — and all beta-related data is deleted within 90 days after the beta ends.
Nexiter LIVE is an independent app and is not affiliated with, endorsed by, or supported by BMW Group or Iternio (ABRP). BMW and ABRP are trademarks of their respective owners.