When I open any file in JT2GO for Android my soft close.
The plan is turn JT2GO a collaborative tool in my factory and turn paperless.
Hardware: 7.1 android Português (BR)
Ram 1gb; Wi-Fi; Usb; Hdmi; CPU Quad-Core Arm Cortex A7 32 Bits 1.20Ghz (VFPv4, Neon)Mali-400 MP Res: 1280 x 720P. (It's a PC Google)
Sorry for not getting back to you on this.
So, a couple of things.
First - On your device, please browse to chrome://gpu and check the Driver Information table for the Reset Notification Strategy. What is the value? If it is 0x0000, JT2Go will not work on the device.
Second - How large is the data you are trying to load? Size of the Jt file? Does it include alot of PMI Data? What is the level of detail of the jt as far as how many triangles may be present (if you know)? JT2Go is very limited in the size of data that can be loaded due to running in a WebView. Typically Jt files have to be 60MB or smaller.
Third - it could be the data itself. 4.0.6 is running with an older version of the viewer and will be upgraded in our 5.0 release, which we are hoping to have done by the end of February. Is there any chance you can attach the Jt file you are trying to load to this thread so we can test with it?
Sorry about the time.
I verify my advice and Reset Notification Strategy have value 0x8252.
About size file, we use smaller files (max 4mb).
Dont use PMI in my assemblies, parts or drafiting.
To be test we did download the last version from JT2go and continues the crashe.
Would it be possible for you to attach one of the Jt files that isn't working to this thread, so we can test it with the upcoming release? The viewer solution in the currently released version is old and is being updated and may resolve the issues.
We were able to load the attached file into JT2Go Mobile 4.0.6 and 5.0 (next release) on two different devices, one using Android 7.0 and one at 8.0. We also put the devices into Portuguese and the file loaded fine on both.
Could you tell me which device you tested?
We tested in Mini Pc Box Android (emulates a tablet device).
Note: We tested in a Samsung tablet android 5.1.1 and show same wrong.