Is there better way to get applications on sd card. Why are we using ext2 ? We can format sd card and partition it without using pc . We can format it into native supported file system of fat. why are need to make dev when in /dev/block device exist ? we need just to modifiee mounted.conf and /etc/fstab
I think because it's easier to say then to do But if you can make it so easy i love to use youre methode! (newest way is pretty easy, flash modded JF rom and exec a script and you are done: http://forum.xda-developers.com/showthread.php?t=480582)
I would think that you could run into issues with permissions/etc if you tried to use a FAT filesystem to store applications.
About the only advantge of FAT is its ubiquity. In every other regard there is a better solution out there. Ext2 is by far the most widely supported linux filesystem that supports the full POSIX feature set.
simply put FAT32/VFAT is a horid horid filesystem, and does not support unix permissions, symlinks, etc.
EXT2 is a native linux filesystem, supports all of the above and has been time tested as stable.
That said it would be slick to get EXT3 (or 4!) support, or even reiserFS support.... journaling FTW
Well, you could just compile the kernel module, but your flash would probably survive a week with journaling... theres a reason you don't use it on flash.
Flash gets worn down by use, and journaling writes every second... So, journaling FTL.
tritron777 said:
Is there better way to get applications on sd card. Why are we using ext2 ? We can format sd card and partition it without using pc . We can format it into native supported file system of fat. why are need to make dev when in /dev/block device exist ? we need just to modifiee mounted.conf and /etc/fstab
Click to expand...
Click to collapse
the phone is linux .. EXT2 is linux .. FAT does not support proper file permissions and if you wanted to try setting something up feel free .. however .. you mention "native" supported file system and that is linux .. storage on the SD comes standard with FAT file system simply because the phone only uses it to store extra files like MP3 and JPG etc .. applications need a higher level of communication that FAT just cannot handle .. that's why Microsoft gave up on it for windows
Ok....I've used partition manager to delete my partition on my sd. I tried to make a new fat32 but it failed. So now when I go into usb mode I can't view my files. Understandable BUT I can still view and acess my files using astro. Is there anyway to delete my partion (format) and create a new fat32 partition through the terminal emulator or adb. PLEASE HELP GUYS my sdcard reader just messed up the other day so I'm screwed.
barger01 said:
Ok....I've used partition manager to delete my partition on my sd. I tried to make a new fat32 but it failed. So now when I go into usb mode I can't view my files. Understandable BUT I can still view and acess my files using astro. Is there anyway to delete my partion (format) and create a new fat32 partition through the terminal emulator or adb. PLEASE HELP GUYS my sdcard reader just messed up the other day so I'm screwed.
Click to expand...
Click to collapse
try the post of the script for partitioning yoru sd card from terminal.. or you need a sd card reader for using paragon partition manager, for best results.
Nitro212 said:
try the post of the script for partitioning yoru sd card from terminal.. or you need a sd card reader for using paragon partition manager, for best results.
Click to expand...
Click to collapse
I dont have a script. I need a command that i can run from either Terminal or adb. Im pretty sure there is a command out there that can repartion a sdcard through terminal or adb.
barger01 said:
I dont have a script. I need a command that i can run from either Terminal or adb. Im pretty sure there is a command out there that can repartion a sdcard through terminal or adb.
Click to expand...
Click to collapse
Try this. It is a program that worked great for me when Partition Magic did not. It is called Copy Commander. Burn to disc and boot. You can install from windows but it requires a key so it's limited. But it'll serve it's purpose. It works on XP and Vista.
in this case you might as well burn a ubuntu disk and partition under linux, which works 100% using the phone itself.
A point to note: most new sd cards are formated as a raw fat, i.e. without a partition table or boot sector. If this is the case, windows cannot create the partition table for you and you cannot create partitions using the build-in disk manager. Linux on the other hand is perfectly okay with this and will happily partition it for you.
Binary100100 said:
Try this. It is a program that worked great for me when Partition Magic did not. It is called Copy Commander. Burn to disc and boot. You can install from windows but it requires a key so it's limited. But it'll serve it's purpose. It works on XP and Vista.
Click to expand...
Click to collapse
I burned it and let it boot up but it never recongnized my sd. I mounted it through my phone and clicked refresh a hundred times but nothing=-(
barger01 said:
I burned it and let it boot up but it never recongnized my sd. I mounted it through my phone and clicked refresh a hundred times but nothing=-(
Click to expand...
Click to collapse
Make sure you have usb devices enabled in your bios.
So I was using Slax. Great LiveCD/USB linux, extremely customizable, modular, fast, and small, and has the capability of either:
- saving changes to its rootfs onto an AUFS mounted on a non-linux FS (FAT32, NTFS) using posixovl (POSIX Overlay FS) with metadata (permissions, etc.) being held in files
- saving changes to a fixed-size loop mount image.
This got me thinking.
If we could insert all the necessary modules, code, etc. for posixovl into the Android linux, and make a modified a2sd script that takes advantage of posixovl, we could effectively do away with the requirement for crazy partitioning.
It should be simple enough for ROM devs to implement, assuming it's ready and installed:
1. Create folder on main partition if it doesn't exist, something like /sdcard/system/[app, app-private, dalvik-cache, app_s]
2. In the init scripts, before the a2sd stuff, mount /sdcard/system with posixovl on /system/sd
3. Run a2sd as normal, it should automatically just work.
I'll hopefully test this once I get my phone to a stable development/testing stage, and I don't need to make phone calls for a while. Anyone else is welcome to try to implement this idea.
My current test environment:
- HTC Dream (T-mo G1) with the deadly SPL of doom
- Cyanogen Experimental, latest build
- Amon_RA's modded recovery
- Wipe /data, move all existing apps to backup, remove a2sd partition, Backup for Root Users to restore some settings and data
Anyone with ideas or improvements, please let me know.
To be tested:
- Feasibility (can it work?)
- Functionality (does it work?)
- Portability (Can it work on other ROMs and devices like Hero, Pulse, Blur etc.? If so, will likely be moved to XDA's new Android board)
- Stability (Will everything Force Close on boot? Does it run fast enough? Does anything get corrupted over time?)
Links:
- http://sourceforge.net/projects/posixovl - Sourceforge page for posixovl
In desktop linux you can create a file with the touch command, and mount the file to a mountpoint after formatting it to ext4 for example.
Maybe this is the easier way?
I have done this about 5 years ago, but I will try it today and report if it worked.
edit: ok done already:
1. create a file of the desired size, eg: dd if=/dev/zero of=filename bs=filesize count=1
2. use mke2fs to format the file
3. create a mountpoint and mount the file
thats all. Now I have a 128MB file on my PC, mountable and usable like a partition.
Archont said:
In desktop linux you can create a file with the touch command, and mount the file to a mountpoint after formatting it to ext4 for example.
Maybe this is the easier way?
I have done this about 5 years ago, but I will try it today and report if it worked.
Click to expand...
Click to collapse
As far as I know, you can do that on the mobile Android, too, and that does work in theory. This technique involves mounting a loop filesystem, and it too will allow one-partition apps2sd, but it's less flexible, and I would think slower, than the overlay method.
For a 512MB apps image:
Create empty 512MB file
# dd if=/dev/zero of=/sdcard/apps.img bs=1024k count=512
Format it to Ext2
# mke2fs -L Apps2SD /sdcard/apps.img
Unmount existing a2sd
# umount /system/sd
mount new a2sd image
# mount -t ext2 -o loop /sdcard/apps.img /system/sd
Make the usual directories, and a mountpoint for the old a2sd partition
# mkdir /system/sd/app; mkdir /system/sd/app-private; mkdir /system/sd/dalvik-cache; mkdir /system/sd/apps-tmp
Mount the old a2sd partition
# mount -t ext2 /dev/mmcblk0p2 /system/sd/apps-tmp/
Move all files from the old partition to the image file
# mv /system/sd/apps-tmp/* /system/sd/
Unmount and remove the mountpoint, we don't need it anymore
# umount /system/sd/apps-tmp
# rmdir /system/sd/apps-tmp
Finally, you add the following line to the init script where the a2sd auto mount happens, and comment out the old line.
Code:
[...]
mount -t ext2 -o loop /sdcard/apps.img /system/sd
#mount -t ext2 /dev/mmcblk0p2 /system/sd/
[...]
This should do what you described, in theory. I can't say whether it will work or not. I can't tell whether it will or won't screw up your phone, I can't be held responsible if you screw something up or overlook the details. Either of us might have made a typo somewhere; apply common sense before doing anything.
This sounds great! I think this would also be usefull for someone like me, who has a sd card that doesn't want to be partitioned anymore (cross-linked files??). Only thing possible is fat32 or ntfs.
Am I correct with my assumption?
This sounds a lot harder and more complicated then partioning. Your also talking about a lot of work needing to be done just so people can avoid doing a simple thing like partioning a sd card. I would say it would be very difficult alone to get the os to run a virtual mounting service especially since that will take up resources and slow down the phone. There is a reason they only use this technique on live cds is it works but its slow. most of the computers they are running on have 1gig of ram and 2ghz cpu's. i really dont think the g1 can push this.
I do not think that this is great, it definitely is slower than a ext4 partition on a good class 6 microSD card. And it is more vulnerable to data loss since 2 different filesystems including a 20 year old non-journaling fs at the base of this construct are involved.
Another problem that came to my mind: when you mount your SD card as external USB device to a PC, the file containing your apps will no longer be accessible, or Android will make using the phone as external data storage impossible.
Interesting.
There is, however, a major problem: What happens when you unmount the fat partition on the phone in order to connect with a computer using UMS? Answer: everything on the phone will crash and burn since the apps filesystem will suddenly disappear = BAD.
posixovl is a nice find though...
Note that aufs, loopmount linux filesystems, etc., wouldn't be needed with this since posixovl appears to be vfat with posix extensions, so you should be able to just use posixovl directly on the sdcard.
There are several problems with that though... i.e. how reliable is posixovl regarding users tampering with it?
In any case, a prerequisite for use of it would be certain other changes being planned...
You might want to contribute to this thread:
http://forum.xda-developers.com/showthread.php?t=577941
(note: the thread links to a thread at android-platform, the one here has, as expected, gone off on a tangent... just ignore the junk.)
TylTru said:
So I was using Slax. Great LiveCD/USB linux, extremely customizable, modular, fast, and small, and has the capability of either:
- saving changes to its rootfs onto an AUFS mounted on a non-linux FS (FAT32, NTFS) using posixovl (POSIX Overlay FS) with metadata (permissions, etc.) being held in files
- saving changes to a fixed-size loop mount image.
This got me thinking.
If we could insert all the necessary modules, code, etc. for posixovl into the Android linux, and make a modified a2sd script that takes advantage of posixovl, we could effectively do away with the requirement for crazy partitioning.
It should be simple enough for ROM devs to implement, assuming it's ready and installed:
1. Create folder on main partition if it doesn't exist, something like /sdcard/system/[app, app-private, dalvik-cache, app_s]
2. In the init scripts, before the a2sd stuff, mount /sdcard/system with posixovl on /system/sd
3. Run a2sd as normal, it should automatically just work.
I'll hopefully test this once I get my phone to a stable development/testing stage, and I don't need to make phone calls for a while. Anyone else is welcome to try to implement this idea.
My current test environment:
- HTC Dream (T-mo G1) with the deadly SPL of doom
- Cyanogen Experimental, latest build
- Amon_RA's modded recovery
- Wipe /data, move all existing apps to backup, remove a2sd partition, Backup for Root Users to restore some settings and data
Anyone with ideas or improvements, please let me know.
To be tested:
- Feasibility (can it work?)
- Functionality (does it work?)
- Portability (Can it work on other ROMs and devices like Hero, Pulse, Blur etc.? If so, will likely be moved to XDA's new Android board)
- Stability (Will everything Force Close on boot? Does it run fast enough? Does anything get corrupted over time?)
Links:
- http://sourceforge.net/projects/posixovl - Sourceforge page for posixovl
Click to expand...
Click to collapse
lbcoder said:
Interesting.
There is, however, a major problem: What happens when you unmount the fat partition on the phone in order to connect with a computer using UMS? Answer: everything on the phone will crash and burn since the apps filesystem will suddenly disappear = BAD.
Click to expand...
Click to collapse
I kinda overlooked that point. Oops.
Though this same problem does exist on regular apps2sd when you remove the card without dismounting it, killing all apps and their processes, and freezing Dalvik's method of autostarting some apps.
I do tend to swap cards every now and then, but only after a reboot. Dalvik re-enumerates and caches dex, which makes for a slow boot, but it seems to just work in most cases that the apk install doesn't drop the app's functional payload (helper Linux/shell utils, libraries, NDK .so's) in /data/data (like some emulators, the Android Scripting Environment)
lbcoder said:
There are several problems with that though... i.e. how reliable is posixovl regarding users tampering with it?
Click to expand...
Click to collapse
As far as I know, the metadata files are marked as hidden and system files, and begin with a '.'. And I haven't tried this, but I think modifying the actual files under Windows has no negative effects, but moving, deleting, or copying files would likely be a no-no.
Also, I don't think there's a 'fsck' for posixovl, meaning that if any metadata files were screwed with the wrong way, the entire overlay FS would be trashed.
lbcoder said:
In any case, a prerequisite for use of it would be certain other changes being planned...
You might want to contribute to this thread:
http://forum.xda-developers.com/showthread.php?t=577941
(note: the thread links to a thread at android-platform, the one here has, as expected, gone off on a tangent... just ignore the junk.)
Click to expand...
Click to collapse
I checked that out. It was actually a small inspiration for what I was thinking of.
In any case, Android's package management system needs an overhaul. The package storage needs to be de-Linuxified, as all it is is a bunch of .apk files and .dex/.odex files, the UIDs of apps are in the AndroidManifest.xml, right?
In a somewhat unrelated note, app data needs to be moved to a specified folder structure on the sdcard. My card is full of folders in the root directory with random names.
If I'm understanding you correctly, you're talking about storing an image file on the normal SD card partition(which has to be FAT32 as far as I've seen) and then mounting it, correct? This idea has been talked about at length before on at least 3 separate occasions(2 of which were on this very forum) and found to be a bad idea due primarily to massive security risks since FAT32 has no permissions.
Also, I believe cyanogen ended up dumping unionfs/aufs due to rampant memory issues.
If you are talking about mounting an image from the FAT32 partition, please don't endorse this. We don't want to be throwing in security bugs into android, especially ones such as this which can't be plugged up.
As a modification to what I said: If you're suggesting doing this(or something similar) on a separate filesystem, after that project to change the AOSP to support one with permissions is finished, then I'm in full support.
If you want to go for a single partition on the sd card, why don't you just make the entire card use ext4? Your linux desktop reads it anyway, it uses journaling and so on, I guess it would be faster compared to fat32 and it is definitely safer to use.
And i guess it is not too complicated to mount this partition and use it for pictures, music and so on.
I have not tried this (yet) and I go to bed in 20 minutes, but maybe I will start testing something in that direction tomorrow.
[email protected] said:
If I'm understanding you correctly, you're talking about storing an image file on the normal SD card partition(which has to be FAT32 as far as I've seen) and then mounting it, correct? This idea has been talked about at length before on at least 3 separate occasions(2 of which were on this very forum) and found to be a bad idea due primarily to massive security risks since FAT32 has no permissions.
Also, I believe cyanogen ended up dumping unionfs/aufs due to rampant memory issues.
If you are talking about mounting an image from the FAT32 partition, please don't endorse this. We don't want to be throwing in security bugs into android, especially ones such as this which can't be plugged up.
As a modification to what I said: If you're suggesting doing this(or something similar) on a separate filesystem, after that project to change the AOSP to support one with permissions is finished, then I'm in full support.
Click to expand...
Click to collapse
UNIX permissions don't do anything in the way of "security" unless you have no access to the actual storage device from another computer (as is the case with the unrooted Dream's internal memory), or unless encryption is used. The posixovl driver OVERLAYS Unix permissions over Fat32 filesystems. But even still, with Unix permissions, nothing's stopping someone else from mounting the Ext2 partition and using chown and chmod.
And the image file on the SD card's Fat32 partition is a complete Ext2 partition complete with Permissions. Nothing is lost.
Archont said:
If you want to go for a single partition on the sd card, why don't you just make the entire card use ext4? Your linux desktop reads it anyway, it uses journaling and so on, I guess it would be faster compared to fat32 and it is definitely safer to use.
And i guess it is not too complicated to mount this partition and use it for pictures, music and so on.
I have not tried this (yet) and I go to bed in 20 minutes, but maybe I will start testing something in that direction tomorrow.
Click to expand...
Click to collapse
We'd just have to find the part in the Android that mounts /sdcard/, and change 'vfat' to 'ext2'. The only reason I wouldn't do this, is because it would immediately make it incompatible with Windows and Mac's default FS drivers. As far as I know, the only FS's that are supported universally within Linux, Mac, and Windows, are FAT and NTFS. And NTFS can be made to have crude support for permissions through security descriptors. Although, the Dream SPL, the Recovery images, and most of Android only uses FAT32.
This is discussed in android-platform Group :
http://groups.google.com/group/andr...read/thread/bf0709c157451cd9/f6aee1830c84620f
The goal is to be able to integrate this in android.
And not having to partition the SDCard is one of the requirements so far...
Unix permissions are not stored using fat or vfat, and ntfs is not really supported in desktop linux and i guess it cannot be used in android linux.
I would not use windows anyway so this is no problem to me, and there are drivers around to mount ext systems in windows. As Mac OS is based on unix there will be a solution for this too.
Access usind adb push and pull, via ftp and so on is not touched by using ext4 on the entire sd card I guess.
And if you don't go the easy way using gparted on a live cd or usb device to create 2 partitions, you will have to live with some disadvantages anyway.
Finally I want to say that my ideas are far from being perfect or usable at all, I see this thread as a kind of brainstorming.
im not as linux or android savvy as probably any of you but before the current method of creating a swap partition became the "standard", people used a swap file on the sdcard and linked that. seems similar to what you are suggesting here.
ofcourse when mounting the fat partition elsewhere (ums in windows for example) that swap file could no longer be used within android. i dont see a way to get passed the same issue, but worse here, due to android not having crucial apps when the fat partition is mounted.
then again, i am pretty much over my head in this conversation and could be over looking something...
I'm kind of fascinated by the FUSE + posixovl method of doing this. In the long run I have a feeling that it's going to perform like ****, but I think it's worth testing.
I managed to get both libfuse and mount.posixovl built and running on Android.
posix-overlay(/sdcard/fuse) on /sdcard/fuse type fuse.posixovl (rw,nosuid,user_id=0,group_id=0,default_permissions)
Giving this a little testing now, it definitely works.
Code:
/sdcard/fuse # ls -l
drwxr-xr-x 2 1000 1000 4096 Nov 5 17:17 test
TylTru said:
UNIX permissions don't do anything in the way of "security" unless you have no access to the actual storage device from another computer (as is the case with the unrooted Dream's internal memory), or unless encryption is used. The posixovl driver OVERLAYS Unix permissions over Fat32 filesystems. But even still, with Unix permissions, nothing's stopping someone else from mounting the Ext2 partition and using chown and chmod.
And the image file on the SD card's Fat32 partition is a complete Ext2 partition complete with Permissions. Nothing is lost.
We'd just have to find the part in the Android that mounts /sdcard/, and change 'vfat' to 'ext2'. The only reason I wouldn't do this, is because it would immediately make it incompatible with Windows and Mac's default FS drivers. As far as I know, the only FS's that are supported universally within Linux, Mac, and Windows, are FAT and NTFS. And NTFS can be made to have crude support for permissions through security descriptors. Although, the Dream SPL, the Recovery images, and most of Android only uses FAT32.
Click to expand...
Click to collapse
Ya, I meant more from the standpoint of a rogue app. Since FAT32 has no permissions, what would prevent such an app from modifying the stored image file to, say, change a trusted app with superuser permissions to some new code of its own making to, for example, watch for credit card numbers and send them back to the person who made the original rogue app? I'm always hesitant with any ideas that suggest storing an image file on the sdcard for appstosd for this reason.
Forget it, it's useless.
An overlay filesystem prevents you from enabling USB storage.
If you want to play around with FUSE on Android, here's a repository for my port of libfuse..
http://github.com/cyanogen/android_external_fuse
Hi,
I have an idea. I used symbian S60 of Nokia, Symbian can install app to sdcard. I see that when I mount sdcard to PC, my phone immediately hold all activations of all applications on my phone. And they have a PC sync software that help us access sdcard but not mount sdcard (like that we copy file from computer to sdcard via debug mode on android).
I think we should find out how symbian can do it and we will use their way .
I'm not a developer, I'm just an user.
I talked to a few people about this, and some deep kernel voodoo is going to be needed for this to really happen without partitioning.
Another idea is to forge ahead with this, and ditch the "unmount fs for usb storage" and use RNDIS + Samba or something like that instead to access files on SD. I kind of like this idea.
So i am on CROMI 3.4.4. and i installed data2sd. I was wondering are you suppose to see you internal storage when you plug the tf700 into you computer? It is weird because i see my fat32 and my ext4.... or is that normal?
hobosuit said:
So i am on CROMI 3.4.4. and i installed data2sd. I was wondering are you suppose to see you internal storage when you plug the tf700 into you computer? It is weird because i see my fat32 and my ext4.... or is that normal?
Click to expand...
Click to collapse
You need to flash a kernel (included in the data2sd 3.4.x mod for CROMI) and you should see an sdcardi mount point that is you old internal storage.
sbdags said:
You need to flash a kernel (included in the data2sd 3.4.x mod for CROMI) and you should see an sdcardi mount point that is you old internal storage.
Click to expand...
Click to collapse
Thanks.
So the sdcardi mount point is only view though root explorer? or can i see it on the computer too?
hobosuit said:
Thanks.
So the sdcardi mount point is only view though root explorer? or can i see it on the computer too?
Click to expand...
Click to collapse
I have CROMI and I can only see the internal card through the root explorer. Not a big deal to me. I can move things around as needed.
http://forum.xda-developers.com/showpost.php?p=33431910&postcount=1 NOTE: I've officially thrown in the towel on the sdcardi USB support on CleanROM. I don't know if it's changes by ASUS or by Scott, but it just does not work. I was able to figure CM out because I could look at the source code on Github and trace the exact changes needed. We don't have source for the stock ROM and I haven't been able to fix it without.
Yes currently PCs can't see the sdcardi mount point.
Blame Asus - but realistically your tab was not built to work this way so it is not entirely unexpected and one of things you will have to give up when going to data2sd
sbdags said:
Yes currently PCs can't see the sdcardi mount point.
Blame Asus - but realistically your tab was not built to work this way so it is not entirely unexpected and one of things you will have to give up when going to data2sd
Click to expand...
Click to collapse
oOo thanks guys
i thought i was going crazy.
sbdags said:
Yes currently PCs can't see the sdcardi mount point.
Blame Asus - but realistically your tab was not built to work this way so it is not entirely unexpected and one of things you will have to give up when going to data2sd
Click to expand...
Click to collapse
I know this is an old thread, but I was wondering how Titanium Backup was able to create a link to the internal storage (it's called data2 for me) when I connect the TF700 to the computer. There's a data2 folder that leads to a TitaniumBackup folder I created on the sd card, but when I use root browser to look at the same directory, the data2 folder is not there. Is there a way to emulate this so I can access the internal storage from my PC? Sorry if the answer was posted already, but I just can't find the solution for the life of me.
omegaslime said:
I know this is an old thread, but I was wondering how Titanium Backup was able to create a link to the internal storage (it's called data2 for me) when I connect the TF700 to the computer. There's a data2 folder that leads to a TitaniumBackup folder I created on the sd card, but when I use root browser to look at the same directory, the data2 folder is not there. Is there a way to emulate this so I can access the internal storage from my PC? Sorry if the answer was posted already, but I just can't find the solution for the life of me.
Click to expand...
Click to collapse
I believe you're talking about 2 different folder here. Once you use your sdcard as data2sd, you have 2 partitions, 1st partition is fat32 and 2nd partition which is ext4. When you connect the tablet to your PC, your PC only see the fat32 partition, it can't see the second partition which is ext4. Your Titanium backup probably use the fat32 partition. The only way you could see the INTERNAL storage is using ES file explorer or Root explorer file browser. Currently there is no way to access the internal storage from your PC.
buhohitr said:
I believe you're talking about 2 different folder here. Once you use your sdcard as data2sd, you have 2 partitions, 1st partition is fat32 and 2nd partition which is ext4. When you connect the tablet to your PC, your PC only see the fat32 partition, it can't see the second partition which is ext4. Your Titanium backup probably use the fat32 partition. The only way you could see the INTERNAL storage is using ES file explorer or Root explorer file browser. Currently there is no way to access the internal storage from your PC.
Click to expand...
Click to collapse
No, I am quite certain that my Titanium backup folder is NOT on the fat32 partition. When I look at my data2 folder with a file browser, it leads to the ext4 partition, which contains my backup folder.
omegaslime said:
No, I am quite certain that my Titanium backup folder is NOT on the fat32 partition. When I look at my data2 folder with a file browser, it leads to the ext4 partition, which contains my backup folder.
Click to expand...
Click to collapse
I'm kind of confuse, but here are the principles for data2sd:
1) you can't use your PC to see the internal storage
2) Root browser or something similar can see the internal storage, ext4 and fat32.
Hope I hit the right spot!
buhohitr said:
I'm kind of confuse, but here are the principles for data2sd:
1) you can't use your PC to see the internal storage
2) Root browser or something similar can see the internal storage, ext4 and fat32.
Hope I hit the right spot!
Click to expand...
Click to collapse
Thanks for replying quickly. Just to clarify, I'm not seeing the internal storage as a separate partition. I'm seeing it as a folder in the ext4 partition that links to the internal storage when I connect it to the computer. I did a little more testing and found that I can see folders from the internal storage when I use titanium backup to create the folder. Unfortunately, I can only see files that titanium backup created and not files that I move into the folder. I hope this clears things up.
omegaslime said:
Thanks for replying quickly. Just to clarify, I'm not seeing the internal storage as a separate partition. I'm seeing it as a folder in the ext4 partition that links to the internal storage when I connect it to the computer. I did a little more testing and found that I can see folders from the internal storage when I use titanium backup to create the folder. Unfortunately, I can only see files that titanium backup created and not files that I move into the folder. I hope this clears things up.
Click to expand...
Click to collapse
Titanium backup should already have its backup folder in internal storage and once you switched to data2sd, you should also have another Titanium backup on the ext4 folder. It's not a good idea to have Titanium backup to use either internal or ext4 partition. It should only use the fat32 partition (on your external SDcard), if something happened to the OS, will not impact your backup and you can access this fat32 partition while on data2sd or return back to your regular setup.
buhohitr said:
Titanium backup should already have its backup folder in internal storage and once you switched to data2sd, you should also have another Titanium backup on the ext4 folder. It's not a good idea to have Titanium backup to use either internal or ext4 partition. It should only use the fat32 partition (on your external SDcard), if something happened to the OS, will not impact your backup and you can access this fat32 partition while on data2sd or return back to your regular setup.
Click to expand...
Click to collapse
When i tried to get it to backup to my ext SD it didn't like it
KinetiClutch said:
When i tried to get it to backup to my ext SD it didn't like it
Click to expand...
Click to collapse
why not? what wrong?, it's a big risk if you backup to internal or ext4 external. These can be wipe when you format data or full wipe (sometime you have no choice in order to recover a bootloop), so you MUST backup to the fat32 partition. If it's not working for you then you may need to reformat your card or something. Titanium backup should work fine.
buhohitr said:
Titanium backup should already have its backup folder in internal storage and once you switched to data2sd, you should also have another Titanium backup on the ext4 folder. It's not a good idea to have Titanium backup to use either internal or ext4 partition. It should only use the fat32 partition (on your external SDcard), if something happened to the OS, will not impact your backup and you can access this fat32 partition while on data2sd or return back to your regular setup.
Click to expand...
Click to collapse
I appreciate the advice, but to get back on topic.... The internal storage initially did not have a backup folder. I made one via Titanium Backup and changed the default backup folder (which was on my ext4) to the new one (which is in the internal storage). This somehow made a link to the internal storage when I connect the device to the PC. I can see the backups I made from the computer. Unfortunately, any other file I try to copy over to the backup folder via root browser can't be accessed and is not seen on the computer. I hope this clears things up a bit.
omegaslime said:
I appreciate the advice, but to get back on topic.... The internal storage initially did not have a backup folder. I made one via Titanium Backup and changed the default backup folder (which was on my ext4) to the new one (which is in the internal storage). This somehow made a link to the internal storage when I connect the device to the PC. I can see the backups I made from the computer. Unfortunately, any other file I try to copy over to the backup folder via root browser can't be accessed and is not seen on the computer. I hope this clears things up a bit.
Click to expand...
Click to collapse
OK, know I know what you're asking. Can you actually copy the backup file from your device to your PC?
buhohitr said:
OK, know I know what you're asking. Can you actually copy the backup file from your device to your PC?
Click to expand...
Click to collapse
Actually yes, if I set the permissions right.