For anyone that may run across this thread in the future, it appears I solved the riddle (at least in my particular case). Ended up changing the navigation mesh settings from Static to Dynamic, and after working out the issues this brought along (quite processor heavy?) it’s now fully functional on Android device.
Based on my experience I would exercise some caution with this setting. I found some of the other meshes in game that were set to affect navigation and it seemed to cause a lot of extra calculations to take place. I also set the “observed paths tick interval” to 0. So, just a couple extra words of caution