termux/termux-app

Virtual keyboard doesn't load in Chrome Tab 10

Open

#1343 opened on Nov 10, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (54,915 stars) (6,572 forks)batch import
chrome-oshelp wanted

Description

Problem description Termux loaded from Play store to an Acer Chrome Tab 10. This is a Chromebook in tablet form - i.e. tablet running Chrome OS.

Steps to reproduce Tap to launch Termux. Then tap on the Termux screen to activate the keyboard. I can see the keyboard for a split second but it doesn't stay up - it disappears. I'm not able to make the keyboard come up and stay up.

Expected behavior The keyboard should load when the screen is tapped so that the user can start inputting commands at the terminal prompt.

Additional information There's no terminal output or warning. The keyboard simply fails to load. This is my first time attempting to use Termux in Chrome OS. So the keyboard has never worked for me.

Contributor guide

Tech stack
javaandroid
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Android input methodChrome OS tablet testingTermux app architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue likely stems from how Termux handles virtual keyboard input on Chrome OS. Investigate files related to input handling, such as `TerminalView` or `TermuxService`. Check Android's `InputMethodManager` API and how it interacts with Chrome OS's virtual keyboard. Reproduce on a Chrome Tab 10 or use Chrome OS emulator. Look for any existing workarounds in similar apps. Since the issue is old, consider if newer Termux versions have addressed this.