Launching a widget after swiping up for home has a 5 second delay

[trygveaa]

Problem description

If you use gestures navigation and try to launch a widget after swiping up to go home, it takes 5 seconds before Termux appears.

Steps to reproduce

1. Use Android 10 and make sure it's set to use gesture navigation
2. Open any app. (I don't think it matters which app you open, it happens for me with all I've tested, including Chrome and Termux itself.)
3. Swipe up to go to the home screen.
4. Click on the widget to launch it.

Expected behavior

Termux should launch immediately, like it does when you use button navigation.

Additional information

• Termux application version: Built from master (commit b943e8a of widget and 9b7c710 of app), but I'm pretty sure it happens for the released versions as well.
• Android OS version: 10
• Device model: Pixel 3

[trygveaa]

I found these posts which talk about the issue. However, the workaround with using a pending intent doesn't seem to work anymore.
https://stackoverflow.com/questions/5600084/starting-an-activity-from-a-service-after-home-button-pressed-without-the-5-seco
http://www.programmersought.com/article/9497587349/
https://www.b4x.com/android/forum/threads/delay-when-startactivity-is-used-when-app-is-paused-by-home-key.105658/

[RalfWerner]

@trygveaa This issue is already 8 months old and you may have already solved the problem! I can not repeat it, but have another device: S610 (Samsung Pad Galaxy Tab S6 Lite) and a slightly different problem. To your 4 reproduction steps:

1. There are two gesture setups (1/3 lines below) that work slightly differently and for the 2nd is a sensitivity slider.
2. Open the app: Setup (top in shot) and files and both in PiP, where termux is also included in the hidden app box.
3. Swipe between start and task screen is problem-free in both setups, but not necessary because of PiP.
4. Click on Widget: ls env ps opens termux here in Picture. Then widget and Termux are on the start screen.

PiP is not necessary for the Swipe effect, but for the Delay problem describe in the Widget: reference. The first tap in Widget open Termux-in-Picture (when PiP-Box is closed) and all following or when PiP-Box is open (top/right in shot) "stacked" as described.

Many taps in Widget lead to many open shells in Termux. Here 21 are displayed, but they only become active with crtl+n. If you know the effect you can live with it. In the three shots above the actions are described on extra keys.

[trygveaa]

This is fixed in version 0.113 of termux-app, after allowing Termux to draw over other apps 🎉 (not sure exactly which version fixed it).

@RalfWerner: That sounds like a separate issue, so you may want to open another issue for that. I'm closing this one, since my issue is fixed.

[RalfWerner]

@trygveaa thanks for feedback

allowing Termux to draw over other apps

Is a new setting in Android 11 (default before). So everybody use Widget has to set it and has to known the needing of it!

You have also discussed with @agnostic-apollo the OS-KB theme too (separate than here in the Issues 2011,2014).
I did this in 1995 ff and will check his last commit too.

The property hide-soft-keyboard-on-startup=true was inserted in the 113 version for hiding the OS-KB at start. Probably we have different wishes to the behavior. I want to avoid the frequent unwanted shopping, as it is rarely necessary on the device with in Picture View and deliberately attended with KB Key Toggles.

[trygveaa]

Is a new setting in Android 11 (default before). So everybody use Widget has to set it and has to known the needing of it!

I was asked by Termux to enable it, so I didn't need to have prior knowledge of it.

You have also discussed with @agnostic-apollo the OS-KB theme too (separate than here in the Issues 2011,2014).
I did this in 1995 ff and will check his last commit too.

The OS-KB theme? I'm not sure what theme you are referring to.

The property hide-soft-keyboard-on-startup=true was inserted in the 113 version for hiding the OS-KB at start. Probably we have different wishes to the behavior. I want to avoid the frequent unwanted shopping, as it is rarely necessary on the device with in Picture View and deliberately attended with KB Key Toggles.

What do you mean by "unwanted shopping"?

And I'm not sure I see the relation between this issue and the keyboard stuff?

[RalfWerner]

I was asked by Termux to enable it, so I didn't need to have prior knowledge of it.

True! One time, in a short notification for 3 seconds and with knowledge of the Steps in Android settings in your language you can do it. In the case "Update Android to 11 and start termux" it could be easily overlooked. Open the Android-Dialog (also needed for storage access), when related data (here ~/shortcuts) exist, is more clearly.

The OS-KB theme? I'm not sure what theme you are referring to.

OS-KB=On Screen KeyBoard! reference and here and some other.

What do you mean by "unwanted shopping"? And I'm not sure I see the relation between this issue and the keyboard stuff?

Sorry not "shopping" - wrong word supplement "Showing (OS-KB)" was meaned and - of course not this (widget) issue!

[trygveaa]

True! One time, in a short notification for 3 seconds and with knowledge of the Steps in Android settings in your language you can do it. In the case "Update Android to 11 and start termux" it could be easily overlooked. Open the Android-Dialog (also needed for storage access), when related data (here ~/shortcuts) exist, is more clearly.

I thought I got a modal asking to enable it last time, but if I disable it now I just get a toast that says I need to enable it. Either way, it was clear enough for me, but maybe it can be improved.

OS-KB=On Screen KeyBoard! reference and here and some other.

I understood that OS-KB is on screen keyboard, but what do you mean with "theme"? There is no theme mentioned in either of those references. But now that I read it again, maybe you meant "thing", as in we were discussing the keyboard?

Sorry not "shopping" - wrong word supplement "Showing (OS-KB)" was meaned and - of course not this (widget) issue!

Okay, not sure when it shows up unwanted for you. For me it is when the keyboard was closed and I return to Termux after unlocking the screen or switching back from another application. As discussed in #2114 it seems like the enable/disable option is the only way to prevent this.

[RalfWerner]

I thought I got a modal asking to enable it last time ... but maybe it can be improved.

That would be great! I had already asked @agnostic-apollo, but he means the three seconds bubble is sufficient. I would also be pleased with a workaround in .bashrc something like [ -d ~/.shortcuts ]&& am broadcast ... as I do with ! -d storage

but what do you mean with "theme ... maybe you meant "thing"

Right "theme=thing"! Widget (here) is one theme and Keybord is another thing and should discuss there