I'll start with a question, too. I put BAMF3.0 rc 4.9 in an SD slot. When I boot in, everything works except Titanium Backup can't find root. Anyone else have this problem?
Each rom gets a slot. Each slot has its own data, system, cache, etc. Basically, it installs a new rom in its own private environment, then changes the boot image to boot to that particular rom. Since every rom has its own data, theres no crossover and apps need to be installed per rom. Kernels as well.sidsixseven said:Not to be a naysayer, but how does this work?
Does it swap ROM images by backing up then restoring or is it true dual boot?
I ask because it seems to me like you have to put a lot of faith in it doing whatever it does correctly or risk a soft brick that you can only fix by flashing an RUU.
And the followup question, how does it handle app data across multiple roms? Seems like some stuff in some apps might not play nice with a quad boot approach and has a higher potential for apps getting messed up.
Again, not trying to be a pessimist, these are just the questions I want answered before using it.
Sent courtesy of SID6.7 and Tapatalk
This assumes all apps store all data in /data. Some apps store stuff in /sdcard and it sounds like all roms use the same /sdcard. This would lead me to believe that there is some bleedover, right?WishRyder said:Since every rom has its own data, theres no crossover and apps need to be installed per rom. Kernels as well.
Good point. I hadn't thought about that actually. I've yet to run into any issues but I'll be sure to keep a closer eye on things.sidsixseven said:This assumes all apps store all data in /data. Some apps store stuff in /sdcard and it sounds like all roms use the same /sdcard. This would lead me to believe that there is some bleedover, right?
But perhaps no different than restoring backups...?
Sent courtesy of SID6.7 and Tapatalk
Boot Manager simply allows additional roms to be installed to the sdcard and then booted from the sdcard. Nothing runs "on top of" anything (its not a virtual machine), as everything gets its own "partition" on the sdcard that the app simply allows you to boot into (rather than into the typical phone rom). The phone rom itself remains untouched and is still available to boot to as normal at any time.dadsterflip said:Please explain this. I've read the manual and all. So once I installed the rom from the sdcard. Does that become the phonerom or is it just running on the sdcard and on top of the phonerom.
Sent from my ADR6400L using Tapatalk
So your saying that whatever you boot on your sdcard becomes the new phone rom correct.? Thx alotWishRyder said:Boot Manager simply allows additional roms to be installed to the sdcard and then booted from the sdcard. Nothing runs "on top of" anything (its not a virtual machine), as everything gets its own "partition" on the sdcard that the app simply allows you to boot into (rather than into the typical phone rom). The phone rom itself remains untouched and is still available to boot to as normal at any time.
Sent from my ThunderBolt using Tapatalk
No. Your phone rom remains installed to your internal rom. The app doesn't change that. The app simply installs roms to your sdcard (as if it were your internal phone rom).dadsterflip said:So your saying that whatever you boot on your sdcard becomes the new phone rom correct.? Thx alot
Sent from my ADR6400L using Tapatalk
No that explains it perfect. That was my main concern was running it on the sdcard. I'm not sure long term effects.WishRyder said:No. Your phone rom remains installed to your internal rom. The app doesn't change that. The app simply installs roms to your sdcard (as if it were your internal phone rom).
The sdcard roms remain on your sdcard. The app essentially allows you to ignore your internal rom during boot, and boot into your sdcard to run the rom from there (again, as if it were your internal phone rom).
Since the additional roms actually run directly from the sdcard itself, this is why there can be lag related issues. At any time, from any rom, you can enter the boot manager app and choose to boot to any of your installed roms (including back into your phone rom).
I wish I could explain it better than that. :-(
EDIT: You could use an sdcard rom as your daily driver, as long as you don't mind running your rom directly off the sdcard (typically runs a little slower).
Sent from my ThunderBolt using Tapatalk
It's similar to dual booting a computer with different Operating Systems on different disk drive partitions. The boot.img file gets changed so that instead of it booting up off the internal phone storage, it boots up from the sdcard instead. Basically, it's like a computer booting up from the D:\ drive instead of the C:\ drive.WishRyder said:I wish I could explain it better than that. :-(
I have been using ext2 for all mine with no problems. I've installed CM7, liquid, Bamf3.0, and the "stock" mr2 build (for fun...I was bored...I'll probably never boot into it again).Rebelxing123 said:This app doesn't seem to work for me. Everytime I try to install a rom, I use Ext 2 and in the middle of making the .img it will show some sort of error that asks "does this rom support ext 2?"
I've tried installing the latest CM7, Synergy Rom, and Das Bamf, but no luck. I'm currently running Liquid Thunderbread 2.5.
$3 isn't a bad price...less than I spend on sodas in a day.D3fault121 said:But for the $3 it costs is it really worth the money over just using different back ups of other roms? I know it takes time/battery to run backups but that isn't really an issue for me.
There seems to be some separation with the sdcard data, too. I am not sure. I downloaded a file in one rom, and when I switched it wasn't in the "downloads" folder like I expected. I haven't rebooted into the other rom to try to find where the file went yet. I've been wondering about this, too.sidsixseven said:And the followup question, how does it handle app data across multiple roms? Seems like some stuff in some apps might not play nice with a quad boot approach and has a higher potential for apps getting messed up.