1

moving media bug

Versions after 5.14.8 have an error, the action of moving a photo or screenshot from folder to folder tightly hangs the media scanner process, only a reboot helps (I tried on 3 Xiaomi mi 11 ultra, Redmi note 10 pro, Redmi note 9 pro devices).

As a result, the moved files in the gallery of any applications are missing until the reboot (telegram, regular gallery or any of the market).

Example:

A1: Wait [MS: 700]

A2: List [Directory: DCIM/Screenshots/ Sort Select: Alphabetic Variable Array: %SCREENSHOTS ]

A3: Move [From: %SCREENSHOTS(1) To: Pictures/Screenshots ]

A4: Vibrate [Time: 200 ]

A5: Scan Media [File: DCIM/ ]

On the version 5.14.8 all works good!

Follow

2 replies

Votes Newest Oldest
АК 
<TaskerData sr="" dvi="1" tv="5.14.8">
        <Profile sr="prof7" ve="2">
                <cdate>1640285533520</cdate>
                <edate>1669051166494</edate>
                <flags>8</flags>
                <id>7</id>
                <mid0>6</mid0>
                <nme>Screenshot Mover</nme>
                <Event sr="con0" ve="2">
                        <code>222</code>
                        <pri>0</pri>
                        <Str sr="arg0" ve="3">DCIM/Screenshots/</Str>
                        <Str sr="arg1" ve="3">Modify</Str>
                </Event>
        </Profile>
        <Task sr="task6">
                <cdate>1640285282514</cdate>
                <edate>1669051151753</edate>
                <id>6</id>
                <nme>Screen_Mover</nme>
                <pri>6</pri>
                <Action sr="act0" ve="7">
                        <code>30</code>
                        <Int sr="arg0" val="700"/>
                        <Int sr="arg1" val="0"/>
                        <Int sr="arg2" val="0"/>
                        <Int sr="arg3" val="0"/>
                        <Int sr="arg4" val="0"/>
                </Action>
                <Action sr="act1" ve="7">
                        <code>412</code>
                        <Str sr="arg0" ve="3">DCIM/Screenshots/</Str>
                        <Str sr="arg1" ve="3"/>
                        <Int sr="arg2" val="0"/>
                        <Int sr="arg3" val="0"/>
                        <Int sr="arg4" val="0"/>
                        <Str sr="arg5" ve="3">%SCREENSHOTS</Str>
                </Action>
                <Action sr="act2" ve="7">
                        <code>400</code>
                        <Str sr="arg0" ve="3">%SCREENSHOTS(1)</Str>
                        <Str sr="arg1" ve="3">Pictures/Screenshots</Str>
                        <Int sr="arg2" val="0"/>
                </Action>
                <Action sr="act3" ve="7">
                        <code>61</code>
                        <Int sr="arg0" val="200"/>
                </Action>
                <Action sr="act4" ve="7">
                        <code>459</code>
                        <Str sr="arg0" ve="3">DCIM/</Str>
                </Action>
        </Task>
</TaskerData>
Comment

Hi. Thanks for the report. can you clarify what you mean by "tightly hangs the media scanner process"? Thanks in advance.

Comment
АК

After moving the media file using the tasker script, the Android media scanning service broken.

This is observed as follows: for example, a screenshot was taken, tasker transferred a file from folder to folder, and after that new media files stop being displayed in galleries (as standard, in the telegram application, etc.). After restarting the phone, everything starts working fine until the script starts working again.

p.s example scenario below

Oh, I see. Unfortunately that seems like a bug in the Android OS itself. Tasker simply moves a file. It doesn't control the system Media scanner itself... Sorry!

АК

The fact is that version 5.14.8 all works fine, the problem started from the 5.15.12+ update

There are dozens of messages about this on the 4pda thematic forum, but no solutions have been found, except for using the old version

Ok, thanks for the info. Do you know which was the last version that it worked on? For example, did it work on 5.15.0?

АК

In version 5.14.8 (November 3, 2021) everything works fine.

The next stable update (5.15.12) caused this problem

------
The problem is reproduced in all subsequent versions:

Tasker (Play Store version) 5.15.3-beta

Tasker (Play Store version) 5.15.4-beta

Tasker (Play Store version) 5.15.6-beta

Tasker (Play Store version) 5.15.10-beta

Tasker (Play Store version) 5.15.12

Tasker (Play Store version) 5.15.13

Tasker (Play Store version) 5.15.14

Tasker (Play Store version) 6.0.0-beta

Tasker (Play Store version) 6.0.2-beta

Tasker (Play Store version) 6.0.4-beta

Tasker (Play Store version) 6.0.5-beta

Tasker (Play Store version) 6.0.7-beta

Tasker (Play Store version) 6.0.8-rc

Tasker (Play Store version) 6.0.9

Tasker (Play Store version) 6.1.4-beta

Thank you! Would it be possible for you to test the in-between versions available here?

https://drive.google.com/drive/folders/1GW55YKFiuOZhJVswnt_BQUCJoGm36ugF?usp=sharing

Thanks in advance!

АК

Yes, I will do it within an hour and give feedback! Thank you so much for responding!

Thank you very much!!

АК

So, I have a separate phone where I conduct various tests. The system (Android 12) is completely clean.

Tasker-5.14.8-20211116_1041.apk - all works fine.

test procedure

1. I installed the application where there is no problem (Tasker-5.14.8-20211116_1041.apk) checked the correct operation.
2. Updated applications on Tasker version-5.15.0-20211111_0906.apk
3. The problem has appeared.
4. Updated to the next version of Tasker-5.15.0-20211111_0913.apk
5. The problem persists.
6. And so we continued updating all versions to beta 6.1.6 with checking the problem.

Next.

Аfter completing the tests, I shot a short video 5.14.8-20211116_1041 where there is no problem and where the problem appeared on version 5.15.0-20211111_0913 and on the latest beta version 6.1.6-beta-2022118_1408

Video: https://drive.deep-net.ru/s/qoKwiBzyzd9YY7r

Thank you! :) I tried changing something based on that info. 

Does this version work for you? https://drive.google.com/file/d/19w0kkEle9oinGusDHMe-1f1u6_xuuifD/view?usp=sharing

If you want you can also check any previous releases here: https://drive.google.com/drive/folders/1GW55YKFiuOZhJVswnt_BQUCJoGm36ugF?usp=sharing

АК

Hello!

Now day I checked (~200 screens)! Yes it's Works correctly!

Tasker.30.apk - everything worked fine all day! It looks like you have found and fixed problem :)

Big thanks!!!!!!!! :)

Unfortunately it's not that easy: the fix is targeting an earlier Android API version, which I cannot do for Tasker on Google Play. :( More details here: https://tasker.joaoapps.com/userguide/en/target_api.html

The Tasker Google Play version can't target old API versions, so I'll have to change it again for the next release. If you really want to keep a version that targets an older API you could purchase the direct purchase version of the app.

Sorry!

АК

Can I learn a little more about how to make a purchase? As far as I read, you can only buy from 25 licenses.... :( That's a lot for me alone

https://tasker .joaoapps.com/faq-ov.html

To purchase a license for the direct-purchase version please sign up as a Patron here: https://www.patreon.com/joaoapps
After you sign up I'll send the corresponding amount of licenses to you. :) Each $4 there grants you a license.

If you want multiple licenses you can sign up with a higher tier right away (for example $8 for 2 licenses, $12 for 3 licenses, etc) or just wait the number of months until the correct $ amount has accumulated.

Let me know if you have any questions!

Reply