After data collection, the app will try to upload data and then it will get a crash. If I restart the app and try to upload data manually, the crash happens too. The log is attached.

Phone: MI 9 OS: MIUI 10 9.2.28 Android: 9 Kernel: 4.14.83

After updating to V1.2.0.300 following error happen after calling

Modeling3dReconstructQueryResult queryResult = Modeling3dReconstructTaskUtils.getInstance(getApplicationContext()).queryTask(taskId);

On V1.1.0.300 everything works without problems.

2021-11-10 09:17:23.217 32513-3129/com.lvonasek.arcore3dscanner I/3DModelingKit_Modeling3dReconstructQuery: Begin to query status!
2021-11-10 09:17:23.217 32513-3129/com.lvonasek.arcore3dscanner I/3DModelingKit_QueryWork: Begin to query status!
2021-11-10 09:17:23.218 32513-3129/com.lvonasek.arcore3dscanner I/3DModelingKit_ReconstructApplication: get ky flag: true
2021-11-10 09:17:23.254 32513-3129/com.lvonasek.arcore3dscanner I/3DModelingKit_RemoteClient: queryTask response code: 405
2021-11-10 09:17:23.489 32513-3129/com.lvonasek.arcore3dscanner I/3DModelingKit_RemoteClient: queryTask response code: 405
2021-11-10 09:17:23.495 32513-3129/com.lvonasek.arcore3dscanner E/3DModelingKit_ResponseUtils: P*r*e *e*C*d* e*r*r*r*.j*o*.J*O*E*c*p*i*n: *o *a*u* f*r *e*C*d*
2021-11-10 09:17:23.501 32513-3129/com.lvonasek.arcore3dscanner I/3DModelingKit_HianalyticsLogProvider: forbiddenHiLog.getVenderCountry=eea
2021-11-10 09:17:23.501 32513-3129/com.lvonasek.arcore3dscanner I/3DModelingKit_HianalyticsLogProvider: forbiddenHiLog openHa = false

Since the beginning of this week many users of 3D Live Scanner report that processing queue takes longer than 30 minutes. What it be possible to allocate to service more resources?

Thank you in advance.

Create a decimal format using new DecimalFormat("0.00") will crash the app if the phone system uses comma as decimal separator. I recommend using the following approach: https://github.com/FStranieri/hms-3d-modeling-demo/commit/5df74ecf340825fcfefa7cdb31af3191cf958df1

Hi, I need help here, to test the capabilities of this HMS 3D modeling app, I have already multiple images 360deg view of the object stored in my phone, how do I manual upload the images to the app instead of using camera to take pictures?

I tested object modeling with TextureMode.PBR: `` Modeling3dReconstructSetting setting = new Modeling3dReconstructSetting.Factory() .setReconstructMode(Modeling3dReconstructConstants.ReconstructMode.PICTURE) .setTextureMode(Modeling3dReconstructConstants.TextureMode.PBR) .create();

        Modeling3dReconstructInitResult modeling3dReconstructInitResult;
        modeling3dReconstructInitResult = modeling3dReconstructEngine.initTask(setting);

When I download the reconstructed model there is diffuse texture only. I tested it with both OBJ and GLTF.

In 3D Live Scanner, users started complaining that the reconstruction does not work. I investigated into it and they keep receiving following error: get taskID error 1118: The request has reached the max limit

Would it be possible to extend the limit? The pro version of the app does not suffer from this issue.

Some devices (e.g. Samsung Galaxy Note 20 Ultra SM-N986B) do not work.

The issue is probably that cameratakelib opens all rear facing cameras at the same time which some devices do not support (I am waiting on user of my app to confirm this).

E/ActivityThread: Failed to find provider info for com.huawei.hms W/dynamic-api_DynamicModule: 3142-3142|null|com.huawei.hms.feature.dynamic.DynamicModule|getRemoteVersion|80|Query remote module:huawei_module_modeling3d_motioncapture exception:com.huawei.hms.feature.dynamic.DynamicModule$g: failed to Query remote version. E/AbstractInitializer: huawei_module_modeling3d_motioncapture -> No need to switch because the context of the dynamic module is null or the context of full sdk E/AbstractInitializer: huawei_module_modeling3d_motioncapture -> The context of the dynamic module belongs to LOCAL D/ImageSkeletonImpl: Initialize E/SkeletonDetectionJNI: loadLibrary failed. UnsatisfiedLinkError e: java.lang.UnsatisfiedLinkError: dlopen failed: library "libnative-lib.so" not found E/.hms.modeling3: No implementation found for int com.huawei.hms.motioncapturesdk.SkeletonDetectionJNI.createInstance(android.content.res.AssetManager, java.lang.String, java.lang.String, java.lang.String, java.lang.String) (tried Java_com_huawei_hms_motioncapturesdk_SkeletonDetectionJNI_createInstance and Java_com_huawei_hms_motioncapturesdk_SkeletonDetectionJNI_createInstance__Landroid_content_res_AssetManager_2Ljava_lang_String_2Ljava_lang_String_2Ljava_lang_String_2Ljava_lang_String_2) D/AndroidRuntime: Shutting down VM E/AndroidRuntime: FATAL EXCEPTION: main Process: com.huawei.hms.modeling3d, PID: 3142 java.lang.UnsatisfiedLinkError: No implementation found for int com.huawei.hms.motioncapturesdk.SkeletonDetectionJNI.createInstance(android.content.res.AssetManager, java.lang.String, java.lang.String, java.lang.String, java.lang.String) (tried Java_com_huawei_hms_motioncapturesdk_SkeletonDetectionJNI_createInstance and Java_com_huawei_hms_motioncapturesdk_SkeletonDetectionJNI_createInstance__Landroid_content_res_AssetManager_2Ljava_lang_String_2Ljava_lang_String_2Ljava_lang_String_2Ljava_lang_String_2) at com.huawei.hms.motioncapturesdk.SkeletonDetectionJNI.createInstance(Native Method) at com.huawei.hms.motioncapturesdk.a.initialize(ImageSkeletonImpl.java:12) at com.huawei.hms.motioncapturesdk.t.b.a(RemoteOnDeviceSkeleton.java:14) at com.huawei.hms.motioncapturesdk.Modeling3dMotionCaptureEngine.create(Modeling3dMotionCaptureEngine.java:13) at com.huawei.hms.motioncapturesdk.Modeling3dMotionCaptureEngineFactory.getMotionCaptureEngine(Modeling3dMotionCaptureEngineFactory.java:1) at com.huawei.hms.modeling3d.utils.skeleton.LocalSkeletonProcessor.(LocalSkeletonProcessor.java:65) at com.huawei.hms.modeling3d.ui.activity.SelectSourceVideoActivity.onCreate(SelectSourceVideoActivity.java:103) at android.app.Activity.performCreate(Activity.java:7994) at android.app.Activity.performCreate(Activity.java:7978) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1309) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3422) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3601) at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85) at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135) at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:223) at android.app.ActivityThread.main(ActivityThread.java:7656) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

Would it be possible to receive result with approximately correct scale?

Considering that the mobile camera focal length is provided you should be able to do the triangulation and calculate the scale of the model, right?