I switched from CM10 to CM9 (the most stable one) on my WFS because my Int2Ext+ script was getting unmounted after 3 to 4 reboots on CM10. I was told that switching to CM9 would fix this as CM10 is still very much in Alpha. But today, after 350MB of my int2Ext+ was filled (on CM9) , my phone asked for a restart and i returned back to having the original internal of 150mb and all my settings were gone too and the 1st boot screen appeared too. Now my question is, is it due to me installing Swapper-2 (which was the last application i installed and i suspect that it was the case in CM10 too) or is it that our WFS cannot take more than 350mb even on int2ext+ !! please help, cause this is getting tedious ! :crying::crying::crying::crying::crying::crying::crying:
Xenux92 said:
I switched from CM10 to CM9 (the most stable one) on my WFS because my Int2Ext+ script was getting unmounted after 3 to 4 reboots on CM10. I was told that switching to CM9 would fix this as CM10 is still very much in Alpha. But today, after 350MB of my int2Ext+ was filled (on CM9) , my phone asked for a restart and i returned back to having the original internal of 150mb and all my settings were gone too and the 1st boot screen appeared too. Now my question is, is it due to me installing Swapper-2 (which was the last application i installed and i suspect that it was the case in CM10 too) or is it that our WFS cannot take more than 350mb even on int2ext+ !! please help, cause this is getting tedious ! :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
See, because of INT2EXT+'s script, it leaves some data on the real internal memory. That's why CronicCorey in his 1st post has listed in the requirements: 100mb internal is required for every 500 mb ext. That's the case for INT2EXT+ and int2ext4+.
So, I suggest you move to INT2EXT (no plus). It moves all to external, so your internal isn't used at all. I am using it myself on my personalized stock ROM. It works flawlessly.
Good luck.
Purposely Burnt From My Epic Toastfire S Unlocked, Rooted and Now Powered By Premium Tomaytos
Tyr Fifteen said:
See, because of INT2EXT+'s script, it leaves some data on the real internal memory. That's why CronicCorey in his 1st post has listed in the requirements: 100mb internal is required for every 500 mb ext. That's the case for INT2EXT+ and int2ext4+.
So, I suggest you move to INT2EXT (no plus). It moves all to external, so your internal isn't used at all. I am using it myself on my personalized stock ROM. It works flawlessly.
Good luck.
Purposely Burnt From My Epic Toastfire S Unlocked, Rooted and Now Powered By Premium Tomaytos
Click to expand...
Click to collapse
Okay, to move to a new script, it says, you should delete the old script first. Now, will formatting the sd-ext in the recovery wipe it off or how do i delete the script to add the new one ?? And are you sure i can go beyong the 350mb mark!
Related
Since I am not allowed to post in the development forum, I am making a new thread here. I just flashed the rom. Followed the instructions, partitioned, installed, rebooted and installed A2SD then rebooted. The performance is terrible. Gmail crashes. And I got continuous messages of com.android.acore (and com.android.phone) is not responding. At a time these pop ups, stop but running apps like the market or even People is very slow. I checked and it consumes hell lot of RAM, only 83mb are free or 140 after a few "kills". A lot less than the 220mb of stock froyo. I am not sure what kills the performance though. Is this normal for this rom?
I had the same issue, after a few hours of putting up with it I gave up and flashed CM7.1 instead
Sent from my CM7.1 Desire using XDA Premium App
At least you guys got it to work. I kept getting bootloops when I tried it.
I reflashed it. Now it seems I achieved a more proper installation. What I mean? Some widgets like the friendstream or the people widget are installed by default to some of the Sense "tabs" or however these are called. At my first installation all Sense tabs were blank. Overally, it seems more responsive, I still get the errors at boot but not at the same amount. Again, its speed is not like the stock rom though. So tomorrow I will flash another one. Any suggestions? I want something fast with 720p recording support.
Well I'm on CyanogenMod 7.1 and its very fast and stable. Its quoted as having 720p recording but some people are debating that, I haven't actually checked yet. It is an aosp ROM though so no sense.
Sent from my CM7.1 Desire using XDA Premium App
I had that issue before, apps take a minute to load.
Solution:
1. Make sure u have class 4 or higher SD card (no class 10).
2. Have at least a 1gb ext4 partition (1024mb, not 1000mb) I had 519mb before, changed to 1gb and its ok now.
3. Create FAT32 before you create ext4, won't work the other way around.
4. Try fix permissions in Rom manager to fix the force close issue.
Sent from my HTC Desire using XDA App
Or maybe u have a corrupted zip file. (somehow)
Sent from my HTC Desire using XDA App
muku_ said:
Since I am not allowed to post in the development forum, I am making a new thread here. I just flashed the rom. Followed the instructions, partitioned, installed, rebooted and installed A2SD then rebooted. The performance is terrible. Gmail crashes. And I got continuous messages of com.android.acore (and com.android.phone) is not responding. At a time these pop ups, stop but running apps like the market or even People is very slow. I checked and it consumes hell lot of RAM, only 83mb are free or 140 after a few "kills". A lot less than the 220mb of stock froyo. I am not sure what kills the performance though. Is this normal for this rom?
Click to expand...
Click to collapse
Did you full wipe before flashing?
To full wipe, you must;
Factory wipe/reset
Then in mounts/storage; format Data, format dalvic, format system and format sdext.
Then in advanced; Wipe Dalvic cache.
What has happened, is remnants of whatever previous ROM(s) you came from have remained in the system. Performing full-wipe above clears everything for your new ROM.
Not always necessary when flashing updates of the same ROM, but definitely a good idea if switching to another...
777ace said:
Did you full wipe before flashing?
To full wipe, you must;
Factory wipe/reset
Then in mounts/storage; format Data, format dalvic, format system and format sdext.
Then in advanced; Wipe Dalvic cache.
What has happened, is remnants of whatever previous ROM(s) you came from have remained in the system. Performing full-wipe above clears everything for your new ROM.
Not always necessary when flashing updates of the same ROM, but definitely a good idea if switching to another...
Click to expand...
Click to collapse
I definitely didn't do a full wipe. I only did the factory reset and i installed after. I was in stock rom before, I don't know if this is relevant to the full wipe. Anyway, I'll try that and see if it fixes the speed problems.
sebastianlow said:
I had that issue before, apps take a minute to load.
Solution:
1. Make sure u have class 4 or higher SD card (no class 10).
2. Have at least a 1gb ext4 partition (1024mb, not 1000mb) I had 519mb before, changed to 1gb and its ok now.
3. Create FAT32 before you create ext4, won't work the other way around.
4. Try fix permissions in Rom manager to fix the force close issue.
Click to expand...
Click to collapse
I fixed the permissions via the recovery menu. I also did the partitions via recovery, so I guess the procedure should be good. 1gb of ext, 64mb swap and the rest Fat.
I was about to order a new sd, because I use the stock one, 4gb class 4. I was thinking about getting a class 10, why did you tell me to avoid class 10? It should be the fastest, no?
Ok I reinstalled after wiping everything except boot from the recovery. Still the same issues. What I have noticed, is that the first time Gingerburst boots, when everything is in phone memory, the phone is fast. With no lags. After I reboot, to install the A2SD zip and then i start again my phone, then the performance sucks. Could it be the sd card? It's the stock card, class 4. Could it be the partitioning? I did it from the recovery. 1gb ext partition, 64mb swap, the rest Fat. Could it be the script installing A2SD problematic? I downloaded from the gingerburst site.
Droidzone highly recommends to do the partitioning with Gparted. Also the R/W speed of your card matters a lot in the speed of the ROM. My stock SD card has a writing speed of 4MB/sec and 5MB/sec for reading. This is definitely too slow to support data2sd, that's why I have ordered a class 6 sd card. You should do it too
UltimateGoblin said:
Droidzone highly recommends to do the partitioning with Gparted. Also the R/W speed of your card matters a lot in the speed of the ROM. My stock SD card has a writing speed of 4MB/sec and 5MB/sec for reading. This is definitely too slow to support data2sd, that's why I have ordered a class 6 sd card. You should do it too
Click to expand...
Click to collapse
I tried gparted at first but the gparted live disk didn't recognize my phone connected to the usb, so I then tried from the recovery. By the way why's everyone suggesting class 6 instead of class 10 sd cards?
Forget GingerBurst, it's a very laggy Gingerbread ROM. If you want Gingerbread with Data2SD, go for SuperNova (also by droidzone). I've experienced what you've experienced (lag, bootloops, fc's) despite my full wiping before flashing the ROM. My SD card is also partitioned by GParted, and it's Class 4 only, but I manage 1800+ Quadrant score w/ it. I went back to StarBurst (froyo) after consistently testing it to be faster than either GingerBurst or SuperNova. droidzone himself uses StarBurst for his personal phone.
No nid swap partition
Sent from my HTC Desire using XDA App
Droidzone said no class 10 :/
Sent from my HTC Desire using XDA App
Damn I guess it's the rom itself then. Although for some reason the lag starts after i install the A2SD. The first time the rom boots, before i install the script for data to sd, everything's pretty fast. I will order in any case a 16gb class 6 sd which i need for the extra storage, test with it and if the problem persists I'll try other roms like supernova you suggested or Leedroid. I am pretty new to this stuff so I don't know which is the best
I can confirm I had the same experience, it was great until I flashed the a2sd script. After that it was unusable.. that was with a class 6 card too
Sent from my CM7.1 Desire using XDA Premium App
I went back from GingerBurst to SuperNova too; now I am testing Unofficial BravoS by coolexe (because I really like Sense 2.1) and seems very good so far, the only thing I really dislike is A2SD+. A version based on Sibere's would be really great.
It's a bit of a relief to hear that other people have met the same issues as me with Gingerburst. I've already ordered my 16gb class 6 although from what you've told me, things won't get better I can't understand why the developer doesn't let us now that his Rom has still issues... I'll take a look to coolexe once I get my new memory. Anyone tried Leedroid HD?
The Rom is definitely fine, its just how you set it up...
Sent from my HTC Desire using XDA App
Just installed Sandvold's ICS ROM after months on CM7 and now I'm having a problem with the 'low on space' notification.
I used 4ext recovery to create a 1gb ext4 partition on my SD card (16gb) and flashed the ROM (after going through format, wipe cache etc etc). Upon installing Sandvold, I opted for the 2nd a2sd option (amarullz I believe - the one where dalvik cache remains on internal memory). Now I am reinstalling all of my apps and have been hit with the 'low on space' notification despite it stating 0.91gb free [see attachment #1 'App Manager'].
After checking the memory usage breakdown, the cause is probably down to the size of any of the following: /system, /cache or /sd-ext [see attachment #2 'Terminal'].
Any ideas what is my problem and how to fix it? I have a feeling it is something obvious!
Thanks.
It looks like your sd-ext partition is too small and nearly used up. You should really have around a 1gb partition. Take a backup of anything you need on your sd card and re-partition your card with a 1gb ext partition. You might need to reflash the rom again afterwards.
hans moleman said:
It looks like your sd-ext partition is too small and nearly used up. You should really have around a 1gb partition. Take a backup of anything you need on your sd card and re-partition your card with a 1gb ext partition. You might need to reflash the rom again afterwards.
Click to expand...
Click to collapse
Hmm maybe, but I've just checked in 4ext recovery where my sd-ext partition is showing what I thought was the case: approx 1gb (see attached screenshot).
Any ideas?
Thanks
I had been using amarullz as my a2sd solution too. However something seems to have broken it in the last few releases of sandvold. I tried the new m2sd from aroma installer but that doesn't install right. So far the only combination I could get to work was flash int2ext or int2ext+ right after flashing sand old. I am happy with that atm.
Sent from my HTC Desire
scaftogy said:
I had been using amarullz as my a2sd solution too. However something seems to have broken it in the last few releases of sandvold. I tried the new m2sd from aroma installer but that doesn't install right. So far the only combination I could get to work was flash int2ext or int2ext+ right after flashing sand old. I am happy with that atm.
Sent from my HTC Desire
Click to expand...
Click to collapse
Well 0.18.1 is the first version of Sandvold I've tried, so I have nothing to compare it against, but you're probably right. - looking at the ROM thread a few others are getting this problem.
I'll try int2ext+ if no one has another solution I guess!
Thanks.
Hello all, I am a noob.
I Have come across a lot of helpful information here but I am falling short of my goal...
I have a wildfire s with wildchild 3 installed on it and guess what... I have storage issues.
I am using link2sd and also have titanium backup pro which as I am aware it the best app to move data.
I have already integrated the sys dalvik into the rom which has provided me with space but the data continiues to clog the phone up.
I have read many forums but can not find a answer that works for me.
I am led to believe that the name for the mount script or folder is stopping me from getting the option in TB to copy data to sd.
I am really lost for answers and seek words of wisdom.
This is the final hurdle and once I pass this then I know my wildfire will be the greatest it can be.
If anyone can help then I would be extremely greatful.
Tony
try this, worked like a charm for me
http://forum.xda-developers.com/showthread.php?t=1735773&page=47
[post 464]
Well I must say this had worked very well for me!... Right up to the point when I rebooted my phone and it got stuck on the ROM loading screen.
I had only installed 2 apps too which I moved to SD and copied the data over from the Google Maps app.
Could it be that the ROM is not compatible?
Asad_612 said:
try this, worked like a charm for me
http://forum.xda-developers.com/showthread.php?t=1735773&page=47
[post 464]
Click to expand...
Click to collapse
tony2986 said:
Well I must say this had worked very well for me!... Right up to the point when I rebooted my phone and it got stuck on the ROM loading screen.
I had only installed 2 apps too which I moved to SD and copied the data over from the Google Maps app.
Could it be that the ROM is not compatible?
Click to expand...
Click to collapse
I thought I had it...
I read on and saw that the mount thing that you mentioned had said to have 100mb free space for every 500mb ext so I partitioned my drive with only 256mb which technically would have worked perfect with the wildfire s' lack of storage,
It was going so well but now again out of the blue the device will not boot. anyone with any other ideas?
I had about 50-60 app's installed before it decided to give up and it showed over 80mb using the mount script that was recommended.
tony2986 said:
I thought I had it...
I read on and saw that the mount thing that you mentioned had said to have 100mb free space for every 500mb ext so I partitioned my drive with only 256mb which technically would have worked perfect with the wildfire s' lack of storage,
It was going so well but now again out of the blue the device will not boot. anyone with any other ideas?
I had about 50-60 app's installed before it decided to give up and it showed over 80mb using the mount script that was recommended.
Click to expand...
Click to collapse
How much size did you allocate for both partitions, FAT 32, and EXT2?
I have a 4GB card, and i partitioned it like this:
FAT 32 , primary, 2.69 GB
EXT2, primary, 1 GB
P.s. Speed Droid's ROM is working fine with this, you could try this if you still have issues
Asad_612 said:
How much size did you allocate for both partitions, FAT 32, and EXT2?
I have a 4GB card, and i partitioned it like this:
FAT 32 , primary, 2.69 GB
EXT2, primary, 1 GB
P.s. Speed Droid's ROM is working fine with this, you could try this if you still have issues
Click to expand...
Click to collapse
FAT32 29.4GB Primary
Linux Ext3 243MB Primary
I never noticed till now that the partition is Ext3. Could this make a difference? The partition was made using clockwork recovery and didn't give me the option to choose.
I am downloading the Speed Droid's ROM for testing but if I was honest... I am a lover of the Wildchild ROM's
tony2986 said:
FAT32 29.4GB Primary
Linux Ext3 243MB Primary
I never noticed till now that the partition is Ext3. Could this make a difference? The partition was made using clockwork recovery and didn't give me the option to choose.
I am downloading the Speed Droid's ROM for testing but if I was honest... I am a lover of the Wildchild ROM's
Click to expand...
Click to collapse
I would suggest to try it like this:
FAT32 27GB Primary
Ext2 2GB Primary (Use the MinitoolPartition Wizard)
Your not going to believe this...
I wasn't doing anything wrong at all. Its Poweramp!!! The app for some unknown reason seems to crash during installation and does some kind of damage to the phone/ROM causing it to not reboot.
I have tested this several times and now have 63 apps minus the system apps and of course minus the rogue poweramp and everything works fine and the phone reboots in way under a minute.
Dude, thank you very much for your help.
I thought that this might have been a common issue but obviously not due to the lack of comments...
With your help my wildfire is now as great as any other phone now.
Thank you
Have you tried cronmod int2ext?
tony2986 said:
Your not going to believe this...
I wasn't doing anything wrong at all. Its Poweramp!!! The app for some unknown reason seems to crash during installation and does some kind of damage to the phone/ROM causing it to not reboot.
I have tested this several times and now have 63 apps minus the system apps and of course minus the rogue poweramp and everything works fine and the phone reboots in way under a minute.
Dude, thank you very much for your help.
I thought that this might have been a common issue but obviously not due to the lack of comments...
With your help my wildfire is now as great as any other phone now.
Thank you
Click to expand...
Click to collapse
:good:
I'm using the CyanogenMod 10 with CM10.1 features for the Wildfire S ROM. ROM boots fine on its own, but when I flash the Cronmod INT2EXT4+ zip, the phone gets stuck on the electron beam bootanimation. I haven't seen anyone else having this problem, could someone please help me?
My SD card is class 4 32GB. My ext4 partition is 1024GB.
Would really appreciate the help, thank in advance!
Hi,
I had this issue with CM9, solved formatting sd-ext partition from CWM recovery after flashing INT2EXT2+, hope it also works with INT2EXT4+
He is right,you need format sd/ext from recovery after you have flashed int2ext.
Also this could be an issue since we only have 150mb internal memory
-100mb internal is needed for every 500mb sd-ext (INT2EXT+/INT2EXT4+)
http://forum.xda-developers.com/showthread.php?t=1716124
I set mine to 512mb (ext3 i think, not sure though lol) and have had no issues with INT2EXT+.
If you are using cm10 use S2E from the Play Store it has less bugs and works fine
But you can also try other init.d scripts, as there are plenty of them in these forums
Envoyé depuis mon Wildfire S A510e
Odp: [Q] Need help getting INT2EXT4+ working on my phone
bobdarkside said:
Also this could be an issue since we only have 150mb internal memory
-100mb internal is needed for every 500mb sd-ext (INT2EXT+/INT2EXT4+)
http://forum.xda-developers.com/showthread.php?t=1716124
I set mine to 512mb (ext3 i think, not sure though lol) and have had no issues with INT2EXT+.
Click to expand...
Click to collapse
You need 100 per 500 MB USED, as + version leaves Dalvik files on internal to increase performance and speed of phone, please next time read carefully before you start confusing people.
Yasounet said:
You need 100 per 500 MB USED, as + version leaves Dalvik files on internal to increase performance and speed of phone, please next time read carefully before you start confusing people.
Click to expand...
Click to collapse
Read the original post there is no mention of the word USED, it is as I stated 100mb internal for 500 mb of sd-ext which i copied verbatim. Since we have a 150 mb internal one could perceive that the biggest sd-ext that could work with would be 750mb. Now if other people have gotten this to work with bigger sd-ext's power to them, since I haven't tried. If I am wrong I am sorry but I just did what the developer suggested.
Prerequisites:
-Rooted Rom with init.d support
-SD-EXT partition
-100mb internal is needed for every 500mb sd-ext (INT2EXT+/INT2EXT4+)
Hello folks
My issue is this:
GSM Desire
Class 10 SD
4ext Recovery (used to partition sd)
I'm trying to install various JB roms. The a2sd never works. When I download the gui it says it can't start because either no scripts, no partition, etc.
I've tried a lot of Roms including ones where a2sd is meant to be built in. I've also installed from Terminal and it seems to optimise all the apps on reboot but internal memory is still the standard and apps still in Internal (it's meant to go up to my ext4 partition right? it's about 1.5G)
I've worked my way through these (can't post the link but its the Alchemister custom rom blogspot for the Desire.)
each one the same problem.
Checkext and diskspace both see the partition. Strangely, L2SD seems to crash each of the Roms if I install it.
So far the only Rom to work correctly is a Supernova Gingerbread one. It gave me the 1.5G. So, the partition appears to be good.
Both are primary too.
I would like a JB one as the supernova rom is very laggy.
Running a Miui at the moment and also really liked the Touchwiz one on the list as well.
I only started doing this two days ago as my contract was up so I'm very new to this. Any help would be greatly appreciated. Thanks.
Let's make sure your partition works. Download the rom in my sig. It's a very stable rom, that has a script integrated that moves data/app and dalvik cache to sd-ext. Flash it, then install a few apps. If the internal storage gets filled up quickly, then it probably is a partition fault, and you'll have to repartition.
If it does work, then you did something wrong when you installed the other roms.
Are you sure you did a full wipe before installing all those roms?
a2sd problem solved
Thankyou Andoo,
I've got it working now. It was two things that were confusing me. They were mentioned in the partitioning guide that you attached.
1. I was not aware that you were not meant to see the full size of your Ext4 partition as internal storage. For anyone else with this problem, you can see how your Ext partition is being used if you download Freespace app from the market. I had assumed that you could see the ext as internal space as that is what a few of the earlier Roms i looked at said that that would happen. (it does for the Supernova Rom)
2. When I was downloading and installing apps such as FB or Maps, they were still taking a big chunk out of my internal memory so I assumed that it wasn't working. However, when I chose to put the data as well as cache to the Ext, it hardly took anything out of my internal storage at all. I have a class 10 card and so far everything seems fairly brisk and responsive. I Chose Y/Y/Y when installing a2sd from Terminal instead of the recommended Y/N/Y.
If things start to get slow, I might try the Mount2SD script in the attachment -I think this allows you to chose individual large apps to go to Ext instead of all of them.
Thanks again for your help. I now have a useful and quick phone again.
PS the MildWild 9.5 Rom you suggested - I hadinstalled this before and had real problems with the WiFi disconnecting every couple of seconds and the same thing happened again when I installed from your link. I'm using the Touchwiz at the moment and all seems well.
abaaaabbbb63 said:
Let's make sure your partition works. Download the rom in my sig. It's a very stable rom, that has a script integrated that moves data/app and dalvik cache to sd-ext. Flash it, then install a few apps. If the internal storage gets filled up quickly, then it probably is a partition fault, and you'll have to repartition.
If it does work, then you did something wrong when you installed the other roms.
Are you sure you did a full wipe before installing all those roms?
Click to expand...
Click to collapse