99% of the problems users are having with Apps2SD are caused by the unclean shutdown of the ext2 filesystem, because Android does not unmount it when rebooting or shutting down the system, and there are no tools on the device to fsck the filesystem on boot. Ext3 is journaled and this isn't an issue because the journal will simply replay on boot.
I'd like to put an end to this.
Attached is e2fsprogs (tune2fs, e2fsck, resize2fs, and mke2fs) built for Android/ARM. You should also use the "-t auto" mount option so that it's still backwards compatible with ext2.
To convert your ext2 to ext3, you can simply run "tune2fs -j /dev/block/mmcblk0p2" after you have these tools on your device, and reboot (assuming your ramdisk allows for mounting as "auto"). You should unmount and e2fsck the partition first, if it's not been checked for errors.
Step by step by neoobs
can we have a noob-friendly guide to this preferably through terminal.
cyanogen said:
99% of the problems users are having with Apps2SD are caused by the unclean shutdown of the ext2 filesystem, because Android does not unmount it when rebooting or shutting down the system, and there are no tools on the device to fsck the filesystem on boot. Ext3 is journaled and this isn't an issue because the journal will simply replay on boot.
I'd like to put an end to this.
Attached is e2fsprogs (tune2fs, e2fsck, resize2fs, and mke2fs) built for Android/ARM. You should also use the "-t auto" mount option so that it's still backwards compatible with ext2.
To convert your ext2 to ext3, you can simply run "tune2fs -j /dev/block/mmcblk0p2" after you have these tools on your device, and reboot (assuming your ramdisk allows for mounting as "auto"). You should unmount and e2fsck the partition first, if it's not been checked for errors.
Click to expand...
Click to collapse
Will this work with ADP JF1.5?
Before I try it, let me get a few things straing. I have to put these files in the corresponding folders, reflash, then type type the commands from terminal on the phone? Or does this have to be done with adb?
Beast84 said:
Will this work with ADP JF1.5?
Before I try it, let me get a few things straing. I have to put these files in the corresponding folders, reflash, then type type the commands from terminal on the phone? Or does this have to be done with adb?
Click to expand...
Click to collapse
its already working for ADP. I have both my phones running on EXT3 and I havent found a problem. Its more reliable and I have gotten a Force Close or Wait screen with all the speed his build has.
cyanogen said:
To convert your ext2 to ext3, you can simply run "tune2fs -j /dev/block/mmcblk0p2" after you have these tools on your device, and reboot (assuming your ramdisk allows for mounting as "auto"). You should unmount and e2fsck the partition first, if it's not been checked for errors.
Click to expand...
Click to collapse
Huh?
Can you explain this in English please?
Henchman said:
Huh?
Can you explain this in English please?
Click to expand...
Click to collapse
I mainly intended this for other ROM makers, so they can incorporate these features into cooked ROMs.
So this basically means all of us with ext2 partitions will have to get a new card or is there anyways for us to convert to ext3?
djdeviance said:
So this basically means all of us with ext2 partitions will have to get a new card or is there anyways for us to convert to ext3?
Click to expand...
Click to collapse
please re-read the first post.
"To convert your ext2 to ext3, you can simply run "tune2fs -j /dev/block/mmcblk0p2" ....
pershoot said:
please re-read the first post.
"To convert your ext2 to ext3, you can simply run "tune2fs -j /dev/block/mmcblk0p2" ....
Click to expand...
Click to collapse
Yes I did read that and tried as well. Was unsuccessful that why I asked.
Premature SD failure from frequent journal commits?
I wondered why this solution wasn't inplemented from the beginning. However, In one of the threads on A2SD, I read that moving /DATA/DATA to SD would negatively affect the longevity of the SD cards because of the frequent write/re-write cycles of files in that directory, particularly sqlite database commits . One contributor suggested that a using a journalled filesystem in this context would have a similar effect in that there would be repeated writes to the specific area of the SD where the journal is stored.
Any thoughts on this?
Once we run the commands in terminal, will that wipe everything off the ext partition? Or will it just convert the ext2 to ext3 & leave all my apps intact?
sir*mez said:
its already working for ADP. I have both my phones running on EXT3 and I havent found a problem. Its more reliable and I have gotten a Force Close or Wait screen with all the speed his build has.
Click to expand...
Click to collapse
I am not on his build. I am on ADP JF1.5
Which is why I asked if it will work on JF's build & not his build. I know it works on his. He's the one who brought it up
arqueware said:
I wondered why this solution wasn't inplemented from the beginning. However, In one of the threads on A2SD, I read that moving /DATA/DATA to SD would negatively affect the longevity of the SD cards because of the frequent write/re-write cycles of files in that directory, particularly sqlite database commits . One contributor suggested that a using a journalled filesystem in this context would have a similar effect in that there would be repeated writes to the specific area of the SD where the journal is stored.
Any thoughts on this?
Click to expand...
Click to collapse
Most Class 6 cards support wear leveling these days.
Beast84 said:
I am not on his build. I am on ADP JF1.5
Which is why I asked if it will work on JF's build & not his build. I know it works on his. He's the one who brought it up
Click to expand...
Click to collapse
aaahhhh... ;p no i dont think jf has made his EXT3 compatable which is why cyangen is asking every dev to use EXT3.
Cyanogen
Can I put these files in my ADP JF1.5 update.zip & flash that? Or does something else need to be done to have it see the ext3 partition? Also your boot.img with the noatime change, can I put that in also? Or could you possibly take the boot.img from JF1.5 & change it for me?
ext3 is built in ;P
Code:
$ adb shell cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev tmpfs
nodev inotifyfs
nodev devpts
ext3
ext2
nodev ramfs
vfat
yaffs
yaffs2
Your ramdisk needs to mount the partition with "-t auto" (or "-t ext3" if you don't want backwards compatibility) instead of "-t ext2" for it to be effective. My build is the only one that does this so far AFAIK. In the JF builds, you need to change the "runme.sh" script.
cyanogen said:
Your ramdisk needs to mount the partition with "-t auto" (or "-t ext3" if you don't want backwards compatibility) instead of "-t ext2" for it to be effective. My build is the only one that does this so AFAIK.
Click to expand...
Click to collapse
I'm guessing that wouldn't be an easy change to do? Well I guess I will have to try one of the new roms which supports this since JF doesn't update his releases like the other guys do
Beast84 said:
I'm guessing that wouldn't be an easy change to do? Well I guess I will have to try one of the new roms which supports this since JF doesn't update his releases like the other guys do
Click to expand...
Click to collapse
It requires a little bit of hacking.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
cyanogen said:
It requires a little bit of hacking.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Wow all I see is matrix code! Thanks anyway I will read up, see what I can make of it. Thanks for pointing me in the right direction at least
Does anyone know if the Behold II supports ext4 partitions? I know that BH_Man's roms support ext3 (which I currently use for apps2sd). Nu11u5 came out with a rooted kernel based on the 1.6 OTA update; however, it doesn't support apps2sd. I was thinking of upgrading my ext3 apps2sd partition to ext4 but I wanted to make sure that it will work first. I tried contacting BH_Man, but he hasn't responded yet.
Since no one has responded, I thought I would add what I found out about ext4 support in the Behold II [BH2]. According to the source code, It seems that the BH2's kernel does indeed have support for ext4; however, I was unable to verify that Samsung actually compiled their kernel with ext4 support.
Back in the old day, before Cyanogen and Amon_Ra's recovery, to upgrade an ext3 partition to ext4, this was all that was needed:
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -fpDC0 /dev/block/mmcblk0p2
When I ran those commands in recovery mode via adb, tune2fs refused to run because of a missing mtab file (meaning tune2fs couldn't verify that mmcblk0p2 was mounted or not). I could be that I needed to use a newer version of tune2fs (but I'm too lazy to compile it myself). Whatever I tried, tune2fs wouldn't run. I actually had to use Acronis Disk Director to upgrade from ext2 to ext3 as I ran into the same problem before btw. I decided to give up and just use ext3 for app2sd. It works well and the slow down isn't really noticeable. Plus I like the added bonus of the journal.
The moral of the story: When buying a phone, make sure there is an actively developed ROM for it (like Cyanogenmod). Otherwise, forget about hacking it.
I'm working in a method to increase SGY's internal /data partition. in my previous method I was using a modified kernel to load sdcard's ext paritition as /data. however, this kernel have bad issue with script manager. I've found the most easy easy way to increase our /data partition size in sgy. no need to install custom kernel, we'll need only a stock kernel with init.d support. with this new method we'll make a script '03data2sd' in init.d folder with these script inside
Code:
#!/system/bin/sh
umount /data
mount -t ext3 -o nosuid,nodev /dev/block/mmcblk0p2 /data
this method will solve my previous kernel incompatibility issue with script manager. however, the gps won't work with this method. the logcat file said that there was something wrong with gps_ril_BRCM. it said that 'RIL LCSAPI' isn't working. does anyone know how to fix it?
I will say this up front for all to read in big bold letters
I DO NOT KNOW IF THIS WORKS. I DO NOT HAVE A DEVICE TO TEST
I ran this through Koush's automated CWR creator located at http://builder.clockworkmod.com/
Touch Version:
https://docs.google.com/open?id=0B0ozkQsJWIScSjdqbEJvemJEU0U
Normal Version:
https://docs.google.com/open?id=0B0ozkQsJWIScUGVpZjdyT25YZ0E
recovery.fstab
Code:
# mount point fstype device
/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
fstab.grouper
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
Working or not, that is a damn good start. Thank you
Sent from my SPH-D710 using xda premium
Umm, this doesn't actually work that well, it forces you to use a USB stick as /sdcard and there's no back button.
P
paulobrien said:
Umm, this doesn't actually work that well, it forces you to use a USB stick as /sdcard and there's no back button.
P
Click to expand...
Click to collapse
Thanks, Paul! At least you confirmed things for me.
I did just use Koush's auto-builder, as my server hard drive crashed, so I couldn't use my own code.
use the cwm made by birdman.
Sent from my HTC Glacier using xda premium
smirkis said:
use the cwm made by birdman.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I rather wait till I get my own device, I can test my own builds before releasing them. I was just excited to give this a try.
Of course, someone might have this done before I get my N7 And if that is the case, I will probably be building a TWRP
Is it CWR (ClockWorkmod Recovery) or CWM ClockWorkMod .
Usually i use CWM.
imfloflo said:
Is it CWR (ClockWorkmod Recovery) or CWM ClockWorkMod .
Usually i use CWM.
Click to expand...
Click to collapse
Those are the same thing, correct me if I am wrong.
mmmcfc said:
Those are the same thing, correct me if I am wrong.
Click to expand...
Click to collapse
Yep. Both are same
Sent from my GT-S5670 using xda premium
imfloflo said:
Is it CWR (ClockWorkmod Recovery) or CWM ClockWorkMod .
Usually i use CWM.
Click to expand...
Click to collapse
Pwahahahah nice =)
Sent from my Nexus 7 using xda premium
We are CWM Touch official, upgrade through app($1.99) or download for manual install here (free)http://www.clockworkmod.com/rommanager
I just need to get the word out, now that I have seen this go from a couple user issue to maybe, getting out of control.....The new TWRP has a issue with formatting data, I have experienced this first hand. It ended for me in a softbrick, and a few users on the forums...I would never want this to happen to anyone.. Im sure TWRP feels the same.... Just be aware of the issue.. I have posted on there fourm page about the issue...Thx as always lj
sbdags said:
You'll have to format the data partition manually with the following in the terminal emulator under advanced in twrp.
mke2fs -T ext4 /dev/block/mmcblk0p8
Note you will lose everything on internal so move backups and your ROM zips to flash onto your micro SD.
Click to expand...
Click to collapse
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8