Navi to Tesla

zipi

About this app

Do you own a Tesla vehicle and use smartphone navigation because the built-in navigation is inconvenient?

With Navi to Tesla, your destination is automatically synchronized with your Tesla vehicle's navigation system when using smartphone navigation.

Stop the inconvenience of using sharing features or manually operating your Tesla vehicle's navigation.

It automatically synchronizes destinations with your Tesla vehicle's navigation system, limited to supported navigation apps.

* Supported Navigation Apps

- Tmap

- [Accessibility Services Required] Kakao Navi

- [Accessibility Services Required] Naver Maps

* Important Notes

- When using the app, the destination synchronized with your Tesla vehicle may not be the destination you intend.

- Please check that the destination has been properly synchronized before you depart.

* Important Information

- If the Tesla app is installed on your device, the destination is shared via that app. In this case, a separate Token is not required.

- If the Tesla app is not installed on your device, a Tesla authentication Token (Refresh Token) is required to use Navi to Tesla. - You can obtain a Token via the methods below.

- Desktop: https://github.com/adriankumpf/tesla_auth

- Web (Developer tools required): https://www.myteslamate.com/tesla-token/

- iOS: https://apps.apple.com/kr/app/auth-app-for-tesla/id1552058613

- The Token is used solely for calling Tesla APIs and is securely encrypted and stored on the user's device.

- For users sharing a vehicle, destination transmission is enabled only when connected to a specific Bluetooth port.

- Destination transmission is possible only in specific situations by integrating with external macro apps such as Tasker or Macro Droid.

* Information on Notification Access Permissions

For Navi to Tesla to function, a method is required to verify whether a navigation app has started providing guidance. For this reason, notification access permission is mandatory.

Some navigation apps include destinations in their notifications, so they read the destination and transmit it to the vehicle. Notifications from apps other than supported navigation apps are not read.

* Information on Accessibility Services

- Some navigation apps (Naver Maps, Kakao Navi) cannot identify the destination via notifications, so the destination is read from the screen using Android accessibility services.

- Information Collected: Driving destination, whether driving guidance is currently in progress

- Time of Collection: When the navigation app starts guiding you to the destination

- Scope of Collection: The screens of other apps are not read; only items necessary to determine the destination and driving mode are read.

- Usage/Sharing: Calls Kakao and Naver APIs to convert the destination into an address or coordinates, and Google Places APIs to verify vehicle integration capabilities. Collected destinations are transmitted to the customer's own Tesla vehicle and are not transmitted or shared with any other servers or third parties.

- Storage: Destination names, addresses, and coordinates are cached internally on the device and are automatically deleted after a certain period.

- You must confirm and enable the guidance in the app settings for it to function, and you can disable it at any time in the Android settings. - This is optional, and other navigation options can be used even if disabled.

* Information on Display over other apps permission

- Required when sending destinations via the Tesla App.

- Permission is required to display a popup allowing selection if multiple destinations have the same name. This can be disabled in Settings.

What’s new

최신 카카오내비 인식 오류 수정