[Moto X Android Development] hachamacha:
Hi, I've got a pretty big hairy dubiously useful post where I list things I've tried and failed with as well as some network and syslog dumps here: http://xdaforums.com/showpost.php?p=66005364&postcount=815 about a page back in this thread.

I had tried "set dhcp to legacy" a few times and it was pretty clear that not only didn't it work, but that there wasn't another version (an earlier one) on my phone (e.g. dhcpcd v.x.x) to switch to. Also as someone says above, (or maybe in another thread I was reading on this fairly common 6.0.1 problem (well, on the 5x anyway), the problem is more likely that the dhcp client isn't even getting to the point where it's being called after a disconnect, so there is no reconnect attempt.

Other things I've tried since then that I've read about: Disabling ipv6 : nogo, Various combinations of bluetooth and wifi: nogo, booting in "safe mode" to eliminate app interference: nogo, and more in that post I mentioned.

A thing of interest (to me anyway). Since the nexus 5x('s in general) running an OTA 6.0.1 immediately began showing a very similar if not identical problem to this one, they are an interesting case to follow because they're current, a bit more popular at the moment than our old Moto X's and you can follow any number of threads on them. What all of the complaints have in common is this: If anyone on 6.0.1 switches back to nexus 5x 6.0.0, the problem is gone. It showed up with the . . .01. I'm going to see if I can download one of each OS and look at network related changes. --

edit 1: I tested at first with the stock kernel and next with tycoo kernel, which to me are indistinguishable from one another as they regard this networking problem.

Edit 2:: dhcpcd testing using pre-6.0.1 (5.1 in my case) android motox::

As I thought I recalled from my linux days, when wi-fi is enabled (not connected, just enabled), dhcpcd (/system/bin/dhcpcd) shows up as a constantly running daemon (is there another kind? ;;)) and that is a significant difference between 5.1 (or 6.0.0) and 6.0.1 (or the latest cm13 version we're all using). Without /system/bin/dhcpcd being present, there is never going to be a reconnect to wi-fi, period. I'll start looking there after I compare the syslogs which I've now got. I don't want to get anyone's hopes up since there is an issue open in the google codebase already and if they can't find it first, well, something is way off.

I'm hoping to get a bit of a clue by seeing how dhcpcd is kicked off during boot (likely from something in rc.local if it exists on android or in (/etc/init.d) via the boot process. It works that one time, never again.

Edit 3: Issue as in codebase (is closed but high-priority for some unknown reason):

https://code.google.com/p/android/i...tars Reporter Opened&groupby=&sort=&id=190667

Anyway: After I read that issue (152 posts + the very last one is mine asking them to reopen it or point us to where this issue is either continued, etc., then I also started to recall that wpa_supplicant could play a huge role in this sort of problem as well. I had completely forgot the Wi-Fi part of this bringing in other primary dependencies. Ah well. Been awhile since I looked at these sorts of things. More stuff to ignore from me to come no doubt.

Continuing to track things: This issue I mentioned above was apparently "fixed" (see comment 61 in the above link to the google bugbase). I'll list the pertinent comments:

If that's so: Then the next decent question (which I asked over on google's bug base) is: Where in the code is the fix or has it been released in any form to anyone, or is there at least a work-a-round. ? I think it might help if a bunch of you guys who are interested went over there and a) signed in b) starred the issue and c) left a comment. They may think this is a dead issue..