Yes, I am a noob. New to Android but not PCs. I have searched all morning for an answer to this question and I am not eligible to post in "developers" yet so I am at your mercy.
Phone in question is box stock SCH-i535 @ 32gb. Will be using 64gb SD card class 6. I want to run BEANS ver 10 TW rom.
Here is the question: Is 'LinktoSD' compatible with or even needed in BEANS 10? If it would be useful in this ROM (to move as many applications as possible to External SD) should the required 2nd partition on the SD card for 'LinktoSD' be formatted as ext2 / ext4 or FAT32? I will probably size it at 2gb.
Any help would be greatly appreciated. I'm just not sure about the best approach with BEANS 10, or if 'LinktoSD' functions are replicated in that ROM. (?) Or if BEANS 10 would have problems with the ext4 partition?
Thanks to this site and all the developers & contributers for making all this great information available to a noob like me! :good:
[email protected] said:
Yes, I am a noob. New to Android but not PCs. I have searched all morning for an answer to this question and I am not eligible to post in "developers" yet so I am at your mercy.
Phone in question is box stock SCH-i535 @ 32gb. Will be using 64gb SD card class 6. I want to run BEANS ver 10 TW rom.
Here is the question: Is 'LinktoSD' compatible with or even needed in BEANS 10? If it would be useful in this ROM (to move as many applications as possible to External SD) should the required 2nd partition on the SD card for 'LinktoSD' be formatted as ext2 / ext4 or FAT32? I will probably size it at 2gb.
Any help would be greatly appreciated. I'm just not sure about the best approach with BEANS 10, or if 'LinktoSD' functions are replicated in that ROM. (?) Or if BEANS 10 would have problems with the ext4 partition?
Thanks to this site and all the developers & contributers for making all this great information available to a noob like me! :good:
Click to expand...
Click to collapse
** To avoid confusion, I understand that a box stock phone can't run BEANS 10. It WILL be rooted and un-locked.
[email protected] said:
Yes, I am a noob. New to Android but not PCs. I have searched all morning for an answer to this question and I am not eligible to post in "developers" yet so I am at your mercy.
Phone in question is box stock SCH-i535 @ 32gb. Will be using 64gb SD card class 6. I want to run BEANS ver 10 TW rom.
Here is the question: Is 'LinktoSD' compatible with or even needed in BEANS 10? If it would be useful in this ROM (to move as many applications as possible to External SD) should the required 2nd partition on the SD card for 'LinktoSD' be formatted as ext2 / ext4 or FAT32? I will probably size it at 2gb.
Any help would be greatly appreciated. I'm just not sure about the best approach with BEANS 10, or if 'LinktoSD' functions are replicated in that ROM. (?) Or if BEANS 10 would have problems with the ext4 partition?
Thanks to this site and all the developers & contributers for making all this great information available to a noob like me! :good:
Click to expand...
Click to collapse
See this thread http://forum.xda-developers.com/showthread.php?t=1849860
It doesn't seem to work on Beans 10, nor did it work on CleanRom 2.0. In fact, I'm not sure what ROM's it works on.
snippits of info..
android94301 said:
See this thread http://forum.xda-developers.com/showthread.php?t=1849860
It doesn't seem to work on Beans 10, nor did it work on CleanRom 2.0. In fact, I'm not sure what ROM's it works on.
Click to expand...
Click to collapse
Thanks android 94301, according to the OP he thinks it should work on any custom TW ROM. In theory, that would include Beans.
I hope someone who has tried 'LinktoSD' on a Beans ROM will chime in. I'm still waiting on my SD card to arrive in the mail so I haven't started yet.
I suppose I could play it safe and install both SD partitions as FAT32 for 'LinktoSD', load Beans10 to see what provisions it contains for moving apps to SD, and if I feel I still need 'LinktoSD' the SD card will be ready. Then I could try installing 'LinktoSD' over Beans10 to see if they play well together. If I understand it correctly, 'LinktoSD' redirects to the SD partition on boot. Beans10 will have to allow it. (?)
Someone with more experience than I have may be able to comment on the compatibility of the two. I'm sure I'm not the only one thinking about this. The feature set on 'LinktoSD' looks good to me.
[email protected] said:
Thanks android 94301, according to the OP he thinks it should work on any custom TW ROM. In theory, that would include Beans.
I hope someone who has tried 'LinktoSD' on a Beans ROM will chime in. I'm still waiting on my SD card to arrive in the mail so I haven't started yet.
I suppose I could play it safe and install both SD partitions as FAT32 for 'LinktoSD', load Beans10 to see what provisions it contains for moving apps to SD, and if I feel I still need 'LinktoSD' the SD card will be ready. Then I could try installing 'LinktoSD' over Beans10 to see if they play well together. If I understand it correctly, 'LinktoSD' redirects to the SD partition on boot. Beans10 will have to allow it. (?)
Someone with more experience than I have may be able to comment on the compatibility of the two. I'm sure I'm not the only one thinking about this. The feature set on 'LinktoSD' looks good to me.
Click to expand...
Click to collapse
yeah the the OP is wrong. In fact, I'm not sure it works on any ROM, at least haven't seen evidence of that on this forum.
Still looking..
android94301 said:
yeah the the OP is wrong. In fact, I'm not sure it works on any ROM, at least haven't seen evidence of that on this forum.
Click to expand...
Click to collapse
That could be true on the developer's thread you quoted above. Zedomax describes that process as a 'hack' based off another program. What he's doing sounds similar but I don't believe he is basing his effort off of the 'LinktoSD' program itself. In that effort several people did report problems. 007willieruiz reported that CM10 needed a custom script, droidstyle reported that the kernel would need int.d support to work. Sshams95 actually did run that hack on the Beans ROM and ended up with duplicate file entries. That's all a bit too far out there for me.
What I was asking about was far more basic. Just running the 'LinktoSD' program itself, on the Beans ROM. The goal being to move 'active programs' (where memory speed is not an issue) from internal memory to the SD card, freeing up as much internal memory as possible for other things like (in my case) off road navigation programs and topo maps that will be resident on the device. 'LinktoSD' is showing downloads in the millions so it shouldn't be much of a stretch to think it's been loaded on a custom ROM somewhere. I should probably reserve judgment untilll I have the Beans ROM loaded, as it's memory management capabilities may be enough.
Input from Galaxy S3 / Beans user?
Well, after more web searches it appears LinktoSD has been and is being used on custom ROMS as expected.
(Since I haven't done 10 post I couldn't submit the link.)
The biggest problem for that user group seems to be broken links to the second SD partition after flashing another custom ROM. I still have not been able to find an example of it being used on a Galaxy S3 running Beans ROM. Anyone?
[email protected] said:
Yes, I am a noob. New to Android but not PCs. I have searched all morning for an answer to this question and I am not eligible to post in "developers" yet so I am at your mercy.
Phone in question is box stock SCH-i535 @ 32gb. Will be using 64gb SD card class 6. I want to run BEANS ver 10 TW rom.
Here is the question: Is 'LinktoSD' compatible with or even needed in BEANS 10? If it would be useful in this ROM (to move as many applications as possible to External SD) should the required 2nd partition on the SD card for 'LinktoSD' be formatted as ext2 / ext4 or FAT32? I will probably size it at 2gb.
Any help would be greatly appreciated. I'm just not sure about the best approach with BEANS 10, or if 'LinktoSD' functions are replicated in that ROM. (?) Or if BEANS 10 would have problems with the ext4 partition?
Thanks to this site and all the developers & contributers for making all this great information available to a noob like me! :good:
Click to expand...
Click to collapse
I have this problem too:cyclops:
Found the dude himself..
Well, I finally found some answers from the man himself (the developer of the program). See the following thread if your wondering about this program as I was. Curious note, the developer said he didn't think the Galaxy Si9000 needed the program as it has ample memory available. Still, a very impressive program. :good:
http://forum.xda-developers.com/showthread.php?t=919326
Pull the trigger..
After reviewing approximately 250 pages of threads and post using over a dozen search phrases related to better utilization of the external SD card on the GS3, I found a few bits of information. I'm posting again because I think this will be a relevant issue for most GS3 users sooner or later. While there were several post speculating that the GS3's internal memory is enough, several users reported running low on memory after installing 15 to 20 applications. If you look at the GS3's processing power compared to it's total available memory, it's memory that comes up short. As a disclaimer though, I'm new to Android and to the GS3. Since I had to invest 3 days in the search, I thought a brief summary of the search highlights might be helpful to other noobs like me. I'm also hoping that those in the know will chime in here and share their insights. I've tried to give credit to the original posters in the info bites below.
As someone who is setting up a new SCH-i535 with the intent of running a custom ROM and being able to fully utilize the external SD card, I need the SD card installed and formatted first! The type of SD card / memory management you choose can determine how the SD card should be formatted, so this decision needs to come first.
Problem #1: The S3's internal storage is named SDCARD, the actual external SD card = SDEXT. This creates problems for programs wanting to write to the external SD card. This means that currently Link2SD, App2SD, Data2SD, etc. all have problems working on the GS3. On the GS3 the SD card is secondary not a primary external. It is seen as emulated. There appears to be no solution without Rooting.
Zedomax has this self described "hack" that swaps internal storage with your external SD card so you can increase your app data storage. This appears to shift everything to the SD card with no UI or controls. The good news is he developed it specifically for the GS3.
http://forum.xda-developers.com/showthread.php?t=1849860
Another approach that seems to be similar "ExternalSD2InternalSD" from Mattiadj.
http://forum.xda-developers.com/showthread.php?t=1772234
Kierrok reports this insight for Data2SD:
20. What are the requirements for using the “Move app data to SD card” (Data2SD) feature?
Our Apps2SD scheme creates symbolic links (one per app) at /data/data/com.x.y that will point to somewhere within an ext2/3/4 partition on the SD card.
The supported mount points for the ext2/3/4 partition are:
/system/sd/ (“classic” sd-ext)
/sd-ext/ (“Cyanogen” sd-ext)
/data/sd/ (“MIUI” sd-ext)
So for Data2SD to work, you’ll need to ensure that your ext2/3/4 partition is mounted at one of these locations. Then create an “app” directory at that location in case it doesn’t exist. Once it’s done, you’ll see a free space gauge for it in the Titanium Backup welcome screen, and you can then long-click on an app in the list and hit the “Move app data to SD” button. Once you do that:
First, Titanium Backup will look for existing symbolic links in /data/data/ and attempt to re-use the same target location, if it lies within the ext2/3/4 partition.
If it finds no existing (or no suitable) destination, it will propose to create a “data2″ folder within the ext2/3/4 partition, and will then move the app’s data inside it.
So by default, you’ll get: /data/data/com.x.y => /system/sd/data2/com.x.y (in the “classic” sd-ext case).
Then there is a complete program that offers the ability to move programs back and forth between device and external SD storage. However, the problems cited above create problems for Link2SD.
The actual Developer's thread for the program:
http://forum.xda-developers.com/showthread.php?t=919326
http://forum.xda-developers.com/showthread.php?t=1737213
Dimerk reports that he has Link2SD working on the GS3.
http://forum.xda-developers.com/showthread.php?t=1694063&page=3
I am most interested in the Link2SD approach. I have posted or PM'd the users who claim to have this program working on the GS3 but as of this moment, I have not heard back from any of them. So, while still looking foreword to input from more experienced users, I am going to proceed down the path of running this program on a custom ICS - TW based ROM (Beans is looking good). If my device flames out and burns a hole through my desk I'll post a photo so you can all have a good laugh.
[email protected] said:
After reviewing approximately 250 pages of threads and post using over a dozen search phrases related to better utilization of the external SD card on the GS3, I found a few bits of information. I'm posting again because I think this will be a relevant issue for most GS3 users sooner or later. While there were several post speculating that the GS3's internal memory is enough, several users reported running low on memory after installing 15 to 20 applications. If you look at the GS3's processing power compared to it's total available memory, it's memory that comes up short. As a disclaimer though, I'm new to Android and to the GS3. Since I had to invest 3 days in the search, I thought a brief summary of the search highlights might be helpful to other noobs like me. I'm also hoping that those in the know will chime in here and share their insights. I've tried to give credit to the original posters in the info bites below.
As someone who is setting up a new SCH-i535 with the intent of running a custom ROM and being able to fully utilize the external SD card, I need the SD card installed and formatted first! The type of SD card / memory management you choose can determine how the SD card should be formatted, so this decision needs to come first.
Problem #1: The S3's internal storage is named SDCARD, the actual external SD card = SDEXT. This creates problems for programs wanting to write to the external SD card. This means that currently Link2SD, App2SD, Data2SD, etc. all have problems working on the GS3. On the GS3 the SD card is secondary not a primary external. It is seen as emulated. There appears to be no solution without Rooting.
Zedomax has this self described "hack" that swaps internal storage with your external SD card so you can increase your app data storage. This appears to shift everything to the SD card with no UI or controls. The good news is he developed it specifically for the GS3.
http://forum.xda-developers.com/showthread.php?t=1849860
Another approach that seems to be similar "ExternalSD2InternalSD" from Mattiadj.
http://forum.xda-developers.com/showthread.php?t=1772234
Kierrok reports this insight for Data2SD:
20. What are the requirements for using the “Move app data to SD card” (Data2SD) feature?
Our Apps2SD scheme creates symbolic links (one per app) at /data/data/com.x.y that will point to somewhere within an ext2/3/4 partition on the SD card.
The supported mount points for the ext2/3/4 partition are:
/system/sd/ (“classic” sd-ext)
/sd-ext/ (“Cyanogen” sd-ext)
/data/sd/ (“MIUI” sd-ext)
So for Data2SD to work, you’ll need to ensure that your ext2/3/4 partition is mounted at one of these locations. Then create an “app” directory at that location in case it doesn’t exist. Once it’s done, you’ll see a free space gauge for it in the Titanium Backup welcome screen, and you can then long-click on an app in the list and hit the “Move app data to SD” button. Once you do that:
First, Titanium Backup will look for existing symbolic links in /data/data/ and attempt to re-use the same target location, if it lies within the ext2/3/4 partition.
If it finds no existing (or no suitable) destination, it will propose to create a “data2″ folder within the ext2/3/4 partition, and will then move the app’s data inside it.
So by default, you’ll get: /data/data/com.x.y => /system/sd/data2/com.x.y (in the “classic” sd-ext case).
Then there is a complete program that offers the ability to move programs back and forth between device and external SD storage. However, the problems cited above create problems for Link2SD.
The actual Developer's thread for the program:
http://forum.xda-developers.com/showthread.php?t=919326
http://forum.xda-developers.com/showthread.php?t=1737213
Dimerk reports that he has Link2SD working on the GS3.
http://forum.xda-developers.com/showthread.php?t=1694063&page=3
I am most interested in the Link2SD approach. I have posted or PM'd the users who claim to have this program working on the GS3 but as of this moment, I have not heard back from any of them. So, while still looking foreword to input from more experienced users, I am going to proceed down the path of running this program on a custom ICS - TW based ROM (Beans is looking good). If my device flames out and burns a hole through my desk I'll post a photo so you can all have a good laugh.
Click to expand...
Click to collapse
Great info. I am still trying to find the magic program that will move apps to the Real SD card. I wonder if making one of the App2sD programs a system application would help things?
Got through the ROM.
As I configure a device I keep running notes. I'll share these as they may help other's who are completly new to Android. They are cryptic but should still be of value.
I'll format the SD card to work with Link2SD > Used Mini Tool Partition Wizard, 2 Primary Partitions.
1st / 57.5gb / FAT32 2nd / 2gb / EXT2
Rooted with: "GS3DebugFSRoot R2" / Unlocked boot loader with EZ-Unlock / Copied internal file structures to External SD Card. / Loaded EZ-Recovery as per guide.
Note: The following caused problems - Must load the apps to be run at the root of internal storage. / Launch Superuser app before running EZ-Unlock, etc. Superuser may not run properly as those apps are launched if you don't run it first. / EZ-Recovery navigates via swipe screen. / Boot into recovery navigates via volume & home buttons. / The stock ROM links in the guide are bad, see P-19. / You only need to load a ROM via desktop ODIN, not a kernel, P-22. / "Wipe Data - Factory Reset" is necessary to prevent bugs & errors on status bar.
Finally got Beans 11 up & running, but I may not keep it. I'll load Link2SD when I've found a ROM I'll stick with. Still deciding that issue.
Changes..
Well fellow noobs, it may be time to close this little thread. As far as I have been able to discern, none of the conventional programs for moving applications to external SD cards mentioned above are compatible with the GS3. (The one script is.) I'm hopeful the developers will eventually port these programs to the GS3. I've contacted one of them. As far as need goes, my device only has 2 market apps loaded and is running with 30% of system RAM used. I know that is a bit deceiving as Android is going to use the RAM if its there. Still, I have about 15 more applications to go and will be paying attention to conventional memory management practices to keep as much RAM available as possible. As to the other half of the thread title, I have switched to a more conservative ROM that I am much happier with. I am learning as I go with the help of this forum and so far, I really like the device and the new to me Android experience. I do find The Play Store's instance on WiFi / Cell downloads directly to the device and strictly from them to be a bit odd for an 'Open Source' community though.
Related
Hi all,
I've been searching through the forums and didn't quite find an answer, so sorry if this has been explained before.
I'm currently running an HTC Desire with stock Froyo (i.e. not rooted). Also, my knowledge of rooting and all its benefits is rather slim, so please bare with me. As some of you might know, the internal space on the Desire is rather on the low side, so I used adb to enable all (well, most) apps to be installable on the SD card (adb shell pm setInstallLocation 2). Now, with this, the apps themselves are moved onto the SD card, but their data and/or cache is still being stored internally. Effectively this means in the long run I still run into the ol' storage space problem.
Now, I read how when rooting a phone you create a partition on the SD card to be handled as if being internal space. Does this mean the above mentioned data/cache/all that jazz that would originally stay in the internal storage when using App2SD with a stock Froyo rom would also go onto the SD card, effectively not using the 'real' internal space at all for apps?
I might have to add, the possibility of a 'real' App2SD might be my highest, if not only motivation to root my phone. So if those two methods (rooted vs. non-rooted App2SD) are basically the same (space saving wise), I might as well disregard that notion.
Thank you in advance.
--Jakob
no they don't work the same
if u root your phone and install Darktremor app2sd it will move to ext partition on sd app+data+cache+dalvik cache
so u will end up with a lot of internal free space
and also from then on all your apps will be instaled to the ext partition
So this is the first phone I've seen where it has SYSTEM memory, SD INTERNAL, and SD EXTERNAL. It's really confusing for me.
When I install an app, is it installing to the 16GB built in memory, or my SD card? I haven't modified anything. And if I do a backup using MyBackupPro, is it using the on board, or the SD card?
It seems like everything favors the internal 16GB, so I guess the 32GB I slid into the device should just be used for things like movies and photos, etc?
I guess this confusion is hampering CWM too since it's not used to handling both these "SD CARDS"
Thanks!
bella92108 said:
So this is the first phone I've seen where it has SYSTEM memory, SD INTERNAL, and SD EXTERNAL. It's really confusing for me.
When I install an app, is it installing to the 16GB built in memory, or my SD card? I haven't modified anything. And if I do a backup using MyBackupPro, is it using the on board, or the SD card?
It seems like everything favors the internal 16GB, so I guess the 32GB I slid into the device should just be used for things like movies and photos, etc?
I guess this confusion is hampering CWM too since it's not used to handling both these "SD CARDS"
Thanks!
Click to expand...
Click to collapse
This also brings up another question. Once ROMs do come out as a result of CWM being modified, normally someone does a format\wipe data\clear cache. This would normally clear anything on the "internal memory"... but since there's some confusion as to if the phone sees the "internal SD" as internal memory or not, do you think this process will wipe that as well?
No confusion. I think you may be confusing yourself in a vicious circle
Everything by default is added to the "internal" SD. There are apps (app2SD) and other ways(GB) to install apps to "external" SD, but not all apps can be.
Backups are saved on "internal" SD. (MBP, i dunno, I use TiB) This folder can be copied to "external" SD BEFORE a wipe and flash, then copied back to "internal" SD, backup program installed and restore apps+data preformed(copying the backup folder to pc suggested also in case All goes Wrong) .
"System" is on "internal" SD but is on a different partition, as well as ROM and Internal DB to their own.
CWM has no issue with SD (internal/external SD'd are not new) but as phones and hardware are different for different models it must be modified for the device.... par for the course. As far as how to CWM ROM, always do as OP of ROM states, until you are at least familiar with the process.
Is this your first android device? or first Samsung? I recommend that if you want to understand better how these devices operate to read the Galaxy S family of forums ( Galaxy S, Captivate, Fascinate, etc) as there is tons of info that will be similar to the Infuse.
Hope I ain't steered you wrong and it helps
13_ said:
No confusion. I think you may be confusing yourself in a vicious circle
Everything by default is added to the "internal" SD. There are apps (app2SD) and other ways(GB) to install apps to "external" SD, but not all apps can be.
Backups are saved on "internal" SD. (MBP, i dunno, I use TiB) This folder can be copied to "external" SD BEFORE a wipe and flash, then copied back to "internal" SD, backup program installed and restore apps+data preformed(copying the backup folder to pc suggested also in case All goes Wrong) .
"System" is on "internal" SD but is on a different partition, as well as ROM and Internal DB to their own.
CWM has no issue with SD (internal/external SD'd are not new) but as phones and hardware are different for different models it must be modified for the device.... par for the course. As far as how to CWM ROM, always do as OP of ROM states, until you are at least familiar with the process.
Is this your first android device? or first Samsung? I recommend that if you want to understand better how these devices operate to read the Galaxy S family of forums ( Galaxy S, Captivate, Fascinate, etc) as there is tons of info that will be similar to the Infuse.
Hope I ain't steered you wrong and it helps
Click to expand...
Click to collapse
I have to say your post made a ton of sense and brought clarity to the issue. I'm new to the way Sammy phones work as my past Android Experience has been LG, and HTC (x2)... Thanks!
Misguided? Yes, I'm always chasing my tail hoping I'll catch it... one day I'll get it! hehe.
I'll look through the Samsung forums. Thanks for the tip
bella92108 said:
I have to say your post made a ton of sense and brought clarity to the issue. I'm new to the way Sammy phones work as my past Android Experience has been LG, and HTC (x2)... Thanks!
Misguided? Yes, I'm always chasing my tail hoping I'll catch it... one day I'll get it! hehe.
I'll look through the Samsung forums. Thanks for the tip
Click to expand...
Click to collapse
Yep. The 16gb internal sd is partitioned into a 13 gb and some change (/sdcard) and 2gb (/data). Then the external sd is mounted as /external_sd.
/sdcard and /external_sd are supposed to be used for media (try taking a 2 minute video at 720p res lol...easily 40-50mb) and android devices usually have a 2gb data partition where your apps install (supposed to install by default).
Sent from my SAMSUNG-SGH-I997 using XDA App
h8rift said:
Yep. The 16gb internal sd is partitioned into a 13 gb and some change (/sdcard) and 2gb (/data). Then the external sd is mounted as /external_sd.
/sdcard and /external_sd are supposed to be used for media (try taking a 2 minute video at 720p res lol...easily 40-50mb) and android devices usually have a 2gb data partition where your apps install (supposed to install by default).
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Cool, thanks for the great info
is there way to make every thing store directly on the phone?
Hi all,
I've just purchased a Samsung Tab 2 7.0 P3113 due to the fact that it has an external SD Card slot. I have found that I can not move any applications to the external card. This was one of the primary reasons I purchased the device. I have been using android devices for a while and my first Sony X10, was rooted and running custom roms within the first few weeks after I purchased it. In any case, I have read a number of threads, regarding this subject for the Tab 2 but I have not been able to have an installed app be moved to the external SD Card. Most post will say you have to root the device, (which I have) and use apps such as App2SD. I have even gone as far as loading a custom ROM, but no success. My last resort is to actually partition and repackage a ROM for an external 64GB SD Card and attempt to boot off of it so I will have more space. If anyone has truly been able to move an installed app to the external SD Card could you please point me in the right direction.
I would like some help on this too. But the silence is haunting.
Found this under a compilation thread that covers the 3113's and is down further on the same page in this forum.
http://forum.xda-developers.com/showthread.php?t=1961097
I hope this helps and sorry for the re-re-re editing
AFAIK (and correct me if Im wrong veterans), is a defect of the OS not hardware. ICS and JB of the GT2's do not allow it as the internal memory is already labeled as sdcard. or that seems to be the prevailing opinion so far. I would like a work around but short of flashing a custom rom and/or kernel it seems unlikely to happen. Downside to that is some things don't work all the way in some roms. Ahh for the old days of my stock+ on my incredible. wait. Im still using it from back last summer and it works fine. TY wildstang!!
Dev
Hail Link2SD !!
Only way to move Apps to ExternalSD is using Link2SD for ICS / JB. I have done lot of research and there is no other way.However Link2SD does not move the data files and hence your internal memory will still be filled up as and when you install more apps but at slower rate.
If you want to install games like NFS-MW , Asphalt etc you have to use DirectoryBind tool to move the huge data files (More than 1.5 GB) to external card.
There is a nice tutorial how to use Link2SD here on the forum (http://forum.xda-developers.com/showthread.php?t=919326).
You can use ext4 partition as i found ext2 and ext3 were not being recognized by Link2SD. Just a pointer.
PS: ICS and above no longer support moving apps to SD card. If i am wrong experts correct me.
root is your best bet. check this link, use the script and follow the directions. this script worked wonders. my tab thinks i have 32 gb internal and 4gb sd.
http://forum.xda-developers.com/showthread.php?t=1961097
Hello All,
I have a tablet here that I haven't been able to fix (yet!)
It's a mid vimicro vortex vc0882, armv7, grh55 with android 2.3 November 2011 firmware (resistive 7'') 512mb ram, 4 gb sandisk class 4 internal memory.
Although since getting this one, I now have several other much faster ones to choose from, I really like this tablet with it's chunky yet smooth navigation and so far no pc, laptop, netbook or tablet has beaten me!
Some time around early December 2012 this device experienced a system crash (freeze) that left several apps and games crashing on next boot.
This had happened once before. At which time I performed a simple factory reset from settings\privacy menu and all was well. Not the case after this more recent crash!
The device is stuck with all data as of the crash date. It will install and uninstall apps cleanly within the session, it will write to the internal sd card, yet next time the machine is started, everything is back as it was. The external sd card seems fine and unaffected (moving apps to this doesn't improve the situation, as in still not writing current configuration correctly).
ADB will push basic requests incl installation of apps, but that's as far as it goes. Any clockwork mod based tools don't help. Recovery menu has been tried with every combination. Any recovery / update from zip has been rejected due to e signature error. Tried flash tools and nothing has got through. Once the machine restarts, all is back to crash date groundhog day!
The machine is rooted (has been for most of it's life) and this didn't seem to create any problems.
I have contacted the suppliers for any firmware / recovery that they have, no joy there yet.
Sorry about the long post!
As I have root access does anyone have ideas about a system file workaround / mod or a forced clockwork mod to enable update from zip that bypasses the e-signature verification?
Permissions have been checked and system cleaned on a regular basis.
This tablet is very close to the wopad one just different buttons/button locations, with power/menu/home and back buttons.
Thanks for any positive input!
Bob
Update... Anyone out there?
After removing the internal sd card and exploring the fat 32 partition via windows, I deleted a few non essential local files (one or two of them I had to change the permissions to do so). Refreshed the disk (sd card) and the files were back. So it appears that there is an error in the sd card. Based on this idea, I tried to copy the fat 32 + full linux partitions with contents from the original 4gb sandisk to a 4gb kingston card. All appeared correct via linux type explorer software on windows, but it doesn't work for the device. Attached are the details from the partitioning software and another program that questioned the partitioning setup.
Any tips on the best software for the job + which key (possibly hidden elements) need to be included?
Thanks
Bob
3rd time lucky....
In summary, is it realistic to copy an android's internal micro sd card (system) to another blank card including correct formatting of partitions and get it to operate when inserting the copied / cloned internal memory card into the device?
A while back I asked a question regarding a different tablet, which fell on deaf ears, after a bit I sorted it myself.
Considering the nature of this forum, if this one goes "unsuggested" I will be somewhat disappointed.
With a touch of faith?
Bob
bob_mac said:
Update... Anyone out there?
After removing the internal sd card and exploring the fat 32 partition via windows, I deleted a few non essential local files (one or two of them I had to change the permissions to do so). Refreshed the disk (sd card) and the files were back. So it appears that there is an error in the sd card. Based on this idea, I tried to copy the fat 32 + full linux partitions with contents from the original 4gb sandisk to a 4gb kingston card. All appeared correct via linux type explorer software on windows, but it doesn't work for the device. Attached are the details from the partitioning software and another program that questioned the partitioning setup.
Any tips on the best software for the job + which key (possibly hidden elements) need to be included?
Thanks
Bob
Click to expand...
Click to collapse
I'm not a developer by any stretch of the imagination, but this Linux cell phone has ignited my inner geek, and I must bend it to my will.
My basic question is, with the current state of development, how much is it possible to move from the internal storage of an LG Optimus Fuel phone (L34C/KitKat) and onto the external SD card?
I blow stuff up a lot because I'm an inveterate tinkerer, too adventurous for my own good/skill level. I'm an Android noob, but an old hand at Linux, which means I think I know a lot more about what I'm doing with KitKat than I actually do. But at least I do have a fetish for backups, which is all that makes my misadventures endurable.
So I did a Nandroid backup on my L34C after modding it only enough to support the TWRP backup. But the phone's internal storage is puny, and TWRP manager will only write to the internal SD, so I could only install about 300MB more in apps before there no longer was enough space for another Nandroid backup. Which means I've either got to tone down my tweaking (figure the odds!) or find another way to do Nandroids.
Yes, I could do an initial Nandroid, followed by Titanium backups, but where's the fun in that? Same with doing online Nandroid backups. No self-respecting geek every would let someone else be in charge of maintaining his backups (IMHO). And bonus points if I can relieve internal SD overcrowding by installing/moving apps and whatnot to the external storage.
So I'm thinking this is going to require linking, but the OE FAT32 partition on the external SD card won't support it. The OE 4GB SD card was too small to be slicing up, so I bought a 16GB cat4 SD card, formatted half in FAT32 and half in Ext3, but I could never get the Ext3 partition to mount. I wasn't able to find anything definitive, but I did come across information (of unknown validity) that the L34C's lack of init.d support was the reason it wouldn't mount.
So is this true? If I install a kernel with init.d support in my L34C, will I then be able to mount additional partition(s) on the external SD card?
As for the specifics of the partitioning, I found one mention in another forum in a post dated almost three years ago stating partitions on an Android external SD card had to be no more than 2GB in size, and preferably only 1GB. Is this true? Does it still pertain to KitKat? And what is/was the cause of this partition size limitation?
If the 2GB limit is true, what about creating and mounting multiple 2GB partitions? Say, one exclusively for writing the Nandroid backup to, and a second for moving files out of internal storage?
And what of my overall objective? In the current state of development, is writing Nandroid backups to the external SD card of an L34C (or even better, to the USB) known to be possible? Or im-possible?
If not, and presuming I can manage to get an Ext-formatted partition on the external SD card to mount, which of the many <something>2SD apps should I look to to move as much material as possible off of the internals storage?
I did try installing Link2SD, even though there wasn't an external partition available that supported linking. When I tried to move an app with it, one that Link2SD itself had labeled 'movable,' it failed with:
!Failure
App2SD is not supported by your device. Because your device has a primary external storage which is emulated from the internal storage. You can link the app in order to move its files to the SD card.
Click to expand...
Click to collapse
Dunno why it's blaming Apps2SD unless Link2 is built around Apps2.
But the advice was no help because I can't link to a partition that won't mount. And for all I know, the fact that the L34C uses emulated storage might be a show-stopper.
I've asked these same questions at other Android forums, but got no answers. I initially didn't want to even join XDA because you guys are too far above my pay grade. But I don't think I have any other choice, not if I ever want to get to the bottom of this.
Thank you for taking the time to red my long-winded post.
Hi there,
What you may wish to do is transfer them to your pc for safe keeping and not have to worry about it. You could also try inserting your sd card into your PC and manually transferring the nandroids from your pc to your sd card afterwards.
Also regards to the sd card write protection issue, I could not find anything relevant for your device in particular but you can ask your question here and someone may be able to help you.
Good luck