Need a method to forcibly show the keyboard any time

[mikeloeven]

So sometimes there are times when you need a keyboard but dont have one because android doesent see a text context. An example of this is playing browser based games that need wsad input and lack touch support

[demaborisov0]

Open

[glchisenhall]

I agree with most of the OP's statement. However for me, I would just like to be able to use the function keys. As of right now, they have little to no use for me. Although, I'm not sure the uses I'd have are even supported on android anyhow, but just knowing one way or the other would be helpful. Unfortunately, as OP stated, currently no method exists to display the keyboard, thus, is my predicament.

[TPS]

The ☑️ Use permanent notification setting is designed specifically for this scenario. Choosing the notification opens the keyboard anytime.

[mikeloeven]

May need to look at your notification API or the Manifest permissions of the app the persistent notification does not show up on my device even though the option is selected

Using a Galaxy S5 with AT&T
running marshmallow

On October 7, 2016 10:33:48 PM EDT, TPS notifications@github.com wrote:

The ☑️ Use permanent notification setting is designed specifically
for this scenario. Choosing the notification opens the keyboard
anytime.

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#512 (comment)

[TPS]

Since I run Android 4.4.x, it works fine. Obviously, HK hasn't been updated/released since then. What do you think, @klausw?

[mikeloeven]

You might want to go the accessibility route with this function and use the overlay API to show a floating action button that can be dragged around the screen like the call shortcuts

[yassine987]

In LatinIME Class (Line 507) the developer use
notification.setLatestEventInfo(getApplicationContext(), title, body, contentIntent);
This method was removed in M (api 23)
I suggest to delete the line and add this before Line 506

Notification notification = new Notification.Builder(getApplicationContext())
                    .setAutoCancel(false) //Make this notification automatically dismissed when the user touches it -> false.
                    .setTicker(text)
                    .setContentTitle(title)
                    .setContentText(body)
                    .setWhen(when)
                    .setSmallIcon(icon)
                    .setContentIntent(contentIntent)
                    .getNotification();

for more information about the issue StackOverflow

EDIT 17-Oct-2016:
delete notification declaration Line491 to avoid notification variable already exist error.

[TPS]

@yassine987 2 suggestions:

• The vast majority of users (as of this note) use Android < M, so support for all versions could be done via conditional statement(s).
• Once the above is worked out, it'd be amazing if this could be turned into a proper PR.

Thanks for the work on this! 👏

[mikeloeven]

I would still be using lollipop if it wasn't for AT&T's forced ninja updates

[yassine987]

@TPS
I tested the app with the above changes in 3 devices Samsung GT-S7580 (Android 4.2.2, API 17), Samsung SM-G355H (Android 4.4.2 API 19), Samsung SM-J200F (Android 5.1.1, API 22), the Use permanent notification works great, unfortunately, don't have an M device to know if it solved.

[mikeloeven]

If you can post a link to the updated APK I'll test it for you

[yassine987]

@mikeloeven APK

the updated APK has the same package org.pocketworkstation.pckeyboard, maybe you have to uninstall the old one first.

waiting for the result ^_^

[mikeloeven]

Permanent notification is confirmed working on marshmallow with yassine987's fix any idea when we can expect this fix to be pushed the Play Store

[yassine987]

I think @klausw is the only one who can update Hacker's keyboard in Play Store.

Now, I'm working on a keyboard app based on hacker's keyboard with a new feature, will be available in December 2016 (If everything goes as planned), I can let you know when it's available in Play Store.

[TPS]

I'd love to try it.… Is your dev fork on GitHub? & would you mind pulling in all the other work & PRs from other folks here, & acknowledge all of the above via a clear Apache-2.0–compatible license?

[yassine987]

@TPS not yet, but I create a new one for this issue.

I have some questions if you don't mind

• As I mentioned above, I'm working on a keyboard app based on hacker's keyboard with a new feature, different themes etc...., and I'm planning to publish it on Github and Play Store. So, is it ok if I push it as a new Repository?
• Is it legal to publish it at Play Store (I'll mention Hacker's keyboard in my about) ?

[TPS]

@yassine987 IANAL nor the original author (@klausw _is!_), but, AFAICT:

• I think it'd better to fork from here, as it's more likely to receive more attention & help doing so, given that your app's a derivative of this 1 only, with your additions & modifications.
• As mentioned above, as many of us assume an Apache 2.0 license (@klausw, a clarification would be _amazing!_), you should be ok if you follow its terms correctly.

[mikeloeven]

@yassine987 found a slight issue with your build its launching as a delayed startup instead of at boot causing the system to default to the system keyboard each restart

[TPS]

@yassine987 I forgot to mention maybe the most important reason to fork this repo: Inheriting the issues here, as you solve them & mention that you did so, you immediately increase your userbase among the users tracking these issues.

[klausw]

@yassine987 @TPS Sorry about the long silence, things have been too busy. Thank you for investigating this issue, I'll merge this and look into getting a new release out (any year now). I can apply the change manually, but if you want attribution in the source it would be easiest if you can make a pull request.

As far as forking and publishing on the Play Store is concerned, you're welcome to do so. The Apache 2.0 license allows this, but please change the application name and contact info in documentation to make it clear that it is a modified version. That's mainly to avoid user confusion and ensure that contact attempts go to the right author.

The Play Store releases are signed with a cryptographic key, so you'd need a different package name and use your own signing key. That way the new application can be installed alongside the current package, it can't replace it. Before you ask, I don't intend to share the existing key. I think it wouldn't be fair to existing users to have software updated in-place with someone else's version, especially considering that a keyboard is security sensitive. But I'd be willing to provide links to alternate maintained versions if mine continues being neglected.

[klausw]

I've included this change in the latest alpha version 1.39.0.

You can use this link to opt-in as a tester for the alpha version: https://play.google.com/apps/testing/org.pocketworkstation.pckeyboard

It may take a few hours for the new version to propagate, you can check your version at the bottom of the keyboard's settings menu.

[klausw]

Closing, 1.39.1 is now set as live on Play Store. It may take a day or so until your device sees the update.

[typxxi]

1.39.1 arrived - a few hours ago and I noticed that after I tfied to use Ctrl + a which did not work anymore - instead a hint appeared and therefore I checked the configuration and finally found that new option.

@klaus: Thanks for the update - hope to see more

[RSW2019]

I have a little app that does this, you can use it to bring up any keyboard you have installed, gboard or whatever

https://play.google.com/store/apps/details?id=com.rswspinningyarns.keyboardlaunchernoads