Originally Posted by jonbonazza
You can either open an emulator (very slow and limited functionality, but provides quick testing) or test directly on your device by tethering it via USB.
Right, I'm talking about the USB tethering method. The problem is, the android device doesn't know how to resolve back to my local testing environment. This is more of a nameserver issue. So I'm curious what techniques you guys/gals are using. Do most of you use an emulator? The emulator seems brutally slow and clunky on OS X.
: I ended up rooting the device and now it's not an issue. I can edit my /etc/hosts file as needed, although I had to mount the /system drive as read/write since it is a read only file system.
Here's what I did in case anyone else needs to edit or update their /etc/hosts file in android (after rooting it). First root the device then get an SSH daemon up and running on it. Log into it then:
1) Find out how your /system directory is mounted:
You should see something like:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 372612 32 372580 0% /dev
tmpfs 372612 0 372612 0% /mnt/asec
tmpfs 372612 0 372612 0% /mnt/obb
/dev/block/mmcblk0p3 604736 491228 113508 81% /system
/dev/block/mmcblk0p8 13194624 186608 13008016 1% /data
/dev/block/mmcblk0p4 1214016 32844 1181172 3% /cache
/dev/block/mmcblk0p6 30224 4136 26088 14% /system/vendor
/dev/fuse 13194624 186608 13008016 1% /mnt/sdcard
3862528 558720 3303808 14% /mnt/external_sd
Mine above has /system mounted as "/dev/block/mmcblk0p3 /system"
2) Remount the drive as readable/writable:
#mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p3 /system
Just make sure the last part of the path matches your system.
3) Now you can edit /etc/hosts:
Rooting seems the way to go I guess.