> For the complete documentation index, see [llms.txt](https://docs.ipdunar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipdunar.com/integrations/mobile/android.md).

# Android

Android lets you set a per-Wi-Fi proxy. The catch: native authentication for HTTP proxies is limited — modern Android prompts for credentials in-app rather than at OS level, so apps that don't honor the system proxy auth dialog will fail.

## Per-Wi-Fi proxy (Android 10+)

1. **Settings → Wi-Fi → {your network} → Modify network → Advanced options**.
2. Proxy: **Manual**.
3. Hostname: `gate.ipdunar.com` (or ISP IP).
4. Port: `7777`.
5. Bypass: `localhost,127.0.0.1`.
6. **Save**.

\[screenshot: Android Wi-Fi proxy form]

Android **does not** have a field for proxy auth — credentials must be entered when the first authenticated app prompts.

## When the OS-level proxy isn't enough

Apps that ship their own networking stack (e.g. many games, some social apps) ignore the Wi-Fi proxy entirely. For those, use either:

* **Drony** (a free VPN-style app that intercepts traffic and routes via proxy) — works for non-rooted devices and supports auth
* **NetGuard** or **Tasker + AutoTools** for app-level rules
* **Rooted device + ProxyDroid** for true global proxy with auth

These tools route all device traffic through ipdunar; configure them with:

| Field    | Value                                                        |
| -------- | ------------------------------------------------------------ |
| Type     | HTTP or SOCKS5                                               |
| Host     | `gate.ipdunar.com` (or ISP IP)                               |
| Port     | `7777`                                                       |
| Username | full proxy username (gateway) or `ipdunar_s1a2b3c4d5e` (ISP) |
| Password | sub-user password                                            |

## ADB for testing

```bash
adb shell settings put global http_proxy "gate.ipdunar.com:7777"
```

To clear:

```bash
adb shell settings put global http_proxy :0
```

## Verify

Open the device browser to `https://ipv4.icanhazip.com`.

## Common pitfalls

* **App ignoring system proxy** — common with apps that pin SSL or roll their own HTTP stack. Use Drony or rooted tools.
* **HTTPS targets failing in Chrome on Android** — typically a captive portal or DNS issue. Verify with `chrome://net-internals/#proxy`.
* **Per-network setting** — moving to mobile data drops the proxy. Re-configure per Wi-Fi network.


---

# 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://docs.ipdunar.com/integrations/mobile/android.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.
