I would say no, you dont need to. Unless the linked apps disappear or are gone after reboot, then you should flag it.
Maybe the 1st partition is what you have your apps linked to, and the 2nd is where your data is. In that case, stock Android ROMs wouldnt be able to access the data partition.In my sdcard i ' ve 2 partition. 1 for the applications linked and 1 for data.
With Your help now the Partition with applications work and is visible by android system, while the second is not visible by android. If i open file manager of twrp, it see the partition with the data, files, everýthing. But if i start phone normally the partition of data is invisible, like it Was not inserted
Can you take a picture of it with another phone?I think there is a problem in the script.
My phone has 64gb of intern memory.
Have AN sdcard of 256gb partitioned in one partition of 56gb for applications and one of 200 for data.
But if i look in android, it Was like intern memory of 28gb.
I can' t install anything and i can't make screenshot, because it says there isn't enough space
So you are out of space even without the SD card? If that's the case, then only a firmware/ROM reflash or factory data reset will fix it.
Thanks, Will try Aparted!@YK RAJ: The "SDcard" partition is first, and sdext2 is 2nd. So, assuming your MicroSD is formatted this way (and it should be this way, due to how stock Android firmwares only natively mounts the 1st primary partition that has a compatible filesystem), then you will need to delete 2nd partition, increase size of 1st partition, then recreate 2nd partition as something being smaller than what it is now.
If you currently have apps linked to sdext2, you should unlink or uninstall them before proceeding.
You can do this in Windows with something like MiniTool free edition. Or in Linux, it has numerous partitioning programs. You can also do it on the phone with Apps2SD or AParted (although I think Apps2SD's inbuilt partitioner isn't so flexible, and will force you to format the entire card). I personally recommend AParted for this, just be careful not to delete what you wish to keep.
I meant linking the internal data (located in the userdata partition of the device). To my knowledge fbind can't do that. But even if it's possible to bind mount an entire user, it's not something I would recommend doing. Too much opportunity for weird bugs, crashes, etc to occur. I don't know that much about fbind beyond using it to link some stuff from internal storage to external storage. So if you have questions about it, I'd ask in that thread. @VR25 also has Telegram chat channels you can join.
Su.d was originally a function of SuperSU. But it's basically nothing more than a function of auto running scripts on boot. Init.d has been able to do that for a long time, and Magisk also. I'm using /data/adb/service.d. if you're using Apps2SD on Android 11/12 in particular, I would also enable the setting to not let the app modify system partition. Too much chance of a bootloop/inability to boot on newer Android versions. It happened to me once on 11, I had to go through a somewhat complicated process to undo Apps2SD's changes and get back into Android. Setting the su.d path works fine though, since it doesn't modify Android's system files.
Can't advise much with adoptable storage and issues relates to linking/binding with it. I tried it once a few months ago and lost over 150GB of files that can't be recovered. Much of it wasn't critical, but some was. Still reeling a bit recovering from that. As a result, I won't use AS again unless I'm confronted with a scenario where there are no other viable options.Great, thanks for all the tips. I had already heeded your advice to choose not to have the app modify the sys partition when it asked me.
I'm finishing setting up my new Nokia 6.1 with LineageOS 18.1 (Android 11), also running latest Magisk and latest LSPosed. I've formatted my SD card as internal aka "adoptable storage" for encryption. Above all what I want to do is move and bind 2 apps' data from #/data/data/app.path to adoptable storage. Before on my Samsung (SD as regular mobile) I achieved that via Symlinks with Root Explorer or FX Explorer [root], but this is not working anymore in my new setup. And XInternalSD isn't helping here.
Get rid of adoptable storage while you can, go back to what Android calls "portable storage".Sorry to hear about your data loss due to messing with AS. I know how that feels.
Thanks for your explanation of how AS works. Already having read many pros and cons about it, I'm still lamenting if how AS works is really what I want. Esp. because of the way migrating works - that I can't choose what is getting migrated but am forced to migrate everything. I initially had thought AS would only merge the SD card into Internal Storage, and not also move /data/apps and data/data hidden in the background. Esp. since hardly and app works if run from AS anyway and I had to enable a switch to install and keep apps on internal. I think much rather I'd prefer to have all apps and data on internal by default, and continue to choose willingly via XinternalSD and root Symlinks what exactly to move to SD card.
Re. backups: very good points - here's how I've been doing it:
- backup via TWRP -> images to PC
- phone booted into Android & connected to PC: manual copies of Internal and SD-card's folders/files -> PC
- with SD formatted as AS: SD-card via adapter into PC then 1:1 RAW clone saved as compressed image
The path to folder with the encryption keyfile in /data/misc/vold is great to know - I just backed the entire folder up