Sorry to keep you waiting. It is suspenseful. So after multiple troubleshooting avenues including a support ticket to ESRI a bug was identified and a work-around was provided. The bug was just opened on Jan 23;
[ BUG-000084681 : Unable to authenticate feature service in Collector for Android when the service is using token authentication and Portal is using Active Directory Federation Service (ADFS). ]
The issue lies within the Collector code. Collector has some code that will parse the username for a backslash and parse it out as a domain\username if it has one. So basically, what is happening is that when we enter 'domain\user' as the username, it is then being parsed into a UserCredential object with 'domain' and username, without including the domain. For some reason, this still allows a token to be generated, but the token is invalid because the feature layer service doesn't know the 'user', it knows 'domain\user'.
Work around
A work around to this issue is to use the following username to log in 'domain\domain\user'. This will cause the first 'domain\' to be parsed off and set as the domain, leaving the remaining username as 'domain\user' which will allow the token to be generated and the service authenticate. It's important to note that you only need to use this variation when authenticating the services on Androids.
Although Im happy that I have a resolution to allow my users to use/ test the app it is kinda hokey and doesn't pass without question from my team and users. I'm waiting on some clarification from Tech support on the fix approach and release schedule.
Frank