The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Solved
Rescue + Mobile for Android Crashes on Samsung Tab A with Android 8.1 (Oreo)
Chrome is set as default browser
All apps are up to date
Google Account is signed in and all play services updates are applied
Install Rescue + Mobile for Android
Launch Rescue + Mobile for Android
Agree to Samsung Knox Terms and Conditions
Activate Device Administration privelages for Rescue + Mobile for Android
Open Rescue + Mobile for Android
Enter 6 digit PIN (Generated by Rescue Technician with Mobile License from Desktop Console)
Rescue + Mobile for Android then opens, displays connecting Notification and Chat then Waiting for Technician Notification and Chat then a message that Rescue + Mobile for Android has stopped.
System Maintenance app shows that it was a Forced Stop.
I have tried many different combinations of Android Security settings, including disabling Secure Folder, but could not find any device settings that affected the crash.
I suspect this is an issue that LogMeIn must fix in the app.
Hello again!
The possible fix is available on Live, the new Android applet version is 7.11.8.
Please feel free to try it and give us a feedback whether it solves the issue.
Regards,
Sandor
14 Replies
Great news!
Have a nice day!Thank you!
We have tested the update and it now works.
Hello again!
The possible fix is available on Live, the new Android applet version is 7.11.8.
Please feel free to try it and give us a feedback whether it solves the issue.
Regards,
SandorI have discussed it with the DEV team and the investigation has started. At this point I cannot tell any ETA, but I will provide it as soon as possible.
Thank you for your understanding.
Regards,
SandorWe cannot attempt this method.
1) It is a tablet, not a phone.
2) Alternate method involves rooting the device, which is not an option.
Thank you for your extra info, very useful!
The unknown baseband is a kind of common Samsung issue, I found this article, could you try it?
https://androidflagship.com/33304-restore-null-imei-fix-not-registered-on-network-galaxy-s9sv5 I have a full log file and we have reviewed it. The issue we believe is related to the Samsung Experience version 9.5 returning a NULL value for the baseband version. This field is required by Rescue + Mobile for Android and crashes on the NULL value for baseband version.
In the Settings > About tablet > Software Information we expect to see the baseband version but no baseband section is even available.
Samsung Galaxy Tab A (2017) - SM-T380
Android Version: 8.1.0
Samsung Experience Version: 9.5
Here is the bugreport data for the crash event:
"01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-1
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: Process: com.logmein.rescuemobile, PID: 4332
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: com.google.inject.ProvisionException: Unable to provision, see the following errors:
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime:
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: 1) Map injection failed due to null value for key "OS.BASEBANDNUMBER", bound at: com.logmein.rescuesdk.internal.session.DefaultSessionParamsMapModule$OsVersionMapModule.provideBaseband() (via modules: com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$CombinedModule -> com.logmein.rescuesdk.internal.session.DefaultSessionParamsMapModule$OsVersionMapModule)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at com.lmi.rescue.comm.AppletSessionParams.configure(SourceFile:78) (via modules: com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> com.lmi.rescue.inject.AppletSessionModule -> com.lmi.rescue.comm.AppletSessionParams -> com.google.inject.multibindings.MapBinder$RealMapBinder)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: while locating java.util.Map<java.lang.String, java.lang.String> annotated with com.logmein.rescuesdk.internal.session.FeatureMap()
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: for the 2nd parameter of com.logmein.rescuesdk.internal.session.DefaultSessionParamsMapModule.provideEnrichedSessionParameterMap(Unknown Source)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: while locating java.util.Map<java.lang.String, java.lang.String> annotated with com.logmein.rescuesdk.internal.session.FeatureMapWithDisabledUnsupportedFeatures()
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime:
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: 1 error
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at com.google.inject.internal.InjectorImpl$2.get(SourceFile:1028)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at bpy.a(SourceFile:211)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at btf.i(SourceFile:123)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at btf.c(SourceFile:114)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at bqe.g(SourceFile:68)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at bqe.c(SourceFile:38)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at bqf.run(Unknown Source:2)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
01-07 08:28:04.963 10147 4332 5169 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)"Tried twice with tablet in Landscape mode and it had the same issue.
Could you verify me whether the applet crashes while the tablet in landscape mode?
