[Android Software/Hacking General [Developers Only]] stragulus:
@tom2164 yeah those are for the zt-180, that doesn't work on the flytouch2 though some libs might be useful (opengl?)

I've been playing around some more tonight.

Built a custom rom using the 1623 firmware, but that was highly unstable. Kernel panics, the provided opengl's would sigsegv. So quickly dropped that.

I got the rootfs to work on an ext2 parittion on an sd-card, but wifi exhibited the exact same problems as when using nfs for the rootfs. So nfs can be excluded as a problem.

Then I figured I'd try to setup wifi manually, without going through the android framework to enable the network connection. And that at least appears to work well! I have configured wifi just by using shell commands, and it's solid as a rock :) Soo.. driver should be OK! I even unplugged the ethernet after setting wifi up and making sure it was used as primary network device, and the tablet, with rootfs still over the network, just kept going on and on.

I don't know why it won't work using the android-way though. I know very little about actual android internals, so that will be something to figure out along the road. Chime in if you know more than me here, or if you know where others have stumbled into the same problem.

Anyway.. if you want to try out for yourself, here's what I did:

# start wpa-supplicant. It will display 'Try again', but logcat.log shows it's associating
# make sure wpa_supplicant.conf contains an already configured network! E.g.:

ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
update_config=1

network={
ssid="THEREALDCG"
psk="insert_passphrase_here"
key_mgmt=WPA-PSK
priority=10
}

network={
ssid="DCGUPC"
psk="insert_passphrase_here"
key_mgmt=WPA-PSK
priority=13
}

# now start it:
/system/bin/wpa_supplicant -dd -D wext -ira0 -c/data/misc/wifi/wpa_supplicant.
conf
# look at /data/local/logcat.log to see it associate
# next, start dhcp manually (XXX: use hostname from $(getprop net.hostname) ???)
/system/bin/dhcpcd -dd -B -h localhost ra0
# again, look at logcat.log. Or use getprop:
getprop | grep dhcp
# should list something like:
[init.svc.dhcpcd]: [stopped]
[dhcp.ra0.result]: [ok]
[dhcp.ra0.pid]: [2420]
[dhcp.ra0.reason]: [BOUND]
[dhcp.ra0.dns1]: [213.46.228.196]
[dhcp.ra0.dns2]: [62.179.104.196]
[dhcp.ra0.dns3]: []
[dhcp.ra0.dns4]: []
[dhcp.ra0.ipaddress]: [192.168.3.38]
[dhcp.ra0.gateway]: [192.168.3.1]
[dhcp.ra0.mask]: [255.255.255.0]
[dhcp.ra0.leasetime]: [604800]
[dhcp.ra0.server]: [192.168.3.1]
# if using root over nfs, and you want to force data to go over wifi (replace 192.168.3.1 with your gateway, and 192.168.3.0/24 with your netmask)
ip ro del default via 192.168.3.1 dev eth0
ip ro del 192.168.30/24 dev eth0
# verify settings
ip ro list
# convince android it has a network connection
setprop net.dns1 213.46.228.196
setprop net.dns2 62.179.104.196
# browser now works, although it warns about a lack of connection!

So, as you can see, android doesn't know it's connected, but at least the browser works after the warning. Market & such (which is not even enabled yet) would require to go through the android framework. Not going to fix that for now, the real fix will be to actually get the network setup working from the android settings menu.

And that's all for tonight.