Related
Hi,
I would like to know how to configure it.
I have in my SD:
1024M for swap
1500M for ext2
5000M for Fat32
Sent from my HTC Desire using XDA App
Swap? On a Desire? Don't think you need that, there's plenty of RAM.
So you need to partition your SD card, 512 mB ext3 should be plenty, the rest can be FAT32.
FAT partition must come first.
ok, thank you.
And now how can I enable the A2SD apps ?
raffarein said:
ok, thank you.
And now how can I enable the A2SD apps ?
Click to expand...
Click to collapse
Once you have Apps2SD installed and your SD card partitoned correctly, all there is to do is just install your apps and they will be installed to your ext2 partition on your SD card. Use the Quick System Info app from the Marketplace, or see my thread to check if it is working correctly:
http://forum.xda-developers.com/showthread.php?t=677073
raffarein said:
Hi,
I would like to know how to configure it.
I have in my SD:
1024M for swap
1500M for ext2
5000M for Fat32
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Way too much swap!! For Desire best is 0 for swap, 512mb for Ext2 and rest for Fat32
is it possible to partition the SD card "outside" the phone?
I got a new SD card I want to use, and the old one is running as ext partition, and the phone spasses out if i swap the 2 cards? so how can I make the external partition so I can install on the new one?
Yes, you could try partitioning by accessing Recovery Mode via your PC while having your phone connected with the USB cable. Use the relevant push files (available for download in my sig from the Nimbu guide) to access Recovery Mode, then you will see an option to partition your SD card. You can set the swap, ext2, and FAT32 space of your SD card and convert it from ext2 to ext3.
As advised above, set your swap to 0 MB, ext2 between 512 MB - 1024 MB (max), and rest of space allocated to the FAT32 partition.
Remember to backup your SD card contents beforehand otherwise you will lose everything through partitioning.
Sent from my HTC Desire using XDA App
I'm on r3.1 rom with A2SD+, I'm really pleased with it but I plan to switch to some Froyo rom once htc releases it (with A2SD+ if possible).
What is the proper way to prepare sd card for change of rom ( now I have sd card with standard settings: swap 0 ext2 512 mb fat32 rest).
Do I need to format it again?
The thing that I need to switch between goldcard and my everyday card during the process makes it difficult enough
djoni1980 said:
The thing that I need to switch between goldcard and my everyday card during the process makes it difficult enough
Click to expand...
Click to collapse
On the same topic: Is it possible to partition your SD card first and then make it a goldcard so we don't have to switch between cards during rooting and flashing? Thanks..
djoni1980 said:
I'm on r3.1 rom with A2SD+, I'm really pleased with it but I plan to switch to some Froyo rom once htc releases it (with A2SD+ if possible).
What is the proper way to prepare sd card for change of rom ( now I have sd card with standard settings: swap 0 ext2 512 mb fat32 rest).
Do I need to format it again?
The thing that I need to switch between goldcard and my everyday card during the process makes it difficult enough
Click to expand...
Click to collapse
With DJ Droid's v1.0 R1 BETA rom (Sense with Froyo), it allows you to partition your SD card the exact same way you had done with the r3.1 rom. I have mine setup with a 0MB swap, ext2 size of 512 MB, and rest to FAT32 partition. To install this rom, it is advised to format your SD card again to get rid of any niggling bugs.
AFAIK, all other Froyo roms (ones without Sense) require you to prepare the SD card differently and not have your SD card partitioned, you need to push via ADB to install your apps to the SD card.
manisa236 said:
On the same topic: Is it possible to partition your SD card first and then make it a goldcard so we don't have to switch between cards during rooting and flashing? Thanks..
Click to expand...
Click to collapse
This will not be possible as you need to use the Gold Card to unlock your phone's CID if your phone is network branded. After that, you can root and then flash a rom, and then partition your sd card afterwards.
Thanks for the answers massdroid, you are the most helpful member around
djoni1980 said:
Thanks for the answers massdroid, you are the most helpful member around
Click to expand...
Click to collapse
Thank you buddy. I appreciate your kind words
what are the benifets of app2sd???
The title says it all, I was wondering what are the benefits of storing and running your apps from the sd card other then the obviously being able to install more apps then can be stored on the phones internal memory?
Secondly what is the purpose of zipalign? At a very simplistic level I guess it has something to do with optimizing the apk though I am not really sure what this means.
Even with my Sprint CDMA Hero overclocked to 652 (min) & 710 (max) I still find the keyboard to be a bit laggy, will enabling the above help with this at all?
Yep, by installing apps and their associated cache to your SD, it saves you from having to install them directly to internal memory, which would affect the performance of your phone with the more apps you install. With A2SD installed, you basically save storage space and allows your device to run faster.
Also, consider installing a cache cleaner app to free up more space.
Zipalign makes interacting with apps more efficient after they are optimised making them run faster with the Android OS.
Sent from my HTC Desire using XDA App
where do performance improvements come from?
MasDroid said:
Yep, by installing apps and their associated cache to your SD, it saves you from having to install them directly to internal memory, which would affect the performance of your phone with the more apps you install. With A2SD installed, you basically save storage space and allows your device to run faster.
Also, consider installing a cache cleaner app to free up more space.
Zipalign makes interacting with apps more efficient after they are optimised making them run faster with the Android OS.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I have seen the benchmark tests showing the speed improvements but I don't really see how changing the location of where the apps are installed to would necessarily improve the performance of their execution, I mean the phone's internal storage is separate from the phone's internal ram. Are there fragmentation issues or something when it comes to running the apps from the smaller internal storage vs the larger external storage of the sd card?
I think this question was asked previously but I didn't see an answer for it; when app2sd is set up, when you start installing new apps do they automatically get zipaligned and then installed to the sd card or do you have to do it manually?
Hmm.... i think you have a point there and i agree with what you are saying. With A2SD, i don't think it improves performance since it's ROM space, not RAM, that these apps are occupying. The main advantage of A2SD is having more dedicated space for storage of apps.
Since the 1.6 SDK was released, i think the ADT does this automatically on APK export. Therefore any app which has been updated since ~September (and was developed using the ADT Eclipse plugin) will be zipalign'd.
You can also do this manually, see this link:
http://android-developers.blogspot.com/2009/09/zipalign-easy-optimization.html
Sent from my HTC Desire using XDA App
work in progress...
Prerequisite:
- Get a SanDisk 64GB microSDXC details here http://forum.xda-developers.com/showthread.php?t=1343164
- Root your phone
- Install Link2SD
you can get Link2SD from our in house local developer http://forum.xda-developers.com/showthread.php?t=919326
all Link2SD related bugs or problems should be reported there
you can also get Link2SD directly from the Android Market
Link2SD
Bulent Akpinar
https://market.android.com/details?id=com.buak.Link2SD&hl=en
step 1:
prepare your spanking brand new SanDisk 64GB microSDXC,
you can partition it any way you want, i choose to go 50%&50% as i know i'm will be installing a lot of Apps/Games and i know i've maxed out 16GB easily everytime, that's why i'll need at least 32GB to be comfortable (later on you'll know why) in the new sd card
the best tool to partition your new 64GB SD is Gparted (yes Linux), you can get Gparted in a lot of ways, most times included in any Desktop Linux installation, or you can get the Gparted LiveCD from http://gparted.sourceforge.net/livecd.php
you'll need to create 2x primary partitions, the first partition must be FAT32 (is not really a must, but you'll need that if you want to be able to see your SD card space when mounted as USB storage), the second partition it's highly recommended to use ext4, as Gparted seems to have problem trying to format ext3 on the SanDisk 64GB microSDXC, older phones can use ext2 if the phones are missing the support for ext4 (example Milestone XT720)
if you are not comfortable with Linux, you can easily create 2x FAT32 partitions in your SD card using Disk Management in windows, just make sure both partitions are Primary partitions.
{
"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"
}
step 2:
once you're done with the disk partitioning and formatting of your brand new SanDisk 64GB microSDXC; it's time to finally launch Link2SD to do its magic
as soon as you run Link2SD you'll be greeted with this screen asking you to choose the disk format of your SD card 2nd partition, which is what we did on step 1
if you formatted your 2nd partition as ext4 then you must choose ext4
if you formatted your 2nd partition as FAT32 then you choose FAT32
step 3:
reboot your phone, when Link2SD prompts you to do so,
you must reboot for the changes to take effect
step 4:
when the phone is back from reboot (should not take more than 30 sec)
run Link2SD again, hit the Menu capacitive button, and select Storage Info then you should see this screen confirming everything was a success!
step 5:
now you can start moving apps 2 sd, which in Link2SD term is known as "Create Link" (it actually does way more than just create links)
this is what you'll see...
anything that says on SD Card are created by the build in AOS App2SD "Move to SD card" feature that was available since Froyo 2.2
anything that says Linked -> SD Card are created by Link2SD after you hit the "Create Link" option button
... an unrelated screen-shoot of the phone memory performance
Benefits:
- Apps on SD remains accessible even when the SD is mounted as USB flash drive
- Apps moved to SD will act & behave as if they were installed in the internal memory
- Apps that are not natively Apps2SD compatible can still be moved to SD without breaking it
- Apps compatible
- Games compatible
- Widgets compatible
- you can now go beyond the 1GB~2GB limit of the reserved internal memory space
- you can better and easily manage apps to go between internal, external (/sdcard/external_sd/), SD (/sdcard/), and Link2SD (hidden ext4)
- if you are familiar with CM7, with Link2SD you can also set the default install path to be internal, external or auto
- you can easily keep separate SD cards with different apps / games, specially those you want to Hide from public (family) & friends access
Cons:
- none?
- if you take out the SD card, any Apps & Widget that ran directly from the SD card will be temporally unavailable until you put the SD card back in
Tips & Tricks
Gameloft games
There are 3 types of GL games:
- Older GL games will install all into the internal memory, those are easy to deal with with Link2SD
- Recent GL games that are Froyo App2SD aware, will install a small portion in either internal or to SD, but all the extra "DATA" contents usually in the size of 600+ MB are left on SD card (these are not handled by Link2SD), the work around is simple use a Mount script and forward all the
/sdcard/gameloft/ to /sdcard/external_sd/gameloft/
- The a few more recent kind of GL games will let you select where to store the "DATA" chunk to either internal or external sd, for these types you'll choose internal, then Link2SD will do the rest
Some of you have requested this script i'm using
Code:
mount -o -bind /sdcard/external_sd/gameloft/ /sdcard/gameloft/
mount -o -bind /sdcard/external_sd/ea/ /sdcard/ea/
mount -o -bind /sdcard/external_sd/glu/ /sdcard/glu/
mount -o -bind /sdcard/external_sd/download/ /sdcard/download/
mount -o -bind /sdcard/external_sd/DCIM/ /sdcard/DCIM/
you can even include more stuff there, just be careful with what you add, to not break your OS
for example you can technically also throw in /sdcard/Android/data/ ... but some apps are required during boot, and it might not work if you have it on the /external_SD so the safe way would be to only add the specific apps you know are not required during boot time, like all the games and stuff like that.
thanks for your efforts.
i have some questions:
have you felt any lag between having all apps stored on internal storage, and apps stored on sd ext?
do you feel a difference in preformance based on how many applications have downloaded?
i ask because i used to do this for my g1 back in the days, and the phone was just so slow twards the end of it's life, that i would feel a lag when using apps 2 SD, or maybe it was a placebo, or maybe the phone was just incompetent, does it matter with this much power in our hands?
also while we're on the subject of memory, has any one ever elaborated on the process by which apps are killed to free up ram in the phone, i'm not an expert so i wouldn't know what it's called, but i heard that our ram is so high, and the memory killer kills the apps way too early, causing unnecessary apps to be killed when we could have them just chilling in the ram waiting to be re-opened.
I know exactly what you mean, and I'm happy to report there's no lag whatsoever with this phone.
I have done it before on my older phones and yes indeed there's that 1 or 2 sec loading lag, but none at all in the T989, I'll attribute that to either the Dual Core CPU or the super fast SD card reader, or perhaps a combination of both.
back then on my other phones using a class 6 as well it was still not fast enough, a class 4 was obviously even longer at loading, and a class 2 was pretty much pointless to do APPS2SD
But in this phone even a class 4 is not bad, barely noticeable
so definitely get a class 6 or class 10 SD card for this sort of operations
Sent from my SGH-T989 using xda premium
@allgamer
Why do you need to create two partitions for this?
jeffpzy said:
@allgamer
Why do you need to create two partitions for this?
Click to expand...
Click to collapse
it's a requirement for the Link2SD App
post #3 updated http://forum.xda-developers.com/showpost.php?p=19779495&postcount=3
Ooo I want one!!!!!!!!
Current-*Samsung Galaxy S2 (Gingersnap v1.1)*|*Htc Sensation (rooted w/ XE Dr. Dre Beats Technology)*|*Samsung Galaxy S Vibrant (rooted w/ cm7)*|*Mytouch 4g (stock)*|*Mytouch Slide (stock)*|*Htc G1 (stock)
"you can easily create 2x FAT32 partitions in your SD card using Disk Management in windows, just make sure both partitions are Primary partitions"
Is there a tutorial for this. Thanks
Windows Easy button
dddsj said:
Is there a tutorial for this. Thanks
Click to expand...
Click to collapse
Try this tool. It's super quick and easy, and if you're stuck using Windows then it's about as good as it'll get for ya. Super easy and straight-forward, but in case you're worried (whatever you do don't format the one that is called "C:", lol ) the site has tons of info on how to use it and whatnot. I've been in IT for some time now and whenever someone asks me about partitioning in Windows, this is always where I send 'em for the "do it yourself" easy button.
Here's the program I'm talking about:
http://www.partitionwizard.com
Hope this helps, and good luck!
problems installing/moving apps to sd
Hey guys i have been unable to move/install apps to my sd card ever since changing to MIUI I'm not sure whether this is a problem with the ROM or not (i think i may have insalled applications to SD on a previous GB version of MIUI)
I am using a rooted Samsung Galaxy S2 I9100 with the latest MIUI based on 4.0.4. before MIUI i was on CM7 stable and i remember messing around with some settings there to try and get my phone to read music off the sd card as well as internal memory-(where all my downloaded music was going). I also may have done a dodgy partition on my old 32gb micro sd or some how partitioned my internal storage of my phone...
I have recently partitioned my 64gb micro sdXC to this tutorial successfully...
http://forum.xda-developers.com/showthread.php?t=1343187
when i go to move a 'moveable' app eg. Paypal through 'Link2Sd' it comes up with an error saying "pkg:/data/app/com.paypal.android.p2pmobile-1.apk Failure [INSTALL_FAILED_CONTAINER_ERROR]
when i go to move a 'moveable' app through 'App 2 SD Pro' it says 'couldn't move app'
the following are my phones storage details...please point out if you think there is anything strange about them
this last picture was taken before i partitioned my SD
if you guys have an suggestions please let me know
Good info
TylerMF said:
Try this tool. It's super quick and easy, and if you're stuck using Windows then it's about as good as it'll get for ya. Super easy and straight-forward, but in case you're worried (whatever you do don't format the one that is called "C:", lol ) the site has tons of info on how to use it and whatnot. I've been in IT for some time now and whenever someone asks me about partitioning in Windows, this is always where I send 'em for the "do it yourself" easy button.
Here's the program I'm talking about:
http://www.partitionwizard.com
Hope this helps, and good luck!
Click to expand...
Click to collapse
Good info but as you know nobody is stuck on windows... Linux is free software and its a good practice to partition your Pc and install Linux next to windows, dual boot...
Whatever I try, may phone always says the SD card is damaged.
I exactly followed the steps of this how to, only possible explanation for me is that its not working to use the phone itsself as the cardreader for the partition process.
*edit*
After getting an external SD Card reader it worked like a charm.
So I can just recommend what most people recommend: do not use your phone as SDcard reader for partitioning.
As you mention that partition can be as I like. you choose 50/50 which less then 32G which supported for FAT partition.. Can it work if I want 80/20. Example, having 50G with FAT and another 14 as EXT. because the FAT only support up to 32G. I don't have the card now. Just want to confirm before buying it. Thanks.
This is very helpful! A recent purchaser of the 64 gb class 10. :laugh:
How To ?
AllGamer said:
Gameloft games
There are 3 types of GL games:
- Older GL games will install all into the internal memory, those are easy to deal with with Link2SD
- Recent GL games that are Froyo App2SD aware, will install a small portion in either internal or to SD, but all the extra "DATA" contents usually in the size of 600+ MB are left on SD card (these are not handled by Link2SD), the work around is simple use a Mount script and forward all the
/sdcard/gameloft/ to /sdcard/external_sd/gameloft/
- The a few more recent kind of GL games will let you select where to store the "DATA" chunk to either internal or external sd, for these types you'll choose internal, then Link2SD will do the rest
Some of you have requested this script i'm using
Code:
mount -o -bind /sdcard/external_sd/gameloft/ /sdcard/gameloft/
mount -o -bind /sdcard/external_sd/ea/ /sdcard/ea/
mount -o -bind /sdcard/external_sd/glu/ /sdcard/glu/
mount -o -bind /sdcard/external_sd/download/ /sdcard/download/
mount -o -bind /sdcard/external_sd/DCIM/ /sdcard/DCIM/
you can even include more stuff there, just be careful with what you add, to not break your OS
for example you can technically also throw in /sdcard/Android/data/ ... but some apps are required during boot, and it might not work if you have it on the /external_SD so the safe way would be to only add the specific apps you know are not required during boot time, like all the games and stuff like that.
Click to expand...
Click to collapse
Sorry for taking so long to reply, but I'm intrigued how this method works and if possible would love some further help here
I use LINK2SD, and pretty much link all my games, have noticed that the internal memory used increases even when I link to the sd card, so there does indeed appear to be a portion of the game data going to internal ...
Is there an app or a function in LINK2SD to simplify & automate this process to ensure that ALL data links to the SD card ...
I'm not too familiar with the mount option or how to do it ...
Any advice would be most appreciated, thanks
In older versions of Android the external SD would be mounted as /mnt/sdcard but now that is used for the internal memory and the external SD is now /mnt/sdcard/external_sd. This is a bit of a problem as some apps can only save to /mnt/sdcard and it quickly takes up our phone's internal memory. I have offline GPS maps and a few Gameloft games which can only save their data to /mnt/sdcard and as you can imagine free space is very limited.
What I would like is to switch this around. Basically I have a 32GB SD card that I would like to use a storage for some of my apps as it is not being fully utilized. I've searched around and it doesn't seem like there is an easy way to do this. I'm not completely sure but it seems like there are methods that might be specific to different phones which requires modifying a file in /system/etc.
Will this safely work for our phone?
check this topic
http://forum.xda-developers.com/showthread.php?t=1458153&page=3
posts 21 to 25 and 33 & 34..
For Recovery swapping has been tried..
You may get some idea..
Maybe the use of symbolic links could help, but I never tried it on an Android device.
I had read people Mapping the External under a directory for example the Games directory and therefore all games would in theory be on the External. I think this is what you mentioned as symbolic links.
How can you do that. I tryed a million things. Last time i installed literom with added swap internal memory to sd mod. And after i copy something in phone i loose the mobile signal. I guess the card is getting corrupted or something. How can i make it so the sd card wont be unmounted when i plug the phone in pc ?
Might want to consider this:
Root External 2 Internal SD
I've not used this specific one myself but I have used similar apps in the past.
I didn't use that yet.
But what i found untill now
1. Using Directory Bind wich makes a link between actual place of the files and where they should be. Example You put com.xxx.xxx in your SD card and set the progam to tell android when is looking into sdcard/android/data/com.xxx.xxx go for files in sdcard/external_sd/com.xxx.xxx
This method is good for games and files for them
2. Another thing is modifing vold.fstab and swapping the way adroid mounts those partitions. (this option is buggy somehow)
Hopefully we can implement a "fusion" drive like newer macs. I know it's possible to make your own with a few unix commands, so I wonder if another dev and I could get it working on the S4. A fusion drive is basically a SSD+Traditional HDD that the system sees as one drive. It automatically moves the lesser used items to the slower drive and keeps the system intensive files on the faster drive. Essentially we could use this technology to make our MicroSD and EMMC appear as one unit on the OS.
If any DEVs are willing to work with me please shoot a PM. No other users at this time please.
Try directory bind. Can setup to mirror items on your ext-sd
Sent from my SGH-M919 using xda premium
dannyben said:
Try directory bind. Can setup to mirror items on your ext-sd
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
This wouldn't mirror anything. It would show the system storage as (mine personally) 64gb+16gb as one unit.
Same thing. Can setup a folder on internal sd called extsd and turns internal sd to 80gb
Sent from my SGH-M919 using xda premium
Personally, I think this is silly and hope to never see it implemented on any ROMs that I enjoy. Just my opinion. Could be good as a flashable package that ppl have the option of installing through Recovery, though. I'll throw the idea out there on the irc chats and let me ppl know you're looking for a partner in crime.
I know internal storage reads faster than an sdcard, would this allow us to basically have 48g internal memory?
Sent from my SGH-M919 using xda premium
inphamous36 said:
I know internal storage reads faster than an sdcard, would this allow us to basically have 48g internal memory?
Click to expand...
Click to collapse
If you're asking "will this magically speed up my slower SD card", think about why that's not the best question.
Why not just write a script that swaps internal and external SDs?
Sent from Spaceball One.
blackknightavalon said:
Why not just write a script that swaps internal and external SDs?
Sent from Spaceball One.
Click to expand...
Click to collapse
Not possible/also not a good idea at all to swap the SDs. The only way you can get a "hybrid" system like what the OP suggests is either the actual fusion of the hardware with special custom firmware which handles the offloading of these tasks of moving the most used sectors of data to the faster medium, OR, a custom file system that is drive agnostic and can address multiple storage devices, consistently test their access speeds to assess performance, and intelligently offload data and traffic to the correct disk. Seeing as we have neither in any Android device that I know of, this feat is practically impossible until somebody compiles a new kernel with a file system plugin that does exactly this. It's a great idea, don't get me wrong, however it's going to be a total pain to accomplish, and secondly, removing the external storage, or god-forbid the SD card fails, and the entire checksum for the larger virtual disk has now failed and you've lost all your data. It's a bad idea when you're talking about mobile devices that you depend on daily like this, great for tablets and stuff, but bad for phones (unless you never mess with it or do anything weird that could compromise the SD card).
Cynagen said:
Not possible/also not a good idea at all to swap the SDs. The only way you can get a "hybrid" system like what the OP suggests is either the actual fusion of the hardware with special custom firmware which handles the offloading of these tasks of moving the most used sectors of data to the faster medium, OR, a custom file system that is drive agnostic and can address multiple storage devices, consistently test their access speeds to assess performance, and intelligently offload data and traffic to the correct disk. Seeing as we have neither in any Android device that I know of, this feat is practically impossible until somebody compiles a new kernel with a file system plugin that does exactly this. It's a great idea, don't get me wrong, however it's going to be a total pain to accomplish, and secondly, removing the external storage, or god-forbid the SD card fails, and the entire checksum for the larger virtual disk has now failed and you've lost all your data. It's a bad idea when you're talking about mobile devices that you depend on daily like this, great for tablets and stuff, but bad for phones (unless you never mess with it or do anything weird that could compromise the SD card).
Click to expand...
Click to collapse
Uhh...the script for both the SGS3 and the SGS3mini only works if there's an SDcard in the phone, so it is very much possible.
Sent from Spaceball One.
blackknightavalon said:
Uhh...the script for both the SGS3 and the SGS3mini only works if there's an SDcard in the phone, so it is very much possible.
Sent from Spaceball One.
Click to expand...
Click to collapse
If there is a script for it, awesome, I wouldn't do it myself though, not with only 8gb usable space, I'll burn through that in no time flat. I'm biding my time for 64gb before I invest in a new S4. Back on the topic of the "hybrid"/"fusion" drive, my statement still stands. It's not possible without a file system driver that supports it, or the hardware+firmware to support it (like those hybrid SSD-HDDs on the market).
Cynagen said:
If there is a script for it, awesome, I wouldn't do it myself though, not with only 8gb usable space, I'll burn through that in no time flat. I'm biding my time for 64gb before I invest in a new S4. Back on the topic of the "hybrid"/"fusion" drive, my statement still stands. It's not possible without a file system driver that supports it, or the hardware+firmware to support it (like those hybrid SSD-HDDs on the market).
Click to expand...
Click to collapse
The reasoning is this: The "virtual SD card" is the default storage space. All you'd have to do is apply the script, switch everything over to download into /sdcard, and leave the external SD card alone. For example, this would perpetually leave 9GB of hard drive space open on my phone while it thinks there's 64GB of space to play with.
As I said, it works perfectly on the SGS3mini.
blackknightavalon said:
The reasoning is this: The "virtual SD card" is the default storage space. All you'd have to do is apply the script, switch everything over to download into /sdcard, and leave the external SD card alone. For example, this would perpetually leave 9GB of hard drive space open on my phone while it thinks there's 64GB of space to play with.
As I said, it works perfectly on the SGS3mini.
Click to expand...
Click to collapse
So the script disables the /external_SD and makes it think that the SD card is actually the internal storage, leaving the internal storage alone? Not just swapping them like it sounded? Not bad, that I can see being beneficial with a fast enough SD card in place, however, only in that scenario.
Cynagen said:
So the script disables the /external_SD and makes it think that the SD card is actually the internal storage, leaving the internal storage alone? Not just swapping them like it sounded? Not bad, that I can see being beneficial with a fast enough SD card in place, however, only in that scenario.
Click to expand...
Click to collapse
Have you ever had an older Android device like a G1 or the original MyTouch? The A2EXT hack worked in a similar manner, but this doesn't involve partitioning anything, and a class 4 card could work.
Sent from Spaceball One.
Sorry Cynagen....what I'm talking about requires no special firmware or hardware. It's a unix/linux script that tells the system to read both drives as one. It's not a solution for world hunger or anything, but rather a cool project I plan to work on. Hopefully some smarter people can make it more usable for mass consumption, but I honestly don't care lol. XDA was founded on crazy ideas not intended for the masses anyways
KillaHurtz said:
Sorry Cynagen....what I'm talking about requires no special firmware or hardware. It's a unix/linux script that tells the system to read both drives as one. It's not a solution for world hunger or anything, but rather a cool project I plan to work on. Hopefully some smarter people can make it more usable for mass consumption, but I honestly don't care lol. XDA was founded on crazy ideas not intended for the masses anyways
Click to expand...
Click to collapse
SKIP TO THE BOTTOM FOR THE MOST BASIC OF SCRIPTS TO ACCOMPLISH YOUR GOAL!
Long-winded, drawn-out-explanation:
It requires a whole new file system for a TRUE hybrid system which intelligent offloads the most used files to the fastest media available. You can do a JBOD RAID to do the same thing, but Android doesn't support RAID, and again, that's a "firmware" type thing where the RAID hardware/software translates your calls for sector 6689544 (doesn't exist in the 8gb usable space) to sector 2593544 of your SD card. There is no script that can accomplish this without maintaining an insanely large journal of where everything is located. I thought about this, but it would literally require a faux drive location, an extra service running on Android to listen for the system requesting files (presenting the faux drive location), and then making the appropriate call to the right drive. Wikipedia "File system"
Here's the basics of what happens when a file is requested by an application on ANY operating system:
1. File request to OS
2. File system opens journal (table/list) of files, finds match starting at sector 6689544.
3. File system opens appropriate drive location to retrieve sector 6689544, locks the sector and any other sectors with data for the file (prevent write and corruption of the data)
4. Read-ahead buffers data from subsequent sectors with continued data stream for the requested file
5. A. Returns either data stream if file is larger than buffer size, repeats steps 4 and 5 until finished; B. If smaller than max buffer size, entirety of the file
6. Releases lock on data sector(s) (to prevent corruption during read by an opposing write operation to the same location)
Now, that's just the basics, if you get to the nitty gritty, when you're addressing multiple volumes as one larger volume, this requires intersecting the request for data either at step 2 with replacing the file system, OR providing the original file system a faux "virtual" disk to address as mentioned on Wikipedia:
Some file systems are "virtual", in that the "files" supplied are computed on request (e.g. procfs (Wikipedia)) or are merely a mapping into a different file system used as a backing store.
Click to expand...
Click to collapse
Either way, there has to be something to intelligently keep track of the location of the files, and with a Hybrid system like you're talking about, the best and fastest way would be a whole new file system. Creating a procfs "virtual" service is also possible, but is likely going to be much more prone to bugs and failures unless maintained very heavily. Porting an existing file system that can do this would be much much more feasible and can be built into the kernel directly. A simple script cannot accomplish this without just blindly mapping the SD card into the internal storage file structure.
Short and simple hack to accomplish what you want:
This is called a "symlink" which can already be accomplished quickly with the following command: "mkdir /storage/sdcard0/ext; ln -s /storage/sdcard1 /storage/sdcard0/ext"
There's the script you're talking about, but it's a dirty hack and yes, it'll work provided the "LN" command is available, but again, it's really dirty (I guess most don't care?)
If "mount" and subsequently "umount" are available commands in the Android terminal, something like this should work to completely remove the external SD mapping: (This is based on the Galaxy S II JB file system mappings:
umount /storage/sdcard1
mkdir /storage/sdcard0/ext
mount /dev/emmc /storage/sdcard0/ext
Now this is just a rough sketch of what you want to do, if you could provide me with a dump of a couple things, I can write up a script for you no problem. I'll need the following:
A listing of /dev: "ls /dev" output
The contents of /etc/fstab: "cat /etc/fstab" output
And the information on the "source folder" for the external SD card: "stat /External_SD" (or whatever folder it is)
hope you maje this
LIL_ROOKIE said:
hope you maje this
Click to expand...
Click to collapse
Cynagen said:
I'll need the following:
A listing of /dev: "ls /dev" output
The contents of /etc/fstab: "cat /etc/fstab" output
And the information on the "source folder" for the external SD card: "stat /External_SD" (or whatever folder it is)
Click to expand...
Click to collapse
I don't have this information, I need it to proceed. Pull this data from an ADB connection as root, and dump it to a text file like so:
"ls /dev > /external_sd/dev.txt" (or whatever /external_sd is for the S4's SD card)
"cat /etc/fstab > /external_sd/fstab.txt"
"stat /external_sd > /external_sd/stat.txt"
Then zip those text files and send them to me so I can dissect.
It's fairly simple to use a loop device, a simple chroot environment, and mdraid (reason for chroot) to test this out. You'd use an image file and create a loop device so it can be file system independent. Problem is kernel support for md_raid and loop devices... But I tested this out. .. results weren't that great... But they weren't awful. I used a 64gb SanDisk class 1 billion. . Or whatever that crap is labeled.
I also used rxdsk/rxadm (compiled for armel, obviously) to make a ramdisk. That was quick. That also requires chroot, custom kernel..
Edit: In terms of garbage collection. It's beneficial to have more free space than none. Is there an allotment of hidden space dedicated to this, would increasing the size of that space be beneficial, I don't know.
Heres a little piece from Micron.. What I'd like is info on the (presumably Samsung) nand and if it has said overallotment.
http://www.micron.com/~/media/Docum... Flash/tn2960_garbage_collection_slc_nand.pdf
Blades said:
It's fairly simple to use a loop device, a simple chroot environment, and mdraid (reason for chroot) to test this out. You'd use an image file and create a loop device so it can be file system independent. Problem is kernel support for md_raid and loop devices... But I tested this out. .. results weren't that great... But they weren't awful. I used a 64gb SanDisk class 1 billion. . Or whatever that crap is labeled.
I also used rxdsk/rxadm (compiled for armel, obviously) to make a ramdisk. That was quick. That also requires chroot, custom kernel..
Edit: In terms of garbage collection. It's beneficial to have more free space than none. Is there an allotment of hidden space dedicated to this, would increasing the size of that space be beneficial, I don't know.
Heres a little piece from Micron.. What I'd like is info on the (presumably Samsung) nand and if it has said overallotment.
http://www.micron.com/~/media/Docum... Flash/tn2960_garbage_collection_slc_nand.pdf
Click to expand...
Click to collapse
They're looking to make the EMMC an accessable folder within the internal NAND file structure is what it seems. What I originally thought was they wanted to make a hybrid drive like they were originally mentioning where we could offload the most accessed sectors to the (presumably faster) NAND and relegate all other requests to the slower SD card. Providing a large contiguous drive seamlessly. They just want the dirty hack to accomplish this, and that's their choice. Honestly, I'd rather have the whole package like what you're (and I was previously) aiming for to have the best of both worlds.
Hello. I bought a SM-T210R for my daughter she burnt through her 8GB pretty fast. I told her to just move her apps to the SD card..... Than I found out you couldn't. I rooted it. I would like to know if there is a good app to use to move the apps. I tried some of the apps on the store app2sd, and a few others. They don't seem to work and suggest you ask Samsung for a new rom.... Any Ideas? I am sure it has been asked before, I was looking through all the threads couldn't seem to locate one. So I am sorry if you are answering this question yet again :cyclops: Thank you in advance.
trinitykilla said:
Hello. I bought a SM-T210R for my daughter she burnt through her 8GB pretty fast. I told her to just move her apps to the SD card..... Than I found out you couldn't. I rooted it. I would like to know if there is a good app to use to move the apps. I tried some of the apps on the store app2sd, and a few others. They don't seem to work and suggest you ask Samsung for a new rom.... Any Ideas? I am sure it has been asked before, I was looking through all the threads couldn't seem to locate one. So I am sorry if you are answering this question yet again :cyclops: Thank you in advance.
Click to expand...
Click to collapse
Gl to sd (root) or foldermount. I am not responsible for any damages to your tablet. But these two apps worked for me.
Sent from my SM-T210R using XDA Free mobile app
trazfer said:
Gl to sd (root) or foldermount. I am not responsible for any damages to your tablet. But these two apps worked for me.
Sent from my SM-T210R using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the suggestion I'll giveum a shot. But note I hold everyone responsible for damages!!!!! First you, Then Obama and then THE WORLD muhahahahahahaha!!!!
Really tho thanks
4.2.2
trinitykilla said:
Thanks for the suggestion I'll giveum a shot. But note I hold everyone responsible for damages!!!!! First you, Then Obama and then THE WORLD muhahahahahahaha!!!!
Really tho thanks
Click to expand...
Click to collapse
Hi I know android 4.2.2hasent been officially released for our tablet but a Dev called @mkaymuzik has been porting it works really good and it has move apps to sd card just incase his doesnt help
Since you're already rooted and (I assume) running a custom recovery, there's a somewhat easy solution for this. First, back up everything from the internal memory located at /sdcard, and copy it all over to whatever physical SD card you plan on using - I went with a 64gb. This is probably fastest if you just back up all of /sdcard to the pc, and use some kind of card reader to transfer it over, you'll get much better speed, but you can do this all over MTP with the usb cable if you don't have a reader. Next, reboot into recovery and flash this kernel, which among other things adds support for a storage swap. Clear the cache for good measure, this won't affect any user data. Reboot, and using a terminal emulator or adb shell, run the following command:
Code:
su
setprop persist.customboot.sdcard internal
Reboot once more, and you'll find your physical sdcard is now mounted as /sdcard, while the internal is mounted as /.sdcard (which virtually nothing will use, but that's fine). Any large games you install should put their data in /sdcard/Android/obb, or /sdcard/Android/data, or just random folders on /sdcard, all of which are now your physical card. Once you've finished the swap, you'll want to delete most/all of the files on /.sdcard, since everything there directly uses space in /data/media. Now the only thing that will eat up your internal memory are actual .apk files.
This does have one downside, the storage interface in settings doesn't really know what to think of the mod. It will claim you only have 8gb internal, but then show the free space available on the physical card. If you've got more than 8gb of stuff on the card the bar graph is completely useless, but at least the text does show the correct free amount. I've currently got around 20gb of misc games installed and working great, however if you have any Humble Bundle games keep in mind that these don't use .obb files and the larger ones will quickly eat up your internal space with gigantic .apk files.
You might also want to disable zram once you flash the new kernel. It compresses ram that's not actively being used, effectively giving you more ram at the cost of cpu/battery. I find we have plenty of ram and I'd rather have longer battery life. As root, the command is:
Code:
setprop persist.service.zram 0
You'll need a reboot after running it, of course, but you can enable the sd card swap and disable zram at the same time, rebooting only once.
This is probably the most transparent method, once it's set up you won't need to manually move new apps as you install them, and you don't need to worry about apps that write to random locations on the sdcard.
bakageta said:
Since you're already rooted and (I assume) running a custom recovery, there's a somewhat easy solution for this. First, back up everything from the internal memory located at /sdcard, and copy it all over to whatever physical SD card you plan on using - I went with a 64gb. This is probably fastest if you just back up all of /sdcard to the pc, and use some kind of card reader to transfer it over, you'll get much better speed, but you can do this all over MTP with the usb cable if you don't have a reader. Next, reboot into recovery and flash this kernel, which among other things adds support for a storage swap. Clear the cache for good measure, this won't affect any user data. Reboot, and using a terminal emulator or adb shell, run the following command:
Code:
su
setprop persist.customboot.sdcard internal
Reboot once more, and you'll find your physical sdcard is now mounted as /sdcard, while the internal is mounted as /.sdcard (which virtually nothing will use, but that's fine). Any large games you install should put their data in /sdcard/Android/obb, or /sdcard/Android/data, or just random folders on /sdcard, all of which are now your physical card. Once you've finished the swap, you'll want to delete most/all of the files on /.sdcard, since everything there directly uses space in /data/media. Now the only thing that will eat up your internal memory are actual .apk files.
This does have one downside, the storage interface in settings doesn't really know what to think of the mod. It will claim you only have 8gb internal, but then show the free space available on the physical card. If you've got more than 8gb of stuff on the card the bar graph is completely useless, but at least the text does show the correct free amount. I've currently got around 20gb of misc games installed and working great, however if you have any Humble Bundle games keep in mind that these don't use .obb files and the larger ones will quickly eat up your internal space with gigantic .apk files.
You might also want to disable zram once you flash the new kernel. It compresses ram that's not actively being used, effectively giving you more ram at the cost of cpu/battery. I find we have plenty of ram and I'd rather have longer battery life. As root, the command is:
Code:
setprop persist.service.zram 0
You'll need a reboot after running it, of course, but you can enable the sd card swap and disable zram at the same time, rebooting only once.
This is probably the most transparent method, once it's set up you won't need to manually move new apps as you install them, and you don't need to worry about apps that write to random locations on the sdcard.
Click to expand...
Click to collapse
Awesome thanks!!