Related
Hi there people i just flashed the [ROM][New Sense HD][01 Feb]Z v2.0 D2Ext - Lightning quick !!
from http://forum.xda-developers.com/showthread.php?t=837948
The other roms ive used have not have space problems but this one doesnt seem to work for me. They ahve been a2sd+ and not d2ext
I have a 16 GB Kingston Cat10 card ive partitioned like this.
10gb fat32, 4gb ext4, 1gb ext4, 1gb swap
I figured that would leave me with plenty of space for apps.
But when i try to install android agenda widget it tells me i dont have enough space on the device that seems odd doesnt it? Or should i have gone for a2sd++ instead of d2ext ?
The only reason i rooted was due to lack of space for apps.
Not exactly sure what went wrong but your ext partitions are ridiculously big and I belief you run in to issues with partitions bigger than something around 2Gb.
Try ext partitions accordion to the recommend sizes or at least stay under 2Gb and try again.
On top of what the fella mentions above (he's right), sometimes you get this error with that ROM when you have concurrent downloads ensuing. It's a false call. Let all your installs finish before reinstalling. It should work the second or third time in my experience.
------------------------------
- Sent via HTC Desire -
I might have found the problem but not a solution.
Doesnt realy matter how i partition wipe all partitions and so on.
When i boot recovery with clockwork and flash update.zip i go to wipe/system reset and it tells me the following:
Error mounting SDEXT:!
Apparently it whont mount my ext partition i can mount everything else.
Partition table is now:
11GB Fat32, 2GB Ext4, 1GB ext4 1GB swap.
EDIT.
Might have been semi solved, i flashed a new rom RCS MixHD v2.0
Seems like its basicly the same.
The phone runs and the apps seems to be installed on sd.
Still the same problem in clockwork though.
Might be a stupid question.
Well here's the deal i partitioned my sd card to ext4 (i think i'm not sure how i can find it out if it is ext3 or ext4). I was reading that ext2 was faster and quite better than ext3 or ext4 so i was thinking is there any easy way to deconvert from ext4 to ext2. What is the best way to do this preferably without loosing any data from sd card or the partition?
And how can i find out easily what partition my sdcard is ext3 or ext4?
Im not sure where you get that information but devs wouldn't recommend EXT4 partition if its gonna slowdown the performance of their roms.
I bet gparted can tell what type of ext partition you have and I bet there are other ways to find out... You can flash 4Ext Recovery and that will show you those information as well.
via xda app
4ext recovery converts partitions but only between ext3 and ext4 without data loss. Al though I am scratching my head, where did you read that ext2 is faster than others?
Ext4 has more features than Ext3 and Ext2, main advantage is journaling which gives improved performance and reliability. The only downside with ext4(also ext3) is that the SD Card wears out faster since it can perform more read/write activities. If I was you I would keep things the way they are.
deadlyboss01 said:
4ext recovery converts partitions but only between ext3 and ext4 without data loss.
Click to expand...
Click to collapse
I know but I believe it would be able to tell what type of Ext partition the sd card has
via xda app
I saw something about it on androidforums.com and somewhere else i can't remember where.
There few people said that after going from ext2 to ext3-4 the rom that they had became a little laggy and it said also that some kernel dev said to use ext2 rather than ext3-4.
Also said the same thing you deadlyboss01 said about the sd card wearing out sooner.
Is it maybe silly to use ext2 if i already have ext4?
And if i set up 4ext recovery can i restore nand backups from cwm?
And if i set up 4ext recovery can i restore nand backups from cwm?
Click to expand...
Click to collapse
I believe it can since 4ext recovery is based on cwm but better post the question on the 4ext thread to get an accurate answer. Sorry im not that sure.
via xda app
It seem that you are quite adamant. Have you personally experienced these lags?Also, I had the impression that kernel devs focused more on ext3/ext4. Nevermind, CWM is indeed compatible with 4ext recovery as Stankyou said.
No i personally have not had these lags but it seems that i'm just going to stick to 4ext and try to flash the 4ext recovery and check that out
Thanks to this thread(and others), i got some balls and knowledge. And i've installed, 4eXT Touch Recovery and then converted my ext3 partition to ext4 with 4eXT, way to easy. Needless to say, that Recovery is awesome! Thanks People! !
I also read this on ext2 being better and was confused, some guy had a htc incredible s and experienced lag with ext4 and not on ext2.
Well, i also see alot of devs using ext4 and now this thread... think this is quite simple, Use ext4 if the rom supports it.
I had a problem on the cm7.2 before and I was fedup and switched to the cm9.
Now again I installed the cm7.2 and again the problem seems to be arrising.
I used the s2e on cm7.2 it worked fine. But I was installing the apps from the market and when the message comes "installing" the mobile restarts. Sometimes one or more boot loops occurs.
When the cell swtiched on so i searched in the app drawer the s2e was missing. It disappeared.
This same problem also occurs with the dtapps2sd. After few days or hours, when i install any application either from market or sd card the mobile restarts.
The only soultion to this problem is just factory reset.
I have been using the cm9 with the s2e enabled I was having no problem like this.
I have tried many things like repartioning etc. etc.
I had been experiencing this problem a month ago, and i was not able to find the reason, so today i installed the s2e on the cm7.2 and just figured out that this problem occurs due to the reason that s2e or the dtapp2sd disappears automatically.
Any solution and reason for this, will be appreciated.
Just waiting...
I had the same issue on CM7.2. It turned out that the problem was that my sd-ext partition is not formatted as ext4 but ext2 instead. Make sure that you partition is formatted as ext4. If it's not, then re-format it but do NOT use the recovery but do it on your PC using a card reader as the recovery messes things for some reason and formats partition as ext3 on my case. Also make sure that you do NOT use the 'Set read buffer' option in S2e as this tends to corrupt the partition. Phiexz had mentioned this in his thread, I think. This helped me solve my problem, hope that it will do the same for you as well.
Once you fix the issue, I would not recommend you to move the application data (/data/data) to sd-ext as this causes poor performance. Just an advice
Sent from my GT-S5660 using Tapatalk
Nytmarez said:
I had the same issue on CM7.2. It turned out that the problem was that my sd-ext partition is not formatted as ext4 but ext2 instead. Make sure that you partition is formatted as ext4. If it's not, then re-format it but do NOT use the recovery but do it on your PC using a card reader as the recovery messes things for some reason and formats partition as ext3 on my case. Also make sure that you do NOT use the 'Set read buffer' option in S2e as this tends to corrupt the partition. Phiexz had mentioned this in his thread, I think. This helped me solve my problem, hope that it will do the same for you as well.
Once you fix the issue, I would not recommend you to move the application data (/data/data) to sd-ext as this causes poor performance. Just an advice
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
1st thanks for the reply.
My partition is ext4.
While the factory reset the recovery formats the partition, i hope so it doesn't change its type from ext4 to any other.
I am not moving the application data
I am not changing or messing with the buffer option
I don't know what to do, I don't want to switch again to cm9 because it is still in development stages, alot of functions are not working while some have bugs.
As I said, format the partition on a PC instead. The recovery does not format it properly for some reason. The reason that S2e and A2sd disappear are moved to an incorrectly mounted partition as it is either not ext4 or it's corrupted. I thought mine was ext4 until i looked at it on my Pc using a partitioning software.
Sent from my GT-S5660 using Tapatalk
Nytmarez said:
As I said, format the partition on a PC instead. The recovery does not format it properly for some reason. The reason that S2e and A2sd disappear are moved to an incorrectly mounted partition as it is either not ext4 or it's corrupted. I thought mine was ext4 until i looked at it on my Pc using a partitioning software.
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
Oh thanks Now I checked in the pc it has been changed to ext3.
It is just horrible, how come it changed. I didn't created a partition using the recovery.
I just did factory reset. And during factory reset the recovery automatically formats the ext partition and changes it to ext3...
It is a big bug of the recovery , And it has to be solved because we can't do factory reset as it will change the ext type
I am using the recovery 5.7.2 version
BTW should i check the read buffer in the s2e?
Yeah, that's what I meant. I had the same issue and i was surprised just like you how the ext4 partition had been converted to ext3. I would recommend using px recovery 0.3.6 instead of this old cwm. I cannot tell you whether this problem occurs with it because i flashed it after i managed to fix my problem. Do not set the read buffer in s2e as a lot of people, including me, report that this tends to corrupt your partition too which leads to the same problem that you're currently experiencing (CM not able to mount sd-ext). Did that fix your problem?
Sent from my GT-S5660 using Tapatalk
Nytmarez said:
Yeah, that's what I meant. I had the same issue and i was surprised just like you how the ext4 partition had been converted to ext3. I would recommend using px recovery 0.3.6 instead of this old cwm. I cannot tell you whether this problem occurs with it because i flashed it after i managed to fix my problem. Do not set the read buffer in s2e as a lot of people, including me, report that this tends to corrupt your partition too which leads to the same problem that you're currently experiencing (CM not able to mount sd-ext). Did that fix your problem?
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
Yeah the problem is fix now
Thanks alot man for your quick help
Sent from my GT-S5660 using xda premium
Great. Glad that this worked for you too.
Sent from my GT-S5660 using Tapatalk
I was just curious as to what everyone thought would be the best file system to use for the 2nd partition for link2sd. I did some light searching and didn't really find any answers specific to Xperia Play (or even in general). From my understanding stock firmware on Xperia Play does not support ext4, so I would assume ext3 would be the best chose, but I just wanted to get some other's opinions.
Options for those who don't know and don't wanna search are ext2, ext3, ext4 or FAT32.
I like ext4, it's like Windows' NTFS. Fast mounting and protects against file corruption after a crash/sudden shut down. Ext2 is the simplest, and some say the fastest because of that, though it doesn't protect against corruption. I'd say worst is FAT32 for the 2nd partition, seeing as it wouldn't mount any more quickly than the 1st partition would.
I use ext3
Sent from my Xperia Play using Tapatalk 2
jacklebott said:
I like ext4, it's like Windows' NTFS. Fast mounting and protects against file corruption after a crash/sudden shut down. Ext2 is the simplest, and some say the fastest because of that, though it doesn't protect against corruption. I'd say worst is FAT32 for the 2nd partition, seeing as it wouldn't mount any more quickly than the 1st partition would.
Click to expand...
Click to collapse
I agree with using ext4, but I was under the impression that default firmware on xperia play doesn't support it...?
EDIT: I tried ext4 and it was unable to mount. ext3 however worked fine.
EarthBoundX5 said:
I agree with using ext4, but I was under the impression that default firmware on xperia play doesn't support it...?
EDIT: I tried ext4 and it was unable to mount. ext3 however worked fine.
Click to expand...
Click to collapse
My is stock ROM 2.3.4 with doomkernel, link2sd using ext4 and it's working.
one thing is really annoying me, I moved most of apk/lib/dex to 2nd partition & it saved 150MB from ROM space
But every time i reboot phone, it takes like 10min to enter home page, when it was app2sd, it only takes 2min
my sd card is samsung 32g c10
1 FAT32 Partition 29gb
1 EXT4 Partition 2gb
1 SWAP Partition 256mb
i am using ext2 on my x10 and xplay
I was using FAT32 and then it just stopped mounting randomly. Would i be able to change the type of the partition whilst keeping everything in tact?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Hi there,
I am using Sandvold ICS 0.15 rom for a while. Yesterday i switched the phone off to charge the phone.
Once fully charged, i switched the phone on and it got stuck on the blue X for a long time. I had to try the battery pull and it still had the same issue.
I then performed wipe data/factory reset, wipe cache, wipe dalvik cache. I then reinstalled the rom.
After it booted up etc, i ran a2sd install, y, n, y. It stuck at the boot screen again. I waited for 30 mins and i then realised something is wrong. So i then had to go into recovery menu and do a full wipe and restart again.
At the moment i do not have a2sd enabled.
I am using EXT4 partition. I created it back in July using GParted.
Now in terminal emulator i ran the following commands to investigate what is causing this boot issue:
# mount | grep sd-ext
# /dev/block/mmcblk0p2 /sd-ext ext4, rw, nosuid, nodev, noatime, nodirtime, nousr_xattr, commit=15 barrier=1, data=ordered, noauto_da_alloc 0 0
What does the above mean?
If i dont mount the sd-ext and run the a2sd diskspace command it states that 16MB but my question is how can it if i havent mounted it?
I have also ran the command a2sd checkext and i get the following results
Found block device /dev/block/mmcblk0p2
/sd-ext is mounted
Is there a problem with my SD-EXT partition?
If somebody could assist me please, i would greatly appreciate it
Thanks in advance,
Format and repartition your sd card. That should do the trick.
Try INT2EXT4+
If you don't mind having all your apps installed on your sd transparently, use a script like INT2EXT4+ that mounts your sd-ext partition to /data. Now the sd-ext partition functions as the "internal" /data partition, the internal /data partition itself is mounted to /data/data (for increased speed). The script works very well with sandvold ics and is imo better than a2sd. I use(d) it myself with various ICS and JB roms (including sandvold's), works great.
Download the int2ext4+ script zip to your sd, flash your (ICS) rom and flash the script straight afterwards. The script also zip-aligns your apps at every boot.
Hi there!
I don't remember exactly, but I had the same problem with Sandvold ROM; I've solved updating to the last release 0.18.2.1.
In the past releases, I used another kind of a2sd, whitout (for me) satisfaction.
I do confirm, with the last everything work fine!
Thanks for the suggestions all.
I deleted my ext3 partition and created a new one using GParted. Now the phone works fine, i can get pass the boot screen and use the phone :laugh:
If i switch my phone off and turn it back on does it have any impact on sd-card when app2sd is enabled?
If it does will int2ext4+ script solves that problem.
If i want to use int2ext4 now do i need to start from scratch since i now have the rom installed with app2sd enabled?
Can you direct me where i can find the script on this forum please?
Thanks
I don't exactly know what happens in the background with a2sd (I know it moves apps to sd-ext and makes symlinks, but dunno what else...) but if you have enough internal memory on the /data partition to move all apps back to internal, I would try to first disable a2sd from the console and then reboot into recovery and flash the int2ext4+ script (is your sd-ext ext4 now?!).