Related
I finally decide to have a partion on my 8GB SD other than FAT32. So i used the FuFu Minimod to split my SD. First to Ext2 then to Ext3 and then to Ext4.
It all went fine. I have moved some basic apps like Facebook and Igo to the Ext4 partion.
The weird thing that drove me to create this thread is the fact that my phone became a bit slow... unresponsive... and just because the Ext4 with basic apps on it?
Did i miss something or this is normal?
Appreciate all feedbacks.
WF
Sent from my Milestone using xda premium
Try wipe both Cache and Dalvik-Cache
Thanks... but is not the case... and yes i already did that before creating the thead.
Tks
Well then, manually move the app to the sdcard, then move back to the phone.
It should move into the ext4 partition.
They are all in ext4...
Sent from my Milestone using xda premium
wisefreakz said:
They are all in ext4...
Sent from my Milestone using xda premium
Click to expand...
Click to collapse
I know it is inside ext4. Please try to move to the sdcard and back to the phone again.
I did face this b4
I have done that before you mention... and it looks like its a bit more stable.
One doubt... i notice that all sd-ext\app files are alson in data\app.
Why is that?
Sent from my Milestone using xda premium
Why
Is ext4 faster or what ?
Im kinda noob on this android and stuff things, so i donno.
I can put my apps on SDcard without formatting to ext2, 3 or 4.
Well, now after billions of testing, formating, reflashing... all looks pretty nice now.
@ivanotera: moving apps to sdcard is not the same as moving apps to a second partition where this second partition is journaled - case of ext4.
It means that when you boot your phone, this partition is ready to use and does not need to be "prepared" as the usual fat32 - thats why we see the message after boot up that sd card is being prepared (in fact the OS is checking if the partion is corrupted or not.
Also when moving apps directly to sd card like you are doing, is not good as phone becomes slow, widgets, shortcuts dissapear while booting phone and while phone is connected to pc via usb with sd mounted for access.
With ext4 (using ext4.ko module) OS will think that this second partition is part of the internal storage and all of the above mentioned will not be a problem anymore and you will not get that anoying message that you have not enough space just because you added a couple apps.
Hope this can clarify some important things.
Cya
Sent from my Milestone using xda premium
Yeah, got it.
But another question, is ext4 "viewable" by windows ?
Because i have a 32gb card, so i use it as a "pen drive", have some apps so when i format a pc, not at home, i have some apps already, and dont have to download it.
Or in the case of creating a ext4, i partition the sdcard, so i have the "apps" partition and the "windows" partition ?
I recently had to Run the repartition un-superbrick guide, Where I had to change the Start and end Point of the UMS partition.
After a long battle, I Managed to get a rom Running (Stock ics German open lpy).
The effects of the restoration Process were as follows:
Random Freezes, which require Force reboot. seems to be prone to them right After boot.
The Freeze occurs also when installing any App from play Store. However, I Was able to install SwiftKey 3 via apk.
The Internal sdcard is only 8gb on size, Where it used to be 11.
Any Ideas what to do?
Bump.. No one has any Ideas? :/
+1 same here would love to know as well. Only mine freezes after some multitasking not exactly like yours.
Sent from my GT-N7000 using xda premium
Same issue here. My UMS is 4 Gb. I think is problem of data partition but i restored it about 10 times. I'm running G&B ICS rom
Try to ODIN back to stock Gingerbread, root, and flash a safe CM9 rom.
Edit:
Or stay on Gingerbread. See if you still have freezes.
After restoring from brick, i installed GB stock from my operator and still freezing ramdomly, once was cuz i did multitasking, another one cuz i installed apps from market.... Cyanogen the same, i'm thinking that another partition is bad, but cache is good:
Here my modified values:
mkpartfs primary ext2 5000 6100
mkpartfs primary ext2 9000 11000
mkpartfs primary fat32 11500 15200
name 9 FACTORYFS
name 10 DATAFS
name 11 UMS
Hello
Did you find a solution I got the same problem but I don't know what I can do to solve it
I have the same problem. Anyone can solve it?
im experiencing the same situation, perhaps any solution/findings?]
Install cm based rom from gb, they use around 100mb space instead of 600mb. The issue here is that you're maxing out your reduced partitions so stock roms will struggle.
Sent from my GT-N7000 using xda premium
Changing rom is a good idea.
Another idea is to use tool under adb to check partitions. Use e2fsck with -c option to scan the partitions 7, 9, 10 to see if it find bad blocks and sometimes can fix them. If it reports no bad blocks find, that means those partitions are ok. Some time it find bad blocks and could fix or mark them, then we do not need to do re-partition again. (it will tell kernel to avoid those faulty blocks). If e2fsck freezes then there are serious fault it cannot fix and will requires more re-partition. It also no harm to check partition 11 as well, using dd/parted tool. Hope it may help. cheers.
I have my phone unlocked and rooted and have used Big Bear's Iconic rom to flash my phone. This completed fine but part of the process after flashing describes flashinf with data2sd ext3 script. When i tried this I realised my sdcard was formatted fat 32 and not ext3. My desktop machine uses ubuntu linux and I wondered if its possible to format the card via terminal or some piece of software and in what proportions should i partition it to extend my salsa's pitiful internal memory. Also when this is done does the script need to be on a particular partition or just somewhere on the card.
If its easier to configure the card via windows I also have a winxp laptop that could do the job.
Any help greatly appreciated.
bean12345 said:
I have my phone unlocked and rooted and have used Big Bear's Iconic rom to flash my phone. This completed fine but part of the process after flashing describes flashinf with data2sd ext3 script. When i tried this I realised my sdcard was formatted fat 32 and not ext3. My desktop machine uses ubuntu linux and I wondered if its possible to format the card via terminal or some piece of software and in what proportions should i partition it to extend my salsa's pitiful internal memory. Also when this is done does the script need to be on a particular partition or just somewhere on the card.
If its easier to configure the card via windows I also have a winxp laptop that could do the job.
Any help greatly appreciated.
Click to expand...
Click to collapse
yeah it would be easier via windows, i still not found software on Ubuntu to do the partitions lol.
just copy the data2sd-ext3.zip onto your sd card that's all and flash from there. you only need a small 1gb partition max on the sd cad the rest in fat32.
Cool will give that a try tomorrow and let you know how it goes
Worked a charm thanks I do have a couple of question though if i may. Although working with no probs the script mentions preparing the partition with ext2 (I used ext3) and an app called busybox to be installed into system/xbin. What does this app do and is it needed.
Also is this script tailored to the salsa or can it be used on other android devices to achieve more internal memory?. My Desire has the same issue you see.
Thanks in advance for all the help
Yes busybox is requiredlol, otherwise it wouldn't work. We never changed the txt over from ext2 but its still the same and works on both anyway. As for desire....I have no idea, this was based on wildfire s/salsa only, try it out see what happens lol
Busybox is part of the superuser setup without this builtin or added in we wouldn't have root at all. Deleting it would cause issues too.
BigBear is using Xparent Tapatalk Purple
Busybox is part of the superuser setup without this builtin or added in we wouldn't have root at all
Click to expand...
Click to collapse
So given my phone is rooted (thanks to your help a few weeks ago) I take it I must already have this Busybox installed otherwise the script would have failed correct?
I partitioned my test 1 gig sd card into two equal parts one ext3 and one left fat32, the phone reports equal portions on sd card and internal memory via the Settings----> Storage menu. So I'm assuming all is well.
Yeah busybox will already be there lol. That's all fine on the SD, but just be aware, the lower the class SD your using, I assume its a 2gb, you may have a class 4, which will lag. If you experience lag, reduce the ext3 size to 500mb you will see a difference.
BigBear is using Xparent Tapatalk Purple
Is there any difference between data2sdext3 and data2whatever? If yes which one is better to flash with a custom ROM (I am using Bear's XSeries V11).
(Data2ext3 is causing problems for me. Crashing various apps time to time. Using a class 4 sdcard with 470 MB partition. Found data2whatever on Razer's ROM page)
razasohail said:
Is there any difference between data2sdext3 and data2whatever? If yes which one is better to flash with a custom ROM (I am using Bear's XSeries V11).
(Data2ext3 is causing problems for me. Crashing various apps time to time. Using a class 4 sdcard with 470 MB partition. Found data2whatever on Razer's ROM page)
Click to expand...
Click to collapse
A big difference between them.data2SD ext3 is designed for non apps2SD roms ie mine, data2whatever is for apps2SD roms only.if you're having force close issues then you didn't install something correctly. Using these scripts on the wrong Rom could have adverse affects in the Rom.
Each Rom made will have the correct script to use in the listing. If you choose to use them the opposite way round then the developer won't help you correct the problems I'm afraid, all I can suggest is redo the Rom of your choice till it works correctly.
If your having problems with mine, post up in the thread as long as your using the setup I gave and I'll help as much as I can.
For force close issues you can always use fix permissions in Rom manager or in recovery advanced section, this normally stops them.if it dont reinstall them Rom. It tends to be a user error when this happens, I'm using my own Rom and never get force close problems.
BigBear is using Xparent Tapatalk Purple
I've searched and found a lot of topics on App2sd, data2sd and Link2sd.. after reading all I've come to the conclusion that Link2sd is the one to gos for.. But, I've seen a lot of link2sd apps.. want to know which is the original..
Also, do let me kno which will the best format for the 2nd partition on galaxy ace(ext2,ext3 or ext4) on stability and speed..
Just tell the right steps to follow for using link2sd..
Sent from my GT-S5830 using xda premium
Anyone..plz provide me the solution..
Thank you
Sent from my GT-S5830 using xda premium
varunmehta11 said:
I've searched and found a lot of topics on App2sd, data2sd and Link2sd.. after reading all I've come to the conclusion that Link2sd is the one to gos for.. But, I've seen a lot of link2sd apps.. want to know which is the original..
Also, do let me kno which will the best format for the 2nd partition on galaxy ace(ext2,ext3 or ext4) on stability and speed..
Just tell the right steps to follow for using link2sd..
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
1) create a partition using CWM in advance section of recovery(swap size 0 M) 512 mb is sufficient
2)download app link2sd from market
3)open it...and choose partition type of ur choice (ext4 works well )
4)finally click on any app saved in internal memory and click on CREATE LINK
5)You are done! :beer:
Ask if any problem...
Press thanks if i helped :thumbup:
Ext2/Ext3 is pretty much the same using default settings (unless you enable journaling in ext3). Ext4 adds journaling.
Ext2 is the most friendly for SD life. Ext4, not as much, but it has other perks (GIYF).
Also, you might want to show apps installed on the SD Card, select them all then Create Link first. It'll save you some extra space and re-enable widgets if available. Then you can move your internal apps if you want.
GermainZ said:
Ext2/Ext3 is pretty much the same using default settings (unless you enable journaling in ext3). Ext4 adds journaling.
Ext2 is the most friendly for SD life. Ext4, not as much, but it has other perks (GIYF).
Also, you might want to show apps installed on the SD Card, select them all then Create Link first. It'll save you some extra space and re-enable widgets if available. Then you can move your internal apps if you want.
Click to expand...
Click to collapse
I didn't understand what did u mean by show apps installed on SD card and select them, create link.. Do I have to Create link also for apps already stored in SD card..
And, I think Ext3 will be the best for.. what say?
Sent from my GT-S5830 using xda premium
varunmehta11 said:
I didn't understand what did u mean by show apps installed on SD card and select them, create link.. Do I have to Create link also for apps already stored in SD card..
And, I think Ext3 will be the best for.. what say?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Once you have Link2SD installed, you can select "SD Card" as a filter. It will show all apps installed on the SD card. It would be a good idea to link these apps ("Create Link") (thus moving them back to phone storage, and then again to the SD Card, but to the 2nd partition this time) for three reasons:
You can move the dalvik-cache as well, which means you'll save extra space.
If the app has widgets, you'll be able to use them again (e.g. SoundHound).
Should you mount your SD card to the PC, the apps will still be available since the 2nd partition doesn't get mounted.
I've tested Link2sd.. Only Ext2 gets detected and mounted to be used in Link2sd.. Ext3/4 doesn't get mounted.( I'm using the Stock kernel)
On stock kernels ext3 and ext4 not always work, fat32 or ext2 always work. Its ok, won't make a real difference, the class of the sd card has way more impact on performance.
If you want you can create partition (with ext4) with minitool partition on your pc. (see this thread : http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning)
Same problem, even if partition is formatted as ext4, Link2SD defaults to ext2. I have had a few times where it loses link by itself and all linked apps stops working.
Ext4
If you want to get your ext4 mounted. You must make a partition as ext4 to (I use partition wizard).. Not ext3, or ext2, or either..
I am sorry for my bad english..
Gizmotech said:
Same problem, even if partition is formatted as ext4, Link2SD defaults to ext2. I have had a few times where it loses link by itself and all linked apps stops working.
Click to expand...
Click to collapse
I've had this especially when restoring nandroid backups. The 05mountsd script in the init.d folder of some roms creates a conflict with Link2sd. Simply delete that script, problem solved.
Sent from my GT-S5830
NaraRockingMyAce said:
If you want to get your ext4 mounted. You must make a partition as ext4 to (I use partition wizard).. Not ext3, or ext2, or either..
I am sorry for my bad english..
Click to expand...
Click to collapse
I did format it as EXT4 with MiniTool but mounts as EXT2 on Link2SD upon reboot even after choosing EXT4.
mitchst2 said:
I've had this especially when restoring nandroid backups. The 05mountsd script in the init.d folder of some roms creates a conflict with Link2sd. Simply delete that script, problem solved.
Sent from my GT-S5830
Click to expand...
Click to collapse
I don't have and Init.d support or scripts
Hi,
I have the Virgin Mobile 510, which I have rooted w/ TWRP recovery, still stock otherwise.
I've also created a 1g Ext2 partition in a 32g memory card using MiniTool Partition Wizard
I cannot get the #$!*% card to mount at boot! I want to use Link2sd, of course, so that I can use the Ext2 partition for apps. I've been hammering away on this all day, and I can't seem to figure out what I'm doing wrong. I've re-installed Link2sd numerous times, rebooted numerous times. Extensive googleing (google-ing?) has only confused me more.
Any help would be much appreciated! This is my first time trying this sort of thing.
jamesbarratt said:
Hi,
I have the Virgin Mobile 510, which I have rooted w/ TWRP recovery, still stock otherwise.
I've also created a 1g Ext2 partition in a 32g memory card using MiniTool Partition Wizard
I cannot get the #$!*% card to mount at boot! I want to use Link2sd, of course, so that I can use the Ext2 partition for apps. I've been hammering away on this all day, and I can't seem to figure out what I'm doing wrong. I've re-installed Link2sd numerous times, rebooted numerous times. Extensive googleing (google-ing?) has only confused me more.
Any help would be much appreciated! This is my first time trying this sort of thing.
Click to expand...
Click to collapse
Usually that means you're on a stock "write-protect on" kernel. Try flashing Rhinestone kernel and that should solve your error.
jamesbarratt said:
Hi,
I have the Virgin Mobile 510, which I have rooted w/ TWRP recovery, still stock otherwise.
I've also created a 1g Ext2 partition in a 32g memory card using MiniTool Partition Wizard
I cannot get the #$!*% card to mount at boot! I want to use Link2sd, of course, so that I can use the Ext2 partition for apps. I've been hammering away on this all day, and I can't seem to figure out what I'm doing wrong. I've re-installed Link2sd numerous times, rebooted numerous times. Extensive googleing (google-ing?) has only confused me more.
Any help would be much appreciated! This is my first time trying this sort of thing.
Click to expand...
Click to collapse
connect your sd card with computer and using minitool partition wizard to set the ext2 and link2sd partition as primary.
leafwarbler said:
connect your sd card with computer and using minitool partition wizard to set the ext2 and link2sd partition as primary.
Click to expand...
Click to collapse
The answer that @LarryBoyG gave him was the correct one as I've been through this myself and without a kernel with write protect not removed this suggestion won't do no good!
ALSO, I'm really curious as to WHY you are replying to a post that's NINE(9) months old as if it hasn't been solved by now lmao..