On 15/01/2008, at 1:39 AM, Daryl Spitzer wrote:
I got a response to this question on the Android Beginners mailing
list. "Digit" writes (in
one way to solve this is to have Authoxy listen on a non-local
interface ( e.g. 0.0.0.0), then set the emulated proxy settings to
connect to the non-local IP address of your machine
I don't understand why this would be necessary, but is it possible to
have Authoxy "listen on a non-local interface"?
That's essentially the same as the "Allow other computers to connect"
option in Authoxy's preferences. Checking that option will bind
Authoxy to an externally accessible interface. Now that I've read the
Android thread, I can see how this would be useful - from within the
emulator you essentially have to act as an external client of
Authoxy, hence the suggestion for a non-local interface. If, as
suggested on the Adroid list, the emulator will be able to route
packets out of the emulator and through the external interface of the
native computer, you could be on a winner.
I tried setting the emulator's proxy settings to connect to the
non-local IP address of my machine (as I describe in
but it didn't work. Is there anything else I might need to configure
on my machine to allow the emulator to connect to Authoxy?
On Jan 12, 2008 5:38 PM, Daryl Spitzer <[EMAIL PROTECTED]>
Has anyone successfully configured the Android emulator to work
I followed the instructions in
and when I run:
# sqlite3 /data/data/com.google.android.providers.settings/
"SELECT * FROM system"
in the adb shell, I get:
I restarted the emulator, but I still get "Network Error - Error 80 -
Connection refused" in the browser (on the emulator). Are there any
utilities I can run on the emulator to give me more diagnostic
(I know Authoxy is working, because Safari, iTunes, etc. connect fine
| Heath Raftery <[EMAIL PROTECTED]> |
| HRSoftWorks <http://www.hrsoftworks.net> |
| *The search for a new personality is futile; what is fruitful is |
| the interest the old personality can take in new activities* |
| _\|/_ |