Crashes due to having no code for numpad

[Thewisem]

I have had a crash where the app crashed due to not having a number pad. I would advise to make a keyboard along with the original keyboard which had numbers and signs only. Because some apps will ask for that specific number pad. Some apps only request numbers and not letters. So this would be helpful
:)

[jnnkB]

By numpad do mean this?

Because it seems to exist…

[ndts55]

@Thewisem , can you reproduce the bug? If so, can you describe how to do so?

[Thewisem]

Really

[Thewisem]

Mind explaining this?

[Thewisem]

[Thewisem]

This was a situation which required a numpad

[Thewisem]

And yet it crashed

[Thewisem]

That black screen was what occured when i cliked on that verification bar. Then I went to google and clicked on that bar and it went back to normal. After going to that bar, I went back to this bar and clicked. It stopped working. I think your numpad doesn't adjust to landscape mode and crashes.

[NoahAndrews]

No need to have a hostile tone. They just pointed out that in some circumstances the numpad works fine, and asked how to reproduce the issue. No one accused you of lying.

[Thewisem]

Oh dame, did I came off as that. Sorry, dame didn't want to tone it that way. I wanted to come off as someone who was just curious. I thought I only had the problem. So I thought they might have had an explanation. Sorry Sorry if it came off as being rude. Really didn't want that impact.

[Thewisem]

I said really for the second comment ao as to suggest whether that was the case. It came off after third comment because I didn't have a situation where I needed to use it. :( .

[Thewisem]

I only put my guess on why and I have no clue. I just put an opinion and guessed. Hope this helps :)

[Thewisem]

By numpad do mean this?

Because it seems to exist…

Sorry I wanted to continue from this

[NoahAndrews]

No worries, I'm glad you didn't mean it that way.

As you can see, that works fine for me.

What Android device, version, and web browser are you using?

[Thewisem]

Hmmm see my comment. Try doing that in landscape mode

[Thewisem]

I think it isn't working in landscape mode

[NoahAndrews]

I promise you that it's far more likely to be an incompatibility between OpenBoard and your specific version of Android and/or the browser. Or maybe the fact that it's a tablet, though that seems less likely to me.

[Thewisem]

Hmmm Ok.
Device: Samsung Galaxy Tab A SM P555.
OS: Android 7.1.1 Nougat
Rooted: No
Orientation: Landscape
Browser: Bromite latest version

[Thewisem]

Unfortunately, I can't give crash reports as it doesn't have a crash reporting function like newpipe.

[jnnkB]

If you want to try investigating further you could try finding something relevant in the Logs using some tool like SysLog. But I'm no expert and I don't know how this app works internally so you might find nothing at all.

(I did not fully understand every one of your messages since I'm not a native speaker. If I seemed rude I didn't want to. Just trying to help debugging this problem.)

[NoahAndrews]

The most helpful debugging data you can gather is probably the Logcat logs. Run adb logcat (you'll have to download the Android Platform Tools), cause the crash, and then see what Logcat printed.

[Thewisem]

Uhhhhhhh

[Thewisem]

I don't have a computer

[jnnkB]

You could still try using SysLog since its simply an android app. It also contains the logcat.

[NoahAndrews]

That app needs a special permission though... which you grant from a computer using adb.

[jnnkB]

Oh Ok. Didn't know that.

[dslul]

I can confirm this bug, I managed to reproduce it on an old nexus 7. It seems to be an issue with themes, the old holo white and blue work correctly.

[dslul]

fixed 6796bd8. @Thewisem Sorry for taking so long.

[Thewisem]

No worries. Happy to help. Thankful that you noticed my problem. :). Will comment whether I find it working.

[Thewisem]

When you update the app, please do tell. I will be happy to test it out. Thanks for fixing my issue

[phatpaul]

My openboard is crashing when trying to pair to a BluetoothLE device which requires entry of a 6-digit PIN. I'm guessing it's related to this bug, so I'm not opening a new ticket. Is this fix included in a release yet? I just updated to version 1.4.3 on F-droid, but it didn't fix the problem.

FYI I'm running Android 8.1.0 on a Lenovo TB-8504F.

[jnnkB]

AFAIK it's not included in any release yet. So you'll probably have to wait until the next release.

[Thewisem]

Yeah still not fixed

[Thewisem]

[Thewisem]

Reopen this thread. Cause it isn't fixed. I forgot but thanks to your comment I checked it out. It still isn't working

[jnnkB]

Since @dslul already fixed it in the code and just didn't release a new version yet I think we can leave this issue closed. Or did you test it by compiling from source?

[dslul]

I haven't pushed the update yet, I'll try to do it this weekend.