An app I’ve found indispensable, remote keyboard, by Onyxbits.de, may no longer be installed on a more modern tablet (Samsung Galaxy Tab A9+). The app creates a “keyboard” which listens for a telnet connection from a computer, and may use this for tablet input, so you may type, I stead of hunting and pecking.
Although I’ve developed most of my career, I know nothing about Android app construction.
Can someone more knowledgeable tell me if the FUNCTIONALITY is no longer permitted on recent Android systems (viz. listening on a port) or whether it is a question of installing it via adb and telling the tablet to ignore that it was developed for an earlier version of Android?
Or, perhaps someone can bring this very useful app back to life by adjusting what must be adjusted? I’m too old now to do this myself!
Thank you. It looks like a useful app and program, but has no facility described which creates a " keyboard" on the android which may be operated via network connection from a real keyboard on a connected computer, by telnet or other network communication protocol. See description of Remote Keyboard among the F-Droid apps.
Ah. I found that someone WAS able to overcome the problem by forcing the installation with a switch, using adb, so maybe somebody could rebuild it. That answers my question: that there’s nothing in the app that is no longer allowed,
Yes. I can confirm that this worked, although I seem to have had to use a somewhat earlier version of adb in order to get adb to work properly!!
I’m so relieved!!!
I am using it right now to type this message on the new tablet.
The only slight problem after installation was that the tablet kept warning about how dangerous the world was. But at least now I can rest assured that I don’t have to deal with the hunt-and-peck keyboard on the tablet. I must write one more time to the developer to let him know.
For completeness, I used Android Debug Bridge version 1.0.41, Version 29.0.1.-5644136 installed on an old Windoze 7 computer, connected to a Samsung Galaxy Tab A9+ by usb cable.
And, after verifying connection, and selecting the device, issued
adb install --bypass-low-target-sdk-block [path]/de.onyxbits.remotekeyboard_8.apk
It would still be nice if someone were to bring the app back to life so people don’t need to jump through hula hoops. As I said, I’ve been a software developer all my life, but I’ve never developed anything for the Android platform. I expect it may just be a question of lying about the SDK.
As far as I can see, the app itself is working as it should now.