IMAGE Monarch Client keeps stopping

[ctejada10]

Hello!

I am trying to extend this application to support SVG/PDF loading from a web server in addition to local storage. However, when debugging and testing the resulting app on the Android Studio emulator and on the Monarch, it keeps closing immediately after opening (see emulator screenshot). This is also true with the source code currently present on the Main branch. Any ideas on what is happening and how to fix?

Many thanks in advance!

[jeffbl]

Thanks for the issue @ctejada10! The developer of the IMAGE Monarch Client is out of town right now, but will be back next week. If I had to guess, I'd say that this is likely due to us currently using a special version of the Monarch that does not have the Monarch Keysoft layer, and we have not tested with the full retail Monarch build that I assume you are using. I cannot access the emulator screenshot, but if there is anything relevant in the debug logs, please append to this issue.

Assigning to @VenissaCarolQuadros to take look when you return.

[ctejada10]

Thanks for the prompt reply and update! That makes sense—appreciate the context. Is there any workaround or temporary adjustment I could try in the meantime to get it working with the retail Monarch build? I am attaching (a lot of) execution logs when I run the app in the emulator.

monarch.log

Looking forward to @VenissaCarolQuadros’ insights when you’re back. Thanks again!

[jeffbl]

You should be able to get the log messages from the app via adb. If there is anything relevant there just before the app exits, that would help point us in the right direction. (I'm looking at the log you attached now)

I suspect it will be difficult to get working on a retail Monarch since the firmware we are currently using is also a different version of Android. We'd be very curious to hear more about what you're doing, and give any pointers we can. Feel free to email me (address in my profile) if you'd like to set up a time to do that.

[jeffbl]

@VenissaCarolQuadros it is trying to get the display size and failing:

java.lang.RuntimeException: Unable to start activity ComponentInfo{ca.mcgill.a11y.image/ca.mcgill.a11y.image.selectors.ModeSelector}: java.lang.NullPointerException: Attempt to invoke interface method 'int android.os.BrailleDisplay.getDotLineCount()' on a null object reference

I do not know if this is a difference in API between our firmware version and retail, but that is my guess.

[jeffbl]

@ctejada10 I am not familiar with doing this development in an emulator. Does the emulator have all of the Monarch software extensions? If not, then the problem may be different on the actual device, which may have the appropriate getDotLineCount() method.

[ctejada10]

This happens both on the emulator and the Monarch; however, I did compile the apk to send it over the Monarch (the Monarch is located at the university and I don't have access to it at the moment, a colleague helped me load the apk in). Would doing it this way instead of running directly from Android Studio cause these errors?

[jeffbl]

I don't think it would matter if it is a precompiled APK, but it would be useful to know if the error is the same when running on actual Monarch hardware. If the emulator you're using is exactly like the Monarch hardware, then error should be the same. (I don't want to waste your time doing tests due to my ignorance on this.) Probably best to wait until Venissa is back next week, since this is not a component I have worked on directly.

[ctejada10]

I understand and I appreciate the help! I really doubt that the emulator is anything close to the Monarch--it's the basic "Android tablet" from Android Studio. I might give it another try with the Monarch (remotely) running it through Android Studio and will report back.

Thanks again!

[jeffbl]

Got it. Yeah, a generic tablet emulator will be nothing like running on the actual device. If it is quitting on the actual Monarch as well, the problem could be elsewhere, so if you do get those logs, that would be helpful.

[ctejada10]

Understood! I'll try running from Android Studio to capture the logs (Would this be the correct way of capturing them? This is my first time developing anything on Android)

[jeffbl]

Probably the easiest way, yes. (FYI I haven't done any serious Android development in around 7 years, so I don't know how things have changed in that time...)

[ctejada10]

Understood! I appreciate all the help, regardless!

[VenissaCarolQuadros]

Hi @ctejada,
The issue you're encountering is due to the fact that a standard Android tablet on the emulator doesn't have access to a system-level service that's available on our Monarch build. Unfortunately, we currently have no workaround for this.
That said, as @jeffbl mentioned, we haven’t tested on a retail Monarch unit. There’s a chance that device might still have access to the required service. If you're able to retrieve the application logs from that device and this issue isn’t the root cause, we may be able to help figure out what is going wrong, and if there are any solutions