Hi,
thanks for the example!
I was able to reproduce it on a Samsung S8.
And I found the actual problem - it was related to the 3d model and its parsing: There were unnecessary and unexpected white-spaces in the .obj file and that caused a wrong parsing and the adding of invalid vertices.
That happens on all systems, but some systems the triangles with the invalid (NaN value) vertices are simply ignored, while other systems seem to convert these NaN values to 0 and so cause these rendering errors.
The parsing problem will be fixed in the next krpano release.
To fix the obj files manually for the moment make sure that there are no spaces at the end of lines in the .obj files.
Maybe look for a texteditor that has a 'trim trailing whitespace' function to do that automatically.
Attached here a fixed model from your example:
model_fixed.zip
Best regards,
Klaus