Issue Calling Command

[ukiews]

Trying to run a simple play/pause command “input keyevent 126” but no response.

The command works as expected through Terminal.
I get the initial verification screen to use FYT HW as the trigger for the button, I confirm, but then no reaction.
Are there permissions missing?

[ukiews]

Any ideas on this?

[noenic]

I'm a bit late, sorry.
The problem is that with the new version of android it is not possible to do shell commands anymore.

I'm making a fork of the project that will allow to make commands through ADB

[noenic]

For the moment I could only test it on the android studio emulator because I'm far from my head unit but it works (normally)
https://github.com/noenic/FytHWOneKey

compressed_FytHWOneKey-.-AdbAdapter.java-.FytHWOneKey.app.main.-2023-03-03-23-23-01.mp4

[hvdwolf]

Very nicely done.

What's more: I am not activley maintaining this apk anymore as I don't use it myself for at least 2 years now.
If you want to take over, please do so. (Next to that: I never was a real android programmer. I just needed an apk that did what I needed and it did not exist).
If you want to rename the apk and its packagename you can do so as well. I can point everyone forward to your github and point every link (under my control) also to your github.
What do you think?

[noenic]

Hi,

I believe that credit should be given to the person who did the most work on this project. I simply combined two existing projects and used the Java and Android basics that I am learning in my computer science program. I don't think I will be doing much more than that, as this is an ultra-specific specification and each head unit has different characteristics.

I will wait to test it on my actual head unit when I can, and if it works there, I will open a pull request.

If I decide to add a new important feature someday, I will reconsider your proposal.

Thank you.

[ukiews]

I'm a bit late, sorry. The problem is that with the new version of android it is not possible to do shell commands anymore.

I'm making a fork of the project that will allow to make commands through ADB

Thank you for the effort. However, still not working for me. Uninstalled and reinstalled, and set the BAND button to "By ADB command"
Have also tried "adb shell input keyevent 126"
No go.

"input keyevent 126" through the Material Terminal works every time.

Please let me know if there is some other command I'm missing.

[ukiews]

By the way the app used to generate several supporting (shortcut) apps, these don't exist anymore.

[ukiews]

So looks like "Test ABD connection" fails for me. I'm guessing that's a typo you have there. Should be "ADB" not "ABD".

Anyway, the Developer options are enabled. Not sure if I need to set the port to something specific. Tried both 5555 and 5559.
The headunit is rooted.

[noenic]

Thank you for testing,
Let's start from the beginning, When you use the terminal, do you use adb or do you just write "input keyevent 126", If you use adb, do you connect with the IP localhost and the port 5555?

First you have to make sure that adb is available on your head-unit. Use the remoteADB application (I used the same library)

Connect to localhost and port 5555, do you get an error message?
If you have a timeout try running this command "setprop service.adb.tcp.port 5555" it will enable ADB listening on port 5555 then restart

When you pressed "Test ABD" was there an error message? "refused" or "timeout"?
The typo is only in the user interface.

What did you write in the call action? It should have been for example "shell:input keyevent 126".

I don't know what head-unit you have, guessing by the UI at the top I'd say a T'eyes CC3?

EDIT :

By the way the app used to generate several supporting (shortcut) apps, these don't exist anymore.

Can you give me a bit more informations about that ?

[ukiews]

Yes, I have the CC3.

In terminal I enter "input keyevent 126"

I did try "shell:input keyevent 126"

I have not used ADB before with this unit.

Will check on the other items soon.

Can you give me a bit more informations about that ?

Maybe @hvdwolf can speak to this.
I believe there was an app that specifically triggered the BAND button, and another app for another button, can't recall.

[hvdwolf]

Maybe @hvdwolf can speak to this.
I believe there was an app that specifically triggered the BAND button, and another app for another button, can't recall.

As fas as i know there was never a specific app for these actions, at least not by me.
Up until the PX5 I made Xposed modules to control those keys but all from one Xposed module, not per key. Xposed was not possible anymore on the sc9853i and now the uis7862. That's why I wrote the FytHWOneKey.

[ukiews]

So I get connection refused error.
have tried using the setprop command in terminal and rebooting device, still the same error.

[noenic]

So I get connection refused error. have tried using the setprop command in terminal and rebooting device, still the same error.

Well, this shows that the ADB service is not reachable. It's weird on my CC3 I can connect to ADB as localhost, I just can't remember how...

I know I used the setprop command, I just don't know if it's "setprop persist.adb.tcp.port 5555" or "setprop service.adb.tcp.port 5555"

Then I could access ADB from my laptop by connecting to the head unit's hotspot.

[ukiews]

I have tried both commands now, and neither seem to work.

[noenic]

try to connect with a laptop in ADB to the head unit first using the hotspot.