Skip to main content
All CollectionsHow To's
How-To Enable Discovery Mapping
How-To Enable Discovery Mapping
Updated this week

Discovery Mapping allows subscribers to earn rewards by sharing their location. This allows us to understand where Helium Mobile subscribers are using our network.

Getting Started

Before you enable Discovery Mapping, let’s get prepared! Discovery Mapping requires the latest version of the Helium Mobile app. Go to the App Stores for your device to confirm there’s no update before proceeding:

Now that we’re all set, let’s get mapping!

Turn on Discovery Mapping

  1. To enable Discovery Mapping, navigate to the “Mapping” tab using the bottom menu.

  2. Turn on the toggle next to “Enable Discovery Mapping”.

  3. You will now be asked to accept or deny our location usage policy.

    • This states that “Helium Mobile collects location data when Mobile Mapping is enabled even when the app is closed or not in use.”

  4. Tap “Accept” to continue.

  5. You will be prompted to share your device’s location data with Helium Mobile. Select “Allow While Using the App” to continue.

  6. You will be prompted to share your device’s location data with Helium Mobile. Select “Always Allow” to continue.

  7. You will be prompted to give Helium Mobile access to your Motion & Fitness information. Select “OK”.

    • Motion permission helps detect when your device is in-motion to save battery life when mapping.

  8. That’s it! You can now tap “Sounds good!”, close your Helium Mobile app and continue about your day. Just use your device as normal.

I’ve turned on mapping, now what?

While mapping is enabled, your location data is being used in the background. Make sure your device continues to share its location with Helium Mobile.

For a Discovery Mapper to qualify for rewards, they must map a total of 40 eligible hexes a day. A hex is about the size of 2 basketball courts or 1 supermarket. If you lined up 40 hexes in a row, it’s about the distance of 1 mile.

More questions? Check out the Discovery Mapping FAQ.

As a reminder, Discovery Mapping is designed to collect data regarding typical usage patterns of Helium Mobile subscriber generally, so that the community can continue to efficiently grow the Helium Mobile Network. More info can be found under "Discovery Mapping" in the Terms & Conditions.

Rewards will be claimable in your Helium Mobile app every 24 hours.

Claiming Discovery Mapping Rewards

  1. In the Navigate to the “Mapping” tab using the bottom menu.

  2. Tap the “Earnings” tab.

  3. View the “Claim” button in the middle of the screen with sum of all unclaimed rewards. If you have Discovery Mapping enabled, keep an eye out for unclaimed MOBILE rewards here. If you have no rewards, you’ll see “Nothing to Claim” instead.

  4. If you see MOBILE to claim, congrats! Select “Claim” to begin the claiming process.

  5. You will now see the sum total of unclaimed MOBILE rewards, the cost to claim in SOL, and any discounts. Approximate claiming cost is 0.0003 SOL* per transaction, but this amount can vary over time*. You can read more about Solana transaction fees here: https://docs.solana.com/transaction_fees Helium Mobile will cover one claim per week!

  6. You can now tap “Claim All” to begin the transaction.

  7. You’ll see the spinner while the transaction is in progress. Once transaction completes, the claim dialog will close and you'll be all good to go! You should now see your new MOBILE token balance in the “Tokens” tab of the “Wallet” page.

*The value of Supported Digital Assets has been subject to, and may again in the future experience, extreme volatility, which can be influenced by a variety of unpredictable factors (often with no clear indication of what is driving such volatility). You understand there can be no assurance that the Supported Digital Assets will maintain their present value in the future, or that they will have any value at all.

For clarity, SOL is the native token of the Solana Network. For more information please visit [https://solana.com/learn/blockchain-basics]

Did this answer your question?