Hello everyone,
After the new update the storage permission option is gone from App Permission,though there is Media & Files permission but appa like "Vivavideo" & "Picsart" is unable to save the end project due to missing storage permission.
Need help on this asap, unable to save my video & Picture projects.
You will have to wait till they release there software that is compliant with Android 11.
This is because of scoped storage in android 11. The other comment is right. The software needs to be updated to support scoped storage.
Related
UPDATE: Google's API changes to KitKat means the following, as per Google:
An application may request broad read-oonly permissions for external storage. This means that the application will be able to read the MicroSD only.
Applications cannot obtain permission to write to external storage. This means that file managers cannot edit/create/delete files on MicroSD anymore. This is a casualty of a change meant for security.
With or without requested permission for external storage, an application may now modify conents of its assigned folder on external storage (IE, /android/data). This allows an application to offload content to external storage if the storage is considered "permanent," Ie, MicroSD is considered permanent while OTG is not.
The benefits to this change means that applications required less tweaking to offload their data to external storage. We saw this with the recent Google Music update (and I'm loving that). Even now, it seems updates to recent Google applications are preparing to utilize this functionality. Google's camera.apk has taken up residence on my MicroSD so I suspect that a future update will allow you to store to external storage.
The downsides are that file managers cannot make use of MicroSD anymore, aside from reading the contents. Consider it collateral damage.
-reserved-
Titanium backup. Requires external SD permissions.xml fix to be able to store there.
Sent from my GT-I9505G using Tapatalk
ES doesn't work. If you delete a folder, it will show as deleted. Exit and come back, and the folder remains. Cannot edit or create a folder (in MicroSD).
Bump. OP now has full explanation of what's going on.
jaykresge said:
UPDATE: Google's API changes to KitKat means the following, as per Google:
An application may request broad read-oonly permissions for external storage. This means that the application will be able to read the MicroSD only.
Applications cannot obtain permission to write to external storage. This means that file managers cannot edit/create/delete files on MicroSD anymore. This is a casualty of a change meant for security.
With or without requested permission for external storage, an application may now modify conents of its assigned folder on external storage (IE, /android/data). This allows an application to offload content to external storage if the storage is considered "permanent," Ie, MicroSD is considered permanent while OTG is not.
The benefits to this change means that applications required less tweaking to offload their data to external storage. We saw this with the recent Google Music update (and I'm loving that). Even now, it seems updates to recent Google applications are preparing to utilize this functionality. Google's camera.apk has taken up residence on my MicroSD so I suspect that a future update will allow you to store to external storage.
The downsides are that file managers cannot make use of MicroSD anymore, aside from reading the contents. Consider it collateral damage.
Click to expand...
Click to collapse
Reading from Android Developer new API changes tha way you read and write from External Sd card... but if your app has WRITE_EXTERNAL_STORAGE permission it should be able to write your ext sd card without problems.
This means that current apps (and File Managers) should be updated to support kitkat API level 9 and obtain WRITE_EXTERNAL_STORAGE permission.
public static final String WRITE_EXTERNAL_STORAGE
Added in API level 4
Allows an application to write to external storage.
Note: If both your minSdkVersion and targetSdkVersion values are set to 3 or lower, the system implicitly grants your app this permission. If you don't need this permission, be sure your targetSdkVersion is 4 or higher.
Starting in API level 19, this permission is not required to read/write files in your application-specific directories returned by getExternalFilesDir(String) and getExternalCacheDir().
Constant Value: "android.permission.WRITE_EXTERNAL_STORAGE"
API level 19 is kitkat code....
Regarding 4.4 Kitkat External SD Card access permision, anyone can explain to us what is the objective of having such rigid permissions ?
"....
Starting in Android 4.4, the owner, group and modes of files on external storage devices are now synthesized based on directory structure. This enables apps to manage their package-specific directories on external storage without requiring they hold the broad WRITE_EXTERNAL_STORAGE permission. For example, the app with package name com.example.foo can now freely access Android/data/com.example.foo/ on external storage devices with no permissions. These synthesized permissions are accomplished by wrapping raw storage devices in a FUSE daemon.
..."
Full source : http://source.android.com/devices/tech/storage/
On 4.3 and older, a malicious app can wipe the whole sdcard with standard permissions. New permissions prevent it.
aydc said:
On 4.3 and older, a malicious app can wipe the whole sdcard with standard permissions. New permissions prevent it.
Click to expand...
Click to collapse
So this is useful then not a considered 'bug'..
I guess there will be no benefits anymore to use 3rd party file manager if we dont root our phones. Niche market just collapsed.
Sorry, but I have follow up questions:
I wonder how many malicious pieces of software like that are in a Google Play store to warrant breaking most third party applications that write to SD card? But I guess now, that apps can't write to SD card, there will be not much to protect there anyhow? And how will this all work in the future, once apps get their permissions fixed? I won't be allowed to access my card or format it at will? or will I be able to grant those permissions, but then how would I know the software is malicious any more than I know now? Am I too stupid to grasp the logic of all this?
pete4k said:
Sorry, but I have follow up questions:
I wonder how many malicious pieces of software like that are in a Google Play store to warrant breaking most third party applications that write to SD card? But I guess now, that apps can't write to SD card, there will be not much to protect there anyhow? And how will this all work in the future, once apps get their permissions fixed? I won't be allowed to access my card or format it at will? or will I be able to grant those permissions, but then how would I know the software is malicious any more than I know now? Am I too stupid to grasp the logic of all this?
Click to expand...
Click to collapse
That's what I had in mind too but if you see from the source link above I think Google is anticipating MULTI USER environment where some "stuffs" from me could wrack havoc some of "your stuffs". That scenario actually will only happen on MULTI USER tablet / smartphone, but that surely not mainstream are they ?
pete4k said:
Sorry, but I have follow up questions:
I wonder how many malicious pieces of software like that are in a Google Play store to warrant breaking most third party applications that write to SD card? But I guess now, that apps can't write to SD card, there will be not much to protect there anyhow? And how will this all work in the future, once apps get their permissions fixed? I won't be allowed to access my card or format it at will? or will I be able to grant those permissions, but then how would I know the software is malicious any more than I know now? Am I too stupid to grasp the logic of all this?
Click to expand...
Click to collapse
As stated on source.android.com:
Starting in Android 4.4, the owner, group and modes of files on external storage devices are now synthesized based on directory structure. This enables apps to manage their package-specific directories on external storage without requiring they hold the broad WRITE_EXTERNAL_STORAGE permission. For example, the app with package name com.example.foo can now freely access Android/data/com.example.foo/ on external storage devices with no permissions. These synthesized permissions are accomplished by wrapping raw storage devices in a FUSE daemon.
Has anyone tried to download a file in Chrome? It says it needs storage permission, but there's no longer a storage permission in Q. So basically you can't download files
Caution: Beta 2 introduces significant behavior changes that affect apps. In particular, the latest updates around isolated storage may cause issues with apps that access photos, videos, media, or other files stored on your device, such as when browsing or sharing in social media apps. You may notice this even more if you factory reset your device after taking the over-the-air update (OTA), or when installing new apps.
Click to expand...
Click to collapse
https://www.reddit.com/r/android_beta/comments/b90uvx/android_q_beta_2_now_available/
That said, I have no issues downloading files with Chrome. I don't see storage as a permission for it.
I have the same issue, workaround was to use Chrome beta.
no storage permissions also here with new patch for b2
yes, (dead brained) android developers again broken the file-system access....
as lot of users that have an old device, I use app2sd app to move my app to sdcard (because adoptable storage is a sh..t, that don´t even care about partitioning a sdcard to still allow to use it to store data that I want to access from a pc when the phone has problems... again, theses "clever" google engineer didn't even asked themselves why user created app2sd like app... why they chosen to use dedicated partition and still allow to have a shareable storage... ) , my sdcard speed is fast enough to not see any difference between internal storage and sd card stored app, and I worry more about emmc aging than a few ms....
BUT, seems that the APP_DATA_DIRECTORY_ISOLATION feature prevent moving the data to sdcard, I use lineageos, in developper settings there is override per application compatibility, when I uncheck APP_DATA_DIRECTORY_ISOLATION in this for a particular app linked to sdcard, this solve the issue, and a sd card stored app can be used...
however, this settings isn't persistent... so on next reboot I have to do it again for every app linked to sdcard....
and you know what? it was reported to android dev, that replied... to buy a new phone!!! because emmc storage is much more faster.... I begin to really get upset at android, they took a nice system (linux) and made it s....t, and more, how many cpu power is lost by android checks (since it can be desactivated on the fly per app... this isn't something that rely on kernel....)
so my question, is it possible to have this option set to off by default on boot? how?
thanks
jl forums said:
yes, (dead brained) android developers again broken the file-system access....
as lot of users that have an old device, I use app2sd app to move my app to sdcard (because adoptable storage is a sh..t, that don´t even care about partitioning a sdcard to still allow to use it to store data that I want to access from a pc when the phone has problems... again, theses "clever" google engineer didn't even asked themselves why user created app2sd like app... why they chosen to use dedicated partition and still allow to have a shareable storage... ) , my sdcard speed is fast enough to not see any difference between internal storage and sd card stored app, and I worry more about emmc aging than a few ms....
BUT, seems that the APP_DATA_DIRECTORY_ISOLATION feature prevent moving the data to sdcard, I use lineageos, in developper settings there is override per application compatibility, when I uncheck APP_DATA_DIRECTORY_ISOLATION in this for a particular app linked to sdcard, this solve the issue, and a sd card stored app can be used...
however, this settings isn't persistent... so on next reboot I have to do it again for every app linked to sdcard....
and you know what? it was reported to android dev, that replied... to buy a new phone!!! because emmc storage is much more faster.... I begin to really get upset at android, they took a nice system (linux) and made it s....t, and more, how many cpu power is lost by android checks (since it can be desactivated on the fly per app... this isn't something that rely on kernel....)
so my question, is it possible to have this option set to off by default on boot? how?
thanks
Click to expand...
Click to collapse
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
So I recently ran out of storage on my Motorola G Power 2021, so I bought a micro SD to move some of my less-used but not quite expendable apps. Originally I'd planned to format as internal storage, but my phone doesn't appear to allow this and doesn't even show the option to do so. So I opted for the next best thing, migrating some of the app data over by going to Apps & notifications > All Apps > (app) > Storage & cache, but there's no option to move the app to the external storage device. As per the title, I also turned "Force allow apps on external" in developer settings to no avail. Could Motorola be blocking this too? I've done a little searching, and I can't seem to find any examples of this other than this one which was on a completely different phone brand and this one which seems to have been caused by misunderstanding and resolved.
What I've tried:
Restarting phone - didn't help
Checking other apps - checked about a dozen and none had the move to external storage option
Rooting - can't unlock bootloader as per Motorola's website
Does anyone have any idea what could be causing this, if I can work around it, or even if I can somehow format as internal storage? Any help would be greatly appreciated.
Installing apps over to the microSD card isn't supported by all apps. In fact, many don’t support this feature at all. Some manufacturers - namely, Samsung and LG - reviously allowed users to format microSD cards as internal storage. That meant apps and games would be installed there by default. Sadly, this feature is no longer present on newer devices.
Technically, it’s still possible to install apps on the microSD if you’re willing to go through the trouble of rooting your Android phone and afterwareds use Link2SD to move the apps from internal storage to exernal storage.
xXx yYy said:
Installing apps over to the microSD card isn't supported by all apps. In fact, many don’t support this feature at all. Some manufacturers - namely, Samsung and LG - reviously allowed users to format microSD cards as internal storage. That meant apps and games would be installed there by default. Sadly, this feature is no longer present on newer devices.
Technically, it’s still possible to install apps on the microSD if you’re willing to go through the trouble of rooting your Android phone and afterwareds use Link2SD to move the apps from internal storage to exernal storage.
Click to expand...
Click to collapse
I thought the purpose of "Force allow apps on external" was to be able to transfer any app regardless of the developers' wishes. Is this not the case?
you already gave the answer yourself
Wrig9 said:
Originally I'd planned to format as internal storage, but my phone doesn't appear to allow this and doesn't even show the option to do so.
Click to expand...
Click to collapse
alecxs said:
you already gave the answer yourself
Click to expand...
Click to collapse
Does it have to be formatted as internal storage to be allowed to transfer apps? I guess I didn't really think about that.
Edit: Just to be sure we're all on the same page, the SD card is formatted, just not as part of the internal storage. I can access any files on it, but I can't put any apps there. I was under the impression that if you formatted as internal storage the SD card would act as a direct expansion somehow and automatically install data there once the integrated storage filled.
I haven't tested that specific option but afaik it overrides android:installLocation="preferExternal" in app manifest. that would allow to move the apk to Adoptable Storage, but requires MicroSD Card formatted as internal.
Only new apps are installed external automatically (based on that setting), for existing apps the "Migrate Data" option is offered.