This is due to the 'Mount namespace separation' setting in SuperSU being turned on (by default). Untick that, reboot and try your Titanium Backup operation again.
This happens because the permissions to app-created folders are restricted in newer Android versions, I believe. Ironically, I didn't have this issue on Marshmallow-based CM13, but I did face it ...
Having a similar issue, I read through the comments to your question and ended up doing the following based on a hint suggested by Barleyman:
Go to Settings > Storage & USB › Internal Storage, click on "Migrate data" to move your data back to internal
In case you do not have enough space left on internal to move everything back (which was my case), ...
If you're getting "storage space runout" on your Samsung S2 phone, just dial *#9900# on the tablet and select option 2 “Delete dumpstate/logcat”
It's not necessary to root your android. Restart your phone afterwards.
Signed up to the site specifically to answer this question. I'm also using a Samsung Galaxy S2 with lots of storage but constantly full. I could not install applications or do pretty much anything.
I'm using Cyanogenmod, but this applies to all Androids.
What I did was using a file explorer with Root Permissions (to see all the files), navigated to the /...
Marshmallow internal storage can be better used with a mixed-format SD card as I also explain in my blog here:
First, you need adb working.
Have SD card inserted and formatted as portable.
Eject your SD card from the Storage & USB menu
Use "adb shell" to list your adoptable ...
This looks like the Acer GPS-log leak we had on an Acer Iconia A200:
The bottom line is that when the GPS is used, the GPS driver for ICS
4.0.3 on the Acer A-series tablets apparently writes numerous gl-YYYY-MM-DD-HHMMSS.txt files into the /data/gps directory. The files
are apparently not automatically deleted, and so over time will
consume most of ...
It has worked on Kitkat so may apply to older versions of Android
Settings > Storage > Phone Storage ( or could be Internal storage, wherever Google Play Services is) > apps > Google Play Services > Click Clear cache
(on the same page) Manage space > Clear all data > Manage search storage > clear now
press back button <- twice and you will end up on ...
Even though there already are many answers, there is actually none answering two main questions and the third one just for a case of dumpstate problem. Read just bigger text if you're in a hurry.
Also, I'll explain why solutions mentioned in other answers help only sometimes. And offer another solution in case cat is not your problem.
Why do I get Storage ...
According to Google
Google Play services provides you with easy access to Google services and is tightly integrated with the Android OS.
And from the description in the Play Store
Google Play services is used to update Google apps and apps from Google Play.
This component provides core functionality like authentication to your Google services, ...
Whilst you can uninstall it, it will automatically be re-installed on your device as it is an extension of the Google Play ecosystem and Google automatically updates Google Play services on all supported devices via the Google Play Store to ensure API consistency across devices and versions, and to deliver fixes and new features in a timely fashion.
Android's filesystem hierarchy is a bit complex and people often find it difficult to grasp. A major reason for confusion is that Android isn't very expressive in explaining these things and it's not very clear which files Android put in which category. Another reason is that mostly devices are not rooted and users don't have access to filesystems to verify ...
Many users have had the problem of "6GB of miscellaneous files". The problem might be because of /sdcard0/DCIM/.thumbnails.
You can go ahead and delete the folder. This may free up your memory. To delete .thumbnails folder, you need a file manager that can see hidden files. After deleting the folder, also delete LOST.DIR and reboot. ...
The problem you are facing is not uncommon. Namely Android operating system (like any other) provides different partitions for different usages, among them there is a partition for user installed apps ("apps partition"), and that partition is usually 1 GB or 2 GB or less (depending on the total memory of the device). And you do have only 28 MB on your ...
This happens due to some service change in kitkat. Some research on google showed that there is an app available to modify the platform.xml file. The app once run, prompts the user to allow it to go ahead and make the modifications to the above file. Everything works fine after this.
Right, I have the solution. Swipe down to get notifications, then hold down on the screen where it says 'insufficient storage'. A little window will appear saying 'app info'. Press that and it will take you to settings of your android system. There is a ticked box saying 'show notifications'
Untick that box and the problem is solved.
( the box can be ticked ...
At TB's startup it always displayed a warning that SuperSU's namespace separation feature "might not work reliably on some platforms".
Well, I never faced any problems until a recent SuperSU update...
So disabling that option in SuperSU and rebooting solved the "insufficient space" on my OnePlus One/CM12.1.
This was the obvious solution before fiddling ...
I have the same phone & same SD card setup. David Coleman has good advice, but here are some additional points.
Many apps will not even show the word "Change." That means they cannot be moved to the SD card. Keep looking for ones that do have that word showing.
At least on my phone, every time I tapped on "Change" it came back with an error message. ...
Note: the quoted user was me. And here is the reference. To explain why it wasn't 10% in your case, here's an exception from behind the link: "As long as the device maker doesn't change the default settings". So those 10% are the default setting, but obviously can be altered by the "ROM baker". How often that is done I cannot tell; with that post being from ...
Simple solution. Press phone and select keypad. dial *#9900#. A new menu appears. press the second one down "Delete dumpstate/logcat" then just press home to exit.. Done, you'll have bags of extra device memory with no ill effects. Should free up to a gig of device memory, it did on mine.
Download and install Java Development Kit from Oracle’s website. I downloaded JDK 7u2 for Windows x64 (approximately 87 MB)
Download and install Android SDK from Google’s website. I preferred the recommended Windows Installer
Run Command Prompt with Administrator Privileges on Windows 7 or Windows 8 OS. (Start Menu → type in cmd → Right click ...
See App Install Location for what could be the reason
When your application is installed on the external storage:
The .apk file is saved on the external storage, but all private user data, databases, optimized .dex files, and extracted native code are saved on the internal device memory.
First of all, symlinks don't work on Android's emulated storage. A workaround is to use bind mounts instead. See this answer for details.
But with Adoptable Storage you don't need to:
Create symlink to external SD card
Manually move data to external SD card
Bind mount a directory from external SD card
Because what you see as /sdcard or /storage/emulated/0 ...
Link2SD only moves the app itself to your device's SDCard. App data still go to internal storage (/data/<package_name>). For every app you install, the Android system automatically creates this directory – and I don't know of any app that doesn't put at least a few files here.
For details, please take a look at the app2sd tag-wiki. It not only ...
While several hints can be found in the insufficient-memory tag-wiki, you case seems a little special – as you report to still have ~75 MB free (3 times the limit this error should be triggered).
This should even enable you to install a file manager (if you have not already done so, or a useful file manager was pre-installed). So in order to remove some ...
The answer is...It depends.
As a rough equivalent between Android and Windows PCs:
RAM = RAM
Internal Storage = C: drive
External Storage = D: drive etc...
Allocation of RAM works differently in Android, vs. say Windows or Unix. The usual notion of more is better doesn't necessarily correlate here.
As I understand it, it's diminishing returns once you ...