Tesla Tool for Light Phone III: Unlock and Drive

[BinnyS87]

I would like to build a simple Tesla tool for the Light Phone III and would appreciate feedback from anyone familiar with LightOS, Android development, or Tesla’s API.

The goal for the first version is straightforward:

1. Open the Tesla tool on the Light Phone
2. Tap one button
3. Unlock the car
4. Temporarily authorize it to drive
5. Get in and drive without using the Tesla app or key card

This would be especially useful for people who want to use the Light Phone as their primary phone but still rely on a Tesla. Right now, carrying a second smartphone just for the Tesla app defeats much of the purpose of switching to a Light Phone.

My initial plan is:

1. Build a basic LightOS tool with an “Unlock & Drive” button
2. Have the tool send a secure internet request using the Light Phone’s cellular data
3. Route that request through a small server
4. Use Tesla’s official Fleet API and Vehicle Command Proxy to:

• Unlock the doors
• Send the remote-start-drive command

5. Add separate buttons for lock, climate, trunk, and frunk later

This first version would not be a true Bluetooth phone key. It would require opening the tool and tapping the button, and the phone and car would both need internet access.

A future version could potentially use Bluetooth for passive entry and drive authorization, but that would require persistent background BLE access and deeper native Android integration.

Questions I would appreciate input on:

• Can a LightOS tool make outbound HTTPS requests over cellular data?
• Can tools securely store authentication tokens or credentials?
• Can a tool include native Android or Kotlin code?
• Would this type of tool be allowed in the official LightOS tool ecosystem?
• Is anyone interested in helping build or test it?

Please upvote or comment if this is something you would use.

[dupontgu]

Can a LightOS tool make outbound HTTPS requests over cellular data?

• Yes!
  Can tools securely store authentication tokens or credentials?
• Yes!
  Can a tool include native Android or Kotlin code?
• Yes, although not every standard Android API is available. We may be able to expose more if your tool needs something specific.
  Would this type of tool be allowed in the official LightOS tool ecosystem?
• if it follows our design guidelines and doesn't violate Tesla or anyone else's terms of service, I don't see why not, but I am not the only one who will review. FWIW, if you build it with the SDK and open source the code, you can always distribute it to fellow Light users yourself!