I flashed my HD2 with MIUI 2.3.7 some time ago, but now I'm constantly getting low internal storage errors. One thing I didn't do when I flashed this ROM was repartition the SD card (and I think this ROM has A2SD built in?). So I know that might probably help getting rid of the errors.
But when I checked the phone's internal memory, I saw "200 MB used - 18 MB free". So that's a total of 218MB internal memory? I'm pretty sure I'm missing at least 200Mb there.
I have another HD2 here (running AmeriCanAndroid from SD) so I checked its internal memory under "About Phone". On the HD2 with ACA, it says it has a total of 411MB internal memory. On the HD2 with MIUI, it says it has a total internal memory of 217MB. So where's the missing 194MB?
I read somewhere that the phone probably has a wrong "ClockworkMod Recovery partition layout" and that for MIUI, it needs a "150MB Partition Layout". The article didn't actually explain what those things are or how to set it up.
So, is that indeed what's going on here (any way to check)? And if so, how can I change my phone to this "150MB Partition Layout?"
Thanks in advance.
Like I said, it was quite a while ago when I flashed this ROM so I can't remember what I did when I did. But looking at my HD2 folder on my PC, I probably *did* use a 150MB ClockWorkMod recovery partition size. Also, I *did* create a 1GB ext partition on my SD Card for A2SD.
So why am I getting the "low internal storage" errors?
Many possibilities, could be the ext partition not being recognized, not in proper format...
The script may not be working (?). And you're never going to get the whole 512MB of your ROM. I think it's maximum 400, give or take. so about 400 - 150 you're left with about 250 .. I don't know where that 50 went (maybe it is not actually 400? or maybe you set a slightly larger partition).
I also never believed in a2sd, always datatoext. Your best bet is to back up your apps using titanium (or similar apps), check the partitions, and reflash ROM + a different script; that is because you can't flash a script while having been used the rom. (or you can try your luck).
dat english.
I second that, app2sd is not reliable to get more memory available.
Lack of internal storage is due to a incorrect system partition. It has nothing to do with your ext4 partition, since you're not running NativeSD.
DataOnEXT is your best option. Backup your app data and flash a ROM from start with DataOnExt option.
Be sure to make your system size large enough.
Create an ext4 partition on your sd of 1 to 2 GB for app storage.
Sent from my NexusHD2 using xda app-developers app
You should use Cronmod http://forum.xda-developers.com/showthread.php?t=1716124 INT2EXT+ is recommended
Flash your rom on nand (without dataonext) then flash Cronmod(you must have ext4 partition, 1gb is good)
On clk 1.5 you can easily change partition sizes without computer
Marvlesz said:
Many possibilities, could be the ext partition not being recognized, not in proper format...
Click to expand...
Click to collapse
This is what A2SD reports:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it looks like it's being recognized just fine...
Zippy1970 said:
This is what A2SD reports:
So it looks like it's being recognized just fine...
Click to expand...
Click to collapse
Yes, it is. But the script you're using is useless. Use DataOnExt instead.
WARNING: You need to do a fresh install, so make a backup beforehand.
I tried DataOnExt and I can't get it to work. It keeps giving me force close errors on almost every app/widget and when I reboot my phone, all my widgets loose their settings.
Zippy1970 said:
I tried DataOnExt and I can't get it to work. It keeps giving me force close errors on almost every app/widget and when I reboot my phone, all my widgets loose their settings.
Click to expand...
Click to collapse
Try a different ROM, and increase your /system size to 285MB or 300-350MB if you have badblocks.
Zippy1970 said:
I tried DataOnExt and I can't get it to work. It keeps giving me force close errors on almost every app/widget and when I reboot my phone, all my widgets loose their settings.
Click to expand...
Click to collapse
You can't dirty flash it, you need a fresh install. If you do a dirty one, everything will force close.
Have you considered using NativeSD?
mengfei said:
Have you considered using NativeSD?
Click to expand...
Click to collapse
I second this, NativeSD can be great.
The only few cons I know of, is that NAND is a tad bit more responsive (even with highclass SD cards), battery life is shorter than if you only were to use NAND and your SD card will wear out quicker.
Other than that, it's basically superious to NAND.
Related
So, I recently received my replacement and immediately got it rooted. Since I have tons of apps, I rely on transfering some apps to my SD to get me by. I read that EXT3 would be more appropriate for Myn's 2.2, so I formatted my SD EXT with 0MB swap size and 2GB space with the EXT3 format. Everything seems to have worked fine. I use 'App 2 SD Pro' to notify me of apps that are capable of transferring over and it still shows that I have 22.7GB available on my SD Card. Shouldn't it limit it to the 2GB I dedicated?
There are different kinds of apps2sd. There's the old way, where you format part of your SD card to ext2/3/4 and you have symlinks from your /data/apps directory to that partition. Then there's the new way, where Google let's you put your apps on the FAT32 partition (normal) of your SD card in the .android_secure folder.
If you're doing it with Android's built-in apps2sd functionality, then you don't need to partition your card for ext2/3/4 to put your apps on your SD card.
I run a 500mb ext4 partition, I am using dark tremors a2sd. I use a2sd from the market and it also tells me how much free space is left on the whole SD instead of how much free space is left on the ext partition.
Here's what mine looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sultan.of.swing said:
I run a 500mb ext4 partition, I am using dark tremors a2sd. I use a2sd from the market and it also tells me how much free space is left on the whole SD instead of how much free space is left on the ext partition.
Click to expand...
Click to collapse
In your first pic, you have a2sd+, 384 of 457 available... That's your ext partition, no???
Edit: Bold quoted text... Still confused...
gpz1100 said:
In your first pic, you have a2sd+, 384 of 457 available... That's your ext partition, no???
Click to expand...
Click to collapse
Correct. That's the ext partition.
its just the space on the extened partion of the memory.
What's the difference between using Dark Tremor's and Google's built-in? I'm on Myn's 2.2 btw.
Also, how do I get the remaining A2SD+ ext space I have? Can't find it anywhere.
sultan.of.swing said:
Correct. That's the ext partition.
Click to expand...
Click to collapse
I don't understand?? Edit, disregard. I think your pic is showing the contents of both partitions individually.
@akarol, a little searching goes A LONG way. All your questions are answered in the first post.
http://forum.xda-developers.com/showthread.php?t=715938
Well, ok... that clarifies things a bit. However, I seem to not even know which version I am currently using. I am running Myn's 2.2 RLS 5 atm which I think might just use Froyo's method. For example, App 2 SD Pro guides me to the Manage Application screen for that specific app to move to/from SD. Does this mean I am using Froyo's method? If I am, then I don't need any EXT on my SD card right? If so, how do I remove it in Amon RA's recovery and will I need to wipe my ROM and start from scratch?
akarol said:
Well, ok... that clarifies things a bit. However, I seem to not even know which version I am currently using. I am running Myn's 2.2 RLS 5 atm which I think might just use Froyo's method. For example, App 2 SD Pro guides me to the Manage Application screen for that specific app to move to/from SD. Does this mean I am using Froyo's method? If I am, then I don't need any EXT on my SD card right? If so, how do I remove it in Amon RA's recovery and will I need to wipe my ROM and start from scratch?
Click to expand...
Click to collapse
I am not familiar with Myn's roms, but a quick look at the main thread ( http://forum.xda-developers.com/showthread.php?t=793471), seven bullets down from "Some of the features in RLS 5 (01-07-2011) include:", it clearly says, "Updated Darktremor Apps2SD (2.7.5.2)".
Then, in post #3 (http://forum.xda-developers.com/showpost.php?p=8341836&postcount=3), in the FAQ section, there's a link to more info on the apps2sd function.
Personally, I think the write up in the DT thread is more than sufficient at explaining what it is, and how to set it up. What you are probably missing is that by having DT installed, your apps are automatically installed to the ext partition, transparent to the system. If, you now use the move2sd function in settings/applications, you are in essence, moving them from the ext3 partition (on the sd card) to the main partition (also on the sd card). I see little benefit to do this. Either use one method or the other.
This brings up the point, that with the DT method, even apps that traditionally can not reside on the SD card can do so (usually) without issue. I forget the criteria for being able to be moved, but suspect it has something to do with the fact that the main /sdcard partition can be unmounted from the system's view when connected via usb. DT's method secures the ext partition from such actions.
gpz1100 said:
I am not familiar with Myn's roms, but a quick look at the main thread ( http://forum.xda-developers.com/showthread.php?t=793471), seven bullets down from "Some of the features in RLS 5 (01-07-2011) include:", it clearly says, "Updated Darktremor Apps2SD (2.7.5.2)".
Then, in post #3 (http://forum.xda-developers.com/showpost.php?p=8341836&postcount=3), in the FAQ section, there's a link to more info on the apps2sd function.
Personally, I think the write up in the DT thread is more than sufficient at explaining what it is, and how to set it up. What you are probably missing is that by having DT installed, your apps are automatically installed to the ext partition, transparent to the system. If, you now use the move2sd function in settings/applications, you are in essence, moving them from the ext3 partition (on the sd card) to the main partition (also on the sd card). I see little benefit to do this. Either use one method or the other.
This brings up the point, that with the DT method, even apps that traditionally can not reside on the SD card can do so (usually) without issue. I forget the criteria for being able to be moved, but suspect it has something to do with the fact that the main /sdcard partition can be unmounted from the system's view when connected via usb. DT's method secures the ext partition from such actions.
Click to expand...
Click to collapse
Wow, thanks! I customized my a2sd settings as instructured in post #3. However, I still cannot verify that my apps are placed on the EXT partition or in the main partition of the SD card. Any way to do this?
When trying to dual boot WP & Android the WP partition must always be bigger than the Android partition or more than 1/2 the size of the SD card otherwise it wont work - I still don't know why :silly:
Anyways here's how you can have a smaller partition for WP & having the big chunk of space for Andy.
Here's what we need
2 SD cards, I used 4g(SOURCE) & 16g(TARGET) Cards
2 SD card readers
MiniTool Partition Wizard Home Edition (MTPW)
Initially you setup WP using the smaller Card
if you are not yet familiar in setting WP try the link Below
My 3rd Root & guide for the ultra-noob [WP7/ Android]
Once you've setup WP, we have to adjust the WP partition to the desired space we want.
Follow the link below for partitioning adjustment/ resize
Triple Boot WP7+SD+NativeSD EXT4 @ 1 SD with pictures
• Actually if you used a 4gig SD Card in your initial setup it will create a 3gig partition & I think that's OK already since what we will copy/ image is the partition of WP only & no need to do the process above Unless you want it to be more smaller •
After making sure WP7 is running plug Both SD card in the PC & run MTPW
NOTE: Target SD will be erased!
it would look something like this
You can right click the TAGRGET & delete any partitions it had
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click on the SOURCE - in my case the red (other) 2.50GB partition & choose "COPY PARTITION"
something like below will show
Now move that partition to the RIGHT most side of the partition location (target)
DO NOT RESIZE THAT RED 2.5GB PARTITION
after you hit ok/ enter it will look like this
the WP7 partition will be copied to the target SD
click APPLY & wait for about an hour or so depending on the WP7 partition size
Notice that we have 12.33GB of Unallocated space for our FAT32 & EXT4 partition
Before We continue to the Next step, place the 16gb (TARGET) in the phone to confirm that WP is working with the new card.
Now we partition the 12.33GB of Unallocated space for our FAT32 & EXT4 partition.
The below was my setting
NOTE: Don't forget to modify WP partition to PRIMARY - right click > Modify
& there we have it
4g EXT4 - 8g FAT32 - 2g WP Partition
Hope this helps & Hit thanks if it did.
It would definitely be a really nice guide, but...
When trying to dual boot WP & Android the WP partition must always be bigger than the Android partition or more than 1/2 the size of the SD card otherwise it wont work - I still don't know why
Click to expand...
Click to collapse
That's wrong. I've never had problems. Used Xboxmod's CAB on HD2O ROM to create 10GB FAT32 partition and leave ~4ish GBs for WP, then remove 1GB from FAT partition and create EXT4 from newly created free space.
Everything works perfectly. I even added SWAP not so long ago.
^
thanks for your update, then.
maybe you could share to the community on how it is done?
It's really simple and anyone who has ever seen a partition manager and knows how to press buttons.
Just get WP7 CAB Sender and appropriate CAB for partitioning (ie. EXTRAPART_10G for 10GB FAT partition) from here: http://forum.xda-developers.com/showthread.php?t=1250869
Then send it through, hard-reset WP7, take out the SD card, resize FAT partition, create EXT partition in the free space (it must be after FAT, else won't work). Install ROM of your choice. That is all.
Sorry, i searched it in xda and google but i couldn't find. What is dataonext? How can i do this?
DoubleT34 said:
Sorry, i searched it in xda and google but i couldn't find. What is dataonext? How can i do this?
Click to expand...
Click to collapse
DataonExt is basically using a partition of your sd-card( called the ext partition) to store stuff. This ext partition acts as your phone's internal memory, so when we run into low internal memory situation, after installing apps etc, dataonext usually saves the day.
You need 2 things to use this feature
A. An ext partition on your sd card
B. A script that mounts that ext partition as internal memory
A )
This can be done my using the minitool partition wizard or the CWM recovery.
In CWM menu, go to advanced>partition sd card. Select the partition size you want, keep swap to 0. Most GB roms dont need swap. And thats it, the ext partition is created
WARNING!!
Along with creating an ext partition, YOUR SD CARD WILL BE WIPED. MAKE BACKUPS
B) You need an A2SD script, Most A2SD roms already have this script so when u install the rom, after partitioning, the ext partition is automatically mounted. If you want another script, check my signature
DoubleT34 said:
Sorry, i searched it in xda and google but i couldn't find. What is dataonext? How can i do this?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This was the first thing that came up on google.
So you mean to tell me you have searched google AND xda and you couldn't find an answer? Seems legit.
You're lucky for having people like adil answering your question first.
Marvlesz said:
This was the first thing that came up on google.
So you mean to tell me you have searched google AND xda and you couldn't find an answer? Seems legit.
You're lucky for having people like adil answering your question first.
Click to expand...
Click to collapse
I found it, but isn't it about native? and native is different from nand? am i right?
adil1508 said:
DataonExt is basically using a partition of your sd-card( called the ext partition) to store stuff. This ext partition acts as your phone's internal memory, so when we run into low internal memory situation, after installing apps etc, dataonext usually saves the day.
You need 2 things to use this feature
A. An ext partition on your sd card
B. A script that mounts that ext partition as internal memory
A )
This can be done my using the minitool partition wizard or the CWM recovery.
In CWM menu, go to advanced>partition sd card. Select the partition size you want, keep swap to 0. Most GB roms dont need swap. And thats it, the ext partition is created
WARNING!!
Along with creating an ext partition, YOUR SD CARD WILL BE WIPED. MAKE BACKUPS
B) You need an A2SD script, Most A2SD roms already have this script so when u install the rom, after partitioning, the ext partition is automatically mounted. If you want another script, check my signature
Click to expand...
Click to collapse
Thanks for reply. is it ext3 or ext4 for hd2? and i will mount it "/data" or "/" or no mount? and what about cluster size? And i will use jb rom so i need swap? Thanks.
DoubleT34 said:
I found it, but isn't it about native? and native is different from nand? am i right?
Click to expand...
Click to collapse
It did not say "NativeSD", it said "Native". He is using "Native" here as an English word, not a method of booting android.
In fact, if you had clicked on that and gone further you'd have realized what I mean.
Tip: Next time when you search something, you need to go INTO the things you find, not just read their titles.
And btw, it should be ext4 and don't worry about the cluster size, default is fine.
Marvlesz said:
It did not say "NativeSD", it said "Native". He is using "Native" here as an English word, not a method of booting android.
In fact, if you had clicked on that and gone further you'd have realized what I mean.
Tip: Next time when you search something, you need to go INTO the things you find, not just read their titles.
And btw, it should be ext4 and don't worry about the cluster size, default is fine.
Click to expand...
Click to collapse
Sorry i'm from Turkey and my English is not very well. Thread wasn't basic English. So i can't understand everything everytime, it's my bad. Thanks for reply.
DoubleT34 said:
Thanks for reply. is it ext3 or ext4 for hd2? and i will mount it "/data" or "/" or no mount? and what about cluster size? And i will use jb rom so i need swap? Thanks.
Click to expand...
Click to collapse
To basically just use the ext partition as internal memory, any ext type can be used. The CWM makes a ext3. You need the ext4 partition for NativeSD roms. Thats a WHOLE different thing. And when u use a default rom with A2SD support, you dont need to mount anything, anything that needs to be mounted, IS mounted.
For swap, check the rom thread, it should be there.
Okay so I've already got a WP7.8 rom installed then reset the phone and entered magldr then split up the partitions properly to be ready for android, then just in case I created an ext4 partition (3 partitions now), butttt now suddenly my card reader won't detect the fat32 for android and in "OTHER" threads about a rom and given "SOME" directions "PEOPLE" won't answer me and just drop off the face of the earth leaving me hanging, THANKS A LOT REAL HELPFUL, so what do I do next also how do I access the ext4 partition in windows to place the recovery files...
Never successfully done this when I originally had a hd2, now that I got one again I wanna try and successfully do this, so all steps and help is appreciated, but please don't just post a link and say follow the steps, cause then I'll have to keep track of and follow 2 more threads and who said what where, so if anything post the proper steps here, that's why this thread is titled starting fresh, cause well lets see most of the tutorials are a few years old on top of it all too.
Is this correct so far? If so I can't figure out why I suddenly can't access that 12Gb fat32 partition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or this starting all over again so I have access to the fat32 partition.
the first (top) partition must be fat32
the second is ext4
the third is your wp7 partition
all set to primary
the second screen setup shows up on pc because the first partition is the only one windows can see.
the sd recovery folder is put on the fat32 partition, not the ext4 one, along with your android rom.zip
you then use magldr ad sd dir to select the recovery folder, and boot ad sd.
People have lives other than on xda, it is holiday period too.
Robbie P said:
the first (top) partition must be fat32
the second is ext4
the third is your wp7 partition
all set to primary
the second screen setup shows up on pc because the first partition is the only one windows can see.
the sd recovery folder is put on the fat32 partition, not the ext4 one, along with your android rom.zip
you then use magldr ad sd dir to select the recovery folder, and boot ad sd.
People have lives other than on xda, it is holiday period too.
Click to expand...
Click to collapse
I got a pretty successful duality going right now, AlphaLion WP7.8 and MIUI JellyBean 2.8.24 even extended data.ext4 to 1.05Gb's with Toporesizer...
Second part being what I was talking about and missing all along the simple copy, paste, set and boot type's of rom's.
n1nj4Lo said:
I got a pretty successful duality going right now, AlphaLion WP7.8 and MIUI JellyBean 2.8.24 even extended data.ext4 to 1.05Gb's with Toporesizer...
Second part being what I was talking about and missing all along the simple copy, paste, set and boot type's of rom's.
Click to expand...
Click to collapse
If you are using data.ext4, then you are using the sd build (all on fat32), therefore no need for the ext4 partition. If you have created the ext4 partition, i would suggest you install the sd recovery and flash the nativeSD rom. it is sometimes better to re-format the ext4 partition from recovery before flashing, since minitool formatting of ext4 can give problems for some people.
Basically my entire internal storage is being filled by what android is calling "System memory," which happens to be about the same size as these images from safestrap. If I mount my phone and have explorer add up the storage for internal memory it counts only 200mb but still says its nearly full (out of the 10gb available). My current theory is that these safestrap images, which appear to be the filesystem that is my internal storage are accidentally mounted in a place that android is counting towards the total amount of data. I've attached screenshots of the disk usage in the setting showing the System memory and diskusage showing the /datamedia folder where the safestrap images are mounted for some reason.
View attachment 3359022
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone know what the issue is and how to fix it? Oh and I'm running eclipse rom if that matters to anyone.
fsmv said:
Basically my entire internal storage is being filled by what android is calling "System memory," which happens to be about the same size as these images from safestrap. If I mount my phone and have explorer add up the storage for internal memory it counts only 200mb but still says its nearly full (out of the 10gb available). My current theory is that these safestrap images, which appear to be the filesystem that is my internal storage are accidentally mounted in a place that android is counting towards the total amount of data. I've attached screenshots of the disk usage in the setting showing the System memory and diskusage showing the /datamedia folder where the safestrap images are mounted for some reason.
View attachment 3359022
View attachment 3359015
View attachment 3359016
Anyone know what the issue is and how to fix it? Oh and I'm running eclipse rom if that matters to anyone.
Click to expand...
Click to collapse
How big did you make your ROM slot? You didn't leave it at the default size, did you? That would be almost 6 GB.
Tulsadiver said:
How big did you make your ROM slot? You didn't leave it at the default size, did you? That would be almost 6 GB.
Click to expand...
Click to collapse
TWRP says my rom slot partitions are the following:
System: 3gb total, 1gb free
Data: 6.3gb total, 3gb free
Cache: 300mb, 285mb free
Clearly that's what disk usage is seeing, but that shouldn't be mounted right? The internal storage should be the content of the data partition right? Or is there another partition that is the rest of internal storage after those two where my files are actually stored?
fsmv said:
TWRP says my rom slot partitions are the following:
System: 3gb total, 1gb free
Data: 6.3gb total, 3gb free
Cache: 300mb, 285mb free
Clearly that's what disk usage is seeing, but that shouldn't be mounted right? The internal storage should be the content of the data partition right? Or is there another partition that is the rest of internal storage after those two where my files are actually stored?
Click to expand...
Click to collapse
The internal storage is a total of all three. Everything is completely separate from the stock slot. This is why most people use the stock slot and don't even mess with slots. You can delete that slot and recreate it. Decrease the size of the data slot to around 1000mb to save some space.
Tulsadiver said:
The internal storage is a total of all three. Everything is completely separate from the stock slot. This is why most people use the stock slot and don't even mess with slots. You can delete that slot and recreate it. Decrease the size of the data slot to around 1000mb to save some space.
Click to expand...
Click to collapse
Yeah, I was trying to install the updated twrp to resize the slot, not remembering that I had to do safestrap and couldn't update it, and I broke the install and had to flash back to stock. I just overwrote the stock slot and everything is better now. Thanks for pointing out that this was a partition issue. There should really be something in the beginner threads that says to just use the stock slot since I see people asking the same question on tons of forums and not getting the answer.