I am using an 8GB sd card to boot into CM7. I have checked the partitions and there is the "boot" partition which is really small, then a 1GB Nook Color partition, and a 5GB CM7 Partition.
I am not too concerned about moving partition sizes and such, I know there is some wasted space in there but I just want it to be stable rather than nit picking for space etc.
The problem is that when I am installing Android apps it comes up and tells me I am out of space. This doesn't make sense because both partitions are huge and I only have 1-2 apps installed and TONS of free space.
How can I get it to realize there is a ton of room?
Most android settings refer to saving "on the phone" or "on the SD" and I am not really sure which partition the OS thinks is "the phone".
MuGGzyx said:
I am using an 8GB sd card to boot into CM7. I have checked the partitions and there is the "boot" partition which is really small, then a 1GB Nook Color partition, and a 5GB CM7 Partition.
Click to expand...
Click to collapse
If you used the SASD images by verygreen, then you need to check again... If that's all you see you need to set it up again... there should be 4 total partitions after running the SASD scripts
Ok so I did use verygreens image and created the little 116mb partition. I am reading some other threads that suggest resizing that before booting the Nook.
Is this first partition what the system later thinks is "the phone" for the purposes of installing apps?
If not, which partition does the SD booted Android system think the system drive is for the purposes of installing apps?
Related
I got a shiny new class 6 16GB sd card. I partitioned it at about 15.5GB fat32 and 512 ext2, using the info in cyanogen's wiki: http://wiki.cyanogenmod.com/index.php/Apps2SD_On_CyanogenMod
From there I did the ext3 and then the ext4 updates.
Although I've searched for answers for a few hours now, I've been unable to determine why the device slows to a crawl at each point of user interaction at this point. Even unlocking the screen can time out...
I backed out the changes and copied the apps back over to internal storage and everything is zippy again, so at this point I am looking for suggestions. One thing I noticed was that when I used parted to delete the ext partition so the apps wouldn't go back to the card on the next boot, it still listed the ext partition as ext2. Can someone running ext3 or 4 let me know whether parted lists their partitions as such or if they are always reported as ext2?
What other techniques should I try? I would very much like to make this work as I get constant low-space warnings in my current setup. Thanks.
jasper1 said:
I got a shiny new class 6 16GB sd card. I partitioned it at about 15.5GB fat32 and 512 ext2, using the info in cyanogen's wiki: http://wiki.cyanogenmod.com/index.php/Apps2SD_On_CyanogenMod
From there I did the ext3 and then the ext4 updates.
Although I've searched for answers for a few hours now, I've been unable to determine why the device slows to a crawl at each point of user interaction at this point. Even unlocking the screen can time out...
I backed out the changes and copied the apps back over to internal storage and everything is zippy again, so at this point I am looking for suggestions. One thing I noticed was that when I used parted to delete the ext partition so the apps wouldn't go back to the card on the next boot, it still listed the ext partition as ext2. Can someone running ext3 or 4 let me know whether parted lists their partitions as such or if they are always reported as ext2?
What other techniques should I try? I would very much like to make this work as I get constant low-space warnings in my current setup. Thanks.
Click to expand...
Click to collapse
just used parted to check and it says ext4 .... try using this guide .. worked really well for me to partition my sd ... also if you're having all these problems try wiping dalvik-cache and even data and your ext* partition if it comes down to it
What recovery image are you using?
jndd333 said:
What recovery image are you using?
Click to expand...
Click to collapse
amon ra's 1.2.3
EDIT: lol thought you were the OP
A more careful walk through the partitioning process and I can confirm that everything works as expected, as well as confirming that if upgrade_fs fails, then ext2 is a total dog. One particularly confusing thing was tracking down whether a swap partition was needed or not, but on the latest cyan roms it isn't so I skipped that one.
CM7 can make you install apps on the sd card, how does it differ from app2sd or app2ext? i have been trying to decide if i should partition my new sd card or its not necessary. There must be an advantage to have app2ext right?
Thank you.
CM7 basically allows you to move all applications using Froyo's app2sd mode. Even ones that have disabled it (like live wallpapers and widgets as those won't work when installed that way).
app2sdext works differently as it will install apps directly to an ext partition on your sdcard (that you manually have to set up). This functionality is NOT build into CyanogenMod, but is easily added with a number of different apps/scripts. This will give you a lot more free space on your phone, and all apps can be installed there regardless of whether they have widgets or have services running. Most app2sdext options will also give you the option of moving the dalvik cache to the sdcard which will save you a substantial amount of space on your internal memory.
Basically, if you want a lot of memory intensive apps, your only decent option with a Nexus One is an app2sdext solution. (I have it with a 1GB partition, and I will soon either need to resize it or delete apps... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
bassmadrigal said:
CM7 basically allows you to move all applications using Froyo's app2sd mode. Even ones that have disabled it (like live wallpapers and widgets as those won't work when installed that way).
app2sdext works differently as it will install apps directly to an ext partition on your sdcard (that you manually have to set up). This functionality is NOT build into CyanogenMod, but is easily added with a number of different apps/scripts. This will give you a lot more free space on your phone, and all apps can be installed there regardless of whether they have widgets or have services running. Most app2sdext options will also give you the option of moving the dalvik cache to the sdcard which will save you a substantial amount of space on your internal memory.
Basically, if you want a lot of memory intensive apps, your only decent option with a Nexus One is an app2sdext solution. (I have it with a 1GB partition, and I will soon either need to resize it or delete apps... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
Click to expand...
Click to collapse
why didnt i think of that? thank you for your reply... now i should decide whether to do it now or wait till i have reached maybe about a hundred apps. by the way does it have any effect on the speed of the phone if you do that?
I am on cm7 and decided to put cache apps on sd card using ta utility is there any other new apps like that? ta
Can you do this with rooted stock?
lolobabes said:
why didnt i think of that? thank you for your reply... now i should decide whether to do it now or wait till i have reached maybe about a hundred apps. by the way does it have any effect on the speed of the phone if you do that?
I am on cm7 and decided to put cache apps on sd card using ta utility is there any other new apps like that? ta
Click to expand...
Click to collapse
I have a class 4 32GB card, and I didn't notice any appreciable difference in speed. I have moved my apps and dalvik cache to the sdcard using DarkTremor's a2sd. I currently have 260 apps installed on my phone, and that is pushing the internal phone space and the 1GB partition I set up for ext. I am about to bug danger-rat for his instructions on how he resized his internal partitions to give the data residing on the phone more space (I will basically shrink the cache partition and I am looking at resizing my ext partition to 1.5GB or 2GB.
I couldn't live without this anymore. I don't know how I went so long without it. It is so nice to just browse the online market and click install on countless apps without worrying about your space.
If you want to try and move the app data (resides in /data/data) to the sdcard, I have heard that it is recommended to have a class 10 card to keep up with speed requirements. I am not sure how many apps support that.
brettbellaire said:
Can you do this with rooted stock?
Click to expand...
Click to collapse
I believe you can. You would have to have a custom recovery. The main thing I am not sure is if it will mount the ext partition. If you have a custom recovery, do a nandroid backup (just in case it doesn't work), flash the zip for DarkTremor, and reboot the phone (the first boot will take longer).
brettbellaire said:
Can you do this with rooted stock?
Click to expand...
Click to collapse
yes you can.
bassmadrigal said:
I have a class 4 32GB card, and I didn't notice any appreciable difference in speed. I have moved my apps and dalvik cache to the sdcard using DarkTremor's a2sd. I currently have 260 apps installed on my phone, and that is pushing the internal phone space and the 1GB partition I set up for ext. I am about to bug danger-rat for his instructions on how he resized his internal partitions to give the data residing on the phone more space (I will basically shrink the cache partition and I am looking at resizing my ext partition to 1.5GB or 2GB.
I couldn't live without this anymore. I don't know how I went so long without it. It is so nice to just browse the online market and click install on countless apps without worrying about your space.
If you want to try and move the app data (resides in /data/data) to the sdcard, I have heard that it is recommended to have a class 10 card to keep up with speed requirements. I am not sure how many apps support that.
I believe you can. You would have to have a custom recovery. The main thing I am not sure is if it will mount the ext partition. If you have a custom recovery, do a nandroid backup (just in case it doesn't work), flash the zip for DarkTremor, and reboot the phone (the first boot will take longer).
Click to expand...
Click to collapse
thanks for the reply i think i read on darktremors post class 4 will do for the data2sd. I have class 4 16GB sd card would 1GB good for the ext? ty
It really depends on how much you think you will be installing. I did a 1GB partition on mine, but now that I install most of the Amazon free daily apps, that space is dwindling quickly. I have programs that will resize the partition for me, but most will have to wipe the card and partition it manually. I do have the install location set to automatic, so it allows developers to specify whether they want it in the "internal" (really it is on the sdext partition, but to the phone it is internal) or external using the froyo method. The Angry Bird apps all default to install on the sdcard, so my installed app base is even larger than 1GB.
bassmadrigal said:
... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
Click to expand...
Click to collapse
I second this
Sent from my Nexus One using XDA App
is it true that cwm sets the partition to ext3 by default? unlike in ra recovery where you still need to convert it? ta
I have heard that it creates it in ext3, but right now, DTa2sd is showing that it is a ext2 partition. I can't figure out how to find out for sure while the card is in the phone. Either way, it is getting mounted as an ext2 partition.
temasek said:
I thought CWM will create ext3 by default? Your steps are ok, np.
Anyway when u read the ext partition type in android, most likely u will see ext2 if u are using official DT script cuz of the auto syntax it uses.
Click to expand...
Click to collapse
then it maybe so, this was posted on the darktremor thread
http://forum.xda-developers.com/showthread.php?p=14134665#post14134665
Well, whether or not it is formatted as an ext3 partition, Android is still mounting mine as an ext2 partition.
Code:
mount | grep ext
NOTE: the "|" is called a pipe. On the keyboard it is the shift option on the backslash key "\". I don't know exactly where it is on the stock keyboard, but on swype it is located under the "D" key when the keyboard has the shift key pressed and you access it by longpressing.
To get your sdcard to ext3, you just need to turn on journaling. You can do this through adb while in the recovery (because you need the partition unmounted to do this).
Code:
adb reboot recovery
adb shell
mount system
e2fsk /dev/block/mmcblk0p2
tune2fs -j /dev/block/mmcblk0p2
reboot
Supposedly Android should auto-mount this as ext3 on boot (which you can check with the first command). At that point, I don't think it will matter what a2sd shows. As the writing of the journal (the big thing with ext3, since it helps minimize write errors on a bad shutdown) is done at the OS level, not the a2sd level.
Just got my Nook Color tonight. I booted it from a CWM microSD card, installed CM 7.1 stable, gapps, and ran ROM Manager to install CWM to internal memory.
When I go to Menu, Settings, Storage, under the 'Internal Storage' heading, it says "Total space" of 5.09 GB and "Available space" of 4.68 GB. (One app installed so far)
Looking farther down the screen, it shows /mnt/eemc to have 1.00 GB of space.
Is there a way to combine them so that I have 5.68 GB of usable internal space to install apps to? Also, are those two the full available capacity of the eMMC storage? If not, can it be enlarged to maximum?
Also, further down the screen, it shows /mnt/usbdisk, with no space. Should it be left intact, or can it be safely removed to limit my confusion?
Thanks!
+1 to your question.
I'm gonna use my NC only as a tablet not any book reading so I don't think that 1GB is required.
Still let's wait for a dev. to give expert advice about this and possibly a how-to...
I would leave /mnt/usbdisk alone as it will be useful if you decide to use flash drives through nook tweeks in the usb section. As for the emmc data area, you can store data there with no problem if you are not going to use the nook as an e-reader.
By downloading the nook tweeks app, you will have access to the micro usb port (through an adapter) to transfer data between the nook and a flash drive or (using a powered hub) a card reader. You can also transfer data between the nook and a camera to directly save photos to the nook or view them. Usb host mode opens the nook up to another level and makes it a very functional tablet.
I use my nook with a digital camera on photo shoots so that I can preview my shots on a larger screen than that of the camera. You can check out my threads here concerning host mode. PM me if I can be of any assistance.
Sent from my NookColor using Tapatalk
SweetBearCub said:
Just got my Nook Color tonight. I booted it from a CWM microSD card, installed CM 7.1 stable, gapps, and ran ROM Manager to install CWM to internal memory.
When I go to Menu, Settings, Storage, under the 'Internal Storage' heading, it says "Total space" of 5.09 GB and "Available space" of 4.68 GB. (One app installed so far)
Looking farther down the screen, it shows /mnt/eemc to have 1.00 GB of space.
Is there a way to combine them so that I have 5.68 GB of usable internal space to install apps to? Also, are those two the full available capacity of the eMMC storage? If not, can it be enlarged to maximum?
Also, further down the screen, it shows /mnt/usbdisk, with no space. Should it be left intact, or can it be safely removed to limit my confusion?
Thanks!
Click to expand...
Click to collapse
Hey there, I know long time but iI have some info to share since I'm having the same configuration as yours.
The 'Internal Storage' you're seeing isn't exactly the emmc. Its just that cm7 doesn't know its put on an SD. And it thinks the second or third partition of the SD (i.e. cm7 system partition) is internal.
Also that /mnt/eemc is the actual internal memory and thus these 2 can't be linked. However, the nook has another 5gb emmc internal partition callednmedia which you can possibly combine with emmc.
Sent from my NookColor using Tapatalk
there are many threads about the NC partition layout and changing it. do a search. the 5g partition basically won't be used by your cm7 NC. the apps will go on the 1g. I repartitioned mine for 4g instead of 1g and 2g for /emmc. then you can set cm7 to swap the /emmc and /sdcard and then use the NC without an SD installed.
mr72 said:
there are many threads about the NC partition layout and changing it. do a search. the 5g partition basically won't be used by your cm7 NC. the apps will go on the 1g. I repartitioned mine for 4g instead of 1g and 2g for /emmc. then you can set cm7 to swap the /emmc and /sdcard and then use the NC without an SD installed.
Click to expand...
Click to collapse
I was thinking something else.....
I wanted to merge internal data and media so as to get combined partition. I'm running CM7 off the SD card so I don't need to switch them. I was just thinking of merging them.
Sent from my NookColor using Tapatalk
therkr said:
I was thinking something else.....
I wanted to merge internal data and media so as to get combined partition.
Click to expand...
Click to collapse
Yes, I understand that's what you want to do. However, those partitions are not contiguous space. Search on Nook Color partitions and you will quickly see why.
Specifically, look here:
http://forum.xda-developers.com/showthread.php?t=1094371
which links to here:
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
/dev/block/mmcblk0p6 is the "data" partition
/dev/block/mmcblk0p7 is the "cache" partition
/dev/block/mmcblk0p8 is the "/mnt/emmc" partition
You are wanting to combine "data" and "/mnt/emmc". Problem is the "cache" partition is stuck in between them.
The other problem is your NC uses these two partitions for different things.
I think the suggestion I made before, which is to repartition for 2GB+4GB as in the first link, then do Settings -> CyanogenMod Settings -> Application -> Use internal storage to get them to swap, is the best, simplest solution with the lowest risk. This uses the 2G partition for whatever normally is used for /sdcard by most apps (downloads, misc. files, temp storage, etc.) and 4G partition for your apps, and leaves your whole SD card for use solely for your side-loaded media content. This schema will not interfere with further CM updates or unnecessarily change the default partition scheme for which most of the devs are writing code.
If you want to become a Linux & Android master of partitioning and storage management, then you can probably implement a more custom scheme. In my last job I was a software engineer working on a Linux-based network-attached storage appliance and I wrote most of the system code dealing with disk and partition management, so you could say I know a lot about it, but still I chose the easy path for my NC.
mr72 said:
If you want to become a Linux & Android master of partitioning and storage management, then you can probably implement a more custom scheme. In my last job I was a software engineer working on a Linux-based network-attached storage appliance and I wrote most of the system code dealing with disk and partition management, so you could say I know a lot about it, but still I chose the easy path for my NC.
Click to expand...
Click to collapse
Thanks for the info. But I'm just a highschool sophomore who loves technology. Can't do this unless someone has ever tried (and succeeded) before.
I'll probably use your method when I install CM7 (or CM9) onto emmc.
Sent from my MB502 using XDA App
Can you change the stock partition size on safestrap's stock slot at all? It shows two internal memory slots, one at 3.01gb and the other is 8gb. What is going on with that other 5gb and why isn't it used?
hockeymikey said:
Can you change the stock partition size on safestrap's stock slot at all? It shows two internal memory slots, one at 3.01gb and the other is 8gb. What is going on with that other 5gb and why isn't it used?
Click to expand...
Click to collapse
Not 100% sure, but I believe the non-user 8gb is split between /webtop, /cd, /preinstall, /system, /data, /cache/. /webtop and /preinstall alone eat up 2gb of it.
And, no, it can't be changed. Our resident awesome developer gave it a try a while back, and found that apparently the bootloader checks at power-on to see if the partitions are all "correct". If they're not, it pops an error screen, and there's nowhere to go from there; it pretty much soft-bricks the phone until the stock configuration is restored via fastboot image.
If we had an unlockable bootloader, then it's possible that this restriction could be removed. However, we don't - based on some poking at it by another member, it doesn't even recognize commands to pull information for/enter an unlock code - so we're stuck with stock partition sizes and virtual slots.
If you really have no choice but to use the stock "slot", you might want to look into buying a big SD card, getting Link2SD, and devoting part of said SD card to it. If you're using KitKat, the built-in App2SD might be adequate, but for Lollipop/Marshmallow, the 3gb just...isn't enough. App2SD isn't effective enough.
Otherwise, get a decent SD card and write the internal 8gb off as system storage. Make a slot with a 4gb /data size (the biggest we can go), and 700mb-1gb /system size. Install a gapps package that contains anything you would normally go to the Play Store and download separately; this installs them to /system, leaving /data more free for downloaded apps.
For large apps, use App2SD where you can to shift part of them from /data to the internal 8gb.
If you don't plan on flashing new nightlies very often, you can get apps to convert other apps into system apps, storing them in /system as well. The problem here is that they'll be wiped out whenever a new ROM is flashed, so you'd have to devise some method of backing them up and flashing them after the new nightly (ZipMe might work).
Hello folks. Before going further I need to apologize. I really fighted to use Link2SD on my Galaxy tablet and I succeeded more or less. I thought that my tentative could be useful to others. So I posted this topic.
I worked a little more, and now I am convinced that I was wrong from the beginning.
The reality is that Apps2SD and Link2SD are obsolete utilities.
Forget creating a second volume on your external SD Card :
- Android/Samsung declare your SD Card as corrupted and always wants to reformat it.
- TWRP mounts the wrong partition and you have to manually unmout it and remount the good one
- The partitions need to be declared with a wrong type and this is really not clean
etc...
I suggest that you do not loose your time, forget Link2SD, and read this excellent topic:
https://www.xda-developers.com/divi...gles-fuse-replacement-will-reduce-io-overhead
My Galaxy tab A has only 11 Go available for the user. I bought a 128 Go external SD card to extend both /storage/emulated/0 and /data.
When you first install your SD Card, Android automatically mount this card as /storage/xxxx-xxxx.
This is a FAT volume extended on all your SD Card (128 GB for me).
This is fine for storing ebooks, music, video, and your backups.
But impossible for Link2SD to move your apps on this volume and put a symbolic link on the previous location, because FAT is not a UNIX file system. Link2SD (or Apps2SD) needs a second disk volume on partition 2 (/dev/block/mmcblk1p2) formatted with a UNIX file system (ext4 is fine).
Of course you need to have rooted your device. [A non rooted tablet is not better than a vulgar iPhone ]
To re-partition my SD Card I used ROEHSOFT PARTITION TOOL (SD-USB). (I tried unsuccessfully Aparted, it crashed every time I launch it). ROEHSOFT is convenient but tricky to be used by an advanced user :
- You cannot create a partition in a specific slot (for example /dev/block/mmcblk1p2): It automatically use first slot for the first partition you create, the second slot for the following partition, and so on.
- If you try to foul it, deleting a partition and recreating it in another empty space, it suddenly decides to reorganize your 4 slots. It really wants /dev/block/mmcblk1p1 to be the first partition on your SD Card, /dev/block/mmcblk1p2 the following, etc...
- You cannot create a partition at a specific offset inside an empty space.
After fighting with ROEHSOFT I finally won. I discovered too late that "fdisk" is part of BusyBox. If you know "fdisk" my advice is to use it instead of fighting with a software which pretends to be user friendly but is too limited.
OK, stop bla-bla and work.
1 - Dismount your SD Card : Parameters/Device Maintenance/Storage/Menu-Storage Parameter/Dismount
2 - Delete the only one partition
3 - For a misterious reason, my Android was not happy with his FAT volume on /dev/block/mmcblk1p1. Link2SD wants his UNIX volume on /dev/block/mmcblk1p2. So, if you use ROEHSOFT you need now to create a small dummy partition on /dev/block/mmcblk1p1. For me I created a 4 Go partition to be used by Linux Deploy. This partition needs to be declared as FAT32 (LBA) but should not be formatted as a FAT file system. EXT4 is a good choice.
4 - Create the second partition for Link2SD. I suggest not too much space for it, because you probably want a huge space for the third partion. This partition needs to be declared as FAT32 (LBA) but should be formatted with a UNIX file system. EXT4 is a good choice.
5 - Create the third partition to be used as SD extension for Android. This partition should be very large : you will store on it your music, your movies, your ebooks, and above all your backups. This partition needs to be declared as FAT32 (LBA). I formatted this partition as a EXFAT file system.
6 - Reboot. If you are lucky you will get two notifications : one saying that you have a corrupted memory card, and one saying that you are ready for media files. You will get those two notifications at each reboot.
8 - Recreate mounting scripts inside Lin2SD (or Apps2SD), and reboot.
7 - If you are a UNIX user just type "df -h" in a terminal to verify that the two partitions are mounted with correct sizes).
8 - You can look what Android think of your partitioning :
/Parameters/Device Maintenance/Storage/Menu:Storage Parameter/.
Do not try to mount the two first volumes and NEVER try to reformat them with Android. Those volumes are declared as corrupted but this is normal. Android does not expect to find a UNIX file system on a partition declared FAT32.
If one day, you forget this and ask to Android to reformat a corrupted partition you will have the terrible surprise that Android will not only erase your partition, but will erase everything and recreate one and only one big empty partition. (I guess that you keep all your backups on this SD Card, like me, so this is a really bad surprise).
Do not ask me why Android does not want his SD-Card on first partition. I have no idea. I guess that Android or Samsung reserve this partition for something else.
Do not ask why I had to declared all my partitions as FAT32 even if two of them are formatted as EXT4. I just realized that this configuration works well after fighting during a full day.
I hope that this topic will help some of you.
You really need the second partition on the SD? Or you can have only one ex4 partition that fills all the SD? (Remove the FAT and only have one ext4)
Palatosino said:
You really need the second partition on the SD? Or you can have only one ex4 partition that fills all the SD? (Remove the FAT and only have one ext4)
Click to expand...
Click to collapse
No, I tried but it doesn't work.
I found today a very interesting topic that I will try to master and hopefully wil, understand everything better :
https://www.xda-developers.com/divi...gles-fuse-replacement-will-reduce-io-overhead
Maybe I was wrong from the beginning : perhaps LinkSD and apps2SD are historic patch that are not useful anymore. Perhaps all the burden will be fixed easily just by not using those utilities anymore.
"sdcardfs" is something very new for me who is an old UNIX fellow. This seems to be a major improvement for Android.
I will update this topic when everything will be clear for me.
I didnt have this problem on android 6, but on android 7 . My phone wants to use ext4 as data partition and says its corrupted, link2sd detects this second partition normally, but my data partition fat 32 detected on phone settings and its says its ready but there is no option to mount it.
As far as i understand from this tutorial i need to make 1 fake ext4 partition say 1mb, then second partition ext4 for use with link2sd, and third partition fat32 for use as data storage ??
My phone is samsung j7 2016
So i did follow this , but now my phone wont detect fat32 and link2sd didnt detect 1 of other ext4 partitions
Looking for a definitive way to Root and use link2sd to have my SM-T580 use the SD as a primary parition for apps and data. Been researching and trying a dozen different methods already to no avail. Bonus if there's a way to roll it back easily. Am on the latest android release.
Thank you for all replies.
larpoux said:
I hope that this topic will help some of you.
Click to expand...
Click to collapse
You're my saviour, thank you ! I've been fighting on the same issue for days and didn't think about that trick to declare an ext partition as FAT32 !
I know you probably won't see this, but I just wanted to tell you how much I appreciated this guide.
I have a Galaxy Tab S3 and every since going to a custom rom, I haven't been able to get this working which was such a pain with less than 23 gb of storage. The Rom improved my performance far too much for me to change back and every guide I attempted pointed me in the wrong direction but finally, I'm able to use my 120 gb SD card which has made my tablet worth using again.
To anyone who may attempt in the future,
I'm using Android 9 + Magisk. Using the Advanced type Mount script was the only way it get it functioning but I've had no issues with linking apps and no message regarding a corrupted SD card. It can take a few minutes on boot for everything to properly load in, but the apps all update and there's no performance/loading time issues.
Thanks again!