correct me of course if I am wrong,
The vibrant uses the Reiser File System (RFS) which is the cause of the slower performance, and the lag fixes create a mini partition on the phone storage using EXT4 or whatever number, which in turn solves the performance issue, however the use of symlinks to find the files in that newly created partition are causing other problems?
If this is any way correct ( I'm kinda noob and probably got it all wrong LOL)
Then why can't we use a program like GParted to Create said EXT4 filesystem/ move ALL files to new partition/ reformat first partition to EXT4/ Move files back/ Then merge partitions to one large EXT4 with all data in-tact?
If we could do this to fix lag, then no-one would need to install a lag fix with each rom upgrade. The Lag would be permanently fixed right?
Does the phone (I'm gonna call it ROM but might be Kernel???) need the RFS to work properly for some reason? Like have files that check or call locations on said RFS filesystem and if so, couldn't those files or scripts be edited to call or look for the new FS?
Related
My sdcard(class 4 8gb sandisk) is causing problems with fat32 fs...i use debian all the time and wud like to have a much advanced fs like ext4 for saving my music,videos,pictures etc instead of fat32...how can i achieve taht...Does android use a fstab or something for mounting on boot ???
I'm quite sure android uses fstab for mounting, you just need to set the proper mounting option on your FS to force it to check fstab options. I have one question(since I don't use a linux machine), can you access your ext(2nd) partition(if you have one) when you connect your phone to the PC using debian?
Yep,Android uses fstab to mount all.
anybody interested in setting it up i dont have the requisite knowhow
I have not toyed with fstab myself... but I did find this page which seems to have want your looking for.
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
It isn't exactly what your explaining, BUT seems to go through the commands needed for what you are wanting to try.
Just remember to back up! Good luck!
Sent from my LG-P500 using XDA App
Instructions:
-Suggested at least fat32 partition to be 1gig and the rest to your ext partition. Also, try to use root explorer for everything else. Must have init.d support.
1. On your SD card, make a folder to serve as a door/portal to access your ext partition files.(When testing this, I just used the default "/sdcard/media" folder)
2. Make a blank text file and name it as "11usext"
3. Using root explorer, edit the file and add this line inside it:
Code:
#!/system/bin/sh
busybox mount -t auto /dev/block/mmcblk0p2 /mnt/sdcard/media
change media to the folder that you just made on step 1. Exit and save.
4. Using root explorer move this file to /system/etc/init.d
5. Again using root explorer, change the permission to "rwxrwxrwx"
6. Reboot and play. This would allow you to access your ext partition through the /media or the folder that you have created.
If this does not work, then you should give more details on what setup you are running.
ungaze said:
Instructions:
-Suggested at least fat32 partition to be 1gig and the rest to your ext partition. Also, try to use root explorer for everything else. Must have init.d support.
1. On your SD card, make a folder to serve as a door/portal to access your ext partition files.(When testing this, I just used the default "/sdcard/media" folder)
2. Make a blank text file and name it as "11usext"
3. Using root explorer, edit the file and add this line inside it:
Code:
#!/system/bin/sh
busybox mount -t auto /dev/block/mmcblk0p2 /mnt/sdcard/media
change media to the folder that you just made on step 1. Exit and save.
4. Using root explorer move this file to /system/etc/init.d
5. Again using root explorer, change the permission to "rwxrwxrwx"
6. Reboot and play. This would allow you to access your ext partition through the /media or the folder that you have created.
If this does not work, then you should give more details on what setup you are running.
Click to expand...
Click to collapse
That's a quite dirty implementation. All he want's is an ext4 partition mounted as /sdcard. I want to do the same, but right now I'm messing with the internal fs. I'll look into it.
That's a quite dirty implementation.
Click to expand...
Click to collapse
Dirty it might be(I even tried a dirtier one), but that's all he's got at the moment. If you have a better solution(even just a rough plan), please do share. Maybe we can exchange knowledge on stuff like these.
Using 2 Ext4 partitions on SD instead of one Ext+fat32
Click to expand...
Click to collapse
Would mean that no Fat32 partition exist, and I've never heard of anything like that.
I have one question(since I don't use a linux machine), can you access your ext(2nd) partition(if you have one) when you connect your phone to the PC using debian?
Click to expand...
Click to collapse
And since no one answered this, I have no idea how you could transfer files to your phone without using card readers.
ungaze said:
Dirty it might be(I even tried a dirtier one), but that's all he's got at the moment. If you have a better solution(even just a rough plan), please do share. Maybe we can exchange knowledge on stuff like these.
Click to expand...
Click to collapse
Probably it involves messing with the init.rc (and I think that involves messing with boot and recovery images, but, I'm not sure) or init.d scripts or fstab. Anyway, I'm not sure, but it should be possible.
ungaze said:
Would mean that no Fat32 partition exist, and I've never heard of anything like that.
Click to expand...
Click to collapse
Yes. The /sdcard partition would exist, just not fat32 formatted.
ungaze said:
And since no one answered this, I have no idea how you could transfer files to your phone without using card readers.
Click to expand...
Click to collapse
Linux systems can read and write to ext4 partitions without problems. In fact, it's a linux filesystem. I had problems once when I had a sd_ext partition (for Apps2SD), because both partitions would get mounted when using mass storage mode, while Android only unmounts the /sdcard (fat32) partition, leading to file corruption (because of the same partition being mounted on both systems at once).
We could create the partitions using gparted or cfdisk on a pc. I'm not sure, but maybe simply mounting it with different params (like the filesystem type and other options) at /sdcard would do the trick. Everything else that follows would be easy.
I've been doing some testing and research.
On recovery side:
I've done a little modification in Mik's ClockWork recovery to make it accept ext4 and vfat as valid file systems for the first partition on sdcard. It involves just a little change on /etc/recovery.fstab file, but then you need to rebuild the recovery image.
This is working fine.
On the OS side:
It's not an easy mod. It involves patching the vold (volume manager) and recompiling. There are some proposed patches to Cyanogenmod, but I don't know if it's been accepted and if it made it to Miks CM7 port.
I'll do some tests and post results.
ilarrain said:
I've been doing some testing and research.
On recovery side:
I've done a little modification in Mik's ClockWork recovery to make it accept ext4 and vfat as valid file systems for the first partition on sdcard. It involves just a little change on /etc/recovery.fstab file, but then you need to rebuild the recovery image.
This is working fine.
On the OS side:
It's not an easy mod. It involves patching the vold (volume manager) and recompiling. There are some proposed patches to Cyanogenmod, but I don't know if it's been accepted and if it made it to Miks CM7 port.
I'll do some tests and post results.
Click to expand...
Click to collapse
This got my interest
Mik's CM7 (beta 6.2) recognizes and mounts the ext4 partition just fine.
BUT:
As vfat is a non posix fs, there wasn't any need for the OS to manage permissions, so it's a mess.
Applications on the SD card (I'm not using Apps2SD or Data2SD) don't load, internal applications can't be moved to SD, and many apps can't store data on the SD, even I've set read+write permissions on all files and directories (chmod -R 777 /sdcard/). I have no idea why. I'm stuck.
Hi.
I've rooted my A70s with chulri's kernel and it seems to work ok.
My next goal is to get more app room ... so I guess I need to resize the app/data partition.
I've thought that having my internal storage formatted on ext4, it would be possible to ln the /data folder to /storage/data without problems, but then I should create a boot script for that. The question is... can I do this with my current root status? What would be the way to do it? I'm don't know enough of linux os to make it on my own.
If the system can't be fooled with a ln, then is there any way to resize the data partition, even if I have to backup/restore my current data?
I don't want to use Urukdroid, since all the versions I tried were very unstable on my machine.
Cheers!!
search the forum: http://forum.xda-developers.com/showthread.php?p=14710945#post14710945
Follow chulri's method, or repartition your internal storage in Linux, mount it on the archos, and copy the data there. Then edit init.rc and change the data mount line. If it gets mounted in the kernel, you'll have to umount it first to remount it to the other partition.
http://forum.xda-developers.com/showthread.php?t=717874 original G1
http://forum.xda-developers.com/showthread.php?t=855424 Reused on EVO
I'm wondering if someone smarter then I can Figure out how to mod the script for the Atrix since we have a unlocked bootloader now.
I notice it is for S-OFF phones, but I'm thinking that this doesn't matter on our phone since we are able to flash radio's ect.
The way I see it we have two main groups of Atrix users, those that want to take space from /sdcard and use it in /osh and those that don't care about /osh and would use the increase space in /sdcard
Mods, sorry if this is the wrong section but It is a development question, I though would be best here.
So reading into these it seems that there are two zips/scripts. The first setups the recovery, you then reboot into recovery flash your android back on then run the second script which tells the kernel what to use for partition sizes.
If you want to go back to stock you reflash the recovery image.
The ATRIX has a very different partition table then evo, hero or g1. So well need someone who understands it better then I to look at the scripts.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
Here is more info, this is for the nook color, but it looks as though we could re-partition the internal memory as we desire. The risk is huge. Also I believe that CWM will re-write the partition table when doing wipes. I don't know the way all of this functions well enough to make the jump and make the /osh 2 or 4gb but that is what I'm looking into.
that might be rather dangerous doings resulting in unworkable touchscreen etc, since for seom reason repartitioning the internal nand ****s up /pds . several people had great problems by doing so.
Moved to proper forum.
crnkoj said:
that might be rather dangerous doings resulting in unworkable touchscreen etc, since for seom reason repartitioning the internal nand ****s up /pds . several people had great problems by doing so.
Click to expand...
Click to collapse
I did read that, but it seemed that it was before it was known that we need to back up the pds partition. But of course we should have images of all the partitions before doing something like this. It sounded relativity safe according to those threads. The partition table has to be written every time you flash and ClockWorkMod apparently will correct the partitions to factory settings if things get messed up.
But then this is why I posted the question, I don't know enough about how clockwork mod works nor how moving the pds partition would effect things.
Again if we can figure this out we can get enough room on /osh so that sogarths hack is not needed (it is redundant and sort of a waste of space (not bashing, it is the best option currently avaiable) to copy the /osh part to a new spot on the sdcard then link everything back in). For those not interested in webtop we can get them more system or sdcard space.
/system 315M 301.9M 13.1M 4096
/data 2G 895.9M 1.1G 4096
/cache 619.8M 87.8M 532M 2048
/osh 755.8M 643.1M 112.6M 2048
315M is too small for cm10 to install extra mods like sony walkman. i wonder if someone can resize it
xuefer said:
/system 315M 301.9M 13.1M 4096
/data 2G 895.9M 1.1G 4096
/cache 619.8M 87.8M 532M 2048
/osh 755.8M 643.1M 112.6M 2048
315M is too small for cm10 to install extra mods like sony walkman. i wonder if someone can resize it
Click to expand...
Click to collapse
I agree with you. For those don't using lapdock, /osh partition really waste of memory but resize partition could brick the device.
here another tool to resize partition.
http://forum.xda-developers.com/showthread.php?t=1171531
http://forum.xda-developers.com/showthread.php?t=1370963
So I got tired of my weird configuration of running the apps in a mounts2sd with a second ext4 partition on my sdcard and technically nothing should prevent us from running safestrap on the sdcard. So I looked around and it took me a while but I found Hashcode's source code and spent some time studying all the voodoo he does, and most of it is fairly straight forward. Small breakdown:
* Extend TWRP with ifdef statement to add new buttons
* sh scripts get called to perform the functionality for those button
* Swap out some links in /dev/block when you switch between slots and stock
* The entire boot partition including scripts, TWRP, etc are stored in boot image
* The boot image is stored in the stock system under /etc/safestrap
Like I said before, most of the functionality is done in borne shell scripts, but there is some hardcoding in TWRP like creating the .img file to /ss. I really don't want to try to recompile TWRP at this time. As such, I want to limit my changes to the borne shell and configuration INI files only. The simplest answer is to remap /ss from internal storage to the sdcard storage. Another option is to have "system" and "cache" in the internal storage and moving "data" to the sdcard. The difficulty here is since TWRP is hardcoded to create the .img file under /ss, I need to move it during the format stage which happens in the script. The danger with the first option I don't know if the phone will boot if the sdcard is removed. safestrap looks for that directory to figure out the mappings in /dev/block. I think if the directory is missing then it will attempt to create it. After that, things might go bad.
Anyway, what are your thoughts?
i wish and hope your still working on this..my phone is so low in internal storage..i cant even use a rom slot other than stock,,ive been useing stock slot ,flashing custom rom in stock slot....anyways hope you continue to figure this out..i know lots of people would appreciate it..thanks
So I've tried multiple ways and have had to step away, think about it some more, and come back to it. Essentially I was not able to get system to boot off of the sdcard. However, the good news is today I was able to have system and cache on internal storage and data on sdcard. So here are the keys to the kingdom that I have found....
The CM11 (and I assume other) ROMs there is a /system/etc/kexec/ramdisk.img file. This file is extracted (gunzip < ramdisk.img | cpio -iu) into the root directory "/" (rootfs). There is a shell script "/sbin/fixboot.sh" that gets executed by /init at the start of the android (on fs). That script essentially mounts /ss to /emstorage and does all the loop storage links to the system.img, cache.img, and data.img files. I was able to mount another /ss2 to my sdcard and point the userdata to /ss2/safestrap/rom-slot?/userdata.img. The limitation is that vfat limits all files to 4 GB max, so the userdata.img cannot be more than 4 GB of storage.
So an option is I can create an updated ramdisk.img file. You would just drop this into your /system/etc/kexec directory on the slot-rom you want to use it. The only file changed in ramdisk.img is /sbin/fixboot.sh. ramdisk.img is part of the CM11 distribution so you would need to replace it each time you perform an update on that rom slot. Other than that, safestrap would by default create userdata.img to be in internal storage.
The next part I'm going to look at is to create a f2fs partition on my sdcard and have my userdata use that f2fs partition. I figure I should good considerable more I/O as f2fs is suppose to be a good amount faster than ext3/4 and we wouldn't be going through a loop device from ext3 to vfat for all I/O. In addition, my data partition would no longer be limited to 4GB due to the file limitation size of vfat.
Thoughts...
So Spyder doesn't have f2fs on it so I've been running ext4. The kernel would need to be setup to be compiled with it. I have a second 6Gb partition formatted with ext 4 with writeback journaling but per my timing tests I don't think it has made a difference. Now I have more than enough space left in both the data and internal partitions. I don't know if it is just a placebo effect but my apps do seem to start slightly faster.
There doesn't seem much interest in this but it was a fun exercise for me. This will be good enough for me as I'll probably upgrade my phone sometime in the future.
Sent from my XT912 using XDA Free mobile app
That.
I have an Xperia Arc S (LT18a) with a custom 4.0 ROM (Ultimate Xperia HD) and i just cant make Link2SD to recognize my 2nd partition. The classic mount: no such file or directory stuff. Which bugs me since i bought the Link2SD Pro version.
I have the normal fat32 and a ext4 partition, i've done a lot of things, created a new scrip in the .ind folder, made Link2SD a system app, rebooted, erased SD and re did partitions multiple times, it just doesnt want to work.
So i can recall couple of years ago i actually got my Moto E to work with linked folders and i never created or modified the partitions as far as i remember, so, question.
Can i link folders to install apps on sd without having to create a new partition? Because is a pain in the ass, is a slow trial and error process and im quite done after trying so much and so many different things.
Thanks
Edit. Solved. Dunno how to mark as solve it or closed so just ignore it
Solved, turned that every software **** was worthless, all i had to do was use the CWR partition tool at the recovery menu obviously and now i had correctly partitioned a ext4 partition and a fat32 one.