-
Notifications
You must be signed in to change notification settings - Fork 231
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:Boot not working on Android Oreo #38
Comments
same issue, pixel xl |
same issue, Huawei p20 pro with Android 8. It can start sshd but not node-red. |
@koalaeagle @SDRausty @silversquasher Did you disable the battery optimizations for Termux and Termux:Boot. Which one is/ are both required? (to inform other users about that/ show a permission request to disable the optimizations if possible) |
Same here on Samsung A5 (2017) with LineageOS 16.0 20200309-microG-a5y17lte. Never worked |
It's not working for me also Redmi Note 7 Pro |
Did anyone find a solution? I have the same problem with a Honor 9 lite |
Same here on Lava Iris |
Solution add -D falg to sshd works great for me - Android 8.1 on LG/Nexus 5.x. Here is complete check list.
Settings -> Apps & Notifications -> Adavanced -> Special app access -> Battery optiomization -> Not Optimized
|
@ghost @sergey1369 Thanks. |
Its not working for my Samsung Note 8 |
I have opened the Termux:Boot app several times.
Termux:Boot does not appear to be working under Android Oreo. My scripts are not executed at all. I use Ansible to deploy my configuration so I can be sure it is identical as Nougat. Although, I ended up removing all of my boot scripts since I discovered that termux-wake-lock does not work either under Android Oreo. Since my primary concern is having sshd running on startup I tried making that the only line in the only script.
I tried just "sshd" and also just "sshd -D", neither worked. To ensure it wasn't a problem related to sshd I erased everything and just had a simple "echo test > ~/test" and that did not work either. Has anyone else run into this? Even without the wake lock it should run one line right? If I manually run sshd the daemon works fine and does not seem to exit even without the wake-lock.
The device is a OnePlus 3 running OOS 5.0 (Android 8.0.0).
The text was updated successfully, but these errors were encountered: