Search results

Search for 14908 and 14966 in the template store. The reason the link is "dead" is because your browser isn't redirecting you to MacroDroid.

In your video this isn't enabled, but because it isn't enabled in both macros that's still odd. What happens if you copy the second constraint to the first macro and test it there?

Unless there is a bug, it should indeed always return false.

I understand better now. Device facing shouldn't consider the screen orientation that apps can set but the way your phone is oriented physically.

I tried to test it, for phones it seems the screen is always put in portrait when you turn the screen off but for other devices I'm not sure. Depending on the situation combining these 2 triggers (device orientation if screen on, device facing if screen off) would be the way to do it.

@Sir Michael The first post you read, is right above (now it's on the first page). Here's some links in case you somehow can't find it : https://macrodroidforum.com/index.php?threads/macrodroid-helper-apk.1/#:~:text=Android%2014%20specific,be%20found%20here%3A...

I think I'm going to add 10 red arrows too.

There used to be a workaround before Android 12 (but it only works for apps and it was not implemented in MacroDroid), but on Android 13 and above apps just can't access them. You need to use root or ADB.

It would be device orientation.

@BlatnatHacer49 It, in fact, isn't just for mobile data. I got fooled by its name too, but it actually means any connection, like mobile data, but also wifi, ethernet, bluetooth (who uses bluetooth for network?).

That's why I mentioned both, I wasn't sure if @Karby wanted the real life orientation or the screen orientation.

I imagine you enabled the permission that allows MacroDroid to access your notifications?

One of these two will do what you want.

Oh. This issue. I remember it, Jamie managed to solve it for me after 1 year. What you should do is select the icon quickly, or before writing anything select the icon. If it doesn't work the first time then try again until it works. You can try fixing it but not even reinstall fixed it for me.

Look at the screen content trigger and the UI interaction action.

I guess they want you to show the macro actually in action, you receive a text message and the app sends it back (the system log could help too). Or a likely option is just yet another unexplained rejection.

There is no guarantee that MacroDroid on emulators will work correctly. You can try asking in other forums about Firebase Cloud Messaging (this is how webhooks work).

私はこの問題を別のsmtpサーバーで覚えています。エラーの原因は別として、エラーは同じでした。私の記憶では、それは互換性のないプロトコルのケースでしたが、私は間違っているかもしれません。

No wonder. This code is not JavaScript, it is Java (which is NOT at all the same thing!). I don't think Android allows apps to connect to SSIDs the user hasn't connected to before.

Reminds me, didn't @sampleuserhere have this problem occasionally? Never once a script like that failed for me. Out of the thousands of times I ran a similar script it only failed 8 times which is most likely due to me disabling MacroDroid or device shutdowns and things like that.