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

termux-wake-unlock not running correctly when executed via termux-widget #31

Open
jpdasma opened this issue Jan 12, 2019 · 2 comments
Open

Comments

@jpdasma
Copy link

jpdasma commented Jan 12, 2019

Problem description
termux-wake-unlock not running correctly when executed via termux-widget

Steps to reproduce

  1. Create two script and place them inside ~/.shortcut/background/. These are the ones I'm using.
    a. first.sh
#<<insert bash shebang>>
 termux-wake-lock
sshd -D

b. second.sh

#<<inser bash shebang>>
pkill sshd
termux-wake-unlock
  1. Run the first script via termux-widget, then run the second script.

  2. Termux still has the wake lock.

Expected behavior
Termux will release the wake lock.

Additional information
Post output of command termux-info.

Updatable packages:
All packages up to date
System information:
Linux localhost 3.18.120-PPK29.68-16-8-g0fbb2ba1b5e1 #1 SMP PREEMPT Fri Dec 28 18:52:16 CET 2018 aarch64 Android
Termux-packages arch:
aarch64
Android version:
9
Device manufacturer:
motorola
Device model:
XT1635-02
@fornwall
Copy link
Member

fornwall commented Aug 4, 2019

Hello @jpdasma and sorry for the late reply! I'm unable to reproduce this problem, can you (or anyone else) reproduce it?

@jpdasma
Copy link
Author

jpdasma commented Aug 21, 2019

It's been a while since I filed this issue. I could still reproduce it, however when I called termux-wake-unlock first before killing sshd, it seems to work properly. Will try to see more what's happening on my side, but this is my current workaround.

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

No branches or pull requests

2 participants