[Verizon Motorola Droid Turbo Android Development] Competentpsycho:
[MENTION=5747496]bhb27[/MENTION] will need to see if anything I gleaned is helpful here but it appears the first call in that log ended at 21:37:13. In the dmesg at that time (~890 sec after boot start) we have this:

[ 889.048675,1] type=1400 audit(1491878307.150:72): avc: denied { read } for uid=1000 pid=3831 comm="imsdatadaemon" scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=netlink_socket permissive=1
[ 889.048960,1] type=1400 audit(1491878307.150:73): avc: denied { create } for uid=1000 pid=3830 comm="imsdatadaemon" scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=netlink_route_socket permissive=1
[ 889.052837,1] type=1400 audit(1491878307.150:74): avc: denied { bind } for uid=1000 pid=3830 comm="imsdatadaemon" scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=netlink_route_socket permissive=1
[ 889.052952,1] type=1400 audit(1491878307.150:75): avc: denied { write } for uid=1000 pid=3830 comm="imsdatadaemon" scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=netlink_route_socket permissive=1
[ 889.053056,1] type=1400 audit(1491878307.150:76): avc: denied { nlmsg_read } for uid=1000 pid=3830 comm="imsdatadaemon" scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=netlink_route_socket permissive=1
[ 889.053159,1] type=1400 audit(1491878307.150:77): avc: denied { read } for uid=1000 pid=3830 comm="imsdatadaemon" scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=netlink_route_socket permissive=1
[ 889.773945,3] init: avc: granted { set } for property=net.lte.ims.volte.provisioned pid=2370 uid=1001 gid=1001 scontext=u:r:radio:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 889.774448,3] init: avc: granted { set } for property=net.lte.ims.wfc.provisioned pid=2370 uid=1001 gid=1001 scontext=u:r:radio:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 889.774853,3] init: avc: granted { set } for property=net.lte.ims.vt.provisioned pid=2370 uid=1001 gid=1001 scontext=u:r:radio:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 889.974075,3] init: avc: granted { set } for property=net.lte.ims.volte.provisioned pid=2370 uid=1001 gid=1001 scontext=u:r:radio:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 890.036972,3] init: avc: granted { set } for property=net.lte.ims.wfc.provisioned pid=2370 uid=1001 gid=1001 scontext=u:r:radio:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 890.060126,3] init: avc: granted { set } for property=net.lte.ims.vt.provisioned pid=2370 uid=1001 gid=1001 scontext=u:r:radio:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service

May be something unable to update volte back to available after that initial call. [MENTION=7838338]translucentfocus[/MENTION] do you have SELinux running in enforcing mode or permissive? I think these are related to SELinux, but if it is in permissive mode the system just logs these without actually stopping the operation so it should not affect volte if it is permissive. If it is enforcing this may be related. However it appears based on the logs here it is in permissive mode, but I figured you can confirm for us.

There are also some interesting looking ims logs in the logcat output starting at around 21:38:25 which seems like when sim was pulled and reinserted to regain volte, though I am not sure what to make of them.