Android Emulator Has Two Different Proxy Settings
The emulator's own upstream proxy and Android's app-visible system proxy solve different problems. Pick the mechanism matching the request you need to route.
Android Emulator exposes two proxy mechanisms with different jobs. Android's System Proxy supplies an app-visible setting; Emulator Proxy carries the emulator's TCP traffic through an upstream proxy. Android's emulator guide treats the mechanisms as mutually exclusive.
| Mechanism | Typical requirement |
|---|---|
| Android System Proxy | App traffic using Android's proxy settings, including supported debugging arrangements. |
| Emulator Proxy | Emulator connectivity through an approved upstream proxy. |
Which request needs the route?
For corporate connectivity, inspect Emulator Proxy configuration at launch. Standalone launches and Android Studio can obtain it differently.
For app-level inspection, check whether the application honors Android System Proxy. A custom networking library may not. A debugging certificate changes trust; it does not configure a missing route.
Which process interprets the address?
Android's loopback belongs to the virtual device. The emulator host-networking documentation provides a separate address for reaching a host loopback service from the guest. A setting interpreted by the host emulator process has a different context again.
Record the emulator version, launch method, mechanism, and destination when comparing attempts. Obsolete APN screens and direct settings-database edits from Android 1.x or 2.x are not a current setup procedure.
Authentication and transport
Check the authentication method the proxy requires. A domain username in a URL does not supply a challenge-response implementation. A refused listener and a rejected account occur at different stages, and a working TCP proxy path does not establish UDP support.