[Galaxy S 4 Q&A, Help & Troubleshooting] Parinibbana:
Titanium Backup with insuffiecient storage space - 1 problem , 3 solutions

To summarize, I have come across three solutions to this problem. In fact, it´s four solutions now, since one additional method was pointed out by Vandevandel (see number two below).

1.

Change the backup-location to /storage/emulated/legacy/TitaniumBackup

Just open Titanium and go to Settings/Preferences/Backup folder location

Change to: /storage/emulated/legacy/TitaniumBackup

2.

There is an elegant way of giving TitaniumBackup write access to the external sdcard, without having to forfeit security (as in method 3 below).

Since the time of Android 4.3, Google uses a very clean security-solution by giving apps that request write access to external SD, permission only to their own folder - not to the entire card!

In order to get TitaniumBackup to work without compromising security, you can simply create a folder on the external sdcard,using the following folder-structure: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/

If you already have existing backups, move them with a file-explorer from their current place to: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/

Lastly, go tothe preferences of TitaniumBackup, choose "Backup folder location" and choose the above specified folder.

Finish.

Very clean and safe.

3.

There is a solution for gaining write access to the external sdcard (/mnt/sdcard2). The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. This permission was not required for access to the external sdcard prior to Android 3.2, but for security reasons this is the case now.

If you're rooted and want to make the ext. sdcard writable to all apps, please try the following:

1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.

2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.

3. Add an additional group definition for this permission...<group gid="media_rw" />

4. Save the changes to the file.

5. Restart your tablet.

Original:

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >

<group gid="sdcard_rw" />

</permission>

New:

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >

<group gid="sdcard_rw" />

<group gid="media_rw" />

</permission>

Done.

After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that accesses either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.

This may also fix problems with other apps that have issues writing to the ext. sdcard, but please be aware that in terms of security, solution two (see above) is preferable.

4.

If you had Titanium Backup installed on a previous ROM, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working. Reinstalling the app might lead to an insufficient storage space error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup.

Here’s how:

Using any file explorer like Root Explorer or ES File Explorer, go to /data/app , find and delete ”com.kermidas.TitaniumBackup-1.odex“. Now you can install Titanium Backup again!

If there is no such file in your folder, that´s OK. But please don´t delete any .apk file!

Good luck!

--------------------------------------------------------------------------------

If you find this post useful, pls feel free to click "Thanks".

Have a nice day