Here are my questions for hash: (im on a bionic)
For the sake of this post:
*External sd is just that, the card you insert
*Internal sd is 8 gb partitioned of 16 gb total space (on bionic)
*Emmc is the 8 Gb partitioned for.operating system and data (apps).
1. Where is the stock rom and data stored? Emmc?
2. I understand that the slots are on internal sd, so, to use all that space (hypothetically 8gb), one would need to format that partition. When i formatted in 3.04 recovery, it didn't appear to work. But, assuming it is formatted, I create slots. Slot 1 I did as three gb, installed ROM...when i view that Folder in OS, all i see are the three files that get created in recovery when i create slot. Is this where the actual ROM and data are being stored? I guess I'm thinking if i had a better understanding of where things are being stored, it would make more sense how to size the slots.
3. Can a "stock" ROM / zip be installed on a slot? I.e an ICS leak for bionic.
4. Lastly, before i installed v3, i toggled to UNsafe to boot and uninstall v2 and install v3. There were two odd things. One, the safe strap v2 app wasnt there. I had to reinstall, uninstall 2.11 recovery and then uninstall 2.11 and install 3.04. Also, all the apps that i had installed on safe side in my custom ROM showed up in my UN safe stock ROM. Is this normal behavior if i don't wipe after toggling?
5. What is the ss folder on emmc? (seen at root using a root explorer)
That should do it. As I've said before, this is an astounding application.
Sent from my DROID BIONIC using Tapatalk 2
Whew.
Ok I'll tackle these 1 by 1:
1. There is only 1 emmc chip in the device (it's 16gb) and there are about 25 partitions on it. Of those there's a stock /system, /data and /cache partition (#20, #24 and #21 I believe). There is also the 8gb emstorage partition (#25) shown as /sdcard and formatted vfat to be treated like an SD card as well.
2. I don't think a "format" of the sdcard area will work correctly while in Safestrap (and I should probably build a "smart" replacement for this function). The reason is that the recovery has already mounted that partition and is using it for storage of private Safestrap files (active_slot, translate, and potentially more).
2a. a 3gb data partition is probably overkill for all but the most intensive phone users with literally 100's of apps. My recommendation is to stick with 1GB data unless you are a heavier phone user and then go with a 2GB data partition. If you're a nutty gotta have all of those apps kind of person, then 3GB is the way to go. The reason is that the larger you make any individual rom-slot, the less space there is for others.
2b. Each data slot includes a 600mb system and 300mb cache on top of the size of data partition you select. So for the 1GB data it's very close to 2GB TOTAL space used for that rom-slot. And going with that math, if you create 4 of those you will use almost all of the internal space (which was how it was intended, and why we have 4 slots available).
2c. If you create a 3GB data partition that means you're using close to 4GB for the 1st slot. This means you will only be able to create 2x 1GB data partitions if you had the maximum free space on the emstorage (/sdcard) partition.
2d. The virtual rom-slot files (system.img, userdata.img and cache.img) are all stored in "rom-slot#" directories in the emstorage partition under the "safestrap" folder. These are large partitions formatted as ext3 but kept in 1 file which are mounted at boot time if that rom slot is active. To the OS they are identical as the stock partitions once they've been setup.
3. A stock ROM can be installed in a rom-slot, but only in the form of a "MotoBlur" ROM which has been setup by myself or another ROM dev. The reason is that there are key changes in the init files which let the ROM be setup on the virtual rom-slots. Eventually I might have a feature which copies the stock ROM into a rom-slot and adds the necessary changes. But that's all up in the air.
4. One of the down sides of the v2 Safestrap is that it shared the /data partition across the safe ROM and the stock ROM. So during the "swap" from one to the other, it would take everything on the /data partition and back it up into a file on the sdcard, and then extract the old stock ROM's data information back onto the /data partition. If there was any problems in that transition then you could end up with a mixed set of data (and it happened occasionally for one reason or another). This doesn't happen on v3 because every ROM has it's own set of files.
5. "ss" is the mount used by Safestrap to run the virtual ROM-slots. It's identical to the "/sdcard" mount. The reason I have a seperate mount for Safestrap is that the OS can unmount the "sdcard" at times for various OS features (UMS, etc) and we really can't do that if you're using files on there.
Hopefully, that clears things up.