-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues running on Termux #1
Comments
Generally, if I press the chevron button at the far right of the bottom bar of the Samsung Android OS, the virtual keyboard comes back onscreen, and then typing in the active field on the screen is possible. But, doing the same hack in this situation and context, instead, moves the browser page to prior viewed page and so, the loaded and booted VM of the Alpine Linux image in the browser is lost! Any idea of a workaround? |
Hi @b9Joker108 I don't think by default the v86 is configured as mobile friendly 😅 There is a work around using Xterm.js which may work better on a mobile tablet. Check out this branch: https://github.com/nadchif/in-browser-virtual-machine/tree/boot-linux-terminal Please try it out and share how it goes 🤞😊 |
I am a bit confused how I check out and git clone that branch. I was amazed that I actually did the last one successfully! Could you please spoon-feed me a bit more? |
Sure, git clone https://github.com/nadchif/in-browser-virtual-machine.git Navigate into the directory cd in-browser-virtual-machine Checkout the branch git checkout boot-linux-terminal Install dependencies npm install Run npm run dev |
I am a bit confused, as I installed the branch: |
Hi
Thanks for your code.
I git cloned and checked out only your Alpine Linux branch and installed. But, this is my shell output:
And, the container image booted up successfully in my browser, but as I am on a Tablet, I couldn't enter "root" at the login prompt. When I select the screen to type, the virtual keyboard is off screen and when the keyboard is back on screen, the field isn't selected, so it is a Catch 22! The hack I have learnt to get the keyboard back in similar situations, which in the Samsung flavour of Android is pressing a particular button, doesn't work in the browser context, like it does in other apps, such as Termux and RVMC Viewer, for example.
The text was updated successfully, but these errors were encountered: