v5.47 - Feedback

Status
Not open for further replies.

MacroDroidDev

Administrator
Staff member
@ZnAK I have tested the Bubble sorting many times on 5.47.5 vs 5.47.7 and there is no discernible difference in timings between these two versions.

Your times seem to be incredibly slow compared to what I'm seeing (orders of magnitude slower) so I think there is something else going on here. What device are you running this on?
 

Dev777

Active member
There is a bug with creating dictionary copies.
When you try to create a new dictionary as a copy of an existing one and keeping option Create variable now as checked it instead creates duplicates of the same dictionary instead of having different names.

Version 5.47.7
 

Attachments

  • Screenshot_20240806-124447_crDroid Home.png
    Screenshot_20240806-124447_crDroid Home.png
    121.8 KB · Views: 6

LinerSeven

Active member
Does MacroDroid 4.47.7 not crash for you? Here, it crashes about every ten seconds, making it impossible to use properly!
Hi, @huashimacro,

At least in my environment that problem does not occur.

The fact that it crashes every 10 seconds means that one of the macros may be causing the problem by running regularly.

Could you try to narrow down the problematic macros by switching the enable/disable switch in the macro list category?

Best Regards,
Liner Seven,
 
Hi, @huashimacro,

At least in my environment that problem does not occur.

The fact that it crashes every 10 seconds means that one of the macros may be causing the problem by running regularly.

Could you try to narrow down the problematic macros by switching the enable/disable switch in the macro list category?

Best Regards,
Liner Seven,
Hello, turning off all macros does not trigger a crash, but frequently toggling macros on and off can cause the application to crash. Additionally, the user log is not accessible through the general channel and the sharing feature is not functional. Here is the video of the issue. If you cannot access the video link, please enable a VPN to resolve the issue.
 

MacroDroidDev

Administrator
Staff member
@huashimacro Please use report a bug in troubleshooting so I can try and identify your crash in my crash logs. Please include the macro that causes the crash when you enable it.
 
@huashimacro Please use report a bug in troubleshooting so I can try and identify your crash in my crash logs. Please include the macro that causes the crash when you enable it.
I have already submitted a report, not sure if it has been received. There are three macro toggle actions that most easily trigger a crash in MacroDroid.
 

MacroDroidDev

Administrator
Staff member
I have already submitted a report, not sure if it has been received. There are three macro toggle actions that most easily trigger a crash in MacroDroid.
I don't seem to have any recent report from you related to this issue. Could you please try again?
 
I don't seem to have any recent report from you related to this issue. Could you please try again?
I've tried sending the report multiple times, but it might not have gone through due to regional network issues or some other reasons. I've shared the three macro files individually. Could you please try importing them to see if there's any issue of the system crashing?
 

Attachments

  • 电流-功率90W.macro
    673.7 KB · Views: 4
  • 王者秒换装.macro
    29.1 KB · Views: 2
  • 🔋enable可充电速度⏱️.macro
    7.3 KB · Views: 2

LinerSeven

Active member
I've tried sending the report multiple times, but it might not have gone through due to regional network issues or some other reasons. I've shared the three macro files individually. Could you please try importing them to see if there's any issue of the system crashing?
Hi, @huashimacro,

I understand that @huashimacro is from China.

Then you may not be able to attach detailed system logs.

In my environment (MD Beta v5.47.7 Pro), out of the three macros you attached, 'current efficiency 90W' became significantly unstable and Macrodroid hung, although no crash occurred.

It is a macro that makes it visible about the power supply of the system, but is the device being used introduced ColorOS, such as Xiaomi or OPPO?

----- Chinese Hantaiji as follows by Deepl,

好、HUASHIMACRO 先生、

HUASHIMACRO 先生来自中国。
那么您可能无法附上您系统的详细日志。

在我的环境中(MD Beta v5.47.7 Pro),在您所附的三个宏中,"电流效率 90W "明显不稳定,Macrodroid 挂起,尽管没有发生死机。

这是一个可以显示系统功率的宏,所使用的设备是否安装了 ColorOS(如小米或 OPPO)?

Best Regards,
Liner Seven,
 

Dm114

Well-known member
I've tried sending the report multiple times, but it might not have gone through due to regional network issues or some other reasons. I've shared the three macro files individually. Could you please try importing them to see if there's any issue of the system crashing?
Do you mean you followed the Troubleshooting procedure from the MacroDroid home screen?
 

MacroDroidDev

Administrator
Staff member
I've tried importing those macros and can't see any crash issues caused by them I'm afraid. @huashimacro can I please ask what device and OS version you are running this on.

The bug report is likely failing due to being in China and the Great Firewall of china blocking the services I use for email.
 
Hi, @huashimacro,

I understand that @huashimacro is from China.

Then you may not be able to attach detailed system logs.

In my environment (MD Beta v5.47.7 Pro), out of the three macros you attached, 'current efficiency 90W' became significantly unstable and Macrodroid hung, although no crash occurred.

It is a macro that makes it visible about the power supply of the system, but is the device being used introduced ColorOS, such as Xiaomi or OPPO?

----- Chinese Hantaiji as follows by Deepl,

好、HUASHIMACRO 先生、

HUASHIMACRO 先生来自中国。
那么您可能无法附上您系统的详细日志。

在我的环境中(MD Beta v5.47.7 Pro),在您所附的三个宏中,"电流效率 90W "明显不稳定,Macrodroid 挂起,尽管没有发生死机。

这是一个可以显示系统功率的宏,所使用的设备是否安装了 ColorOS(如小米或 OPPO)?

Best Regards,
Liner Seven,
The device I am using is equipped with Xiaomi Hyper OS. However, in version 5.47.7, the macro named "王者秒换装" cannot be opened or edited; it crashes every time I attempt to open it. The "90W" macro will crash after being opened twice. In versions prior to MacroDroid 5.47.5, these macros did not cause any MacroDroid crashes and all functioned normally without any issues. I have inspected these macro files and logs and did not find any calculation conflicts that would affect the normal operation of MacroDroid. It stands to reason that macros that are not actively running should not cause the app to crash.
 
Hi, @huashimacro,

I understand that @huashimacro is from China.

Then you may not be able to attach detailed system logs.

In my environment (MD Beta v5.47.7 Pro), out of the three macros you attached, 'current efficiency 90W' became significantly unstable and Macrodroid hung, although no crash occurred.

It is a macro that makes it visible about the power supply of the system, but is the device being used introduced ColorOS, such as Xiaomi or OPPO?

----- Chinese Hantaiji as follows by Deepl,

好、HUASHIMACRO 先生、

HUASHIMACRO 先生来自中国。
那么您可能无法附上您系统的详细日志。

在我的环境中(MD Beta v5.47.7 Pro),在您所附的三个宏中,"电流效率 90W "明显不稳定,Macrodroid 挂起,尽管没有发生死机。

这是一个可以显示系统功率的宏,所使用的设备是否安装了 ColorOS(如小米或 OPPO)?

Best Regards,
Liner Seven,
I may have found the cause of the crash issue. I discovered that versions 5.47 and later have added accessibility service status triggers and constraints. However, in the list of accessibility permissions, there is a lack of two assistive features: volume button monitoring and gesture monitoring. Version 5.46.10 still had four accessibility permissions, but in 5.47, there are only two. When macros are enabled and certain accessibility features are used, there might be an error in determining the status of the assistive features, which could lead to MacroDroid crashing!
 

Attachments

  • IMG_20240809_203720.jpg
    IMG_20240809_203720.jpg
    599.5 KB · Views: 10
  • IMG_20240809_203528.jpg
    IMG_20240809_203528.jpg
    512.3 KB · Views: 10

LinerSeven

Active member
I may have found the cause of the crash issue. I discovered that versions 5.47 and later have added accessibility service status triggers and constraints. However, in the list of accessibility permissions, there is a lack of two assistive features: volume button monitoring and gesture monitoring. Version 5.46.10 still had four accessibility permissions, but in 5.47, there are only two. When macros are enabled and certain accessibility features are used, there might be an error in determining the status of the assistive features, which could lead to MacroDroid crashing!
Hi, @huashimacro,

For the automation of Tencent Games' "Wangsha Yaoyao" app, would it be sufficient to have UI manipulation permissions?

I've written a macro to isolate it, but can the attached macro be imported into your environment? Can they be deactivated and made to work?

And if you have any other information, you should email me as @MacroDroidDev says.

----------

好、@huashimacro、

要实现腾讯游戏 "王者荣耀 "应用的自动化,是否只需拥有 UI 操作权限即可?

我编写了一个宏来隔离问题,但所附宏能否导入到您的环境中? 能否停用并使其生效?

如果您有任何其他信息,请按照 @MacroDroidDev 的说法给我发电子邮件。
 

Attachments

  • 王者秒换装・部分的試験.macro
    37.9 KB · Views: 4
Hi, @huashimacro,

For the automation of Tencent Games' "Wangsha Yaoyao" app, would it be sufficient to have UI manipulation permissions?

I've written a macro to isolate it, but can the attached macro be imported into your environment? Can they be deactivated and made to work?

And if you have any other information, you should email me as @MacroDroidDev says.

----------

好、@huashimacro、

要实现腾讯游戏 "王者荣耀 "应用的自动化,是否只需拥有 UI 操作权限即可?

我编写了一个宏来隔离问题,但所附宏能否导入到您的环境中? 能否停用并使其生效?

如果您有任何其他信息,请按照 @MacroDroidDev 的说法给我发电子邮件。
The "Honor of Kings" game has been encrypted, so MacroDroid is unable to read the view ID information of the "Honor of Kings" interface. The macro I wrote for quick equipment change in the game is implemented using X, Y coordinate clicking methods, which can only achieve clicks on a few fixed positions for game equipment. The screen trigger is also unable to read the game content on the screen. The MacroDroid UI accessibility service must be turned on along with the MacroDroid accessibility service. If only the MacroDroid UI accessibility service is turned on, the simulated click actions will not take effect.

The modified macro you sent cannot be imported into version 5.47.7, as MacroDroid will crash directly. However, it can be imported into version 5.46.10, and after enabling the necessary accessibility services, the macro can be opened and used. Therefore, I suspect that the issue is caused by the new accessibility service trigger and constraint features added in the version 47, which lead to the crashes.
 

LinerSeven

Active member
The "Honor of Kings" game has been encrypted, so MacroDroid is unable to read the view ID information of the "Honor of Kings" interface. The macro I wrote for quick equipment change in the game is implemented using X, Y coordinate clicking methods, which can only achieve clicks on a few fixed positions for game equipment. The screen trigger is also unable to read the game content on the screen. The MacroDroid UI accessibility service must be turned on along with the MacroDroid accessibility service. If only the MacroDroid UI accessibility service is turned on, the simulated click actions will not take effect.

The modified macro you sent cannot be imported into version 5.47.7, as MacroDroid will crash directly. However, it can be imported into version 5.46.10, and after enabling the necessary accessibility services, the macro can be opened and used. Therefore, I suspect that the issue is caused by the new accessibility service trigger and constraint features added in the version 47, which lead to the crashes.
好, @huashimacro,

I see, so you are saying that there is no problem with the older versions and the crashes are occurring in new beta version.

So we need 'more and more' crash reports. For developers' analysis.

For example, if there is a video recording function of the operation in HyperOS, it might be possible to utilise it to share the operating status with the developers.

Therein lies the problem of the Great Firewall(金盾). I don't think it's in the interest of the Chinese people, but I wonder if it could be uploaded as a video to Youku(优酷) Service for example...

Best Regards,
Liner Seven,
 
Last edited:

Jacob L

Moderator (Lawsonator)
好, @huashimacro,

I see, so you are saying that there is no problem with the older versions and the crashes are occurring in new beta version.

So we need 'more and more' crash reports. For developers' analysis.

For example, if there is a video recording function of the operation in HyperOS, it might be possible to utilise it to share the operating status with the developers.

Therein lies the problem of the Great Firewall(金盾). I don't think it's in the interest of the Chinese people, but I wonder if it could be uploaded as a video to Youku(优酷) Service for example...

Best Regards,
Liner Seven,
Does this catch the crash? https://github.com/TacoTheDank/Scoop
 

SHAWON

Member
Logcat Message Bug

• Logcat Message trigger not working when screen off.
• When new Logcat Message trigger add then edit, it's make duplicate trigger (same)
 
Status
Not open for further replies.
Top