Well, most arguments in the original article for DHCPv6 in android are based on things that either do not apply to android or are better solved without DHCPv6:

Well, most arguments in the original article for DHCPv6 in android are based on things that either do not apply to android or are better solved without DHCPv6: - DNS search paths can be set with RFC8106 RA options - Changing DNS servers can be done the same way via RA options or via Anycast addresses - tracking IP-host-assignments are better done with 802.1x, MAC filters and ARPwatch/NDwatch (One might use DHCP snooping, but that is usually broken with DHCPv6, also in this case, the security is in the snooping and blocking part, not the DHCP part). Everything else is really easy to fake and therefore useless. - WLC options are only relevant in the control network of your WIFI which shouldn't really be shared with any android device - VoIP phones should be a separate ESSID/VLAN/network because of QoS and security anyways. Also, most VoIP equipment doesn't properly handle IPv6 anyways, Let alone IPv6-only. The only arguments left are: hostname registration and "everybody else is doing DHCPv6". Those are not bad arguments, but maybe don't justify the added support complexity for the android devs.