Skip to content
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

Resizing on Meta Quest gives "No hosts currently connected" #1356

Open
natebragg opened this issue Jan 21, 2024 · 2 comments
Open

Resizing on Meta Quest gives "No hosts currently connected" #1356

natebragg opened this issue Jan 21, 2024 · 2 comments
Labels

Comments

@natebragg
Copy link

Bug description

I installed connectbot onto a meta quest 3. It seems to work fine, but side loaded apps only start in profile, not landscape. To get around this, you can resize windows arbitrarily.

It seems that when I resize connectbot, it no longer displays my session, instead saying "no hosts currently connected".

What I'm doing is unconventional, nevertheless I'm very much hoping I can get this working.

To be clear, when I leave it in profile, it displays my session just fine. I can even make the window maybe 10% bigger, no problem. But if I resize it more, it gives the above message

Steps to reproduce

  1. Sideload connectbot onto a meta quest 3
  2. Click "switch distance", so that apps are in the curved display
  3. Open connectbot and open any connection; notice that the connection succeeded, and text appears fine
  4. Resize connectbot by grabbing and dragging any of the four corners (they will flash white when highlighted).
  5. The console session disappears, and is replaced by the aforementioned message

Expected behavior

It will resize, and the remote terminal remains visible.

Android device

  • Device: Meta Quest 3
  • ConnectBot Version: 1.9.10
@natebragg natebragg added the bug label Jan 21, 2024
@natebragg
Copy link
Author

I realize you probably don't have a meta quest at your disposal, so I have two ideas:

  1. You can point me in the right direction, and I can try to fix this myself, or
  2. We can collaborate to fix this together, with me testing and reporting back.

@TheSteveHan
Copy link

TheSteveHan commented Mar 2, 2024

Ran into the same issue on quest. I can see this warning in LogCat.

TerminalView not displayed because it is too large to fit into a software layer (or drawing cache), needs 7648900 bytes, only 1600000 available

Adding android:hardwareAccelerated="false" to AndroidManifest.xml seems to have resolved the issue for me for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants