[APP] Button Mapper - Customize your hardware buttons

[MarkLev]

Did you ever find a solution to this "toybox: Unknown command am" error when running am command?

Hi @flar2

I was trying to launch an activity using ButtonMapper Pro ut I can't make it work. Here are the things I've tried.

1. Used Shell command: am start -n "com.android.tv.settings/.<ActivityHere>"
But I was getting the toast "toybox: Unknown command am"

2. Used Shell command: adb shell am start -n "com.android.tv.settings/.<ActivityHere>"
But I was getting the toast "toybox: Unknown command adb"

3. I tried to broadcast the Intent with action "com.android.tv.settings.<ACTIVITY>" and checked the option to launch as activity but nothing happens

4. I tried to broadcast the Intent with action "com.android.tv.settings/.<ACTIVITY>" and checked the option to launch as activity but I was getting the toast "Not available"

I tried attempts 3 and 4 again as package and component values but I just get the same result.

Is there any documentation with examples on how to use the Shell and Broadcast Intent options? I tried looking it up but I had no luck.

When I connected my PC to the TV via adb shell, I was able to run the am start command it launches the activity.

But when I run the same shell command via ButtonMapper I get "toybox: Unknown command am"

Thanks!

EDIT:

I tried to call /system/bin/am instead but it gives me an error asking for the permission android.permission.INTERACT_ACROSS_USERS_FULL

EDIT2:

On getting "toybox: Unknown command am", it's weird because am is not under toybox. It's just android built in binary. Why does ButtonMapper think I was invoking toybox? I looked up toybox and it turns out it a port of unix tools to android like busybox.

Can confirm that /system/bin/am exists. I wonder why ButtonMapper can't invoke the am binary. Maybe ButtonMapper can only invoke unix tool binaries under toybox? I haven't tried but maybe Button Mapper can't invoke pm either. I'll try when I get the chance.

EDIT3:

I tried an app called Activity Launcher and it can launch the activity that I wanted. I am not and Android developer so I have no idea how to figure out how Activity Launcer is doing it. Is it invoking shell command and calling the android am (activity manager)? Or is it firing Intents?

Maybe they right option to use in Button Mapper is the Broadcast Intent but I just can't find a guide on how to use it.

If adb command works, and adb tcp/ip is enabled on your TV then another way to make it work is using adb on your androidTV instead of adb on computer.
From androidTV:
adb connect $androidTV_IP
adb -s $androidTV_IP shell...

 

[payas0]

If adb command works, and adb tcp/ip is enabled on your TV then another way to make it work is using adb on your androidTV instead of adb on computer.
From androidTV:
adb connect $androidTV_IP
adb -s $androidTV_IP shell...

Oh, do Android TVs have adb server built in? I didn't know.

Maybe when I need to run other commands, I'll give that a try. But for now, my purpose is to launch activities and the Broadcast Intent handles it so that should ve good for now.

Thanks for the tip though! I'll find uses for that in the future.

EDIT:

I may have misunderstood your comment. I checked and there's no adb binary in the /system/bin so that might not work.

 

[ElBoonoS]

@flar2 Is there a way to support multiple profiles?
can profiles be activated through shell command?
I imagine creating some some profiles and can activate them quickly using termux:widget

Edit: or maybe restore a backup using shell command? This way is simple enough to implement and can easily achieve the above purpose.

Would also be very interested in this.

Doesn't seem to work on my second profile at all. (Kids profile) also cannot activate the pro mode on kids profile. Desperate for help @flar2

 

[MarkLev]

Oh, do Android TVs have adb server built in? I didn't know.

Maybe when I need to run other commands, I'll give that a try. But for now, my purpose is to launch activities and the Broadcast Intent handles it so that should ve good for now.

Thanks for the tip though! I'll find uses for that in the future.

EDIT:

I may have misunderstood your comment. I checked and there's no adb binary in the /system/bin so that might not work.

You can use Termux app, and install adb binary

 

[payas0]

You can use Termux app, and install adb binary

But can you access Termux binaries (adb along with it) inside Button Mapper shell execution?

 

[MarkLev]

But can you access Termux binaries (adb along with it) inside Button Mapper shell execution?

You can use RUN_COMMAND Intent. Refer "top command with am startservice command"

 

[payas0]

You can use RUN_COMMAND Intent. Refer "top command with am startservice command"

Ah, I'll try that when I have a use case. For now I'm satisfied with Button Mapper's broadcast intent feature.

Thanks!

 

[MarkLev]

Ah, I'll try that when I have a use case. For now I'm satisfied with Button Mapper's broadcast intent feature.

Thanks!

I just checked "RUN_COMMAND Intent". I think it is back to "am" command, so it's a no go.

 

[xgerryx]

Going through the ADB process to get screen off keys to work and it states that there was success in granting permissions, but the toggle for that won't stay on, and the off screen keys don't work.

I'm an A12 on a Galaxy s22 Ultra. Did Google remove this functionality?

Edit: seems like it works when the cable is connected to the computer but that's it.

 

[flar2]

Going through the ADB process to get screen off keys to work and it states that there was success in granting permissions, but the toggle for that won't stay on, and the off screen keys don't work.

I'm an A12 on a Galaxy s22 Ultra. Did Google remove this functionality?

Edit: seems like it works when the cable is connected to the computer but that's it.

Screen off actions usually don't works on Samsung and Huawei devices. It's just the way they build the hardware

 

[xgerryx]

Screen off actions usually don't works on Samsung and Huawei devices. It's just the way they build the hardware

Yea that's what I was afraid of. Coming from OnePlus and not having the screen off gestures anymore is a real drag.

 

[TraderJack]

I need some help with intents and Tasker.
Should I be able to use the Public Intent or do I need PRO to broadcast? (And can you please explain the difference?)

I set my Pixel 3XL active edge squeeze with a Public Intent and it gives me "buttonmapper.pref_edge_single_tap"

I put that into Tasker receive intent to run an action but nothing triggers.

What am I doing wrong?

 

[ThimSTR]

Trying to remap any of my buttons on my CCwGTV remote works but if I'm outside of the button mapper app it usually takes 4 seconds for it to run that specific command. Is there any way to fix this and have it respond almost immediately?

 

[4umexdeeay]

Hi there,

(Thanks very much for your efforts with this app.)

-> Just installed on Google TV (Android OS 11, build RTT2.220118.001) for the first time.

I was able to remap the Home button on the tv remote to trigger a couple of installed apps - working great

- but haven't figured out how to trigger a specific input (example: "HDMI 1").

Is this possible?

So far I tried clicking on "+ Add Buttons", then selected the desired button on the remote, then checked out the customization options; I looked through "Actions", "Applications", "Shortcuts", "System", "Advanced", etc, and didn't notice anything that would work.

If I'm missing something, your/anyone's suggestions would be appreciated.

Thx in advance

 

[TraderJack]

@flar2

Possible BUGS?

1)

I've been combing through the thread here and everything I can find and am just not coming up with an answer on Tasker intents for ActiveEdge. (BTW it seems like old instructions for this were posted on G+ and some places link there, but I can't find those instructions anywhere else).

I have tested successfully creating a Tasker Intent Received for a volume down button push:

"buttonmapper.VOLDOWN_SINGLE_TAP"

This properly triggers my tasker profile set to receive this intent.
However, if I instead specify the intent for ActiveEdge squeeze:

"buttonmapper.pref_edge_single_tap"

Then nothing happens. I know that ButtonMapper is properly intercepting the squeeze, since I can get it to do other tasks (like launch an app directly). However it doesn't appear to be sending anything over to Tasker like it does with the volume button.

I purchased the PRO version thinking the "Broadcast intent" option may work instead of the "Public Intent" but I can't figure out how to configure that appropriately (too many fields and no directions).
EDIT: I did figure out how to send the "Broadcast Intent" to package "net.dinglisch.android.taskerm" with an action name I defined (I actually used the same action name from the "Public Intent" and it worked fine).


2)

The ActiveEdge intent seems a bit flaky even when configured working as above. I don't know how to describe it other than one of my use situations:

I use the intent to trigger a profile in Tasker which presents a sidebar scene when the screen is on/unlocked. If the screen is off/locked the squeeze toggles the flashlight.

The sidebar seems to work fine, but the flashlight trigger is spotty. When I squeeze it sometimes it works normal (maybe 30% of the time), but usually it flickers the light multiple times sometimes ending on the proper state (on/off), but often not.

I have tried my exact same BM/Tasker configuration using the Volume Down button instead of ActiveEdge and do not have this problem. If I use the built-in toggle flashlight option it appears not to have this issue with screen on or off.
My guess (?) is that the intent is actually firing more than once when squeezing the device even though I only feel the squeeze vibration once.

I have had to resort to using a logcat event to capture the squeeze in Tasker with the screen off because BM appears to be unreliable.


Would really appreciate any tips/insight regarding the ActiveEdge issues mentioned above.

 

[Talon]

But it will require a rooted phone

strangely enough - but this function works on my Sony TV ...
- and now it very lacking ... - ( for closes the applications... and, most importantly, it return to the android launcher from other HDMI inputs screens - it just simply killing them )

and Flar please - make the 'volume panel bypass' worked on Sony TV.... - look for the posibility for normally adjust the volume on the Sony TV ... - it's hellish torture to adjust volume one by one step for each press (and in my case it twice - bcs the step is 0.5 due to CEC incompatibility with the receiver)
...

 

[4umexdeeay]

Hi there,

(Thanks very much for your efforts with this app.)

-> Just installed on Google TV (Android OS 11, build RTT2.220118.001) for the first time.

I was able to remap the Home button on the tv remote to trigger a couple of installed apps - working great

- but haven't figured out how to trigger a specific input (example: "HDMI 1").

Is this possible?

So far I tried clicking on "+ Add Buttons", then selected the desired button on the remote, then checked out the customization options; I looked through "Actions", "Applications", "Shortcuts", "System", "Advanced", etc, and didn't notice anything that would work.

If I'm missing something, your/anyone's suggestions would be appreciated.

Thx in advance

 

[kwyjibo2000]

I've just bought a Philips Android TV (OLED806) and would like to use Button Mapper to directly select an HDMI input source. I am able to execute the following adb command to successfully swithch to HDMI1:

adb shell am start -a android.intent.action.VIEW -d content://android.media.tv/passthrough/com.mediatek.tvinput%2F.hdmi.HDMIInputService%2FHW5 -n org.droidtv.playtv/.PlayTvActivity -f 0x10000000

How do I convert this into an action that can be mapped to a button? I have seen this question more on this forum but haven't seen an answer. It seems that it should somehow be converted into a Broadcast intent, but I have no idea what information to fill out where in the 'Intent to Broadcast' button mapper section. Any help on how to accomplish this (if possible) would be greatly appreciated, thanks!

Edit: my best guess is the following:
Action: android.intent.action.VIEW
Package: org.droidtv.playtv
Component: org.droidtv.playtv.PlayTvActivity
Data: content://android.media.tv/passthrough/com.mediatek.tvinput/.hdmi.HDMIInputService/HW5

This results in a black screen when pushing the button (not an actual switch to the HDMI input). Some questions I have:
- The adb command sends flag 0x10000000, where would I put that in the button mapper broadcast?
- The adb command uses the %2F escape code for forward slash in two locations, and the post where I found this command (https://community.home-assistant.io/t/android-tv-hdmi/234411/27) indicates this is important. I tried entering %2F into button mapper but it changed them into a forward slash. Could this affect the outcome?

 

[discapacidad5]

If it's Bluetooth, it probably won't work. Not sure why, but a lot of Bluetooth devices handle button presses internally. If they are not detected by the add buttons dialog, there is no ability to remap them at all.

hello I have bluetooth headphones that have three Play buttons forward and back, the funny thing is that the buttons are recognized by the music player they are also recognized by Zello workie talkie,which by the way has an option to add custom buttons very similar to renaper and the buttons recognize it perfectly I think it would be good if they did a review,because I am sure that the buttons work well and are recognized by other applications, I think there is something that they are not doing well so that the bluetooth buttons are recognized

 

[flar2]

hello I have bluetooth headphones that have three Play buttons forward and back, the funny thing is that the buttons are recognized by the music player they are also recognized by Zello workie talkie,which by the way has an option to add custom buttons very similar to renaper and the buttons recognize it perfectly I think it would be good if they did a review,because I am sure that the buttons work well and are recognized by other applications, I think there is something that they are not doing well so that the bluetooth buttons are recognized

That's different, those apps are responding to the media commands issued by those buttons, not suppressing the original action and doing something else. My app Next Track works like that but is very limited compared to Button Mapper.

But the main reason I can't have that in button Mapper is the remapping would only work if Button Mapper continuously played a media file or was actively recording. It would kill the battery.