Hi Russ,
1. Android 4.4.2, Samsung Galaxy Note 10.1 (SM-P605)
2. Group has been created, map has been shared, you have been invited... Let me know whether everything is set correctly.
After some further "research" I have found a way how to bring up the problem - it appears after turning the internet access off and restarting the device (or clearing the RAM). When I just disconnect the device and start using Collector offline (without restarting the device or clearing the RAM), it works. So it seems to me that the problem is related to RAM. (?)
You may be wondering why I want to restart the device. I don´t mean a "real-time" restart, but turning the device off and turning it on later (next day, etc.)... Lets say that users will use the device/app once a week. So the required "workflow" is: day 1: in the office - get connected, download area, disconnect, turn the device off; day 2: in the field - turn the device on, collect data offline. Is this explanation sufficient?
BTW - Thank you, I really appreciate your attitude to solving problems this way on the forum. This is much more effective than "standard" way!
EDIT:
I am observing a very strange behaviour - having the problem described earlier, when I turn on the internet connection, the problem disappear and Collector is working properly (both on-line and off-line)! To obtain the problem again, it is necessary to clear RAM/restart device... BUT - this is not a solution! There will be situations when it will not be possible to get connection.
I have sent a few standard "crash reports" with system info, I hope it will help. Does it even go to ESRI (as I hope), or is it just some Google stuff?