Xperia C Custom ROM suggestions - Sony Xperia C

Hi there
I used to be an HTC HD2 owner, now that I switched to Xperia C, I found it very lacking in many terms.
I was able to get init.d support on it, but I couldn't get the most of it. because when I tried to get SD-ext support, I always ran into a bootloop. I don't have the knowledge required to edit kernels, and all my edits on the vold.fstab file either failed or just switched the device memory with the SD.
So here are some suggestions with explanations:
init.d support: it means being able to run scripts on boot. it makes us capable of changing processor speed, add tweaks..etc automatically every time the device turns on.
SD-EXT support: You have a big SD card that you don't know what to do with? create a new 8GB EXT4 partition on it, add a script to init.d folder and yo get a whopping 8GB device memory. Tried 4GB on the HD2 with no trouble.
Removing the "Device memory changed" message: having all of the above means we get enough device memory to have everything, so the automatic change of installation folder to the SD would be pointless. and if you have SD-EXT support, it's faster to keep all your apps on one place on the SD card.
I know the X C has less developers and is harder to make custom ROMs for it, but it has such great potential that if we have at least SD-EXT support, I'd keep it for a few more years.
If you have any other suggestion, let me know about it and I'll add it to the list.

Related

[Q] About swap, ext

Hi, i'm a newcomer.
I want to know how to create swap, ext ? Is it necessary ?
I'm using rom Hellmonger Edition .
Help !
trinhpct said:
Hi, i'm a newcomer.
I want to know how to create swap, ext ? Is it necessary ?
I'm using rom Hellmonger Edition .
Help !
Click to expand...
Click to collapse
Hi See http://www.youtube.com/user/reverendkjr#p/u (Watch Linux Videos (2 part) and Den Khal Rom Video (2 part)) for how to create swap, ext........
Benefits - Swap brings stability to the phone, so you won't face force closes too often and ext partition let you install ur apps on sd card. Well its not compulsory it depends what you want from your XT720.
Is Swapping different from creating an Ext2 partition? I know how to make an Ext2 using partition manager, but I have no idea what is swapping, or how to do it.
creating ext2/3/4 partitions are for you to store your apps on your sd ext partition instead of your phone internal memory. many of the xt720 users use ext because of our low internal memory, which limits us to only a few apps which we want to keep on our phone. however, you can use link2sd instead, which stores the application on your sd card (on a second partition which can be fat32 or others like ext). you might wanna use link2sd instead of the rom's built in function to install apps on ext as it is easier to partition an extra fat32 than to partition ext.
i dont know exactly swap does, but i know you can get much more free ram as the system swaps the cache into the sd card or something. e.g. usually you get 60mb free without swap on, and when you activate swap, free ram can hit higher than 100mb so you can do more multitasking. however, to use swap on our phone, we have to plug our phone in to the computer and use command prompt or terminal and use adb to fastboot fjfalcon's boot.img. we cant flash the boot.img because of the stupid locked bootloader. to use swap, you also have to create an extra partition (called linux-swap) on your sd card.
hope this was helpful!
Can you help me how to enble it, i use Minitool partition to create 3 primary : Fat32, ext2, swap ... But when i use link2d, mount script error : mount scriptcannot be created - muont: Device or resource busy .. When i use A2SDGui ( on hellmoger rom ), swap is deactivated, cannot enble ... Help me. Thank for advance !
I don't think Link2sd is compatible with Hellmonger's ROM yet, it's still on the "to do" list. To use swap you have to fastboot (check out Reverendkjr's YouTube videos) one of fjfalcon kernels every time you reboot your phone.
eejin2 said:
i dont know exactly swap does, but i know you can get much more free ram as the system swaps the cache into the sd card or something. e.g. usually you get 60mb free without swap on, and when you activate swap, free ram can hit higher than 100mb so you can do more multitasking. however, to use swap on our phone, we have to plug our phone in to the computer and use command prompt or terminal and use adb to fastboot fjfalcon's boot.img. we cant flash the boot.img because of the stupid locked bootloader. to use swap, you also have to create an extra partition (called linux-swap) on your sd card.
hope this was helpful!
Click to expand...
Click to collapse
Yes! that is exactly wat I was referring to. The sdcard internal storage thing is not an issue for me with my ROM, but I sorta have an addiction for constantly finding ways to better my phone. I am just wondering if creating a swap, or using applications like Swapper can help my phone. An increased amount of RAM can help multitasking and reduce lag right? By repartitioning, does all my files get erased? will it affect the rom that I am running?
i think i theoretically know how the apps2ext works cos i dont use it so i dont have first hand experience. but on hellmongers xda special final rc1, apps2ext should be already in place, but you have to create an apps folder in your sd-ext partition.
there is already tutorial made by another xda user reverendkjr on how to activate swap. if you already have the three primary partitions, there's actually nothing much left to do but to learn a little of how to use adb. to activate swap, you have to boot into fjfalcons custom kernel because the stock one doesnt support it, so you have to fastboot the boot.img. just search around the xda forums for the fastboot and download it. the video will show you what to do. http://www.youtube.com/watch?v=pu1EjoUGEgQ
you dont have to use any swapper app from the market. fastbooting into fjfalcon's kernel will activate swap automatically. the problem is that once you reboot normally after fastboot, the fastboot will be gone and you will boot into the stock kernal again. you can only activate swap when you are at your computer. swap wont affect the rom you are using. most roms around this subforum support swap if you fastboot your phone into the custom img.
swap will give you a lot more free ram and you will be able to do more multi tasking, but it will take up a very little bit more battery.
yes, to partition your sd card means that your info will be gone. you should just save everything in your sd card into a folder on your computer so that once you partition the sd card, you can just put them back instead of finding some files back one by one and saving it in the card. i'd do this if i were you anyway because some files on the sd card are required for us to boot into open recovery, so if they are missing, you have to do the "install system recovery" thing from the open recovery apk again.
trinhpct said:
I want to know how to create swap, ext ?
Help !
Click to expand...
Click to collapse
Use xdl2.4pda.ru/937329/pwhe52.exe?000636ffb23196624e4c7d69000000004d9e4343117ca335f76a096de7f0f02e can't use links in my posts yet
eejin2 said:
.
i dont know exactly swap does, but i know you can get much more free ram as the system swaps the cache into the sd card or something.
Click to expand...
Click to collapse
Just to clarify for people who don't understand the concept behind swap. For a computer to run its processes and applications they must be loaded to physical memory from where they are managed. This happens on your computers RAM. So when you open an application the OS loads that application to your RAM which is a physical chip inside your computer. The more programs you open while multitasking more RAM gets used till it is full. The computer then either kills the least important proccess to make room for what you are doing then, or shifts your process in an idle state to a small temporary partition on your harddrive. This temporary virtual space in windows is called the page file, and in linux its called swap. The same goes for your phone which is basically a small computer.
When you activate swap, all your idle processes can be shifted to your swap while you run heavy or many applications. Increasing stability, and ability to not have your apps killed and started from scratch when you move onto to other tasks on your phone.
There has been much debate over the usefulness of swap on phones, but generally according to most people it increases the overall performance of the phone. Most users recommend having a higher class SD card for swap as your apps are written onto the swap partition and are thus limited by the read/write speed of your card. Also this process consumes modest amounts of battery.
The reason we need to fastboot for swap is because swap needs a custom kernel. A kernel is that basic program which communicates between your hardware and software. Because we have a a locked bootloader on our phone custom kernels cannot be flashed because the bootloader rejects them because of a signature mismatch which we bypass by fastbooting.
Hope that made sense
i only hav a class 2 sdcard and my phone doesn't experience any lag. so I should refrain from swapping since class 2 is too low rite
firzen_net said:
i only hav a class 2 sdcard and my phone doesn't experience any lag. so I should refrain from swapping since class 2 is too low rite
Click to expand...
Click to collapse
You're phone performance and how you feel about it is all that matters , personally I also use the stock class 2 card and didn't have many problems when I used swap some time ago. I, however don't do any hardcore gaming and couldn't go throught the trouble of fastbooting every time so don't use it much now except for experimental purposes.
for the swap kernel right, where can i find the swap kernel compatible with hellmonger's edition?

[Q] gingerbread better file system mounting support (ext4 or btrfs) on sd card?

I have a Samsung galaxy tab 7" currently running the latest version of the overcome rom (but i'm not married to it if others here have better recommendations), and for whatever reason, whenever i try to format my newly purchased 32gb sd card that i've placed inside, it wants to format it in fat32, which is one of the worst filesystems for data integrity ever devised (no journaling or data protection features of any kind). I have attempted to use my fat32 formatted sd card for a few ebooks that i've got, but when i move them from one folder to another, and then reboot, I get a lost+found directory full of corrupt, errant data and an empty folder where i attempted to move my stuff... this is, of course, unacceptable.
first off, why is fat32 used for the sd card in the first place when the system clearly uses rfs by default (upgraded to ext4 by my overcome installation), and anyone who is technologically inclined knows the pretty extreme limitations of fat32 (4gb single file data limit, no file protection mechanisms)?
and secondly, how do I fix this problem? the tab doesn't seem to accept my sd card when i format it in ext4 using my ubuntu desktop and an sd card reader, nor does gingerbread seem to have any advanced mount controls at all (including strangely the lack of mount support for cifs/smb, which i think is crazy as well but probably well out of the scope of this particular post).
tldr: external storage support on gingerbread is archaic and broken, how do i fix it for regular use?
Pinging this thread for IMPORTANCE
I very much hate FAT32, yet am forced to keep using it in my external SD card on phone in the same way. I would love to see all devs add full ROM support for reformatting and mounting external SD cards with full suite of OS supported file systems. How is it OS supports EXT4 yet I am still bound to FAT32 on SD card !!!!????
This is very important to me, and should be to you all too. we need file system journaling and large file support!
Wouldn't hurt to build in advanced visual presentation for formatting/converting any partition on phone from/to all supported types with ability to setup swap partitions. I know I ask for a lot.
------Running--------
SPH-D710, Starburst ROM v2.0, EK02 modem, custom startup screen/sounds
---------------------
cpgeek said:
I have a Samsung galaxy tab 7" currently running the latest version of the overcome rom (but i'm not married to it if others here have better recommendations), and for whatever reason, whenever i try to format my newly purchased 32gb sd card that i've placed inside, it wants to format it in fat32, which is one of the worst filesystems for data integrity ever devised (no journaling or data protection features of any kind). I have attempted to use my fat32 formatted sd card for a few ebooks that i've got, but when i move them from one folder to another, and then reboot, I get a lost+found directory full of corrupt, errant data and an empty folder where i attempted to move my stuff... this is, of course, unacceptable.
first off, why is fat32 used for the sd card in the first place when the system clearly uses rfs by default (upgraded to ext4 by my overcome installation), and anyone who is technologically inclined knows the pretty extreme limitations of fat32 (4gb single file data limit, no file protection mechanisms)?
and secondly, how do I fix this problem? the tab doesn't seem to accept my sd card when i format it in ext4 using my ubuntu desktop and an sd card reader, nor does gingerbread seem to have any advanced mount controls at all (including strangely the lack of mount support for cifs/smb, which i think is crazy as well but probably well out of the scope of this particular post).
tldr: external storage support on gingerbread is archaic and broken, how do i fix it for regular use?
Click to expand...
Click to collapse

LinktoSD + Beans10 = ?

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.

[Completed] [Q]Mounting 2nd part. on ext. SD, moving internal files on LG Optimus Fuel L34C

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

Does Android (12) support XFS file system?

Considering Android is based on Linux, albeit with an ancient kernel, does it support XFS file system? I'm guessing it formats the microSD card as any of the extended file systems (2, 3 or 4) but if it does support XFS, I'd prefer to format it as that FS.
Xfs on android (ported for sdcard)
Update: I've attached clockworkmod with support for xfs(or any other file system the kernel supports) all i did is put my kernel and modify /etc/recovery.fstab ). just untar it ,go to bootloader menu and do fastboot flash recovery...
forum.xda-developers.com
I saw that topic but it's 10 years old. I was hoping for more recent answers.
Why ? For what purpose exactly ? If you want better performance use an A2 microsd card. If you want a better filesystem try exfat , the xfs you can try to format it on Linux and see if the Android will work with it, however I don't recommend that, could introduce risk.
Check out ssdfs if you are into dev stuff however without GPT-5 I can't foresee much interesting happening in filesystems and storage handling due to complexity.
Network_Pro said:
Why ? For what purpose exactly ? If you want better performance use an A2 microsd card. If you want a better filesystem try exfat , the xfs you can try to format it on Linux and see if the Android will work with it, however I don't recommend that, could introduce risk.
Check out ssdfs if you are into dev stuff however without GPT-5 I can't foresee much interesting happening in filesystems and storage handling due to complexity.
Click to expand...
Click to collapse
For faster uploading of files. Ever since I formatted my storages to XFS they move/copy files between each other with the maximum speed their manufacturer says they can do. When they were ext4, copying 50 GB from one device to another was like on Windows - start fast then drop to a ridiculously slow speed, like 20 MB/sec, for instance. And I'm getting the same slow performance RN with the microSD card formatted by Android 12. I wanna upload 400 GB to the SD card but with the current file system I'll never have the 150 MB/sec the card's manufacturer says it can reach for writing. Which means I'll be uploading these 400 GB a whole year. I barely managed to upload my music which is 85 GB and it took me 3 hours to do that.
IDK how to format the microSD card on Linux. I don't even know if that's possible, bc GParted doesn't detect the phone as a device at all - even when it's mounted.
Ah here we are again trying to overcome corporations limitations they imposed on us by their retardation.
Well well well. Whos decision was it to Not use XFS in the first place? Give me a name... Someone from Google who was responsible for Android? Someone from the Phone Device manufacturer? The sd association for not informing developers about a correct filesystem? The makers of ext4 probably sponsored by Redhat ?
They are all GUILTY if you ask me. GUILTY !!!
They should give us our money back for all their crappy products !!!
We should start a class action law suit against all of them, for all of their bull**** limitations, separately for their retardation, and separately for their LIES in their advertising.
How do you know XFS is faster if you can not format the sdcard on Linux?
To format a sdcard on Linux - you connect Only the sdcard. After it's formatted - insert the sdcard in the phone and see if the phone can work with it, or not.
1.)SD cards are usually formatted with exfat.
2.)You will have to build your own kernel with explicit XFS support to enable XFS support.
Now I don't remember, but you can multipartition SD card
Keep the first partition as exfat, the second partition as XFS or ext4 or btrfs.
and loop mount it in a directory.
It's a convoluted process and not sure if it is worth the hassle.

Categories

Resources