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

Keyboard Not Showing Up After Phone Inactivity (only option is to restart) #1335

Open
AaronKnowls opened this issue Jan 31, 2025 · 6 comments
Labels
bug Something isn't working

Comments

@AaronKnowls
Copy link

  • When after 4 hours of not using the phone I'm forced to enter the password, the keyboard doesn't show up and I have to restart the phone.
  • This didn't happen before a couple of the last Heliboard updates.
  • Might not be related to Heliboard, but I'm desperate. I've researched and researched, tested and tested, and nothing seems to work. Sometimes it's very inconvenient to restart the phone if you're in a hurry to use it.
  • Hopefully someone has faced this issue before and can shed some light.
  • In any case, thank you so so much for this amazing app. I'm so so grateful for it.

App version
Latest

Device:

  • Model: Asus Zenfone 10
  • OS: Official updated Android 14
@AaronKnowls AaronKnowls added the bug Something isn't working label Jan 31, 2025
@Helium314
Copy link
Owner

This issue sounds like it will be awful to debug...
I can't remember anyone else reporting this, only know a remotely related issue #801.

Do you have another keyboard installed and enabled the system could switch to automatically?
Currently my only idea is that HeliBoard is crashing for some reason, and I'm thinking how to get the logs, which are lost on rebooting. Do you know how to use ADB / logcat?

Another thing that may help would be identifying the change or at least version causing your issue.
You don't need to uninstall / downgrade your normal install for this, you could switch to adebug APK of an older version and see at which version the problem starts (and the keyboard doesn't...).

@AaronKnowls
Copy link
Author

AaronKnowls commented Feb 3, 2025

I'm so so thankful for your thoughtful and thorough answer.

"Do you have another keyboard installed and enabled the system could switch to automatically?"

I've been trying and researching how to do this but failed.
I have another keyboard but the system switcher can be ran but not accessed due to the phone password blocking. You couldn't imagine how many crazy things I've tried regarding that!

"Do you know how to use ADB / logcat?"

I can use ADB, I'll learn the logcat part.

"Another thing that may help would be identifying the change or at least version causing your issue."

This is a brilliant idea! I'm going to test that.

Thank you for your time and care.

@Helium314
Copy link
Owner

I can use ADB, I'll learn the logcat part.

This would be ideal if you can get the logs like that. I'm not sure whether ADB connection is possible while the device is locked.

@AaronKnowls
Copy link
Author

The tests with the debug versions (I tried 2.1, then 2.0, and then 1.something) failed.

At least one of those versions worked properly in the past (regarding the issue at hand).

Shall I conclude that the issue is, then, related to some firmware update of the phone?

I'm running out of solutions for this.

@Helium314
Copy link
Owner

At least one of those versions worked properly in the past (regarding the issue at hand).

If you can't find a working version, maybe it's related to a system upgrade that somehow broke something...

I'm running out of solutions for this.

Did you try getting logs via ADB & Logcat? Especially if its from the debug version there should be a lot of potentially useful information.

@AaronKnowls
Copy link
Author

OK, after some more testing I've found the issue: an app called Edge Gestures.

I still don't get what is going on, since there are no problems before that 4 hours inactivity, and I have no idea why that app only in that circumstances makes the keyboard disappear. So I'm guessing it was an update of that app (everything worked fine before) what caused the problem.

Maybe this information would help someone else.

Thank you so much for your time and attention, Helium314. I hope I didn't waste your precious time.

(I would love if anyone wiser than me has any idea of what's going on here)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants