Disabling "scoped storage" via ADB on Note 10+ updated to Android 11

So far for me it didn't work.
Using my Note10+ (Exynos Variant) with Android 11 OnUI 3.0 last updatet by end of january to the second Android 11 release for this device.
Full Samsung Stock and not rootet.
What did I test?
With Samsung's own File Explorer (My Files) on pre Andorid 11 Firmware you have fully access to the Android/data folder on the SD-Card (External Storage).
Since Google mandatory Scoped Storage with Android 11, the Samsung's File Manager My Files only shows an empty directory here.
But via adb shell I have read access to all folders in the directory Android/data on my SD-Card (External Storage)
with ls -lah --color i can see all the subfolders that containing the specific app Data.
Unfortunately the adb shell rm commend doesn't work.
So if there is any Applikation writing to the Android/data/nameofApp Folder this could be running in problems with less storage.
If the App has the option build in to move or delete files from this location this will help, but if not I see no way tzo delete that zombie files from the sd-card, except to remove the card from the device and try to access it via an adapter from the PC or Mac. But this will only work on non encrypted sd-cards!

So i give it a try with the adb shell
after connecting to my device i opened the shell for adb with te command adb shell


so i guess the force close was necassary for overtaking the changed app options.

This doesn't change anything, so for me it doesn't work.

The only way, in my opinion, is that samsung is going to request a special Access (MANAGE_EXTERNAL_STORAGE) by google for their app my files, as mentioned at the end of the linked youtube video.

paggps said:

Disable:
adb shell cmd appops set your-package-name android:legacy_storage allow && \
adb shell am force-stop your-package-name

Enable:
adb shell cmd appops set your-package-name android:legacy_storage default && \
adb shell am force-stop your-package-name

Did someone try these ADB commands? Teoretically, with these one can fix any compatibility issue with Android 11.

Thank you.

Click to expand...

Click to collapse

hi out there

i did try these commands and they worked for Osmand and Sygic, as well as for Root Explorer. of course you have to be rooted.
i am still struggling with windows, not seeing /Android/data on the SDcard though.
would anyone happen to know, to which apps i have to apply those commands to allow windows to write to external/android/data/ ?

what i absolutely do not understand: this scoped storage was introduced to raise security, in the way that apps can't see other apps data. but: looking at internal storage Android/data/ i see all files and i can also overwrite them.

i assume, that these changes will be gone, once you update the apk and you will have to re-apply them. also this is a temporary behaviour - i assume google will in the future prevent these modifications.

conclusion: if i want to use two apps like Guru Maps and Osmand, both of them store around 50 GB of data just for Europe, i have to have all those maps in the internal memory. let's assume i only have 128 GB ... Or, as far as i understood, you can still have the data on the sdcard (some apps can), but everytime you startup the app, it will copy the data to a temp directory to internal memory - which is in fact the same as having the data in internal: you NEED to have the space. i tried with Osmand - it works, but it takes ... around 20 minutes until the app starts.

all this seems not to be very handy to me

blackspy_ said:

hi out there

i did try these commands and they worked for Osmand and Sygic, as well as for Root Explorer. of course you have to be rooted.
i am still struggling with windows, not seeing /Android/data on the SDcard though.
would anyone happen to know, to which apps i have to apply those commands to allow windows to write to external/android/data/ ?

what i absolutely do not understand: this scoped storage was introduced to raise security, in the way that apps can't see other apps data. but: looking at internal storage Android/data/ i see all files and i can also overwrite them.

i assume, that these changes will be gone, once you update the apk and you will have to re-apply them. also this is a temporary behaviour - i assume google will in the future prevent these modifications.

conclusion: if i want to use two apps like Guru Maps and Osmand, both of them store around 50 GB of data just for Europe, i have to have all those maps in the internal memory. let's assume i only have 128 GB ... Or, as far as i understood, you can still have the data on the sdcard (some apps can), but everytime you startup the app, it will copy the data to a temp directory to internal memory - which is in fact the same as having the data in internal: you NEED to have the space. i tried with Osmand - it works, but it takes ... around 20 minutes until the app starts.

all this seems not to be very handy to me

Click to expand...

Click to collapse

Scope storage is a resource hog and serves little or no purpose for experienced users.
Know what you load, monitor, and use a VNP firewall like Karma Firewall* to enforce security.

I refuse to leave Pie for the psuedo security bs of Q and 11. It's performance impact is less noticeable on the even faster cpu's/ram of the newest phones but it's stealing their edge too.




*Karma's logging feature appears to not work with Q and above... you know for security

Scope storage is another 'milestone' on Google's way, which in my opinion goes in the absolutely wrong direction, of taking away more and more rights from the Android user over his device and patronizing the user more and more.
With this, Google takes away a not to be underestimated advantage of its operating system compared to IOS, in addition completely unnecessary because the security of private data can also be ensured in a much simpler way.
For whatever reason Google is going down this path, it once again looks as if this is a side blow against expandable memory, SD cards have always been a thorn in Google's side.

Tanis64 said:

Scope storage is another 'milestone' on Google's way, which in my opinion goes in the absolutely wrong direction, of taking away more and more rights from the Android user over his device and patronizing the user more and more.
With this, Google takes away a not to be underestimated advantage of its operating system compared to IOS, in addition completely unnecessary because the security of private data can also be ensured in a much simpler way.
For whatever reason Google is going down this path, it once again looks as if this is a side blow against expandable memory, SD cards have always been a thorn in Google's side.

Click to expand...

Click to collapse

Lol, another depth marker as Google heads to crush depth.
Google must be smoking Bill Gates bad stash and are power mad. They want to control everything and everyone. A malignant cancer at this point.

Anyone thinking about loading 11 better read this.
Quick summary; it's a lick on you.

Here's a possible workaround for some of this crap... maybe:

blackhawk said:

Here's a possible workaround for some of this crap... maybe:

How to get rid of Google Photos' out-of-sync changes prompt on Android 11

The fix requires an ADB shell command and only works on some phones

www.androidpolice.com

Click to expand...

Click to collapse

I don't think scoped storage is the best thing under the sun, however, I work with IT users all day, sometimes they do the weirdest stuff imaginable, dumb stuff that defies common logic, other times they do things I didn't even know where possible and screw up.

I think scoped storage is like child proofing. We know it sucks, we know it restricts us but for the average Joe it may actually be useful.

I once had a user call me because they wanted to #upgrade the DPI on a S8 and increased it out of the displays range. I have no idea where he went and got that information, how he ran the command and why, but he lost the phone, went to OEM support where they told him no fix was available besides MB replacement (squeezing cents maybe) and I helped him by setting the default values via ADB. Still have no idea where he got that info and why he wanted to do it...

Sometimes the needs of the many really outweigh the needs of the few ...

Bomn said:

I don't think scoped storage is the best thing under the sun, however, I work with IT users all day, sometimes they do the weirdest stuff imaginable, dumb stuff that defies common logic, other times they do things I didn't even know where possible and screw up.

I think scoped storage is like child proofing. We know it sucks, we know it restricts us but for the average Joe it may actually be useful.

I once had a user call me because they wanted to #upgrade the DPI on a S8 and increased it out of the displays range. I have no idea where he went and got that information, how he ran the command and why, but he lost the phone, went to OEM support where they told him no fix was available besides MB replacement (squeezing cents maybe) and I helped him by setting the default values via ADB. Still have no idea where he got that info and why he wanted to do it...

Sometimes the needs of the many really outweigh the needs of the few ...

Click to expand...

Click to collapse

No one needs a big sister... not even a moron.
The biggest source of malware is still the user.
The user needs a certain level of wherewithal otherwise something will eat them for sure.
No saving dumb bunnies.

The Star Trek movies just suck more the older I get

ungoogled-chromium-android-extensions apparently doesn't support android 11 "scoped storage" (more info on

android 11 : this app (ungoogled-chromium-android-extensions) can not longer load files (d3ward's floatly extension) from phone storage ? it worked on android 10 though ... any help ??
by u/pierro78 in AndroidQuestions

) does somebody know if there would be a workaround in android 11 to allow ungoogled-chromium-android-extensions to load extensions from the phone storage ??

thanks !

​

​

I just got a new N10+ that's running on Android 10 (so I have one running on Pie, one on Q).
Q concerned me however it appears scoped storage isn't active on any of my apps maybe because they are older. Other than killing Karma Firewall's valuable logging feature almost everything else including the Double Tap apk seems to work. Permissions and navigation are worse than Pie but not completely overbearing like they are in R. Dark mode is better.
Q maybe snapper than Pie, power consumption is similar; too soon to call that though.

Do Not upgrade to 11, it's not a pretty picture. Q is as high as you can go without incurring major bs issues. R is a bloatware packed hog of a OS.
If this fat lady sings... run.

edit, got my Q's and R's confused... feel the stress
Q killed the hell out of Brave browser. No fix. Now bad sites can hide in plain sight.
Good Lock's analog clocks suck, of course Samsung just had to change styles to be hip. Groovy.

If I disable Framework the battery life in Q might exceed my Pie variant however overall it's less functional because of excessive app restrictions. Pie had similar but less restrictive issues as Q while R is just simple unusable... R is a no go, a dead horse in the sun is no fun.
My Pie variant never has any malware issues, only Android's already over active security restrictions. What's Android do? Made it even worse.
Fktard Gookill, you do know the definition of insanity, don't you?

This may be helpful. It doesn't apply to me yet but it seemed interesting...

If you're running on Pie, Q or R draw the line in the sandbox and stay on your current OS!
Disable OTA updates asap*.
Pie, great usability and functionality, reasonably secure.
Q, not as good but still reasonably usable/functional.
R, it's starting to really hurt.
12... fubar, avoid at all costs


*OTA update apks that need to be killed:

blackhawk said:

No saving dumb bunnies.

Click to expand...

Click to collapse

Exactly. Learning how to use a phone is necessary, just like learning to drive. At the very least, power users should have the an option to get back normal access.

Tanis64 said:

SD cards have always been a thorn in Google's side.

Click to expand...

Click to collapse

Indeed. Google has a conflict of interest as a provider of cloud storage. Imagine SanDisk owned Android and blocked Google Drive. Everyone would recognize the conflict of interest. And end users complain to the developers rather than Google.

[This post is in the public domain, CC0 1.0, excluding quotes.]

See also:

• Don't kill my app
• Why Google's arguments to restrict storage access are nonsense.
• MicroSD cards give you control over your data.