This application practically never works on Galaxy S9 FE

[wlinna]

Hello, I just installed the software on my tablet. I gave Nabla accessibility permissions and added it to battery saving exceptions. Nabla says the service is on. The problem is that 99 % of the time the application doesn't work at all.

For example, if I input .alpha., I might get the desired unicode character, but most of the time I will not. I have never been able to make something like .x^2. work, and .x_2. has worked only twice. I have tried with both a physical keyboard and the touch screen. I use Gboard by the way. I have tried at least two different programs but neither of them work consistently with Nabla.

I installed Nabla from Play, and I'm running version 1.3.4 on Android 14 One UI 6.0.

[ray-pH]

Yeah, unfortunately, this is a common issue. The app is just broken on some phones, while it works just fine on others.

unfortunately, I don't have easy access to those phones where I can test and investigate something. I'll see if I can try to get my hands on those phones/emulator. But It might be a while

[ray-pH]

Wait a minute, just to make sure, did you turn off the Quick Mode? Because since 1.2, the default setting is with the Quick Mode turned on. In that mode, you don't write .alpha.<space> but .alpha<space>

[wlinna]

Thank you for your responses. I tested with both Quick Mode turned on and off. Sometimes Quick Mode worked, sometimes "Slow" Mode worked. I wasn't able to establish any pattern, unfortunately.

[ray-pH]

Okay, thanks for the info

[wlinna]

Just tested with Samsung Keyboard, but it didn't work any better, unfortunately

[ray-pH]

I tried running the app in the Samsung Remote Test Lab, and I didn't experience any issue

[ray-pH]

Are you comfortable with running a debug version of the apk?

I'm interested in seeing the debug message like these

If not, that's okay. I'll try to figure out something else

[wlinna]

I guess I could do it . How would I get the debug messages out? And where can I get a debug APK (without setting up an Android toolchain)

I wonder if having multiple languages has anything to do with it. Or maybe I need to turn off and on again :P

[ray-pH]

I just remembered that on the early version of the app, there's a weird quirk where if you have Typing Hero installed and enabled, it'll help Nabla works. I think that quirk should be gone in the later version, but maybe you can try that first.

[wlinna]

I'm not very comfortable installing proprietary software (Typing Hero) that has access to my keystrokes across the system, but thanks for the recommendation :)

[ray-pH]

I guess I could do it . How would I get the debug messages out?

I think the only way is via ADB. Are you familiar with that? I tried checking some logcat apps, but none of them seems to pick up the log from an AccessibilityService

[ray-pH]

Does the app stop working immediately, or does it take a while until the service stops working?

[wlinna]

It seems to stop working almost immediately. Just now:

1. I went to the settings and changed the start and end string to ...
2. I switched to Joplin (already open),
3. Wrote ..alpha.., pressed space, and got the Greek alpha letter that I wanted.
4. Then I pressed enter, and wrote ..x^2.., press space, but nothing happens.
5. I emptied the line
6. I wrote ..alpha.., but it didn't work anymore, so I removed it.
7. I wrote ..x^2.. again
8. I switched to Nabla settings and pressed "Save string".
9. I quickly switched back to Joplin, and pressed space after ..x^2.., and I got x²
10. I tried ..alpha.., but it didn't work anymore

I don't seem to have this problem on my Galaxy A54 5G which has pretty much all the same keyboard and accessibility settings .

[wlinna]

I guess I could do it . How would I get the debug messages out?

I think the only way is via ADB. Are you familiar with that? I tried checking some logcat apps, but none of them seems to pick up the log from an AccessibilityService

Not very familiar, but I don't suppose it will be too hard. I might try that on Sunday

[ray-pH]

I've been able to recreate the issue. It's somehow app-specific. The issue started happening when I used Chrome (weirdly enough chrome in my phone works fine, that issue only occurs in Samsung), and maybe I'll check Joplin next.

I think I can investigate myself from there.

I'm out of free daily credits on Samsung Remote Test Lab right now, I'll test again later