gparodi1410
commented
5 months ago How works second workaround?!? Ty
Open jonny333 opened 5 months ago
gparodi1410
commented
5 months ago How works second workaround?!? Ty
jonny333
commented
5 months ago How works second workaround?!? Ty
You open the wireless debugging menu and enter split screen mode and open another app that would need the keyboard (for example messenger) you click on pair with code and when the shizuku notification appear you click on the messenger to type the message so that the keyboard appears, then you click on your shizuku notification to enter the code and voilà :)
gparodi1410
commented
5 months ago Ok thanks!
kaoneko
commented
3 months ago Thanks @jonny333, this was driving me nuts! I think last time I worked around it by connecting my phone to my laptop with a USB cable and running adb shell input text <pairing code> while the input field of the notification had focus. This time I used the split screen method. I'm also using Edge Gestures (and several other accessibility services) 👀
Medard22
commented
2 months ago The workarounds doesn´t work on my Retroid Pocket 4 Pro, once I input text on the keyboard or use adb to send input the notification loses focus. Even the split screen method doesn´t work.
Exonymos
commented
5 days ago Thanks a lot. My issue was the same with edge gestures.
psiie
commented
2 days ago Wait, your issue was the same with edge gestures by "ChYK the dev"? I also use edge gestures and have the same issue. Interesting. (It's not like it's a wildly popular app :P)
I'm playing with another solution which is to use macrodroid. But waiting until I have to pair again because I'm lazy. (PS: there is a script someone made in the Macrodroid-Template repo that works really well for starting Shizuku on boot. Highly recommend)
Exonymos
commented
1 day ago Wait, your issue was the same with edge gestures by "ChYK the dev"? I also use edge gestures and have the same issue. Interesting
Yea 😅
there is a script someone made in the Macrodroid-Template repo that works really well for starting Shizuku on boot
I'll look it up thanks
Please report bugs of Shizuku itself (Pixel 8)
Requirements:
Change "[ ]" to "[x]" if it meets the requirements.
Reports not meet the requirements will be immediately closed.
Information:
Logs:
Related full logcat.
Describe the bug: When I try to pair via wireless debugging and go to the option click on pairing code and the shizuku notification pop up as soon as I try to type anything my keyboard dissapears. If I pull the notifications and try to type again (without seeing the code on the screen) the keyboard doesn't pop up thus I'm unable to type the code. I recorded a video of it which you can see here https://drive.google.com/file/d/1jJBagiYPB4vcDexCc_983zGIkLlHbnUN/view?usp=sharing
Additional context: I tried with 2 different keyboards and the outcome was the same (Gboard/ Swift). The workaround I found is to connect a physical keyboard and type the code that way but it's not optimal if you don't have immediate access to a physical keyboard and an usb c dongle
Add any other context about the problem here.
I presume it's some kind of a security from android because if the I'm not in the wireless debugging menu I can type things in the notification. Have another pixel (4a) running android 13 where this problem do not exist
UPDATE:
I can't reply to any notifications as long as I'm in Settings app (not even chats)
UPDATE 2:
another workaround I just found is to split the screen between settings and another app that uses the keyboard (for example messenger) and invoke the keyboard their and then use it to fill in the code in the notification
FINAL UPDATE:
I found the culprit. It was an app called "Edge gestures" if you disable it the keyboard no longer dissapears while in settings. I presume similar apps will cause this as well so maybe close the issue but don't delete it.