i have just gotten my hand on a HTC desire over the weekend, with zero knowledge on rooting or android. after installing a few apps, namely FB, gmail, maps, flipboard and whatsapp i was given the "low memory" warning. uh... i have not even installed candy crush yet... so i did some read up on a few sites and straightaway attempted to mod the desire to increase the internal memory.
what i did :
s-off using Revolutionary tool and installed CWM.
partitioned an 8gb class10 card, 2048mb ext3 and the balance FAT32,
CyanogenMod 7.0.2.1 stable release.
Data2SD
to my delight everything work out and i get increased internal memory and i was happily re-installing all the above apps. problem is some of the apps -youtube and facebook, could not be started. after choosing "move to sd" then it can be started and used, albeit a tad laggy. the only issue left is whatsapp, after activation, it went on and on in the "initialising" for a very long time without any sign of it ever getting into working condition, i had to force close it.
i am thinking of repeating the whole process once again, clean install, but based on the read-up about data2sd, if i were to reflash rom on a device that already has data2sd prior, i would need to use Data2SDReinstaller.zip instead of Data2SDinstaller.zip that i have acquired earlier.
after googling up like mad, i still could not find anywhere to download Data2SDReinstaller.zip. hope that anyone who still has this would share it up here. Thanks a lot!
Well done for getting this far on your own! A few things you could do to improve check:
- How did you partition your sd card? Should be done in gparted or 4EXT recovery only, not minitool. Also might as well use ext4, slightly faster than ext3
- Next you should also install cyanogenmod on cm7r2 hboot to maximise your actual internal memory. Currently you're still on stock hboot with 250MB /system and you're only using ~140MB. You can convert this wasted 110MB into extra /data (internal memory), goes from 147MB to 287MB
- I personally don't recommend data2sd. Might the reason you're getting errors. Also you shouldn't need to use 'move to sd' anymore that moves to the fat32 partition not the sd-ext. Use a different script to move apps and dalvik to sd-ext, keep app data on internal.
So try:
- backup everything if you haven't already (titanium backup for apps etc)
- change hboot to cm7r2 using fastboot, search for guides
- (optional) flash 4EXT recovery using fastboot
- backup and repartition sd card if necessary using 4EXT as above
- full wipe and reinstall ROM again
- use another app/script such as mount2sd, S2E or darktremor A2SD, move apps and dalvik to sd-ext. They do the same thing. You won't necessarily see you're internal memory increase to 'internal + sd-ext' but it's working. Don't 'move to sd' as before, keep them on internal to trick to sd-ext.
- restore apps. Install something like diskusage to check your partitions are working.
eddiehk6 said:
Well done for getting this far on your own! A few things you could do to improve check:
- How did you partition your sd card? Should be done in gparted or 4EXT recovery only, not minitool. Also might as well use ext4, slightly faster than ext3
- Next you should also install cyanogenmod on cm7r2 hboot to maximise your actual internal memory. Currently you're still on stock hboot with 250MB /system and you're only using ~140MB. You can convert this wasted 110MB into extra /data (internal memory), goes from 147MB to 287MB
- I personally don't recommend data2sd. Might the reason you're getting errors. Also you shouldn't need to use 'move to sd' anymore that moves to the fat32 partition not the sd-ext. Use a different script to move apps and dalvik to sd-ext, keep app data on internal.
So try:
- backup everything if you haven't already (titanium backup for apps etc)
- change hboot to cm7r2 using fastboot, search for guides
- (optional) flash 4EXT recovery using fastboot
- backup and repartition sd card if necessary using 4EXT as above
- full wipe and reinstall ROM again
- use another app/script such as mount2sd, S2E or darktremor A2SD, move apps and dalvik to sd-ext. They do the same thing. You won't necessarily see you're internal memory increase to 'internal + sd-ext' but it's working. Don't 'move to sd' as before, keep them on internal to trick to sd-ext.
- restore apps. Install something like diskusage to check your partitions are working.
Click to expand...
Click to collapse
hi eddie, thanks for your pointers!
i used CWM to partition the card earlier on, only to discover that it was partitioned on ext3 with no choice to . prior to data2sd, i have tried link2sd, with the impression that it is similar to S2E & mount2sd. sad to say that after installing apps as listed earlier, the same low memory warning still popped up, so i assumed these script is not what i wanted.
for my next step, i plan on a full wipe and start afresh, thinking of using minitool to hammer the whole card flat on a single, FAT32 partition, and then using Aparted to create an ext4 partition. (downloadable from market, yeah that would mean putting the phone into stock CM firmware first and re-wipe again after that).
i have zero knowledge on linux nor any of my machines running it and i am so used to windows environment, that is the reason i did not start out on using Gparted in the first place, and used CWM's own partitioning tool.. 4ext recovery could be an alternative from what i read, but can 4ext be installed when CWM is already in place?
just to update, found the download for the data2sdreinstaller files, in some sections of xda i forgot which thread but i have it now. i will try on re-doing data2sd first. if the phone still give me issues then next would be doing as what you have suggested. thanks again!
Don't use clockworkmod. It's not that it's a bad recovery generally, but for desire it's not recommended as it tends to not create properly aligned partitions.
Backup sd, delete all partitions and repartition from scratch, use gparted or 4EXT recovery, don't recommend anything else. Now that you're s-off it's quite easy to change recovery, it will simply replace CWM.
gparted is also not that bad once you get the hang of it, I use bootable live cd and personally prefer it as I can see everything. I never used linux either... Use this guide
I've never had any luck with link2sd, never liked it. Yes it's supposed to do the same thing, but the idea of linking seemed a bit odd, maybe just not for me, and you may not have had any luck due to a bad partition. Try the others suggested, move apps and dalvik to sd-ext.
Remember to also change hboot to optimise space further.
eddiehk6 said:
Don't use clockworkmod. It's not that it's a bad recovery generally, but for desire it's not recommended as it tends to not create properly aligned partitions.
Backup sd, delete all partitions and repartition from scratch, use gparted or 4EXT recovery, don't recommend anything else. Now that you're s-off it's quite easy to change recovery, it will simply replace CWM.
gparted is also not that bad once you get the hang of it, I use bootable live cd and personally prefer it as I can see everything. I never used linux either... Use this guide
I've never had any luck with link2sd, never liked it. Yes it's supposed to do the same thing, but the idea of linking seemed a bit odd, maybe just not for me, and you may not have had any luck due to a bad partition. Try the others suggested, move apps and dalvik to sd-ext.
Remember to also change hboot to optimise space further.
Click to expand...
Click to collapse
noted with many a thanks. hopefully learning this on Desire would allow me to do the same on some other Android devices in future. Funny to think i am doing this as all these while i am just a plain nokia user with all stock firmware.
the jargons for androids are abit overwhelming for me.
Don't worry, it's all a learning process. For most in the desire forums it was their first android device, like me too.
All of the stuff I've written above, I knew none of that at the start either.
Like anything, the more you read the more you learn. It'll start to make sense sooner or later
Related
Hey,
I've been using ICS (beta 0.4.2.1 now, beta 0.3.9 previously) and none of the a2sd scripts seem to be working. I tried to use the one you have to activate through adb, and today when I updated to 0.4.2.1 I chose another one from the installer. My phone still reports 148 MB of internal storage...
I've had a thorough search of similar threads, but you know how difficult it is to find any meaningful information on this forum; can someone please point me in the right direction? Thank you!
I flashed ICS and installed the bundled a2sd script and it worked like the script on Insertcoin. That is the system still displayed the data partition size of my hboot but the SD ext4 partition was utilised for apps. If you have titanium backup you can see the data usage on the home screen.
I also flashed amarullz script. This script did change the reported internal memory to my SD card partition size. I did not use it long so I can't comment on how it runs on s class 4 SD card.
Sent from my HTC Desire using XDA
You did not understand how A2SD works. It moves all apps (with A2SD+ also dalvik-cache) you install automatically to an EXT-partition (some of their data still remain in internal memory). But it does not increase / decrease the size of internal memory.
If you want to change the size of internal memory, you have to use a script which moves the whole /data-partition to an EXT-partition. The size of this partition is then the size of your internal memory. The name of this scripts is DATA2SD / DATA2EXT.
Sent from my HTC Desire using Tapatalk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Did you ever get a fix for your problem?
I have something similar. Was running 0.3.9. and decided for a couple days ago to upgrade to a newer edition. Wiped data/factory reset, wiped cached and dalvik-cache, and installed the new version.
Used stock everything, activated a2sd and tried to start and install some apps from google play. Got a message that it was not sufficient space.
Did get titanium installed, and that reports the different "drives" correctly, but I still don't get it to work as it should. If I try to install from play, it says not sufficient space, even if I try to restore from titanium, still no luck.
Anyone got any ideas?
Start Terminal. Type:
su
a2sd install
yes (move dalvik-cache)
no (don't move appdata) (yes will make device slower)
yes (restart)
After reboot you have more space, but don't see it.
Start terminal
su
a2sd diskspace
gives the size of your sd-ext and how much is used
arsvendg said:
If I try to install from play, it says not sufficient space, even if I try to restore from titanium, still no luck.
Click to expand...
Click to collapse
Same problem here. I tried to wipe caches and even recreated the partitions but still no luck with the stock a2sd.
robla1000 said:
Start Terminal. Type:
su
a2sd install
yes (move dalvik-cache)
no (don't move appdata) (yes will make device slower)
yes (restart)
After reboot you have more space, but don't see it.
Start terminal
su
a2sd diskspace
gives the size of your sd-ext and how much is used
Click to expand...
Click to collapse
Just wondering. Isn't the whole idea with the as2d to move the appdata to the sd-card?
arsvendg said:
Just wondering. Isn't the whole idea with the as2d to move the appdata to the sd-card?
Click to expand...
Click to collapse
App and appdata are different things:
The App it's the "core" and are loaded in the RAM when you start them, so if you move them to sdcard you get a slowdown only on the boot of the app itself
The Appdata it's the data created and used by the program to run, likes databases and so; if you move it to the sdcard you get a slowdown 'cause the program continuosly try to access it.
someone correct me if I'm wrong, i'm still learning the stuff
Long story short: normal A2SD+ methods (like DarkTremor or m2sd) only move a part of /data, linking the files; you will NOT see the increased space but your Apps will occupy less memory.
Data2sd method like data2sd or Amarullz A2SDX will "swap" the ext space with the internal data memory, giving you a visible increase in your internal space.
TL;DR if you have a fast SD card you can go for the latter, else stick to m2sd wich is a new and good method to move application!
For partitioning, I suggest you to use 4ext touch recovery, you can install it on your phone from 4ext.net and flash your new recovery directly from your phone (you need to have S-OFF!); after you have your new recovery flashed:
make a backup of your SD card data (you have to format it)
Reboot in recovery
Go to "Tools"
"partition sd card ->"
"Remove all partitions and start from scratch"
Now you have to set, in order, you primary ext dimension, your secondary ext dimension and the swap dimension
I usually go for - 1st ext: 1024 -2nd ext: 0 - swap: 0
Select ext4 for your first ext partition
Now you are ready to use wathever a2sd method you want.
Hope this will help you!
Regards,
Ryther
Ahh I'm just going to leave this here.
All the ICS Devs have done a great job - Kudos to them.
But if you want a bugfree ROM which works well, for now - GIVE UP on ICS.
Go back to CM7 - it'll do you good.
Don't give up on ICS because SOME people have issues. I've ran an ICS build with a2sd working just fine no bugs whatsoever. I have not tried a data2ext script on an ICS build though so I don't know about that.
Hey guys, as the title mentions, I've got my device almost up to speed. The trouble is, I can't seem to get it to partition properly. Or at all. I'm at 20mb of internal space left, and that's really hampering my ability to enjoy this otherwise fantastic phone.
I've tried Minitool Partition wizard, but my device thinks its corrupts my SD card. I've tried ROM manager (setting it to 512mb external and 0mb swap), but rom manager runs, reboots the phone, and nothing changes. Well. Mostly. I tested it out by installing a 10mb app from the store, but it used up the internal storage space, and disappeared! I can't find and uninstall it anymore! This is driving me absolutely crazy. I've lost so much time looking through forums and trying things out.
- uninstall rom manager
- do not use minitool partition wizard
- backup your sd card and use gparted to partition sd card, step 5 here. alternatively you can use 4ext recovery, easy to install as you are already s-off. copy everything back once partitioned.
you say you are 'hbooted', but have you actually changed your hboot to cm7r2, this will repartition your internal memory so you have more space. search for guides (how to change hboot...), recommend to do this through fastboot commands (again this is easy because you are already s-off).
once this is all set up (cm7r2 hboot and correctly partitioned sd card), you need to use a script or app to move the apps to the partition. i recommend something like s2e or link2sd.
for general reading, i recommend these set of guides.
Use 4ext recovery to partition SD, and get rid of ROM Manager.
Sent from my HTC Desire using xda premium
k3lcior said:
... and get rid of ROM Manager.
Click to expand...
Click to collapse
Curious to know why. I have never used ROM Manager but was going to...
murtuzasb said:
Curious to know why. I have never used ROM Manager but was going to...
Click to expand...
Click to collapse
it's not that it's a bad app, just particularly bad for htc desire. can screw things up. found out here, suroot is well respected and i trust his advice
plus you don't actually need to use rom manager...all the actions can be carried out within recovery anyway.
Hey Eddie, thanks for the info. I'll load up the Gparted this evening. Get this damn device running properly finally.
Once partitioned, I'm worried about this aforementioned missing facebook app. I don't care that it's not working, only that it's taking up unusable space. I'm down to 13mb of internal storage. After using Gparted to partition, would it be best for me to do a fresh install of CM7? And would that reset my root and S-off?
I'm also constantly getting confused about fastboot and hboot. Aren't they intrinsically linked? Actually, scratch that. What is fastboot, and how does it relate to hboot?
And why, when I tried to partition my card using clockwork recovery, did it update (and possibly replace) my recovery?
As for whether I have CM7 hboot set up, I'm honestly not sure. My hboot / fastboot window (the one that shows up after rebooting, with a white screen and 3 android on the bottom on skateboards, with the options for FASTBOOT/RECOVERY/CLEAR STORAGE/SIMLOCK?) is set to -REVOLUTIONARY-, HBOOT 6.93.1002. If that doesn't answer the question, how can I check if I have the CM7 hboot?
Thanks for the time, man. I appreciate you helping me understand how all this works! There was a time when I thought I was understanding the process. Then things stopped working. =p
Dysoncube said:
Hey Eddie, thanks for the info. I'll load up the Gparted this evening. Get this damn device running properly finally.
Once partitioned, I'm worried about this aforementioned missing facebook app. I don't care that it's not working, only that it's taking up unusable space. I'm down to 13mb of internal storage. After using Gparted to partition, would it be best for me to do a fresh install of CM7? And would that reset my root and S-off?
I'm also constantly getting confused about fastboot and hboot. Aren't they intrinsically linked? Actually, scratch that. What is fastboot, and how does it relate to hboot?
And why, when I tried to partition my card using clockwork recovery, did it update (and possibly replace) my recovery?
As for whether I have CM7 hboot set up, I'm honestly not sure. My hboot / fastboot window (the one that shows up after rebooting, with a white screen and 3 android on the bottom on skateboards, with the options for FASTBOOT/RECOVERY/CLEAR STORAGE/SIMLOCK?) is set to -REVOLUTIONARY-, HBOOT 6.93.1002. If that doesn't answer the question, how can I check if I have the CM7 hboot?
Thanks for the time, man. I appreciate you helping me understand how all this works! There was a time when I thought I was understanding the process. Then things stopped working. =p
Click to expand...
Click to collapse
There u go, technicial definitions: http://forum.xda-developers.com/showthread.php?t=805247
If u havent changed your Hboot since u s-offed then it should be stock.
Dysoncube said:
Hey Eddie, thanks for the info. I'll load up the Gparted this evening. Get this damn device running properly finally.
Once partitioned, I'm worried about this aforementioned missing facebook app. I don't care that it's not working, only that it's taking up unusable space. I'm down to 13mb of internal storage. After using Gparted to partition, would it be best for me to do a fresh install of CM7? And would that reset my root and S-off?
I'm also constantly getting confused about fastboot and hboot. Aren't they intrinsically linked? Actually, scratch that. What is fastboot, and how does it relate to hboot?
And why, when I tried to partition my card using clockwork recovery, did it update (and possibly replace) my recovery?
As for whether I have CM7 hboot set up, I'm honestly not sure. My hboot / fastboot window (the one that shows up after rebooting, with a white screen and 3 android on the bottom on skateboards, with the options for FASTBOOT/RECOVERY/CLEAR STORAGE/SIMLOCK?) is set to -REVOLUTIONARY-, HBOOT 6.93.1002. If that doesn't answer the question, how can I check if I have the CM7 hboot?
Thanks for the time, man. I appreciate you helping me understand how all this works! There was a time when I thought I was understanding the process. Then things stopped working. =p
Click to expand...
Click to collapse
take your time and read the guides i first linked you, and the one above to help with definitions.
minitool can go horribly wrong. clockworkmod recovery is also not very good at partitioning. gparted is always recommended.
you are currently on stock hboot because you haven't changed it. hboot just refers to the way all your internal memory partitions are laid out. in other words currently you have a 250MB system partition, but your cm7 rom system size is say 140MB (i.e. you're wasting 110MB)
when you change hboot to cm7r2, it has a 145MB system, so you waste say only 5MB. the extra reparitioned space becomes more internal memory (increases from 147MB to 287MB)
i say fastboot commands because that's just a method of actually changing your hboot.
so:
- use an app like titanium to backup all your apps. backup you contacts to gmail if you haven't already, use another app to backup sms if you need them too.
- backup your entire sd card to PC
- partition sd card, ~1gb ext4 should be enough, using the guide i linked.
- copy everything back to sd
- change hboot to cm7r2, search for guides (i recommend using fastboot commands)
- boot into recovery, nandroid backup
- full wipe and reinstall (you won't lose root or s-off)
- before you restore, install s2e or link2sd. select to move apps to sd-ext, keep app data and dalvik cache on internal (287MB should be enough space unless you have LOADS of apps), may need to reboot afterwards.
- restore everything else.
- i recommend to use another app like 'diskusage' to check all your partitions are working correctly.
seems like a faff, but this should have been the way to set it up in the first place
So, things went well, thanks to you guys.
I had already paritioned using minitool partition wizard. Gparted would NOT work for me, so I gave the minitool partition another shot. Installed the CM7 HBoot, wiped everything, reinstalled CM7 (since I was getting a bootloop problem), now everything seems to be running fine. Android detects 280mb of internal storage. I installed a 40mb app, transferred it to the SD card, and it's working beautifully. Im pretty darn happy with how things have turned out. Are there any other things I should verify, to make sure everything installed alright?
it wont boot coz u partitioned ur sdcard and changed hboots. so because u didnt do a backup u will have to flash the CM7 rom again. put CM7 rom on ur sdcard, boot into recovery, full wipe and flash the rom
Sent from my HTC Desire
Dysoncube said:
So, things went well, thanks to you guys.
I had already paritioned using minitool partition wizard. Gparted would NOT work for me, so I gave the minitool partition another shot. Installed the CM7 HBoot, wiped everything, reinstalled CM7 (since I was getting a bootloop problem), now everything seems to be running fine. Android detects 280mb of internal storage. I installed a 40mb app, transferred it to the SD card, and it's working beautifully. Im pretty darn happy with how things have turned out. Are there any other things I should verify, to make sure everything installed alright?
Click to expand...
Click to collapse
gparted should always work if done correctly, what exactly would not work? if repartitioning using gparted, delete all existing partitions and start from scratch. as per guide, FAT32 should be first (on the left), ext4 partition second, both labelled as primary.
if minitool worked then you got lucky (many cases including myself in early days when it just screwed things up), i'd still recommend giving gparted another go.
when you say transferred to sd card, are you manually moving apps to sd using 'move to SD' within settings? if so then you're actually moving them to FAT32 partition of sd card, and not the ext4 partition...
follow what i said before, use an app (easiest) or script to move apps to sd-ext. if done correctly you shouldnt have to move any apps to sd, keeing them on should internal 'trick' them to sd-ext, it moves all of the app (and can move widgets too). and like i said, another app like 'diskusage' you can actually see your sd-ext filling up if setup correctly.
[you successfully changed hboots which is good! :victory:]
I'm trying to install m2sd on cm7. I do a full wipe, install the Rom, gapps, and m2sd script. After starting up I enable m2sd for apps and reboot. Then I start installing software, but they take up space on internal memory. After moving them to sd they don't go to ext partition but to the fat one.
What could be the issue?
how did you partition you sd card? should be done with gparted (step 5 here) or 4ext recovery only (not minitool or clockworkmod recovery).
depending on the options chosen for m2sd, some stuff will still take space on internal, for instance app data is best left on internal for performance. use an app like 'diskusage' to browse all your partitions.
make sure you're also s-off and on cm7r2 hboot to maximise space (have a look for further guides if this doesnt make sense).
Try also enabling dalvik cache to sd.
Or the data + r-mount combination (which is I'm using now with no problem at all).
eddiehk6 said:
how did you partition you sd card? should be done with gparted (step 5 here) or 4ext recovery only (not minitool or clockworkmod recovery).
depending on the options chosen for m2sd, some stuff will still take space on internal, for instance app data is best left on internal for performance. use an app like 'diskusage' to browse all your partitions.
make sure you're also s-off and on cm7r2 hboot to maximise space (have a look for further guides if this doesnt make sense).
Click to expand...
Click to collapse
I just did it all again, to make sure I used gParted, so I'm sure I have 10gig Fat32, 4gig EXT4 and 256meg Swap. Then I did a full wipe of the phone, installed cm7, gapps, and when the system booted I installed and configured m2sd APK and rebooted. Still, in the gui section you can see "File System Type: N/A". It looks like it didn't recognise the FS but I have tried setting that to auto and EXT4
EDIT
Does anyone know what a2sd script has been used in THIS rom?
gaseki said:
I just did it all again, to make sure I used gParted, so I'm sure I have 10gig Fat32, 4gig EXT4 and 256meg Swap. Then I did a full wipe of the phone, installed cm7, gapps, and when the system booted I installed and configured m2sd APK and rebooted. Still, in the gui section you can see "File System Type: N/A". It looks like it didn't recognise the FS but I have tried setting that to auto and EXT4
Click to expand...
Click to collapse
follow the guide again...
4gb ext4 partition is too much, you won't even need that much for apps! absolute maximum that i've read you should use is 2gb, personally i recommend 1.5gb.
you also don't need swap.
both partitions also need to be primary as per the guide.
EDIT
Does anyone know what a2sd script has been used in THIS rom?
Click to expand...
Click to collapse
that rom uses terminal emulator to enable A2SD. follow the guides/instructions in that thread.
Hi guys..
Hope someone will be so nice to help me..
So..I have this desire and it was running with the supernova rom. Problem is it gives me a annoying issue that i didn't manage to solve...not even reset it nor reflashing the rom. It always comes out again..
I decided to try some other roms...and in the last few days i flashed so many, but i never managed to make one to see the ext* partition...at second boot it always shows only some MB as internal memory.. I tried to do it on any way...formatting sd withing the recovery, from pc, flashing alignment..nothing..
Now i'm asking...do i have to have or to do anything special before flashing one of those roms? Why the supernova works with no problem and all the other never?
Thank you in advance
How did u partition ur sdcard?
Use this guide
http://forum.xda-developers.com/showthread.php?t=2125513
You should partition your sd card as above, no alignment or anything needed as gparted or 4EXT make properly aligned partitions.
Depending on the ROM, you may still not 'see' the ext partition i.e. you won't see "internal + ext" as your reported internal memory like supernova, but your apps still go to sd-ext. Most of the time you just have to keep your apps on internal (i.e. don't 'move to SD'), which tricks the apps to sd-ext.
Some roms require you activate A2SD via terminal commands, others have built in scripts, see each rom thread for details. Make sure you're also on the right hboot (requires s-off) to maximise actual internal memory /data).
A good way to check is to use an app like 'Diskusage' to browse all your partitions. As long as you're sd-ext is filling up, it's working
jmcclue said:
How did u partition ur sdcard?
Use this guide
http://forum.xda-developers.com/showthread.php?t=2125513
Click to expand...
Click to collapse
I tried every possible way...as i told.. From recovery and from pc...
Titanium backup actually sees the ext partition...but..when i install the app...after a while internal memory gets full...so..
I don't know...i'm..disappointed and frustrated... Don't get why only tha supernova works as it should without any problem...
eddiehk6 said:
You should partition your sd card as above, no alignment or anything needed as gparted or 4EXT make properly aligned partitions.
Depending on the ROM, you may still not 'see' the ext partition i.e. you won't see "internal + ext" as your reported internal memory like supernova, but your apps still go to sd-ext. Most of the time you just have to keep your apps on internal (i.e. don't 'move to SD'), which tricks the apps to sd-ext.
Some roms require you activate A2SD via terminal commands, others have built in scripts, see each rom thread for details. Make sure you're also on the right hboot (requires s-off) to maximise actual internal memory /data).
A good way to check is to use an app like 'Diskusage' to browse all your partitions. As long as you're sd-ext is filling up, it's working
Click to expand...
Click to collapse
Thank you..i will try...
Again..just tried with another one...and...as much as i put back my apps...internal memory gets full...
I don't know what rom is the right one..too many..and too complicated chosing the right one...
I just wish i could have sense and the working ext partition...
Cell is rooted and s-off... Hboot..dunno....it says 0.93.001
Thanks for the answers..
darkchild_74 said:
Thank you..i will try...
Again..just tried with another one...and...as much as i put back my apps...internal memory gets full...
I don't know what rom is the right one..too many..and too complicated chosing the right one...
I just wish i could have sense and the working ext partition...
Cell is rooted and s-off... Hboot..dunno....it says 0.93.001
Thanks for the answers..
Click to expand...
Click to collapse
How many apps do you have? over 50?
abaaaabbbb63 said:
How many apps do you have? over 50?
Click to expand...
Click to collapse
Yeap...last time i tried to put back apps from titanium backup it told 81...i wasn't putting back them all..but surely more than 50
darkchild_74 said:
Yeap...last time i tried to put back apps from titanium backup it told 81...i wasn't putting back them all..but surely more than 50
Click to expand...
Click to collapse
What rom did you try, except supernova?
abaaaabbbb63 said:
What rom did you try, except supernova?
Click to expand...
Click to collapse
Cool3d, LeeDrOiD, and so many other i don't remember...
Just tried RunnymedeMod...seems that it uses the ext partition...but...i get the low memory space warning anyway...it's..useless...
THe only one wichi works for me is supernova..
darkchild_74 said:
Cool3d, LeeDrOiD, and so many other i don't remember...
Just tried RunnymedeMod...seems that it uses the ext partition...but...i get the low memory space warning anyway...it's..useless...
THe only one wichi works for me is supernova..
Click to expand...
Click to collapse
Ok. Now let me explain what happens.
Supernova has a script that moves data/data to sd-ext. Data/data is the folder that occupies most of the data partition. It's the application data itself.
The other ROMs leave data/data on the internal memory, for performance reasons, and move other stuffs, like data/app, or dalvik cache to sd-ext.
You have many apps, so only moving dalvik cache and data/app isn't enough. You should be using ROMs that use INT2EXT or INT2SD scripts, like this one:
http://forum.xda-developers.com/showthread.php?t=1315961URL
Or, use the INT2EXT4 script from here:
http://forum.xda-developers.com/showthread.php?t=1716124
darkchild_74 said:
Cool3d, LeeDrOiD, and so many other i don't remember...
Just tried RunnymedeMod...seems that it uses the ext partition...but...i get the low memory space warning anyway...it's..useless...
THe only one wichi works for me is supernova..
Click to expand...
Click to collapse
So you partitioned using 4EXT or gparted? (NOT minitool or clockworkmod recovery as recommended?) If not then backup your sd card and repartition, so we know that it's definitely properly done.
Before you reinstall all your apps in one go, just restore or install one. Then like I said, install 'Diskusage' as well, and try to find where this app has been installed to. If it's on sd-ext, then it's working, and if it's on /data, then it's not.
Depending on the ROM, some stuff will still get stored on the /data (internal memory) partition. So there is always an upper limit to how many apps you can install. Most of the time, app data gets saved on internal. Sometimes dalvik-cache also gets stored there, but you may be able to move it to ext.
Regardless of which ROM or A2SD method or other script, the first step is to work out and understand what is being stored where, hence why I keep recommending 'Diskusage'
Also you are still on stock hboot, which has a very low /data (internal memory) partition, only 147MB. Some ROMs are better on other hboots before you flash them as they have a smaller /system size, and thus a larger /data partition. For instance, many ROMs fit on cm7r2 hboot, with a larger 287MB /data partition which fills up a lot slower. If you decide on a ROM, all of them should say which hboot is best for it, you should download them from alpharev.nl, and flash them via fastboot, guide here.
Thank you guys...so much.. SItuation is more clear now...
So..if i use that Rom with INT2EXT it should work like supernova and it would use the exp partition instead of the data partition..and it could be ok... I got performances would be worse, but again...i was already running a rom with same script..and it was ok... Would i get again that issue about cell reloading the system now and then...or it's caused by the system using the sd instead of the internal memory as data partition?
Again...i think ext partition is ok...i tried to check it...and...the system uses it.. THe problem is that with so many apps...internal memory gets full anyway...so..i have to find another solution...
I checked..and i always read that it was ok with stock hboot....i'm not such an expert...but since i never touched it..i thought it was stock... As i told, i rooted it..and turn it s-off...
I know the bad things about this cell is the low memory space, i just wanted to use it 'cause for the rest isn't bad...and even changing the internal partition...will make it better...but...dunno if it will worth the...risk..?? I
I will think about it.. Guess i can even give up on some apps...and put there only the apps i really need...it won't be a problem...
Thanks again to both
Really appreciated
darkchild_74 said:
Thank you guys...so much.. SItuation is more clear now...
So..if i use that Rom with INT2EXT it should work like supernova and it would use the exp partition instead of the data partition..and it could be ok... I got performances would be worse, but again...i was already running a rom with same script..and it was ok... Would i get again that issue about cell reloading the system now and then...or it's caused by the system using the sd instead of the internal memory as data partition?
Click to expand...
Click to collapse
Glad it's starting to make sense. Yes that script should work for a lot of apps. Don't know about the "reloading system" issue, but your main goal is space for apps.
Again...i think ext partition is ok...i tried to check it...and...the system uses it.. THe problem is that with so many apps...internal memory gets full anyway...so..i have to find another solution...
Click to expand...
Click to collapse
It's always best if it is created using gparted or 4EXT recovery, they are the recommended methods by far.
I checked..and i always read that it was ok with stock hboot....i'm not such an expert...but since i never touched it..i thought it was stock... As i told, i rooted it..and turn it s-off...
I know the bad things about this cell is the low memory space, i just wanted to use it 'cause for the rest isn't bad...and even changing the internal partition...will make it better...but...dunno if it will worth the...risk..?? I
I will think about it.. Guess i can even give up on some apps...and put there only the apps i really need...it won't be a problem...
Thanks again to both
Really appreciated
Click to expand...
Click to collapse
Yes, you are still on stock hboot. Once you understand why you may want to change hboot, it's worth the small 'risk', because that way you do actually get more internal memory . I believe on some of the ROMs you tried you simply ran out of memory faster because you didn't change hboot.
As for which hboot you use, it is entirely dependent on the ROM, you have to search this yourself. I would recommend a ROM with at least cm7r2 hboot, and a int2ext script if possible.
(And I'll keep recommend installing 'diskusage' until you try it and understand how and where all your memory is used)
Just to let you know i managed to change the hboot with proper one...partitioned the sd again via 4ext recovery..installed the right rom and it shows me the ext4 partiiom as internal memory..
Now just have to test it and see if i will get the same problem i was having with supernova, and if it works properly..
Thank you so much to both for the help...really appreciated...
HI
Im new to this forum so please forgice me if my post is in the wrong place.
I have the 2010 htc desire and have it rooted and am running MILDWILD 8.0 which is great on this phone. my question is how do i add extra internal memory using partion ext on sd card. I can partion the sd card with clockword recovery but when i reboot it always hangs on the htc logo. can any one help with this?
Thanks
CWM-made partitions dont cope well with this phone. Reformat the partition using this guide.
I followed the guide but mildwild 8.0 still shows 148 on htc desire internal memory.
That's because you're still on stock hboot, no better than before it was rooted.
- Install DiskUsage, enable root and browse to your /system partition.
- You will see a lot of free space on /system. This is wasted space.
- You can convert this wasted space to extra /data (internal memory) by flashing a different hboot with a smaller /system partition.
(You need to be s-off for the following, if you're not, use 'revolutionary')
- Nandroid backup
- Flash cm7r2 hboot using fastboot
- Full wipe and nandroid restore
- Go again to DiskUsage, your free space on system is greatly reduced :good:, and your /data will go up to 287MB
- This 287MB will be used for app data (e.g. saved game data), and will allow for more apps to be installed.
- You won't see your sd-ext reported in your total internal memory (i.e. it won't read 'internal + sd-ext')
- Keep your apps on 'internal' (don't 'move to sd'), this will trick them automatically to sd-ext.
- If you use DiskUsage to browse to /sd-ext, you'll see apps and dalvik cache there, which means it's working as it should.
do i need to do this? if so can you show me a guide.
also does mild wild 8.0 have built in apps2sd scripts and if so how do i use them.
i have saw videos on youtube with the htc desire internal memory going from 148mb to 1.5gb how can i do this?
thanks
You don't technically need to do to it, but in order to gain more app space you should understand exactly how your memory is being used in the first place.
Apps2sd is already enabled in the ROM by default as stated in the ROM OP. You do not need to do anything extra. Like I said, keep apps on internal and your apps and dalvik cache will be moved to /sd-ext, you should be able to check this now with DiskUsage.
I recommend starting here for fastboot guide, that's the only thing you're missing. Flashing things through fastboot isn't that hard once you get used to it, and can be crucial in certain situations. Once you flash the ROM on cm7r2 hboot, you'll be using your space more efficiently and have a lot more space for apps.
I know 287MB doesn't seem like much more. But this is /data partition is only used for app data. This will still get filled up as you install apps, but much more slowly :good: The apps and dalvik cache which take up much more space go to sd-ext, which is what you want.
You can refer to the same videos if you really want to see 1.5GB internal memory, they likely use a 'data2sd' or equivalent script but in my experience it's not worth it. You would have to remove the current working script, and replace it with something else, which is risky if it's incompatible and untested. Even if you do this, you're not actually gaining anything extra. You have already created the sd-ext partition; it's size is whatever size you set it when you partitioned. It does not change depending on the A2SD script.
I understand that having a 'visible' 1.5GB memory looks better...but once you realise your partition is already there and being used correctly, you don't need to see it.
thanks
i now have 288mb of internal storage with an ext partion sd of 1.4gb,
is that all i need to do now?
so when i install apps the mildwild 8.0 rom will move all to ext4 partion automatically?
also some apps i use to use now say "compatible with your device" is there a way around this so i can install them on my desire?
Thanks
Pretty much yes. Keep them on internal as instructed (don't 'move to SD') to trick them to sd-ext.
All you really need is reassurance that your ext partition is actually being used, which is why I always recommend DiskUsage. Have you actually tried it as first recommended?
Browse to your /sd-ext (or similar name) folder, the one which is ~1.4GB in total size. What can you see?
As for incompatible apps. Don't know. Which ones, are they for higher versions of Android? Have you tried sideloading the apks?
eddiehk6 said:
Pretty much yes. Keep them on internal as instructed (don't 'move to SD') to trick them to sd-ext.
All you really need is reassurance that your ext partition is actually being used, which is why I always recommend DiskUsage. Have you actually tried it as first recommended?
Browse to your /sd-ext (or similar name) folder, the one which is ~1.4GB in total size. What can you see?
As for incompatible apps. Don't know. Which ones, are they for higher versions of Android? Have you tried sideloading the apks?
Click to expand...
Click to collapse
yes i have tried it as recommended.
when i browse /sd-ext i see 1423mib then the following dalvik-cache 76.7mib, app 66.4mib, system data 104.3 mib and freespace 1175mib
I also liked the guide on fast boot you sent me, as from using tips from it i was able to flash a new splash screen and boot animation. so thank you.
by side loading do you mean installing the apps with the apk file and not through the play store?
if so this works for some apps but now others. the app Im looking to use is the Argos app. before the recent update it worked fine but now when i went to update i get the device is incompatible message in play store. I have read some stuff on the build.prop method but am unsure if this would work.
tronic44522 said:
yes i have tried it as recommended.
when i browse /sd-ext i see 1423mib then the following dalvik-cache 76.7mib, app 66.4mib, system data 104.3 mib and freespace 1175mib
I also liked the guide on fast boot you sent me, as from using tips from it i was able to flash a new splash screen and boot animation. so thank you.
by side loading do you mean installing the apps with the apk file and not through the play store?
if so this works for some apps but now others. the app Im looking to use is the Argos app. before the recent update it worked fine but now when i went to update i get the device is incompatible message in play store. I have read some stuff on the build.prop method but am unsure if this would work.
Click to expand...
Click to collapse
Yep, all good, it's filling up so you have successfully added internal memory :good: plenty more space for apps.
Yeh that guide worked for me which is why I always recommend it. I liked changing the splash screen too (ironically can't be done on Nexus devices as far as I know)
Sideloading is as you described
The Argos app is compatible with Android versions 4.0 and higher as on the play store page, which is why it's incompatible with CM7 which is 2.3.x. The same probably applies to the other apps you're having trouble with. I've never messed with build.prop, probably could work, just make sure you make a nandroid backup before trying any of it.