Keyboard often gets stuck with a key down.

[Fortyseven]

What the title says. I haven't been able to reliably reproduce it, but once every couple minutes a key will get stuck, causing a long string of letters (or backspaces, or spaces, etc) to spew forth until the same key is pressed again.

(Using a Samsung Galaxy S21 Ultra on Android 11.)

[yourealwaysbe]

Argh. What are your settings for Show/Hide In-App Keyboard and Movement Style?

I guess the basic reason will likely be that the ACTION_UP event is not being delivered to the keyboard. Is the keyboard being hidden while the key is still down? Maybe some other part of the screen is being touched?

I wonder if it might also be a concurrency bug. Are you able to build/install Forkyz from here? I could make a branch with some debugging / experiments to try and track it down. Else i could send you an apk to install.

[yourealwaysbe]

Reviewing the code, there was a possibility of a concurrency error. I can't see why this would have caused the behaviour you describe, but concurrency bugs are funny things. I've protected against the possibility now, and the update is in Version 8, which should be on F-Droid soonish. Let me know if the problem continues after update.

[Fortyseven]

I know I'm a bit late getting back to you about the settings (day job project has been beating me up), and you've already pushed an update (I'll keep an eye out for it). But just for completeness:

• Show/Hide In-App Keyboard == Always Show
• Movement Style == Next clue in same direction

I've been trying to observe what I'm doing when it happens, like maybe I'm hitting two at once, or I'm sliding off one key and onto another, etc. And sometimes that's true, but not always.

Anyway, I'll give it a go when it shows up and report back. 🥃

[yourealwaysbe]

No problem -- finding time can be tricky. Thanks for the settings info, i can play with that and see if i start to see the issue on my end.

[ckcin]

I just switched over to forkyz from the original shortyz and have the same issue on my pixel 4A. For me it typically only happens when pressing the letter P on the top half of the puzzle

[yourealwaysbe]

Dang. I guess the concurrency fix didn't help. I'm notable to reproduce this on my end. Are you able to compile/install Forkyz from source (or i could send you versions to install)? We could try some experiments to narrow it down. -- Sent from my phone: apologies for poor formatting and bizarre typos...

[ckcin]

I installed via F-Droid, is it possible the version there is out-of-date?

as for compiling... not at the moment, on my todo list, but I can definitely sideload a precompiled package.

This said, the issue doesn't happen everytime. in the last case, I deleted the puzzle and redownloaded and it worked. Is it possible that there is an issue during downloading? Also it happens most often with the USA Today puzzles, I don't think I've seen it with any of the puzzles I manually download an open with the app.

[yourealwaysbe]

I installed via F-Droid, is it possible the version there is out-of-date?

F-Droid should have the fix i tried. I have another idea though which i'll implement after i've finished another keyboard change (essentially my code assumes it will get a key ACTION_UP, but ACTION_CANCEL is another possibility if you've started some kind of gesture during the button press).

as for compiling... not at the moment, on my todo list, but I can definitely sideload a precompiled package.

Thanks. I'll put one up somewhere on here when there's one to be tested.

This said, the issue doesn't happen everytime. in the last case, I deleted the puzzle and redownloaded and it worked. Is it possible that there is an issue during downloading? Also it happens most often with the USA Today puzzles, I don't think I've seen it with any of the puzzles I manually download an open with the app.

It would be odd if the puzzle itself was causing the issue as there's no flow of information from the puzzle to the keyboard. At least not that i'm aware of, but then bugs come from unexpected places almost by definition.

[yourealwaysbe]

Here is a version with the ACTION_CANCEL handled forkyz.apk.zip. Let me know if the problem persists.

[ckcin]

installed... I'll keep you posted.

On Thu, Aug 26, 2021 at 11:29 AM yourealwaysbe @.***> wrote:

Here is a version with the ACTION_CANCEL handled forkyz.apk.zip https://github.com/yourealwaysbe/forkyz/files/7060868/forkyz.apk.zip. Let me know if the problem persists.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-906514075, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXHUXNIPLO7WKBMC73LT6ZMUFANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[ckcin]

Just happened again...and again the 'p' key. Are there any logs I can grab for you?

-Nick

On Thu, Aug 26, 2021, 12:23 PM Nick Carrasco @.***> wrote:

installed... I'll keep you posted.

On Thu, Aug 26, 2021 at 11:29 AM yourealwaysbe @.***> wrote:

Here is a version with the ACTION_CANCEL handled forkyz.apk.zip https://github.com/yourealwaysbe/forkyz/files/7060868/forkyz.apk.zip. Let me know if the problem persists.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-906514075, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXHUXNIPLO7WKBMC73LT6ZMUFANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[yourealwaysbe]

Just happened again...and again the 'p' key. Are there any logs I can grab for you?

Bargh. Thanks for trying.

Do you know how to grab logcats? If so i can put in some debug statements. Otherwise i could hack in something to log to a file.

[ckcin]

I've done it before.. I'll look it up. I know I have the developer options currently disabled on this device, but can turn it on.

-Nick

On Thu, Aug 26, 2021, 3:49 PM yourealwaysbe @.***> wrote:

Just happened again...and again the 'p' key. Are there any logs I can grab for you?

Bargh. Thanks for trying.

Do you know how to grab logcats? If so i can put in some debug statements. Otherwise i could hack in something to log to a file.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-906696335, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXD44IWAONAZU2TPF6DT62LGHANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[yourealwaysbe]

Coo, thanks. Here is a version that does some logging: forkyz.apk.zip

You can limit the logcat to lines containing "ForkyzKeyboard" if you want to filter other data out.

[yourealwaysbe]

Perhaps clutching at straws a bit, but here's another version that also "consumes" the possible intermediate touchscreen events between the ACTION_DOWN and ACTION_UP sequence. It's possible that if you don't consume an intermediate event, the system stops sending any events in the sequence. I can't see anything in the Android documentation about this, but people on stack overflow have various opinions on it.

It also has the logging code in case the problem persists.

forkyz.apk.zip

[ckcin]

So if been waiting to email you with a log, but at this point with the last day of changes you put in, I haven't had the error again. Been doing at least 1 if not 2-3 puzzles a day. If you want the log let me know and I'll prepare to extract it after my next puzzle.

-Nick

On Fri, Aug 27, 2021, 5:32 AM yourealwaysbe @.***> wrote:

Perhaps clutching at straws a bit, but here's another version that also "consumes" the possible intermediate touchscreen events between the ACTION_DOWN and ACTION_UP sequence. It's possible that if you don't consume an intermediate event, the system stops sending any events in the sequence. I can't see anything in the Android documentation about this, but people on stack overflow have various opinions on it.

It also has the logging code in case the problem persists.

forkyz.apk.zip https://github.com/yourealwaysbe/forkyz/files/7065843/forkyz.apk.zip

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-907066096, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXACYJHYTZGIPKH3P3TT65LUXANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[yourealwaysbe]

I haven't had the error again...

That sounds promising. Thanks for the update. Hopefully it doesn't come back :)

If you want the log let me know...

If the problem isn't happening, there's no need for the log.

[ckcin]

I spoke too soon... It happened again last night, but by the time I got up this morning.... either the logs had cleared themselves or it didn't write anything to the logs.. I deleted the puzzle and redownloaded it... I'll try that one again later this morning to see if it was specific to the puzzle or just an anomaly.

I'll keep you posted.

On Tue, Aug 31, 2021 at 6:36 AM yourealwaysbe @.***> wrote:

I haven't had the error again...

That sounds promising. Thanks for the update. Hopefully it doesn't come back :)

If you want the log let me know...

If the problem isn't happening, there's no need for the log.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-909113768, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXEI7G3ZL7NK6Z3Y2UDT7SWC5ANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[yourealwaysbe]

I spoke too soon... It happened again last night, but by the time I got up this morning.... either the logs had cleared themselves or it didn't write anything to the logs..

I thought it might -- these kind of bugs like to hide until you think they've gone. The logcat buffer isn't that big, which means you usually have to grab them fairly soon after the bug, which isn't ideal for a bug that happens once per week.

You can try installing a logcat reader on your phone. There's one on fdroid, but you need to do a bit of ADB jiggery pokery for it to work.

Otherwise, i can set up Forkyz to write the logs to its own file somewhere, but inevitably it's not as straightforward as i'd hoped. Which version of Android are you on?

[yourealwaysbe]

So here's one version that logs to a file: forkyz.apk.zip

edit: i realise you can't downgrade the loggin one without clearing all app data, so here's one without logging that can be installed over it: forkyz.apk.zip

The logging one saves to the app's internal storage, so it might be tricky to get access to. Once installed, click a few keys, then try

$ adb pull /data/data/app.crossword.yourealwaysbe.forkyz/files/debug.log

and then look inside the fetched debug.log to see if it has a bunch of key presses. E.g.

1630585274634: touch keyCode=34 action=1 actionMasked=1
1630585274635: handled: true
  2131296519: null
  2131296520: null
  2131296521: null

Trouble is, it might get large, so if you notice the app slowing down, you can clear it with (you probably want to be super careful with this command to make sure you're not deleting a different file!)

$ adb shell rm /data/data/app.crossword.yourealwaysbe.forkyz/files/debug.log

You might need to be using ADB as root:

$ adb root

[ckcin]

I'll have to try that one. I went with matlog libre, the material fork of catlog which I used to use a long time ago, but it too seems to have gone dormant. I'm all set with the adb permissions so I should be able to trap the logs next time it happens.

-Nick

On Thu, Sep 2, 2021, 8:02 AM yourealwaysbe @.***> wrote:

I spoke too soon... It happened again last night, but by the time I got up this morning.... either the logs had cleared themselves or it didn't write anything to the logs..

I thought it might -- these kind of bugs like to hide until you think they've gone. The logcat buffer isn't that big, which means you usually have to grab them fairly soon after the bug, which isn't ideal for a bug that happens once per week.

You can try installing a logcat reader on your phone. There's one on fdroid https://www.f-droid.org/en/packages/com.dp.logcatapp/, but you need to do a bit of ADB jiggery pokery for it to work https://github.com/darshanparajuli/LogcatReader#usage.

Otherwise, i can set up Forkyz to write the logs to its own file somewhere, but inevitably it's not as straightforward as i'd hoped. Which version of Android are you on?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-911594775, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXDPAYN6EVT4NUXOXT3T75RULANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[yourealwaysbe]

Ok, maybe it still works. Might be worth just opening forkyz and clicking a few keys, then checking right after if matlog shows anything in the logs. It should have some output with the ForkyzKeyboard tag.

[ckcin]

Just had the arrow key "stick" attached is the log filtered on forkyz

-Nick

On Thu, Sep 2, 2021, 9:30 AM yourealwaysbe @.***> wrote:

Ok, maybe it still works. Might be worth just opening forkyz and clicking a few keys, then checking right after if matlog shows anything in the logs. I should have some output with the ForkyzKeyboard tag.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-911685222, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXAOSM3WNF33RNJKWBTT75355ANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

<<< log_count = 14 >>> [09-02 20:32:12.438 1582:3919 I/ActivityTaskManager] START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.BrowseActivity bnds=[641,304][844,635]} from uid 10239

[09-02 20:32:12.494 1582:1684 I/ActivityManager] Start proc 23068:app.crossword.yourealwaysbe.forkyz/u0a376 for pre-top-activity {app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.BrowseActivity}

[09-02 20:32:14.060 1582:1582 D/NotificationService] 0|app.crossword.yourealwaysbe.forkyz|0|null|10376: granting content://settings/system/notification_sound

[09-02 20:32:14.062 1582:1582 D/NotificationService] 0|app.crossword.yourealwaysbe.forkyz|0|null|10376: granting content://settings/system/notification_sound

[09-02 20:32:16.342 1582:2709 I/ActivityTaskManager] START u0 {cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} from uid 10376

[09-02 20:36:06.600 1582:1666 W/NotifHistoryProto] notification package name (app.crossword.yourealwaysbe.forkyz) not found in string cache

[09-02 20:36:06.600 1582:1666 W/NotifHistoryProto] notification channel id (forkyz.downloads) not found in string cache

[09-02 20:41:16.238 1582:2205 I/ActivityTaskManager] START u0 {cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PuzzleFinishedActivity} from uid 10376

[09-02 20:41:16.356 1582:1682 I/ActivityTaskManager] Displayed app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PuzzleFinishedActivity: +118ms

[09-02 20:41:19.482 1582:1667 I/ActivityManager] Killing 23068:app.crossword.yourealwaysbe.forkyz/u0a376 (adj 905): remove task

[09-02 20:41:19.546 1582:4011 I/WindowManager] WIN DEATH: Window{84ba59 u0 app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.BrowseActivity}

[09-02 20:41:19.547 1582:4011 W/InputDispatcher] Attempted to unregister already unregistered input channel '84ba59 app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.BrowseActivity (server)'

[09-02 20:41:19.551 1582:3919 I/WindowManager] WIN DEATH: Window{ee5963d u0 app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity}

[09-02 20:41:19.551 1582:3919 W/InputDispatcher] Attempted to unregister already unregistered input channel 'ee5963d app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity (server)'

[yourealwaysbe]

Thanks for this. Unfortunately it's not quite what i need. It's showing the system events /about/ Forkyz, rather than the debug log of Forkyz.

I had a play with the logcat reader from darshanparajuli (available on F-Droid) and discovered it's not easy to get the right settings. At first i had to give the required permissions:

adb shell "pm grant com.dp.logcatapp android.permission.READ_LOGS"
adb shell "am force-stop com.dp.logcatapp"

and then i had to get the right filter. Just searching for the Forkyz keyword didn't work. I had to set the "tag" specifically to ForkyzKeyboard, like so:

and then the logs would give the keyboard debug info:

If your app has recorded the logs, it's possible that you can get this output just by picking a different filter. Else, you could try the same logcat read i did.

(Sorry this is turning into a mission!)

[ckcin]

I've set the tag up and will wait for the next occurrence.

As for the mission aspect, no worries, I'm a sw engineer and don't mind digging through logs and such. And besides, helping debug an open source app if the least I can do given that the work you are doing is for free.

-Nick

On Fri, Sep 3, 2021, 4:41 AM yourealwaysbe @.***> wrote:

Thanks for this. Unfortunately it's not quite what i need. It's showing the system events /about/ Forkyz, rather than the debug log of Forkyz.

I had a play with the logcat reader from darshanparajuli https://github.com/darshanparajuli/LogcatReader (available on F-Droid) and discovered it's not easy to get the right settings. At first i had to give the required permissions:

adb shell "pm grant com.dp.logcatapp android.permission.READ_LOGS" adb shell "am force-stop com.dp.logcatapp"

and then i had to get the right filter. Just searching for the Forkyz keyword didn't work. I had to set the "tag" specifically to ForkyzKeyboard, like so:

[image: Screenshot showing tag setting] https://user-images.githubusercontent.com/372397/131976767-10db53c1-373c-4a65-9386-3cd9c876bb49.png

and then the logs would give the keyboard debug info:

[image: Screenshot showing correct debug info] https://user-images.githubusercontent.com/372397/131976852-48139eee-53ca-4901-be67-8d19f25b8f6b.png

If your app has recorded the logs, it's possible that you can get this output just by picking a different filter. Else, you could try the same logcat read i did.

(Sorry this is turning into a mission!)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-912368246, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXBUD3ZAOIUXO6R4X4LUACC5FANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[yourealwaysbe]

I had a play with MatLog and it seems to show the right log output for me, and just searching for ForkyzKeyboard was enough. Do you see something similar to this if you press a few keys on Forkyz then check the log? The MatLog documentation doesn't make explicit that you need to restart the app after giving the READ_LOGS permission via adb.

[ckcin]

Just happened again...I hope this time I got the log right

-Nick

On Fri, Sep 3, 2021, 9:43 AM yourealwaysbe @.***> wrote:

I had a play with MatLog and it seems to show the right log output for me, and just searching for ForkyzKeyboard was enough. Do you see something similar to this if you press a few keys on Forkyz then check the log? The MatLog documentation doesn't make explicit that you need to restart the app after giving the READ_LOGS permission via adb.

[image: Screenshot of MatLog logs with ForkyzKeyboard messages] https://user-images.githubusercontent.com/372397/132014995-9de4b55c-2769-401c-818f-3f0f18f07fac.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-912550555, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXHYVMTQ5B2LBOAJEVDUADGH3ANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

<<< log_count = 30 >>> [09-12 03:58:47.805 1722:3906 I/ActivityTaskManager] START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.BrowseActivity bnds=[439,1838][642,2021]} from uid 10239

[09-12 03:58:47.847 1722:1958 I/ActivityManager] Start proc 22856:app.crossword.yourealwaysbe.forkyz/u0a376 for pre-top-activity {app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.BrowseActivity}

[09-12 03:58:50.414 1722:5669 I/ActivityTaskManager] START u0 {cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} from uid 10376

[09-12 04:09:23.254 1722:4520 I/ActivityTaskManager] START u0 {cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PuzzleFinishedActivity} from uid 10376

[09-12 04:09:46.737 1722:4046 I/ActivityTaskManager] START u0 {cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} from uid 10376

[09-12 04:14:09.300 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 23 lines

[09-12 04:14:22.280 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 13 lines

[09-12 04:15:04.190 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 23 lines

[09-12 04:15:21.171 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 15 lines

[09-12 04:15:55.316 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 15 lines

[09-12 04:16:08.870 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 21 lines

[09-12 04:16:21.441 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 18 lines

[09-12 04:16:33.589 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 24 lines

[09-12 04:16:49.803 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 18 lines

[09-12 04:17:03.406 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 27 lines

[09-12 04:17:18.572 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 30 lines

[09-12 04:17:33.710 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) expire 264 lines

[09-12 04:17:44.739 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 4 lines

[09-12 04:17:46.751 1722:6053 I/ActivityTaskManager] START u0 {cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} from uid 10376

[09-12 04:24:09.877 1722:2336 D/InputDispatcher] Waiting to send key to Window{38723c u0 app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} because there are unprocessed events that may cause focus to change

[09-12 04:24:09.878 1722:2336 D/InputDispatcher] Waiting to send key to Window{38723c u0 app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} because there are unprocessed events that may cause focus to change

[09-12 04:24:14.963 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-12 04:24:15.020 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-12 04:24:15.094 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-12 04:24:15.159 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-12 04:24:15.233 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-12 04:24:15.308 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-12 04:24:15.383 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-12 04:24:15.459 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-12 04:24:15.534 22856:22856 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[matthewhague]

Thanks for that. It still doesn't appear right: instead of the Forkyz debug output, it says things like "expire x lines". Perhaps that's a MatLog thing with old output getting erased?

However, these bits are intriguing:

Waiting to send key to Window{38723c u0 app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} because there are unprocessed events that may cause focus to change

When i have more time i'll look into what could be causing that.

[ckcin]

I actually switched to the logcat tool you recommended. So maybe I need to play with the filter some more. Also I updated to the latest version that got posted to FDroid, does that version have the added logging? Or do you want me to reinstall the last zipfile version you sent me?

-Nick

On Wed, Sep 15, 2021, 6:45 PM matthewhague @.***> wrote:

Thanks for that. It still doesn't appear right: instead of the Forkyz debug output, it says things like "expire x lines". Perhaps that's a MatLog thing with old output getting erased?

However, these bits are intriguing:

Waiting to send key to Window{38723c u0 app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} because there are unprocessed events that may cause focus to change

When i have more time i'll look into what could be causing that.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-920440122, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXCSQWZL4BFY7QLAIXTUCEOYRANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[yourealwaysbe]

The latest version on FDroid doesn't have logging (it generates a lot of log output). The last zip file version is probably best.

I haven't used that logcat app for much more than monitoring logs on the fly. Perhaps the logs need to be collected soon after to avoid them "expiring"?

[ckcin]

New logfile... Just got stuck on the "p" character again

On Thu, Sep 16, 2021, 9:07 AM yourealwaysbe @.***> wrote:

The latest version on FDroid doesn't have logging (it generates a lot of log output). The last zip file version is probably best.

I haven't used that logcat app for much more than monitoring logs on the fly. Perhaps the logs need to be collected soon after to avoid them "expiring"?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yourealwaysbe/forkyz/issues/26#issuecomment-920884797, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQXGV5NI2OG3EOGW52DDUCHTZXANCNFSM455FBFBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

-Nick

<<< log_count = 11 >>> [09-22 21:15:47.941 1609:3597 I/ActivityTaskManager] START u0 {cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PuzzleFinishedActivity} from uid 10376

[09-22 21:16:04.509 1609:3844 I/ActivityTaskManager] START u0 {cmp=app.crossword.yourealwaysbe.forkyz/app.crossword.yourealwaysbe.PlayActivity} from uid 10376

[09-22 21:21:54.425 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-22 21:21:54.496 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-22 21:21:54.572 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-22 21:21:54.646 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-22 21:21:54.721 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-22 21:21:54.796 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-22 21:21:54.872 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-22 21:21:54.947 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[09-22 21:21:55.022 811:811 I/chatty] uid=10376(app.crossword.yourealwaysbe.forkyz) identical 1 line

[matthewhague]

Hi, thanks for persisting. However, these are still not the right logs. I'm not sure what is happening with your logcat app, but it does not include the actual logging output of the app.

With Logcat Reader, this is a screenshot of what i am hoping to see. Notice that it includes output such as "touch keyCode=47...". Perhaps you have the wrong search filter? I am just searching for the text "ForkyzKeyboard".

A saved version of the log is logcat_09-23-2021_09-26-05.txt

Here is Version 12 of Forkyz that produces the output i need in case you don't have the right one from the various versions i posted: forkyz.apk.zip

[dtoxic47]

Sorry for a bit of topic question (did not want to open a new issue) is there a way to use the Default (Samsung) keyboard? cant seem to find the setting (if there is one)

[yourealwaysbe]

Sorry for a bit of topic question (did not want to open a new issue) is there a way to use the Default (Samsung) keyboard? cant seem to find the setting (if there is one)

I removed that option when i discovered Android keyboards don't really work on the level of key presses, but instead by insertion, edit, removal of chunks of text. Many deliver the key presses anyway, but some don't (e.g. #16). Forcing the native keyboard was a bit hacky anyway, so i went for just a built in keyboard.

Making a crossword app that works with Android input methods would ultimately be nicer, but i haven't had the ideas or time to figure out how to do that nicely.

[dtoxic47]

hmm ok, i am asking because i used Shortyz and the native keyboard worked just fine,anyway do consider adding that option at some point in future if possible

[jancborchardt]

@Fortyseven @ckcin @matthewhague @dtoxic47 you might not have seen this, but @yourealwaysbe graciously added an option to use the native keyboard, which could possibly resolve issues you were seeing?

[Fortyseven]

I'll check it out! :sunglasses:

Now that you mention it, though, I should probably note that I haven't been experiencing the originally reported issues for a while. I don't know when it stopped happening, exactly. I just kind of did and it snuck up on me.

So far the entire app has felt solid as hell. :beers:

[yourealwaysbe]

Thanks, i'll close this for now. Let me know if it reappears.