And that was exactly some of my reasoning for not worrying about the Androids:  Though on the same logical network, the Android device addresses were assigned in a different part of the address space than the addresses I was using for the cubes and the proxies; I have my DHCP leases set for 7 days; my DHCP server pings the address as it's being assigned to be sure that there isn't a "squatter" on the address before offering it.  It's pretty difficult for a lease to expire and create an address conflict under those circumstances.  Further, I saw the same behavior with the proxies in my DHCP space as I did with them assigned statically outside of the DHCP pool.

I haven't spent the time, and probably won't, to dive deeper into what's going on on the network, but I can say with some confidence that it's not an issue of IP address conflicts, unless the android devices are "making up" addresses to use elsewhere in the address space, and managing to do that without causing other devices to squawk about an address conflict.  Ultimately, however, that turns into a Quixotic discussion - there definitely IS something about having cubes on the same network with other devices, likely Androids, and the solution is the same regardless of the root cause: get them isolated from each other.

My solution has been to create a completely separate physical network.  I've used different IP addressing for that network, but since they aren't interconnected, it really doesn't matter.  It's a little bit of an extreme solution, but very effective.