Partioning - Samsung Galaxy S Blaze 4G

I don't no what it takes to develop a rom (I wish I did) but was thinking with cm9/ cm10 roms. Why isnt the system partioned with much less space. And if so, couldn't that extra memory be added to internal SD card(1.4gb) cm roms are like 150 MB (don't understand why was less memory than any other rom)
Anyways there's like 500+ MB in system, would just be nice to have that or some added to internal storage

trevor7428 said:
I don't no what it takes to develop a rom (I wish I did) but was thinking with cm9/ cm10 roms. Why isnt the system partioned with much less space. And if so, couldn't that extra memory be added to internal SD card(1.4gb) cm roms are like 150 MB (don't understand why was less memory than any other rom)
Anyways there's like 500+ MB in system, would just be nice to have that or some added to internal storage
Click to expand...
Click to collapse
Partitioning can be... hairy at times. I've thought about this too, but generally unless you have to, people stay away from interesting partitioning.
First, you'd need to have all the requisite partitions near each other since I imagine you'd be afraid to try and move the non-android related partitions that are meant to boot the phone. If you consider that the system, cache, and user data are all next to each other, then that might not be all that difficult.
You'd need to modify the pit (I imagine... I'm talking out of my [email protected]$ here at this point cuz I've never done this outside of a PC), and likely reflash some things (maybe the recovery would do?) with the pit involved and the repartition option. The current system partition is 575MB...
How much space is left over after an install? At best, I think you'd only get back something like 200 mb to shift to the user data, and that just doesn't feel like enough to warrant this kinda change. Especially since you wouldn't be able to just go back to a stock rom without re-partitioning.
Check out https://github.com/CyanogenMod/android_device_samsung_t769/blob/jellybean/BoardConfig.mk for the parition sizes and locations (in the comments). System and UserData are right next to each other. But the sizes aren't that compelling...

Related

getting swapfile working on /data partition

Im trying out a theory. I running JAC Hero 2.3 and wanna try running the swapfile on the /data partition. I moved app_s over to /system/sd and used swapper app to create the swapfile but android doesnt seem to use it. when i run free It says Total/used/free are all 0 but the swap file is 34 meg. I tried putting it in a sub folder and chown root.root on the folder before setting up and still no luck. Anyone have any ideas why it wont work on /data or how to get it to work on /data?
Once you run swapper go into the setting and change the location of your swap file from /sdcard/swapfile.swp to /system/sd/swap.swp ( see sxfx post[url]
you don't want to do that. Swapping involves a lot of writing and erasing, it'll wear out your internal chip and you'll start experiencing reduced capacity, write cycles for nand are even less than for flash memory!
jubeh said:
you don't want to do that. Swapping involves a lot of writing and erasing, it'll wear out your internal chip and you'll start experiencing reduced capacity, write cycles for nand are even less than for flash memory!
Click to expand...
Click to collapse
not to mention, swapon as implemented (on every build i've tried) doesn't work on a swapfile stored on a yaffs2 partition
jubeh said:
you don't want to do that. Swapping involves a lot of writing and erasing, it'll wear out your internal chip and you'll start experiencing reduced capacity, write cycles for nand are even less than for flash memory!
Click to expand...
Click to collapse
Actually /sdcard/ is your fat32 portion of your sd card, /system/sd/ is the ext2/3 of your sd card.
Also I have done a bunch of research on this write/read fiasco just because of android.
And even if you set a swap file to your SD sure it will shorten your life of the card but it will still last you at least 2 years.
I have been using USB devices on linux as swap locations forever now and I still have thumb drives that have been used and abused for months and months as a swap place and they are still pulling strong.
As for the internal chip, Im not sure what you mean by that?
Even if you could put swap on the internal flash, its not going to be faster.
Putting swap on the internal flash will make things slower as the internal flash is about 3 to 5 times slower than a class 6 sdcard.
you're comparing using a flash drive for swap in a full blown computer that probably has around 1-4gb of ram, the swap file is hardly ever touched, unless you're running a lot of applications at a time. Dream has only 90 mb available to dalvik, and rosie is a big fat... lady... plus linux/dalvik manage memory in a different way, so files are often dropped to swap and they dont stay there for long (maybe in a 256 swap, but not in a 32 mb one).
the OP also is talking about moving his swap to his internal storage (chip, nand, whatever), as he thinks it's having no effect working from the sd card. Personally, i think that both a2sd and swapper are flawed. They're overcompensating for an os that was not meant to run on that device, and the real work should be in porting (as in developing, not just file-swapping as most "devs" do here) a launcher app that we can feel comfortable with running on a stock android system with stock (or slightly improved) libraries and that we can call comparable to rosie. Just look at ahome or dxtop or openhome, they're good, solid, great looking home replacements that work as well or better than rosie, but they run out of the stock libraries. I wonder why nobody has made a free, open source home replacement app yet
jubeh said:
you're comparing using a flash drive for swap in a full blown computer that probably has around 1-4gb of ram, the swap file is hardly ever touched, unless you're running a lot of applications at a time. Dream has only 90 mb available to dalvik, and rosie is a big fat... lady... plus linux/dalvik manage memory in a different way, so files are often dropped to swap and they dont stay there for long (maybe in a 256 swap, but not in a 32 mb one).
the OP also is talking about moving his swap to his internal storage (chip, nand, whatever), as he thinks it's having no effect working from the sd card. Personally, i think that both a2sd and swapper are flawed. They're overcompensating for an os that was not meant to run on that device, and the real work should be in porting (as in developing, not just file-swapping as most "devs" do here) a launcher app that we can feel comfortable with running on a stock android system with stock (or slightly improved) libraries and that we can call comparable to rosie. Just look at ahome or dxtop or openhome, they're good, solid, great looking home replacements that work as well or better than rosie, but they run out of the stock libraries. I wonder why nobody has made a free, open source home replacement app yet
Click to expand...
Click to collapse
You make a very good point about computer having 1-4gigs of ram and not needing a swap file.
Honestly I almost never run a swap file on a computer that has more then 1gig of ram.
Plus90% of the time when I do run a swap file is when Im running a live distro of linux of a cd, but also 90% of the time I run the distro from the flash drive instead of cd cause its much faster.
So now imagine how many reads/writes I abuse that flash drive with by running a full OS on it.
Also I don't understand how a2sd or swapper is flawed? Just because they do their job? I mean it's not really our fault that they made the G1 with a little less memory spaces then we would like it to have.
But that's exactly why we have tools like swapper and a2sd. Plus no one is really forced to run these roms on the G1 phone and those of us that do realize that we have to take extra steps in creating tools to help it.
And that's not only true for the G1 but anywhere in the computer world these days.
dwang said:
Even if you could put swap on the internal flash, its not going to be faster.
Putting swap on the internal flash will make things slower as the internal flash is about 3 to 5 times slower than a class 6 sdcard.
Click to expand...
Click to collapse
I'd like to spread swap over the sd and internal storage if possible -- should make paging a lot less evident if priorities are set up properly.
dwang said:
Even if you could put swap on the internal flash, its not going to be faster.
Putting swap on the internal flash will make things slower as the internal flash is about 3 to 5 times slower than a class 6 sdcard.
Click to expand...
Click to collapse
internal memory is faster. class 6 guarantees 6mbs read/write times but doesnt mean the bus can support those times. if you run a test copying something to /system/sd and to /data you will see /data is faster. as for those saying it will degrade the internal memory, that is not the case being the flash memory inside is designed to have much much much more read/write cycles. Think about it in a stock G1, this is where dalvik-cache is writen to as well as email, sms, user settings, cache for browser and uTube. Do not confuse internal flash memory to sd card flash memory
Are you sure about that? This guy has some test results and it indicates that a class 6 sdcard is much faster than the internal flash.
http://forum.xda-developers.com/showpost.php?p=4059520&postcount=15
MonkySlap said:
internal memory is faster. class 6 guarantees 6mbs read/write times but doesnt mean the bus can support those times. if you run a test copying something to /system/sd and to /data you will see /data is faster. as for those saying it will degrade the internal memory, that is not the case being the flash memory inside is designed to have much much much more read/write cycles. Think about it in a stock G1, this is where dalvik-cache is writen to as well as email, sms, user settings, cache for browser and uTube. Do not confuse internal flash memory to sd card flash memory
Click to expand...
Click to collapse
dwang said:
Are you sure about that? This guy has some test results and it indicates that a class 6 sdcard is much faster than the internal flash.
http://forum.xda-developers.com/showpost.php?p=4059520&postcount=15
Click to expand...
Click to collapse
That's interesting. Going to have to try that test out. I just noticed when xfering stuff to /data it was faster then to /system/sd. If it is then touche my friend.....touche

[Q] Will future versions of the Android OS fix this blasted "out of space" problem?

[Q] Will future versions of the Android OS fix this blasted "out of space" problem?
So I have been an avid fan of Google for many, many years. I was looking forward to the Google phone before any Android details came out. So I naturally jumped at the chance to own one. But lately, I'm starting to have a change of heart. These constant out of space warnings are really getting annoying.
So much in fact, I don't know that I want my next phone to be an Android device sadly. I really want to want another one. But this experience is starting to sour my taste for them.
I currently run a rooted (virtuous) Dinc. I have gotten the out of space notification many, many times. I have now started to get it again after installing the Google Music app after being invited into the beta. I have removed about 15 programs, but I still only have about 17MB free on that stupid 149MB partition!
This is beyond annoying. If the phone has something like 8GB of internal memory, why can't I use it? Why can't the apps install there? Why limit this massive amount of storage to a measly 150MB? What year is this, 1995?
I know I'm preaching to the choir here, but I am fed up. I don't know what else to do here and I'm ready to walk away. Someone please tell me that Google has saw the light and is going to fix this glaring bug of theirs in Gingerbread or Ice Cream Sandwich!
Why did you create a partition so small? You should create a larger partition to prevent these notifications so often since you'll have more space and use up the extra space not being used. Also, it's not the Android OS's fault that your phone has a small partition made. Since the partition is so small, and you have hardly any memory left (17mb) then it's just one of the phone's functions to notify you about this which should be a good thing to let you know.
theonew said:
Why did you create a partition so small? You should create a larger partition to prevent these notifications so often since you'll have more space and use up the extra space not being used. Also, it's not the Android OS's fault that your phone has a small partition made. Since the partition is so small, and you have hardly any memory left (17mb) then it's just one of the phone's functions to notify you about this which should be a good thing to let you know.
Click to expand...
Click to collapse
Umm...I didn't make the partition...Android did. Trust me, if it were my choice it would be bigger!
ned4spd8874 said:
Umm...I didn't make the partition...Android did. Trust me, if it were my choice it would be bigger!
Click to expand...
Click to collapse
Android doesn't just make partitions by itself. Maybe the rom you have did that. try getting a new rom because this is not normal.
theonew said:
Android doesn't just make partitions by itself. Maybe the rom you have did that. try getting a new rom because this is not normal.
Click to expand...
Click to collapse
Wrong. At least on the HTC Droid Incredible, ROM's have a standard 150 megabyte \data\data partition. For either odexed or deodexed ROM's space is taken in that partition by pretty much every installed application. I've seen contacts hog nearly 70 megabytes of that partition for some handsets, and Sense takes a lot of it, too. Odexed ROM's allegedly require less of the space.
I've run several Froyo ROM's and they all have that limitation. I cannot speak for AOSP ROM's, only Sense ROM's.
There is an app which I have used (but don't seem to be able to find in the Market any more, and the dev isn't responding to PM's here at xda, but I digress) called NotEnoughSpace which allows some portions of the contents to be shifted elsewhere. I found it was very helpful when I was on Froyo, but it does not appear to work on GingerSense. On the other hand, the partition appears to be bigger in GingerSense. The flip side is that the GingerSense ROM's are so fat, there's less RAM available for applications to run.
Pick your poison. I agree it's a stupid limitation that somebody should figure out a way to fix.
hgoldner said:
Wrong. At least on the HTC Droid Incredible, ROM's have a standard 150 megabyte \data\data partition. For either odexed or deodexed ROM's space is taken in that partition by pretty much every installed application. I've seen contacts hog nearly 70 megabytes of that partition for some handsets, and Sense takes a lot of it, too. Odexed ROM's allegedly require less of the space.
I've run several Froyo ROM's and they all have that limitation. I cannot speak for AOSP ROM's, only Sense ROM's.
There is an app which I have used (but don't seem to be able to find in the Market any more, and the dev isn't responding to PM's here at xda, but I digress) called NotEnoughSpace which allows some portions of the contents to be shifted elsewhere. I found it was very helpful when I was on Froyo, but it does not appear to work on GingerSense. On the other hand, the partition appears to be bigger in GingerSense. The flip side is that the GingerSense ROM's are so fat, there's less RAM available for applications to run.
Pick your poison. I agree it's a stupid limitation that somebody should figure out a way to fix.
Click to expand...
Click to collapse
Yes, thanks for explaining that much better than I could!
I do have NotEnoughSpace and don't use it for that purpose anymore. I just use it to see how much space I have available and to clean up the dalvik cache. When I was using it to get more space, my apps kept disappearing on me and I would have to re-install them constantly!
is this just a droid problem? i have an epic 4g and it allows me to use the entire 485mb for app storage. what about an apps to sd option? i know at least half of my apps have the option of being stored on the sd card. just wondering.
darksideauto said:
is this just a droid problem? i have an epic 4g and it allows me to use the entire 485mb for app storage. what about an apps to sd option? i know at least half of my apps have the option of being stored on the sd card. just wondering.
Click to expand...
Click to collapse
Every app that can be moved to the SD is. But I still have only 17MB available.
ned4spd8874 said:
Every app that can be moved to the SD is. But I still have only 17MB available.
Click to expand...
Click to collapse
This does not make any sense. If an app is moved to the SD Card, the space it took up on the device (some if not all) should be gained back since it's not there any longer. Whenever I move an app to the SD Card, I get back my space. There really must be something wrong with your rom/phone.
You sir have alot of apps then.
Sent from my SPH-D700 using XDA App
The small internal Storage is a massive problem. I agree to you.
But I know there are several ways to fix this. What I don't know is how...
There are several ROMs who support different kinds of app2sd scripts so you get more 'virtual' internal storage on the sd card.
As you can see on the pictures attached i have approx. 550 mb free internal storage but more than 40 apps that could be pushed to sd.
To get this it is necessary to re-partition your sd-card and install the correct scripts.
Unfortunately, as i said, i'm not able to tell you exactly how to get this work. I just followed a step-by-step guide somwhere in this forum.
The ROM i use, uses D2SD automatically, if the SD-card is partitioned the right way.
I'm sure you will find something that fits to the ROM you use.
darksideauto said:
You sir have alot of apps then.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have 75 non-standard/included apps. I've read where other people have hundreds!
pistolero0 said:
The small internal Storage is a massive problem. I agree to you.
But I know there are several ways to fix this. What I don't know is how...
There are several ROMs who support different kinds of app2sd scripts so you get more 'virtual' internal storage on the sd card.
As you can see on the pictures attached i have approx. 550 mb free internal storage but more than 40 apps that could be pushed to sd.
To get this it is necessary to re-partition your sd-card and install the correct scripts.
Unfortunately, as i said, i'm not able to tell you exactly how to get this work. I just followed a step-by-step guide somwhere in this forum.
The ROM i use, uses D2SD automatically, if the SD-card is partitioned the right way.
I'm sure you will find something that fits to the ROM you use.
Click to expand...
Click to collapse
I've used the app2sd and notenoughspace programs in the past, but it seems they have done more harm than good. Apps would stop working. They would disappear completely. The system would crash, etc. I kinda gave up hope on using those approaches.
I was hoping the Google Android team would wake up and just fix this instead of us paying users have to perform work-arounds just to use our devices.
ned4spd8874 said:
I've used the app2sd and notenoughspace programs in the past, but it seems they have done more harm than good. Apps would stop working. They would disappear completely. The system would crash, etc. I kinda gave up hope on using those approaches.
I was hoping the Google Android team would wake up and just fix this instead of us paying users have to perform work-arounds just to use our devices.
Click to expand...
Click to collapse
Then you are pretty unlucky. I never had problems with this stuff. All works just fine as it should.
But, of course you are right, i can't understand why they don't give us a GB or so as internal storage either.
Damn scrooges.
ned4spd8874 said:
I've used the app2sd and notenoughspace programs in the past, but it seems they have done more harm than good. Apps would stop working. They would disappear completely. The system would crash, etc. I kinda gave up hope on using those approaches.
I was hoping the Google Android team would wake up and just fix this instead of us paying users have to perform work-arounds just to use our devices.
Click to expand...
Click to collapse
Try using a cleaner ROM for your DInc (ie "stock Android"- no Sense UI). I just got a DInc yesterday, switching from an Aria. Did a factory wipe, rooted, and installed the CM7 nightly 100. I believe I currently have s2e on my 8gb MicroSD (just swapped it from my Aria, which had s2e and CM7). Anyway, I have 118MB used, 630MB free internal storage space for apps. This clearly isn't a Google/Android problem. Could be an HTC Sense problem, I suppose.
edit: My Aria even has 185MB available for apps. Not a huge amount, but considering it has a lot less internal space than a DInc, yeah, OP something is wrong.

[Q] Storage? Storage!

OK, I am having storage/space issues with my Blaze that are making the cameras inoperable (I keep getting a message stating there's a lack of memory or space on the SD card). I am running CM10 Stable on Android 4.1.2 with the CM kernel.
When I go into Settings and look at the Storage, here's what it says (I tried taking Screenshots but they didn't work):
Total Space= 1.12GB
814MB of Apps
252MB Available
Internal Storage= 1.4GB
208MB Apps
553MB Pics/Videos
4.78MB Downloads
SD Card= 3.69MB Total Space
1.99GB Available
Here's the thing: I have NO pics/videos, yet somehow 553 MB are being used for this. So what's the deal? Can someone give me the quickie/noob explanation? Or at least explain what's the best way to control your storage on the Blaze (and yes, I've used Search but haven't really found what I was looking for)? I would really appreciate it, this is a very annoying and frustrating issue.
Thanks!
Vinotas said:
OK, I am having storage/space issues with my Blaze that are making the cameras inoperable (I keep getting a message stating there's a lack of memory or space on the SD card). I am running CM10 Stable on Android 4.1.2 with the CM kernel.
When I go into Settings and look at the Storage, here's what it says (I tried taking Screenshots but they didn't work):
Total Space= 1.12GB
814MB of Apps
252MB Available
Internal Storage= 1.4GB
208MB Apps
553MB Pics/Videos
4.78MB Downloads
SD Card= 3.69MB Total Space
1.99GB Available
Here's the thing: I have NO pics/videos, yet somehow 553 MB are being used for this. So what's the deal? Can someone give me the quickie/noob explanation? Or at least explain what's the best way to control your storage on the Blaze (and yes, I've used Search but haven't really found what I was looking for)? I would really appreciate it, this is a very annoying and frustrating issue.
Thanks!
Click to expand...
Click to collapse
i think you never cleaned up ur cache and over time lots of crap got accumulated hogging up all your space...also u need to look into your thumbnails as they tend to stay over time even if you move the actual photo...all you need to do is to backup your apps and their data n then boot in recovery mode and do a factory reset and then boot and go to any file manager and move whatever pics and vids you have on internal storage(by change if u have any) to external storage and delete the DCIM folder then...if even that doesnot let you do anything i think you are in need to format your system, cache, data and dalvik and flash the rom u use fresh and start over...you will be good as new then for sure even if it takes lil more time to set up things as u want again but thats better than being frustated and not able to do anything...hope that helps you
Check the ".thumbnails" directory under DCIM (or camera, I forget). My daughter's blaze seems to like accumulating 100+MB files I'm there.
Definitely check app cache too. The Cheeseburger Network app was pulling 500MB of cache on my S2.
Sent from my Nexus 7 using Tapatalk
I was traveling but I read your recommendations and deleted a ton of files under DCIM folder. That seems to have fixed the issue for now, thanks so much. But I do need to re-flash the ROM anyway due to another issue so that will help.
Thanks! :good:

Would this trick work on a OnePlus...?

Relocate the Dalvik Cache
http://www.xda-developers.com/android/relocate-dalvik-cache-free-space-moto-g/
?
Why would you even want to do this with 64 GB of storage?
Silverquark said:
Why would you even want to do this with 64 GB of storage?
Click to expand...
Click to collapse
space. I can store a lotta notes/docs in 600 MB. My music and pics take up a good portion! Lots of music.
So I am wondering of this can be done.
It should work theoretically, but only if you are not using ART Runtime of course. Also maybe the cache partition has a different size on the oneplus, not sure about that. So if you really want to, make a nandroid backup and just try it
Edit: Dont do it. Cache partition size is 503 mb. at least for me it is. So you could relocate all your cache to there, but if you have too many apps or get to many apps after youve done this (happens very fast on a 64gb phone) you're screwed because theres no space left. Just try to check the size of your /data/dalvik-cache directory and you will see
Why would 600MB matter on a phone of 64GB, im sure you dont have your internal memory filled up yet.
The article is about the moto G having that partition, no idea if the one has that same partition aswell.

Rooted phone: requesting info re: ext partition size, type of ext, and others

Hi:
I am a newbie, but I've learned a lot about things using this site and others. Thank you!
I have a rooted LG Volt, which of course has the odious KitKat restrictions on putting apps on SD cards. I've read about mini-tools and have Link2SD (premium, so I can link everything to the SD), but haven't tried it out yet because I wanted to ask some questions first. For reference, I have a 16g (class?) 10 SD card, which I've verified is legit using an app (forgot name).
1) Is there a maximum size for the second (ext) partition? I've read 2g, but other sites have said that there are now no restrictions. 2g is quite small for me since the Volt has very little internal memory, and I download a ton of apps; I don't use as much data. Ideally, I'd like to go half and half (approx. 8/8g data/app partition).
2) If it is limited to 2g, is there any workaround that doesn't require a ton of knowledge? I read something about changing system apps to user apps, but would this work--and is there a noob-friendly walk through?
3) Is there a preferred ext partition type? Again, I've read varied opinions; most say that ext2 is optimal, but others say ext4 might work better with Link2SD.
4) Is there any advantage to using a swap file? Again, varied opinions, but it seems mostly beneficial in terms of speed, and not to a degree that it matters.
I have other questions regarding partition alignment (found a calculator, so I think I can figure out how to optimize the partitions) and will probably have more in the future, but I would really love answers (or else links to answers) about these issues.
Thanks in advance!
anoukaimee said:
Hi:
I am a newbie, but I've learned a lot about things using this site and others. Thank you!
I have a rooted LG Volt, which of course has the odious KitKat restrictions on putting apps on SD cards. I've read about mini-tools and have Link2SD (premium, so I can link everything to the SD), but haven't tried it out yet because I wanted to ask some questions first. For reference, I have a 16g (class?) 10 SD card, which I've verified is legit using an app (forgot name).
1) Is there a maximum size for the second (ext) partition? I've read 2g, but other sites have said that there are now no restrictions. 2g is quite small for me since the Volt has very little internal memory, and I download a ton of apps; I don't use as much data. Ideally, I'd like to go half and half (approx. 8/8g data/app partition).
2) If it is limited to 2g, is there any workaround that doesn't require a ton of knowledge? I read something about changing system apps to user apps, but would this work--and is there a noob-friendly walk through?
3) Is there a preferred ext partition type? Again, I've read varied opinions; most say that ext2 is optimal, but others say ext4 might work better with Link2SD.
4) Is there any advantage to using a swap file? Again, varied opinions, but it seems mostly beneficial in terms of speed, and not to a degree that it matters.
I have other questions regarding partition alignment (found a calculator, so I think I can figure out how to optimize the partitions) and will probably have more in the future, but I would really love answers (or else links to answers) about these issues.
Thanks in advance!
Click to expand...
Click to collapse
First of all, you haven't told us what are you trying to do. If you are just trying to get a few questions anwsered just say so.
From what I see you are trying to use Link2SD because of the kitkat sd card restriction?
Note: Apps can't detect if an SD card is fake. It will just test how fast it is and guess if it's fast engough for it's class
You can remove the KitKat SD restriction with this app: SDFix
1) Yes, there is a restriction but it depends on how it's formated: on ext2 and 3 the limit is 35184 GB on a single partition and ext4 has a max limit of 1152921500 GB.
2) It's not limited to 2GB. Changing system apps to user and user to system is useless and should not be done if you don't know what exactly and why you are doing it. Don't let root fool you. Deleting system apps will NOT give you more free space for all the games.
3) Depends on support. If your phone supports ext4 (and it does) use that if not use lower such as ext3 then 2 and so on.
4) Look at this as a glass and some water. Water is memory to be put in ram and the glass is the ram your phone has.
The more water you put in it, the less space there is. And when it's full it will overflow, and your phone will freeze or reboot.
What swap does is when the water overflows in the glass (the ram gets full), the water (memory) that overflows goes to a swap file instead of it just getting lost and the phone getting frozen.
But remember, any SD card is MUCH SLOWER that RAM and using swap will not give any preformacne improvments.
The swap sould be factory set anyways and it also uses a lot of storage.
You REALLY shouldn't mess with the partitions.
You could break your phone forever.
What I recommend using is FolderMount and GL2SD. FolderMount is exactly like Link2SD, but you don't need to do any fancy partitioning. And GL2SD works great too, the only downside is that you have to run the apps (you moved to SD) from within the app.
Thank you!
Wonderful, clear answers! Yes, just trying to figure out "what to do" so I can add more apps to the Volt in the easiest manner possible. Apologize for not being clearer about that.
Just some follow-up questions:
1) will the app cited above (nextapp) allow me to move apps to the sd, or just data? Never having had an android other than this one with the dread KitKat, I don't know how it typically works after a KitKat fix. So should I format the entire sd card as FAT32 or ext4 (is the latter even possible)? And where will the data that I do have be saved if I don't partition the card? All on the one partition?
2. RE: FolderMount and GL2SD: that sounds great. The one concern that I have is that Link2SD's support (I THINK that's where I found this) said that the problem with putting an app on an sd card versus linking it is that if you take the sd card out, all of the apps will be gone. Is that just incorrect?
Thanks again! Very helpful.

Categories

Resources