not able to write to external storage

278 views
Skip to first unread message

N Mok

unread,
Sep 2, 2017, 9:53:38 PM9/2/17
to Tasker
any idea why I'm not able to write to my external storage? I'm running Android 7.0, root'd on an LGV20. my external storage is referenced as B45D-F8AF, but what's odd is that there's mention of A021-2A41, which I think may have been my old SD card. any suggestions on how to fix this?


21.36.10/Variables doreplresult: |%path| -> |/storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier|
21.36.10/Variables doreplresult: |%TNET| -> |T-Mobile|
21.36.10/Variables doreplresult: |%path| -> |/storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier|
21.36.10/FileUtil haveAccess: test : content://com.android.externalstorage.documents/tree/A021-2A41%3A wr: false ww: true ir: true iw: true
21.36.10/FileUtil haveAccess: fullPath: /
21.36.10/FileUtil nrda: need request: /storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier: false
21.36.10/E checkSDPath: /storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier useRoot: false there: false file: true dir: false
21.36.10/FileUtil Write File/checkSDPath: wudf: no write needed
21.36.10/E Write File: checkSDPath: /storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier useDocFile: false
21.36.10/E Write File: checkSDPath: /storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier ok true
21.36.10/Variables doreplresult: |%TNET| -> |T-Mobile|
21.36.10/FileUtil fromFileTree: stringToFile: /storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier createIntermediate: false leafMime: text/*
21.36.10/FileUtil extension from mime: null existing: 
21.36.10/FileUtil try tree: content://com.android.externalstorage.documents/tree/A021-2A41%3A path: /
21.36.10/FileUtil tree match: content://com.android.externalstorage.documents/tree/A021-2A41%3A/document/A021-2A41%3A remainder: storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier
21.36.10/FileUtil content://com.android.externalstorage.documents/tree/A021-2A41%3A/document/A021-2A41%3A: has no child storage lastElem: false
21.36.10/FileUtil stringToFile: no tree path for /storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier at part storage
21.36.10/FileUtil fromFileTree: stringToFile: no permission granted for /storage/B45D-F8AF/Android/data/net.dinglisch.android.taskerm/phone_carrier
21.36.10/E result: stop task (error)
21.36.10/E Error: 1
21.36.10/MacroEdit action finished exeID 1 action no 1 code 410 status: Err next 1

Pent

unread,
Sep 3, 2017, 5:32:50 AM9/3/17
to Tasker
Try granting permission in Menu / More / Android Settings.

The reference to the old SD is just because you granted permissions for it, which havn't
been revoked apparently.

Pent

N Mok

unread,
Sep 4, 2017, 12:54:19 AM9/4/17
to Tasker
Pent, I did do that... but no change. I ended up having to go into Settings > Apps > Tasker > Storage > External Storage > Clear access. after doing that then I was able to use what you mentioned to get everything working...

Michael DiGregorio

unread,
Jul 6, 2018, 11:19:18 AM7/6/18
to Tasker
N Mok--

Any idea how to steps would change on Android 6?  I'm having the same problem as you (put in a new SD card, which was given a different ID, and the same error as yours where it lists both the old and new ID).  However, when I go to Apps > Tasker > Storage, there is no option for "External Storage" (and thus "Clear Access").  Any ideas?

Thanks.

N Mok

unread,
Jul 6, 2018, 1:10:16 PM7/6/18
to Tasker
Unfortunately I'm not sure how you would do that on Android 6... unless someone else knows, the only other suggestion I would say to do is backup your Tasker settings and then wipe data followed by restoring the settings.

Michael DiGregorio

unread,
Jul 6, 2018, 1:50:10 PM7/6/18
to Tasker
Thanks for the reply.  :-)

Michael DiGregorio

unread,
Jul 6, 2018, 4:23:04 PM7/6/18
to Tasker
For anyone who has a similar problem, uninstalling, then reinstalling did fix the issue for me.  (running Android 6)
Reply all
Reply to author
Forward
0 new messages