How to press on a number 0-9 when calling with MD ?

[Christoph]

Hi, I have this macro started when I do a call to a given number:



The 1st UI works, but not the others for the 0-9 buttons.
Here is the phone graphical interface:

 

[Snurre]

You could try with x, y coordinates instead

 

[OscariBot]

Yea x, y coordinate should work fine... But Id is more reliable even though some device makes it really difficult use

 

[Christoph]

I have tried with x,y coordinate, it works. But it is so much more complex to setup and not easy to read/modify afterwards.
Can someone with a Samsung phone, share his experience about using dialpad_buttons command ? I wonder if it is just me or if it is for all Samsung users.

 

[OscariBot]

Try using AutoInput plugins. Then use dial pad button IDs instead.

 

[OscariBot]

I just tried it on my old Samsung Galaxy and it works... But I don't knw for sure why using IDs didn't work with native macrodroid but it work perfectly with AutoInput plugins.

 

[Endercraft]

I just tried it on my old Samsung Galaxy and it works... But I don't knw for sure why using IDs didn't work with native macrodroid but it work perfectly with AutoInput plugins.

It probably means AutoInput uses a different ID system.

 

[Jacob L]

Why not use the read screen contents action and store them in a variable and use those with UI interaction action to click

 

[OscariBot]

I expected MD to use d best and easiest way

It probably means AutoInput uses a different ID system.

 

[OscariBot]

Why not use the read screen contents action and store them in a variable and use those with UI interaction action to click

I tried read screen, it seems not to read dialpad screen content on my Android 12 except I use AutoInput plugin... But it works well on my old Samsung Galaxy without plugin

 

[Christoph]

I just tried it on my old Samsung Galaxy and it works... But I don't knw for sure why using IDs didn't work with native macrodroid but it work perfectly with AutoInput plugins.

When you write about using AutoInput you mean this ? https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput
the last update is from 2019 ! So it is very old, is it a good thing to use this in Android v13 ?

 

[OscariBot]

When you write about using AutoInput you mean this ? https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput
the last update is from 2019 ! So it is very old, is it a good thing to use this in Android v13 ?

Yea . That's the plugin... It may be long it was updated but it still works.
Why not give it a try

 

[Christoph]

Why not give it a try

Before installing I wondering, if if this is a possible workaround with native MD:

Why not use the read screen contents action and store them in a variable and use those with UI interaction action to click

but how it is possible to do that ?

 

[Jacob L]

Before installing I wondering, if if this is a possible workaround with native MD:


but how it is possible to do that ?

Create a macro with shake trigger, action: read screen, set variable. Lock the device and put the screen on, shake and see your variable

 

[Dimlos]

I tried using AutoInput with Android 13 on a Samsung device.
It does indeed work with AutoInput.

 

[Christoph]

I tried using AutoInput with Android 13 on a Samsung device.
It does indeed work with AutoInput.

Good news, so this workaround will work.

I am interested if it is possible to do it with native MD :

Create a macro with shake trigger, action: read screen, set variable. Lock the device and put the screen on, shake and see your variable

This is the content of the variable :


when shaking on the screen:



How to use this result ?
To me it confims:

should be working.
But in reality it is not the case.

 

[OscariBot]

Good news, so this workaround will work.

I am interested if it is possible to do it with native MD :


This is the content of the variable :
View attachment 4926

when shaking on the screen:
View attachment 4927


How to use this result ?
To me it confims:
View attachment 4929
should be working.
But in reality it is not the case.

I advice you not to focus on Native macrodroid action on this....it seems not to work on some device but AutoInput work flawlessly

 

[Christoph]

I advice you not to focus on Native macrodroid action on this....it seems not to work on some device but AutoInput work flawlessly

I have installed AutoInput , which action do you use for that ?


Does AutoInput need accessibility access for this ?

 

[OscariBot]

I have installed AutoInput , which action do you use for that ?
View attachment 4941

Does AutoInput need accessibility access for this ?

Yes...you must turn on accessibility option.

Use number 1

 

[Christoph]

I have added this AutoInput action, but the command does not work : did you use these options?