Closed Joomsy closed 9 months ago
Thank you for reporting this. It's the protobuf dependency.
I need to produce and release a new build. Ideally, I would do periodic automated builds to catch this kind of breakage early but I haven't had the time to set it up yet...
Thank you for reporting this. It's the protobuf dependency.
I need to produce and release a new build. Ideally, I would do periodic automated builds to catch this kind of breakage early but I haven't had the time to set it up yet...
Ah, good to know! And thank you for the quick response. That's also completely understandable. No rush from me for a fix. I can fall back on a PC for the time being, but glad I could bring this to your attention.
This also happens to me!
There are some complications but I started working on a fix.
Try to upgrade now. It should work again.
I also took the opportunity to update to the latest version of android-tools instead of just recompiling the old one.
Everything looks good from my end. I didn't test much, but I was able to pair and connect to local wireless debugging, and run a shell command.
Describe the bug Not exactly sure what updated to cause this, or rather, I assume something did, because this started happening after installing package updates. An error about creating an executable link is generated when attempting to run
termux-adb
.To Reproduce Just attempt to run
termux-adb
.Expected behavior
termux-adb
should execute, but doesn't.Smartphone (please complete the following information):
Attach output of the following commands
RUST_LOG=debug ./termux-adb
(run with debug logs enabled)pkg show android-tools
(show package info)adb version
(show adb version)Attach contents of the following files (after running with debug logs enabled)
/data/data/com.termux/files/usr/tmp/adb.10233.log
No log generated
/data/data/com.termux/files/usr/tmp/termux-adb.10233.log
No log generated
Additional context Attempting to run with logging enabled just produces the same result.