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.
Related
Would it be possible to cook a ROM to put the persistent storage on the Storage Card and then just be sure to NEVER ever remove the card? Then utilize the NAND on the flash ROM and the NOR on the internal ROM (with XIP)
Here, http://blogs.msdn.com/windowsmobile/archive/2006/03/16/552996.aspx
Mike Caligaro mentions on an MSDN thread:
"it's possible to mount the internal storage on an SD card. We did this during WM5 development to let us do work on a device that didn't have enough flash available. However, the system can't handle it's persistent storage being removed on the fly. If you were to have your storage mounted on an SD card and you ejected the card, the system would crash. That was acceptable for development, but we'd never make end users put up with it."
Click to expand...
Click to collapse
Couldn't the same setup that his development team made, be made with the tools available here?
So, my question is:
Is there a way to cook a ROM to make use of both forms of flash ROM, both NAND (on card) and NOR (onboard) thereby taking advantage of the fast erase speeds of the NAND and, the fast read speeds and XIPing ability of the NOR (with the caveat of NEVER EVER being able to remove the card)
Appreciate any help in understanding this. Thanks.
wow, i second curiosity on this idea. wish i had more ideas to help implement it...
With 2 cards slots on the 4700, and then have one set to NEVER remove and use the other normally. Don't know if it's possible. The dev team put the internal storage on a card but what about the rest? MikeCal talks about the Treo like that.
MikeCal said:
NAND has some advantages over NOR, but NOR has other advantages over NAND. NOR is much better to execute code from, and NAND is much better to store data in. The ideal is to have the system code stored in NOR and the user data stored in NAND. That, by the way, is what the Treo 700w did.
Click to expand...
Click to collapse
Phones typically have a partition of encrypted memory for the OS and Apps. Most Win7 Phones have 512MB of this ROM. In other phones, the ROM severely limits the number or size of apps. Are apps in Windows 7 Phone stored in the ROM as well?
I didn't think so until I saw some phones have 1GB of ROM. If just the OS + 60MB of pre-installed software is allowed, what's the advantage of 1GB of ROM?
ROM should be Read Only Memory, so I guess that nothing except maybe major system updates will be installed on the ROM.
ROM is a misnomer but nevertheless the ROM partition is what manufacturers refer to for application space.
I don't see the point of having larger ROM partitions unless apps will be stored on the ROM. I'm hoping that if Windows 7 Phone stores apps on the ROM, it can efficiently recognize and install only the necessities onto the ROM and string the rest of the app over the single storage volume. Otherwise, we're looking at an OS with severely limited app storage.
I read in the Microsoft spec that any app pre-installed by the manufacturer needs to be restorable. So they probably have a backup copy of the app in the ROM section in that case.
athompson said:
I read in the Microsoft spec that any app pre-installed by the manufacturer needs to be restorable. So they probably have a backup copy of the app in the ROM section in that case.
Click to expand...
Click to collapse
Yes you are correct, however, as stated in the original post, the limit for pre-installed software is 60MB.
I know that side-loading isn't possible, but I still have to ask: can you remove the sd card and load an app directly onto it with a card reader? I know that removing the card causes a hard reset, but if you pull the battery first, then can you remove the card, mess with it, replace the card and then replace the battery without having the device hard reset? It seems like you could at least access the sd card file system this way (but I'm probably missing something).
Farmer Ted said:
I know that side-loading isn't possible, but I still have to ask: can you remove the sd card and load an app directly onto it with a card reader? I know that removing the card causes a hard reset, but if you pull the battery first, then can you remove the card, mess with it, replace the card and then replace the battery without having the device hard reset? It seems like you could at least access the sd card file system this way (but I'm probably missing something).
Click to expand...
Click to collapse
Surely, if the OS is split between the SD and phone memory then trying to just use the SD in that way would result in corruption?
Also, I imagine that the OS does self consistency checks, in some way, so that when you reinserted the SD card it'd notice that it's been altered?
Of course, that's a guess and I could be completely wrong.
I think I read in another thread that a few people have pulled the sd card, and couldn't read it with a reader. I guess it's encrypted (makes sense, but it still sucks).
Farmer Ted said:
I think I read in another thread that a few people have pulled the sd card, and couldn't read it with a reader. I guess it's encrypted (makes sense, but it still sucks).
Click to expand...
Click to collapse
Da_G mentioned its like a RAID0 with striping between the internal flash and the external flash card. Striping means that the data is divided between the two storage divices, which makes access faster (since you can get them both in parallel). It also means that if one of the memory devices fails, all data is lost. Which comfirms what we've seen in the Microsoft documentation, that if you remove the flash card and replace it with a different one, all your data is lost.
athompson said:
Da_G mentioned its like a RAID0 with striping between the internal flash and the external flash card. Striping means that the data is divided between the two storage divices, which makes access faster (since you can get them both in parallel). It also means that if one of the memory devices fails, all data is lost. Which comfirms what we've seen in the Microsoft documentation, that if you remove the flash card and replace it with a different one, all your data is lost.
Click to expand...
Click to collapse
That makes me think, If it's like a raid0, and your internal memory has 8gb, then you dump in a 16gb card, will it be like raid where only 8gb of the 16gb will be usable (in the raid) ?
DavidinCT said:
That makes me think, If it's like a raid0, and your internal memory has 8gb, then you dump in a 16gb card, will it be like raid where only 8gb of the 16gb will be usable (in the raid) ?
Click to expand...
Click to collapse
That's a good point, it doesn't sound too cool, does it. From what I understand about raid0, the purpose is to divide the data between two different disks, so you can get twice the IO bandwidth (since you can load half the file from each one, get it twice as fast). Raid0 doesn't do any backup, so if either hard drive fails, the whole thing is unrecoverable. Which is why most people don't use raid0.
But since it doesn't do any backup, it means there's no 'wasted' space, which means the full 16gb will likely be usable.
RAID0 is in ", better expression is JBOD (but data is stripped between the drives somehow).
Anyway, it is similar to current WM. There is IMGFS with some reserved space (a lot more actually, so all image updates fit in there without flashing phone, I'd be guessing that about 200MB is left as reserved space). The rest of the storage is as userspace, where are all stuff installed.
DavidinCT,
Your thinking of RAID 1 (mirroring) RAID 0 is striping without parity. So it basically writes/reads across both .. it looks like one volume but writes/reads could be on either storage.. depending on where they were written..
So.. when you remove the card .. or if you alter the card... it beaks the stripe set.. and toasts the storage volume.. if the storage is encrypted that would additionally complicate things..
My HTC Incredible has 8GiB of internal flash available for use. I assume some other Android devices also have a good amount of internal flash.
I have a 32GiB microSD card, but I'd like to add in that other 8GiB, as it's a substantial amount.
I can put things there from adb, or some file managers, but a lot of apps don't access it and mounting the flash to /sdcard and then swapping back gets old.
So, idea -- would it be possible to "merge" the two by a trick of mounting (sort of like JBoD RAID) and get the entire 40GiB under /sdcard? en.wikipedia.org/wiki/Union_mount
I believe UnionFS and AUFS can do this, and I believe Cyanogenmod already has the latter. Has anyone tried making use of that otherwise nearly-wasted chunk of space?
Thanks.
I modified my vold.fstab file to trick the phone into thinking one was the other, but for what your asking I don't think can be done. Symlinks aren't possible using FAT32 (which is what we have the sdcard and emmc formatted as) so that's out. Overall I can't think of any way to do it. Not sure what you're thinking about there with CM, it most assuredly doesn't do that. Also, there are only a small handful of other devices that have emmc's out there, the majority only have sdcards.
Another Newbie Question here.
So AT&T only provides the 16MB Note 2, so of course we add a nice juicy 64GB SD card. But it seems that the stock phone does not really use it for much (that I can tell) to store anything.
First question: On the stock ROM, what apps can be told to use the SD card as default, and how do you change the app settings?
Second Question, for the future: Assuming one Root's the Note 2, what can be safely moved to the SD and how? Or is another ROM required?
Humbly yours - thanks in advance!
Flame Red said:
Another Newbie Question here.
So AT&T only provides the 16MB Note 2, so of course we add a nice juicy 64GB SD card. But it seems that the stock phone does not really use it for much (that I can tell) to store anything.
First question: On the stock ROM, what apps can be told to use the SD card as default, and how do you change the app settings?
Second Question, for the future: Assuming one Root's the Note 2, what can be safely moved to the SD and how? Or is another ROM required?
Humbly yours - thanks in advance!
Click to expand...
Click to collapse
I also have a 64gb card. I put all of my Titanium backups and Nandroids on the external SD (right now TWRP doesn't work with the exfat formatting of my card, so if I want to restore I'll have to move it from ext to int SD).
I also have Spotify set to store any offline music on the external SD. You can do this by installing an old version of Spotify, pointing it to external SD, then updating the app. A quick Google search will find this if it's something you want to do.
It's hard to tell you what to move to the external card without knowing what apps you use. You can get an app called Directory Bind that will point any internal SD location to your external SD. http://forum.xda-developers.com/showthread.php?t=1889550
SD card setup/directory optimization
Really like Android and the Note 2 so far.
Thanks for the directory bind guide link...interesting. Maybe my answer is somewhere in there, so I will take a look either way.
New to external SD use on Android as well (or any phone, that is). I have a 64GB sandisk as well, and It was pre-formatted for Android apparently with some s/w on it. Which is fine, if that is the way I should go.
Just playing around with it at first and copied a music album over, in similar format to my iTunes directory structure -I figured, why not. Perhaps there is a better way to structure my directories though? More general way for all apps to recognize? Moot point?
I assume different apps might require different directory structures...to be efficient, or to be able to work with those dirs/files. I'd rather have the most optimal structure now, before I start messing with creating more directories, etc down the road.
The general questions are, should I format this as something else? What is best to use? (Still looking into different file manager/transfer apps for now, and MAY root and keep stock ROM in the future, but acclimating myself with Android OS has been more than enough for now...I do enough Linux at work, so not in any rush )
Since I went there, I don't know if the OP's question was fully answered...so again, here's a quick (newbie) question for those who root but keep the stock ROM: can apps be moved to the SD card in that case? Or do I need to break out of stock ROM to do that?
Thanks in advance!
Wanted to report back that I tried a simple case of using Directory Bind for something non-critical as a test. Used it to remount Titaniumn Backup to the external SD. Yes, I know you can just point it there. Just wanted to test Directory Bind.
It seemed to work until I rebooted the phone. Then it lost all the binding even tough I had checked off to save it for reboot and saved the binds to a file. So just beware that if you were using Directory Bind for something critical - you might have to recover the phone! I removed the package for now.
dponte said:
Really like Android and the Note 2 so far.
Thanks for the directory bind guide link...interesting. Maybe my answer is somewhere in there, so I will take a look either way.
New to external SD use on Android as well (or any phone, that is). I have a 64GB sandisk as well, and It was pre-formatted for Android apparently with some s/w on it. Which is fine, if that is the way I should go.
Just playing around with it at first and copied a music album over, in similar format to my iTunes directory structure -I figured, why not. Perhaps there is a better way to structure my directories though? More general way for all apps to recognize? Moot point?
I assume different apps might require different directory structures...to be efficient, or to be able to work with those dirs/files. I'd rather have the most optimal structure now, before I start messing with creating more directories, etc down the road.
The general questions are, should I format this as something else? What is best to use? (Still looking into different file manager/transfer apps for now, and MAY root and keep stock ROM in the future, but acclimating myself with Android OS has been more than enough for now...I do enough Linux at work, so not in any rush )
Since I went there, I don't know if the OP's question was fully answered...so again, here's a quick (newbie) question for those who root but keep the stock ROM: can apps be moved to the SD card in that case? Or do I need to break out of stock ROM to do that?
Thanks in advance!
Click to expand...
Click to collapse
If your'e just talking about music, you can put it in any folder and any structure you'd like. The Android Media Server process scans your entire SD card for media (including music) except for folders with a ".nomedia" file in them. It will use the tags to identify the artist, song, and album, then sort them based on that information.
Flame Red said:
Wanted to report back that I tried a simple case of using Directory Bind for something non-critical as a test. Used it to remount Titaniumn Backup to the external SD. Yes, I know you can just point it there. Just wanted to test Directory Bind.
It seemed to work until I rebooted the phone. Then it lost all the binding even tough I had checked off to save it for reboot and saved the binds to a file. So just beware that if you were using Directory Bind for something critical - you might have to recover the phone! I removed the package for now.
Click to expand...
Click to collapse
bummer
don't bother moving any apps to the external sd, since you have TONS OF ROOM in your internal memory on this phone..On the original note, I had over 300 apps installed on the internal, and still had over 5 gigs of room left..
just keep your music, movies, pictures, and other space hogs on it..trust me, leaving apps alone will never be a problem when you have a phone with this much storage space!
wase4711 said:
don't bother moving any apps to the external sd, since you have TONS OF ROOM in your internal memory on this phone..On the original note, I had over 300 apps installed on the internal, and still had over 5 gigs of room left..
just keep your music, movies, pictures, and other space hogs on it..trust me, leaving apps alone will never be a problem when you have a phone with this much storage space!
Click to expand...
Click to collapse
11GB is a lot (available to start with on the ATT model) if you use the external for media (and app cache) and leave the internal for apps mainly...agreed.
Most apps are small in size...however, one app like NOVA3 is 2GB and that is a big bite of your 11GB available, so that is a little concerning
I haven't had the device or android long enough to know, but, are app databases and cache allowed to reside on the external card --in lue of the ability to move apps to the SD being taken away since Jelly Bean (was it at that update)? Can someone point to a good thread on the reason and discussion about that? Thanks.
http://forum.xda-developers.com/showthread.php?t=1994046
App2SD change external to internal.
Sent from my SAMSUNG-SGH-I317 using xda premium
You can make your external your main storage device by using this root technique. But some people don't advise it saying it slows down your processing on apps.
wase4711 said:
don't bother moving any apps to the external sd, since you have TONS OF ROOM in your internal memory on this phone..On the original note, I had over 300 apps installed on the internal, and still had over 5 gigs of room left..
just keep your music, movies, pictures, and other space hogs on it..trust me, leaving apps alone will never be a problem when you have a phone with this much storage space!
Click to expand...
Click to collapse
Note II is a Unified Storage device. It has 11gb available for both user content (pictures, movie, music etc) and apps. I lost 2gb of space moving from my S2 to the N2.
S2 is not a Unified storage device, so it has 11gb of storage available for user content and a separate Apps partition of 2gb.
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!!