> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/id/guide/devices-and-settings/device-specific-controls/power-management/battery-charge-mode.md).

# Modus pengisian baterai

Pilih kapan baterai cadangan perangkat GPS di Navixy mengisi daya, dengan opsi otomatis, hanya saat pengapian aktif, atau saat pengapian aktif dengan cadangan saat baterai lemah.

Mengontrol kapan baterai cadangan perangkat diisi daya.

## Pengaturan

* **Mode pengisian daya**: pilih kapan pengisian berlangsung:
  * **Secara otomatis saat diperlukan**: perangkat diisi daya sesuai kebutuhan.
  * **Hanya saat pengapian menyala**: pengisian hanya saat kendaraan berjalan.
  * **Saat pengapian menyala atau baterai lemah**: mengisi daya saat pengapian menyala, atau secara otomatis kapan pun tingkat baterai turun di bawah 30%.

## Ketersediaan

Muncul pada model perangkat berbasis baterai yang menyediakan mode pengisian daya.

## Lihat juga

* [Mode Sleep](/docs/user/id/guide/devices-and-settings/device-specific-controls/power-management/sleep-mode.md): konfigurasikan kondisi tidur hemat daya.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/user/id/guide/devices-and-settings/device-specific-controls/power-management/battery-charge-mode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.