you won't even feel the difference.
Basic functions and all that. Also remember we are also still using internal storage as well.
I believe only the system.img is saved on the extSD
Basic functions and all that. Also remember we are also still using internal storage as well.
I believe only the system.img is saved on the extSD
I thought about it some more. You're probably keeping the partition mapping somewhere that get's read by the 2nd init process.
Maybe, but I already have a 64GB EVO in my phone now and it seems slow as molasses, especially when writing to it. So I wanted to try a faster one.
slow?
Im very accustomed to SanDisk cards, this is actually my first Samsung card.
slow in which manner?Maybe, but I already have a 64GB EVO in my phone now and it seems slow as molasses, especially when writing to it. So I wanted to try a faster one.
Im very accustomed to SanDisk cards, this is actually my first Samsung card.
The fast sequential read/write speeds will be good for large file transfers. For the system ROM fast random read speeds will have the largest impact. In any case if you go with either card hsbadr has you get the best of both worlds :good:Maybe, but I already have a 64GB EVO in my phone now and it seems slow as molasses, especially when writing to it. So I wanted to try a faster one.
Running unencrypted backups in safestrap took 45 minutes, backing up Nova launcher settings took 20 seconds (10KB file) - stuff like that
---------- Post added at 05:11 PM ---------- Previous post was at 05:10 PM ----------
That was my thinking.
This has been answered in MultiSytem Q&A thread. Yes, the APK manages all functions including ROM activation & reboot to current system, another stock/virtual system, download mode, recovery, ... etc.
Yup, that's a good deal, but Note 3 doesn't support this high speed. However, it'll be useful anyway when you upgrade to a newer device.
Will the 80 MB's sdcard work in the Note 3 but at a lower speed, or will the Note 3 not even see the sdcard?
It'll work at maximum speed supported by Note 3. So, it's good to go anyway.Will the 80 MB's sdcard work in the Note 3 but at a lower speed, or will the Note 3 not even see the sdcard?
Couple questions.
1) if virtual systems are read only, how do we modify them? Do we have to boot to another multisystem rom to modify a virtual rom?
2) how is a corrupt virtual rom handled? Does it see its bad and default to stock system?
3) does android do any maintenance whatsoever on stored data within /data or external sd? So if I have an app installed on 1 system and not on another system will android see it and clear the data?
Sent from Cerj's Kickass Themed Tapatalk App on my Eye Candy Duece_Biggin's Rom.
1) if virtual systems are read only, how do we modify them? Do we have to boot to another multisystem rom to modify a virtual rom?
2) how is a corrupt virtual rom handled? Does it see its bad and default to stock system?
3) does android do any maintenance whatsoever on stored data within /data or external sd? So if I have an app installed on 1 system and not on another system will android see it and clear the data?
Sent from Cerj's Kickass Themed Tapatalk App on my Eye Candy Duece_Biggin's Rom.
1) The stock system partitions is mounted by default read only & so are the virtual systems. To modify a stock/virtual system, the MultiSystem APK remounts them read/write. You can modify the currently running virtual system, copy it & modify the copy, modify another stock/virtual system.
2) At early boot, MultiSystem checks for the microSD & active virtual ROM to boot it. To fail safe, you can remove the microSD card to boot to stock system. There's a boot menu that gives you options to select a stock/virtual system, but it crashes on LP. I'm debugging it, but all functions won't be affected if I removed it. To fail safe, you can remove the microSD card to boot to stock system & restore/repair your virtual ROMs.
3) No, all storage partitions are shared between ROMs. If you installed an app, it'll be availabe for all of them. Since on locked devcies we're limited to stock manufacturer-based ROMs, this makes the switch between ROMs very convinient (you don't have to worry about your changes/data/setup & storage space on the another ROM; all ROMs share everything except system). However, you should make regular backups in case a virtual ROM (probably with unsafe mods) results in bootloop due to your user data. In this case, it's safe to wipe data & selectively restore apps/data from backup(s). Another advantage of sharing all storage partition is that your messages/emails/etc received on a virtual ROM are immediated synced (actually shared) to the other ROMs.
Added to OP.
Thanks hsbadr. To clarify question 3, I was talking if we installed an app on the system partition the unshared partition. So one system has an app and it saved some info to /data/data then I swap to say stock system partition and it doesn't have the app in system or /data/app will android notice that the app isn't available and wipe the data for it in /data/data?
Thanks!
Sent from Cerj's Kickass Themed Tapatalk App on my Eye Candy Duece_Biggin's Rom.
No, it'll be there but unused by the new system. That's what CorpseFinder in SD Maid app does; it cleans the data for uninstalled/removed apps.
Multisystem only seems like an academic exercise. It's nice that you made it, but it sounds so complicated that I don't see most adopting it.
What if I want a rooted lollipop experience and I don't want my SD card involved? Multisystem can't be the only way. One of the biggest reasons I use my SD card is to keep files/data and rom backups completely separate from the system. This combines them and lowers my total storage even further.
What if I want a rooted lollipop experience and I don't want my SD card involved? Multisystem can't be the only way. One of the biggest reasons I use my SD card is to keep files/data and rom backups completely separate from the system. This combines them and lowers my total storage even further.
Multisystem is different but it doesn't sound to complicated to me. Hsbadr has explained it very well and if everyone would actually read and follow directions it should go smoothly. This is the best and only option for now anyway. You can always choose to stay on KK. Thanks @hsbadr for all the hard work and long hours you ha e put in this.
Use a bigger card. I think your name absoluteparanoia says it all. Be glad we have someone dedicated to this to begin with.
To an extent I can agree with you. However, 4gb out of a 64gb card is not much. For me it is a slight issue, but not a deal breaker.
The thing you need to ask yourself is... What other options are there? It seems that we will not be getting any more updates to Safestrap for a while.
If you have not been keeping up with the news in Android:
- HashCode, the creator of SS has moved on to a new career in Project Ara.
- Google has been restricting access to more and more system files, making root nearly impossible to obtain. We are almost at a year since the last known (proven) root method was available.
- Samsung has made increasingly stronger moves to lock down their devices. Blacklisting all previous versions of bootloaders to keep people from being able to Odin/flash back to older system images.
- As result of Samsung locking down the bootloaders further, newer baseband versions have killed off the usability of Safestrap.
As android moves on, new loop holes to obtain root and installation of custom recoveries (like SS) close with every new release. I truly think that the best days of android are now over. We had our fun, and that fun was openness. Google continues to close off openings and make android more secure, for the sake of "Security". And that is not going to get any better. Android continues to grow, adopted by more manufactures as the OS of choice in their products.
After asking many questions from Hsbader about the MultiSystem design and allowances, I feel that this is about the closest we will get to Safestrap and custom recovery for a long time into the future.
You can thank Verizon and AT&T for that one. They are the ones requiring locked bootloaders on all Samsung devices (and others) they sell.
Big red does not want you to be able to uninstall that BLOATware. It makes them money to install that crap like Blockbuster and all the other junk apps. Then come the Verizon apps that spy on your usage details and patterns. They may not get specific details about what you just searched in Google for, but it makes you wonder.
For what Hsbadr has accomplished with this MultiSystem, I am truly amazed. I do not know if he is solely working on this by himself, but I must give props.
AND, he has been on top of answering most questions here in the threads on XDA. Also... he put up with me asking too? many questions? LoL
I was honestly curious myself about some specific details, but also wanted others to know what to expect. Once you upgrade past baseband NC4 on the Note3, there is no going back.
There may not be any more options for our VZW Note 3's in the future. This may be "IT".
And for future Samsung devices. It only gets harder to modify with every new device and software revision. That is why I hate the way Samsung is moving with the Galaxy S6. No more sdcard slot. That seriously limits future options. And being that Samsung and the Galaxy line are the largest name brand competitor to the likes of Apple, this may continue trends for other manufactures to follow.
If Samsung and the biggest selling smartphone can omit extSD cards while maintaining high sales numbers, why wouldn't HTC, Motorola, and LG to save a buck or two? I really hate the direction the Android world is moving.
I am very sorry for such a long post. Maybe if others read this they will feel more at ease with moving on to LP and using MultiSystem.
I honestly feel this is the best we will have for now on our Verizon devices.
Thank you Hsbadr for your work
Last edited:
I too am happy to have life after death with multisystem, but I'm convinced my next phone will be a Note 5 developer edition next September.
Sent from my SM-N900V using Tapatalk
Sent from my SM-N900V using Tapatalk
Umm, you can already have a rooted LP experience as hsbadr has provided us Jasmine 5.0. Since there is no root method for anything after NC4 (4.4.2) and you cannot restore your device to a rootable state if you're on firmware greater than NC4. Therefore right now MultiSystem will be the only way. In fact we are fortunate that hsbadr is spending any time providing us the ability to be rooted on LP and giving us any utilities at all.